Showing posts with label Interview Questions. Show all posts
Showing posts with label Interview Questions. Show all posts

cics abend:

ABENDS

ABEND code index Find name
1. User codes USECD
2. System codes SYSCD
3. Return codes RETCD
4. File status codes STACD
5. SQL codes SQLCD
6. Misc codes/msgs MISCD
7. CICS codes CICSCD
8. IMS codes IMSCD

----------------------------------------------------------------------
USECD - User codes
----------------------------------------------------------------------
U0001 - CHECK FOR WRONG BLOCKSIZE.

U0002 - IMS PROBLEM - CALL OPERATION TO CHECK ON STATUS. IMS CRASHED.

U0016 - IN UCC11 STEP - TRYING TO RESTART NON-RESTARTABLE STEP.
IF JOB HAS STARTED AND HAS SORTWORKS IN THE STEP ABENDING
TRY INCREASING THE SORTWORKS & RESTARTING THE JOB.

U0016 * PROBABLE SORT CAPACITY EXCEEDED. (MAX TO BOT OF JOBLOG)
* IF EXECUTING SORT W/ PARM=MAXSORT AND JOB ABENDS WITH SORTOUXX
DEVICE MIXING PROHIBITED, CHANGE THE SORTOU00 DD DSN'S TO
UNIT=CTAPE AND RESTART. THIS ABEND CAN OCCUR UNTIL DASD
CONVERSION IS COMPLETE, ABOUT THE 1ST OF NOV. 92.

U0016 * BLOCKSIZE ON INPUT FILE SHOULD BE OMITTED.

U0020 - IN UCC11 STEP - DATA SETS USED FOR RESTART DIFFER FROM PRODUCTION
RUN. TRY CANCELLING ABENDED JOB, DEMAND JOB IN ON HOLD, TYPE=
RES, EDIT JCL, SATISFY HOLD REQUIREMENT TO RESTART. FOR I/P
GDG CHANGE, USE BYPGDG: YES FIELD ON RESTART SCREEN.

U0040 - IN UCC11 STEP - INCORRECT STEP RESTARTED, IMPROPER OR
IMCOMPLETE STEP NAME.

U0046 - PROBABLE PSB PROBLEM - READ VS UPDATE - CALL DBA ON CALL.

U0064 - IN THE UCC11 STEP = CMT NOT CORRECT (GDG PROBLEM). THERE IS NO
GDG BASE RECORD OR JOB IS CALLING ON A (0) GENERATION BUT THERE
ARE NO GENERATIONS CATALOGUED.
ALSO CAN BE DEADLOCK, CHECK SQLCODE, TRY RESTARTING.

U0102 - PROBABLE IMS PROBLEM, TRY RESTARTING.
- 10/31/92 U0102 IMSLOGR DD STATEMENT MISSING - WHEN EXECUTING
CICSBTPH. DELETED STEPLIB DD PER KOSKI TO RUN. YOU COULD
SUGGEST THIS TO DEV.

U0109 - CHECK FOR SQL CODE.

U0175 - DEADLOCK / CONTENTION.

U0200 - CHECK SQL CODE IN ABENDED JOB.

U0240 - A message processing application program exceeded the
allowable execution time (set at IMS system definition) in a message
processing region. In the case of a BMP, this abend indicates that the
value specified in "CPUTIME=" has been exceeded.

System Action: A storage dump is taken and the dependent region program
controller is reattached. In the case of a BMP step, the step is
terminated.

Programmer Response: Refer to the TRANSACT macro in IMS/ESA System
Definition Reference.

U0246 - ???

U0261 - INCORRECT PARM IN DL/I CALL.

U0271 - I/O ERROR DETECTED WHILE PURGING BUFFERS DURING CKPOINT OPERATION

U0273 - I/O ERROR DETECTED WHILE REPOSITIONING A GSAM DATASET DURING RESTART.
resolution: TRY BY GIVING OPTION AS COLD=COLD AT THE EXEC STEP.

U0295 - SORT-X PROGRAM LOADED USING WRONG EXECUTE.

U0304 - The caller passed a non-zero value in register 1.

U0311 - A reserved field is not equal to 0 in one of the 20-byte
description elements in the entry table description (ETD).
Register 2 contains the entry index associated with the
description element.

U0312 - The program identified in one of the 20-byte description
elements could not be found. Register 2 contains the entry
index associated with the description element.

U0313 - The entry indexes are not in ascending order. Register 2
contains the entry index that was not in ascending order.

U0314 - A job step attempted to issue an ETCRE macro, but a prior job
step owned space-switch entry tables. (Subsequent job steps
are not permitted to issue PC/AUTH macros.)

U0402 - PROBABLE IMS PROBLEM, TRY RESTARTING.

U0428 - PSB NOT DEFINED AS AN IMS BMP/CONTACT DBA IN MORNING.

U0437 - APPLICATION GROUP NAME OR RESOURCES SPECIFIED ARE NOT VALID
FOR DEPENDENT REGION

Resolution : MAY NEED 'AGN=' PARAMETER, SEE MEMBER '#RACF' in IFP.PROB.RES.DOC.

U0452 - PSB CONTENTION / 2 DB JOBS DEALLOCATING AT SAME TIME.
IF YOU GET MORE THAN 2 U0452 ABENDS, RESTART THE TRANSACTION
(SIGN ON IMS AND /STA TRAN DB????CP) (SAME NAME AS PSB)

U0456 - PSB IS STOPPED, /STA PROG ALL, STARTS ALL STOPPED PSB'S.
SEE 'CMISCOP.UCC7.SCHEDULE(CA7OS) FOR HOW TO DISPLAY IMS INFO.

U0458 - DATABASE IS STOPPED/CONTACT DBA ON CALL, UNLESS B/U'S ARE RUNNING.

U0474 - CANCELLATION OF JOB THROUGH /STOP REGION ABDUMP

U0476 - PSB OR PCB PROBLEM - CALL PROGRAMMER.

U0519 - ??????????

U0522 - JOB TIMED OUT WAITING FOR A TAPE MOUNT.

U0688 - LOST IMS FROM THE MIX, CHECK WITH OPERATIONS ON STATUS.
Resolution : Try by changing the CLASS .
May be the problem with CLASS and IMS Proc combination
( Ex : I0012 , I0010 ......). Change class to 0 ( ZERO ) and try .

U0755 - ???

U0775 - ISOLATION DEADLOCK - CONTENTION TRY RESTARTING 3 OR 4 TIMES,
BEFORE CONTACTING CARDS ON CALL FOR THE JOB.
1 TIME IN 10,000 TOTAL MIX HAS CAUSED THE POOL TO BE FILLED
MORE TIMES THAN NOT A PROGRAM HAS GONE BESERK, NOT CHECKPOINTING
OR NOT CHECKPOINTING ENOUGH. LENGTH OF TIME TO BACK OUT SHOULD
BE A POINTER TO THE PROBLEM JOB.

U0777 - IMS CONTENTION/RESTART JOB LATER.

U0811 - POINTER PROBLEM.

U0844 - DATA BASE IS FULL, NOTIFY DBA.

U0849 - NOT LISTED IN IMS MSG & CODES, BUT A RESTART CAN WORK
- AN 849 ABEND IS CAUSED BY AN ILLEGAL DATASHARE OF A DATABASE.

U0850 - DATA BASE ERROR, NOTIFY DBA.

U0852 - DATABASE POINTERS OUT OF SYNC - CALL DBA ON CALL - TRY RESTART FIRST.

U0918 - ?

U0999 - GENERALLY A RACF ABEND, BUT CHECK FOR OTHER MESSAGES IN OUTPUT.

SG90214P FLAGS A U999, BUT IS ACTUALLY A B37 IN SAS STEP:

SASB#001 EXEC SAS,SORT=300,WORK='999,999',OPTIONS= ETC.
INCREASE SPACE SHOWN BELOW IN WORK PARM.

SASB#001 EXEC SAS,SORT=300,WORK='1500,1500',OPTIONS= ETC.

U0853 - DATA BASE ROOT PROBLEM/ (CC14533P RUNNING)?? TRY RESTARTING.

U1000 - ???

U1002 - : A storage allocation failure occurred during initialization.
The system attempted to allocate storage for the main NPM control blocks,
but insufficient storage was calculated by FNMIN0S0.

U1003 - ???

U1020 - The Fast Path asynchronous task has terminated abnormally,
and this abend is issued to stop the rest of the IMS system.

System Action: IMS terminates abnormally.

Programmer Response: Correct the problem, and rerun the job.

System Operator Response: Contact the IMS system programmer.

U1035 - DCB=DBLKSIZE=___ NOT SPECIFIED ON A DUMMY DD STMT

U1100 - CONTENTION.

U1234 - ???

U1250 - ????

U1302 * ALL RECORDS WERE'NT RETURNED FROM SORT, TRY BIGGER REGION. 4096K O

U1311 - POSSIBLE REGION SIZE ERROR - INCREASE REGION SIZE ON EXEC STATE. 4096K O

