Control-m Error Codes

12 views

Skip to first unread message

Enrique Vasquez

unread,

Aug 3, 2024, 5:41:31 PM8/3/24

to presrimisou

This topic provides the list of all error codes for the individual modules and objects of the BMC Client Management , such as operational rules, rollouts and performance counters. The table displays to which modules/object types and or situations it applies, the error code number, its translation and possibly an explanation where required:

Incompatible Format.nnYou must set the format to table, add a second column to your subreport or modify your columns.nTo use one of the chart formats your subreport must have at least one data column returning a numeric type.

This query is assigned to device groups or security profiles. Any modification of the criteria may cause a reevaluation of the group members, thus causing assignments or unassignments of operational rules and/or a reevaluation of the administrators' rights. Are you sure you want to continue?

External Integration is not enabled for the specified user name. Ensure that the user name you specified matches the login specified in BMC Client Management under Global Settings > External Integration.

The project build failed because it conflicts with the active project \ProjectId\ on the MAC address or PXE Mask \MacAddress\. Disable the project or target responsible for this conflict to continue.

Explanation: The sort routine invoked by the CTVUPGDB utility ended with errors. The CTVUPGDB utility issues this message whenever the sort routine it invokes ends with a return code other than 0.

Explanation: The CTVGDB routine invoked by the CTVUPGDB utility ended with errors. The CTVUPGDB utility issues this message whenever the CTVGDB routine it invokes ends with a return code other than 0.

Explanation: The CTVUPGDB utility tried to add another main index to the Global Index database when it had already added the maximum number for this run. The MAXINDX parameter defines the maximum number of indexes that may be added to the Global Index database in each run of the CTVUPGDB utility.

Explanation: The CTVUPGDB utility is trying to add an index that is already in the Global Index database. The GIX029I message, which follows the current message, provides details about the index that caused the error.

Explanation: This information message is issued by the CTVUPGDB utility before the GIX017E error message and displays the index name and data set name of the index file for which the dynamic allocation error occurs.

Explanation: This information message follows the CTD908S message. The GIX02FE message identifies the VSA key of the record that was being accessed when the error occurred that caused the CTD908S message to be issued.

Explanation: The CTVUPGDB utility tried to add a path that was already in the Global Index database with different length parameters. This message occurs during an attempt to change the length of the index value in the definition of the decollation mission for a path that is already in the Global Index database.

Corrective Action: Either change the length of the index value in the definition of the decollation mission that is causing the incorrect path or delete the old path from the Global Index database.

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started searching ACTIVE and MIGRATED user files. This message makes it easier to calculate how long it takes to run each stage of the housekeeping utility.

Explanation: This information message indicates that the CTVGICL Global Index housekeeping utility started deleting VSA entries from the Global Index database. This message makes it easier to calculate how long it takes to run each stage of the housekeeping utility.

Explanation: The CTVUPGDB Global Index utility could not read the specified library member of the CTD PARM library. CTVUPGDB was trying to read GLOBIDB or the member specified by the CHKPTID input parameter to see if the member needed to be restarted from the checkpoint as a result of an earlier abnormal ending.

Corrective Action: If there are no other messages, and the utility ended normally, no action is required. This message may be triggered by the first run of the CTVUPGDB utility. Otherwise, examine the other error messages and respond accordingly.

Explanation: The parm input parameter for the CTVUPGDB Global Index housekeeping utility is in the wrong position. The ALT and BASELEN parameters may be specified only once each and must appear after the PATH parameter because they refer to a specific path.

Explanation: This information message is the header for a list of reports that the DELRPT function of the CTVGICL Global Index housekeeping utility deleted. The GIX046I message is followed by one or more instances of the GIX047I message.

Explanation: This information message identifies a report that was deleted by the CTVGICL utility. The first GIX047I message in a series is preceded by either the GIX046I or the GIX04II message.

Explanation: A request to retrieve data from the Global Index DB2 database is rejected because the corresponding DB2 table is in use by another job that is loading or deleting data. This message is directed to the WebAccess user who issued the request.

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

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.

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.

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, GTWA01W.

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.

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.

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.

Explanation: The Control-M NJE Gateway ended with an error. The Control-M NJE Gateway log, the Control-M NJE Gateway messages file, or the SYSPRINT file usually contain additional messages about the specific error.

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.

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.

An attempt was made to start an Control-M NJE Gateway that was already active. Two Control-M NJE Gateways with the same QNAME cannot run at the same time in the same MVS. If resources are shared by more than one MVS, this restriction applies to every MVS that shares these resources.

Explanation: At startup, the MFCONNECTION definition was not valid. Either the syntax of one of the two statements following MFCONNECTION is not valid, or the definition names a host system that was not specified.

Explanation: At startup, the MFCONNECTION statement in the specified statement was already defined earlier. During comparison of MFCONNECTION statements, the order of the host arguments on the statement is not significant.

Explanation: At startup, the HOST and CONNECT initialization parameters were identical. The HOST parameter identifies the local host, and the CONNECT parameter identifies a partner host. They cannot be the same.

Explanation: This message is issued by the New Day procedure. The data set described by the DAPROG DD statement contains a list of programs to be activated by the New Day procedure. Possible causes are:

Explanation: The pgm program was not in the load list of the Daily subsystem. The DAPROG DD statement describes a data set that contains a list of programs to be activated as part of the Daily subsystem.

Explanation: The pgm Control-M or Control-D internal program that was activated by New Day processing finished with a return code higher than the maximum allowed in the program list. Positions 10-11 in the program list indicate the highest return code that is still considered OK for this program.

Corrective Action: Check the report produced by the AMASPZAP utility to determine the cause of the problem. The zap was probably modified incorrectly. Restore the original JCL job stream, as follows:

If the problem is not due to a user modification of the zap, contact BMC Customer Support for assistance. Your representative will need the report produced by the AMASPZAP utility to resolve the problem.