Jcl Error Cond Code 0012
Contents |
while using IEBGENER JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc... Post a reply Previous topic • Next topic • 2 posts • Page 1 of 1 maxcc=12 while using IEBGENER by weishi » Tue May 12, 2009 11:17 am Hi, when I used IEBGENER to copy a PS, maxcc=12,but the data set was copied and no errors encountered, I want to know the reasons,thanks. my jcl: Select all//QR115 JOB ,'QR115',MSGLEVEL=(1,1),MSGCLASS=A, // CLASS=A,NOTIFY=QR115 //**************************************
Cobol Error Codes
//* QR115 SHIWEI 2723103003 * //* THIS PROGRAM COPY A SEQUENCE DS jcl interview questions * //* TO A NEW SEQUENCE DS * //************************************** //S1 EXEC PGM=IEBGENER
Jcl Tutorial
//SYSPRINT DD SYSOUT=* //SYSIN DD DUMMY //SYSUT1 DD DSN=QR115.SOFTWARE.EXAMPLE, // DISP=SHR //SYSUT2 DD http://www.ibm.com/support/knowledgecenter/SSEPH2_13.1.0/com.ibm.ims13.doc.msgs/msgs/0012.htm DSN=QR115.SOFTWARE.NEWONE, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(2,1)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=80), // VOL=SER=USER03, // UNIT=3390 // and jesysmsg:Select allICH70001I QR115 LAST ACCESS AT 13:31:47 ON TUESDAY, MAY 12, 2009 IEF236I ALLOC. FOR QR115A01 S1 IEF237I JES2 ALLOCATED TO SYSPRINT http://www.ibmmainframeforum.com/jcl/topic1872.html IEF237I DMY ALLOCATED TO SYSIN IEF237I 0A98 ALLOCATED TO SYSUT1 IGD100I 0A98 ALLOCATED TO DDNAME SYSUT2 DATACLAS ( ) IEF142I QR115A01 S1 - STEP WAS EXECUTED - COND CODE 0012 IEF285I QR115.QR115A01.JOB00650.D0000101.? SYSOUT IEF285I QR115.SOFTWARE.EXAMPLE KEPT IEF285I VOL SER NOS= USER03. IEF285I QR115.SOFTWARE.NEWONE CATALOGED IEF285I VOL SER NOS= USER03. IEF373I STEP/S1 /START 2009132.1332 IEF374I STEP/S1 /STOP 2009132.1332 CPU 0MIN 00.01SEC SRB 0MIN 00.00SIEF375I JOB/QR115A01/START 2009132.1332 IEF376I JOB/QR115A01/STOP 2009132.1332 CPU 0MIN 00.01SEC SRB 0MIN 00.00S******************************** BOTTOM OF DATA ******************************** weishi Posts: 1Joined: Tue May 12, 2009 11:03 am Hasthanked: 0 time Beenthanked: 0 time Top Re: maxcc=12 while using IEBGENER Top Re: maxcc=12 while using IEBGENER by dick scherrer » Tue May 12, 2009 1:25 pm Hello and welcome to the forum,What is in the sysprint?I suspect that there might be a conflict with the 2 datasets.Somewhere the reason for the cc=12 is recorded. Hope this helps,d.sch. dick scherrer Global modera
or worth reading for someone please like mainframegeek facebook page. Abend Codes Abend happens during the execution of a program in a step(JCL). Generally it can be categorized into system abend and user abend. System Abend - It will occurs when the system http://mainframegeek.me/abend-codes-and-explanation/ is not able to execute a statement which is coded in a program. This abend code will be thrown by OS. User Abend - This is due to unexpected condition occurs in data passed; this abend will be thrown by http://condor.depaul.edu/jpetlick/JCL_09.html application based on the requirement. Condition Code Abends CC=0001 - (1016) PIE JOBS - BAD PART NUMBER - FOLLOW PACBOOK VERY CAREFULLY CC=001 - I/O ERROR CC=002 - I/O INVALID RECORD CC=0004 - DATASET NOT FOUND, TABLESPACE IN COPY jcl error PENDING, ETC MAY BE OK(CHECK COND STATEMENTS OR CALL ADM TO VERIFY) CC=0008 - EQUIP CHECK, UNABLE TO DBR DB RLAO00, RC-08 SQL ERROR, EMPTY DATASET CC=0010 - (CC=0016 IN HEX) BAD DATA CC=0012 - I/O ERROR TAPE, VSAM DATASETS CLOSED, INVALID DATA, EMPTY TABLE, COULD BE ANYTHING CC=0014 - CC=0016 - COULD BE ANYTHING, CONTENTION ,INVALID DATA, EMPTY TABLE, # OF FILES EXPECTED NOT EQUAL TO # OF FILES RECEIVED CC=0020 - COULD BE ANYTHING (CATCHALL) CC=0030 - DB2 codes list pdf TABLES WRONG DATES CC=0152 - ERROR ATTEMPTING TO TRANSLATE NEXT TRANSACTION CC=0696 - FTP LINE DOWN CC=804 OR 80A - REGION SIZE TOO SMALL - SPECIFY REGION=0M CC=1000 - BAD DATA, CONTENTION(-911) CC=1008 - TOTALS OUT OF BALANCE CC=1016 - NUMBER OF FILES EXPECTED DOES NOT EQUAL NUMBER RECEIVED, BAD DATA, CONTENTION CC=1999 - DATA EXCEPTION, BAD DATA CC=2000 - RESOURCE NOT FOUND (07D0), PROGRAMMING ERROR WAITING FOR FILE, RACF (-922), REBIND (-805) CC=2004 - CYCLE OUT OF SEQUENCE CC=2016 - TOO MUCH DATA FOR ARRAY SIZE, TABLE UPDATE INCORRECT, NULL DATA CC=2444 - INVALID RECORD LENGTH CC=8000 DATASET ALREADY IN USE, I/O ERROR, FILES NOT SENT RESOURCE NOT AVAILABLE CC=FFF - FATAL INTER ADDRESS COMMUNICATION ERROR User Abends U046 - NOT ENOUGH OR NO SORT WORK SPACE ALLOCATED. U048 - USER DOES NOT HAVE ACCESS AUTHORIZATION FOR THE DATASET U061 - REORDER DATASETS, CHECK BLOCKSIZES. LARGEST BLOCKSIZE FIRST U063 - CHECK SPELLING OF DD STATEMENTS U099 - DATASET NOT FOUND U0000 - DB2 STOPPED UTILID, TABLESPACE U0007/U0240 - VSAM I/O ERROR ON ACKS DATASET(WIDEBAND PROBLEM) U0100 - USER ERROR U0102 - PROBLEM WITH CHECKPOINT - MAY NOT HAVE BEEN ANY CHECKPOINTS U0103 - ENTRY NOT FOUND U0111 - TAPE TOO SHORT U0136 - I/O Error on a Read Data CCW for the first VTOC record on a migration target volume U0240 - BAD TRANSMISSION U0378 - I/O ERROR, DIRTY TAPE DRIVE, EQUIP CHECK U0436 -
greater. Create a new load module library using either JCL or TSO/ISPF 3.2 The compile/link/go procedure puts programs into a temporary PDS dataset and then executes the program via a referback in the GO step. The GO step of the compile, link and go procedure has an execute statement of //GO EXEC PGM=*.LKED.SYSLMOD which is a referback to a program the library created in the link edit step. Make the current COB2J procedure more readable using temporary datasets and symbolic parameters. To populate the PDS with load modules: - copy a module from another load module PDS - compile and link a program into the new PDS (create a PROC that does the Compile and Link or use PROC member COB2CLJ of SYS1.PROCLIB or use CL member from JPETLIC.CSC.CNTL) MVS search SYS1.LINKLIB as the default load library when looking for programs. To execute a program saved in a library other than SYS1.LINKLIB, direct MVS to other PDS load libraries by using STEPLIB DD and/or JOBLIB DD statement(s). //STEPLIB DD can be used after an EXEC statement and will direct the system to look in the DSN= library only when executing that step. i.e. //stepname EXEC PGM=PARMCODE //STEPLIB DD DSN=CCPF##.CSC.LOAD,DISP=SHR //JOBLIB DD can be used after the JOB card and will direct the system to look at the specified DSN= libraries in those steps which do not have a //STEPLIB DD statement. i.e. //jobname JOB (etc.) //JOBLIB DD DSN=CCPF##.CSC.LOAD,DISP=SHR //stepname EXEC PGM=PARMCODE Load module libraries may have to be reorganized because each compile and linkedit of a program will cause replacement copies to use a new data space. PROGRAM STATUS - a completion code number issued at a program's termination. As each program returns control to the system, it gives the system its final program status as a coded number. The final program status number may be useful for determining whether to execute the subsequent programs, MVS preserves the program status number and makes it available for job control. IBM software using the following convention regarding program execution: COND CODE 0000 - program successful COND CODE 0004 - warning messages COND CODE 0008 - Serious flaws COND CODE 0012 - Very serious flaws COND CODE 0016 - Disaster COBOL programmers control the final status of their programs by moving a number to RETURN-CODE. If RETURN-CODE is not used in the program, the default number is zero. i.e. MOVE 16 TO RETURN-CODE GOBACK. COND CODE - AN EXEC PARAMETER TO BYPASS STEP EXECUTION Define conditions which, when true, do not execute a step. Stated conversely, if the con