 |
» |
|
|
|
This appendix contains messages that might occur
when you validate the SNA IMF configuration data. Configuration
file validation is discussed in Chapter 3 “SNA IMF Configuration” of this
manual. MESSAGE: Corrupt configuration file.
Missing IMF path. (IMFVALERR 3) | CAUSE: The SNA IMF path is missing from the configuration
file. ACTION: Restore the configuration file from a backup tape
and retry the validation. Also, submit an SR. |
MESSAGE: Corrupt configuration file.
Missing SNA IMF version. (IMFVALERR 4) | CAUSE: No version stamp exists for the SNA IMF path. ACTION: Restore the configuration file from a backup tape
and retry the validation. Also, submit an SR. |
MESSAGE: No configuration data exists
for SNA IMF subsystem. (IMFVALWARN 5) | CAUSE: No data is configured for SNA IMF. Note that this
is a warning message. ACTION: If you do not want SNA IMF to be configured, no
action is necessary. If you want SNA IMF to be configured, you must
configure it before validating the configuration file again. |
MESSAGE: Path: NMMGRpath — Node
NodeName is not configured under SNANODE screen. (IMFVALERR 6) | CAUSE: A node listed as a configured SNA IMF node was
not configured as an SNA node. ACTION: Configure the indicated node as an SNA node on
the SNANode Configuration screen. |
MESSAGE: Path: NMMGRpath — No
classes configured for this path. (IMFVALERR 7) | CAUSE: No security classes were configured for the node
indicated in the path. ACTION: Configure the node's security classes
on the SNA IMF Configuration: Security Classes screen. |
MESSAGE: Path: NMMGRpath — No
data configured for this security class. (IMFVALERR 8) | CAUSE: No LUs are configured for the security class indicated
in the path name. ACTION: Configure the correct LUs for the security class
on the SNA IMF Configuration: Security Class Data screen. |
MESSAGE: Path: NMMGRpath — LU
LUName is not a valid LU for SNAnode NodeName. (IMFVALERR 9) | CAUSE: The indicated LU is not configured under the indicated
SNA node. ACTION: Ensure that the LU should be configured under
the SNA node. If it should be configured, configure it on the SNANode
Configuration: LU Data screen. |
MESSAGE: Path: NMMGRpath — Corrupt
configuration file. Missing USERLIST path. (IMFVALERR 10) | CAUSE: The USERLIST path (for the user list data) is
missing from the configuration file. ACTION: Restore the configuration file from a backup tape
and retry the validation. Also, submit an SR. |
MESSAGE: Path: NMMGRpath — Corrupt
configuration file. Missing PGMLIST path. (IMFVALERR 11) | CAUSE: The PGMLIST path (for the program list data) is
missing from the configuration file. ACTION: Restore the configuration file from a backup tape
and retry the validation. Also, submit an SR. |
MESSAGE: Path: NMMGRpath — The
USERLIST for this security class is empty. (IMFVALERR 12) | CAUSE: No authorized users are configured for the security
class indicated in the path: no users will be able to use the security
class. This happens when the Users field of the SNA IMF Configuration: User List
Data screen is intentionally blanked out and then the Save Data key ([f6]) is pressed. ACTION: Configure at least one authorized user for the
security class. |
MESSAGE: Path: NMMGRpath — The
PGMLIST for this security class is empty. (IMFVALERR 13) | CAUSE: No authorized programs are configured for the
security class indicated in the path: no programs will be able to
use the security class. This happens when the Programs field of the SNA IMF Configuration: Program List
Data screen is intentionally blanked out and then the Save Data key ([f6]) is pressed. ACTION: Configure at least one authorized program for
the security class. |
MESSAGE: Path: NMMGRpath — Unknown
error occurred while getting this path. (IMFVALERR 14) | CAUSE: An unexpected error occurred while attempting
to obtain a path from the configuration file. This usually indicates
a problem with the validation procedure. ACTION: Restore the configuration file from a backup tape
and retry the validation. Also, submit an SR. |
MESSAGE: Path: NMMGRpath — Unknown
error occurred while reading the path data. (IMFVALERR 15) | CAUSE: An unexpected error occurred while attempting
to read data from the configuration file. This usually indicates
a problem with the validation procedure. ACTION: Restore the configuration file from a backup tape
and retry the validation. Also, submit an SR. |
|
