Previous Topic: Initiate Logging on Your TerminalNext Topic: Initiate Logging on Another Terminal


Log Another Terminal

If you type O on the Log Options Menu or L.O on the Primary Options Menu, CA Verify for VTAM displays the Other Terminal Log menu.

 ----------------------------  OTHER TERMINAL LOG  ---------------------11:20:10  ENTER COMMAND ===>                                                           L2                                                                                   LOG TEST STREAM AS:                                                                DDNAME      ===> TCADS                                                           APPLICATION ===>                                                                 MEMBER      ===>                                                                 VERSION     ===> 001                                                                                                                                            DESCRIPTION ===>                                                                             ===>                                                                             ===>                                                                                                                                                  TERMINAL TO BE LOGGED    ===>                                                    STOP OPTION              ===> DISC       (DISC, MAN, PF__, PA_,OR CLEAR)         PROCESS WITH RULES       ===> N          (Y/N)                                   TEST STREAM PROTECTION   ===>            (R-READ W-WRITE P-PRINT)                LOG INPUT SCREENS ONLY   ===> N          (Y/N)                                   EXTEND TEST STREAM       ===> N          (Y/N)                                   VIRTUAL TERMINAL         ===>            (TO USE A SPECIFIC VIRTUAL TERMINAL)    INTERRUPT SESSION        ===> QUEUE      (NO, QUEUE, REQUEST, UNCOND, OR FORCE)  RULESET NAME:                                                                                                                                                     F1-HELP        F3-END        F4-RETURN                                        

This menu is identical to the Single Terminal Log menu except for two additional fields: Terminal to be Logged, and Interrupt Session. Also, the Stop option is interpreted differently and the Process With Rules field only applies certain rule actions.

TERMINAL TO BE LOGGED

The name of the terminal to be logged. If the terminal is in use by a user, logging will not begin until the user exits from CA Verify for VTAM.

STOP OPTION

How logging will be terminated. See the Logging Your Terminal section for an explanation of the options.

Remember that the Stop option you select applies to the terminal being logged, not to your terminal. For example, if you select PF12, the operator of the terminal being logged must press PF12 to terminate logging. If the operator at that terminal is unaware of the logging, select MAN as the Stop option. Then you can use the Inquiry function to terminate logging.

PROCESS WITH RULES

If Y is typed in this field and L.O is specified, application and user rule actions are applied, while terminal rule actions are ignored.

INTERRUPT SESSION

If the terminal to be logged is already in a session, this option determines the type of deactivation that should occur to terminate this session.

No

Do not interrupt the current session and do not queue a session for the terminal. Logging will not begin until the user at the terminal to be logged ends the current session and logs onto CA Verify for VTAM.

Queue

Do not interrupt the current session. Logging will begin when the current session ends. This is the default.

Request

Request that the application currently in session with the terminal terminate the session. The application may deny this request.

Uncond

Instruct the application currently in session with the terminal that it must terminate the session. CA Verify for VTAM waits for the application to formally terminate the session before beginning to log the terminal.

Force

Force termination of the session. Generally, this type of deactivation is not recommended; however, it may be advisable for terminals in sessions that do not terminate when the Request or Uncond parameters are in effect.

The default for this option is specified at installation. The five parameters represent five levels of interruption, with No as the lowest level and Force as the highest. Only a security administrator can specify a higher level of interruption on this menu than the installation default.

For example, if the installation default is Uncond, users (other than a security administrator) can change the parameter to No, Queue, or Request, but not to Force.