Messages CTM800 through CTM8xx

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.

CTM800E COMMAND NOT FOUND

Explanation: Invalid TSO command supplied.

Corrective Action: Correct the command and re-enter.

CTM801S PROGRAM pgm ABEND CODE abCode

Explanation: The pgm TSO program, which has been activated by the IOA Online interface, abended with the abend code abCode.

Corrective Action: You can continue working on any of the IOA screens.

CTM802S BLDL/LOAD FAILED FOR CTMTCON - "CTx TTRA" FACILITY NOT AVAILABLE

Explanation: BLDL/LOAD for the CTMTCON module failed (the DATRA DD statement). The DATRA DD statement should describe the IOA MINILOAD library which is used by the IOA screen transfer facility.

Corrective Action: Press Enter to enter the TSO command. To return to other IOA screens, exit the TSO command or application. Trying to use the TSO CTMTTRA or CTDTTRA command causes an error.

Correct the CLIST used to enter the IOA online interface so that you will not have to enter or exit TSO applications, such as ISPF, in an inconvenient way.

CTM803S PROGRAM pgm ACTIVE, CANNOT EXIT

Explanation: You entered an X command in one of the IOA screens, but the TSO program is still active. IOA expects you to exit the TSO application in an orderly manner.

Corrective Action: Press Enter to enter the TSO application. Exit from the TSO application. You will exit the IOA online interface. You cannot return to one of the IOA screens after you have entered the X command.

CTM804S OPEN FAILED FOR DDNAME "DATRA"- "CTxTTRA" FACILITY NOT AVAILABLE

Explanation: Opening of IOA MINILOAD file failed (the DATRA DD statement) during activation of a TSO application.

Activation of the IOA Online Transfer Facility requires loading of a special module from the IOA MINILOAD library. When this module is not loaded, the transfer facility does not function, but the TSO command is executed normally.

Possible causes are:

The DATRA DD statement is missing.
There is insufficient memory.

Corrective Action: Press Enter and you will enter the TSO command. To return to other IOA screens, exit the TSO command or application. Trying to use the CTMTTRA or CTDTTRA TSO command causes an error.

Correct the CLIST used to enter the IOA online interface so that you will not have to enter or exit TSO applications, such as ISPF, in an inconvenient way.

CTM805I CLISTS NOT SUPPORTED YET

Explanation: This information message states that CLISTs are not yet supported by Control-M or Control-D.

Corrective Action: Perform the CLIST under ISPF.

CTM806E MISSING OR INVALID TRANSFER PARAMETER

Explanation: A missing or invalid transfer parameter was supplied to the CTMTTRA or CTDTTRA TSO command. The transfer parameter should be one of the IOA screens or X. It must be specified in the command line of the TSO application (for example, ISPF).

Transfer is not performed.

Corrective Action: Press Enter to return to the TSO command, and enter a correct parameter.

CTM807E MAXIMUM TSO LEVELS EXCEEDED. CANNOT OPEN "CTxTTRA" ENVIRONMENT

Explanation: More than four levels of IOA Online interface have been opened, one under the other. Only four TSO levels are allowed for the transfer facility.

You can open more than four TSO levels, but the system will not allow a transfer between them.

Corrective Action: Either use the END command to exit at least one TSO level, or do not transfer between TSO levels.

CTM808E MEMBER $$ID IS IN USE BY ANOTHER USER (RC=rc)

Explanation: The $$ID member in the JCL library that was specified in the //*CONTROLM statements is being held by you or another user. This member is being held for editing. It must be released if the job is to be ordered.

The job is not ordered.

Corrective Action: Try to resubmit the job. If it fails again, find out who is holding the member, and have the member released.

CTM809E DYNAMIC ALLOCATION OF DDNAME "DAINTRDR" FAILED, RC=rc,errCode

Explanation: Dynamic allocation of internal reader (INTRDR) by the Control-M Quick Submit command failed. This message appears while trying to submit a job under ISPF by the Control-M Quick Submit command.

The variables in this message are:

rc - the return code of the failed allocation
errCode - the error code and information code that were returned from that SVC

The job is not submitted.

Corrective Action: Refer to IBM documentation on dynamic allocation. Compare with the data in the message and correct accordingly.

CTM810E SUBMIT FAILED - OPEN OF DDNAME "DAINTRDR" FAILED

