Ivica and others. Thank you for the help. Increasing the size of the
control disk fixed the problem.
Steve
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of Ivica Brodaric
Sent: Saturday, March 12, 2011 8:12 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: SFS
I will be out of the office starting 14/03/2011 and will not return until
21/03/2011.
On Paternity leave ! If urgent please contact TST MF front shop on 52580.
Three Films Chronicle IBM's Century of Innovation
ARMONK, N.Y. - 10 Mar 2011: IBM is marking its 100th year as a
company of innovators and inventions through a series of
documentary films that chronicle the ways in which the company
has changed the world through scientific and technology
Not that it matters,
In my situation, this is what worked.
Update MPROUTE CONFIG
Update sysname TCPIP
Update directory entry for TCPIP
set vswitch vswitch1 disconnect
set vswitch vswitch1 rdev 2f00
set vswitch vswitch1 connect
force tcpip
autolog tcpip
set vswitch vswitch2 disconnect
set
Hi,
We did a P.O.R this weekend. We added DASD rdev, the only thing we are
supposed to do and now we can vary online a same rdev to both MVS V
M. We
check back the modifications. The chpid are shared, the rdev are
shareable=NO in the MVS IODEF. We don't know where to look at. We chang
ed
Basically all you did was tell the OSs that the devices were not being
shared. If you did not specifically limit the access to a particular LPAR
then all the LPARs can see because the CHPID is shared.
On Mon, Mar 14, 2011 at 1:29 PM, Alain Benveniste a.benveni...@free.frwrote:
Hi,
We did a
Is there a good or widely accepted way to wait in autolog1 until the vmsys:
pool is up and available?
--
Robert P. Nix Mayo Foundation.~.
RO-OC-1-18 200 First Street SW/V\
507-284-0844 Rochester, MN 55905 /( )\
-
A non-zero return code from QUERY FILEPOOL STATUS filepool indicates
the target filepool is off-air. Brace for a flood of response messages
if the filepool *is* on-air.
On 3/14/2011 3:34 PM, RPN01 wrote:
Is there a good or widely accepted way to wait in autolog1 until the
vmsys: pool is up
On Monday, 03/14/2011 at 03:34 EDT, RPN01 nix.rob...@mayo.edu wrote:
Is there a good or widely accepted way to wait in autolog1 until the
vmsys:
pool is up and available?
In decreasing order of preference:
1. Loop on ACCESS VMSYS:AUTOLOG1. B with an appropriate delay. (Enroll
AUTOLOG1, of
Bob, we use the following PIPE technique: Pipe Literal +30 | Delay |
Pipestop
The 30 is seconds. VMSERVS comes up pretty quick, but I can still
understand a need to momentarily pause.
Steve
From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On
Behalf Of RPN01
Sent:
On Mon, 14 Mar 2011 13:29:59 -0400 (EDT), Alain Benveniste wrote:
We did a P.O.R this weekend. We added DASD rdev, the only thing we
are supposed to do and now we can vary online a same rdev to both
MVS VM. We check back the modifications. The chpid are shared,
the rdev are shareable=NO
Hello!
Apologies in advance, Len, if this is the wrong place to do this, but I
remember registering for that event. I even have the printed out
confirmation thing for the event.
But I've not gotten a confirmation note from the service machine where all
of you are for the event. According to the
12 matches
Mail list logo
