CICS LOCKTIME And OPTIME Settings In Top Secret

book

Article ID: 49604

calendar_today

Updated On:

Products

CA Cleanup CA Web Administrator for Top Secret CA Top Secret CA Top Secret - LDAP

Issue/Introduction

What is the difference between LOCKTIME and OPTIME which are CICS timeout related settings?

Environment

Release:
Component: AWAGNT

Resolution

LOCKTIME is a Facility parameter in Top Secret:

For example TSS MODI FAC(CICSPROD):

TSS9550I FACILITY DISPLAY FOR CICSPROD
TSS9551I INITPGM=DFH ID=C TYPE=004
TSS9554I UIDACID=8 LOCKTIME=030 DEFACID=*NONE* KEY=8

This will lock the user's terminal in the CICS TOR region after 30 minutes of inactivity. The user will need to enter their password to resume the session.

OPTIME can be added to an individual user's ACID, a profile ACID, or the CICS default user (DFLTUSER= in the CICS System Initialization Table):

TSS ADD(acid) OPTIME(hhmm)

Where 'hhmm' is the length of time of inactivity before the user should be signed off. (For example, TSS ADD(acid) OPTIME(30) says after 30 minutes of inactivity, the signoff will be driven.)

Adding a non-zero OPTIME to the CICS DFLTUSER gives a default value for OPTIME to any user who does not have a non-zero OPTIME already assigned:

OPTIME controls the period of time allowed before CICS considers a terminal user to be "timed-out". The action taken by CICS depends on a CICS parameter, SIGNOFF, which is specified in the TYPETERM definition. See the IBM documentation for more information about the use and setting of this field.

Top Secret provides the OPTIME field to support IBM CICS TIMEOUT functionality. When the user signs on, CA Top Secret places the OPTIME value into the user's TCTTE. CICS then scans the idle time for each terminal. When OPTIME/TIMEOUT is exceeded, CICS will take action based on the TYPETERM SIGNOFF parameter associated with the user's terminal.

SIGNOFF=YES will signoff the user but not log them off CICS.
SIGNOFF=LOGOFF will sign the user completely off CICS.