IBM Support

Setting Up the HSM Problem Determination Aid (PDA) Facility

Question & Answer


How do I set up and use HSM's PDA trace facility?


Customer wants to use HSM's PDA trace facility.


The HSM PDA trace function is designed to facilitate first-failure data capture of problems that occur during HSM processing. The trace facility requires minimal system resources with negligible performance degradation to HSM.

To enable the HSM PDA, you must first ensure the PDOX and PDOY data sets are pre-allocated. PDA data sets can be SMS-managed or non-SMS managed. If you decide to SMS-manage them, you must use GUARANTEED SPACE.  It is recommended that you assign them to a management class that does not perform MIGRATION or BACKUP.

Here is an example of an allocation for non-SMS-managed PDA data sets:

//         UNIT=?TRACEUNIT,SPACE=(CYL,(20,2))                                    
//         UNIT=?TRACEUNIT,SPACE=(CYL,(20,2))        

Both data sets must be allocated on the same volume. The size of the data sets depends on how busy your system is and how much trace information you want the PDA to contain. You can tune the size of the PDA data sets by monitoring for ARC0037I messages while PDA is enabled. HSM generates an ARC0037I message each time the PDA data sets swap.  Tune the size of the PDOX and PDOY data sets until the PDA data sets swap at an acceptable frequency.

When the PDA data sets are allocated, the trace facility must be enabled. There are three places where the PDA data set is controlled:

1. In the HSM STARTUP PROC, set PDA to 'YES' to ensure PDA tracing begins when the HSM startup procedure runs.

2. In the HSM ARCCMDxx PARMLIB member, ensure the command 'SETSYS PDA(ON)' is present.

3. While HSM is processing, the PDA can be toggled ON/OFF interactively with the commands:


When PDA is enabled, you can manually swap the PDA data sets with the command:


You can retain PDA trace information for days, weeks, or months with an auto-op program and a GDG:

1. Allocate a GDG to hold the contents of the PDOY data.

2. Create a job that copies the PDOY data set into the GDG that you allocated in step 1.
3. Set up an auto-op job to run the job from step 2 when an ARC0037I message is received.  The ARC0037I message is generated by HSM when the PDOX and PDOY data sets are swapped.

Ensure that the PDA data sets are large enough so the auto-op job completes before HSM needs to swap the PDA again.  If HSM attempts to swap the PDA while the job is copying the PDOY data set, PDA tracing fails.

You can determine the time period that a PDA data set covers by browsing the data set with ISPF.  The first record in the PDA data set is a time stamp that indicates when the first record was written.  The time stamp looks like this:
11049.TIME....÷Ü.Ú045718.GߨN2 ..¯1H*MCVTFPDA*X...6 .......
In the example, the time stamp was made on the 049 Julian date of 2011 at 04:57:18.

HSM writes these time stamps periodically through the PDA.  The last time stamp in the PDA data set indicates the approximate end time.


[{"Product":{"code":"SSLTBW","label":"z\/OS"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"5695DF170 - DFSMS\/MVS HIERARCHICAL STORAGE MANAGER (HSM)","Platform":[{"code":"PF035","label":"z\/OS"},{"code":"","label":"OS\/390"},{"code":"","label":"MVS\/ESA"}],"Version":"Not Applicable","Edition":"Advanced","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
11 December 2019