Messages

This list contains messages produced by the components of the conversion tool.

A message code usually consists of the following parts:
CTMyyynnx
where CTM indicates that the message pertains to Control-M, and where:

Item	Explanation
yyy	3-character identifier of the conversion tool component that produced the message.
nn	2-character numeric identifier for the message
x	1-character alphabetic identifier for the severity of the message, as follows: A: Action E: Error I: Information S: Severe W: Warning.

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.

BCLnnnS msg txt

Explanation: An error occurred in the IOABLCAL utility.

The IOABLCAL utility is invoked when necessary during conversion, to combine two calendars. It is invoked by the CTMOP008 program. For details of this utility, see the INCONTROL for z/OS Utilities Guide.

BCLnnn messages are generated by the utility, not the conversion programs. nnn represents any message code issued by the utility. All BCL messages are individually documented and explained in the INCONTROL for z/OS Messages Manual.

System Action: Processing continues. However, the validity of succeeding calendars built by the conversion cannot be guaranteed until all errors have been resolved.

User Response: Check the INCONTROL for z/OS Messages Manual for the meaning of the specific message, and perform the corrective action indicated. Then rerun the job.

BLTnnnx ctmblt-message

Explanation: An error occurred in the Control-M CTMBLT utility. The CTMBLT utility is invoked during the conversion, to build tables. For details of this utility, see the INCONTROL for z/OS Utilities Guide.

BLTnnn messages are generated by the CTMBLT utility, not by the conversion programs. nnn represents any message code issued by the utility. All BLTnnn messages are individually documented and explained in the INCONTROL for z/OS Messages Manual.

Message BLT899E, specifying MISPLACED KEYWORD PARAMETER GROUP-ENTITY, most likely indicates that a duplicate table name has been encountered during the conversion process.

System Action: Processing continues. However, the validity of the current table built by the conversion cannot be guaranteed until all errors have been resolved.

User Response: Check the INCONTROL for z/OS Messages Manual for the meaning of the specific message, and perform the corrective action indicated. Then rerun the job.

For message BLT899E (parameter GROUP-ENTITY), ensure that all table names constructed by the conversion tool are unique. Use parameter TBLUNIQ (see Conversion Parameters) for this purpose.

BLT89DI NO JOB DEFINITIONS SELECTED BY "SEL" CRITERIA

Explanation: An error occurred in the CTMTBUPD utility.

The Control-M CTMTBUPD utility is invoked to process OPC rule-based run-cycle scheduling criteria, and to update the Control-M tables created in a previous step of the job. For details about this utility, see the INCONTROL for z/OS Utilities Guide.

BLTnnn messages are generated by the utility, not by the conversion programs. nnn represents any message code issued by the utility. All BLT messages are individually documented and explained in the INCONTROL for z/OS Messages Manual.

During OPC conversion, message BLT89DI is usually produced when an OPC application contains more than 32 run-cycle definitions, which is not supported by the conversion tool.This causes the SMART Table to be created without any Rule-Based Calendars, and therefore the SEL selection criterion is not satisfied.

System Action: Processing continues. However, the validity of the table built by the conversion cannot be guaranteed until all errors have been resolved. The step terminates with a return code of 8.

User Response: Check the INCONTROL for z/OS Messages Manual for the meaning of the specific message, and perform the corrective action indicated. Then rerun the job or manually update the affected table scheduling definition.

CTMOP002-00E - RESMAX CONVERSION OPTION EXCEEDED

Explanation: The maximum number of OPC special resources whose names exceed 20 characters has been exceeded. This maximum number is defined in the RESMAX conversion default options.

User Response: Increase the value of the RESMAX conversion option and rerun JOB1.

CTMOP002-02E - WSMAX PARAMETER EXCEEDED

Explanation: The maximum number of workstations, as defined in the WSMAX conversion option, has been exceeded.

User Response: Increase the value of WSMAX and rerun JOB1.

