Examples of origin data creation

An SNA LU example and a web example help you to understand how origin data is stored and passed to other tasks.

SNA LU example

A task is started in a region when a transaction identifier is entered at an SNA LU. The origin data is stored at the point of origin and is passed to any other tasks that are started in the same region as a consequence of the initial task:
  1. The task is at the boundary of the CICSplex and at a point of origin. CICS® populates the origin data (SNA LU information) from other fields in its association data when the task is attached.
  2. If the task issues a DPL request that is serviced in another region using an IPIC connection, the origin data is passed with the DPL request.
  3. The remote region that receives the message extracts the origin data and passes the data to the mirror transaction, which is attached to service the DPL request.
In this example, the mirror transaction contains the following information in its association data:
  • The values that describe the mirror transaction itself; for example, task ID and principal facility of the IPIC connection
  • The same origin data that the LU task that scheduled the DPL created and stored in its own association data
In this example, the associated data exit, XAPADMGR, can run when the LU task is attached, but the exit is not called when the mirror task is initialized.

Web example

Figure 1 shows an HTTP request that has been passed through a TCP/IP network and arrives for CICS processing. The origin data is stored at the point of origin and is passed to any other tasks that are started in the same region as a consequence of the initial task. In this example, the origin data is populated from two different tasks:
  1. The HTTP request is passed by a CSOL system task to CICS.
  2. The request is processed by a CWXN task. CWXN is at a point of origin and CICS populates the origin data (HTTP request information) from other fields in its association data when the CWXN task is attached. The XAPADMGR exit can be used to provide origin data in the CWXN task. The exit runs before the HTTP request has been received by CICS so the exit cannot make use of the EXEC CICS WEB READ HTTPHEADER, WEB READ FORMFIELD or WEB RECEIVE commands. This method uses the indirect attach task process. An alternative option is to use the direct attach task process, as the socket listener task CSOL is optimized to directly attach user transactions for fast arriving HTTP requests. This means the web attach task is bypassed, therefore reducing the CPU time that is required to process each request. For more information, see HTTP requests are processed by directly attached user transactions.
  3. A new CWBA task is attached and CWBA inherits the ODR from CWXN. CWBA and CWXN might run under different user IDs, but the user ID (userid2) used by the CWBA task is more useful for audit purposes. As a result, the user ID used by the CWBA task is stored in the origin data of CWBA.
  4. An application program that is running under the control of the CWBA task issues a DPL request that is serviced over an IPIC connection. The origin data is passed unchanged with the DPL message to the CISR system task.
  5. The remote region that receives the DPL message extracts the origin data and passes the origin data to a mirror transaction (CSMI) and the mirror transaction is attached to service the DPL request.
  6. The program running under the mirror transaction issues a START command. The origin data is inherited by the task (USER) that is attached to service the START request.
Figure 1 shows how origin data is created when CICS processes an HTTP request and how the origin data is inherited by other tasks that are attached to fulfill the request.
Figure 1. Creation and movement of origin data when an HTTP request is processedThe diagram shows the flow of steps detailed in the example. The information flows from CWXN (with userid1) to CWBA (with userid2). The user ID used by the CWBA task is stored in the origin data of CWBA and sent across the IPCONN connection to CISR unchanged. The mirror transaction CSMI (userid3) inherits the origin data (userid2)and the program running under CSMI issues a start command. The USER task (userid4) also inherits the origin data from userid2.


dfht1_origindataexamples.html | Timestamp icon Last updated: Sunday, 4 June 2017