Data interface stubs

To correlate a sequence of requests relating to a result set, the data interface uses a STUB header for DATA/GET, DATA/FETCH, and DATA/DISCARD commands.

The stub header is similar to a CICSPlex® SM API result set token, except it is valid for one request only. Each DATA/GET and DATA/FETCH command generates a new STUB header and the client application must use the new value on its next request against the result set. Failure to use the correct STUB value results in a BADSTUB response.

The Web User Interface server manages each active data interface result set as a single user session window. Each user session can have a maximum of 64 windows active at anyone time, and these are shared between the client application data interface and the HTML web browser interface.

The Web User Interface server creates a new result set in response to a DATA/GET command that omits the STUB option. The client application can request the server to replace the contents of a result set with the result of a new query by issuing a DATA/GET command that specifies the STUB value of an existing result set.



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