BUMPSNAP command: Difference between revisions
No edit summary |
No edit summary |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
The <var>BUMPSNAP</var> command is identical to the <var class="product">Model 204</var> <var>[[BUMP command]]</var> | The <var>BUMPSNAP</var> command is identical to the <var class="product">Model 204</var> <var>[[BUMP command]]</var> | ||
with the exception that a CCASNAP is taken for the user or users being BUMPed. | with the exception that a [[Storing_diagnostic_information_(CCASNAP)|CCASNAP]] is taken for the user or users being BUMPed, if the user is in a BUMPable wait. | ||
When the <var>BUMPSNAP</var> command is issued, the following message is written to CCAAUDIT/CCAJLOG and is printed at the top of each page of CCASNAP: | When the <var>BUMPSNAP</var> command is issued, the following message is written to [[Tracking_system_activity_(CCAJRNL,_CCAAUDIT,_CCAJLOG)|CCAAUDIT/CCAJLOG]] and is printed at the top of each page of CCASNAP: | ||
<p class="code">MSIR.0661: Snap taken, user bumped by BUMPSNAP command</p> | <p class="code">MSIR.0661: Snap taken, user bumped by BUMPSNAP command</p> | ||
This can be useful in diagnosing a hung user situation where the | This can be useful in diagnosing a hung user situation where the | ||
error is believed to be a <var class="product">Model 204</var> internals problem. | error is believed to be a <var class="product">Model 204</var> internals problem. | ||
Whether or not a CCASNAP or SYSMDUMP/VMDUMP is actually taken | Whether or not a CCASNAP or SYSMDUMP/VMDUMP is actually taken | ||
depends on many factors, including the settings of the SNAPCTL | depends on many factors, including the settings of the <var>[[SNAPCTL_parameter|SNAPCTL]]</var> | ||
system parameter, the presence of DD cards or FILEDEFs for | system parameter, the presence of DD cards or FILEDEFs for | ||
CCASNAP or dump datasets, and the setting of SNAPLIM and the current | CCASNAP or dump datasets, and the setting of <var>[[SNAPLIM_parameter|SNAPLIM]]</var> and the current | ||
number of CCASNAPs already taken. | number of CCASNAPs already taken. | ||
| Line 28: | Line 28: | ||
<ul> | <ul> | ||
<li>An operator command, | <li>An operator command, | ||
that is, as a reply to the HALT message under OS | that is, as a reply to the <var>[[HALT_command|HALT]]</var> message under z/OS | ||
<li>A command typed on the Online virtual console under CMS | <li>A command typed on the Online virtual console under CMS | ||
</ul> | </ul> | ||
Latest revision as of 08:49, 29 July 2020
Note: This is a Sirius Mods-only command prior to Version 7.5 of Model 204.
The BUMPSNAP command is identical to the Model 204 BUMP command with the exception that a CCASNAP is taken for the user or users being BUMPed, if the user is in a BUMPable wait. When the BUMPSNAP command is issued, the following message is written to CCAAUDIT/CCAJLOG and is printed at the top of each page of CCASNAP:
MSIR.0661: Snap taken, user bumped by BUMPSNAP command
This can be useful in diagnosing a hung user situation where the error is believed to be a Model 204 internals problem. Whether or not a CCASNAP or SYSMDUMP/VMDUMP is actually taken depends on many factors, including the settings of the SNAPCTL system parameter, the presence of DD cards or FILEDEFs for CCASNAP or dump datasets, and the setting of SNAPLIM and the current number of CCASNAPs already taken.
The syntax of the BUMPSNAP command is identical to that of the BUMP command.
The BUMPSNAP command, like the BUMP command, allows BUMPing and SNAPping of more than one user with a single command. Generally, this is not what is desired with a BUMPSNAP command, so use caution when issuing a BUMPSNAP command that doesn't specify a user number (but instead specifies something more generic like a userid or a subsystem name or file), since this could result in a large number of snap dumps being taken. For most purposes, the BUMPSNAP command should simply be followed by the user number of the user for which a snap is desired.
The BUMPSNAP command can be issued as either of these:
- An operator command, that is, as a reply to the HALT message under z/OS
- A command typed on the Online virtual console under CMS