On Mon, 5 Oct 2009 00:48:49 +0000, Ted MacNEIL wrote: >>Some characteristic might be better than jobname. What about jobclass? And >>I still think about OWNER. Either >production jobs run with job scheduler as OWNER, or job scheduler has >sufficient authority to control the >OWNER of submitted jobs. > >Why OWNER? >Userid is the common control for production (independent of job-name). > I'm naive; enlighten me. In what cases does userid differ from OWNER? How can the programmer control these independently? Rexx has a userid() function; JCL has &SYSUID. Does either Rexx or JCL have a function or variable to query OWNER? Conversely, SDSF shows OWNER. If I scroll right far enough, will I see userid?
>>Some programmers might have >both test and production IDs. The production IDs would have no RACF TSO >segments, guranteeing that production jobs are not submitted from TSO sessions. > >Giving programmers production ID's is one heck of an exposure. > I'm naive; I don't work in a production shop. I bow to your expertise about separation of functions. >>RACF profiles would severely limit test ID access to production data >sets (likely read-only). > >In most (if no all) shops this is already restricted. >And, usually, not even read only is allowed. > As above. >>Much of the enforcement could >be delegated to common RACF facilities, with less than the historical >(pre-RACF technology) dependency on user >exits sensitive to jobnames. > >Welcome to 1980! >I know of nobody using jobname to protect access. >But, I could be wrong! > Jobname must be protecting access to something, else what's the point of enforcing jobname rules and the intense concern that test programmers not use production jobnames? Prior plies in this thread suggest that in some chargeback shops jobname is used to protect access to funds in those charged accounts. But this could be likewise based on OWNER (userid?). And isn't there an ACCOUNT parameter on the JOB statement which seems to be designed for this purpose? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
