"Nonclass" Errors

**note** Class !'s mode is now !

**warning** language localized string "NMMGR" too long

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.

Contact your software representative responsible for maintaining system files.

**warning** Class ! is already associated with device !

User is trying to add a class to a device more than once.

Use another class name or leave unchanged.

**warning** can't get NMMGR info for file !.

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.

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.

**warning** path doesn't exist

The path that the user referenced doesn't exist.

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.

**warning** class ! doesn't exist

The class that the user referenced doesn't exist.

Enter the LCLASS command to display a list of current class names and the LDEVs assigned to each. Enter a valid class name.

**warning** no volumes left to list

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.

Enter the LVOL command without the volume name parameter.

**warning** volume name does not exist

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.

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.

**warning** Can't open offline list device--online used

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.

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.

**warning** class ! degraded to mode !

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.

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.

**warning** class ! is of mode !--user mode ignored

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.

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.

**warning** Not enough room for dcc devices in class !

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.

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).

**warning** docc devices in class ! degraded to mode !

Attempting to share a class with NMMGR has caused the mode requested by NMMGR to be degraded to the given mode.

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.

**warning** class ! won't accept dcc's mode of ! anymore

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.

Either remove the device that caused the incompatibility, or change the class name of the DCC device in NMMGR.

**warning** dcc devices degrade class ! to mode !

Although the doc devices are able to share this class with SYSGEN, their presence degrades access to SYSGEN's devices.

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.

**warning** language localized string "USER" too long

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.

Contact your software personnel responsible for maintaining system files.

**warning** Class ! already exists

User is trying to add class !, and it already exists.

To modify an existing class, use the MCLASS command.

**warning** Class ! already exists--class mode ignored

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.

Enter the LCLASS command to verify that the class exists and to verify that LDEVs are associated with the class name.

**warning** level parameter ignored-path parameter used instead.

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.

None required.

**warning** mgrname parameter ignored--path parameter used instead.

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.

None required.

**warning** The correct delimiter at this level is a "!"

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.

None required. SYSGEN replaces the incorrect delimiter.

Path (up to this level) changed to !

Issued with previous to indicate what the correct path is.

None required. SYSGEN has replaced the incorrect delimiter.

**warning** iopath ! (from DCC) does not exist

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).

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.

**warning** path ! (from DCC) has a bad component (too large, or non-numeric)

The path specified in NMMGR for either the DCC devices or the NS devices is invalid. It might be either too large, or nonnumeric.

Change the path from within NMMGR to be valid.

**warning** path name (from DCC) too long

It is possible, though unlikely, that the path specified from within NMMGR is too long to fit into SYSGEN's data structures.

Shorten the path from within NMMGR.

**warning** OUTDEV must equal LDEV: Correct value used

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.

None required. SYSGEN has used the correct value.

**warning** OUTDEV must be zero (0): Correct value used

All devices except for terminals and the streams device(s) must have an output device of zero.

None required. SYSGEN has used the correct value.

**error** class ! already exists

The class name you have entered already exists.

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).

**error** classname does not exist

You are trying to delete or modify a class name that does not exist.

Use the LCLASS command to display existing class names and associated devices.

**error** new volume name already exists

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.

Use the LVOL command to view existing volume names. Choose an unused volume name.

**error** can't read I/O volume configuration file

SYSGEN cannot read the configuration data file IOVOLP. The program terminates.

Refer to the file system error for action to take.

**error** can't modify I/O volume configuration

SYSGEN cannot read the configuration data file IOVOLP. The program terminates.

Refer to the file system error for action to take.

**error** volume name does not exist

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.

Use the LVOL command without a parameter to display all existing volume names. Choose an existing name for the modify or delete operation.

**error** can't add volume to I/O configuration

SYSGEN cannot write the configuration data file IOVOLP. The program terminates.

Refer to the file system error for action to take.

**error** ldev ! is reserved for system console

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.

Chose another unassigned LDEV for adding or modifying a local device or volume.

**error** ldev is already assigned to configured volume

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.

Chose another unassigned LDEV for the new or modified volume.

**error** can't read Ioldev configuration file

SYSGEN cannot read the configuration data file IOLDEVP. The program terminates.

Refer to the file system error for action to take.

**error** can't read Ioclass configuration file

