IMS-ABENDCODES

'AC' - PROCEDURE DIVISION ENTRY STATEMENT DID NOT MATCH PSB.'AC' - BE SURE THAT THE PGM/PSB IS KNOWN TO THE SYSTEM AS A BMP IF IT'AC' IS A BMP OR TRANSACTION IF IT IS A TRANSACTION.'AD' - SYNC CALL WAS MADE WITH DB PCB WHEN IT SHOULD'AD' HAVE USED I/O PCB.'AD' IF THIS PGM IS GOING TO ACCESS THE MSG QUEUE IT MUST HAVE THE'AD' PARM FOR BATCH PROC "IN=XXX" XXX TRANSACTION NAME.'AI' - DDNAME IN JCL DID NOT MATCH ENTRY STATEMENT FOR'AI' GSAM FILE..'AI' - REGION MAY BE TOO SMALL. (AI ON OUTPUT GSAM)'AI' - VSAM BUFFERS NOT LARGE ENOUGH. IF USING PROC DLIBATCH TRY USING'AI' - DLICHKPT.'AJ' - ON 'ISRT', I WAS USING A QUALIFIED SSA INSTEAD OF'AJ' AN UNQUALIFIED SSA.'AK' - INVALID SSA FIELD NAME: FIELD NAME NOT DEFINED IN THE DBD.'AK' ALSO CHECK: THE PROC STATEMENT IN THE PCB MUST BEGIN IN COL. 16.'AK' ALSO CHECK: IF PSB REFERENCES A SECONDARY INDEX BE SURE THAT THE'AK' PCB DATA LINE ENDS WITH A COMMA AND THAT THERE IS 'X' IN'AK' COL. 72.'AM' - FIRST CHECK IN STG1 TO SEE IF THE TRANS IS DEFINED TO THE SYSTEM'AM' AS INQ=NO. IF YES MEANS INQUIRY ONLY.'AM' HAVE DBA CK PSB - IT COULD HAVE BEEN GEN'D FOR INQUIRY INSTEAD'AM' OF UPDATE'AM' - BE SURE THE FILE NAMES POINT TO THE DATASETS CORRECTLY.'AO' - GSAM CONTROL BLOCK DUMP:'AO' 1. DATASETS ALLOCATED VIA IEFBR14.'AO' 2. DCB'S MISSING IN JCL.'A2' - TXN WOULD BLOW UP ON SECOND CHANGE CALL. HAD TO'A2' INSERT THEN PURGE INSTEAD OF PURGE WITH I/O AREA.'A3' - DESTINATION NOT SET, NO CHANGE CALL ISSUED'A3' NOTE: IF YOU ARE A BMP WITH CHECKPOINT/RESTART ON'A3' FAST PATH DATABASE AND MESSAGE SWITCHING TO'A3' ANOTHER PROGRAM, YOU COULD GET THIS STATUS.'A3' THE CHANGE CALL LOSES THE DESTINATION UPON'A3' TAKING CHECKPOINTS. HAVE TO CODE A CHANGE'A3' CALL AFTER TAKING A CHECKPOINT.'FD' - DEADLOCK OCCURRED, RESTART PROGRAM AND TRY AGAIN'FE' - FSA ERROR, NOT FIELD NAME

'FH' - DEDB IS DOWN, CALL TO DBA TO RESOLVE'FN' - FSA ERROR, FIELD NAME'FR' - FOR BMP - ADD 'NBA=8' AND 'OBA=4' PARMS TO JCL'FR' - FOR MPP - CALL TO DBA TO BFMP UP BUFFER ALLOCATION'FS' - DEDB AREA FULL - (DATA BASE FULL)'FT' - TOO MANY SSAS ON CALL'FW' - WARNING FOR FAST PATH DATABASES, REQUIRE MORE'FW' CSA RESOURCES.'FW' - FOR MPP - ABEND --- NOTIFY DBA'FW' - FOR BMP - TAKE A CHECKPOINT CALL IN ORDER TO RELEASE'FW' RESOURCES FOR FAST PATH DATABASE.'GP' NO PARENTAGE ESTABLISHED.'V1' DLET/REPL DB: SEG LEN NOT WITHIN LIMITS OF DBDGEN'V1' ISRT/LOAD DB: SEG LEN NOT WITHIN LIMITS OF DBDGENAID - TO TURN OFF ABENDAID SUPPLY //ABNLIGNR DD DUMMYA13 - A13-08 REQUESTED FILE SEQUENCE NUMBER IS LESS THAN THAT OF THEA13 - FIRST FILE.A13 - A13-10 REQUESTED FILE SEQUENCE NUMBER IS NOT FOUND. IF YOU AREA13 - READING A FILE YOU NEED TO VERIFY YOU HAVE THE CORRECT LABELA13 - NUMBER. IF YOU ARE WRITTING A FILE THEN YOU HAVE REACHED THEA13 - MAX NUMBER OF TAPES ALLOWED, WHICH IS DETERMINED BY THE VOLA13 - STATEMENT IN THE FIRST STEP THAT WRITES TO THE TAPES. FORA13 - EXAMPLE IF PS020 SAYS VOL=(,,,20) THEN IN PS070 YOU TRY TOA13 - WRITE THE 22 TAPE YOU WILL ABEND WITH THIS CODE. YOU WILL NEEDA13 - TO CHANGE THE VOL STATEMENTS AND RESTART IN THE FIRST STEP THATA13 - WRITES TO THE TAPES.B14 - B14-0C = ATTEMPTED TO UPDATE DIRCTORY OF A PARTITIONED DATASET.B14 - FIX IT BY REALLOCATING PDS WITH MORE DIRCTORY BLOCKS AND SPACE.LD20 - PME ERROR . UNABLE TO OPEN LOAD FILE -LD20 - SUPPLY DCB=(LRECL=...,BLKSIZE=...,RECFM=FBA)NOTES - Q= ABNORMAL CONDITION NUMBERS - POSSIBLE CAUSES.......NOTES -NOTES - (Q) WHAT PRINTER NUMBERS DENOTE FLINT PRINT CENTER PRINTERS?NOTES - 1. PRINTER NUMBERS 49 THRU 56 PRINT IN FLINT, ALL OTHERS ARENOTES - IN TROY.

NOTES - (Q) WHY ARE THE TRANSACTION SCHEDULING DEFAULT PARAMETERS BEINGNOTES - RESET TO ZEROS IN OLSJIM15(IMSTEST) EACH MORNING?NOTES - 1. THE TRANSACTION IS DEFINED TO IMS INCORRECTLY. IT ISNOTES - DEFINED AS A BMP INSTEAD OF A TRANSACTION WHICH CAUSES THENOTES - PARAMETERS TO BE SET TO ZERO.NOTES - (Q) WHAT IS THE DIFFERENCE BETWEEN TAPE AND TAPE9?NOTES - 1. TAPE = SINGLE DENSITY 6250 BYTES PER INCHNOTES - TAPE9 = DUAL DENSITY 1600/6250 BYTES PER INCHNOTES - (Q) HOW CAN A DATASET CHANGE FROM FB TO VB IF IT WAS NOT REALLOCATED?NOTES - 1. A TSO 'COPY' COMMAND IN OPTION 6 WILL REPLACE THE DBCS IN THENOTES - TARGET DATASET WITH THE ATTRIBUTES FROM THE "COPY FROM" DATASET.NOTES - 2. INCORRECT KEY LENGTH IN DBD.NOTES - (Q) "AJ" STATUS CODES :NOTES - 1. ALL SSA'S INCLUDING SSA WITH "D" COMMAND CODE MUST BENOTES - QUALIFIED FOR PATH INSERTS.NOTES - 2. INCORRECT KEY LENGTH IN DBD.NOTES - (Q) APPARENT LOOP DURING RESTART:NOTES - 1. MISSPELLED SAVE AREA NAME FOR CHKPT/XRST CALL.NOTES - 2. SAVE AREA TOO SHORT.NOTES - (Q) PROGRAM SEEMS TO BE WAITING AND WON'T LEAVE VIA ABDUMP,NOTES - AND IS USING ALMOST NO CPU:NOTES - 1. GSAM FILE DUMMIED OR OMITTEDNOTES - (Q) REQUESTED BLOCK NOT AVAILABLE ON AN INSERT TO A PRINTER:NOTES - 1. PRINTER MAY NOT BE CONNECTED IN THE TEST SYSTEM.NOTES - 2. PLACE PRINTER IN 'MFSTEST' MODE.NOTES - (Q) BTS PROGRAM GETS U(4000) WITHOUT GOING THRU ON ERRORNOTES - BLOCK, CO3 ALSO FOLLOWS 4000:NOTES - 1. PCNT TO LARGE.NOTES - 2. BTSIN OPEN ERROR.NOTES - (Q) PROGRAM CODE GETTING OVERLAYED:NOTES - 1. "D" COMMAND CODE USED WHEN IOAREA IS NOT BIG ENOUGH FORNOTES - THE PATH OF SEGMENTS.NOTES - (Q) PGM WHICH RECEIVES DATA FROM PARM STMT IN JCL NOT WORKING:NOTES - 1. PROGRAM COMPILES AS IMS.NOTES - (Q) COMPARE STMTS NOT WORKING WHEN LOOKING AT ALPHA INPUT DATA:NOTES - 1. DATA CREATED AS LOWERCASE.

