Messages CTMR00 through CTMRxx

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.

CTMR01W Control-M AJF SPACE REUSE FACILITY WILL BE ACTIVATED AFTER NEWDAY, AJF FORMAT OR COMPRESS

Explanation: The AJF Space Reuse Facility was enabled by the user, but the AJF has not yet been formatted to include the special index records required to manage the AJF Space Reuse Facility.

The AJF Space Reuse Facility will be activated automatically by Control-M after the upcoming New Day process.

Corrective Action: No action is required.

CTMR02E CONTROL-M AJF SPACE REUSE FACILITY DISABLED. REASON rsn

Explanation: Internal facility-wide errors were encountered in the AJF Space Reuse Facility.

The possible values of rsn are explained in the following table:

rsn	Explanation
WRONG MIF	Invalid index record detected
MIF ERROR	Invalid index record structure detected
NO MEMORY	GETMAIN failure
CTMMIF	Error encountered in module CTMMIF
READTGT	Error encountered in READTGT routine
WRITTGT	Error encountered in WRITTGT routine
GETMAIN	GETMAIN failure
FREEMAIN	FREEMAIN failure

The AJF Space Reuse Facility is disabled.

Corrective Action: Do the following:

Contact BMC Customer Support.
To reactivate the AJF Space Reuse Facility, format or compress the AJF and recycle the Control-M monitor.

CTMR03I JOB jobName ORDERID orderId PERMANENTLY DELETED FROM AJF

Explanation: This information message indicates that the AJF Space Reuse Facility is active and, as expected, deleted an entry from the AJF.

Corrective Action: No action is required.

CTMR04E INTERNAL ERROR IN AJF SPACE REUSE PROCESSING FOR JOB jobName/orderId CODE rsn

Explanation: Internal errors were encountered in the AJF Space Reuse Facility for this job.

The possible values of rsn are explained in the following table:

rsn	Explanation
GROUP JOB	error in removing a job from a group
END TIME	error in extracting the job's end time

The indicated job will not be deleted from the AJF.

Corrective Action: No action is required.

CTMR05E AJF SPACE REUSE FACILITY IS NOT ACTIVATED BECAUSE AJF IS FULL

Explanation: The user formatted or compressed the AJF, but there is no room for the special index records required to manage the AJF Space Reuse Facility.

The AJF Space Reuse Facility is not activated.

Corrective Action: To reactivate the AJF Space Reuse Facility, format a larger AJF and recycle the Control-M monitor.

CTMR06E ATTEMPTING TO REUSE ACTIVE AJF ENTRY. AJF SPACE REUSE FACILITY DISABLED.

Explanation: When Control-M attempted to reuse an unused job entry in the AJF, a last-moment check indicated that the job entry slot in the AJF was an active entry. This is an unexpected internal error.

The AJF Space Reuse Facility is disabled.

Corrective Action: Do the following:

Contact BMC Customer Support.
To reactivate the AJF Space Reuse Facility, format a larger AJF and recycle the Control-M monitor

CTMR07E activeJobEntrySlot

Explanation: This message displays the first 65 characters of the active job entry slot referenced by message CTMR06E.

Corrective Action: No action is required.

CTMR09E userExit CANNOT BE RELOADED BY THE RELOAD COMMAND (reason)

Explanation: The RELOAD= userExit operator command was issued by the user, but it aborted because of one of these reasons:

reason	Explanation
NOT 123415	The user attempted to reload a module which is not CTMX001, CTMX002, CTMX003, CTMX004, or CTMX015
LINK-EDITED	The user attempted to reload CTMX001 but it has been link-edited by the user into CTMJOB, or the user attempted to reload CTMX002 but it has been link-edited by the user into CTMSUB
NOT FOUND	The user attempted to reload a user exit but it was not found in the STEPLIB concatenation

The RELOAD command is aborted.

Corrective Action: No action is required.

CTMR0AI userExit RELOADED. OLD=mm/dd/yy-hh.mm NEW=mm/dd/yy-hh.mm

Explanation: This information message indicates that the userExit user exit was successfully reloaded as a result of the RELOAD= userExit operator command. The date and time of the 'old' and 'new' user exits are only accurate when the IOAEXNM userExit macro is used to provide standard entry linkage in the user exit.

