SNAPCTL parameter - Revision history

DCameron: /* Comparing SNAPCTL to MSGCTL */

2017-07-26T11:50:07Z

Comparing SNAPCTL to MSGCTL

← Older revision		Revision as of 11:50, 26 July 2017
Line 157:		Line 157:
	====Comparing SNAPCTL to MSGCTL====		====Comparing SNAPCTL to MSGCTL====
	<p>		<p>
	The <var>SNAPCTL</var> parameter settings correspond to the following <var>MSGCTL</var> command options: </p>		The <var>SNAPCTL</var> parameter settings correspond to the following <var>[[MSGCTL_command\|MSGCTL]]</var> command options: </p>
	<table>		<table>
	<tr class="head"><th>SNAPCTL setting</th>		<tr class="head"><th>SNAPCTL setting</th>

DCameron: /* Special settings */

2017-07-26T11:47:01Z

Special settings

← Older revision		Revision as of 11:47, 26 July 2017
Line 131:		Line 131:
	<tr><th><var><p>X'05'</p></var></th>		<tr><th><var><p>X'05'</p></var></th>
	<td><p>Under z/OS only, you can enable a complete region [[#Asynchronous dump option for z/OS\|asynchronous dump]]. <br />		<td><p>Under z/OS only, you can enable a complete region [[#Asynchronous dump option for z/OS\|asynchronous dump]]. <br />
	This setting is not required when SYSMDUMP or CCAMDMP<i>n</i> DDs are present. If set to 5 in those cases, two SVCDUMPs will be generated: one to DSN=SYS1.DUMP<i>nn</i> and one to //SYSMDUMP or //CCAMDMP<i>n</i>.</p>		This setting is not required when SYSMDUMP or [[CCAMDMP_data_sets\|CCAMDMP]]<i>n</i> DDs are present. If set to 5 in those cases, two SVCDUMPs will be generated: one to DSN=SYS1.DUMP<i>nn</i> and one to //SYSMDUMP or //CCAMDMP<i>n</i>.</p>
	</td></tr>		</td></tr>

JAL: misc formatting

2017-07-24T16:27:28Z

misc formatting

Show changes

DCameron: /* Summary */

2017-07-24T15:27:33Z

Summary

← Older revision		Revision as of 15:27, 24 July 2017
Line 18:		Line 18:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V6.1</var> or earlier		<dd><var class="product">Model 204 V2.1</var> or earlier
	</dl>		</dl>

JAL: misc formatting

2017-03-09T01:12:18Z

misc formatting

Show changes

Alex: /* Including half-byte defaults */

2014-05-21T02:52:02Z

Including half-byte defaults

← Older revision		Revision as of 02:52, 21 May 2014
Line 52:		Line 52:
	<p class="code">SNAPCTL X'28' SNAP/DUMP OPTIONS		<p class="code">SNAPCTL X'28' SNAP/DUMP OPTIONS
	</p>		</p>
	<p>Similarly, if you specify SNAPCTL=X'20', <var class="product">Model 204</var> sets the X'20' snap action ("snap ~~PDL~~") 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 VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>		<p>Similarly, if you specify SNAPCTL=X'20', <var class="product">Model 204</var> 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 VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>
	<p class="code">SNAPCTL X'28' SNAP/DUMP OPTIONS		<p class="code">SNAPCTL X'28' SNAP/DUMP OPTIONS
	</p>		</p>

Alex: /* Description */

2014-05-21T02:51:13Z

Description

Alex: /* Including half-byte defaults */

2014-05-21T02:48:36Z

Including half-byte defaults

← Older revision		Revision as of 02:48, 21 May 2014
Line 48:		Line 48:
	====Including half-byte defaults====		====Including half-byte defaults====
	<p>The SNAPCTL default takes effect at initialization. If you set or reset SNAPCTL, <var class="product">Model 204</var> 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.</p>		<p>The SNAPCTL default takes effect at initialization. If you set or reset SNAPCTL, <var class="product">Model 204</var> 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.</p>
	<p>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. <var class="product">Model 204</var> sets the X'08' dump action ("no dump") and includes the snap half-byte default action (X'20', "~~Snap whatever the message specifies~~" under Model 204 7.5 and later).</p>		<p>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. <var class="product">Model 204</var> 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).</p>
	<p>Your specification of X'08' is translated to X'28'. When a snap is called for, <var class="product">Model 204</var> snaps whatever the message specifies and produces no dump. If you VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>		<p>Your specification of X'08' is translated to X'28'. When a snap is called for, <var class="product">Model 204</var> snaps whatever the message specifies and produces no dump. If you VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>
	<p class="code">SNAPCTL X'48' SNAP/DUMP OPTIONS		<p class="code">SNAPCTL X'28' SNAP/DUMP OPTIONS
	</p>		</p>
	<p>Similarly, if you specify SNAPCTL=X~~ ~~'20', <var class="product">Model 204</var> sets the X '20' snap action ("snap PDL") and includes the dump half-byte default action (X '04', "dump ~~whatever the message specifies~~"). Your specification of X '20' is translated to X~~ ~~'24'. If you VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>		<p>Similarly, if you specify SNAPCTL=X'20', <var class="product">Model 204</var> sets the X'20' snap action ("snap PDL") 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 VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>
	<p class="code">SNAPCTL X'24' SNAP/DUMP OPTIONS		<p class="code">SNAPCTL X'28' SNAP/DUMP OPTIONS
	</p>		</p>
	<p>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', <var class="product">Model 204</var> combines the X '40' action ("snap whatever the message specifies") and the X '01' action (region dump). If you VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>		<p>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', <var class="product">Model 204</var> combines the X'40' action ("snap whatever the message specifies") and the X '01' action (region dump). If you VIEW SNAPCTL, <var class="product">Model 204</var> displays: </p>
	<p class="code">SNAPCTL X'41' SNAP/DUMP OPTIONS		<p class="code">SNAPCTL X'41' SNAP/DUMP OPTIONS
	</p>		</p>
	<p>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. </p>		<p>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.</p>
	<p>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'. </p>		<p>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'. </p>

	====Special settings====		====Special settings====

Alex: /* Special settings */

2014-05-21T02:45:24Z

Special settings

← Older revision		Revision as of 02:45, 21 May 2014
Line 88:		Line 88:
	<p>X'20'</p>		<p>X'20'</p>
	</var></th><td>		</var></th><td>
	<p>If SNAPCTL=X '20', <var class="product">Model 204</var> 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 ~~form~~ snaps as the control blocks necessary to diagnose most problem are likely to be in such a whereas any more complete snaps are likely to be massive and unwieldy and not contain any more useful information, anyway.</p>		<p>If SNAPCTL=X '20', <var class="product">Model 204</var> 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.</p>
	<p>See [[SNAPPDLX parameter\|SNAPPDLX: PDL SNAP extender]] if you are having Horizon thread problems.</p>		<p>See [[SNAPPDLX parameter\|SNAPPDLX: PDL SNAP extender]] if you are having Horizon thread problems.</p>
	</td></tr>		</td></tr>

Alex: /* Special settings */

2014-05-21T02:44:42Z

Special settings

← Older revision		Revision as of 02:44, 21 May 2014
Line 75:		Line 75:
	</td></tr>		</td></tr>
	<tr><th><var>		<tr><th><var>
	<p>X '02'</p>		<p>X'02'</p>
	</var></th><td>		</var></th><td>
	<p>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. </p>		<p>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. </p>
	</td></tr>		</td></tr>
	<tr><th><var>		<tr><th><var>
	<p>X '05'</p>		<p>X'05'</p>
	</var></th><td>		</var></th><td>
	<p>Under only z/OS, you can enable a complete region [[#Asynchronous dump option for z/OS\|asynchronous dump]]. <br />		<p>Under only z/OS, you can enable a complete region [[#Asynchronous dump option for z/OS\|asynchronous dump]]. <br />
Line 86:		Line 86:
	</td></tr>		</td></tr>
	<tr><th><var>		<tr><th><var>
	<p>X '20'</p>		<p>X'20'</p>
	</var></th><td>		</var></th><td>
	<p>If SNAPCTL=X '20', <var class="product">Model 204</var> takes a snap of the registers, module link map, allocated storage map, pushdown list trace, KOMM, disk buffers containing ~~<var class="product">~~Model 204~~</var>~~ file pages held by the current user ~~(maximum of 4)~~, and ~~patch~~ information.</p>		<p>If SNAPCTL=X '20', <var class="product">Model 204</var> 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 form snaps as the control blocks necessary to diagnose most problem are likely to be in such a whereas any more complete snaps are likely to be massive and unwieldy and not contain any more useful information, anyway.</p>
	<p>See [[SNAPPDLX parameter\|SNAPPDLX: PDL SNAP extender]] if you are having Horizon thread problems.</p>		<p>See [[SNAPPDLX parameter\|SNAPPDLX: PDL SNAP extender]] if you are having Horizon thread problems.</p>
	</td></tr>		</td></tr>
	</table>		</table>

	====Asynchronous dump option for z/OS====		====Asynchronous dump option for z/OS====
	<p>You can generate asynchronous SVC dumps and write to SYS1.DUMP data sets on <var class="product">Model 204</var> ABENDs. <var class="product">Model 204</var> 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.</p>		<p>You can generate asynchronous SVC dumps and write to SYS1.DUMP data sets on <var class="product">Model 204</var> ABENDs. <var class="product">Model 204</var> 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.</p>

← Older revision		Revision as of 02:51, 21 May 2014
Line 29:		Line 29:
	<tr><th>Hex</th><th>Dec</th><th>Action</th></tr>		<tr><th>Hex</th><th>Dec</th><th>Action</th></tr>
	<tr><td><b>Snap settings</b></td></tr>		<tr><td><b>Snap settings</b></td></tr>
	<tr><th><var>X '80'</var></th><td>128</td><td>Do not produce a snap </td></tr>		<tr><th><var>X'80'</var></th><td>128</td><td>Do not produce a snap </td></tr>
	<tr><th><var>X '40'</var></th><td>64</td><td>Snap whatever the individual message specifies</td></tr>		<tr><th><var>X'40'</var></th><td>64</td><td>Snap whatever the individual message specifies</td></tr>
	<tr><th><var>X '20'</var></th><td>32</td><td>~~Snap PDL (pushdown list)~~. See [[#Special settings\|Special settings]] for more information.</td></tr>		<tr><th><var>X'20'</var></th><td>32</td><td>Smart snap. See [[#Special settings\|Special settings]] for more information.</td></tr>
	<tr><th><var>X '10'</var></th><td>16</td><td>Produce a complete formatted snap </td></tr>		<tr><th><var>X'10'</var></th><td>16</td><td>Produce a complete formatted snap </td></tr>
	<tr><td><b>Dump settings</b></td></tr>		<tr><td><b>Dump settings</b></td></tr>
	<tr><th><var>X '08'</var></th><td>8</td><td>Do not produce a dump</td></tr>		<tr><th><var>X'08'</var></th><td>8</td><td>Do not produce a dump</td></tr>
	<tr><th><var>X '05'</var></th><td>5</td><td>Enable an asynchronous dump. See [[#Special settings\|Special settings]] for more information.</td></tr>		<tr><th><var>X'05'</var></th><td>5</td><td>Enable an asynchronous dump. See [[#Special settings\|Special settings]] for more information.</td></tr>
	<tr><th><var>X '04'</var></th><td>4</td><td>Dump whatever the individual message specifies</td></tr>		<tr><th><var>X'04'</var></th><td>4</td><td>Dump whatever the individual message specifies</td></tr>
	<tr><th><var>X '02'</var></th><td>2</td><td>Dump whatever the individual message specifies and spin off SNAPs (z/OS). See [[#Special settings\|Special settings]] for more information. </td></tr>		<tr><th><var>X'02'</var></th><td>2</td><td>Dump whatever the individual message specifies and spin off SNAPs (z/OS). See [[#Special settings\|Special settings]] for more information. </td></tr>
	<tr><th><var>X '01'</var></th><td>1</td><td>Produce a complete region dump</td></tr>		<tr><th><var>X'01'</var></th><td>1</td><td>Produce a complete region dump</td></tr>
	<tr><th><var>X '00'</var></th><td>0</td><td>Do not produce a dump. See [[#Special settings\|Special settings]] for more information.</td></tr>		<tr><th><var>X'00'</var></th><td>0</td><td>Do not produce a dump. See [[#Special settings\|Special settings]] for more information.</td></tr>
	</table>		</table>
	====SNAP and dump half-bytes====		====SNAP and dump half-bytes====
Line 88:		Line 88:
	<p>X'20'</p>		<p>X'20'</p>
	</var></th><td>		</var></th><td>
	<p>If SNAPCTL=X '20', <var class="product">Model 204</var> 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.</p>		<p>If SNAPCTL=X '20', <var class="product">Model 204</var> 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 <i>smart snaps</i>.</p>
	<p>See [[SNAPPDLX parameter\|SNAPPDLX: PDL SNAP extender]] if you are having Horizon thread problems.</p>		<p>See [[SNAPPDLX parameter\|SNAPPDLX: PDL SNAP extender]] if you are having Horizon thread problems.</p>
	</td></tr>		</td></tr>