Explanation: Open of the DAINTRDR dynamically allocated DD statement failed (Control-M Quick Submit command).

The job is not submitted.

Corrective Action: Look for additional information that will clarify the reason for the problem, for example, the console log, TSO sysout, and the like.

CTM811E INTERNAL ERROR IN CTMQSB - NOTIFY THE IOA ADMINISTRATOR error_code,rc

Explanation: An internal error occurred in either the Quick Submit program (CTMQSB) or a user program that calls the CTMAJO Control-M routine.

The job is not ordered.

Corrective Action: If error_code,rc is SELECTAB, xx the CTMAJO routine returned an unknown return code (xx) to the calling program.

If this error was encountered during an ISPF submit command, call the INCONTROL administrator.
If it occurred in a user program, correct it to support all the possible return codes that the CTMAJO routine can return.
Otherwise, call your INCONTROL administrator.

CTM812E MISSING/INVALID INFORMATION IN "//*CONTROLM" CARDS (RC=rc)

Explanation: The //*CONTROLM statement or statements in the job contain invalid or insufficient information for performing the job-order (Control-M Quick Submit Command).

Return codes values:

Return Code	Explanation
04	Only one type of Control-M statement has been found; there should be two: TABLE and JCL.
08	Invalid keyword as the first parameter in a //*CONTROLM statement.
12	Missing tables scheduling library parameter.
16	Missing table name parameter.
20	Missing JCL library parameter.

The job is not ordered.

Corrective Action: Correct the error and submit again.

CTM813E UNABLE TO READ TABLE tableName (RC=rc)

Explanation: The Control-M Quick Submit command failed to locate the table member specified in the //*CONTROLM TABLE statement.

Valid values for rc are:

Return Code	Explanation
8	There is insufficient memory.
12	The tableName table member was not found in the specified scheduling library.
36	The library specified was not found.

The job is not ordered.

Corrective Action: Correct the error and submit the job again.

CTM814E UNABLE TO READ THE $$ID MEMBER. (RC=rc)

Explanation: Open or read of the $$ID member in the JCL library failed. (Control-M Quick Submit command).

Possible return code values, and their explanations, are:

12 - The $$ID member is not in the library specified in the //*CONTROLM JCL statement.
36 - The library specified in the //*CONTROLM JCL statement was not found.

The job is not submitted.

Corrective Action: Look for additional information that will clarify the reason (for example, the console log, TSO sysout, and so on).

CTM815E ERROR WHILE UPDATING THE $$ID MEMBER. (RC=rc)

Explanation: Update of the $$ID member in the JCL library failed (Control-M Quick Submit command). A return code of 56 indicates a D37 abend on the library specified in the //*CONTROLM JCL statement.

The job is not submitted.

Corrective Action: Look for additional information that will clarify the reason. For a return code of 56, compress or enlarge that library.

CTM816E ERROR WHILE SAVING THE JOB. (RC=rc)

Explanation: Writing the job to the JCL library failed (Control-M Quick Submit command).

Possible values of rc, and their explanations, are:

56 - There is insufficient space (abend D37) in the library specified in the //*CONTROLM JCL statement. Possible reasons are:
The directory is full in the library specified in the //*CONTROLM JCL statement.
The data set needs a secondary extent, but DASD space is not available.
A security violation has occurred.
64 - The member already exists or there is no space in the directory.

The job is not submitted.

Corrective Action: Do one of the following:

If the return code is 56, compress or enlarge the appropriate library.
If the return code is 64, there is a member in that library with the same name. Determine the reason and correct the problem.

CTM817E INVALID ID-NUMBER IN THE $$ID MEMBER

Explanation: The five characters in the first line of the $$ID member in the JCL library are not numeric. There should be one line containing the current ID. It should be five numeric digits, and left-justified.

The job is not submitted.

Corrective Action: Correct the $$ID member accordingly.

CTM821I MANUAL-COND cond ODATE odate action

Explanation: This information message displays the results from NEW or ERASE command. The condition cond of the odate original scheduling date was either erased from the Manual Conditions file or added to the Manual Conditions file.

Corrective Action: No action is required.

CTM822E MISSING PARAMETER OF NEW REQUEST

Explanation: The NEW command was supplied without any additional parameter. At least one parameter is expected after the NEW command. Valid parameters are COND, LCOND or CONDITION.

Corrective Action: Supply the correct command.

