Skip to content
CA Top Secret® for z/OS - 16.0
Documentation powered by DocOps

Terminal Locking

Last update June 19, 2015

The automatic terminal locking feature is available for TSO. Locking is enforced whenever a command (not subcommand) is about to be executed. If the amount of time since the last command execution exceeds the LTIME threshold for the user or the LOCKTIME of the facility, the terminal becomes locked.

CA Top Secret sees the time difference between command executions only. It does not see keystrokes or recognize when a user presses the Enter key. This is important for users who spend long periods of time in EDIT or SPF/EDIT. Use the timeout feature of your session manager if the LOCKTIME feature in the TSO does not meet you needs.

If a user has been in EDIT or SPF/EDIT, his terminal may lock when he ends the edit session. If this occurs, the user must enter the TSS UNLOCK command by switching to menu 6, or under TSO/E, on the menu command line.

Note: When TOP SECRET locks the terminal, TSO responds with a S806 abend.

A locked terminal can be logged off. Also, terminal locking does not interfere with the MVS timeout feature (S522 abend).

Was this helpful?

Please log in to post comments.

  1. Benjamin Burrows
    2017-12-28 05:20

    You really need to say what happens when LOCKTIME is set in FACILITY and LTIME is set at the ACID level: 1. LTIME, I believe, takes precedence, if it is present, so that LTIME could be set shorter or longer for special users, compared to the facility LOCKTIME standard. 2. What happens if LOCKTIME=0 or LTIME=0? 3. What is the default value of LOCKTIME, if not set in PARMFILE initialization?

    1. Kris Horgen
      2017-12-28 09:06

      Hi Ben,

      Thanks for checking in. Will look at tweaking the doc accordingly!