Wiki Category: VNAC

The reason for spin processing. The value is either line limit or time limit.

The position of the message in the file affected by spin processing. The value is either start of file or end of file.

The configured number of minutes until the file is spun off. If both spin-hours and spin-minutes are zero, then no time threshold was configured.

The configured number of lines until the file is spun off. If this value is zero, then no line-count threshold was configured.

The configured number of hours until the file is spun off. If both spin-hours and spin-minutes are zero, then no time threshold was configured.

The DD name of the file affected by spin processing. The value is VNCOUT, VNCLOG, or SYSLOG.

The JES2 output class of the spin-file.

The address of a shared variable buffer passed to IRXEXCOM. The IRXSHVB layout is documented in the IBM manual z/OS TSO/E System Diagnosis: Data Areas.

A one-byte hexadecimal return code from IRXEXCOM resulting from a failed attempt to retrieve the value of a REXX variable.

X′00′ = request successful
X′01′ = variable did not exist
X′02′ = last variable transferred for fetch next request
X′04′ = truncation occurred for fetch request
X′08′ = invalid variable name
X′10′ = invalid value specified
X′80′ = invalid function code

A unique identifier assigned to each VNAC session. When a new session is created, the session number is reported in VNC0310I.

In many VNAC messages, an individual command is uniquely identified by the concatenation #sess-number.cmd-index.cmd-number.

Other messages use the variable full-cmd-id, which concatenates sess-number.cmd-index.cmd-id and resolves to an identical value.