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.
You can find these extended File Status Codes in isCOBOL's documentation, in the Appendices on the "File Status Codes" page. The text for each code is also listed below.
You can get extended error information by either:

  1. Creating a runtime log with iscobol.tracelevel set to a value that includes 8
       iscobol.tracelevel=15
       iscobol.logfile=<path>/mylog.txt
    
  2. Capture the error and call "C$RERR"
       display-file-error.
          call "C$RERR"     using crerr-status, crerr-text
          call "C$RERRNAME" using rerrname
          display message "Error "  crerr-status, ", ", crerr-text " on " rerrname 
    
The following list of extended values is from the runtime framework source code:
   static final String errMess[] = {
         /* 100 */ "duplicate record",
         /* 101 */ "file not open",
         /* 102 */ "illegal argument",
         /* 103 */ "illegal key desc",
         /* 104 */ "too many files open",
         /* 105 */ "bad isam file format",
         /* 106 */ "non-exclusive access",
         /* 107 */ "record locked",
         /* 108 */ "key already exists",
         /* 109 */ "is primary key",
         /* 110 */ "end/begin of file",
         /* 111 */ "no record found",
         /* 112 */ "no current record",
         /* 113 */ "file locked",
         /* 114 */ "file name too long",
         /* 115 */ "",
         /* 116 */ "can't alloc memory",
         /* 117 */ "bad custom collating",
         /* 118 */ "Cannot read log file record",
         /* 119 */ "Record format of transaction-log file cannot be recognized",
         /* 120 */ "Cannot open transaction-log file",
         /* 121 */ "Cannot write to transaction-log file",
         /* 122 */ "Not in transaction",
         /* 123 */ "",
         /* 124 */ "Beginning of transaction not found",
         /* 125 */ "incompatible operation with open mode",
         /* 126 */ "function not supported",
         /* 127 */ "disk full",
         /* 128 */ "rec changed",
         /* 129 */ "no more locks available",
         /* 130 */ "missing file",
         /* 131 */ "invalid permission",
         /* 132 */ "file exixsts",
         /* 133 */ "system error",
         /* 134 */ "Unknown error",
         /* 135 */ "Unknown error",
         /* 136 */ "Unknown error",
         /* 137 */ "Unknown error",
         /* 138 */ "Unknown error",
         /* 139 */ "Unknown error",
         /* 140 */ "Unknown error",
         /* 141 */ "Unknown error",
         /* 142 */ "Unknown error",
         /* 143 */ "Unknown error",
         /* 144 */ "Unknown error",
         /* 145 */ "Unknown error",
         /* 146 */ "Unknown error",
         /* 147 */ "Unknown error",
         /* 148 */ "Unknown error",
         /* 149 */ "Unknown error",
         /* 150 */ "Too many connections",
         /* 151 */ "Malformed url",
         /* 152 */ "Error on connection: error in iserrio",
         /* 153 */ "Error on connection: no permission",
         /* END */ "Unknown error"

Authored by: Veryant Support This question has been viewed 10872 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 support 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. Can I call from an isCobol program a stored procedure?
  8. Why do I get the error message “java.lang.ClassNotFoundException: ctree2" ?
  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 &quot;assign to&quot; clause of the select statement without source code changes?
  11. Did you know you can encrypt an indexed file?
  12. Handling the extension on indexed data files
  13. How to hide the user and password used to connect to an RDBMS
  14. Can we use Micro Focus format data and indexed files directly or do they need some form of conversion?
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.