CICS : CANNOT NEWCOPY

rajesh 35 · New User Joined: 21 Sep 2010 Posts: 7 Location: chennai

Hi,

I have compiled an existing a program with some modifications in it, while doing new copy in cics region got below error message “CANNOT NEWCOPY” .

SET PROG(XXXX) NEW
STATUS: RESULTS - OVERTYPE TO MODIFY
Prog(XXXX ) Len(0010352) Cob Pro Ena Pri Ced CANNOT NEWCOPY
Res(001) Use(0000000068) Bel Uex Ful Qua Le3

I have checked my program in library where this library assigned in STEPLIB of CICS region program is found and also I have cross checked the LEN(0010352) in CICS region with LEN 2870 (HEX ) in steplib library so from this I understood that it pickup of latest load but it is saying that CANNOT NEWCOPY message.

Why it saying that CANNOT NEWCOPY even the load is exist in steplib library ?

To solve this I have recompiled the program again now length of load in CICS steplib is 00002878 ( HEX ) and tried to do new copy in CICS region using CEMT this time LEN is ( 0010352 ) it means it is picking up the old load which I have replaced with new load.

SET PROG(XXXX) NEW
STATUS: RESULTS - OVERTYPE TO MODIFY
Prog(XXXX ) Len(0010352) Cob Pro Ena Pri Ced CANNOT NEWCOPY
Res(001) Use(0000000068) Bel Uex Ful Qua Le3

Even why it is taking the old load which has no more exist in steplib due to it is replaced the new load ( length 2878 Hex ) ?

Bill Woodger · Posted: Wed Aug 03, 2011 1:07 pm

Have you googled? Hit the manuals? Asked around your colleagues? Your technical support?

Mostly you'll get quicker answers that way.

When you "compiled again", what had you changed to make it 8 bytes longer? Not relevant to the answer, I'm sure, but just wondering.

Try to see if RES or USE is getting in the way.

PeterHolland · Posted: Wed Aug 03, 2011 1:36 pm

Try to do a DISCARD PROGRAM before the SET PROGRAM

dbzTHEdinosauer · Posted: Wed Aug 03, 2011 1:52 pm

might want to check if someone is expediting the module
CEMT INQ TASK

Robert Sample · Posted: Wed Aug 03, 2011 4:42 pm

valyk · Posted: Wed Aug 03, 2011 7:07 pm

Robert Sample · Posted: Wed Aug 03, 2011 7:21 pm

valyk, another possibility is that an EXEC CICS LOAD PROGRAM(XXXX) command was executed in some CICS transaction somewhere.

Bill O'Boyle · Posted: Wed Aug 03, 2011 7:53 pm

DBZ has the answer.

Someone is Expediting the program and has walked away from the session, gone home, went to lunch, or the session was cancelled altogether, but Xpediter still has the program.

Go to CECI and issue a RELEASE PROGRAM until you get a NOTFND.

Then go back to CEMT and try the NEWCOPY (check the RES count first).

Normally, you should be issuing a PHA ("PHASEIN") as opposed to NEW.

Bill

rajesh 35 · New User Joined: 21 Sep 2010 Posts: 7 Location: chennai

Hi All

Thanks for your comments, now I can able understand and think in different ways which cause the issue.

Hi Robert/Valyk/Bill,

I have gone through google find about what RES specifies or indicates,

PeterHolland · Posted: Wed Aug 03, 2011 9:04 pm

valyk · Posted: Wed Aug 03, 2011 9:13 pm

Robert Sample · Posted: Wed Aug 03, 2011 9:25 pm

Yes, I forgot to put the HOLD on the command in my post -- I've used it in the past, so I should have gotten it right!

sriramp777 · New User Joined: 29 Sep 2008 Posts: 6 Location: Bangalore

I read through the replies on this topic. But I am facing a peculiar behaviour.

Even after doing the below,
LOAD (progname)
RELEASE (progname) [twice]

I get the message as INVREQ with EIB details as

EIBRESP=+0000000016 EIBRESP2=+0000000007

And I still have the Rescount for progname greater than 0.

I would appreciate if someone would help me to find out what is holding on the progname.

Many thanks,

Regards,
Sriram

Robert Sample · Posted: Tue Dec 17, 2013 4:15 pm

As was made clear in the discussion for this thread, if the RESCOUNT is greater than zero, you cannot do a NEWCOPY on that program -- period. If the RESCOUNT is 7, you must execute the RELEASE 7 times to get the RESCOUNT to zero. Of course, if a transaction executes to increase the RESCOUNT before you get the NEWCOPY done, the NEWCOPY will fail -- again.