Thanks to all who responded to my recent question about the jobclass override
field in the XPL. Our current exit for z/OS 1.4 is in exit 3, which I think
should have been exit 2. That is why I am putting it in exit 2/52 when we go
to z/OS 1.7.
Dave Barrows
---
At 17:33 -0500 on 02/02/2006, Bill Planer wrote about Re: JES2 exit
52 jobclass override:
I just had occasion to look at the code that processes the job class
override.
It moves just the first byte of the override field in the parameter list
into a one byte class field in the relevent JES2
:
MainframeSubject: Re: JES2 exit 52
jobclass override
Discussion List
I just had occasion to look at the code that processes the job class
override.
It moves just the first byte of the override field in the parameter list
into a one byte class field in the relevent JES2 control block. (I don't
have it in front of me right now, but probably a JCT field.) So just se
If you really want to do the deed during input processing, exits 20/50 are the
right places--set X020JCLS/X050JCLS as per the JES2 Installation Exits book. I
prefer Skip's suggestion of making such decisions at conversion time.
Bob
Dave Barrows wrote:
I am researching how to force job class
I haven't seen a reply to this question, so I'll toss in a couple of pence.
Are you converting an old exit to run in 1.7, or are you adding new
function you did not have in previous releases?
We use Exit 6 to force job class, mainly because by that time in processing
we know a lot more about a job
I am researching how to force job class selection through JES2 exits in z/OS
1.7. Looking at the XPL fields, I see one that says it is for job class
override. If I want to force a job to execute in class 'R', do I just move 'R'
to
this field? The reason I am asking is the field shows up as C
7 matches
Mail list logo