"Nonclass" Errors
MPE documents | |
 Complete PDF | |
| Table of Contents | |
| E0701 Volume II | |
| E0300 Volume I | |
| E0300 Volume II ♥ | |
| E0300 Volume III | |
| E0394 Volume I | |
| E0796 Volume II | |
| E0494 Volume III |
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:
DCC STARTUP - OK!
 |
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. |
DCC Messages
- 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:
XXF0 - XXFF
HPMC Messages
- 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 9-1 "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.
Log File Error Messages
| 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 |
| 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.
- 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.
- 1140
- MESSAGE
**error** Ldev configuration is corrupted!
- CAUSE
The permanent configuration data file IOLDEV is corrupted. The problem is the record size, that was probably assigned through the previous configuration change or through an improper addition to IODFAULT.PUB.SYS.
- ACTION
Contact the software personnel responsible for updating and maintaining these files.
- 1141
- MESSAGE
rsize ! is invalid
- CAUSE
This message, following the LDEV configuration corruption gives the record size in question.
- ACTION
Go back to a known good configuration. If the problem recurs, contact SE.
- 1142
- MESSAGE
**error** Path configuration is corrupted!
- CAUSE
The permanent configuration data file IOPATH 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 additional messages.
- ACTION
Contact the software personnel responsible for updating and maintaining these files.
- 1143
- MESSAGE
physical manager priority of ! is invalid
- CAUSE
This message gives the physical manager's priority, that is being questioned.
- ACTION
See the path configuration corruption message above.
- 1144
- MESSAGE
! max. expected concurrent I/Os is invalid
- CAUSE
This message gives the maximum number of concurrent I/Os, that is being questioned.
- ACTION
See the path configuration corruption message above.
- 1145
- MESSAGE
**error** Class configuration is corrupted!
- CAUSE
The number of DCC devices field has been corrupted in IOCLASSP.
- ACTION
Go back to a known good configuration. If problem recurs, contact SE.
- 1146
- MESSAGE
**error** USER device requires all parameters!
- CAUSE
You have omitted one or more parameters.
- ACTION
Reenter command with all parameters.
- 1147
- MESSAGE
**error** Can't change to id=!
- CAUSE
You cannot change the ID to this value. Most often USER.
- ACTION
Reenter command with proper ID= parameter.
- 1150
- MESSAGE
**error** Can't seek to beginning of ioclass file
- CAUSE
SYSGEN encountered an internal system error in attempting to initialize the ioclass configuration file for processing.
- ACTION
Contact the software personnel responsible for updating and maintaining these files.
- 1153
- MESSAGE
**error** Couldn't determine appropriate class mode for ldev !
- CAUSE
SYSGEN has encountered an internal system error in attempting to obtain the class and mode from the ioclass configuration file.
- ACTION
Contact the software personnel responsible for updating and maintaining these files.
- 1154
- MESSAGE
**error** Class ! can't accept ldev !--incompatible modes
- CAUSE
You have attempted to include a device whose mode is incompatible with the other devices in this class.
- ACTION
Reenter the command without the device under question.
- 1155
- MESSAGE
**error** Class ! can't accept mode !
- CAUSE
You have attempted to add a mode that is incompatible with some or all the devices in this class.
- ACTION
Review the conflict and reenter the command with the proper MODE= parameter.
- 1156
- MESSAGE
**error** Too many devices in class !--device not added
- CAUSE
A device class can only hold so many devices--currently 255.
- ACTION
Remove other devices from class, or create a new class.
- 1157
- MESSAGE
**error** class info is corrupt (class !)
- CAUSE
The records of the IOCLASS configuration file, that contains the information for this LDEV, is corrupted.
- ACTION
Contact the software personnel responsible for updating and maintaining these files.
- 1158
- MESSAGE
**error** Class VTERM is reserved
- CAUSE
You cannot assign this name to a class. The system has reserved its usage for a special purpose.
- ACTION
Reenter the command with another name for the class.
- 1159
- MESSAGE
**error** Class ! is reserved and cannot be deleted
- CAUSE
You have attempted to delete a class that the system has reserved for its special purpose.
- ACTION
None.
- 1160
- MESSAGE
**error** Class ! is reserved and cannot be changed
- CAUSE
You have attempted to modify a class that the system has reserved for its own special purpose.
- ACTION
None.
- 1161
- MESSAGE
**error** Can't create class ! with mode !--class not added
- CAUSE
You have attempted to create a class with an inconsistent mode. SYSGEN does not accept the class operation.
- ACTION
Review the conflict and reenter the command with the proper mode.
- 1162
- MESSAGE
**error** ldev ! does not exist
- CAUSE
You have attempted to add an LDEV to this class that does not exist.
- ACTION
Reenter command with a proper LDEV number.
- 1163
- MESSAGE
**error** class file or DCC mode bad--mode is !
- CAUSE
SYSGEN's class file is in conflict with NMMGR's configuration file. The displayed mode is in question.
- ACTION
Contact software personnel responsible for updating and maintaining these configuration files.
- 1164
- MESSAGE
**error** Can't remove class ! from device !
- CAUSE
You are attempting to delete a class from a device, that could cause the system not to be able properly determine its function.
- ACTION
Contact software personnel responsible for updating and maintaining this file.
- 1165
- MESSAGE
**error** mpe type only configurable for USER devices
- CAUSE
These device types are only associated with the 'classic' 16-bit HP 3000 systems and are honored only to support those programs ported over from those systems. Therefore, they are restricted to USER devices.
- ACTION
Assigned to USER devices or contact software personnel who is responsible for maintaining these file for adivice.
- 1166
- MESSAGE
**error** mpe subtype only configurable for USER devices
- CAUSE
These device subtypes are only associated with the 'classic' 16-bit HP 3000 systems and are honored only to support those programs ported over from those systems. Therefore, they are restricted to USER devices.
- ACTION
Assigned to USER devices or contact software personnel who is responsible for maintaining these file for advice.
- 1167
- MESSAGE
**error** MODE=NLIO not configurable for this device
- CAUSE
Setting MODE equal to NLIO is allowed only for printers and terminals. You probably set it for a different device.
- ACTION
Check the configuration and specify an appropriate device.
- 1170
- MESSAGE
**error** Use the adev command to add devices
- CAUSE
You have attempted to add a device that has not been defined through the parameters to this command.
- ACTION
Add the device prior to using this command.
- 1171
- MESSAGE
**error** Can't change this path to be a device
- CAUSE
You have attempted to change a path designation to be a device. SYSGEN does not accept the operation.
- ACTION
None.
- 1172
- MESSAGE
**error** Can't change ldevs to paths or paths to ldevs
- CAUSE
You have attempted to interchange LDEVs and paths. SYSGEN does not accept the operation.
- ACTION
Reenter the command with the proper parameters.
- 1173
- MESSAGE
**error** Use the mdev command to modify devices
- CAUSE
You have attempted to change some of the device configuration elements within this command. SYSGEN does not accept the operation.
- ACTION
None.
- 1180
- MESSAGE
**error** OUTDEV invalid
- CAUSE
You have attempted to designate a device that is incompatible with OUTDEV requirements. SYSGEN does not accept the operation.
- ACTION
Reenter the command with the proper device.
Miscellaneous (MISC) Configurator Messages
- 0500
- MESSAGE
**warning** # of rins must be at least !--misc value changed.
- CAUSE
You have requested a number of RINs that is below the minimum.
- ACTION
Reenter the command with the minimum value.
- 0501
- MESSAGE
**warning** # of global rins must be at least !--misc value changed.
- CAUSE
You have requested a number global RINs that is less than the minimum.
- ACTION
Reenter the command with the minimum value.
- 0502
- MESSAGE
**warning** rin ! does not exist
- CAUSE
You have entered a RIN that the system does not recognize.
- ACTION
Reenter the command with the proper RIN.
- 0503
- MESSAGE
**warning** Unless you've made a tape, any rins
- CAUSE
This warning is to let you know that the deleted RINs only disappear upon a system update.
- ACTION
Create boot tape and update the system.
- 0504
- MESSAGE
you've deleted will no longer be deleted.
- CAUSE
This is the second half of message above.
- ACTION
None.
- 0510
- MESSAGE
**warning** default NM stack size cannot be greater than maximum.
- CAUSE
You have requested a default native mode stack size that is greater than the specified maximum value.
- ACTION
Either reenter the command with a valid stack size or set to the maximum.
- 0511
- MESSAGE
**warning** default CM stack size cannot be greater than maximum.
- CAUSE
You have requested a default compatibility mode stack size that is greater than the specified maximum value.
- ACTION
Either reenter the command with a valid stack size or set to the maximum.
- 0512
- MESSAGE
**warning** default HEAP size cannot be greater than maximum.
- CAUSE
You have requested a default heap size greater than the specified maximum value.
- ACTION
Either reenter the command with a valid heap size or set to the maximum.
- 0514
- MESSAGE
fault reduced to !
- CAUSE
This message displays resulting default for message above.
- ACTION
None.
- 0523
- MESSAGE
**warning** DEFAULT NM STACK must be a multiple of 4096. New value is !.
- CAUSE
The nm parameter must be a multiple of 4096 (page_size).
- ACTION
SYSGEN has rounded DEFAULT NM STACK up to next multiple of 4096. No further action required.
- 0524
- MESSAGE
**warning** MAXIMUM NM STACK must be a multiple 4096. New value is !.
- CAUSE
The maxnm parameter must be a multiple of 4096 (page_size).
- ACTION
SYSGEN has rounded MAXIMUM NM STACK up to next multiple of 4096. No further action required.
- 0525
- MESSAGE
**warning** DEFAULT HEAP must be a multiple of 4096. New value is !.
- CAUSE
The heap parameter must be a multiple of 4096 (page_size).
- ACTION
SYSGEN has rounded DEFAULT HEAP up to next multiple of 4096. No further action required.
- 0526
- MESSAGE
**warning** MAXIMUM NM HEAP must be a multiple of 4096. New value is !.
- CAUSE
The maxheap parameter must be a multiple of 4096 (page_size).
- ACTION
SYSGEN has rounded MAXIMUM NM HEAP up to next multiple of 4096. No further action required.
- 1000
- MESSAGE
**error** can't read MISC configuration data
- CAUSE
SYSGEN encountered an error in trying to read the miscellaneous configuration data file.
- ACTION
Refer to the file system error.
- 1001
- MESSAGE
**error** system ID too long
- CAUSE
You have entered a system ID that has too many characters. The limit is eight.
- ACTION
Reenter the command with the proper system ID value.
- 1005
- MESSAGE
**error** can't display parameter ! in misc display table
- CAUSE
SYSGEN has encountered an error in trying to display this parameter from the miscellaneous configuration data file.
- ACTION
Contact software personnel responsible for updating and maintaining these files.
- 1007
- MESSAGE
**error** prompt too long
- CAUSE
You have requested a string for the prompt that has too many characters for the configuration file entry.
- ACTION
Reenter the command with a shorter string.
- 1008
- MESSAGE
**error** Can't get an extra data segment for rin table
- CAUSE
Same as message.
- ACTION
Refer to system error message for action.
- 1009
- MESSAGE
**error** Can't initialize extra data segment for rin table
- CAUSE
SYSGEN has encountered an internal system error in attempting to initialize the new space granted for RIN table expansion.
- ACTION
Refer to system or file system error for action.
- 1010
- MESSAGE
**error** Can't list rins
- CAUSE
SYSGEN has encountered a system error in trying to list the RINs as requested.
- ACTION
Refer to system error or file system error message for the action to undertake.
- 1011
- MESSAGE
**error** Can't alter extra data segment for rin table
- CAUSE
SYSGEN has encountered an internal system error in trying to make changes in the new area of the RIN table.
- ACTION
Refer to system error message for the action.
- 1012
- MESSAGE
**error** Can't read from extra data segment for rin table
- CAUSE
SYSGEN has encountered a system error in trying to read the RIN table in trying to process your command.
- ACTION
Refer to the system or file system error for the action.
- 1013
- MESSAGE
**error** Can't free extra data segment for rin table
- CAUSE
SYSGEN has encountered a system error in trying to release a portion of the RIN table in trying to process your command.
- ACTION
Refer to the system error for the action.
- 1014
- MESSAGE
**error** Can't get rin table size from extra data segment
- CAUSE
SYSGEN has encountered as error in trying to obtain the RIN table size while processing your command.
- ACTION
Refer to the system error for action.
- 1020
- MESSAGE
**error** can't write MISC configuration data
- CAUSE
SYSGEN has encountered an error while trying to write to the miscellaneous configuration data file.
- ACTION
Refer to the system or file systems error for action.
- 1021
- MESSAGE
**error** Only the factory can change this.
- CAUSE
You have attempted to change an item in the miscellaneous configuration data that is reserved for factory maintenance.
- ACTION
None.
- 1025
- MESSAGE
**error** sysprompt string in MISC configuration corrupt!
- CAUSE
SYSGEN has encountered an error in trying to obtain the system prompt string value.
- ACTION
Contact software personnel responsible for updating and maintaining these files.
- 1026
- MESSAGE
**error** ciprompt string in MISC configuration corrupt!
- 1030
- MESSAGE
**error** configuration files incompatable with this version of SYSGEN
- 1031
- MESSAGE
SYSGEN version = ! Config files version = !
Logging (LOG) Configurator Messages
- 0500
- MESSAGE
**warning** of logging processes is smaller than LID table.
- CAUSE
Reducing the value of nlogprocs below what is currently used the LID table to be rebuilt from scratch, losing any current logging IDs (only effect if UPDATE CONFIG or INSTALL done with tape made from this config).
- ACTION
If you want logging IDs preserved, raise the value. Otherwise, ignore it.
- 0501
- MESSAGE
LID table on tape will be empty!
- 1000
- MESSAGE
**error** can't read LOG configuration data
- CAUSE
SYSGEN cannot read the configuration data file LOGP for whatever reason. Program dies.
- ACTION
Refer to the file system error for action to take.
- 1001
- MESSAGE
**error** can't write LOG configuration data
- CAUSE
SYSGEN cannot write the configuration data file LOGP for whatever reason. Program dies.
- ACTION
Refer to the file system error for action to take.
System File (SYSFILE) Configurator Messages
- 0201
- MESSAGE
**warning** boot image ! not deleted
- CAUSE
The boot image cannot be replaced or deleted.
- ACTION
None for system manager normally. Should be handled by personnel with programming or SYSFILEP file maintenance responsibilities.
- 0202
- MESSAGE
**warning** File not an IPL file. Include anyway?
- 0204
- MESSAGE
**warning** no NMCONFIG file in this configuration
- CAUSE
A remote configuration file has not been designated through the SYSFILE RDCC command. SYSGEN uses the default NMCONFIG.PUB.SYS file if it exists.
- ACTION
Enter a remote configuration file name through RDCC in the SYSFILE Configurator. If a remote configuration does not exist, create one through NMMGR.
- 0205
- MESSAGE
**warning** ! is now the NMCONFIG file
- CAUSE
This message is issued with the prior message, indicating the default remote configuration file that is used. Usually, NMCONFIG.PUB.SYS is now the NMCONFIG file appears.
- ACTION
If you want a different remote configuration file used, designate the file through the SYSFILE configurator RDCC command.
- 1000
- MESSAGE
**error** can't create temporary segment file
- 1001
- MESSAGE
**error** can't initialize temporary segment file
- 1002
- MESSAGE
**error** can't write to temporary segment file
- 1003
- MESSAGE
**error** You must specify a CM SL first
- 1004
- MESSAGE
**error** can't find system program file
- CAUSE
Nonexistent file, misspelled name, and so on.
- 1005
- MESSAGE
**error** segment name already exists
- 1006
- MESSAGE
**error** can't create temporary CM SL
- 1007
- MESSAGE
**error** can't open system SL
- 1008
- MESSAGE
**error** can't update system file configuration
- CAUSE
SYSGEN cannot update the SYSFILE for whatever reason. The program dies.
- ACTION
Refer to the file system error for action to take.
- 1009
- MESSAGE
**error** can't read from system SL
- 1010
- MESSAGE
**error** can't write to temporary SL
- 1011
- MESSAGE
**error** can't delete system file
- 1012
- MESSAGE
**error** can't find system file --!
- CAUSE
Nonexistent file, misspelled, and so on.
- 1013
- MESSAGE
**error** can't add record to system file configuration
- CAUSE
SYSGEN cannot add record to SYSFILE for whatever reason. The program dies.
- 1014
- MESSAGE
**error** can't add segment "!" to temporary SL
- 1015
- MESSAGE
**error** command rejected by segmenter
- 1016
- MESSAGE
**error** command conditionally accepted by segmenter
- 1017
- MESSAGE
**error** illegal calling sequence in segmenter
- 1018
- MESSAGE
**error** unable to create segmenter process
- 1019
- MESSAGE
**error** unable to activate segmenter process
- 1020
- MESSAGE
**error** unable to send mail to segmenter process
- 1021
- MESSAGE
**error** unable to receive mail from segmenter process
- 1022
- MESSAGE
**error** segmenter process aborted
- 1023
- MESSAGE
**error** can't delete segment "!" from temporary SL
- 1024
- MESSAGE
**error** can't find system catalog
- CAUSE
Nonexistent system catalog, misspelled, and so on.
- 1025
- MESSAGE
**error** can't read from Sysfile configuration file
- CAUSE
SYSGEN cannot read from SYSFILEP for whatever reason. The program dies.
- ACTION
Refer to the file system error for action to take.
- 1026
- MESSAGE
**error** file ! does not exists
- CAUSE
Nonexistent file.
- ACTION
Check file spelling. Use name of file that exists.
- 1027
- MESSAGE
**error** system program already exists
- CAUSE
Trying to add program file that has already been added, (possibly as a boot file, or other type).
- ACTION
Do a SHOW SYSFILE to determine what it is.
- 1028
- MESSAGE
**error** NM library already exists
- 1029
- MESSAGE
**error** CM SL is not switched
- 1030
- MESSAGE
CM SL has pending changes, want to ignore them (yes/no)?
- 1031
- MESSAGE
**CM SL is not switched**
- 1032
- MESSAGE
**error** temporary CM SL prep fails
- 1033
- MESSAGE
**error** can't find boot images
- 1034
- MESSAGE
**error** file already exists in SYSFILE configuration
- 1035
- MESSAGE
**error** file not found, or of different type: !
- CAUSE
Deleted system program, or doesn't exist.
- ACTION
Use correct delete, or check name.
- 1036
- MESSAGE
**error** image already exists in SYSFILE configuration
- CAUSE
Each image must be unique across all types.
- 1037
- MESSAGE
**error** image doesn't exist in SYSFILE configuration
- CAUSE
Can't delete if not there.
- 1042
- MESSAGE
**error** The version parm is only valid with disc boot files
- 1043
- MESSAGE
**error** start version ! is already in use
- 1044
- MESSAGE
**error** all start versions are in use
- 1045
- MESSAGE
**error** nmlib version ! is already in use
- 1050
- MESSAGE
**error** parameter name is too long
- 1051
- MESSAGE
**error** Can't delete !. Delete the boot file instead.
- 1052
- MESSAGE
**error** Can't find start's library (shouldn't happen!)
- 1053
- MESSAGE
**error** The image you replace must be an IPL image
- 1054
- MESSAGE
**error** There's already a ! file
- CAUSE
Can only have one.
- 1055
- MESSAGE
**error** Only ! tape boot files are allowed.
- CAUSE
Only ! fits in directory ISL uses.
- 1056
- MESSAGE
**error** Only ! disc boot files are allowed.
- CAUSE
Only ! fits in directory ISL uses.
- 1058
- MESSAGE
**error** Only ! system files are allowed.
- 1060
- MESSAGE
**error** Only the factory can ABOOT IPL files.
- 1061
- MESSAGE
**error** Couldn't find any files of mode !
Outerblock Messages
Outerblock Messages
- 0080
- MESSAGE
** configuration files not saved **
- CAUSE
This message occurs when you abort a KEEP by not purging previous files, when an error occurs that does not allow SYSGEN to save the new configuration information, or when a TAPE generation fails.
- ACTION
None. Information only.
- 0081
- MESSAGE
** configuration files successfully saved **
- CAUSE
This message occurs when a KEEP operation is successful.
- ACTION
None. Information only.
- 0082
- MESSAGE
** successful execution **
- CAUSE
This message occurs when the TAPE command execution is successful.
- ACTION
None. Information only.
- 0083
- MESSAGE
** group "!" is created **
- CAUSE
This message occurs when SYSGEN created a new configuration group (referenced by name) in the SYS account.
- ACTION
None. Information only.
- 0084
- MESSAGE
** group "!" is replaced **
- 0085
- MESSAGE
** boottape ! is generated **
- 0088
- MESSAGE
**warning** new configuration group is not yet defined
- 0092
- MESSAGE
** no configurators are modified **
- CAUSE
This information message appears when a global SHOW command is entered and no changes have been made through any of the configurators.
- ACTION
None.
- 0100
- MESSAGE
keeping to group !
- CAUSE
This message occurs when a newgroup is specified and you enter a KEEP without a group name.
- ACTION
None. Information only.
- 0105
- MESSAGE
**note** factory user mode is "ON"
- 0500
- MESSAGE
**warning** group "!" is already the current base
- CAUSE
This message occurs when you attempt to replace the current basegroup through the BASEGROUP command using the same name as the another group name.
- ACTION
Select another group name.
- 0501
- MESSAGE
**warning** You haven't kept your changes yet! These changes
- 0502
- MESSAGE
will be lost. Do you still want to continue (yes/no)?
- CAUSE
This message occurs in all the global and configurator modules when you either try to exit without holding changes or exit SYSGEN without keeping changes.
- ACTION
Respond yes to exit or no to enter the HOLD or KEEP command.
- 0504
- MESSAGE
**warning** control Y not available
- 0510
- MESSAGE
**warning** There are no configuration files in group !
- 0511
- MESSAGE
creating a default set!
- 1000
- MESSAGE
**warning** Current account is not 'SYS'.
- 1003
- MESSAGE
**error** new group name ! is not valid. ! will be used.
- 1005
- MESSAGE
**error** Unnumbered line found in numbered input.
- 1016
- MESSAGE
**error** couldn't save configuration files! !
- CAUSE
This message occurs when an error prevents KEEP execution from saving the temporary configuration data file information to a permanent file set.
- ACTION
Refer to preceding SYSGEN errors and possibly file system errors for action to take.
- 1022
- MESSAGE
**error** unexpected end of file on default file
- 1023
- MESSAGE
**error** SYSGEN terminates in initialization
- CAUSE
This message occurs when the SYSGEN utility aborts abnormally upon encountering an error in the CI specification or while attempting to access a configurator or execute a configurator command. You are returned to the command interpreter.
- ACTION
Refer to preceding SYSGEN errors and possibly file system errors for the action to take.
- 1029
- MESSAGE
**error** base group not changed!
- CAUSE
This message occurs when SYSGEN, for whatever reason, cannot replace the basegroup with the group you enter in the BASEGROUP command.
- ACTION
Refer to preceding SYSGEN errors and possibly file system errors for the action to take.
- 1030
- MESSAGE
**error** group "!" does not exist
- CAUSE
This message occurs when you reference a basegroup that does not exit, such as when trying to replace the existing basegroup with a group that does not exist in the SYS account.
- ACTION
You have probably misspelled the group name. Reenter the name.
- 1031
- MESSAGE
**error** Couldn't get start group name
- CAUSE
Couldn't get name from OS. Internal error shouldn't happen.
- ACTION
Contact the software personnel responsible for maintaining system files.
- 1033
- MESSAGE
**error** Start group name ! too long for SYSGEN
- CAUSE
The start group name from OS is too long for SYSGEN. Internal error shouldn't happen.
- ACTION
Contact the software personnel responsible for maintaining system files.
- 1034
- MESSAGE
**error** catalog name ! is too long for SYSGEN
- CAUSE
Same as message.
- ACTION
Contact the software personnel responsible for maintaining system files.
- 1035
- MESSAGE
**error** can't open catalog !
- CAUSE
SYSGEN cannot open either the message catalog or CATALOG.PUB.SYS.
- ACTION
Contact the software personnel responsible for maintaining system files.
- 1036
- MESSAGE
**error** output name ! too long
- CAUSE
This message occurs when you enter a name that has too many characters in the OUTPUT parameter of the CI specification. Program dies.
- ACTION
Enter a name of eight or fewer characters.
- 1037
- MESSAGE
**error** input name ! too long
- CAUSE
This message occurs when you enter a name that has too many characters in the INPUT parameter of the CI specification. Program dies.
- ACTION
Enter a name of eight or fewer characters.
- 1038
- MESSAGE
**error** base group name ! too long
- CAUSE
This message occurs when you enter a name that has too many characters in the BASEGROUP parameter of the CI specification.
- ACTION
Enter a name of eight or fewer characters.
- 1039
- MESSAGE
**error** new group name ! too long
- CAUSE
This message occurs when you enter a name that has too many characters in the NEWGROUP parameter of the CI specification.
- ACTION
Enter a name of eight or fewer characters.
- 1040
- MESSAGE
**error** extra characters (!) in info string
- CAUSE
This message occurs when you enter extra characters in the INFO= parameter specification.
- ACTION
Reenter the information. If the problem persists, contact your CE.
- 1041
- MESSAGE
**error** Only ! files will fit in the LIF directory
- CAUSE
This message occurs when you try to build a tape with too many boot images. Only 63 total files are accepted by the LIF directory.
- ACTION
Delete boot images necessary to generate the tape.
- 1045
- MESSAGE
**error** No tape made due to previous errors
- 1046
- MESSAGE
**error** No keep done due to previous errors
Service (SERVE) Messages
Service (SERVE) Messages
- 0001
- MESSAGE
**error** invalid command
- CAUSE
The command you have entered is not valid for the configurator or GLOBAL module, or you have entered parameter values without the command or command abbreviation.
- ACTION
Enter HELP without a parameter to list all configurator or global module commands. check how you have specified your command.
- 0004
- MESSAGE
**error** can't create temporary configuration file --!
- CAUSE
For whatever reason, SYSGEN cannot create the referenced temporary configuration file. Program dies.
- ACTION
If the file is IOLDEVP, it could be the available disk space does not provide enough room for another configuration. check available disk space with the DISCFREE command. Refer to the file system error for other action to take.
- 0005
- MESSAGE
**error** can't open configuration file --!
- CAUSE
For whatever reason, SYSGEN cannot create the referenced configuration file. Program dies.
- ACTION
If the file is IOLDEVP, it could be that the available disk space does not provide enough room for another configuration. check available disk space with the DISCFREE command. Refer to the file system error for other action to take.
- 0016
- MESSAGE
**error** invalid parameter
- CAUSE
The keyword parameter used in the command is not valid.
- ACTION
Use the HELP command to display the command syntax.
- 0019
- MESSAGE
**error** fail to initalize primary configuration file.
- 0025
- MESSAGE
**error** can't update temporary configuration file
- CAUSE
SYSGEN uses temporary files to store current configuration changes until they are kept to the permanent configuration data file. Here, SYSGEN cannot update a temporary file. The program dies.
- ACTION
Refer to the file system error for action to take.
- 0027
- MESSAGE
configuration changes are not kept yet!
- CAUSE
You try to exit a configurator without holding or clearing the changes with the HOLD or CLEAR command, or you try to exit the SYSGEN GLOBAL module without keeping the changes. You are given an additional chance to hold or keep the changes.
- ACTION
If in one of the four configurators, answer either no, hold the changes, and then exit, or answer yes and abandon the changes.
- 0028
- MESSAGE
still want to exit (yes/no)?
- CAUSE
Continuation of previous message.
- ACTION
Same as previous message.
- 0030
- MESSAGE
**error** illegal group name
- CAUSE
The group name entered is not valid.
- ACTION
Check the name you have entered and how it is specified. If necessary, use the HELP command to list the command syntax and check the parameter requirement.
- 0035
- MESSAGE
**error** illegal filename
- CAUSE
The file name or fully qualified file name is not valid for the operation.
- ACTION
Enter a valid file for the operation.
- 0037
- MESSAGE
**error** can't create configuration file !
- CAUSE
SYSGEN, for whatever reason, cannot create the specified configuration data file in the specified configuration group.
- ACTION
check permissions, see if the file is being access.
- 0041
- MESSAGE
**error** can't purge configuration file !
- CAUSE
SYSGEN, for whatever reason, cannot purge the specified configuration data file in the specified configuration group.
- ACTION
- 0042
- MESSAGE
**error** can't save configuration file !
- CAUSE
SYSGEN, for whatever reason, cannot save the specified configuration data file in the specified configuration group.
- ACTION
- 0050
- MESSAGE
**error** can't find filename
- CAUSE
SYSGEN cannot find the file name entered for the FILE= parameter. check any additional file system error messages.
- ACTION
As the file name entry is probably misspelled or references a file that does not exist in the group and/or account, reenter a valid file name.
- 0052
- MESSAGE
**error** duplicate filename (sysfile) --!
- 0053
- MESSAGE
**error** duplicate filename (io) --!
- 0061
- MESSAGE
**error** duplicate system filename (sysfile) --!
- 0062
- MESSAGE
**error** duplicate system filename (io) --!
- 0063
- MESSAGE
(CIERR !)
- 0070
- MESSAGE
HOLD is invalid here. Use KEEP to permanently save your changes.
- CAUSE
You have entered a HOLD command as an outer block (main menu) command.
- ACTION
If you want to make additional changes, use a configurator command. If you want to save the changes as is, use the KEEP command.
- 1000
- MESSAGE
**error** missing !
- CAUSE
Usually, missing option. Something required for the command entry is missing.
- ACTION
Refer to the reference for the action to take.
- 1001
- MESSAGE
**error** The first letter of a ! cannot be a number
- CAUSE
Usually, the first letter of an LDEV cannot be a number. Any parameter that requires a character string can generate this message. This is usually caused by specifying a parameter value in the wrong position, or is a trying mistake.
- ACTION
Refer to the reference for the action to take. If necessary, use the HELP command to display the syntax and positional parameters.
- 1002
- MESSAGE
**error** ! too long
- CAUSE
Normally, the entered character string value for the parameter exceeds the maximum number of characters.
- ACTION
Use SHOW to display minimum and maximum values (or characters) for the parameter, or use the HELP command to display the parameter requirements.
- 1003
- MESSAGE
**error** Can't supply a lockword with wild characters
- CAUSE
This occurs in the SYSFILE configurator. A lockword cannot be composed of wildcard or "wild" characters, for example, @.
- ACTION
Reenter the command and parameters, supplying a valid lockword without wildcards or "wild" characters.
- 1004
- MESSAGE
**error** Invalid characters in ! name
- CAUSE
Either an invalid character has been entered in a file or group name, or SYSGEN interprets one as being there. For example, MPEXL;; from an INFO= parameter specification.
- ACTION
Reenter the reference file or group name.
- 1005
- MESSAGE
**error** file specification too long. file spec=1
- CAUSE
You have entered a file name or fully qualified file name that is too long.
- ACTION
Enter the required file name specification. Use the HELP command to display the requirement of the parameter.
- 1010
- MESSAGE
**error** Can't create group "!"
- CAUSE
For whatever reason, SYSGEN cannot create the referenced configuration group.
- ACTION
If this occurs while keeping to a NEWGROUP name, try the name a second time and, if the error is returned, save the files to a group of a different name.
- 1015
- MESSAGE
**error** Hold command not valid here
- 1017
- MESSAGE
**error** Error occurred in killing segmenter process
- 1020
- MESSAGE
**error** There are no configuration files in group !
- CAUSE
The group entered as the basegroup for the command line specification (INFO=) or the name entered through the GLOBAL module BASEGROUP command does not contain a permanent file set of configuration data files or the user does not have READ access to the files.
- 1021
- MESSAGE
**error** Missing configuration files ! in group !
- CAUSE
For whatever reason, one or more of the configuration data file sets no longer exists in the group specified as the basegroup.
- ACTION
If the group name is used in the INFO= parameter of the command line specification, SYSGEN terminates. If you specify the group name as the basegroup within the GLOBAL module, SYSGEN issues the message and returns the current basegroup.
- 1022
- MESSAGE
**error** Error attempting to validate group existence
- CAUSE
SYSGEN cannot determine that the group exists.
- 1024
- MESSAGE
**error** Can't access LID table
- CAUSE
SYSGEN cannot access the user logging ID table.
- 1025
- MESSAGE
**error** Can't access LID table--error !
- CAUSE
SYSGEN cannot access the user logging ID table.
- 1026
- MESSAGE
**error** Can't read input
- CAUSE
SYSGEN read the command input file or job stream.
- ACTION
Exit and correct the command input file, or reenter the job stream.
- 1027
- MESSAGE
**error** End of file on input
- CAUSE
Usually the problem occurs from how SYSGEN was executed from the command line, using a designated command input file.
- ACTION
Use the command interpreter REDO command to verify how you have executed SYSGEN from the command line. Use the EDITOR subsystem to display your commands in the input file. check for errors. check that the file is unnumbered. If necessary BUILD the file as a permanent ASCII file.
- 1028
- MESSAGE
**error** Error talking to console--can't continue
- 1031
- MESSAGE
**error** invalid command
- 1040
- MESSAGE
**error** FPOINT failed on a temporary file
- 1041
- MESSAGE
**error** couldn't close temporary file !
- 1042
- MESSAGE
**error** can't read temporary file !
- 1043
- MESSAGE
**error** Can't write temporary file !
- 1044
- MESSAGE
**error** Can't open a temporary file !
- 1045
- MESSAGE
**error** Can't purge a temporary file !
- 1050
- MESSAGE
**error** No closing brace for comment in IODFAULT
- 1051
- MESSAGE
**error** record too long in IODFAULT
- 1060
- MESSAGE
**error** checksum error in file !
- 1061
- MESSAGE
**error** record read from ! file is too short!
- 1070
- MESSAGE
**error** bad filename--expected period as delimiter
Other Messages
Other Messages
- 0500
- MESSAGE
**warning** missing optional parameter
- 0520
- MESSAGE
**warning** Information display only mode ! ! !
- CAUSE
The account has insufficient capability to make configuration changes. You can view configuration data only.
- ACTION
Add SM capability or access an account, if allowed, with SM capability.
- 0530
- MESSAGE
**warning** offline list device not currently open
- CAUSE
This error is caused when the OCLOSE command is entered and nothing has yet been sent.
- ACTION
You must have used DEST=OFFLINE at least once since beginning SYSGEN or the last OCLOSE.
- 0535
- MESSAGE
**warning** Can't find CM procedure doccnmdata!
- 1000
- MESSAGE
**error** Can't open file !
- CAUSE
SYSGEN cannot open the designated file. Usually, the file does not exist.
- ACTION
check that you entered the proper file name.
- 1001
- MESSAGE
**error** FFILEINFO error on file !
- CAUSE
The FFILEINFO intrinsic returned an error for file !
- ACTION
Refer to the file system error message, also returned.
- 1002
- MESSAGE
**error** can't open output device
- 1003
- MESSAGE
**error** The string ! is too long! (int. catalog error)
- 1004
- MESSAGE
**error** You must have SM capability to make a tape!
- CAUSE
The TAPE command has been entered from an account that does not have SM capability. Generally, you are in the wrong account and you try to generate a tape.
- ACTION
Add SM capability or, if allowed, access an account with SM capability.
- 1005
- MESSAGE
subsys=! error=!
- CAUSE
Continuation of previous message.
- ACTION
Continuation of previous message.
- 1006
- MESSAGE
**error** Can't write to offline list device!
- CAUSE
The offline device is probably connected and active, but the output spooling function is not.
- ACTION
Use the STARTSPOOL command and appropriate device number from the master console to activate the output spooling function.
- 1007
- MESSAGE
**error** Can't closs offline list device!
- CAUSE
For whatever reason, SYSGEN cannot close the list device.
- 1008
- MESSAGE
**error** You must have SM capability to do a KEEP!
- 1009
- MESSAGE
**error** user has insufficient capability. SYSGEN TERMINATES.
- CAUSE
The account has insufficient capability to allow you to change or view SYSGEN data. You are probably trying to access SYSGEN from the wrong account.
- ACTION
Use the SHOWME command to see the current account. Log on to an account with sufficient capability to request the operator to add the capability to your account.
- 1010
- MESSAGE
**error** Catalog is missing a path type message.
- 1011
- MESSAGE
**error** You must have SM capability to make changes
- 1012
- MESSAGE
**error** Can't close a permanent configuration file
- CAUSE
For whatever reason, SYSGEN cannot close the configuration data file from that data was written from one or more temporary files. Program dies.
- ACTION
Refer to the file system error for action.
- 1013
- MESSAGE
**error** Can't read a permanent configuration file
- 1014
- MESSAGE
**error** Can't write a permanent configuration file
- 1015
- MESSAGE
**error** Can't FPOINT a permanent configuration file
- 1016
- MESSAGE
**error** Redo only valid interactively
- 1018
- MESSAGE
**error** language localized devtype name too long.
- 1020
- MESSAGE
**error** switch to alterrin failed. Switch error=!
- 1021
- MESSAGE
**error** switch to compactrin failed. Switch error=!
- 1022
- MESSAGE
**error** switch to deleterin failed. Switch error=!
- 1023
- MESSAGE
**error** switch to initrin failed. Switch error=!
- 1024
- MESSAGE
**error** switch to listrin failed. Switch error=!
- 1025
- MESSAGE
**error** switch to dtermctyp failed. Switch error=!
- 1026
- MESSAGE
**error** switch to segmenter failed. Switch error=!
- 1027
- MESSAGE
**error** switch to dccmdata failed. Switch error=!
- 1030
- MESSAGE
**error** error* Can't find CM procedure dtermctyp!
- 1035
- MESSAGE
**error** set ! (message !) not found in message catalog
- CAUSE
A message set is missing from SYSGEN's message catalog.
- 1036
- MESSAGE
**error** message number ! of set ! not found in message catalog
- CAUSE
A message is missing from SYSGEN's message catalog.
Scanner Messages
Scanner Messages
- 0001
- MESSAGE
**error** parameter value out of range
- CAUSE
The number of values, or value range, is more than the parameter can accept. Program can die under certain character string conditions.
- ACTION
Use the SHOW command to check range values. Cross-check IODFAULT.PUB.SYS listings for maximum modes and classes. Enter a value within the permissible range.
- 0003
- MESSAGE
**error** ldev number must be integer
- CAUSE
An alphabetic character has been entered in an LDEV parameter or keyword. Usually happens when a parameter entry is made out of position.
- ACTION
Enter the proper LDEV number, or check the command syntax through the HELP command, and enter the parameter value in the appropriate place.
- 0004
- MESSAGE
**error** parameter name is too long
- CAUSE
The parameter string is too long. Most character strings are limited to eight alphanumeric characters. Exceptions include logical and physical manager names, volume names, and some identification names.
- ACTION
check parameter name limitations under the appropriate command and configurator in this manual and/or against system default values. Enter a parameter name that does not exceed the maximum length.
- 0005
- MESSAGE
**error** too many classnames are specified
- CAUSE
The maximum number of classnames is eight.
- ACTION
Enter no more than eight class names.
- 0006
- MESSAGE
**error** volume name is too long
- CAUSE
The name entered to add a volume or to modify the existing name through the AVOL or MVOL command is too long. The message can also appear as volume too long.
- ACTION
Enter a volume name of up to 32 characters.
- 0007
- MESSAGE
**error** beginning ldev is larger than ending ldev
- CAUSE
The numbers entered in the range command have been reversed or entered incorrectly. The beginning device number is larger than the ending number. For example, LDEV 100/20 instead of LDEV 20/100 or LDEV 10/20 generates this message.
- ACTION
Begin the range entry with the smallest LDEV number or the beginning and ending numbers.
- 0008
- MESSAGE
**error** missing ending ldev
- CAUSE
The ending LDEV number has been omitted from the range specification, for example, LD 10/ or LD (1/,20,22).
- ACTION
Reenter the range specification.
- 0009
- MESSAGE
**error** product ID is too long
- CAUSE
The product identification string for the path or device ID= parameter is too long. Usually an entry mistake.
- ACTION
Reenter the product identification or check the IODFAULT.PUB.SYS listing for the existing product identification string.
- 0010
- MESSAGE
**error** io path is too long
- CAUSE
The iopath entry exceeds the requirement or is of a level that cannot exist.
- ACTION
Use the HELP command to check the command syntax and entry the proper path designation.
- 0011
- MESSAGE
**error** io path must start with bus converter number
- 0012
- MESSAGE
(channel adaptor # : min=1, max=3)
- 0013
- MESSAGE
(device adaptor # : min=1, max=6)
- 0014
- MESSAGE
(device # : min=1, max=8)
- 0015
- MESSAGE
**error** logical device adaptor number does not match device adaptor number
- 0016
- MESSAGE
**error** incomplete I/O path specification
- CAUSE
A lower level path for the PATH= parameter than is required. For example, AD 117 8.2 HP7978 generates this message as PATH= looks for ca.da.d#. Also, improper punctuation such as AD 117 8,2,4 HP7978 generates this message.
- ACTION
Enter the required iopath level.
- 0017
- MESSAGE
**error** manager name is too long
- CAUSE
When adding or modifying an iopath or device, particularly when USER path or device is designated, the MANAGER=, PMGR= or LMGR= parameter name exceeds the permissible parameter length.
- ACTION
For a supported device, use the default name from IODFAULT.PUB.SYS. For a user name, enter a name that does not exceed 32 characters.
- 0018
- MESSAGE
**error** invalid file specification
- CAUSE
An invalid file name has been entered in a NAME= parameter that expects a fully qualified file name.
- ACTION
Enter an existing, fully qualified file name.
- 0019
- MESSAGE
**error** filename is too long
- CAUSE
The file name exceeds eight characters. Other messages should appear noting additional problems such as numbers or invalid characters in the file name.
- ACTION
Enter an existing file name of up to eight characters. File names must begin with an alphabetic character and should not contain special characters or punctuation within the name.
- 0020
- MESSAGE
**error** groupname is too long
- CAUSE
The group name exceeds eight characters.
- ACTION
Enter an account group name up to eight characters in length.
- 0021
- MESSAGE
**error** account name is too long
- CAUSE
The account name exceeds eight characters.
- ACTION
Enter an account name up to eight characters in length.
- 0023
- MESSAGE
**error** file specificaton must start with filename
- CAUSE
An entry other than a file name has been entered as the value for the FILE= parameter. This is usually caused by entering a value out of position.
- ACTION
Use the HELP command to check the command syntax and enter the parameter values in the proper position or by keyword. Enter a fully qualified file name for the FILE= parameter.
- 0024
- MESSAGE
**error** device type is too long
- CAUSE
The TAPE= parameter entry exceeds eight characters.
- ACTION
Enter a device type name that does not exceed eight characters.
- 0025
- MESSAGE
**error** missing '.' before device number
- 0026
- MESSAGE
**error** segment name is too long
- CAUSE
The SEG= parameter name of the ACMSL or RMCSL command exceeds eight characters.
- ACTION
Enter a segment name that does not exceed eight characters.
- 0027
- MESSAGE
**error** sl name is too long
- CAUSE
The SL= parameter name file name entered for the CMSL command exceeds eight characters.
- ACTION
Enter a file name that does not exceed eight characters, or enter a fully qualified file name.
- 0028
- MESSAGE
**error** program name is too long
- CAUSE
The PROG= parameter file name entered for the ASPROG or RSPROG command exceeds eight characters.
- ACTION
Enter a file name that does not exceed eight characters, or enter a fully qualified file name.
- 0030
- MESSAGE
**error** parameter name is too long
- CAUSE
Unspecified parameter name has too many characters, usually occurring with user-specified devices, or too many subparameters given for the parameter value.
- 0031
- MESSAGE
**error** parameter value too long
- CAUSE
The numeric value you enter for the parameter exceeds the maximum permissible value.
- ACTION
Use the SHOW command to display minimum and maximum parameter values. Enter a value within the range.
- 0032
- MESSAGE
**error** parameter value too small
- CAUSE
The numeric value you enter for the parameter is less than the minimum perimissible value.
- ACTION
Use the SHOW command to display minimum and maximum parameter values. Enter a value within the range.
- 0033
- MESSAGE
**error** parameter name must start with an alphabetic
- CAUSE
The parameter requires a string value that begins with an alphabetic character. The value starts with a number.
- ACTION
Enter a valid name beginning with an alphabetic character.
- 0034
- MESSAGE
**error** parameter name contains illegal character
- 0035
- MESSAGE
(bus converter # : min=1, max=2)
Boot Tape Messages
Boot Tape Messages
- 0001
- MESSAGE
**error** can't open boottype
- CAUSE
The TAPE command has been issued but SYSGEN cannot generate a boot tape.
- ACTION
Check to see the tape is unlabeled, not specially formatted, and of proper density. check prior file equations for TAPE commands. Check to be sure the tape is not damaged.
- 0013
- MESSAGE
**error** fail to write boottape label
- CAUSE
The tape does not meet SYSGEN requirements; the TAPE command cannot properly format the tape.
- ACTION
Check to see the tape is unlabeled, not specially formatted, and of proper density. check prior file equations for TAPE commands. Check to be sure the tape is not damaged.
- 0015
- MESSAGE
**error** error write file ! onto boottape
- CAUSE
A file designated in SYSFILEP does not exist, is corrupted, or there may be a tape problem.
- ACTION
check system program files through the SYSFILE configurator SHOW command for spelling and duplication. Cross-check suspect files through the command interpreter LISTF command.
- 0016
- MESSAGE
**error** can't read file !
- CAUSE
Usually, a file designated in SYSFILEP does not exist. Program dies.
- ACTION
Verify that the file does not exist. Remove the entry from SYSFILEP through the DSPROG command.
- 0018
- MESSAGE
**error** boot tape was opened incorrectly
- CAUSE
SYSGEN requires a tape of a specific record size and format on reel-to-reel media. The file equation for SYSGTAPE changes something it should not.
- ACTION
Change the file equation for the proper record size and format.
- 0019
- MESSAGE
**error** can't get boot tape information
- CAUSE
SYSGEN cannot determine if the tape was opened correctly.
- ACTION
Change the file equation for the proper record size and format.
- 0020
- MESSAGE
**error** SYSGEN won't write labelled tapes
- CAUSE
A file equation that created a labeled tape has been entered. SYSGEN does not generate labeled tapes.
- ACTION
Change the file equation for the proper format.
- 0022
- MESSAGE
**boot tape is successfully built**
- CAUSE
The boot tape is successfully generated.
- ACTION
None.
- 0023
- MESSAGE
**error** can't create store.pub.sys process
- 0024
- MESSAGE
**error** can't activate Store.pub.sys process
- 0025
- MESSAGE
**error** can't get reply from Store.pub.sys process
- 0026
- MESSAGE
**error** error occurs while storing userfiles
- 0027
- MESSAGE
EOT is encountered. Please mount next reel to continue tape operation. When tape is ready, enter "yes" to continue.
- 0029
- MESSAGE
boottape generation. Otherwise, enter "no". (yes/no)?
- 0040
- MESSAGE
**Boottape generation is aborted**
- 0041
- MESSAGE
**error** fail to mark end of tape
- 0051
- MESSAGE
pme = !
- 0052
- MESSAGE
label
- 0100
- MESSAGE
Please mount another tape for SYSGEN. This will be reel # !
- 0101
- MESSAGE
Is SYSGEN's tape (reel !) ready (y/n)?
- 0105
- MESSAGE
Do you really want to abort the TAPE generation (y/n)?
- 0200
- MESSAGE
! non-user files will be written to tape
- 0201
- MESSAGE
dumping ! to tape
- 0500
- MESSAGE
**warning** No network configuration dumped! !
- CAUSE
A valid network configuration does not exist at the time SYSGEN generates the boot tape.
- ACTION
Usually none. If you require a remote configuration file, abort the tape and add a remote configuration file to the local configuration through the SYSFILE configurator RDCC command.
- 0501
- MESSAGE
**warning** ! will be ! on the tape.
- CAUSE
The file name is changed to a new file name on the boot tape; for example, the remote configuration file becomes NMCONFIG.PUB.SYS.
- ACTION
None.
- 0502
- MESSAGE
**warning** illegal file type. File ! dumped as system file
- CAUSE
A file type created in the SYSFILE configurator is corrupted. The file is dumped as a system program type.
- ACTION
Either allow the system to use the default configuration file(s) or reconfigure the file through the SYSFILE configurator and generate a new tape.
- 0503
- MESSAGE
**warning** File ! is empty.
- 1000
- MESSAGE
**error** couldn't find file !
- 1001
- MESSAGE
**error** Error in counting number of diag files
- 1002
- MESSAGE
**error** ! is not a bootable image
- CAUSE
Through the SYSFILE configurator, you have declared a file to be a bootable image. It is not.
- ACTION
After tape generation, check your file for errors. Correct it and add it to the system through the SYSFILE SBOOT command.
- 1003
- MESSAGE
**error** Can't read file label of file !
- CAUSE
This is caused by an I/O error.
- 1004
- MESSAGE
**error** No disc ipl boot file--Can't make tape.
- CAUSE
Through deletion or modification, no boot image is designated as the ISC IPL file. The system requires that both a disk and a tape IPL file be present.
- ACTION
As the original file should still exist in the proper account, add the image and file name to SYSFILEP through the SYSFILE configurator command ABOOT. Retry the TAPE command.
- 1005
- MESSAGE
**error** No tape ipl boot file--Can't make tape.
- CAUSE
Through deletion or modification, no boot image is designated as the tape IPL file. The system requires that both a disk and a tape IPL file be present.
- ACTION
As the original file should still exist in the proper account, add the image and file name to SYSFILEP through the SYSFILE configurator command ABOOT. Retry the TAPE command.
- 1006
- MESSAGE
**error** records of file ! too long for SYSGEN
- CAUSE
The tape block size is greater than the size required by SYSGEN (currently 16 K).
- ACTION
Decrease the block size in the file.
- 1007
- MESSAGE
**error** The tape boot files must fit on 1 tape.
- CAUSE
All files of type (tapeboot, tapeauto, tapeipl) as well as type both (bothboot, botauto, bothipl) must fit on one reel.
- ACTION
Use a tape of sufficient size, and delete unnecessary or outdated boot files through the SYSFILE configurator DBOOT command.
- 1008
- MESSAGE
Ran out of tape while dumping file: !
- CAUSE
Same as above.
- 1009
- MESSAGE
**error** Couldn't write eof mark on tape
- CAUSE
A hardware failure occurs on the drive.
- ACTION
Check that the tape is good and that it has been mounted properly. Replace the tape if necessary and try again. If failure occurs, the problem is more than likely with the tape drive. Try another drive. Contact your CE.
- 1010
- MESSAGE
**error** Can't rewind tape
- CAUSE
A hardware failure occurs on the drive.
- ACTION
Check that you tape is still mounted properly. check that the drive is still functioning. If the problem is not immediately discernible, use another drive for generating your tapes.
- 1011
- MESSAGE
**error** File ! is empty.
- 1015
- MESSAGE
**error** Can't close file !.
- 1016
- MESSAGE
**error** bad diagnostic file name (!) in !
- 1020
- MESSAGE
**error** Can't create temporary LID file
- 1021
- MESSAGE
**error** Can't close temporary LID file
- 1022
- MESSAGE
**error** Can't create temporary DST file
- 1023
- MESSAGE
**error** Can't close temporary DST file
- 1024
- MESSAGE
**error** Can't write to temporary file for !
- 1030
- MESSAGE
**error** Tape command failed SYSGEN tape is NO GOOD
- CAUSE
There is a problem with the tape used, a base system file is corrupted, or the configuration file SYSFILEP contains a file name that is no longer valid.
- ACTION
First, check any associated message that appears, particularly messages that indicate a file cannot be found or is corrupted. SYSDILEP contains a listing of files SYSGEN expects to put out to a boot tape. Check to be sure the base file is still a valid file for your current software release. If it is not, delete the file from SYSFILEP using the DSPROG command in the SYSFILE configurator. If a file is corrupted, restore it from your system backup tape. If there are no accompanying messages, mount a different tape. Check the tape drive.
LANGINST Messages
LANGINST Messages
- MESSAGE
A nonnumeric graphic character is expected.
- CAUSE
An alphabetic or special character (but not numeric) is expected.
- ACTION
Enter a valid character.
- MESSAGE
Attempting to add too many character sets.
- CAUSE
Adding this language would exceed the maximum configurable character sets.
- ACTION
Do not configure languages from so many character sets.
- MESSAGE
Building and empty langdef.
- CAUSE
There was no existing LANGDEF file, so a new, empty file is being built.
- ACTION
None. If you have already configured languages, find LANGDEF.PUB.SYS on a backup and restore it. Otherwise, reconfigure the languages with this program.
- MESSAGE
Deletion terminated; attempting to delete NATIVE-3000.
- CAUSE
The language NATIVE-3000 may not be deleted from the list of configured languages.
- ACTION
None.
- MESSAGE
Erroneous starting year number. Expected a number from 0 to 99.
- CAUSE
The number entered is not valid.
- ACTION
Reenter the year's number. It must be a number from 0 to 99.
- MESSAGE
Input too long. Please reenter:
- CAUSE
The program does not expect so much input.
- ACTION
Reenter the data correctly.
- MESSAGE
Internal error. Please report.
- CAUSE
Internal error.
- ACTION
Contact your Hewlett-Packard Support Representative.
- MESSAGE
Invalid date format. Expected MM/DD/YY.
- CAUSE
The format date is not valid.
- ACTION
Enter the date again in the form MM/DD/YY. Example 07/20/91.
- MESSAGE
LANGNAME is already configured.
- CAUSE
The language selected has already been configured.
- ACTION
None.
- MESSAGE
LANGNAME is an illegal language name (or number).
- CAUSE
The language name or number entered is not valid.
- ACTION
Enter the language again, correctly.
- MESSAGE
LANGNAME is an invalid system default language.
- CAUSE
The language selected is not configured on your system.
- ACTION
Add the language to the list of currently configured languages with this program, or choose a configured language.
- MESSAGE
LANGNAME is not a configured language.
- CAUSE
The language selected is not configured on your system.
- ACTION
Add the language to the list of currently configured languages with this program.
- MESSAGE
LANGNAME is not configured.
- CAUSE
The language entered is not configured on your system.
- ACTION
Add the language to the list of currently configured languages with this program.
- MESSAGE
LANGNAME is not in the CHRDEF file.
- CAUSE
One of the CHRDEFXX files is not consistent with the NLSDEF file.
- ACTION
Restore all CHRDEFXX files and NLSDEF in PUB.SYS from the master backup.
- MESSAGE
NATIVE-3000 is always configured.
- CAUSE
NATIVE-3000 may not be added to the list of configured languages because it is always configured.
- ACTION
None.
- MESSAGE
NATIVE-3000 may not be modified.
- CAUSE
The language definition of NATIVE-3000 may not be modified.
- ACTION
None.
- MESSAGE
The CHRDEFXX file is missing. The addition has been cancelled.
- CAUSE
The character definition file for the selected language is missing.
- ACTION
Restore the missing file from PUB.SYS from the master backup.
- MESSAGE
The decimal separator and thousands separator should be different.
- CAUSE
The decimals and thousands separators have been defined to be the same.
- ACTION
Change the decimal and/or thousands indicator.
- MESSAGE
The expected name should contain alphabetic characters only.
- CAUSE
Only alphabetic characters are allowed in this context.
- ACTION
Reenter the value, using alphabetic characters only.
- MESSAGE
The filecode for CHRDEFXX.PUB.SYS is incorrect.
- CAUSE
The character definition file for the selected language has a bad file code. The file is probably corrupted.
- ACTION
Restore the missing CHRDEFXX file from the PUB.SYS group of the master backup.
- MESSAGE
The filecode for LANGDEF.PUB.SYS is incorrect.
- CAUSE
The current language definition file has a bad file code. The file cap is probably corrupted.
- ACTION
Restore LANGDEF.PUB.SYS from a backup copy. Or purge it, and re-create it by reconfiguring the desired languages with this program.
- MESSAGE
The filecode for NLSDEF.PUB.SYS is incorrect.
- CAUSE
The master NLS definition file has a bad file code. The file is probably corrupted.
- ACTION
Restore NLSDEF.PUB.SYS from the master backup.
- MESSAGE
The lanugage you are attempting to delete is the system default language.
- CAUSE
The system default language may not be deleted from the list of configured languages.
- ACTION
If you wish to delete this language, you must first change the system default language to another configured language.
- MESSAGE
The user should be MANAGER.SYS, running in the PUB group.
- CAUSE
The user is not MANAGER.SYS or is not logged on in the PUB group.
- ACTION
Log on as MANAGER.SYS in the PUB group, and run the program again.
- MESSAGE
There is no more room for additional date periods. Please report.
- CAUSE
There is no room for additional entries in the national date table.
- ACTION
Contact your Hewlett-Packard Support Representative.
- MESSAGE
Too many languages have been configured.
- CAUSE
Adding another language would exceed the maximum configurable languages.
- ACTION
Do not configure so many languages on one system.
- MESSAGE
Unable to rename LANGDEF to LANGDnnn. The existing LANGDEF will be purged.
- CAUSE
The old LANGDEF file could not be renamed because all files, LANGD000 through LANGD999, already existed.
- ACTION
Purge some or all of the files, LANDG000 to LANGD999, so the most recent changes to LANGDEF can be saved in the future.
- MESSAGE
Unknown option. Please reenter.
- CAUSE
The option selected is not a valid one.
- ACTION
Enter the number corresponding to one of the currently valid options.
|
Chapter 9 Class Errors |
Chapter 10 Store/Restore (Native Mode) and TurboSTORE/iX I |