Many of the CICSPlex® SM API commands are interrelated; you use them in conjunction with each other to accomplish the objectives of your program. For example, you issue a GET command to build a result set and then issue a FETCH command to access the resource table records in that result set.
To correlate the results of various operations with subsequent requests that you make, CICSPlex SM assigns 4-byte tokens to the following objects of the API environment:
So, for example, each processing thread has a unique, 4-byte identifying token. You must specify a thread token on each API command that your program issues to identify the thread where it should be processed. Likewise, once a result set or filter is created, you refer to it on subsequent commands by supplying the token value assigned to it by CICSPlex SM. And each LISTEN request is given a token so that you can cancel the request using the CANCEL command.
Token values are not only unique for individual objects, but the structure of the tokens varies by object type. So a thread token cannot be mistaken by CICSPlex SM for any other type of token. If you specify an invalid token (such as, a result set token on the FILTER option), you receive a RESPONSE value of INVALIDPARM.
[[ Contents Previous Page | Next Page Index ]]