SYSGEN cannot read the configuration data file IOCLASSP. The program terminates.

Refer to the file system error for action to take.

**error** can't reset Ioldev file

**error** can't reset Ioclass file

**error** can't reset Iovolume file

**error** A device can only have ! volume classes.

Too many volume classes have been assigned to a volume through the CLASS= parameter.

Limit the number of volume classes to the number that appears in the message.

**error** A device can only have ! classes.

Too many classes have been assigned to an LDEV through the CLASS= parameter.

Limit the number of classes to the number that appears in the message.

**error** can't write to Ioldev configuration file

**error** unknown device type

The device type entered in the TYPE= parameter is unsupported, or incorrectly specified.

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.

**error** device mode too long

**error** illegal device mode for this device

The device mode entered in the MODE= parameter is not appropriate for this particular device.

Enter an appropriate mode. If necessary, check the IODFAULT file for permissible modes.

**error** This device is not supported.

You have entered a product identification that does not exist in IODFAULT.PUB.SYS. Usually, the error is a simple entry mistake.

Enter the proper Hewlett-Packard product IDs. If necessary, check for supported product IDs.

**error** iopath level mismatch

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.

Correct the path entry

**error** can't find record in Ioldev configuration file

SYSGEN cannot find a particular record in the configuration data file. The program terminates.

Refer to the file system error for action to take.

**error** # new devices must watch # old devices

**error** can't update record in Ioldev configuration file

**error** can't open I/O default file

**error** iopath already exists

**error** missing physical file for physical manager

**error** missing physical manager for physical file

**error** missing logical file for logical manager

**error** missing logical manager for logical file

**error** iopath does not exist

**error** manage ! is not in the configuration

**error** physical manager does not exist.

**error** logical manager does not exist

**error** can't write to Iopath configuration file

**error** can't delete I/O path.

**error** can't find record in Iopath configuration file

**error** can't update Iopath configuration file

**error** can't read from Iopath configuration file

**error** can't open I/O default file

**error** I/O default file does not exist

**warning** ldev ! already has ! classnames.

class '!' cannot be added to it.

**error** iopath must be added in an hierarchical order

I/O path specified has pending devices.

Want to delete all of them (yes/no) ?

** no iopath is deleted **

**error** this iopath has no logical device manager

**error** manager '!' currently used.

it cannot be deleted

**error** ldev is not yet configured

**error** ldev is not a disc

**error** ldev ! is configured as a system volume.

it cannot be deleted

**error** ldev ! already exists

**warning** ldev ! does not exist

it must be replaced with a disc type device

**error** iopath is currently referenced by a configurated ldev

it cannot be deleted

**error** iopath ! is currently referenced by a configurated ldev

**error** ldev ! must be the system disc

**error** ldev ! must be the system console

**error** invalid mode parameter

*error** iopath is already assigned

**error** please specify an associated manager

**error** iopath ! does not exist

**error** can't delete system console

**error** can't delete system disc

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.

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.

**error** can't delete system tape drive

You are attempting to delete the system tape drive through DDEV command by referencing its LDEV number, product identification, or class.

Reenter the command, if you want to delete a device other than the system tape drive.

**error** must specify volume member name

The VNAME parameter is omitted from the DVOL, MVOL, or AVOL command.

Specify a volume name.

**error** ldev ! is already configured as the system master volume

You are attempting to add a device with an LDEV that has already been configured as the system master volume.

Assign the device to another LDEV.

**error** can't delete the system master volume

You are attempting to delete the system master volume that is not allowed.

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.

**error** can't modify this parameter of the system master volume

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.

Reenter the command if you wish to modify a nonprotected parameter.

**error** this path has an associated ldev

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.

Use the LPATH command and LEVEL= parameter to list paths and associated devices. Base your action on the information.

**error** Can't read from default file

SYSGEN, for whatever reason, cannot read the default configuration file IODFAULT.PUB.SYS. Program dies.

Refer to the file system error for action to take.

**error** outdev is too long

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.

Enter a new value of acceptable length. Contact the software personnel responsible for maintaining the system file.

**error** manager name is too long

The manager name that you entered exceeds the acceptable number of characters for the string.

Enter a shorter name for your manager name.

**error** bad default file

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.

Contact the software personnel responsible for updating and maintaining this file.

