Database Management Solutions post-install ssid0002 bind job fails with 'DATASET NOT FOUND' error
Article ID: 447398
Updated On:
Products
Issue/Introduction
While performing the post-installation tasks for Database Management Solutions for Db2 for z/OS, the ssid0002 (Bind Product Plans and Packages) job fails with a DATASET NOT FOUND error.
The error typically occurs during dataset allocation for specific libraries that may no longer exist in the environment or were incorrectly referenced during JCL generation.
Cause
The ssid0002 job obtains its ISPF library allocations (ISPLLIB, ISPMLIB, ISPPLIB, ISPSLIB, ISPTLIB) from an ISPFxx parmlib member located in the hlq.CDBAPARM library.
If this member (e.g., ISPF00 or ISPFLL) contains references to legacy, deleted, or incorrect datasets, the generated ssid0002 JCL will attempt to allocate these non-existent files, leading to the failure.
Resolution
To resolve this issue, identify and clean up any invalid allocations within your ISPFxx parmlib member and then regenerate the bind JCL.
Step 1: Identify the ISPFxx Member in Use
- Access the INSMAIN (post-install) dialog.
- Determine which ISPF suffix is being utilized (e.g., 00, LL). This corresponds to the ISPFxx member within the hlq.CDBAPARM dataset.
Step 2: Clean Up the ISPFxx Member
Review the dataset allocations within the ISPFxx member:
- Ensure that no Broadcom product libraries or personal TSO user datasets are referenced within the ISPFxx member.
- If the ISPFxx member if populated automatically, there may be data set contention with active TSO users when you submit customization JCL generated by post-install processing.
To prevent contention errors with active TSO users, delete all user data sets and Broadcom product libraries from the ISPFxx global parmlib member.
Step 3: Recreate the ISPF Global Parmlib Member
It is highly recommended to use the Create an ISPF Global Parmlib Member procedure within the INSMAIN dialog to recreate a clean member:
- Select the option to create/update the ISPF parmlib member.
- Ensure it only picks up the necessary system allocations and valid Broadcom product libraries.
Step 4: Regenerate and Run SSID0002
- Regenerate the ssid0002 Bind JCL using the updated ISPFxx member.
- Verify the JCL to ensure the DATASET NOT FOUND libraries are no longer present in the DD concatenations.
- Execute the job. A successful execution typically ends with a maximum condition code of 4 or 0.
Additional Information
Feedback
