ims abend codes

IMS ABEND CODES

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 DBDGEN

AID - TO TURN OFF ABENDAID SUPPLY //ABNLIGNR DD DUMMY

A13 - A13-08 REQUESTED FILE SEQUENCE NUMBER IS LESS THAN THAT OF THE

A13 - FIRST FILE.

A13 - A13-10 REQUESTED FILE SEQUENCE NUMBER IS NOT FOUND. IF YOU ARE

A13 - READING A FILE YOU NEED TO VERIFY YOU HAVE THE CORRECT LABEL

A13 - NUMBER. IF YOU ARE WRITTING A FILE THEN YOU HAVE REACHED THE

A13 - MAX NUMBER OF TAPES ALLOWED, WHICH IS DETERMINED BY THE VOL

A13 - STATEMENT IN THE FIRST STEP THAT WRITES TO THE TAPES. FOR

A13 - EXAMPLE IF PS020 SAYS VOL=(,,,20) THEN IN PS070 YOU TRY TO

A13 - WRITE THE 22 TAPE YOU WILL ABEND WITH THIS CODE. YOU WILL NEED

A13 - TO CHANGE THE VOL STATEMENTS AND RESTART IN THE FIRST STEP THAT

A13 - 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 ARE

NOTES - IN TROY.

NOTES - (Q) WHY ARE THE TRANSACTION SCHEDULING DEFAULT PARAMETERS BEING

NOTES - RESET TO ZEROS IN OLSJIM15(IMSTEST) EACH MORNING?

NOTES - 1. THE TRANSACTION IS DEFINED TO IMS INCORRECTLY. IT IS

NOTES - DEFINED AS A BMP INSTEAD OF A TRANSACTION WHICH CAUSES THE

NOTES - PARAMETERS TO BE SET TO ZERO.

NOTES - (Q) WHAT IS THE DIFFERENCE BETWEEN TAPE AND TAPE9?

NOTES - 1. TAPE = SINGLE DENSITY 6250 BYTES PER INCH

NOTES - TAPE9 = DUAL DENSITY 1600/6250 BYTES PER INCH