U1320 - POSSIBLE REGION SIZE ERROR - INCREASE REGION SIZE ON EXEC STATE. 4096K O

U1807 - CHECK FOR SQL CODE

U2300 - ????????

U2478 - SEVERAL JOBS ABENDED W/THIS 03/20/92, CAUSED BY TRANS PUTTING
- MESSAGE ON QUEUING THAT HAD ONE LINE EOT. CAUSED TEMP STORAGE
- TO FILL; RECOVERY TOKEN KEPT CHANGING. JASON BUTLER HAD TO
- DELETE RECORD OFF QUEUING DATA BASE.

U2486 - TO MANY WAITING PST'S (60 LIMIT) JUST RESTART JOB.

U2860 - POINTER ERROR PER CHUCK WISE (04/15/90). KDF.

U3300 - D/B PROBLEM, IRLM IS FULL, PROBABLY CAUSED BY ANOTHER JOB
RUNNING AND NOT CHECKPOINTING ENOUGH. TRY RESTARTING.

U3300 - (SEA-LAND) JOBNAME FOR THE JOB EXECUTING 'UTILWTOR'IS NOT ON
- THE UTILWTOR TABLE IN PROD.CTLIB.

U3303 - USUALLY DUE TO LOSING A CICS - RESTART THE STEP AFTER REGION UP.
COULD INDICATE A STOPPED DATA BASE PER D. DAVIES.

U3505 - TRYING TO CLOSE A CLOSED FILE OR OPEN AN OPENED FILE.

U3601 - LIBRARY POINTED TO BY IMS DD STATEMENT COUNT NOT BE OPENED

U3602 - BLDL REQUEST FAILED FOR THE SPECIFIED PSB.

U3603 - REQUESTED PSB COULD NOT BE LOADED

U3604 - ERROR WAS DETECTED DURING GSAM INITIALIZATION

U3604 * MISSING DD NAME ON GSAM FILE.

U3610 - THE COUNT FIELD IN THE USERS PARAMETER LIST IS INVALID

U3611 - ADDRESS FOR GSAM,PCB IN USERS PARAMETER LIST INVALID

U3612 - ERROR DETECTED DURING EXTENDED CHECKPOINT CALL PROCESSING

U3613 - ERROR DETECTED DURING USERS CALL TO A GSAM DATABASE

U3614 - ERROR WHILE PURGING GSAM BUFFERS DURING CHECKPOINT PROCESSING

U3620 - ERROR IN RECURSIVE CALL TO CADDRPE DURING EXTENDED RESTART

U3707 * CICS NOT AVAILABLE

U3708 * NO THREADS AVAILABLE

U3710 - BAD INPUT

U3710 * CHECK SPIE AREA;
SPIE 0007 DATA EXCEPTION
SPIE M004 ADDRESS EXCEPTION
SPIE 0001 PSB ERROR, USE WRONG PROC ON SHR/BTCH COMPILE

U3714 - MIRROR TASK ABEND
* ATCH- SYSTEM HUNG SO IT DUMPED PGM, TRY AGAIN
* AXFN- NO PGM GEN FOR PSB, OR USED PROD PSB IN TEST
* 775 - ENQUE FILE FULL
* 828 - INSERTING A DUPLICATE SECONDARY INDEX, DBA CAN FIX
* 844 - DATABASE IS FULL, CALL DBA
* 850 - DATABASE POINTERS ARE BAD, CALL DBA

U3717 * PCB NOT DEFINED IN PSB.

U3718 * NO FUNCTION CODE.

U3723 * REASON=801 PSB NOT IN ACB LIBRARY.
REASON=805 PSB NOT SCHEDULED/ DB NOT AVAILABLE
REASON=828 TRYING TO INSERT DUPLICATE SECONDARY INDEX
REASON=8FF DLI NO ACTIVE.

U3734 * INCREASE REGION

U4015 - BAD GNP CALL (GET NEXT PARENT)

----------------------------------------------------------------------
SYSCD - System codes
----------------------------------------------------------------------
SA14-04 MAY BE CONTENTION - TRY RESTARTING ONCE ACCORDING TO INSTRUCTION

SA78-10 MAY BE CONTENTION - TRY RESTARTING ONCE ACCORDING TO INSTRUCTION.

SA0A * INACTIVE PGM OVERRIDES FREE AREA, AREA TO BE RELEASED OVERLAPS
* A FREE AREA.
* INITIATOR FAILURE.

SB0A * COBOL - CONTROL PASSED BEYOND END OG PGM DUE TO INVALID PERFORM.

SB14 * ERROR ATTEMPTING TO CLOSE A PDS OPENED FOR OUTPUT TO A MEMBER.
* THE STOW ROUTINE, WHICH PLACES THE MEMBER NAME IN THE DIRECTORY
FAILED BECAUSE NO SPACE WAS LEFT IN THE DIRECTORY OR THE NAME
ALREADY EXISTS OR AN INCORRECTABLE I/O ERROR OCCURED.
* AN ATTEMPT IS BEING MADE TO ALLOCATE A PDS AND ADD A MEMBER
FROM AN INVALID COBOL COMPILATION.

SB37 - SPACE - NEED TO INCREASE SPACE ON THE SORTED OUTPUT DATA SET.
* ALSO CAN MEAN IT COULDNT FIND ENOUGH SPACE ON THE VOLUME TO
* ALLOCATE THE 15 EXTENTS OF SECONDARY.
* IF JOB HAS THIS TYPE OF JCL - EXEC SORT,REGION=2M,PARM='CORE=
500K',CYL=50, AND JOB FAILS WITH RC16, INCREASE SORT SIZE BY
IN CYL=XX TO INCREASE THE SORT WORK SIZE. THERE WILL BE NO SORT
WORKS IN THE JCL ITSELF TO INCREASE.
* SOME DM* JOBS ALLOCATE SPACE IN KILOBYTES IE
SPACE=(1,(1500,500)),AVGREC=K

SC03 - USER FILE HAS NOT BEEN CLOSED, NOTIFY DESIGNER.
* FILE STATUS=92 OPENED FILE, DIDNT READ, TRIED TO REWRITE.

SC13 * ERROR DURING OPEN PROCESSING. AN I/O ERR WAS FOUND OR THE SVC
* ROUTINE WAS UNABLE TO LOCATE A CONCATENATED PARTITIONED DATASET.
* THIS COULD BE AN ATTEMPT TO OPEN CONCAT. PDS FOR OUTPUT.
* IT COULD ALSO BE THE FORMAT 1 DSCB COULD NOT BE LOACTED IN THE
* VTOC OF THE DASD REFERENCED.

SC78 - NOT ENOUGH C-POOL AVAIL NOT ENOUGH VIR STORAGE AVAIL.

SD00 * NEEDS LARGER REGION.

SD37 * MORE SPACE NEEDED IN SPACE PARM. THERE WAS NO SECONDARY SPACE
* SPECIFIED.

SE37 - SPACE PROBLEM - IF DSN IS A FOCUS D/S - TRY COMPRESSING THE DSN
THRU 3.1.
* THIS RESULTS WHEN AN OUTPUT PDS FILLS UP ITS SPACE. IT ALSO
* HAPPENS WHEN THE PDS CANT ACQUIRE ITS 15 EXTENTS ON ONE VOLUME.
* A PDS CAN NOT SPAN MORE THAT ONE VOLUME.
SFFF PROBABLE CONTENTION - RESTART JOB

SF13 * A SUPERVISOR CAL (SVC) INSTRUCTION CONTAINED AN INVALID OPERAND
* OR THE SVC INSTRUCTION CALLED WAS NOT INCLUDED IN THE OPERATING
* SYSTEM. THIS OCCURS DURING OPEN PROCESSING. IT COULD BE A PDS
* MEMBER COULD NOT BE FOUND, OR CONFLICTING OR MISSING DCB PARMS.
* INVALID PARMS PASSED TO SUPERVISOR CALL ROUTINE.

SF22 * I/O TIME ESTIMATE EXCEEDED.

SF2D * OVERLAY SUPERVISOR - INVALID SUPERVISOR CALL
* BAD LOAD MODULE, RE-LINKEDIT MODULE.

SF37 * INPUT/OUTPUT ERR IN END-OF- VOLUME PROCESSING OR END-OF-VOLUME
* COULD NOT FIND A REQUIRED DATASET CONTROL BLOCK(DSCB). IT COULD
* BE NO DSCB COULD BE FOUND FOR A CONCATENATED DSN ON DASD, OR
* AN INVALID PARM WAS PASSED TO END-OF-VOLUME SVC (SVC 55). IT
* COULD ALSO BE AN I/O ERROR READING A FORMAT DSCB OR READING
* VOLUME LABEL ON THE SECOND VOLUME.

