PDSE operational problem determination

Partitioned Data Set Extended (PDSE) is an advanced implementation of the MVS partitioned (PO) data set organization. PDSE files:

PDSE can be used in place of a PDS to store data, or to store executable programs in the form of program objects. PDSE data sets are processed using most of the same access methods and macros as PDS files.

PDSE data set access is accomplished by means of a client server relationship between the PDSE user (batch jobs, started tasks, or TSO users) and the SMSPDSE and, optionally, the SMSPDSE1 address space.

Basic PDSE problem determination functions

PDSE provides the following functions to assist with first failure data capture and problem determination.
  • System generated ABEND0F4 dumps
  • EREP reports
  • SYSLOG messages
  • The SMSPDSE and the SMSPDSE1 monitor task
  • PDSE system commands
  • The IEBPDSE PDSE Verification Utility program.

Collecting documentation for PDSE

The support center routinely requests a standard set of diagnostic data for PDSE issues, included is:
  • The first system generated ABEND0F4 dump.
  • Detailed EREP report or raw LOGREC data that brackets the dump by two hours. Raw LOGREC is the preferred format.
  • SYSLOG or OPERLOG for the same time frame as LOGREC/EREP.
  • In the event of PDSE data set corruption, an ADRDSSU physical dump of the affected PDSE data set.

In event that a system generated dump was not taken or if the dump was DAE suppressed then an operator initiated dump of the PDSE address space or spaces may be required.

Pre-allocating an IEADMCxx PARMLIB member, to dump the PDSE processing environment, will save time. Create the member as follows:
JOBNAME=(*MASTER*,SMSPDSE*),                                          
SDATA=(PSA,CSA,SQA,GRSQ,LPA,LSQA,RGN,SUM,SWA,TRT,COUPLE,XESDATA)  
Issue the following command when you need to obtain a dump:
DUMP COMM=(title),PARMLIB=xx
Where, ‘xx’, is the suffix of the IEADMCxx parmlib member that contains the SMSPDSE dump options.