Assembly of DBSYSID has CC 1
Article ID: 107835
Updated On:
Products
Datacom
DATACOM - AD
CIS
COMMON SERVICES FOR Z/OS
90S SERVICES
DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS
COMMON PRODUCT SERVICES COMPONENT
Common Services
CA ECOMETER SERVER COMPONENT FOC
Easytrieve Report Generator for Common Services
INFOCAI MAINTENANCE
IPC
UNICENTER JCLCHECK COMMON COMPONENT
Mainframe VM Product Manager
CHORUS SOFTWARE MANAGER
CA ON DEMAND PORTAL
CA Service Desk Manager - Unified Self Service
PAM CLIENT FOR LINUX ON MAINFRAME
MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME
GRAPHICAL MANAGEMENT INTERFACE
WEB ADMINISTRATOR FOR TOP SECRET
Xpertware
Issue/Introduction
As part of the CA Datacom/AD and CA Datacom/DB installation and configuration for each MUF, there are jobs to run to assemble the DBSYSID macro, resulting in the DBSIDPR load module (object). For CA Datacom/AD, the jobs are AXCUS01 (version 14.0), AXACTUPG and AXCUSNEW (version 15.0). For CA Datacom/DB, the jobs are BDCUSNEW and BDCUSUPG (version 14.0 and 15.0), and BDCUSNEW, BDCUSUP1, and BDCUSU15 (version 15.1).
After running my customization job, the assembly of the DBSYSID macro produced a CC 1 in ASMSTP, and the LNKSTP completed with a CC 0. Is there a problem with the assembly?
After running my customization job, the assembly of the DBSYSID macro produced a CC 1 in ASMSTP, and the LNKSTP completed with a CC 0. Is there a problem with the assembly?
Environment
Release: DATABB00200-14.0-Datacom/AD
Component:
Component:
Resolution
There is no problem here. The CC 1 is the result of using an 8-character MUF/CXX name.
In the CA Datacom/DB administration documentation, the section Modifying DBSIDPR Parameters entry for CXXNAME says:
This is what the installation documentation for CA Datacom/AD says about this:
The ASMSTP in this job should also have produced an MNOTE message:
CXXNAME=cxxname IS OK BUT BEST PRACTICE IS 7 MAX
As a result, if there were no other errors, the configuration process can continue with the next step.
In the CA Datacom/DB administration documentation, the section Modifying DBSIDPR Parameters entry for CXXNAME says:
If specified it must be 1-8 positions long, but if 8 a MNOTE 1 warning occurs noting that a best practice is to have the name only 1-7 positions. 1-7 positions allow the same name to be used for the MUF name optionally suffixed by a number or letter. The keyword is required when using the Simplify option (SIMPLIFY_MODE=NO not specified), and in this case the name must match the name in the CXX being used to provide security and protection of this particular environment.
This is what the installation documentation for CA Datacom/AD says about this:
Choosing to use a full 8-byte name at this time causes the customization member AXCUSNEW to receive a condition code 1. The only way to rectify a condition code 1 is to follow the best practices by using a 1 to 7 byte name. Using the 1 to 7 byte name allows member AXCUSNEW to end with condition code zero.
The ASMSTP in this job should also have produced an MNOTE message:
CXXNAME=cxxname IS OK BUT BEST PRACTICE IS 7 MAX
As a result, if there were no other errors, the configuration process can continue with the next step.
Additional Information
As always, please contact CA Technologies support for CA Datacom if you have further questions.
Feedback
Yes
No
Powered by
