Messages

This list contains only messages produced by the components of the conversion tool. Messages issued by other Control-M components are described in the INCONTROL for z/OS Messages Manual.

Messages contain the following parts:

  • A message code that consist of the following parts:

    • CTMyyyaa-nnx: CTM indicates that the message pertains to Control-M.

    • The variables in the message code are:

      • Item

      Explanation

      yyy

       

      3-character identifier of the conversion tool component that produced the message. Examples:

      • CA7—CTMCA7aa-nnx

      All CA-Driver messages (CTMCASxxx and CTM51xxx) can be found in the Control-M for z/OS for CA-SCHEDULER Conversion Guide.

      aa

      2-character identifier for the component that produced the message.

      nn

      2-character numeric identifier for the message.

      x

      1-character alphabetic identifier for the severity of the message. Valid values are:

      • R – Action

      • E – Error

      • I – Information

      • S – Severe

      • W – Warning

  • A message description, that contains any or all of the following:

    • Explanation: A 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.

CTMCA702-00W NO JCL LIBRARIES FOUND IN INITDECK. JCL PROCESSING BYPASSED

Explanation: No CA-7 JCL control statements were found in the CA-7 Initdeck file.

System Action: JCL checking and processing is bypassed.

CTMCA702-01W JOB NAME jobname DIFFERENT FROM JCL MEMBER NAME

Explanation: The jobname CA-7 job name differs from its JCL member name.

In Control-M, jobs are identified by their JCL member names, and the conversion tool uses the JCL member name as the job identifier. When the CA-7 job name differs from its JCL member name, the conversion tool creates an in-stream AutoEdit JCL statement %%INCLIB jcl-lib %%INCMEM member-name in the job definition.

User Response: For more information, see 1. JOB and MEMBER.

CTMCA702-02W JOB NAME jobname REQUIREMENT JOB req_job IGNORED. SAME AS TRIGGERED JOB

Explanation: The Conversion tool converts job definitions in both the 'TRIGGERED JOBS' and 'REQUIREMENTS AND NETWORK CONNECTIONS' paragraphs of the CA-7 LJOB report, to CONTROL-M IN and OUT conditions. When the same job/schid appears in both these paragraphs, a logical job flow loop is created that results in the following situation:

A 'G' line command in IOA screen 2 for the jobname job fails and the following message is issued:

Copy 
FLW009E A JOB FLOW LOOP DETECTED. CHART CANNOT BE COMPLETED FOR GROUP

and the CTMRFLW batch utility fails with the following message:

Copy 
A BREAK IN A DETECTED JOB FLOW LOOP

To prevent this situation, the conversion ignores the req_job job in the 'REQUIREMENTS' paragraph.

User Response: Examine and correct the job definition, if necessary, and recreate the LJOB report.

CTMCA702-03E CONTROL-M SCHEDULING TABLE NAME tblname NOT UNIQUE

Explanation: The Applications Report file (the DASYSN DD statement) contains duplicate occurrences of the tblname Control-M table name. Since table names are also PDS member names, they must be unique.

User Response: Replace duplicate occurrences of tblname in the Applications Report file with unique table names and rerun JOB1.

CTMCA702-04E CONTROL-M SCHEDULING TABLE NAME tblname NOT A VALID PDS MEMBER NAME

Explanation: The Applications Report file (the DASYSN DD statement) contains an invalid Control-M table name, identified by the variable tblname. If the tblname is blank, check if the LJOB report is empty or is not in FB (Fixed block) format.

User Response: Do the following:

Replace tblname in the Applications Report file with a valid PDS member name.

Rerun the job.

CTMCA702-05W JCL FOR CA-7 JOB jobname SET FOR OVERRIDE LIBRARY

Explanation: The CA-7 job definition for the jobname job states that the JCL member of the Override library must be used for the next run of jobname. However, the conversion uses the JCL member from the original library (identified by the CA-7 JCL ID or JCLLIB variable).

User Response: Check modifications of the JCL in the Override library. The Control-M AutoEdit facility can be used to perform JCL modifications.

CTMCA702-06W TRIGGERING NETWORK netwk_name IN JOB jobname NOT SUPPORTED

Explanation: Triggering networks are not supported and are not converted.

CTMCA702-07S APPLICATION LIST FILE EMPTY. PROCESSING STOPS

Explanation: The Application Report file contains no data.

Possible causes are:

  • The DASYSN DDstatement in JOB2 does not point to the correct file.

  • The LJOB command in JOB1 (LJOB,JOB=*) might have been modified to produce only an insufficient subset of the CA-7 jobs.

User Response: Do the following:

Check that DASYSN points to the correct file, correct the JCL, and rerun JOB2.

