Messages CTM700 through CTM7xx

This group includes messages for the Control-M for z/OS, Control-M/Assist, Control-M/Links for z/OS, and Control-M/Restart products.

CTM700E PLEASE FILL IN LIBRARY NAME

Explanation: The library name is missing.

Corrective Action: Specify the library name.

CTM701E PLEASE FILL IN TABLE NAME OR OMIT JOB NAME

Explanation: The job name is specified, but the table name is missing. A job must be defined in a table.

Corrective Action: To get a list of tables in the library, either fill in a table name, or omit the job name.

CTM703E ELAPSE VALUE CANNOT EXCEED 1440 MINUTES (ONE DAY)

Explanation: An invalid value is specified in the ELAPSE parameter. The maximum ELAPSE time for a job is 1440 minutes.

Corrective Action: Enter a value not greater than 1440.

CTM704E MAXIMUM NUMBER OF STEP RANGE LINES EXCEEDED

Explanation: More than 100 STEP RANGE lines were specified on the Job Scheduling Definition screen or on the Job Zoom screen. The maximum number of STEP RANGE lines permitted on a Job Scheduling Definition screen is 100.

Corrective Action: Remove the excess STEP RANGE lines.

CTM705E INVALID OPTION FOR GROUP DEFINITION

Explanation: The line command is invalid for a group definition.

The command is not executed.

Corrective Action: Either choose a line command that is valid for group definitions, or select a job definition for which the line command is valid.

CTM706E ORDER COMMAND NOT ALLOWED FOR GROUP TABLE

Explanation: The O (ORDER) line command was entered for a job that is part of a group. The O line command is valid only for jobs that do not belong to a group.

Control-M prompts for a new line command.

Corrective Action: Change the line command.

CTM707E INVALID CALENDAR REFERENCE OR SCHEDULING ERROR

Explanation: The P option was used to view the scheduling dates of a job containing an error in its basic scheduling criteria. The basic scheduling criteria of this job had at least one parameter that could not be correctly evaluated by the CTMRPLN utility.

Possible causes are:

• The DCAL or WCAL parameter points to a member that does not exist in the calendar library.
• The calendar member does not contain the date range specified by the user. Both the current and next year following the end date should be defined in the calendar.

The P option is not executed for this job.

Corrective Action: Check the DCAL and WCAL parameters in the basic scheduling criteria for the job. Check the date range in the calendar member. Correct accordingly, and reactivate the P option.

CTM708E DELETE COMMAND NOT ALLOWED FOR LAST JOB IN GROUP TABLE

Explanation: An attempt to delete the last remaining job definition in a group table failed. Every group table must have at least one job definition.

The D (Delete) option is not executed for this job definition.

Corrective Action: Delete the entire group table.

CTM709I COPY CANCELLED DUE TO USER REQUEST

Explanation: A copy process was cancelled by the PF03 key. A window is displayed when a request is submitted to copy a job definition.

The copy process is terminated.

Corrective Action: No action is required.

CTM70AE REQUIRED FIELD IS MISSING

Explanation: The user failed to specify a mandatory field. Values must be specified for several fields, for example, the destination table name.

The copy request is not processed.

Corrective Action: Press PF03 to cancel the copy request or fill in the required data.

CTM70BE CANNOT COPY TO THE SAME TABLE

Explanation: The specified destination table is the table that currently contains the job definition. An attempt to copy a job definition from a table into the same table failed.

The copy request is not processed.

Corrective Action: Press PF03 to cancel the copy request or specify a different destination table name.

CTM70CI COPY WAS EXECUTED SUCCESSFULLY

Explanation: The message is issued when one of the following components has been successfully copied:

• IOA component job definition
• CTO rule
• CMEM rule
• CTT rule
• CTD mission definition
• IOA calendar definition

Corrective Action: No action is required.

CTM70DE SPECIFIED LIBRARY DOES NOT EXIST

Explanation: The user tried to copy a job definition into a destination data set that does not exist.

The copy process is not implemented.

Corrective Action: Allocate the destination data set and try again to copy the job definition.

CTM70EE THIS ENTRY TYPE CANNOT BE COPIED

Explanation: An attempt to copy a group job into another table failed. A job that is part of a group cannot be copied into another table.

The copy process is not implemented.

Corrective Action: No action is required.

CTM70FE GENERAL ERROR DURING COPY PROCESS RC = rc

Explanation: Usually, an error has occurred during the copy process, causing a return code (rc) of 004 to be generated.

The copy process is terminated.

Corrective Action: Contact BMC Customer Support.

CTM70GE CANNOT COPY TO THE SAME RBC

Explanation: The current RBC definition is specified as the RBC destination. The copy request is not processed.

Corrective Action: Cancel the copy request or specify a different RBC definition.

CTM70HI RBC RENAMED SUCCESSFULLY

Explanation: An RBC definition has been successfully renamed.

Corrective Action: No response needed.

CTM70II RENAME CANCELLED DUE TO USER REQUEST

Explanation: A rename process was cancelled by the PF03 key. A window is displayed when a request is submitted to rename an RBC definition. The rename process is terminated.

Corrective Action: No response needed.

CTM710E PLEASE FILL IN A VALID OPTION - "Y" OR "N"

Explanation: An invalid exit option was specified. The cursor points to the invalid value.

Valid options are:

• Y (Yes)
• N (No)

Corrective Action: Type Y (Yes) or N (No) in one of the exit options.

CTM711E ONE (AND ONLY ONE) EXIT OPTION MUST BE MARKED AS "Y" OR "N"

Explanation: Both exit options were marked either as Y or N. One exit option must be marked Y the other N.

Corrective Action: Change one of the exit options to Y or N accordingly.

CTM712E MISSING CONTINUATION CONDITION NAME

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the continuation condition field is empty. In this case, the continuation condition field must contain at least one character.

Corrective Action: Do one of the following:

• For a short condition, remove CONT from the first dateref field.
• For a long condition, type at least one character in the continuation condition field.

CTM713E LENGTH OF CONTINUATION CONDITION MAY NOT EXCEED 19 CHARACTERS

Explanation: The continuation condition field contains more than 19 characters, which is the maximum allowed.

Corrective Action: Ensure that the text of the continuation condition contains at least one, but no more than 19 characters.

CTM714E INVALID DATE REF 'CONT' - COND NAME MUST BE 20 CHAR

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the first condition field has less than 20 characters. In this case, all 20 spaces in the first condition field, and at least one in the continuation condition field, must be used.

Corrective Action: Do one of the following:

• For a short condition, remove CONT from the first dateref field.
• For a long condition, use all 20 spaces in the first condition field, and at least one in the continuation condition field.

