DFS0548E ERROR BUILDING RESOUCE CLEANUP ENVIRONMENT, RC=rc - details
Explanation
An error occurred while IMS was establishing its resource cleanup and online dump formatting environment during IMS initialization.
- rc
- The return code from the failing service.
- details
- A one-line explanation of the type of error that was detected.
The details portion of the DFS0458E message further explains the error detected and can be one of the following values:
- ERROR OBTAINING GRMB STORAGE
- IMS could not obtain storage required for a GRMB (Global Resource Manager Block). rc in the message is the return code from the z/OS® STORAGE OBTAIN macro.
- ERROR OBTAINING XSSCT STORAGE
- IMS could not obtain storage required for an XSSCT (IMS 31 bit extended SSCT). rc in the message is the return code from the z/OS STORAGE OBTAIN macro.
- ERROR OBTAINING DFSMRC20 STORAGE
- IMS could not obtain storage to direct load module DFSMRC20. rc in the message is the return code from the z/OS STORAGE OBTAIN macro.
- BPESVC FUNC=INIT ERROR
- An error occurred during BPESVC FUNC=INIT processing. rc in the message is the return code from the BPESVC macro.
- ERROR ISSUING BLDL FOR DFSMRC20
- An error occurred issuing a BLDL macro call for module DFSMRC20. rc in the message is the return code from the z/OS BLDL macro.
- ERROR LOADING DFSMRC20
- IMS could not load module DFSMRC20. rc in the message is the return code from the z/OS LOAD macro.
- ERROR LOADING DFSRTM00
- IMS could not load module DFSRTM00. rc in the message is the return code from the z/OS LOAD macro.
- ERROR ADDING ADDRSPC RESMGR
- IMS could not dynamically add an address space resource manager to the system. rc in the message is the return code from the z/OS RESMGR macro.
- ERROR ADDING TASK RESMGR
- IMS could not dynamically add a task resource manager to the system. rc in the message is the return code from the z/OS RESMGR macro.
- AN ABEND OCCURRED
- An abend occurred during the building of the IMS resource cleanup environment. rc in the message is the abend code.
- UNABLE TO ESTABLISH ESTAE
- IMS was unable to establish an ESTAE recovery routine to protect the resource cleanup environment initialization. rc in the message is the return code from the z/OS ESTAEX macro.
- ENQ FAILED ON SYSZDFS DFSGRMB
- IMS was unable to obtain
an exclusive ENQ on the resource
SYSZDFS DFSGRMB
. rc in the message is the return code from the z/OS ENQ macro. - ERROR OBTAINING DFSMRC00 STORAGE
- IMS could not obtain storage to direct load module DFSMRC00. rc in the message is the return code from the z/OS STORAGE OBTAIN macro.
- ERROR ISSUING BLDL FOR DFSMRC00
- An error occurred issuing a BLDL macro call for module DFSMRC00. rc in the message is the return code from the z/OS BLDL macro.
- ERROR LOADING DFSMRC00
- IMS could not load module DFSMRC00. rc in the message is the return code from the z/OS LOAD macro.
- UNKNOWN ERROR
- An unexpected error occurred during the IMS resource manager cleanup initialization.
- ERROR OBTAINING DFSAFMX0 STORAGE
- IMS could not obtain storage to direct load module DFSAFMX0. rc in the message is the return code from the z/OS STORAGE OBTAIN macro. IMS initialization continues; however, online dump formatting for IMS is unavailable.
- ERROR ISSUING BLDL FOR DFSAFMX0
- An error occurred issuing a BLDL macro call for module DFSAFMX0. rc in the message is the return code from the z/OS BLDL macro. IMS initialization continues; however, online dump formatting for IMS is unavailable.
- ERROR LOADING DFSAFMX0
- IMS could not load module DFSAFMX0. rc in the message is the return code from the z/OS LOAD macro. IMS initialization continues; however, online dump formatting for IMS is unavailable.
- DFSAFMX0 IEFSSI ADD FAILED
- IMS was unable to add a subsystem dynamically to z/OS to enable IMS to perform dump formatting for SNAP, SYSABEND, and SYSUDUMP dumps. The top 2 bytes of rc in the message is the return code from the z/OS IEFSSI REQUEST=ADD macro. The bottom 2 bytes of rc in the message is the reason code from IEFSSI. IMS initialization continues; however, online dump formatting for IMS is unavailable.
- DFSAFMX0 IEFSSI ACTIVATE FAILED
- IMS was unable to dynamically activate a subsystem to z/OS to enable IMS to perform dump formatting for SNAP, SYSABEND, and SYSUDUMP dumps. The top 2 bytes of rc in the message is the return code from the z/OS IEFSSI REQUEST=ACTIVATE macro. The bottom 2 bytes of rc in the message is the reason code from IEFSSI. IMS initialization continues; however, online dump formatting for IMS is unavailable.
- DFSAFMX0 IEFSSVT CREATE FAILED
- IMS was unable to create a subsystem vector table for the IMS-added subsystem to enable IMS to perform dump formatting for SNAP, SYSABEND, and SYSUDUMP dumps. The top 2 bytes of rc in the message is the return code from the z/OS IEFSSVT REQUEST=CREATE macro. The bottom 2 bytes of rc in the message is the reason code from IEFSSVT. IMS initialization continues; however, online dump formatting for IMS is unavailable.
- DFSAFMX0 IEFSSVT EXCHANGE FAILED
- IMS was unable to update the DFSAFMX0 subsystem vector table entry to point to a copy of DFSAFMX0 more recent than the copy that had been previously installed. The top 2 bytes of rc in the message is the return code from the z/OS IEFSSVT REQUEST=EXCHANGE macro. The bottom 2 bytes of rc in the message is the reason code from IEFSSVT. IMS initialization continues. The previously installed copy of DFSAFMX0 is used as the IMS online dump formatting exit.
System action
For errors during the initialization of the online dump formatter exit DFSAFMX0, the module detecting the error, DFSRTMI0, returns a zero return code to its caller. IMS continues execution; however, IMS online dump formatting might not be available for this instance of IMS.
For all other errors, the module detecting the error, DFSRTMI0, returns a non-zero return code to its caller.
System programmer response
If the error described in this message is caused by environmental conditions (for example, insufficient storage or modules missing from IMS.SDFSRESL), correct the indicated problem and restart the address space. Otherwise, save any dump and SYSLOG information, and contact IBM® Software Support.