CTM823E INVALID TYPE IN NEW REQUEST

Explanation: Invalid NEW type supplied. At least one parameter is expected after the NEW command. Valid parameters are COND, LCOND or CONDITION.

Corrective Action: Specify the requested NEW type.

CTM824I MANUAL-COND cond ODATE odate EXISTS

Explanation: This information message indicates that the condition added by the NEW command already exists in the file.

Addition request ignored.

Corrective Action: No action is required.

CTM825E NEW FOR cond ODATE odate FAILED. FILE IS FULL

Explanation: The Manual Conditions file is full.

The condition is not added to the file.

Corrective Action: Try to delete conditions from the specified day in other months of the year. If you need all the conditions in the file for all the months, then consult your system programmer about the possibility of increasing the capacity of the IOA Manual Conditions file.

CTM826E CONDITIONS FILE OR MANUAL CONDS FILE IN USE, PLEASE TRY AGAIN LATER

Explanation: Another user or another IOA component is currently updating the file.

The command requested is not performed.

Corrective Action: Try again.

CTM828E UNEXPECTED RETURN CODE FROM CTMUNR

Explanation: Internal error. Invalid return code from the CTMUNR Control-M internal utility.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM829S INTERNAL ERROR - INVALID REQUEST TO CTMUNR

Explanation: Internal error. Invalid request to the CTMUNR IOA internal utility.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM830S INTERNAL ERROR - INVALID RESOURCE TYPE (CTMUNR)

Explanation: Internal error. Invalid resource type passed to the CTMUNR IOA internal utility.

The function requested is not performed.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM831E MANUAL-COND cond ODATE odate IS NOT IN THE FILE

Explanation: The cond condition that was marked for addition (the A option) has been deleted from the Manual Conditions file. While you were working on the screen, another IOA user deleted the condition from the Manual Conditions file.

The condition is not added to the Conditions file.

Corrective Action: Manually add the deleted condition to the Manual Conditions file using Screen 4.

CTM832E AT LEAST ONE OF "PENDING" OR "ADDED" MUST BE "Y"

Explanation: Neither the PENDING nor the ADDED option is marked as Y.

Corrective Action: Mark one retrieval option as Y.

CTM833S INTERNAL ERROR. INVALID RETURN CODE FROM CTMUNR

Explanation: Internal error. Invalid return code from the CTMUNR Control-M internal utility.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM834S OPEN OF IOA MANUAL CONDITIONS SYNC FILE FAILED

Explanation: Open of the IOA Manual Conditions Synchronization file failed. Possible causes are:

The DANSINC DD statement is missing.
The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but is a different version or for a different IOA installation.

Corrective Action: Correct the JCL for the job or the allocations of the CLIST.

CTM835S FILE ALLOCATED TO DDNAME "DANSINC" IS NOT THE MANUAL SYNC FILE

Explanation: The file allocated to the DANSINC DD statement is not the Manual Conditions Synchronization file. Possible causes are:

The file allocated to the DANSINC DD statement is not the IOA Manual Conditions Synchronization file.
The file allocated to the DANSINC DD statement is the IOA Manual Conditions Synchronization file, but it is a different version or for a different IOA installation.

Corrective Action: Check your TSO user allocations, and check for specific messages on the system log.

CTM836E VALID VALUES ARE 'P' 'N' '-' OR '+'

Explanation: The SAC job scheduling parameter for a Group entity scheduling definition contains an invalid value.

Valid values for SAC for a group entity job definition are:

P - previous day
N - next day
- (minus sign) - previous day only
+ (plus sign) - next day only

Corrective Action: Correct the value.

CTM837E VALID VALUES ARE 'P' OR 'N'

Explanation: The SAC job scheduling parameter for a job scheduling definition contains an invalid value.

Valid values for SAC for a job scheduling definition are:

P - previous day
N - next day

Corrective Action: Correct the value.

CTM846S INSUFFICIENT SPACE FOR type cond odate

Explanation: The output IOA Conditions file has insufficient space for all the prerequisite conditions from the input file. The combination of the LRECL parameter with the CNDREC# parameter is smaller in the output file than in the input file, and some prerequisite conditions in the input file could not be copied to the output file.

The variables in this message are:

type - the type of condition
cond - the condition name
odate - the original date

Conversion or copying of the file stops. The content of the output file is unpredictable.