S001 - I/O ERROR
* WRONG LENGTH RECORD OR PHYSICAL BLOCK
* NO END OF FILE MARKER
* ATTEMPT TO READ RECORD AFTER END-OF-FILE CONDITION FOUND
* HARDWARE ERROR
* TRIED TO WRITE ON AN INPUT FILE
* INCORRECT USE OF BLOCK CONTAINS CLAUSE - COBOL
* SECONDARY SPACE TO SMALL- (LIKE SB37)
* TAPE BEING READ IN WRONG DENSITY
* TRTCH PARM WAS WRONG
* RECFM V IS INCOMPATIBLE WITH TRTCH ET

S001 * IF USING VSAM FILES IT COULD BE ONE OF THE FOLLOWING:
1) NO INVALID KEY CONDITION ON RANDOM PROCESSING.
2) KEY IS WRONG IN THE FD STATEMENT.

S001-1 WRONG RECORD LENGTH OR BLOCKSIZE.

S002 - RECORD LENGTH--ALSO CHECK FOR SQL CODE IN OUTPUT.

S002-OC FILE BLOCKED TOO LARGE, EXCEEDS TRACK CAPACITY.
* WRONG RECFM OR BLOCKSIZE IN JCL

S013 - CONFLICTING OR UNSUPPORTED PARAMETERS IN DCB
* BLOCKING IN PROGRAM=0; MUST HAVE BLOCKSIZE IN JCL.
* FILE LENGTH DIFFERENT THAN DEFINED IN PROGRAM
* MEMBER NAME SPECIFIED IN DD COULD NOT BE FOUND.
* NO BLKSIZE/DCB SPECIFIED FOR A DUMMY DD.
** WHEN EXECUTING IEBGENER WITH SYSUT1 IS DD DUMMY, FOLLOWED BY

SYSUT2 CREATING NEW DS, THE DCB INFORMATION MUST BE IDENTICAL.
* JCL - TRIED TO CREATE A PDS WITHOUT ALLOCATING DIRECTORY BLOCKS

S013-18 CANNOT FIND FILE, MAYBE EXECUTING WRONG PGM.
* CANNOT FIND FILE LARGE, EXCEEDS TRACK CAPACITY

S013-20 BLKSIZE NOT A MULTIPLE OF LRECL OR WRONG DSN.

S013-60 NEED 'FB' IN DCB (RECFM=FB)

S016 - SORT-X PGM; JCL DOES NOT CONTAIN SORT FIELDS

S031 - I/O ERROR UNDER - PHYSICAL DAMAGE TO RECORDING MEDIUM
INDEXED SEQUENTIAL - OUT OF SEQUENCE KEY WHEN LOADING AN
ACCESS (QISAM) ISAM DATA SET
- WRONG LENGTH RECORD OR BLOCK

S03A - INCREASE REGION

S03B - ERROR IN OPEN - DATA SET HAD NOT BEEN CREATED
PROCESS FOR AN - DATA CONTROL BLOCK HAD NOT BEEN CLOSED
INDEXED SEQUENTIAL AFTER DATA SET CREATED
DATA SET - ERROR IN LRECL OR BLKSIZE

S03D - ERROR IN OPEN - INDEXED SEQ ORGANIZATION NOT SPECIFIED
PROCESS FOR AN IN DSORG OF DCB, REQUIRED EVEN IF
INDEXED SEQUENTIAL SPECIFIED IN SOURCE PROGRAM
DIRECT DATA SET - NOT ALL VOL-SER NUMBERS SPECIFIED OR
INCORRECT SEQUENCE

S04E - CONTENTION WITH ANOTHER JOB. - - - WHEN THE JOB IS A DB2 IMAGE
COPY RESTART THE JOB FROM THE TOP ONLY WHEN THE MESSAGE AT THE
BOTTOM OF OUTPUT READS RESOURCES UNAVAILABLE....JOYCE DILVER....

S062 - RETURN CODE EQUAL TO OR GREATER THAN VALUE OF NULL ARGUMENT PRODUCED

S0B0 - I/O ERROR ON SYSTEM JOB QUEUE

S0C1 - OPERATION EXCEPTION
* A MISSING OR MISSPELLED DD.
* DATASET WAS OPEN OR CLOSED WHEN AN INPUT/OUTPUT INSTRUCTION
* WAS ISSUED FOR IT. IT SHOULD HAVE BEEN THE OPPOSITE.
* BAD LOAD MODULE OR OBJECT DECK.
* FORTRAN- MISSING DIMENSION STATEMENT, SAME NAME FOR ARRAY AND A
* SUBROUTINE.
* COBOL- USING SORT VERB, DDNAME WAS NOT SORTOUT WHEN THE GIVING
* OPTION WAS USED.
* COBOL- SUBROUTINE PROG ID WAS THE SAME AS THE ENTRY NAME.
* COBOL- TRIED TO CALL WITHIN COBOL F SORT I/O PROCEDURE.
* COBOL- TRIED TO CALL A SUBROUTINE WHICH COULDNT BE FOUND.

S0C2 - PRIVILEGED OPERATION EXCEPTION
* COBOL- MISSING PERIOD AT END OF PARAGRAPH OR PARAGRAPH NAMES.
* COBOL- MISSING GOBACK AFTER SORT VERB - LOGIC FELL INTO
* INPUT PROCEDURE.
* A MISSING OR MISSPELLED DD.
* DATASET WAS OPEN OR CLOSED WHEN AN INPUT/OUTPUT INSTRUCTION
WAS ISSUED FOR IT. IT SHOULD HAVE BEEN THE OPPOSITE.

S0C4 - PROTECTION EXCEPTION
* INDEXING (SUBSCRIPTING) OUTSIDE THE PGM'S ASSIGNED LIMITS.
* UNITIALIZED INDEX.
* A MISSING OR MISSPELLED DD.
* AN ATTEMPT TO READ AN UNOPEND INPUT FILE.
* BLOCKSIZE AND RECORD SIZE BEING SPECIFIED AS = FOR VARIABLE
LENGTH RECORDS

S0C5 - ADDRESSING EXCEPTION
* INDEXING (SUBSCRIPTING) OUTSIDE THE PGM'S ASSIGNED LIMITS.
* UNITIALIZED INDEX.
* A MISSING OR MISSPELLED DD.
* AN ATTEMPT TO CLOSE A DATASET A SECOND TIME.
* AN INPUT/OUTPUT INSTRUCTION TERMINATED BECAUSE OPEN WAS
UNABLE TO COPLETE THE DCB.

S0C6 - SPECIFICATION EXCEPTION
* AN ADDRESS DOES NOT SPECIFY THE BOUNDARY REQUIRED.

S0C7 - DATA EXCEPTION- DATA WAS OF INCORRECT FORMAT FOR THE INSTRUCTION
ATTEMPTING TO PROCESS IT.
* UNINITIALIZED INDEX OR SUBSCRIPT.
* FIELDS IN DECIMAL ARITHMETIC OVERLAP INCORRECTLY.
* INDEX/SUBSCRIPT VALUE INCORRECT AND INVALID DATA WAS REFERENCED.
* THE DECIMAL MULTIPLICAND HAS TOO MANY HIGH-ORDER SIGNIFICANT
DIGITS.
* DATA FIELD WAS NOT INITIALIZED, BLANKS WERE READ INTO A FIELD
DESIGNED TO BE PROCESSED WITH PACKED DECIMAL INSTRUCTIONS.

S0C8 - FIXED POINT OVERFLOW EXCEPTION

S0C9 - FIXED POINT DIVIDE EXCEPTION. INCREASING REGION TO 0M WORKED
FOR GARY STRAITZ ON A JOB HE WAS RUNNING.

S0CA - DECMIAL OVERFLOW EXCEPTION -
DESTINATION FIELD TOO SMALL FOR RESULT

S0CB - DECIMAL DIVIDE EXCEPTION, QUOTIENT EXCEEDS SPECIFIED DATA FIELD
SIZE.

S0CC - EXPONENT OVERFLOW EXCEPTION

S0CD - EXPONENT UNDERFLOW EXCEPTION

S0CE - SIGNIFICANCE EXCEPTION

S0CF - FLOATION POINT DIVIDE EXCEPTION DIVIDE BY ZERO

S0F1 -

S0F2 -

S0F3 -

S106 - PGM IS IN PGMLIB BUT POINTERS ARE BAD. HAVE PGMR COMPILE IT IN
TESTLIB AND PUT STEPLIB IN JCL TO PULL FROM TESTLIB.

S106 * ERROR WHILE LOADING MODULE INTO MAIN STORAGE/NEEDS MORE CORE
OR ADD REGION PARM TO JOB CARD

S117 -

S122 - OPERATOR CANCEL , REQUESTED DUMP

S137 - I/O ERROR ERROR IN LABEL PROCESSING
* MULTI-VOLUME DATASET WITH INCONSISTENT LABELING.
* NO TRAILER LABELS OR TAPE MARKS EXISTS AT END OF DATA.
* LABEL FORMAT INCORRECT.

S14F * CARD INPUT MISSING

S1E7 * DSN DOES NOT MATCH THE DSN ON THE VOLUME REQUESTED

