Code

Description

-1

Unable to lock file. MS-DOS Share command not loaded.

-2

Unable to re-open file.

-3

Unable to access the file specified by the OPEN operation. File does not exist or is not located within a Logged On Drive or search path. File is already open in EXCLUSIVE mode by another program/process. You may need to increase the number of files in CONFIG.SYS for MS-DOS. If sub-code 05 is given under MS-DOS, a possible cause is insufficient SHARE buffer space. See the MS-DOS user's guide on how to allocate a larger SHARE buffer space. Also the number of files specified in CONFIG.SYS may need to be increased or the .TXT portion of an .ISI or .AAM file could not be found in a search path.

-4

Unable to access the ISAM file specified by the OPEN instruction. See 'I03' error above.

-5

I/O operation attempted on an unopened file.

-6

Insufficient file handles available to PREP/OPEN the specified file.

-7

The path and filename size is too large to be placed into an AAM or ISI header during a PREPARE instruction. Valid subcodes that can occur with this error as follows:

20: A text file name without a path is larger than 47 characters. The text file name size must be less than 47 characters.

21: A text file name that may or may not include pathing information is larger than 47 characters and cannot be placed into an AAM or ISI header. If pathing information is included, the user may want to use a NOPATH keyword on an AFILE/IFILE declaration to prevent the path information from being placed into an AAM or ISI header.

-8

During PREP, insufficient write or create privileges for the directory. During I/O, insufficient write privileges for the file/directory or file space full. You may need to increase number of files in CONFIG.SYS in MS-DOS.

-9

Unable to locate the file referenced by the CLOSE operation. Occurs if a file was deleted between the OPEN and CLOSE operations.

-10

Unable to PREP/OPEN the requested file. Insufficient memory available for requested file buffer size. Insufficient rights/privileges (write access) to the directory or file space full. Attempt to OPEN a read only file (444) in SHARE/EXCLUSIVE mode.

-11

Invalid file specification during OPEN, PREP, ERASE, or RENAME operation.

-12

Invalid sector number in WRITAB instruction. Either beyond End Of File or negative access number less than -4.

-13

Invalid record length. Either zero or greater than maximum.

-14

Invalid key length. Either zero, greater than maximum or greater than record length.

-15

Obsolete file format. SUNINDEX or SUNAAMDX the file with the correct version of the utility.

-16

A NULL key is invalid for an ISAM WRITE/INSERT operation. This error can also occur for an ISAM WRITE/INSERT operation when no key is specified and the IFILE being used does not have key location specifications identified.

-17

Key used in ISAM operation is longer than allowed for file.

-18

Invalid method variable in FILEIO operation.

-19

Invalid OPEN or PREP mode value further defined by the following subcodes:

30: The EOR type specified by the MODE={value} bitmap value indicates an end of record type that is not the same as the end of record that was found in the AFILE/IFILE/FILE text file being accessed.

31: The MODE={value} bitmap value contains an undefined open mode definition. This error occurs when the open mode bit mask specified is not one of the following definitions:

CMP_SHARE - 0x00000000
CMP_EXCLUSIVE - 0x00000010
CMP_SHARENF - 0x00000020
CMP_READ - 0x00000040

32: The MODE={value} bitmap value contains an undefined EOR type definition. This error occurs when more than one EOR type is specified by the value.

-21

Attempt to tab across the sector boundary.

-22

Standard file open or prep dialog was canceled. (PLBCMP-GUI)

-23

FILELIST error further defined by the following subcodes:

30: FILELIST MFD type error. All files declared in a FILELIST must be opened either as a managed (MFD) file or opened as non-managed file. It is not valid to mix managed and non-managed files in the same FILELIST.

31: FILELIST MFD invalid for SUNDM. All of the files declared for a FILELIST must be under the control of the same SUNDM.

32: FILELIST requires same FIXED record length. When using FIXED length records, all files in a FILELIST must be declared or created with the same record length.

33: FILELIST file must be FIXED record type. All files in the FILELIST must be declared or created with FIXED length records specified. Mixing FIXED and VARIABLE length records in a FILELIST is not allowed.

34: FILELIST requires VARIABLE record type. All files in the FILELIST must be declared or created with VARIABLE length records specified. Mixing FIXED and VARIABLE length records in a FILELIST is not allowed.

35: FILELIST file record length is invalid. When using VARIABLE length records, the primary or first file in the FILELIST must have a record length less than or equal to any of the secondary files in the FILELIST.

36: FILELIST file requires valid key specifications. It is invalid to execute a FILELIST DELETE, UPDATE, or WRITE operation when using an AFILE/IFILE opened without key specification data available for an ISAM file.

