Inserting a Transaction Element

A TRANSACT name is required and must be unique. The naming conventions are the same as for an IMSGEN.

The APPLCTN parameter is required unless the transaction associated with the PSB is defined to a remote system. The PSB name can be a PSB created during an IMSGEN, one added previously by a DELTA List execution, or one added during the execution of the current list.

The DELTA List edit routine does not reject the insertion or revision of a transaction if the name of the PSB is missing. If the PSB name is required (because the transaction is defined to the local IMS system) and you do not supply it, DELTA List Check or Executeprocessing will fail.

These parameters are the same as for a normal IMSGEN when defining a TRANSACT. Because these fields are validated at entry, certain entries may be rejected, even though they may appear valid. For example, the INQUIRY(2) field cannot be set to NO unless the INQUIRY(1) field has previously been set to YES and the SPA(1) field has been set to 0.

Specify NONE, which is the default, to indicate that no parallel processing is allowed. Specify 0 through 32767 to indicate that parallel processing is allowed.

FPATH is a required parameter with a YES or NO specification. It is equivalent to the FPATH keyword parameter of the TRANSACT macro used during an IMSGEN. It indicates whether the transaction can be processed by the Fast Path feature of IMS.

Fast Path transactions must be single segment input, response mode, non-MSC remote, and non-conversational. These transactions may not currently have any messages on the message queue and a Fast Path route code must exist with a route code name identical to the transaction code.

The Fast Path status of the transaction will be one of the following: non-Fast Path, Fast Path potential, or Fast Path exclusive. The status selected depends in part on whether the PSB referenced is Fast Path.

• Non-Fast Path: Both the APPLCTN and TRANSACTION specified FPATH=NO.
• Fast Path potential: The APPLCTN specified FPATH=NO and the TRANSACTION specified FPATH=YES.
• Fast Path exclusive: The APPLCTN (PSB) specified FPATH=YES. In this case, the TRANSACTION can specify FPATH=YES or FPATH=NO.

DELTA IMS automatically sets the sync point per transaction (MODE=SNGL) and recoverable transaction options for a Fast Path transaction.

The FPSIZE parameter specifies the Fast Path EMH buffer size. It corresponds to the FPATH=YES parameter in the IMS TRANSACT macro. If FPSIZE is greater than zero, FPATH=YES is implied.

The MODE parameter can be set to YES (SNGL) or NO (MULT). The default is NO(MULT). IMS requires MODE=SNGL for conversational and wait-for-input (WFI) transactions; therefore, if a conversational or WFI transaction is added via DELTA IMS, MODE=SNGL is forced, regardless of what is specified in the MODE field.

These parameters are the same as for a normal IMSGEN when defining a TRANSACT. Because these fields are validated at entry, certain entries can be rejected even though they may appear to the user to be valid. For example, if the INQUIRY(2) field is currently set to NO, any attempt to set the SPA(1) field to a nonzero value is rejected.

The Input Edit Routine for this transaction code can be set the same as another transaction code that is already defined to IMS which uses the same input edit routine that is defined for this transaction.

To copy an Input Edit routine from one transaction to another, specify an existing transaction code that uses the required Input Edit Routine in the EDIT(2) field. The transaction code specified must be one that has already been defined to IMS. DELTA IMS updates the transaction code being added or revised to use the same Input Edit Routine as the transaction named in the EDIT(2)field or none if it does not use one.

To use the revise operation to delete an Input Edit routine from a transaction, type NONE in the EDIT(2) field.

This is the only valid SPA field for SPA=(size).

The STRUNC or RTRUNC option may be specified. If either option is used, that specification is set for the conversation and is used for the SPA inserted into the output message.

The SYSID, ROUTING, and DCLWA parameters are the same as the keyword parameters for a normal IMSGEN when defining a TRANSACT. For example, specifying a SYSID for the transaction does not create a PDIR (application) control block.

The SERIAL and MAXRGN parameters are the same as for a normal IMSGEN when defining a TRANSACT.

The AOI parameter indicates whether the transaction is allowed to issue the Automated Operator Interface (AOI) command call (IMS 9.1 and later).

The FORCE parameter requires a YES or NO value. If you specify NO, the transaction is not modified if its queue count is greater than zero. If you specify YES, the transaction is modified regardless of its queue count.

The FORCE keyword is ignored for requests that revise and rename transactions.

The FORCE=YES is ignored for queued transactions when a request to revise a transaction also renames the transaction, or when an attempt is made to revise a local transaction to a remote transaction (or vice versa).