When issuing DBRC commands in an IMS Managed ACB environment, there are times when you’d want to access the staging directory instead of the active directory. For example, you need to add a new database definition (DBD) or make changes to an existing database definition, but you don’t want to IMPORT these changes to the active directory for general use until you can test it first.
With APAR PH17441, PTF UI69829, for the following DBRC commands, you can now specify that either the staging directory or the active directory be used for data base definitions:
When using these command, one can specify either STAGING keyword to access the staging directory or ACTIVE keyword to access the active directory.
The two new keywords, STAGING and ACTIVE, are mutually exclusive and optional. You choose which catalog directory should be used, STAGING or ACTIVE. If you do not specify which one is to be used, ACTIVE is the default.
To improve serviceability with this enhancement, we’re adding a new message, DSP1279I, and modifying an existing message, DSP0141I.
The new message DSP1279I indicates whether the ACTIVE or STAGING directory is in use when a Catalog API error is encountered. The API function, as well as its return code and reason code, is displayed. Here is the message format:
funcidentifies the function being processed by the IMS Catalog API.
statusindicates whether the ACTIVE or STAGING directory was being used by this operation.
rsncodeindicate the return and reason codes from the IMS Catalog API.
If this message is issued, processing is terminated. What’s your next step? Check for prior error messages, which may be issued to help diagnose the problem. In addition, the return and reason codes of the identified IMS Catalog API (DFS3CATQ) can be checked for more information. As always, if you need more help, you can contact IMS support.
Existing message DSP0141I is now also issued if the DBRC command specifies the STAGING or ACTIVE keyword, but the job is using DBDLIB. The STAGING or ACTIVE keywords are only applicable when you are using the IMS directory, not when you are using the DBDLIB. Here is the format of the DSP0141I message:
DSP0141I parameter PARAMETER SHOULD NOT BE SPECIFIED
You can now rest easy knowing that your database definition changes are safe to IMPORT to your active directory because you are able to verify them using the staging directory.
For more information, be sure to check out the Knowledge Center. Also, don’t forget to check out our IMS Community page as well as subscribe to the eNews for the latest updates from the IMS team, such as this blog!