**error** default file records too long

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.

Contact the software personnel responsible for updating and maintaining this file.

**error** name too long in default file

The device name, manager, or mode entry added to IODFAULT.PUB.SYS is too long. SYSGEN does not accept the device operation.

Contact the software personnel responsible for updating and maintaining this file.

**error** invalid integer in default file

An invalid numeric value has been added to IODFAULT.PUB.SYS. SYSGEN does not accept the device operation.

Contact the software personnel responsible for updating and maintaining this file.

**error** couldn't write to internal default file

For whatever reason, SYSGEN cannot write the device information to the internal default file. Program dies.

See the file system error for the action to take.

**error** nonexistent volume: !

The volume name entered is not recognized by the system. (Misspelled?)

Correct and reenter the command.

**error** path ! has no periods in it

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.

Reenter the path specification.

**error** path ! ends in a period

The referenced path is incomplete and ends in a period, or has an extra period.

Reenter the path for the operation.

**error** path ! has a bad component (too large, or non-numeric)

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.

Reenter the path.

**error** path name too long

The path you have entered has too many levels.

Reenter the path.

**error** path ! already exists.

You are trying to add a path or device that already exists.

Use the LPATH command and necessary level to list the existing paths. If necessary, use the LDEV command to list associated devices.

**error** mode 'NONE' can't be used with other modes

The device mode NONE cannot be used with other modes when more than one mode is assigned to a device.

Either add or modify the device and assign NONE as the only mode or enter the proper modes.

**error** % permanent + % transient must be at lease 100 percent

The total amount of permanent and transient space assigned to a volume must be at least 100 percent.

Increase either the transient or permanent percentage until the sum is 100 percent.

**error** Class name ! is too long.

The class name entered exceeds either characters.

Reduce the number of characters in the class name.

**warning** SYSGEN and NMMGR configuration conflict!

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.

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.

keep configuration anyway (yes/no)?

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.

Enter YES if you wish to save, or NO if not.

**error** can't delete NMMGR devices from SYSGEN

You are attempting to delete a device assigned by NMMGR. SYSGEN cannot add, delete,or modify NMMGR devices.

Delete the device through NMMGR.

**error** can't update iovol file

For whatever reason, SYSGEN cannot update the IPVOLP configuration data file. Program dies.

Refer to the file system error for the action to take.

**error** Bad device number (!) in ioldev file

The LDEV number found in the file does not fit into a 16-bit integer field.

Return to a known good set of configuration files.

**error** can't delete NMMGR classes from SYSGEN

Classes with the type NMMGR are displayed for reference only and cannot be changed or deleted through SYSGEN.

Run NMMGR to remove the class.

**error** can't write ioclass file

FWRITE failed to write to IOCLASSP file.

Refer to file system message, also returned.

**error** SYSGEN ans NMMGR are both using class !

**error** SYSGEN and NMMGR are both using ldev !

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.

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.

**error** SYSGEN and NMMGR are both using path !

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.

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.

**error** FFIND failed on iopath file

SYSGEN has encountered an internal system error in attempting to initialize the processing of the iopath configuration file.

Contact the software personnel responsible for updating and maintaining these files.

**error** can't change path ! to !

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.

As this normally occurs from an entry mistake, reenter the proper path(s); otherwise, use the APATH command to add the iopath structure.

**warning** path not changed for ldev !

The iopath for the device referenced cannot be changed to the new path, for whatever reason.

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.

**error** can't delete NMMGR paths from SYSGEN

An NMMGR path, once defined through NMMGR and set through the SYSFILE RDCC command, cannot be deleted through the I/O configurator DPATH command.

None.

**error** can't change NMMGR paths from SYSGEN

An NMMGR path, once defined through NMMGR and set through the SYSFILE RDCC command, cannot be modified through the I/O configurator MPATH command.

None.

NMMGR path ! is incomplete

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.

Through RDCC, designate a valid remote configuration file.

**error** Volume configuration is corrupted!

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.

Contact the software personnel responsible for updating and maintaining these files.

ldev ! is invalid

This message furnishes the LDEV identity of the previous volume configuration corruption message.

See the volume configuration corruption message.

!% transient is invalid

This message gives the transient percentage of the previous volume configuration corruption message.

