Batch jobs steps with no PSB

This page provides an Activity log summary of batch jobs steps for which no matching PSB was found in the RAA® inventory. You access this error summary page by clicking the non-zero count for this error on the Errors page.

To view the details page for a particular batch job, click the name in the Asset column. The Batch job details page opens in the current window.

Connecting PSBs to run units

The Connect PSB to run unit Analysis queue requests (queue type 16) are automatically generated and put on the Analysis queue when IMS Run units are identified. Identification of run units involving PSBs occurs during inventory collection, originating from IMS transactions and Batch jobs when DFSRRC00, batch IMS, is detected. The goal of a queue type 16 request is to populate the PSB_ID column in the DMH_INVOKE_RU table for Batch jobs and the DMH_TRANSACTION table for IMS transactions.

When no matching PSB can be located for a batch job step, a Warning message that indicates none was found is written to the Activity log. From the Batch job details page, review the Analysis Messages section for DMH1030W messages that indicate the specific PSB name and Job step name.

Resolving Batch job steps with no PSB

Adding more assets to the inventory almost always improves the overall picture and understanding of the enterprise. PSBs that are associated with batch jobs and IMS transactions can be resolved for the completeness of the inventory. However, it is not mandatory. The Warning messages on the asset's details pages can be ignored. Otherwise, to provide PSB control blocks to the inventory, choose one of the following options:

Scan the PSB control blocks, either the binary IMS PSBLIB or ACBLIB, but not both.
Tip: For more information about IMS inventory, see Scanning IMS subsystems.
Collect inventory for the PSBGEN source files, instead of the binary files.
Tip: For more information about relating a PSB source file container to an IMS subsystem, see Scanning source code.

Option 1 automatically connects the IMS subsystem with the binary library.

Option 2 requires an additional manual step to relate the IMS subsystem to the PSB source file container.

Tip: For more information about relating a PSB source file container to an IMS subsystem, see Relate a container and IMS subsystem.