HP 3000 Manuals HP 3000 Manuals
Network Services Environment Error Messages
Environment error messages are produced when an error is detected in the
definition of an environment by a DSLINE or a REMOTE command. They are
displayed on $STDLIST during the execution of the command, usually
preceding a CI error or ENVIRONMENT message. These error messages are
found in CATALOG.PUB.SYS, message set 16 (DS errors). When an
environment error is detected, the DSERR job control word is set to the
error number. The environment error message is not displayed if the
command is executed through the COMMAND intrinsic.
620 MESSAGE NO ENVIRONMENT FOR envid.
CAUSE A DSLINE envid;RESET was executed, and there is
no generic environment for envid.
ACTION Correct envid and reissue the command.
622 MESSAGE ENVIRONMENT TABLE IS FULL.
CAUSE The session environment table is full; there is
no room for additional information on new
environments or tracing.
ACTION Delete any unused environments, turn off any
unused service tracing, and reissue the command.
623 MESSAGE NO DEFAULT ENVIRONMENT SET BY A :DSLINE OR
:REMOTE.
CAUSE A command using a default environment was
executed, but no default environment was set by
a previous DSLINE or REMOTE command.
ACTION Insert an environment ID into the syntax and
reissue the command.
624 MESSAGE NO ENVIRONMENT FOR # envnum.
CAUSE An environment number was used in a DSLINE or
REMOTE and the envnum does not correspond to any
existing environments.
ACTION Correct the environment number and reissue the
command. The DSLINE @.@.@ command can be used
to get a list of environments and their numbers.
625 MESSAGE ACTIVE SERVICES FOR envid; CLOSE IGNORED.
CAUSE A DSLINE CLOSE was executed for an environment,
identified by envid, that has one or more active
services (RFA, RDBA). The environment is not
closed, and the services continue to be active.
ACTION Terminate the service or services, and reissue
the command. The DSLINE SHOW command will
display which services are active for an
environment.
627 MESSAGE CANNOT OPEN TRACE FILE filename.
CAUSE A DSLINE TRACE=ON was issued, but the indicated
trace file cannot be opened.
ACTION Check the parameters for the TRACE option,
correct if in error, and reissue the command.
628 MESSAGE CANNOT CLOSE TRACE FILE filename.
CAUSE A DSLINE TRACE=OFF was issued, but the indicated
trace file cannot be closed.
ACTION Check the parameters for the TRACE option,
correct if in error, and reissue the command.
629 MESSAGE CANNOT OBTAIN DATA SEGMENT FOR ENVIRONMENT
TABLE.
CAUSE An extra data segment was not available for the
session environment table, because of a lack of
memory or DST entries. No environments can be
defined.
ACTION Wait and reissue the command later, when memory
or DST entries may become available. If this
error occurs frequently, there may be
insufficient DST entries or memory. The system
manager may have to increase the DSTs or memory.
630 MESSAGE CANNOT CHANGE NODE NAME FROM nodename WHILE
ACTIVE SERVICES.
CAUSE A DSLINE envid = nodename was executed for an
environment for which one or more services have
been established on a remote node other than
nodename. The environment of this node cannot
be changed until the services are finished.
ACTION Wait for the services to terminate, or terminate
the services. The DSLINE SHOW command can be
used to determine the active services for the
environment.
631 MESSAGE INVALID ENVIRONMENT ID OR NODE NAME LENGTH.
CAUSE A fully qualified environment or node name in a
command was longer than the allowed maximum of
50 characters.
ACTION Shorten the name and reissue the command.
632 MESSAGE ID OR NODE IN name DOES NOT BEGIN WITH AN ALPHA.
CAUSE The first part of a (fully qualified)
environment ID or node name does not begin with
an alphabetic character.
ACTION Correct the name and reissue the command.
633 MESSAGE ID OR NODE IN name IS GREATER THAN 16
CHARACTERS.
CAUSE The first part of a (fully qualified)
environment ID or node name is longer than the
allowed 16 characters.
ACTION Shorten the name and reissue the command.
634 MESSAGE ID OR NODE IN name CONTAINS A NON-ALPHANUMERIC
CHARACTER.
CAUSE The first part of a (fully qualified)
environment ID or node name contains a character
that is not alphabetic or numeric special
characters @ # - . _ or ?.
ACTION Correct the name and reissue the command.
635 MESSAGE EXPECTED A DOMAIN AFTER THE NODE OR ID IN name.
CAUSE Something other than a domain followed the node
or ID part of name.
ACTION Correct the name and reissue the command.
636 MESSAGE DOMAIN IN name DOES NOT BEGIN WITH AN ALPHA.
CAUSE The second (domain) part of a (fully qualified)
environment ID or node name does not begin with
an alphabetic character.
ACTION Correct the name and reissue the command.
637 MESSAGE DOMAIN IN name IS GREATER THAN 16 CHARACTERS.
CAUSE The second (domain) part of a (fully qualified)
environment ID or node name is longer than the
allowed 16 characters.
ACTION Correct the name and reissue the command.
638 MESSAGE DOMAIN IN name CONTAINS A NON-ALPHANUMERIC
CHARACTER.
CAUSE The second (domain) part of a (fully qualified)
environment ID or node name contains a character
that is not alphabetic or numeric.
ACTION Correct the name and reissue the command.
639 MESSAGE EXPECTED ORGANIZATION AFTER DOMAIN IN name.
CAUSE Something other than an organization followed
the domain part of a (fully qualified)
environment ID or node name.
ACTION Correct the name and reissue the command.
640 MESSAGE ORGANIZATION IN name DOES NOT BEGIN WITH AN
ALPHA.
CAUSE The third (organization) part of a (fully
qualified) environment ID or node name does not
begin with an alphabetic character.
ACTION Correct the name and reissue the command.
641 MESSAGE ORGANIZATION IN name IS GREATER THAN 16
CHARACTERS.
CAUSE The third (organization) part of a (fully
qualified) environment ID or node name is longer
than the allowed 16 characters.
ACTION Correct the name and reissue the command.
642 MESSAGE ORGANIZATION IN name CONTAINS A NON-ALPHANUMERIC
CHARACTER.
CAUSE The third (organization) part of a (fully
qualified) environment ID or node name contains
a character that is not alphabetic or numeric.
ACTION Correct the name and reissue the command.
643 MESSAGE TOO MANY HIERARCHY LEVELS IN name; EXPECTED
NAME.DOMAIN.ORG.
CAUSE The fully qualified environment ID or node name
has more than three parts.
ACTION Correct the name and reissue the command.
644 MESSAGE TRANSPORT NOT INITIALIZED.
CAUSE A DSLINE or REMOTE command has been issued and
the Network Transport has not been started by a
NETCONTROL command.
ACTION Wait until the transport is started, or issue a
NETCONTROL to start the transport. (Only users
with NM capability can use the NETCONTROL
command.)
645 MESSAGE UNKNOWN NODE nodename.
CAUSE A DSLINE or REMOTE command was issued for a
non-existent node. Also, this error may be
displayed when a valid NS node name is used, but
the NS transport has not been started.
ACTION If the node name is invalid, correct the name
and reissue the command. If the node name is
valid, wait for the transport to be started or
start the transport with the NETCONTROL command.
646 MESSAGE name IS NOT A NODE NAME OR DS LOGICAL DEVICE.
CAUSE A DSLINE command was issued using a DS logical
device instead of a node name.
ACTION Use a node name or environment name and issue
the command again.
647 MESSAGE ALREADY LOGGED ON AS user.acct.
CAUSE A DSLINE with a LOGON option has been issued for
an environment that has its remote session
logged on.
ACTION Wait for the remote session to be logged off, or
log off the remote session (for example, by
terminating any services using the environment).
687 MESSAGE CANNOT CHANGE NS NODE NAME FROM nodename TO
GIVEN DOMAIN NAME.
CAUSE The environment already exists with an NS node
name.
ACTION First delete the old environment and then create
a new environment with the domain node name.
688 MESSAGE CANNOT CHANGE DOMAIN NODE NAME FROM nodename TO
GIVEN NS NAME.
CAUSE The environment already exists with a DOMAIN
node name.
ACTION First delete the old environment and then create
a new environment with the ns name.
689 MESSAGE ERROR NO ASGLOBAL TABLE.
CAUSE NS global table was not created or was
corrupted.
ACTION Internal error. See "Submitting an SR" in
appendix A of this manual.
690 MESSAGE ERROR NO ROOM IN SID TABLE.
CAUSE NS services users has reached the maximum limit.
ACTION Wait until some NS users log off then try again.
691 MESSAGE ERROR NO SESSION ID.
CAUSE NS session ID table was not created or was
corrupted.
ACTION Internal error. See "Submitting an SR" in
appendix A of this manual.
692 MESSAGE ERROR DUPLICATE SESSION ID.
CAUSE Random number generator created a duplicate
session ID for this session.
ACTION Try the command again. If it fails again, then
see "Submitting an SR" in appendix A of this
manual.