S213 - DSCB NOT FOUND. I/O ERROR IN READING OR WRITING DSCB
(DSCB=DATA SET CONTROL BLOCK)
* THE FORMAT DSCB COULD NOT BE FOUND ON DASD.
* DISP=OLD OR SHR FOR AN OUTPUT DSN.
* SPACE PARM WAS NOT SPECIFIED.
* DISP=MOD BUT THE DATA SET SHOULD REALLY
BE NEW
* DISP=NEW AND UNIT AFFINITY REQUESTED
(UNIT=AFF=DDNAME) DEFERRED MOUNTING IS
IMPLIED AND NO SPACE IS ALLOCATED.

S214 - TAPE POSITIONING OR INVALID DISP
- HARDWARE DEVICE DIFFICULTIES
- BAD PHYSICAL SPOT ON RECORDING MEDIUM
- NO TAPEMARK FOLLOWING DATA
- DATA OBLITERATION

S222 - OPERATOR CANCELED

S228 - STORAGE VIOLATION - PROGRAM MIGHT HAVE BEEN COMPILED USING WRONG
RMODE, AMODE.

S237 - ERROR AT END OF VOLUME. S237-08 MAY BE CAUSED BY INTERNAL AND
EXTERNAL TAPE LABEL NOT MATCHING, TRY WHATTAPE ON TAPE NUMBERS
PRIOR AND RIGHT AFTER MISMATCHED TAPE.
* BLOCK COUNT WRONG ON TRAILER LABEL.
* VOL=SER SPECIFIED WRONG IN JCL.
* TAPE BLOCK COUNT DIDNT AGREE WITH DCB BLOCK COUNT, POSSIBLE
SKIPPED BLOCK DUE TO HARDWARE ERROR.

