Messages BBMZA200 through BBMZA299
This topic contains messages for the BMC AMI Ops Infrastructure product.
Number | Description |
|---|---|
BBMZA220 | Unable to Obtain Dataset Information for DD ddname Explanation: During CAS startup, the names of certain DDs from the CAS startup PROC statement are recorded in the RTCS registry. If a DD is not part of the startup PROC statement, this message is issued. User response: No action is required. |
BBMZA221 | Failure During Retrieval of Dataset Information Explanation: During CAS startup, the names of certain DDs from the CAS startup PROC statement are recorded in the RTCS registry. An internal logic error occurred during this process. User response: Contact BMC Support. |
BBMZA222 | IWM4EDEL failed, Rc=rc, Rsn=rsn Explanation: The IWM4EDEL macro failed. Processing continues. User response: Set a SLIP with MSGID=BBMZA222,SDATA=(RGN,CSA,TRT). If the problem occurs again on restart, contact BMC Support and provide the dump. |
BBMZA223 | BBMLIB failed: Unable to locate BBACTDEF Explanation: The BBACTDEF DD statement could not be found in the CAS. Processing continues without the BBMLIB DD. The HELPMSG command cannot provide message help without BBMLIB. User response: Make sure that the CAS has a BBACTDEF DD statement. Collect the complete joblog of the CAS and contact BMC Support for further assistance. |
BBM0ZA24 | BBMLIB failed: BBACTDEF JFCB access fail Explanation: The dynamic allocation of the BBMLIB DD in the CAS could not be completed because of the BBACTDEF JFCB access failure. Processing continues without the BBMLIB DD. The HELPMSG command cannot provide help message without the BBMLIB DD. User response: Make sure that the CAS has a BBACTDEF DD statement. Collect the complete joblog of CAS and contact BMC Support for further assistance. |
BBM0ZA25 | BBMLIB failed: DSN transformation fail Explanation: The dynamic allocation of the BBMLIB DD in the CAS could not be completed because of failure in transforming the BBACTDEF LLQ to BBMLIB LLQ. Processing continues without the BBMLIB DD. The HELPMSG command cannot provide help message without BBMLIB. User response: The BBACTDEF low-level qualifier is a non-standard name. Use the SETMSH view to define the non-standard name that contains the BBMLIB information. |
BBM0ZA26 | BBMLIB failed: Unable to allocate BBMLIB DSN RC=xxxx, ERR=xxxx, INF=xxxx, EIN=xxxx, EER=xxxx, ERS=xxxx Explanation: The dynamic allocation of the BBMLIB DD in the CAS has failed. Processing continues without the BBMLIB DD. The HELPMSG command cannot provide help message without BBMLIB. If you are using a 3270 user interface, you can use the MSG command instead of HELPMSG until the problem can be resolved. User response: The probable cause is that the data set name for the BBACTDEF DD in the CAS JCL is not in the standard format. The SVC 99 diagnostic information is displayed with the message. For further assistance, contact BMC Support with complete joblog of CAS and SVC 99 diagnostic information. |
BBM0ZA27 | BBMLIB allocation using OSZDYALN failed Explanation: The dynamic allocation of the BBMLIB DD in the CAS has failed. Processing continues without the BBMLIB DD. The HELPMSG command cannot provide message help without the BBMLIB DD. If you are using a 3270 user interface, use the MSG command instead of HELPMSG until the problem can be resolved. User response: Collect the complete joblog of the CAS and contact BMC Support for further assistance. |
BBM0ZA28 | BBMLIB datasets from SETHELP view used for allocation Explanation: The BBMLIB DD is not present in the CAS JCL. However, BBMLIB data sets are defined in the SETHELP view. Therefore, the data sets from the SETHELP view are used for allocating BBMLIB DD in the CAS. Data sets defined in the SETHELP view are used for the BBMLIB DD allocation in the CAS. User response: No action is required. |
BBM0ZA29 | BBMLIB DD re-allocated using datasets defined in SETHELP view Explanation: The user has updated the BBMLIB data sets using the SETHELP view. Therefore the BBMLIB DD is dynamically re-allocated using the data sets defined in the SETHELP view. The BBMLIB DD in the CAS is re-allocated using the data sets defined in the SETHELP view. User response: No action is required. |
BBMZA230 | Datasets defined in BBMLIB DD in CAS JCL used for allocation Explanation: The BBMLIB DD is present in the CAS JCL. However, no data sets are defined in the SETHELP view. The BBMLIB DD in the CAS is allocated using data sets defined in the BBMLIB DD in the CAS JCL. User response: No action is required. |
BBMZA231 | Despite BBMLIB is defined in SETHELP, BBMLIB datasets from CAS JCL are used for allocating BBMLIB DD in CAS. Explanation: The BBMLIB DD in the CAS JCL is given preference to the SETHELP BBMLIB definition. The data sets defined in the BBMLIB DD in the CAS JCL are used for allocating the BBMLIB DD. User response: To use the data sets from the SETHELP view for allocating the BBMLIB DD, delete BBMLIB DD from the CAS JCL. |
BBMZA232 | Bufferlength (x) is less than RTCS structurelength (x) Explanation: The input buffer length is less than the structure length fetched from the RTCS registry. The structure fetched from the RTCS registry was not copied to the buffer, therefore it is not available in the calling program. User response: Collect the complete CAS joblog and contact BMC Support for further assistance. |
BBMZA233 | Structure structureName not found at RTCS Registry path Registry_key/subkey. Explanation: The structure name does not exist in the RTCS registry path. User response: No action is required. |
BBMZA234 | Failed to retrieve structure structureName from RTCS Registry path Registry_key/subkey. RC=returnCode. Explanation: An error encountered while accessing the RTCS registry. User response: Determine why the RTCS registry is not available. When the registry is available, restart the CAS. If the problem persists, contact BMC Support with the complete joblog of the CAS and any other diagnostic information. |