PTF UJ98129 for APAR OA68463 (3Q25)

PTF UJ98129 for APAR OA68463 (3Q25) provides enhancements for the PDCOLLECT utility action in Configuration Manager.

Configuration Manager-only updates

The following enhancements have been made to the Problem Determination Data Collection (PDCOLLECT) utility action that is provided in Configuration Manager:

The PDCOLLECT action now creates a configuration data set that you can use to customize the collection of your diagnostic data. During the initial run of the utility, the PDCOLLECT action creates the data set PDCLDEF and member $USER. You can customize the $USER member with your own settings to use for collecting diagnostic data during subsequent runs of the utility. For more information, see PDCLDEF($USER).

Note: The PDCOLLECT action also creates members DEFAULTS and KCIVARS. These members are for internal use by the utility and for reference only. Do not update these members.
The PDCOLLECT action now supports multiple formats for the packaged output. If needed, you can produce more than one type of output in a single job. The following additional packaging formats are now available:
- PAX (.pax) file, created in a specified z/OS® UNIX® System Services directory
- ADRDSSU archive
Note: The PDCOLLECT action continues to support the terse (.TRS) file format, which is created using the IEBCOPY UNLOAD function and is retained for compatibility.
Specifying parameters RTE_PLIB_HILEV and RTE_NAME is now optional. Omitting the runtime environment information provided by these parameters limits the types of diagnostic data that the PDCOLLECT action can collect.
You can now capture several snapshots of SDSF Display Active Users (DA) data for specified started tasks. The default is 10 samples every 10 seconds, and you can customize these settings.
You can now capture logs and SDSF DA snapshots for multiple started tasks in a single job by using filtering and wildcard characters.
You can now select the diagnostic data to collect at a detailed level by using collection flags. By collecting only the types of data that you need, you can reduce both the time and storage used by the PDCOLLECT action job. For more information, see PDCOLLECT collection flags.
Enhanced status reporting for the PDCOLLECT action now appears in the KCIPRINT output data set. New messages are in the range KFJ00240I to KFJ00262I.
Sample job TKANSAM(KFJMAINT) has been updated.

To support these enhancements, the following parameters have been introduced or modified:

Table 1. PDCOLLECT parameters
Parameter	Description
RTE_PLIB_HILEV RTE_NAME	Runtime environment information
KFJ_PDCOL_COLLECT_`data`	Diagnostic data collection flags
KFJ_PDCOL_DA_INTERVAL KFJ_PDCOL_DA_SAMPLES	Control the frequency of SDSF Display Active Users (DA) data collection
KFJ_PDCOL_HLQ	High-level qualifier for data sets that the PDCOLLECT action uses
KFJ_PDCOL_JOB_NAME KFJ_PDCOL_JOB_ID KFJ_PDCOL_JOB_FILTER	Collect diagnostic data when OMEGAMON started task logs are in the SDSF output queue
KFJ_PDCOL_JOB_OUTPUT	Collect diagnostic data when OMEGAMON address space logs have been copied to a sequential data set
KFJ_PDCOLLECT_COMPATIBILITY KFJ_PDCOLLECT_ADRDSSU KFJ_PDCOLLECT_PAX KFJ_PDCOLLECT_PAX_DIR	PDCOLLECT action output package formats
KFJ_PDCOLLECT_RESTORE KFJ_PDCOL_RESTORE_HLQ KFJ_PDCOL_ADR_ARCHIVE	Restore ADRDSSU archive Note: These parameters are for use by IBM Software Support only.

For more information about using the Configuration Manager PDCOLLECT action, see Collecting diagnostic data using PDCOLLECT.