 |
» |
|
|
 |
|  |  |
Run-Time Codes: System Activity Indicator |  |
When the system is up and running, the LED display issues an
alternating run-time message code as FxFF, where "x" is a hexadecimal digit from 0-A. The digit represents the percentage of non-idle time. DCC Error Codes |  |
Toward the end of system start, the data communication
configurator (DCC) executes. This creates the LINK and DTS
managers defined in NMCONFIG.PUB.SYS. If the DCC completes
successfully, the following message is displayed: However, if an error occurs, one of the following error messages is displayed. These messages contain a DCC error number and description. In the messages below, the P-L number is a DCC procedure
number and DCC location number. These values are needed by your local DCC support person when a problem is reported. The SSSSSSSS in some messages is an 8-digit hexadecimal value. MMM and LLL are decimal values. PATH is a NMCONF path or LLIO physical path.  |  |  |  |  | NOTE:
Currently, the last message issued to the console during a system startup is DCC STARTUP - ERROR. This is not an actual error. Enter a Return and the system prompt MPE/XL: is displayed. |  |  |  |  |
- MESSAGE
DCC ERROR P-L, (LLIO status SSSSSSSS).
- CAUSE
Low-level I/O services reported status SSSSSSSS. DCC employs
LLIO services io_config, io_get_frame, io_release_frame,
io_get_timer, and io_send.
- ACTION
For more information decode SSSSSSSS.
- MESSAGE
DCC ERROR P-L, (reply status SSSSSSSS, MSG descriptor MMM).
- CAUSE
Reply message MMM contained reply status SSSSSSSS.
- ACTION
For more information decode MMM and SSSSSSSS.
- MESSAGE
DCC ERROR P-L, (NMCONF file error SSSSSSSS).
NM path: PATH
- CAUSE
NMCONFIG file may not exist, or it is locked by another entity.
- ACTION
check to see if NMCONFIG.PUB.SYS exists, if it's a NMCONF type file, or if it is locked by another entity.
- MESSAGE
DCC ERROR P-L, (NMCONF record error SSSSSSSS).
NM path: PATH
- CAUSE
The DCC surrogate was unable to read an NMCONFIG record, or the data in NMCONFIG.PUB.SYS was not validated or is corrupted.
- ACTION
Validate NMCONFIG.PUB.SYS again (for example, VALIDATE DTS/LINK) and reboot more information decode SSSSSSSS.
- MESSAGE
DCC ERROR P-L, configuration record data was invalid.
NM path: PATH
- CAUSE
data in NMCONFIG.PUB.SYS was not validated or is corrupted.
- ACTION
Contact your support personnel. Validate NMCONFIG.PUB.SYS again (for example, validate the DTS/LINK) and reboot.
- MESSAGE
DCC ERROR P-L, (HILO status SSSSSSSS. ldev LLL).
- CAUSE
high-level I/O services reported status SSSSSSSS for logical
device number LLL. DCC employs HILO services
configure_hilo_device, allocate_device and ldm-port.
- ACTION
Logical device numbers <99 should not be employed by data comm products.
- MESSAGE
DCC ERROR P-L, (buffer manager status SSSSSSSS).
- CAUSE
data comm buffer manager reported status SSSSSSSS.
- ACTION
check buffer-size and number-of-buffer fields in
NMCONFIG.PUB.SYS. For more information decode SSSSSSSS.
- MESSAGE
DCC ERROR P-L, (External procedure not found).
- CAUSE
Native library did not contain expected data comm manager
procedure. Either NMCONFIG.PUB.SYS or the image is corrupted.
- ACTION
Validate NMCONFIG.PUB.SYS again and reboot.
- MESSAGE
DCC ERROR P-L, (memory management status SSSSSSSS).
- CAUSE
memory management reported status SSSSSSSS. DCC could not acquire
memory. This is serious condition and requires the
intervention of your Hewlett-Packard Support Representative.
- ACTION
Contact your Hewlett-Packard Support Representative.
- MESSAGE
DCC ERROR P-L, (Ports status SSSSSSSS).
- CAUSE
Ports reported status SSSSSSSS. DCC employs ports procedures
create_port and extended_receive.
- ACTION
For more information, decode SSSSSSSS.
- MESSAGE
DCC ERROR P-L, time out on reply msg, descriptor MMM.
- CAUSE
DCC did not receive reply message MMM in the allotted time.
- ACTION
Contact your DCC support personnel.
- MESSAGE
DCC ERROR P-L, too many DTCs configured.
- CAUSE
NMCONFIG.PUB.SYS contains more than the supported ten DTCs.
- ACTION
Remove excess DTCs and reboot.
- MESSAGE
DCC ERROR P-L, link name specified for DTS does not exist.
- CAUSE
The link name in DTS.DTC screen was not found. The name may be
incorrect in either the LINK screen or the DTC screen or the
NMCONFIG.PUB.SYS file may contain more than the supported two
links.
- ACTION
Remove excess links and reboot.
- MESSAGE
DCC ERROR P-L, link name for specified DTS is not available.
- CAUSE
Some error occurred during link configuration.
- ACTION
Usually the error is hardware related; the card is not in the configured
slot, the card is not connected to the LAN, and so on.
There should be another DCC error message displayed that relates to the
link configuration error. Check additional error messages.
- MESSAGE
DCC ERROR P-L, TOO MANY LINKS CONFIGURED.
- CAUSE
NMCONFIG.PUB.SYS contains more than the supported two links.
- ACTION
Remove excess links and reboot.
- MESSAGE
DCC ERROR P-L, message received on wrong subqueue.
- CAUSE
Valid message received on wrong subqueue: the message was
rejected.
- ACTION
None.
- MESSAGE
DCC ERROR P-L, unrecognized message received. All junk mail will
be rejected.
- CAUSE
Unrecognized message received.
- ACTION
None.
- MESSAGE
DCC ERROR P-L, internal DCC logic error
- CAUSE
Unknown.
- ACTION
Contact your local DCC support person.
- MESSAGE
DCC ERROR P-L, (DAM error status SSSSSSSS).
LLIO path: PATH
- CAUSE
IEEE802.3 DAM (for example, the link) reported an error during
configuration. Usually the error is hardware related; for
example, the card is not in the configured slot or the card is not connected to the LAN.
- ACTION
Fix and reboot the system.
- MESSAGE
DCC warning PL, add ldev to class failure (HILO status
SSSSSSSS, ldev LLL).
- CAUSE
Classes are not supported.
- ACTION
Remove class from all profiles and reboot.
- MESSAGE
DCC ERROR P-L, (External procedure not found).
- CAUSE
This error is printed during each system startup. It does not affect the startup however, and the startup is
successful even though the message is printed.
- ACTION
None.
High-Priority Machine Check (HPMC) Errors |  |
High-priority machine check messages take the form: - F1
- MESSAGE
No message. System halts. (E) - CAUSE
instruction TLB parity error occurs. - ACTION
Contact your Hewlett-Packard Support Representative.
- F2
- MESSAGE
No message. System halts. (E) - CAUSE
data TLB parity error occurs. instruction Unit. - ACTION
Contact your Hewlett-Packard Support Representative.
- F3
- MESSAGE
No message. System halts. (E) - CAUSE
Mid-bus address parity error occurs, or no slave response. - ACTION
Contact your Hewlett-Packard Support Representative.
- F4
- MESSAGE
No message. System halts. (E)
- CAUSE
Mid-bus read data parity error occurs. The cache (master) performs a
read transaction and detects bad parity from the slave. - ACTION
Contact your Hewlett-Packard Support Representative.
- F5
- MESSAGE
No message. System halts. (E) - CAUSE
Multiple bit read error occurs. - ACTION
Contact your Hewlett-Packard Support Representative.
- F6
- MESSAGE
No message. System halts. (E)
- CAUSE
Mid bus write data parity error occurs.
- ACTION
Contact your Hewlett-Packard Support Representative.
- F7
- MESSAGE
No message. System halts. (E) - CAUSE
Mid-bus CMD or external interrupt request register data parity error occurs, or a mid-bus timeout occurs. - ACTION
Contact your Hewlett-Packard Support Representative.
- F8
- MESSAGE
No message. System halts. (E) - CAUSE
cache tag parity error occurs. - ACTION
Contact your Hewlett-Packard Support Representative.
- F9
- MESSAGE
No message. System halts. (E)
- CAUSE
Data cache read parity error occurs.
- ACTION
Contact your Hewlett-Packard Support Representative.
- FA
- MESSAGE
No message. System halts. (E)
- CAUSE
Floating-point high priority machine check.
- ACTION
Contact your Hewlett-Packard Support Representative.
- FB
- MESSAGE
No message. System halts. (E)
- CAUSE
Instruction parity error occurs.
- ACTION
Contact your Hewlett-Packard Support Representative.
 |  |  |  |  | NOTE:
