DFSMSdfp provides a problem determination work area trace started task, IFGOCETR, to allow tracing of dynamically allocated non-VSAM data sets. The started task will create a trace table in CSA/ECSA storage. Once the area is created it will remain for the duration of the IPL. This is intended to be used for dynamically allocated data sets but can also be used instead of specifying DCB=DIAGNS=TRACE on the DD statement of a data set for which tracing is desired.

The work area trace started task is activated by the operator specifying S IFGOCETR. The operator must then respond to message IEC980A, providing the data set name and/or the job name and/or the DD statement name identifying the data sets for which tracing is desired. Any combination of these specifications is allowed, but the more specific the information provided, the more selective O/C/EOV will be in determining which data sets are to be traced. For example, if only a job name is specified, then all data sets processed by that job would be eligible to be traced. This is probably not what was intended. Therefore, it is recommended to specify as many keys as necessary to limit tracing to the specific data set to be traced. Message IEC980I is issued for both informational and error purposes. The maximum number of trace table entries that can be active is 10. If a request is made to activate an entry when the maximum has been reached, then the operator will be requested to delete one or all of the currently active entries. The operator also has the option to display the active entries list. See Work area trace started task messages for more information concerning messages IEC980A and IEC980I. The active trace table entries will not actually be traced until the operator starts GTF activating the optional work area trace.

The started task does not have to be active in order to activate the GTF trace. Once the table entries are built, the started task can be terminated.