How can I run DBUTLTY REPORT MEMORY=MVS before customizations jobs are run?

book

Article ID: 5429

calendar_today

Updated On:

Products

CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware

Issue/Introduction

When starting the configuration for CA Datacom/DB version 14.0, Customization Step1 says to run a memory report after the PC modules have been loaded by the BDRIM01 job. However, running with only the CABDLOAD results in an abend (S806) because the DBSIDPR module is not found, and running with a previous version (version 12.0) does not show anything about these modules.

Cause

There was an error in the manuals, and this DBUTLTY job cannot be run until after the BDCUSNEW or BDCUSUPG job has been run to create the new version 14.0 CUSLIB.

Environment

Release:
Component: DB

Resolution

If there is a desire or need to verify that the PC modules have been loaded correctly into the environment, wait until Configuration Step 1 is complete, and the BDCUSNEW or BDCUSUPG job has been run. At this point, you will have a CUSLIB and DBSIDPR module available and the report will work as expected.

Additional Information

As always, please contact CA Technologies support for CA Datacom if you have further questions.

***