Troubleshooting Persistent Data Store (PDS) Problems

Preventive Service Planning


Abstract

Experiencing PDS issues in my agent and / or Tivoli Management Server (TMS), how do I debug these issues.

Content

This document will assist you in troubleshooting a PDS issue in z/OS. This addresses V622, V623 and V630 of IBM Tivoli Monitoring (ITM).

Updated maintenance for PDS is in the following PTFs:

ITM Version
PTF
Description
622
UA65748
ITM 622 FP9 is recommended.
UA76530
Persistent Data Store files goes offline after the maintenance jobs completes.
623
UA73317/UA73318
ITM 623 FP5 recommended.
UA76315
ABEND U1208 or ABEND S0C4 while running the PDS extract job, KPDXTRAJ.
UA76531
Persistent Data Store files goes offline after the maintenance jobs completes.
UA76635
Memory allocations intended to be 4k are actually allocated as 8k.
630
UA76202
ITM630 FP4 is recommended.
UA76316
ABEND U1208 or ABEND S0C4 while running the PDS extract job, KPDXTRAJ.
UA76532
Persistent Data Store files goes offline after the maintenance jobs completes.
UA76636
Memory allocations intended to be 4k are actually allocated as 8k.


If possible, ensure PDS performs a graceful shutdown, in cases where this is not possible, the PDS maintenance will attempt to close the PDS files after writing the data in the buffer to the PDS files.

The latest PDS maintenance will attempt to create PDS dumps which will assist support in isolating your problem. Before reporting PDS issues to IBM Support Center, ensure the PTFs specified above are installed. If problem persists with PDS after the above PTFs are installed, provide the documentation as specified below and open a SR with the IBM Support Center.

PROBLEM
RESOLUTION
ABEND occurred in line nnn of @@nnnnn(ITBL) ,offset nnnnnn
Program terminated by operating system. ABEND code = S0C4
Send in dump and all logs from this address space.
LSCX010 **** ERROR ****
ABEND occurred in ASRTFL called from line nnn of _DYNAMN(MANE) ,
Program terminated by call to abort. ABEND code = U12nn
Calling trace:
Check for another abend prior to this abend. The first abend should be addressed first.

If no other abend, send in the dump and all logs from this address space.

KPDIFIL: Invalid status information detected in file hiLevel.Qualifier.table name
(group group-name).........The file had not been closed properly.
Try to issue the recover command and see if this resolves the issue: F address-space,KPDCMD RECOVER FILE=DSN:datasetname (where datasetname is the full-qualified name of the file, without quotes)
KPDMN004 PDS IS INACTIVE For some reason PDS did not initiate correctly or it has abended, in the current design there is no command to re-activate PDS. A recycle of the address space is required.
KPDIFIL: Error opening file pdshilev.lowlev, RC = 14202 Verify pdshilev.lowlev exists, if it exists verify it was built correctly.
If built correctly, verify it is not being allocated by another address space.
  1. If PDS continues to abend, you can execute a batch job to try to recover the data. The batch jobs can be found in &rhilev.&rte.RKANSAMU:
    1. KPDEXPTJ - Batch job to export a persistent datastore
    2. KPDRESTJ - Batch job to restore a persistent datastore from a file that was created by KPDEXPTJ.
    3. KPDXTRAJ - Batch job to extract table data from a persistent datastore dataset.
  2. If all else fails, you can scratch and reallocate the PDS files. In PARMGEN the WKANSAMU dataset contains standalone jobs to reallocate the PDS files, run the composite KCIJPALO RTE build job after deleting the PDS files. In ICAT, you can execute the #P and #Q jobs after deleting the PDS files.

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli OMEGAMON XE for CICS on z/OS 4.2.0, 5.1.0, 5.3.0
Systems and Asset Management Tivoli OMEGAMON XE on z/OS 5.1.0, 5.1.1, 5.3.0, 4.2.0
Systems and Asset Management Tivoli OMEGAMON XE for CICS TG on z/OS 4.2.0, 5.1.0, 5.3.0
Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Expert for z/OS 5.1.0, 5.1.1, 5.2.0
Systems and Asset Management Tivoli OMEGAMON XE for DB2 Performance Monitor for z/OS 5.1.0, 5.1.1, 5.2.0
Systems and Asset Management Tivoli OMEGAMON XE for IMS on z/OS 4.2.0, 4.1.0, 5.1.0
Systems and Asset Management Tivoli OMEGAMON XE for Mainframe Networks 4.2.0, 5.1.0, 5.1.1, 5.3.0
Storage Management Tivoli OMEGAMON XE for Storage on z/OS 4.2.0, 5.1.0, 5.2.0, 5.3.0
Systems and Asset Management Tivoli OMEGAMON XE for Messaging for z/OS 7.0, 7.0.1, 7.1.0, 7.3.0

Document information


More support for:

Tivoli Monitoring V6

Software version:

6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.3.0

Operating system(s):

OS/390, z/OS

Reference #:

1623100

Modified date:

2015-05-11

Translate my page

Content navigation