Indicates no record found. An attempt has been made to access a record, identified by a key, and that record does not exist in the file. Relative and indexed files only. Indicates a boundary violation. Possible causes: Attempting to write beyond the externally defined boundaries of a file. Attempting a sequential WRITE operation has been tried on a relative file, but the number of significant digits in the relative record number is larger than the size of the relative key data item described for the file.
Too many Indexed files opened. This can also happen when a sequential file is open for input and an attempt is made to open the same file for output. This condition indicates that an attempt has been made to write beyond the externally defined boundaries of a sequential file. Trying to open a file that does not exist. A conflict has been detected between the actual file attributes and the attributes specified for the file in the program.
This is usually caused by a conflict with record-length, key-length, key-position or file organization. Other possible causes are: 1. Alternate indexes are incorrectly defined Key length or position, duplicates or sparse parameters.
The Recording Mode is Variable or Fixed or not defined the same as when the file was created. For files with variable-length records the minimum and maximum record lengths for the actual file may not match the minimum and maximum record lengths used by the program. Files in sequential access mode. A boundary violation exists. Micro Focus For line sequential files this refers to the physical size of the record, that is after space removal, tab compression and null insertion.
In this case, the physical size of the new record is allowed to be smaller than that of the record being replaced. Status-key-2 Decimal. Status-key-2 Hex. Illegal file name. File information missing for indexed file. Micro Focus This could indicate the filename. IDX is missing. Indexed structure overflow. Could indicate that you have reached the maximum number of duplicate keys.
Connection to remote system is failing. This can be caused by issuing a read after the end-of-file has been reached during sequential processing. Codes beginning with a '1' are considered "At End" messages, those beginning with a '2' are considered "Invalid Key" messages, File Status Codes beginning with a '3' are considered "Permanent Errors", keys like '4x' are "Logical Errors" and '9x' are "Implementer defined". The input-output statement was successfully executed, but a duplicate key was detected.
A duplicate key exist for at least one alternate key for which duplicates are allowed. Possible causes:. For a READ statement, the key value for the current key is equal to the value of that same key in the next record in the current key of reference. A READ statement was successfully executed, but the length of the record being processed did not conform to the fixed file attributes for that file.
It means the size of the record just read does not agree with the size specified in the program. This does not apply to VSAM sequential files. Sequential files only. A sequential READ statement was attempted and no next logical record existed in the file because the end of file EOF had been reached, or the first READ was attempted on an optional input file that was not present.
A sequential READ statement was attempted for a relative file, and the number of significant digits in the relative record number is greater than the size specified for the relative key data item.
Indicates a sequence error. Prime record key values must be in ascending order. Indicates a duplicate key condition. An attempt has been made to access a record, identified by a record key prime or alternate for indexed file, relative key for relative files , and that record does not exist in the file. File closed with lock - cannot be opened. Record length or key data inconsistency.
File already open - cannot be opened. File not open - cannot be closed. No current record defined for sequential read. Program abandoned at user request. Random read on sequential file. Malformed line-sequential file. Called program not found. End-of-file marker error. Console input or console output open in wrong direction. Attempt to open line-sequential file for I-O. File name too large. Error in variable length count. File size too large.
Record number too large in relative or indexed file. File is closed with lock. Too many locks. Operating system shared file limit exceeded. BirdyF , is dry-run broken for your package specifically, or what happens if you try dry-run for another package?
We would be curious to fix this if dry-run publishing is broken Hopefully you won't be able to publish the package -- that would be a security issue, hehe :. So the problem is coming from my package I suppose. Maybe, it could also be we're running different versions of pub, and that we're on different systems.
Another way to debug this would be to clone this repository, and try to run tests locally. Error on line 21, column 5 of pubspec. Please file new issues instead of commenting on unrelated issues. For general support please consider stackoverflow, or one of the other community forums Skip to content. Star
0コメント