Rob, we had a similar problem back in the middle of Dec. 2016. It was on a new
HMC that came with a z13s that we had installed in the summer of 2016. We
opened a ticket with IBM. They replaced it and that fixed it.
Steve
-Original Message-
From: Linux on 390 Port
Mike, is this distro dependent or does it affect all distros?
Thanks,
Steve
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Michael
MacIsaac
Sent: Monday, December 19, 2016 9:12 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Root, sudo, su and preserving
Will z/VM and/or zLinux support the Netapp product FAS8060?
Thanks,
Steve
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
There are at least 3 combinations of DASD usage for Linux implementation.
They are:
1) Everything on 3390 storage
2) Everything on non-3390, external disk via a fiber card
3) A combination of 1 & 2
What are the thoughts on using these? Is one preferred over the other?
Thanks,
Today is World Penguin Day
I'm surprised nobody has mentioned it. I just heard about it a few minutes ago.
Steve
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the
Are you asking if you have and IFL and IPL z/VM from it, will it use it? Yes.
Are you running an existing z/VM in a non-IFL LPAR, will z/VM use it? I don't
think so but IBM can be pretty tricky sometimes.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On
While we do not currently run z/Linux, we rarely IPL z/VM. Even in a previous
work environment, we rarely would IPL z/VM. The IPL would usually occur at the
Spring and Fall time change. But with changes to z/VM, we don't have to do
that anymore.
Do you really need to cycle z/Linux or is it
If you want read only, multiple links can be done.
If you need R/W access, you might consider an SFS pool and sub-directory.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Thursday, April 02, 2015 3:02 PM
To:
Agree with both of you. Watched an episode last night on 60 Minutes(?)
regarding rare earth magnets. Discussed mining process to final product.
Technology to make these magnets was created here, in the US, and then sold.
We probably shouldn't clog the list with this thread but selling that
In your steps, I don't see where you do a DIRECTXA to update the online
directory.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Dazzo,
Matt
Sent: Wednesday, March 11, 2015 3:29 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Unable to get device
Ditto what Scott said. We have to do compliance also, but we are told
specifics; what functions or process are supposed to comply with what rules or
standards.
Steve
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Scott
Rohling
Sent:
With the way you describe your situation, you need to copy the files on the
existing/current CMS minidisk to a temporary area. That could be another
minidisk of equal or larger size or TAPE DUMP the minidisk (if you have some
kind of tape subsystem available). Once the COPY or TAPE DUMP is
While your statement is technically correct, it is best to use 500 as the mdisk
with RSU's, ptf's, etc. That being said, the user should move 500 to a larger
area, some place with approx. 1500 cylinders.
Steve
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU]
(cross posted to Linux list)
Has anyone setup a z/Linux print server and are using it in production? I am
wondering if there any pit falls, etc. And if you had to do it over, would you
do it again. I'm considering setting one up but don't want to get into a
management nightmare.
Thanks,
Regarding XSTOR and VM 6.3. Is it true XSTOR will be going away in VM 6.3
and/or after 6.3?
Steve
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of David
Boyes
Sent: Monday, December 30, 2013 10:39 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re:
I don't doubt that since z is a different architecture (in their minds).
There will be some differences between the Linux's but again, it mostly
architecture based. Someone can probably go into the finer details of
the differences.
-Original Message-
From: Linux on 390 Port
Sorry, MHH. Not a good day for typing.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Gentry, Steve
Sent: Thursday, August 30, 2012 4:58 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Too true to be funny - 51% of the surveyed Americans think
I've seen similar pictures with letters 'MMH' (Miracle Happens Here)
linked to said cloud.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
McKown, John
Sent: Thursday, August 30, 2012 11:33 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Too true to be
I'm all for that since VSAM for z/VM has been removed from marketing.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Mike Noel
Sent: Wednesday, August 08, 2012 1:39 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: porting kicks
Actually I meant
To my knowledge there is no product currently marketed by IBM to
enterprises, etc.
IBM does have a product that is available only to ISV. I think you have
to make a case for the box initially and then it's renewed on an annual
basis.
I read about this last week, kept the documentation but can't
Have you manually checked to see if the DASD is online? i.e. QUERY DASD volid
or QUERY dasd_addr
If they are not online, check your SYSTEM CONFIG file to be sure they either
are not coded as OFFLINE or use an ONLINE statement to put them on line at IPL.
If they are online check again to be
I still like to occasionaly connect to zLinux and use the GUI Desktop
interface. IIRC, Xterm isn't a good option because of security issues.
What is the preferred method, these days, to use the GUI Desktop?
(Yes, I realize that using the GUI, Desktop isn't the best thing to do)
Thanks,
Steve
22 matches
Mail list logo