CTM715E RIGHT PARENTHESIS IS NOT VALID IN CONTINUATION CONDITION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the first condition field contains a Boolean right (closing) parenthesis character ')'. In this case, the condition must continue into the continuation condition field. A Boolean closing parenthesis may not end the condition in the first condition field.

Corrective Action: Do one of the following:

• For a short condition, remove CONT from the first dateref field.
• For a long condition, remove the closing parenthesis from the first condition field, use all 20 spaces in the first condition field, and use at least one space in the continuation condition field.

CTM716E LEFT PARENTHESIS IS NOT VALID IN CONTINUATION CONDITION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the continuation condition field contains a Boolean left (opening) parenthesis character '('. In this case, the condition must begin in the first condition field. A Boolean opening parenthesis may not start the condition in the continuation condition field.

Corrective Action: Do one of the following:

• For a short condition, remove CONT from the first dateref field and clear the continuation condition field.
• For a long condition, move the opening parenthesis to the beginning of the first condition field and use all 20 spaces in the first condition field, and use at least one space in the continuation condition field.

CTM717E OR SIGN '|' IS NOT VALID IN CONTINUATION CONDITION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the continuation condition field of a long condition contains a logical OR symbol '|'. In this case, the condition must begin in the first condition field. The logical OR symbol is valid only at the beginning of the first condition field of a long condition.

Corrective Action: Do one of the following:

• For a short condition, remove CONT from the first dateref field and clear the continuation condition field.
• For a long condition, move the logical OR symbol to the beginning of the first condition field, use all 20 spaces in the first condition field, and use at least one space in the continuation condition field.

CTM718E ONLY BLANK ALLOWED IN CONTINUATION CONDITION DATE-REF OPTION

Explanation: The first dateref field contains CONT, which specifies a long condition. However, the first opt field for the condition is not blank. In this case, the first opt field must be blank and the second opt field, after the continuation condition and the second dateref field, controls condition handling at the end of the job.

For short conditions, the value in the first opt field controls whether the condition is added to the Conditions file at the end of the job (+) or removed from it (-).

Corrective Action: Do one of the following:

• For a short condition, remove CONT from the first opt field and clear the continuation condition field.
• For a long condition, clear the first opt field and enter a valid value (+ or -) in the second one.

CTM719E TOO MANY "DO COND" - ONLY 245 ARE ALLOWED

Explanation: There are more that 245 DO COND statements in a single job scheduling definition. The maximum number of DO COND statements in each job scheduling definition is 245.

Corrective Action: Remove any extra DO COND statements.

CTM71AE PLEASE FILL IN AT LEAST ONE ADDRESS IN THE "TO" FIELD

Explanation: No address was entered in the TO field of a DO MAIL statement.

Corrective Action: Enter at least one address in the TO field of the DO MAIL statement.

CTM71BE TOO MANY DO MAIL "TO" LINES - ONLY 255 ARE ALLOWED

Explanation: More than 255 lines were entered in the TO field of a DO MAIL statement.

Corrective Action: Correct the contents of the TO field in the DO MAIL statement so that the field contains no more than 255 lines.

CTM71CE TOO MANY DO MAIL "CC" LINES - ONLY 255 ARE ALLOWED

Explanation: More than 255 lines were entered in the CC field of a DO MAIL statement.

Corrective Action: Correct the contents of the CC field in the DO MAIL statement so that the field contains no more than 255 lines.

CTM71DE TOO MANY DO MAIL TEXT LINES - ONLY 255 ARE ALLOWED

Explanation: More than 255 lines were entered in the TEXT field of a DO MAIL statement.

Corrective Action: Correct the contents of the TEXT field in the DO MAIL statement so that the field contains no more than 255 lines.

CTM71EE PLEASE FILL IN A VALID OPTION - "Y" OR "N" OR "D"

Explanation: An invalid value was entered for ATTACH SYSOUT.

Corrective Action: Correct the field contents.

CTM720E PLEASE FILL IN MEMBER NAME

Explanation: Missing MEMBER NAME. The MEMNAME field is obligatory.

Corrective Action: Fill in the name of the member you wish to submit in the MEMNAME field. In the case of a started task, fill in its name.

CTM721E INVALID TASK TYPE

Explanation: Invalid tasktype.

Valid values for the TASKTYPE parameter are:

• JOB - batch job (default)
• CYC - cyclic job
• STC - started task (STC)
• CST - cyclic STC
• EMR - emergency job
• ECJ - emergency cyclic job
• EST - emergency STC
• ECS - emergency cyclic STC
• WRN - warning message

For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the TASKTYPE field.

CTM722E INVALID OPTION (USE "Y", "N" OR BLANK)

Explanation: An invalid option has been entered in the NCT2 field.

Valid options for running NCT2 (NOT CATALGD2) are:

• Y (Yes) - Prevent errors by removing old data sets. This option is not valid for started tasks (STCs).
• N (No) - Do not prevent errors.
• Blank (Default) - Use the site-defined default, which is set during Control-M/Restart installation.

Corrective Action: Specify Y or N, or leave the field blank to use the site default.

CTM723E MAXWAIT SHOULD BE 00-98 OR 99

Explanation: An invalid value was entered for the MAXWAIT parameter.

The value of MAXWAIT should be from 00 through 98, meaning the number of extra days that the job can wait to be executed, or 99, meaning that the job remains in the Active Jobs file forever, even after executing).

Corrective Action: Correct the value in the MAXWAIT field.

CTM724E FIELD MUST BE BLANK OR NUMERIC WITH LEADING ZEROES

Explanation: The field contains data which are neither numeric characters nor blank. If numeric values are used, then no trailing (or preceding) blanks are allowed. The cursor points to the invalid field value.

Corrective Action: Correct field contents.

CTM725E INVALID FORMAT OF DAYS PARAMETER

Explanation: An invalid format was set for the DAYS parameter.

The DAYS parameter should contain 1 through 31, ALL, +1, +3, and so on. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct field contents.

CTM726E "ALL" PARAMETER MIXED WITH SPECIFIC - CORRECT

Explanation: The ALL parameter was specified together with specific days in the DAYS parameter or the WDAYS parameter. You cannot use specific WDAYS or DAYS together with the ALL option.

Corrective Action: Omit either the ALL option or the specific days options.

CTM727E INVALID FORMAT OF WDAYS PARAMETER

Explanation: Invalid format of WDAYS parameter. WDAYS parameter should contain 0 through 6, ALL, +1, and so on. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the WDAYS field.

CTM728E INVALID CONDITION DATE REFERENCE

Explanation: An invalid condition date reference has been specified. Date reference should be ODAT, PREV, ****, or mmdd (or ddmm, depending on the site standard). For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Correct the date reference.

CTM729E MISSING/INVALID CONTROL-TYPE. USE "E" - EXCLUSIVE OR "S" - SHARED