CTMOP002-08W - APPLID: appl CONTAINS 0 OPERATIONS. SMART TBL WILL CONTAIN 0 JOBS.

Explanation: An OPC application is defined with no operations in it. The conversion converts it to a Control-M SMART Table containing a SMART Table Entity only, without any job scheduling definitions. Empty SMART Tables are created only in the scheduling library initially created on the mainframe, but not in the XML that is exported to CTM/EM. As a result, such SMART Tables may be subsequently lost.

User Response: If the IOA Profile variable PGRPEMPT is set to No, Control-M Screen 2 expects every SMART Table to contain at least one job. Set PGRPEMPT to Yes or add a dummy job definition to the table.

CTMOP002-17S - OPERATION WORK STATION DOES NOT EXIST FOR APPLICATION ID appl WORKSTATION/OPERATION NAME wsname

Explanation: Workstation wsname comprises part of an Operation name for application appl, but it does not exist in the Workstation Report

Operation names for each application are listed in the Application Detail report. An Operation name is composed of both a workstation ID and an operation code. Any workstation ID that comprises part of the Operation name in an application must appear in the Workstation report.

System Action: The program ends with a return code of 12.

User Response: Check the indicated application in the OPC Application Detail report. Add the missing workstation definition using OPC, recreate the Workstation Report, and then rerun the conversion.

CTMOP002-18E - RUN CYCLE rcycname WAS NOT PROCESSED FOR APPLICATION ID appl

Explanation: Either the appl application has more than 32 run cycles (if rcycname is blank) or the rcycname run cycle (period) does not exist in the OPC Period reports.

System Action: If rcycname is blank, only one Control-M job scheduling definition is created for the application, and it does not contain any scheduling information. If rcycname does not exist in the Period report, the run cycle is ignored in creating the Control-M job scheduling definition for the application.

User Response: If rcycname is blank, reduce the number of run cycles to 32 or less. Otherwise, define the rcycname run cycle and produce the Period report again, or delete the run cycle definition from Application appl. In either case, produce the Application Detail report again, and rerun the conversion.

CTMOP002-19W - APPL: appl , ONLY NEGATIVE RUN-CYCLES WERE DEFINED.

Explanation: This warning message indicates that the application contained only negative run-cycles.

CTMOP002-20W - APPL=appl ,QUANTITY OF SPECIAL RESOURCE IN A JOB quantity TOO LARGE. 9999 WILL BE USED.

Explanation: Special resources quantity in the job exceeded 4 digits.

System Action: The maximum quantity that will be taken is 9999.

CTMOP003-10E - APPLID: applid1 NOT FOUND IN APPL TABLE. APPL ID: applid2 USED

Explanation: The full 16 character application ID applid1 was not found in the application table built from the OPC Report.

The probable cause is that old Application ID applid1 in the Application Names table has been modified (which is not permitted), or applid1 is named as an internal or external predecessor of an application but was never defined to OPC as an application.

System Action: The first eight characters of the application ID are used in constructing a Control-M schedule table name for use in a converted condition name.

User Response: Correct the Application Name file and rerun the conversion, or define applid1 as an application to OPC and rerun the conversion.

CTMOP003-11W - COMPOSITE CALENDAR BUILT FOR RBC rbc-name IN TABLE table-name,FREEDAY=x,OFFSET=offset

Explanation: An OPC Application contains a run-cycle which specifies an unsupported combination for Freeday rule and Run offset (+/-nnn). A composite calendar incorporating the scheduling criteria of the freeday rules and offsets of the run cycle is built.

System Action: Processing continues.

User Response: No user action is required.

CTMOP003-12W - MULTIPLE RUNCYCLES WITH DIFFERENT ARRIVAL TIMES IN APPL appl-id