37: FILELIST file key specifications not present in ISAM file. It is not possible to determine the key specifications from the ISAM file. The ISAM file must be re-indexed or prepared using valid key specifications.

38: FILELIST file invalid for direct operations. Individual AFILE/IFILE file variables for a FILELIST cannot be used in a DELETE, INSERT, UPDATE, or WRITE operation. The AFILE/IFILE file variables can only be used to DELETE, UPDATE, and WRITE using the FILELIST label reference.

39: FILELIST text file mismatch detected. One of the files in a FILELIST is using a text data file that is different from the primary or first file in the FILELIST.

40: An IFILE included in a FILELIST was generated using the alternate primary key specification ("P{type}"{col}{func}{'string'}") option. The user should re-index the ISI file and use the primary key specification (P{nn}{=|#}{c}) option.

-24

CPU or demo version executing on a networked computer.

-25

File OPEN/PREP in EXCLUSIVE mode denied, file busy. Specified file is already in EXCLUSIVE mode use by another process.

-6

DELETE, INSERT, UPDATE, or WRITE operation attempted on a file opened in READ mode.

-30

Error returned while trying to delete a file during a CLOSE operation.

-31

Unable to perform requested ERASE or RENAME operation. The file to be renamed was not found. Illegal global/wildcard naming convention used (i.e., asterisks or question marks).

-32

WEOF statement was unable to set the file to the requested length.

-38

Valid READ or WRITE operation required prior to an INSERT operation. (Also see the PLBWIN_QNAME keyword.)

-39

Invalid data file for INSERT operation. Data file for the INSERT operation is not the same as the data file for the preceding READ or WRITE operation. (Also see the PLBWIN_QNAME keyword.)

-40

Valid READ required prior to an UPDATE, DELETE, READKG, or READKGP operation.

-41

Internal AAM write error (system error).

-42

Invalid match criteria on AAM READ operation. Attempt to READ without the non-blank, non-wildcard minimum bytes required.

-43

Illegal key field on AAM READ operation. Key field number is greater than the number of keys specified at file creation. Verify that the field number in all key are valid.

-44

No corresponding record in text file for specified key. Either a text record was deleted without deleting all secondary indices or a file erroneously points to an Invalid portion of the data file (system error). An I44 error can also occur with a random read if the data has been deleted.

-45

Insufficient access rights or disk resources during AAM key file block write.

-46

Insufficient information for a valid AAM READ. READ using Free form key less than the three byte, non-blank, minimum.

-47

Record length exceeds the declared buffer size for the FILE. Record written larger than declared BUFFER/FIX/FIXED size (256 byte default). Also, INSERT attempted with an invalid associated data record length. The following sub-codes further define the error:

101: The IFILE is declared for FIXED records and the record length being inserted is different than the IFILE fixed record length.

102: The IFILE is declared for VARIABLE or COMPRESSED records and the record length being inserted is greater than the buffer allocated for the IFILE.

103: The AFILE is declared for FIXED records and the record length being inserted is different than the AFILE fixed record length

104: The AFILE is declared for VARIABLE or COMPRESSED records and the record length being inserted is greater than the buffer allocated for the AFILE

-48

Null keys specified in AAM PREP operation.

-49

Key specification error in AAM PREPARE operation. Key specified was greater than the defined record length or the maximum key length.

-50

Inserted item overstored an existing record.

-51

Non-ISAM WRITE on ISAM file. Sequential write against an IFILE.

-52

An ISAM WRITE operation has failed because a DRN ( data record number ) could cause data in the text data file to be overwritten.

20: A data record number retrieved from an ISI deleted data record map is invalid.

21: A data record position, determined from the ISI file, points into the TXT data file before the actual end of file position.

-53

The file position for this INSERT or UPDATE operation points to a deleted record. MS-DOS SHARE utility has not been loaded.

-54

Too many AAM key specifications given for an AAM read operation.

-55

Attempt to write duplicate key to IFILE declared as NODUP.

-56

Internal ISAM stack error - Overflow/Underflow (system error).

-57

The record data last READ for an AFILE/IFILE variable in the FILELIST has been changed before a FILELIST UPDATE/DELETE operation was performed. This failure indicates that multiple users are changing data records for a file without the use of FILEPI or record locking.

-60

Unable to read ISAM sector. Possible hardware problem.

-61

Unable to write ISAM sector. Possible hardware problem.

-62

ISAM file structure fault. Reindex the file.

-63

ISAM tree stack underflow (system error).

-64

Update file position is invalid.

-65

Attempt to UPDATE a compressed file.

-66

DELETE requires FIXED file declaration.

-67

Attempted to write record longer than specified record length.

-68

Invalid record number specified in FILE DELETE. User has specified a record number that does not exist. Also, occurs when a -1, -2, -3, or -4 is specified as record number or when the data items are shorter than the record length.

-69

Unable to lock record before operation.

-71

Record locking requested and runtime does not support record locking.

-77

WEOF attempted to shorten a file and the file could not be shortened. Only happens on Linux systems that do not have the CHSIZE system call and on a file opened in SHARE mode. Try changing the file to EXCLUSIVE mode.

-80

Inconsistent FCB parameters on text file seek (system error).

-81

A problem occurred while communicating with the SUNDM server task. The following subcode values describe the possible cause of the error:

1: Insufficient memory to perform SUNDM server operations.

2: SUNDM unable to start child task.

3: Invalid SUNFHSYS.DLL version used.

4: Bad message type encountered.

5: SUNDM not found. Verify hostname, portnum, and IP addresses.

6: Failed to start socket.

7: Bad IP address.

8: Socket creation failure.

9: Socket communication failure.

10: SUNDM time expiration error.

11: SUNDM connection count has been exceeded.

12: The PL/B runtime and the Sunbelt Data Manager being accessed have versions that are incompatible.

14: The PL/B runtime has lost a connection to SUNDM while receiving a message.

-82

An error has been detected while trying initiate or perform an operation for a managed file. The following subcode values describe the possible cause of a specific error:

1: The version found in a '.MFD' file is invalid for use with this runtime.

2: The file used for managed file redirection is not a valid '.MFD' file.

3: The 'SUNFHSYS.DLL' version is invalid when used for managed file support with this runtime.

10: The number of controls and parameters in a READ list exceeds the available buffer size used for managed file operations.

20: The number of controls and parameters in a WRITE list exceeds the available buffer size used for managed file operations.

21: The runtime does not use encryption while the Sunbelt Data Manager requires encryption. Verify encryption setup provided by the runtime executing the PL/B program that received the I82 error.

22: The LOGON ID used by the runtime is invalid for the Logon Id list used by the Sunbelt Data Manager. User should contact the administrator who can setup or verify the current logon ids allowing access to SUNDM.

23: The current IP address used by the client workstation connecting to SUNDM is identified to be invalid by existing on a non-approved IP address list. The user should contact the administrator who can setup or verify the the current workstation IP addresses that may access SUNDM.

24: The current IP address used by the client workstation connecting to SUNDM is not valid to access the data manager. The user should contact the administrator who can setup or verify the current workstation IP addresses that can access SUNDM.

25: SUNDM section security error. Contact the system administrator.

26: SUNDM is unable to access IP filtering list. Contact the system administrator.

27: SUNDM does not use encryption while the runtime is specifying encryption keys. Contact the system administrator to verify runtime encryption requirements to access SUNDM.

30: Compression/Decompression error occurred while processing a message for SUNDM.

31: Either the runtime or SUNDM requires encryption and one of the connecting processes does not provide the encryption capability.

32: Encryption is enabled and the key specified by the runtime to access SUNDM is not valid.

-97

COMFILE not open.

-98

External call routine returned an error condition. The exact interpretation depends on the user logic executed for the EXTCALL statement

-99

File too (greater than 32k - Demo version only) or FILEPI already in effect.

-102

Invalid SET_PLB_EOR ConfigValue

-103

Invalid SA_CONFIG KeyValue

-104

Invalid BufLen for SA_CONFIG

-105

Unable to allocate memory for SA_CONFIG

-106

Error setting SET_OPENUSEIP, SET_PREPUSEIP, or SET_DMALTIP

-107

Invalid ConfigValue for SET_PLB_COPYFILEBUFFSZ

Sub-code

Definition

Windows Error

2

ENOENT

ERROR_FILE_NOT_FOUND

ERROR_INVALID_DRIVE

ERROR_INVALID_NAME

ERROR_NOT_DOS_DISK

ERROR_OPEN_FAILED

ERROR_PATH_NOT_FOUND

5

EIO

ERROR_CRC

ERROR_DISK_CORRUPT

ERROR_FILE_CORRUPT

ERROR_IO_DEVICE

Sub code

Definition

Error

9

EBADF

ERROR_INVALID_HANDLE

12

ENOMEM

ERROR_OUTOFMEMORY

13

EACCES

ERROR_ACCESS_DENIED

ERROR_CANNOT_MAKE

ERROR_PATH_BUSY

ERROR_SHARING_VIOLATION

16

EBUSY

ERROR_BUSY

17

EEXIST

ERROR_ALREADY_EXISTS

20

ENOTDIR

ERROR_DIRECTORY

23

ENFILE

ERROR_TOO_MANY_OPEN_FILES

28

ENOSPC

ERROR_DISK_FULL

ERROR_HANDLE_DISK_FULL