Explanation: A CONTROL resource was specified, but the CONTROL type is invalid or missing. The CONTROL type should be E (Exclusive) or S (Shared). For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Type E or S in the CONTROL type field.

CTM72AE DESCRIPTION LENGTH CAN'T EXCEED 4000 CHARACTERS

Explanation: The length of the description cannot exceed 4000 characters.

Corrective Action: Shorten the description.

CTM72BE INVALID OPTION (USE "Y", "N", "L", "F" OR BLANK)

Explanation: An invalid option has been entered in the NCT2 field.

Valid options for running NCT2 (NOT CATALGD2) are:

• Y (Yes) - Prevent errors by removing old data sets. This option is not valid for started tasks (STCs).
• N (No) - Do not prevent errors.
• L (List) - List GDG data sets with the corresponding level from the original job in the SYSOUT file using CTR301I messages.
• F (Flush) - Upon finding an error, prevent further processing.
• Blank (Default) - Use the site-defined default, which is set during Control-M/Restart installation.

Corrective Action: The only value that is valid for a started task is N, or leave the field blank.

CTM72CE INTERVAL LIMIT IS EITHER 45 DAYS, 1080 HOURS, OR 64,800 MINUTES

Explanation: An interval specification exceeded one of the following:

• 64,800 minutes
• 1080 hours
• 45 days

For more information, see the INTERVAL parameter in the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the INTERVAL field.

CTM72DE VALID DISPLAY VALUES ARE 'M' MINUTES, 'H' HOURS, OR 'D' DAYS

Explanation: An interval type specification was invalid. The valid interval types are:

• M - minutes
• H - hours
• D - days

For more information, see the INTERVAL parameter in the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the type.

CTM72EE VALID SYSTEM ID FORMATS ARE: XXXX OR /XXXX

Explanation: The length of the system ID value may be up to 4 characters. In a JES3 system this value may be preceded by a slash character, indicating NOT.

Corrective Action: Correct the value in the SYSID field according to the format indicated in the message.

CTM72FE DUPLICATE CONTROL RESOURCE NAMES ARE NOT ALLOWED

Explanation: Two CONTROL resources with the same name are not allowed.

Corrective Action: Remove one of the CONTROL resources.

CTM72GE 5 CHARACTER SYSID VALUE NOT ALLOWED IN COMPATIBILITY MODE

Explanation: Compatibility mode implies conformity to previous Control-M versions in which a maximum of 4 characters could be specified for the SYSID field.

Corrective Action: Specify a maximum of 4 characters in the SYSID field.

CTM730E QUANTITY MUST BE A FOUR DIGIT NUMBER

Explanation: Invalid quantity (for a quantitative resource). Quantity should be a non-zero, 4-digit number. For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Correct the quantity field.

CTM731E INVALID TIME

Explanation: Invalid time specified. The format of the TIME parameter should be hhmm. For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Correct the TIME field (FROM or UNTIL).

CTM732E MISSING/INVALID CONDITION OPTION. TRY "+" TO ADD OR "- " TO DELETE

Explanation: Invalid or missing condition option. The value of the condition option should be + for add, or - for delete. For more details, see the job production parameters chapter in the appropriate user guide.

Corrective Action: Specify + or - in the condition option field.

CTM733E INVALID SYSOUT OPTION

Explanation: An invalid sysout option was specified.

Valid SYSOUT option are:

• D
• R
• F
• N
• C

Some SYSOUT options require additional sysdata.

For more details see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the SYSOUT field.

CTM734E MAXRERUN LIMIT IS 255

Explanation: More than 255 reruns were specified. The maximum number of times a cyclic job may be rerun or restarted is 255. For more information, see MAXRERUN in the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the MAXRERUN field.

CTM735E INVALID FINISH CODE

Explanation: An invalid job or step finish code was specified. For valid codes, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the finish code field.

CTM736E INVALID ACTION

Explanation: An invalid action was specified in a DO statement. For valid actions, see the job production parameters chapter in the Control-M for z/OS User Guide. This message can also be produced when specifying DO statements valid only if certain products are installed, for example, specifying DO IFRERUN when Control-M/Restart is not installed.

Corrective Action: Correct the DO action field.

CTM737E INVALID URGENCY. USE "R" - REGULAR, "U" - URGENT OR "V" - VERY URGENT

Explanation: An invalid value was specified for the SHOUT URGN (urgency) subparameter.

Valid values for SHOUT URGN are:

• R - regular
• U - urgent
• V - very urgent.

For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Type R, U, or V in the SHOUT urgency field.

CTM738E INVALID "WHEN" ATTRIBUTE

Explanation: An invalid WHEN attribute was specified in a SHOUT statement.

For valid values, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the value in the WHEN field.

CTM739E PLEASE FILL IN USER ID

Explanation: Missing user ID. The USER ID field is obligatory.

Corrective Action: Insert a user ID.

CTM73AE Finish code must be Cnnnn/Unnnn, where nnnn is asterisk or 0000 to 4095

Explanation: Finish code was not correctly defined.

Corrective Action: Correct the finish code.

CTM73BE Finish code must be Shhh, where hhh are hex digits (0 to F) or asterisk

Explanation: Finish code was not correctly defined.

Corrective Action: Correct the finish code.

CTM73CE INVALID OPTION, SPECIFY "W" (WORD),"C" (CHAR) OR BLANK

Explanation: An invalid option was specified.

Corrective Action: Specify W for word, C for character, or leave blank.

CTM73DE INVALID VALUE. SPECIFY A NUMERIC VALUE (00-255)

Explanation: An invalid value was specified.

Corrective Action: Specify a numeric value in the range from 0 to 255.

CTM73FE INVALID VALUE. SPECIFY A NUMERIC VALUE (00-99999999)

Explanation: An invalid value was specified.

Corrective Action: Specify a numeric value in the range from 0 to 99999999.

CTM73GE INVALID VALUE. SPECIFY A BLANK OR NUMERIC VALUE (00-44)

Explanation: An invalid value was specified.

Corrective Action: Specify a blank or a numeric value in the range from 0 to 44.

CTM73HE PLEASE SPECIFY AN AUTO-EDIT VARIABLE NAME (%%VARNAME)

Explanation: An invalid AutoEdit name was specified.

Corrective Action: Specify a valid AutoEdit name beginning with the %% characters.

CTM73JE CAPTURED VARIABLE NAME LENGTH CANNOT EXCEED 18 CHARACTERS.

Explanation: The variable name that was specified is too long.

Corrective Action: Specify a variable name with not more than 18 characters.

CTM73KE POOL NAME LENGTH CANNOT EXCEED 20 CHARACTERS.

Explanation: The pool name that was specified is too long.

Corrective Action: Specify a pool name with not more than 20 characters.

CTM740E EXPECTED CONTINUATION NOT RECEIVED (AFTER ",")

