Subject: RE: CICS error
From: Kevin Corkery (kcorkery@comcast.net)
Date: Fri Apr 04 2008 - 12:45:46 EST
Maybe ... // EXEC DTRIATTN,PARM='MSG <yourcics>,DATA=CEMT S PROG(<yourprogram>) PHASEIN ' There is a small window of opportunity for the problem from the time of the COPY until the command but it would generally be negligible. BTW, the above assume CICS/TS is in use although somewhat similar steps would be required for CICS/VSE. Also, if your have more than one CICS image you may wish to consider issuing the command to all instances unless there's a hard and fast rule to identify the program as being "owned" by a particular image. In our case we always MOVE the phase from out test library to our production library (no LPAR here) so we issue the command to both CICS instances. That way the production library member is always used on the test system unless there's a test version in the test library which, of course, preceeds the production library in the search chain. Kevin P Corkery Independent Consultant Voorhees, New Jersey -----Original Message----- From: owner-vse-l@Lehigh.EDU [mailto:owner-vse-l@Lehigh.EDU] On Behalf Of Randy Evans Sent: Friday, April 04, 2008 1:30 PM To: VSE Discussion List Subject: RE: CICS error No apology is warranted - the existence of this problem and your mention of only a single CICS is how I (erroneously) arrived there. Since you *do* have a production CICS and this problem still occurs, then I suggest the problem lies more with the change management process. As you pointed out, the programmer "should" NEWCOPY, but it certainly appears that the job done isn't getting done in all cases. I think if you search back through these archives, you might find some suggestions from others on how to automate the NEWCOPY function in the same JCL that performs the LIBR COPY. If that isn't successful, you might pose a new query back on this list as to how others have skinned that cat lately. In my past experience, the process of moving programs test-to-production was made the responsibility of computer operations, using JCL provided by the systems programmers. The jobs involved included steps to perform the NEWCOPY using a home-grown utility. This process significantly improved CICS uptime statistics for production CICS but as you can guess, I don't recall anyone in the applications development group being much in favor of this change at the time (mid 80s). Randy Evans, Viaserv, Inc.
This archive was generated by hypermail 2b25 : Sat May 17 2008 - 00:35:06 EDT