Use of the Client Token

The contents of the token pointed to by field SSS2CTKN are created by JES. Using the token reduces the time to find the associated data set. Don't compare or otherwise use the tokens except on SAPI or Extended Status calls. Two different tokens obtained by different means may point to the same data set.

There are several ways to have obtained a token:

A previous Extended Status request (see field STSTCTKN)
As the output of a PUT/GET request (in field SSS2DSTR)
Dynamic Allocation specified the DALRTCTK text unit.

The content of this SSS2CTKN field is used in addition to any other specified parameters. This way you can make sure the output data set still has the characteristics you would expect and have not been modified. If these characteristics are unimportant to you, specify SSS2CTKN as the only input parameter.

The CTOKEN maps the JES dependent portion of the client (SYSOUT) token (mapped by IAZCTKN). The client (SYSOUT) token has a length defined by the field, CTKNSIZE. The CTOKEN specifically maps the field, CTKNJESD, in IAZCTKN. The JES dependent portion of the client (SYSOUT) token contains the information that JES needs to uniquely identify and locate the data set represented by the client (SYSOUT) token. Also, a bit map from the CTOKEN maps the field, CTKNBMAP, in IAZCTKN. The bit map provides information as to which parts of the client (SYSOUT) token are valid for comparison between client (SYSOUT) tokens.