Page 1 of 1

copy error while doing a new copy in CICS region,

Posted: Fri Jan 03, 2025 8:24 pm
by Arul Ravi
Hi All, need help

I am getting new copy error while doing a new copy in CICS region, I believe I have done a new copy while I am using debugger, after realising that I have terminated the debugger and tried doing new copy but still didn’t work.

I tried doing CECI RELEASE PROGAM this also giving an error, response INVREQ AND EIBRESP -16, EIBRESP2- 7

Any help to resolve this is highly appreciated 

Thanks

Re: copy error while doing a new copy in CICS region,

Posted: Sat Jan 04, 2025 11:24 am
by Anuj Dhawan
The error you’re encountering during a new copy in the CICS region is likely due to the program being locked or in use by a CICS task, possibly as a result of the earlier debugging session.

Understand the INVREQ Error
  • EIBRESP -16: This indicates INVREQ (Invalid Request).
  • EIBRESP2 7: This is a secondary reason code that typically signifies the program is currently in use or cannot be released because of an active reference.
Try

Code: Select all

CEMT INQUIRE PROGRAM(PROGRAM-NAME) 
Look at the USECNT field in the output. If it’s non-zero, the program is still in use by a task. If so, we should be purging the task - to know task, use

Code: Select all

CEMT INQUIRE TASK
Note the task ID and terminate:

Code: Select all

CEMT SET TASK(task-id) PURGE
After ensuring no active tasks are using the program, issue the following command:

Code: Select all

CEMT SET PROGRAM(PROGRAM-NAME) RELEASE
This should reset the lock on the program.

Retry New Copy.

Re: copy error while doing a new copy in CICS region,

Posted: Mon Jan 06, 2025 12:25 pm
by Arul Ravi
Thank you, this worked. 

Re: copy error while doing a new copy in CICS region,

Posted: Mon Jan 06, 2025 12:46 pm
by Anuj Dhawan
Great, appreciate the feedback.

Re: copy error while doing a new copy in CICS region,

Posted: Wed Jan 08, 2025 2:17 am
by florry372
Nothing beats that moment when a technical hiccup gets resolved, especially in CICS. Props to Anuj for the detailed steps, classic example of knowledge sharing saving the day!