Corrective Action: Create a larger output file and run the utility again.

CTM850S modName BLDL FAILED FOR MODULE

Explanation: BLDL for the modName module failed.

Probable causes are:

The module is not in one of the load module libraries used by the IOA Online Facility (Linklist, STEPLIB or invoked CALL library).
There is insufficient memory to load the program.

The modName module is not activated. Control is returned to the calling program. The IOA Online Facilities may abend on initialization.

Corrective Action: Verify whether the module appears in IOA Load library or any other concatenated load module library.

CTM855S INVALID PARAMETER SUPPLIED TO MODULE mod-name - parm

Explanation: Either an input parameter was omitted from, or an invalid input parameter (parm) was supplied to, the modName main IOA online module.

The variables in this message are:

modName - the name of the main IOA online module
parm -the identity of the missing or invalid parameter

The modName module expects a series of parameters to be input, describing the environment in which it is to be activated. The expected parameters are:

APPLTYPE=type,APPLID=id

In this expression:

type is S (for TSO), R (for KSL), I (for ISPF) or X (for OMEGAMON)
id is the user application ID

The IOA online environment is not built.

Corrective Action: Check for errors in the CLIST which activates the IOA online interface.

CTM856S DDNAME ddName NOT ALLOCATED

Explanation: Highlighted, unrollable message.

The DD name specified in the error message was not allocated before the user entered IOA.

The IOA Online facility terminates.

Corrective Action: Allocate the specified DD name and reenter IOA.

CTM857S PRODUCT productName NOT RECOGNIZED

Explanation: Highlighted, unrollable message.

A user tried to enter IOA using a user-defined transaction member which contained a definition of a product not recognized by IOA.

The IOA Online facility stops.

Corrective Action: Correct the product definition in the transaction member and reenter IOA.

CTM858S MEMBER NAME - memName IN TRANID transMem NOT FOUND IN PARM LIBRARY

Explanation: Highlighted, unrollable message.

A user tried to enter IOA using a user-defined transaction. The TRANID refers to a member which pointed to a PGM member name that did not exist in the parameter library referenced by the DD name DAONLPRM.

The Online facility terminates.

Corrective Action: Check that the PGM member is correctly specified in the transaction member. If it is correctly specified in this member, add it to the parameter library. Reenter IOA.

CTM859E INVALID RC rc FROM routineName ROUTINE

Explanation: The program ended with unexpected return code.

If the CTMRCAL utility is running, rc is 16, and routineName is IOABSR. In this case, the REPTYPE utility control statement is probably missing the S subparameter.

System action depends on the calling program. Execution may continue, or it may stop with a condition code of 08 or 12.

Corrective Action: If the REPTYPE utility control statement is missing the S subparameter, specify it with the S subparameter as REPTYPE nS, where n is 0, 1 or 2. Otherwise, notify your INCONTROL administrator.

CTM859S TRANID MEMBER NOT FOUND - transMem

Explanation: The user tried to enter IOA using a user-defined transaction. TRANID refers to a member that does not exist in the parameter library referenced by the DAONLPRM DD statement.

The IOA Online facility stops.

Corrective Action: Add the transaction member identified in the message to the parameter library and reenter IOA.

CTM85AS INVALID KEYWORD FOUND IN - transMem

Explanation: The user tried to enter IOA using a user-defined transaction. The TRANID refers to a member which contained an invalid keyword.

The Online facility stops.

Corrective Action: Check the keywords in the transaction member and correct them accordingly. See the section on transaction members in the INCONTROL for z/OS Administrator Guide. Reenter the IOA Online facility.

CTM85BS PLEASE CHECK THE TRANID MEMBER - transMem.

Explanation: An internal error occurred when a user tried to enter IOA using a user-defined transaction.

The internal error occurred when the IOA Online facility tried to initiate the IOA session using the transaction member identified in the message.

The IOA Online facility stops.

Corrective Action: Supply BMC Customer Support with a printout of the transaction member identified in the message.

CTM85CS ERROR OCCURRED DURING ALLOCATION PROCESS. PLEASE CHECK THE ALC MEMBERS

Explanation: IOA online system failed to allocate a file.

When the IOA Online facility starts up, it allocates all the files needed for the current session. At least one of these files could not be allocated.

Preceding messages detail the files that could not be allocated.

The IOA Online system stops.

Corrective Action: Correct the ALC xxx members according to information from the preceding messages and reenter IOA.

