We have two SMFLIMxx policies in effect 1) JOBNAME(*) 2) JOBNAME(specific) with no region settings at all.
Regardless of the order the policies are defined in the member, the job with the specific jobname gets assigned the region limits defined in the JOBNAME(*) policy. What I'm trying to do is have all jobs except the ones specifically listed assigned the region limits in the JOBNAME(*) policy and nothing being done to the specifically listed ones. Yes, I can use RACF to prevent specific userids from being assigned limits set by the JOBNAME(*) policy, but there doesn't seem to be a way to do it on a jobname basis if there are multiple jobnames using that same RACF userid. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] On Thursday, August 22nd, 2024 at 8:21 AM, Radoslaw Skorupka <[email protected]> wrote: > How do you recognize the job is "specific"? > Is it smell or colour? :-) > > Seriously: > you can use jobname mask or RACF access to some resource. > Or some other identifiers, like jobclass, program name, stepname, > account number... > > > -- > Radoslaw Skorupka > Lodz, Poland > > > > > W dniu 20.08.2024 o 18:53, Mark Jacobs pisze: > > > How can I code SMFLIMxx such that all batch jobs be assigned limits using > > the policy, except for specific jobs. For those jobs I don't want the > > policy limits to be used. I've been reading the manual and can't seem to > > find a way to accomplish this task. > > > > Mark Jacobs > > > ---------------------------------------------------------------------- > 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
