Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Resource entry blocks z/OS Communications Server: SNA Customization SC27-3666-00 |
|||||||||||||||||||||||||||||||||||||||||||||
There is a resource entry block for each LU contained in the device that powered on. For the resource entry blocks that have the REBERROR bit set to 0, the exit is responsible for ensuring that the resource entry block contains a model LU name and a valid VTAM® name for the LU. If the REBDEFND bit is set to 1, the resource entry block represents the redefinition of an existing LU. In this case, the LU name is already in the REBNAME field and cannot be changed by the exit. If the REBDEFND bit is set to 0, the resource entry block represents the definition of a dynamic LU that has not yet been named. The exit must generate an LU name and place it in the REBNAME field. The REBMODEL field of the resource entry block contains the model acronym of the device that powered on. The exit can use the model acronym or override it with another model name from the model LU group specified on the PU definition statement for the device the dynamic definition request represents. The format of a resource entry block is described in Table 1.
|
Copyright IBM Corporation 1990, 2014
|