CTM85DS ddName DDNAME IS ALLOCATED. PLEASE FREE IT AND TRY AGAIN

Explanation: The ddName file was already allocated to the IOA Online environment when the IOA Online facility started up.

When the IOA Online facility starts up, certain files are dynamically allocated by it to the IOA environment. In this case, the ddName file identified in the message was already allocated to the IOA environment when IOA started up.

The Online facility terminates.

Corrective Action: Deallocate this DD name from the IOA environment.

CTM85ES MODULE modName RETURNED WITH RC=rc

Explanation: A severe error occurred in the modName module when the user tried to enter an IOA option. In most cases, the called program could not issue an error message.

Valid values for rc are:

rc	Explanation
08	There is no region below the line for the application.
12	There is no region above the line for the application.
16	A severe error occurred. The called program issued an error message.
20	A severe error occurred. An error message could not be issued.

The called program abends.

Corrective Action: The user response depends on the return code, as follows:

08 / 12 - In case of TSO, log off and log on again. In case of IOAOMON, stop and restart IOAOMON. If this does not help, reduce the number of IOAOMON users by modifying the MAXSESS parameter in the IOAXPRM member.
16 - Follow the instructions in the error message issued by the called program.
20 - Contact BMC Customer Support.

CTM85FS MAXIMUM NUMBER OF IOA SESSIONS REACHED

Explanation: TSO user tried to activate a fifth IOA session in his TSO address space.

In the TSO environment, the user can activate IOA sessions by executing the IOATSO or IOAISPF CLISTs. IOA allows a maximum of four sessions to be activated. If the user tries to activate a fifth session, this error message is generated.

The fifth session is not established.

Corrective Action: Terminate one of the previous sessions in order to initiate a new session.

CTM85IS GLOBAL PROFILE VARIABLES ($PROFILE) COULD NOT BE ACCESSED

Explanation: An attempt to access the $PROFILE member in the IOAENV library failed.

The most common cause is that the member is held by another user or program.

The IOA Online facility is not entered.

Corrective Action: Determine which user or program is holding the member, and try to obtain its release.

CTM860E OPTION NOT SUPPORTED YET

Explanation: The requested option is not yet supported. The option will be available in future IOA releases.

Corrective Action: No action is required.

CTM861I PLEASE SELECT OPTION

Explanation: No option selected.

Corrective Action: Select one option.

CTM862S ERROR IN COMMAND MEMBER - CALL SYSTEM PROGRAMMER

Explanation: Each IOA screen is controlled by an external command member that contains a list of all the commands and synonyms supported by the screen. Command members reside in IOA parameter libraries. They should be named T scrCMD1, where scr is the screen name.

Possible causes for this error message are:

Somebody incorrectly changed the contents of the command member.
The DACMD xx DD statement is allocated to the wrong library.

For more information on command members, see the section that describes how to define new application types in the IOA chapter of the INCONTROL for z/OS Installation Guide.

The screen is locked.

Corrective Action: To exit, press PA1 a few times. Allocate the parameters library to the DACMD xx DD statement, where xx is the application ID. If necessary, call your system programmer for assistance.

CTM863W THE CONTROL-M ACTIVE JOBS FILE IS NEARLY FULL

Explanation: Highlighted, unrollable message.

This message is issued when the threshold value specified by the AJFTHRSH CTMPARM parameter is reached. The message is issued in conjunction with message CTML17I, which displays the percentage of the Active Jobs file currently utilized.

Corrective Action: Contact your INCONTROL administrator immediately. It may be necessary to compress the Active Jobs file or to increase its size.

CTM864I PLEASE NOTIFY THE IOA ADMINISTRATOR

Explanation: Highlighted, unrollable message.

This message is usually issued after a severe Control-M error that must be handled by an experienced Control-M person.

Corrective Action: Contact your INCONTROL administrator immediately.

CTM865E PLEASE FILL IN FROM STEP

Explanation: Possible causes for this message are:

RESTART is set to Y in the rerun or confirmation window, but the FROM field is blank.
A TO step name is specified in the restart decision line in the Zoom screen (Screen 3), but the FROM step field is blank.
STEP RANGE name is specified, but the FROM field in this STEP RANGE line is blank.

Corrective Action: Specify a step name in the FROM field, or set RESTART to N, erase the TO step name, and erase the STEP RANGE name.

