Previous Page Contents Page Next Page

3.38 DEFINE_PARTNER_LU

The DEFINE_PARTNER_LU verb defines the parameters of a partner LU for LU-LU sessions between a local LU and the partner LU, or modifies an existing partner LU. You cannot change the partner LU alias of an existing partner LU.

There is normally no requirement to define partner LUs, because SNAP-IX will set up an implicit definition when the session to the partner LU is established; you should only need to define the LU if you need to enforce non-default values for logical record size, conversation security support, or parallel session support. You may also have an APPC application that uses a partner LU alias when allocating a session, therefore you need to define a partner LU in order to map the alias to a fully-qualified partner LU name.

If the local node or the remote node (where the partner LU is located) is a LEN node, note that you need to define a directory entry for the partner LU to allow SNAP-IX to access it. This can be done using either DEFINE_ADJACENT_LEN_NODE or DEFINE_DIRECTORY_ENTRY. If both the local and remote nodes are network nodes, or if one is a network node and the other is an end node, the directory entry is not required, because SNAP-IX can locate the LU dynamically.

3.38.1 VCB Structure

typedef struct define_partner_lu
{
   AP_UINT16        opcode;               /* verb operation code             */
   unsigned char    reserv2;              /* reserved                        */
   unsigned char    format;               /* reserved                        */
   AP_UINT16        primary_rc;           /* primary return code             */
   AP_UINT32        secondary_rc;         /* secondary return code           */
   PLU_CHARS        plu_chars;            /* partner LU characteristics      */
} DEFINE_PARTNER_LU;
typedef struct plu_chars
{
   unsigned char    fqplu_name[17];       /* fully qualified partner LU name */
   unsigned char    plu_alias[8];         /* partner LU alias                */
   unsigned char    description[32];      /* resource description            */
   unsigned char    reserv2[16];          /* reserved                        */
   unsigned char    plu_un_name[8];       /* partner LU uninterpreted name   */
   unsigned char    preference;           /* reserved                        */
   AP_UINT16        max_mc_ll_send_size;  /* maximum MC send LL size         */
   unsigned char    conv_security_ver;    /* already-verified security       */
                                          /*  supported?                     */
   unsigned char    parallel_sess_supp;   /* parallel sessions supported?    */
   unsigned char    reserv3[8];           /* reserved                        */
} PLU_CHARS;

3.38.2 Supplied Parameters

The application supplies the following parameters:

opcode

AP_DEFINE_PARTNER_LU

plu_chars.fqplu_name

Fully qualified LU name for the partner LU. The name is a 17-byte EBCDIC string, right-padded with EBCDIC spaces. It consists of a network ID of up to 8 A-string characters, an EBCDIC dot (period) character, and a network name of up to 8 A-string characters.

plu_chars.plu_alias

LU alias of the partner LU. This is an 8-byte ASCII string, using any locally displayable characters, padded on the right with spaces if the name is shorter than 8 bytes.

If the fqplu_name parameter above matches the fully qualified name of an existing partner LU, this parameter must match the partner LU alias in the existing definition. You cannot change the partner LU alias for an existing partner LU, or set up more than one LU alias for the same fully qualified name.

plu_chars.description

A null-terminated text string (0-31 characters followed by a null character) describing the partner LU. This string is for information only; it is stored in the node's configuration file and returned on the QUERY_PARTNER_LU and QUERY_PARTNER_LU_DEFINITION verbs, but SNAP-IX does not make any other use of it.

plu_chars.plu_un_name

Uninterpreted name of the partner LU (the name of the LU as defined to the remote SSCP). The name is an 8-byte EBCDIC character string.

To use the default uninterpreted name (the same as the network name taken from the fqplu_name parameter above), set this parameter to 8 binary zeros. This parameter is only relevant if the partner LU is on a host and dependent LU 6.2 is used to access it.

plu_chars.max_mc_ll_send_size

The maximum size of logical records that can be sent and received by mapped conversation services at the partner LU. Specify a number in the range 1-32,767, or zero to specify no limit (in this case the maximum is 32,767).

plu_chars.conv_security_ver

Specifies whether the partner LU is authorized to validate user IDs on behalf of local LUs; that is, whether the partner LU may set the already verified indicator in an Attach request. Possible values are:

AP_YES

The partner LU can validate user IDs.

AP_NO

The partner LU cannot validate user IDs.

plu_chars.parallel_sess_supp

Specifies whether the partner LU supports parallel sessions. Possible values are:

AP_YES

The partner LU supports parallel sessions.

AP_NO

The partner LU does not support parallel sessions.

3.38.3 Returned Parameters: Successful Execution

If the verb executes successfully, SNAP-IX returns the following parameters:

primary_rc

AP_OK

3.38.4 Returned Parameters: Parameter Check

If the verb does not execute because of a parameter error, SNAP-IX returns the following parameters:

primary_rc

AP_PARAMETER_CHECK

secondary_rc

Possible values are:

AP_DEF_PLU_INVALID_FQ_NAME

The fqplu_name parameter contained a character that was not valid.

AP_INVALID_UNINT_PLU_NAME

The plu_un_name parameter contained a character that was not valid.

Common Return Codes lists further secondary return codes associated with AP_PARAMETER_CHECK, which are common to all NOF verbs.

3.38.5 Returned Parameters: State Check

If the verb does not execute because of a state error, SNAP-IX returns the following parameters.

primary_rc

AP_STATE_CHECK

secondary_rc

Possible values are:

AP_PLU_ALIAS_CANT_BE_CHANGED

The plu_alias parameter of an existing partner LU cannot be changed.

AP_PLU_ALIAS_ALREADY_USED

The plu_alias parameter is already used for an existing partner LU with a different LU name.

Common Return Codes lists further secondary return codes associated with AP_STATE_CHECK, which are common to all NOF verbs.

3.38.6 Returned Parameters: Other Conditions

Common Return Codes lists further combinations of primary and secondary return codes that are common to all NOF verbs.

Previous Page Contents Page Top of Page Next page