CICS/Timeout enhances security and reduces resource consumption by automatically logging off or signing off inactive users, even those running conversational tasks. Time intervals may be specified by terminal-id, net name or USERID, so you can control how long each user has to be inactive before he is signed off or logged off. If a terminal with a conversational task is inactive, you can have CICS/Timeout abend the task before signing or logging the terminal off.
Your auditors will like the fact that unattended terminals are less vulnerable to unauthorized use. Users who dial in from remote locations can also be logged off, saving on long distance charges.
With CICS/Timeout specific transactions, userids and/or operator ids can be excluded from time out. Specifying terminals for timeout or exclusion from timeout is made easy by use of terminal, net name, USERID, operator id, or transaction ranges and/or generic representations.
CICS/Timeout can be started automatically by a PLT entry or invoked at anytime by a terminal operator with administrator authority. You may have it start monitoring immediately or specify a time of day for it to start. You can also specify a time of day for it to automatically disable.
An audit trail is sent to the console and CSMT log showing when CICS/Timeout is turned on or off, and whenever a terminal is signed off or logged off by CICS/Timeout. Depending on your preference, different levels of detail can be displayed with each message.
By using the CICS/Timeout sign off function and the display of active users, you can improve security and find out who is using CICS and what transactions they are using. When you want to shut CICS down, you can easily see who is still on the system without having to call each department.
When you need to do a new copy on a CICS program or close a CICS file, CICS/Timeout can show all terminals using the transaction(s) which would be affected. Those users can be notified to avoid using the transaction for a few minutes. CICS/Timeout shows the transaction whether it is active or pending (NEXTTRAN id).
Besides logging or signing off terminals, additional actions can also be taken when a terminal is timed out. They include deleting TS Queues and starting special cleanup transactions. Actions can vary depending on the transaction being timed out. All of this is accomplished online and can be modified at any time.