The key to a production environment is a startup member that is executed when a user signs on to CA Ideal. It contains the SET and RUN commands necessary to run the production application in a sheltered environment. You can establish this environment so that there is no CA Ideal command area (see the following example) and so that CA Ideal is totally transparent to the end user. The startup member is associated with the transaction ID and is specified in the TRNDATA= parameter of the SCF Transaction Table entry.
It executes for any user who specifies that transaction ID. The startup member overrides any signon member that can exist for a user who signs on to CA Ideal using the transparent signon.
The following example illustrates a production environment startup member for CICS:
MEM PROD
MEMBER:
SEQ DATA
000100 SEL SYS ORD
000200 SET CMD LINES 0
000300 SET CMD SEP N
000400 SET ENV ACCOUNT-ID ORDS
000500 SET RUN QUITIDEAL YES
000600 SET ENV FINAL-ID NONE
000700 SET RUN CLEAR RESHOW
000800 RUN ORDERS PROD
The commands are as follows:
Indicates that the ORD system is selected.
Suppresses the command region by specifying 0 command lines. This prevents the user from issuing any CA Ideal commands.
Suppresses the line that separates the command and message area from the display area. In addition to restricting the user from using CA Ideal commands, these two commands increase the screen size available for running production applications.
ORDS is designated as the transaction for which statistics are recorded (instead of SCFD, which is the default when IDLX is invoked). There must be a PCT entry for the ORDS transaction. You can model this entry from the SCFD PCT entry. (For tuning purposes, the priority assigned to ORDS can be higher or lower than SCFD.)
Note: This command is designed for use in CICS. It can be issued in batch, or it is ignored.
Issues an automatic OFF when the current RUN ends.
Does not schedule a CICS transaction when CA Ideal is signed off. This returns control directly to CICS and displays a blank screen.
Note: You can issue this command in batch but it is ignored.
The CLEAR key refreshes the current panel (instead of ending the RUN).
The ORDERS program is invoked with a RUN command. This eliminates the need for the end user to know the name of the program or the format of the RUN command. This also places the presentation area under the control of the application at the beginning of the session. Also, since only the PROD versions of programs, subprograms, and dataviews are run in this example, you can use it in a transported environment.
When the first user signs on using a transparent signon-ID, the start-up member is read from the IDDAT member library. The member is then compressed. Leading and trailing blanks are compressed from the member. All comments are dropped. However, multiple blanks between command words are not removed.
Some tips for making the most of this optimization are:
If the compressed member is less than 800 bytes, a CICS GETMAIN is issued for CICS. This eliminates I/O for subsequent transparent signons using that start-up member. To change the member, edit or delete it on the same CICS where the change is needed.
If the compressed member is more than 800 bytes, it is not built in core. If the member name is SIGNON and the user ID is the same as the user signing on, the member is not loaded into global storage.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|