Corrective Action: No action is required.

CTMR0BW taskname INT. ERR, MAYBE DELETE: grpnameapplorder_idodate

Explanation: This warning message indicates that there was an internal error in taskname during the New Day procedure. As a result of this error, grpname might be deleted from the Active Jobs file.

The variables in this message are:

grpname--the group entity name
appl--the application to which the group entity belongs
order_id--the order ID of the group entity
odate--the ODATE of the group entity

Corrective Action: Send the Control-M Backup Active Jobs file and the output of the New Day procedure to technical support.

CTMR0CE 'DO REMEDY' ERROR: error

Explanation: Control-M encountered an error when attempting to execute a DO REMEDY request.

The possible values of error that can appear are explained in the following table:

error	Explanation
INIT FUNCTION FAILED RC = rc	The initialization function failed with a return code of rc.
SEND FUNCTION FAILED RC = rc	The send function failed with a return code of rc.
FEATURE DISABLED	The feature has previously been disabled.
TICKET ALREADY OPEN FOR JOB	A REMEDY problem ticket has already been opened for this job.
SUMMARY LINE TRUNCATED	The summary line was too large and was truncated.
DESCRIPTION LINE TRUNCATED	The description line was too large and was truncated.
ERROR IN DO REMEDY CODES	An internal error was encountered in the schedule definition.

Corrective Action: The following table has valid return code (rc) values for the error SEND FUNCTION FAILED, together with their explanations and the appropriate corrective action.

Return Code	Explanation	Corrective Action
64	Can not load IOAMAIL.	Contact BMC Customer Support.
68	Can not load IOAMEM.	Contact BMC Customer Support.
72	At REMTMPLx one of the variables which are surround by double %% are not defined, a valid variables are: SUMM DESC URGENCY USER	Check REMTMPLx for invalid variable.
76	REMCONF or REMTMPLx member at IOA.PARM does not exist.	Check the existence of REMCONF member or REMTMPLx at IOA.PARM library or the filed REMTMPLS at REMCONF to suits one of the REMTMPLx.
80	REMCONF member at IOA.PARM is corrupted.	Check REMCONF member for missing single quotes or undefined fields.

The DO REMEDY request is aborted (or sent truncated if the summary or description was too large).

Contact BMC Customer Support.

CTMR0DE 'DO REMEDY' FEATURE IS DISABLED

Explanation: Control-M encountered an error during the initialization or send function of a DO REMEDY request.

All DO REMEDY requests are aborted until Control-M is recycled.

Corrective Action: Contact BMC Customer Support.

CTMR0FW INT. ERR, JOB HLD: tasknamegrpnameapplorder_idodate

Explanation: This warning message indicates that there was an internal error in taskname during the New Day procedure.

The variables in this message are:

grpname--the group entity name
appl--the application to which the group entity belongs
order_id--the order ID of the group entity
odate--the ODATE of the group entity

As a result of this error, the job is put on hold and the job is longer part of group grpname.

Corrective Action: Send the Control-M Backup Active Jobs file and the output of the New Day procedure to technical support.

CTMR11I JOB/GROUP name ORDERID orderId COPIED TO HISTORY AJF

Explanation: This information message indicates that job name, whose order ID is orderId, was successfully copied to the History AJF. The job records are now available for space reuse.

Corrective Action: No action is required.

CTMR12E COPY TO HISTORY FILE FAILED: rsn REASON CODE: rc

Explanation: An error occurred while copying records from the AJF to the History AJF.

The variables in this message are:

rsn - the cause of the error
rc - the reason code, which may contain additional information

History processing for space reuse jobs is disabled. Jobs having a retention period will no longer be eligible for space reuse.

Corrective Action: No action is required.

CTMR13E JOB/GROUP name ORDERID orderId

Explanation: This message accompanies message CTMR12E and indicates that job name, whose order ID is orderId, was being processed when the error occurred.

Corrective Action: No action is required.

CTMR14E ALLOCATION OF FILE fileName FAILED RC rc

Explanation: The Control-M Monitor failed to allocate the fileName file. The reason for the failure is described by a return code value of rc.

The Control-M monitor continues normal processing. Since the History file is not allocated to the Control-M monitor, jobs having a retention period will no longer be eligible for space reuse.