HPMC codes FC through FF are currently undefined. If more than one error occurs, only the error with the smallest error code is displayed. For example, if both errors F4 and F7 occur, only F4 is displayed. |  |  |  |  |
Console Messages for Log File Errors |  |
Log file errors are reported in one of the following messages. Refer to Table 13-2 “Log File Errors” for a summary of log file error numbers, their meaning, and whether they are recoverable or irrecoverable errors. LOG FILE NUMBER xxxx ERROR #nn. LOGGING STOPPED indicates that an
irrecoverable error occurred. System logging is disabled until the next system
startup. LOG FILE NUMBER xxxx ERROR #nn. LOGGING SUSPENDED indicates that a recoverable error occurred. A recoverable error temporarily suspends logging until the RESUMELOG command is issued. Table 13-2 Log File Errors | ERROR NO. | ERROR | RECOVERABLE? |
|---|
| 1 | Input/output error in accessing the system disk. | No
| | 2 | Input/output error in accessing disk log file. | No
| | 21 | data parity error. | No
| | 26 | Transmission error. | No
| | 27 | Input/output timeout. | No
| | 28 | data overrun. | No
| | 29 | SIO failure. | No
| | 30 | Unit failure. | No
| | 46 | Insufficient disk space to create log file. | Yes
|
Table 13-3 Log File Errors (Continued) | ERROR NO. | ERROR | RECOVERABLE? |
|---|
| 47 | Input/output error on file label. | No
| | 57 | Virtual memory not sufficient. | No
| | 61 | Group (PUB) disk space exceeded in creating log file. | Yes
| | 62 | Account (SYS) disk space exceeded in creating log file. | Yes
| | 63 | Group disk space exceeded in allocating new extent to the log file. |
Yes
| | 64 | Account disk space exceeded in allocating new extent to the log file.
| Yes
| | 100 | A file of the same name as the current log file already exists in the system file directory. | Yes
| | 102 | Directory input/output error. | No
| | 103 | System directory overflow. | No
| | 105 | Illegal variable block structure. | No
|
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.
- 1010
- MESSAGE
**error** can't read Ioclass configuration file - CAUSE
SYSGEN cannot read the configuration data file IOCLASSP. The program terminates. - ACTION
Refer to the file system error for action to take.
- 1011
- MESSAGE
**error** can't reset Ioldev file
- 1012
- MESSAGE
**error** can't reset Ioclass file
- 1013
- MESSAGE
**error** can't reset Iovolume file
- 1015
- MESSAGE
**error** A device can only have ! volume classes. - CAUSE
Too many volume classes have been assigned to a volume through
the CLASS= parameter. - ACTION
Limit the number of volume classes to the number that appears in the message.
- 1016
- MESSAGE
**error** A device can only have ! classes. - CAUSE
Too many classes have been assigned to an LDEV through the CLASS= parameter. - ACTION
Limit the number of classes to the number that appears in the message.
- 1017
- MESSAGE
**error** can't write to Ioldev configuration file
- 1018
- MESSAGE
**error** unknown device type - CAUSE
The device type entered in the TYPE= parameter is unsupported, or incorrectly specified. - ACTION
Verify the type has been entered correctly, and is an HP- supported device. The file IODFAULT.PUB.SYS contains all currently supported devices. If your device is not in IODFAULT, you must add it as a USER device. Hewlett-Packard only supports devices in the IODFAULT file.
- 1019
- MESSAGE
**error** device mode too long
- 1020
- MESSAGE
**error** illegal device mode for this device - CAUSE
The device mode entered in the MODE= parameter is not
appropriate for this particular device. - ACTION
Enter an appropriate mode. If necessary, check the IODFAULT file for permissible modes.
- 1021
- MESSAGE
**error** This device is not supported. - CAUSE
You have entered a product identification that does not exist in IODFAULT.PUB.SYS. Usually, the error is a simple entry mistake. - ACTION
Enter the proper Hewlett-Packard product IDs. If necessary, check for supported product IDs.
- 1022
- MESSAGE
**error** iopath level mismatch - CAUSE
In specifying the MADDRESS command, the paths of the FROM= and TO= parameters have different levels, for example, MA 8.4.8 4.2. Usually, an entry mistake. - ACTION
Correct the path entry
- 1023
- MESSAGE
**error** can't find record in Ioldev configuration file - CAUSE
SYSGEN cannot find a particular record in the configuration
data file. The program terminates. - ACTION
Refer to the file system error for action to take.
- 1024
- MESSAGE
**error** # new devices must watch # old devices
- 1025
- MESSAGE
**error** can't update record in Ioldev configuration file
- 1026
- MESSAGE
**error** can't open I/O default file
- 1027
- MESSAGE
**error** iopath already exists
- 1029
- MESSAGE
**error** missing physical file for physical manager
- 1030
- MESSAGE
**error** missing physical manager for physical file
- 1031
- MESSAGE
**error** missing logical file for logical manager
- 1032
- MESSAGE
**error** missing logical manager for logical file
- 1034
- MESSAGE
**error** iopath does not exist
- 1037
- MESSAGE
**error** manage ! is not in the configuration
- 1038
- MESSAGE
**error** physical manager does not exist.
- 1039
- MESSAGE
**error** logical manager does not exist
- 1040
- MESSAGE
**error** can't write to Iopath configuration file
- 1041
- MESSAGE
**error** can't delete I/O path.
- 1042
- MESSAGE
**error** can't find record in Iopath configuration file
- 1043
- MESSAGE
**error** can't update Iopath configuration file
- 1044
- MESSAGE
**error** can't read from Iopath configuration file
- 1045
- MESSAGE
**error** can't open I/O default file
- 1046
- MESSAGE
**error** I/O default file does not exist
- 1047
- MESSAGE
**warning** ldev ! already has ! classnames.
- 1048
- MESSAGE
class '!' cannot be added to it.
- 1049
- MESSAGE
**error** iopath must be added in an hierarchical order
- 1050
- MESSAGE
I/O path specified has pending devices.
- 1051
- MESSAGE
Want to delete all of them (yes/no) ?
- 1052
- MESSAGE
** no iopath is deleted **
- 1053
- MESSAGE
**error** this iopath has no logical device manager
- 1054
- MESSAGE
**error** manager '!' currently used.
- 1055
- MESSAGE
it cannot be deleted
- 1056
- MESSAGE
**error** ldev is not yet configured
- 1057
- MESSAGE
**error** ldev is not a disc
- 1058
- MESSAGE
**error** ldev ! is configured as a system volume.
- 1059
- MESSAGE
it cannot be deleted
- 1060
- MESSAGE
**error** ldev ! already exists
- 1061
- MESSAGE
**warning** ldev ! does not exist
- 1062
- MESSAGE
it must be replaced with a disc type device
- 1063
- MESSAGE
**error** iopath is currently referenced by a
configurated ldev
- 1064
- MESSAGE
it cannot be deleted
- 1065
- MESSAGE
**error** iopath ! is currently referenced by a
configurated ldev
- 1066
- MESSAGE
**error** ldev ! must be the system disc
- 1067
- MESSAGE
**error** ldev ! must be the system console
- 1069
- MESSAGE
**error** invalid mode parameter
- 1071
- MESSAGE
*error** iopath is already assigned
- 1072
- MESSAGE
**error** please specify an associated manager
- 1076
- MESSAGE
**error** iopath ! does not exist
- 1077
- MESSAGE
**error** can't delete system console
- 1078
- MESSAGE
**error** can't delete system disc - CAUSE
You are attempting to delete the system disk through the DDEV command by referencing its LDEV number, product identification, or class. The system volume (MASTER) cannot be deleted from the configuration. - ACTION
Reenter the command, if you want to delete a device other than the system disk or another system volume (MEMBERx), without referencing a configured disc's LDEV, product identification, or class.
- 1079
- MESSAGE
**error** can't delete system tape drive - CAUSE
You are attempting to delete the system tape drive through DDEV command by referencing its LDEV number, product identification, or class. - ACTION
Reenter the command, if you want to delete a device other than the system tape drive.
- 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.
|