Messages

This list contains messages produced by the components of the conversion tool, except those issued by various Control-M utilities which are described in the INCONTROL for z/OS Messages Manual.

A message code usually consists of the following parts:

CTMESPaa-nnx

where CTMESP indicates that the message pertains to the Control-M CA ESP Conversion Tool, where:

Table 4 CA ESP Control-M Conversion message parts

Message descriptions contain any or all of the following:

Explanation: Description of the cause of the message, and other related information.

System action: System action when this message is issued.

User response: Recommended actions to correct the problem.

CTMESP01-01W JOB= jobname TBL= tbl-name LIBL PARM TRUNCATED

Explanation: An ESP AS400 LIBL parameter value exceeded the maximum length supported by the conversion and was only partially converted.

System action: The values in the LIBL list are truncated.

User response: Manually update the LIBL list (in Control-M/EM) by adding all the truncated values.

CTMESP01-02W EVENT event OF NOTIFY STATEMENT IS NOT FOUND IN THE EVENT/TABLE NAMES CROSS REFERENCE LIST

Explanation: The event that appears in the NOTIFY... EVENT statement does not appear in the event-name to table-name mapping list. This list is extracted from the EVENTS file.

System action: The EVENT parameter of the NOTIFY statement is not converted. The program continues.

User response: Validate the event name of the NOTIFY statement or add an appropriate EVENT section in the EVENTS file.

CTMESP01-03W TBL=tbl-name, JOB=jobname, OPT: text ESP-procedure-library-name

Explanation: The conversion tool does not support the CA ESP option or element referred to in text.

If the unsupported element is an IF block, the display of the IF block in the message is determined by the IFBLKERR parameter — either all lines of the IF block or just the first line.

System action: The procedure or event containing the unsupported option is not fully converted.

User response: Manually complete the job conversion.

CTMESP01-04W TABLE=table, JOBNAME=jobname UNABLE TO RESOLVE VARIABLE IN TEMPLATE DEFINITION

Explanation: A variable defined in a CA ESP Template definition could not be resolved.

CTMESP01-06W TABLE=tablename JOBNAME=jobname INVALID CHARACTER ($) FOUND

Explanation: An ESP jobname contains a character ($), which is not a valid character for usage in jobnames in Control-M/EM.

System action: The conversion tool creates the job definition in Control-M with the ESP jobname as-is. When the XML created by the conversion is loaded to Control-M/EM, an error message will be generated for each such job.

User response: : Take appropriate action to rename the jobs. Condition names that depend on such job names must also be renamed.

CTMESP01-07W TABLE=tablename DSN=library-name, INVALID CHARACTER ($) FOUND IN NAME

Explanation: An ESP Application name contains a character ($), which is not a valid character for usage in folder names in Control-M/EM.

System action: The conversion tool creates the folder definition in Control-M with the ESP application name as-is. When the XML created by the conversion is loaded to Control-M/EM, an error message will be generated for each such folder.

User response: Take appropriate action to rename the folders. Condition names that depend on such folder names must also be renamed.

CTMESP01-09E TABLE=table-name. JOBNAME=jobname, UNABLE TO DECOMPOSE SQL DB_URL

Explanation: The conversion process is unable to interpret a SQL DB_URL statement.

System action: The statement is skipped, and the conversion process continues.

User response: Verify that the SQL DB_URL syntax is the following:

xxx :databasetype:host:port/databasename

CTMESP01-10E TABLE=table-name JOBNAME=jobname, NUMBER OF CONTROL RES/RBCS EXCEEDED control res name/status

Explanation: This message is issued in one of the following scenarios:

• The number of control resources exceeds 2000 per job.

• The number of rule-based calendars (RBC) exceeds 4000 per job.

System action: The program does not update the job definition with the excess resources/RBCs.

User response: Manually handle the processing of control resources or RBCs that were not processed.

CTMESP01-11W TABLE=table-name MISSING x in EVENT CMD

Explanation: The conversion encountered an error. An EVENT command in table table-name is missing a character (x), either a period or a closing parenthesis.

System action: Conversion continues normally.

User response: Check the converted table and ensure that the converted table is correct, or edit the original Event to avoid the problem.

CTMESP01-15W DUPLICATE JOB=jobname TBL= tablename

Explanation: The conversion tool job jobname was found more than once in the ESP application tablename.

System action: The program continues.

User response: Assign a qualifier name to the duplicate jobname. Note that IN/OUT prerequisite conditions for connected jobs will need to be adjusted.

CTMESP02-00I MESSAGES FOR jobname [.qualifier] tablename

Explanation: During the conversion process, at least one CA ESP feature could not be converted.

This informational message serves as a header message for the following error messages that detail the problems encountered during conversion of a CA ESP feature.

