BUMPSNAP command: Difference between revisions
m (1 revision) |
m (1 revision) |
||
| Line 1: | Line 1: | ||
The BUMPSNAP command is identical to the [[Model 204]] <var>BUMP</var> command | The <var>BUMPSNAP</var> command is identical to the [[Model 204]] <var>BUMP</var> command | ||
with the exception that a CCASNAP is taken for the user or users | with the exception that a CCASNAP is taken for the user or users | ||
being BUMPed. | being BUMPed. | ||
| Line 10: | Line 10: | ||
number of CCASNAPs already taken. | number of CCASNAPs already taken. | ||
The syntax of the BUMPSNAP command is identical to that of the BUMP | The syntax of the <var>BUMPSNAP</var> command is identical to that of the BUMP | ||
command, so the [[Model 204 Command Reference Manual]] should be consulted for more details. | command, so the [[Model 204 Command Reference Manual]] should be consulted for more details. | ||
The BUMPSNAP command, like the <var>BUMP</var> command, allows BUMPing and SNAPping | The <var>BUMPSNAP</var> command, like the <var>BUMP</var> command, allows BUMPing and SNAPping | ||
of more than one user with a single command. | of more than one user with a single command. | ||
Generally, this is not what is desired with a BUMPSNAP command, so use caution | Generally, this is not what is desired with a <var>BUMPSNAP</var> command, so use caution | ||
when issuing a BUMPSNAP command that doesn't specify a user number | when issuing a <var>BUMPSNAP</var> command that doesn't specify a user number | ||
(but instead specifies something more generic like a userid or a subsystem name | (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. | 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 | For most purposes, the <var>BUMPSNAP</var> command should simply be followed by the | ||
user number of the user for which a snap is desired. | user number of the user for which a snap is desired. | ||
The BUMPSNAP command can be issued as either of these: | The <var>BUMPSNAP</var> command can be issued as either of these: | ||
<ul> | <ul> | ||
<li>An operator command, | <li>An operator command, | ||
Revision as of 21:12, 27 June 2011
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. 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, so the Model 204 Command Reference Manual should be consulted for more details.
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 OS/390
- A command typed on the Online virtual console under CMS