After executing the Post Install IDB2SYS job why is the Post Install ssid0525 job stating that the IDB2SYS job has not been run due to missing datasets

Products

• SYSVIEW Performance Management Option for DB2 for z/OS

Issue/Introduction

Generated and ran the Post Install IDB2SYS job for Sysview Performance Management Option for Db2 for z/OS (IDB2).
The job ran successfully.  Then continued with the Post Install configuration for IDB2 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: 'hlq.SOURCE' DATASET
NOT FOUND SECURITY: 'hlq.SECURITY' DATASET NOT FOUND TGTREQ: 'hlq.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. 

Cause

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 'xxx.xxx.xxxxxxx.xxxxxxx' the highlevel was truncated to 'xxx.xxx.xxxxxxx.xxxxx'.  This truncated highlevel was then stored in 
the parmlib (hlq.CDBAPARM) IDB2VARS member.  The subsequent ssid0525 Post Install job reads the IDB2VARS member, thus looking for datasets with the
'xxx.xxx.xxxxxxx.xxxxx' highlevel, and could not find them for they had been manually renamed to the 'xxx.xxx.xxxxxxx.xxxxxxx' highlevel.

Resolution

The simple resolution was to ensure the CDBAPARM IDB2VARS member reflected the same highlevel for the IDBSHLQ and IDBVHLQ variables as what was
created in the IDB2SYS job.

Additional Information

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 datasets (used for archiving) having a 35 character limitation (hlq.ssid.COPYDDnn).