In a previous life at the late great Security Pacific, we an *elaborate* scheme based on account numbers. Even the job name was generated from account number. To control all this, we had a VSAM file containing all valid account numbers along with indications of who could submit jobs with each number. An array of JES2 and SMF exits were employed to make all this work. At the end of the year, account numbers were used for chargeback to respective departments for resource usage.
There is no way in h*ll I would recommend this complex scheme for a modern shop. But yes, with enough time and $$, it can be done. . . 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 robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Lizette Koehler Sent: Wednesday, November 4, 2020 10:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: JES2 Policies *** EXTERNAL EMAIL - Use caution when opening links or attachments *** Initial Request: The current goal is to change a job's class or service class depending on certain values in the accounting information. It also seems to me that a JCL tool, Like JCLPLUS could put rules into JCL Scanning and force users to adhere to a standard. But that would mean you have a Source management system that is used to deploy Jobs to various systems. It could have rules that say, if Account Code is this, then the job should have Service Class STCLOW and CLASS X Lizette -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Allan Staller Sent: Wednesday, November 4, 2020 11:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2 Policies Wouldn't RACF jobclass controls be more appropriate? -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Joe Monk Sent: Wednesday, November 4, 2020 10:31 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: JES2 Policies [CAUTION: This Email is from outside the Organization. Unless you trust the sender, Don’t click links or open attachments as it may be a Phishing email, which can steal your Information and compromise your Computer.] Radoslaw, I think what the OP is really saying is that certain accounts should be restricted from certain jobclasses i.e. DEV cant use PROD jobclasses. So, if they code a CLASS=X, but the account info says that they dont have access to CLASS=X, then dump the job. OP: This has been around a long time, and is very mature... Joe On Wed, Nov 4, 2020 at 8:20 AM R.S. <r.skoru...@bremultibank.com.pl> wrote: > W dniu 04.11.2020 o 13:10, Gadi Ben-Avi pisze: > > Hi, > > I've started looking into JES2 Policies. > > > > The current goal is to change a job's class or service class > > depending > on certain values in the accounting information. > > >From reading the manual, it seems that this is possible. > > > > Has anyone done something like this? > > Is there a way to debug these policies? > > > > Is this feature mature enough to use? > > I dare to disagree ...with your goal. More precisely I disagree with > your presentation of the goal. > Does it really have to depend on account information? Why? > > That means user has to code something in the jobcard, in the first > positional. So he may code CLASS= keyword as well, can't he? > Maybe your accnt infor is already somehowe controlled (my guess, lack > of information). However jobclass can be RACF-controlled. > And this is quite mature way to control job classes and (indirectly) > service classes. > > -- > Radoslaw Skorupka > Lodz, Poland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
