General Errors

Error Code

Error Condition

Explanation/Possible Fix

0x0001

Invalid function error

An attempt was made to call a function which does not exist or is not supported. This is generally caused by a bug in the userís application. Debug the application.

0x0002

File not found error. File does not exist.

Check the command syntax.

0x0003

Path not found error. Bad path specifier.

Check the command syntax.

0x0004

No file handles left.

Close some files or reconfigure the HAN DLES= parameter.

0x0005

Access denied error. Operation cannot be sup ported at this time.

This generally occurs when an illegal operation such as deleting a read-only file is attempted.

0x0006

Invalid Handle error.

An attempt was made to use an unopened or non-existent file handle. This is gener ally a bug in the userís application. Debug the application.

 

 

 

0x0012

No more files. The search next has exhausted all possible matches.

Normal error received at end of search.

0x0013

File already exists.

An attempt was made to create a file or directory that already exists. This is an illegal operation.

0x0014

Unable to make dir entry. Error in directory cre ation.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drives have been serviced and cleaned.

0x0090

Recovered a bad CDR.

The system found a bad directory record and recovered it. You may have lost a part of your file. Do not report this error to Pegasus. Contact your hardware manufac turer.

0x0091

The system found a bad data link and cor rected it.

You may have lost a part of the file. Do not report this error to Pegasus.

0x0092

 

 

 

0x0093

The system recovered a bad file size.

 

A descrepancy in the BTREE.

It corrected the file that did not match the actual recorded size. Do not report this error to Pegasus.

 

This normally indicates that there is a problem with the InveStore cache record for a particular volume. To correct this, un-mount the suspected volume with the "Delete Cache" option, and then re-mount the volume again.

 

0x009f

Disk marked full because of write error - spares table full.

The disk is not physically full, but the controller will no longer allow writes.

0x00a0

Disk full error. No more free sectors.

The disk can no longer be written to.

0x00a1

Unknown con trol record. Directory record cannot be recog nized.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00a2

Directory record found is not a valid File Descriptor block.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00a3

Control record missing.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00a4

The recorded file size does not match the num ber of data descriptors.

 

0x00a5

Bad Data Seg ment Descrip tor. Control record con tained an invalid DSD.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00a7

Unreadable disk parameter block. System area contains failing sectors.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00a8

Bad system parameter block. System area contains failing sectors.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00a9

Bad Partition parameter block. System area contains failing sectors.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00aa

Low Level Disk label unread able. System area contains failing sectors.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00ab

File Descriptor block is miss ing. Directory is damaged.

This is generally caused by a media error. Check the log file. Make sure your car tridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manu facturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00ac

Control Record name doesn't match File Descriptor Block.

The directory record is corrupt. This is generally caused by a media error. Check the log file. Make sure your cartridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manufacturer and provide them with the SCSI error codes that have been recorded in the log file.

0x00ae

Disk has not been software formatted.

Issue the format command before mount ing the cartridge.

0x00af

Disk not PDT format.

The disk has been initialized by some other file system. Disk must be reformat ted (if it is an erasable disk) before it can be used. WORM disks that contain another file system cannot be used by the Pegasus software.

0x00b0

Mag Cache/Storage Cache mis match.

The configuration file contains invalid cache parameters. Use the Cache Managagement option under Administrative tools to correct this. The Pegasus kernel will use the defaults for the cache options instead.

0x00b2

The number of users in the Reg istry is in error and is out of range.

Legacy entry.

0x00b3

Invalid number of volume speci fied in configu ration file.

VOLUMES= specified is out of range. Configuration file contains invalid vol ume parameters. The Pegasus ker nel will use the defaults for the VOL UMES= options instead.

0x00b4

Bad/missing numeric value in configuration file.

The configuration file contains an invalid line that does not specify a value. The Pegasus kernel will use the defaults for the cache options instead.

0x00b6

Invalid mag netic partition size. The mag netic partition specification was invalid.

The configuration file contains an invalid magnetic partition value. The opti cal.cnf file has been incorrectly set. The Pegasus kernel will use the defaults for the cache options instead.

0x00b8

Bad parameter in configuration file.

The configuration file contains an invalid line that specifies an unknown parameter. The Pegasus kernel will discard the invalid line.

0x00c0

Magnetic file open failure. Unable to open cache or spool file.

Make sure that the Pegasus kernel has at least 50M bytes of free disk space.

Make sure the Pegasus software is not using the same drive as the operating sys tem virtual memory disk swapper.

Make sure that someone has not deleted the Pegasus cache files while the system was in operation.

0x00c1

Magnetic file close failure. Unable to close cache or spool file.

Make sure that the Pegasus kernel has at least 50M bytes of free disk space.

Make sure the Pegasus software is not using the same drive as the operating sys tem virtual memory disk swapper.

Make sure that someone has not deleted the Pegasus cache files while the system was in operation.

0x00c2

Magnetic file read failure. Unable to read desired data from cache or spool file.

 

0x00c3

Magnetic file write failure. Unable to write specified bytes to cache or spool file.

This generally occurs because of insuffi cient disk space. Make sure your SPOOL FILES= parameter has been correctly set. If SPOOL FILES was set to use a ram disk, make sure the ram disk still exists.

Make sure that the Pegasus kernel has at least 5M bytes of free disk space.

Make sure the Pegasus software is not using the same drive as the operating sys tem virtual memory disk swapper.

Make sure that someone has not deleted the Pegasus cache files while the system was in operation.

0x00c4

Magnetic file create failure. Unable to create cache or spool file.