CTMESP02-01I JOB NAME short-jobname CORRESPONDS TO original-jobname

Explanation: In many cases the jobname of an ESP job may be too long for the conversion tool to properly process it. In such a case, the conversion assigns a short name of the format +xxxx to the job for all internal processing (including all error messages). The final output of the converted job in Control-M contains the job definition with its original job name restored.

This message informs you of the correspondence between the conversion-assigned short name and the original ESP job name.

CTMESP02-02W - EVENT event-name FOR NOTIFY/TRIGGER IS NOT FOUND IN EVENT/TABLE NAMES CROSS REFERENCE LIST

Explanation: The event name specified in the NOTIFY <event-name> / TR[IGGER] <event-name> ESP commands does not match any entries in the list of defined event names and their associated table names. As a fallback, the default ESP application name is used.

System action: The program proceeds normally.

User response: Ensure that the event is properly defined in the Events file, including an ESP invoke command that specifies the correct table name and its DSN. Rerun the conversion.

CTMESP02-03W UNSUPPORTED OPTION: text

Explanation: The conversion tool does not support the CA ESP parameter in text.

System action: The procedure/event containing the unsupported option is not fully converted.

User response: Manually complete the job conversion.

CTMESP02-05W MULTIPLE CTM JOB SCHEDULING DEFINITIONS MAY BE REQUIRED FOR RUN CRITERIA

Explanation: Due to the complexity of the CA ESP [NO]RUN/[NO]SCHEDULE or IF TODAY statements, the conversion tool most likely will not be able to accurately convert the keywords to a single Control-M job scheduling definition.

Most likely, multiple Control-M job scheduling definitions will be required to properly convert the CA ESP [NO]RUN/[NO]SCHEDULE statement.

User response: Examine the [NO]RUN/[NO]SCHEDULE statement to determine if a manual conversion is necessary (perhaps into multiple job scheduling definition).

System action: The event containing the specified statement is not fully (or properly) converted.

CTMESP02-06W EXTERNAL "HOME" JOB NOT FOUND

Explanation: The CA ESP EXTERNAL keyword on a JOB statement identifies to CA ESP that the job is part of another Application which allows the establishment of relationships between jobs in different Applications. However, the conversion was unable to find the ‘home’ application in which the job resides.

User response: No action is required.

CTMESP02-07W "DUPLICATE" JOB SCHEDULING DEFINITION MAY BE CREATED DUE "IF TODAY ELSE DO" LOGIC

Explanation: Due to the complexity of the ESP IF TODAY statements, the conversion tool most likely will not be able to accurately convert the keywords to a single Control-M job scheduling definition.

System action: A duplicate job definition with the scheduling criteria contained within the IF TODAY clause is created and any statements in the DO clause override the original parameters definitions in the duplicate job definition. Note that a negative RBC definition is placed into the original job definition to prevent the job from running on the same days as the duplicate job.

User response: Examine both the original job definition and its duplicate to ensure that the conversion was accurately done.

CTMESP02-08S ONSPOOL TABLE EXCEEDED, INCREASE MAXJOBS

Explanation: The number of job names and data set names in DSTRIG has exceeded the MAXJOBS conversion option.

System action: Program terminates.

User response: Increase the MAXJOBS conversion option in the SET ESP CONVERSION DEFAULTS OPTIONS panel and rerun JOB1.

CTMESP02-09E TRUNCATED PARAM/MAILBX VALUE- STRING TOO LONG

Explanation: An ESP parameter value (in a Command line, Argument, etc.) or mailbox value in a Notify statement exceeded the maximum length supported by the conversion.

System action: The too long value is truncated.

User response: For long mailbox names, truncate the name at '@' and use DFLTSFFX.

Alternatively, change the long (>12) mailbox names to short NICK or GROUP names (either pre-conversion or post-conversion) and define the NICK/GROUP name in the MAILDEST member of the IOA PARM lib. For more details, see The Mail Destination Table in the INCONTROL for z/OS Administrator Guide.

CTMESP02-11E - SEND MESSAGE TEXT EXCEEDS 70 CHARACTERS – TRUNCATED

Explanation: The length of the text defined in the SEND statement exceeds the maximum supported length of 70 characters.

System action: The conversion tool truncates the value.

User response: Manually modify the text (if necessary) and rerun the conversion.

CTMESP02-12W APPLEND/APPLSTART REQUIRES MANUAL INSERTION OF OUT/IN-CONDITIONS

Explanation: The ESP APPLEND/APPLSTART statement specifies a self-completing workload object and is used to automatically perform processing at the end of an application. The conversion converts the APPLEND|APPLSTART events as DUMMY jobs and with an IN-condition name of tablename-jobname-APPLEND|APPLSTARST.

