Guardian User's Guide

Managing Users and Security
Guardian User’s Guide—425266-001
16-30
Task 6: Check, Stop, and Restart Terminal
Communication Lines
Task 6: Check, Stop, and Restart Terminal Communication Lines
If a user still has no TACL access after you have performed Tasks 1 through 5 of this
subsection, you should check and possibly stop and restart the user’s terminal
communication line.
1. Check the user’s terminal communication line.
a. Make sure you are logged on as a super-group user (255,n).
b. Run the SCF utility.
4> SCF
c. At the SCF prompt, ssume the user’s terminal line name:
-> ASSUME LINE $line
line is the terminal line name, and is the same as the first component of the
user’s terminal name; for example, $JT1.
d. Assume the subdevice name of the user’s terminal:
-> ASSUME SU #subdevice
subdevice is the subdevice name, and is the same as the second component
of the user’s terminal name; for example, #J01.
e. Check the status of the line and subdevice:
-> STATUS
The STATE display appears indicating whether the terminal communication
line is started or stopped.
•
If the STATUS command reports STARTED, the terminal communication
line is working. You should follow your local procedure for problem
reporting and escalation.
•
If the STATUS command reports STOPPED, the terminal communication
line is not working. Proceed to Step 2.
2. Stop the terminal communication line and subdevice.
-> ABORT
3. Restart the line and subdevice.
-> START
Caution. The ABORT command will stop the subunit #subdevice when a subunit is assumed
with the ASSUME command. Aborting a line will usually affect other users connected to
subunits associated with the line, so it is not usually done unless all subunits (subdevices) on a
particular line are being affected by a problem.