CICS LOCKTIME And OPTIME Settings

book

Article ID: 49604

calendar_today

Updated On:

Products

CA Cleanup CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Top Secret CA Top Secret - LDAP CA Top Secret - VSE

Issue/Introduction

Description:

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

Solution:

LOCKTIME is a Facility parameter:

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 lockout users working in the CICS TOR region after 30 minutes.

OPTIME is on individual ACID or DFLTUSER. Adding a non-zero OPTIME to 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 these fields.

CA-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.

Environment

Release:
Component: AWAGNT