S306 - THIS CAN HAPPEN IF A MEMBER GETS REMOVED FROM CICS LOADLIB
SUCH AS CMSSGP.CICS.LOADLIB1 DAVE PADGETT CAN PUT THIS BACK
ON THE APF LIST WITH A RESOLV COMMAND. CAN ALSO BE A RACF ABEND.
(WILL SHOW MODULE XXXXXXXX NOT ACCESSED, USER UNAUTHORIZED.

S314 - I/O ERROR READING DSCB.

S322 - TIME OUT (CPU TIME LIMIT EXCEEDED), TRY ADDING TIME PARM
120 CPU MINUTES IS THE SYSTEM DEFAULT FOR EACH STEP IN A JOB.

S400 - INVALID CONTROL - INVALID DCB PARAMETER BLOCK

S413-08 I/O ERROR, RESTART JOB IN ABENDED STEP.
* THE VOLUME COULDNT BE MOUNTED ON THE REQUESTED DEVICE.
* THE VOLUME SERIAL # INCORRECT.
* THE VOLUME SERIAL # WASNT SPECIFIED FOR AN INPUT DSN
* VOLUME SEQUENCE # SPECIFIED IN CATLG OR JCL WAS GREATER THAN
THE # OF VOLUMES CURRENTLY ALLOCATED TO THE DSN.

S422 - JOB REQUIRED TOO MUCH SPACE IN SYSTEM JOB QUEUE.

S437 - ERROR OCCURRED AT END OF VOLUME

S428 - PSB AND REGION - IF PSB 'T' REGION = I003
INCOMPATIBLE - IF PSB 'P' REGION = I002

S513 - ERROR AT OPEN FOR TAPE DATA SET ON TAPE VOLUME.
* ASSIGNMENT OF TWO DATASETS TO THE SAME TAPE DEVICE.

S522 - TIME OUT (TASKS IN JOB STEP IN WAIT STATE DUE TO UNATTAINABLE
RESOURCE E.G, PHYSICAL DEVICE, DATA SET, CPU)
* PROGRAMMED TIMED OUT WAITING FOR TAPE MOUNT

S606 - NOT ENOUGH MAIN STORAGE WAS AVAILABLE TO LOAD PROGRAM

S60A * NEEDS MORE CORE

S613 - TAPE OR CARTRIDGE POSITION ERROR
* MISSING DCB .
* DENSITY IS WRONG.
* RECFM=F IN JCL WHEN FILE IS ACTUALLY FB

S637 - I/O ERROR DURING END-OF-VOL; SEE SPECIFIC RETURN CODES IN IEC026I BOOK.
* CONCATENATED DSNS HAVE UNLIKE ATTRIBUTES. I BOOK.

S706 - THE REQUESTED LOAD MODULE WAS MARKED BY THE LINKAGE EDITOR
AS NOT EXECUTABLE...

S713 - ERROR DURING OPEN DUE TO EXPIRATION DATE VIOLATION.

S714 - UNCORRECTABLE I/O ERROR OCCURRED IN TAPE LABEL PROCESSING (CRIMP
IN TAPE, TAPE LABEL DESTROYED OR WRITTEN INCORRECTLY).

S722 - TIMEOUT (OUTPUT LIMIT REACHED, JOB EXCEEDED NUMBER OF ALLOWABLE
LINES)

S737 - ERROR DURING END-OF VOLUME OR DURING ALLOCATION OF SECONDARY
DASD SPACE AS REQUESTED IN SPACE PARM OF DD, POSSIBLY NEEDS
MORE SPACE.
* CONCATENATED DSN CANT BE FOUND.

S755 - ENQUE FILE FULL - TOO MANY ENQUES (GET HOLD, ETC.)

S775 - NO THREADS - SYSTEM SHUTTING DOWN -TRY LATER

S80A - ERROR DURING GETMAIN - TRY INCREASING REGION PARM.
4096K OR 7M. 8M IS MAX BUT SHOULD EXERCISE CAUTION IN USING PER
JOHN SHULTZ. 0 USES WHATEVER'S NEEDED, LIKE A 1440 PARM.

S804 * NEEDS LARGER REGION SIZE.

S806 - REQUESTED MODULE NOT FOUND / PROGRAM PROBLEM
* MISSING STEPLIB OR JOBLIB CARD?
* OBJECT PROGRAM NOT FOUND

S813-04 TAPE MOUNTED DOES NOT HAVE DSN THAT THE JCL IS LOOKING FOR
(COULD BE 2 TAPES WITH THE SAME INTERNAL NUMBER)

S822 - REGION UNAVAILABLE (LIKE IN REGION=6M)
- SYSTEM ERROR IN INITIATOR U11STEP (USUALLY IN CHANGE ACCUMS);
REGION UNAVAILABLE, ERROR CODE=20 - TRY RESUBMITTING

S837 - VOLUME COUNT PARM INSUFFICIENT VOL=(,,,10) (LABEL=TAPE,VOL=(,,,99)
CAN SOMEONE EXPLAIN THE LABEL= TAPE PARM?????

S850 USER ABEND ISSUED BY IMS.
DATA BASE POINTER ERROR WHEN READING FROM A REGION NOT THE
UPDATING REGION.
CALL DBA. DATA BASE NEEDS TO BE DEALLOCATED AND REALLOCATED

S678 - NEEDS REGION PARM ADDED ON JOB CARD (REGION=7M)

S878 - VIRTUAL STORAGE REQUESTED NOT AVAILABLE. - TRY INCREASING REGION PARM.
4096K OR 7M. 8M IS MAX BUT SHOULD EXERCISE CAUTION IN USING PER
JOHN SHULTZ. 0 USES WHATEVER'S NEEDED, LIKE A 1440 PARM.
ADD REGION=4096K ON JOB CARD OR STEP.

S90A * TRYING TO CLOSE A CLOSED FILE OR OPEN AN OPENED FILE.

S913-38 ICH408I INSUFFICIENT AUTHORITY RACF

----------------------------------------------------------------------
RETCD - Return codes
----------------------------------------------------------------------
R/C 12 GENERIC ABEND, CHECK OUTPUT FOR SPECIFIC REASON, IE SB37,
CONTENTION.

R/C 12 DO A FIND ON SQL, IF SQLCODE=00000091J THIS IS A DEADLOCK AND
THE JOB SHOULD BE RESTARTED PER THE XT-42 INSTRUCTIONS
IF SQLCODE=00000090M CHECK WITH DATA BASE
ABOUT ENABLE UTILITY AFTER THAT RESTART JOB
PER XT-42

R/C 16 WHEN EXECUTING SYNCSORT,PARM='RC16=ABE' JOB WILL RETURN CODE 16.
MAX TO BOTTOM TO SEE IF ABEND IS EXPLAINED.
* IF JOB HAS THIS TYPE OF JCL - EXEC SORT,REGION=2M,PARM='CORE=
500K',CYL=50, AND JOB FAILS WITH RC16, INCREASE SORT SIZE BY
IN CYL=XX TO INCREASE THE SORT WORK SIZE. THERE WILL BE NO SORT
WORKS IN THE JCL ITSELF TO INCREASE SPACE.

----------------------------------------------------------------------
STACD - File status codes
----------------------------------------------------------------------
I/O STATUS '35' -
DDNAME MISSING (COBOL II).

I/O STATUS '37' -
CHECK FD RECORD LENGTH AGAINST DCB LENGTH (COBOL II).

I/O STATUS '39' -
CHECK BLOCK CONTAINS CLAUSE IN FD (COBOL II).

I/O STATUS '46'
READ PAST END OF DATA ON FILE (COBOL II).

I/O STATUS '47'
READ AFTER FILE CLOSED (COBOL II).

I/O STATUS '48' -
WRITING TO FILE OPENED AS INPUT.

FILE STATUS '92' -
1. ANY I/O REQUEST AGAINST A FILE THAT IS NOT OPEN.
2. ANY I/O REQUEST THAT IS NOT ALLOWED FOR THE OPTION THAT
WAS SPECIFIED WITH THE OPEN STATEMENT. (I.E. READ A FILE
OPENED AS AN OUTPUT OR REWRITE A FILE OPENED AS INPUT).
3. ANY WRITE OR REWRITE OF A RECORD WHOSE LENGTH IS GREATER
THAN THE MAXIMUM SIZE SPECIFIED IN THE FD (DCB).
4. ANY ATTEMPTED ACTION ON A FILE AFTER END-OF-FILE CONDITION
HAS OCCURED.

----------------------------------------------------------------------
SQLCD - SQL return codes
----------------------------------------------------------------------
NOTES:

* IN DB2 RELATED JOBS, DO A FIND ON SQL

SQL 100 - ROW NOT FOUND FOR FETCH--CONTACT PROGRAMMER, RETRY WON'T WORK.

-203 - A REFERENCE TO COLUMN colum-name is AMBIGUOUS

-204 - NAME IS UNDEFINED NANE

-205 - column-name IS NOT A COLUMN OF TABLE table-name

-501 - CURSOR IDENTIFIED IN FETCH OR CLOSE IS NOT OPEN

-502 - CURSOR IDENTIFIED IN OPEN IS ALREADY OPEN

-504 - THE CURSOR NAME cursor-name IS NOT DEFINED

-803 - INSERT/UPDATE VALUES INVALID; CONTACT SYS DEV

-805 - PROGRAM NOT FOUND; PROGRAM NOT BOUND AS PART OK PLAN NAME.
CONTACT SYS DEV.

91J - DEADLOCK, RESTART; LIKE -911.

90M - STOPPED UTILITY, UTILITY IS ACTIVE; CK. IF IMAGE COPIES ARE
RUNNING. RESTART AFTER IMAGE COPIES COMPLETE.

-904 - DB2-TABLE IS DOWN CONTACT SYSTEM DEV. (RESOURCE UNAVAILABLE)
OR CAN BE A TEMPORARY CONTENTION - RESTART LATER.

-911 - RESOURCE CONTENTION, RESTART AFTER JOB CAUSING CONTENTION ENDS

-913 - RESOURCE CONTENTION, RESTART AFTER JOB CAUSING CONTENTION ENDS

-04E - DATA PROBLEM OR DB2 INTERNAL ERROR

-818 - BIND PROBLEM, RELATED TO PRODUCTION UPDATES.

-923 - DB2 CONNECTION DOWN, CHECK STATUS OF DB2 PRODUCTION

-924 - DB2 CONNECTION INTERNAL ERROR = OPERATIONS CHECK SUBSYS DB2
CAF ERROR: DB2 CONNECTION LIMIT HAS BEEN REACHED = TOO MUCH RUNNING
IN DB2; RESTART AFTER ANOTHER DB2 JOB ENDS

----------------------------------------------------------------------
MISC - Miscellaneous codes and messages
----------------------------------------------------------------------

PATTERN DSCB NOT FOUND IN VTOC -IF GDG WITH DISP=NEW,CATLG,DELETE,
GDGMODEL MUST BE INCLUDED IN DCB= SUCH AS DCB=(GDGMODEL,RECFM=FB,ETC.

NO PRIMARY VOLUME AVAILABLE MSG - NO VOLUME'S AVAILABLE WITH ENOUGH
SPACE FOR RECALL.

NO STORAGE VOL - VOL=PRIV ASSUMED - UNABLE TO ALLOCATE -- CHECK JCL FOR
(SPGGRP,9); SPGGRP (OR OTHER ESOTERIC) MAY HAVE DECREASED NUMBER OF
VOLUMES. SPGGRP HAD BEEN DECREASED TO 8 CAUSING THIS JCLERR.

ALLOCATION FAILED DUE TO DATA FACILITY SYSTEM ERROR
IGD17273I ALLOCATION HAS FAILED FOR ALL VOLUMES SELECTED FOR DATA SET ..NAME
IGD17277I THERE ARE (XX) CANDIDATE VOLUMES OF WHICH XX ARE ENABLED OR QUIESCED..
THIS IS BASICALLY THE SAME AS SPACE REQUESTED NOT AVAILABLE. TRY
DECREASING SPACE ALLOCATION PER GENE WILL 02/10/91, AND LET JONES & CO
KNOW OF THIS SORT OF ABEND DURING WORK HOURS UNLESS UNABLE TO RESOLVE.
**UPDATE 06/15/91 - TO DD STATEMENT ADD STORCLAS=NONSMS, IE
UNIT=SYSDA,STORCLAS=NONSMS,SPACE=(ETC), THEN CHANGE/ADD USER=TTSVDMP,
PASSWORD=???????? TO JOB CARD TO RESTART PER JOHN SHULTZ.
01/11/92 - CHANGING TO UNIT=(SPGGRP,3) CAN WORK. KDF
03/21/92 - OR ADDING MORE SORTWORKS. KDF

----------------------------------------------------------------------
CICSCD - CICS abend codes
----------------------------------------------------------------------
ADCA - PSB MAY NOT BE IN SYNC WITH THE SOURCE PROGRAM
CHECK THAT THE DATABASE BEING CALLED IS REF-
ERENCED IN THE PSB.

AUEP - TIMEOUT. WHEN A PROGRAM READS A LOT OF DATA,
IT REACHES THE THRESHOLD LIMIT AND
ABENDS.

ADCC - HAVE SYSTEMS MANAGEMENT RECYCLE DBCTL IN THE
REGION THAT THE ABEND IS OCCURRING. IF THIS
FAILS THEN CALL TECH SUPPORT

ADLA - POSSIBLY DATABASE FULL, CALL DBA.
THIS IS A GENERAL IMS FILE REGION ABEND CODE.
PROGRAMMER CAN PULL DUMP USING CICS TRANS SP31
WHERE TASK=CSM5 / ABEND=ADLA / REGION=FILE REGION
REGISTER 1 WILL CONTAIN IMS ABEND CODE (IN HEX).
CORRESPONDING CICS AZI6 DUMP WILL TELL WHICH DATA BASE.

ADLC - PROGRAM TRIED TO ACCESS A DATABASE THAT IS
DISABLED.

ADLF - DL/I CALL MADE FOR A DATABASE, BUT THE LINK TO
THE SYSTEM ON WHICH IT RESIDES IS DOWN,
CALL DBA.

ADLG - ERRORS IN THE DL/I ARGUMENT LIST.
(VERIFY PCB IS SCHEDULED)

AEIP - CICS INVREQ CONDITION - IF USING LOGICAL PAGING
CHECK TO SEE IF A MAP W/O PAGING WAS SENT AFTER
ACCUM PAGING INITIATED.

AEIV - LENGERR - INVALID LENGTH ON SEND, RECEIVE, AND
OTHER VERBS

AEXT - DB2 NOT COMPILED WITH DL/I OPTION TURNED ON

AEY9 - DB2 HAS COME DOWN AND BACK UP BUT HAS NOT BEEN
RE-ATTACHED. TRY ATTACHING BY CODING:
IN CICS4 - "DSNC STRT 5"

AKCS - DEADLOCK TIMEOUT.

AICA - RUNAWAY TASK CONDITION, POSSIBLE LOOP.

APCT - REQUESTED MODULE CANNOT BE LOCATED IN THE PPT
OR ENTRY DISABLED (MODULE NOT FOUND IN THE
LOAD LIBRARY).

ASRA - USUALLY DATA EXCEPTION ERROR.

ATNI - CICS DECIDES IT NEEDS TO ABEND THE TRANSACTION.
COULD BE: INCORRECT DEFINITION IN TCT.
INVALID DATA STREAM FOR DEVICE TYPE.

AZI2 - TOO MANY DATABASE CALLS, NOT TAKING CHECKPOINT
(CHECK TO SEE IF IN LOOP WITH DL/I CALLS).

AZI4 - INTERREGION COMMUNICATION REQUEST CAN NOT BE
COMPLETED BECAUSE THE OTHER SYSTEM HAS BECOME
UNAVAILABLE.

AZI6 - TIME OUT, PROGRAM MAY BE IN A LOOP.
ISRT WITH SECONDARY INDEX THAT EXISTS RATHER
THAN AN 'II' STATUS CODE.
DATA BASE POINTER PROBLEM - INTER-REGION
READ. RELATED TO BUFFERS.
THIS IS A GENERAL ABEND CODE, OFTEN ACCOMPANIED
BY AN ADLA ABEND FOR THE FILE REGION (SEE ADLA).

1009 - COBOL 2 ABEND - WORKING STORAGE TOO LARGE, COB2
ALLOWS FOR VERY LARGE WS BUT CICS STILL LIMITS
AT 64K.

1011 - COBOL 2 ABEND - INDICATES USE OF ACCEPT,
DISPLAY, ETC. INVALID VERB.

APLC - SHARED LIBRARY FACILITIES ARE REQUIRED BY THE
PROGRAM, BUT WERE NOT INCLUDED IN THE CICS
SYSTEM DURING INITIALIZATION/INSTALLATION.

APLD - ERROR DURING TRANSMISSION OF A RECORD TO THE
CPLD QUEUE.

APLE - ERROR DURING PL1 PROGRAM MANAGEMENT (EQUAL TO
4000 NON CICS ABEND)

APLG - A GET STORAGE REQUEST TO THE STORAGE ALLOCATION
ROUTINE SPECIFIED A SIZE > THAN CICS/OS/VS
PERMITTED MAX (65,496) EITHER A BASED OR
CONTROLLED VARIABLE THAT IS TOO LARGE IN AN
ALLOCATE STMT, TOO MANY LARGE 'AUTOMATIC
VARIALBES.

APLI - ERROR DURING TRANSMISSION OF A RECORD TO THE
CPLI QUEUE.

APLM - NO MAIN PROCEDURE

APLS - TERMINATION IS CAUSED BY THE 'ERROR' CONDITION,
AND THE 'ERROR' CONDITION WAS NOT CAUSED BY
AN ABEND (OTHER THAN AN ASRA ABEND).

APLX - TOTAL POSSIBLE 'LIFO' STORAGE SEGMENTS HAVE
BEEN EXHAUSTED. CHECK PROGRAM FOR LOOPS OR
INCREASE THE 'ISASIZE' OR 'ISAINC'.

----------------------------------------------------------------------
IMSCD - IMS abend codes
----------------------------------------------------------------------
COMMOM ABENDS/REASONS
ABEND REASON
----- ------------------------------------------

S000 -
- 0260 TRYING TO CHKP WITHOUT PRIOR XRST
- 0261 PSB OUT OF SYNC WITH PROGRAM - NOT ENOUGH
GSAMS DEFINED IN PSB.
(IN I004BMP OR I003BMP MAKE SURE PROGRAM
IS COMPILED AS SHRBATCH NOT BATCH)
- 0428 PSB NEEDS TO BE DEFINED IN THE IMS REGION
- 0437 RACF ABEND ON A MESSAGE QUEUEING PROGRAM USING
A PSB NAME THAT MATCHES THE PROGRAM NAME.
(JCL MUST CONTAIN "AGN=AGPAMS4" ON THE EXEC CARD)
- 0456 PSB NEEDS TO BE RESTARTED AFTER PRIOR ABEND
OR PSB NOT FOUND
(FOR TEST CHECK DB15563P FOR TEST PSB JOB
THAT SHOULD RUN AT 10, 12, 2 AND 4)
- 0474 OPERATOR CANCEL
- 0476 PSB ERROR
- PROGRAM NOT COMPILED AS SHRBATCH
- REFERING TO -SC NOT -PCB IN CALL
- 0688 CTL PROGRAM NOT ACTIVE; CHECK IF EXECUTING
WRONG IMS (EX, I002BMP IN CLASS J)
- 0805 PSB NOT SCHEDULED/A DATA BASE IS NOT AVAILABLE
- 0811 BAD DATA BASE POINTERS - CONTACT DBA
- 0844 DATA BASE IS FULL
- 0849 CALL WITH 'GO' ON SEGMENT THAT HAS BEEN
PREVIOUSLY RETRIEVED BUT NOT COMMITED.
DATA INTEGRITY NOT INSURED.
- 0850 INTER-REGION DATA BASE BUFFER PROBLEM
- 3303 SIMILAR TO 0805.
DATA BASE OFFLINE IN IMS - DATA SHARING
DATA BASE MAY STILL BE AVAILABLE IN ONLINE
REGION.
3042 - RUNNING INVALID PROC IN JCL
(EXAMPLE TRYING TO EXECUTE DB2 IN PROC
THAT DOES NOT SUPPORT IT OR TRYING TO
EXECUTE BMP PROC FOR DB2)

3601 - LIB POINTED TO BY IMS DD COULD NOT OPEN

3602 - BLDL REQUEST FAILED FOR PSB

3603 - REQUESTED PSB COULD NOT BE LOADED

3604 - MISSING DDNAME ON GSAM FILE

3610 - LOOK AT YOUR RESTART

3611 - GSAM PSB IN USER LIST INVALID

3612 - ERROR DURING EXTENDED CHKPT CALL

3613 - ERROR DURING USER CALL TO GSAM DATABASE

3614 - ERROR DURING PURGING GSAM BUFFERS AT CHKPT

3620 - ERROR IN A RECURSIVE CALL TO CADDRPE
DURING EXTENDED RESTART

3707 - CICSXXX NOT AVAILABLE
CLASS NOT = J FOR TEST SHARE BATCH
CLASS NOT = K FOR PROD SHARE BATCH

- 0101 SAVEAREA TOO SMALL
- 0102 NO RESTART RECORD - DELETE CC505

3710 - ABEND WITH USER CODE, CHECK SPIE AREA
- 0001 PSB ERROR; WRONG PROC OR COMPILE
- 0004 ADDRESS EXCEPTION
- 0007 DATA EXCEPTION

3711 - CICS NOT UP
'KILLER' PROGRAM - NEED MORE CHKPTS

3714 - AXFN NO PROGRAM GEN OR TEST PSB
- ADLF CICS FILE REGION IS DOWN
- DFH2 POSSIBLE CHKPT QUEUE CONTENTION
- 775 ENQUE FILE FULL
- 828 INSERTING DUPLICATE SECONDARY INDEX
- ADLA/844 DATABASE FULL, CHECK SECONDARY INDEX
- 850 BAD DATA BASE POINTERS
- 852 BAD DATA BASE POINTERS
- 853 INDEX POINTER PROBLEM
- 913 INSUFFICIENT ACCESS

3717 - PCB NOT DEFINED IN PSB OR INVALID DLI
ARGUMENT LIST. CHECK 'LANG' PARM IN JCL
CHECK LANGUAGE PARAMETER IN CICS SHARED
BATCH PROC. REMEMBER DEFAULT IS PL/1.

3723 - 801 PSB NOT IN TABLES
- 803 PSB ALREADY SCHEDULED
- 805 PSB NOT IN ACBLIB OR DATA BASE OFFLINE
- 806 PROGRAM NOT IN TEST LOAD LIB. CHECK 'MBR='
AND RECOMPILE.
- 828 INSERTING DUPLICATE SECONDARY INDEX.

4036 - INVALID LANG PARM IN JCL - PROGRAM IS PL/I,
LANG PARM IS 'C'.

S322 - EXCEEDS TIME PARAMETER

S522 - OPERATOR DID NOT MOUNT TAPE ON TIME.

S722 - OUTLIM EXCEEDED

S878 - NEED TO INCREASE CORE.

S1320 - BLOW UP TAKING CHKPT, NEED MORE REGION

U0102 - RESTART FAILED BECAUSE IMS CANNOT FIND
RESTART INFO ASSOCIATED WITH CHECKPOINT ID.
CHECK FOR LOW-VALUES IN RESTART RECORD.

U0437 - APPLICATION GROUP NAME OR RESOURCES
SPECIFIED ARE NOT VALID
FOR DEPENDENT REGION
* MAY NEED 'AGN=' PARAMETER,
SEE MEMBER '#RACF'.

U0456 - PSB NEEDS TO BE RESTARTED - SCHEDULING
FOR TEST PSBS RUNNING IN IMS3 (USING PROC
I003BMP OR I003DB2), GET INTO DBAE IN TSO,
USE OPTION STARTPSB.
OR
PSB NOT NEW COPIED IN IMS
(FOR TEST CHECK DB15563P FOR TEST PSB JOB
THAT SHOULD RUN AT 10, 12, 2 AND 4)

U0688 - RUNNING 2 REGIONS IN 1 JOB.

U1904 - CHKPT UTILITY RECORD NOT CREATED



0C4 One of the following exceptions occurred:

4 Protection exception. The key of the storage area
that the running program tries to access is
different than that of the running program. The key
of the running program can be obtained from the PSW
key field. The key of the storage can be obtained
using the IPCS LIST subcommand. The programmer
should determine whether the program is running
with correct the key or whether the storage address
is set up correctly.

10 Segment-translation exception. This error can be
caused by either the segment table being paged out
with the program running disabled or the segment
table entry indicates that all of the storage
referenced by the entry is not allocated. If the
program is running disabled, the programmer should
determine whether the storage should be page fixed
prior to running disabled or whether the storage
address is set up correctly.

11 Page-translation exception. This error can be
caused by either the page table entry being paged
out with the program running disabled or the
referred storage area is not allocated. If the
program is running disabled, the programmer should
determine whether the storage should be page fixed
prior to running disabled, whether the storage area
is still obtained through a GETMAIN or whether the
storage address is set up correctly.

0C5 Addressing exception. The reason code is 5.

0C6 Specification exception. The reason code is 6.

0C7 Data exception. The reason code is 7.

0C8 Fixed-point-overflow exception. The reason code is 8.

0C9 Fixed-point-divide exception. The reason code is 9.

0CA Decimal-overflow exception. The reason code is A.

0CB Decimal-divide exception. The reason code is B.

0CC Exponent-overflow exception. The reason code is C.

0CD Exponent-underflow exception. The reason code is D.

0CE Significance exception. The reason code is E.

0CF Floating-point-divide exception. The reason code is F.

Source: Supervisor control

System Action: The system abnormally ends the task, unless a recovery
routine was provided to handle the interruption. The hardware action
is given in Principles of Operation.

System Programmer Response: Determine whether the problem program or
control program was in error.

If the problem program contained an error, correct it, and run the job
step again.


Note : In the jcl QMFBATCH one parameter i,e., DB2 cpu parameter is to be
supplied immediately after job card.

//jobparm sysaff=sysi

DB23 not operational :

Note : In the jcl QMFBATCH one parameter i,e., DB2 cpu parameter is to be
supplied immediately after job card.

//jobparm sysaff=sysi

sysi - production db2 cpu
sysg - test db2 cpu

____________________________

Syntax for see the index in db2

SELECT INDNAME, DEFINER, TABSCHEMA, TABNAME, 
COLNAMES, COLCOUNT, UNIQUERULE, INDEXTYPE 
FROM SYSCAT.INDEXES
WHERE TABSCHEMA NOT LIKE 'SYS%' AND
TABNAME = 'TABLE_NAME'

VSAM Interview Questions - Part 2


1. What are the different types of VSAM files available?
ESDS: Entry Sequence Data Set
KSDS: Key Sequence Data Set
RRDS: Relative Data Set
2. What is IDCAMS ?
IDCAMS is the Access Method Services program. You run the IDCAMS program and supply AMS commands thru SYSIN. (examples of AMS commands are DELETE, DEFINE, REPRO etc..).
3. Can AMS commands be run from the TSO prompt ?
Yes
4. Syntax of AMS modal commands ?
Note: these can be used only under IDCAMS and not from the TSO prompt.
IF LASTCC(or MAXCC) >(or <,= etc..) value -
THEN -
DO -
command set (such as DELETE, DEFINE etc..)
ELSE -
DO -
command set
LASTCC - Condition code from the last function(such as delete) executed
MAXCC - Max condition code that was returned by any of the prev functions
SET is also a valid AMS command. SET LASTCC (or MAXCC) = value
The maximum condition code is 16. A cond code of 4 indicates a warning. A cond code of 8 is usually encountered on a DELETE of a dataset that is not present.
5. Under IDCAMS , multiple functions can be executed, each of which returns a cond code. What will be the condition code returned to the operating system ?
The maximum condition code generated is returned as the condition code of the IDCAMS step.
6. What is Control Interval, Control Area ?
Control Interval is analogous to a physical block for QSAM files. It is the unit of i/o. Must be between 512 bytes to 32 k. Usually either 2K or 4K. A larger control interval increases performance for sequential processing while the reverse is true for random access. Under CICS when a record is locked, the entire CI gets locked.
Control area is a group of control intervals. CA is used during allocation. CA size is calculated based on the allocation type (cyl, tracks or records) and can be max of 1 cylinder
7. What is FREESPACE ?
Coded in the DEFINE as FREESPACE(ci ca) where ci is the percentage of each control interval to be left free for insertions, ca is the percentage of control intervals in each control area to be left empty.
8. How do you decide on optimum values for CI, FREESPACE etc..?
CI size should be based on record length, type of processing. Usually CI is 4K. If record length is larger(>1K), chose 6K or 8K.
FREESPACE should be large if more number of insertions are envisaged. Usual values are (20 20) when heavy updates are expected. CI size can be calculated.
9. Would you specify FREESPACE for an ESDS?
No. Because you cannot insert records in an ESDS, also when you rewrite a record, it must be of the same length. Thus putting any value for freespace does not make any sense.
10. What is SHAREOPTS ?
SHAREOPTS is a parameter in the DEFINE and specifies how an object can be shared among users. It is coded as SHAREOPTS(a b), where a is the cross region share option ie how two or more jobs on a single system can share the file, while b is the cross system share option ie how two or more jobs on different MVSes can share the file. Usual value is (2 3).
11. What is the meaning of each of the values in SHAREOPTS(2 3)?
Value of 2 for cross region means that the file can be processed simultaneously by multiple users provided only one of them is an updater. Value of 3 for cross system means that any number of jobs can process the file for input or output (VSAM does nothing to ensure integrity).
12. How do you define a KSDS ?
DEFINE CLUSTER(cluster name) with the INDEXED parameter. Also specify the ds name for the DATA component & the ds INDEX component. Other important parms are RECORDSIZE, KEYS, SHAREOPTIONS.
13. How do you define an ALTINDX ? How do you use ALTINDXs in batch, CICS pgms ?
DEFINE ALTERNATEINDEX. Important paramters are RELATE where you specify the base cluster name, KEYS, RECORDSIZE,SHAREOPTIONS,UNIQUEKEY(or NONUNIQUEKEY), DATA(ds name for the data component), INDEX(ds name for the index component).
Then DEFINE PATH. Important paramters are NAME (ds name for the path), PATHENTRY (ds name of the alternate index name), UPDATE(or NOUPDATE) which specifies whether an alt index is updated when a update to the base cluster takes place.
Then BLDINDEX. Parameters are INDATASET(ds name of base cluster), OUTDATASET(ds name of AIX).
Using alternate indexes in batch pgms:
In the JCL, you must have DD stmts for the cluster and for the path(s). In the cobol pgm, SELECT .. ASSIGN TO ddname for base cluster RECORD KEY IS... ALTERNATE RECORD KEY IS..
Using alternate indexes in CICS pgms:
FCT entries must be created for both base cluster & the path. To read using the alternate index, use the dd name of the path in CICS file control commands.
14. What happens when you open an empty VSAM file in a COBOL program for input?
A VSAM file that has never contained a record is treated as unavailable. Attempting to open for input will fail. An empty file can be opened for output only. When you open for output, COBOL will write a dummy record to the file & then delete it out.
15. How do you initialize a VSAM file before any operation? a VSAM with alternate index?
Can write a dummy program that just opens the file for output & then closes it.
16. What does a file status of 02 on a VSAM indicate?
Duplicate alternate key . Happens on both input and output operation
17. How do you calculate record size of an alternate cluster? Give your values for both unique and non-unique.
Unique Case: 5 + ( alt-key-length + primary-key )
Nonunique Case: 5 + ( alt-key-length + n * primary-key )
where n = # of duplicate records for the alternate key
????Any one who knows - can you explain ?
18. What is the difference between sequential files and ESDS files?
Sequential(QSAM) files can be created on tape while ESDS files cannot.
Also, you can have ALTINDEX for an ESDS while no such facility exists for QSAM files.
19. How do you load a VSAM data set with records ?
Using the REPRO command.
20. How do you define a GDG ?
Use the DEFINE GENERATIONDATAGROUP command. In the same IDCAMS step, another dataset must be defined whose DCB parameters are used when new generations of the GDG are created. This dataset is known as the model dataset. The ds name of this model dataset must be the same as that of the GDG, so use a disp of keep rather than catlg and also specify space=(trk,0)
21. Do all versions of the GDG have to be of the same record length ?
No, the DCB of the model dataset can be overridden when you allocate new versions.
22. How are different versions of GDG named ?
base-file-name.GnnnnnV00 where nnnn= generation number (upto 255).
nnnn will be 0000 for the 1st generation.
23. Suppose 3 generations of a GDG exist. How would you reference the 1 st generation in the JCL?
Use GDG name(-2).
24. Suppose a generation of GDG gets created in a particular step of a proc. How would you refer the current generation in a subsequent step? What would be the disposition of this generation now?
Relative generation numbers are updated only at the end of the job, not at the end of a step. To allocate a new generation, we would be using (+1) with a DISP of (NEW,CATLG,DELETE). To refer to this in a subsequent step in the same job, we would again use (+1) but with a DISP of SHR or OLD.
25. What more info you should give in the DD statement while defining the next generation of a GDG?
Give (+1) as the generation number, give (new,catlg) for disp, give space parameter, can give the dcb parameter if you want to override the dcb of the model dataset.
26. Assuming that the DEFINE jcl is not available, how do you get info about a VSAM file�s organisation ?
Use the LISTCAT command.
27. During processing of a VSAM file, some system error occurs and it is subsequently unusable . What do you do ?
Run VERIFY.

VSAM Interview Questions


Q1)     What are the types of VSAM datasets?
A1)     Entry sequenced datasets (ESDS),  key sequenced datasets (KSDS) and relative record dataset (RRDS).  

Q2)     How are records stored in an ESDS, entry sequenced dataset?
A5)     They are stored without respect to the contents of the records and in the order in which they are included in the file.

