Asynchronous Execution › Setting Up an Asynchronous Execution

Setting Up an Asynchronous Execution

To use the SCASTRAN feature, the SCF Asynchronous Transaction Table must be assembled and linked. The entries in SCASTRAN specify the CA Ideal program to be run.

An entry in SCASTRAN is defined using the following parameters:

• TRANID=xxxx
  • xxxx-Four-character transaction-id defined in CICS with TWASIZE=64 to invoke program SC00NATD.
• TRNDATA=sssppppppppvvvvx
  • sss-Three-character SYSTEM name where the program resides.
  • pppppppp-Eight-character program name. The name must be padded with blanks if less than eight characters.
  • vvvv-Four-digit version number or PROD for production status programs.
  • x- Code N indicates that the RUN PARAMETER clause is not used when the RUN command for the program is executed, even if data is specified in the FROM option of the EXEC CICS START command invoking the asynchronous run (for example, when starting a process from MQSeries). The default value is Y.

  Note: If no FROM data is specified in the EXEC CICS START command, no run parameter data is expected.

• DFLTUSR=uuu
  • uuu-Three-character user ID that runs the program. This user ID must be defined with specific authorization for the system specified in the TRNDATA parameter. This applies even if the user ID has ADMINISTRATOR authority. If a user has a SIGNON member, it is executed prior to the RUN. This allows SET RUN commands to be processed for the environment.

A CICS transaction definition must be added for the transaction defined in the SCASTRAN entry. Transaction definitions must specify PROGRAM(SC00NATD) and TWASIZE(64). The command DISPLAY PCT will verify if the transaction has a CICS definition and the corresponding SCASTRAN entry.

Any messages other than internal errors (which are always logged in ADRLOG) are not available for an asynchronous run. If there are errors in a user signon member that fail before the program executes, there is no place to send an error or informational message since there is no terminal. Programs that run asynchronously are not attached to a terminal; therefore any TRANSMIT or NOTIFY statements are invalid for this type of run.

RUNLIST and REPORT output directed to destination LIBRARY will be routed to the user-id specified by the DFLTUSR parameter in the SCASTRAN entry.

This asynchronous run is similar to a run started within CA Ideal by the INITIATE statement. A single 01-level run parameter can be passed to the program (a group field cannot be passed). The run parameter is limited to a maximum of 43 characters. Internally, the RUN command is executed with the parameter option, which leaves a maximum of 43 characters for the actual run parameter data.

To start a transaction that executes SC00NATD, the CICS 'FROM' option on the EXEC CICS START command can be used to specify the data for the CA Ideal run parameter. If the length of this data is more than 43 characters, the option to ignore the run parameter can be specified in the SCASTRAN entry (TRNDATA='sssppppppppvvvvN').

The QUITIDEAL option may not be used for asynchronous runs. If the QUITIDEAL option has been set to YES for the site, then there must be a SIGNON member for the DFLTUSR user-id that contains SET RUN QUITIDEAL NO. The command DISPLAY SESSION RUN will show the QUITIDEAL option.