I generated and ran the Post-Install IDB2SYS job for Sysview PMO for DB2 for z/OS. The job ran successfully. I then continued with the Post-Install
configuration for Sysview PMO for DB2 for z/OS, and went into option 3 (DB2 Catalog Customization Tasks), and tried to generate the ssid0525 job.
The creation of this job failed with the messages:
THE INITIAL PART OF THE CA SYSVIEW FOR DB2 POST INSTALL "EXECUTE PRODUCT SPECIFIC CUSTOMIZATION TASKS" FROM THE DB2
TOOLS INSTALLATION MAIN MENU HAS NOT BEEN COMPLETED SUCCESSFULLY. ONE OR MORE OF THE FOLLOWING INSTALL DATASETS
ARE MISSING OR ARE NOT AT THE CORRECT LEVEL: INST LEVEL: '190' CUR LEVEL: '190' SOURCE: 'IRM.SYS.CYC1705.I2R14.SOURCE' DATASET
NOT FOUND SECURITY: 'IRM.SYS.CYC1705.I2R14.SECURITY' DATASET NOT FOUND TGTREQ: 'IRM.SYS.CYC1705.I2R1405.CDBATREQ' OK
YOU MUST PERFORM THE PRODUCT SPECIFIC CUSTOMIZATION TASK FOR CA SYSVIEW FOR DB2 BEFORE YOU CAN PERFORM THE "EXECUTE
DB2 TASKS" FOR CA SYSVIEW FOR DB2. REFER TO THE INSTALLATION GUIDE FOR MORE INFORMATION.
The cause of this condition was due to the manual editing of the IDB2SYS job, and modifying the IDB2 dataset names to reflect the correct highlevel name.
The need for this editing was due to the fact that the IDB2SYS panel limited the requested highlevel name for the IDB2 Non-VSAM and VSAM datasets to
21 bytes. Instead of 'IRM.SYS.CYC1705.I2R1405' the highlevel was truncated to 'IRM.SYS.CYC1705.I2R14'. This truncated highlevel was then stored in
the parmlib (.CDBAPARM) IDB2VARS member. The subsequent ssid0525 Post-Install job reads the IDB2VARS member, thus looking for datasets with the
'IRM.SYS.CYC1705.I2R14' highlevel, and could not find them for they had been manually renamed to the 'IRM.SYS.CYC1705.I2R1405' highlevel.
The simple resolution was to ensure the parmlib IDB2VARS member reflected the same highlevel for the IDBSHLQ and IDBVHLQ variables as what was
created in the IDB2SYS job or after the manual renaming of them: IRM.SYS.CYC1705.I2R14 was changed to IRM.SYS.CYC1705.I2R1405.
Performing this edit in the IDB2VARS parmlib member allowed the ssid0525 job to be generated and to run successfully.
The dictate of only allowing 21 bytes for the Non-VSAM and VSAM dataset highlevels in the IDB2SYS Post-Install panel is due to the GDG datsets (used for
archiving) having a 35 character limitation (HLQ.SSID.COPYDDnn).