define_adjacent_len_node adds entries to the node directory database for an adjacent
LEN node and its associated LUs, or adds additional LU entries for
a previously-defined LEN node.
This command is equivalent to a series of define_directory_entry commands for the LEN node and its associated LUs; it
provides a fast method of defining the LEN node's configuration
with a single command. To query the directory entries created by
this command, use query_directory_entry.
If the command is issued to an end node, the LEN node's resources
are accessible only to that end node.
Supplied Parameters |
 |
Parameter name Type Length Default
[define_adjacent_len_node]
cp_name character 17
description character 31 (null string)
lu_name character 8
wildcard_lus constant NO
|
(Up to 10 lu_name entries may be included.)
Supplied parameters are:
- cp_name
The fully qualified name of the CP in the adjacent
LEN end node. This name should match the name the LEN node sends
on its XIDs (if the LEN node supports XIDs) and the adjacent CP
name specified on the define_ls command for the link to the LEN node.
Specify 3-17 characters that consist of a 1-8
character network name, followed by a period, followed by a 1-8 character
partner LU name.
- description
A text string of 0-31 characters followed
by a null character that describes the adjacent node. SNAplus2 uses
this string for information only. It is stored in the node's configuration
file and returned on the query_directory_entry command.
- lu_name
Name of an LU defined on the LEN node. Specify 1-8 characters
corresponding to the second part of the fully qualified LU name
(the first part of the fully-qualified name is defined by the cp_name parameter).
To define an adjacent node with more than 10 LUs, use multiple define_adjacent_len_node commands for the same CP name.
To define the LU associated with the LEN node's control point
(the CP LU or default LU), specify the node's fully qualified CP
name in the cp_name parameter, and include the 'network name' part of this name
(the 8 characters after the period) as one of the LU names.
You can specify a 'wildcard' LU name to match multiple LU
names by specifying only the initial characters of the name. For
example, the wildcard LU name LU will match LUNAME or LU01 (but
will not match NAMELU). However, all the LU names
specified on a single command must be of the same type (wildcard
or explicit), as defined by the wildcard_lus parameter. To add both types of LU names for the same
adjacent node, use multiple define_adjacent_len_node commands.
- wildcard_lus
Indicates whether the specified LU names are wildcard entries
or explicit LU names. Possible values are:
- YES
The specified LU names are wildcard entries.
- NO
The specified LU names are explicit entries.
Returned Parameters |
|
No parameters are returned by SNAplus2 when this command executes successfully.
Error Return Codes |
|
If the command cannot be executed, SNAplus2 returns a primary
return code to indicate the type of error and a secondary return
code to provide specific details about the reason for unsuccessful
execution.
If the command does not execute because of a parameter error,
SNAplus2 returns the following parameters:
- primary_rc
PARAMETER_CHECK
- secondary_rc
Possible values are:
- INVALID_CP_NAME
The cp_name parameter contained a character that was not valid.
- INVALID_LU_NAME
One or more of the specified LU names contained
a character that was not valid.
- INVALID_WILDCARD_NAME
The wildcard_lus parameter was set to YES,
but one or more of the specified LU names was already defined on
a different parent node.
If the command does not execute because of a state error,
SNAplus2 returns the following parameters:
- primary_rc
STATE_CHECK
- secondary_rc
Possible values are:
- INVALID_CP_NAME
The CP name specified by the cp_name parameter was already defined in a directory entry
and is not a LEN node.
- INVALID_LU_NAME
One or more of the LU names specified by the lu_name parameter were already defined on a different parent node.
Printable version