Q3)     What is a CI, control interval?
A3)     A control interval is the unit of information that  VSAM transfers between virtual and auxiliary storage.

Q4)     What are the distinctive features of a ksds, key sequenced dataset?
A4)     The index and the distributed free space.

Q5)     What is a CA, control area?
A5)     A group of control intervals makes up a control area.

Q6)     What is a sequence set?
A6)     This is the part of the index that points to the CA and CI of the record being accessed.

Q7)     What is the index set?
A7)     This is the other part of the index.  It has multiple levels with pointers that ultimately reach to the sequence set.

Q8)     What is a cluster?
A8)      A cluster is the combination of the index, sequence set and data portions of the dataset.  The operating system gives program access to the cluster, ie. to all parts of the dataset simultaneously.

Q9)     What is the catalog?
Q9)     The catalog contains the names of all datasets, VSAM and non-VSAM. It is used to access these datasets.

Q10)   What is an alternate index?
Q10)   An AIX is a file that allows access to a VSAM dataset by a key other than the primary one.

Jcl and gdg interview questions

Q1) What
is a Generation Data Group (GDG)?
A1) Generation Data
Group is a group of chronologically or functionally related datasets. GDGs are
processed periodically, often by adding a new generation, retaining previous
generations, and sometimes discarding the oldest generation.

