|
|
|
|
|
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.
Explanation: This information message indicates a normal start of MVS Gateway for Enterprise Controlstation.
Corrective Action: No action is required.
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.
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.
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.
Explanation: Initialization of an IOAGATE internal task failed. The system code indicating the exact reason can be found in the system log. Possible causes are:
The IOAGATE shuts down.
Corrective Action: Call your system programmer for assistance. If necessary, increase the IOAGATE REGION size.
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.
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.
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.
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.
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.
IOAGATE continues executing
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.
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.
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.
The Control-M NJE Gateway shuts down.
Corrective Action: Check the Control-M NJE Gateway log or the system log for the reason. Call your system programmer for assistance if needed. Try to restart the Control-M NJE Gateway.
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.
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.
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.
Explanation: Control-M NJE Gateway detected an internal error. Internal CTWPUT operation that was issued by PUTID putId, under subtask number taskId, failed with return code rc. If the return code was 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 was 20, increase the region size.
Explanation: Highlighted, unrollable message.
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.
The newly started Control-M NJE Gateway shuts down.
Corrective Action: No action is required.
Explanation: The Control-M NJE Gateway main task failed to open the DACONN DD statement at startup. The DD statement is probably missing.
The started NJE Gateway task stops.
Corrective Action: Correct the problem, and restart the job.
Explanation: The Control-M NJE Gateway main task read an empty parameter file at startup.
The started NJE Gateway task stops.
Corrective Action: Correct the problem, and restart the job.
Explanation: At startup, the specified statement in the parameter file was not valid.
The started Control-M NJE Gateway task stops.
Corrective Action: Correct the problem, and restart the job.
Explanation: At startup, the specified statement in the parameter file occurred twice.
The started Control-M NJE Gateway task stops.
Corrective Action: Correct the problem, and restart the job.
Explanation: At startup, the MFCONNECTION was defined incorrectly. The MFCONNECTION description must include one MFCONNECTION statement, and two HOST descriptor statements.
The started Control-M NJE Gateway task stops.
Corrective Action: Review installation instructions, correct the problem, and restart the job.
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.
The started Control-M NJE Gateway task stops.
Corrective Action: Review installation instructions, correct the problem, and restart the job.
Explanation: At startup, the syntax of the MFCONNECTION statement was not valid.
The started Control-M NJE Gateway task stops.
Corrective Action: Review installation instructions, correct the problem, and restart the job.
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.
The started Control-M NJE Gateway task stops.
Corrective Action: Correct the problem, and restart the job.
Explanation: At startup, there was no MFCONNECTION definition in the parameter file. The parameter file must contain at least one MFCONNECTION definition.
The started Control-M NJE Gateway task stops.
Corrective Action: Correct the problem, and restart the job.
Explanation: At startup, the EXEC PGM parameter specified in the started task of the NJE Gateway was not valid.
The started Control-M NJE Gateway task stops.
Corrective Action: Review installation instructions, correct the problem, and restart the job.
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.
The main Control-M NJE Gateway task stops.
Corrective Action: Correct the HOST and CONNECT parameters, and restart the job.
Explanation: Due to an internal error, an internal call (ECAPUT) failed with return code rc. In this message, userId identifies the user from whom the message was received.
The message causing the error is ignored.
Corrective Action: Contact BMC Customer Support.
Parent Topic |