One of our product uses below JCL and JES2 commands to cancel the jobs running in the JES2 environment based on JOB ID and it works absolutely fine in the JES2 environment, however, we haven’t tested it in the JES3 environment. One of our customers wants to know whether it works in JES3 or not? we have hit an impasse because we don't have the JES3 environment, so we had requested to setup JES3, unfortunately, our server is down with some H/w issue and it appears will take more time.
Does anyone have a JES3 environment and test this, it would be of great help.!! or Any suggestions/pointers are highly appreciated.!
To run this script you should have set up JESINTERFACELEVEL to 2 and also the RACF CONTROL access to profile JES%.**
I have gone through it, to cancel a job the command is different. I would like to know whether my script is Compatible in JES3. That's why I need help from someone who has the JES3 environment can verify this. please let me know your view on this.
Joined: 10 May 2007 Posts: 2407 Location: Hampshire, UK
I do not see any script but the JCL you posted will work on JES3 as JCL is the same. JES3 commands are different so your JES2 commands will not work and your command will be processed on the system that the job was submitted on unless you specify differently (SYSAFF ???) so if you put a JES3 command in there you must make sure that the system affinity is set too or that the job is submitted on the JES3 system.
I do not know why you need a TIME or a REGION parameter on an IEFBR14. Both are a waste of every resource .
Ok, for starters I think that you should change the
to a JCL command statement like
// COMMAND '$CJ6911'
substituting the JES2 cancel command with the proper JES3 equivalent. You will have to put it after the JOB statement. The initiator must allow commands, and the job userid must have operator command authority, the latter I think is identical to a JES2 system.