|
|
|
|
|
This group includes messages for the IOA (infrastructure) product.
Explanation: This information message indicates that the Functional monitor was started.
Corrective Action: No action is required.
Explanation: The Functional monitor is not APF authorized. The IOAFMON module is not in an APF authorized library, and it does not have the AC=1 attribute.
The Functional monitor ends with a return code of 8.
Corrective Action: Add the name of the library in which IOAFMON resides to the IEAAPF00 member in the SYS1.PARMLIB library.
Explanation: An invalid parameter was passed to the Functional monitor by means of a modify command. Following this message, one or copies of message IOAM14I appear on the operator console, each containing a valid modify parameter.
The modify command is ignored.
Corrective Action: Specify the modify command with a valid parameter.
Explanation: Initialization of one of the Functional monitor subtasks failed. Possible causes are:
The Functional monitor shuts down.
Corrective Action: Call your system programmer for assistance. If necessary, increase the region size of the Functional monitor.
Explanation: An unrecoverable error occurred in the IOA Functional Monitor.
The IOA Functional Monitor stops running.
Corrective Action: Check for any accompanying message that describe the nature of the problem, correct accordingly, and restart the monitor.
Explanation: A subtask of the Functional monitor abended.
The Functional monitor shuts down with user abend 0006. A dump of the abending subtask 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 indicates that an operator command requesting shutdown of the Functional monitor was issued.
The Functional monitor starts to shut down.
Corrective Action: No action is required.
Explanation: A Functional monitor was started with the same QNAME as an already active Functional monitor. It is impossible to run two Functional monitors with the same QNAME at the same time.
The newly started Functional monitor is shut down.
Corrective Action: No action is required.
Explanation: This information message indicates that the Functional monitor is shutting down. Messages describing the reason for the shutdown are in at least one of the following:
Corrective Action: If the shutdown was not requested, check messages in the above mentioned locations for more information on the reasons for the shutdown.
Explanation: The Functional monitor ended with an error. Messages describing the error may be in the following locations:
The Functional monitor shuts down.
Corrective Action: Check the above mentioned locations for the reasons for the error. If necessary, ask your system programmer for assistance
Explanation: An invalid Functional monitor Sleeping Interval was specified in a modify command. The Functional monitor Sleeping Interval is specified in seconds. It must be a 2-digit value from 03 through 99.
The modify command is ignored.
Corrective Action: Enter the following modify command with a valid sleeping interval: F monitorname,INTERVAL=xx
Explanation: An invalid parameter was specified for a modify command. In this message, valid_parm is a valid modify parameter for the relevant command. This information message follows message IOAM03E. It may be issued more than once, with each occurrence specifying another valid parameter.
Corrective Action: No action is required.
Explanation: This information message indicates that the specified Functional monitor sleeping interval (nn) has been set by means of a modify command.
Corrective Action: No action is required.
Explanation: The available storage is insufficient for execution of the Functional monitor.
The Functional monitor shuts down.
Corrective Action: Increase the region size and restart the Functional monitor.
Explanation: An internal error was detected during the AutoEdit initialization phase of the specified service. In this message, rc is the return code from the AutoEdit initialization phase.
The service is shut down, and as a result the Functional monitor shuts down.
Corrective Action: Have your system programmer call BMC Customer Support for assistance.
Explanation: When an input task attempted to place a request in queue for the Functional monitor no executor was found in the IOAFMON table for this request. This message indicates an internal error.
The variables in this message are:
The request is ignored.
Corrective Action: Contact BMC Customer Support.
Explanation: An internal error occurred during the validity checks phase of the specified service.
The service is shut down and as a result the Functional monitor shuts down.
Corrective Action: Have your system programmer call BMC Customer Support for assistance.
Explanation: The Functional monitor encountered a severe internal error.
The Functional monitor shuts down.
Corrective Action: Have your system programmer call BMC Customer Support for assistance.
Explanation: The specified service failed to load the CTMJSP module. Possible causes are:
The service shuts down and, as a result, the Functional monitor shuts down.
Corrective Action: Correct the problem and restart the Functional monitor.
Explanation: The IOAFCPL utility was unable to obtain the necessary main storage.
The IOAFCPL utility is ended.
Corrective Action: Increase the region size for the IOAFCPL utility.
Explanation: An attempt to open the Functional monitor Log failed. The FMLOG DD statement may be missing or in error in the JCL of the Functional monitor.
The Functional monitor is shut down.
Corrective Action: Check and correct the FMLOG DD statement. Restart the Functional monitor.
Explanation: Either the Functional monitor or the IOAFCPL utility determined that writing the next record into the FMLOG file would destroy previously written information that is not yet obsolete. FMLOG is a cyclic file with periodic checkpoints. A checkpoint is a record of all information in the queue of the functional monitor at a given time. Possible causes are:
If the FMLOG file is too small, this message may result from an attempt to write a new checkpoint to the FMLOG file. If an FMLOG file bigger than 100 tracks is allocated, it will never become full, thereby preventing the problem indicated by this message.
The Functional monitor shuts down.
Corrective Action: Allocate a bigger FMLOG file, and copy the contents of the old file into the new one by means of the IOAFCPL utility.
Explanation: The last checkpoint could not be found in the Functional monitor Log (FMLOG). The FMLOG file is unusable. This message indicates an internal error.
The program that issued this message is terminated.
Corrective Action: Suggested actions:
Explanation: Loading of the shout destination table (dest_table) failed. Possible causes are:
Corrective Action: Correct the problem and issue the modify command with the NEWDEST parameter.
Explanation: Invalid NEWDEST command was given to Functional monitor. Valid format is NEWDEST or NEWDEST=dest_table.
The modify command is rejected.
Corrective Action: Enter a valid NEWDEST modify command.The format is: F monitorname,NEWDEST/NEWDEST=dest_table.
Explanation: This information message indicates that the Functional monitor now starting, determined that the FMLOG is in an invalid format.
The Functional monitor reformats the FMLOG file.
Corrective Action: No action is required.
Explanation: I/O error occurred on FMLOG the file. In this message, explanation is the information provided about this error by MVS macro SYNADAF.
The program that issued this message is terminated.
Corrective Action: Allocate a new FMLOG file, or restore the old one from backup. If the text in this message indicates a software related problem, report it to BMC Customer Support and send a copy of the FMLOG file.
Explanation: This information message indicates that a NEWDEST operator command was passed to Functional monitor and was accepted.
The Functional monitor directs shout messages according to the new destination table.
Corrective Action: No action is required.
Explanation: The initialization phase of the Functional monitor failed. Messages describing the error can be found in the following locations:
The Functional monitor shuts down.
Corrective Action: Have your system programmer call BMC Customer Support for assistance.
Explanation: This information message indicates that user exit IOAX038 is not active. The exit was probably deleted. Exit IOAX038 checks each request to be written to the request queue.
Processing proceeds without checking requests written to the request queue.
Corrective Action: Check if exit IOAX038 was deleted from the IOA Load library. Notify your INCONTROL administrator.
Explanation: An exit called to validate a request produced a non-zero return code.
The variables in this message are:
The request is not processed.
Corrective Action: No action is required.
Explanation: Processing of a DO SET request failed. The Functional monitor failed to add the specified line to the specified member in the dsn data set.
The Functional monitor does not perform this DO SET command, and proceeds to handle subsequent requests.
Corrective Action: For more information, look for previous messages in the IOA Log and in the DASETPRT DD statement, which is allocated by the Functional monitor.
Explanation: This information message indicates that a DO SET request was successfully performed. The Functional monitor inserted the lineNum line into the memName member in the dsn data set.
Corrective Action: No action is required.
Explanation: Open failed for input or output file. The DD statement specifying this file is either missing or in error.
In this message, type is the type of file that failed to open. Valid values are:
The program that issued this message is terminated.
Corrective Action: Correct the JCL and restart the program.
Explanation: The input file specified for the IOAFCPL utility is not in correct FMLOG format.
The IOAFCPL utility is terminated.
Corrective Action: Verify that the FMLOGI DD statement points to a valid FMLOG file.
Parent Topic |