NOTES - (Q) WHAT IS THE MAXIMUM MESSAGE SIZE ALLOWED PER ISRT TO ANOTES - SCREEN OR PRINTER?NOTES - 1. MAXIMUM MESSAGE LENGTH IS 3800 BYTES.NOTES -NOTES - (Q) WHEN ABENDING A COBOL PGM. IN BTS THROUGH WAASABEND WHY DONOTES - I GET LOGGED OFF TSO?NOTES - 1. WHEN CALLING WAASABEND MUST PASS IT A PARM OF 'DN' TO DUMPNOTES - WITH TASK TERMINATION ONLY. DEFAULT IS 'DS' WHICH LOGS YOUNOTES - OFF TSO. SEE VOL 1-WAASABEND FOR FURTHER DETAILS.NOTES -NOTES - (Q) WHY DO 'HIDDEN' FIELDS SHOW UP ON THE 'O/P' WHEN I USE THE PRINTNOTES - KEY TO PRINT A SCREEN FROM PRODUCTION IMS.NOTES - 1. THE 'PRINTER SOFTWARE' NEEDS TO BE UP GRADED TO A CURRENT RELEASE.NOTES - EXAMPLE FOUND IN PRODUCTION: PRINTER IN CUSTOMER AREA WAS RUNNINGNOTES - RELEASE 4, MOST OTHER PRINTERS RUNNING RELEASE 12.NOTES -NOTES -NOTES - (Q) WITH TWO USERID'S (USERID - USERIDT), HOW COME I CAN'T VIEW JOBSNOTES - SUBMITTED UNDER USERIDT IN IOF?NOTES - 1. IN =I. MAKE SURE THE "USERID" FIELD IS BLANK.NOTES -NOTES - I DISPLAYED A TRANSACTION AND IT WAS SUSPENDED. HOW DO I RESTART?NOTES - CK FOR STOPPED DATABASE - ELSE CMD /DEQ SUSPENDNOTES -NOTES - IEF211 DATASET RESERVATION UNSUCCESSFUL --NOTES - IEF211 MAKE SURE DISP = OLDNOTES - SOMEONE OR SOMETHING ELSE IS USING THE DATASET. TRY AGAINNOTES - USE WHOHASIT FOR THE ELSE SOMEONE/SOMETHINGNOTES -NOTES - (Q) WHY AM I NOT GETTING ALL MY STRUCTURE DATA WRITTEN OUT TONOTES - MY GSAM FILE.NOTES - (A) THE LENGTH OF THE MOVE IS CONTROL BY THE DCB'S IN THE DDNOTES - PORTION OF THE JCL, NOT BY THE LENGTH OF THE STRUCTURE.NOTES - YOU ARE USING ISRT'S INSTEAD OF A WRITE STATMENT.

