BUMP command: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Created page with "'''BUMP user_num''' This operator command requests that the equivalent of the Model 204 BUMP command be issued against the indicated user number. This command is useful if a...")
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
'''BUMP user_num'''
==Summary==
<dl>
<dt>Privileges
<dd>System administrator or operator
<dt>Function
<dd>Logs out a particular user or a set of users
</dl>
==Syntax==
<p class="syntax">BUMP  
    {[FORCE]
    <var class="term">userid</var> | <var class="term">usernumber</var>
    | ALL | FILE <var class="term">filename</var>
    | <b>SUBSYSTEM</b> <var class="term">subsysname</var> FROM <var class="term">location</var>
    | [QUEUEMANAGER | QM] <var class="term">qmname</var>
    | MODULE <var class="term">module-name</var>}
</p>
<b>Where:</b>
<table>
<tr>
<th><var>FORCE</var></th>
<td> specifies to interrupt users that are running an external module. Users that are not running an [[External_Call_Facility#External_Module_statement|external module]] are not affected by the FORCE option. If specified in combination with other options, the FORCE option must be the first option.</td>
</tr>
<tr>
<th>userid</th>
<td> is a character string that identifies the user who logged in to <var class="product">Model&nbsp;204</var>. All users who logged in under this user ID are logged out.</td>
</tr>
<tr>
<th>usernumber</th>
<td> is the number associated with a particular user.</td>
</tr>
<tr>
<th><var>ALL</var></th>
<td> are all current users.</td>
</tr>
<tr>
<th>filename</th>
<td> is the name of a <var class="product">Model&nbsp;204</var> file.</td>
</tr>
<tr>
<th>subsysname</th>
<td> is the name of a <var class="product">Model&nbsp;204</var> [[Application_Subsystem_development|application subsystem]]. To bump all local users of a [[PQO:_Overview_of_Parallel_Query_Option/204|Parallel Query Option/204]] remote service subsystem, use:
<p class="code">BUMP <b>SUBSYS</b>TEM <var class="term">subsysname</var> FROM <var class="term">location</var>
</p></td>
</tr>
<tr>
<th>qmname</th>
<td> is the name of queuemanager created with a <var>[[MQ/204_command_reference#DEFINE_QUEUEMANAGER:_Identifying_a_WebSphere_MQ_queue_manager|DEFINE QUEUEMANAGER]]</var> command using MQ/204 to support MQSeries.</td>
</tr>
<tr>
<th>module-name</th>
<td> specifies the particular external module whose users are logged off when using the [[External_Call_Facility|External Call Facility]].</td>
</tr>
</table>


This operator command requests that the equivalent of the [[Model 204]] <var>BUMP command</var> be issued against the indicated user number. This command is useful if a high priority user is looping in an Online, making it impossible for anyone else to do anything.
==Example==
 
<p class="code">BUMP 237
To &#x201C;bump&#x201D; user number 18, for example. issue the command:
</p>
 
==Usage notes==
BUMP 18
The BUMP command logs out of <var class="product">Model&nbsp;204</var>:
 
<ul>
Unlike the ''Model 204'' <var>BUMP command</var>, the operator <var>BUMP command</var> only accepts a single user number, and it does not accept userids or file names. To determine the user number of the running user, issue the [[MONITOR command]]. It is recommended that the MONITOR command be issued several times to ensure that a single user is indeed looping and that the performance problem is not simply the result of excess demand.
<li>
 
<p>All users of a <var class="product">Model&nbsp;204</var> login user ID</p>
If a loop situation is caused by a ''Model 204'' bug, it is possible that a <var>BUMP command</var> will fail to force the looping user off the system. In this case, it might be necessary to issue the [[RESTART Command|RESTART command]] to break the loop.
</li>
 
[[Category:Operator commands]]
<li>
<p>A particular user</p>
</li>
<li>
<p>All current users</p>
</li>
<li>
<p>All current users of a file</p>
</li>
<li>
<p>All users of a specified subsystem (except those in non-bumpable states such as back out)</p>
</li>
<li>
<p>All users on a specified queue</p>
</li>
<li>
<p>All users of a specified external module</p>
<p class="note"><b>Note:</b> Only users who are running the specified external module at the time the BUMP MODULE command is issued are bumped; subsequent users of the module are not affected. To prevent subsequent use of the module, use the EXTERNAL STOP statement.</p>
<p>The status flags displayed by the MONITOR command can indicate whether the user is bumped immediately.</p>
<p>User IDs, which are specified by the system manager, can be all-numeric strings. User numbers, which are supplied by <var class="product">Model&nbsp;204</var>, are always all-numeric. When an all-numeric string is specified in the BUMP command, <var class="product">Model&nbsp;204</var> first attempts to find a matching user ID. If no match is found, <var class="product">Model&nbsp;204</var> then assumes that the string refers to a user number.</p>
<p>Whenever a BUMP message is displayed, it is preceded by a header line as is shown:</p>
<p class="code">BUMP username HELLO
<b></b>*** M204.1124: 1 USER(S) SCHEDULED FOR BUMP
</p>
</li>
<li>
<p>The bumped user sees, if [[SYSOPT_parameter|SYSOPT]]=8 is not set: </p>
<p class="code">*** M204.1401: FORCED LOGOUT DUE TO BUMP
</p>
</li>
<li>
<p>If SYSOPT=8 is set, the bumped user sees no message from <var class="product">Model&nbsp;204</var> and is returned to the interface from which he came.</p>
</li>
</ul>
<p>An operator can enter a BUMP command in response to the outstanding reply generated by the HALT command. However, BUMP cannot be used to terminate Host Language Interface IFAM2 or IFAM4 threads.</p>
<p>After the BUMP command has been run, the system manager, system administrator, User 0, or operator who issued the command is informed of how many other users were affected.</p>
[[Category: System administrator commands]]
[[Category: Operator commands]]
[[Category:Commands]]

Latest revision as of 15:06, 7 February 2019

Summary

Privileges
System administrator or operator
Function
Logs out a particular user or a set of users

Syntax

BUMP {[FORCE] userid | usernumber | ALL | FILE filename | SUBSYSTEM subsysname FROM location | [QUEUEMANAGER | QM] qmname | MODULE module-name}

Where:

FORCE specifies to interrupt users that are running an external module. Users that are not running an external module are not affected by the FORCE option. If specified in combination with other options, the FORCE option must be the first option.
userid is a character string that identifies the user who logged in to Model 204. All users who logged in under this user ID are logged out.
usernumber is the number associated with a particular user.
ALL are all current users.
filename is the name of a Model 204 file.
subsysname is the name of a Model 204 application subsystem. To bump all local users of a Parallel Query Option/204 remote service subsystem, use:

BUMP SUBSYSTEM subsysname FROM location

qmname is the name of queuemanager created with a DEFINE QUEUEMANAGER command using MQ/204 to support MQSeries.
module-name specifies the particular external module whose users are logged off when using the External Call Facility.

Example

BUMP 237

Usage notes

The BUMP command logs out of Model 204:

  • All users of a Model 204 login user ID

  • A particular user

  • All current users

  • All current users of a file

  • All users of a specified subsystem (except those in non-bumpable states such as back out)

  • All users on a specified queue

  • All users of a specified external module

    Note: Only users who are running the specified external module at the time the BUMP MODULE command is issued are bumped; subsequent users of the module are not affected. To prevent subsequent use of the module, use the EXTERNAL STOP statement.

    The status flags displayed by the MONITOR command can indicate whether the user is bumped immediately.

    User IDs, which are specified by the system manager, can be all-numeric strings. User numbers, which are supplied by Model 204, are always all-numeric. When an all-numeric string is specified in the BUMP command, Model 204 first attempts to find a matching user ID. If no match is found, Model 204 then assumes that the string refers to a user number.

    Whenever a BUMP message is displayed, it is preceded by a header line as is shown:

    BUMP username HELLO *** M204.1124: 1 USER(S) SCHEDULED FOR BUMP

  • The bumped user sees, if SYSOPT=8 is not set:

    *** M204.1401: FORCED LOGOUT DUE TO BUMP

  • If SYSOPT=8 is set, the bumped user sees no message from Model 204 and is returned to the interface from which he came.

An operator can enter a BUMP command in response to the outstanding reply generated by the HALT command. However, BUMP cannot be used to terminate Host Language Interface IFAM2 or IFAM4 threads.

After the BUMP command has been run, the system manager, system administrator, User 0, or operator who issued the command is informed of how many other users were affected.

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=BUMP_command&oldid=117136"