LOGWHO command - Revision history

Tbullock: Leading zeros

2015-12-09T20:10:46Z

Leading zeros

← Older revision		Revision as of 20:10, 9 December 2015
Line 27:		Line 27:
	For Parallel Query Option/204 (PQO) users, the LOGWHO display depends on whether it is issued for a client or server. Issued at a client node, LOGWHO shows the remote files currently open. Issued at a server node for a service thread, the display includes identification of client users and any service thread subsystem.		For Parallel Query Option/204 (PQO) users, the LOGWHO display depends on whether it is issued for a client or server. Issued at a client node, LOGWHO shows the remote files currently open. Issued at a server node for a service thread, the display includes identification of client users and any service thread subsystem.
	<p>		<p>
	The format of the PQO display follows. The fields are left-justified and blank-filled, except for nn, the user number, which is right-justified, ~~blank~~-filled, and in a field of two digits for numbers 0 through 99 or of as many digits necessary for larger numbers. <b>bb</b> is two blanks.</p>		The format of the PQO display follows. The fields are left-justified and blank-filled, except for nn, the user number, which is right-justified, zero-filled, and in a field of two digits for numbers 0 through 99 or of as many digits necessary for larger numbers. <b>bb</b> is two blanks.</p>
	<p class="code">USER nn userid<b><i>bb</i></b>termid<b><i>bb</i></b>file1<b><i>bb</i></b>file2...<b><i>bb</i></b>		<p class="code">USER nn userid<b><i>bb</i></b>termid<b><i>bb</i></b>file1<b><i>bb</i></b>file2...<b><i>bb</i></b>
	[CLNT:<b><i>bb</i></b>mmmmm<b><i>bb</i></b>ON<b><i>bb</i></b>clntname] [APSY: apsyname]		[CLNT:<b><i>bb</i></b>mmmmm<b><i>bb</i></b>ON<b><i>bb</i></b>clntname] [APSY: apsyname]

JAL: /* Usage notes */

2013-06-24T21:48:46Z

Usage notes

← Older revision		Revision as of 21:48, 24 June 2013
Line 21:		Line 21:
	<p>The LOGWHO command lists the user IDs of all users currently logged in to <var class="product">Model 204</var>. LOGWHO also lists each SNA Communications Server (formerly VTAM) terminal that is in session with <var class="product">Model 204</var> even if no user is currently logged in through that thread; in this case, NO ACCOUNT appears in the user ID field of the output.</p>		<p>The LOGWHO command lists the user IDs of all users currently logged in to <var class="product">Model 204</var>. LOGWHO also lists each SNA Communications Server (formerly VTAM) terminal that is in session with <var class="product">Model 204</var> even if no user is currently logged in through that thread; in this case, NO ACCOUNT appears in the user ID field of the output.</p>
	<p>For each user ID listed, LOGWHO provides a terminal identification field if the SNA Communications Server or IUCV access method is being used by that thread. LOGWHO also displays the names of any files opened by each user ID.</p>		<p>For each user ID listed, LOGWHO provides a terminal identification field if the SNA Communications Server or IUCV access method is being used by that thread. LOGWHO also displays the names of any files opened by each user ID.</p>
	<p>LOGWHO also lists process and processgroup names.</p>		<p>
	~~<p>~~For Parallel Query Option/204 (PQO) users, the LOGWHO display depends on whether it is issued for a client or server. Issued at a client node, LOGWHO shows the remote files currently open. Issued at a server node for a service thread, the display includes identification of client users and any service thread subsystem. </p>		LOGWHO also lists process and processgroup names.</p>
	~~<p>~~The format of the PQO display follows. The fields are left-justified and blank-filled, except for nn, the user number, which is right-justified, blank-filled, and in a field of two digits for numbers 0 through 99 or of as many digits necessary for larger numbers. <b>bb</b> is two blanks.</p>
			====LOGWHO for PQO====
			For Parallel Query Option/204 (PQO) users, the LOGWHO display depends on whether it is issued for a client or server. Issued at a client node, LOGWHO shows the remote files currently open. Issued at a server node for a service thread, the display includes identification of client users and any service thread subsystem.
			<p>
			The format of the PQO display follows. The fields are left-justified and blank-filled, except for nn, the user number, which is right-justified, blank-filled, and in a field of two digits for numbers 0 through 99 or of as many digits necessary for larger numbers. <b>bb</b> is two blanks.</p>
	<p class="code">USER nn userid<b><i>bb</i></b>termid<b><i>bb</i></b>file1<b><i>bb</i></b>file2...<b><i>bb</i></b>		<p class="code">USER nn userid<b><i>bb</i></b>termid<b><i>bb</i></b>file1<b><i>bb</i></b>file2...<b><i>bb</i></b>
	[CLNT:<b><i>bb</i></b>mmmmm<b><i>bb</i></b>ON<b><i>bb</i></b>clntname] [APSY: apsyname]		[CLNT:<b><i>bb</i></b>mmmmm<b><i>bb</i></b>ON<b><i>bb</i></b>clntname] [APSY: apsyname]
Line 30:		Line 34:
	<table>		<table>

	<tr> <th>		<tr class="head">
	<p>Term~~</p>~~		<th>Term</th> <th>Thread</th> <th>Meaning</th> </tr>
	</th> <th>
	<p>Thread ~~</p>~~
	</th> <th>
	<p>Meaning~~</p>~~
	</th> </tr>

	<tr> <th rowspan="2">		<tr> <th rowspan="2">
