SNAPCTL parameter

From m204wiki
Jump to navigation Jump to search

Snap/dump options


Default value

At initialization only:

Hex settingBits summed
X'28' (7.5 and later) Bits X'08' and X'20'
X'41' (z/VM, pre-7.4) Bits X'01' and X'40'
X'44' (z/OS, z/VSE, pre7.5) Bits X'04' and X'40'
Parameter type
Where set
On User 0's parameter line or reset by system manager
Related products
Model 204 V2.1 or earlier


The snap and dump action Model 204 takes when a snap is produced

The table below shows the basic settings of SNAPCTL with their associated actions. The top four actions (X '80' through X '10') are the snap options, and the remainder are the dump options.

As explained below the table, any SNAPCTL specification actually results in both a snap action and a dump action, because Model 204 adds a default snap or dump action to your specification.

Snap and dump settings
Snap settings
X'80' 128 Do not produce a snap
X'40' 64 Snap whatever the individual message specifies
X'20' 32 Smart snap. See Special settings for more information.
X'10' 16 Produce a complete formatted snap
Dump settings
X'08' 8 Do not produce a dump
X'05' 5 Enable an asynchronous dump. See Special settings for more information.
X'04' 4 Dump whatever the individual message specifies
X'02' 2 Dump whatever the individual message specifies and spin off SNAPs (z/OS). See Special settings for more information.
X'01' 1 Produce a complete region dump
X'00' 0 Do not produce a dump. See Special settings for more information.

SNAP and dump half-bytes

The above table is divided into the hexadecimal and decimal settings corresponding to the first (left) four bits of the SNAPCTL value byte, the second four bits, and the special case, zero.

One SNAPCTL byte, divided into a first half-byte and a second half-byte, controls both the snap action and the system dump action. Your specification for SNAPCTL activates both a snap action and an operating system dump action.

The first SNAPCTL half-byte controls the snap action, and the second half-byte controls the dump action, as shown below.


Including half-byte defaults

The SNAPCTL default takes effect at initialization. If you set or reset SNAPCTL, Model 204 overrides the initialization default and replaces it with separate defaults for each SNAPCTL half-byte. Under Model 204 7.5 and later, X'20' is the snap half-byte default, and X'08' is the dump half-byte default. Under earlier Model 204 versions, X'40' is the snap half-byte default, and X'04' is the dump half-byte default.

The default for a half-byte takes effect only if your SNAPCTL setting includes none of the bits of that half-byte. For example, if you specify SNAPCTL=X '08', you are including none of the snap half-byte bits. Model 204 sets the X'08' dump action ("no dump") and includes the snap half-byte default action (X'20', "minimal CCASNAP" under Model 204 7.5 and later).

Your specification of X'08' is translated to X'28'. When a snap is called for, Model 204 snaps whatever the message specifies and produces no dump. If you issue VIEW SNAPCTL, Model 204 displays:


Similarly, if you specify SNAPCTL=X'20', Model 204 sets the X'20' snap action ("smart snap") and includes the dump half-byte default action (X'08', "no dump" under Model 204 7.5 and later). Your specification of X'20' is translated to X'28'. If you issue VIEW SNAPCTL, Model 204 displays:


If you specify a SNAPCTL setting that includes bits from both half-bytes, neither half-byte default action is automatically included. For example, if you specify SNAPCTL=X '41', Model 204 combines the X'40' action ("snap whatever the message specifies") and the X '01' action (region dump). If you issue VIEW SNAPCTL, Model 204 displays:


You cannot specify a combination of two snap half-byte bits or two dump half-byte bits. With one exception, the bit settings within each half-byte are mutually exclusive. For example, if you specify SNAPCTL=X'60' (X'40' plus X'20'), you get an error message stating that conflicting attributes prevent the resetting of SNAPCTL.

X'02' is the only bit setting that you can combine with other bits in its half-byte. For example, if you specify SNAPCTL=X'43', you get the combined actions of X'02', X'01', and X'40'.

Special settings

The following SNAPCTL settings require further comment.

SNAPCTL setting Comments...

X '00'

The zero bit is treated as if it belongs to the dump half-byte. Specifying SNAPCTL=X '00' is equivalent to specifying SNAPCTL=X '08'.


Under only z/OS, you can spin off a snap. Spinning off a snap means dynamically allocating the snap to SYSOUT, making output available immediately rather than waiting for the end of the run.


Under z/OS only, you can enable a complete region asynchronous dump.
This setting is not required when SYSMDUMP or CCAMDMPn DDs are present. If set to 5 in those cases, two SVCDUMPs will be generated: one to DSN=SYS1.DUMPnn and one to //SYSMDUMP or //CCAMDMPn.


If SNAPCTL=X '20', Model 204 takes a snap of the registers, module link map, allocated storage map, pushdown list trace, KOMM, areas near registers at the time of the error, disk buffers containing Model 204 file pages held by the current user, the current user's server, patch information, and other contextually determined areas.

In general, this is a good setting for snaps, as the control blocks necessary to diagnose most problem are likely to be in such a snap, whereas any more-complete snaps are likely to be massive and unwieldy and not contain any more useful information, anyway. As such, CCASNAPs produced with the X'20 SNAPCTL setting are called smart snaps.

See SNAPPDLX: PDL SNAP extender if you are having Horizon thread problems.

Asynchronous dump option for z/OS

You can generate asynchronous SVC dumps and write to SYS1.DUMP data sets on Model 204 ABENDs. Model 204 continues as soon as the pages are copied to the DUMPSERV address space. All physical I/O is done from DUMPSERV, which frees the Online system sooner.

You can enable the asynchronous dump by specifying SNAPCTL=X'05', which is a separate setting that produces a complete region asynchronous dump.

WARNING: Familiarize yourself with the memory requirements of the asynchronous dump process to ensure that enough expanded and page space is available. Memory shortage can cause severe system degradation while an asynchronous dump is processing the DUMPSERV address space. If you use this setting and you have not properly configured the DUMPSERV memory requirements, you risk locking your z/OS system.

If the dump is not taken, due to suppression by SLIP traps-Dump Analysis Elimination (DAE) or a z/OS problem, the following IBM error message is written to the operator:


The reason codes are listed in the SDUMPX macro in the z/OS Auth Assm Service Reference LLA-SDU. The number of the manual varies according to the release of z/OS.


The SNAPCTL parameter settings correspond to the following MSGCTL command options:

SNAPCTL setting MSGCTL option