See the volume configuration corruption message.

!% permanent is invalid

This message gives the permanent percentage of the previous volume configuration corruption message.

See the volume configuration corruption message.

**error** Ldev configuration is corrupted!

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.

Contact the software personnel responsible for updating and maintaining these files.

rsize ! is invalid

This message, following the LDEV configuration corruption gives the record size in question.

Go back to a known good configuration. If the problem recurs, contact SE.

**error** Path configuration is corrupted!

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.

Contact the software personnel responsible for updating and maintaining these files.

physical manager priority of ! is invalid

This message gives the physical manager's priority, that is being questioned.

See the path configuration corruption message above.

! max. expected concurrent I/Os is invalid

This message gives the maximum number of concurrent I/Os, that is being questioned.

See the path configuration corruption message above.

**error** Class configuration is corrupted!

The number of DCC devices field has been corrupted in IOCLASSP.

Go back to a known good configuration. If problem recurs, contact SE.

**error** USER device requires all parameters!

You have omitted one or more parameters.

Reenter command with all parameters.

**error** Can't change to id=!

You cannot change the ID to this value. Most often USER.

Reenter command with proper ID= parameter.

**error** Can't seek to beginning of ioclass file

SYSGEN encountered an internal system error in attempting to initialize the ioclass configuration file for processing.

Contact the software personnel responsible for updating and maintaining these files.

**error** Couldn't determine appropriate class mode for ldev !

SYSGEN has encountered an internal system error in attempting to obtain the class and mode from the ioclass configuration file.

Contact the software personnel responsible for updating and maintaining these files.

**error** Class ! can't accept ldev !--incompatible modes

You have attempted to include a device whose mode is incompatible with the other devices in this class.

Reenter the command without the device under question.

**error** Class ! can't accept mode !

You have attempted to add a mode that is incompatible with some or all the devices in this class.

Review the conflict and reenter the command with the proper MODE= parameter.

**error** Too many devices in class !--device not added

A device class can only hold so many devices--currently 255.

Remove other devices from class, or create a new class.

**error** class info is corrupt (class !)

The records of the IOCLASS configuration file, that contains the information for this LDEV, is corrupted.

Contact the software personnel responsible for updating and maintaining these files.

**error** Class VTERM is reserved

You cannot assign this name to a class. The system has reserved its usage for a special purpose.

Reenter the command with another name for the class.

**error** Class ! is reserved and cannot be deleted

You have attempted to delete a class that the system has reserved for its special purpose.

None.

**error** Class ! is reserved and cannot be changed

You have attempted to modify a class that the system has reserved for its own special purpose.

None.

**error** Can't create class ! with mode !--class not added

You have attempted to create a class with an inconsistent mode. SYSGEN does not accept the class operation.

Review the conflict and reenter the command with the proper mode.

**error** ldev ! does not exist

You have attempted to add an LDEV to this class that does not exist.

Reenter command with a proper LDEV number.

**error** class file or DCC mode bad--mode is !

SYSGEN's class file is in conflict with NMMGR's configuration file. The displayed mode is in question.

Contact software personnel responsible for updating and maintaining these configuration files.

**error** Can't remove class ! from device !

You are attempting to delete a class from a device, that could cause the system not to be able properly determine its function.

Contact software personnel responsible for updating and maintaining this file.

**error** mpe type only configurable for USER devices

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.

Assigned to USER devices or contact software personnel who is responsible for maintaining these file for adivice.

**error** mpe subtype only configurable for USER devices

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.

Assigned to USER devices or contact software personnel who is responsible for maintaining these file for advice.

**error** MODE=NLIO not configurable for this device

Setting MODE equal to NLIO is allowed only for printers and terminals. You probably set it for a different device.

Check the configuration and specify an appropriate device.

**error** Use the adev command to add devices

You have attempted to add a device that has not been defined through the parameters to this command.

Add the device prior to using this command.

**error** Can't change this path to be a device

You have attempted to change a path designation to be a device. SYSGEN does not accept the operation.

None.

**error** Can't change ldevs to paths or paths to ldevs

You have attempted to interchange LDEVs and paths. SYSGEN does not accept the operation.

Reenter the command with the proper parameters.

**error** Use the mdev command to modify devices

You have attempted to change some of the device configuration elements within this command. SYSGEN does not accept the operation.

