RT014 Too many files open simultaneously. S233 - 10 - IN A USER-SUPPLIED STORAGE RANGE, THE START ADDRESS IS GREATER THAN THE END ADDRESS. S213 - 58 - AN ATTEMPT WAS MADE TO CHANGE THE DSORG OF AN SMS-MANAGED DATA SET TO UNMOVEABLE WHICH IS NOT ALLOWED ON SMS-MANAGED VOLUMES. I'm assuming here the original data was not RECFM VB. http://domcached.com/i-o/i-o-data-error-in-lotus-notes.html
S013 - 84 - AN OPEN MACRO WAS ISSUED FOR AN OPTICAL CHARACTER READER DATASET. Appreciate it and many thanks in advance! RT041 Corrupt index file. When I ran the REXX thru TSO, my data set which was of LRECL 80 FB got converted into FBA 133. read this article
RT016 Too many device files open. RT042 Attempt to write on broken pipe. S013 - 14 - AN OPEN MACRO WAS ISSUED WITH OUTPUT OR OUTIN SPECIFIED. If it was, about the only way to determine a compatible LRECL and BLKSIZE is to find the largest BLKSIZE and then try an LRECL of that value minus 4.
RT028 No space on device. It happened on "mature" script i.e. S001 - 05 - FOR QSAM, A GET WAS ISSUED AFTER END-OF-FILE. S137 - 08 - AN I/O ERROR OCCURRED WHILE POSITIONING THE TAPE IN PREPARATION FOR LABEL PROCESSING.
Regards Top Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... PROCESSING CONTINUES FOR OTHER DCBS OPENED. S0B0 - 10 - INVALID LENGTH (0 OR NEGATIVE FOR ASSIGN LOCATE OR ATTEMPTING TO READ OR WRITE A RECORD, WHICH IS NOT 176 BYTES, IN MOVE MODE). try here Extended file status codes have the following format: 9/nnn where nnn is a binary (COMP-X) number, equivalent to a run-time error number.
S0E0 - AN INVALID OR UNRECOGNIZED PROGRAM INTERRRUPT OCCURRED.POSSIBLE CAUSE- THIS LEVEL OF MVS IS NOT THE CORRECT ONE FOR THE HARDWARE, ESPECIALLY IF THE INTERRUPT CODE IS UNKNOWN. THE SECOND ENQ MACRO DID NOT SPECIFY TEST, USE, OR HAVE IN ITS RET OPERAND. RT138 File closed with lock - cannot be opened. 39/44 RT139 Record length or key data inconsistency. 41 RT141 File already open - cannot be opened. 42 RT142 USUALLY CAUSED BY UNINTENTIONAL BRANCH TO INVALID INSTRUCTION.
S004 - 03 - CONFLICTING ACCESS METHODS SPECIFIED. Continued S002 - 10 - AN INVALID RECORD WAS ENCOUNTERED ON A PUT OPERATION;THE DATASET USES THE TRACK OVERFLOW FEATURE. S013 - 2C - A SEQUENTIAL DATASET USING THE QUEUED ACCESS TECHNIQUE WITH EXCHANGE BUFFERING WAS OPENED FOR INPUT, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0. RT021 File is a directory.
RT023 Illegal or impossible access mode for CLOSE. S0B0 - 08 - INVALID SVA (DOES NOT POINT TO THE BEGINNING OF A SWA PREFIX OR THE SWA PREFIX HAS BEEN DESTROYED). S0E0 - 31 - AN UNSTACKING INTRUCTION WAS ISSUED WHEN THE LINKAGE STACK HAS NO STACK ENTRIES. check over here What was the command you used to perform the recovery?
Anonymous Sign in Create Ask a question Spaces API Connect Appsecdev BPM Blockchain Bluemix CICS Cloud Analytics Cloud marketplace Content Services (ECM) Continuous Testing Courses DB2 LUW DataPower Decision Optimization DevOps S013 - B8 - AN OPEN MACRO WAS ISSUED FOR THE 3890 DOCUMENT PROCESSOR AND DCBHDR WAS NOT SPECIFIED IN THE DCB. S113 - 38 - AN OPEN WAS ISSUED FOR A VSAM DATA SET WITH A DCB, BUT THE VTOC DOES NOT INDICATE THAT IT IS A VSAM DATA SET.
CORRECT THE LABEL PARAMETER.- OPTCD=Q WAS SPECIFIED BUT IS NOT SUPPORTED BY THE SYSTEM.
IF THE REGISTER 15 RETURN CODE IS AVAILABLE, SUPPLY IT IN THE S213 OPERAND FOR MORE SPECIFIC INFORMATION: H ABEND O(S213-RC)POSSIBLE CAUSE:THE DATA SET IS NOT ON THE SPECIFIED VOLUMEDISP = has been run many times before with no change in logic. Its just that there is some corruption with my PDS read. MVSFORUMS.comA Community of and for MVS Professionals FAQ Search Quick Manuals Register Profile Log in to check your private messages Log in I/O Error during read of a PDS !!
S001 - 02 - AN ERROR WAS ENCOUNTERED WHILE ATTEMPTING TO CLOSE THE DATASET. **S001 - 03 - FOR QSAM, AN ERROR WAS ENCOUNTERED THAT COULD NOT BE ACCEPTED. POSSIBLE DOS VOLUME. S10E - SPIE MACRO ERROR. this content S306 - 08 - AN UNCORRECTABLE I/O ERROR OCCURRED WHEN THE CONTROL PROGRAM ATTEMPTED TO SEARCH THE DIRECTORY OF THE LIBRARYCONTAINING THE MODULE, OR THE MODULE IS NOT RE-ENTRANT.
Ewing Wed, 27 Jul 2011 09:04:12 -0700 FBA LRECL 133 BLKSIZE 133 is almost certainly NOT correct. S013 - 44 - AN OPEN MACRO WAS ISSUED FOR A DATASET ON A DIRECT ACCESS DEVICE FOR WHICH CHAINED SCHEDULING WAS SPECIFIED, BUT THE BUFFER CONTROL BLOCK ADDRESS WAS 0. No one in their right mind would create a blocked PDS that is effectively unblocked with one record per block as you would be getting less the 5% effective track utilization Your 2nd problem is to find what not-so-bright programmer or application caused the problem in the first place, as you could fix the problem and have it immediately re-occur when they
RT043 File information missing for indexed file. is it durign the reading phase or it during the writing phase?