Explanation: This message indicates that a TWS Application had more than 1 run-cycle, but not all of them had the same arrival times. When multiple normal/regular run cycles are specified for an application, and they have different arrival and deadline times, the application is converted to a cyclic table using the enhanced cyclic specific run times feature (see 27. Rule/Period Name). However, in some circumstances, usually when mixed (both offset-based and rule-based) run cycles are specified or when the run cycles specify different runs days/rule definitions, the application cannot be successfully converted to a cyclic table and this message is produced. In such cases, the conversion tool uses the arrival and deadline time of the last run cycle for the Control-M FROM and DUE-OUT times. The last arrival and deadline time is also used for operations that do not specify their own arrival and deadline times.

System Action: Processing continues.

User Response: The user should manually create the proper scheduling criteria. In many cases, this may involve creating a copy of the original scheduling table with alternate scheduling criteria to allow the table to be ordered multiple times on some of its scheduled days, when necessary.

CTMOP003-21I - quantitative resources | nnnn

Explanation: OPC Special Resources that have quantity larger than 1 (or all Special Resources if parameter SPECCND=Q), are converted to Control-M Quantitative Resources. At the end of the conversion, a list of all Quantitative Resources that are used by jobs created by the conversion, is produced, each resource with the highest value used by any single job. This list should be used as the base for a daily job that would reset the quantity of each quantitative resource to the initial value.

System Action: None.

User Response: Build the daily job based on the information supplied by all occurrences of this message.

CTMOP005-03S - APPL ID: appl MATCHING RUN CYCLE FOR THIS APPLICATION DOES NOT EXIST IN CALENDAR NEW NAME TABLE

Explanation: The Calendar Names file has probably been incorrectly modified.

System Action: Processing terminates.

User Response: Correct the Calendar Names file and rerun the job.

CTMOP007-05E - MORE THAN 15 NEGATIVE RUN CYCLES ARE ADDED TO NEW CALENDAR cal

Explanation: Calendar cal has more than 15 negative run cycles associated with it.

User Response: Edit the Calendar Names file to ensure that calendar cal has no more than 15 negative run cycles associated with it.

CTMOP007-07E - DUPLICATE CALENDAR NAME – cal

Explanation: In the process of converting an OPC calendar name to a Control-M calendar name, the name encountered in the Calendar Names file was a duplicate of a previously processed name.

Control-M calendar names must be unique.

User Response: The Calendar Names file was illegally modified. Correct and rerun the job.

CTMOP007-09E - CALENDAR NAME IS NOT A LEGAL NAME: cal

Explanation: While processing an OPC calendar name, the name encountered was blank or not a legal PDS member name.

User Response: Modify the problematic name in the Calendar Names file and rerun the job.

CTMOP008-01E - CALENDAR cal HAS TOO MANY PERIODS, AND MUST BE MANUALLY ADJUSTED

Explanation: The conversion program supports a maximum of 62 periods per calendar. This limit has been exceeded for calendar cal.

User Response: Reduce the number of periods for calendar cal and rerun the conversion, if possible. Otherwise, contact BMC Technical Support.

CTMOP008-07S - MISSING PERIOD REPORT FOR CALENDAR calendar-name (TRYING TO READ period-name)

Explanation: An OPC period-name specified in a Rule-based run-cycle PERIOD parameter was not found in any of the input OPC Period Reports.

User Response: Either add the Period Report, which contains the period name, to the Rule-based run-cycle, or correct the period name in the run-cycle to refer to an existing period, and then rerun the conversion.

CTMOP008-08E - COMBINATION OF OLD CALENDAR cal AND OLD PERIOD per DOES NOT EXIST IN CALENDAR TABLE.

Explanation: A new calendar could not be built for period per because calendar cal was not found in the Calendar Names file.

The probable cause is that the Calendar Names file has been incorrectly modified.

User Response: Correct the Calendar Names file and rerun the job.

CTMOP008-09I - OLD CALENDAR cal DOES NOT EXIST IN CALENDAR TABLE

Explanation: A new calendar could not be built by the IOABLCAL utility (using an existing period) because calendar cal was not found in the Calendar Names file (CALNAME). For details, see the INCONTROL for z/OS Utilities Guide.

