"Nonclass" Errors (Cont'd) [ MPE/iX Error Messages Manual Volume II ] MPE/iX 5.5 Documentation
MPE/iX Error Messages Manual Volume II
"Nonclass" Errors (Cont'd)
Interpreting SYSGEN Messages and Error Codes
Three types of messages (informational, error, and warning) may occur
during SYSGEN operations.
Informational messages indicate something out of the ordinary has
happened. Do not take any action. SYSGEN continues normally.
Warnings are more serious. They indicate SYSGEN has encountered
difficulties, but can handle the problem. Determine if any action should
be taken. SYSGEN continues normally. Warnings follow the string,
**warning**.
Errors fall into two categories: fatal and nonfatal. Fatal errors make
it impossible for SYSGEN to continue. In the case of a fatal error, the
job control word (JCW) is set to SYSTEM.
Nonfatal errors are caused by user mistakes.
Both fatal and nonfatal errors follow the string **error**.
The "!" is replaced with actual information when you encounter the error.
-------------------------------------------------------------
Input/Output (I/O) Configurator Messages.
-------------------------------------------------------------
0375 MESSAGE **note** Class !'s mode is now !
ACTION
-------------------------------------------------------------
0401 MESSAGE **warning** language localized string "NMMGR" too
long
CAUSE When this catalog was language localized, the
string "NMMGR" in message 350 was replaced with a
string that is to long to fit into SYSGEN's I/O
display format.
ACTION Contact your software representative responsible
for maintaining system files.
-------------------------------------------------------------
0402 MESSAGE **warning** Class ! is already associated with
device !
CAUSE User is trying to add a class to a device more than
once.
ACTION Use another class name or leave unchanged.
-------------------------------------------------------------
0403 MESSAGE **warning** can't get NMMGR info for file !.
CAUSE Cross-validation error SYSGEN and NMMGR does not
occur. This occurs when there is a problem with
the remote configuration file, usually when set by
the SYSFILE RDCC command. The file is missing
elements, such as proper path information. Also,
this message can be displayed when there is no
remote configuration file. Related messages should
appear.
ACTION It is possible you have entered the wrong file name
or a configuration file that is no longer valid.
Use the RDCC command in SYSFILE to designate the
file with the proper remote configuration
information. If you feel you have the proper file,
recheck your remote configuration through NMMGR and
cross-validate the file again with SYSGEN.
-------------------------------------------------------------
0404 MESSAGE **warning** path doesn't exist
CAUSE The path that the user referenced doesn't exist.
ACTION If you think the path does exist, use the LPATH
command to verify existing paths. If you are
certain that the path you gave should exist, exit
the I/O Configurator and use the Main Menu SHOW
command to verify you are in the proper
configuration. Enter a valid iopath.
-------------------------------------------------------------
0405 MESSAGE **warning** class ! doesn't exist
CAUSE The class that the user referenced doesn't exist.
ACTION Enter the LCLASS command to display a list of
current class names and the LDEVs assigned to each.
Enter a valid class name.
-------------------------------------------------------------
0406 MESSAGE **warning** no volumes left to list
CAUSE You have entered a volume name in the LVOL command
that does not exist. SYSGEN has searched the list
of volume names and has come to the end of the
list.
ACTION Enter the LVOL command without the volume name
parameter.
-------------------------------------------------------------
0407 MESSAGE **warning** volume name does not exist
CAUSE This message appears with the preceding message
when an LVOL is made for a volume name that does
not exist. This message appears when you use the
DVOL or MVOL command to delete or modify a volume
and specify a volume name that does not exist.
ACTION Enter the LVOL command to see a list of existing
volumes. Usually, the error occurs when the volume
name is misspelled. If you are certain the volume
name you entered should exist and doesn't, exit the
I/O configurator and use the SHOW command to check
that you are in the proper configuration group.
Verify that the name hasn't been previously
modified.
-------------------------------------------------------------
0408 MESSAGE **warning** Can't open offline list
device--online used
CAUSE Usually, this error message appears when the
printer has not been spooled out. The offline
device, also, may be powered off or has been
disconnected.
ACTION Inform your operations personnel that the offline
device that you were attempting to use is
unavailable. If the device has not been spooled,
they are able to start spooling for you.
-------------------------------------------------------------
0410 MESSAGE **warning** class ! degraded to mode !
CAUSE The combination of devices that you have placed
into the given class force all devices in that
class to operate in a less than optimal manner.
This is caused by combining unlike devices (for
example, a tape drive and a printer) into the same
class.
ACTION Although the devices still operate in the degraded
mode, it is best to only put devices of a similar
type into the same class. Review the named class
and separate it into two classes.
-------------------------------------------------------------
0411 MESSAGE **warning** class ! is of mode !--user mode
ignored
CAUSE Although the user requested a specific class mode
for the given class, the devices in the class do
not allow that mode. Instead, the mode displayed
in the message is used.
ACTION If you feel that the class should accept the given
mode, use the LCLASS command to determine that
devices are in the class--a device of a different
type would cause the class to reject your chosen
mode. Remove any such devices from the class.
-------------------------------------------------------------
0414 MESSAGE **warning** Not enough room for dcc devices in
class !
CAUSE Each class may only contain a finite number of
devices. For first release, this is 256. The
total number of devices requested for the class by
both SYSGEN and NMMGR is more than this number.
When the system is rebooted, some or all of the DCC
devices fail to be configured, rendering them
unusuable.
ACTION Change either the class name, or the number of
devices in the class. This must be done in SYSGEN
for local devices (those configured in SYSGEN), and
in NMMGR for DCC devices (those configured in
NMMGR).
-------------------------------------------------------------
0415 MESSAGE **warning** docc devices in class ! degraded to
mode !
CAUSE Attempting to share a class with NMMGR has caused
the mode requested by NMMGR to be degraded to the
given mode.
ACTION If you feel the class should accept NMMGR's mode,
use the LCLASS command to determine that devices
are in the class--a device of a different type
would cause the class to reject NMMGR's mode.
Remove any such devices from the class, or change
the class name that NMMGR is using by running
NMMGR.
-------------------------------------------------------------
0416 MESSAGE **warning** class ! won't accept dcc's mode of !
anymore
CAUSE In determining the mode of a class, devices
configured by SYSGEN always take precedence. If a
device is added to a class that is shared with
NMMGR, and the new device causes the class to
become incompatible with the DCC devices, the mode
of the DCC devices is rejected. The DCC devices
with the given class are not configured when the
system is rebooted, rendering them inoperable.
ACTION Either remove the device that caused the
incompatibility, or change the class name of the
DCC device in NMMGR.
-------------------------------------------------------------
0417 MESSAGE **warning** dcc devices degrade class ! to mode !
CAUSE Although the doc devices are able to share this
class with SYSGEN, their presence degrades access
to SYSGEN's devices.
ACTION Either change the class name of the DCC devices in
NMMGR, or else remove any local devices from the
class whose mode is not compatible with the DCC
devices.
-------------------------------------------------------------
0418 MESSAGE **warning** language localized string "USER" too
long
CAUSE When this catalog was language localized, the
string "USER" in message 351 was replaced with a
string that is too long to fit into SYSGEN's I/O
display format.
ACTION Contact your software personnel responsible for
maintaining system files.
-------------------------------------------------------------
0419 MESSAGE **warning** Class ! already exists
CAUSE User is trying to add class !, and it already
exists.
ACTION To modify an existing class, use the MCLASS
command.
-------------------------------------------------------------
0420 MESSAGE **warning** Class ! already exists--class mode
ignored
CAUSE When adding a device with ADEV, the mode of the
class(es) specified may be given with the CMODE
parameter; however, it is ignored if the class
already exists.
ACTION Enter the LCLASS command to verify that the class
exists and to verify that LDEVs are associated with
the class name.
-------------------------------------------------------------
0421 MESSAGE **warning** level parameter ignored-path
parameter used instead.
CAUSE If both the LEVEL= and PATH= parameters are given
in the LPATH command, only the PATH= parameter is
used to determine that path to list.
ACTION None required.
-------------------------------------------------------------
0422 MESSAGE **warning** mgrname parameter ignored--path
parameter used instead.
CAUSE If both the MGR= and PATH= parameters are given in
the LPATH command, only the PATH= parameter is used
to determine that path to list.
ACTION None required.
-------------------------------------------------------------
0425 MESSAGE **warning** The correct delimiter at this level
is a "!"
CAUSE In specifying a path, all bus converters must be
followed by a "/", while all other devices and
adapters must be followed with a ".". SYSGEN knows
what the appropriate delimiter is, and warns the
user.
ACTION None required. SYSGEN replaces the incorrect
delimiter.
-------------------------------------------------------------
0426 MESSAGE Path (up to this level) changed to !
CAUSE Issued with previous to indicate what the correct
path is.
ACTION None required. SYSGEN has replaced the incorrect
delimiter.
-------------------------------------------------------------
0430 MESSAGE **warning** iopath ! (from DCC) does not exist
CAUSE The channel adapter (and possibly the bus
converter(s) for the path given by NMMGR for either
the DCC device adapter or the NM device adapter has
not been defined in SYSGEN. This causes the
configuration of the DCC devices to fail. This
message also occurs when SYSGEN is being used to
create a configuration for a system with devices at
different addresses (for example, running SYSGEN on
a 935 to create a 950 configuration).
ACTION If the configuration is intended for the current
machine, add the appropriate channel adapter(s) and
bus converter(s). If the configuration is intended
for another machine, make sure that the channel
adapters and bus converters are set up correctly
for that machine. If you are also creating an
NMMGR configuration for the target machine, SYSGEN
can be told to use that configuration for
validation purpose by issuing the RDCC command in
the SYSFILE configurator.
-------------------------------------------------------------
0431 MESSAGE **warning** path ! (from DCC) has a bad component
(too large, or non-numeric)
CAUSE The path specified in NMMGR for either the DCC
devices or the NS devices is invalid. It might be
either too large, or nonnumeric.
ACTION Change the path from within NMMGR to be valid.
-------------------------------------------------------------
0432 MESSAGE **warning** path name (from DCC) too long
CAUSE It is possible, though unlikely, that the path
specified from within NMMGR is too long to fit into
SYSGEN's data structures.
ACTION Shorten the path from within NMMGR.
-------------------------------------------------------------
0440 MESSAGE **warning** OUTDEV must equal LDEV: Correct value
used
CAUSE The output device must equal the input device for
all terminal devices. The LDEV number entered on
the ADEV or MDEV command is considered the input
device for terminals.
ACTION None required. SYSGEN has used the correct value.
-------------------------------------------------------------
0441 MESSAGE **warning** OUTDEV must be zero (0): Correct
value used
CAUSE All devices except for terminals and the streams
device(s) must have an output device of zero.
ACTION None required. SYSGEN has used the correct value.
-------------------------------------------------------------
1000 MESSAGE **error** class ! already exists
CAUSE The class name you have entered already exists.
ACTION Enter the LCLASS command to verify that the class
exists and to verify that LDEVs are associated with
the class name. If you were adding a class prior
to adding a device, use the ADEV command to add the
device and enter a name in the CLASS= parameter to
associate the device with a class name (other than
the system default).
-------------------------------------------------------------
1001 MESSAGE **error** classname does not exist
CAUSE You are trying to delete or modify a class name
that does not exist.
ACTION Use the LCLASS command to display existing class
names and associated devices.
-------------------------------------------------------------
1002 MESSAGE **error** new volume name already exists
CAUSE The volume name you are adding through the AVOL
command or the name you designate as the new volume
name through the MVOL command already exists.
ACTION Use the LVOL command to view existing volume names.
Choose an unused volume name.
-------------------------------------------------------------
1003 MESSAGE **error** can't read I/O volume configuration
file
CAUSE SYSGEN cannot read the configuration data file
IOVOLP. The program terminates.
ACTION Refer to the file system error for action to take.
-------------------------------------------------------------
1004 MESSAGE **error** can't modify I/O volume configuration
CAUSE SYSGEN cannot read the configuration data file
IOVOLP. The program terminates.
ACTION Refer to the file system error for action to take.
-------------------------------------------------------------
1005 MESSAGE **error** volume name does not exist
CAUSE The volume name you try to list, modify or delete
as the name designed in the volume parameter of the
LVOL, MVOL, or DVOL command does not exist.
ACTION Use the LVOL command without a parameter to display
all existing volume names. Choose an existing name
for the modify or delete operation.
-------------------------------------------------------------
1006 MESSAGE **error** can't add volume to I/O configuration
CAUSE SYSGEN cannot write the configuration data file
IOVOLP. The program terminates.
ACTION Refer to the file system error for action to take.
-------------------------------------------------------------
1007 MESSAGE **error** ldev ! is reserved for system console
CAUSE The LDEV you chose to add through the ADEV or AVOL
command or use as a new device number in the MDEV
or MVOL command is the LDEV reserved for the system
console.
ACTION Chose another unassigned LDEV for adding or
modifying a local device or volume.
-------------------------------------------------------------
1008 MESSAGE **error** ldev is already assigned to configured
volume
CAUSE The LDEV you chose to add through the AVOL command
or use as a new device in the MVOL command is
already assigned to a configured volume.
ACTION Chose another unassigned LDEV for the new or
modified volume.
-------------------------------------------------------------
1009 MESSAGE **error** can't read Ioldev configuration file
CAUSE SYSGEN cannot read the configuration data file
IOLDEVP. The program terminates.
ACTION Refer to the file system error for action to take.
-------------------------------------------------------------
MPE/iX 5.5 Documentation