GNAM entry for GNAME macro invoked (Part 1)

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

Byte (hex)

Contents

00–03

Record ID: C"GNAM"

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 GNAME 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 GNAME only if SEARCH is CF&LOCAL.

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 back level 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 mismatched.

X'66'

An attempt to register a generic resource with the work load manager failed because of the use of an STOKEN that is not valid.

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 re-read 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 generic resource mapping.

X'02'

Find generic resource mapping or USERVAR.

X'03'

Add the application program network name to generic mapping.

X'04'

Delete the application program network name from generic mapping.

X'05'

Write generic mapping to coupling facility structure.

X'06'

Free local copy of generic mapping.

X'07'

Find a generic resource name for an application program network name.

X'08'

Find the generic number for a generic resource name.

07

Event flags:

Bit

Meaning

1... ....

The addition or deletion of an application program network name is because of a change in CP-CP status.

.1.. ....

The addition or deletion of an application program network name is because of a SETLOGON GNAMEADD or SETLOGON GNAMEDEL.

..1. ....

Partner is local, a local real instance will be given precedence used for resolution only. See byte 14.

...1 ....

Resolve to this node, the real instance must be on this node used for resolution only. See byte 14.

.... 1...

Update resolution count, the resolution count will be incremented or decremented used for resolution and termination only. See byte 14.

.... .1..

Update session count, the session count will be incremented or decremented used for resolution and termination only. See byte 14.

.... ..1.

Real instance is a subordinate resource.

.... ...x

0

08–0F

Generic name

10–13

Address of the invoker of the GNAME macro

14

Reason code (used for reason macros X'01' and X'05')

X'00'

Resolution

X'01'

Reserved

X'02'

Update session counts

X'03'

Termination

15–16

0

17

Resolution count or 0

18–1B

The generic number if available, otherwise 0

1C–1F

Request parameter header (RPH) address