NOTES - (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 THE

NOTES - 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 BE

NOTES - 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 OMITTED

NOTES - (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 ERROR

NOTES - 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 FOR

NOTES - 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 A

NOTES - SCREEN OR PRINTER?

NOTES - 1. MAXIMUM MESSAGE LENGTH IS 3800 BYTES.

NOTES -

NOTES - (Q) WHEN ABENDING A COBOL PGM. IN BTS THROUGH WAASABEND WHY DO

NOTES - I GET LOGGED OFF TSO?

NOTES - 1. WHEN CALLING WAASABEND MUST PASS IT A PARM OF 'DN' TO DUMP

NOTES - WITH TASK TERMINATION ONLY. DEFAULT IS 'DS' WHICH LOGS YOU

NOTES - 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 PRINT

NOTES - 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 RUNNING

NOTES - RELEASE 4, MOST OTHER PRINTERS RUNNING RELEASE 12.

NOTES -

NOTES -

NOTES - (Q) WITH TWO USERID'S (USERID - USERIDT), HOW COME I CAN'T VIEW JOBS

NOTES - 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 SUSPEND

NOTES -

NOTES - IEF211 DATASET RESERVATION UNSUCCESSFUL --

NOTES - IEF211 MAKE SURE DISP = OLD

NOTES - SOMEONE OR SOMETHING ELSE IS USING THE DATASET. TRY AGAIN

NOTES - USE WHOHASIT FOR THE ELSE SOMEONE/SOMETHING

NOTES -

NOTES - (Q) WHY AM I NOT GETTING ALL MY STRUCTURE DATA WRITTEN OUT TO

NOTES - MY GSAM FILE.

NOTES - (A) THE LENGTH OF THE MOVE IS CONTROL BY THE DCB'S IN THE DD

NOTES - 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 SET

NOTES - 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 READ

TPROC - /*JOBPARM R=SA03,PROCLIB=TEST

PME - ERROR LD02 LOOK FOR MISSING PME$EOJ MEMBER IN YOUR PME.JOBSET

PME - 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 A

D100 - QUERY IS AN EMPTY TABLE.

D162 - TABLESPACE HAS BEEN PLACED IN CHECK PENDING

D304 - A VALUE WITH DATA TYPE 1 CANNOT BE ASSIGNED TO A HOST VARIABLE

D304 - BECAUSE THE VALUE IS NOT WITHIN THE RANGE OF THE HOST

D304 - VARIABLE BECAUSE THE VALUE IS NOT WITH THE RANGE OF THE

D304 - HOST VARIABLE.

D304 - WHEN A FIELD IS DEFINED TO DB2 IT IS POSSIBLE TO GIVE THE

D304 - FIELD VERTAIN VALUE LIMITS. THE VALUE USED IN THIS UPDATE

D304 - 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 TERMINATED

D101 - THE STATEMENT IS TOO LONG OR TOO COMPLEX

D102 - THE LENGTH OF THE STRING CONSTANT IS GREATER THAN 254 CHARACTERS

D103 - AN INVALID NUMERIC LITERAL

D120 - A WHERE CLAUSE OR SET CLAUSE INCLUDES A COLUMN FUNCTION OR A

D120 - WHERE CLAUSE REFERENCES A COLUMN WHICH IS DERIVED FROM A

D120 - COLUMN FUNCTION OR EXPRESSION IN A VIEW DEFINITION.

D121 - THE COLUMN IS IDENTIFIED MORE THAN ONCE IN AN INSERT OR UPDATE

D129 - THE STATEMENT CONTAINS TOO MANY TABLE NAMES

D161 - 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 QUALIFICATION

D181 - THE STRING REPRESENTATION OF A DATETIME VALUE IS NOT A VALID

D181 - DATETIME VALUE.

D204 - TABLE NOT FOUND.

D208 - THE ORDER BY CLAUSE IS INVALID BECAUSE A COLUMN NAME IS NOT

D208 - PART OF THE RESULT TABLE.

D401 - THE OPERANDS OF AN ARITHMETIC OR COMPARISON OPERATION ARE NOT

D401 - COMPARABLE.

D504 - THE CURSOR NAME IS NOT DEFINED.

D507 - THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS

D507 - NOT OPEN.

D508 - THE CURSOR IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS

D508 - NOT POSITIONED ON A ROW.

D509 - THE TABLE IDENTIFIED IN THE UPDATE OR DELETE STATEMENT IS NOT

D509 - THE SAME TABLE DESIGNNATED BY THE CURSOR.

D612 - A DUPLICATE COLUMN NAME IS IN THE STATEMENT

D803 - AN INSERTED OR UPDATED BALUE IS INVALID BECAUSE THE INDEX

D803 - CONSTRAINS COLUMNS OF THE TABLE SUCH THAT NO TWO ROWS CAN

D803 - 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 PERFORM

D922 - THIS FUNCTION.

SA13 - SEE A13

SB0A - 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 GSAM

SB37 - FILE AND A RESTART IS NECESSARY

SB37 - ADD A VOL=SER=XXXXXX (XXXX IS ANOTHER PACK SER NUMBER IN

SB37 - YOUR POOL).THIS WILL CAUSE YOUR DATASET TO SPAN OVER TO

SB37 - 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 BEING

SC03 - DELETED OR ISSUED AN XCTL MACRO CAUSING THE SYSTEM TO REUSE

SC03 - THE PGM STORAGE CONTAINING THE DCB.

SC03 - PLEASE CONTACT ABEND-AID ADMINISTRATOR.

SC03 - DID NOT MOVE ZERO TO W-COCS903-PRCDR-CNTR AND CALL COCSS03

SC03 - AT THE END OF A COBOLII IMS PROGRAM.

SD37 - LIBRARY FULL

SD37 - D37-04 DSN OPENED AS OUTPUT USED ALL THE PRIMARY SPACE AND

SD37 - 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 APPLICATION

SPND - DATA BASES IN YOUR PSB IS STOPPED. WHEN YOUR APPLICATION

SPND - 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 NOT

SPND - 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 ABENDING

S0C1 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 CARD

S0C1 - 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 WITH

S0C1 - RENT AND RES AND THE DRIVER IS LINKED WITHOUT RENT AND RES THEN

S0C1 - 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 BEING

S0C3 - DELETED OR ISSUED AN XCTL MACRO CAUSING THE SYSTEM TO REUSE

S0C3 - THE PGM STORAGE CONTAINING THE DCB.

S0C3 - PLEASE CONTACT ABEND-AID ADMINISTRATOR.

S0C3 - DID NOT MOVE ZERO TO W-COCSS03-PRCDR-CNTR AND CALL COCSS03

S0C3 - AT THE END OF A COBOLII IMS PROGRAM.

S0C4 - MAY NEED TO INCREASE REGION

S0C4 - FOR IMS STEP, TRY ADDING PARM "REG=4M," TO IMSBATCH CARD

S0C4 - VERIFY DCB'S

S0C4 - IF NEW IMS PROGRAM OR ADDED A D/B MAKE SURE PSB WAS GEN'D

S0C4 - IF PGM IS BEING COMPILED THRU CHAMP BE SURE YOU HAVE THE RIGHT

S0C4 - 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 TO

S0C4 - COCSS03 WAS MADE WITH A PRCDR-CNTR = 0. PRCDR-CNTR SHOULD ONLY

S0C4 - = 0 FOR FINAL CALL.

S0C4 - WHEN USING SDB BLKSIZE=0000, BE SURE TO USE DSORG=PS

S0C4 - IF CODE IS COBOL II, ENSURE FD HAS FOLLOWING: ACTUAL LRECL IN

S0C4 - RECORD CONTAINS CLAUSE, CORRECT RECORDING MODE, AND A GOOD DATA

S0C4 - 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 EXCEPTION

S0C7 - WATCH FOR EXCEEDING TABLE BOUNDARIES

S0C7 - AT END STATEMENT FOLLOWED BY CONDITIONAL STATEMENT

S0C9 - ARITHMETIC ERROR IN PROGRAM

S0CA - DECIMAL OVERFLOW - DESTINATION TOO SMALL FOR RESULT

S0CB - DECIMAL DIVIDE EXCEPTION

S0CB - A QUOTIENT EXCEEDS THE SPECIFIED DATA FIELD SIZE.

S0F1 - RECORD DESCRIBED AS WRONG LENGTH

S0F2 - ATTEMPT TO WRITE A VARIABLE LENGTH FILE WHICH HAS A BLOCK

S0F2 CONTAINS 0 RECORDS IN THE FD AND DCB PARAMETERS. THIS ONLY WORKS

S0F2 ON FIXED LENGTH.

S0F3 - DISK I/O FAILURE - CALL PLANO!!!!

S001 - I/O ERROR READING INPUT FILE

S001 - IF USING TAPE, THE TAPE MAY BE BAD, TRY A NEW ONE

S001 - TRIED TO READ PAST END OF FILE

S001 - TRIED TO WRITE ON AN INPUT FILE

S001 - INCORRECT USE OF LABEL PARAMETER IN COBOL PGM

S001 - OUT OF SPACE IN A PDS

S001 - INPUT FILE DESCRIBED INCORRECTLY, LENGTH ERROR

S001 - ATTEMPT TO OPEN AN OPENED FILE OR CLOSE A CLOSED FILE

S002 - RECORD IS GREATER THAN 32,768 BYTES, EXCEEDS MAXIMUM TRACK LGTH

S002 - OR STATED BLOCK SIZE................

S002 - WHEN READING UNLOAD TAPES THE PREFIX MAY NOT AGREE W/UNLOAD TAPE

S002 - DCB HAD THE WRONG BLOCKSIZE

S002 - WRONG RECORD FORMAT SPECIFIED IN JCL

S002 - FD AND 01 IN COBOL PGM DO NOT AGREE ON RECORD LENGTH

S013 - 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 FOR

S013 - 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 LABEL

S106 - CSV011 & IEA995I FETCH FAILED FOR MODULE A0770.

S106 - 8.1 COMP LINKED, BUT 8.2 DIDN'T. FIXED PROBLEM BY

S106 - BUMPING UP REGION IN JCL FOR A0770.

S106 - ERROR RECEIVED TRYING TO BTS TEST A LARGE COBOL PROGRAM, FIXED

S106 - 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 THE

S117 - 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 IEC215

S137 - 714-0C I/O ERROR OCCURED WRITING A TAPE MARK. RESTART JOB

S200 - FILLED OUT BUFNO INCORRECTLY.

S200 - BUFFERS FILLED CORE

S213 - 04 VOL=SER DOES NOT MATCH WHAT IS ON THE TAPE

S213 - BAD DISP= FOR TAPE

S213 - DATA SET WAS CATALOGED, BUT HAS BEEN DELETED

S213 - IEC143I 213-30: ATTEMPTING TO UPDATE TWO MEMBERS OF SAME PDS

S213 - INCORRECT SPELLING OF DSNAME.

S214 - INCORRECT DSP

S214 - TAPE POSITIONING ERROR

S222 - OPERATOR CANCELLED

S237 - 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. VERIFY

S237 CORRECT VOLUME OR DSNAME WERE SPECIFIED.

S237 - INCORRECT VOLSER.

S237 - INCORRECT LABEL.

S273 - AN ERROR WAS DETECTED WHILE REPOSITIONING A GSAM DATA SET

S273 - DURING AN XRST CALL.

S273 - BAD O/P (GENERAL).

S30A - MISSING A BLOCKSIZE ON AN OUTPUT DISK DATA SET.

S304 - MISSING SORTLIB DD CARD

S304 - 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 FILE

S337 - TRIED TO WRITE ON TAPE DEFINED AS INPUT

S400 - SYSTEM CONTROL BLOCK OVERLAID (DCB) - SEE S0C1

S402 - UNAUTHORIZED ATTEMPT TO USE IMS.

S402 - THE REGION WAS PROBABLY TAKEN DOWN WHILE PROCESSING

S413 - MISSING DCB INFORMATION.

S413 - HAD DISP=NEW INSTEAD OF SHR

S413 - RECFM MISSING

S413 - ERROR DURING INPUT INSTRUCTION.

S413 - INPUT, SPECIFIED BUT NO SERIAL NUMBER FOR SER IN DD; I/O

S413 - ERROR IN TAPE POSITIONING OR LABEL PROCESSING; COULD NOT

S413 - MOUNT ON DEVICE; MORE DEVICES ALLOCATED THAN VOLUMES;

S413 -

S413 - IF OUTPUT FILE IS TO TAPEC, USE THE FOLLOWING EXAMPLE TO

S413 - 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 FILE

S413 - 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 GREATER

S413 - THAN THE NUMBER OF VOLUMES CONTAINING THE DATA SET(IEC145I)

S422 - JOB OVERFLOWS QUEUE. TOO MANY STEPS IN JCL

S430 - GENPSB FAILED DUE TO LACK OF CMPAT=YES IN PROD PSB SOURCE. CORRECT

S430 - 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 THE

S522 - 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 THE

S613 - TAPE WAS ORIGINALLY CREATED ON.

S613 - DCB MISSING.

S613 - TAPE POSITIONING ERROR

S613 - SEE S413

S622 - TSO SESSION WAS CANCELED

S637 - 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 LINK

S713 - MAG TAPE WAS MOUNTED AS A SCRATCH TAPE BUT THE RETENTION PERIOD

S713 - HAD NOT YET EXPIRED.

S714 - I/O ERROR WRITING LABEL

S722 - SYSPRINT LINES EXCEEDED

S737 - ERROR OCCURRED AT END OF VOLUME DURING ALLOCATION OF A SECONDARY

S737 - QUANTITY OF DIRECT ACCESS STORAGE. MESSAGE IEC027I GIVES MORE

S737 - 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 THE

S80A - MODULE IS BEING LOADED INTO THE SAME ADDRESS SPACE EVERYTIME.

S80A - (I.E. IF YOU ARE CALLING WAASDATE, BE SURE THE W-DOUBLE FIELD

S80A - IS ONLY INITIALIZED ONCE. THE FIRST CALL PLACES THE LOAD ADDR

S80A - INTO THE 2ND BYTE AND THAT ADDRESS IS REUSED.)

S800 - TRIED TO OPEN A FILE THAT DID NOT HAVE A DD

S804 - 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 CORRECT

S806 - IF LOG MESSAGE IS PREFIXED BY A CSV--- NUMBER CHECK GSAM....

S806 - CHECK SETOOLS FOR GSAMCHK TO SEE IF ON FILE

S806 - CALLING A FORTRAN PROGRAM FROM COBOL NEED TO INITIALIZE

S806 THE FORTRAN ENVIRONMENT BY CALLING COCSFE

S806 - PSB USES GSAM FILES - PSB MUST BE IN PSBLIB AND ACBLIB/DCBLIB

S806 - NOT ENOUGH CORE AVAILABLE.

S813 - DATA SET NAME IN JCL DOES NOT MATCH DATA SET NAME IN LABEL

S837 - 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 OR

S878 - ENDING FOR MORE REGION THAN AVAILABLE OR REGION LENGTH WAS NEGAT

S878 - INCREASE SORTWORK SPACE AND MAKE IT CONTIGUOUS

S913 - SECURITY VIOLATION (ACF2)

S913 - 913-0C ON MSTR CATALOG CHECK JCL FOR A DD RECORD THAT MIGHT

S913 - HAVE DSN=DUMMY

SECG - CICS ABEND CODE - SECURITY ERROR ON TRANSACTION

U002 - TEST HAS TERMINATED AND HAS FORCED TERMINATION OF ALL ACTIVE

U002 - 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 WITHIN

U012 - SYSIN CARDS. REMOVE THE COMMENTS AND P=XCE THEM ELSEWHERE.

U016 - WHEN USING WAAPDSUT, THERE ARE MAJOR ERRORS IN THE CONTROL CARDS

U016 - CONCAT. DATA SETS ON A SORT. FIRST DATA SET DOES NOT CONTAIN THE

U016 - LARGEST BLOCKSIZE.

U016 - JOB REQUIRES MORE SPACE TO EXECUTE. ADD AMOUNT OF CYL ON

U016 - 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) OCCURRED

U069 - RC 8 = F/P WAS UNAVAILABLE AND A F/P CALL WAS DETECTED

U069 - NOTIFY DBA REPRESENTITIVE FOR CORRECTION.

U080 - ACF2 ON A DATASET - CHECK LOG IN EXECUTION

U080 - WHEN TESTING WITH 'DLICHKPT' THE DD NAMES FOR YOUR DATABASE MAY

U080 - BE INCORRECT. CHECK THE PSBLIB.

U084 - PL/I ERROR ON-CODE; SIGNIFIES UNDEFINED FILE CONDITION WAS

U084 - RAISED WHEN THERE WAS AN ATTEMPT TO OPEN A FILE FOR WHICH

U084 - NO DD STATEMENT EXISTS IN JCL JOBSTREAM.

U089 - RESTART-- EVERYTHING.

U100 - WRONG USER CODE GENERATED BY PROGRAM. CHECK PROGRAM FOR PROBLEM

U100 - FIX IT AND CHANGE USER CODE TO A CORRECT PROGRAM GENERATED CODE.

U102 - CHECKPOINT NOT FOUND ON RESTART

U102 - GO INTO IMSCHKPT, AND SET CHECKPOINT COUNTER TO ZERO IF YOU

U102 REALLY DON'T CARE TO RESTART

U102 - TO RESTART >>>>>>>>>>DO NOT CHANGE JOB NAME ON RESTART<<<<<<<<<<

U102 - MAYBE THE CHECKPOINT RECORD GOT DELETED BECAUSE YOU DID NOT

U102 - TRY AND RESTART IMMEDIATELY. YOUR RESTART RECORD WAS ROLLED OFF

U102 - 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 REGION

U134 - SHUTDOWN WAS IN PROGRESS. (IMS TEST IS IN PROCESS OF COMING

U134 - DOWN).

U205 - ERROR OCCURED DURING A FORM OF FREEMAIN MACRO INSTRUCTION.

U205 - NO REAL STORAGE AVAILABLE FOR A REQUEST. TRY JOB AGAIN

U205 - SAME ERROR CALL SYSTEMS GROUP.

U222 - CANCELLED BY OPERATOR.

U240 - THE EXECUTION (CPU TIME) ALLOTTED FOR A TRANSACTION HAS

U240 - 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 OUTPUT

U259 - SHOULD BE (24) AMODE IF NOT SEEK HELP.

U260 - PCNT = 0

U260 - IF COBOL PGM AND ON A OPEN STMT RECOMMEND DO NOT UES PCNT OPTION

U260 - AND REMOVE ANY COMMAS IN THE STMT.

U261 - ADD 3 CHAMP LINK CONTROL STATEMENTS TO COBOL PROGRAM

U261 - * STARTCTL:

U261 - * LINKB4: ENTRY DLITCBL

U261 - * ENDCTL:

U261 - ONE OF THE PARMAMETERS PASSED IN A DL/I CALL FROM THE APPLICATION

U261 - PROGRAM TO IMS/VS IS INVALID. IT EITHER EXCEEDS OBJ MACH SIZE,DOES NOT

U261 - MEET ALIGNMENT REQUIREMENTS, OR VIOLATES STORAGE PROTECTION BOUNDS

U261 - POSSIBLE PROBLEM CAN BE THAT A POINTER IS BEING USED TO POINT TO

U261 - DB SEGMENT BUT WAS NEVER SET TO AN ADDRESS.

U261 - I/O AREA NAME OR SSA NOT DECLARED.

U261 - PCNT TO LARGE

U261 - MISSPELLED FUNCTION CODE

U261 - 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 THAT

U262 - THE IMS SYSTEM WAS UNDERGOING A CHECKPOINT FREEZE OR SHUTDOWN.

U271 - INCREASE CHECK POINT RESTART LIMITS

U271 - POSSIBLE I/O ERROR ON GSAM FILE

U273 - COULD NOT PROCESS CHECKPOINT FILE. EITHER THE FILE IS BAD, OR

U273 - IS NOT FOUND.

U322 - CPU TIME LIMIT EXCEEDED

U328 - PSB NOT DEFINED

U402 - BAD IMS CALL LIST

U402 - TP PCB MISSING IN PSB

U428 - #IMS STATEMENT DOES NOT MATCH PSB OR PGM DOES NOT HAVE A PSB

U428 - PROGRAM NOT DEFINED TO THE SYSTEM

U428 - 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 POOLS

U430 - TO CORRECT - SUPPLY REGION RECORD ON JOB CARD OF 1024 OR GTR.

U430 - TRY INCREASING THE SIZE OF THE REGION PARAMETER.

U452 - TRANSACTION STOPPED

U452 - TRANACTION STOPPED

U454 - PGM STARTED AFTER A SHUTDOWN CHECKPOINT HAD ALREADY STOPPED

U454 - ALL OTHER REGIONS. (IMS IS DOWN).

U456 - PROGRAM/TRANSACTION IS STOPPED OR DCB LIBRARY TOOK AN

U456 - 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 PROBLEM

U456 - IN IOF LOOK AT OLSJIM15(IMSTEST) THAT IS RUNNING IN THE (6)HARDCPY1

U456 - IF ZIP PSB, MUST BE IN DCBLIB.

U456 - THE PSB IN QUESTION MAY BE STOPPED BY A PRIOR PGM FAILURE

U456 - IF DOPT , CN NOT BE IN ACBLIB ... ONLY IN DBDLIB.

U456 - PSB STOPPED

U456 - 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 JOB

U476 - #IMS STMT DOES NOT MATCH PSB OR DLI CALL ARGUMENTS COUNT WRONG

U476 - DLI CALL ARGUMENTS NOT IN CORRECT ORDER.

U476 - MAY NEED TO ADD LINKB4 CARDS FOR CHAMP 3.1 COMPILES

U476 - A DL/I CALL DOES NOT INCLUDE A VALID PCB ADDRESS.

U476 - POSSIBLE CAUSE IS THAT NUMBER OF PCBS IN PSB DO NOT MATCH

U476 - THE #IMS STATMENT IN THE PROGRAM. IF THEY DO, ALSO CHECK IF

U476 - DBA ADDED A TP DEFINITION IN THE PSB GEN. IF SO, ANOTHER TPPCB

U476 - MUST BE ADDED TO THE PROGRAM #IMS STATEMENT.

U476 - IF YOU ARE MAKING A DLI CALL FROM A SUBPROGRAM, MAKE SURE

U476 - THE "USING" LIST OF ARGUMENTS IN THE MAIN PROGRAM'S CALL

U476 - STATEMENT MATCHES THE "USING" LIST IN THE SUBPROGRAM'S ENTRY

U476 - STATEMENT

U476 - CHECK LANGUAGE TYPE IN PSB

U476 - CMPAT = YES FOR BATCH ONLY

U476 - PSB CHGED TO ADD GSAM D/B,BUT JCL/PGM NOT CHGED. ABENDS AT CHKPT

U476 - MUST NOT HAVE>CMPAT=YES FOR TRANSACTION

U476 - INVALID DB PCB NAME.

U476 - DCB'S MISSING ON GSAM D/B.

U476 - NBR OF PCBS IN PSB DOES NOT AGREE WITH #IMS IN PROGRAM

U476 - 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- AND

U476 - CONTENT IN THE ENTRY SECTION IS IN LINE WITH THE -PSB-

U476 - ENTRY STATEMENT DOES NOT MATCH PSB

U476 - MAKING A CALL TO A DB NOT DEFINED IN THE ENTRY

U476 - STATEMENT OR PSB. (EX. SECONDARY INDEX DB)

U476 - ENSURE CALL HAS A DATABASE POINTER NAME

U476 - PROGRAM WAS NOT COMPILED AS AN IMS PROGRAM,

U476 - RECOMPILE AND TRY AGAIN.

U476 - IF PROGRAM IS COBOL AND COMPILED IN CHAMP, MAKE SURE DS

U477 - IMS BMP DOING GETMAINS FOR MORE SPACE DURING EXECTION, ABENDS

U477 - WHEN SPACE NOT AVAILABLE. JUST HAVING PROGRAM RESTARTED MAY

U477 - SOLVE YOUR PROBLEM.

U499 - MAXIMUM INSERT CALL COUNT EXCEEDED. A "A7" STATUS IS RETURNED

U499 - CHECK APP. PGM AND MAKE SURE IT RECOGNIZES A7 OR INCREASE THE

U499 - 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 WITH

U502 - PIC S9(04) COMP AND IT SHOULD HAVE BEEN

U502 - PIC S9(09) COMP

U513 - IF ISRTING A MSG TO A PRINTER INCLUDE A OUTBUF=9000 ON YOUR

U513 - ./D CARD WITHIN YOUR BTS CONTROL CARDS. BE SURE TO USE THE

U513 - "MDL" OPTION WITH "P1" OR "P2" IF YOU ARE NOT USING MFS OR

U513 - "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 THE

U551 - 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 USE

U662 - 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. IMS

U688 - CONTROL REGION NOT ACTIVE.

U688 - OPERATOR CANCEL. IMS IS DOWN.

U688 - IF RUNNING TESTBTCH OR MDLDBTCH ON SYSTEM N, MUST HAVE A

U688 - SYSAFF=AHI7 ADDED TO THE JOB'S JOBPARM STATEMENT.

U717 - REGION SIZE POSSIBLY TOO SMALL.

U722 - CANCELLED BY OPERATOR - LINES PRINTED EXCEEDS LIMIT

U742 - PROBLEM WITH IMS ** CALL IMS GROUP OR ABENDS

U752 - AN ISAM SETL MACRO CALL WAS ISSUED SPECIFYING THE KEY WHICH

U752 - INITIATES THE DATA SET. A MESSAGE WAS RETURNED WITH THE NEXT

U752 - HIGHER KEY IN THE DATA SET, INDICATING THAT THE ERROR CONDITION

U752 - WAS NOT FOUND. A SECOND SETL ALSO FAILED BECAUSE OF THE ERROR

U752 - NOT BEING FOUND. THE SECOND SETL MAY HAVE FAILED BACAUSE THE

U752 - DATABASE WAS NOT COMPLETELY LOADED OR BECAUSE THE DD STATEMENT

U752 - 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 YOUR

U775 - CHECKPOINT COUNT IN THE PROGRAM CAUSING THE ABEND.

U777 - SEE U777

U777 - IMS CHOSE YOUR PGM TO TERMINATE TO AVOID A DEADLOCK. HAVE JOB

U777 - RESTARTED.

U778 - AN SQL ERROR OCCURED AND THE ABORT ROUTINE WAS CALLED. THE

U778 - ABORT ROUTINE ISSUED A ROLLBACK COMMAND WHICH GIVES THE

U778 - U778 CODE. TO SEE THE REAL SQL CODE IN ERROR VIEW DATASET

U778 - PRPAC.DBAUF.ABORTTEST(0) THE DAY AFTER THE ABEND, OR CALL

U778 - 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 CHECKPOINT

U80A - REGION SIZE TOO SMALL

U801 - DATABASE NOT OPENED FOR UPDATE.

U806 - INVALID RETURN FROM BUFFER HANDLER.

U806 - (GSAM NAME) GSAM DBD IS NOT PRESENT OR THE ACB GEN WAS NOT

U806 - 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 JCL

U840 - THERE IS A PROBLEM WITH A BMC PRODUCT THAT UTILIZED

U840 DATA PACKER. CONTACT DBA! THIS IS NOT A PROGRAM PROBLEM.

U844 - NOT ENOUGH SPACE ON DATABASE

U844 - NO AVAILABLE SPACE IN DATA SET -- DATABASE FULL

U844 - DATABASE MAY BE FOUND IN I.OLSJIM15(IMSTEST) (HARDCPY1), MAX. TO THE

U844 - 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 FILE

U852 - DATA BASE BAD.

U852 - BAD POINTER - DAMAGED DATABASE - WRONG DBD BEING USED

U853 - 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 SERIOUS

U888 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 USING

U999 - A ROUND TAPE DRIVE (UNIT=TAPE9) AS AN OUTPUT FILE, THE

U999 - PROBLEM COULD BE BECAUSE THE TAPE DRIVE IS DIRTY. HAVE

U999 - AUBURN HILLS CLEAN THE TAPE DRIVE AND TELL YOUR SUPERVISOR!!!!

U999 - IF USING PGM SSGPXLBL, MAKE SURE DSNAMES IN JCL MATCH DSNAMES

U999 - IN SYSIN CARDS.


U0016 - CONCAT. DATA SETS ON A SORT. FIRST DATA SET DOES NOT CONTAIN THE

U0016 - LARGEST BLOCKSIZE.

U0016 - JOB REQUIRES MORE SPACE TO EXECUTE.

U0016 - SYSIN * ON A SORT MAY HAVE TOO MANY ENTRIES.


U0016 - IF USING SYNCSORT, CHECK 'SYSOUT' MESSAGES WITH SYNCSORT MANUAL

U0016 - SYNCSORT: CHECK LRECL OF SORTIN AND SORTOUT FILES.

U0016 - SYNCSORT: USE PARM VLTEST=0 SO WON'T VERIFY THE LRECLS

U0102 - SEE U102

U0211 - JCL IN 'ALWAYS LOAD' DATASET, BUT NO PROC IN CHAMP

U0250 - ONE OR MORE DATASETS NOT CLOSED AT THE END OF THE PROGRAM.

U0271 - SEE U271

U0428 - SEE U428

U0457 - SEE U457

U0474 - SEE U474

U0688 - SEE U688

U0777 - SEE U777

U0844 - SEE U844

U0999 - SEE U999

U1002 - I/O EXCEPTION-CHECK TO SEE IF RECORD LENGTH IN PROGRAM AND

U1002 - 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 LINK

U1005 - OR, IN COBOL A RECENT COMPILE (AFTER 7/90) HAS MIX OF RES/NORES

U1012 - PROGRAM STOPPED BEFORE SORT WAS FINISHED, CHECK TO SEE IF

U1012 - 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 THE

U1033 - DEPENDENT REGIONS JCL. IF A TRANSACTION THEN ASSIGN TO A DIFFERENT

U1033 - 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 ALLOWED

U3303 - THIS USER ABEND BASICALLY MEANS THAT ONE OF THE APPLICATION

U3303 - DATA BASES IN YOUR PSB IS STOPPED. WHEN YOUR APPLICATION

U3303 - 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 NOT

U3303 - 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 UPDATES

U3560 - 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 AGAINST

U3560 - FAST PATH DATABASES.

U3561 - MAY NEED TO CHANGE DBD IN DVAN SEGD HEADER RECORD TO POINT

U3561 - 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 BUT

U3592 - I HAD FAILED TO SPECIFY 'Y' AT 'FAST PATH DB'S?' PROMPT.

U1006 - JOB IS ASKING FOR MORE FAST PATH BUFFERS (NBA) THAN IS CURRENTLY

U1006 - AVAILABLE - USE IMS COMMAND "/DIS POOL FPDB" AND LOOK AT

U1006 - "UNFIXED" TO DETERMINE HOW MANY BUFFERS ARE CURRENTLY AVAILABLE.

U1006 - YOU MUST THEN REDUCE THE JOB NBA PARAMETER TO REQUEST NO MORE

U1006 - THAN WHAT IS "UNFIXED" OR WAIT FOR OTHER JOBS TO END AND THUS

U1006 - FREE UP MORE BUFFERS........ RFS 2/6/90

U1008 - SYNC CALL HAD TO BE MADE AT END OF RUN. THIS IS

U1008 - FOR EITHER AN UPDATER OR AN INQUIRY BMP.

U1008 - FOR IFP MESSAGE DRIVEN APPLICATION PROGRAMS AND MPPS

U1008 - PROGRAM RETURNED NORMALLY BUT WITHOUT A QC STATUS CODE

U1008 - POSTED IN I/O PCB OR WITHOUT RELEASING FAST PATH BUFFERS.

U1008 - SOLUTION: RETURN CONTROL TO IMS ONLY AFTER A QC STATUS CODE

U1008 - IS RETURNED IN I/O PCB OR AFTER ISSUING A SYNC OR ROLB CALL TO

U1008 - RELEASE BUFFERS.

U1016 - DD CARD IN THE JCL IS MISSING

U1017 - PSB IS MISSING OR DOES NOT MATCH THE PROGRAM

U1017 - DD CARD IN THE JCL IS INCORRECT

U1017 - FOR COBOL -- OPEN OF DISPLAY/ACCEPT FILE WAS UNSUCCESSFUL. CHECK

U1017 - TO SEE IF THE DDNAME IS SUPPLIED IN THE JCL OR CLIST

U1017 - IF RUNNING BTS YOU NEED A "SYSOUT(D)" ON THE PROC LINE OF YOUR

U1017 - BTS CLIST

U1020 - THE PROGRAM TRIED TO READ PASS THE END OF FILE

U1020 - MARKER ON THE INPUT RECORD

U1020 - THE PROGRAM TRIED TO CLOSE AN UNOPENED FILE

U1020 - THE PROGRAM TRIED TO OPEN AN ALREADY OPENED FILE

U1020 - FOR GSAM FILE, MAKE SURE THE DCB IS INCLUDED ON

U1020 - THE INPUT DD STATEMENT

U1020 - ADD SORTWK DD STATEMENTS TO JOB STEP USING PRINT

U1020 - UTILITY (DMGPRPT).

U1020 - THE PROGRAM ABENDED ON A CLOSE STATEMENT BECAUSE

U1020 - THERE WAS NOT ENOUGH SPACE IN THE FILE FOR EOF MARK

U1034 - FILE SECONDARY ALLOCATION LIMIT ENCOUNTERED.......

U1035 - WRONG DDNAME IN JCL OR IN COBOL-FD IS MISSING BLOCK CONTAINS

U1035 - OR, AN OPEN ERROR HAS OCCURED. THIS MAY BE BECAUSE YOU ARE

U1035 - PROCESSING A VARIABLE BLOCKED FILE AND THE RECORD LENGTH IN

U1035 - YOUR PROGRAM FD DOES NOT MATCH THE VB FILE'S LRECL MINUS FOUR

U1035 - OR, CHECK JCL FOR IMPROPER RECORD LENGTH

U1320 - ERROR WRITING CHECK POINT, INCREASE REGION ON STEP OR JOB

U1055 - DD NAME IS MISSPELLED OR MISSING

U1525 - NOT CAT2 CONDITION DURING A CHECK POINT/RESTART EXECUTION

U1806 - CHECK THE GSAM FILE NAME MATCES DD NAME IN JCL

U2047 - 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 RELOAD

U2749 - BMC2749, OPEN FAILURE ON DDNAME ' '.

U2871 - REGION SIZE IS NOT LARGE ENOUGH - INCREASE IT

U3001 - 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-AID

U3007 - 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 MEMBERS

U3007 - IN DATASET AND RETRY.

U3300 - STORAGE SPACE FOR DATABASE ENQUEUES HAS BEEN FILLED UP. ALL

U3300 - IMS PROGRAMS CURRENTLY RUNNING WILL ABEND. CAUSE IS: AN UPDATE

U3300 - BMP IS NOT CHECKPOINTING FREQUENTLY ENOUGH. THE SYSTEM DOES NOT

U3300 - IDENTIFY WHICH BMP IS AT FAULT. OLD ABEND CODE WAS U775.

U3303 - INSTEAD OF U458 WHEN PROGRAM IS ACCESSING A

U3303 - DATABASE THAT HAS BEEN STOPPED. TRAN PUT ON

U3303 - SUSPEND QUEUE. DO A /STA TRAN COMMAND AFTER

U3303 - DATABASE IS BACK UP

U3500 - GENERIC USER ABEND CODE USED FOR PROGRAMMER FORCED ABENDS

U3500 - CHECK SYSOUT FOR DESCRIPTIVE ERROR MESSAGES DISPLAYED BY PROGRAM

U3500 - REPLACEMENT OF THE COMPUTE XXX = 1 / 0 STATEMENT

U3501 - INVALID PARM LENGTH OR VALUE

U3502 - ERROR DETECTED BUT NO ABEND; RETURN CODE SPECIAL

U3502 - REGISTER SET TO 3502 AND INTERROGATED IN THE

U3502 - JCL TO EXECUTE WAASABND.

U3503 - ENCOUNTERED STOP AND/OR ACCEPT STATEMENT

U3504 - AFTER ANY INVALID RETURN CODE FROM "WAASDYN"

U3505 - WHEN THE CHECKPOINT LIMIT RECORD IS INVALID

U3506 - RESERVED AS THE STANDARD JCL PARM= VALUE FOR

U3506 - PROGRAM "CURPB002"

U3507 - INVALID SQLCODE VALUE AFTER EXECUTION OF ANY SQL

U3507 - CODE IN TSO BATCH DB2 APPLICATION PROGRAMS

U3508 - USED BY CURSU002 (DATE/TIME) WHEN A BAD RETURN

U3508 - 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 - ISSUED

U3511 - BY S9999-ABORT-ROUTINE FOLLOWING A ROLB CALL

U3512 - DATA SET EMPTY

U3513 - SSDPDB2Q - INVALID FUNCTION CODE PARM

U3514 - SSDPDB2Q - UNSUCCESSFUL DEQUEUE

U3515 - ANY NON-DATABASE RELATED TPS ERROR IN TSO BATCH

U3515 - APPLICATION PROGRAMS

U3516 - BAD RETURN FROM CURSU002 IN CAL-DATE CALL

U3516 - REPLACEMENT.

U3517 - RETURN CODE INDICATING AN UNSUCCESSFUL CALL

U3517 - TO WAASCTLM.

U3518 - INTERNAL TABLE LIMIT EXCEEDED.

U3501 - GENERIC USER ABEND CODE USED FOR PROGRAMMER FORCED ABENDS

U3501 - CHECK SYSOUT FOR DESCRIPTIVE ERROR MESSAGES DISPLAYED BY PROGRAM

U3506 - NO TIE CONDITION FOR ELECTRONIC TIEINS

U3514 - BAD RETURN FROM ISRT TO RI7ORDR

U3516 - BAD RETURN FROM GHU TO RI7PRGM

U3550 - BAD RETURN FROM CHKPT/RSTR CALL TO COCSS03

U3599 - BAD RETURN FROM DB CALL

U3600 - BAD RETURN FROM OPEN OF GSAM FILE

U3604 - THE ABEND-CODE SENT TO WAASABEND WAS TOO HIGH

U3604 - ONLY 1 THRU 4905 IS ACCEPTABLE

U3650 - BAD RETURN FROM CLOSE OF GSAM FILE

U3700 - BAD RETURN FROM READ OF GSAM FILE

U4000 - CHECK DISPOSITION OF FILES BEING USED FOR POSSIBLE NOT-CATLG-2

U4000 - ERROR WITH FIRST XRST CALL TO CHECKPOINT.

U4002 - PSB AND CONTROL NUMBER DO NOT MATCH

U4002 - 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 UPDATE

U4011 - JOB WAS RUNNING. PLEASE FOLLOW RESTART INSTRUCTIONS AFTER

U4011 - 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 PSB

U4032 - 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 A

U4036 - 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,BLKSIZE

U4036 - 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 WAS

U4078 - 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 EXCEPTION

U9999 - DUMMY

0002 - (ONCODE) RUNTIME ERROR FROM IMS TEST REGION BEING CANCELLED.

0003 - (ONCODE) ATTEMPT MADE TO EXEC STMT DIAGNOSED IN ERROR AT COMPILE TIME

0009 - (ONCODE) SIGNAL ERROR INSTRUCTION, USER 3001.

0042 - (ONCODE) POSSIBLE BAD DATA.

0093 - (ONCODE) POSSIBLE CAUSE: INSUFFICIENT REGION,

0093 TRY INCREASING REGION

0093 - VSAM FILE STATUS 2 CHAR. RETURN CODE. IF FILE WITH BAD RETURN

0093 CODE IS NOT ALLOCATED TO AN ONLINE REGION, AND PROGRAM IS

0093 COBOLII, CHANGE RECORD CONTAINS CLAUSE IN FD FROM '0' TO THE0093 ACTUAL LRECL OF THE FILE.

NOTES - (Q) HOW CAN A DATASET CHANGE FROM FB TO VB IF IT WAS NOT REALLOCATED?

NOTES - 1. THE 'PRINTER SOFTWARE' NEEDS TO BE UP GRADED TO A CURRENT RELEASE.

NOTES - EXAMPLE FOUND IN PRODUCTION: PRINTER IN CUSTOMER AREA WAS RUNNING

TPROC - TO USE SYS4.TEST.PROCLIB AND SYS3.CHAMP.TESTPROC -- JCL SHOULD READ

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 GREATER

S837 OUTPUT DD RECORD VOL=(,,,XX). XX= MAX NUMBER OF OUTPUTS EXPECTED OR 99.

U100 - WRONG USER CODE GENERATED BY PROGRAM. CHECK PROGRAM FOR PROBLEM

U102 - TO RESTART >>>>>>>>>>DO NOT CHANGE JOB NAME ON RESTART<<<<<<<<<<

U261 - PROGRAM TO IMS/VS IS INVALID. IT EITHER EXCEEDS OBJ MACH SIZE,DOES NOT

U261 - MEET ALIGNMENT REQUIREMENTS, OR VIOLATES STORAGE PROTECTION BOUNDS

U3560 - YOU MAY NEED TO ADD THE PARMS "NBA=4 AND OBA=4" IF PROCESSING AGAINST

0003 - (ONCODE) ATTEMPT MADE TO EXEC STMT DIAGNOSED IN ERROR AT COMPILE TIME

ims abend codes

Documents