Created , Updated


z/IRIS creates z/OS Work traces for APM using SMF record type 30 records. z/OS Work traces provide visibility into critical batch jobs, processes, transactions and users that may impact business applications and services. Tags/attributes provide further information about the performance, the consumption of system resources and identifies any associated users and systems.

SMF record type 30

Types of Work

SMF 30 records provide accounting information for units of work on z/OS systems. A unit of work (UOW) in this context, can refer to one of the following:

  • TSO/E session

  • APPC/MVS transaction program

  • OMVS forked or spawned address space

  • Started task

  • Batch job

z/IRIS will recognize the type of UOW using SMF30WID and, depending on the APM vendor, users may locate traces under the following value groups:

  • TSO

  • OMVS

  • JES2

  • STC

  • INTERVAL

  • SYSTEM ADDRESS SPACE

Subtypes 1-6 of the type 30 SMF record generally signal one of the following:

  • A state of the UOW (i.e., started or ended)

  • The recording of accounting statistics is complete for the customized accounting interval.

As such, z/OS Work traces will contain information relevant to the subtype of the type 30 SMF record.

Subtype 1

Signals either that

  • a user logged onto a z/OS system via TSO or

  • a UOW started.

z/OS Work traces created from this subtype, provide identification information for

  • the UOW,

  • any associated user,

  • and relevant z/OS system.

These traces do not contain attributes that provide information about performance or consumption of system resources.

Subtype 2 and 3

Signals that the recording of statistics for interval accounting has ended. z/OS system programmers activate interval accounting by customizing INTVAL (and optionally SYNCVAL) in the SMFPRMxx parmlib member.

Refer to IBM Documentation to find out more about SMFPRMxx statements and parameters.

z/OS Work traces created from these subtypes monitor the UOWs active during the customized interval, and provide the following information:

  • UOW identifiers

  • Associated user information

  • Relevant z/OS system

  • Performance (e.g., processor consumption)

  • Resource usage (e.g., storage consumption)

Subtype 4

Signals that a step in a batch job has completed.

z/OS Work traces created from this subtype provide the following information:

  • Batch job and step identifiers

  • Associated user identifiers

  • Relevant z/OS system

  • Duration of the step (i.e., the amount of time between the start and end of the step’s processing)

  • Performance (e.g., processor consumption)

  • Resource usage (e.g., storage consumption)

z/IRIS signals an error for a non-zero completion code and may provide error information using APM vendor events or using OpenTelemetry’s APIs to provide error descriptions in traces.

Subtype 5

Signals either that

  • a user logged off from a z/OS system or

  • A UOW ended.

z/OS Work traces created from this subtype contain:

  • UOW identifiers

  • Associated user identifiers

  • Relevant z/OS system

  • Duration of the UOW (i.e., the amount of time between the start and end of the UOW processing)

  • Performance (e.g., processor consumption)

  • Resource usage (e.g., storage consumption)

z/IRIS signals an error for a non-zero completion code and may provide error information using APM vendor events or using OpenTelemetry’s APIs to provide error descriptions in traces.

Subtype 6

Provides statistics for started tasks running on z/OS systems.

z/OS Work traces created from this subtype contain:

  • Started task identifiers

  • Associated user identifiers

  • Relevant z/OS system

  • Duration of the started task (i.e., the amount of time since the started task was initiated until the current time of the trace)

  • Performance (e.g., processor consumption)

  • Resource usage (e.g., storage consumption)


>> z/OS Work observability in Instana APM

>> z/OS Work OpenTelemetry Observability