Initial data for the back-end transaction

While connecting the back-end transaction, the front-end transaction can send initial data to it.

T his kind of data, called program initialization parameters (PIPs), is placed in specially formatted structures and specified on the GDS CONNECT PROCESS command. The PIPLIST (along with PIPLENGTH) option of the GDS CONNECT PROCESS command is used to send PIPs to the back-end transaction.

To examine any PIPs received, the back-end transaction uses the GDS EXTRACT PROCESS command.

PIP data is used only by the two connected transactions and not by the CICS systems. APPC systems other than CICS may not support PIP, or may support it differently.

The PIP data must be formatted into one or more subfields according to the SNA-architected rules. The content of each subfield is defined by the application developer. You should format PIP data as follows:
Figure 1. Format of PIP data.
PIP data consists of one or more subfields; each subfield contains
  • A halfword binary integer specifying the total length of the subfield in bytes
  • A reserved halfword
  • The PIP data itself
The length includes the length field itself and the length of the reserved field; that is, if the PIP field is n bytes long, then the length field contains n + 4 .
This figure shows the layout of a PIP record

CICS inserts information in the reserved fields so that the PIP is architecturally correct. The PIPLENGTH option must specify the total length of the PIP list and must be between 4 and 32763.



dfhp6c0049.html | Timestamp icon Last updated: Monday, 5 June 2017