Probable causes for this message are:

• When the message suffix is E (error): the Calendar Names file has been incorrectly modified.

• When the message suffix is I (informational): the cal calendar was not specified in any OPC application defined in the Application Detail report

System Action: Processing terminates or continues depending on the message suffix.

User Response: The response depends on the cause, as follows:

1. When the message suffix is E: Check the Calendar Names file, make any necessary corrections, and rerun the job.

2. When the message suffix is I: If the cal calendar was not specified in any OPC application defined in the Application Detail report, it is not required by the conversion. In such a case, this message can be ignored.

CTMOP008-10E LAST CHAR OF newcal IS NOT NUMERIC. IT WILL BE SKIPPED

Explanation: While processing the CAL.NAMES dataset, the conversion tool encountered a NEW CALS name that does not end with a numeric character. This could result in duplication of calendar names in the conversion process. The calendar name is skipped.

System Action: The NEW CAL name is skipped, and processing continues.

User Response: If you changed the original NEW CAL names in the CAL.NAMES library, ensure that all the NEW CALS names end with a numeric character.

CTMOP008-15E - FINAL NEGATIVE CALENDAR cal NOT CREATED BECAUSE ONE OF THE COMBINED CALENDARS DOES NOT APPEAR IN CALENDAR TABLE

Explanation: New calendar cal could not be built by the IOA IOABLCAL utility because either the NORMAL or NEGATIVE (that is, one of the negative run cycle components) calendars used as input to the utility could not be found in the Calendar Names file.

The probable cause is that the Calendar Names file has been incorrectly modified. See the discussion of the Calendar Names file in JOB1: Extract Workstation and Application Info.

User Response: Correct the Calendar Names file and rerun the job.

CTMOP012-01E - APPL ID appl OPER ID operid NOT IN XRF TABLE. INSTRUCTION TEXT IGNORED

Explanation: No DESC parameters were created because the appl application name was not found in the cross reference job table built from the OPC report.

User Response: Create operation operid in application appl, recreate the Application detail report, and rerun the conversion. Alternatively, the user can ignore this message if the operation operid in application appl is no longer valid.

CTMOP012-02E - INCREASE CONVERSION OPTION JOBMAX

Explanation: The maximum number of jobs in OPC, as defined by the JOBMAX default conversion option, has been exceeded.

System Action: Processing terminates.

User Response: Increase the value coded for JOBMAX to a number greater than the number of records in the cross reference report created in JOB1, and rerun the failing job.

CTMOP014-08I - PROCESSING ENDED FOR LIBRARY

Explanation: This information message indicates that a JCL library conversion process has ended.

CTMOP014-09I - MODIFICATIONS WERE DONE TO MEMBER memname LIBRARY libname

Explanation: This information message indicates that JCL member memname has been modified. Note that lines may have been deleted without conversion from the memname member due to their function not being supported by the converted Control-M utility.

CTMOP015-00E JOB jobname, OPC BATCH COMMAND cmd COULD NOT BE CONVERTED, RC=rc

Explanation: In the process of converting the OPC or PSS JCL library to Control-M format, the conversion tool encountered an error in trying to process a library member. The member in which the error occurred (jobname) is displayed in the message.

Some typical error situations are:

• In an OPC Batch utility step, the SYSIN file referred to a dataset which could not be processed or to a PDS member which could not be found.

• An error occurred in processing a CLIST library when trying to determine whether a %name parameter was an OPC variable name or a CLIST command.

System Action: Processing continues.

User Response: Manually convert the unsupported command.

CTMOP015-01E - member line-in-error

Explanation: In the process of converting the OPC or PSS JCL library to Control-M format, the conversion tool encountered an invalid or unsupported command or JCL directive.

The member in which the error occurred and the member line in questions are displayed in the message.

Some typical error situations are:

• An unsupported OPC JCL directive was encountered

• An unsupported PSS JCL comment statement was encountered

