CTV–CVI

This group includes messages for the Control-D, Control-M for z/OS and Control-V products.

CTV messages

This group includes messages for the Control-D includes: Control-D/Image Control-D/Page on Demand product.

Messages CTV500 through CTV5xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CTV5F0E INVALID MEDIA = `mediaName` WAS SPECIFIED FOR FILE `fileName`

Explanation: The media name specified for the specified file to be deleted is invalid. The CTVCLMIG utility calls the CTVDEL program to delete specified files and the media on which they reside. Some of the input for CTVDEL was invalid.

The system skips the problematic file, and continues processing.

Corrective Action: Check the media name in IOASPRM, correct the problem, and try again.

CTV5F1E `media` DEVICE `device` SM-CMD-INTF FAILED. COMMAND `cmd`

Explanation: The SM-CMD-INTF command, which is used to delete FileTek files, failed for the specified media and device.

In this message, cmd is the command that caused the error.

The system skips the problematic file, and continues processing.

Corrective Action: Use FileTek interfaces to determine the cause of the failure, and the status of the file to be deleted. Fix the problem and try again.

CTV5F2E DELETE FAILED. `fileName` RC : `rc`

Explanation: The FileTek delete command failed for the specified file.

The system skips the problematic file, and continues processing.

Corrective Action: Check FileTek messages to determine the significance of the reason code. Then, use FileTek interfaces to determine the cause of the failure, and the status of the file to be deleted. Fix the problem and try again.

CTV5F3I DELETED `fileName`

Explanation: This information message indicates that the specified FileTek file was successfully deleted.

Corrective Action: No action is required.

CTV5F4E COLLECTION `collect-name` NOT DELETED FROM DB2 RC = `rc`

Explanation: The attempt to delete collection collect-name from a DB2 database failed.

Corrective Action: No action is required.

Messages CTV700 through CTV7xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CTV700E "INDEX" MUST BE FILLED IN

Explanation: The index name was not specified in a decollating mission DO INDEX statement. Each index must be identified by a unique name which may later be used to access part of a report according to a specific index. A DO INDEX statement without a name is invalid.

Corrective Action: Specify an index name or mask.

CTV702E ONLY 3 INDEX LINES CAN BE SET TO R=Y

Explanation: An attempt was made to designate more than three indexes as disk-resident. A maximum of three indexes can be defined as disk-resident.

The index is not designated disk-resident. It will be deleted from DASD when the corresponding report is deleted, and will only be available on migrated media, if report is migrated.

Corrective Action: Redefine the Report Decollation Mission so that no more than three indexes are specified disk-resident.

CTV703E FROM/UNTIL COL ARE OBLIGATORY

Explanation: The FROM COL parameter or the UNTIL COL parameter (or both) of the index value or the value mask was not specified in the Decollation Mission DO INDEX statement.

Corrective Action: Specify FROM COL and UNTIL COL parameters to locate the index value. Either omit the value mask or specify FROM COL and UNTIL COL parameters to locate the mask.

CTV704E FIELD SHOULD BE BLANK WHEN " `fieldname`" IS BLANK

Explanation: Either

The report line and column location of an index mask were specified without specifying the mask itself.
The TYPE or STORED parameters of an index print mission were specified without specifying the print mission itself.

Corrective Action: Depending on the problem, either

Specify an index mask, or do not specify the mask location, for the index.
Specify an index print mission, or do not specify the TYPE and STORED subparameters.

CTV705E "MIGRATE" MUST BE FILLED IN

Explanation: The Migration Mission name was not specified in a DO MIGRATE statement.

Corrective Action: Specify a Migration Mission name or omit the DO MIGRATE statement.

CTV706E SUBINDEX LEVEL MUST BE IN THE RANGE OF 02-10

Explanation: There was an attempt to specify a subindex level below 02 or above 10. The LVL parameter indicates the hierarchical index level of the subindex. The default value is one level below the previously specified (sub)index. The specified value must be between 02 and 10.

The invalid value is not accepted and the cursor remains in the LVL field.

Corrective Action: Set a valid value for the LVL parameter, or blank out the Level field to activate the default value.

CTV707E NEXT SUBINDEX LEVEL MUST BE AT ANY EXISTING LEVEL OR THE NEXT ADJACENT LEVEL

Explanation: The value specified for the LVL parameter is not at the level of any existing subindex, and is more than one level of the previously specified index or subindex.

The LVL parameter indicates the hierarchical index level of the subindex. The default value is one below the previously specified level. The level of the subindex currently being specified must be either:

one below the previously specified index level
the same as a previously specified subindex level

The invalid value is not accepted and the cursor remains in the LVL field.

Corrective Action: Specify a subindex level that is one below the previously specified index level, or the same level as a previously specified subindex.

CTV708E FIELD SHOULD BE BLANK WHEN "SUBINDEX" IS BLANK

Explanation: A LINE, COL range or MASK was specified for a subindex whose name was not specified. The LINE, COL range and MASK parameters cannot be specified for a subindex unless the subindex name has been specified.

The specified value is not accepted and the cursor remains in the LINE, CO or MASK field.

Corrective Action: Specify the name of the subindex name before specifying its LINE, CO range or MASK values, or blank out all fields for the subindex whose name is not specified.

CTV709E ONLY 9 SUBINDEXES ARE ALLOWED

Explanation: There was an attempt to define more than 9 subindexes for one main index. Each main index can have up to 9 subindexes.

Corrective Action: Blank out the extra subindex fields.

CTV70AE INVALID SUBINDEX DEFINITION IN THE BRANCH OF MULTI-VALUE INDEX

Explanation: A subindex that is defined in additional value branch of a multi-value index is absent in the base branch at the same level.

Corrective Action: Define a subindex according to the base branch of a multi-value index structure.

CTV70BE INVALID OPTION. TRY "M", "A", "T" OR BLANK

Explanation: An invalid option was specified in the M parameter of a DO INDEX statement.

Valid values are:

M - creates a multi-value index from one range, according to a mask
A - defines a multi-value index from additional ranges
T - defines a multi-value index with separate subindex values
Blank - defines a regular index

Corrective Action: Specify M, A, T, or blank.

CTV70CE INVALID OPTION. TRY "M", "A" OR BLANK

Explanation: An invalid option was specified in the M parameter of an AND statement.

Valid values are:

M - creates a multi-value index from one range, according to a mask
A - defines a multi-value index from additional ranges
Blank - defines a regular index

Corrective Action: Specify M, A, or blank.

CTV70DE VALID OPTIONS IS "T" ONLY

Explanation: An invalid option was specified in the M parameter of an INDEX for an additional value branch of a multi-value index.

T is the only valid option.

Corrective Action: No action is required.

CTV70EE MASK SHOULD BE IN ASTERISKS.

Explanation: The MASK parameter is not enclosed in asterisks. MASK should be enclosed in asterisks if M=M is specified in the INDEX statement.

Corrective Action: Enclose the MASK parameter in asterisks.

CTV70FE INDEX COL MUST BE RELATIVE (+/-)

Explanation: The INDEX COL is not relative. INDEX COL must be relative if M=M is specified in the INDEX statement.

Corrective Action: Define the relative INDEX COL parameter.

CTV70GE ONLY ONE "DO APPROV" STATEMENT PER "WHEN" STATEMENT MAY BE SPECIFIED

Explanation: An attempt was made to open a DO APPROV statement in a WHEN criteria statement that already contains a DO APPROV statement.

Corrective Action: Delete the second DO APPROV statement by clearing the DO field.

Messages CTVG00 through CTVGxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CTVG31E THIS OPTION IS INVALID WHEN THE INDEX NAME IS BLANK

Explanation: A line command (option) was entered in an Index Window on a line that does not contain an index name. The Index Window displays a list of indexes whose values can be used to retrieve a report or section of a report. Options S (Select) and Q (Quick Index) can only be used to select an existing index.

Corrective Action: Use the S or Q line command to select a filled-in index name, or exit the Index Window using the PF04 or PF16 key.

CTVG32E NO INDEX EXISTS FOR THIS REPORT

Explanation: Option X to list a report indexes in the Index Window was specified in the Active Report List screen but the selected report has no index.

Corrective Action: Define one or more indexes with DO INDEX statements in the Report Decollation Mission if this report should be indexed.

CTVG33I ONLY NINE INDEXES MAY BE DISPLAYED

Explanation: This information message indicates that an attempt was made to display more than nine indexes. The screen on which indexes are displayed has room for nine indexes.

Only the first nine indexes are displayed.

Corrective Action: Redefine the Report Decollation Mission to specify no more than nine indexes for this report.

CTVG34E ONLY "S", "Q" OR " " ARE ALLOWED IN THIS FIELD

Explanation: A character other than S, Q or blank was entered in an Index Window Option field. S selects an index and displays its Values of Index Panel. Q displays the Quick Access Panel for the specified index.

The specified character is ignored. The system waits for a valid option or command.

Corrective Action: Specify option S or Q, or press PF03 or PF04 to redisplay the Active User Report List.

CTVG36E NO VALUES IN INDEX

Explanation: The specified index has no values in the specified user report. An error probably occurred in:

Specifying or dynamically retrieving a user name.
Specifying an index.

Corrective Action: Check the Decollation Mission Definition for this report. Be sure the user-recipient and index are properly specified.

CTVG39E IF A VALUE STARTS WITH A QUOTE, IT MUST END WITH THE SAME TYPE OF QUOTE