User response: Add the above condition as an OUT condition to each job in an ESP procedure that contains an APPLEND|APPLSTART event when the jobs do not specify any successors (except for jobs that are triggered by the APPLEND|APPLSTART event).

CTMESP02-13E - VARIABLE IS UNDEFINED

Explanation: A conversion variable is not defined in the ESPDEF member of the conversion INSTWORK library. This is caused by a lack of synchronization between the conversion program and the ESPDEF member.

System action: The program terminates.

User response: Update the ESPDEF member of the ESP INSTWORK conversion library, by rerunning Stage 0 – Set Conversion Defaults of the ESP conversion from the ICE interface.

CTMESP02-14W MORE THAN ONE HOME JOB FOR JOB=jobname

Explanation: During conversion, more than one home job was detected.

System action: The first home job is associated with the external job.

User response: If necessary, manually associate the relevant home job with the external job.

CTMESP02-15E xxxx UNSUPPORTED APPL-LEVEL CONDITIONAL SCHEDULING CRITERIA (IF TODAY)

Explanation: Orphan CTMBLT scheduling parameters are suppressed.

An Orphan CTMBLT scheduling parameter xxxx may be any one of the following:

WDAYS, DAYS, DATES, MONTH, DCAL, WCAL, CONFCAL, SHIFT, EXT-SHIFT, RELATION, PERIOD

Orphan parameters may occur when an application-level IF TODAY(xxx) block contains statements other than ESP Job definitions or SELECT statements.

Orphan CTMBLT parameters often cause CTMBLT errors of the type 'MISPLACED PARMAETER' and subsequently cause a converted folder not to be created in the converted scheduling library.

User response: Manually manage such application-level conditional processing, either at a pre-conversion stage or a post-conversion stage.

CTMESP02-16W - EXTERNAL JOB WITH NO APPLID; RELEASE PROCESSED FOR 1ST HOME JOB ONLY

Explanation: An ESP external job without the APPLID attribute has been detected during the conversion process. You must specify the name of the APPLID for the external job, to determine the correct home job for creation of the Control-M condition link from the current job.

System action: If an APPLID is not specified for the ESP external job, the condition link is established only with the first home job of the possible home jobs. For more information about CA ESP EXTERNAL job handling, see 45. EXTERNAL, APPLID.

User response: Verify the input statement and add the APPLID attribute manually, if needed.

CTMESP02-17W - SCRIPTNAME IN IF-TODAY BLOCK IS IGNORED, MANUAL CHANGE IS NEEDED

Explanation: When a DS job contains an IF-TODAY statement with a SCRIPTNAME in its scope, the SCRIPTNAME is ignored. This is because, when an IF-TODAY statement is present in the ESP job definition, the conversion process generates a duplicate Control-M job definition, in addition to the original one, to reflect the scheduling logic implemented in the IF-TODAY statement. The name used for the duplicate job is the same as the original one. Therefore, any SCRIPTNAME, if present in the IF-TODAY clause, is ignored.

System action: The script name is ignored, and the program processing continues.

User response: Verify that the Control-M converted definitions reflect the expected behavior. If not, correct the input statement manually, considering that the original job name is used to generate both the original job definition and the duplicate one with the IF-TODAY scheduling logic.

CTMESP02-18W - RESOURCE resource IN RESOURCE FILE - UNSUPPORTED ATTRIBUTE: attribute

Explanation: A resource defined in the RESDEF file was defined with an unsupported attribute.

System action: Processing continues.

CTMESP02-19W - RESOURCE resource - NOT DEFINED IN THE RESOURCE FILE. SCHED: scheduling_table JOB: job

Explanation: A resource referred to in the definitions of a specific job in a specific scheduling table is not defined in the RESDEF file.

System action: Processing continues.

CTMESP02-20W - RESOURCE resource REFERRED BY SCHED: scheduling_table JOB: job HAS UNSUPPORTED ATTRIBUTE

Explanation: A resource defined in the RESDEF file and referred to in the definitions of a specific job in a specific scheduling table was defined with an unsupported attribute.

System action: Processing continues.

CTMESP02-21W - THE JCLLIB/TEMPLIB WAS FOUND AT JOB LEVEL AND IS NOT PROPAGATED TO ALL THE FOLLOWING JOB DEFS IN THE APPLICATION.

Explanation: This warning message notifies you that a JCLLIB or TEMPLIB statement was encountered in a job definition and not at the application level.

User response: If necessary, manually update the MEMLIB or OVERLIB parameter definitions in the current job and in the jobs that follow.

System action: The conversion treats the JCLLIB or TEMPLIB statement as a local job definition and the statement is not propagated to the subsequent jobs inside the application.

CTMESP02-22E – JOB jobname HAS A COND WITH "AND" RELATIONSHIP IN RELEASE/AFTER STATEMENT.