• SRTAT command, the special resource name is not enclosed in quotes

• In an OPSTAT command, ADID, or JOBNAME is not specified, or a STATUS other than C was specified

System Action: Processing continues.

User Response: Correct the invalid command or manually convert the unsupported command or directive.

CTMOP015-03W - member-name RESNAME=resource-name DOES NOT EXIT IN OPC DATABASE

Explanation: In the process of converting the OPC JCL library to Control-M format, the conversion tool encountered the following situation in an OPC JCL member: An OPC SRTAT command specifies a special resource name whose length exceeds 20 characters, however, no matching special resouce name could be found in the OPC Application Detail (AD) report. The member in which the error occurred and the special resource name are displayed in the message.

System Action: The SRSTAT command is ignored and processing continues.

User Response: Correct (or delete) the special resource name in the SRSTAT command and rerun the JCL conversion.

CTMOP015-06E -memberline-in-error

Explanation: In the process of converting the OPC JCL library to Control-M format, the conversion tool was unable to convert an OPC variable to Control-M AutoEdit format in an OPC JCL member. The error occurs because the OPC variable &varname cannot be expanded to the AutoEdit equivalent %%varname due to insufficient blanks on the line. Even where sufficient blanks apparently exist on the line to accommodate the expansion, the error might be produced when specifying ICE conversion option SHIFTEND=Y and the number of trailing blanks on the line are insufficient, for example, a JCL data line that contains TSO sequence numbers in columns 73-80. The member in which the error occurred and the member line in question are displayed in the message.

System Action: The JCL line is ignored and processing continues.

User Response: Try specifying the ICE conversion option SHIFTEND=N and rerun the JCL conversion.

CTMOP015-07W -membername tablename MEMSYM NAME MAY NOT EXIST OR MAY BE INCORRECTLY RESOLVED AT RUNTIME

Explanation: In the process of converting the OPC JCL library to Control-M format, the conversion tool produced message CTMOP1505E above. The member in which the error occurred and the member line in questions are displayed in the message. The name in a TWS SEARCH/TABLE directive might not exist in the JCLVAR file or the name contains symbolic variables that are only resolved at run time and might result in an AutoEdit %%INCMEM name exceeding 8 characters.

System Action: Processing continues.

User Response: Ensure that the %%INCMEM name points to an existing member in the %%INCLIB library (created from the TWS JCLVAR file).

CTMOP015-08W -membername SET STMT VARIABLE NAME UNRESOLVED: line-in-error

Explanation: In the process of converting the OPC JCL library to Control-M format, the conversion tool encountered an unsupported SET statement variable name which contains a '&' prefix and/or embedded delimiter (for example, '.'). The member in which this occurred and the line in question are displayed in the message.

The remainder of the SET statement is processed normally.

System Action: Processing continues.

User Response: Examine the SET statement and make any necessary changes.

CTMOP015-09W ALTWS WILL BE IGNORED, NOT SUPPORTED IN CONTROL-M.

Explanation: While processing the OPC JCL library, the conversion tool encountered an OPC WSSTAT command with an ALTWS parameter.

This parameter requests to move the workload to another workstation if the original workstation is set offline. As no similar concept exists in Control-M, the ALTWS parameter will be ignored.

System Action: The ALTWS parameter is ignored, and processing continues.

User Response: Verify that the conversion of the WSSTAT command reflects your expectations.

CTMOP015-10W ?-VARS IN A LINE ARE NOT PROCESSED IN MEMBER member-name AND MAY BE COLUMN SHIFTED

Explanation: During the conversion of JCL libraries, if a line contains multiple ?-Variables, only the first variable is processed.

However, if there is a single blank space after the first ?-Variable, it is not processed.

Substitution of ?-Variables with %%Variables may result in right-shifting of the text in these lines.

System Action: Processing continues. The converted JCL member may not be valid.

User Response: Perform corrective actions. Then rerun the job.

