Browse Prior Art Database

Started Task for Tracing Dynamically Allocated Non-VSAM Data Sets

IP.com Disclosure Number: IPCOM000119173D
Original Publication Date: 1997-Dec-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 4 page(s) / 76K

Publishing Venue

IBM

Related People

Lynds, J: AUTHOR

Abstract

Disclosed is a started task that eliminates the requirement to edit the Job Control Language Data Definition statement (JCL DD stmt.) in order to activate Generalized Trace Facility (GTF) tracing of non-VSAM data sets during Open/Close/End of Volume processing (O/C/EOV is part of DFSMS*). It is now feasible to activate O/C/EOV tracing for dynamically allocated data sets which have no associated JCL.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Started Task for Tracing Dynamically Allocated Non-VSAM Data Sets

      Disclosed is a started task that eliminates the requirement to
edit the Job Control Language Data Definition statement (JCL DD
stmt.) in order to activate Generalized Trace Facility (GTF) tracing
of non-VSAM data sets during Open/Close/End of Volume processing
(O/C/EOV is part of DFSMS*).  It is now feasible to activate O/C/EOV
tracing for dynamically allocated data sets which have no associated
JCL.

      O/C/EOV provides an optional Problem Determination Work Area
Trace to obtain diagnostic information during the processing of
non-VSAM data sets.  Trace records are written to the GTF trace data
set after each O/C/EOV module executes.  Each record includes the
module flow and  a snapshot of the main O/C/EOV work area, associated
Data Control Block/Access method Control Block (DCB/ACB) and Data
Extent Block (DEB).

      A new started task can now activate this component trace.  The
requirement to edit the JCL DD statement associated with the data set
to be traced is eliminated when the started task is used.

      System Command:  START IFGOCETR entered at the MVS/ESA system
console initiates a message dialogue prompting for trace key
information.  The three trace keys are job name (JN=) and/or DD name
(DDN=) and/or data set name (DSN=).  The trace key data supplied is
used to activate one of ten possible entries in a trace table built
and maintained by the started task.  This trace table resides in
subpool 241 key 0, in above the line CSA/ECSA...