View previous topic :: View next topic
|
Author |
Message |
Musab Ahmed
New User
Joined: 10 Dec 2012 Posts: 37 Location: India
|
|
|
|
Hi All,
I moved a modified PROC into production through endevor but the production job that is running using that PROC is currently running with the previous PROC.
The modified PROC is not reflecting in the current run. The PROC was moved at around 02:30 P.M and the job runs for every two hours starting at 12:00 P.M.
I checked the instance at 14:00 and 16:00 and 18:00 hrs but it still uses the old PROC. I checked the PROC in endevor and it shows the modified PROC.
We use TWS as a scheduler at our site.
Any idea why this is happening? |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
instead of asking on a forum You should speak to Your TWS support
we do not know the system setup, they do. |
|
Back to top |
|
|
Nic Clouston
Global Moderator
Joined: 10 May 2007 Posts: 2455 Location: Hampshire, UK
|
|
|
|
When were the jobs actually submitted? At run time or before your Endevor update? |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
again speak to Your support,
generally the <promotion> process for JCLs and PROCs is different from the one for a COBOL program |
|
Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007 Posts: 1742 Location: Tirupur, India
|
|
|
|
Yes, I am 94.5% sure that TWS has not loaded the latest version of the JCL from your ENDEVOR library.
In our shop, TWS loads the complete day's schedule in the morning and if any JCL changes are made to the ENDEVOR library then the job needs to be loaded into TWS manually, so the updated version is picked up.
Ask your operations team to load the latest version of the JCL from Endevor library into scheduler and restart the job. Most likely it would work. |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
Quote: |
Yes, I am 94.5% sure that TWS has not loaded the latest version of the JCL from your ENDEVOR library. |
TWS does not load procedures.
Maybe the TS is using an in-stream procedure? |
|
Back to top |
|
|
Musab Ahmed
New User
Joined: 10 Dec 2012 Posts: 37 Location: India
|
|
|
|
Hi All,
I have found the issue. There was a HOLDPROC configured in the JCLLIB ORDER statement. An old version of the PROC was sitting in the HOLDPROC while the new version was placed in the main PROCLIB by Endevor. So the old version was picked up by the job.
I have now deleted the old PROC from the HOLDPROC and the new PROC was picked up. It was a simple mistake from my end to not check if there was a PROC already sitting in the HOLDPROC.
Thanks all for your suggestions. |
|
Back to top |
|
|
vasanthz
Global Moderator
Joined: 28 Aug 2007 Posts: 1742 Location: Tirupur, India
|
|
|
|
Thanks for letting us know |
|
Back to top |
|
|
Marso
REXX Moderator
Joined: 13 Mar 2006 Posts: 1353 Location: Israel
|
|
|
|
Usually you can see where the proc is coming from in the JESYSMSG output in SDSF:
Code: |
STMT NO. MESSAGE
2 IEFC001I PROCEDURE XXXXXXX WAS EXPANDED USING SYSTEM LIBRARY HLQ.PROC.LIB |
|
|
Back to top |
|
|
Musab Ahmed
New User
Joined: 10 Dec 2012 Posts: 37 Location: India
|
|
|
|
The idea of old PROC sitting in HOLDPROC never struck my mind so never bothered to look into JESYSMSG. |
|
Back to top |
|
|
|