Corrective Action: Use the return code (rc) to determine the cause of the allocation error and use the modify command HISTALOC=ENABLE to try and allocate the History file again.

CTMR15E DEALLOCATION OF FILE fileName FAILED RC rc

Explanation: The Control-M Monitor failed to deallocate the fileName file. The reason for the failure is described by a return code of rc.

The Control-M monitor continues normal processing.

Corrective Action: Use the return code (rc) to determine the cause of the allocation error and use the modify command HISTALOC=DISABLE to try and deallocate the History file.

CTMR16E VALUE MUST BE C(DEFAULT), V(VARYING), OR S(RUN AT SPECIFIC TIMES)

Explanation: An invalid option has been entered in the CYCLIC type field. The valid values are:

C - A cyclic job can be submitted only at fixed intervals (such as every 5 minutes or every hour).
V - Varying intervals when a cyclic job can be submitted (such as every 30 minutes, and every hour, and every 3 days).
S - Specific times when a cyclic job can be submitted (such as at 9 AM, or at 2 PM).

Corrective Action: Specify C or V or S, or leave the field blank (same as entering a value of C ).

CTMR21I CTMRSMF STARTED

Explanation: This information message indicates that the CTMRSMF utility has begun.

Corrective Action: No action is required.

CTMR22I CTMRSMF ENDED

Explanation: This information message indicates that the CTMRSMF utility has ended normally.

The utility terminates normally with a return code of zero.

Corrective Action: No action is required.

CTMR23S UNABLE TO OPEN SMF INPUT FILE

Explanation: The CTMRSMF utility was unable to open the input SMF file.

The utility terminates with a return code other then zero.

Corrective Action: Check the JCL to ensure that the dd statement DASMF is pointing to a valid SMF file.

CTMR24S UNABLE TO OPEN CSV OUTPUT FILE

Explanation: The CTMRSMF utility was unable to open the output .CSV file.

Processing terminates with non-zero return code

Corrective Action: Check the JCL to ensure that the dd statement DACSV is present pointing to a valid CSV file.

CTMR25S INVALID SMF RECORD - SEE SNAP

Explanation: During execution of the CTMRSMF utility, an invalid SMF record was encountered in the DASMF file.

The utility terminates with a return code other then zero.

Corrective Action: Send all the output from the CTMRSMF job to BMC technical support.

CTMR27E UNABLE TO OPEN PRINT FILE, DDNAME "DAREPORT"

Explanation: The CTMEVRT utility was unable to open the output DD DAREPORT.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMR28E UNABLE TO OPEN THE ddname DD

Explanation: The CTMEVRT utility was unable to open the input or output DD specified.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMR29E INCLTIME NOT SPECIFIED

Explanation: The period of time DSNEVENTs were not handled by CMEM must be specified for the CTMEVRT utility.

The utility terminates with a return code of 8.

Corrective Action: Specify the recovery time range using the INCLTIME parameter.

CTMR2AE SYSID OR SYSTEM NOT SPECIFIED

Explanation: The system identification must be specified for the CTMEVRT utility.

The utility terminates with a return code of 8.

Corrective Action: Specify the LPAR for which the events must be recovered, by using either the SYSID or SYSTEM parameters.

CTMR2BE INVALID STATEMENT SPECIFIED

Explanation: An invalid statement was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Correct the SYSIN statement.

CTMR2CE DUPLICATE STATEMENTS SPECIFIED

Explanation: Duplicate statements were specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Remove one of the duplicate SYSIN statements.

CTMR2DE INVALID VALUE SPECIFIED

Explanation: An invalid value was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid value.

CTMR2EE INVALID TIME SPECIFIED: time

Explanation: An invalid time was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid time, in the range from 00:00 to 23:59, using the hh:mm format.

CTMR2FE INVALID DATE SPECIFIED: date

Explanation: An invalid date was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid date, using the yyyy/mm/dd format.

CTMR2GE INVALID TIME RANGE SPECIFIED

Explanation: An invalid time range was specified in the CTMEVRT utility SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify a valid time range, ensuring that end of the range is after the beginning of the range.

CTMR2HE INVALID STATEMENT SPECIFIED IN DSNEVEXL: statement