Line 118:		Line 117:
	<p>Name of the subsystem into which service thread is logged, if any</p>		<p>Name of the subsystem into which service thread is logged, if any</p>
	</td> </tr>		</td> </tr>

	</table>		</table>
	<p>In addition to the list of regular user IDs, LOGWHO prints a list of terminal lines that have encountered severe I/O errors and have been shut down (dead users). Also printed is a list of users to be reactivated (hardwired terminals that have been temporarily shut down because of I/O errors and that can be reactivated with the REACTIVATE command).</p>		<p>
	<p>To execute the LOGWHO command, reply STATUS to the outstanding HALT message.</p>		In addition to the list of regular user IDs, LOGWHO prints a list of terminal lines that have encountered severe I/O errors and have been shut down (dead users). Also printed is a list of users to be reactivated (hardwired terminals that have been temporarily shut down because of I/O errors and that can be reactivated with the REACTIVATE command).</p>
			<p>
			To execute the LOGWHO command, reply STATUS to the outstanding HALT message.</p>

	====Sending LOGWHO output to the USE data set====		====Sending LOGWHO output to the USE data set====
	<p>If there is an open USE data set, the LOGWHO command output is directed to it. See [[RESET COMMAND command\|RESET COMMAND: Control USE data set support]] for a discussion of how to direct the output.</p>		<p>
			If there is an open USE data set, the LOGWHO command output is directed to it. See [[RESET COMMAND command\|RESET COMMAND: Control USE data set support]] for a discussion of how to direct the output.</p>
	[[Category: System administrator commands]]		[[Category: System administrator commands]]
	[[Category:Commands]]		[[Category:Commands]]

Dme: /* Syntax notes */

2013-06-24T18:00:02Z

Syntax notes

← Older revision		Revision as of 18:00, 24 June 2013
Line 10:		Line 10:
	</p>		</p>
	==Syntax notes==		==Syntax notes==
	LOGWHO ~~cannot~~ be issued from within a procedure.		LOGWHO <b>can</b> be issued from within a procedure - this has been the case since V6R1, or perhaps longer.

	==Example==		==Example==
	<p class="code">LOGWHO		<p class="code">LOGWHO

Alex: Automatically generated page update

2013-02-28T01:05:09Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>System administrator
<dt>Function
<dd>Lists the user IDs of all users who are currently logged in to <var class="product">Model 204</var>
</dl>
==Format==
LOGWHO

==Syntax notes==
LOGWHO cannot be issued from within a procedure.
==Example==
LOGWHO
USER 0 SUPERKLUGE
USER 1 CCA CENSUS CARS
USER 3 DPH HEALTH

==Usage notes==
The LOGWHO command lists the user IDs of all users currently logged in to <var class="product">Model 204</var>. LOGWHO also lists each SNA Communications Server (formerly VTAM) terminal that is in session with <var class="product">Model 204</var> even if no user is currently logged in through that thread; in this case, NO ACCOUNT appears in the user ID field of the output.
For each user ID listed, LOGWHO provides a terminal identification field if the SNA Communications Server or IUCV access method is being used by that thread. LOGWHO also displays the names of any files opened by each user ID.
LOGWHO also lists process and processgroup names.
For Parallel Query Option/204 (PQO) users, the LOGWHO display depends on whether it is issued for a client or server. Issued at a client node, LOGWHO shows the remote files currently open. Issued at a server node for a service thread, the display includes identification of client users and any service thread subsystem. 
The format of the PQO display follows. The fields are left-justified and blank-filled, except for nn, the user number, which is right-justified, blank-filled, and in a field of two digits for numbers 0 through 99 or of as many digits necessary for larger numbers. bb is two blanks.
USER nn useridbbtermidbbfile1bbfile2...bb
[CLNT:bbmmmmmbbONbbclntname] [APSY: apsyname]

where: 
<table>

<tr> <th>
Term
</th> <th>
Thread 
</th> <th>
Meaning
</th> </tr>

<tr> <th rowspan="2">
nn
</th> <td>
Client
</td> <td>
User thread number 
</td> </tr>

<tr> <td>
Service
</td> <td>
User thread number of the service thread
</td> </tr>

<tr> <th rowspan="2">
userid
</th> <td>
Client
</td> <td>
User login ID
</td> </tr>

<tr> <td>
Service
</td> <td>
Client user's login ID
</td> </tr>

<tr> <th rowspan="2">
termid
</th> <td>
Client
</td> <td>
User terminal ID or z/VM machine name
</td> </tr>

<tr> <td>
Service
</td> <td>
Client's node name as specified on local DEFINE PROCESSGROUP command REMOTEID parameter
</td> </tr>

<tr> <th rowspan="2">
file1, file2,...
</th> <td>
Client
</td> <td>
Names of any open local files, and
Names of open remote files, using the full remote file specification (filename AT location)
</td> </tr>

<tr> <td>
Service
</td> <td>
Names of any open local files
</td> </tr>

<tr> <th>
mmmmm 
</th> <td>
Service
</td> <td>
User number of the client thread currently using the service thread
</td> </tr>

<tr> <th>
clntname
</th> <td>
Service
</td> <td>
Client User 0 LOCATION parameter value
</td> </tr>

<tr> <th>
apsyname
</th> <td>
Service
</td> <td>
Name of the subsystem into which service thread is logged, if any
</td> </tr>

</table>
In addition to the list of regular user IDs, LOGWHO prints a list of terminal lines that have encountered severe I/O errors and have been shut down (dead users). Also printed is a list of users to be reactivated (hardwired terminals that have been temporarily shut down because of I/O errors and that can be reactivated with the REACTIVATE command).
To execute the LOGWHO command, reply STATUS to the outstanding HALT message.
====Sending LOGWHO output to the USE data set====
If there is an open USE data set, the LOGWHO command output is directed to it. See [[RESET COMMAND command|RESET COMMAND: Control USE data set support]] for a discussion of how to direct the output.
[[Category: System administrator commands]]
[[Category:Commands]]