Isn't this simply a case where your JES Exit 52 code hasn't been modified to 
cope with job classes greater than one character? 

I'm assuming the logic of the code goes something like:

-Ignore comment cards.
-Search jobcard (or statement buffer) or for text CLASS=, save the next byte in 
a single byte field (DS CL1 or similar) in the exit work area.
-At the same time search for TIME= parameter, remove it. 
-On last jobcard reached and processed, add comma to the end, and compare the 
saved one-character jobclass byte to a table of single-byte jobclasses, add 
appropriate site standard TIME= from table to a new trailing jobcard.

If so, you need to update the exit to:
-Change the field in the exit work area where the jobclass is saved to be eight 
bytes instead of one. 
-Change the logic of the jobcard parsing to save a jobclass of up to eight 
characters (everything between CLASS= and the next comma or blank). Pad (or 
pre-load) saved jobclass field with blanks.
-Change the table of site jobclasses to hold eight-byte jobclasses (pad with 
blanks) instead of single byte.
-Change the compare of the jobclass to compare eight bytes, not a single byte.

The above isn't awesomely difficult. Is the real problem your site lacks anyone 
with the necessary assembler skills?

Ant.

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Staller, Allan
Sent: Friday, 5 September 2014 12:01 AM
To: [email protected]
Subject: Re: JES2 v2.1 exit question

I do something similar, however, in my case it's slightly different.
A specific job class is assigned a CPU limit by JES. JES2 Exit 6 is use to 
eliminate the TIME= from the jobcard, (coded by users to avoid the limit),  and 
force the default limit specified in the relevant jobclass definition.

HTH,

<snip>
All jobs that are submitted in class G get a time parm.
This way, the user cannot override the time value that can be coded in the 
JOBCLASS statement.

The problem is that if we create a class named GABC (the class in the case is 
four characters long) it will also get the time parm added.
All of our classes are defined as:
JOBCLASS(G)  AUTH=INFO,BLP=YES,COMMAND=DISPLAY,JOURNAL=NO,SWA=ABOVE,
          MSGLEVEL=(1,1),PERFORM=1,REGION=2M,RESTART=NO,TIME=(6,0)

Gadi


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Lizette Koehler
Sent: Thursday, September 04, 2014 12:47 PM
To: [email protected]
Subject: Re: JES2 v2.1 exit question

So which of the following is true
1)  All jobs using CLASS=G get a time parm
2)  Specific Job Names in CLASS=G get a time parm

The reason I ask is that on the JOBCLASS statement in the JES2 DECK can provide 
a default time parameter for jobs.  If the user codes the TIME= on the EXEC or 
JOB Statement, I believe that would override the default in the
JES2 JOBCLASS statement.  Could you let me know why that may or may not work 
for you?


Could you provide the JOBCLASS statements from the JES2 Init deck for the 
Classes of G,A,B,C?


Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] 
> On Behalf Of ??? ?? ???
> Sent: Thursday, September 04, 2014 1:18 AM
> To: [email protected]
> Subject: JES2 v2.1 exit question
>
> Hi Everyone,
>
> We are in the process of customizing z/OS v2.1 We have a JES2 exit
(EXIT52) that
> adds a time parameter to certain classes.
> It looks like the variable the exit is using is only one byte long, 
> and
this is a problem
> since we want to use long class names.
>
> For example, we add a time card to jobs that are submitted in CLASS G.
> If we define a class called GABC, jobs that are submitted in that 
> class
also have a
> time card added to them.
>
> How can we get the full value for the class name.
>
> Thanks
>
> Gadi
></snip>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to