Explanation: An invalid statement was specified in the CTMEVRT utility DSNEVEXL PARM member.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the invalid statement. Valid statements are: EXCLDSN= and EXCLJOB=. Specify a valid job name or data set name mask.

CTMR2IE TOO MANY STATEMENTS SPECIFIED IN DSNEVEXL: statement

Explanation: Too many statements were specified in the CTMEVRT utility DSNEVEXL PARM member.

The utility terminates with a return code of 8.

Corrective Action: Contact BMC technical support.

CTMR2JE ERROR LOADING THE SORT MODULE

Explanation: The SORT module cannot be loaded.

The utility terminates with a return code of 8.

Corrective Action: Check the job log for additional messages related to the problem. If you still cannot resolve the issue, contact BMC technical support.

CTMR2KE SORT INVOCATION ERROR, RC=rc

Explanation: The invocation of the SORT module ended with errors.

The utility terminates with a return code of 8.

Corrective Action: For more details, check the SYSOUT DD SORT error messages. If you still cannot resolve the issue, contact BMC technical support.

CTMR2LE NONE OF THE SMF RECORDS SATISFIED THE INCLTIME AND SYSID OR SYSTEM CRITERIA

Explanation: The CTMEVRT utility did not find any SMF records matching the time period and/or the system identification specified in the SYSIN.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement.

CTMR2ME THE REQUIRED SMF TYPES WERE NOT PROVIDED FOR THE INCLUDED PERIOD OF TIME

Explanation: The CTMEVRT utility did not find any of the mandatory SMF types in the SMF input. The mandatory SMF types are 14, 15, 17, 30, 61, 64, and 65.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement that contains the SMF record types.

CTMR2NW NO CMEM/CTO EVENTS WERE FOUND IN INPUT SMF - DSNEVENTS LIST NOT GENERATED

Explanation: The CTMEVRT utility did not find any DSNEVENTs in the SMF data that would have been caught by CMEM or Control-O during the time period specified.

The utility terminates with a return code of 4.

Corrective Action: No action is required.

CTMR2OE MANDATORY SMF TYPE SMF_type NOT FOUND IN INPUT

Explanation: The CTMEVRT utility did not find this mandatory SMF record type in the SMF input. The mandatory SMF types are 14, 15, 17, 30, 61, 64, and 65.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement.

CTMR2PE DSNEVENTS LIST MAY BE PARTIAL BECAUSE OF MISSING DISP INFORMATION IN THE SMF INPUT

Explanation: Data sets for which the CTMEVRT utility did not find any matching SMF records are excluded from the event list generated. See message CTMR2ZE for more details.

The event list is generated but the utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement that contains the SMF record types missing. If all SMF types were provided to the utility, provide the DASMF records to BMC Support.

CTMR2QW SMF TYPE 119-70 (FTP SERVER) NOT FOUND IN INPUT, INCOMING FTP DSNEVENTS COULD NOT BE GENERATED

Explanation: The CTMEVRT utility did not find any SMF record type 119, subtype 70, in the SMF input. As a result, the utility cannot find and list DSNEVENTs triggered by FTP transfers originating in remote systems.

The utility continues to execute.

Corrective Action: If SMF 119 is collected at the site, specify the correct SMF data set(s) in the DASMF DD JCL statement and re-run the utility.

CTMR2RE INTERNAL ERROR - error_description

Explanation: An internal error has occurred during the execution of the CTMEVRT utility.

The utility terminates with a return code of 8.

Corrective Action: Send all the output from the CTMEVRT job to BMC technical support.

CTMR2SW INVALID SMF RECORD(S) ENCOUNTERED - SEE SNAP

Explanation: During execution of the CTMEVRT utility, one or more invalid SMF records were encountered in the DASMF file.

The utility continues to execute.

Corrective Action: Send all the output from the CTMEVRT job to BMC technical support.

CTMR2TE CMEM/CTO EVENTS COULD NOT BE FOUND DUE TO AN ERROR WHILE LOADING RULES

Explanation: The CTMEVRT utility was unable to read CMEM or Control-O rules from the DACTMLST DD. No rules defining DSNEVENTs were found.

The utility terminates with a return code of 8.

Corrective Action: Check DAREPORT for additional messages related to the problem.