None.

**error** OUTDEV invalid

You have attempted to designate a device that is incompatible with OUTDEV requirements. SYSGEN does not accept the operation.

Reenter the command with the proper device.

**warning** # of rins must be at least !--misc value changed.

You have requested a number of RINs that is below the minimum.

Reenter the command with the minimum value.

**warning** # of global rins must be at least !--misc value changed.

You have requested a number global RINs that is less than the minimum.

Reenter the command with the minimum value.

**warning** rin ! does not exist

You have entered a RIN that the system does not recognize.

Reenter the command with the proper RIN.

**warning** Unless you've made a tape, any rins

This warning is to let you know that the deleted RINs only disappear upon a system update.

Create boot tape and update the system.

you've deleted will no longer be deleted.

This is the second half of message above.

None.

**warning** default NM stack size cannot be greater than maximum.

You have requested a default native mode stack size that is greater than the specified maximum value.

Either reenter the command with a valid stack size or set to the maximum.

**warning** default CM stack size cannot be greater than maximum.

You have requested a default compatibility mode stack size that is greater than the specified maximum value.

Either reenter the command with a valid stack size or set to the maximum.

**warning** default HEAP size cannot be greater than maximum.

You have requested a default heap size greater than the specified maximum value.

Either reenter the command with a valid heap size or set to the maximum.

fault reduced to !

This message displays resulting default for message above.

None.

**warning** DEFAULT NM STACK must be a multiple of 4096. New value is !.

The nm parameter must be a multiple of 4096 (page_size).

SYSGEN has rounded DEFAULT NM STACK up to next multiple of 4096. No further action required.

**warning** MAXIMUM NM STACK must be a multiple 4096. New value is !.

The maxnm parameter must be a multiple of 4096 (page_size).

SYSGEN has rounded MAXIMUM NM STACK up to next multiple of 4096. No further action required.

**warning** DEFAULT HEAP must be a multiple of 4096. New value is !.

The heap parameter must be a multiple of 4096 (page_size).

SYSGEN has rounded DEFAULT HEAP up to next multiple of 4096. No further action required.

**warning** MAXIMUM NM HEAP must be a multiple of 4096. New value is !.

The maxheap parameter must be a multiple of 4096 (page_size).

SYSGEN has rounded MAXIMUM NM HEAP up to next multiple of 4096. No further action required.

**error** can't read MISC configuration data

SYSGEN encountered an error in trying to read the miscellaneous configuration data file.

Refer to the file system error.

**error** system ID too long

You have entered a system ID that has too many characters. The limit is eight.

Reenter the command with the proper system ID value.

**error** can't display parameter ! in misc display table

SYSGEN has encountered an error in trying to display this parameter from the miscellaneous configuration data file.

Contact software personnel responsible for updating and maintaining these files.

**error** prompt too long

You have requested a string for the prompt that has too many characters for the configuration file entry.

Reenter the command with a shorter string.

**error** Can't get an extra data segment for rin table

Same as message.

Refer to system error message for action.

**error** Can't initialize extra data segment for rin table

SYSGEN has encountered an internal system error in attempting to initialize the new space granted for RIN table expansion.

Refer to system or file system error for action.

**error** Can't list rins

SYSGEN has encountered a system error in trying to list the RINs as requested.

Refer to system error or file system error message for the action to undertake.

**error** Can't alter extra data segment for rin table

SYSGEN has encountered an internal system error in trying to make changes in the new area of the RIN table.

Refer to system error message for the action.

**error** Can't read from extra data segment for rin table

SYSGEN has encountered a system error in trying to read the RIN table in trying to process your command.

Refer to the system or file system error for the action.

**error** Can't free extra data segment for rin table

SYSGEN has encountered a system error in trying to release a portion of the RIN table in trying to process your command.

Refer to the system error for the action.

**error** Can't get rin table size from extra data segment

SYSGEN has encountered as error in trying to obtain the RIN table size while processing your command.

Refer to the system error for action.

**error** can't write MISC configuration data

SYSGEN has encountered an error while trying to write to the miscellaneous configuration data file.

Refer to the system or file systems error for action.

**error** Only the factory can change this.

You have attempted to change an item in the miscellaneous configuration data that is reserved for factory maintenance.

