27.12.2012 Views

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

z/VM: CP Commands and Utilities Reference - z/VM - IBM

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

FORCE<br />

Usage Notes<br />

Responses<br />

1. FORCE may not be able to cause the logoff of a hung-up user, nor of a user<br />

with I/O outst<strong>and</strong>ing, because either of these conditions may prevent completion<br />

of the LOGOFF function. As an alternative, the DISCONNECT option may be<br />

used to disassociate the user ID from its terminal, thus freeing up the device.<br />

2. If the user’s virtual machine is hung waiting for a device which is not operational<br />

or the system operator can determine the I/O device involved <strong>and</strong> either make<br />

that device ready or enter a HALT comm<strong>and</strong>; this allows the user to continue<br />

operation or be forced from the system. (Use QUERY to determine the status of<br />

all or selected devices) For more information see the description of the HALT<br />

comm<strong>and</strong>.<br />

3. The disconnect performed by the FORCE comm<strong>and</strong> may take significant time to<br />

complete because of the attempt made to process the disconnect even in the<br />

case of a hung terminal.<br />

4. If a user is force disconnected while a read is posted from the user’s virtual<br />

machine or from <strong>CP</strong>, <strong>and</strong> that user does not have a logged on secondary user,<br />

the user then has some installation-defined grace period (usually 15 minutes) in<br />

which to log on or else his virtual machine is automatically logged off.<br />

5. Users who are being forced from the system will be given QUICKDSP<br />

designation to expedite the logoff of the user.<br />

6. If the user who is being forced from the system has an open RDR file <strong>and</strong> the<br />

user’s virtual reader is spooled NOHOLD <strong>and</strong> NOKEEP, the open file will be<br />

retained on the user’s RDR queue in USER hold status.<br />

7. If none of the WITHIN, BY, <strong>and</strong> IMMEDIATE options are specified, <strong>and</strong> if the<br />

default signal timeout interval is set, it is used to delay the FORCE <strong>and</strong> give the<br />

guest system an opportunity to terminate. Refer to “SET SIGNAL” on page 1388<br />

for additional information about this behavior.<br />

Response 1:<br />

{LOGOFF } AT hh:mm:ss zone weekday mm/dd/yy {DISCONNECT} {userid}<br />

In addition, if logoff has been selected, then this response will accompany the<br />

normal accounting message produced at logoff.<br />

LOGOFF<br />

DISCONNECT<br />

indicates whether the virtual machine was logged off or disconnected.<br />

hh:mm:ss<br />

identifies the current time in hours:minutes:seconds.<br />

zone<br />

identifies the time zone.<br />

442 z/<strong>VM</strong>: <strong>CP</strong> <strong>Comm<strong>and</strong>s</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Reference</strong><br />

weekday<br />

identifies the current day of the week.<br />

mm/dd/yy<br />

identifies the current date in month/day-of-month/year format.<br />

SYSTEM<br />

userid<br />

indicates who forced the logoff or disconnect your virtual machine. If you were<br />

forced by another user, <strong>and</strong> not the system, that user’s userid appears in the<br />

message.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!