support: Customer Portal
Focused on delivering choice, investment protection and flexibility to organizations with valuable COBOL assets
 

Veryant Knowledge Base
Home > All Categories > Data Access > How do I interpret file status 9? and other EXFS extended file status codes (e.g. 9i,105)?
Question Title How do I interpret file status 9? and other EXFS extended file status codes (e.g. 9i,105)?

The letter after the 9 is the character representation of the extended file status using ASCII encoding. For example, a 9i is the same as file status 9 with extended status 105 (i.e. EXFS=105) because 'i' is 105 in ASCII.

The following is from the runtime framework source code:

   // IO ERROR
   static final int E_IO_DUPL = 100; /* duplicate record */
   static final int E_IO_NOTOPEN = 101; /* file not open */
   static final int E_IO_BADARG = 102; /* illegal argument */
   static final int E_IO_BADKEY = 103; /* illegal key desc */
   static final int E_IO_TOOMANY = 104; /* too many files open */
   static final int E_IO_BADFILE = 105; /* bad isam file format */
   static final int E_IO_NOTEXCL = 106; /* non-exclusive access */
   static final int E_IO_LOCKED = 107; /* record locked */
   static final int E_IO_KEXISTS = 108; /* key already exists */
   static final int E_IO_PRIMKEY = 109; /* is primary key */
   static final int E_IO_ENDFILE = 110; /* end/begin of file */
   static final int E_IO_NOREC = 111; /* no record found */
   static final int E_IO_NOCURR = 112; /* no current record */
   static final int E_IO_FLOCKED = 113; /* file locked */
   static final int E_IO_FNAME = 114; /* file name too long */
   static final int E_IO_BADMEM = 116; /* can't alloc memory */
   static final int E_IO_BADCOLL= 117; /* bad custom collating */
   static final int E_IO_LOGREAD= 118; /* Cannot read log file record. */
   static final int E_IO_BADLOG = 119; /* Record format of transaction-log file
                                      cannot be recognized. */
   static final int E_IO_LOGOPEN =120; /* Cannot open transaction-log file. */
   static final int E_IO_LOGWRIT =121; /*Cannot write to transaction-log file.*/
   static final int E_IO_NOTRANS =122; /*Not in transaction. */
   static final int E_IO_NOBEGIN =124; /* Beginning of transaction not found. */
   /*
    * JISAM extended error codes
    */
   static final int E_IO_BADOPENMODE=125; /*incompatible operation with
                                            open mode*/
   static final int E_IO_NOTSUPP    =126; /* function not supported */
   static final int E_IO_DISKFULL   =127; /* disk full */
   static final int E_IO_RECCHANGED =128; /* rec changed */
   static final int E_IO_NOLOCKS    =129; /* no more locks available */
   static final int E_IO_MISSINGFILE=130; /* missing file */
   static final int E_IO_PERMISSION =131; /* invalid permission */
   static final int E_IO_FILEEXISTS =132; /* file exists */
   static final int E_IO_SYSTEM     =133; /* system error */
   static final int E_IO_UNKNOWN    =134; /* Unknown error */
   // Cobol only errors
   static final int E_IO_ALREADY_OPEN=135; /* Already open */
   static final int E_IO_NOTFORINPUT =136; /* File not open for INPUT or I-O */
   static final int E_IO_NOTFOROUTPUT=137; /* File not open for OUTPUT or I-O */
   static final int E_IO_NOTFORIO    =138; /* File not open for I-O */
   static final int E_IO_INVALIDWRITE=139; /* Invalid write */
   static final int E_IO_NO_REMAPPABLE=140; /* Error non remappable in COBOL */
   static final int E_IO_CLOSE_WITH_LOCK=141; /* File closed with lock */
   static final int E_IO_INVALID_OPEN=142; /* Invalid open mode */
   static final int E_IO_INVSEQDELREW=143; /*Invalid sequential rewrite/delete*/
   static final int E_IO_NOTSTART    =144; /*Unable to start service*/
   static final int E_IO_BOUNDVIOL   =145; /* Boundary violation */
Authored by: Veryant Support This question has been viewed 7734 times so far.
Click Here to View all the questions in Data Access category.
File Attachments File Attachments
There are no attachment file(s) related to this question.
How helpful was this article to you?
User Comments User Comments Add Comment
There are no user comments for this question. Be the first to post a comment. Click Here
Related Questions Related Questions
  1. File Types Comparison : isCOBOL - Micro Focus COBOL - ACUCOBOL-GT - RM/COBOL
  2. What format does isCOBOL use for ORGANIZATION RELATIVE files?
  3. What is 9l,10 error and why is it happening?
  4. Does isCOBOL supports Data General file status codes?
  5. Can we use Micro Focus data format and indexed files directly or do they need some type of conversion?
  6. Can I install the UDBC 32 bit on my 64 bit computer in order to have the Veryant * driver for ODBC32 bits Administrator?
  7. Why do I get the error message “java.lang.ClassNotFoundException: ctree2" ?
  8. Can I call from an isCobol program a stored procedure?
  9. Why do I get 'ct_init ERROR 19:133:0' ?
  10. Did you know you can use an alias to map a different disk file name to an existing "assign to" clause of the select statement without source code changes?
  11. Did you know you can encrypt an indexed file?
  12. How to hide the user and password used to connect to an RDBMS
Article Information Additional Information
Article Number: 150
Created: 2010-10-18 5:01 PM
Rating: 2 Stars
 
Article Options Article Options
Print Question Print this Question
Email Question Email Question to Friend
Export to Adobe PDF Export to PDF File
Export to MS Word Export to MS Word
Bookmark Article
Subscribe to Article Subscribe to Article
 
Search Knowledge Base Search Knowledge Base



 
 

© Veryant - All Rights Reserved
Veryant and isCOBOL are trademarks or registered marks of Veryant in the United States and other countries. All other marks are the property of their respective owners.