CTM866E PLEASE FILL IN A VALID SET STATEMENT. FORMAT "%%VARNAME=VALUE"

Explanation: Invalid specification of an AutoEdit assignment in a DO SET statement.

The correct syntax for the SET statement line is: DO SET %%VARNAME=VALUE (for example, DO SET %%THISRUN=RERUN).

Corrective Action: Correct the AutoEdit variable assignment.

CTM867E INSUFFICIENT MEMORY, UNABLE TO PROCESS

Explanation: There is insufficient memory to perform the requested action.

The request is ignored.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM868E TABLE "dsn (tableName)" IS IN USE. TRY AGAIN LATER

Explanation: The specified member from an IOA definition library is currently in use by another user.

The variables in this message are:

dsn - the name of the data set containing the requested table
tableName - the name of the requested table

The request is ignored.

Corrective Action: Wait until the requested member is freed, then retry the request.

CTM869E TABLE "tableName " IS NOT A VALID SCHEDULING TABLE (CARD NUMBER stmtNum)

Explanation: The job table that was to be downloaded to Control-M/Enterprise Manager is not a valid scheduling table, for example, because the format of a statement is incorrect.

The variables in this message are:

tableName - the name of the problematic job table
stmtNum - the line number of the problematic statement within the job table

The download request is ignored.

Corrective Action: Either correct the errors in the scheduling table or specify the name of a valid scheduling table, then retry the download request.

CTM86AE INVALID VALUE, USE [0-9999]S or [0-9999]M FOR Delayed_Submission_variable

Explanation: Invalid value of a Delayed Submission variable in a DO SET or SETVAR statement.

Corrective Action: Correct the value of the Delayed Submission variable to a number between 0 and 9999, followed by S for a delay in seconds or M for a delay in minutes. The value cannot be more than 4 digits.

CTM86BE THIS IS A DELAYED SUBMISSION VARIABLE, USE ANOTHER VARIABLE NAME

Explanation: Incorrect use of a Delayed Submission variable in an INTO field of the CAPTURE BY option in the 2.Z or 3.Z screen.

Corrective Action: Do not use this variable name, as it is reserved for a Delayed Submission variable. Choose another variable name.

CTM86DE TOO MANY SETVAR STATEMENTS SPECIFIED

Explanation: More than 256 SETVAR statements have been specified in ORDER request.

The request is ignored.

Corrective Action: Specify up to 256 SETVAR statements.

CTM870E CTMMEM FAILED. TABLE=tableName, FUNCTION=func, RC=rc

Explanation: The CTMMEM internal service routine ended with an error.

The variables in this message are:

tableName - the name of the table for which CTMMEM was issued
func - the name of the relevant function
rc - the return code of the error

For more information about CTMMEM functions and return codes, see the DOCIMEM member in the IOAP DOC library.

The download request is ignored.

Corrective Action: Note the values of tableName, func, and rc, prepare the Control-M monitor full output, and contact BMC Customer Support.

CTM871S CTMDUL INITIALIZATION FAILED: descr

Explanation: The initialization of the CTMDUL internal program failed.

In this message, descr is a brief description of the reason for the failure. Possible values for descr are:

LOAD FAILED FOR MODULE modName
GETMAIN FAILED

No tables are downloaded.

Corrective Action: Have your system programmer prepare the Control-M monitor full output and contact BMC Customer Support.

CTM872E TABLE tableName HAS BEEN CHANGED SINCE LAST DOWNLOAD. UPLOAD FAILED

Explanation: Uploading of a table to the mainframe was attempted. However, the table was changed following the last download to the Control-M/Desktop. Jobs can be uploaded to a table after another being downloaded by another user. However, this wipes out any jobs updated to the mainframe since the last download.

The upload utility terminates with a return code of 12.

Corrective Action: Either force the table to be uploaded or save the table under another table name. Force uploading a table will overwrite any earlier version currently on the mainframe. Use great caution with a forced upload. If a forced upload is used, jobs updated to the mainframe since the last download will be lost.

CTM873E ERROR CONVERTING TABLE "tableName " JOB "jobName ": descr

Explanation: The job could not be downloaded or uploaded.

The variables in this message are:

tableName - the identity of the problematic table
jobName - the identity of the problematic job
descr - a short description of the cause of the failure

The download or upload request is ignored.

