Resource entry blocks

The exit should build a set of resource entry blocks for each dynamic resource associated with the XID vector.

The first resource entry block must be for a PU definition. You can have one PU entry and a variable number of LU entries, depending on the PU type.

PU type 2 devices, the maximum number of LUs allowed is 255
PU type 1 devices, the maximum number of LUs allowed is 64

The format for each entry is the same. You need a block for every dependent LU attached to the PU. The exit cannot build independent LUs from a model. If the exit attempts to build an independent LU, the resource entry block for that LU will fail. If a resource entry block returns a PU, LU, or model resource name that is not valid, the resource entry block fails.

Table 1. Configuration services XID exit resource entry block format
Dec (Hex) offset	Size (Bytes)	Description
0 (0)	1	Resource entry block type X'71' This block is for a PU. X'81' This block is for an LU.
1 (1)	1	Bit setting B'1... ....' If this bit is on, the value coded in the address override field (offset X'12' below) overrides the address in the model definition. The remaining bits are reserved.
2 (2)	8	This is the minor node name of the PU or LU, created dynamically, that is represented by this resource entry block. VTAM® will define the dynamic device by this name. If the X'10' bit was on in the XID vector received by the exit, then this will be the name received by VTAM in the REQACTPU from a DLUR when the PU was not found. VTAM passes the name to the exit to use as the name for the dynamic PU.
10 (A)	8	This is the name of a model resource defined in a model major node.
18 (12)	1	This address override field contains one of the following addresses: If this resource entry block represents a PU, this field contains a station address. If this resource entry block represents an LU, this field contains a local address. The value in this field is ignored unless the bit in byte 1 of this resource entry block is set to indicate that the value is valid. Descriptions of the local address and station address fields are found in the z/OS Communications Server: SNA Resource Definition Reference.
19 (13)	1	Bit setting If this resource entry block represents a PU: B'1... ....' If this bit is on, the value coded in the MAXOUT override field (offset X'14' below) overrides the field coded in the model definition. B'.1.. ....' If this bit is on, the value coded in the MAXDATA override field (offset X'15' below) overrides the field coded in the model definition. If this resource entry block represents an LU: B'1... ....' If this bit is on, the value coded in the DLOGMOD override field (offset X'14' below) overrides the field coded in the model definition. B'.1.. ....' If this bit is on, the value coded in the LOGTAB override field (offset X'1C' below) overrides the field coded in the model definition. B'..1. ....' If this bit is on, the value coded in the MODE table override field (offset X'24' below) overrides the field coded in the model definition. B'...1 ....' If this bit is on, the value coded in the LOGAPPL override field (offset X'2C' below) overrides the field coded in the model definition. B'.... 1...' If this bit is on, the value coded in the USS table override field (offset X'3C' below) overrides the field coded in the model definition.
If the resource entry block represents a PU, the following formats apply:
20 (14)	1	MAXOUT override
21 (15)	2	MAXDATA override
23 (17)	45	The resource entry block for a PU must be equal that for an LU.
If the resource entry block represents an LU, the following formats apply:
20 (14)	8	DLOGMOD—default LOGMODE name override
28 (1C)	8	LOGTAB—interpret table override
36 (24)	8	MODE table override
44 (2C)	16	LOGAPPL value override
60 (3C)	8	USS table override
68 (44)	0	This byte is the start of the next resource entry block, if any. If there are no more resource entry blocks, this byte does not appear.