None.

**error** sysprompt string in MISC configuration corrupt!

SYSGEN has encountered an error in trying to obtain the system prompt string value.

Contact software personnel responsible for updating and maintaining these files.

**error** ciprompt string in MISC configuration corrupt!

**error** configuration files incompatable with this version of SYSGEN

SYSGEN version = ! Config files version = !

**warning** of logging processes is smaller than LID table.

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).

If you want logging IDs preserved, raise the value. Otherwise, ignore it.

LID table on tape will be empty!

**error** can't read LOG configuration data

SYSGEN cannot read the configuration data file LOGP for whatever reason. Program dies.

Refer to the file system error for action to take.

**error** can't write LOG configuration data

SYSGEN cannot write the configuration data file LOGP for whatever reason. Program dies.

Refer to the file system error for action to take.

**warning** boot image ! not deleted

The boot image cannot be replaced or deleted.

None for system manager normally. Should be handled by personnel with programming or SYSFILEP file maintenance responsibilities.

**warning** File not an IPL file. Include anyway?

**warning** no NMCONFIG file in this configuration

A remote configuration file has not been designated through the SYSFILE RDCC command. SYSGEN uses the default NMCONFIG.PUB.SYS file if it exists.

Enter a remote configuration file name through RDCC in the SYSFILE Configurator. If a remote configuration does not exist, create one through NMMGR.

**warning** ! is now the NMCONFIG file

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.

If you want a different remote configuration file used, designate the file through the SYSFILE configurator RDCC command.

**error** can't create temporary segment file

**error** can't initialize temporary segment file

**error** can't write to temporary segment file

**error** You must specify a CM SL first

**error** can't find system program file

Nonexistent file, misspelled name, and so on.

**error** segment name already exists

**error** can't create temporary CM SL

**error** can't open system SL

**error** can't update system file configuration

SYSGEN cannot update the SYSFILE for whatever reason. The program dies.

Refer to the file system error for action to take.

**error** can't read from system SL

**error** can't write to temporary SL

**error** can't delete system file

**error** can't find system file --!

Nonexistent file, misspelled, and so on.

**error** can't add record to system file configuration

SYSGEN cannot add record to SYSFILE for whatever reason. The program dies.

**error** can't add segment "!" to temporary SL

**error** command rejected by segmenter

**error** command conditionally accepted by segmenter

**error** illegal calling sequence in segmenter

**error** unable to create segmenter process

**error** unable to activate segmenter process

**error** unable to send mail to segmenter process

**error** unable to receive mail from segmenter process

**error** segmenter process aborted

**error** can't delete segment "!" from temporary SL

**error** can't find system catalog

Nonexistent system catalog, misspelled, and so on.

**error** can't read from Sysfile configuration file

SYSGEN cannot read from SYSFILEP for whatever reason. The program dies.

Refer to the file system error for action to take.

**error** file ! does not exists

Nonexistent file.

Check file spelling. Use name of file that exists.

**error** system program already exists

Trying to add program file that has already been added, (possibly as a boot file, or other type).

Do a SHOW SYSFILE to determine what it is.

**error** NM library already exists

**error** CM SL is not switched

CM SL has pending changes, want to ignore them (yes/no)?

**CM SL is not switched**

**error** temporary CM SL prep fails

**error** can't find boot images

**error** file already exists in SYSFILE configuration

**error** file not found, or of different type: !

Deleted system program, or doesn't exist.

Use correct delete, or check name.

**error** image already exists in SYSFILE configuration

Each image must be unique across all types.

**error** image doesn't exist in SYSFILE configuration

Can't delete if not there.

**error** The version parm is only valid with disc boot files

**error** start version ! is already in use

**error** all start versions are in use

**error** nmlib version ! is already in use

**error** parameter name is too long

**error** Can't delete !. Delete the boot file instead.

**error** Can't find start's library (shouldn't happen!)

**error** The image you replace must be an IPL image

**error** There's already a ! file

Can only have one.

**error** Only ! tape boot files are allowed.

Only ! fits in directory ISL uses.

**error** Only ! disc boot files are allowed.

Only ! fits in directory ISL uses.

**error** Only ! system files are allowed.

**error** Only the factory can ABOOT IPL files.

**error** Couldn't find any files of mode !