Now that the OP has clarified his requirement, my initial thought was that the PROC could be changed to simply re-submit a new job via INTRDR. This would direct the job to the required job class.
PROCA - do what you do now PROCB - INTRDR submit to run in different class. On Wed, Dec 19, 2018 at 3:37 AM Jesse 1 Robinson <[email protected]> wrote: > We historically use a combination of JES(2) exits to set JOBCLASS for a > whole host of reasons. PROC does not happen to be one, but with standard > documented exits, you can test for almost anything in one exit and > communicate with other exits to achieve the result you want. The great > Class Setter is probably Exit 6, which can take direction from other exits > to decide what class a job should run in. > > I'm not necessary recommending that a shop set off on an exit-writing > binge. In particular, in OP's case, I'm still puzzled as to what needs to > be accomplished. Just pointing out that the levers and buttons are probably > available to an ambitious coder. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > [email protected] > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Farley, Peter x23353 > Sent: Monday, December 17, 2018 10:48 PM > To: [email protected] > Subject: (External):Re: Enforcing CLASS in instream proc > > Peter, > > There is no way I know of to select or enforce a JOB class based on the > presence and usage of any particular PROC (instream or not). > > Your best bet may be to write a utility program that svans the DD's in the > job to see if it uses one of those product libraries and also retrieves to > JOB class via control block chasing. > > Then if the job class is not the one in which you want those > libraries/products to run, ABEND the job with a message to the programmers > to change the JOB CLASS to the required one and resubmit the job. > > Unless you have a product like JCLCHECK or JCLPREP which can scan JCL and > enforce shop standard JCL rules (like using the right JOB CLASS) I think > you are probably not going to be able to automate this requirement at all. > > There may be some JCL scanning tools on the CBT site that could possibly > help if you can't afford ISV products like JCLCHECK or JCLPREP. I haven't > investigated that area on CBT so I am not personally aware of any such > tools, but there may be some there. > > Is this desire to run zIIP-enabled software in a particular JOB CLASS just > a management request for no good technical reason, or are there real CPU > reporting or license-enforcement rules that specifying a particular job > class would make it easier to do or report? > > In other words, what problem does enforcing a particular job class for > zIIP-enabled software solve for you? > > Peter > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Peter > Sent: Sunday, December 16, 2018 2:51 AM > To: [email protected] > Subject: Enforcing CLASS in instream proc > > Hi > > We have some job which runs with a default class B. > > We would like to redirect some of the Job which uses a particular instream > to use a different class. > > Is there a way to enforce the class selection while using a specific > instream proc ? > > I am seeing the manual on instream. Procedure override but I don't find > any reference on my requirement > > > Has anyone tried this similar and have a working solution ? > > Peter > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
