|
|
|
|
|
This group includes messages for the IOA (infrastructure) product.
Explanation: This information message indicates that the IOADBF utility has started. The IOADBF utility allocates and formats an IOA Access Method file component primary or secondary extent.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOADBF utility ended with a return code of rc.
Possible values of rc are listed in message CTD908S.
The IOADBF utility terminates.
Corrective Action: If rc is not zero, check the IOA Log file and the system log for additional messages that describe the error. Correct the problem before rerunning the IOADBF utility.
Explanation: Insufficient storage to initialize the File Transfer task.
The file transfer task is not started.
Corrective Action: Increase the REGION size in the File Transfer monitor procedure. Stop and restart the File Transfer monitor.
Explanation: This message is issued in two cases:
The SPACE parameter specifies the number of primary and secondary blocks to be allocated. Primary and secondary SPACE parameter values must be a number from 2 through 65535. Database file definition statements are usually located in a member of the IOA INSTWORK library.
The IOADBF utility terminates.
Corrective Action: Do the following:
For more information on the IOADBF utility, see the INCONTROL for z/OS Utilities Guide.
Explanation: The File Transfer monitor could not dynamically allocate a file to be transferred. The function that failed, ALLOC, DEALLOC, or CONCATENATE, the reason code, and the return code from SVC 99 are displayed in the message.
The File Monitor continues processing other files.
Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for an explanation of the reason code and return code in the message.
Explanation: This information message indicates that one or more files listed in the Active Transfer file cannot be transmitted to the specified IP address.
The task continues processing other files. The status of the entry in the Active Transfer file is set to WAIT TRANSMIT.
Corrective Action: Check if the server with the specified IP address is active.
Explanation: The BLKSIZE and LRECL parameters specified in the IOA Access Method file Definition statements member for an IOA Access Method file index component are not equal. The logical record length and block size of IOA Database file index components must be equal. Database file Definition statements are usually located in a member of the IOA INSTWORK library.
The IOADBF utility terminates.
Corrective Action: Delete the LRECL parameter to set the logical record length to the value of the BLKSIZE parameter, and rerun the IOADBF utility.
Explanation: The IOADBF utility could not open an IOA Access Method (IAM) file component for reformatting. During reformatting of an IAM file index or data component, the IOADBF utility failed to open and read the file control record from the first extent.
The IOADBF utility terminates.
Corrective Action: Check the IOA Log file and system log for additional messages that describe the error. Correct the problem before rerunning the IOADBF utility.
Explanation: This is one of two messages with the same ID, but different text.
The IOADBF utility could not open the SYSOUT file or the data set referenced by the SYSPRINT DD statement. The IOADBF utility encountered an error while opening the file referenced by the SYSPRINT DD statement. This file is used to write message output during utility execution.
The IOADBF utility terminates.
Corrective Action: Check the IOA Log file and system log for additional messages that describe the error. Correct the problem before rerunning the IOADBF utility.
Explanation: This is one of two messages with the same ID, but different text.
An error occurred during transmission of a file to the PC. The message text describes the reason for the problem.
The file is not transmitted.
Corrective Action: Correct the problem, and restart the File Transfer monitor.
Explanation: This information message indicates that the specified files were successfully transmitted to the PC. The message specifies
Corrective Action: No action is required.
Explanation: The IOADBF utility could not obtain the memory required for execution. The IOADBF utility received a non-zero return code from macro GETMAIN.
The IOADBF utility terminates.
Corrective Action: Take the following steps:
Explanation: The IOADBF utility detected inconsistent parameters for formatting an IOA Access Method file in the member that contains the IOA Access Method definition statements. The parameters that were passed to the IOADBF utility were not of the type required for formatting the file.
The IOADBF utility terminates.
Corrective Action: Take the following steps:
Explanation: The KEYLEN mandatory parameter was not specified in the IOA Access Method (IAM) file definition statements member for the IAM file index component being processed. The KEYLEN parameter is mandatory when allocating and formatting an IAM file index component. IAM file definition statements are usually located in a member of the IOA INSTWORK library.
The IOADBF utility terminates.
Corrective Action: Set the value of the KEYLEN parameter to the value required for the IAM file index component being processed. Rerun the utility.
Explanation: The LRECL parameter is specified in the IOA Access Method (IAM) file definition statements member for the IAM file index component being processed. The internal structure of the Database file index component being processed requires that each block consist of one record. Therefore, the LRECL parameter is not applicable and may not be specified. IAM file definition statements are usually located in a member of the IOA INSTWORK library.
The IOADBF utility terminates.
Corrective Action: Remove the LRECL parameter from the member. Rerun the program.
Explanation: This information message is issued when the File Transfer monitor starts to transfer a package to the identified IP address.
The variables in this message are:
Corrective Action: No action is required.
Explanation: During the operation of the File Transfer monitor, an unrecoverable error occurred when access was attempted to the Active Transfer file.
The File Transfer monitor shuts down.
Corrective Action: Contact your INCONTROL administrator.
Explanation: A serious error occurred while the File Transfer monitor was working. The transfer of the package was rejected by a security exit, or by User Exit 23.
Every transfer request is sent to both the security exit and the user exit, if they exist. Either exit can reject a transfer request.
The package is not transferred.
Corrective Action: If you consider that you ought to have authority to transfer the package, contact your INCONTROL administrator.
Explanation: This warning message is issued when the transfer process fails because the status of the corresponding record in the ATF can not be updated. It can occur if a package, whose time has come for transfer, can not find the corresponding record in the ATF because it was reformatted and refreshed during the NEWDAY process.
CTDFTM continues to work and the subtask with the specified IP address is closed.
Corrective Action: If the package remains at the status NOT TRANSMITTED, reorder the package.
Explanation: The KEYLEN parameter should not be specified in the IOA Access Method (IAM) file definition statements member for IAM file data components. Key fields are only applicable to IAM file index components. The KEYLEN parameter should not be specified for an IAM file data component. IAM file definition statements are usually located in a member of the IOA INSTWORK library.
The IOADBF utility terminates.
Corrective Action: Remove the KEYLEN parameter from the member. Rerun the program.
Explanation: The value specified for the TYPE parameter in the IOA Access Method (IAM) file definition statements member is invalid. Database file definition statements are usually located in a member of the IOA INSTWORK library.
Possible TYPE parameter values are:
The IOADBF utility terminates.
Corrective Action: Specify a valid TYPE parameter in the member. Rerun the program.
Explanation: The value specified for the QUANT1, QUANT2, or QUANT3 parameter in the IOA Access Method (IAM) file definition statements member for the IAM file component being processed is invalid. The QUANT1, QUANT2 and QUANT3 parameters are used with variable record length IAM file components for managing free space areas when new records are written. These parameters must correlate with the BLKSIZE parameter as follows:
QUANT1 < QUANT2 < QUANT3 < BLKSIZE
IAM file definition statements are usually located in a member of the IOA INSTWORK library.
The IOADBF utility terminates.
Corrective Action: The QUANT1, QUANT2, and QUANT3 parameters are for internal use only. Do not modify them without prior consent of BMC Customer Support. When appropriate values are approved, specify valid QUANT1, QUANT2, and QUANT3 parameters in the member, and rerun the utility.
Explanation: The block size specified in the IOA Access Method (IAM) file definition statements member is less than the length of the control record of the IAM file component being processed. The BLKSIZE parameter of the IAM file definition statements member for the IAM file component being processed must not be less than the length of the control record of the component. IAM file definition statements are usually located in a member of the IOA INSTWORK library.
The IOADBF utility terminates.
Corrective Action: For IAM file components containing variable length records, change the relevant definition statements member to increase the BLKSIZE value or reduce the number of blocks specified in the SPACE parameter. For IAM file components containing fixed length records, the BLKSIZE parameter should be more than 255.
Explanation: An attempt to dynamically allocate or deallocate an IOA Access Method (IAM) file component failed. IAM Database processing routines received a non-zero return code from an allocation or deallocation request using SVC 99. The data set name of the IAM file component is specified in message IOAF20S.
The IOADBF utility terminates.
Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the return code and reason code received. If the problem remains unresolved, contact BMC Customer Support.
Explanation: During processing of an IOA Access Method (IAM) file index or data component, the IOADBF utility could not open and read the file control record from the first extent.
The IOADBF utility terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: The IOADBF utility could not read an IOA Access Method (IAM) file component header record. During processing of an IAM file index or data component, an attempt to read the file control record from the first extent failed.
The IOADBF utility terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: The IOADBF utility could not update an IOA Access Method (IAM) file component control record. During processing of an IAM file index or data component, an attempt to update the file control record in the first extent failed.
The IOADBF utility terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: The IOADBF utility could not close an IOA Access Method (IAM) file index or data component.
The IOADBF utility terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: An invalid parameter was passed to the IOADBF utility. A parameter specified in the IOA Access Method (IAM) file definition statements member or the FUNC parameter specified in the JCL procedure is invalid.
The IOADBF utility terminates.
Corrective Action: Set the parameter in error to a valid value. Rerun the program.
Explanation: A dynamic allocation or deallocation error occurred when processing data set dsn. This message indicates the name of the IOA Access Method (IAM) file component that could not be allocated or deallocated. The preceding IOAF14S message indicates the return code received from the allocation or deallocation request using SVC 99.
The IOADBF utility terminates.
Corrective Action: See the IBM manual MVS Programming: Authorized Assembler Services Guide for a description of the return code and reason code received. If the problem remains unresolved, contact BMC Customer Support.
Explanation: The length of the name of the IOA Access Method (IAM) file component being processed exceeds the 44-character maximum for data set names. The IAM file component data set name includes the value assigned to the DSN parameter in the IAM file definition member, plus the data set extent number suffix appended automatically by IOA. IAM file definition statements are usually located in a member of the IOA INSTWORK library.
The program terminates.
Corrective Action: Set the DSN parameter to a value defined by 39 characters or less, and rerun the program.
Explanation: During processing of an IAM file index or data component, an attempt to open and read the IAM file definition statements member failed. IAM file definition statements are usually located in a member of the IOA INSTWORK library.
The program terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: Access was denied by IOA Access Method (IAM) allocation and formatting exit routine IOAX036. An attempt to allocate, format or extend an IAM file component was denied, because exit routine IOAX036 returned a non-zero return code.
The program terminates.
Corrective Action: If the executing program should have been granted access to process the IAM file, contact your system or security administrator for assistance.
Explanation: This information message is the header for IOA Access Method (IAM) file definition statement parameter settings that follow.
Processing continues. IAM file definition statement parameter settings are displayed in message IOAF25I.
Corrective Action: No action is required.
Explanation: This information message displays the setting of an IOA Access Method (IAM) file definition statement parameter.
Corrective Action: No action is required.
Explanation: An internal error occurred while attempting to format an IOA Access Method (IAM) file component. Formatting of an IAM file component could not be completed because an internal error was encountered by an IAM service routine.
The program terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: During formatting of an IOA Access Method Data File type F, the IOADBF utility issues this message when the number of records per block in the IOA Access Method Data File type F exceeds 256.
The IOADBF utility terminates.
Corrective Action: Correct the LRECL and BLKSIZE parameters in the corresponding member in the installation library to provide no more than 256 records per block in IOA Access Method Data File type F. Rerun the IOADBF utility.
Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.
I/O request fails.
Corrective Action: Notify your INCONTROL administrator.
Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.
I/O request fails.
Corrective Action: Notify your INCONTROL administrator.
Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.
I/O request fails.
Corrective Action: Notify your INCONTROL administrator.
Explanation: Function TRKCALC returned a non-zero return code.
The I/O operation fails. Further action depends on the current IOA function.
Corrective Action: Contact BMC Customer Support.
Explanation: An internal error occurred in an IOA Access Method routine while processing an IOA Access Method file.
I/O request fails.
Corrective Action: Notify your INCONTROL administrator.
Explanation: An I/O error occurred while trying to access an IOA Access Method file. This message can be the result of a software or hardware error.
The I/O operation fails. Further action depends on the current IOA function.
Corrective Action: Check if there are any hardware problems with the disk on which the IOA Access Method file resides. If the problem seems to be a software problem, contact BMC Customer Support.
Explanation: This information message indicates that the IOADPT utility started. The IOADPT utility prints IOA Access Method (IAM) file component records in dump format.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOADPT utility ended.
Corrective Action: If the IOADPT utility ended with a non-zero return code, check the system log for additional messages that describe the error. Correct the problem before rerunning the IOADPT utility. If the problem remains unresolved, contact BMC Customer Support.
Explanation: An invalid parameter or sequence of parameters was passed to an IOA Access Method (IAM) print the IOADPT utility.
The IOADPT utility terminates.
Corrective Action: Correct the parameter or parameter sequence. Rerun the utility.
Explanation: The IOADPT utility could not open the SYSOUT file or the data set referenced by the SYSPRINT DD statement, which writes message output during program execution.
The IOADPT utility terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: An IAM service routine encountered an internal error while attempting to access an IOA Access Method (IAM) file component.
The utility terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the utility. If the problem remains unresolved, contact BMC Customer Support.
Explanation: An IAM service routine encountered an internal error while attempting to access an IOA Access Method (IAM) file index component.
The utility terminates.
Corrective Action: Check the system log for additional messages that describe the error. Correct the problem before rerunning the utility. If the problem remains unresolved, contact BMC Customer Support.
Explanation: The FUNC parameter specified in the JCL procedure of the IOADPT utility is invalid.
Valid FUNC values are:
The IOADPT utility terminates.
Corrective Action: Set the FUNC parameter to a valid value, and rerun the utility.
Explanation: An empty parameter string was passed to the IOADPT program.
The IOADPT program terminates.
Corrective Action: Specify needed parameters, and rerun the program. Refer to the INCONTROL for z/OS Utilities Guide for more information.
Explanation: This information message indicates the number of records printed by the IOADPT program.
The IOADPT program terminates.
Corrective Action: No action is required.
Explanation: No record was found in the key range that the customer used.
The IOADPT program continues.
Corrective Action: Validate that the key range (set by parameters KEYFROM and KEYTO in job IOALOGXD in the IOA JCL library) are correct. If not, change them and resubmit the job.
Explanation: Processing of an IOA Access Method (IAM) file component cannot be completed because an internal error was encountered by an IAM service routine. Messages IOAF70I and IOAF71I display information describing the internal error that occurred while attempting to process an IAM file component.
The program terminates. Additional diagnostic messages may precede or follow this message.
Corrective Action: Check the IOA Log or the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: Processing of an IOA Access Method (IAM) file component cannot be completed because an internal error was encountered by an IAM service routine. Messages IOAF70I and IOAF71I display information describing the internal error that occurred while attempting to process an IAM file Component.
The program terminates. Additional diagnostic messages may precede or follow this message.
Corrective Action: Check the IOA Log or the system log for additional messages that describe the error. Correct the problem before rerunning the program. If the problem remains unresolved, contact BMC Customer Support.
Explanation: Mirror database file is not identical to the main database file. If the database files have mirror files, during each database access request, IOA Access Method programs check that the main and mirror files are identical. If they are not, this message is issued, and only the main database file is used.
IOA Access Method uses only the main file.
Corrective Action: Reformat the mirror database file, and copy the main database file into it, using the IOADCPY utility.
Explanation: An attempt to obtain storage for message edit processing failed because not enough memory was available to edit and issue an error message from the IOA Access Method.
Processing continues if the unissued message was for a noncritical event.
Corrective Action: Increase the REGION size. If the problem remains unresolved, contact BMC Customer Support.
Explanation: This information message indicates that XCF communication is supported under this implementation of Control-O. Control-O is joined to the grp XCF group as member mem.
Corrective Action: No action is required.
Explanation: An error was detected while issuing XCF command xcf_cmd. The return code is rc. The reason code is rsn.
Possible values of xcf_cmd and the XCF macro indicated by each:
Return code rc and reason code rsn are documented separately for each XCF macro in the IBM manual MVS Programming: Authorized Assembler Services Guide.
Corrective Action: Fix the problem according to the specific xcf_cmd/XCF MACRO.
Explanation: This information message indicates that Control-O did not initialize the XCF Group User Interface module under the current installation.
Corrective Action: No action is required.
Explanation: During initialization of the modName communication module, storage allocation for the Control-O communication facility failed because the communication component could not obtain sufficient working storage for processing. The return code rc is obtained from register R15 of the STORAGE OBTAIN macro.
XCF communication is not activated. Processing continues.
Corrective Action: Check current memory usage for unknown problems. Based on the return code, fix the problem and restart Control-O to activate XCF support.
Explanation: This information message indicates that the XCF Statistic User Interface module was not activated. During its initialization, Control-O did not initialize the Statistic User Interface.
Corrective Action: No action is required.
Explanation: Control-O attempted to initialize the XCF Message User Interface (MUI) module and failed. In this message, modName is the name of the Message User Interface module that Control-O attempted to initialize.
XCF support is not activated.
Corrective Action: Verify that the modName MUI module is in the STEPLIB. Restart the last XCF operation. If the problem persists, contact BMC Customer Support.
Explanation: This information message indicates that Control-O communication by means of XCF is down. The memName Control-O XCF member from the grp group is down.
Corrective Action: No action is required.
Explanation: During XCF processing, Control-O detected an internal error. The IOAXCF module failed with general return code g_rc, specific return code s_rc, and reason code rsn.
Corrective Action: Restart the last XCF operation. If the problem persists, contact BMC Customer Support.
Explanation: The IOA housekeeping routine found an unexpected error during one of its cycles.
The Control-O or CMEM monitor terminates. Other monitors may behave differently.
Corrective Action: Use earlier messages to determine the cause of the failure.
Explanation: The XES housekeeping routine found an error while it was either processing a request that was queued by an XES exit, or while it was checking an XES control block. The XES housekeeping routine processes requests that are queued by asynchronous execution of XES SRB exits.
The Control-O or CMEM monitor terminates. Other monitors may behave differently.
Corrective Action: Send the sysout files for your monitor to BMC Customer Support.
Explanation: An internal error occurred during internal chaining. An internal chaining mechanism queues requests as they pass from one component to another, for example, from SRB exits from XES to the housekeeping task. This mechanism detected an internal error that may result from a programming error.
The Control-O or CMEM monitor terminates. Other monitors may behave differently.
Corrective Action: Send the SVCDUMP of the address space issuing the message and the sysout files for your monitor to BMC Customer Support for analysis.
Explanation: This information message indicates that Control-O or CMEM started initialization of the subtask that performs XES housekeeping.
Corrective Action: No action is required.
Explanation: The subtask of Control-O or CMEM that performs XES housekeeping found an unexpected error during one of its cycles.
Both the subtask and Control-O or CMEM terminate.
Corrective Action: Use earlier messages to determine the cause of the failure.
Explanation: This information message indicates that Control-O or CMEM finished initializing the subtask that performs XES housekeeping.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOA initialization routine started initializing XES activities, and is currently in control.
Corrective Action: No action is required.
Explanation: This information message indicates that the IOA initialization routine stopped initializing XES activities. It does not indicate whether or not all activities were completed successfully.
The routine that initializes XES activities passes control back to the caller.
Corrective Action: No action is required.
Explanation: The IOA initialization routine for XES activities received an invalid list of parameters from the caller.
The Control-O or CMEM monitor terminates. Other monitors may behave differently.
Corrective Action: Send the sysout files for your monitor to BMC Customer Support for analysis.
Explanation: The IOA initialization routine for XES failed to get enough storage space. The routine could not GETMAIN one of the chunks of storage needed to process the XES request.
The Control-O or CMEM monitor terminates. Other monitors may behave differently.
Corrective Action: Review calculations of storage requirements for Control-O or CMEM (private, E/CSA). If you cannot find the problem, send the sysout files for your monitor to BMC Customer Support for analysis.
Explanation: The IOA initialization routine for XES failed to get enough resources for the XAE (SYSPLEX-wide AutoEdit) facility of Control-O or CMEM. Initialization of the XAE facility requires resources, such as storage, programs and calculations.
The Control-O or CMEM monitor terminates.
Corrective Action: Use earlier messages to determine the cause of the failure.
Explanation: Connection to one of the required XAE structures produced a nonzero return code. A list, a cache, and a lock structure must be allocated for the XAE (SYSPLEX-wide AutoEdit) facility on Coupling facility units. This error indicates that one of these structures could not be allocated or connected.
The Control-O or CMEM monitor terminates.
Corrective Action: Check the following:
Explanation: Disconnection from one of the required XAE structures produced a nonzero return code. A list, a cache, and a lock are allocated for the XAE (SYSPLEX-wide AutoEdit) facility on Coupling facility units. This error indicates that one of these structures could not be released or disconnected.
The Control-O or CMEM monitor continues with its other actions, without performing the action that caused this error.
Corrective Action: Check the messages that precede this error. If you cannot find the problem, send the sysout files for your monitor to BMC Customer Support for analysis.
Explanation: The RESMGR service macro of MVS produced a nonzero return code. XES requires MVS resource managers to protect the system from unexpected EOT or EOM events before disconnection from structures is completed.
The Control-O or CMEM monitor terminates.
Corrective Action: Send the sysout files for your monitor to BMC Customer Support for analysis.
Explanation: Termination of XES facilities produced an error. Some resources, such as programs or memory, could not be released.
Termination of XES facilities stops. The Control-O or CMEM monitor continues with its other actions.
Corrective Action: Send the sysout files for your monitor to BMC Customer Support for analysis.
Explanation: Control-O or CMEM failed to connect to the structure.
Control-O or CMEM fails to start.
Corrective Action: Check the reason in the message to see why the connection failed, and whether this can be solved by changes to the CF or IOA parameters. If not, contact BMC Customer Support for assistance.
Explanation: This information message indicates that Control-O or CMEM failed to connect to the structure because a system-managed process is currently in progress.
Control-O or CMEM waits for a short time and tries to connect again. After 10 retries, Control-O or CMEM ends.
Corrective Action: If Control-O or CMEM ends, and there is a system-managed process in progress, wait until it ends and start Control-O or CMEM. Otherwise, contact BMC Customer Support for assistance.
Explanation: This message indicates that Control-O or CMEM failed to connect to the structure because a system-managed process is currently in progress.
Control-O or CMEM issues message IOAFBCW and waits until the structure becomes available, or the operator responds to message IOAFBCW.
Corrective Action: See message IOAFBCW.
Explanation: This message follows message IOAFBBW and lets the operator decide whether to let Control-O or CMEM wait until the structure is available, or cancel Control-O or CMEM and start it later.
If the operator replies CANCEL, Control-O or CMEM will terminate. Otherwise, Control-O or CMEM waits for the structure to become available, connects to the structure and continues the initialization process.
Corrective Action: Check the status of Control-O or CMEM structures and the status of the coupling facility to determine the reason why the connection was prevented. Decide whether to reply CANCEL, or let Control-O or CMEM wait until the structure is available.
Explanation: The ENFREQ LISTEN or DELETE request for event 35 failed. If LISTEN failed, Control-O or CMEM will not be able to wait after connection to a structure is prevented, to be notified when the structure becomes available for connection.
For the LISTEN request, if connection to the XAE structures is allowed, Control-O or CMEM will work normally. If connection to the XAE structures is prevented, Control-O or CMEM will not wait to be notified when the structure is available, but will fail. For the DELETE request, Control-O or CMEM will continue to work normally.
Corrective Action: Contact BMC Customer Support for assistance.
Explanation: This information message indicates that a system-managed rebuild started for the structureName structure. Requests issued for this structure will be deferred until the system-managed rebuild ends, and the structure becomes available again. This will cause delays in accesses to IOA Global variables.
Corrective Action: No action is required.
Explanation: This information message indicates that the structureName structure created by the system-managed rebuild was allocated on the cfname coupling facility.
Corrective Action: No action is required.
Explanation: This information message indicates that the system-managed rebuild or duplex rebuild finished processing the structure, and it is available again. Requests to the structure will be processed by XES.
Corrective Action: If this message is preceded by message IOAF2EI or IOAFE5I, the system-managed process ended successfully. Otherwise, the system-managed process was stopped or failed. See the system log (syslog) for details about the system-managed process.
Explanation: This information message indicates that the system-managed duplex rebuild started for this structure. Requests issued for this structure will be deferred until the system-managed duplex rebuild ends and the structure becomes available again. This will cause delays in accesses to IOA Global variables.
Corrective Action: No action is required.
Explanation: This information message provides information about the structure mode. The message is issued when:
Corrective Action: No action is required.
Explanation: System-managed duplexing was stopped for this structure. There are several instances when structure duplexing is stopped:
Corrective Action: If duplexing is required for this structure, check the system log for messages explaining why duplexing was stopped, and act accordingly.
Explanation: The structureName structure is unavailable, but the reason is unknown. Requests for this structure will not be honored by XES until the structure becomes available again.
Corrective Action: Contact BMC Customer Support for assistance.
Explanation: Control-O or CMEM failed to respond to an XES event.
Detailed information is written to DATRACE.
Corrective Action: If the error causes problems in the interface to XES, restart Control-O or CMEM. Contact BMC Customer Support for assistance.
Parent Topic |