ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

In PTIMSG output from a PDA statistics collection, the ACCESS parameter is listed 3 times. What do these mean (they can be different values)

book

Article ID: 53347

calendar_today

Updated On:

Products

RC Compare for DB2 for z/OS Database Analyzer for DB2 for z/OS Fast Unload for DB2 for z/OS Fast Check for DB2 for z/OS Fast Index for DB2 for z/OS Fast Load for DB2 for z/OS Rapid Reorg for DB2 for z/OS CA Distributed Database Management CA Database Analyzer for DB2 for Oracle Database Analyzer (IMS Tools) Mainframe Configuration Manager for IMS for z/OS IMS TOOLS - MISC Compress Data Compression (IMS Tools) Database Analyzer for IMS for z/OS Database Copier for IMS for z/OS Database Organizer for IMS for z/OS Mainframe Extended Terminal Manager (IMS Tools) High Performance Recovery for IMS for z/OS Database Organizer (IMS Tools) Mainframe Program Restart Manager for IMS for z/OS Secondary Index Builder for IMS for z/OS Secondary Index for IMS for z/OS

Issue/Introduction

Description

Example PDA output as follows. Values can be different and cause confusion over there meaning.

  1. Options specified when procedure was SUBMITted:
    COLLECTION - FASTSCAN
    STATS ID: ssid BUFFERS: 0360 ERRORS : 0010
    WTOR CD : 00 SCAN : 0006 ACCESS : VSAM
  2. PTIIPT input control cards:

    check the first control card, in column 32

    e.g. x'88' this means use VSAM access, extract procedure.

    (The description of values in this control card are listed in Appendix C of the PDA Ref Guide.)

  3. Collection of data statistics Started - Subsystem - ssid

    Access: V/EXCP Buffers: 0360 Scans: 0006 Scantype: FASTSCAN

Solution

The first two values listed represent the "Obj Read Access" value of the user's PDA Profile at the time the extract JCL was created.

The third value actually represents the access method used.

This can be different (as in the example given) as the value of EXCP_READ_ACCESS in the PDA member of the users PARMLIB can affect the ACCESS used.

In this case EXCP_READ_ACCESS is set to TS_COLL so overrides the value of VSAM that was defined in the profile.

Environment

Release:
Component: DBA