If the Application Report file now contains data, continue with step 3. If the Application Report file still does not contain data, continue with step 2.

Specify a more generic JOB parameter in the LJOB command of JOB1 to generate a sufficient number of jobs to produce an Application Report file.

Rerun the conversion.

CTMCA702-07W NON-ZERO LEAD-TIME, lead-time FOR job-connection IN JOB job-name NOT SUPPORTED

Explanation: A non-zero satisfaction lead-time indicates that since the last run of this job, the predecessor job has started and completed successfully within the last nn hours. If nn=99, the satisfaction lead-time indicates that the requirement is never considered initially satisfied when the job enters the request queue and that the dependent job must complete normally while this job is in the request queue. Such functionality is not supported within Control-M, and the lead time is not converted.

CTMCA702-08W JOB jobname DSN CONNECTION PERIODS REMOVED IN IN-CONDITION

Explanation: The jobname job contains a DSN-type job connection longer than 39 characters.

System Action: The dsn connection will be used in a Control-O ONDSNEVENT rule OUT condition name with the periods removed from the dsn. The connected job will specify this name in an IN condition.

CTMCA702-09E JOB jobname CONTAINS UNKNOWN CONDITION-CODE RELATION

Explanation: The CA-7 job definition for the jobname job contains a job-level condition code that uses an unknown relational operator.

System Action: The condition code is ignored by the conversion tool.

User Response: Do either of the following:

  • Correct the relation operator in the RO parameter of the CA-7 database, and rerun the conversion.

  • Modify the Control-M job scheduling definition.

CTMCA702-10E ERROR WHILE SCANNING CA-7 INITDECK

Explanation: A problem occurred while the conversion tool was analyzing relevant lines in the CA-7 Initdeck member. The conversion tool uses the CA-7 Initdeck in order to extract the CA-7 JCL library names, determine the job entry subsystem to which JCL is submitted (JES2 or JES3), and so on.

User Response: Correct the Initdeck and rerun the conversion.

CTMCA702-11S JOB jobname DUPLICATED IN CA-7 LJOB REPORT

Explanation: The conversion tool found the jobname job twice in the CA-7 LJOB report.

Since job names are unique in the CA-7 database, the error is probably due to a concatenated CA-7 LJOB report.

System Action: The program terminates.

User Response: Make sure that you have not concatenated multiple CA-7 LJOB reports that contain jobs of the same name. If this is the case, each CA-7 LJOB must be converted separately.

CTMCA702-12W - TRIGGERED DATASET NAME IS LONGER THAN MAXIMUM (44) FOR JOBNAME -jobname – TRUNCATED.

Explanation: During an attempt to create a file watcher job, the conversion encountered a triggered data set name that was longer than 44 characters, and truncated it to 44 characters.

System Action: The program continues executing. The date set name is truncated.

User Response: No action required.

CTMCA702-14E – JOB – jobname SCHEDULE ID-schid SOME PERIODIC CRITERIA NOT CONVERTED.

Explanation: Certain periodic scheduling criteria could not be converted in this job definition and schedule ID.

User Response: Review the converted job definition and manually update the scheduling criteria.

CTMCA702-15W JOB jobname SCHEDULE ID schid SCHDMOD CURRENT IGNORED. RESOLV SCHEDULE AND RERUN CONVERSION

Explanation: The SCHDMOD CURRENT indicator in this schedule-id and job is ignored while processing the LJOB/LSCHD report. The effect of ignoring the SCHDMOD CURRENT indicator is to limit the number of additional Control-M calendars that must be created by the conversion, whenever possible.

User response: The created Control-M scheduling criteria do not include the (temporary) changes indicated by the SCHDMOD CURRENT indicator. Therefore, the user is urged to RESOLV schedules and rerun the conversion.

CTMCA702-16W - NON-ZERO LEAD-TIME- lead-time FOR DSN – dataset-name IN JOB – jobname IS NOT SUPPORTED.

Explanation: Non-zero CA-7 lead times are not supported for dataset requirements. A non-zero (01-98) satisfaction lead-time indicates that since the last run of this job, the required dataset has been successfully transmitted within the last nn hours. Lead-time=99 is similarly not supported.

System Action: The job continues processing.

User Response: No action required.

CTMCA702-17S PARM VALUE SMALLER THAN NUMBER OF JOBS

Explanation: The CA-7 LJOB report contains more jobs than the value specified for the MAXIMUM NUMBER OF JOBS IN LJOB REPORT parameter in the Minor Step 10 of ICE.

User Response: Increase the parameter value, and rerun the conversion.

CTMCA702-20W JOB jobname SCHEDULE ID schid CONTAINS DOTM/STARTM BEFORE NEWDAY TIME, AND SUBTM IS AFTER