Explanation: The DAYS or WDAYS parameter ended with a comma. Additional data is expected after comma.

Corrective Action: Correct the parameter.

CTM741E INVALID SHOUT DESTINATION CODE

Explanation: Invalid SHOUT destination code.

For valid destination codes, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Correct the SHOUT destination field.

CTM742E CANNOT MIX DAYS OPTION WITH WDAYS OPTION

Explanation: Values were set for the DAYS parameter and the WDAYS parameter. The DAYS parameter conflicts with the WDAYS parameter.

Corrective Action: Delete either the value in the DAYS parameter or the value in the WDAYS parameter.

CTM743E DATES PARAMETER CONFLICTS WITH DAYS OR DCAL OPTION

Explanation: Both the DATES parameter and the DAYS, WDAYS or MONTHS parameters were specified.

The DATES parameter must appear alone.

Corrective Action: Erase any data in the DAYS, WDAYS and MONTHS parameters.

CTM744E CANNOT MIX DATES OPTION WITH CALENDAR OPTION

Explanation: The DATES parameter and the DCAL, WCAL or CONFCAL parameters were specified simultaneously.

The DATES parameter cannot be specified if the DCAL or WCAL or CONFCAL parameter is specified.

Corrective Action: Delete the value in the DATES field or in the DCAL, WCAL and CONFCAL fields.

CTM745E CANNOT MIX MINIMUM/PDS WITH OPTIONS DAYS, WDAYS, MONTH, DATES OR CALENDAR

Explanation: The MINIMUM or PDS parameter was specified simultaneously with the DAYS, WDAYS, MONTHS, DATES or CALENDAR parameters.

The MINIMUM and PDS parameters cannot be specified with date-related parameters.

Corrective Action: Specify either the MINIMUM and PDS parameters or one of the date-related parameters.

CTM746E MINIMUM AND PDS MUST BE FILLED IN TOGETHER

Explanation: A value was set for the MINIMUM parameter, but the PDS field is empty (or vice versa).

The MINIMUM and PDS parameters must be filled in together.

Corrective Action: Fill in both the MINIMUM and PDS fields.

CTM747E PLEASE FILL IN THE "IN" PREREQUISITE CONDITION NAME

Explanation: There is no IN prerequisite condition name.

The condition date reference was specified without a corresponding prerequisite condition name.

Corrective Action: Fill in the IN prerequisite condition name field.

CTM748E PLEASE FILL IN THE "CONTROL" RESOURCE NAME

Explanation: Missing control resource name. The control resource type was specified without a corresponding control resource name.

Corrective Action: Fill in the control resource name field.

CTM749E PLEASE FILL IN THE "QUANTITATIVE" RESOURCE NAME

Explanation: Missing quantitative resource name. The quantitative resource quantity was specified without a corresponding quantitative resource name.

Corrective Action: Fill in the quantitative resource name field.

CTM750E PLEASE FILL IN THE PREREQUISITE CONDITION NAME

Explanation: Missing prerequisite condition name in DO COND statement.

At least one condition is expected in DO COND statement.

Corrective Action: Fill in the prerequisite condition name.

CTM751E PLEASE FILL IN NEW CLASS (ONE LETTER)

Explanation: Missing new class on SYSOUT option C.

When you specify C (Change sysout class) as the SYSOUT option, a 1-letter new class parameter is needed.

Corrective Action: Fill in the new class (one letter).

CTM752E PLEASE FILL NEW DESTINATION (1-8 LETTERS)

Explanation: Missing new destination on SYSOUT option N. When SYSOUT option N is specified to change the sysout destination, a destination code is needed. Maximum length is 8 characters.

Corrective Action: Fill in the new destination (1-8 characters).

CTM753E PLEASE FILL IN FILE NAME

Explanation: Missing file name on SYSOUT option F. When SYSOUT option F is specified to copy the sysout to a file, a file name is needed. Maximum length is 44 letters.

Corrective Action: Fill in the file name.

CTM754E REDUNDANT TEXT IN SYSOUT DATA FIELD

Explanation: The sysout data field contains data which is not relevant to the sysout option specified.

Corrective Action: Erase the redundant text.

CTM755E USE OF PREV/NEXT DATE REFERENCE CONFLICT PDS/MINIMUM OPTIONS

Explanation: A PREV (or NEXT) date reference has been specified for a job scheduled by the PDS parameter. There is no next date or previous date when the job is scheduled according to the status of the library.

Corrective Action: Use another valid date reference.

