RE: CICS startup JCL

New Message Reply Date view Thread view Subject view Author view Other groups

Subject: RE: CICS startup JCL
From: Allan Peterson (Allan.Peterson@revera.co.nz)
Date: Mon Aug 31 2009 - 19:19:51 EDT 

Thanks I like it  .....this is  mine and I'm looking to fine tune before applying to the preprod & production ones

Allan

/*
// SETPARM CICS41=''
// SETPARM CICS41J=''                      <== I never implemented this
// EXEC PROC=CICS,CICS41,CICS41J
/*
 // IF CICS41 EQ ACTIVE THEN
// GOTO EMERGCY
/* IF CICS41J EQ ACTIVE THEN
/* GOTO EMERJNL
/*
/. COLD
// EXEC DTRSETP,SIZE=AUTO,PARM='CICS;NINZ.PRODUCT;SET CICS41=ACTIVE'
/*
// EXEC DTRSETP,SIZE=AUTO,PARM='CICS;NINZ.PRODUCT;SET CICS41J=ACTIVE'
/*
NOLOG
// UPSI 10000000
// EXEC DFHSIP,SIZE=7426K,DSPACE=2M
SIT=41,START=COLD,BMS=FULL,$END
/*
// GOTO FINISH
 /. EMERGCY
// EXEC DTRSETP,SIZE=AUTO,PARM='CICS;NINZ.PRODUCT;SET CICS41=ACTIVE'
/*
/* EXEC DTRSETP,SIZE=AUTO,PARM='CICS;NINZ.PRODUCT;SET CICS41J=ACTIVE'
/*
// UPSI 10000000
// EXEC DFHSIP,SIZE=7426K,DSPACE=2M
SIT=41,BMS=FULL,$END
/*
/. FINISH
// EXEC DTRSETP,SIZE=AUTO,PARM='CICS;NINZ.PRODUCT;SET CICS41=INACTIVE'
/*

From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of industrynews@winwholesale.com
Sent: Tuesday, 1 September 2009 10:28 a.m.
To: VSE Discussion List
Subject: Re: CICS startup JCL


owner-vse-l@Lehigh.EDU wrote on 08/31/2009 05:02:55 PM:
> What have you put into your JCL to ensure that a CICS is cold, emer,
> warm started.
> At the moment I get the OPS to key in start=cold,$end or just $end .

        I use the VSE-supplied method with a little modification.  The supplied method is to use the CPUVARn.PROC member to hold the current status and start options for CICS.  The start option we have in that proc is as follows:

SETPARM XMODEBG='WARM  ' * PARTITION STARTUP MODE *
SETPARM XMODEF1='WARM  '
SETPARM XMODEF2='WARM  '
SETPARM XMODEI1='AUTO'
SETPARM XMODEI2='AUTO'
SETPARM XMODEI3='AUTO'

        Class "I" is for the interactive (CICS) partitions.  Then, in the CICS startup, VSE supplies something like this (different partition id, but you get the idea):

// SETPARM XNCPU=''
// EXEC   PROC=$COMVAR,XNCPU
// SETPARM XAPPLI1=''
// SETPARM XMODEI1='AUTO'
// EXEC   PROC=CPUVAR&XNCPU,XAPPLI1,XMODEI1
// EXEC   PGM=DTRSETP,PARM='CPUVAR&XNCPU;;SET XSTATI1=ACTIVE'
/* EOD

        For more dynamic usages, I modified that and have this:

// SETPARM XNCPU=''
// EXEC   PROC=$COMVAR,XNCPU
// SETPARM XPARTCP=''
// EXEC   PROC=CPUVAR&XNCPU,XPARTCP
// SETPARM XAPPL&XPARTCP.=''
// SETPARM XMODE&XPARTCP.='AUTO'
// EXEC   PROC=CPUVAR&XNCPU,XAPPL&XPARTCP.,XMODE&XPARTCP
// SETPARM APPL=''
// EXEC   REXX=RXSETSYM,PARM='APPL=XAPPL&XPARTCP',APPL,XAPPL&XPARTCP
// SETPARM MODE=''
// EXEC   REXX=RXSETSYM,PARM='MODE=XMODE&XPARTCP',MODE,XMODE&XPARTCP
// EXEC   PGM=DTRSETP,PARM='CPUVAR&XNCPU;;SET XMODE&XPARTCP.=AUTO'
/* EOD
// EXEC   PGM=DTRSETP,PARM='CPUVAR&XNCPU;;SET XSTAT&XPARTCP.=ACTIVE'
/* EOD

        The above modification is for three reasons.  The primary reason is to not have the partition identifier hard-coded in the JCL.  Thus, the above dynamically determines the correct partition identifier and combines it with other prefixes to dynamically obtain reference to the other symbolic parameters.  The second reason is so that a COLD start, if desired, may be controlled from outside of the JCL.  All that is required is to edit the CPUVARn.PROC member (which BIM-EDIT gives direct access to such editing -- perhaps DITTO, too) to change the appropriate MODE parameter to "COLD".  Then, the finally reason is to automatically change the start mode back to the default of "AUTO" after the current start mode (whatever it may be) is extracted for later use -- as follows:

// EXEC  PGM=DFHSIP,SIZE=8704K,PARM='SIT=P1,APPLID=&APPL.,START=&MODE.,X
               GRPLIST=PRODLIST,$END',DSPACE=3M

        Then, of course, the final bit is also VSE-supplied but I modified that, too:

// EXEC   PGM=DTRSETP,PARM='CPUVAR&XNCPU;;SET XSTAT&XPARTCP.=INACTIVE'
/* EOD

Sincerely,

Dave Clark

WinWholesale Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331


This email message and any attachments is for use only by the named addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission.

New Message Reply Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b25 : Wed Sep 02 2009 - 20:20:12 EDT