"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 (Continued)
Input/Output (I/O) Configurator Messages (Continued).
1080 MESSAGE **error** must specify volume member name
CAUSE The VNAME parameter is omitted from the DVOL, MVOL,
or AVOL command.
ACTION Specify a volume name.
-------------------------------------------------------------
1081 MESSAGE **error** ldev ! is already configured as the
system master volume
CAUSE You are attempting to add a device with an LDEV
that has already been configured as the system
master volume.
ACTION Assign the device to another LDEV.
-------------------------------------------------------------
1082 MESSAGE **error** can't delete the system master volume
CAUSE You are attempting to delete the system master
volume that is not allowed.
ACTION Reenter the command, if you want to delete a device
other than the system master volume or any other
system member volume (MEMBERx), without referencing
a configured system's LDEV, product identification,
or class.
-------------------------------------------------------------
1083 MESSAGE **error** can't modify this parameter of the
system master volume
CAUSE You are attempting to modify a parameter of the
system master volume's identification and control
elements that is fixed and protected by the system.
ACTION Reenter the command if you wish to modify a
nonprotected parameter.
-------------------------------------------------------------
1087 MESSAGE **error** this path has an associated ldev
CAUSE This message occurs when the iopath you attempt to
delete or modify has a configured device or a
sublevel contains a device that would be deleted.
ACTION Use the LPATH command and LEVEL= parameter to list
paths and associated devices. Base your action on
the information.
-------------------------------------------------------------
1188 MESSAGE **error** Can't read from default file
CAUSE SYSGEN, for whatever reason, cannot read the
default configuration file IODFAULT.PUB.SYS.
Program dies.
ACTION Refer to the file system error for action to take.
-------------------------------------------------------------
1090 MESSAGE **error** outdev is too long
CAUSE This message appears when you enter a value that is
too long for the OUTDEV= parameter, or one that has
been added to IODFAULT.PUB.SYS.
ACTION Enter a new value of acceptable length. Contact
the software personnel responsible for maintaining
the system file.
-------------------------------------------------------------
1091 MESSAGE **error** manager name is too long
CAUSE The manager name that you entered exceeds the
acceptable number of characters for the string.
ACTION Enter a shorter name for your manager name.
-------------------------------------------------------------
1092 MESSAGE **error** bad default file
CAUSE There is a problem with the default configuration
file IODFAULT.PUB.SYS. The file has been edited and
an error has occurred. SYSGEN does not accept the
device operation.
ACTION Contact the software personnel responsible for
updating and maintaining this file.
-------------------------------------------------------------
1093 MESSAGE **error** default file records too long
CAUSE A device has been added to the IODFAULT.PUB.SYS
file, and the entry of one or more records exceeds
the acceptable maximum. SYSGEN does not accept the
device operation.
ACTION Contact the software personnel responsible for
updating and maintaining this file.
-------------------------------------------------------------
1094 MESSAGE **error** name too long in default file
CAUSE The device name, manager, or mode entry added to
IODFAULT.PUB.SYS is too long. SYSGEN does not
accept the device operation.
ACTION Contact the software personnel responsible for
updating and maintaining this file.
-------------------------------------------------------------
1095 MESSAGE **error** invalid integer in default file
CAUSE An invalid numeric value has been added to
IODFAULT.PUB.SYS. SYSGEN does not accept the device
operation.
ACTION Contact the software personnel responsible for
updating and maintaining this file.
-------------------------------------------------------------
1096 MESSAGE **error** couldn't write to internal default file
CAUSE For whatever reason, SYSGEN cannot write the device
information to the internal default file. Program
dies.
ACTION See the file system error for the action to take.
-------------------------------------------------------------
1097 MESSAGE **error** nonexistent volume: !
CAUSE The volume name entered is not recognized by the
system. (Misspelled?)
ACTION Correct and reenter the command.
-------------------------------------------------------------
1100 MESSAGE **error** path ! has no periods in it
CAUSE The referenced path has been improperly entered.
SYSGEN requires periods as separators in the path
definition to be able to check the components in
the path.
ACTION Reenter the path specification.
-------------------------------------------------------------
1101 MESSAGE **error** path ! ends in a period
CAUSE The referenced path is incomplete and ends in a
period, or has an extra period.
ACTION Reenter the path for the operation.
-------------------------------------------------------------
1102 MESSAGE **error** path ! has a bad component (too large,
or non-numeric)
CAUSE The iopath that you entered contains an alphabetic
or special symbol, a number that is too large, or
some other entry that cannot be recognized.
ACTION Reenter the path.
-------------------------------------------------------------
1103 MESSAGE **error** path name too long
CAUSE The path you have entered has too many levels.
ACTION Reenter the path.
-------------------------------------------------------------
1104 MESSAGE **error** path ! already exists.
CAUSE You are trying to add a path or device that already
exists.
ACTION Use the LPATH command and necessary level to list
the existing paths. If necessary, use the LDEV
command to list associated devices.
-------------------------------------------------------------
1105 MESSAGE **error** mode 'NONE' can't be used with other
modes
CAUSE The device mode NONE cannot be used with other
modes when more than one mode is assigned to a
device.
ACTION Either add or modify the device and assign NONE as
the only mode or enter the proper modes.
-------------------------------------------------------------
1106 MESSAGE **error** % permanent + % transient must be at
lease 100 percent
CAUSE The total amount of permanent and transient space
assigned to a volume must be at least 100 percent.
ACTION Increase either the transient or permanent
percentage until the sum is 100 percent.
-------------------------------------------------------------
1107 MESSAGE **error** Class name ! is too long.
CAUSE The class name entered exceeds either characters.
ACTION Reduce the number of characters in the class name.
-------------------------------------------------------------
1109 MESSAGE **warning** SYSGEN and NMMGR configuration
conflict!
CAUSE There is a conflict between SYSGEN's local
configuration and NMMGR's remote configuration.
This can occur over LDEVs, classes, and iopaths.
SYSGEN displays a subsequent message as to the
specific problem.
ACTION If the conflicts are not resolved through either
the local or remote configuration, the conflicting
NMMGR devices, classes,or paths are discarded. In
this case, several devices can be removed from the
network configuration. Resolve the conflicts
either through SYSGEN or NMMGR.
-------------------------------------------------------------
1115 MESSAGE keep configuration anyway (yes/no)?
CAUSE Some error has occurred, but SYSGEN is giving you
the option to either save the work you have done or
discard the changes and start over.
ACTION Enter YES if you wish to save, or NO if not.
-------------------------------------------------------------
1116 MESSAGE **error** can't delete NMMGR devices from SYSGEN
CAUSE You are attempting to delete a device assigned by
NMMGR. SYSGEN cannot add, delete,or modify NMMGR
devices.
ACTION Delete the device through NMMGR.
-------------------------------------------------------------
1118 MESSAGE **error** can't update iovol file
CAUSE For whatever reason, SYSGEN cannot update the
IPVOLP configuration data file. Program dies.
ACTION Refer to the file system error for the action to
take.
-------------------------------------------------------------
1121 MESSAGE **error** Bad device number (!) in ioldev file
CAUSE The LDEV number found in the file does not fit into
a 16-bit integer field.
ACTION Return to a known good set of configuration files.
-------------------------------------------------------------
1122 MESSAGE **error** can't delete NMMGR classes from SYSGEN
CAUSE Classes with the type NMMGR are displayed for
reference only and cannot be changed or deleted
through SYSGEN.
ACTION Run NMMGR to remove the class.
-------------------------------------------------------------
1123 MESSAGE **error** can't write ioclass file
CAUSE FWRITE failed to write to IOCLASSP file.
ACTION Refer to file system message, also returned.
-------------------------------------------------------------
1124 MESSAGE **error** SYSGEN ans NMMGR are both using class !
-------------------------------------------------------------
1125 MESSAGE **error** SYSGEN and NMMGR are both using ldev !
CAUSE There is an LDEV conflict between SYSGEN's local
configuration and NMMGR's remote configuration.
SYSGEN displays a subsequent message as to the
specific problem. For example, SYSGEN and NMMGR
are both using LDEV 38.
ACTION Change the LDEV for either the SYSGEN device
through the I/O configurator or the NMMGR device.
If the LDEV is not changed, SYSGEN's device is
used, and the remote device is logically removed
from the overall configuration.
-------------------------------------------------------------
1126 MESSAGE **error** SYSGEN and NMMGR are both using path !
CAUSE There is a path conflict between SYSGEN's local
configuration and NMMGR's remote configuration.
SYSGEN displays a subsequent message as to the
specific problem. For example, SYSGEN and NMMGR
are both using LDEV 38.
ACTION Change the path for either the SYSGEN device
through the I/O configurator or NMMGR. If the path
is not changed, SYSGEN's device is used and the
remote device is logically removed from the overall
configuration.
-------------------------------------------------------------
1127 MESSAGE **error** FFIND failed on iopath file
CAUSE SYSGEN has encountered an internal system error in
attempting to initialize the processing of the
iopath configuration file.
ACTION Contact the software personnel responsible for
updating and maintaining these files.
-------------------------------------------------------------
1130 MESSAGE **error** can't change path ! to !
CAUSE The iopath you are modifying as the TO= parameter
already exists and has an assigned device, or does
not exist and needs to be added in hierarchical
order. The iopaths entered as FROM= and TO= are in
conflict.
ACTION As this normally occurs from an entry mistake,
reenter the proper path(s); otherwise, use the
APATH command to add the iopath structure.
-------------------------------------------------------------
1131 MESSAGE **warning** path not changed for ldev !
CAUSE The iopath for the device referenced cannot be
changed to the new path, for whatever reason.
ACTION Enter a new iopath that exists and does not have an
assigned device or use the APATH command to add the
iopath structure in proper level sequence.
-------------------------------------------------------------
1133 MESSAGE **error** can't delete NMMGR paths from SYSGEN
CAUSE An NMMGR path, once defined through NMMGR and set
through the SYSFILE RDCC command, cannot be deleted
through the I/O configurator DPATH command.
ACTION None.
-------------------------------------------------------------
1134 MESSAGE **error** can't change NMMGR paths from SYSGEN
CAUSE An NMMGR path, once defined through NMMGR and set
through the SYSFILE RDCC command, cannot be
modified through the I/O configurator MPATH
command.
ACTION None.
-------------------------------------------------------------
1135 MESSAGE NMMGR path ! is incomplete
CAUSE Usually, this is caused by setting an improper file
as the remote configuration file through the SYSGEN
configurator RDCC command. Currently, the message
reads NMMGR path 9.0 is incomplete.
ACTION Through RDCC, designate a valid remote
configuration file.
-------------------------------------------------------------
1136 MESSAGE **error** Volume configuration is corrupted!
CAUSE The permanent configuration data file IOVOLP
contains an error as displayed. The error occurs
from the previous configuration KEEP or through an
improper addition to IODFAULT.PUB.SYS. Specific
details are in subsequent messages.
ACTION Contact the software personnel responsible for
updating and maintaining these files.
-------------------------------------------------------------
1137 MESSAGE ldev ! is invalid
CAUSE This message furnishes the LDEV identity of the
previous volume configuration corruption message.
ACTION See the volume configuration corruption message.
-------------------------------------------------------------
1138 MESSAGE !% transient is invalid
CAUSE This message gives the transient percentage of the
previous volume configuration corruption message.
ACTION See the volume configuration corruption message.
-------------------------------------------------------------
1139 MESSAGE !% permanent is invalid
CAUSE This message gives the permanent percentage of the
previous volume configuration corruption message.
ACTION See the volume configuration corruption message.
-------------------------------------------------------------
MPE/iX 5.5 Documentation