

Special Features and Customization Tasks › Control Application Sessions with OPENGATE › Build Control Users
Build Control Users
To build a control user for an application controlled by OPENGATE
Note: You define a control user as you would any other user. For more information, see the Administration Guide. You must use a defined, not dynamic, control user ID for OPENGATE.
- Create the control user ID:
- Specify a user ID identical to the name of your control ACL/E program for the application.
- Specify NONE in the Security system field on the Userid Maintenance Detail Panel.
- Specify NONE in the Transfer option field on the Userid Maintenance Detail Panel.
- Define a session for the controlled application:
- Access the Userid Maintenance Table Entry List and define a session for the application.
Note: If multiple users will be starting and/or ending sessions concurrently to the controlled application, you can define additional sessions for the application to handle the concurrent session setup/cleanup activity. If a user tries to access the application while all of the control user's sessions are busy, the control ACL/E program will be scheduled on the session that has been processing for the longest amount of time (the session that should free up first).
- Access the Userid Maintenance Detail Panel and enter Y in the Start at signon field. This causes the session to start automatically when the control user is signed on to CA TPX.
- Create and define a startup ACL/E program for the session:
- Create a startup ACL/E program to perform initialization on the application before session setup and/or cleanup occurs (for example, signing on to IMS).
Note: The startup ACL/E program is not the same as the control ACL/E program. A startup ACL/E program is necessary only if the application requires initialization before session setup and/or cleanup activity can be performed.
- Enter the name of the program in the Startup ACL field on the Userid Maintenance Detail Panel.
Copyright © 2013 CA.
All rights reserved.
 
|
|