Q2) How
is a GDG base created?
A2) A GDG base
is created in the system catalog and keeps track of the generation numbers used
for datasets in the group. IDCAMS utility is used to define the GDG base.

Q3) What
is model dataset label(Model DSCB)?
A3) A model
dataset label is a pattern for the dataset label created for any dataset named
as a part of the GDG group. The system needs an existing dataset to serve as a
model to supply the DCB parameters for the generation data group one wishes to
create. The model dataset label must be cataloged. The model DSCB name is
placed on the DCB parameter on the DD statement that creates the generation
data group.

Q4) How
are GDGs concatenated?
A4) Generation
Data Groups are concatenated by specifying each dataset name and the
generation number for all generations of the generation data
group. Otherwise to have all generations of a generation data group,
omit the generation number. The DD statement will refer to all generations. The
result is the same as if all individual datasets were concatenated. If
generations are not on the same volume, this will not work.

Q5) How
is a new GDG coded?
A5) A new GDG is
coded as (+1) after the dataset name as follows: DSN=JAN.DATA(+1). This will
cause all generations to be pushed down one level at the end of the job.

Q6) When
should DISP=MOD is used?
A6) DISP=MOD is
used to either extend an existing sequential dataset or to create a dataset if
it does not exist. If the dataset exists, then records are appended to the
dataset at the end of the existing dataset. If the dataset does not exist, the
system treats MOD as if it were NEW, provided that the volume parameter has not
been used. If the volume parameter is used, the system terminates the job and
does not create the new dataset. MOD can be used to add to a dataset that
extends onto several volumes. Always specify a disposition of CATLG with MOD
for cataloged datasets, even if they are already cataloged, so that any
additional volume serial numbers will be recorded in the catalog.

