Hi,
I am asking this in the main forum hopefully it will be a simple answer, that I 
just don’t see.

So I have lots of experience setting up RACF  STARTED class with STDATA so that 
started tasks run under a certain userid.

Here we run our CICS's as jobs, since we are a development company, the 
programmers, can start/stop their CICS's when they need to.

We are doing WEB pipeline development and I setup the directory structure for 
the CICSDFLT userid and the group is everyone else.

If a batch job submits/starts CICS the CICS userid is picked up and everything 
works great.

If the user needs to recycle the region its picking up their userid and then 
the CICS gets access issues.

Is there a way to force it to use the DFLTUSER for batch jobs like I can setup 
for started tasks?

I think I could use user=DFLTUSER on the jobcard, but then I would have to 
setup those userids as RESTRICTED, because no password. There is a small 
security risk with this, but these userids don’t have TSO Segments, so its a 
limited exposure.

Is there any other way to set this up?  Besides as STC's.

Ms Terri E Shaffer
Senior Systems Engineer,
z/OS Support:
ACIWorldwide – Telecommuter
H(412-766-2697) C(412-519-2592)
[email protected]
________________________________
 [https://go.aciworldwide.com/rs/030-ROK-804/images/aci-footer.jpg] 
<http://www.aciworldwide.com>
This email message and any attachments may contain confidential, proprietary or 
non-public information. The information is intended solely for the designated 
recipient(s). If an addressing or transmission error has misdirected this 
email, please notify the sender immediately and destroy this email. Any review, 
dissemination, use or reliance upon this information by unintended recipients 
is prohibited. Any opinions expressed in this email are those of the author 
personally.

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

Reply via email to