PSB Detail report reference
The PSB Detail report displays PSB instances stored in the IMS catalog database and information about them. The report also shows PSB members in the IMS directory, allowing you to check the consistency of PSBs in the IMS catalog and IMS directory.
If the IMS management of ACBs is not enabled, ACB libraries are analyzed instead of the IMS directory.
This report is generated by running a batch job. To create and run the batch job and view the report, select .
Operations available from the PSB Detail Report panel
You can perform the following operations from the PSB Detail Report panel:
- View PSB statements
- Use this line command to view IMS PSB macro statements.
Place the cursor on the line for the PSB, press the PF4 key to display the action list, and select View PSB statements.
- XREF PSB to DBD
- Use this line command to display the XREF PSB to DBD report and position the cursor on
the line of the selected PSB instance.
Place the cursor on the line for the PSB, press the PF4 key to display the action list, and select XREF PSB to DBD.
- Delete the instance
- Use this line command to delete an instance.
- An instance can be deleted only when the IMS system is online. To delete instances when the IMS system is offline, build JCL statements and submit the batch job.
- Active and pending instances cannot be deleted if the IMS management of ACBs is enabled.
- Members in the IMS directory and the ACB library cannot be deleted.
- If the IMS catalog database is not registered to DBRC, instances cannot be deleted. To delete instances from an IMS catalog database that is not registered to DBRC, build JCL statements and submit the batch job.
Place the cursor on the line for the PSB, press the PF4 key to display the action list, and select Delete the instance.
- Generate JCL to delete all obsolete instances
- You can delete all obsolete instances at once by a batch job. Obsolete instances are
indicated as OBSOLETE in the Status column.
Use primary command DEL (Build JCL to Delete Obsoleted All) to build JCL statements for deleting obsolete instances and submit the batch job. Obsolete instances that will be deleted at run time are those identified as obsolete at the time when the job is executed. The job can be run when the IMS system is online or offline.
PSB Detail report reference
- PSB resource name
- The name of the PSB resource.
- Size of PSB instance in IMS catalog database
- The size of the PSB instance in the IMS catalog database.
- C: Condition of the PSB resource
- The function compares the following timestamps and displays an asterisk (*) in this
column when it detects a mismatch:
- IMS catalog header timestamp and the timestamp of the instance (if the IMS catalog header segment contains timestamps)
- Timestamp of the instance in the IMS catalog and the timestamp of the member in the IMS directory or ACB libraries
- Status
- The status indicators differ based on how the IMS system is configured.
- Status indicators for IMS-managed ACBs environment
- The following table summarizes status indicators used for members in the IMS
directory active and staging data sets.
Table 1. Status indicators for members in the IMS directory active and staging data sets Status Description ACT-DIR PSB member is in the IMS directory active data sets. PEND-DIR PSB member is in the IMS directory staging data set. The following table summarizes status indicators used for instances in the IMS catalog database.
Table 2. Status indicators for instances in the IMS catalog database Status Description ACTIVE Instance whose timestamp matches the active timestamp in the header segment of the IMS catalog database. The header segment of the IMS catalog database contains active timestamp and pending timestamp. Each instance also has its timestamp. IMS Administration Tool compares the timestamp of the instance with the active timestamp in the header segment.
Each member in the IMS directory also has its timestamp. The three timestamps (active timestamp in the header segment of the IMS catalog database, timestamp of the instance in the IMS catalog database, and the timestamp of the member in the IMS directory) must be the same. If they are different, an asterisk (*) is displayed in column C.
PENDING Instance whose timestamp matches the pending timestamp in the header segment of the IMS catalog database. The header segment of the IMS catalog database contains active timestamp and pending timestamp. Each instance also has its timestamp. IMS Administration Tool compares the timestamp of the instance with the pending timestamp in the header segment.
Each member in the IMS directory also has its timestamp. The three timestamps (pending timestamp in the header segment of the IMS catalog database, timestamp of the instance in the IMS catalog database, and the timestamp of the member in the IMS directory) must be the same. If they are different, an asterisk (*) is displayed in column C.
OBSOLETE Instance that is not used by the IMS system. OBSOLETE is shown for the instance that is not ACTIVE nor PENDING.
You can delete obsolete instances by using the delete command (PF6 key) or by building JCL statements and running the job.
- Status indicators for non-IMS-managed ACBs environment
- The following table summarizes status indicators used for members in the ACB
libraries.
Table 3. Status indicators for members in the ACB libraries Status Description ACT-ACBL PSB member is in the ACB library active data set. PEND-ACBL PSB member is in the ACB library staging data set. INACT-ACBL PSB member is in the ACB library inactive data set. The following table summarizes status indicators used for instances in the IMS catalog database.
When the IMS management of ACBs is not enabled, the header segment of the IMS catalog database does not contain active and pending timestamps. IMS Administration Tool determines whether an instance is active or pending by comparing the timestamp of the instance with the timestamp of the member in ACB libraries. To distinguish from ACTIVE and PENDING indicators, which are used when the instance timestamp and header timestamp match, (ACTIVE) and (PENDING) indicators are used.
Table 4. Status indicators for instances in the IMS catalog database Status Description (ACTIVE) Instance whose timestamp matches the timestamp of the member in the ACB library active data set. (PENDING) Instance whose timestamp matches the timestamp of the member in the ACB library staging data set. (INACT) Instance whose timestamp matches the timestamp of the member in the ACB library inactive data set. OBSOLETE Instance that is not used by the IMS system. OBSOLETE is shown for the instance that is not (ACTIVE) nor (PENDING).
You can delete obsolete instances by using the delete command (PF6 key) or by building JCL statements and running the job.
- Status indicators for non-IMS-managed ACBs environment - When IMS catalog is shared with other IMS systems that use IMS-managed ACBs
- The header segment of the IMS catalog database contains active timestamp and pending timestamp. ACTIVE and PENDING indicators are shown for instances whose timestamp matches the timestamp in the header segment. Other indicators are the same as those used for Status indicators for non-IMS-managed ACBs environment.
- Generation Date and Time
- The date and time when the PSB instance was generated.
- PCBs
- The number of TPPCBs, and the number of DB and GSAM PCBs.
- Referenced DBDs
- The number of DBDs that the PSB refers to.
- Shows the number of references only for active PSB instances.
- If multiple DBPCBs in the PSB reference the same DBD, it is counted as one reference.
- Indirect references to DBDs through logical or index relationships are also included in the count.
- If the referencing active or usable DBD instance does not exist in the IMS catalog, it is not counted. For example, if the specific version of an active or usable DBD instance that the PSB references does not exist in the IMS catalog, this reference is not counted.
The following figure shows an example of the PSB Detail report when IMS-managed ACBs are used:
IBM IMS Administration Tool - "PSB Detail Report"
5655-CAT DATE: 06/03/2025 TIME: 04.43.41 ATY@OBJU - V1.R1
IMSID: IMSA
Size in IMS ----- Generation ----- ---- PCBs ---- Referenced
PSB Name Catalog(B) C Status Date Time TP DB&GSAM DBDs
-------- ----------- - --------- ---------- ----------- ----- ------- ----------
TSTPSBAL 3512 PENDING 2025/06/03 04:02:39.41 0 1
TSTPSBAL PEND-DIR 2025/06/03 04:02:39.41
TSTPSBAL 3242 OBSOLETE 2025/06/03 04:02:11.92 0 1
TSTPSBAL 3242 ACTIVE 2025/06/03 04:01:44.90 0 1 1
TSTPSBAL ACT-DIR 2025/06/03 04:01:44.90
TSTPSBAL 3242 OBSOLETE 2025/06/01 01:30:25.40 0 1The following figure shows an example of the PSB Detail report when IMS-managed ACBs are not used:
IBM IMS Administration Tool - "PSB Detail Report"
5655-CAT DATE: 06/03/2025 TIME: 04.33.22 ATY@OBJU - V1.R1
IMSID: IMSB
Size in IMS ----- Generation ----- ---- PCBs ---- Referenced
PSB Name Catalog(B) C Status Date Time TP DB&GSAM DBDs
-------- ----------- - --------- ---------- ----------- ----- ------- ----------
TSTPSBAL 3512 PENDING 2025/06/03 04:02:39.41 0 1
TSTPSBAL PEND-ACBL 2025/06/03 04:02:39.41
TSTPSBAL 3242 (INACT) 2025/06/03 04:02:11.92 0 1
TSTPSBAL INACT-ACBL 2025/06/03 04:02:11.92
TSTPSBAL 3242 ACTIVE 2025/06/03 04:01:44.90 0 1 1
TSTPSBAL ACT-ACBL 2025/06/03 04:01:44.90
TSTPSBAL 3242 OBSOLETE 2025/06/01 01:30:25.40 0 1