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.
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.