NOTES -NOTES - TO TURN OFF IPC BROADCAST EDIT YOUR PROFILE(WBLPROF) AND SETNOTES - DATE VALUES TO 99/MM/DD AND SAVE. (NO MORE IPC BROADCASTS)NOTES -PRTR - PRINTER ASSIGMENTS AT FDC ARE PRT49-PRT56 (010892)TPROC - TO USE SYS4.TEST.PROCLIB AND SYS3.CHAMP.TESTPROC -- JCL SHOULD READTPROC - /*JOBPARM R=SA03,PROCLIB=TESTPME - ERROR LD02 LOOK FOR MISSING PME$EOJ MEMBER IN YOUR PME.JOBSETPME - ERROR LD20 LOOK FOR MISSING BLKSIZE IN DCB.R4 - NO RECORDS SELECTED (EASYTREV ONLY).R8 - DATA SETS NOT CATALOGED.B37 - SEE SB37 - OUT OF SPACE.R12 - CONFLICTING DCB'S (WCSGENER ONLY).D100 - ROW NOT FOUND FOR FETCH, UPDATE OR DELETE, OR THE RESULT OF AD100 - QUERY IS AN EMPTY TABLE.D162 - TABLESPACE HAS BEEN PLACED IN CHECK PENDINGD304 - A VALUE WITH DATA TYPE 1 CANNOT BE ASSIGNED TO A HOST VARIABLED304 - BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOSTD304 - VARIABLE BECAUSE THE VALUE IS NOT WITH THE RANGE OF THED304 - HOST VARIABLE.D304 - WHEN A FIELD IS DEFINED TO DB2 IT IS POSSIBLE TO GIVE THED304 - FIELD VERTAIN VALUE LIMITS. THE VALUE USED IN THIS UPDATED304 - CALL IS NOT WITHIN THOSE LIMITS.D625 - THE TABLE IS NOT COMPLETELY DEFINED BY THE DBA GROUP.D007 - STATEMENT CONTAINS AN ILLEGAL CHARACTER.D010 - THE STRING CONSTANT IS NOT TERMINATEDD101 - THE STATEMENT IS TOO LONG OR TOO COMPLEXD102 - THE LENGTH OF THE STRING CONSTANT IS GREATER THAN 254 CHARACTERSD103 - AN INVALID NUMERIC LITERALD120 - A WHERE CLAUSE OR SET CLAUSE INCLUDES A COLUMN FUNCTION OR AD120 - WHERE CLAUSE REFERENCES A COLUMN WHICH IS DERIVED FROM AD120 - COLUMN FUNCTION OR EXPRESSION IN A VIEW DEFINITION.D121 - THE COLUMN IS IDENTIFIED MORE THAN ONCE IN AN INSERT OR UPDATED129 - THE STATEMENT CONTAINS TOO MANY TABLE NAMESD161 - THE INSERT OR UPDATE IS NOT ALLOWED BECAUSE A RESULTING ROW

D161 - DOES NOT SATISFY THE VIEW DEFINITION.D164 - YOU DO NOT HAVE PRIVILEGES TO CREATE A VIEW WITH QUALIFICATIOND181 - THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALIDD181 - DATETIME VALUE.D204 - TABLE NOT FOUND.D208 - THE ORDER BY CLAUSE IS INVALID BECAUSE A COLUMN NAME IS NOTD208 - PART OF THE RESULT TABLE.D401 - THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOTD401 - COMPARABLE.D504 - THE CURSOR NAME IS NOT DEFINED.D507 - THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT ISD507 - NOT OPEN.D508 - THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT ISD508 - NOT POSITIONED ON A ROW.D509 - THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOTD509 - THE SAME TABLE DESIGNNATED BY THE CURSOR.D612 - A DUPLICATE COLUMN NAME IS IN THE STATEMENTD803 - AN INSERTED OR UPDATED BALUE IS INVALID BECAUSE THE INDEXD803 - CONSTRAINS COLUMNS OF THE TABLE SUCH THAT NO TWO ROWS CAND803 - CONTAIN DUPLICATE VALUES IN THOSE COLUMNS.D811 - THE RESULT OF A SELECT OR SUB-QUERY RETURNED MORE THAN 1 ROW.D818 - THE LOAD MODULE TIMESTAMP AND BIND TIMESTAMP DO NOT MATCH.D818 - RE-BIND THE PLAN.D922 - AUTHORIZATION TO THE TABLE OR PLAN DO NOT ALLOW YOU TO PERFORMD922 - THIS FUNCTION.SA13 - SEE A13SB0A - NOT ENOUGH REGION SIZE--CHANGE OR ADD TO JOB CARD(512K INCR)SB37 - OUT OF SPACE.SB37 - INFO: SHOULD YOU RUN OUT OF SPACE ON THE PACK AND IT IS A GSAMSB37 - FILE AND A RESTART IS NECESSARYSB37 - ADD A VOL=SER=XXXXXX (XXXX IS ANOTHER PACK SER NUMBER INSB37 - YOUR POOL).THIS WILL CAUSE YOUR DATASET TO SPAN OVER TOSB37 - ANOTHER PACK.SB37 - EX: UNIT=(SYSDA,2),

SB37 - VOL=SER=(NFDPDI,NFDPDF)SB37 - CAN ALSO CHANGE THE SPACE REQUIREMENTS(SECONDARY ALLOC ONLY)SC03 - CONTROL PGM UNABLE TO CLOSE DATASET AT TERMINATION OF TASK.SC03 - DATASET THEREFORE LEFT OPEN, REQUIRES CLOSING.SC03 - CAN BE CAUSED BY PGM OVERLAYING A DCB, OR BY THE PGM BEINGSC03 - DELETED OR ISSUED AN XCTL MACRO CAUSING THE SYSTEM TO REUSESC03 - THE PGM STORAGE CONTAINING THE DCB.SC03 - PLEASE CONTACT ABEND-AID ADMINISTRATOR.SC03 - DID NOT MOVE ZERO TO W-COCS903-PRCDR-CNTR AND CALL COCSS03SC03 - AT THE END OF A COBOLII IMS PROGRAM.SD37 - LIBRARY FULLSD37 - D37-04 DSN OPENED AS OUTPUT USED ALL THE PRIMARY SPACE ANDSD37 - NO SECONDARY SPACE WAS REQUESTED.SE37 - PDS OUT OF SPACE(SUGGEST COMPRESS FIRST THAN REALLOC)SPND - THIS USER ABEND BASICALLY MEANS THAT ONE OF THE APPLICATIONSPND - DATA BASES IN YOUR PSB IS STOPPED. WHEN YOUR APPLICATIONSPND - GOES AFTER IT, SOME SORT OF SUBTASK ABEND OCCURS.SPND - BEFORE CURRENT RELEASE OF IMS THE PGM WOULD ABEND ON A U458.SPND - MEANS THAT THE PGM WILL RUN UNTIL A DATABASE THAT IS NEEDED IS NOTSPND - AVAILABLE.SPND - ENSURE THAT ALL THE NEEDED DATABASE ARE UP AND RUNNING.SPND - U458 -- DB USED BY A BMP IS STOPPED.S0C1 - IF IMS PROGRAM CHECK THE CHECKPOINT I/O AND SAVE LENGTHS.S0C1 - MISSING OR MISSPELLED DDNAME. CHECK SYSTEM MESSAGE FROM ABENDINGS0C1 STEP.S0C1 - TRYING TO READ A FILE WHICH WAS NOT OPENED.S0C1 - INCOMPLETE DCB FOR SORTIN.S0C1 - TRYING EXECUTE AN IMS PROGRAM AS A NON IMS PROGRAM CK EXEC CARDS0C1 - TRYING TO WRITE AN UNOPENED DATASET.S0C1 - TRYING TO WRITE A DATASET THAT HAD BEEN CLOSED.S0C1 - BRANCHED TO A DATA AREA AND TRIED TO USE DATA AS AN INSTRUCTION.S0C1 - SUBROUTINE IS MISSING.S0C1 - POSSIBLE WORKING-STORAGE TABLE OVERFLOW, PERFORMED GREATER THAN

S0C1 - OCCURS STATEMENT.S0C1 - IF YOUR COBOL PGM USES SUB PGMS AND THE SUB PGMS ARE LINKED WITHS0C1 - RENT AND RES AND THE DRIVER IS LINKED WITHOUT RENT AND RES THENS0C1 - RECOMPILE ALL PGMS THAT ARE NECESSARY WITH THE SAME OPTIONS.S0C1 - USE E.F.3.1 ON THE OBJ LIBRARY AND SELECT THE MEMBER WITH A "N"S0C1 - TO SEE HOW THE MBRS WHERE LINKED. FIELDS NAME A/R(ANY) OR A/R(24).S0C3 - CONTROL PGM UNABLE TO CLOSE DATASET AT TERMINATION OF TASK.S0C3 - DATASET THEREFORE LEFT OPEN, REQUIRES CLOSING.S0C3 - CAN BE CAUSED BY PGM OVERLAYING A DCB, OR BY THE PGM BEINGS0C3 - DELETED OR ISSUED AN XCTL MACRO CAUSING THE SYSTEM TO REUSES0C3 - THE PGM STORAGE CONTAINING THE DCB.S0C3 - PLEASE CONTACT ABEND-AID ADMINISTRATOR.S0C3 - DID NOT MOVE ZERO TO W-COCSS03-PRCDR-CNTR AND CALL COCSS03S0C3 - AT THE END OF A COBOLII IMS PROGRAM.S0C4 - MAY NEED TO INCREASE REGIONS0C4 - FOR IMS STEP, TRY ADDING PARM "REG=4M," TO IMSBATCH CARDS0C4 - VERIFY DCB'SS0C4 - IF NEW IMS PROGRAM OR ADDED A D/B MAKE SURE PSB WAS GEN'DS0C4 - IF PGM IS BEING COMPILED THRU CHAMP BE SURE YOU HAVE THE RIGHTS0C4 - DATASET TYPE FOR THE COMPILE PROCEDURE. (EG: IMS VS NON-IMS;S0C4 - CB2PBEX VS CB2SBEX)S0C4 - MISSING OR INCORRECT DD STATEMENT.S0C4 - IF CALLING CHECKPOINT RESTART, CHECK TO SEE IF PREVIOUS CALL TOS0C4 - COCSS03 WAS MADE WITH A PRCDR-CNTR = 0. PRCDR-CNTR SHOULD ONLYS0C4 - = 0 FOR FINAL CALL.S0C4 - WHEN USING SDB BLKSIZE=0000, BE SURE TO USE DSORG=PSS0C4 - IF CODE IS COBOL II, ENSURE FD HAS FOLLOWING: ACTUAL LRECL INS0C4 - RECORD CONTAINS CLAUSE, CORRECT RECORDING MODE, AND A GOOD DATAS0C4 - RECORD STATEMENT.S0C5 - RECORDING MODE NOT PRESENT IN FD.S0C5 - READING OR WRITING A CLOSED FILE OR PAST EOF.

S0C5 - CLOSING A FILE THAT WAS NEVER OPENED.S0C5 - USING COBOL SORT AND TRYING TO MOVE FD INSTEAD OF SD.S0C6 - REFERENCED AN I/O AREA BEFORE READ, WRITE, OR OPEN.S0C6 - TRIED TO WRITE TO FILE OPENED AS INPUT.S0C6 - DECIMAL MULTIPLIER OR DIVISOR EXCEEDS 15 DIGITS.S0C6 - ADDRESS, DATA OR INSTRUCTION ON IMPROPER BOUNDARY.S0C6 - SUBSCRIPT EXCEEDED LIMIT AND OVERLAID INSTRUCTION.S0C6 - MISSPELLED DD NAME.S0C7 - DATA EXCEPTIONS0C7 - WATCH FOR EXCEEDING TABLE BOUNDARIESS0C7 - AT END STATEMENT FOLLOWED BY CONDITIONAL STATEMENTS0C9 - ARITHMETIC ERROR IN PROGRAMS0CA - DECIMAL OVERFLOW - DESTINATION TOO SMALL FOR RESULTS0CB - DECIMAL DIVIDE EXCEPTIONS0CB - A QUOTIENT EXCEEDS THE SPECIFIED DATA FIELD SIZE.S0F1 - RECORD DESCRIBED AS WRONG LENGTHS0F2 - ATTEMPT TO WRITE A VARIABLE LENGTH FILE WHICH HAS A BLOCKS0F2 CONTAINS 0 RECORDS IN THE FD AND DCB PARAMETERS. THIS ONLY WORKSS0F2 ON FIXED LENGTH.S0F3 - DISK I/O FAILURE - CALL PLANO!!!!S001 - I/O ERROR READING INPUT FILES001 - IF USING TAPE, THE TAPE MAY BE BAD, TRY A NEW ONES001 - TRIED TO READ PAST END OF FILES001 - TRIED TO WRITE ON AN INPUT FILES001 - INCORRECT USE OF LABEL PARAMETER IN COBOL PGMS001 - OUT OF SPACE IN A PDSS001 - INPUT FILE DESCRIBED INCORRECTLY, LENGTH ERRORS001 - ATTEMPT TO OPEN AN OPENED FILE OR CLOSE A CLOSED FILES002 - RECORD IS GREATER THAN 32,768 BYTES, EXCEEDS MAXIMUM TRACK LGTHS002 - OR STATED BLOCK SIZE................S002 - WHEN READING UNLOAD TAPES THE PREFIX MAY NOT AGREE W/UNLOAD TAPES002 - DCB HAD THE WRONG BLOCKSIZES002 - WRONG RECORD FORMAT SPECIFIED IN JCLS002 - FD AND 01 IN COBOL PGM DO NOT AGREE ON RECORD LENGTHS013 - INFORMATION DOESN'T MATCH THAT OF DATA SET IN DD STATEMENT.S013 - S013-18 PDS MEMBER TO BE OPENED DOES NOT EXIST.S013 - S013-20 CHECK RECFM AGAINST BLKSIZE AND LRECL ETC..S013 - LOOK IN LOG FILE FOR S013-XX THEN LOOK AT MSGS CODE BOOK FORS013 - IEC141I.. THE ABOVE XX IS THE GOOD REASON FOR THE ABEND.S013 - CHECK IF THERE IS A RECORD CONTAINS CLAUSE IN THE FD.S052 - MODULE NOT FOUND - PROBABLY NOT IN TEST LIBRARY.

S1FB - DATA SET NAME IN JCL DOES NOT MATCH DATA SET NAME IN LABELS106 - CSV011 & IEA995I FETCH FAILED FOR MODULE A0770.S106 - 8.1 COMP LINKED, BUT 8.2 DIDN'T. FIXED PROBLEM BYS106 - BUMPING UP REGION IN JCL FOR A0770.S106 - ERROR RECEIVED TRYING TO BTS TEST A LARGE COBOL PROGRAM, FIXEDS106 - BY LINKING PGM WITH "RESIDENT" COMPILE OPTION.S106 - REGEN PSB FOR THE VERSION YOU ARE TESTING IN.S106 - TEST REGIONS MAY HAVE TO BE RECYCLED AFTER TESTLIB MAINT.S117 - IMS CHECK POINT PROBLEM. IF YOU WERE NOT TRYING TO RESTART THES117 - PROGRAM THEN RESET THE IMS CHECK POINT IN IMSCHKPT.S122 - OPERATOR CANCELLED JOB.S137 - ERROR OCCURED AT AN END-OF-VOLUME ON A MAGNETIC TAPE.S137 - RESTART JOB. FOR MORE INFO SEE IEC215S137 - 714-0C I/O ERROR OCCURED WRITING A TAPE MARK. RESTART JOBS200 - FILLED OUT BUFNO INCORRECTLY.S200 - BUFFERS FILLED CORES213 - 04 VOL=SER DOES NOT MATCH WHAT IS ON THE TAPES213 - BAD DISP= FOR TAPES213 - DATA SET WAS CATALOGED, BUT HAS BEEN DELETEDS213 - IEC143I 213-30: ATTEMPTING TO UPDATE TWO MEMBERS OF SAME PDSS213 - INCORRECT SPELLING OF DSNAME.S214 - INCORRECT DSPS214 - TAPE POSITIONING ERRORS222 - OPERATOR CANCELLEDS237 - BAD OUTPUT.S237 - 04,BLKCNT IN DCB DOES NOT MATCH BLKCNT IN TRLR REC.S237 - 08,HDR LBL DOES NOT MATCH THAT IN THE SECOND REEL. VERIFYS237 CORRECT VOLUME OR DSNAME WERE SPECIFIED.S237 - INCORRECT VOLSER.S237 - INCORRECT LABEL.S273 - AN ERROR WAS DETECTED WHILE REPOSITIONING A GSAM DATA SETS273 - DURING AN XRST CALL.S273 - BAD O/P (GENERAL).S30A - MISSING A BLOCKSIZE ON AN OUTPUT DISK DATA SET.S304 - MISSING SORTLIB DD CARDS304 - I/O FAILURE - CALL PLANO!!!S322 - JOB STEP TOOK LONGER THAN TIME SPECIFIED.S322 - RUN IN CLASS WITH MORE TIME ALLOWANCE (LIKE 'X')S337 - TRIED TO READ PAST END OF FILES337 - TRIED TO WRITE ON TAPE DEFINED AS INPUTS400 - SYSTEM CONTROL BLOCK OVERLAID (DCB) - SEE S0C1

S402 - UNAUTHORIZED ATTEMPT TO USE IMS.S402 - THE REGION WAS PROBABLY TAKEN DOWN WHILE PROCESSINGS413 - MISSING DCB INFORMATION.S413 - HAD DISP=NEW INSTEAD OF SHRS413 - RECFM MISSINGS413 - ERROR DURING INPUT INSTRUCTION.S413 - INPUT, SPECIFIED BUT NO SERIAL NUMBER FOR SER IN DD; I/OS413 - ERROR IN TAPE POSITIONING OR LABEL PROCESSING; COULD NOTS413 - MOUNT ON DEVICE; MORE DEVICES ALLOCATED THAN VOLUMES;S413 -S413 - IF OUTPUT FILE IS TO TAPEC, USE THE FOLLOWING EXAMPLE TOS413 - CODE A TAPE VOL=SER OVERRIDE IN YOUR JOB:S413 -S413 - //NPS030.P829015B DD DISP=(MOD,CATLG,KEEP),S413 - // VOL=SER=(XNNNN1,XNNNN2,..ETC)S413 -S413 - 1C -(FROM EXPERIENCE)IF THE DATASET IS GSAM AND AN EDIT IS DONE,S413 - CHECKPOINT/RESTART WILL NOT BE ABLE TO REPOSITION IN THE FILES413 - ALSO CHKPT/REST WILL NOT SUPPORT CONCATENATED DATASETS.S413 -S413 - 1C -(FROM THE BOOK)AN OPEN MACRO INSTRUCTION WAS ISSUED FOR A DATA SET,S413 - BUT VOLUME SEQUENCE NUMBER ON THE ASSOCIATED DD STATEMENT WAS GREATERS413 - THAN THE NUMBER OF VOLUMES CONTAINING THE DATA SET(IEC145I)S422 - JOB OVERFLOWS QUEUE. TOO MANY STEPS IN JCLS430 - GENPSB FAILED DUE TO LACK OF CMPAT=YES IN PROD PSB SOURCE. CORRECTS430 - PROD PSB SOURCE AND REGEN FOR PROPER DEFINITION.S513 - VOLUME SER WAS INCORRECT.S522 - ALL OF THE TASKS IN A JOB STEP WERE IN AN SVC WAIT STATE FOR THES522 - TIME SPECIFIED IN THE JWT PARAMTER.S606 - NOT ENOUGH MAIN STORAGE WAS AVAILABLE. REDUCE REGION PARAMETER.S613 - I/O ERROR IN LABEL PROCESSING. TRY USING SAME DRIVE THAT THES613 - TAPE WAS ORIGINALLY CREATED ON.S613 - DCB MISSING.S613 - TAPE POSITIONING ERRORS613 - SEE S413S622 - TSO SESSION WAS CANCELEDS637 - I/O ERROR IN WRITING TAPE MARK.

S637 - BAD TAPE DRIVE.S637 - TRY TO RE-RUN THE JOB.S637 - RC=2C I/O ERROR WHILE REWINDING TAPE TO VERIFY LABEL (RESUBMIT JOB)S706 - PGM IS MARKED AS NON-EXECUTABLE. THE PGM DID NOT LINKS713 - MAG TAPE WAS MOUNTED AS A SCRATCH TAPE BUT THE RETENTION PERIODS713 - HAD NOT YET EXPIRED.S714 - I/O ERROR WRITING LABELS722 - SYSPRINT LINES EXCEEDEDS737 - ERROR OCCURRED AT END OF VOLUME DURING ALLOCATION OF A SECONDARYS737 - QUANTITY OF DIRECT ACCESS STORAGE. MESSAGE IEC027I GIVES MORES737 - INFORMATION ON WHICH DD RECEIVED THE ERROR.S737 - BE SURE ALL THE DATASETS EXIST FOR CONCATENATED FILES.S80A - PROGRAM REGION SIZE IS TO SMALL.S80A - IF YOU ARE CALLING A SUB-PROGRAM OR UTILITY, BE SURE THES80A - MODULE IS BEING LOADED INTO THE SAME ADDRESS SPACE EVERYTIME.S80A - (I.E. IF YOU ARE CALLING WAASDATE, BE SURE THE W-DOUBLE FIELDS80A - IS ONLY INITIALIZED ONCE. THE FIRST CALL PLACES THE LOAD ADDRS80A - INTO THE 2ND BYTE AND THAT ADDRESS IS REUSED.)S800 - TRIED TO OPEN A FILE THAT DID NOT HAVE A DDS804 - PROGRAM EXCEEDED REGION SIZE.S804 - NOT ENOUGH MAIN STORAGE AVAILABLE.S806 - PROGRAM NOT FOUND ON LIBRARY YOU ARE USING. CHECK JCL FOR LIB.S806 - IF PROGRAM NOT FOUND-IS IT A GSAM FILE NAME? PSB IS NOT CORRECTS806 - IF LOG MESSAGE IS PREFIXED BY A CSV--- NUMBER CHECK GSAM....S806 - CHECK SETOOLS FOR GSAMCHK TO SEE IF ON FILES806 - CALLING A FORTRAN PROGRAM FROM COBOL NEED TO INITIALIZES806 THE FORTRAN ENVIRONMENT BY CALLING COCSFES806 - PSB USES GSAM FILES - PSB MUST BE IN PSBLIB AND ACBLIB/DCBLIBS806 - NOT ENOUGH CORE AVAILABLE.S813 - DATA SET NAME IN JCL DOES NOT MATCH DATA SET NAME IN LABELS837 - I/O ERROR READING OR WRITING JFCB FROM OR ONTO DIRECT ACCESS;S837 - 08 JCL DID NOT ALLOW FOR ENOUGH OUTPUT VOLUMS - VOL=(,,,99)S837 DEFAULT IS AS IF CODED - VOL=(,,,5)S837 IF YOU KNOW THAT MORE THAT 5 REELS OF OUTPUT IS OK THEN CODE IN YOUR

S837 OUTPUT DD RECORD VOL=(,,,XX). XX= MAX NUMBER OF OUTPUTS EXPECTED OR 99.S878 - INCREASE REGION SIZE ON JOB CARD ORS878 - ENDING FOR MORE REGION THAN AVAILABLE OR REGION LENGTH WAS NEGATS878 - INCREASE SORTWORK SPACE AND MAKE IT CONTIGUOUSS913 - SECURITY VIOLATION (ACF2)S913 - 913-0C ON MSTR CATALOG CHECK JCL FOR A DD RECORD THAT MIGHTS913 - HAVE DSN=DUMMYSECG - CICS ABEND CODE - SECURITY ERROR ON TRANSACTIONU002 - TEST HAS TERMINATED AND HAS FORCED TERMINATION OF ALL ACTIVEU002 - MESSAGE REGIONS AND BATCH MESSAGE REGIONS.U002 - AFTER OPERATIONS HAS RESTARTED THE REGIONS, RESUBMIT USING CKPT.U012 - WHEN USING SYSIN CARDS, YOU CANNOT HAVE COMMENT CARDS WITHINU012 - SYSIN CARDS. REMOVE THE COMMENTS AND P=XCE THEM ELSEWHERE.U016 - WHEN USING WAAPDSUT, THERE ARE MAJOR ERRORS IN THE CONTROL CARDSU016 - CONCAT. DATA SETS ON A SORT. FIRST DATA SET DOES NOT CONTAIN THEU016 - LARGEST BLOCKSIZE.U016 - JOB REQUIRES MORE SPACE TO EXECUTE. ADD AMOUNT OF CYL ONU016 - EXECUTE STATEMENT AFTER PARM. EXAMPLE: CYL=50.U016 - SYSIN * ON A SORT MAY HAVE TOO MANY ENTRIES.U016 - MAY BE SORTING BEYOND REC LENGTH WHEN WORKING WITH VAR RECORDS.U047 - NO DATA BASE AUTHORIZATION.U049 - CALL TO DBA GROUP TO BUMP UP BUFFER ALLOCATION.U069 - ERROR FOR FAST PATH DATABASES CHECK R15 FOR RETURN CODE.U069 - RC 4 = RECURSIVE ENTRY TO INTERREGION COMM (IRC) OCCURREDU069 - RC 8 = F/P WAS UNAVAILABLE AND A F/P CALL WAS DETECTEDU069 - NOTIFY DBA REPRESENTITIVE FOR CORRECTION.U080 - ACF2 ON A DATASET - CHECK LOG IN EXECUTIONU080 - WHEN TESTING WITH 'DLICHKPT' THE DD NAMES FOR YOUR DATABASE MAYU080 - BE INCORRECT. CHECK THE PSBLIB.U084 - PL/I ERROR ON-CODE; SIGNIFIES UNDEFINED FILE CONDITION WASU084 - RAISED WHEN THERE WAS AN ATTEMPT TO OPEN A FILE FOR WHICHU084 - NO DD STATEMENT EXISTS IN JCL JOBSTREAM.U089 - RESTART-- EVERYTHING.U100 - WRONG USER CODE GENERATED BY PROGRAM. CHECK PROGRAM

FOR PROBLEMU100 - FIX IT AND CHANGE USER CODE TO A CORRECT PROGRAM GENERATED CODE.U102 - CHECKPOINT NOT FOUND ON RESTARTU102 - GO INTO IMSCHKPT, AND SET CHECKPOINT COUNTER TO ZERO IF YOUU102 REALLY DON'T CARE TO RESTARTU102 - TO RESTART >>>>>>>>>>DO NOT CHANGE JOB NAME ON RESTART<<<<<<<<<<U102 - MAYBE THE CHECKPOINT RECORD GOT DELETED BECAUSE YOU DID NOTU102 - TRY AND RESTART IMMEDIATELY. YOUR RESTART RECORD WAS ROLLED OFFU102 - THE RESTART FILE.U102 - OPERATOR STARTED WRONG LOG TAPE.U102 - ENSURE THAT THE MBR= IN BOTH DLICHKPT STEPS ARE THE SAME.U103 - CHECKPOINT SAVE AREA LENGTH IS 0 OR NEGATIVE.U134 - DEPENDANT REGION ISSUED AN IDENTIFY REQUEST WHEN CONTROL REGIONU134 - SHUTDOWN WAS IN PROGRESS. (IMS TEST IS IN PROCESS OF COMINGU134 - DOWN).U205 - ERROR OCCURED DURING A FORM OF FREEMAIN MACRO INSTRUCTION.U205 - NO REAL STORAGE AVAILABLE FOR A REQUEST. TRY JOB AGAINU205 - SAME ERROR CALL SYSTEMS GROUP.U222 - CANCELLED BY OPERATOR.U240 - THE EXECUTION (CPU TIME) ALLOTTED FOR A TRANSACTION HASU240 - BEEN EXCEEDED. PROBABLY IN A LOOP.U242 - INCORRECT GSAM, DATA COUNT TO LARGE.U242 - SPECIFY DIRCA=ON BMP.U250 - ONE OR MORE DATASETS NOT CLOSED AT THE END OF THE PROGRAM.U259 - CHECK THE AMODE DATA IN THE LINKAGE EDITOR OUTPUTU259 - SHOULD BE (24) AMODE IF NOT SEEK HELP.U260 - PCNT = 0U260 - IF COBOL PGM AND ON A OPEN STMT RECOMMEND DO NOT UES PCNT OPTIONU260 - AND REMOVE ANY COMMAS IN THE STMT.U261 - ADD 3 CHAMP LINK CONTROL STATEMENTS TO COBOL PROGRAMU261 - * STARTCTL:U261 - * LINKB4: ENTRY DLITCBLU261 - * ENDCTL:U261 - ONE OF THE PARMAMETERS PASSED IN A DL/I CALL FROM THE APPLICATIONU261 - PROGRAM TO IMS/VS IS INVALID. IT EITHER EXCEEDS OBJ MACH SIZE,DOES NOT

U261 - MEET ALIGNMENT REQUIREMENTS, OR VIOLATES STORAGE PROTECTION BOUNDSU261 - POSSIBLE PROBLEM CAN BE THAT A POINTER IS BEING USED TO POINT TOU261 - DB SEGMENT BUT WAS NEVER SET TO AN ADDRESS.U261 - I/O AREA NAME OR SSA NOT DECLARED.U261 - PCNT TO LARGEU261 - MISSPELLED FUNCTION CODEU261 - PCNT DECLARED AS FIXED BIN(15) RATHER THAN 31.U261 - PCBNAME DOES NOT HAVE "P" AT END.U261 - NO CMPAT=YES FOR BATCH.U261 - LEVEL NBR MISSING FROM FIELD IN STRUCTURE.U261 - PROGRAM NOT LINKED AS AN 'IMS' PROGRAM.U262 - BMP IGNORED A 'XD' STATUS FROM CHECKPOINT, WHICH MEANS THATU262 - THE IMS SYSTEM WAS UNDERGOING A CHECKPOINT FREEZE OR SHUTDOWN.U271 - INCREASE CHECK POINT RESTART LIMITSU271 - POSSIBLE I/O ERROR ON GSAM FILEU273 - COULD NOT PROCESS CHECKPOINT FILE. EITHER THE FILE IS BAD, ORU273 - IS NOT FOUND.U322 - CPU TIME LIMIT EXCEEDEDU328 - PSB NOT DEFINEDU402 - BAD IMS CALL LISTU402 - TP PCB MISSING IN PSBU428 - #IMS STATEMENT DOES NOT MATCH PSB OR PGM DOES NOT HAVE A PSBU428 - PROGRAM NOT DEFINED TO THE SYSTEMU428 - MAKE SURE PROGRAM WAS DEFINED TO THE SYSTEM(NUCREQ)U430 - IS A RESULT OF TOO SMALL OF A REGION OR NO REGION SUPPLIED.U430 - DFS0430 AND DFS0432 MESSAGES ARE ABOUT VSAM BUFFER POOLSU430 - TO CORRECT - SUPPLY REGION RECORD ON JOB CARD OF 1024 OR GTR.U430 - TRY INCREASING THE SIZE OF THE REGION PARAMETER.U452 - TRANSACTION STOPPEDU452 - TRANACTION STOPPEDU454 - PGM STARTED AFTER A SHUTDOWN CHECKPOINT HAD ALREADY STOPPEDU454 - ALL OTHER REGIONS. (IMS IS DOWN).U456 - PROGRAM/TRANSACTION IS STOPPED OR DCB LIBRARY TOOK ANU456 - EXTENT, CALL DBA FOR POINTER CHANGE TO NEW EXTENT AREA.U456 - PSB NOT FOUND FOR PROGRAM.U456 - LOOK AT TWDDB.OLSJIM15.PSBLIB(MEMBER) IF NOT THERE PROBLEMU456 - IN IOF LOOK AT OLSJIM15(IMSTEST) THAT IS RUNNING IN THE

(6)HARDCPY1U456 - IF ZIP PSB, MUST BE IN DCBLIB.U456 - THE PSB IN QUESTION MAY BE STOPPED BY A PRIOR PGM FAILUREU456 - IF DOPT , CN NOT BE IN ACBLIB ... ONLY IN DBDLIB.U456 - PSB STOPPEDU456 - PROGRAM WAS STOPPED WHEN EXECUTING.U457 - PSB WAS SCHEDULED IN ANOTHER REGION.U457 - PSB WAS SCHEDULED IN ANOTHER REGION.U458 - DB USED BY A BMP IS STOPPED.U474 - IMS TAKEN DOWN WHEN PROGRAM EXECUTING.U474 - '/STOP REGION N ABDUMP' WAS USED TO CANCEL JOBU476 - #IMS STMT DOES NOT MATCH PSB OR DLI CALL ARGUMENTS COUNT WRONGU476 - DLI CALL ARGUMENTS NOT IN CORRECT ORDER.U476 - MAY NEED TO ADD LINKB4 CARDS FOR CHAMP 3.1 COMPILESU476 - A DL/I CALL DOES NOT INCLUDE A VALID PCB ADDRESS.U476 - POSSIBLE CAUSE IS THAT NUMBER OF PCBS IN PSB DO NOT MATCHU476 - THE #IMS STATMENT IN THE PROGRAM. IF THEY DO, ALSO CHECK IFU476 - DBA ADDED A TP DEFINITION IN THE PSB GEN. IF SO, ANOTHER TPPCBU476 - MUST BE ADDED TO THE PROGRAM #IMS STATEMENT.U476 - IF YOU ARE MAKING A DLI CALL FROM A SUBPROGRAM, MAKE SUREU476 - THE "USING" LIST OF ARGUMENTS IN THE MAIN PROGRAM'S CALLU476 - STATEMENT MATCHES THE "USING" LIST IN THE SUBPROGRAM'S ENTRYU476 - STATEMENTU476 - CHECK LANGUAGE TYPE IN PSBU476 - CMPAT = YES FOR BATCH ONLYU476 - PSB CHGED TO ADD GSAM D/B,BUT JCL/PGM NOT CHGED. ABENDS AT CHKPTU476 - MUST NOT HAVE>CMPAT=YES FOR TRANSACTIONU476 - INVALID DB PCB NAME.U476 - DCB'S MISSING ON GSAM D/B.U476 - NBR OF PCBS IN PSB DOES NOT AGREE WITH #IMS IN PROGRAMU476 - INVALID FUNCTION CODE.U476 - PSB ADDRESS NOT ESTABLISHED (I.E. GSAM PTR)U476 - NO LEVEL NBRS ON THE ELEMENT FIELD NAMES IN THE STRUCTURE.U476 - IF PROGRAM IS COBOL CONSIDER THE FOLLOWING. SEE THAT THE DATA:U476 - CONTENT IN THE LINKAGE SECTION IS IN LINE WITH THE -PSB- ANDU476 - CONTENT IN THE ENTRY SECTION IS IN LINE WITH THE -PSB-U476 - ENTRY STATEMENT DOES NOT MATCH PSBU476 - MAKING A CALL TO A DB NOT DEFINED IN THE ENTRYU476 - STATEMENT OR PSB. (EX. SECONDARY INDEX DB)

U476 - ENSURE CALL HAS A DATABASE POINTER NAMEU476 - PROGRAM WAS NOT COMPILED AS AN IMS PROGRAM,U476 - RECOMPILE AND TRY AGAIN.U476 - IF PROGRAM IS COBOL AND COMPILED IN CHAMP, MAKE SURE DSU477 - IMS BMP DOING GETMAINS FOR MORE SPACE DURING EXECTION, ABENDSU477 - WHEN SPACE NOT AVAILABLE. JUST HAVING PROGRAM RESTARTED MAYU477 - SOLVE YOUR PROBLEM.U499 - MAXIMUM INSERT CALL COUNT EXCEEDED. A "A7" STATUS IS RETURNEDU499 - CHECK APP. PGM AND MAKE SURE IT RECOGNIZES A7 OR INCREASE THEU499 - THE MAX. INSERT COUNT SPECIFIED IN THE TRANSACT MACRO AT SYSGEN.U502 - START TRANSACTION AND PROGRAM AND TRY AGAIN.U502 - WAASABND WAS CALLED WITH ABEND CODE WITHU502 - PIC S9(04) COMP AND IT SHOULD HAVE BEENU502 - PIC S9(09) COMPU513 - IF ISRTING A MSG TO A PRINTER INCLUDE A OUTBUF=9000 ON YOURU513 - ./D CARD WITHIN YOUR BTS CONTROL CARDS. BE SURE TO USE THEU513 - "MDL" OPTION WITH "P1" OR "P2" IF YOU ARE NOT USING MFS ORU513 - "TYPE=SCS1" IF YOU ARE USING MFS FOR THIS MSG.U551 - GSAM PCBS WERE PRESENT BUT DEPENDENT REGION IS NOT A BMP.U551 - CHECK YOUR PSB, PROBABLY GENNED AS BMP. DBA MUST REDO THEU551 - PSB.U616 - I/O AREA LGTH TOO SMALL, ABEND AT XRST CALL.U616 - LOG DATASETS ARE FULL, INCREASE CHECKPOINT LIMIT.U662 - FIRST POSITIONAL VALUE IN PARM FIELD IS INVALID. TRIED TO USEU662 - EXEC PGM=A0770,PARM=ISASIZE(4K),R) IN JCL.U688 - IMS DOWN WHEN JOB STARTED, OR YOU ARE SUBMITTING UNDER SYTEM 'N'U688 - AND THE JOB NEEDS TO RUN UNDER SYSTEM '7' OR VICE VERSA.U688 - HAVE OPERATIONS BRING UP TEST IMS.U688 - OPERATOR CANCELLED IN RESPONSE TO MESSAGE DFS690A. IMSU688 - CONTROL REGION NOT ACTIVE.U688 - OPERATOR CANCEL. IMS IS DOWN.U688 - IF RUNNING TESTBTCH OR MDLDBTCH ON SYSTEM N, MUST HAVE AU688 - SYSAFF=AHI7 ADDED TO THE JOB'S JOBPARM STATEMENT.U717 - REGION SIZE POSSIBLY TOO SMALL.U722 - CANCELLED BY OPERATOR - LINES PRINTED EXCEEDS LIMITU742 - PROBLEM WITH IMS ** CALL IMS GROUP OR ABENDSU752 - AN ISAM SETL MACRO CALL WAS ISSUED SPECIFYING THE KEY WHICHU752 - INITIATES THE DATA SET. A MESSAGE WAS RETURNED WITH THE

NEXTU752 - HIGHER KEY IN THE DATA SET, INDICATING THAT THE ERROR CONDITIONU752 - WAS NOT FOUND. A SECOND SETL ALSO FAILED BECAUSE OF THE ERRORU752 - NOT BEING FOUND. THE SECOND SETL MAY HAVE FAILED BACAUSE THEU752 - DATABASE WAS NOT COMPLETELY LOADED OR BECAUSE THE DD STATEMENTU752 - FOR THE DATA SET SEPCIFIED FECFM = F INSTEAD OF RECFM = FB.U752 - RESPONSE IN SYSTEM MANUAL: RELOAD DATA BASE SPECIFYING RECFM=FB.U758 - MESSAGE QUEUE DATASET FULL.U769 - SERIOUS SYSTEM ERROR. DO A RESTART.U769 - MAY REFER TO A S322 - TIME ALLOTMENT EXCEEDED - INFINITE LOOP?U775 - UNABLE TO AQUIRE A BLOCK OF STORAGE FOR QUEING CONTROL BLOCKS,U775 - THE ENQUEUE TABLE IS FULL.U775 - PROGRAM IS NOT TAKING ENOUGH CHECKPOINTS. DECREASE YOURU775 - CHECKPOINT COUNT IN THE PROGRAM CAUSING THE ABEND.U777 - SEE U777U777 - IMS CHOSE YOUR PGM TO TERMINATE TO AVOID A DEADLOCK. HAVE JOBU777 - RESTARTED.U778 - AN SQL ERROR OCCURED AND THE ABORT ROUTINE WAS CALLED. THEU778 - ABORT ROUTINE ISSUED A ROLLBACK COMMAND WHICH GIVES THEU778 - U778 CODE. TO SEE THE REAL SQL CODE IN ERROR VIEW DATASETU778 - PRPAC.DBAUF.ABORTTEST(0) THE DAY AFTER THE ABEND, OR CALLU778 - YOUR LOCAL IBM DBA TO CREATE THIS DATASET FOR YOU.U778 - IF ON-LINE PRESS PA2 KEY. THIS WILL SHOW YOU THE ERROR.U779 - TO MANY "Q" COMMANDS BETWEEN CHECKPOINTU80A - REGION SIZE TOO SMALLU801 - DATABASE NOT OPENED FOR UPDATE.U806 - INVALID RETURN FROM BUFFER HANDLER.U806 - (GSAM NAME) GSAM DBD IS NOT PRESENT OR THE ACB GEN WAS NOTU806 - PERFORMED TO DCBLIB.U806 - INCORRECT JOBLIB/STEPLIB OR PROGRAM WAS NOT LINKED.U811 - DLETE/REPLA ATTEMPING TO CHANGE A POINTER IN A SEG'S PREFIX.U811 - IT FOUND THAT THE OLD VALUE OF THE POINTER WAS NOT AS EXPECTED.U811 - PRIOR POINTER MAINTANCE WAS ERRONEOUS.

U813 - DATA SET NAME ON TAPE DOESN'T MATCH ONE SPECIFIED IN JCLU840 - THERE IS A PROBLEM WITH A BMC PRODUCT THAT UTILIZEDU840 DATA PACKER. CONTACT DBA! THIS IS NOT A PROGRAM PROBLEM.U844 - NOT ENOUGH SPACE ON DATABASEU844 - NO AVAILABLE SPACE IN DATA SET -- DATABASE FULLU844 - DATABASE MAY BE FOUND IN I.OLSJIM15(IMSTEST) (HARDCPY1), MAX. TO THEU844 - BOTTOM AND FIND 'DATASET FULL' PREV.U844 - CALL A DATA BASE ADMIN PERSON OR TELL OPERATION TO CALL ONE..U850 - LIKE A B37, RAN OUT OF SPACE ON THE GSAM FILEU852 - DATA BASE BAD.U852 - BAD POINTER - DAMAGED DATABASE - WRONG DBD BEING USEDU853 - BAD POINTERS ON THE DATA BASE.U853 - DATABASE CLOBERED BY BTS TEST BECAUSE OF AN INVALID BACKOUT.U888 - WHEN USING F.A.T.A.R. : FATAR HAS ABENDED DUE TO A SERIOUSU888 ERROR. GO TO THE BOTTOM OF SYSPRINT FOR ABEND DETAILS.U888 - CORE UNAVAILABLE.U905 - INSUFFIEIENT STORAGE FOR PSB (INCREASE REGION SIZE)U913 - THE NAMED DBD CONTAINS AN INVALID OR UNKNOWN ACCESS METHOD.U929 - BLDL-FAILED -CAN NOT FIND MBR TO BUILD FROM (PSB/DBD LIB )U999 - WRONG LRECL ON INPUT DATA SET OF A SORT STEP.U999 - ONE OF THE DATA SETS THAT IS INPUT TO THE SORT MAY BE EMPTY.U999 - IF THE ABOVE TWO CONDITIONS ARE FALSE, AND THE JCL IS USINGU999 - A ROUND TAPE DRIVE (UNIT=TAPE9) AS AN OUTPUT FILE, THEU999 - PROBLEM COULD BE BECAUSE THE TAPE DRIVE IS DIRTY. HAVEU999 - AUBURN HILLS CLEAN THE TAPE DRIVE AND TELL YOUR SUPERVISOR!!!!U999 - IF USING PGM SSGPXLBL, MAKE SURE DSNAMES IN JCL MATCH DSNAMESU999 - IN SYSIN CARDS.U0016 - WHEN USING WAAPDSUT, THERE ARE MAJOR ERRORS IN THE CONTROL CARDSU0016 - CONCAT. DATA SETS ON A SORT. FIRST DATA SET DOES NOT CONTAIN THEU0016 - LARGEST BLOCKSIZE.U0016 - JOB REQUIRES MORE SPACE TO EXECUTE.U0016 - SYSIN * ON A SORT MAY HAVE TOO MANY ENTRIES.U0016 - MAY BE SORTING BEYOND REC LENGTH WHEN WORKING WITH VAR RECORDS.U0016 - IF USING SYNCSORT, CHECK 'SYSOUT' MESSAGES WITH SYNCSORT MANUALU0016 - SYNCSORT: CHECK LRECL OF SORTIN AND SORTOUT FILES.

U0016 - SYNCSORT: USE PARM VLTEST=0 SO WON'T VERIFY THE LRECLSU0102 - SEE U102U0211 - JCL IN 'ALWAYS LOAD' DATASET, BUT NO PROC IN CHAMPU0250 - ONE OR MORE DATASETS NOT CLOSED AT THE END OF THE PROGRAM.U0271 - SEE U271U0428 - SEE U428U0457 - SEE U457U0474 - SEE U474U0688 - SEE U688U0777 - SEE U777U0844 - SEE U844U0999 - SEE U999U1002 - I/O EXCEPTION-CHECK TO SEE IF RECORD LENGTH IN PROGRAM ANDU1002 - RECORD LENGTH OF FILE ARE THE SAME.U1002 - REGION SIZE MAY BE TOO SMALL FOR SORT.U1005 - MIXED PROGRAM CALLS OF DYNAMIC AND STATIC CALL, IMPROPER LINKU1005 - OR, IN COBOL A RECENT COMPILE (AFTER 7/90) HAS MIX OF RES/NORESU1012 - PROGRAM STOPPED BEFORE SORT WAS FINISHED, CHECK TO SEE IFU1012 - PROGRAM FALLS THRU. ADD A SECTION AFTER THE SORT EXIT.U1026 - POINTERS IN YOUR DATABASE ARE MUCKED UP. CALL DBA!!!U1033 - MORE FAST PATH DATABASE BUFFERS NEEDED. INCREASE NBA/OBA IN THEU1033 - DEPENDENT REGIONS JCL. IF A TRANSACTION THEN ASSIGN TO A DIFFERENTU1033 - CLASS SO THAT IT RUNS IN A REGION WITH MORE NBA/OBA.U1999 - DYNAMICALLY CALLED MODULE HAS EXPIRED 'WAASDATE'U2301 - CHECK IMS RETURN CODES FROM DATABASE CALLS.U2750 - LINK CANNOT FIND A CALLED SUBROUTINE.U2750 - IF LATE AT NIGHT, THE SYSTEM MAY BE COMING DOWN.U2750 - MAY ALSO INDICATE PSB IS MISSING.U2810 - INSUFFICIENT SPACE FOR WORK FILE, SEE IOF FOR FILE.U3072 - NEEDS MORE RESOURCES THAN ALLOWEDU3303 - THIS USER ABEND BASICALLY MEANS THAT ONE OF THE APPLICATIONU3303 - DATA BASES IN YOUR PSB IS STOPPED. WHEN YOUR APPLICATIONU3303 - GOES AFTER IT, SOME SORT OF SUBTASK ABEND OCCURS.U3303 - BEFORE CURRENT RELEASE OF IMS THE PGM WOULD ABEND ON A U458.U3303 - MEANS THAT THE PGM WILL RUN UNTIL A DATABASE THAT IS NEEDED IS NOTU3303 - AVAILABLE.U3303 - ENSURE THAT ALL THE NEEDED DATABASE ARE UP AND RUNNING.

U3303 - U458 -- DB USED BY A BMP IS STOPPED.U3560 - DATAVANTAGE ERROR DUE TO LACK OF CHECKPOINT ROUTINE FOR UPDATESU3560 - ADD TO EXEC STMT: ,MBR=DV1CHKP AS NOTED ABOVE FOR UPDATE ONLY.U3560 - YOU MAY NEED TO ADD THE PARMS "NBA=4 AND OBA=4" IF PROCESSING AGAINSTU3560 - FAST PATH DATABASES.U3561 - MAY NEED TO CHANGE DBD IN DVAN SEGD HEADER RECORD TO POINTU3561 - TO CORRECT DBD FOR TEST VERSION.U3561 - DVAN RAN OUT OF BUFFERS. INCREASE NBA AND OBA PARMS.U3592 - BTS TEST RAN OUT OF BUFFERS, PGM WAS USING FAST PATH DB'S BUTU3592 - I HAD FAILED TO SPECIFY 'Y' AT 'FAST PATH DB'S?' PROMPT.U1006 - JOB IS ASKING FOR MORE FAST PATH BUFFERS (NBA) THAN IS CURRENTLYU1006 - AVAILABLE - USE IMS COMMAND "/DIS POOL FPDB" AND LOOK ATU1006 - "UNFIXED" TO DETERMINE HOW MANY BUFFERS ARE CURRENTLY AVAILABLE.U1006 - YOU MUST THEN REDUCE THE JOB NBA PARAMETER TO REQUEST NO MOREU1006 - THAN WHAT IS "UNFIXED" OR WAIT FOR OTHER JOBS TO END AND THUSU1006 - FREE UP MORE BUFFERS........ RFS 2/6/90U1008 - SYNC CALL HAD TO BE MADE AT END OF RUN. THIS ISU1008 - FOR EITHER AN UPDATER OR AN INQUIRY BMP.U1008 - FOR IFP MESSAGE DRIVEN APPLICATION PROGRAMS AND MPPSU1008 - PROGRAM RETURNED NORMALLY BUT WITHOUT A QC STATUS CODEU1008 - POSTED IN I/O PCB OR WITHOUT RELEASING FAST PATH BUFFERS.U1008 - SOLUTION: RETURN CONTROL TO IMS ONLY AFTER A QC STATUS CODEU1008 - IS RETURNED IN I/O PCB OR AFTER ISSUING A SYNC OR ROLB CALL TOU1008 - RELEASE BUFFERS.U1016 - DD CARD IN THE JCL IS MISSINGU1017 - PSB IS MISSING OR DOES NOT MATCH THE PROGRAMU1017 - DD CARD IN THE JCL IS INCORRECTU1017 - FOR COBOL -- OPEN OF DISPLAY/ACCEPT FILE WAS UNSUCCESSFUL. CHECKU1017 - TO SEE IF THE DDNAME IS SUPPLIED IN THE JCL OR CLISTU1017 - IF RUNNING BTS YOU NEED A "SYSOUT(D)" ON THE PROC LINE OF YOURU1017 - BTS CLISTU1020 - THE PROGRAM TRIED TO READ PASS THE END OF FILE

U1020 - MARKER ON THE INPUT RECORDU1020 - THE PROGRAM TRIED TO CLOSE AN UNOPENED FILEU1020 - THE PROGRAM TRIED TO OPEN AN ALREADY OPENED FILEU1020 - FOR GSAM FILE, MAKE SURE THE DCB IS INCLUDED ONU1020 - THE INPUT DD STATEMENTU1020 - ADD SORTWK DD STATEMENTS TO JOB STEP USING PRINTU1020 - UTILITY (DMGPRPT).U1020 - THE PROGRAM ABENDED ON A CLOSE STATEMENT BECAUSEU1020 - THERE WAS NOT ENOUGH SPACE IN THE FILE FOR EOF MARKU1034 - FILE SECONDARY ALLOCATION LIMIT ENCOUNTERED.......U1035 - WRONG DDNAME IN JCL OR IN COBOL-FD IS MISSING BLOCK CONTAINSU1035 - OR, AN OPEN ERROR HAS OCCURED. THIS MAY BE BECAUSE YOU AREU1035 - PROCESSING A VARIABLE BLOCKED FILE AND THE RECORD LENGTH INU1035 - YOUR PROGRAM FD DOES NOT MATCH THE VB FILE'S LRECL MINUS FOURU1035 - OR, CHECK JCL FOR IMPROPER RECORD LENGTHU1320 - ERROR WRITING CHECK POINT, INCREASE REGION ON STEP OR JOBU1055 - DD NAME IS MISSPELLED OR MISSINGU1525 - NOT CAT2 CONDITION DURING A CHECK POINT/RESTART EXECUTIONU1806 - CHECK THE GSAM FILE NAME MATCES DD NAME IN JCLU2047 - PROD REGION W/TEST PSB (OR IMS DATASET) OR VICE VERSA.U2047 - REGION AND PSB/DATASET MISMATCH.U2658 - BMC2658, CANNOT FIND SEGMENT NAME IN DBD FOR RELOADU2749 - BMC2749, OPEN FAILURE ON DDNAME ' '.U2871 - REGION SIZE IS NOT LARGE ENOUGH - INCREASE ITU3001 - TRYING TO USE GENERATION DATA GROUPS IN TESTLIB? - CANNOT.U3001 - CATCH-ALL...KEEP LOOKING!!!!!!!!!!!!!!!!!U3001 - ABEND AID: ISSUED BY PL/I AFTER NORMAL RETURN FROM AN ERROR,U3001 - OR FINISH ON-UNIT FOR ERROR ON-CODE 0084.U3001 - CHECK SYSPRINT, OR ABEND-AIDU3007 - ABEND DURING AN ASSEMBLY OF A MFS SCREEN. UNABLE TO STOW.U3007 - DIRECTORY BLOCKS ARE FULL.U3007 - IMSVS1.TEST.TFORMAT DATASET IS FULL. DELETE UNNEEDED MEMBERSU3007 - IN DATASET AND RETRY.U3300 - STORAGE SPACE FOR DATABASE ENQUEUES HAS BEEN FILLED UP. ALLU3300 - IMS PROGRAMS CURRENTLY RUNNING WILL ABEND. CAUSE IS: AN UPDATE

U3300 - BMP IS NOT CHECKPOINTING FREQUENTLY ENOUGH. THE SYSTEM DOES NOTU3300 - IDENTIFY WHICH BMP IS AT FAULT. OLD ABEND CODE WAS U775.U3303 - INSTEAD OF U458 WHEN PROGRAM IS ACCESSING AU3303 - DATABASE THAT HAS BEEN STOPPED. TRAN PUT ONU3303 - SUSPEND QUEUE. DO A /STA TRAN COMMAND AFTERU3303 - DATABASE IS BACK UPU3500 - GENERIC USER ABEND CODE USED FOR PROGRAMMER FORCED ABENDSU3500 - CHECK SYSOUT FOR DESCRIPTIVE ERROR MESSAGES DISPLAYED BY PROGRAMU3500 - REPLACEMENT OF THE COMPUTE XXX = 1 / 0 STATEMENTU3501 - INVALID PARM LENGTH OR VALUEU3502 - ERROR DETECTED BUT NO ABEND; RETURN CODE SPECIALU3502 - REGISTER SET TO 3502 AND INTERROGATED IN THEU3502 - JCL TO EXECUTE WAASABND.U3503 - ENCOUNTERED STOP AND/OR ACCEPT STATEMENTU3504 - AFTER ANY INVALID RETURN CODE FROM "WAASDYN"U3505 - WHEN THE CHECKPOINT LIMIT RECORD IS INVALIDU3506 - RESERVED AS THE STANDARD JCL PARM= VALUE FORU3506 - PROGRAM "CURPB002"U3507 - INVALID SQLCODE VALUE AFTER EXECUTION OF ANY SQLU3507 - CODE IN TSO BATCH DB2 APPLICATION PROGRAMSU3508 - USED BY CURSU002 (DATE/TIME) WHEN A BAD RETURNU3508 - FROM WAASDATE IS FOUND.U3509 - REPLACEMENT OF SETTING THE ATTRIBUTE STATUS TO "-1"U3509 - IN BATCH COBOL PROGRAMS.U3510 - AFTER ANY INVALID RETURN CODE FROM "DM028X"U3511 - USER ABEND IN "BATCH PRINT" PROGRAM - ISSUEDU3511 - BY S9999-ABORT-ROUTINE FOLLOWING A ROLB CALLU3512 - DATA SET EMPTYU3513 - SSDPDB2Q - INVALID FUNCTION CODE PARMU3514 - SSDPDB2Q - UNSUCCESSFUL DEQUEUEU3515 - ANY NON-DATABASE RELATED TPS ERROR IN TSO BATCHU3515 - APPLICATION PROGRAMSU3516 - BAD RETURN FROM CURSU002 IN CAL-DATE CALLU3516 - REPLACEMENT.U3517 - RETURN CODE INDICATING AN UNSUCCESSFUL CALLU3517 - TO WAASCTLM.U3518 - INTERNAL TABLE LIMIT EXCEEDED.U3501 - GENERIC USER ABEND CODE USED FOR PROGRAMMER FORCED ABENDSU3501 - CHECK SYSOUT FOR DESCRIPTIVE ERROR MESSAGES DISPLAYED BY PROGRAMU3506 - NO TIE CONDITION FOR ELECTRONIC TIEINSU3514 - BAD RETURN FROM ISRT TO RI7ORDR

U3516 - BAD RETURN FROM GHU TO RI7PRGMU3550 - BAD RETURN FROM CHKPT/RSTR CALL TO COCSS03U3599 - BAD RETURN FROM DB CALLU3600 - BAD RETURN FROM OPEN OF GSAM FILEU3604 - THE ABEND-CODE SENT TO WAASABEND WAS TOO HIGHU3604 - ONLY 1 THRU 4905 IS ACCEPTABLEU3650 - BAD RETURN FROM CLOSE OF GSAM FILEU3700 - BAD RETURN FROM READ OF GSAM FILEU4000 - CHECK DISPOSITION OF FILES BEING USED FOR POSSIBLE NOT-CATLG-2U4000 - ERROR WITH FIRST XRST CALL TO CHECKPOINT.U4002 - PSB AND CONTROL NUMBER DO NOT MATCHU4002 - CHECK THE PROGRAM NAME -- DO NOT ADD 'T'!U4006 - IMS BATCH ABEND, ONE OR MORE FILES WERE NOT CLOSED AT END.U4011 - TC UPDATE ABEND, CURRECT UPDATE JOB NOT ZERO, ANOTHER UPDATEU4011 - JOB WAS RUNNING. PLEASE FOLLOW RESTART INSTRUCTIONS AFTERU4011 - OTHER UPDATE JOB IS DONE. HAVE A NICE DAY!!!!!U4028 - INVALID ISA SIZE. INITIAL STORAGE AREA NOT LARGE ENOUGH.U4032 - GSAM FILE NOT SPECIFIED IN PSBU4032 - IF ACCESS TO CHAMP LOST: LOGOFF/LOGON TO RESET POINTERS.U4036 - ERROR IN IBM ERROR HANDLING ROUTINE. (CHECK STMT TO DEBUG)U4036 - A PROGRAM CHECK OCCURRED DURING AN IMS CALL STATEMENT.U4036 - REGISTER 2 POINTS TO THE PIE/EPIE. SUGGESTION TO PUT AU4036 - CHECK STATEMENT ON EACH PROC TO DETERMINE WHICH PROC ABENDED.U4036 - SYSTEM USUALLY WILL NOT REFLECT WHERE THE ABEND OCCURRED.U4036 - BE SURE THAT YOU ARE EXECUTING "EXEC TESTBTCH,MBR=XXXXXX"U4036 - CHECK DCB INFO IS PRESENT AND CORRECT IN JCL. LRECL,BLKSIZEU4036 - BE SURE THAT PROGRAM HAS CORRECT DATA SET TYPE IN CHAMP.U4048 - CHECK THAT A TABLE (ARRAY) IS NOT BEING OVERFILLED ALSO.U4050 - THE IMP2CNTL DD STATEMENT WAS NOT PROVIDED OR IS DUMMY.U4051 - THE IMP1LIST DD STATEMENT WAS NOT PROVIDED.U4052 - FILE DD MISSING ON JCL (IMP1****)U4078 - THE CHKPM VALUE SPECIFIED IN THE CHKP OPERAND OF MI1UDATA WASU4078 - EXHAUSTED PRIOR TO THE ARRIVAL OF A SEQUENCED UNIQUE SEGMENT.U4078 - EXAMINE AND ADJUST MI1UDATA CHECKPOINT PARAMETERS.

U4094 - HARDWARE ERROR; NOT A SOFTWARE PROBLEM, RESTART AND TRY AGAIN.U8094 - (ONCODE) PROTECTION EXCEPTION. MISSPELLED PCB NAME IN CALL.U8094 - (ONCODE) PTR NOT SET OR PTR NO SET FOR BASED STRUCTURE.U8097 - (ONCODE) DATA EXCEPTIONU9999 - DUMMY0002 - (ONCODE) RUNTIME ERROR FROM IMS TEST REGION BEING CANCELLED.0003 - (ONCODE) ATTEMPT MADE TO EXEC STMT DIAGNOSED IN ERROR AT COMPILE TIME0009 - (ONCODE) SIGNAL ERROR INSTRUCTION, USER 3001.0042 - (ONCODE) POSSIBLE BAD DATA.0093 - (ONCODE) POSSIBLE CAUSE: INSUFFICIENT REGION,0093 TRY INCREASING REGION0093 - VSAM FILE STATUS 2 CHAR. RETURN CODE. IF FILE WITH BAD RETURN0093 CODE IS NOT ALLOCATED TO AN ONLINE REGION, AND PROGRAM IS0093 COBOLII, CHANGE RECORD CONTAINS CLAUSE IN FD FROM '0' TO THE0093 ACTUAL LRECL OF THE FILE.