CTM756E ONLY CODE OPTION "-" ALLOWED FOR DATE REFERENCE $$$$/****

Explanation: Code option + specified for a generic date reference. It is impossible to ADD a prerequisite condition on all possible dates of the year.

Corrective Action: Either enter "-" in the code option or use a different date reference.

CTM757E RERUN OPTION CONFLICTS WITH CYCLIC TASK TYPE

Explanation: The RERUN option has been specified for a CYCLIC task type. You cannot use the RERUN option for a CYCLIC task type.

Corrective Action: Omit the RERUN option.

CTM758E PLEASE FILL IN STEP NAME BEFORE THE FINISHING CODE

Explanation: A job or step finishing code appears without a step name. A step name is obligatory in an ON STEP CODES statement. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Fill in the step name or erase the finishing code.

CTM759E MAXIMUM 245 FINISHING CODES FOR ONE STEP

Explanation: Too many finishing codes for one step. The maximum number of finishing codes for one step is 245.

Corrective Action: If you want to use more finishing codes, you can open a new ON STEP statement.

CTM760E AT LEAST ONE FINISHING CODE IS EXPECTED AFTER PREVIOUS STEP NAME

Explanation: A step name is not followed by at least one finishing code. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Specify a finishing code.

CTM761E PLEASE FILL IN THE PREVIOUS STEP/CC LINE

Explanation: A DO statement is filled in, but the previous STEP/CC line is empty. The ON STEP CODES line is obligatory in CODES statement.

Corrective Action: Fill in the previous ON STEP CODES line or erase the DO statement.

CTM762E REDUNDANT TEXT IN SHOUT PARAMETER

Explanation: The SHOUT WHEN statement contains data which is not relevant to the shout option specified.

Corrective Action: Erase the redundant text.

CTM763E PLEASE FILL IN PREREQUISITE NAME FOR SHOUT OPTION "COND"

Explanation: A prerequisite name for a SHOUT option is missing. For more details, see the job production parameters chapter in the Control-M for z/OS User Guide.

Corrective Action: Fill in a prerequisite name.

CTM764E INVALID SHOUT REFERENCE. USE "- " OR BLANK

Explanation: A SHOUT reference is invalid.

Valid SHOUT references are:

• " " (Blank) - for checking the existence of a condition
• " - " - for checking the absence of a condition.

Corrective Action: Type " - " in the SHOUT reference field, or leave the field blank.

CTM765E PLEASE FILL IN THE SHOUT LINE BEFORE THIS MESSAGE LINE

Explanation: A message is filled in, but the SHOUT line that precedes it is empty.

Corrective Action: Fill in the SHOUT WHEN field. If necessary, fill in the TO destination field also.

CTM766E PLEASE FILL IN THE MESSAGE

Explanation: There is no message in the SHOUT statement.

Corrective Action: Fill in the message.

CTM767E CONFLICT BETWEEN "OK", "NOTOK" AND "RERUN" FOR THE SAME STEP

Explanation: There is a conflict of actions for the same ON STEP statement. A job cannot at the same time be OK and NOTOK, or OK and RERUN.

Corrective Action: Select one of the options: OK, NOTOK and RERUN, and omit the rest.

CTM768I TOP OF JOBS LIST

Explanation: This information message indicates that the current job is the first job in the jobs list. The message may appear after entering the command PREVJOB in the Job Zoom screen.

Corrective Action: No action is required.

CTM769I BOTTOM OF JOBS LIST

Explanation: This information message indicates that the current job is the last job in the jobs list. The message may appear after entering the command NEXTJOB in the Job Zoom screen.

Corrective Action: No action is required.

CTM76BE INVALID VARIABLE NAME, USE '%%VARNAME' OR '%%\VARNAME'

Explanation: You specified an invalid variable name in the ON VAR statement. The variable name must begin with %% for a local variable, or with %%\ for a global variable.

Corrective Action: Correct the variable name and try again.

CTM76CE INVALID OPERATOR CODE

Explanation: You specified an invalid operator code in the ON VAR statement.

The following operators are valid for an integer:

• EQ - Equal to (=)
• NE - Not equal to (!=)
• GT - Greater than (>)
• GE - Greater than or equal (>=)
• LT - Less than (<)
• LE - Less than or equal (<=)
• IR - In range (a<=x<=b)
• NR – Not in range (x<a or x>b)

The following operators are valid for a string:

• LK - Like
• NL - Not like
• IX - Is exactly
• NX - Is not exactly
• SW - Starts with
• EW - Ends with
• CO - Contains
• NC - Does not contain
• MP - Is empty
• NP - Is not empty

Corrective Action: Correct the operator code and try again.

CTM76DE WHEN UFLOW IS 'Y' THE JOB NAME MUST BE EMPTY

Explanation: The UFLOW option is performed for all jobs in a forced table. It is relevant only when the JOB name is empty.

Corrective Action: If you are forcing a single job, leave the UFLOW field empty or enter a value of 'N'. On the other hand, if you want to force a unique job flow for all jobs in a table, ensure that the JOB field is empty.

CTM76EE INVALID VALUE, THE VALUE MUST BE AN INTEGER UP TO 10 DIGITS

Explanation: This message indicates that you specified an invalid variable value in the ON VAR statement. For an integer operator, the VAL, MIN, and MAX fields must contain an integer value up to 10 digits.

You can include a plus (+) or minus (-) sign as the first character of the numeric string, and this character is not counted as one of the 10 digits of the number.

When one of these fields contains the ‘%%’ characters, no verification is performed for the on-screen fields, and the value is validated only at the execution stage of the job or table.

The following strings are examples of valid values: +1234567890, -1234567890, 1234567890, %%VALUE1

Corrective Action: Correct the variable value and try again.

CTM770E PLEASE FILL IN LIBRARY NAME

Explanation: In Control-M, this message indicates that the library name is missing. LIBRARY name is obligatory.

Corrective Action: Fill in a LIBRARY name. For started tasks type the computer ID and started task parameters.

CTM770I INVALID TRACE LEVEL WAS SPECIFIED: xxxxxxxxxxxxxxxx

Explanation: This information message is issued when TRACE is turned on for the IOA online monitor and the trace level is invalid.

When the F IOA-monName, TRACE is set to nnn, the command ON or OFF is used to turn TRACE ON or OFF, and the TRACE level is invalid, this message is issued. The TRACE level may be set to any value from 1 through 256.

The system ignores the command and continues processing.

Corrective Action: Reset the TRACE level to a valid value and try again.

CTM771E PROC STEP MUST BE PRECEDED BY PGM STEP

Explanation: A PROCST (procstep) name has been filled in, but the PGMST field is empty. A PGMST name is obligatory when using PROCST.

Corrective Action: If you really want to reference all the steps in the procedure designated in the PROCST field, insert ANYSTEP in the PGMST field.

CTM771I FORMATTING OF CONTROL-D COMMUNICATION FILE STARTED

Explanation: This information message indicates that the Control-D Communication file is currently being formatted.

Corrective Action: No action is required.

CTM772E OK, NOTOK AND EXERR CANNOT BE SPECIFIED FOR A SPECIFIC STEP NAME

Explanation: OK, NOTOK, or EXERR events have been specified in the same ON STEP statement.

Corrective Action: To specify any event (in any case), use the event *****.

CTM772I FORMATTING OF CONTROL-D COMMUNICATION FILE ENDED

Explanation: This information message indicates that the formatting of Control-D Communication file by the CTDFRCOM utility has ended.

Corrective Action: No action is required.

CTM773E REQUIRED CALENDAR DEFINITION IS MISSING

Explanation: The option used in the DAYS or WDAYS parameter requires a name of a calendar to work with.

Corrective Action: Either correct the DAYS or WDAYS definition, or enter a calendar name.

CTM773S FORMATTING OF CONTROL-D COMMUNICATION FILE - WRITE I/O ERROR

Explanation: An I/O error occurred during formatting of the Control-D Communication file. This may occur when there is incompatibility between the definition of the Communication file in the Installation Parameters (COMSIZE in CTDPARM) and the JCL SPACE or DCB parameters.

The utility stops executing with a condition code of 08.

Corrective Action: Correct either the JCL or the Installation Parameters.

CTM774E PERIOD IDENTIFIER SPECIFIED IS INVALID

Explanation: The period identifier specified in a DnPi date selection is invalid. It must be A-Z, 0-9, or * (except Y and N).

Corrective Action: Specify a valid period identifier.

CTM774S CONTROL-D COMMUNICATION FILE WAS NOT BUILT

Explanation: The CTDFRCOM utility failed.

Corrective Action: Look for previous error messages that describe the type of error.

CTM775I monName - validModifyParm

Explanation: This information message follows the CTM649E message, which is issued when a MODIFY command parameter is invalid.

Corrective Action: No action is required.

CTM776I monName - SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message indicates that the specified Online monitor is shutting down because of an operator’s request.

Corrective Action: No action is required.

CTM777E "FROM" FIELD SHOULD BE BLANK

Explanation: A value was specified in the FROM field, but the field should be blank. The FROM field indicates how the next run time of the job should be calculated. A value should only be specified in one of the following circumstances:

• The TASKTYPE value is CYC, indicates a cyclic job (valid values are CYC, CST, ECJ, or ECS)
• The MAXRERUN field contains a value

Neither of these criteria applies to this job. Therefore, no value should be specified.

Corrective Action: Delete the value in the FROM field.

CTM777I monName - ONLINE MONITOR INITIALIZATION STARTED

Explanation: This information message indicates that the specified Online monitor was started and is currently building the required internal environment.

Corrective Action: No action is required.

CTM778E VALID VALUES ARE 'TRGT', 'STRT', OR 'END'

Explanation: Either an incorrect value or no value was specified in the FROM field. This message displays available valid values, one of which should be specified.

The FROM field indicates how the next run time of the job should be calculated. A valid value must be specified when TASKTYPE is set to CYC, indicating a cyclic job, or if the MAXRERUN field contains a value. This job satisfies one of those criteria.

Valid values are:

• STRT - The interval between runs from the start of execution of a job.
• END - The interval between runs from the end of the job run.
• TRGT - The interval between runs from the start of the previous interval.

Corrective Action: Specify one of the above values for the job.

CTM778I monName - ONLINE MONITOR INITIALIZATION COMPLETED

Explanation: The monName Online monitor is ready to serve the user’s sign-on request.

Corrective Action: No action is required.

CTM779E monName - ONLINE MONITOR INITIALIZATION FAILED RC rc IN STEP step#

Explanation: The specified Online monitor initialization has encountered an internal error.

The following step and return codes can appear in the message:

The specified online monitor will shut down.

Corrective Action: Act according to the step number and return code as follows:

CTM77AI USER userId WAS CANCELED DUE TO TIMEOUT

Explanation: This information message indicates that the communication session with the specified user was terminated because no data was transmitted during a period of time which exceeded the timeout interval.

This message is generated by the CTMXSND program, which communicates with the OMON cross-memory monitor.

Corrective Action: No action is required.

CTM77BE VALID VALUES ARE 'S' 'R' 'N' OR 'A'

Explanation: An invalid value was specified in the DYNAMIC INSERT JOB INTO GROUP field of the Confirmation Window for a FORCE/ORDER option in a Job List Screen.

Valid value for this field are:

• S - This opens a panel with a list of all group entities, and allows the user to select the group entity to force the job into the Active Job File. The Order ID of each group is displayed.
• R - Add the job to the group entity (in the Active Job File) that was most recently ordered.
• N - Force a job belonging to a group entity, and the group entity itself, to the Active Jobs File.
• A - Default value. Force a job or a group entity to the Active Jobs File.

Corrective Action: Specify a valid value.

CTM77DE VALUE 'N' NOT ALLOWED FOR REGULAR JOB

Explanation: The value specified in the DYNAMIC INSERT JOB INTO GROUP field of the Confirmation window for the FORCE/ORDER option for a regular job definition is invalid.

Corrective Action: Specify one of the following values:

• S - Selects the group entity to force the job into the Active Jobs file.
• R - Adds the job to the group entity that was most recently ordered.
• A - Forces the job into the Active Jobs file.

CTM77FE VALID VALUES ARE 'STRT' AND 'END'

Explanation: For CYCLIC type 'V' (Varying intervals), the FROM value must be either STRT or END.

Corrective Action: Correct the field contents.

CTM780I monName - NO USER IS SIGNED ON TO THIS ONLINE MONITOR

Explanation: This information message is displayed when the operator inquires about active users in the specified Online monitor, but there are none.

Corrective Action: No action is required.

CTM781E monName - INSUFFICIENT STORAGE FOR USER usr. SIGN ON FAILED

Explanation: There is insufficient virtual storage in the Online monitor address space.

The user sign-on request is terminated.

Corrective Action: Do the following:

1. Increase the REGION size of the Online monitor.
2. If the problem persists, reduce the number of users allowed to sign on to the Online monitor by lowering the value of the MAXSESS parameter of the specific monitor in IOAXPRM. For more details, see the description of installing the IOA Online monitor in the INCONTROL for z/OS Installation Guide.

CTM782E monName - INSUFFICIENT STORAGE FOR INITIALIZATION

Explanation: Highlighted, unrollable message.

There is insufficient memory for the online monitor.

The monName online monitor will shut down.

Corrective Action: No action is required.

CTM783W monName - CONTROLM YES PARAMETER WILL BE IGNORED

Explanation: There is a contradiction between the CONTROLM parameter in Control-D Installation Parameters (CTDPARM) and the parameters file (member) allocated by the DAXMMIN DD statement.

The CONTROLM YES parameter is ignored.

Corrective Action: Correct the parameters file allocated to the DAXMMIN DD statement and correct CTDPARM.

CTM784E monName - AN ONLINE MONITOR WITH THE SAME STC NAME IS ALREADY ACTIVE

Explanation: The operator entered a START command in order to activate a monitor.

Control-D and Control-M online monitors may work simultaneously provided that each monitor uses a unique name.

The newly started online monitor terminates.

Corrective Action: If an additional online monitor is needed, define another JCL procedure with a different name to support it.

CTM785I EXISTING USERS (IF ANY) ARE NOT USING A TREE

Explanation: A DISPLAY TREES inquiry has been made, but no users are using a Control-D Recipient Tree.

Corrective Action: No action is required.

CTM786I monName - NEW TREE LOADED. NEW USERS WILL BE SIGNED ON TO THE NEW TREE

Explanation: This information message indicates that the operator has modified the Online monitor with the LOADTREE command.

A new tree was loaded from the data set (member) allocated to the DATREE DD statement. The new tree will be in effect for all users who sign on from this point in time.

Corrective Action: No action is required.

CTM787W monName - MAXIMUM NUMBER OF TREES LOADED. A TREE MUST BE FREED IN ORDER TO LOAD A NEW ONE

Explanation: The operator entered a LOADTREE command but there are already five trees in storage. Only five tree copies can be loaded.

Corrective Action: Wait and retry. A tree is freed when the last user session working with that tree leaves the user screen, or is cancelled.

CTM788I monName - THE FOLLOWING USERS ARE SIGNED ON TO TREE NUMBER num

Explanation: This information message is the result of a DISPLAY TREES inquiry to one of the online monitors. It acts as a header for the CTM789I message. The message is displayed for each Recipient Tree that is loaded in the online monitor.

Corrective Action: No action is required.

CTM789I monName - userId1 userId2 ...

Explanation: This information message displays the result of a DISPLAY TREES inquiry to one of the online monitors. It is displayed for each group of six users.

The variables in this message are:

• monName - the name of the online monitor started task
• userId - the user ID of the person that is using the Recipient Tree

Corrective Action: No action is required.

CTM78AE ioaomon stc name INITIALIZATION OF THE LIBRARY ddName FAILED

Explanation: The IOA online monitor could not process the library referenced by the ddName DD statement. The error occurred when the IOA online monitor address space attempted to initialize processing for the library or a member within the library.

The IOA online monitor terminates with a return code of 8.

Corrective Action: Check for the presence of the ddName DD statement, the library referenced by it, and the member name in the ALC allocation member and in the JCL for the monitor. Add the missing entry or correct the entry in error. Restart the IOA online monitor.

CTM78BE ioaomon stc name MEMBER PRMXMM WITH COMMON COMMANDS AND PFKEYS IS NOT FOUND

Explanation: The IOA online monitor did not find the PRMXMM member in the IOA PARMCMD library. The library referenced by the DACMDCU DD statement under the IOA online monitor does not contain the PRMXMM member, which internally defines common COMMANDS and PFKEYS.

The IOA online monitor terminates with a return code of 8.

Corrective Action: Ensure that the DACMDCU DD statement correctly refers to the IOA PARMCMD library. Ensure that the PRMXMM member exists in the library. If the problem persists, contact BMC Customer Support.

CTM78CI ioaomon stc name MEMBER memName WITH COMMANDS OR PFKEYS IS NOT FOUND

Explanation: The IOA online monitor did not find the COMMAND or PFKEYS member in the IOA PARMCMD library. The libraries referenced by the DACMDCU and DAPFCMD DD statements under the IOA online monitor do not contain the COMMAND member or the PFKEYS associated with the currently displayed screen.

The IOA online monitor continues execution. Problems may occur when attempting to execute commands entered on the user’s screen.

Corrective Action: Do the following:

• Ensure that the DACMDCU and DAPFCMD DD statements correctly refer to the IOA PARMCMD library.
• Ensure that all necessary COMMAND and PFKEYS members exist in the library.
• If the problem persists, contact BMC Customer Support.

CTM78DE jobName JOBNAME NOT DEFINED IN IOAXPRM

Explanation: When starting up, the jobName IOA Online monitor was not found in IOAXPRM (either explicitly, or by mask).

The IOA Online monitor terminates.

Corrective Action: Use a valid job name, or make the necessary changes to IOAXPRM, and restart the monitor.

CTM78EE jobName WRONG LEVEL OF IOAXPRM

Explanation: The eye-catcher of the IOAXPRM member was not found in storage.

The probable cause is that the eye-catcher was overwritten by another module.

The startup of the IOA monitor stops.

Corrective Action: Contact your INCONTROL administrator. If no solution can be found for the problem, contact BMC Customer Support.

CTM790E SECURITY VIOLATION details

Explanation: where details is PASSWORD IS NOT AUTHORIZED or PASSWORD HAS EXPIRED.

An invalid or expired password has been specified in the IOA Online Entry Panel.

The logon request is denied.

Corrective Action: If details is PASSWORD IS NOT AUTHORIZED, reenter your password (three attempts to enter the correct password are allowed). If details is PASSWORD HAS EXPIRED, renew your password and try again.

CTM791S USER IS NOT AUTHORIZED TO ENTER IOA ENVIRONMENT

Explanation: The IOAX006 or IOAX009 IOA user exit indicated that the user cannot use the IOA Online facility.

The IOA Online facility terminates.

Corrective Action: No action is required.

CTM792E PLEASE FILL IN THE USER ID AND PASSWORD AND PRESS ENTER

Explanation: Either the USER ID or PASSWORD field in the IOA Online Entry Panel is empty.

Corrective Action: Fill in the missing information, either USER ID field or PASSWORD field.

CTM793I monName - ONLINE MONITOR SHUTTING DOWN

Explanation: Highlighted, unrollable message.

The monName Online monitor is shutting down.

Corrective Action: No action is required.

CTM794I monName - USER usr NOT FOUND

Explanation: A DISPLAY USER= usr inquiry was entered with a user name (usr) which is not active in the specified Online monitor.

Corrective Action: No action is required.

CTM795I monName - USER usr CANCELLED

Explanation: The usr Online user was cancelled upon operator’s request. The usr user session will be terminated.

Corrective Action: No action is required.

CTM796E INVALID "ON STEP CODES" ARGUMENTS FOR A "DUMMY" JOB

Explanation: Arguments are specified in the ON PGMST statement of a DUMMY job. The ON PGMST, PROCST and CODES fields in the ON PGMST statement must be blank for a DUMMY job. Since DUMMY jobs are not actually submitted, you cannot check how they finished. They always finish OK.

Corrective Action: Clear the ON PGMST, PROCST and CODES fields for this DUMMY job.

CTM797E ONLY ONE IF RERUN STATEMENT IN EACH "ON PGMSTEP"

Explanation: A second DO IF RERUN action was entered for the same ON PGMSTEP. Only one DO IF RERUN action is allowed per ON PGMSTEP.

Corrective Action: Use the existing DO IFRERUN for defining the requested restart processing for this ON PGMSTEP.

CTM798E "IFRERUN" CANNOT BE USED WITH "RERUNMEM"

Explanation: A DO IFRERUN action was entered for a task that has a recovery member defined in the RERUNMEM field. RERUNMEM and DO IFRERUN are mutually exclusive. Restart is only allowed for the same member.

Corrective Action: Decide whether RERUNMEM or restart processing is needed and define the job accordingly.

CTM799E {IF RERUN | CTBSTEP | OVERLIB} IS NOT SUPPORTED FOR A STARTED TASK

Explanation: The user has typed a DO IF RERUN, DO IF OVERLIB, or DO IF CTBSTEP action for a started task (STC) task type. STC and DO IF RERUN, DO IF OVERLIB, DO IF CTBSTEP are mutually exclusive.

Corrective Action: Decide whether STC type or restart processing is needed and define the task accordingly.

CTM79AE "STOPCYCL" OPTION IS VALID FOR CYCLIC TASK TYPE ONLY

Explanation: A DO STOPCYCL post-processing parameter was specified in the job scheduling definition for non-cyclic job or task. DO STOPCYCL can only be specified for cyclic jobs or cyclic started tasks.

Corrective Action: Delete the DO STOPCYCL parameter.

CTM7A0I monName - VTAM MONITOR INITIALIZATION STARTED

Explanation: This information message indicates that the monName VTAM monitor started, and is currently building the required internal and external environments. This is a normal start message for the VTAM monitor initialization process.

Corrective Action: No action is required.

CTM7A1I monName - VTAM MONITOR INITIALIZATION COMPLETED

Explanation: This information message indicates that the monName VTAM monitor is ready to serve the user’s sign-on requests.

Corrective Action: No action is required.

CTM7A2E monName - VTAM MONITOR INITIALIZATION FAILED IN STEP stepName

Explanation: The monName VTAM monitor initialization has encountered an internal error.

The monName VTAM shuts down.

Corrective Action: Check the contents of the IOA Log and the system log for prior messages to determine the reason for the failure. If you cannot determine the reason, and the problem recurs whenever you start the VTAM monitor, contact BMC Customer Support.

CTM7A3S monName - VTAM MONITOR ENDED WITH ERROR

Explanation: A severe error has occurred. The monName IOA VTAM monitor is shutting down. Detailed information on this error is available in the messages which were previously displayed on the operator console.

The monName IOA VTAM monitor shuts down.

Corrective Action: Check the system log for additional messages.

CTM7A4I monName - VTAM MONITOR SHUTTING DOWN

Explanation: This information message is displayed when the monName VTAM monitor is shutting down.

Corrective Action: No action is required.

CTM7A5E monName - VTAM ACB FOR APPLID applId IS NOT DEFINED TO VTAM OR IT IS NOT CURRENTLY ACTIVE

Explanation: The monName VTAM monitor is unable to open the ACB for the specified application ID, such as, CTMS. The VTAM monitor opens the ACB as part of its initialization. This action is required before a LOGON can be issued. Possible causes are:

• VTAM is down.
• The VTAM application ID is inactive.
• The application is not defined to VTAM.

The monName VTAM monitor shuts down.

Corrective Action: Check that the application ID is defined, and that it is active. The command VARY NET,ACT,ID= applId activates the application. Start the VTAM monitor again.

CTM7A6E monName - VTAM MONITOR CANNOT OPEN THE VTAM ACB. CHECK THE VTAM APPLICATION DEFINITION

Explanation: The monName VTAM monitor is unable to open the VTAM ACB. The VTAM monitor opens the ACB as part of its initialization. This action is required before a LOGON can be issued. Generally, this message is issued when the cause of the error is not one described in CTM7A5E. Possible causes are:

• VTAM is down.
• The VTAM application ID is inactive.
• The application is not defined to VTAM.

Generally, this message is issued when the cause of the error is not one described in CTM7A5E.

The monName VTAM monitor shuts down.

Corrective Action: Check the application definition in VTAM. The command D NET,ID= applId displays the status of the application.

CTM7A7E monName - VTAM MONITOR CANNOT ISSUE THE SETLOGON COMMAND

Explanation: The monName VTAM monitor is unable to start the logon process. The VTAM monitor cannot accept any logon until the SETLOGON operation completes successfully. Possible causes are

• A temporary shortage of storage exists for VTAM.
• Some other VTAM problem has occurred.
• A problem exists in the application definition.

The VTAM monitor monName shuts down.

Corrective Action: Check the application definition in VTAM. The command D NET,ID= applId displays the status of the application.

CTM7A8I monName - VTAM MONITOR SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message indicates that the monName VTAM monitor is shutting down based on an operator’s request.

Corrective Action: No action is required.

CTM7A9E monName - VTAM MONITOR UNABLE TO CLOSE ACB

Explanation: The monName VTAM monitor is unable to close the VTAM ACB. During shutdown processing, the VTAM monitor closes the ACB to ensure successful future initialization.

The monName VTAM monitor shuts down.

Corrective Action: Refer to prior messages in the system log to determine cause of the VTAM monitor shutdown.

CTM7AAE monName - INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

Explanation: An invalid parameter was passed to the monName IOA VTAM monitor by an operator modify command (F). A list of valid modify parameters appear on the operator console following this message. This is a header message for message CTM7ABI.

The modify command is rejected.

Corrective Action: Enter a correct modify parameter.

CTM7ABI monName - validModifyParm(s)

Explanation: This message is issued when an invalid modify parameter has been entered. The header for this message is message CTM7AAE.

Corrective Action: No action is required.

CTM7ACI monName ACCEPTING LOGONS TO access_ctrl_blk

Explanation: This information message indicates that the monName IOA VTAM monitor started successfully and is accepting logons to the access_ctrl_blk access control block.

Corrective Action: No action is required.

CTM7AEI monName - NO USER IS SIGNED ON TO THIS VTAM MONITOR

Explanation: This information message is issued if the operator inquires about active users in the monName VTAM, but there are none.

Corrective Action: No action is required.

CTM7AFI monName SETLOGON GNAMEADD FAILED FOR gname RTNCD=rtcnd,FDB2=fdb2

Explanation: The VTAM generic resource name was not added at logon.

The variables in this message are

• monName - the identity of the VTAM monitor
• gname - generic resource name
• rtcnd - VTAM return code
• fdb2 - VTAM FDB2

The monName IOA VTAM monitor ignores the failure and proceeds.

Corrective Action: Check the VTAM return code and FDB2 in the IBM manuals and correct the problem.

CTM7B0I monName - TERMINAL TRANSID

Explanation: This information message is issued as the result of an operator DISPLAY command to the monName VTAM monitor. This is a header for message CTM7B1I.

Corrective Action: No action is required.

CTM7B1I monName - terminal transid

Explanation: This information message is the result of an operator DISPLAY command to the monName VTAM monitor. It is displayed for each active user.

The variables in this message are

• monName - the identity of the VTAM monitor
• terminal - the identity of the VTAM terminal
• transid - the identity of the current transaction supplied as the DATA parameter of the LOGON command.

Corrective Action: No action is required.

CTM7B2E monName - VTAM MONITOR SHUT DOWN UPON VTAM FAILURE OR VTAM OPERATOR COMMAND

Explanation: The monName VTAM monitor is shutting down due to VTAM failure or upon operator request. When VTAM fails, or an operator closes the application, such as, by using an INACT command, the VTAM monitor shuts down.

The monName VTAM shuts down.

Corrective Action: Refer to prior messages in the system log to determine the cause of the VTAM monitor shutdown.

CTM7B3W stc - VTAM MONITOR, WAITING FOR VTAM STARTUP TO COMPLETE

Explanation: Highlighted, unrollable message.

The VTAM monitor (IOAVMON) cannot be initialized because VTAM is not active. This message is displayed on the console if the VTAM monitor (IOAVMON) is started before VTAM is active, usually at IPL time. When VTAM becomes available, the VTAM monitor will start its initialization process and this message will be deleted.

Wait for VTAM startup to be completed.

Corrective Action: No action is required.

CTM7B5I oper FROM TERMINAL terminal FAILED, WAITING TIME IS OVER

Explanation: This information message is issued if there is a delay of 30 seconds or more in either the IOAVMON logon or the IOAVMON logoff process. The process terminates.

The variables in this message are:

• oper--the identity of the IOAVMON logon or the IOAVMON logoff process
• terminal--the identity of the VTAM terminal

Corrective Action: If the delay occurs in the IOAVMON logon process, determine the reason for the delay and then try to logon again.