Thanks all for your help, everything working now. Is there any benefit/harm in proceeding with the setup of RACF TCP/IP documented in appendix A of the TCP/IP planning guide? The limited TCP/IP services we use seem to be working just fine with the generic setup of VMBATCH described in the virtualization cookbook.
Chris Will -----Original Message----- From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott Rohling Sent: Wednesday, June 12, 2013 3:09 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: After initial setup of generic vmbatch resource, all new ids are set up with discrete (I think) I believe RAC RDELETE VMBATCH LINMON would do it for your example.. without a discrete definition it should default to the generic one (if I'm reading Bruce correctly) - so just delete it. Scott Rohling On Wed, Jun 12, 2013 at 12:01 PM, Will, Chris <cw...@bcbsm.com> wrote: > Is there a command to "fix" the userids I have already set up? > > -----Original Message----- > From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of > Bruce Hayden > Sent: Wednesday, June 12, 2013 2:15 PM > To: LINUX-390@VM.MARIST.EDU > Subject: Re: After initial setup of generic vmbatch resource, all new > ids are set up with discrete (I think) > > What you do is leave that line in the config file but with no value, as in: > RACF_RDEFINE_VMBATCH_DEFAULTS= > Then, DIRMAINT won't create a VMBATCH resource when a new user is created. > You'd also do this if you don't control Diag D4 (so you have no need > for VMBATCH resources. And the same is true for VMRDR - if you don't > use it or use generic resources instead, put this line in CONFIGRC DATADVH: > RACF_RDEFINE_VMRDR_DEFAULTS= > > > > On Wed, Jun 12, 2013 at 1:53 PM, Scott Rohling > <scott.rohl...@gmail.com > >wrote: > > > Are you saying that you are using the DIRMAINT/RACF interface and > > it's > not > > generating VMBATCH right? If so, I'm not sure how much you can alter > > this.. I'd have to read up on these options in CONFIGRC DATADVH where > the > > following line is from: > > > > RACF_RDEFINE_VMBATCH_DEFAULTS= UACC(NONE) AUDIT(FAILURES(READ)) > > > > I don't think that allows you to specify the generic profile though.. > > > > I have found that you're fairly limited in what you can do with the > > DIRMAINT/RACF 'interface' .. you would likely have to use a > > DIRMAINT exit > > - or simpler - an EXEC you run after adding a new user via DIRMAINT to > > tweak RACF the way you really want it. Either that or I just don't know > > all the right RACFxxxxx = values in CONFIGRC DATADVH..... > > > > Scott Rohling > > > > > > On Wed, Jun 12, 2013 at 10:31 AM, Will, Chris <cw...@bcbsm.com> wrote: > > > > > Here is a display of a new userid I set up with dirmaint. It > > > looks like the vmbatch resource is not generic which I want > > > > > > rac rlist vmbatch linmon > > > CLASS NAME > > > ----- ---- > > > VMBATCH LINMON > > > > > > LEVEL OWNER UNIVERSAL ACCESS YOUR ACCESS WARNING > > > ----- -------- ---------------- ----------- ------- > > > 00 DIRMAINT NONE ALTER NO > > > > > > When I initial set up racf using the procedures in the the > > > Virtualization Cookbook for z/VM 6.2 all ids used a generic vmbatch. > > > Here is an example from another lpar. > > > rac rlist vmbatch linmon > > > CLASS NAME > > > ----- ---- > > > VMBATCH ** (G) > > > > > > LEVEL OWNER UNIVERSAL ACCESS YOUR ACCESS WARNING > > > ----- -------- ---------------- ----------- ------- > > > 00 IBMUSER NONE ALTER NO > > > > > > How do I change these ids to use the generic vmbatch? > > > > > > Chris Will > > > > > > > > > > > > > > > > > > > > > > > > The information contained in this communication is highly > > > confidential > > and > > > is intended solely for the use of the individual(s) to whom this > > > communication is directed. If you are not the intended recipient, > > > you are hereby notified that any viewing, copying, disclosure or > > > distribution of this information is prohibited. Please notify the > > > sender, by electronic mail or telephone, of any unintended receipt > > > and delete the original message without making any copies. > > > > > > Blue Cross Blue Shield of Michigan and Blue Care Network of > > > Michigan are nonprofit corporations and independent licensees of > > > the Blue Cross and > > Blue > > > Shield Association. > > > > > > ------------------------------------------------------------------ > > > -- > > > -- For LINUX-390 subscribe / signoff / archive access > > > instructions, send email to lists...@vm.marist.edu with the > > > message: INFO > > > LINUX-390 or visit > > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > > ------------------------------------------------------------------ > > > -- > > > -- For more information on Linux on System z, visit > > > http://wiki.linuxvm.org/ > > > > > > > -------------------------------------------------------------------- > > -- For LINUX-390 subscribe / signoff / archive access instructions, > > send email to lists...@vm.marist.edu with the message: INFO > > LINUX-390 or visit > > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > -------------------------------------------------------------------- > > -- For more information on Linux on System z, visit > > http://wiki.linuxvm.org/ > > > > > > -- > Bruce Hayden > z/VM and Linux on System z ATS > IBM, Endicott, NY > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > > > The information contained in this communication is highly confidential > and is intended solely for the use of the individual(s) to whom this > communication is directed. If you are not the intended recipient, you > are hereby notified that any viewing, copying, disclosure or > distribution of this information is prohibited. Please notify the > sender, by electronic mail or telephone, of any unintended receipt and > delete the original message without making any copies. > > Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan > are nonprofit corporations and independent licensees of the Blue Cross > and Blue Shield Association. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, send > email to lists...@vm.marist.edu with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ The information contained in this communication is highly confidential and is intended solely for the use of the individual(s) to whom this communication is directed. If you are not the intended recipient, you are hereby notified that any viewing, copying, disclosure or distribution of this information is prohibited. Please notify the sender, by electronic mail or telephone, of any unintended receipt and delete the original message without making any copies. Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are nonprofit corporations and independent licensees of the Blue Cross and Blue Shield Association. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
