 |
» |
|
|
|
This section lists the messages that NMMGR may generate when validating
the APPC portion of HP-IBM configuration. | | | |  | NOTE: During HP-IBM validation, NMMGR attempts to validate
all SNA subsystems. Whenever it finds no configuration data for
a particular subsystem, it generates a warning message. Disregard
any warning messages about subsystems you have not installed on
your system. | | | | |
In the following messages, an exclamation point (!)
indicates a value that the system will provide when the message
is generated. MESSAGE: ---> VALIDATION OF
APPC SUBSYSTEM STARTED <--- | CAUSE: NMMGR has started to validate the APPC subsystem
portion of the configuration file. ACTION: No action required. |
MESSAGE: ---> VALIDATION OF
APPC SUBSYSTEM FINISHED <--- | CAUSE: NMMGR has finished validating the APPC subsystem
portion of the configuration file. ACTION: No action required. |
MESSAGE: INTERNAL ERROR. Get data failed
with result code !. (APPCVALERR 3) | CAUSE: An internal error in NMMGR has occurred. ACTION: Notify your HP Representative |
MESSAGE: INTERNAL ERROR. Get path failed
with result code !. (APPCVALERR 4) | CAUSE: An internal error in NMMGR has occurred. ACTION: Notify your HP Representative. |
MESSAGE: Configuration file corrupt.
Missing APPC Path. (APPCVALERR 5) | CAUSE: The configuration file you are validating does
not contain APPC path information and cannot be used. ACTION: Notify your HP Representative. |
MESSAGE: Configuration file corrupt.
Missing APPC Version. (APPCVALERR 6) | CAUSE: The configuration file you are validating does
not contain APPC version information and cannot be used. ACTION: Notify your HP Representative. |
MESSAGE: No configuration data exists
for the APPC subsystem. (APPCVALWARN 7) | CAUSE: You have attempted to validate the APPC subsystem
portion of the configuration file, but no data has been configured
for the APPC subsystem. ACTION: Configure the APPC subsystem before validating
the configuration file. |
MESSAGE: Path : APPC.NETID
Required
NETID is not configured. (APPCVALERR 8) | CAUSE: You have attempted to validate the APPC subsystem configuration
without having entered a Local Network ID in the APPC: Network ID
Data screen. ACTION: Configure your Local Network ID in the APPC: Network
ID Data screen. |
MESSAGE: Path : APPC.MODE.!
!
is an invalid value for Maximum Send RU Size. (APPCVALERR 9) | CAUSE: You have entered a Maximum Send RU Size that is outside the allowable range. ACTION: Configure an RU size from 256 through 2048. |
MESSAGE: Path : APPC.MODE.!
!
is an invalid value for Maximum Receive RU Size. (APPCVALERR 10) | CAUSE: You have entered a Maximum Receive RU Size that is outside the allowable range. ACTION: Configure an RU size from 256 through 2048. |
MESSAGE: Path : APPC.MODE
"!" is
a reserved name and can not be reconfigured. (APPCVALERR 11) | CAUSE: You have attempted to configure a mode name that
is internally defined by the APPC subsystem and cannot be reconfigured. ACTION: Rename the mode type. |
MESSAGE: Path : APPC.MODE.!
No
data is configured for this Mode Type. (APPCVALERR 12) | CAUSE: A mode was configured in the APPC: Select Mode
Type screen, but no data was configured for it in the APPC: Mode
Type Data screen. ACTION: Configure the data for the specified mode type
in the APPC: Mode Type Data screen. |
MESSAGE: Path : APPC.SESSION
At
least one Session Type must be configured. (APPCVALERR 13) | CAUSE: You have attempted to validate the APPC subsystem configuration
file without configuring any session types. ACTION: Configure at least one session type before validating
the configuration file. |
MESSAGE: Path : APPC.SESSION.!
No
data is configured for this Session Type. (APPCVALERR 14) | CAUSE: A session type was configured in the APPC: Select
Session Type screen, but no data was configured for it in the APPC:
Independent or Dependent LU Session Type Data screen. ACTION: Configure the data for the specified session type. |
MESSAGE: Paths : APPC.SESSION.!, APPC.SESSION.!
Local
LU Name "!" is not unique. It can not be configured
for both SNA Node "!" and SNA Node "!".
(APPCVALERR 15) | CAUSE: The same local LU is configured on two different
SNA Nodes (PUs). ACTION: Correct the SNA Node configuration so that each
local LU is configured on exactly one SNA Node. |
MESSAGE: Paths : APPC.SESSION.!, APPC.SESSION.!
These
Independent Session Types have the same triple (Local LU, Mode,
Remote LU). (APPCVALERR 16) | CAUSE: Duplicate independent LU session types have been
configured. ACTION: Delete one of the duplicate session types, or
modify one to use a different Local LU, Mode Type, or Remote LU. |
MESSAGE: Paths : APPC.SESSION.!, APPC.SESSION.!
A
single Local LU — Remote LU pair can not support both single
and parallel sessions. (APPCVALERR 17) | CAUSE: Two independent LU session types have been configured
using the same Local LU and Remote LU; one uses a single session
and one uses parallel sessions. ACTION: Configure a different Local LU for one of the
session types, or modify one session type so that both use single
sessions or both use parallel sessions. |
MESSAGE: Path : APPC.SESSION.!
Mode
Name "!" is not configured under APPC.MODE. (APPCVALERR 18) | CAUSE: You have configured a session type that uses an
unconfigured Mode Name. ACTION: Configure the Mode Name in the APPC: Select Mode
Type screen and the APPC: Mode Type Data screen. |
MESSAGE: Path : APPC.SESSION.!
SNA
Node "!" does not support dependent LUs. (APPCVALERR
19) | CAUSE: You have configured a dependent LU session type
to use a Type 2.1 SNA node without dependent LU support. ACTION: Specify Node 2.1 Dependent LU Support = Y in the "SNA Node Configuration: PU Data" screen
for that node, or specify a different SNA node for the session type. |
MESSAGE: Path : APPC.SESSION.!
SNA
Node "!" is not a PU 2.1 type node. (APPCVALERR
19) | CAUSE: You have configured an independent LU session
type to use a Type 2.0 SNA node. Independent LU session types must
use Type 2.1 SNA nodes. ACTION: Change the node type of the SNA node to 2.1, or
configure a different SNA node for the session type. |
MESSAGE: Path : APPC.SESSION.!.LULIST
There
are no LU names configured for this path. (APPCVALERR 21) | CAUSE: You have configured a dependent LU session type
with no local dependent LUs. ACTION: Configure as many dependent LUs as you will have
sessions of the session type configured. Dependent LUs are configured
in the APPC: Dependent LU List Data screen. |
MESSAGE: Path : APPC.SESSION.!
Node "!" is
not configured under the SNANODE screen. (APPCVALERR 22) | CAUSE: You have configured a session type to use an unconfigured
SNA node. ACTION: Configure the SNA node in the SNA Node Configuration screen. |
MESSAGE: Path : !
LU "!" is
not configured under the SNANODE.! screen. (APPCVALERR 23) | CAUSE: You have configured a session type to use a local
LU that is not configured on the SNA node you specified for the
session type. ACTION: Configure the local LU in the SNA Node Configuration:
LU Data screen for the SNA node used by the session type, or change
the local LU to one that is already configured. |
MESSAGE: Path : APPC.SESSION.!
LU "!" is
not an independent LU under SNANODE.! screen. (APPCVALERR 24) | CAUSE: You have configured an independent LU session
type to use a local LU that is not configured as an independent
LU on the SNA node you specified for the session type. ACTION: Specify an LU that is configured as an independent
LU on the correct SNA Node. (Independent LUs must have no LU# configured
in the "SNA Node Configuration: LU Data" screen.) |
MESSAGE: Path : APPC.SESSION.!
Number
of LUs in LULIST (!) does not equal the Maximum Number of Sessions
(!). (APPCVALERR 25) | CAUSE: You have configured more or fewer dependent LUs
than you can have sessions of the specified session type. ACTION: Delete some dependent LUs from the LU list, or
add some dependent LUs to the LU list, until the number of LUs equals
the Maximum Number of Sessions configured for that session type. Or change the Maximum Number of Sessions value to match the number of LUs configured. |
MESSAGE: Path : APPC.SESSION.!
"!" is
not a correctly formatted Remote LU Name. (APPCVALERR 26) | CAUSE: You have specified a Remote LU Name that does not have the correct format. ACTION: Specify the Remote LU Name as netid.luname, where netid is the network identifier for the remote system, and luname is the name of the remote LU. |
MESSAGE: Path : APPC.TP.!
There
is no Transaction Program Data configured. (APPCVALERR 27) | CAUSE: A transaction program name was configured in the
APPC: Select Transaction Program screen, but no data was configured
for it in the APPC: Transaction Program Data screen. ACTION: Configure the data for the specified transaction
program. |
MESSAGE: Path : APPC.TP.!
"!" is
not a correctly formatted job name. (APPCVALERR 28) | CAUSE: You have specified a Job Name that does not have the correct format. ACTION: Specify the Job Name as file.group.account. The file must not contain any lockwords. |
MESSAGE: Path : APPC.TP.!
TP
Job Name "!" does not exist on the system. (APPCVALWARN
29) | CAUSE: You have specified a Job Name that cannot be found. ACTION: Create a job to stream the configured local TP.
Make sure it has the same file name and is located in the same group
and account you specified in the Job Name field of the APPC: Transaction Program Data screen. |
MESSAGE: Path : APPC.TP
"!" is
a reserved name and can not be reconfigured. (APPCVALERR 30) | CAUSE: You have specified a TP Name that is already being used internally by the APPC
subsystem. ACTION: Rename the configured TP. |
MESSAGE: Path : LOGGING
Logging
subsystem "SUB0016" is not configured. (APPCVALERR
31) | CAUSE: No logging has been configured for subsystem SUB0016, the logging subsystem for the APPC subsystem. ACTION: Configure the logging options for that subsystem,
and make sure the data in the logging configuration screen has been
saved. See the SNA Link/XL Node Manager's Guide for
information about logging configuration. |
MESSAGE: Path : LOGGING.SUB0016
No
classes are configured for SUB0016 logging. (APPCVALERR 32) | CAUSE: SUB0016 has been named, but no logging classes have been configured
for it. ACTION: Go to the Logging Configuration: Logging Classes
screen for SUB0016 and configure the logging classes. See the SNA
Link/XL Node Manager's Guide for information
about logging configuration. |
MESSAGE: Path : LOGGING.SUB0016
Logging
class "!" is not configured. (APPCVALERR 33) | CAUSE: The specified logging classes has not been configured
for subsystem SUB0016. ACTION: Go to the Logging Configuration: Logging Classes
screen for SUB0016 and configure the indicated logging class. See
the SNA Link/XL Node Manager's Guide for
information about logging configuration. |
MESSAGE: Path : LOGGING.SUB0016
"!" is
not a valid class for SUB0016 logging. (APPCVALERR 34) | CAUSE: The specified logging class cannot be configured
for subsystem SUB0016. ACTION: Go to the Logging Configuration: Logging Classes
screen for SUB0016 and correct the logging class specifications.
Valid SUB0016 logging class names are CLAS0010, CLAS0011, CLAS0012, CLAS0013, and CLAS0014. See the SNA Link/XL Node Manager's
Guide for information about logging configuration. |
MESSAGE: Path : LOGGING.SUB0016
"!" is
not a correctly formatted User Name. (APPCVALERR 35) | CAUSE: The User Name specified was not in the proper
format. ACTION: See the SNA Link/XL Node Manager's
Guide for information about logging configuration. |
MESSAGE: Path : APPC.SESSION.!.LULIST
LU "!" is
not a dependent LU under SNANODE.! screen. (APPCVALERR 36) | CAUSE: The specified dependent LU, which you configured
in the "APPC: Dependent LU List Data" screen,
is not configured as a dependent LU on the SNA node you specified
in the "APPC: Dependent LU Session Type Data" screen. ACTION: In the "APPC: Dependent LU List Data" screen,
list only the dependent LUs that are configured on the SNA node
you will use for the session type. |
|