Explanation: The jobname CA-7 job definition for schedule ID schid specifies either DOTM or STARTM between midnight and the Control-M New Day Start time (that is, the start of the new logical workday), but the SUBTM time is after the New Day Start time.

Generally, SHOUT WHEN LATE messages are issued at the start time of the job. However, when the submission time is after the New Day Start time, the SHOUT WHEN LATE message is only issued after the New Day Start time.

CTMCA703-01W JOB jobname CONVERTED TO CYCLIC. SCHIDS IN JCL SPECIAL OVERRIDE STMTS OF JOB FLOW MEMBERS MAY NEED MANUAL ADJUSTMENTS

Explanation: A CA-7 job definition which specifies multiple schedule-ids that differ only in their time parameters (due-out, submit, start) has been converted to a Control-M cyclic or enhanced cyclic SMART table. If the time intervals between the schedule-ids are fixed, then the job is converted to a regular cyclic SMART table with the INTERVAL parameter specified. If the time intervals are not fixed, then the job is converted to an enhanced cyclic SMART table with a list of specific times.

However, SCHIDs in the job definition (in the "SCHEDULES" or "TRIGGERED BY JOBS" sections) may be lost while being extracted into a single RBC (SCHID 000 or *). Therefore, any usage of specific SCHIDs (such as #JI, #JO, #XI, or #XO) in the JCL members further down in the job flow will be false.

System Action: The Control-M job scheduling definition is created as an (enhanced) cyclic SMART table.

User Response: Validate all converted JCL members in the flow of this cyclic job to ensure that the corresponding usage of the SCHIDs is correct. Perform manual adjustments, as necessary, including a re-design of the flow according to Control-M standards.

CTMCA703-02W TRIGGERED JOB trig-job SCHID schid IN CYCLIC FOLDER folder-name REQUIRES SPECIAL PROCESSING

Explanation: CA-7 head-of-tree (HOT) jobs, which create implicit Control-M cyclic folders (that is, HOT specifies multiple schedule-ids with identical scheduling criteria but different start times), may contain an incorrect job flow when the list of triggered jobs includes jobs that specify a non-zero schedule-id.

System Action: The cyclic folder is created with the job that specifies the non-zero trigger schedule-id included in the job flow.

User Response: Modify the cyclic folder by removing the job(s) specified by the above message(s), and manually create a separate cyclic folder by copying the original folder and modifying the cyclic interval or specific run-times to accommodate the job(s) specified in the message.

CTMCA705-01W JCL MEMBER memname NOT FOUND IN lib – WILL NOT BE EXECUTED, RC=nn

Explanation: During the conversion process, the JCL member of each job is read in order to extract additional information. The specified JCL member could not be found in the lib library, or in its alternate JCL library, if one was specified (in the JCL Library Variables report or using the ALT parameter of the JCL Initialization Statement).

System Action: The Control-M job scheduling definition is created, but the job cannot run if the JCL member cannot be found.

User Response: Determine whether the job is needed. If it is needed, create a JCL member for the job.

CTMCA705-02S SYSTEM sysname SCHID schid NOT FOUND IN APPLS TABLE – PROCESSING STOPS

Explanation: While trying to assign the Control-M table name to a job, its CA-7 system name and schedule ID could not be located in the Applications Report file. This error indicates that the Applications Report file was probably incorrectly modified manually.

System Action: The job stops processing.

User Response: Correct the Applications Report file and rerun the job.

CTMCA705-03E JOB jobname NOT INCLUDED IN LJOB REPORT, TRIGGERING JOB trigjob

Explanation: The conversion tool could not find the jobname job in the LJOB report.

This message may be due to one of the following:

  • The jobname job, which is triggered by the trigjob job that appears in the LJOB report, does not itself appear in the LJOB report.

  • The jobname job, as specified in a DEMAND command in a CA-7 Batch Terminal step in the trigjob job, does not appear in the LJOB report.

  • The jobname job, which appears as a dependent (successor) job of the trigjob job in the LJOB report, does not itself appear in the LJOB report.

System Action: The conversion tool cannot define the jobname job.

User Response: Determine whether the jobname job is needed, then do the following:

  • If the jobname job is needed, add the jobname job definition to the CA-7 database.

  • If the jobname job is not needed, modify the definition of the trigjob triggering job in the CA-7 database so that it no longer triggers the jobname job.

  • Irrespective of whether the jobname job is needed, reproduce the LJOB report and rerun the conversion.

WARNING: You must eliminate all occurrences of this error message. Failure to do so might result in

  • necessary jobs or tables not being created, causing loss of data

  • improper triggering relationships being established in the Control-M tables created by the conversion tool

  • error conditions occurring when the CTMBLT utility is run later in the conversion

CTMCA705-05E TOO MANY LEVELS FOR JOB TREE STARTING WITH JOB jobname SCHEDULE ID schid

Explanation: As supplied, the conversion tool can handle job trees of up to 999 levels. The specified job tree contained too many levels.

This usually means that a recursive job tree has been defined in the CA-7 database for the CA-7 jobs. The recursive job can be defined by triggering, or by a CA-7 DEMAND command from the JCL.

User Response: Verify that there is no recursive job tree in the CA-7 database.

CTMCA705-06E - TRIGGERED BY JOB trigbyjob NOT INCLUDED IN LJOB REPORT, JOB jobname

Explanation: The conversion tool could not find job the trigbyjob in the LJOB report.

System Action: Processing continues for jobname, but because of the absence of trigbyjob, it may not be included in an appropriate job flow and may be created in an orphan table that contains just this job.

User Response: Ensure that the LJOB contains all necessary job definitions. You may have improperly modified the LJOB report parameters that were delivered with the conversion tool. In such a case, restore LJOB to its original settings and recreate the CA-7 input data, and then rerun the conversion.

CTMCA705-06W - NODE IS MISSING FOR DISTRIBUTED JOB jobname

Explanation: The conversion was unable to obtain a NODE ID for a distributed job (from the LJOB report, JCL member, or other source) to convert to a Control-M AGENT name.

System Action: The job continues processing. An error may be produced when the distributed XML is uploaded to Control-M/EM.

CTMCA705-07W – UNSUPPORTED [SAP|PEOPLESOFT] PARAMETER param_name IN JOB jobname.

Explanation: The specified distributed SAP or PEOPLESOFT parameter is not supported by the conversion.

User Response: Examine the PARM parameter to determine if any manual actions are necessary to incorporate the unsupported feature in Control-M.

CTMCA705-08W - UNSUPPORTED SYMETRIC PARAMETER IN "REPEAT" SCHED-ID IN JOB jobname.

Explanation: The conversion does not support the conversion of jobs whose scheduling criteria specifies both the REPEAT and SYMETRIC keywords.

System Action: A Control-M calendar is created for the job.

CTMCA705-09W NUMBER OF OCCURRENCES OF JOB jobname IN SCHEDULING TABLE tbl EXCEEDS THE MAXIMUM VALUE

Explanation: As a result of CA-7 recursive TRIGGERED JOBS definitions (in LJOB), the jobname job has exceeded the maximum number of occurrences defined by the JOBMXOC conversion option in the tbl table.

System Action: The job continues processing, but ignores any further occurrences of the specified job.

User Response: Do the following:

Either manually restructure the application by means of Control-M features such as ON PGMST or DO FORCEJOB, or increase the value of JOBMXOC.

Rerun the conversion.

CTMCA705-10E DCAL CALENDAR NOT FOUND FOR JOB jobname

Explanation: The conversion tool could not find a calendar in the Calendar Names List file (created by JOB1) to supply the proper calendar name in the DCAL parameter of the Control-M job scheduling definition.

Most likely, the CA-7 job schedule was not RESOLVEd. Therefore, no calendar was available for display in the LSCHD report, to be used in the Control-M DCAL parameter. This leads to improper Basic Scheduling parameters being created in the job scheduling definition.

Alternatively, the error might be caused by the fact that the CA-7 LSCHD is not in alphabetical job name order. If it is not, you must reproduce the LSCHD report in the proper order and rerun the conversion jobs (see the User response below).

This error might result in Control-M/EM validity check errors and duplicate RBCs being created in SMART tables.

System Action: Processing continues.

User Response: Do the following:

Ensure that all CA-7 scheduling members are RESOLVEd.

Rerun STEP2 of JOB0 to recreate the LSCHD report.

Rerun the conversion job.

Alternatively, you can manually update the Control-M job scheduling definition to conform to the CA-7 scheduling definition parameters.

CTMCA705-11W JOB jobname SCHEDULE ID schid IS TRIGGERING/DEMANDING ITSELF. USE CYCLIC JOB

Explanation: The conversion tool found that the jobname job of the schid schedule ID is either triggering or demanding itself. To prevent such looping, the conversion tool ignores this recursive definition.

User Response: Use the Control-M TASKTYPE cyclic job scheduling definition to accomplish this task. To prevent the job from being continually resubmitted, it is recommended that the cyclic job either delete the prerequisite conditions that triggered its operation, or set a TIME UNTIL parameter.

CTMCA705-12W JOB jobname RELATION OPERATOR ‘ro’ NOT SUPPORTED IN #SCC

Explanation: In a CA-7 #SCC JCL override statement in the jobname job, the conversion tool encountered a relational operator, ro, that is not supported by Control-M.

System Action: The job continues processing, but the #SCC statement is ignored.

CTMCA705-14I PHASE n

Explanation: The CA-7 conversion tool is entering the second or third phase, converting any CA-7 jobs that were not processed during the main conversion phase.

Normally, if the CA-7 database (the LJOB report) was maintained as required, you do not see any further messages after this message. If there are any further messages, the probable reason is that the CA-7 database contains "orphan" job definitions or "broken" triggering structures. Conditions of those types are normally indicated by occurrences of the CTMCA705-03E message during the main conversion phase.

System Action: Normal processing continues.

User Response: Examine any tables written during the second or third phase.

CTMCA705-15E JOB jobName IN RESOURCE XREF REPORT NOT FOUND IN LJOB

Explanation: According to the CA-7 Job-to-Resource Cross Reference report, the jobName job uses certain resources. However, this job is not defined in the CA-7 LJOB created by JOB0.

System Action: The resource associated with the jobName job is ignored.

User Response: Define the job in the CA-7 database, and recreate the LJOB report in JOB0.

CTMCA705-16E JOB jobName FREE OPTION A/N NOT SUPPORTED FOR SHR/EXC RES resourceName

Explanation: The resourceName shared or exclusive resource in the CA-7 Job-to-Resource Cross Reference report specifies a FREE option of either A or N, which is not supported by the conversion tool.

System Action: The FREE option is ignored.

User Response: The resourceName resource is converted to a Control-M CONTROL resource. Examine the resource in the jobName job and decide whether its definition requires manual modification.

CTMCA705-20E – ARFSET arfset-name NOT FOUND IN LARF REPORT FOR JOB jobname.

Explanation: An ARFSET referenced in the LJOB was not defined in the CA-7 LARF report.

User Response: Define the specified ARFSET in the CA-7 LARF report and rerun the job.

CTMCA705-23W - SAPR3-STEP-S01-DEPT FIELD dept-value IS TRUNCATED TO 12 CHARACTERS IN JOB jobname OF TABLE tblname

Explanation: When the SAPR3-STEP-S01-DEPT FIELD is longer than 12 characters, it is truncated to 12 characters.

System Action: Normal processing continues.

User Response: None.

CTMCA705-24S NUMBER OF CALENDARS EXCEEDS MAXCALS VALUE

Explanation: The number of calendars produced in JOB1 exceeds the value specified in the MAXCALS conversion parameter.

System Action: The job stops processing.

User Response: Do the following:

Increase the value of the MAXCALS conversion parameter in the DEFAULTS member.

Rerun the conversion.

CTMCA706-01E JOB=jobname ERROR IN FORMAT OF #SCC LINE

Explanation: The conversion tool encountered an invalid or unsupported parameter when converting a #SCC CA-7 JCL override statement for the jobname job.

System Action: The conversion tool may create a partial ON PGMST post-processing parameter and continue processing.

User Response: Modify the Control-M ON PGMST parameter in the job scheduling definition of the jobname job.

CTMCA706-02E JOB=jobname ERROR IN U11RMS PARM

Explanation: While processing the jobname job in a CA-7 or CA-11 JCL library, the conversion tool encountered an invalid PARM parameter in a CA-11 U11RMS step.

System Action: The PARM parameter is not converted, but the job continues processing.

User Response: Do the following:

Correct the PARM parameter. For more information, refer to the CA-11 User Guide.

Rerun JOB2.

CTMCA706-03E JOB=member-name, UNSUPPORTED USE OF #J IN DS JOB

Explanation: The conversion tool encountered a CA-7 special override statement (#JI, #JO, …) while processing a JCL member that contains distributed job script statements. These CA-7 override statements are not supported for Control-M distributed job definitions.

System Action:The conversion tool ignores the CA-7 override statements and continues processing.

User Response: Manual adjustment of the converted job definition or the creation of additional job definitions may be necessary.

CTMCA706-05E JOB= jobname ERROR IN "PARAMETER" STATEMENT

Explanation: An error was detected in a PARAMETER statement of a distributed job definition within a JCL member jobname.

System Action: The conversion tool disregards this statement and proceeds with the conversion process.

User Response: Review and adjust or rewrite the PARAMETER statement.

CTMCA707-00R HAVE YOU ENSURED THAT PROD JCL LIBRARIES WILL NOT BE MODIFIED (SECT3/STEP2) (Y/N)?

Explanation: This query is always issued by JOB3 to force verification that copies of the Production JCL and BTI parameter libraries are converted to Control-M format and not the actual Production libraries.

System Action: If the reply is N, the program terminates without processing the JCL and parameter libraries. If the reply is Y, normal library conversion is performed.

User Response: Reply Y (Yes) or N (No) as appropriate.

CTMCA707-01S TOO MANY BTERM ENTRIES. MAX IS 10

Explanation: The number of Batch Terminal Parameter Control Statements (in the BATCH TERMINAL DEFINITIONS panel) may not exceed 10.

System Action: Processing terminates.

User Response: Contact your local INCONTROL representative.

CTMCA707-09I MEMBER=memname, LIBRARY=lib action

Explanation: When conversion option PJCLCNV is set to N, this information message indicates that the memname JCL member, or a member (memname) pointed to by the SYSIN statement in a JCL or parameter member, has been modified.

When conversion option PJCLCNV is set to Y, this information message indicates that the memname JCL member has been processed. Only members that are associated with jobs defined in the CA-7 LJOB report(s) will be processed and converted. The action indicates the type of processing performed and is one of the following:

  • MODIFIED – CA-7 elements contained in the member were converted to the corresponding Control-M elements.

  • COPIED – no CA-7 elements that required conversion were found in the member and the member was copied

  • BYPASSED – the member corresponded to a distributed job definition and was not copied. These members contain control statements that specify the job’s attributes (such as CMDNAME and AGENT) that are incorporated into the Control-M job scheduling definition, and after conversion the member is no longer needed.

Note that lines may have been deleted from the memname member without conversion because their function was not supported by the converted Control-M utility.

CTMCA707-10I MEMBER INCLUDED INTO JCL: include-member

Explanation: A JCL INCLUDE statement that specifies the include-member was encountered in a JCL member that was subject to conversion. The contents of the include-member cannot be converted (if necessary) unless the library in which it resides was specified in the DSNXLT file (via ICE) or the PJCLCNV conversion option was specified as N.

System Action: The job continues processing normally.

CTMCA707-11I ATTEMPT TO MODIFY PRODUCTION LIBRARY: lib

Explanation: The conversion attempted to modify a member in the JCL library, but the library was not found in the DSNXLT file.

System Action: Members in this JCL library will not be modified by the conversion.

User Response: Include the library in the DSNXLT file (via ICE) to allow updates to the members within it.

CTMCA709-01E JOB=jobname, BATCH TERMINAL COMMAND cmd COULD NOT BE CONVERTED DSN=jcl-libname

Explanation: A Batch Terminal in-stream command, a Batch Terminal JCL PARM parameter, or the Batch Terminal SYSIN DD statement could not be processed. Possible reasons include the following:

  • An in-stream DEMAND command did not specify the JOB parameter.

  • An in-stream POST command did not specify one or more of the following parameters:

  • — the JOB parameter
    — the DEPJOB parameter
    — the USR parameter

  • In trying to convert a DEMAND, POST or RESCHNG command in a JCL PARM parameter, the equivalent CTMUTIL command overflowed column71, and could not be contained on one JCL line.

  • The Batch Terminal SYSIN DDstatement does not specify in-stream data, and the JCL DSN parameter could not be found in the SYSIN DDstatement.

  • In a DEMAND or POST command, the JOB or DEPJOB parameters can contain a job name that exceeds8 characters, or the SCHID parameter can contain a schd-id that exceeds 3 digits.

  • An in-stream RQVER command specified UPDATE=YES, which is not supported.

  • An in-stream ADDRQ or D=dsn command was specified, but these are not supported.

  • For errors involving SYSIN (only), the explanation is contained in the message immediately preceding this message.

System Action: The cmd command is not converted, or is only partially converted.

User Response: Inspect the indicated JCL member, and manually convert the cmd command (or commands).

CTMCA709-02W JOB=jobname, UNSUPPORTED PARM COMMAND=cmd-text DSN=jcl-libname

Explanation: While processing the jobname job in a CA-7 or CA-11 JCL library, the conversion tool encountered an unsupported PARM parameter in a CA-7 Batch Terminal step.

User Response: Examine the PARM parameter to determine if any manual actions are necessary to incorporate the unsupported feature in Control-M.

System Action: The PARM parameter is nullified by placing a blank at the end of the PARM statement.

CTMCA709-03W JOB=jobname , UNSUPPORTED CA-7 UTILITY ca7-utility DSN=jcl-libname

Explanation: While processing the member jobname in a CA-7 or CA-11 JCL library, the conversion tool encountered an unsupported CA-7 Utility program. Some examples of unsupported CA-7 utilities are SASSBCLP and CA-EARL.

User Response: Delete the CA7 Utility and determine if any manual actions are necessary to substitute for the unsupported program in Control-M.

System Action: The job continues processing.

CTMCA709-04W - JOB=jobname, MEMBER=member-name CONTAINS VARIABLE. CANNOT BE CONVERTED DSN=library-name.

Explanation: A SYSIN member name contains a symbolic variable and cannot be resolved. The contents of the member are ignored.

System Action: The program continues executing.

User Response: If necessary, manually convert the contents of the member.

CTMCA709-05W – COMMAND: cmd SET CONDITION TO GLOBAL, JOB=jobname DSN= library-name.

Explanation: This message may be produced when processing the PARM=xxx of the CA-7 utility CAL2X2WB (whose purpose is to route SYSIN commands to a different node for execution). If the SYSIN command is converted to an ADD|DEL COND condition, then the message indicates that the condition name must manually be made global, and that the jobs at the remote system that wait for this condition must be modified to wait for the global condition.

System Action: The job continues processing without converting this command.

User Response: Perform a manual adjustment.

CTMCA709-06E - NODE= node DOES NOT EXIST AT NODEMAP, JOB=jobname DSN=library name.

Explanation: The specified node does not exist in the NODEMAP file.

System Action: The job continues processing without converting this NODE to an equivalent Control-M datacenter name.

User Response: Add the node name and its equivalent Control-M datacenter name to the NODEMAP file, and then rerun the job.

CTMCA709-07W - THE VALUES jobname / system-name / SCHID IN JOB/ SYSTEM/ SCHID FIELDS IN LGVAR REPORT ARE NOT SUPPORTED AND IGNORED.

Explanation: Non-blank values in the JOB, SYSTEM, or SCHID fields in the LGVARS Global Variable report are not supported by the conversion and are ignored.

User Response: If necessary, manually adjust the usage of the affected global variables.

CTMCA711-04S - DATA WAS TRUNCATED IN LSCHD REPORT DUE TO CA-7 BSRT-17 ERROR MESSAGE

Explanation: The LSCHD report is truncated due to a problem in the CA-7 utility that produced it. Control-M calendars for one or more jobs might be missing, incomplete, or corrupted.

System Action: The program terminates with error code 12.

User Response: Use less inclusive criteria in the JOB= keyword of the LSCHD,JOB=*,LIST=BYSID command. This produces multiple smaller LSCHD reports that do not overlap and which you can concatenate together when you rerun the conversion.

CTMCA712-01W – DSN library-name DOES NOT EXIST IN THE TRIGDSN FILE.

Explanation: This warning message indicates that the DSN does not exist in the file where you provide a list of jobnames versus TRIGGERING.

User Response: If necessary, add the missing DSN and the corresponding jobname to the list in the file that you provide.

CTMCA712-02W - DOFORCEJ MEMBER DOES NOT EXIST

Explanation: This warning message indicates that the DOFORCEJ member does not exist.

User Response: No action required.

CTMCA799-02E func FAILED FOR BLOCK blkname [MEMBER=memname DDNAME=ddname]

Explanation: The func MVS memory acquisition or freeing function (GETMAIN or FREEMAIN) failed for the blkname block. The JCL REGION parameter specification is not large enough.

User Response: Contact BMC Customer Support.

CTMCA799-08I PROCESSING ENDED FOR LIBRARY lib

Explanation: This information message indicates the completion of the conversion from CA-7 format to Control-M format of all members of JCL Library library.

CTMCA799-09I MODIFICATIONS WERE DONE TO MEMBER memname LIBRARY lib

Explanation: This information message indicates that the memname JCL member, or a member (memname) pointed to by the SYSIN statement in a JCL or parameter member, has been modified. Note that lines may have been deleted without conversion from the memname member because their function was not supported by the converted Control-M utility.

CTMCA799-13S TOO MANY LIBRARIES IN INPUT. MAX IS 256

Explanation: The CA-7 Initdeck can contain up to 256 JCL library names. This maximum has been exceeded.

User Response: Contact your local INCONTROL representative.

CTMCA7AR-01E UNSUPPORTED OR MISSING OPTION IN ARFSET arfset-name.txt val

Explanation: The conversion tool encountered an invalid or unsupported parameter when converting ARFSET. arfset-name.txt is a short description of the invalid or unsupported parameter, and val is the value of the parameter.

System Action: The conversion tool may create a partial arfset scheduling definition and continue processing.

User Response: Modify the resulting Control-M job scheduling definition.

CTMCA7RB-01W TABLE table-name HAS BEEN CONVERTED FROM A CYCLIC TABLE TO A NON-CYCLIC TABLE

Explanation: In Minor Step 12, the CONVERTED SCHEDULING LIBRARY BE IN SMART TABLE FORMAT option was set to N, resulting in the Control-M Scheduling library being created in non-SMART table format. In such a case, all Cyclic SMART table definitions were converted to regular tables resulting in the loss of their cyclic nature.

User Response: BMC recommends that the CONVERTED SCHEDULING LIBRARY BE IN SMART TABLE FORMAT option be set to Y to prevent the loss of cyclic table definitions.

System Action: Processing continues and the program terminates with a return code of 8.

CTMCA7SO-02I LJOB FILE RE-SORTED BY JOBNAME

Explanation: This is an informative message indicating that the input CA-7 LJOB report file was not created in sorted jobname order as a result of multiple overlapping LJOB prefix specifications in the ICE ‘EXTRACT CONVERSION INPUT DATA’ step and has been sorted by the conversion tool.

System Action: Normal processing continues.

User Response: None.

CTMCA7SO-03W DUPLICATE JOB jobname BYPASSED IN LJOB FILE

Explanation: A duplicate job jobname was found when processing the input CA-7 LJOB report file as a result of multiple overlapping LJOB prefix specifications in the ICE ‘EXTRACT CONVERSION INPUT DATA’ step.

System Action: Since jobs in CA-7 must have unique job names, the conversion bypasses all duplicate job definitions encountered in the LJOB report. The step terminates with a return code of 4.

User Response: None.

CTMCA7V5-01S PARM VALUE SMALLER THAN NUMBER OF LINES IN TABLE tblname: intermediate-table IN PROCESS

Explanation: JOB2 attempted to build a SMART Table (tblname) with more lines than specified in the MAXIMUM '#' OF LINES IN ANY SMART TABLE value (ICE Minor Step 12).

To determine the progress of the program in merging all the intermediate-tables in tblname,refer to the APPLS file for the name of the intermediate-table.

User Response: Increase the parameter value, then rerun JOB2.

CTMCA7V5-11E COND cond_name NOT ADDED TO TABLE tblname

Explanation: The conversion can create a maximum of 600 OUT conditions in a SMART Table entity to delete conditions. This message indicates that this SMART Table already contains 600 defined OUT conditions and no additional conditions will be added to the table.

System Action: The program continues executing.

User Response: Manually split the SMART Table into multiple SMART Tables, thereby reducing the number of OUT conditions in each table.

CTMCA7V5-12S MAXIMUM SMART TABLE-ENTITY SIZE EXCEEDED, INCREASE MAXGENT

Explanation: The maximum number of lines in a SMART Table entity has been exceeded.

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

User Response: Increase the value of the MAXGENT parameter in the SET CA-7 CONVERSION DEFAULTS OPTIONS panel (Stage 0), then rerun JOB2 job.

CTMCA7V7-01I - REDUNDANT EMPTY RBCS ARE REMOVED FROM TABLE DEFINITION tblname

Explanation: Empty Rule-Based Calendars (RBCs) that contain no scheduling criteria have been removed from the CONTROL-M Scheduling Definitions tables. For further details regarding empty RBCs, see the notes in 36. SCHID.

User Response: No action required.

CTMCD51-07I STARTING CONVERSION OF CA DRIVER PROCEDURES

Explanation: This information message indicates that the conversion of the CA-DRIVER procedure libraries is beginning.

User Response: No action required.

CTMCD51-08I STARTING TO PROCESS LIBRARY lib

Explanation: This information message indicates that JOB4 of the conversion tool is starting to convert the lib CA-DRIVER procedures library from CA-SCHEDULER format to Control-M format.

User Response: No action required.

CTMCD51-09I CA-DRIVER PROCEDURES CONVERSION ENDED

Explanation: This information message indicates that the conversion of the CA-DRIVER procedure libraries has ended.

User Response: No action required.

CTMCD52-11S PROCEDURE LIBRARY IS EMPTY

Explanation: The CA-DRIVER procedure library (the DAPROC DD statement) has no members.

User Response: Check previous messages of JOB4 in the Conversion messages file (the DAPRINT DD statement). Correct any errors accordingly, and rerun JOB4.

CTMCD52-08I JCL LIBRARIES CONVERSION ENDED

Explanation: This information message indicates that the conversion of the JCL procedure libraries has ended.

User Response: No action required.

CTM680E MEMBER memName DOES NOT EXIST IN THE LIBRARY

Explanation: The memName member that was requested is not in the library specified in DD statement DABLTARF. This is because an ARFSET specified in a CA-7 job definition (memName) does not exist in the CA-7 LARF report. This message is issued by Control-M utility CTNBLT.

System Action: The CTMBLT MODEL statement, which specifies the ARFSET, is ignored.

User Response: Either remove the ARFSET from the CA-7 job definition or add the missing ARFSET definition to the CA-7 LARF report.

Rerun the conversion from JOB1.