Corrective Action: Proceed on the basis of the information contained in descr.

CTM874S NEW TABLE "tableName " IS TOO BIG (MORE THAN 200,000 CARDS)

Explanation: The job table could not be uploaded to Control-M because it would require more than 200,000 statements.

The maximum size of a job table is 200,000 statements.

In this message, tableName is the name of the problematic job table.

The upload request is ignored.

Corrective Action: Correct the contents of the tableName job table so that it requires less than 200,000 statements when uploaded to Control-M.

CTM875E PLEASE FILL IN CALENDAR NAME OR OMIT YEAR

Explanation: A year was specified, but the calendar name is missing. A year can be defined only in a calendar.

Corrective Action: Either fill in a calendar name or omit the year to get a list of calendars in the library.

CTM880E CANNOT ADD MORE YEARS TO CALENDAR (MAXIMUM 10)

Explanation: The calendar is full. The maximum number of years in a calendar is 10. You cannot add more years.

Corrective Action: Split the calendar into two calendars, or delete unnecessary years.

CTM881E CALENDAR TOO LARGE. ERASE UNNECESSARY YEARS

Explanation: The calendar is too large to be handled by IOA Online.

Possible causes are:

Insufficient storage to process the calendar.
The calendar is too large.

Corrective Action: Do one of the following:

Log on again using a larger size parameter.
If you are using many IOA screens concurrently, exit some of them using the END command.
Split the calendar into two calendars.
Erase redundant years from the calendar.

CTM885E INVALID YEAR (OR YEAR NOT IN VALID RANGE)

Explanation: The specified year is not a valid year, or is not in the range supported in IOA.

Corrective Action: Specify a valid year.

CTM886I TOP OF YEARS LIST

Explanation: This information message indicates that the current year is the first year in the years list. The message may appear after entering the command PREVYEAR in the Year screen.

Corrective Action: No action is required.

CTM887I BOTTOM OF YEARS LIST

Explanation: This information message indicates that the current year is the last year in the years list. The message may appear after entering the command NEXTYEAR in the Year screen.

Corrective Action: No action is required.

CTM888E VALID OPTIONS ARE "Y", "+", "- ", "N" OR BLANK

Explanation: An invalid day selection option has been specified. The cursor points to the invalid day value.

Valid day selection options are:

Y - Yes
N - No
' ' (blank) - No
+ (plus) - the next date in a relative calendar
- (minus) - the previous date in a relative calendar

Corrective Action: Specify Y, N, +, -, or blank.

CTM891E OPTION SPECIFIED IS INVALID IN CASE OF A PERIODIC CALENDAR

Explanation: The characters Y, N, +, and - are not supported under periodic calendars.

Corrective Action: Use another period identifier.

CTM899E REDUNDANT PARAMETER

Explanation: The number of occurrences of the fields listed below exceeds the maximum number allowed:

DATES - 12
WDAYS=DnWm parameters - 11
MAIL-TO, MAIL-CC, MAIL-TX - 255
RMD-SUM - 2
RMD-DES - 15

Corrective Action: Delete the additional occurrences and rerun the job.

CTM89AS LIBRARY NAME IS NOT SPECIFIED

Explanation: Either the LIBRARY parameter was not specified, or the specified library does not exist.

Corrective Action: Depending on the cause, either correct the specification or create the specified library; then rerun the job.

CTM89BE PLEASE SPECIFY parm

Explanation: The parm parameter is missing. At least one TABLE parameter is required after the LIBRARY parameter. At least one MEMNAME parameter is required for each TABLE parameter.

Corrective Action: Add any missing statements, and rerun the job.

If an attempt is being made to create a group scheduling table with only a group entity and no job scheduling definitions, then set the EMPTYGRP parameter to Y in the CTMPARM member of the IOA PARM library, and then rerun the job.

CTM89CE SPECIFIED SUB-PARAMETER IS OUT OF SEQUENCE

Explanation: The parameter or subparameter specified is out of sequence.

The sequence in which certain parameters and subparameters appear in a CTMBLT input file is important. For more information on this sequence, see the Control-M chapter in the INCONTROL for z/OS Utilities Guide.

This message is accompanied by other messages that provide additional information, including a message that identifies the parameter or subparameter that was not coded in the correct sequence.

Corrective Action: Correct the sequence of the parameters and subparameters and rerun the job.

Parent Topic

CTM messages