Subject: RE: CICS startup JCL
From: Allan Peterson (Allan.Peterson@revera.co.nz)
Date: Mon Aug 31 2009 - 18:12:02 EDT
Well yes , but ....it has worked for 25 years , except once or twice when OPS forgot and that's what screwed us, and it also appears the nightly job checklist was not consulted, ie confirm that the CICS came to a normal EOJ before you start anything new I had been playing around with a thought that to make damn sure all the ducks were aligned CICS gone to EOJ, CICS logs copied, set the parameter and at startup time have some IF's If you have then copied the CICS logs to a backup and then initialized then does it impact a warm start. At month end CICS11 is shutdown and a CIC11R is started. CICS11R is pseudo DL/I read only (no update PSB's or applications), separate Databases and DFHJ01A/B, but uses the original DFHTEMP, RSD etc -----Original Message----- From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Tom Duerbusch Sent: Tuesday, 1 September 2009 9:38 a.m. To: VSE Discussion List Subject: Re: CICS startup JCL We use START=AUTO. That will do a WARM start if CICS was shutdown normally, or EMER if CICS came down abnormally. If I need a cold start done, we release the following job and bring CICS backup. * $$ JOB JNM=COLDPROD,DISP=L,PRI=3,CLASS=8,USER='TOM DUERBUS GENERATED * $$ LST CLASS=J,DEST=(,MAINT) // JOB COLDPROD SETUP PROD FOR COLD START /* ID STATEMENT SUPPRESSED */ // OPTION LOG // SETPARM XNCPU='' // EXEC PROC=$COMVAR,XNCPU // EXEC DTRSETP,PARM='CPUVAR&XNCPU;;SET XMODEF8=COLD' /* /& * $$ EOJ GENERATED Tom Duerbusch THD Consulting >>> <Rbotsis@aol.com> 8/31/2009 4:31 PM >>> We handle it with FAQS/ASO. COLD start always, but then we don't have DL/I.
This archive was generated by hypermail 2b25 : Wed Sep 02 2009 - 20:20:12 EDT