This article describes the different functions of CICS transactions designated as ACCOUNT-IDs and FINAL-IDs in CA Ideal for CA Datacom applications.
ACCOUNT-IDs are useful in a production CICS region to provide separate user-specified CICS transactions. Without ACCOUNT-IDs, all CA Ideal transactions and transaction DDOL are executing as SCFD after signon. Using ACCOUNT-IDs within CA Ideal applications allows CICS performance analysis packages or transaction accounting packages to isolate transactions for charge-back and resource consumption analysis.
The transaction definition for SCFD invokes SC00DISP, the Session Control Facility Dispatcher program. Additional transaction definitions can be specified as any valid 4 characters (IBM recommends transactions IDs do not begin with C). An ACCOUNT-ID transaction must have a TRANSACTION definition in CICS with the same options as the SCFD entry. An entry in SC00TRAN, the SCF Transaction Table, is not required for an ACCOUNT-ID. Like the SCFD transaction, an ACCOUNT-ID is a synchronous CICS task attached to a terminal invoking SC00DISP, the SCF dispatcher program. ACCOUNT-ID transactions must only invoke SC00DISP.
The dispatcher transaction for an application is designated by the following command:SET ENVIRONMENT ACCOUNT-ID xxxx
This command can be executed from the CA Ideal command line or a startup MEMBER. Another method for designating a user-defined dispatcher transaction is to code the following statement in an CA Ideal program:SET $ACCOUNT-ID = 'xxxx'
When the dispatcher transaction is designated from within the application code, it becomes effective with the next TRANSMIT statement (a CICS transaction boundary).
FINAL-IDs may be designated as the next transaction to execute at the end of an CA Ideal session. A FINAL-ID can be any valid CICS synchronous transaction that could also be invoked directly from the terminal. Using FINAL-IDs within an CA Ideal application provides the ability to create a smooth transition from one CA Ideal application to another, as well as to COBOL and Assembler CICS applications.
FINAL-IDs invoking CA Ideal applications must be Transparent Signon transactions that invoke SC00INIT, the SCF initialization program. Transparent Signons must have an entry in SC00TRAN, the SCF Transaction Table, and are defined to CICS as a TRANSACTION invoking the program SC00INIT.
A FINAL-ID can never be a transaction invoking SC00DISP (i.e. SCFD or an ACCOUNT-ID). A FINAL-ID is always a terminal-based transaction for which no input parameters are required. A FINAL-ID can only be invoked from a terminal-based session. It is not valid to useSET $FINAL-ID from within an CA Ideal program that has been invoked by the INITIATE statement to run asynchronously.
A FINAL-ID can be designated by the following command:SET ENVIRONMENT FINAL-ID xxxx
This command can be executed from the command line or a startup MEMBER. Like ACCOUNT-ID, there is also a PDL statement to schedule the next transaction after an CA Ideal session:SET $FINAL-ID = 'xxxx'
When the CA Ideal session ends, either at the end of a RUN with the command SET RUN QUITIDEAL YES in effect or when OFF has been entered from the command line, the FINAL-ID transaction will be started at the current terminal. FINAL-ID may also be set to the keyword NONE in order to have a blank screen at the end of an CA Ideal session, instead of getting the Signoff panel.
The CA Ideal command DISPLAY PCT will show all the CICS transactions that invoke a SCF module such as SC00INIT, SC00DISP or SC00SAST and will indicate whether or not there is a corresponding entry in SC00TRAN.
For additional information on ACCOUNT-ID and FINAL-ID see the CA Ideal for CA Datacom Administration Guide.