Jcl Error #10114
Contents |
a recovery action. CAN The job or started task was canceled by the operator or by a TSO user before execution. This code is also possible if the job-termination event (type 3P) is missing. CCUN The completion code is unknown. The job or started task has ended, but no completion code is available. This code is also possible if the job-end event (type 3J) is missing. Check the job log and SYSLOG. JCCE An error during JCC (job completion checker) processing prevented the JCC from determining an error code for the http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.ieam800/hh452i.htm operation. JCL A JCL error was recognized after the job or started task began to execute, or a JCL error was recognized after syntax checking in the internal reader. JCLI A JCL error occurred immediately; that is, the error was detected before the job or started task began. This code is also possible when both the job-start event (type 2) and the job-end event (type 3J) are http://publib.boulder.ibm.com/tividd/td/TWS/SC32-1268-00/en_US/HTML/EQQQ1MST46.htm missing. MCP The operation was manually set to error in the MCP dialog. OFxx The system that the operation is defined on has gone offline. The WSOFFLINE parameter on the JTOPTS initialization statement specifies that started operations should be marked as ended-in-error. xx is the status and extended status of the failing operation. Operations that were running (status SS) have a step-code error status of OFFL. OJCV An error occurred during JCL-variable substitution when the job or started task was submitted, or the scheduler detected an error in the RECOVER statement during automatic recovery. Browse the JCL for the operation or the EQQMLOG data set to find more information about the failure. OSEQ A job or started task began to execute before all its predecessors had completed. This can occur only if the job was not submitted by the scheduler and if either HOLDJOB(NO) or HOLDJOB(USER) is specified for the scheduler event writer options. For fault-tolerant workstations, the OSEQ code can indicate that a dependency on another operation or a special resource was added after the job started, but before the event reached the controller. Refer to Customization and Tuning. OSUB A failure occurred when the scheduler attempted to
- JOB NOT RUN - JCL http://www.ibmmainframeforum.com/jcl/topic5424.html ERROR JES, JES2, JCL utilities, IDCAMS, Compile & Run JCLs, PROCs etc... Post a reply Previous topic • Next topic • 12 http://www.hivmr.com/db/89xp1sdd3adadm3msa1zz7fka1kja9dz posts • Page 1 of 2 • 1, 2 IEFC452I - JOB NOT RUN - JCL ERROR by cooldude14344 » Sat Mar jcl error 05, 2011 1:32 am HI All,I get the JCL Error - JOB NOT RUN with JCL Error Number different everytime. I get the new numbers everytime i run the jcl .The numbers i got till now are029325728167839The erro message and job details are below. jcl error codes Please help to resolve it.19.49.44 JOB06848 IRR010I USERID S38707 IS ASSIGNED TO THIS JOB. 19.49.44 JOB06848 IEFC452I DOCEASYT - JOB NOT RUN - JCL ERROR 029 ------ JES2 JOB STATISTICS ------ 28 CARDS READ 201 SYSOUT PRINT RECORDS 0 SYSOUT PUNCH RECORDS 14 SYSOUT SPOOL KBYTES 0.00 MINUTES EXECUTION TIME 1 //DOCEASYT JOB CLASS=B,MSGCLASS=X,MSGLEVEL=(1,1),TIME=(30,00), // NOTIFY=S38707 //*JCL: ISPF UTILITY DATASET 2 //PROCLIBS JCLLIB ORDER=(CSFT.MASTER.PRODSUP.SKELS) //* 3 //STEP0120 EXEC PROC=NWCPROC, // USERHLQ=S38707.DDFD, // LVL2=TEST, // NWCIN='S38707.NWTEST.CSFFILE', // LODLOAD1='DOCT.NDVR.DOC.LOADZOS', // LODLOAD2='DOCS.NDVR.DOC.LOADZOS', // LODLOAD3='DOCU.NDVR.DOC.LOADZOS', // RGMLOAD1='DOCT.NDVR.DOC.RGMLOAD', // RGMLOAD2='DOCS.NDVR.DOC.RGMLOAD', // RGMLOAD3='DOCU.NDVR.DOC.RGMLOAD', // CEXEC='DOCT.NDVR.DOC.CEXEC', // REXXLIB='DOCT.NDVR.DOC.REXX', // DOCREG='DOCT.NDVR.DOC.DOCREG', // DATADEF='DOCT.NDVR.DOC.DATADEF', // DYTABL='DOCT.NDVR.DOC.DYTABL', //* // FONTDEF='DOCS.NDVR.DOC.FONTDEF', // ROCTL='DOCT.NDVR.DOC.ROCTL', // AVGREC=U XXRUNGEN1 PROC USERHLQ='DOCTD.DEFAULT', XX NWCIN='DOCTD.DEFAULT', XX LODLOAD1='DOCP.NDVR.DOC.LOADZOS', XX LODLOAD2='DOCP.NDVR.DOC.LOADZOS', XX LODLOAD3='DOCP.NDVR.DOC.LOADZOS', XX LODLOAD4='DOCP.NDVR.DOC.LOADZOS', XX RGMLOAD1='DOCP.NDVR.DOC.RGMLOAD', XX RGMLOAD2='DOCP.NDVR.DOC.RGMLOAD', XX RGMLOAD3='DOCP.NDVR.DOC.RGMLOAD', XX RGMLOAD4='DOCP.NDVR.DOC.RGMLOAD', XX* DOCREG='DOCP.NDVR.DOC.DOCREG', XX DATADEF='DOCP.NDVR.DOC.DATADEF', XX FON
against those dbs are via terminalemulation or screen scrapping technology that connects a propriatory middleware. I think also that the mainframe has OSLAN. As the mainframe is not going to go away we need to expose transactions withina WLS environment. So the questions are as follows. 1 : is tuxedo the right technology 2 : does tuxedo provide any technology to do this, or do we still need a thirdparty screen scraping product ? Any comments will be very usefull. Thanks Nick DB:4.78:Tuxedo &Amp; Icl Mainframe 89 Tuxedo has two adapters, one TMA OSI-TP adapter to link Tuxedo to ICLmainframe using OSI and WTC to connect to WLS. In this configuration youcould have end to end transactions (i.e. from ICL to WLS and vice versa).There are delpoyments in such configurations, but these customers alreadyhad Tuxedo in their environment. If you do not have Tuxedo already and are looking for WLS/ICL connectivity,you could look for a WLS adapter for ICL mainframe first. I am not awarefor any such offerings.Deepak "Nick" nick.floros@theaa.com wrote in message news:40e1a60c$1@mktnews1... Hi, we have a number of dbs hosted on an ICL Trimetra SY 680 mainframe. Thedbsare writen in IDMSX, currently transactions against those dbs are viaterminalemulation or screen scrapping technology that connects a propriatorymiddleware. I think also that the mainframe has OSLAN. As the mainframe is not going to go away we need to expose transactionswithina WLS environment. So the questions are as follows. 1 : is tuxedo the right technology 2 : does tuxedo provide any technology to do this, or do we still need athirdparty screen scraping product ? Any comments will be very usefull. Thanks Nick Read All 2 Posts RELEVANCY SCORE 3.39 DB:3.39:Tuxedo Osi Tp Interface mk We are currently investigating using an OSITP Domain link from our Tuxedo 6.5 Systemrunning on NT4 to our ICL Mainframe running Open VME and Open TPMS 630. Our problem is that we are unsure if the link is possible, what if any additionalsoftware we require and how to configure the communications. The ICL documentation mentions that the VME system can interface to BEA TuxedoServers (through one or more Connect OSI TP Gateways) and the Tuxedo documentationfor build_dgw mentions buildi