CTMR2VW RULE cmem_rule TABLE table IS CHECKING ON THE UNSUPPORTED DISP NCT2

Explanation: The selection criteria in the CMEM rule specifies DSNEVENTs with a disposition of NOT CATLG 2 (NCT2). The CTMEVRT utility cannot detect such events, therefore this rule will not be found and listed by this utility. The rule/event cannot be recovered; the rule cannot be triggered and the DSNEVENT cannot be restored.

The utility continues to execute.

Corrective Action: No action is required.

CTMR2WE SMF RECORDS NOT FOUND IN THE INPUT DD "DASMF"

Explanation: The CTMEVRT utility did not find any SMF record in the DASMF input DD.

The utility terminates with a return code of 8.

Corrective Action: Specify the correct SMF data set(s) in the DASMF DD JCL statement.

CTMR2XI EVENTS WILL BE EXCLUDED FROM OUTPUT DUE TO DSNEVEXL SETTINGS:

Explanation: The CTM PARM member DSNEVEXL contains the listed exclude statement(s). The events triggered by these data sets and/or jobs will be excluded from the DAEVENTS list.

Corrective Action: No action is required.

CTMR2YE TOO MANY STATEMENTS SPECIFIED

Explanation: An input statement has been specified more than the allowed number of times.

The utility terminates with a return code of 8.

Corrective Action: Remove the redundant statement(s).

CTMR2ZE CANNOT DETERMINE DISP FOR FTP-ED DATA SET data-set-name

Explanation: The CTMEVRT utility did not find matching SMF types 14, 15, 17, 30, 61, 64, and 65 to the FTP records it read.

The event list is generated but the utility terminates with a return code of 8.

Corrective Action: Perform the following actions:

Specify the correct SMF data set(s) in the DASMF DD JCL statement that contains the SMF record types missing.
If all SMF types were provided to the utility, adjust the _BPX_JOB parameter, as necessary.
If the issue is not yet resolved, provide the DASMF records to BMC Support.

CTMR31E UNABLE TO OPEN THE "DACTMLST" DD

Explanation: The CTMEVRT utility was unable to open the CMEM rule order list DD DACTMLST.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMR32E DACTMLST IS EMPTY

Explanation: The CTMEVRT utility found no rule tables defined in the CMEM rule order list DD DACTMLST.

The utility terminates with a return code of 8.

Corrective Action: Check and correct DACTMLST.

CTMR33E GETMAIN FAILED FOR DACTMLST ENTRIES

Explanation: There is not enough memory to load the CMEM rule order list. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR34E GETMAIN OF 1M FOR RULES FAILED

Explanation: There is not enough memory to load the CMEM rule order list. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR35E GETMAIN FOR DIRECTORY AREA FAILED

Explanation: There is not enough memory to load the CMEM rule order list. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR36E IOAMEM DIRECTORY FAILED. RC=rc RS=rsn LIB=library

Explanation: The CTMEVRT utility was unable to read CMEM rules from the library library because IOAMEM failed to read its directory.

The utility terminates with a return code of 8.

rc is the return code and rsn is the reason code returned by IOAMEM with the DIRECTORY function call. For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If rc and rsn descriptions are not sufficient to solve the problem then prepare the full CTMEVRT output, and contact BMC Customer Support.

CTMR37W EMPTY LIBRARY=library

Explanation: The CTMEVRT utility was unable to find any members in the library library.

The utility continues to read DACTMLST entries.

Corrective Action: Check the library name and if it is correct but empty, remove its entry from the DACTMLST rule list.

CTMR38W IOAMEM DIRECTORY FAILED. RC=rc RS=rsn MEM=member LIB=library

Explanation: The CTMEVRT utility was unable to read CMEM rules from the library library because IOAMEM failed to read the member member. The return code=rc and reason code=rsn were issued.

The utility continues to read DACTMLST entries.

For more information on these codes, see the description of IOAMEM in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If rc and rsn descriptions are not sufficient to solve the problem then prepare the full CTMEVRT output, and contact BMC Customer Support.

CTMR39E GETMAIN FOR DIRECTORY AREA FAILED

Explanation: There is not enough memory to load the CMEM rules member member from the library library because a GETMAIN of size size for it failed. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR3AE NO ELIGIBLE RULES FOUND IN DACTMLST