Explanation: The AND relation between the return codes inside the COND statement is not supported.

User response: Manually adjust the job definition, as necessary.

System action: The conversion produces the standard OUT condition.

CTMESP02-23W - RESOURCE resource-name REFERRED BY SHED appname JOB: jobname[.qualifier] RENAMED (ENDED WITH $)

Explanation: A trailing $ in the name of a quantitative resource was substituted with the first non-$ sign in the resource name.

System action: Conversion continues normally.

User response: No action required.

CTMESP02-24W – DEFAULT RESOURCE old-resource RENAMED TO new-resource

Explanation: A trailing $ in a default resource name was substituted with the first non-$ sign in the resource name.

System action: Conversion continues normally.

User response: No action required.

CTMESP02-25W – NOCHANGE WITH MISSING OR INVALID ARGUMENT – IGNORED

Explanation: A NOCHANGE parameter with unexpected syntax was detected in the WOBTRIG statement during the conversion process. The correct syntax is NOCHANGE(min), where min is the number of minutes that the file must remain unchanged to satisfy the monitor condition. The Maximum limit is 2,147,483,647.

System action: The NOCHANGE parameter is ignored, and the program continues.

User response: If necessary, manually correct the ESP NOCHANGE statement.

CTMESP03-01W - CTO RULE=Event-name INTERVAL REDUCED TO 999 MINUTES

Explanation: An ESP Event specifies a cyclic event whose cyclic interval exceeds 999 minutes.

System action: The interval is reduced to 999 minutes.

User response: Determine whether the above limitation is acceptable or the rule must be restructured.

CTMESP04-01E 4-DIGIT YEAR REQUIRED IN PARM

Explanation: The JCL PARM parameter for program CTMESP04 must be a 4-character year yyyy.

System action: The Step is terminated.

User response: Correct the PARM and rerun JOB1.

CTMESP06-01E text UNSUPPORTED SYMBOLIC VARIABLE DEF

Explanation: A statement from a symbolic variable file was not processed for one of the following reasons:

• The symbolic variable name is too long (exceeds 20 characters).

• The value of the symbolic variable could not be found.

• The end delimiter of the symbolic variable value could not be found.

• An unsupported statement was encountered (for example INTEGER or GENTIME).

User response: Determine if the symbolic variable is improperly specified and correct it. When necessary, unsupported statement must be handled manually.

CTMESP06-05S PROC TBL EXCEEDED, INCREASE MAXPROC

Explanation: The number of ESP procedures has exceeded the MAXPROC conversion option.

System action: Program terminates.

User response: Increase the MAXPROC conversion option in the SET ESP CONVERSION DEFAULTS OPTIONS panel and rerun JOB1.

CTMESP07-01E EVENT=event-name UNSUPPORTED MULTIPLE SUSPEND/RESUME STMTS WITH (CYCLIC) SCHEDULE STMT; ONLY 1 PAIR PROCESSED

Explanation: In an ESP event, a SCHEDULE statement was used together with multiple occurrences of one or both of the following statements: SUSPEND, RESUME.

The SUSPEND and RESUME statements are used to suspend and resume the execution window of an event based on scheduling criteria provided on the statements and are (usually) different than the scheduling criteria specified on the SCHEDULE statement. The conversion only processes the first occurrence of the SUSPEND and RESUME statements and ignores all other occurrences. Processing of the Events file continues.

User response: If necessary, manually modify the resultant Control-M rule.

CTMESP08-01E - UNABLE TO RESOLVE INVOKE MEMBER membname library-name IN PROCEDURE procname

Explanation: A symbolic variable in the member-name of an INVOKE statement could not be resolved.

CTMESP08-02S - MAXPROC OPTION EXCEEDED

Explanation: The number of ESP procedures has exceeded the MAXPROC conversion option.

System action: Program terminates.

User response: Increase the MAXPROC conversion option in the SET ESP CONVERSION DEFAULTS OPTIONS panel and rerun JOB1.

CTMESP08-03E - UNDEFINED SYMLIB symlib IN EVENT event-name

Explanation: The symlib specified in event-name could not be found in the ESP LISTSYML report.

System action: Program continues.

User response: Correct the LISTSYML report and rerun the job.

CTMESP08-04E - COPY OF SEQ FILE seq-invoke-filename FAILED IN table-name

Explanation: The sequential file was mistakenly paired with a PDS in the XLATDSN file or was specified by an unresolved symbolic variable.

System action: Program continues.

User response: Correct the XLATDSN file and rerun the job.

CTMESP08-05W - PROC MEMBER proc-member INVOKED BY MULTIPLE EVENTS