This is generally caused by an invalid SPOOL FILES= parameter in the configu ration file or by insufficient magnetic disk space.

Make sure your SPOOL FILES = parame ter has been correctly set. If SPOOL FILES was set to use a RAM disk, make sure the RAM disk still exists.

Make sure that the Pegasus kernel has at least 5M bytes of free disk space.

Make sure the Pegasus software is not using the same drive as the operating sys tem virtual memory disk swapper.

Make sure that someone has not deleted the Pegasus cache files while the system was in operation.

0x00c5

Magnetic file position failure. Unable to move cache or spool file pointer to desired location.

Make sure that someone has not deleted the Pegasus cache files while the system was in operation. If this is not the case, report the error to Pegasus Disk Technolo gies.

0x00c6

Insufficient Magnetic disk space. Cache is exhausted or below minimum level.

You will have to free some disk space. The Pegasus kernel will not be able to write any data or make any new directo ries until more disk space is available.

0x00c7

Magnetic file delete failure. Unable to delete cache or spool file.

 

Make sure your SPOOL FILES= parame ter has been correctly set. If SPOOL FILES was set to use a RAM disk, make sure the RAM disk still exists.

Make sure that the Pegasus kernel has at least 5M bytes of free disk space.

Make sure the Pegasus software is not using the same drive as the operating sys tem virtual memory disk swapper.

Make sure that someone has not deleted the Pegasus cache files while the system was in operation.

0x00c8

Invalid file num ber. Attempt to access cache file with an invalid number.

This is an internal error. Please report this to Pegasus following the procedure specified in Appendix B, "Troubleshooting."

0x00c9

Magnetic cache is completely consumed. No more magnetic disk space.

Make sure your SPOOL FILES= parame ter has been correctly set. If SPOOL FILES was set to use a RAM disk, make sure the RAM disk still exists.

Make sure that the Pegasus kernel has at least 5M bytes of free disk space.

Make sure the Pegasus software is not using the same drive as the operating sys tem virtual memory disk swapper.

Make sure that someone has not deleted the Pegasus cache files while the system was in operation.

0x00ca

Attempt to access cache file type that does not exist.

This is an internal error. Please report this to Pegasus following the procedure specified in Appendix B, "Troubleshooting." Shut down the system and restart.

0x000d

 

 

 

 

 

 

 

0x00d1

inconsistency in FAD structures.

 

 

 

 

 

 

Error condition in directory files.

The FAD structures are apart of the InveStore cache files used to track the status of writes to the storage device.

 

This error means that there was a problem during a write operation, and the FAD were not completed or closed properly.

 

 

Rebuild cache files for affected volume set.

 

0x00d2

Volume already mounted. Attempt to mount the same volume twice.

This is a user error. Do not report this error to Pegasus.

0x00d3

Duplicate vol ume error. Attempt to mount a volume with the same name as an existing volume.

You have attempted to mount a cartridge that contains the same low level disk name and disk id. This operation is ille gal. This is a user error. Do not report this error to Pegasus.

0x00d6

Error getting volume id. Unable to create a virtual volume id.

This is an internal error. Please report this to Pegasus following the procedure specified in Appendix B, "Troubleshooting." Shut down the system and restart.

0x00d7

Disk not vol ume labeled. No valid name for disk.

The disk must contain a valid label. Rela bel the cartridge before mounting.

0x00d8

Unknown or invalid volume.

An attempt was made to access a non- existent volume. This is the same as a BAD PATH error. Check your command syntax.

0x00d9

Volume not mounted.

An attempt was made to access files on an off-line volume. Mount the cartridge if access to the data is required.

0x00da

Kernel not ini tialized.

An attempt was made to access software before it has been initialized. You must allow the system to initialize before it can be used.

0x00de

Kernel already active.

An attempt was made to install a second copy of the kernel Illegal operation. Only one copy of the kernel can run.

0x00e4

Volume ID is missing.

This is a bug in the userís application when attempting to use the VIM interface directly. Debug the application.

0x00e5

Attempt to rename files across volumes.

This operation is illegal.

0x00e7

Canít assign storage drive. Invalid drive ID was specified.

This error message is usually generated for one of three reasons: when a request is made for a drive that is not available, when a drive ID is specified that doesnít exist, or when a drive cannot be used for the requested operation. The drive status may be set to off-line. Check the drive sta tus.

0x00e8

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

0x00f0

Unable to Directory Mount Volume

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Bad file pointer adjustment.

This indicates that the library and the InveStore directory cache files are no longer in synch. This error may also indicate that the requested volume or volume set is not I/O accessible. This error can be returned to in response to an InveStore API call for an offline volume.

To recover from a directory cache file synch problem, please see the Standard Recovery procedure.

To recover from an API request, ensure that the requested volume is online or "nearline".  Data I/O is not possible from offline volumes.  

An attempt was made to illegally change file pointer location to before the begin ning of the file. This indicates a bug in the userís applications. This operation is illegal.

0x00fe

File is in the pro cess of being deleted.

This file logically no longer exists.

0x00ff

End of file error.

The control record is missing data seg ment descriptors which describe the file. Generally indicates that the control record is corrupt. Sometimes occurs if cache files are corrupt.

Generally caused by a media error.

Check the log file.

Make sure your cartridges and drive have been serviced and cleaned. If the log file reports any type of media error, call the drive or media manufacturer and provide them with the SCSI error codes that have been recorded in the log file.

0x8001

Operating sys tem indepen dent layer out of memory.

You may not have a large enough page file for the operating system.

0x8002

Operating sys tem indepen dent layer cannot set file handle count.

Report this error to Pegasus.