IAM/RLS, IAM/PLEX, and IAMLOGVR Messages
The following informational and error messages may occur during IAM/RLS or IAM/PLEX processing. They will generally appear on the RLSLOGDD, and some critical error message will appear on the consoles and system logs. For most of the information provided on the messages, the use of IAMRLS or IAM/RLS generally can also occur for IAM/PLEX address spaces. Several of the messages are for diagnostic purposes that will contain information useful only to BMC technical support personnel.
Number | Description |
|---|---|
IAML0001 | LOGGING OF MESSAGES DISABLED Explanation: IAMRLS was unable to obtain storage for the message table used by IAMLOGER and has disabled logging of messages to RLSLOGDD. System Action: Increase the REGION size of the IAMRLS address space. |
IAML0002 | GLOBAL NAME TOKEN AREA RETRIEVED Explanation: IAMRLS was able to retrieve and reuse the Global Token area left from a previous iteration of the IAMRLS address space. System Action: None |
IAML0003 | UNABLE TO START VIF Explanation: IAMRLS received a non-zero return code from IAMSTART while attempting to start VIF. System Action: Check for other messages issued by IAMSTART to the SYSLOG which will provide further information as to the reason VIF could not start. |
IAML0004 | GETMAIN OR LOCK OBTAIN FAILURE Explanation: IAMRLS could not obtain the local lock needed for a CSA getmain, or there was not enough CSA available to satisfy the CSA getmain request. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0005 | GLOBAL NAME TOKEN AREA CREATE FAILED Explanation: IAMRLS was unable to create a Global Token area. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0006 | DATASPACE BUILD FAILED Explanation: IAMRLS was unable to create a data space. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0007 | SYSEVENT FAILED Explanation: The SYSEVENT macro issued to make the IAMRLS address space non-swappable failed. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0008 | LOAD OF SERVICE MODULE FAILED Explanation: IAMRLS was unable to load one of its service modules. System Action: Make sure you have an IAM load library that has all of the modules distributed on the IAM distribution tape included in either the LINKLIST or a JOBLIB/STEPLIB. |
IAML0009 | LOCAL NAME TOKEN AREA CREATE FAILED Explanation: IAMRLS was unable to create the Local Name Token area. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0010 | GETMAIN OF CELL POOL STORAGE FAILED Explanation: IAMRLS was unable to acquire storage for the cell pools set up during initialization. System Action: Raise the region size for the IAMRLS address space. |
IAML0011 | TASK WORK AREA GETMAIN FAILED Explanation: The getmain for the TASK work area storage failed. System Action: Raise the region size for the IAMRLS address space. |
IAML0012 | ATTACH PROCESSOR FAILED, CANNOT CONTINUE Explanation: IAMRLS was unable to attach one of its subtasks. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0013 | GLOBAL NAME TOKEN AREA DELETED Explanation: IAMRLS deleted the Global Token Area during shutdown. System Action: None. |
IAML0014 | OPEN/CLOSE TASK ATTACHED Explanation: IAMRLS attached the OPEN/CLOSE subtask. System Action: None. |
IAML0015 | LOGGING TASK ATTACHED Explanation: IAMRLS attached the LOGGING subtask. System Action: None. |
IAML0016 | WORKLOAD MANAGER ATTACHED Explanation: IAMRLS attached the WORLOAD MANAGER subtask. System Action: None. |
IAML0017 | JOURNAL TASK ATTACHED Explanation: IAMRLS attached the JOURNAL subtask. System Action: None. |
IAML0018 | TRACE TASK ATTACHED Explanation: IAMRLS attached the TRACE subtask. System Action: None. |
IAML0019 | IAMRLS ESTAE ENTERED FOR ABEND SxxX Explanation: The ESTAE for module IAMRLS was entered for an abend condition. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0020 | PRELOAD OF PROCESSING MODULE FAILED Explanation: IAMRLS was unable to preload some of the processing modules. System Action: Check the IAM load library to make sure it contains all of the modules distributed with the IAM product. |
IAML0021 | ADDRESS SPACE ALREADY ACTIVE Explanation: IAMRLS detected an address space running under the same name. System Action: None. |
IAML0022 | IAMBREST SUBTASK ATTACHED Explanation: IAMRLS attached the DYNAMIC BACKOUT subtask. System Action: None. |
IAML0023 | IAMBWJRN SUBTASK ATTACHED Explanation: IAMRLS attached the Journal Buffer Flush subtask. System Action: None. |
IAML0024 | cccccccc SUBTASK ATTACHED Explanation: The subtask named cccccccc in the message was attached during startup. System Action: None. |
IAML0025 | BASE NAME TOKEN AREA CREATE FAILEDExplanation: IAMRLS was unable to create a Global Token area to be used as an anchor for the Multiple IAMRLS address space support. System Action: Contact BMC for help in diagnosing the cause of this problem. |
IAML0026 | IAMRLS ACTIVE WITH RLSID= nnnn Explanation: IAMRLS address space is active, with the indicated RLSID. System Action: None. |
IAML0027 | RLSID OF TEST IS INVALID, CANNOT CONTINUE Explanation: Specification of an RLSID value of TEST is not permitted on the start up of IAM/RLS or IAM/PLEX. An RLSID of TEST is automatically assigned when an IAM/RLS address space is started with a PARM=TEST on the start command or on the EXEC card in the proc. System Action: Change the value of the RLSID parameter in the startup parameters for the IAM/RLS or IAM/PLEX proc to something other than TEST. If you desire to start a TEST IAM/RLS address space with an RLISID of TEST, then start it with PARM=TEST. |
IAML0028 | IAMRLS ACTIVE WITH RLSID=rlsid IS A REMOTE RLS ONLY Explanation: Indicates that the IAM/PLEX address space was started with the REMOTERLS parameter. This IAM/PLEX address space can only handle file I/O operations, it cannot be directly connected to users of the IAM/PLEX facilities. This is used when multiple IAM/PLEX address spaces in the same RLSGROUP are active on the same LPAR. System Action: None. This is an informational message only. |
IAML0029 | BRLOK INITIALIZATION FAILED, CANNOT CONTINUE Explanation: Indicates that the IAM Record Lock Manager initialization has failed. There should be additional messages indicating the exact cause of this failure. System Action: Review the other messages and correct the error condition, then restart the IAM/RLS or IAM/PLEX address space. For assistance, contact BMC support. |
IAML0030 | RESOURCE MANAGER ADD FAILED, IAMRESMG NOT ACTIVE AS IAMRLS RESOURCE MANAGER Explanation: Unable to activate IAMRESMG as the IAMRLS resource manager System Action: IAMRLS will be unable to cleanup resources for failing jobs or address spaces. Contact BMC for support. |
IAML0031 | IAMRESMG NOW ACTIVE AS IAMRLS RESOURCE MANAGER Explanation: IAMRESMG has been activated as the IAMERLS resource manager. System Action: None. |
IAML0032 | DELETING IAMRESMG AS RESOURCE MANAGER Explanation: IAMRESMG is being deleted as the IAMRLS resource manager. System Action: None. |
IAML0033 | IAMRESMG DELETING AS RESOURCE MANAGER. Explanation: IAMRESMG has been deleted as the IAMRLS resource manager. System Action: None. |
IAML0035 | CHANGEDSNT REQUEST SENT TO REMOTE RLSID=rlsid Explanation: A CHANGEDSNT operator command issue to an IAM/PLEX address space on one LPAR is propagated to other IAM/PLEX address spaces running on other LPARs that belong to the same RLSGROUP. System Action: None. This is an informational message only. |
IAML0036 | CHANGEDSNT REQUEST REJECTED FOR RLSID=rlsid Explanation: In response to a CHANGEDSNT operator command, this IAM/PLEX address space attempted to send the request to the IAM/PLEX address space with the indicated RLSID. XCF rejected the send request with a non-zero return code. System Action: If the IAM/PLEX address space indicated by the RLSID is either not active or having some type of problem then take appropriate action to correct that error condition. If the IAM/PLEX address space indicated appears to be functioning normally, Contact BMC support. |
IAML0037 | REMOTE CHANGEDSNT REQUEST PROCESSED Explanation: The IAM/PLEX address space issuing this message has received and processed a CHANGEDSNT command that was sent from another IAM/PLEX address space. System Action: None. This is an informational message only. |
IAML0038 | VIFKEY MISMATCH FOR MODULE nnnnnnnn Explanation: The IAMRLS module detected a mismatch in the VIFKEY for one of it's processing modules. All of the modules loaded by IAMRLS have to be at the same release level, initialization of the IAMRLS address space ends. System Action: Ensure all of the modules in the IAM load library are at the same level and then try again. |
IAML0047 | GLOBAL TOKEN AREA NOT FOUND FOR THE RLSID PROVIDED Explanation: The IAMRLSX program was executed to delete the Global Token Area from CSA storage, but the Global Token area for the specified IAM RLS address space did not exist. System Action: None. This is an informational message only. |
IAML0048 | RLSID MUST BE PROVIDED TO DELETE THE GLOBAL TOKEN AREA Explanation: The IAMRLSX program was executed to delete the Global Token Area from CSA storage, but the user did not provide the RLSID of the Global Token Area to be deleted. System Action: Add the required RLSID parameter and rerun. |
IAML0049 | ADDRESS SPACE STILL ACTIVE, ISSUE STOP, QUIESCE, OR QUIESCE FORCE TO DEACTIVATE. Explanation: The IAMRLSX program was executed to delete the Global Token Area from CSA storage, but a flag was set in the token area indicating that IAMRLS was still active. System Action: This program should not be run until the IAMRLS address space has been deactivated. Quiesce IAMRLS and run this program again. |
IAML0050 | GLOBAL NAME TOKEN AREA DELETED Explanation: IAMRLSX successfully deleted the Global Token Area from CSA storage. System Action: None. This is an informational message only. |
For more information about this topic, read IAML0051-IAML0075-IAMOPCOM-MESSAGES