Explanation: The CTMEVRT utility was unable to find any eligible CMEM rules among the DACTMLST entries. Eligible rules are DSNEVENT CMEM rules performing either DO FORCEJOB, DO COND, or both.

The utility terminates with RC=08.

Corrective Action: Ensure there are eligible rules in the DACTMLST rule list.

CTMR3BW NO RECORDS IN MEM=member LIB=library

Explanation: The CTMEVRT utility was unable to find any CMEM rule records in the member member in the library library.

The utility continues to read DACTMLST entries.

Corrective Action: If rules in the library member can be skipped, remove its entry from the DACTMLST rule list.

CTMR3CW INVALID FIRST RECORD IN RULE. MEM=member LIB=library

Explanation: The first record that the CTMEVRT utility encountered in the member CMEM rules member in the library library is invalid.

The utility continues to read DACTMLST entries.

Corrective Action: Check the validity of the rule by viewing it in the IOA screen C and possibly by ordering it, then correct it or remove it from DACTMLST.

CTMR3DI DACTMLST entry sequence number: dactmlst_entry

Explanation: The CTMEVRT utility prints the DACTMLST entry dactmlst_entry, which is being handled, and its assigned sequence number.

Corrective Action: No action is required.

CTMR3EW MASK=mask DOES NOT MATCH ANY MEMBER IN LIB=library

Explanation: The CTMEVRT utility was unable to find any member in the library library matching the mask member mask specified in the current DACTMLST entry.

The utility continues to read DACTMLST entries.

Corrective Action: If rules in the library member can be skipped, remove its entry from the DACTMLST rule list.

CTMR3FE GETMAIN OF 4K FAILED

Explanation: There is not enough memory to convert the CMEM rules order list to an internal representation. The region might be too small.

The utility terminates with a return code of 8.

Corrective Action: Increase the size of the region and restart CTMEVRT. If there still is not enough memory, contact your local systems analyst.

CTMR3GW TRUNCATED RULE=rule MEM=member LIB=library

Explanation: The CTMEVRT utility encountered an invalid truncated CMEM rule rule in the member member in the library library.

The utility continues to read the next rule in the member.

rule is the name of the rule as it appears in the IOA screen C.

Corrective Action: Check the validity of the rule by viewing it in the IOA screen C and possibly by ordering it, then correct it or remove it from the rules table.

CTMR3HW INVALID RECORD IN RULE=rule MEM=member LIB=library

Explanation: The CTMEVRT utility encountered an invalid record CMEM rule rule in the member member in the library library.

The utility continues to read the next rule in the member.

rule is the name of the rule as it appears in the IOA screen C.

This message is followed by message CTMR3II.

Corrective Action: Check the validity of the rule by viewing it in the IOA screen C and possibly by ordering it, then correct it or remove it from the rules table.

CTMR3II INVALID RECORD=record

Explanation: This message displays the invalid record referred to in the previous message CTMR3HW.

Corrective Action: See the CTMR3HW message.

CTMR3JW MEM=member NOT FOUND IN LIB=library

Explanation: The CTMEVRT utility did not find the member member in the library CMEM rules library.

The utility continues to read DACTMLST entries.

Corrective Action: Correct the member name or add it to the CMEM rules library or remove its entry from the DACTMLST rule list.

CTMR3SE UNABLE TO READ DD "DAEVENTS". RC=rc

Explanation: The CTMEVRT utility failed to read the DAEVENTS DD using the REXX EXECIO command.

The utility terminates with a return code of 8.

Corrective Action: Check the job sysout for related messages. Also check the JCL to ensure that the DAEVENTS DD statement exists and is pointing to a valid DAEVENTS file.

CTMR3TE ERROR WHILE READING IOAPARM. RC=rc

Explanation: The CTMEVRT utility failed to read the IOAPARM and CTMPARM members using the REXX EXECIO command.

The utility terminates with a return code of 8.

Corrective Action: Check the job sysout for related messages. Also check the JCL to ensure that the DAPARM DD statement exists and is pointing to a valid IOA parameter library.

CTMR3UE ALLOCATION OF DD "ddname" FAILED. RC=rc

Explanation: The CTMEVRT utility failed to dynamically allocate DD ddname.

The utility terminates with a return code of 8.

