DLUR_PU_INDICATION

This indication is generated whenever a DLUR PU is activated or deactivated. This allows a registered application to maintain a list of currently active DLUR PUs.

VCB Structure

typedef struct dlur_pu_indication
{
   unsigned short  opcode;              /* verb operation code             */
   unsigned char   reserv2;             /* reserved                        */
   unsigned char   format;              /* format                          */
   unsigned short  primary_rc;          /* primary return code             */
   unsigned long   secondary_rc;        /* secondary return code           */
   unsigned char   data_lost;           /* previous indication lost        */
   unsigned char   reason;              /* reason for this indication      */
   unsigned char   pu_name[8];          /* PU name                         */
   unsigned char   pu_id[4];            /* PU identifier                   */
   unsigned char   pu_location;         /* downstream or local PU          */
   unsigned char   pu_status;           /* status of the PU                */
   unsigned char   dlus_name[17];       /* current DLUS name               */
   unsigned char   dlus_session_status; /* status of the DLUS pipe         */
   unsigned char   reserv5[2];          /* reserved                        */
} DLUR_PU_INDICATION;

Parameters

opcode
AP_DLUR_PU_INDICATION
format
Identifies the format of the VCB. This field is set to zero to specify the version of the VCB listed above.
primary_rc
AP_OK
secondary_rc
Equals zero.
data_lost
Specifies whether data has been lost (AP_YES or AP_NO). It is set when an internal component detects a failure that has caused a previous indication to be lost. If the data_lost flag is set to AP_YES then subsequent data fields can be set to null. The application should issue a QUERY verb to update the information that has been lost.
reason
The cause of the indication. It is one of the following:
AP_ACTIVATION_STARTED
The PU is activating.
AP_ACTIVATING
The PU has become active.
AP_DEACTIVATING
The PU has become inactive.
AP_FAILED
The PU has failed.
AP_ACTIVATION_FAILED
The PU has failed to activate.
pu_name
Name of the PU. This is an 8-byte alphanumeric type A EBCDIC string (starting with a letter), padded to the right with EBCDIC spaces.
pu_id
The PU identifier defined in a DEFINE_INTERNAL_PU verb or obtained in an XID from a downstream PU. This is a 4–byte hexadecimal string. Bits 0–11 are set to the block number and bits 12–31 are set to the ID number that uniquely identifies the PU.
pu_location
The location of the PU. This can be one of the following:

AP_INTERNAL
AP_DOWNSTREAM

pu_status
The status of the PU (as seen by DLUR). This can be set to one of the following:
AP_RESET_NO_RETRY
The PU is in reset state and will not be retried.
AP_RESET_RETRY
The PU is in reset state and be retried.
AP_PEND_ACTPU
The PU is waiting for an ACTPU from the host.
AP_PEND_ACTPU_RSP
After forwarding an ACTPU to the PU, DLUR is waiting for the PU to respond.
AP_ACTIVE
The PU is activate.
AP_PEND_DACTPU_RSP
After forwarding an DACTPU to the PU, DLUR is waiting for the PU to respond.
AP_PEND_INOP
DLUR is waiting for all necessary events to complete before it deactivates the PU.
dlus_name
The name of the DLUS node that the PU is currently using (or attempting to use). This is a 17–byte string composed of two type A EBCDIC character strings concatenated by an EBCDIC dot, that is right padded with EBCDIC spaces. (Each name can have a maximum length of 8 bytes with no embedded spaces.) If the PU activation has failed, this field will be set to all zeros.
dlus_session_status
The status of the DLUS pipe currently being used by the PU. This can be one of the following:

AP_PENDING_ACTIVE
AP_ACTIVE
AP_PENDING_INACTIVE
AP_INACTIVE