Explanation: The conversion tool adds the symbolic variable ESPEVENT=xxx (where xxx is the invoking event name) to all Procedures which are invoked by an ESP Event, hence any INVOKE statement in the procedure which, at run time, is dependent on its invoking event name will use the value of ESPEVENT inserted above (or some variant of it). Therefore, if a procedure is INVOKEd by more than one event, the conversion will use only the first matching event name it encounters to set ESPEVENT in the resolution of the INVOKE member name.

System action: Program continues.

CTMESP08-06W - INVOKE FILE invoke-filename NOT DEFINED IN XLATDSN

Explanation: The filename in an INVOKE statement (either in a Procedure or the Event file) was not specified in the XLATDSN file.

User response: Define the invoke-filename in the XLATDSN file and rerun the job (see JOB1 Input for details).

CTMESP08-07E - RECURSIVE INVOCATION OF dsn member-name NOT SUPPORTED

Explanation: An INVOKEd procedure contains a recursive invocation of a higher level INVOKE.

System action: the recursive INVOKE is ignored during the process of replacing the INVOKE with the contents of the invoked file/member.

CTMESP08-08E MAXIMUM (4) INVOKE NEST LEVEL EXCEEDED DSN=library-name MEMBER=member-name

Explanation: The conversion tool only supports 4 levels of nesting of INVOKE statements when resolving the contents of invoked members in ESP Events or procedures.

System action: INVOKES statements nested beyond 4 levels are not resolved.

User response: manually resolve any INVOKE statements exceeding the above limitation.

CTMESP08-09W MAXRUNTIME VARIABLE VALUE REDUCED TO 999 JOB=jobname

Explanation: The ESP MAXRUNTIME variable value exceeds 999 minutes.

System action: The program continues.

User response: The run-time variable value in the converted Control-M SHOUT statement is reduced to 999.

CTMESP08-10W - LONG JOB NAME, TRUNCATED TO 60 CHARS, JOB=jobname

Explanation: The jobname long job name is too long. The maximum length of an ESP LONGNAME is 64. In the Control-M conversion process, the maximum supported length of a job LONGNAME is 60. If it is longer, the job long name is truncated to 60.

The length of jobname is computed by the conversion prior to symbolic variable resolution. In the case of LONGNAMEs with variables, this can cause the maximum length to be exceeded, because the var names may be longer than the resolved values.

System action: The conversion process continues.

User response: Verify the input statement. If the implication of the job name truncation is not acceptable, correct the statement manually.

CTMESP08-11W - SYMBOL STATEMENT SPECIFIED, APPL=xxx JOB=yyy

Explanation: A SYMBOL statement has been encountered at the Application level (xxx) or job level (yyy) of an ESP procedure and is processed as described in Appendix E. However, the SYMBOL processing is not propagated to any corresponding JCL members associated with the Application or job.