Corrective Action: Check the DAPRINT DD for additional messages related to the problem. If you still cannot resolve the issue, contact BMC technical support.

CTMR3VI CTMPARM DAYTIMEM (time) AND NOT CTOPARM DAYTIMEO (time) IS USED TO DETERMINE ODAT

Explanation: During the startup of the CTMEVEX, the value of the DAYTIMEO Control-O parameter was not identical with the value of the DAYTIMEM Control-M parameter.

The DAYTIMEO Control-O parameter sets the start of the work day for Control-O. The DAYTIMEM Control-M parameter sets the start of the work day for Control-M. Any discrepancy between these two parameters might result in the same time being interpreted differently by Control-O and Control-M.

CTMEVEX uses DAYTIMEM to set the work day (ODATE) for a DSNEVENT action.

Corrective Action: Contact your INCONTROL administrator.

CTMR3WE INVALID RECORD FOUND IN "DAEVENTS" DD:record

Explanation: The CTMEVEX utility found a record in an unexpected format in the DAEVENTS DD. The only supported format for DAEVENTS is as it is written by the CTMEVRT utility. If the record was added as a comment, prefix it with an asterisk (*).

The utility terminates with a return code of 8.

Corrective Action: Check the JCL to ensure that the DAEVENTS DD statement is pointing to the DAEVENTS output dataset created by the CTMEVRT utility. If events were added to DAEVENTS, make sure that they are in the same format as the CTMEVRT-written events, or comments.

CTMR3XE MEMBER member NOT FOUND IN DAPARM LIBRARY=library

Explanation: The CTMEVRT utility could not find the IOAPARM or CTMPARM member in the library allocated as DAPARM.

The utility terminates with a return code of 8.

Corrective Action: Check the JCL to ensure that the DAPARM DD statement exists and is pointing to the IOA parameter library.

CTMR3YE UNABLE TO OPEN THE "ddname" DD

Explanation: The CTMEVRT utility was unable to open the required output DD.

The utility terminates with a return code of 8.

Corrective Action: Check and correct the JCL statement.

CTMRS0E SECURITY, FAILED TO UPDATE RESOURCE FILE

Explanation: An unauthorized attempt to update the resource file failed.

Corrective Action: Ensure that the user has sufficient authorization.

CTMRS1E SECURITY, FAIL TO action resourceType RESOURCE resourceName

Explanation: An unauthorized attempt to add/delete/update a resource.

Corrective Action: Ensure that the user has sufficient authorization.

CTMRS3E INTERNAL ERROR, RESOURCE FILE NOT FREE

Explanation: Failed to use the resource file because the file is being used.

Corrective Action: Wait to the file to be released. Retry the process.

CTMRS4E INTERNAL ERROR, INVALID resourceType RESOURCE RECORDS IN FILE HEADER

Explanation: The resource file header contains an invalid number of resource type slots.

Corrective Action: This is an internal error. Retry the process and if the problem reoccurs, call BMC Customer Support.

CTMRS5E ERROR, QUANTITY SLOTS NUMBER GREATER THAN FILE

Explanation: The actual number of quantity base slots is greater than the counter in the resource file header.

Corrective Action: This is an internal error. Retry the process and if the problem reoccurs, call BMC Customer Support.

CTMRS7E FAIL TO ADD QUANTITY BASE RESOURCE resourceName, reason

Explanation: Failed while adding the base resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRS8E FAIL TO DELETE QUANTITY BASE RESOURCE resourceName, reason

Explanation: Failed while deleting the base resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRS9E FAIL TO UPDATE QUANTITY BASE RESOURCE resourceName, reason

Explanation: Failed while updating the base resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRSBE FAIL TO OBTAIN resourceType RESOURCE resourceName, reason

Explanation: Failed while trying to obtain the resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRSCE FAIL TO RELEASE resourceType RESOURCE resourceName, reason

Explanation: Failed while trying to release the resource as explained by the reason.

Corrective Action: Fix the issue and retry the process.

CTMRSDE FAIL TO OBTAIN resourceType RESOURCE, ALL SLOTS IN USE

Explanation: Failed while trying to obtain the resource because all slots for this resource type are being used.

Corrective Action: Increase the file size and retry the process.

Parent Topic

CTM messages