Q7) How
is a dataset passed from one step to another?
A7) A dataset is
passed from one step to another based on what is coded on the DISP parameter.
The dataset can only be passed to subsequent steps
if PASS was used on the disposition
parameter.

Q8) How
are datasets concatenated?
08) Datasets are
concatenated by writing a normal DD statement for the first dataset and then
adding a DD statement without a DDNAME for each dataset
to be concatenated in the order they are to be read.
The following is an example of three datasets concatenated:
//YEARDAT DD DSN=JAN.DATA,DISP=SHR
// DD DSN=FEB.DATA,DISP=SHR
// DD DSN=MAR.DATA,DISP=SHR

Q9) What
is the difference between the JOBLIB and the STEPLIB statements?

A9) The JOBLIB statement is placed after the JOB
statement and is effective for all job steps. It cannot be placed in a
cataloged
procedure. The STEPLIB statement is placed after the EXEC statement and is
effective for that job step
only.
Unlike the JOBLIB statement, the STEPLIB can be placed in a cataloged
procedure.

Q10) Name some of the
JCL statements that are not allowed in procs.?

A10) Some of the JCL statements which are not allowed in
procedures are:
1. JOB, Delimiter(/*), or Null statements
2. JOBLIB or JOBCAT DD statements
3. DD * or DATA statements
4. Any JES2 or JES3 control statements

Jcl Procedures FAQs, Interview Questions

Q: How are in-stream procedures (procs) built?A: In-stream procedures are built by coding a set of statements and placing them after the JOB statement and before the EXEC statement. In-stream procedures begin with a PROC statement and end with a PEND statement. Up to 15 in-stream procedures can be included in a single job.
Each in-stream procedures may be invoked several times within the job. In-stream procedures can use symbolic parameters in the same way as catalogued procedures.

Q: What is the difference between an in-stream procedure and a catalogued procedure?A: An In-stream procedure is basically same as a catalogued procedure. The difference is that to execute an in-stream procedure one places it after the JOB statement and before the EXEC statement and must end it with a PEND statement. A catalogued procedure is catalogued on a procedure library and is called by specifying the procedure name on the EXEC statement. An in-stream procedure is useful to test the procedure before making it a catalogued procedure.

Q: Name some of the JCL statements that are not allowed in the procs.A: Some of the JCL statements that are not allowed in the procs are:
1. JOB Delimiter (/*) or Null (//) statements
2. JOBLIB or JOBCAT DD statements
3. DD * or DATA statements
4. Any JES2 or JES3 control statements

Q: What parameters are good candidates to make symbolic parameters?
A: Any parameter, sub parameter, or value in a procedure that may vary each time the procedure is called is a good candidate to be coded as a symbolic parameter.

Q: Which type of override parameter requires that one know the parameters that can be overridden?A: Regular parameters require that one know the parameters that can be overridden, such as step names within the procedure, the DDnames of the statements overridden, and the order of the DD statements.

Q: How is a symbolic parameter coded?A: A symbolic parameter is preceded by an ampersand (&) and followed by a name (&FIRST). The first character must be alphabetic. Symbolic parameters can be coded only in the operand field of the JCL statements; they cannot appear in the name or operation field of the JCL statements. If more than one value is assigned to the symbolic parameters on a PROC or EXEC statement, only the first one is used. Symbolic parameters may be coded in any order on the PROC or EXEC statement.

Q: How are values assigned to symbolic parameter?A: Values can be assigned to symbolic parameter on the PROC statement, on the EXEC statement, or on a SET command. Values containing special characters other than blank must be enclosed in apostrophes. The Values assigned to symbolic parameter can be of any length, but it cannot be continued onto another line.

Q: Can symbolic parameter concatenated?A: Symbolic parameter can be concatenated with other symbolic parameters, regular parameter or with the portions of the regular parameters as follows
Symbolic/symbolic – PARM-&FIRST&LAST
Symbolic/regular – SPACE-&SPACES
Symbolic/portion – SPACE-CTRK, &PRIMARY

Q: What are some of the rules involved in overriding parameters on the EXEC statements in a procedure?
A: To override EXEC parameter one should follow these rules
1. A PGM parameter cannot be overridden.
2. The parameter for each step do not need to be coded in the same order as they appear on the procedure EXEC statement
3. To add or override a parameter on an EXEC statement, code it as follows parameter.procstepname=value.
4. If a parameter which does not exist is coded on the EXEC statement, the parameter will be added
5. All parameters in each step must be coded in order: the first step must be coded first, second step second, third step third, etc.

Q: What are some of the rules involved in overriding DD statements in procs?A: The following rules apply when overriding a DD statement:
1. DD statement overrides precede the DDname with procstepname
2. The JCL parameter is replaced unless it does not exist on the original statement, in which case it is added. For the DCB each sub parameter can be overridden
3. DD statement overrides should carry DDnames that already exist in the step they are to effect
4. DD statement overrides must be coded preceding any added DD statement for the proc step
5. DD override statement must be listed in the order in which they are shown in the proc
6. DD override statement are only in effect for the duration of the run

Q: How are concatenated DD statements in the proc overridden?A: Overriding concatenated DD statements requires the following:
1. To override only the first DD statement in a concatenation, code only one overriding DD statement
2. To override all DD statements in a concatenation, code an overriding DD fo each concatenated DD statement
3. The overriding concatenated DD statements must be in the same order as the concatenated DD statement
4. Code a DDname on the first overriding DD statements only. Leave the DDname blank on the following DD statements.
5. To leave a concatenated statements unchanged, code its corresponding, overriding DD statement with a blank operand field