 |
» |
|
|
|
The start_internal_pu command requests DLUR to initiate SSCP-PU session activation
for a previously defined local PU that is served by DLUR. This command must be issued to a running node. Supplied Parameters | |
Parameter name Type Length Default
[start_internal_pu]
pu_name character 8
dlus_name character 17 (null string)
bkup_dlus_name character 17 (null string)
|
Supplied parameters are: - pu_name
Name of the internal PU to be started. This PU must have
been previously defined using define_internal_pu. The name is a type-A character string starting with
a letter. - dlus_name
Name of the DLUS node that DLUR will contact to solicit
SSCP-PU session activation for the given PU. Specify 3-17
type-A characters, consisting of a 1-8 character network
name, followed by a period, followed by a 1-8 character
DLUS node name. To use the DLUS specified in define_internal_pu, or the global default specified in define_dlur_defaults if no DLUS was specified in define_internal_pu, do not specify this parameter. - bkup_dlus_name
Name of the DLUS node that DLUR will store as the backup
DLUS for the given PU. Specify 3-17 type-A characters,
consisting of a 1-8 character network name, followed by
a period, followed by a 1-8 character backup DLUS name. To use the backup DLUS specified in define_internal_pu, or the global backup default specified in define_dlur_defaults if no backup DLUS was specified in define_internal_pu, do not specify this parameter.
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_DLUS_NAME
The dlus_name parameter contained a character that was not valid
or was not in the correct format. - INVALID_BKUP_DLUS_NAME
The bkup_dlus_name parameter contained a character that was not valid
or was not in the correct format.
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: - NO_DEFAULT_DLUS_DEFINED
A DLUS name was not specified either on this command
or on define_internal_pu, and there is no default DLUS defined (because define_dlur_defaults has not been issued). - PU_NOT_DEFINED
The supplied PU name was not the name of an internal PU
defined using define_internal_pu. - PU_ALREADY_ACTIVATING
The PU is already being activated. - PU_ALREADY_ACTIVE
The PU has already been activated.
If the command does not execute because the node's configuration
does not support it, SNAplus2 returns the following parameters: - primary_rc
- FUNCTION_NOT_SUPPORTED
The node does not support DLUR; support is defined
by the dlur_support parameter on the define_node command.
- secondary_rc
(This parameter is not used.)
If the command does not execute because other conditions exist, SNAplus2
returns the following parameters: - primary_rc
UNSUCCESSFUL - secondary_rc
Possible values are: - DLUS_REJECTED
The DLUS rejected the session activation request. - DLUS_CAPS_MISMATCH
The configured DLUS name was not a DLUS node. - PU_FAILED_ACTPU
The local node rejected a message from the DLUS.
This can be caused by an internal error, a resource shortage, or
a problem with the received message; check the SNAplus2 log files
for messages providing more information.
Appendix A “Common Return Codes from snapadmin Commands” lists combinations
of primary and secondary return codes that are common to all commands. |
Printable version
