Cross posted in VM and Linux390 lists.
A question arrised to me yesterday:
If I have and installation running z/VM (with no VSE or Z/OS guests),
but with DB2 and VisualAge I need an engine configured as CP or I can
run these workload under IFL?
Question arrised since customer should have some
Carlos,
What is the Release of your VM?
Rgs,
Fernando Gieseler
f...@br.ibm.com
+55 51 9988 8177
-- mens. original --
Assunto: A doubt: z/VM and Linux
De: Carlos Bodra - Pessoal cbo...@terra.com.br
Data: 18/08/2011 09:13
Cross posted in VM and Linux390 lists.
A question arrised
We may be getting a z114 to test the feasibility of z/VM/Linux on Z for our
shop.
I'm not a mainframer but I'd like to know what storage devices can be
provisioned for the z114 and what the preferred method is to accomplish
this.
--
Thank you,
Bob Molerio
Systems Administrator
New York
We finally have RACF LDAP server running on z/OS with the TDBM backend and
native authentication. We thought we were done as all our testing
completed successfully. However, when the operator booted Linux, the
console is flooded with the following messages on the shutdown and
startup. It is very
How often do you patch your linux servers. I have been patching once every 3-4
months (over 100 servers - sles 9 thru 11) and have been told that I had to
start patching much more frequently. I'd like to find out what other people are
doing.
Thank you
DB2 LUW runs quite well on Linux under z/VM and, for us at least, requires
fewer resources per server than the AIX boxes we came off of. Our VM LPAR
has no CPs defined to it - only IFLs. For us, the only need for CPs is to
run z/OS and to pay CA. If I could get the WebSphere crew to move off of
Hard part is done.
Now become the instance owner ( or dbadm or secadm depending on how your
security is configured ) and grant the user connect on the database and any
other useful things they need ( like, maybe, select on a table or two).
If the user will actually be logging on to the Linux
Bob,
I assume you are interested in SAN based storage, not direct attached
(System z can do it either way). I'm only familiar with IBM storage, so
the others on the list will have to chime in on other vendors. The FICON
adapters in the z114 can run in either FICON or FCP mode. In FCP mode,
Linux on 390 Port LINUX-390@vm.marist.edu wrote on 08/18/2011 10:10:16
AM:
From: Martha McConaghy u...@vm.marist.edu
To: LINUX-390@vm.marist.edu
Date: 08/18/2011 10:20 AM
Subject: Re: z114
Sent by: Linux on 390 Port LINUX-390@vm.marist.edu
Bob,
I assume you are interested in SAN based
Monthly.
Marcy
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Levy, Alan
Sent: Thursday, August 18, 2011 6:22 AM
To: LINUX-390@vm.marist.edu
Subject: [LINUX-390] patching frequency
How often do you patch your linux servers. I have been
In our RHEL 6, there is an RHNSD task that the man page says queries 'Red Hat
Network for updates and information'. It is suppose to check in every 4 hours,
the default, this is also specified in /etc/sysconfig/rhn/rhnsd.
According to /etc/init.d/rhnsd it uses /etc/sysconfig/rhn/up2date as its
We only patch twice a year, unless there's a specific security fix we
need before then.
-- Pat
On 08/18/2011 10:24 AM, Marcy Cortes wrote:
Monthly.
Marcy
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Levy,
Alan
Sent: Thursday, August
If someone told me to patch more frequently - I would make them explain
exactly how often and why. For convenience sake, patching every x weeks or
months might be nice .. but there should be policies in place that
distinguish between security fixes and other types, and give
rules/guidelines for
I should explain further. There is a group that evaluates everything put out
by the support providers.
They categorize them into criticial, urgent, and standard.
There is an install time frame for each level of severity.
For all intents and purposes, it usually ends up monthly here.
Marcy
And one other thing.
It doesn't matter what organization the patch is from, or what it's for, I
always apply it in a Test/Dev environment to make sure it does no harm.
Even 'super critical, got to have it now' patches go onto a Test/Dev
environment, if only for a few days.
Dave
Dave
Hi all,
I'm trying to figure out the best way to define authority to a SYSPROG
group under RACF/VM. I don't want SYSPROG members to have all authority
so I don't want to just add SPECIAL and OPERATION attributes to the group.
But they should be able to perform system-wide list operations and
We may be getting a z114 to test the feasibility of z/VM/Linux on Z for our
shop.
I'm not a mainframer but I'd like to know what storage devices can be
provisioned for the z114 and what the preferred method is to accomplish
this.
The usual suspects all work if you have FICON storage
On VM our SYSPROG users do not have any special RACF authority. We do have
LOGONBY access to all of the maintenance machines including MAINT and TCPMAINT.
This allows for any maintenance you may need to do. We also set the VM
privileges to ABCDEFG for those users which allows them to see and
I have the following set in /etc/ldap.conf
bind_policy soft
nss_initgroups_ignoreusers
root,ldap,haldaemon,messagebus,dbus,bin,daemon,postfix,sshd,polkituser,uuidd,100,101
However, these messages are overwhelming. I get them for udevd and vol_id.
These might be a startup timing issue as soon as
We may be getting a z114 to test the feasibility of z/VM/Linux on Z for our
shop.
I'm not a mainframer but I'd like to know what storage devices can be
provisioned for the z114 and what the preferred method is to accomplish
this.
The usual suspects all work if you have FICON storage
Hello, Troy.
Consider also give authority to individual userids, when justified. And
consider products self protection.
Example: DIRMAINT have his own mechanism to enable administrators
(AUTHUSER), RSCS have self protection for his commands, OPERATOR must be
managed by individuals defined into
Scott, only to feed this discussion:
Apply 5 patchs by month looks better than 15 by quarter or 30 by
half-year. Less corrections is faster, easy to analyze and less
problematic to fallback, if needed.
Is it a valid argument?
Regards,
PS. Only ideas, I don't work in the Linux team. Don't know the
Well - I mostly was objecting to the idea of 'patching more frequently'
without some structure and reasoning behind it. Patching just to patch
isn't really a strategy.
But yes - I would agree that it is usually better to apply a few patches at
once rather than many, for the reasons you state.
Your nsswitch says to search ldap before anything local. I use passwd:
files ldap (same for shadow group). Thus, it never even tries ldap
if it finds a local entry.
This has also come in handy for a few weird exceptions where the
application absolutely had to do something weird and
On 18/08/2011 14:22, Levy, Alan wrote:
How often do you patch your linux servers.
As often as necessary :)
I have been patching once every
3-4 months (over 100 servers - sles 9 thru 11) and have been told that I had
to start patching much more frequently. I'd like to find out what other
25 matches
Mail list logo
