SPT entry for SPT macro invoked (Part 1)

This trace record is written when partner LU mapping information in the generic resource coupling facility structure is created, deleted, or changed using the SPT macroinstruction.

Byte (hex)

Contents

00–03

Record ID: C"SPT"

04

ID is the primary address space ID (ASID). This field is 0 if the ASID is greater than X'FF'.

05

Return code from the SPT macro

X'00'

Request completed successfully. This is an existing USERVAR return code.

X'01'

Request completed successfully and local data was returned. This is returned from SPT if SEARCH is CF&LOCAL only.

X'04'

Resource specified could not be located. This is an existing USERVAR return code.

X'51'

Request failed because of APPC restrictions. This is an existing USERVAR return code.

X'52'

Request failed because of a parameter specification that was not valid. This is an existing USERVAR return code.

X'53'

The function requested could not be completed because of a storage allocation failure. This is an existing USERVAR return code.

X'54'

The real instance of user variable to be deleted could not be located. This is an existing USERVAR return code.

X'55'

A conflict was found because of NETIDs.

X'56'

A conflict was found because of CPNAMEs.

X'57'

VTAM® is halting.

X'58'

ENDAFFINITY was issued for a session that was VTAM owned.

X'59'

RSCTYPE value conflicted between USERVAR and GR.

X'5A'

An attempt to change the generic name for a given application failed because SPTEs pertaining to the previous generic name still exist.

X'60'

A session pair could not be found in an SPT entry.

X'61'

An attempt to change the generic name for a given application failed because either (1) the existing generic name was never deleted, or (2) because SPTEs pertaining to the existing generic name still exist.

X'62'

An attempt to repopulate the generic resource coupling facility structure has failed because the local data being used for repopulation is backlevel compared to data already in the structure.

X'63'

An attempt to repopulate the generic resource coupling facility structure has succeeded but backlevel data has been identified in the structure and additional structure cleanup may be required.

X'64'

An attempt to increment the session count for an SPTE failed because the name type of the SPTE did not match what was expected.

X'65'

Request failed because of TSO mismatch.

X'66'

An attempt to register a generic resource with the workload manager failed because a STOKEN that was not valid was used.

X'A0'

A request made against the generic resources coupling facility structure will complete synchronously.

X'A1'

An attempt to update information in the generic resources coupling facility structure failed because that data had changed since it was last read. The data should be reread and then modified again.

X'A2'

An attempt to access the generic resources coupling facility structure failed for an unexpected reason.

X'A3'

There is currently no connection to the generic resources coupling facility structure.

X'A4'

The buffers provided for reading data from the generic resources coupling facility structure were insufficient for buffering all the data associated with the list entry being read. No data (adjunct or element) is returned.

X'A5'

A read from the generic resources coupling facility structure failed because the requested data could not be found in that structure.

X'A6'

Data could not be added to the generic resources coupling facility structure because there is insufficient storage in the generic resources coupling facility structure to hold it.

06

Reason macro invoked:

X'01'

Find an SPT entry.

X'02'

Add a session pair to the SPT entry.

X'03'

Decrement the session count for a session pair.

X'04'

Increment the session count for a session pair.

X'05'

End the affinity between the generic resource and its partner LU.

X'06'

Update an affinity between the generic resource and its partner LU.

X'07'

Delete a session pair in an SPT entry.

X'08'

Free local SPT entry that was read from the coupling facility structure.

X'09'

Create a local copy of an SPT entry.

07

Flags:

x... ....

Name type

B"0"

Real names only

B"1"

Generic names allowed

.1.. ....

This SPT will persist until the application issues the CHANGE OPTCD=ENDAFFIN macroinstruction. See z/OS Communications Server: SNA Programming for additional information.

..x. ....

Ownership indicator

B"0"

VTAM-owned

B"1"

Application-owned

...x ....

Multinode persistent session indicator

B"0"

SPT entry is not associated with a multinode persistent session application program

B"1"

SPT entry is associated with a multinode persistent session application program

.... xx..

Affinity creator.

B"00"

The affinity was created during a previous request.

B"01"

VTAM selected the instance of the generic resource.

B"10"

The MVS™ WLM selected the instance of the generic resource.

B"11"

The Generic Resources Exit selected the instance of the generic resource.

.... ..1.

This affinity is for an LU 6.2 session that is not a user sync point or a limited resource.

.... ...x

0

08–0F

Generic resource name

10–13

Address of the issuer of the SPT macro

14–1B

Application program network name

1C–1F

Request parameter header (RPH) address