CTMOP015-11E - MEMBER= member name. INVALID ADID VALUE application name IN OPSTAT COMMAND – IGNORED.

Explanation: While processing the OPC JCL library, the conversion tool encountered the following situation in an OPC JCL member: an OPSTAT ADID keyword contains a wrong application name. Verify that the application name is not longer than 16 characters.

System action: The OPSTAT ADID keyword is ignored, and the processing continues.

User response: Verify the name of the application referred to in the ADID. It is not valid because the OPC applications names cannot be longer than 16 characters.

CTMOP015-12W - NOP DIRECTIVE FOUND AFTER JOB CARD IN MEMBER membername - PLEASE VERIFY THE CONVERTED JCL OR EDIT THE ORIGINAL MEMBER

Explanation: An OPC NOP directive was found but it was not placed before the JOB card.

System Action: Conversion continues normally.

User Response: Check the converted JCL and ensure that it is correct, or edit the original JCL and place the NOP directive before the JOB card.

CTMOP016-01E - WRONG CALENDAR STRUCTURE

Explanation: A Control-M calendar has been created without a full year span in the Calendar and Period reports.

System Action: Processing terminates.

User Response: Ensure that the calendars in the reports are defined for a full year.

CTMOP017-01W JOB member-name NOT FOUND IN XREF FILE OR NOT IN SCHEDULING TABLES

Explanation: While processing the OPC JCL library, the conversion tool encountered the following situation in an OPC JCL member: An OPC RECOVER directive was specified in JCL member member-name, however, no matching job name could be found in the Control-M Scheduling Library created from the OPC Application Detail (AD) report. The member in which the error occurred is displayed in the message.

System Action: The RECOVER directive is ignored and processing continues.

User Response: Verify whether the JCL member is an active OPC job, define the OPC job definition, if necessary, and rerun the OPC Conversion.

CTMOP018-01E %%variable-name VARIABLE VALUE OVERFLOW IN TABLE appl-id

Explanation: A TWS variable defined in the JCLVAR report has a value that exceeds the limit of Control-M AutoEdit variable length. This is usually due to embedded blanks in the variable value that must be expanded to the system AutoEdit variable %%BLANKn.

System Action: Processing continues.

User Response: Adjust the AutoEdit variable value.

CTMOP019-02E: job-name NON-SUPPORTED DS JOBTYPE

Explanation: While processing the OPC JCL library, the conversion tool encountered a DS job with a JOBREC clause containing an unsupported JOBTYPE parameter.

System action: The job is converted to a dummy job.

User response: No particular action is required.

CTMOP019-03W: MEMBER member-name DOES NOT EXIST IN JCL LIB

Explanation: While processing the OPC JCL library, the conversion tool encountered a member that is not present in any of the specified OPC JCL libraries.

System action: The processing continues.

User response: Verify that the job is a part of the conversion and copy it to the JCL library.

CTMOP019-04I: //*%OPC DIRECTIVE INTERCEPTED IN job_name DISTRIBUTED JOB.

Explanation: While processing the OPC JCL library, the conversion tool encountered an OPC directive in a distributed job.

System action: The //*%OPC directive is copied to the converted script, and the processing continues.

User response: The convert_linux_jcl.py utility must be run as post conversion processing.

CTMOPCCF-01E: DATE FORMAT date_format NOT SUPPORTED. REFER TO THE OPC CONVERSION GUIDE FOR USER RESPONSE.

Explanation: While processing the OPC PARMFILE, the conversion tool encountered an unsupported date format in the OPC BATCHOPT DATEFORM parameter.

System action: Processing terminates.

User response: Modify the OPC DATEFORM parameter in the BATCHOPT member of the OPC Installation PARM library to specify a valid date format and reproduce the OPC reports.

Valid formats are:

• DDMMYY

• DDMMYYYY

• YYMMDD

• MMDDYY

• MMDDYYYY

• YYYYMMDD

• YYDDD

Default: DDMMYY