Explanation: The VALUE field in the User Reports Entry Panel began with a single (’) or double (") quote but did not end with the same type of quote.

The specified value is ignored.

Corrective Action: Specify a valid index value in the VALUE field or leave the field empty.

CTVG3AE DYNAMIC ALLOCATION OF INDEX FILE FAILED, REASON CODE=`rsn`

Explanation: Control-D or V failed to dynamically allocate an index file.

The index file is not allocated.

Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the reason code received. If you cannot resolve the problem, record the rsn and contact BMC Customer Support.

CTVG3BE OPTION MUST BE BLANK OR ONE OF 1, 2 OR 3

Explanation: An invalid option was specified in the OPTION field of the User Reports Entry Panel.

The only valid options are:

1 - Display a Permanent Report List
blank or 2 - Display an Active Report List
3 - Display a History Report List

Corrective Action: Specify a valid option.

CTVG3CE ONLY "Y", "N" OR "O" ARE ALLOWED IN THIS FIELD

Explanation: An invalid option was specified in the SHOW MIGRATED field of the User Reports Entry Panel.

The only valid options are:

Y - Display both active and migrated reports.
N - Display active reports only.
O - Display migrated reports only.

Corrective Action: Specify a valid option. Blank is not valid.

CTVG3DE OPEN OF INDEX FILE FAILED

Explanation: An index file could not be opened. It was probably deleted or uncataloged.

Corrective Action: Check the IOA Log file for a message indicating the report name and the name of the index file that could not be opened. Recreate the index which could not be opened by decollating the report again.

CTVG3EI INDEX/VALUE NON-UNIQUE. VIEW FULL REPORT

Explanation: This information message indicates that more than one index satisfies the specified index mask or more than one value satisfies the specified value prefix.

The entire report will be viewed or printed unless the User Action described below is taken.

Corrective Action: Use the Index Window to specify a unique index or use the Values of Index Panel to specify a unique value before viewing or printing the report.

CTVG3FI INDEX VALUE NOT FOUND. VIEW FULL REPORT

Explanation: This information message indicates that the specified value does not exist in the specified index.

The entire report is viewed or printed unless a unique existing value is specified before viewing or printing.

Corrective Action: Specify the desired index and value in the User Reports Entry Panel. Use the Index Window to determine if the desired index exists. Use the Values of Index Panel to determine if the desired value exists.

CTVG40S "E" IS NOT SUPPORTED FOR MIGRATED REPORTS. USE VIEW AND PF4 TO EDIT RULER

Explanation: Option E is not supported for migrated reports.

Corrective Action: Use option V to view the migrated report and PF04 to edit its ruler.

CTVG41E THE DISPLAY TYPE CANNOT BE CHANGED WHEN BYPASS PANEL=Q

Explanation: There was an attempt to change the Display Type by means of the DISPLAY command. However, while the BYPASS PANEL parameter is set to Q, only Display Type Q (Quick Access) is valid and no other Display Type is available.

Setting the BYPASS PANEL parameter in the User Reports Entry Panel to Q enables users to work directly with the Quick Access Panel. If more than one report matches selection criteria while the BYPASS PANEL parameter is set to Q, the matching reports are listed so users can specify which report to display in the Quick Access Panels. While this list is displayed, only Display Type Q and option Q are valid.

Corrective Action: To change the Display Type, use the RETURN command to access the User Reports Entry Panel. Change the value of the BYPASS PANEL parameter to Y or N. Specify the desired Display Type in the DISPLAY TYPE parameter in the User Reports Entry Panel or, after pressing Enter to display the User Reports List, use the DISPLAY command.

CTVG42E FROM DATE="LAST" TO DATE MUST BE BLANK

Explanation: An invalid date parameter was specified in the User Report List Entry Panel. The TO DATE field must be blank when specifying FROM DATE=LAST.

Corrective Action: Correct the date parameter.

CTVG43E DATE="LAST". USER MUST BE SPECIFIED

Explanation: An invalid combination of values was specified in the User Report List Entry Panel. The USER field must not be blank when specifying FROM DATE=LAST.

Corrective Action: Specify a valid user name in the USER field or do not specify LAST in the FROM DATE field.

CTVG44E THERE IS NO PREVIOUS INDEX

Explanation: The PREV command was entered, or the PF10 or PF22 key was pressed in the Quick Access Panel to display a previous index for a report, but no previous index exists.

The current index-report combination remains displayed in the Quick Access Panel.

Corrective Action: Use the NEXT command or PF11 or PF23 key to display the next index, if any exists, for the report.

CTVG45E THERE IS NO NEXT INDEX

Explanation: The NEXT command was entered, or the PF11 or PF23 key was pressed in the Quick Access Panel to display the next index for a report, but no next index exists.

The current index-report combination remains displayed in the Quick Access Panel.

Corrective Action: Use the PREV command, or press the PF10 or PF22 key to display the previous index, if any exists, for the report.

CTVG46E NO INDEX FOUND FOR THIS REPORT

Explanation: Display of Quick Access Panels was requested for a report that has no indexes. Quick Access Panels cannot be displayed for a report that has no indexes.

Quick Access Panels are not displayed.

Corrective Action: Determine why the report has no index. If necessary, modify and rerun the Decollation Mission to create one or more indexes for the report.

CTVG47E REQUIRED VALUE DOES NOT EXIST IN THIS INDEX

Explanation: The index value entered in the Quick Access Panel does not exist in the current index. The user attempted to print a report, or section of a report, based on an index value specified in the Quick Access Panel. The specified value does not exist in the current index for the report.

The report is not printed.

Corrective Action: Display the Values of Index Panel for the specified report and index to list existing index values.

CTVG48E DISPLAY TYPE Q IS VALID ONLY WHEN BYPASS PANEL=Q

Explanation: DISPLAY Q was entered on the command line of an Active User Reports List. Display Type Q facilitates the display of data about a report in the Quick Access Panels. Display Type Q is only available when the BYPASS PANEL parameter in the User Reports Entry Panel is set to Q. Display Type Q cannot be implemented by means of the DISPLAY command.

Corrective Action: Use option Q in any display type of the Active User Reports List to access the Quick Access Facility. The display type does not need to be changed to Q in order to use option Q.

CTVG49E ERROR IN `routineName` CACHE ROUTINE - RC= `rc`

Explanation: Due to an internal error in routine routineName, a cache request could not be satisfied. The return code from routine routineName was rc. The View option (V) was specified. Routine routine was called by the View function.

Possible causes and return codes by routine name:

IOASCRQ - Possible return codes:
4 - OSE (open session entry) was not active.
8 - Another request was issued with this OSE.
24 - PC-call (cross memory addressing) error.
IOASAOS - Possible return codes:
4 - ENQ query for user existence failed.
16 - There is no free OSE (open session entry).
IOAXCP5 - Return code is 8, REQ (request queue element) error.
IOAXPC7 - Return 8, requested media not defined in the IOASPRM member.
IOASCAW - Return code 4, cannot copy the OSE (open session entry).

The report is not displayed or only partially displayed.

Corrective Action: Use the information above to determine what is wrong with the cache request mechanism. If the error cannot be resolved, record the error message and contact BMC Customer Support.

CTVG4AE IOASMON ARCHIVE SERVER NOT ACTIVE - RC= `rc`

Explanation: The IOA Archive Server was either terminated or not started.

The cache request is not performed.

Corrective Action: Ask the operator to start the IOA Archive Server.

CTVG4BE REQUESTED MEDIA NOT ACTIVE

Explanation: The media to which the requested report migrated is not active in the IOA Archive Server. The required media was terminated or not started.

The cache request is not performed.

Corrective Action: Ask the operator to activate the required media in the IOA Archive Server.

CTVG4CE ERROR LOCATING MIGRATED REPORT

Explanation: The requested report was not found in the catalog. The IOA Archive Server searched the catalog for the requested migrated report but did not find it.

The cache request is not performed.

Corrective Action: Contact your INCONTROL administrator to find out what happened to the required data set.

CTVG4DE REQUESTED VOLUME NOT FOUND IN OSS DATABASE

Explanation: The requested report migrated to a volume that has been manually deleted from the OSS database.

The cache request is not performed.

Corrective Action: Contact your OSS operator to find out what happened to the required volume.

CTVG4EE REQUESTED PLATTER NOT FOUND IN OSS DATABASE

Explanation: The requested report migrated to a volume that resides on a platter that has been exported or manually deleted from the OSS database.

The cache request is not performed.

Corrective Action: Contact your OSS operator to find out what happened to the required platter.

CTVG4FE NO DEVICES ARE ACTIVE FOR THIS MEDIA

Explanation: The media to which the requested report migrated has no currently active device in the IOA Archive Server. The devices of the required media were terminated or not started.

The cache request is not performed.

Corrective Action: Ask the operator to activate at least one device of the required media in the IOA Archive Server.

CTVG4GE CTVX001 COULD NOT ACCESS INDEXES

Explanation: The CTVX001 exit, could not retrieve an index value from a non-Control-V index file.

The system stops.

Corrective Action: Contact BMC Customer Support.

CTVG4HS `x` IS NOT SUPPORTED FOR ACTIVE REPORTS

Explanation: Options R and C are not supported for migrated reports.

Corrective Action: Specify a valid option.

CTVGB0E ERROR ALLOCATING DEVICE

Explanation: The IOA Archive Server could not allocate a device to retrieve a migrated report. See messages DVT191E or IOA191E and DVT192E or IOA192E in the IOA Log file for the error code and information about the failed allocation.

The cache request is not performed.

Corrective Action: Correct the problem that caused the allocation to fail, and retry.

CTVGB1E OPERATOR COULD NOT MOUNT REQUESTED TAPE

Explanation: The operator did not mount a volume requested by the IOA Archive Server. The requested volume could not be found or the operator did not mount the volume for some other reason.

The cache request is not performed.

Corrective Action: Contact the operator to determine why the requested volume was not mounted.

CTVGB2E CACHE REQUEST FAILED - SERVER CODE = `rc`

Explanation: Due to an internal error in the cache mechanism, a cache request was not performed. Return code rc was produced as a result, as shown below.

rc	Explanation
20	Media error in adding request to chain.
24	Media error in GETMAIN for TVL.
28	Media error handling multivolume file.
36	Media error: File resides on more than five volumes.
60	Media error: An RQC was queued without RBAs.
64	OASDVT error: An RQC was queued with a zeroed RBA.
68	Media error during deallocation. See messages DVT191E or IOA191E and DVT192E or IOA192E in the IOA Log file for the error code and more information.
76	Media error: Open failed.
80	Media error: Task abended during open. See message DVT194E or IOA194E in the IOA Log file for the abend code.
84	Media error: I/O error on device. See message DVT193E or IOA193E in the IOA Log file for the input or output error description.
92	IOASDVT error while reading the descriptor block of a migrated CDAM file.
96	IOASDVT error while acquiring storage for a migrated CDAM descriptor block. See message DVT180S in the IOA Log file for more information.
100	IOASDVT error while reading the first block from a migrated CDAM file.
104	IOASDVT error while acquiring storage for the first block of a migrated CDAM file. See message DVT180S in the IOA Log file for more information.
108	IOASDVT error while acquiring storage for cache. See message DVT180S in the IOA Log file for more information.
112	IOASDVT error: Extent number in RBA is out of range.
116	Error while translating RBA to BBB.
120	IOASDVT error: block number is out-of-range.
124	Error while translating BBB to RBA.
128	IOASDVT error while issuing ENQ to test user existence. See message DVT181E or IOA181E in the IOA Log file for more information.
132	IOASDVT error: Task abended during cache request processing.
140	Media error: Assigned device could not be allocated because it is unavailable. See messages DVT191E or IOA191E and DVT192E or IOA192E in the IOA Log file for the error code and more information.

The cache request is not performed.

Corrective Action: See the IOA Log file for messages regarding the event. Use the return code to determine what caused the IOA Archive server cache mechanism to fail. If the error cannot be resolved, contact BMC Customer Support.

CTVGB3E INDEX/VALUE NON-UNIQUE. PRINT REQUEST DENIED

Explanation: This message indicates that more than one index satisfies the specified index mask, or more than one value satisfies the specified prefix value.

The report is not printed.

Corrective Action: To print a specific portion of the report use the Index window to specify a unique index, or use the Values of Index panel to specify a unique value.

CTVGB4E INDEX VALUE NOT FOUND - PRINT REQUEST DENIED

Explanation: This message indicates that the specified value does not exist in the specified index.

The report is not printed.

Corrective Action: Use the Index window to determine whether or not the required index exists. Use the Values of Index panel to determine whether or not the required value exists. Specify the required index and value for the print request.

CTVGB5I NO MORE SUBINDEXES FOR THIS BRANCH

Explanation: This information message indicates that there are no lower level indexes for this index.

Corrective Action: No action is required.

CTVGB6I NO VALUES EXIST FOR THIS INDEX

Explanation: This information message indicates that no values of the specified index appear in the user’s report.

Corrective Action: No action is required.

CTVGB7E INVALID MEDIA SPECIFIED FOR REPORT

Explanation: A migrated report could not be accessed because the media to which it was migrated was not found. The $SYSDATA entry that corresponds to this migrated report specifies a migrated media which does not appear in IOASPRM.

The migrated report is not accessed.

Corrective Action: Have your INCONTROL administrator correct IOASPRM to reference the migrated media that appears in the $SYSDATA entry.

CTVGC5S INTERNAL ERROR - FREEMAIN ERROR. RC = `rc`

Explanation: An internal error occurred during the execution of a FREEMAIN macro. This error occurred during the execution of the database conversion utility. See CVIGC5S.

The database conversion utility terminates with an error. The conversion of the VSAM file to an IOA Access Method file is not completed.

Corrective Action: Contact BMC Customer Support.

Messages CTVP00 through CTVPxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CTVP40E UNABLE TO ACCESS INDEXES - RC = `rc`

Explanation: An internal error occurred when accessing the Index facility of Control-D/WebAccess Server Page On Demand or Control-D PRINT monitor.

The requested action is not performed.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTVP41E NOT ENOUGH SPACE FOR INDEXES - SOME INDEXES ARE MISSING

Explanation: There are too many index paths for this report. Some index paths cannot be accessed using Page On Demand.

Only the displayed index paths are accessible using Page On Demand.

Corrective Action: You can access the rest of the index paths by means of the Control-D Index facility.

CTVP42E INTERNAL ERROR - INVALID REQUEST SUB-TYPE - MUST BE BETWEEN 1 AND `n`

Explanation: An internal error occurred when the user attempted to access an Index facility of Control-D/WebAccess Server Page On Demand.

The function is not performed.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTVP43E INTERNAL ERROR FREEING STORAGE - RC = `rc`

Explanation: An internal error occurred when the user attempted to exit from the Index facility of Control-D/WebAccess Server Page On Demand.

The server on the host cannot close the index used. Other problems may occur because of this error.

Corrective Action: Check the IOA Log and the system log for additional error messages. Report the problem and any additional error messages to BMC Customer Support.

CTVP44S INSUFFICIENT STORAGE - INCREASE REGION SIZE

Explanation: Insufficient memory in the host server to perform the index request.

The indexes cannot be accessed.

Corrective Action: Increase the REGION size of the server task on the host, and restart the server.

CTVP45E REPORT ENTRY DELETED - CANNOT ACCESS INDEXES

Explanation: The report entry corresponding to the index being processed does not exist. The report entry was probably deleted by another user or by CTDDELRP utility.

The report is not displayed.

Corrective Action: Refresh the User Report list to get a current list of existing report entries.

CTVP46S ERROR IN INPUT MESSAGE LENGTH - MESSAGE IS TOO SHORT

Explanation: An internal communication error occurred between Control-D/WebAccess Server and the Control-D Application Server.

The requested action is not performed.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTVP47S EOR IN INPUT MESSAGE - INDEX PATH IS INCORRECT

Explanation: Internal error in communication between Control-D/WebAccess Server and the Control-D Application Server.

The report section is not retrieved.

Corrective Action: Report this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTVP48S INTERNAL ERROR - LOAD OF MODULE `modName` FAILED

Explanation: The Control-D Application Server failed to load a load module.

The requested function is not performed. Other problems may follow.

Corrective Action: Consult your INCONTROL administrator. If necessary, report this problem to BMC Customer Support.

CTVP49S INTERNAL ERROR - MISMATCH BETWEEN INDEX RECORD AND USER RECORD

Explanation: Internal error in the Control-D Application Server or Control-D PRINT monitor.

The requested action is not performed.

Corrective Action: Report this problem, the report entry for which it occurred, and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTVP4AS INTERNAL ERROR IN INPUT PARAMETERS

Explanation: An internal error occurred when accessing the Index facility of Control-D/WebAccess Server Page On Demand.

The requested action is not performed.

Corrective Action: Record this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTVP4BS INTERNAL ERROR - CANNOT LOCATE THE PREVIOUS VALUE FROM WHICH TO START

Explanation: An internal error occurred when accessing the Index facility of Control-D/WebAccess Server Page On Demand.

The requested action is not performed.

Corrective Action: Record this problem and any relevant error messages from the IOA Log and the Control-D Application Server to BMC Customer Support.

CTVP4CE CANNOT VIEW REPORT SECTION - INDEX PATH VALUES ARE NOT UNIQUE

Explanation: The index values in the selected path are not unique. The report cannot be viewed.

The report section is not viewed.

Corrective Action: Choose index values from the List of Index Values, and then attempt to View the report.

CTW messages

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.

Messages CTW0 through CTW0xx

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.

CTW001W `taskName` : COMMUNICATION IS NOT ACTIVE

Explanation: Communication with the Enterprise Manager gateway was disconnected. IOAGATE reported the disconnection to the Application Server of Control-M. The task-name task of the Application Server issues this message.

The Application Server waits until communication is connected again.

Corrective Action: Check IOAGATE messages to identify and fix the communication problem.

CTW002W `taskName` : NO RESPONSE RECEIVED WITHIN EXPECTED TIME INTERVAL

Explanation: The Enterprise Manager gateway did not respond to an IOAGATE transmission within the time allowed.

The Control-M Application Server waits for a message from the Enterprise Manager gateway.

Corrective Action: Check the Enterprise Manager gateway to find out why it is not responding.

CTW003W `taskName` : COMMUNICATION SLOWDOWN

Explanation: IOAGATE buffers are full. IOAGATE can not accept any new messages from the Control-M Application Server. IOAGATE informs the Application Server. The taskName task of the Application Server tries to transmit again several times and, if it does not succeed, issues this message.

The Control-M Application Server stops.

Corrective Action: Check IOAGATE messages to try to identify and fix the problem. If necessary, contact BMC Customer Support.

CTW004E `taskName` : MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: `funcName` RC= `rc`

Explanation: An internal error occurred in the MBX API.

The Control-M Application Server terminates.

Corrective Action: Contact BMC Customer Support.

CTW046S BLDL/LOAD FAILED FOR THE MODULE "`modName` "

Explanation: Loading of the modName module failed.

Possible causes are:

The IOA Load library is not in the load modules search list (STEPLIB + Linklist).
There is insufficient memory.
There is some other system-oriented reason, which may be found in the syslog.

Execution might stop.

Corrective Action: Prepare the Control-M monitor full output and contact BMC Customer Support.

Messages CTW100 through CTW1xx

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.

CTW125W FOLDER LIBRARY NOT FOUND

Explanation: The specified job scheduling library is not correct.

Corrective Action: Correctly specify the library.

Messages CTW300 through CTW3xx

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.

CTW392S OPEN OF DDNAME `ddName` FAILED

Explanation: The opening of the data set referenced by the ddName DD statement failed.

Possible causes are:

the DD statement referring to the data set referenced by the ddName DD statement is missing.
The data set referenced by the ddName DD statement does not exist.

System action depends on the calling program. Execution may continue, or it may stop.

Corrective Action: Correct the JCL and rerun.

Messages CTW500 through CTW5xx

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.

CTW567I COND `cond` ODATE `odate` {ADDED | DELETED | FOUND} BY USER `userId` / `jobName (jobId)`

Explanation: This information message indicates that the ADD, DELETE, or CHECK option completed successfully and the cond condition with the odate original scheduling date was added to or deleted from, or found in the IOA Conditions file.

In this message, odate is the date on which the message is issued. If the ADD, DELETE, or CHECK option is run by the IOACND utility in batch mode, the user ID (userId), job name (jobName), and job ID (jobId) of the batch file are also displayed.

Corrective Action: No action is required.

CTW581S OPEN OF IOA SYNCHRONIZATION FILE FAILED. DDNAME "DASINC"

Explanation: The opening of the IOA Conditions Synchronization file failed (DD statement DASINC).

Possible causes are:

The DD statement DASINC is missing.
The file allocated to the DD statement DASINC is not the IOA Synchronization file.
The file allocated to DD statement DASINC is the IOA Synchronization file, but it is of a different version or of a different Control-M monitor.

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

CTW586S OPEN OF IOA CONDITIONS FILE FAILED. DDNAME "DACNDSF"

Explanation: Open of IOA Conditions file failed (DD statement DACNDF).

Possible causes are:

The DD statement DACNDF is missing.
The file allocated to the DD statement DACNDF is not an IOA Conditions file.
The file allocated to the DD statement DACNDF is the IOA Conditions file, but it is of a different version or of a different IOA Installation.

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

Messages CTW900 through CTW9xx

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.

CTW912S ERROR IN CONTROL- `x` INSTALLATION PARAMETERS - INVALID DAYTIME

Explanation: Invalid format of Control- x Installation DAYTIME parameter. DAYTIME is the start time of the Control-M work day in your installation. Valid formats are +hhmm or -hhmm.

For more details see the section that describes installation parameters in the chapter for the appropriate products in the INCONTROL for z/OS Installation Guide.

The requested function terminates.

Corrective Action: Call your system programmer to correct the DAYTIME parameter in the CT xPARM member.

CTW913S OPEN OF DDNAME "SYSPRINT" FAILED

Explanation: The opening of a print file failed.

Possible causes are:

The DD statement SYSPRINT is missing.
The data set referenced by the DD statement SYSPRINT cannot be accessed for sequential write.

The program stops executing.

Corrective Action: Correct the JCL and submit again.

CTW914S ERROR IN IOA INSTALLATION PARAMETERS - INVALID DATETYP

Explanation:Highlighted, unrollable message.

The DATETYP IOA Installation Parameter is invalid. DATETYP is the type of date format used in the installation. Valid formats are:

A - mmddyy
W - ddmmyy
J - yymmdd

For more details refer to the section that describes how to set IOA installation parameters in the IOA chapter of the INCONTROL for z/OS Installation Guide.

The requested function stops.

Corrective Action: Call your system programmer to correct the DATETYP parameter in the IOAPARM member.

CTW916W PROGRAM `pgm` WAITING FOR `resourceName`

Explanation: One of the IOA monitor internal programs detected an IOA resource in use by a TSO user or batch job. This message normally appears a few times a day.

The variables in this message are:

pgm - the name of the internal program that is waiting for the resource that is in use
resourceName - the name of the resource that is in use

Valid values are:

rname	Meaning
CNDF	The IOA Conditions file
RESF	The Control-M Resources file
LOG	The IOA Log file
Control-M	The Control-M New Day procedure
JES_SSRQ	A JES subsystem request
CKPT	The Control-M Active Jobs file or the Control-D Active Missions file

The message is displayed on the operator console.

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

If the message appears many times every few seconds, the file may be hung. This situation must be resolved by determining which program is holding the specified resourceName. Look for the IOA QNAME that is specified in the IOA Installation Parameter and take appropriate corrective action.
If pgm is CTMFRM and resourceName is CONTROLM, some possible reasons are:
there are several Control-M monitors running with the same QNAME
there is a user daily job running that has a date control record in which columns 60 through 65 are not blank, meaning that it is acting as the Control-M New Day procedure and therefore Control-M has been enqueued
the Control-M New Day procedure was started externally (manually) rather than being started by the monitor, and as a result waits for the monitor to be suspended

Take appropriate corrective action.

If the program name pgm is CTMJES and the resourceName is JES_SSRQ, then Control-M (in its postprocessing phase) has called the JES2 interface using IEFSSREQ (a JES2 subsystem request) and is waiting for some function to be executed by JES2, but the execution of that function is being delayed in JES2. If the message persists in this situation, prepare the Control-M monitor full output and contact BMC Customer Support.

CTW918S INSUFFICIENT MEMORY TO RUN CONTROL- `x`

Explanation:Highlighted, unrollable message.

More memory is required for the INCONTROL monitor.

The specified monitor will shut down.

Corrective Action: Increase the REGION size of the specified monitor.

CTW919S INTERNAL ERROR IN CONTROL-M MONITOR

Explanation:Highlighted, unrollable message.

An internal error occurred in the Control-M monitor.

The Control-M monitor abends with the user abend 0008.

Corrective Action: Try to start the Control-M monitor again. In any case, keep the dump and call BMC Customer Support for assistance.

Messages CTWG00 through CTWGxx

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.

CTWG00I ENTERPRISE/CS MAINFRAME GATEWAY STARTED, RELEASE= `rel`

Explanation: This information message indicates a normal start of MVS Gateway for Enterprise Controlstation.

Corrective Action: No action is required.

CTWG01I ENTERPRISE/CS MAINFRAME GATEWAY DEBUG LEVEL IS SET TO `debugLevel`

Explanation: This information message indicates that the Enterprise Controlstation Mainframe Gateway DEBUG level was set by an operator modify command (F).

The TRACE level is set to a new level. Each TRACE level activates the trace option on different components of the Enterprise Controlstation Mainframe Gateway.

Corrective Action: No action is required.

CTWG02E ENTERPRISE/CS MAINFRAME GATEWAY NOT APF-AUTHORIZED

Explanation: The Enterprise Controlstation Mainframe Gateway is not APF-authorized. The CTWGTW module is not in an APF-authorized library or does not have the AC=1 attribute.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Either add the library name in which CTWGTW resides to the IEAAPF00 member in SYS1.PARMLIB, or relink the module with the AC=1 attribute.

CTWG03E INVALID MODIFY PARAMETER. VALID PARAMETERS ARE:

Explanation: An operator modify command (F) passed an erroneous parameter to the Enterprise Controlstation Mainframe Gateway. One or more GTWG25I messages are displayed on the operator console after this message, each containing a valid modify parameter.

The modify command is rejected.

Corrective Action: Enter a valid modify parameter.

CTWG04E BLDL/ATTACH FAILED FOR TASK `taskName`

Explanation: Initialization of one of the Enterprise Controlstation Mainframe Gateway’s internal tasks failed. The system code indicating the exact reason can be found in the system log.

This may be due to one of the following:

Task taskName is not found in the IOA Load library.
Insufficient storage is available for the Enterprise Controlstation Mainframe Gateway.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Call your system programmer for assistance. If necessary, increase the Enterprise Controlstation Mainframe Gateway REGION size.

CTWG05E UNRECOVERABLE ERROR ENCOUNTERED

Explanation: An unrecoverable error occurred in the operation of the Enterprise Controlstation Mainframe Gateway. The IOA Log, or the Enterprise Controlstation Mainframe Gateway JES messages file or SYSPRINT file, should contain a message with more details about the error. See also, CTWA01W.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, call BMC Customer Support for assistance.

CTWG06E ONE OF THE SUBTASKS HAS ABENDED

Explanation: One of MVS Gateway for Enterprise Controlstation’s internal subtasks has abended.

MVS Gateway for Enterprise Controlstation shuts down with user abend 0006. A dump of the abending task is included in the SYSABEND output file.

Corrective Action: Call your system programmer for assistance. If the problem is not resolved, contact BMC Customer Support.

CTWG07I SHUT DOWN UPON REQUEST FROM OPERATOR

Explanation: This information message confirms that an operator command (P) was issued, requesting shutdown of MVS Gateway for Enterprise Controlstation. This message is followed by message GTWG20I, indicating completion of the shutdown.

MVS Gateway for Enterprise Controlstation starts to shut down.

Corrective Action: No action is required.

CTWG10E TRACE LEVEL MUST BE A NUMBER BETWEEN 0 AND 255

Explanation: An invalid TRACE level was entered, either in the operator modify command (F) or in the operator start command (S). When activating the Enterprise Controlstation trace facilities, specify a number from 0 through 255, inclusive, for the TRACE level. 0 specifies no tracing.

Corrective Action: Issue the command again with the correct TRACE level. The required TRACE level should be supplied by BMC Customer Support.

CTWG11I SERVICE ID " `id` " IS {ENABLED | DISABLED}

Explanation: This information message confirms the current enable or disable status of service ID, after the operator has issued an operator modify command (F) that enables or disables it.

Corrective Action: No action is required.

CTWG12E INVALID PARAMETERS (`parms`) PASSED TO THE ENTERPRISE/CS MAINFRAME GATEWAY

Explanation: One or more parameters which were passed to the Enterprise Controlstation Mainframe Gateway in an operator start command (S) were invalid.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Restart the Enterprise Controlstation Mainframe Gateway with valid parameters.

CTWG13E OPEN OF CONTROL-M ACTIVE JOBS FILE FAILED. DDNAME "DACKPT"

Explanation: Open of the Control-M Active Jobs file failed (the DACKPT DD statement). This may be due to one of the following:

The DACKPT DD statement is missing.
The data set pointed to by the DACKPT DD statement is not the Control-M Active Jobs file.

The program stops executing.

Corrective Action: Correct the JCL for the job or started task and rerun or restart it.

CTWG14I ENTERPRISE/CS MAINFRAME GATEWAY `subtaskName` (`id`) STARTED

Explanation: This information message indicates that a Control-M NJE subtask started normally.

Corrective Action: No action is required.

CTWG15I ENTERPRISE/CS MAINFRAME GATEWAY `subtaskName` (`id`) SHUT DOWN UPON REQUEST FROM MAIN TASK

Explanation: This information message indicates that a Control-M NJE subtask terminated normally.

Corrective Action: No action is required.

CTWG16E OPEN OF CONTROL-M STATISTICS FILE FAILED. DDNAME "DASTAT"

Explanation: The program is unable to open the Control-M Job Execution Statistics file (DD statement DASTAT). Possible causes are:

The DASTAT DD statement is missing.
The data set pointed to by the DACKPT DD statement is not the Control-M Job Execution Statistics file.
VSAM open error.

The program continues executing, but without accessing the Job Execution Statistics file.

Corrective Action: Look for VSAM messages or other system messages. Correct the JCL for the job or started task and rerun or restart it.

CTWG17E FILE ALLOCATED TO DDNAME "DACKPT" IS NOT YOUR CONTROL-M ACTIVE JOBS FILE

Explanation: The data set pointed to by the DACKPT DD statement is not your Control-M Active Jobs file. This is due to one of the following:

The data set pointed to by the DACKPT DD statement is not the Control-M Active Jobs file.
The data set pointed to by the DACKPT DD statement is the Control-M Active Jobs file, but of another monitor, or of a different Control-M version.

The program stops executing.

Corrective Action: Correct the JCL of the job or started task and rerun or restart it.

CTWG19W DUPLICATE `processing_parm` FOUND IN JOB `jobName` ORDERID `orderId`

Explanation: During download of the Control-M Active Jobs file or update of the Active network, a job was encountered that contained a duplicate processing parameter entry.

Only one of the duplicate entries will be downloaded.

Corrective Action: It is advisable to correct the job definition in the mainframe so that it does not contain any duplicate processing parameter entries.

CTWG20I ENTERPRISE/CS MAINFRAME GATEWAY SHUTTING DOWN

Explanation: This information message is issued when the Control-M NJE Gateway shuts down, either as a result of an operator command (P), or due to internal Control-M NJE Gateway events. The Control-M NJE Gateway log, the Control-M NJE Gateway JES messages file, or the SYSPRINT file usually contain additional messages concerning the reason for the shutdown.

The Control-M NJE Gateway shuts down.

Corrective Action: No action is required.

CTWG21S ENTERPRISE/CS MAINFRAME GATEWAY ENDED WITH ERRORS

Explanation: The Enterprise Controlstation Mainframe Gateway ended with an error. The IOA Log, or the Enterprise Controlstation Mainframe Gateway JES messages file or SYSPRINT file, should contain additional messages concerning the specific error.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: Check the IOA Log or the system log for the reason. Call your system programmer for assistance if needed. Try to start the Enterprise Controlstation Mainframe Gateway again.

CTWG22W DUPLICATE `processing parm` FOUND IN JOB `jobName` TABLE `tableName`

Explanation: During table download, a job was encountered that contained a duplicate processing parameter entry.

Only one of the duplicate entries will be downloaded.

Corrective Action: It is advisable to correct the job definition in the mainframe so that it does not contain any duplicate processing parameter entries.

CTWG23I CONTROL-M NJE GATEWAY INTERVAL IS SET TO `nn` SECONDS

Explanation: This information message displays the current NJE Gateway sleeping interval after it is set by an operator Modify command (F).

The NJE Gateway wakes up every nn seconds to check what it must do.

Corrective Action: No action is required.

CTWG24E INTERVAL MUST BE A TWO-DIGIT NUMBER BETWEEN 03 AND 99 SECONDS

Explanation: Invalid Enterprise Controlstation Mainframe Gateway sleeping interval specified in an operator modify command (F). The Enterprise Controlstation Mainframe Gateway sleeping interval must be a 2-digit number from 03 to 99 seconds.

The modify command is rejected.

Corrective Action: Enter a valid sleeping interval.

CTWG25I `valid parm`

Explanation: This information message accompanies message GTWG03E, which indicates that an invalid modify parameter was specified. This message contains a valid modify parameter. This message may appear more than once. Each occurrence lists another valid modify parameter.

Corrective Action: No action is required.

CTWG26E MAXIMUM "ON" CODES EXCEEDED IN JOB `jobName` TABLE `tableName`

Explanation: During Table Download, a job was encountered that contained too many ON codes. There is insufficient space in the internal buffer for the number of ON codes in the job definition.

The table download fails.

Corrective Action: It is advisable to correct the job definition in the mainframe so that it contains fewer ON codes.

CTWG27S INSUFFICIENT STORAGE FOR CONTROL-M APPLICATION SERVER

Explanation: Insufficient storage available for the Control-M Application Server to execute.

The Control-M Application Server shuts down.

Corrective Action: Increase the REGION size parameter for the CTMAS procedure. If it is already REGION=0M, contact BMC Customer Support.

CTWG28E MAXIMUM "ON" CODES EXCEEDED IN JOB `jobName` ORDERID `orderId`

Explanation: During download of the Active Jobs file or update of the Active network, a job was encountered that contained too many ON codes. There is insufficient space in the internal buffer for the number of ON codes in the job definition.

Download of the Active Jobs file or update of the Active network will continue, but the specific job will not be downloaded.

Corrective Action: It is advisable to correct the job definition in the mainframe so that it contains fewer ON codes.

CTWG29E CTWGNRL FAILED. TASKID= `id` FUNCTION= `func` RC= `rc`

Explanation: MVS Gateway for Enterprise Controlstation detected an internal error beyond user control. This error message is issued by the CTWGTW program, which is activated as part of MVS Gateway for Enterprise Controlstation.

MVS Gateway for Enterprise Controlstation shuts down.

Corrective Action: Contact BMC Customer Support.

CTWG30E CTWPUT FAILED. TASKID= `taskId` PUTID= `putId` RC= `rc`

Explanation: Control-M NJE Gateway detected an internal error. Internal CTWPUT operation that was issued by PUTID putId, under subtask number taskId, failed with a return code of rc. If rc=20, a GETMAIN failure occurred above the 16M line.

For some errors, Control-M NJE Gateway shuts down. For other errors, operation continues.

Corrective Action: If Control-M NJE Gateway shuts down, contact BMC Customer Support. If rc=20, increase the region size.

CTWG31W YOUR ENTERPRISE/CS MAINFRAME GATEWAY IS ALREADY ACTIVE. QNAME `qName`

Explanation:Highlighted, unrollable message.

An attempt was made to start an Enterprise Controlstation Mainframe Gateway which was already active. It is impossible to run two Enterprise Controlstation Mainframe Gateways with the same QNAME at the same time.

The newly started Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: No action is required.

CTWG32E CONTROL-M RELEASE NOT SUPPORTED (`rel`)

Explanation: The Enterprise Controlstation Mainframe Gateway was started on a Control-M installation with a release (rel) that is not supported. The Enterprise Controlstation supports Control-M Release 3.0.0 and above.

The Enterprise Controlstation Mainframe Gateway shuts down.

Corrective Action: No action is required.

CTWG33E INCOMPATIBLE GATEWAY VERSIONS. MAINFRAME GATEWAY VERSION `mainframe_version`. WORKSTATION GATEWAY VERSION `workstation_version`

Explanation: The version of MVS Gateway for Enterprise Controlstation is not compatible with the Workstation Gateway version. The two gateways should be installed from the same installation version. If only one gateway was upgraded, the link cannot become active.

MVS Gateway for Enterprise Controlstation shuts down.

Corrective Action: Either upgrade the lower version gateway, or restore the upgraded gateway to the previous version.

CTWG34E CONTROL-M APPLICATION SERVER DOES NOT SUPPORT COMPATIBILITY MODE

Explanation: The Control-M compatibility mode in IOAPARM is set to 2 (MODECTM=3). The Control-M application server can work in no compatibility mode (MODECTM=3).

The Control-M application server terminates with a return code of 8.

Corrective Action: Correct the error and try again, or start a Control-M application server from an earlier version.

CTWG41I CURRENT STATE: DOWN, REQUIRED STATE: UP

Explanation: This information message indicates that the Control-M monitor component being monitored by the Control-M/CM Application Server is DOWN, while its desired state is UP.

Corrective Action: Start the Control-M monitor, or change the desired state to DOWN.

CTWG42I CURRENT STATE: UP, REQUIRED STATE: DOWN

Explanation: This information message indicates that the Control-M monitor component being monitored by the Control-M/CM Application Server is UP, while its desired state is DOWN.

Corrective Action: Stop the Control-M monitor, or change the desired state to UP.

CTWG43E CTMCAS CANNOT START, `param` PARAMETER IS MISSING

Explanation: The Control-M/CM Application Server could not be started, because mandatory parameter param is missing from the CTMPARM member.

The Control-M/CM Application Server shuts down.

Corrective Action: Specify the missing parameters in CTMPARM and then restart the Control-M/CM Application Server.

CTWG51E ENTERPRISE/CS MAINFRAME GATEWAY INTERNAL ERROR. RC= `rc`

Explanation: An internal error occurred. A call to internal routine ECAPUT failed with return code rc.

The IOA Gateway shuts down.

Corrective Action: Contact your INCONTROL administrator.

Messages CTWH00 through CTWHxx

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.

CTWH00I DOWNLOAD OF ACTIVE DATABASE STARTED

Explanation: Information message issued by the Control-M Application Server indicating that the download of the IOA and Control-M database is currently in progress.

Corrective Action: No action is required.

CTWH01I DOWNLOAD OF ACTIVE DATABASE ENDED SUCCESSFULLY

Explanation: Information message issued by the Control-M Application Server indicating that the download of the IOA and Control-M database has ended successfully.

Corrective Action: No action is required.

CTWH02I SERVER IS READY TO RECEIVE REQUESTS

Explanation: This information message indicates that the Enterprise Controlstation Workstation Gateway server has finished its initialization. The server is now ready to receive requests issued by the Enterprise Controlstation Workstation Gateway.

Corrective Action: No action is required.

CTWH03E DOWNLOAD OF ACTIVE DATABASE FAILED

Explanation: Download of the IOA and Control-M database failed.

The download of the IOA and Control-M database, performed by the Control-M Application Server, has ended with an error.

The Control-M Application Server shuts down.

Corrective Action: Look in the job log, SYSPRINT and IOA Log for messages containing the reason for the failure. After the problem has been resolved, restart the Control-M Application Server.

CTWH04E MODULE `modName` SHOULD BE REUSABLE

Explanation: This message indicates that an IOA module that should have been reusable, is not.

The modName module is supplied with the IOA installation tape with the reusable attribute bit on. However, the reusable attribute has become corrupted.

The program stops executing.

Corrective Action: Copy the modName module from the IOA installation tape to the IOA load library, refresh LLA, and rerun the program.

CTWH05E ERROR DETECTED BY WORKSTATION GATEWAY DURING DOWNLOAD

Explanation: Download of the Active Jobs file failed due to an error encountered by the Workstation Gateway.

Download of the Active Jobs file was initiated, but the Workstation Gateway indicated that an error was encountered on the workstation side.

Download of the Active Jobs file fails.

Corrective Action: Look for error messages issued by the workstation and correct the problem accordingly.

CTWH06I WORKSTATION DATABASE IS SYNCHRONIZED WITH THE MAINFRAME DATABASE

Explanation: This information message is issued after establishment of communication, and indicates either that download of the Active Jobs file has ended successfully, or that it is not required.

Corrective Action: No action is required.

CTWH07E KSL INTERNAL ERROR TYPE `type`, RC = `rc`

Explanation: The Control-M Application Server encountered problems interfacing with the KSL subtask.

In this message, type is one of the following:

type	Description
TYPE 0001	Attempt to initialize KSL subtask.
TYPE 0002	Waiting for KSL subtask to perform a request.
TYPE 0003	KSL subtask ended abnormally.

The return code contains the system abend code.

The Control-M Application Server shuts down.

Corrective Action: Check the messages in the job log and the output in file DAKSLOUT. If message CTM555S appears, increase the REGION size. If no relevant messages appear, contact BMC Customer Support.

CTWH08I DOWNLOAD OF {CONTROL-M ACTIVE JOBS | IOA CONDITIONS/ RESOURCES} FILE {STARTED | ENDED}

Explanation: This information message indicates that downloading of the specified file started or ended.

The specified file is being downloaded from Control-M on the mainframe to an Enterprise Controlstation. This message indicates which phase of the download process was reached.

Corrective Action: No action is required.

CTWH09E OPEN OF KSL COMMUNICATION FILE FAILED. DDNAME "KSLCOMM"

Explanation: Open of the KSL Communication file failed (the KSLCOMM DD statement). This error message is issued by the Control-M Application Server and may be due to one of the following:

The KSLCOMM DD statement is missing.
The Control-M Application Server JCL procedure has been modified.

The Control-M Application Server shuts down.

Corrective Action: Correct the Control-M Application Server JCL procedure, and restart the Control-M Application Server.

CTWH10I {CTWSRVE | CTWDET} {STARTED | ENDED}

Explanation: This information message indicates that the Control-M Application Server initiated or shut down subtasks.

Corrective Action: No action is required.

CTWH12E SERVER INTERNAL ERROR TYPE `type`

Explanation: The server program detected an internal error.

This error message is issued by the CTWSRVR program, which is activated as part of the Control-M Application Server, and is due to reasons beyond the user’s control.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

CTWH18E MEMBER: `memName` ORDERID: `orderId` NOT FLAGGED FOR EXCLUSION: `rc rsn`

Explanation: Indicates that a job, which caused an abend while downloading to Control-M/EM, and was therefore supposed to be flagged for exclusion from the next download, could not be flagged. The full message details the return code and reason code, which specify why the job could not be flagged.

Corrective Action: If the problem occurring during download persists, contact Control-M support.

CTWH53E FORMAT OF ACTIVE JOBS FILE ABENDED

Explanation: An abend occurred when the Active Jobs file was last formatted. The New Day process did not finish OK. ECSGATE cannot work with the AJF, because the AJF might be corrupted.

The Control-M Application Server shuts down.

Corrective Action: Inform your INCONTROL administrator.

CTWH57I ACTIVE JOBS FILE IS BEING FORMATTED

Explanation: This information message indicates that the Control-M Active Jobs File (AJF) is currently being formatted.

The Control-M Application Server holds updates. After formatting is finished, it executes a full download to the Enterprise Controlstation.

Corrective Action: No action is required.

CTWH60W RUN NUMBERS `run_num1` TO `run_num2` OF `jobName` HAVE NOT BEEN CAPTURED

Explanation: The Control-M Application Server detected that during its last sleeping period it missed some events.

This message is issued by the Control-M Application Server when it detects that the run number of the jobName job in the Control-M Active Jobs file has changed by more than one during the last sleeping period of the Control-M Application Server. This means that run numbers run_num1 to run_num2 of the job have not been captured by the Control-M Application Server.

Corrective Action: Consider decreasing the SLEEPINT parameter in the relevant APSERVER statement in the ECAPARM member.

CTWH61E DETECTOR INTERNAL ERROR TYPE `type`

Explanation: The detector program detected an internal error. This error message is issued by the Control-M Application Server, and is due to reasons not in user control.

The Control-M Application Server shuts down.

Corrective Action: Please have your INCONTROL administrator contact BMC Customer Support.

CTWH67I DOWNLOAD PROCESS WILL TAKE PLACE SINCE `rsn`

Explanation: This information message indicates that a download will be executed, and the reason.

Possible causes of this message are:

The Control-M Active Jobs File (AJF) was formatted since the last Application Server cycle.
The Control-M Application Server received a STARTLINK modify command.

Possible values for rsn are:

ACTIVE JOBS FILE WAS FORMATTED
STARTLINK COMMAND WAS ISSUED

The Control-M Application Server requests and will execute a full download to the Enterprise Controlstation.

Corrective Action: No action is required.

Messages CTWI00 through CTWIxx

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.

CTWI00I DOWNLOAD OF IOA DATA BASE STARTED

Explanation: This information message is issued by the Enterprise Controlstation Download utility to indicate that downloading of the IOA and Control-M database is currently in progress.

Corrective Action: No action is required.

CTWI01I DOWNLOAD OF IOA DATA BASE ENDED SUCCESSFULLY

Explanation: Information message issued by the Enterprise Controlstation Download utility, indicating that the download of the IOA and Control-M database has ended successfully.

Corrective Action: No action is required.

CTWI02E RESOURCE `resourceName` CONTAINS NULL, INTERNAL CODE `code`

Explanation: A resource containing nulls in its name was encountered during download or database update. A null is not valid in the name of a quantitative or control resource.

The Control-M Application Server terminates with a condition code of 08.

Corrective Action: Report the occurrence to BMC Customer Support.

CTWI03E OPEN OF ENTERPRISE/CS INFO DOWNLOAD FILE FAILED. DDNAME "DWNINFO"

Explanation: The Enterprise Controlstation Download utility could not open the Download Info file (DD statement DWNINFO).

Possible causes are:

The DWNINFO DD statement is missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

CTWI04E OPEN OF ENTERPRISE/CS JOBS DOWNLOAD FILE FAILED. DDNAME "DWNJOBS"

Explanation: The Enterprise Controlstation Download utility could not open the Download Jobs file (DD statement DWNJOBS).

Possible causes are:

The DWNJOBS DD statement is missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

CTWI06E INSUFFICIENT STORAGE FOR THE ENTERPRISE/CS DOWNLOAD UTILITY

Explanation: The Enterprise Controlstation Download utility requires more storage in order to execute.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Increase the REGION size and rerun the download job.

CTWI07E DOWNLOAD INTERNAL ERROR TYPE `type`

Explanation: An internal error occurred during execution of the Enterprise Controlstation Download utility.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Have your INCONTROL administrator contact BMC Customer Support.

CTWI08E OPEN OF ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE FAILED. DDNAME "DAGROUP"

Explanation: The Control-M Application Server or Download utility is unable to open the Application-Group Definition file (DD statement DAGROUP). This may be due to one of the following:

The DAGROUP DD statement is missing.
The Control-M Application Server JCL procedure, or the download JCL procedure, or the JCL of the download job, has been modified.

The Control-M Application Server or Download utility continues executing, but without processing the applications.

Corrective Action: Correct the Control-M Application Server JCL procedure and restart the Control-M Application Server, or correct the download JCL procedure or the JCL for the download job and rerun the download job.

CTWI09E MAXIMUM APPLICATIONS IN ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE EXCEEDED. DDNAME "DAGROUP"

Explanation: The Control-M Application Server or Download utility is unable to process all the applications in the Application-Group Definition file (the DAGROUP DD statement). Too many applications were defined in the Application-Group Definition file.

The Control-M Application Server or Download utility continues executing, but processes only some of the applications.

Corrective Action: Check the Application-Group Definition file, and if it is correct, contact BMC Customer Support.

CTWI10E MAXIMUM GROUPS IN ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE EXCEEDED. DDNAME "DAGROUP"

Explanation: The Control-M Application Server or Download utility is unable to process all the groups in the Application-Group Definition file (the DAGROUP DD statement). Too many groups were defined in the Application-Group Definition file.

The Control-M Application Server or Download utility continues executing, but processes only some of the groups.

Corrective Action: Check the Application-Group Definition file, and if it is correct, contact BMC Customer Support.

CTWI11E INVALID STATEMENT IN ENTERPRISE/CS APPLICATION-GROUP DEFINITION FILE. DDNAME "DAGROUP"

Explanation: The Control-M Application Server or Download utility is unable to process a statement in the Application-Group Definition file (the DAGROUP DD statement). An invalid statement appeared in the Application-Group Definition file.

The Control-M Application Server or Download utility continues executing, but skips processing of the invalid instruction.

Corrective Action: Correct the syntax in the Application-Group Definition file, and restart the Control-M Application Server or rerun the Enterprise Controlstation Download utility.

CTWI14E OPEN OF ENTERPRISE/CS CONTROL RESOURCES DOWNLOAD FILE FAILED. DDNAME "DWNCNTRL"

Explanation: The Enterprise Controlstation Download utility could not open the Download Control Resources file (the DWNCNTRL DD statement). Possible causes are:

The DWNCNTRL DD statement is missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

CTWI15E OPEN OF ENTERPRISE/CS QUANTITATIVE RESOURCES DOWNLOAD FILE FAILED. DDNAME "DWNQUANT"

Explanation: The Enterprise Controlstation Download utility is unable to open the Download Quantitative Resources file (the DWNQUANT DD statement).

Possible causes are:

The DWNQUANT DD statement missing.
The download JCL procedure or the JCL of the download job has been modified.

The Enterprise Controlstation Download utility stops executing.

Corrective Action: Correct the download JCL procedure or the JCL for the download job and rerun the download job.

CTWI50I BUILDING OF ECS COMMUNICATION DATASET STARTED

Explanation: This information message indicates that the Enterprise Controlstation Communication Dataset formatting utility started allocating and formatting the Enterprise Controlstation Communication Dataset file.

Corrective Action: No action is required.

CTWI51I BUILDING OF ECS COMMUNICATION DATASET ENDED

Explanation: This information message indicates that the Enterprise Controlstation Communication Dataset formatting utility completed allocation and formatting of the Enterprise Controlstation Communication Dataset file normally.

Corrective Action: No action is required.

CTWI52E BUILDING OF ECS COMMUNICATION DATASET FAILED

Explanation: The Enterprise Controlstation Communication Dataset formatting utility failed.

The utility fails.

Corrective Action: Look for an earlier error message that describes the type of error.

CTWI53E OPEN OF DDNAME DAM2G FAILED

Explanation: The Enterprise Controlstation Communication Dataset formatting utility failed to open the Enterprise Controlstation Communication Dataset file that is allocated to DD statement DAM2G. Possible causes are:

The DAM2G DD statement is missing.
There is insufficient memory for the job.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the JCL and rerun the job.

CTWI54E I/O ERROR OCCURRED WHILE BUILDING THE ECS COMMUNICATION DATASET

Explanation: An I/O error occurred in the Enterprise Controlstation Communication Dataset formatting utility while formatting the Enterprise Controlstation Communication Dataset file.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the file DCB parameters, and rerun the job. If necessary, contact BMC Customer Support.

CTWI55E THE SIZE OF SHOUT TO ECS COMMUNICATION DATASET IS NOT SET CORRECTLY

Explanation: An invalid value was specified on installation for the M2GSIZE parameter. The utility stops executing with a condition code of 08.

Corrective Action: Specify a valid value for the M2GSIZE parameter, and rerun the file creation process, as follows:

If this message was issued in a customized installation, do the following to set a valid value for the M2GSIZE parameter:

Open the IOA Installation and Customization Engine (ICE).
On the ICE Main Menu, select Installation.
On the IOA Installation screen, select Customized installation.
Set the Product ID to IOA, type 2 (INSTALL IOA) in the OPTION field, and press Enter.
Select Major Step 21 (Install Control-M Application Server), Minor Step 2 (Shout to Control-M/EM Parameters).
Change the value of the M2GSIZE parameter.

If this message was issued in a Default installation, save and exit the installation, change the value using the ICE Main Menu Customization option, run the job, and then return to the Default installation.

If this message was issued in a cloning installation, you first need to finish the cloning installation and then change the value using the ICE Main Menu Customization option. For more information, see the “Customizing INCONTROL products” section of the INCONTROL for z/OS Installation Guide.

CTWI56W SHOUT TO ECS COMMUNICATION DATASET OVERFLOWED. SOME MESSAGES MAY BE LOST

Explanation: The number of Shout messages written to the Enterprise Controlstation Communication Dataset file exceeded the available space. The Enterprise Controlstation Communication Dataset file contains a fixed number of blocks determined by the M2GSIZE parameter. Each block may contain one Shout message. Each time a Shout message is read from the file, a block is freed. Messages are being written to the file faster than they are read.

Old messages in the file are overwritten by newer Shout messages.

Corrective Action: If this condition occurs regularly, increase the size of the Enterprise Controlstation Communication Dataset file.

Messages CTWJ00 through CTWJxx

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.

CTWJ01E UPD INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the type type occurred during processing of the UPD subtask.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

CTWJ02E OVERRUN OF THE UPDATE MESSAGES QUEUE. TRANSMISSION TOO SLOW OR NOT ENOUGH MEMORY

Explanation: The storage available for database update messages is full.

New database update messages have overwritten old messages that have not yet been sent. This may be due to a lack of memory or may happen when a large number (usually several thousand) of update messages have been accumulated without being sent, due to slow transmission of the messages.

Slow transmission may be due to one of the following:

Communications bottleneck, such as inadequate communication bandwidth
Mainframe bottleneck, such as high paging of the Control-M Application Server
Workstation bottleneck, such as CPU overload

The Control-M Application Server shuts down.

Corrective Action: If an xxxJ07E message (for example, UPDJ07E) precedes this message, implement the User Action from that message. Otherwise, determine where the bottleneck is and resolve it.

CTWJ03E ADD INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the type type occurred during processing of the CTWADD subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

CTWJ04E DEL INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the type type occurred during processing of the CTWDEL subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

CTWJ05E READ INTERNAL ERROR. TYPE `type`

Explanation: An internal error of the type type occurred during processing of the CTWREAD subroutine.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

CTWJ06E LOCK OF UPD CHAIN FAILED. STD= `std` FUNC= `func`

Explanation: Locking of the update messages chain has failed.

Access to the update messages chain is serialized by a locking mechanism. The number std subtask in the func function attempted to lock the chain several times but was unsuccessful.

The Control-M Application Server shuts down.

Corrective Action: Contact BMC Customer Support.

CTWJ07E GETMAIN FOR UPD MESSAGE FAILED. OLDEST MESSAGE(S) WILL BE DELETED

Explanation: The storage available for database update messages is full.

New database update messages have overwritten old messages that have not yet been sent. This happens when a large number (usually several thousand) of update messages have been accumulated without being sent, due to slow transmission of the messages.

Slow transmission may be due to one of the following:

Communications bottleneck, such as inadequate communication bandwidth
Mainframe bottleneck, such as high paging of the Control-M Application Server
Workstation bottleneck, such as CPU overload

Storage space is made available for these messages by deleting the oldest message not yet sent. The Control-M Application Server continues processing. As long as there is a lack of storage space, old messages not yet sent will continue to be deleted to make room for new messages.

Corrective Action: Increase the storage space available by increasing the REGION size of the Control-M Application Server. If slow transmission is a problem, determine where the bottleneck is and resolve it.

CTWJ08E MAXIMUM MESSAGES IN UPD CHAIN REACHED. OLDEST MESSAGE WILL BE DELETED

Explanation: The storage available for database update messages is full.

Slow transmission may be due to one of the following:

Communications bottleneck, such as inadequate communication bandwidth
Mainframe bottleneck, such as high paging of the Control-M Application Server
Workstation bottleneck, such as CPU overload

Corrective Action: Determine where the bottleneck is and resolve it.

CTWJ50I CTWUPD STARTED

Explanation: This information message indicates that the Control-M Application Server started the CTWUPD subtask.

Corrective Action: No action is required.

CTWJ51I LOGICAL CONNECTION IS SUSPENDED WHILE THE ACTIVE JOBS FILE IS BEING FORMATTED

Explanation: This information message indicates that the logical connection between the Control-M Application Server and the Workstation Gateway is temporarily suspended, because the Active Jobs file is currently being formatted.

The workstation database is not up-to-date, and no requests issued by the Enterprise Controlstation Control Application will be handled, until the format of the Active Jobs file is completed.

Corrective Action: No action is required.

CTWJ52I LOGICAL CONNECTION RESUMED

Explanation: This information message indicates that the logical connection between the Control-M Application Server and the Workstation Gateway has been resumed.

The workstation database may now request synchronization, and other requests issued by the Enterprise Controlstation Control Application will now be handled.

Corrective Action: No action is required.

CTWJ58E DATABASE UPDATES SENT TO THE WORKSTATION GATEWAY HAVE NOT BEEN CONFIRMED IN TIME

Explanation: The Control-M Application Server sent database updates to the Enterprise Controlstation Workstation Gateway, but did not receive confirmation for them in time.

This error message is issued by the Control-M Application Server and is due to one of the following:

The Workstation Gateway has stopped responding, due to an error condition in the software or hardware.
Responses are delayed because of poor performance.

Corrective Action: Check if the workstation is hanging and if there are any error messages at the workstation which indicate the cause of the problem. If the workstation is not hanging, there must be some performance bottleneck in the system. Try to determine whether this bottleneck is at the workstation side, in the communication media, or at the mainframe.

CTWJ59E CONFIRMATION SEQUENCE NUMBER ERROR. EXPECTED= `exp_num` RECEIVED= `rcv_num`

Explanation: The Control-M Application Server has received an out of sequence confirmation of a database update.

This error message is issued by the Control-M Application Server. The Mainframe Gateway expects to receive confirmations for database updates in increasing order, but a confirmation with a sequence number of rcv_num has been received, when a confirmation with a sequence number of at least exp_num was expected.

The Control-M Application Server continues executing.

Corrective Action: Contact BMC Customer Support.

CTWJ60E DATA BASE UPDATE TYPE `msgType` HAS BEEN REJECTED BY THE WORKSTATION GATEWAY

Explanation: The Enterprise Controlstation gateway rejected a message of the msgType type from the Control-M Application Server.

This message is issued each time a database update message is rejected by the Enterprise Controlstation gateway.

Valid values for msgType are:

msgType	Explanation
A	Update of full Active Jobs file record.
B	Short update of an Active Jobs file record.
N	New job that was added to the Active Jobs file.
O	Update of full Active Jobs file record.
X	Update of only the fixed part of an active jobs.
C	Condition update.
R	Control resource update.
Q	Quantitative resource update.
T	Alert (Shout message) to workstation.

The gateway continues processing. Rejected database updates rejected are written to the file referenced by the DASNAP DD statement.

Corrective Action: Look for error messages on the workstation side and correct the problem accordingly. Review the rejected database updates in the file referenced by DASNAP.

Messages CTWL00 through CTWLxx

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.

CTWL01E INTERNAL ERROR, ORDER ID order_id PROCESS EXCEEDING THRESHOLD

Explanation: The archiver "get log" request exceeds the threshold, so the request is canceled.

Corrective Action: No action is required. The archiver will usually retry to obtain the log again after some time.

CTWL02I LOG LOAD INDEX IS NOT ENABLED

Explanation: This information message indicates that the index log is not enabled and the "get log" request might take more time.

Corrective Action: No action is required.

CVI messages

This group includes messages for the Control-V product.

Messages CVIG00 through CVIGxx

This group includes messages for the Control-V product.

CVIGC0S INTERNAL ERROR IN CONVERSION PROGRAM

Explanation: An internal error occurred when converting index records from VSAM into IOA Access Method records. The error occurred during the transfer of internal parameters.

The database conversion utility terminates with an error. The VSAM file is not converted into an IOA Access Method file.

Corrective Action: Supply BMC Customer Support with the sysout of the conversion job.

CVIGC1E CLOSE OF INDEX FILE `fileName` FAILED

Explanation: An internal error occurred when converting index records from VSAM into IOA Access Method records. The conversion utility was unable to close an index file.

The database conversion utility terminates with an error. The VSAM file is not converted into an IOA Access Method file.

Corrective Action: Supply BMC Customer Support with the sysout of the conversion job and the name of the index file identified in the message.

CVIGC5S INTERNAL ERROR - FREEMAIN ERROR. RC = `rc`

Explanation: The FREEMAIN macro failed to free space that is controlled by GETMAIN.

The executing program may stop. The system response varies with the environment that issued the message.

Corrective Action: Contact BMC Customer Support.

CVIGC6E INSUFFICIENT MEMORY - GETMAIN ERROR. RC = `rc`

Explanation: There is not enough memory to convert a VSAM file into an IOA Access Method file.

The database conversion utility terminates with an error. The VSAM file is not converted into an IOA Access Method file.

Corrective Action: Increase the region size and rerun the utility.

CTV–CVI

CTV messages

Messages CTV500 through CTV5xx

CTV5F0E INVALID MEDIA = mediaName WAS SPECIFIED FOR FILE fileName

CTV5F1E media DEVICE device SM-CMD-INTF FAILED. COMMAND cmd

CTV5F2E DELETE FAILED. fileName RC : rc

CTV5F3I DELETED fileName

CTV5F4E COLLECTION collect-name NOT DELETED FROM DB2 RC = rc

Messages CTV700 through CTV7xx

CTV700E "INDEX" MUST BE FILLED IN

CTV702E ONLY 3 INDEX LINES CAN BE SET TO R=Y

CTV703E FROM/UNTIL COL ARE OBLIGATORY

CTV704E FIELD SHOULD BE BLANK WHEN " fieldname" IS BLANK

CTV705E "MIGRATE" MUST BE FILLED IN

CTV706E SUBINDEX LEVEL MUST BE IN THE RANGE OF 02-10

CTV707E NEXT SUBINDEX LEVEL MUST BE AT ANY EXISTING LEVEL OR THE NEXT ADJACENT LEVEL

CTV708E FIELD SHOULD BE BLANK WHEN "SUBINDEX" IS BLANK

CTV709E ONLY 9 SUBINDEXES ARE ALLOWED

CTV70AE INVALID SUBINDEX DEFINITION IN THE BRANCH OF MULTI-VALUE INDEX

CTV70BE INVALID OPTION. TRY "M", "A", "T" OR BLANK

CTV70CE INVALID OPTION. TRY "M", "A" OR BLANK

CTV70DE VALID OPTIONS IS "T" ONLY

CTV70EE MASK SHOULD BE IN ASTERISKS.

CTV70FE INDEX COL MUST BE RELATIVE (+/-)

CTV70GE ONLY ONE "DO APPROV" STATEMENT PER "WHEN" STATEMENT MAY BE SPECIFIED

Messages CTVG00 through CTVGxx

CTVG31E THIS OPTION IS INVALID WHEN THE INDEX NAME IS BLANK

CTVG32E NO INDEX EXISTS FOR THIS REPORT

CTVG33I ONLY NINE INDEXES MAY BE DISPLAYED

CTVG34E ONLY "S", "Q" OR " " ARE ALLOWED IN THIS FIELD

CTVG36E NO VALUES IN INDEX

CTVG39E IF A VALUE STARTS WITH A QUOTE, IT MUST END WITH THE SAME TYPE OF QUOTE

CTVG3AE DYNAMIC ALLOCATION OF INDEX FILE FAILED, REASON CODE=rsn

CTVG3BE OPTION MUST BE BLANK OR ONE OF 1, 2 OR 3

CTVG3CE ONLY "Y", "N" OR "O" ARE ALLOWED IN THIS FIELD

CTVG3DE OPEN OF INDEX FILE FAILED

CTVG3EI INDEX/VALUE NON-UNIQUE. VIEW FULL REPORT

CTVG3FI INDEX VALUE NOT FOUND. VIEW FULL REPORT

CTVG40S "E" IS NOT SUPPORTED FOR MIGRATED REPORTS. USE VIEW AND PF4 TO EDIT RULER

CTVG41E THE DISPLAY TYPE CANNOT BE CHANGED WHEN BYPASS PANEL=Q

CTVG42E FROM DATE="LAST" TO DATE MUST BE BLANK

CTVG43E DATE="LAST". USER MUST BE SPECIFIED

CTVG44E THERE IS NO PREVIOUS INDEX

CTVG45E THERE IS NO NEXT INDEX

CTVG46E NO INDEX FOUND FOR THIS REPORT

CTVG47E REQUIRED VALUE DOES NOT EXIST IN THIS INDEX

CTVG48E DISPLAY TYPE Q IS VALID ONLY WHEN BYPASS PANEL=Q

CTVG49E ERROR IN routineName CACHE ROUTINE - RC= rc

CTVG4AE IOASMON ARCHIVE SERVER NOT ACTIVE - RC= rc

CTVG4BE REQUESTED MEDIA NOT ACTIVE

CTVG4CE ERROR LOCATING MIGRATED REPORT

CTVG4DE REQUESTED VOLUME NOT FOUND IN OSS DATABASE

CTVG4EE REQUESTED PLATTER NOT FOUND IN OSS DATABASE

CTVG4FE NO DEVICES ARE ACTIVE FOR THIS MEDIA

CTVG4GE CTVX001 COULD NOT ACCESS INDEXES

CTVG4HS x IS NOT SUPPORTED FOR ACTIVE REPORTS

CTVGB0E ERROR ALLOCATING DEVICE

CTVGB1E OPERATOR COULD NOT MOUNT REQUESTED TAPE

CTVGB2E CACHE REQUEST FAILED - SERVER CODE = rc

CTVGB3E INDEX/VALUE NON-UNIQUE. PRINT REQUEST DENIED

CTVGB4E INDEX VALUE NOT FOUND - PRINT REQUEST DENIED

CTVGB5I NO MORE SUBINDEXES FOR THIS BRANCH

CTVGB6I NO VALUES EXIST FOR THIS INDEX

CTVGB7E INVALID MEDIA SPECIFIED FOR REPORT

CTVGC5S INTERNAL ERROR - FREEMAIN ERROR. RC = rc

Messages CTVP00 through CTVPxx

CTVP40E UNABLE TO ACCESS INDEXES - RC = rc

CTVP41E NOT ENOUGH SPACE FOR INDEXES - SOME INDEXES ARE MISSING

CTVP42E INTERNAL ERROR - INVALID REQUEST SUB-TYPE - MUST BE BETWEEN 1 AND n

CTVP43E INTERNAL ERROR FREEING STORAGE - RC = rc

CTVP44S INSUFFICIENT STORAGE - INCREASE REGION SIZE

CTVP45E REPORT ENTRY DELETED - CANNOT ACCESS INDEXES

CTVP46S ERROR IN INPUT MESSAGE LENGTH - MESSAGE IS TOO SHORT

CTVP47S EOR IN INPUT MESSAGE - INDEX PATH IS INCORRECT

CTVP48S INTERNAL ERROR - LOAD OF MODULE modName FAILED

CTVP49S INTERNAL ERROR - MISMATCH BETWEEN INDEX RECORD AND USER RECORD

CTVP4AS INTERNAL ERROR IN INPUT PARAMETERS

CTVP4BS INTERNAL ERROR - CANNOT LOCATE THE PREVIOUS VALUE FROM WHICH TO START

CTVP4CE CANNOT VIEW REPORT SECTION - INDEX PATH VALUES ARE NOT UNIQUE

CTW messages

CTV5F0E INVALID MEDIA = `mediaName` WAS SPECIFIED FOR FILE `fileName`

CTV5F1E `media` DEVICE `device` SM-CMD-INTF FAILED. COMMAND `cmd`

CTV5F2E DELETE FAILED. `fileName` RC : `rc`

CTV5F3I DELETED `fileName`

CTV5F4E COLLECTION `collect-name` NOT DELETED FROM DB2 RC = `rc`

CTV704E FIELD SHOULD BE BLANK WHEN " `fieldname`" IS BLANK

CTVG3AE DYNAMIC ALLOCATION OF INDEX FILE FAILED, REASON CODE=`rsn`

CTVG49E ERROR IN `routineName` CACHE ROUTINE - RC= `rc`

CTVG4AE IOASMON ARCHIVE SERVER NOT ACTIVE - RC= `rc`

CTVG4HS `x` IS NOT SUPPORTED FOR ACTIVE REPORTS

CTVGB2E CACHE REQUEST FAILED - SERVER CODE = `rc`

CTVGC5S INTERNAL ERROR - FREEMAIN ERROR. RC = `rc`

CTVP40E UNABLE TO ACCESS INDEXES - RC = `rc`

CTVP42E INTERNAL ERROR - INVALID REQUEST SUB-TYPE - MUST BE BETWEEN 1 AND `n`

CTVP43E INTERNAL ERROR FREEING STORAGE - RC = `rc`

CTVP48S INTERNAL ERROR - LOAD OF MODULE `modName` FAILED

CTW001W `taskName` : COMMUNICATION IS NOT ACTIVE

CTW002W `taskName` : NO RESPONSE RECEIVED WITHIN EXPECTED TIME INTERVAL

CTW003W `taskName` : COMMUNICATION SLOWDOWN

CTW004E `taskName` : MBX INTERNAL ERROR ENCOUNTERED. FUNCTION: `funcName` RC= `rc`

CTW046S BLDL/LOAD FAILED FOR THE MODULE "`modName` "

CTW392S OPEN OF DDNAME `ddName` FAILED

CTW567I COND `cond` ODATE `odate` {ADDED | DELETED | FOUND} BY USER `userId` / `jobName (jobId)`

CTW912S ERROR IN CONTROL- `x` INSTALLATION PARAMETERS - INVALID DAYTIME

CTW916W PROGRAM `pgm` WAITING FOR `resourceName`

CTW918S INSUFFICIENT MEMORY TO RUN CONTROL- `x`

CTWG00I ENTERPRISE/CS MAINFRAME GATEWAY STARTED, RELEASE= `rel`

CTWG01I ENTERPRISE/CS MAINFRAME GATEWAY DEBUG LEVEL IS SET TO `debugLevel`

CTWG04E BLDL/ATTACH FAILED FOR TASK `taskName`

CTWG11I SERVICE ID " `id` " IS {ENABLED | DISABLED}

CTWG12E INVALID PARAMETERS (`parms`) PASSED TO THE ENTERPRISE/CS MAINFRAME GATEWAY

CTWG14I ENTERPRISE/CS MAINFRAME GATEWAY `subtaskName` (`id`) STARTED

CTWG15I ENTERPRISE/CS MAINFRAME GATEWAY `subtaskName` (`id`) SHUT DOWN UPON REQUEST FROM MAIN TASK

CTWG19W DUPLICATE `processing_parm` FOUND IN JOB `jobName` ORDERID `orderId`

CTWG22W DUPLICATE `processing parm` FOUND IN JOB `jobName` TABLE `tableName`

CTWG23I CONTROL-M NJE GATEWAY INTERVAL IS SET TO `nn` SECONDS

CTWG25I `valid parm`

CTWG26E MAXIMUM "ON" CODES EXCEEDED IN JOB `jobName` TABLE `tableName`

CTWG28E MAXIMUM "ON" CODES EXCEEDED IN JOB `jobName` ORDERID `orderId`

CTWG29E CTWGNRL FAILED. TASKID= `id` FUNCTION= `func` RC= `rc`

CTWG30E CTWPUT FAILED. TASKID= `taskId` PUTID= `putId` RC= `rc`

CTWG31W YOUR ENTERPRISE/CS MAINFRAME GATEWAY IS ALREADY ACTIVE. QNAME `qName`

CTWG32E CONTROL-M RELEASE NOT SUPPORTED (`rel`)

CTWG33E INCOMPATIBLE GATEWAY VERSIONS. MAINFRAME GATEWAY VERSION `mainframe_version`. WORKSTATION GATEWAY VERSION `workstation_version`

CTWG43E CTMCAS CANNOT START, `param` PARAMETER IS MISSING

CTWG51E ENTERPRISE/CS MAINFRAME GATEWAY INTERNAL ERROR. RC= `rc`

CTWH04E MODULE `modName` SHOULD BE REUSABLE

CTWH07E KSL INTERNAL ERROR TYPE `type`, RC = `rc`