Wasn't it that you moved MAINT CF1 and that a SHUTDOWN REIPL used the
contents of the old CF1.
I tried to APAR it, but got a WAD..
2009/11/16 Schuh, Richard
> It does reread the system config file. Several years ago, we had a problem
> of it picking up the old module. The way we got around that
On Monday, 11/16/2009 at 02:53 EST, Rob van der Heij
wrote:
> You're putting different traces in my mouth. It does not have to be a
> bogus PGM New PSW. It can also be something happening in the program
> check handler. A popular trick is when the old PSW is massaged in some
> way before doing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is exactly what CSE is meant for. Yes, we use it.
CSE + Dirmaint shared directory + Shared disk == not quite a cluster.
(I'm still holding on for cluster level split brain protection, as well
as the nifty live migration in the someday SSI)
-
Cross posted to linux-390 and ibmvm:
I kind of waited to see if anyone from IBM would even mention this here. It
came out last week. Prices have come down... a lot...
http://www-03.ibm.com/systems/z/solutions/editions/linux.html
Those of you thinking of consolidating or even adding more need
My mistake - I was linking with the wrong vdev address. VM:Account
expected 1A0, not 123.
Thanks for the responses.
Dave
-Original Message-
From: Scott Rohling
Reply-to: The IBM z/VM Operating System
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: VM:Account & MAINT's 123 disk
Date: Mon, 16
It does reread the system config file. Several years ago, we had a problem of
it picking up the old module. The way we got around that was to specify the
MODULE CPLOAD parameter. If you do that, it will work regardless of whether you
have changed the CP. I imagine it probably will work without t
We do that across several lpars. We run with a shared directory (DIRMAINT).
We have put code in place to verify that the Linux guest is not running on
another lpar.
Paul Feller
AIT Mainframe Technical Support
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listse
You're not really specifying the requirements.. but reading between the
lines - you want to be able to bring up the guest on one LPAR or the
other.. so you will have to share the full volumes.
You don't necessarily need unique minidisks for the 191 or swap,
though...
What 'is' the requirement?
We share DASD between two z/VM LPAR's, and have guests set up so they
can log on to either one. We use the Cross-System Link (XLINK) feature
of CSE to make sure that they don't try to run on both LPAR's at once.
Dennis
"Of all tyrannies, a tyranny exercised for the good o
It's the "assuming of course" part that will bite you :) One false move and
wham, all is gone.
And how to keep the directory in sync is another bit of the fun.
The future promises to solve this for us.
In the meantime, you can use CSE.
Or wait...
Marcy
"This message may contain confidentia
My mistake, I have always been under the impression that SHUTDOWN REIPL did not
re-read the SYSTEM CONFIG file. Thanks for clarifying that.
Thank you,
Scott
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Marcy Cortes
Sent: Monday,
Not in 6.1, but the future one.
Not sure if it has a number or not yet.
Many of us will be dancing in the streets when it shows up.
Marcy
"This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you mu
Have you applied all the zaps from CA to VMACCT? We experienced a VMACCT PRG001
abend and VMACCT looping problem on z/VM 5.3 and z/VM 5.4. It was fixed by a
zap from CA. I don’t know the case/issue number as I was not the one applying
the zap.
Our VMACCT is link to the MAINT 123.
From: The IB
Single System Image is not in z/VM 6.1. It's a Statement of Direction,
which means IBM intends to put it in a future release, but isn't
promising anything.
Dennis
"Of all tyrannies, a tyranny exercised for the good of its victims may
be the most oppressive. It may be bett
No, VM:Account does not need a write link to the object directory. VM:Secure
and VM:Director are the only VM:Manager products that need a write link to the
object directory. MAINT 123 will show up as OS-formatted when you access it
under CMS. That’s normal.
Reloads the nuc AND re-reads the system config.
Marcy
"This message may contain confidential and/or privileged information. If you
are not the addressee or authorized to receive this for the addressee, you must
not use, copy, disclose, or take any action based on this message or any
informat
Does a SHUTDOWN REIPL 'reload' the CP Nucleus?
I applied a PTF and generated a new nucleus. After renaming the current CPLOAD
MODULE to CPOLD MODULE, I copied the one from 493 (K). If I instruct
operations to do a SHUTDOWN REIPL, will the new nucleus be loaded? I think it
does, but would l
Make sure it is a LINK to MAINT’s 123 as 1A0 RR
LINK MAINT 123 1A0 RR
Verify the name in the VMACCT CONFIG file on VMACCT 191 you should see a
statement like this toward the top
DIRECT 1A0 540RES
If yours does not say 540RES than you need to change it to match the VOLSER of
wh
VM:Account is fine with a RR link.
But it wants a link to a full pack minidisk where the active object directory
is housed.
And you must put a statement in it's VMACCT CONFIG with the virtual address and
the real label like:
DIRECT 1A0 540RES
In the dir:
LINK MAINT 123 1A0 RR
Marcy
"Th
I bet you will be happy when z/VM 6.1 is installed and the Single image
facility is ready for production.
Larry Davis
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Robert J McCarthy
Sent: Monday, November 16, 2009 4:08 PM
To: IBMVM@
Oops -- I saw CA and then just assumed it was the directory management
product you were using.. don't do an MW link for VMACCT! Not sure
exactly why it wants to read the object directory... but a readonly should
suffice.
Sorry!
Scott
On Mon, Nov 16, 2009 at 2:34 PM, Scott Rohling wrote:
>
Does your VM:Account software a good level to support the z/VM level?
Usualy, DIRMAINT 123 and MAINT 123 point to the same physical disk.
The VM Resident is not CMS formatted indeed, it contains other stuff than
only CMS files. When the disk is formattted (using ICKDSF CPVOL), ICKDSF
will write so
I'm quite sure it will want an MW link to MAINT 123 since it will need to
update the directory...
Scott
On Mon, Nov 16, 2009 at 2:29 PM, Dave Keeton wrote:
> I am attempting to install CA:Account and I have been unable to get it to
> start properly (it abends) because it isn't reading the obje
I am attempting to install CA:Account and I have been unable to get it
to start properly (it abends) because it isn't reading the object
directory. I have defined a read-only link to MAINT's 123 disk (540RES)
where the user directory is located, but it appears as OS formatted and
not CMS to the VMA
We have a growing VM/Linux environment with currently about 75 linux gues
ts
spread across three VM lpars. All DASD is defined as shared. All of the
linux guests have been defined as TCPIP Layer 2; so that we can easily mo
ve
guests between lpars for performance/maintenance reasons. Each guests
On Mon, Nov 16, 2009 at 8:04 PM, Alan Altmark wrote:
> Only a class C user can escalate a user's privilege beyond what is in
> their directory entry.
>
> USER OPERATOR ** ABDEFGS
> COMMAND SET PRIVCLASS -S
Oooh... I bow deep and admire the cool elegance of this piece of art.
On Mon, Nov 16, 2009 at 6:19 PM, Alan Altmark wrote:
>> As soon as I reply with >>r 00,sysp=00,clpa<< everything dies with a
>> HCPGIR453W CP entered; program interrupt loop message.
>
> As Rob says, HCP453W indicates that the PROGRAM NEW PSW was corrupted or
> otherwise not valid when a Program
And then only if the set privclass feature is enabled in SYSTEM CONFIG
Scott
On Mon, Nov 16, 2009 at 12:04 PM, Alan Altmark wrote:
> On Monday, 11/16/2009 at 01:03 EST, Kris Buelens
> wrote:
> > No, he won't. But, with CP class A, he can issue SET PRIVCLASS * +S.
>
> Only a class C user can es
On Monday, 11/16/2009 at 01:03 EST, Kris Buelens
wrote:
> No, he won't. But, with CP class A, he can issue SET PRIVCLASS * +S.
Only a class C user can escalate a user's privilege beyond what is in
their directory entry.
USER OPERATOR ** ABDEFGS
COMMAND SET PRIVCLASS -S
Then the operator
Thank you for verifying my assumption.
Thank you,
Scott
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Kris Buelens
Sent: Monday, November 16, 2009 12:02 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: Question on MODIFY COMMAND
No, he won't. But, wi
No, he won't. But, with CP class A, he can issue SET PRIVCLASS * +S.
You your change is only safe to avoid accidental FORCEs or SHUTDOWNs
2009/11/16 Wandschneider, Scott
> If I change SHUTDOWN and FORCE with the following:
> MODIFY COMMAND SHUTDOWN PRIVCLASS S
> MODIFY COMMAND FORCEPRIVC
If I change SHUTDOWN and FORCE with the following:
MODIFY COMMAND SHUTDOWN PRIVCLASS S
MODIFY COMMAND FORCEPRIVCLASS S
...and OPER1 does not have class S but does have class A, can OPER1 still
successfully issue SHUTDOWN or FORCE?
Thank you,
Scott R Wandschneider
Senior Systems
On Monday, 11/16/2009 at 08:17 EST, "J. Cassidy"
wrote:
> am trying to run (believe it or not) an OS/390 2.4 guest under z/VM 5.3
> (0703) on a CP (z990).
...
> As soon as I reply with >>r 00,sysp=00,clpa<< everything dies with a
> HCPGIR453W CP entered; program interrupt loop message.
As Rob sa
I will be out of the office starting 15/11/2009 and will not return until
18/11/2009.
I will respond to your message when I return.
Please consider the environment before deciding to print this email.
This email and any attachments are confidential and may be legally privileged
or protected by
On Mon, Nov 16, 2009 at 12:47 PM, J. Cassidy wrote:
> As soon as I reply with >>r 00,sysp=00,clpa<< everything dies with a
> HCPGIR453W CP entered; program interrupt loop message.
That means it gets a program check in the program check handler.
You should probably look at the PGMOLD PSW and see
Hello all,
am trying to run (believe it or not) an OS/390 2.4 guest under z/VM 5.3
(0703) on a CP (z990).
The usual CP Directory statements are in place, memory is 1G.
I am getting as far as the first reply request, see below:
===
IEA371I SYS1.PARMLIB ON DEVICE 0847 SELECTED FOR IPL PARAMETERS
36 matches
Mail list logo