Delimiters can be present between Year, Day, and Month. The delimiter can be any character other than C, Y, M, or D.

CTMOPnnnE BAD RC[=rc] FROM routine [FOR val AREA/FUNCTION] [mem]

Explanation: One of the following routines failed: GETMAIN, FREEMAIN, or SORT.

This description applies to the CTMOP305E, CTMOP307E, CTMOP401E, CTMOP810E, CTMOP1204E, and CTMOP1401E messages.

The return code, when present, is rc.

For GETMAIN, val is the area that the program attempted to obtain.

User Response: If a GETMAIN error occurred, increase the REGION size. For the other functions, take appropriate action based on the return code.

CTMOPGRP-01W APPLICATION ID applid. GROUP DEFINITION group-def DOES NOT EXIST IN APPL FILE

Explanation: The Group Definition ID group-def was not found in the OPC Application Detail Report.

System Action: The scheduling criteria of application applid are not modified and processing continues.

User Response: Correct the Application Detail file and rerun JOB2, or define the Group Definition group-def as an application to OPC and rerun the conversion.

CTMOPPSS-02E member line-in-error

Explanation: In the process of converting the OPC or PSS JCL library to Control-M format, the conversion tool encountered an invalid or unsupported command or JCL directive.

The member in which the error occurred and the member line in questions are displayed in the message.

A typical error situation is where an unsupported PSS JCL comment statement was encountered.

System Action: Processing continues.

User Response: Correct the invalid command or manually convert the unsupported command or directive.

CTMOPPSS-03W MEMBER-mem, PSS VARIABLES REQUIRE VALIDATION/CONFIRMATION

Explanation: A PSS variable in a member defined in a //*%2V or //*%2S JCL comment statement requires operator intervention or processing using a PSS exit program.

User Response: In the job scheduling definition corresponding to this member, set the CONFIRM parameter to Y, and define the variables and their default values in SET VAR parameters. This allows manual intervention to set the proper variable values at submission time.

CTMOPRUL-01E APPL=appl, txt, UNSUPPORTED OPTION

Explanation: In OPC application appl, a rule-based run cycle specifies an ADRULE parameter (txt) that is not supported by the conversion tool.

System Action: Processing continues.

User Response: In the Control-M table corresponding to the OPC application, manually supply the appropriate basic scheduling criteria and calendar to support the OPC ADRULE parameter.

CTMOPRUL-02E APPL=appl, UNSUPPORTED COMBINATION OF PARAMETERS

Explanation: In OPC application appl, a rule-based run cycle specifies a combination of ADRULE or SHIFT parameters that cannot be converted by the conversion tool.

System Action: Processing continues.

User Response: In the Control-M table corresponding to the OPC application, manually supply the appropriate basic scheduling criteria and/or calendar to support the OPC ADRULE parameter.

CTMOPUCB-00I member-name - MULTIPLE DS STEPS IN ONE JOB PROCESSED

Explanation: Multiple Universal Command/Universal Broker/SSH steps in the member member-name were processed as a single distributed job definition by combining the respective scripts in a single Embedded Script statement.

User Response: No action is required.

CTMOPUCB-01E member-name -host/-s[-cmd]/-x[-userid] NOT FOUND IN SYSIN, STEP=step-name

Explanation: In a Universal Command step in the member member-name, at least one of the following switches were not found:

• -host

• -s or -cmd

• -x or -userid

This causes the job in question to be only partially converted.

User Response: Correct the step in the member in question and rerun the job.

CTMOPUCB-05E member-name MIXED DS(UCMD/BROKER/SSH) AND MF STEPS IN ONE JOB. MF STEPS IGNORED.

Explanation: JCL member member-name contains multiple steps of mixed types, namely, at least one step that executes either Universal commands, Universal Broker, or SSH commands, and at least one other step that does not execute any of the above.

User Response: Review the Control-M job definition that was created. This definition may need to be modified. Additional jobs for the ignored steps may need to be created and integrated with the distributed job definition that was created.