User response: Replicate this functionality when necessary, either at a pre-conversion stage (for example, by adding a //*ESPSYMBOL statement to the appropriate JCL members) or post-conversion stage.

CTMESP08-12W - PROC MEMBER member DUPLICATED IN DIFFERENT PROC LIBS. THE MEMBERS ARE MERGED INTO THE SAME CONTROL-M TABLE.

Explanation: When an ESP procedure member is INVOKEd from different procedure libraries (with the same member name), the conversion merges them under the same table name and warns about it.

User response: If the merged table is unsatisfactory, separate the tables under different table names or create an alternative scheduling library that one of the tables can be moved into.

CTMESP08-13W - RESOURCE old-resource RENAMED TO new-resource job jobname [.qualifier]

Explanation: A trailing $ in the name of a quantitative resource was substituted with the first non-$ sign in the resource name.

System action: Conversion continues normally.

User response: No action required.

CTMESP08-14W - TEMPPROC FILE filename NOT DEFINED IN XLATDSN

Explanation: The filename in an TEMPPROC statement (in the Event file) was not specified in the XLATDSN file.

System action: The conversion tool replaces the filename with the filename specified in the INVOKE statement.

CTMESP09-08I PROCESSING ENDED FOR LIBRARY ds_name

Explanation: All the members of the JCL library ds_name have been processed.

User response: No action is required.

CTMESP09-09I MODIFICATIONS WERE DONE TO MEMBER memb DSNAME lib

Explanation: An informational message indicating that the conversion tool modified the memb JCL member.

CTMESP09-10W LIBRARY NOT IN THE EXTRACTED FILES AND CANNOT BE MODIFIED DSNAME= library-name

Explanation: The JCL library-name cannot be found in the tersed extracted files, and the conversion tool cannot convert the library-name.

System action: The program continues.

User response: Ensure that the JCL library is properly identified during ICE processing and rerun JOB2.

CTMESP09-11W DUPLICATE MEMBER NAME: membername DSN: library-name

Explanation: The conversion tool found member membername in more than one of the CA-ESP libraries.

System action: The program continues, after skipping the duplicate member.

User response: Make sure that you have not concatenated more than one CA-ESP library that contain members of the same name. If this is the case, each CA-ESP must be converted separately.

CTMESP09-12E – EVENT NAME TO PROC MEMBER NAME MAP FILE CAN’T BE OPEN. TR COMMANDS IN JCL MEMBERS CAN’T BE CONVERTED

Explanation: The EVENT NAME TO PROC MEMBER NAME MAP FILE (MEMEVTMP) links event names used by the TR[igger] command within the JCL members with their corresponding procedure name specified in an INVOKE statement in the EVENT definition in the EVENTS file. This message explains the program termination when the map file is not specified for generation in the JOB1 JCL (via the OUTMPEVT DD cards). This can occur if you have updated the conversion with the PTF that added this functionality, but did not refresh the JOB1 JCL via ICE.

System action: The program stops.

User response: Create and submit the most recent version of conversion JOB1 through the ICE interface to ensure that JOB1 JCL is updated. This generates the necessary map file DD cards.

CTMESP10-01E member text

Explanation: During conversion processing, a line in the member JCL member could not be converted. text is the JCL line in question.

System action: The indicated JCL line is not converted, but conversion processing continues.

User response: If necessary, manually convert the indicated JCL line.

CTMESP10-02E varname VARIABLE VALUE OVERFLOW

CTMESP10-02E - JCL LIBRARY: jcl-libraryname

Explanation: An attempt to convert a CA ESP variable to Control-M format failed because the converted variable value contained too many characters. This may happen when CA ESP variables contain embedded blanks that the conversion tool replaces with ‘%%BLANKnn%%, which usually expands the length of the variable value. This message now has two lines. The second line shows the JCL Library name.

System action: The variable value is incompletely converted.

User response: Manually convert the CA ESP variable to Control-M format.

CTMESP10-03W member JCL/DATA OVERFLOW FROM COL 71/80

Explanation: In converting a line in a JCL member, the conversion tool encountered data in column 71 (for lines beginning with //) or in column 80 (for lines not beginning with //), and this data will be lost.

When the conversion tool encounters a CA ESP % variable or a constant appended to CA ESP Variable the conversion tool converts the % variable to a Control-M AutoEdit %% variable or to the AutoEdit Concatenation symbol %%. This action causes the JCL line in question to expand, which can potentially cause data at the end of the line to be lost.

System action: Processing continues.

User response: Examine the JCL line in question and manually ensure that no data is lost or truncated.

CTMESP10-04W UTILITY=utility-name NOT SUPPORTED BY CONVERSION. JCL MEMBER: member-name LIBRARY: library-name.

Explanation: The conversion tool does not support the ESP utility-name in the JCL member.

System action: The utility in the JCL member is not converted, but the conversion processing continues.

User response: If necessary, manually convert the utility in this JCL member.

CTMESP10-05W JCL-MEMBER=member-name UNSUPPORTED DATA FOUND IN TRIGGER COMMAND.

Explanation: An unsupported TRigger subparameter was encountered on the Trigger command in the JCL member member-name. The conversion converts the TRIGGER statement to an in-stream invocation of the CTMAPI utility, which issues an ORDER command to order the Control-M scheduling table specified by the triggered event.

System action: The Trigger command is partially converted, and conversion processing continues.

User response: If necessary/possible, manually modify the CTMAPI utility.

CTMESP10-06W JCL MEMBER=member-name, SUBSYS PARM VALUE=parm-value NOT EQUAL TO LOCAL (ICE) SUBSYS VALUE=ICE-value

Explanation: The SUBSYS subsystem parameter in the JCL member is not equal to the local subsystem parameter specified in the ICE option LOCLESP (ESP FUNCTIONALITY SETTINGS).

System action: The conversion tool replaces the SUBSYS parameter in the JCL-member to the local SUBSYS parameter value specified in ICE.

CTMESP10-06I JCL MEMBER=member-name, MEM=table-name, ROOT KEYWORD INCLUDES JOBS: jobname

Explanation: An informational message indicating that a jobname was included in the ROOT KEYWORD of the Trigger command.

User response: None.

CTMESP10-07W JCL MEMBER=member-name, A ''+'' AT END OF JOBNAME IS NOT SUPPORTED

Explanation: The conversion tool does support a TRigger ROOT keyword that specifies “+” as a jobname suffix. This ESP functionality is not supported by the CTMAPI utility (see message CTMESP10-05W).

System action: The “+” suffix of the jobname is ignored.

CTMESP10-08W - JCL MEMBER jcl-member-name, UNABLE TO DETERMINE THE TABLE NAME TO ORDER, TRIGGER COMMAND NOT SUPPORTED.

Explanation: The conversion tool assumes that the event name is the same as the member name in its INVOKE statement for the TR (TRigger) command processing. If the event name is longer than 8 characters, this warning message is issued.

System action: The conversion tool skips this event name and processing continues.

User response: Consider modifying the event name (or its qualifier) so that it is shorter than 9 characters, and then rerun the conversion process.

CTMESP10-10W DATA SET NOT IN THE EXTRACTED FILES AND CANNOT BE MODIFIED DSNAME= library-name

Explanation: See CTMESP09-10W.

CTMESP10-12W SEQFILE CAN'T BE OPEN

Explanation: The conversion tool cannot open the sequential file specified in the SYSIN of an ESP Utility step.

System action: The sequential file is not converted to Control-M format.

CTMESP11-01I SCHEDULING TABLE=tablename UPDATED WITH RBC=rbc-name CYCLIC SPECIFIC RUNTIME(S)=time

Explanation: An RBC is added to the table-entity of tablename, reflecting the scheduling criteria specified in the ESP Event that Invokes this table. When an Event specifies multiple SCHEDULE statements or multiple CA-ESP events specify INVOKE (DO FORCEJOB) of the same CA-ESP procedure and the SCHEDULEs/Events have the same scheduling criteria and different FROM times, then instead of adding another (duplicate) RBC to the corresponding converted Control-M, the table is turned into a Cyclic table using the enhanced cyclic specific run times feature.

User action: None.

CTMESP11-02W TIME IGNORED=time AND/OR INTERVAL IGNORED

Explanation: Multiple ESP Event rules that INVOKE the same procedure but have different scheduling criteria cause multiple schedule RBCs to be added to the corresponding table definitions. In such a case, if the multiple ESP Events also have different FROM times specified, then the above warning message is issued about the different times.

System action: The RBC is added to the Control-M table and a warning message is issued.

CTMESP11-03S TABLE-ENTITY=table-name CORRUPTED

Explanation: A severe error occurred during processing of the job scheduling library.

User response: Prepare a tersed package of all the conversion inputs and contact BMC Software.

CTMESP11-03W EVENT OWNER/USER owner PROPAGATED ON DISTRIBUTED JOB jobname

Explanation: The conversion tool propagated either the owner-qualifier or value of the USER(owner) keyword parameter to the distributed job jobname from the Event that invokes the table that contains the job, since the ESP job definition or the application that it is in did not contain a USER parameter.

User response: Investigate the appropriateness of the conversion action.

CTMESP12-00I MESSAGES FOR jobnamex[.qualifier] tablename

Explanation: During the conversion process, at least one CA ESP feature could not be converted.

This informational message serves as a header message specifying the jobname and tablename that apply to the following error messages that detail the problems encountered during conversion of a CA ESP feature.

CTMESP12-03W UNSUPPORTED OPTION: text

Explanation: The conversion tool does not support the CA ESP parameter in the text.

System action: The procedure/event containing the unsupported option is not fully converted.

User response: Manually complete the job conversion.

CTMESP13-00I MESSAGES FOR jobname.qualifier tablename

Explanation: During the conversion process, at least one CA ESP feature could not be converted.

This informational message serves as a header message specifying the jobname and tablename that apply to the following error messages that detail the problems encountered during conversion of a CA ESP feature.

CTMESP13-03W UNSUPPORTED OPTION: text

Explanation: The conversion tool does not support the CA ESP parameter in the text.

System action: The procedure/event containing the unsupported option is not fully converted.

User response: Manually complete the job conversion.

CTMESP13-04W EXCLUDE RBC NOT CREATED FOR NEGATIVE JOB= jobname

Explanation: Due to a complex ESP RUN REF NOT jobname clause, the conversion tool was unable to create a negative RBC corresponding to it.

User response: Review the converted job definition and, if necessary, adjust the scheduling criteria or job’s RBCs accordingly.

CTMESP13-05W - MULTIPLE CTM JOB SCHEDULING DEFINITIONS MAY BE REQUIRED FOR RUN CRITERIA

Explanation: Due to the complexity of the CA ESP [NO]RUN/[NO]SCHEDULE or IF TODAY statements, the conversion tool will probably not be able to accurately convert the keywords to a single Control-M job scheduling definition. Most likely, multiple Control-M job scheduling definitions will be required to properly convert the CA ESP [NO]RUN/[NO]SCHEDULE statement.

User response: Examine the [NO]RUN/[NO]SCHEDULE statement to determine if a manual conversion is necessary (perhaps into multiple job scheduling definitions).

System action: The event that contains the specified statement is not fully (or properly) converted.

CTMESP13-09E - UNSUPPORTED PARAMETER VALUE- STRING TOO LONG

Explanation: A string that is too long has been detected during the conversion process. The maximum length of the internal buffer to process ESP parameters/values is 156.

System action: The parameter is skipped, and the process continues.

User response: Verify that the Control-M converted definitions reflect the expected behavior. If not, manually correct the input statement, considering that the maximum length of the internal buffer to process ESP parameters/values is 156.

CTMESP14-01I - RBC rbc-name UPDATED

Explanation: The Control-M level RBC, identified by the rbc-name, has been created in the IOA RBC library.

System action: The process continues.

User response: None.

CTMESP14-02E - RBC rbc-name JOB NOT FOUND.

Explanation: An internal error occurred while creating the RBC identified by the rbc-name, during the conversion process.

System action: The process continues.

User response: Contact BMC support and provide all the information listed in Problem Reporting.

CTMESP14-03S - TABLE-ENTITY table-name CORRUPTED

Explanation: The conversion process detected a corrupted table entity due to internal errors; it is not a SMART table.

System action: The process terminates.

User response: Contact BMC support and provide all the information listed in Problem Reporting.

CTMESP16-01I USER=username NOT FOUND IN JCL. SCHED TABLE: table-name JOB: jobname

Explanation: This informational message indicates that the conversion tool cannot find the username in the JCL. This username is referred to in the specific scheduling table and job.

System action: The scheduling definition is not updated. The program continues processing.

User response: Update the username in the JCL and rerun the job.

CTMESP16-02E USER=username CONTAINS A VAR NAME. SCHED TABLE: table-name JOB: jobname.

Explanation: The user parameter in the JCL contains a variable.

System action: The program does not update the job definition.

CTMESP16-03W - A NUMBER OF LIBS CONTAIN MEMBERS WITH THE SAME NAME. SCHED TABLE: table-name JOB: job-name

Explanation: See message CTMESP16-03I.

CTMESP16-03I - USER=username IS TAKEN FROM library-name(member-name)

Explanation: The conversion determined that a job scheduling definition OWNER parameter must be modified according to the USER specified in a JCL member JOB statement. However, the conversion discovered that there are multiple JCL members with the same jobname, and chose the username from library-name(member-name).

User response: If necessary, change the username.

CTMESP16-04E – MEMLIB=library-name NOT DEFINED IN XLT. SCHED: table-name JOB: jobname.

Explanation: This error message indicates that the MEMLIB=library name was not defined in the DSNXLT library.

System action: The program stops processing the table.

User response: Define the MEMLIB in the DSNXLT and rerun the job.

CTMESP16-05E - DDNAME=ddname KEYWORD NOT SUPPORTED. SCHED: table-name JOB: jobname ADJUST THE USER FIELD MANUALLY.

Explanation: This warning message indicates that the scheduling definition contains MEMLIB=DDNAME=ddname, this MEMLIB format is not supported during the OWNER update phase of the conversion process.

System action: The scheduling definition is not updated. The program continues processing.

CTMESP16-06I - THE TABLE=table-name, HAS BEEN UPDATED.

Explanation: This informational message indicates that the conversion tool updated TABLE=table-name.

CTMESP16-07I - JCL MEMBER NOT FOUND. SCHED TABLE: table-name JOB: jobname.

Explanation: This informational message indicates that the conversion tool cannot find the JCL-member in JCL SCHID table-name.

System action: The scheduling definition of the job referred to by the message is not updated. The program continues processing.

CTMESP16-08W - SCHEDULING LIBRARY IS EMPTY

Explanation: This warning message indicates that the scheduling library is empty.

CTMESP16-09E - IOAMEM ERROR. RC: return_code RSN: reason_code FUNCTION: function MEMBER: member

Explanation: For more information about this error, see the list of return codes and reason codes for the IOAMEM Assembler Macro in the INCONTROL for z/OS Administrator Guide.

System action: The program does not update the job definition.

CTMESP16-10E - CONVERSION PACKAGE DOES NOT CONTAIN JCL LIBRARIES

Explanation: The JCL libraries are not defined in ICE.

System action: The program terminates.

User response: Add the conversion package to the ICE JCL libraries and rerun the job.

CTMESP18-01W - THE VARIABLE VALUE LENGTH EXCEEDS THE LIMIT. var-value

Explanation: The conversion process detected a variable value, var-value, that exceeds the length limit of 71.

System action: The output string is truncated, and the process continues.

User response: Verify the input variable and manually decrease its length, if needed.

CTMESP99-02E function FAILED FOR BLOCK blockname [MEMBER=member DDNAME=ddname]

Explanation: A MVS memory acquisition (GETMAIN) or free (FREEMAIN) function failed for block blockname. The JCL REGION parameter specification is not large enough.

User response: Increase the value of the REGION parameter for the failing step and reru[LIBRARY]n the job.