:39 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Parallel Sysplex Training
>
> Hello,
> I am looking for classroom/Virtual/Online Parallel Sysplex
> training. Please help me if you have any idea on this.
>
> --
> Thanks & Regards
> Saurabh
>
> --
@bama.ua.edu
Subject: Parallel Sysplex Training
Hello,
I am looking for classroom/Virtual/Online Parallel Sysplex
training. Please help me if you have any idea on this.
--
Thanks & Regards
Saurabh
--
For IBM-
On 06/13/2012 09:39 AM, saurabh khandelwal wrote:
Hello,
I am looking for classroom/Virtual/Online Parallel Sysplex
training. Please help me if you have any idea on this.
Check out www.mentor-services.com
Mike Myers
saurabh khandelwal wrote:
Hello,
I am looking for classroom/Virtual/Online Parallel Sysplex
training. Please help me if you have any idea on this.
There might be some Parallel Sysplex information in the Education
Assistant materials (which are free), but they are not well
Try veroef training
On Jun 13, 2012 7:10 PM, "saurabh khandelwal" <
sourabhkhandelwal...@gmail.com> wrote:
> Hello,
> I am looking for classroom/Virtual/Online Parallel Sysplex
> training. Please help me if you have any idea on this.
>
>
Hello,
I am looking for classroom/Virtual/Online Parallel Sysplex
training. Please help me if you have any idea on this.
--
Thanks & Regards
Saurabh
--
For IBM-MAIN subscribe / signoff / archive access instruct
On Fri, 18 May 2012 16:03:51 +0200, R.S. wrote:
>I forgot to customize sysplex name during ServerPac installation.
>Now I want to fix it.
>I found it's coded in couple datasets only (and LOADxx).
>
>Q1. Is there any other place where I should change the sysplex name?
>
I forgot to customize sysplex name during ServerPac installation.
Now I want to fix it.
I found it's coded in couple datasets only (and LOADxx).
Q1. Is there any other place where I should change the sysplex name?
Q2. How to do it? The only idea I know is to delete and re-create all
th
Biggest thanks goes to the sysplex parallel sysplex development team.
Reconfiguration is much more robust and easier to manage than when we
started out in the mid 90s.
We just finished upgrading both CECs in our production complex, one
push-pull at a time, about three weeks apart. I built two
Thank you all for taking interest, especially to Skip, who answered what was
really the question here. We followed this procedure for our sandbox sysplex,
we will do the same for test and production.
Best regards,
Natasa
--
For
t: Tuesday, February 14, 2012 4:10 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Changing sysplex hardware
Resync after the secondary volume is updated? If the mirroring
software supports that, it would save a lot of retransmitting. I am
fairly sure the ESS F20 and 800 PPRC did not have that, and the us
There are two sides to the sysplex coin: one lives on DASD, the other
lives in the CF. As long as DASD is fully replicated, the newly IPLed
sysplex member(s) should look exactly like the old.
CF is another matter. In the CFRM policy, each CF is identified by a
unique combination of properties
ehalf
> Of Mike Schwab
> Sent: Tuesday, February 14, 2012 2:59 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Changing sysplex hardware
>
> Since you are moving the entire datacenter and all dasd is already
> replicated, then.
> Old location:
> 1. Shut down your existing sy
ed targets. Is this not how replication
works?
Rex
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of
Mike Schwab
Sent: Tuesday, February 14, 2012 2:59 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: Changing sysplex hardware
Since you are mo
Since you are moving the entire datacenter and all dasd is already
replicated, then.
Old location:
1. Shut down your existing systems.
Old location prefered.
2. Break dasd replications.
New location.
3. IPL one system.
4. Start Sysplex using your new datasets.
5. IPL the other systems.
Backout
It is not clear if you are moving the entire SYSPLEX, or merely one or
more of the members.
It you are moving the entire SYSPLEX, perhaps a SYSPLEX wide restart is
appropriate. However, even if you are moving one or more members of the
SYSPLEX, why not use the "standard" SYSPLEX fac
Hello,
we are moving data center to another location. The data is already there on
DASD, replicated synchronously. We plan to stop the sysplex and IPL from the
replicated data , on new processor. We pretty much answered all questions so
far, except for the sysplex and CF. On new location we
I also received this:
User Group Number - MR1026112735
Document Status - Recognized
Title - Provide a utility to remove residual systems from the sysplex CDS IBM
agrees with the request and a solution appears to be a desirable objective. A
solution however may not presently appear feasible or
he product. I'll work with the
planners to see if we can get it done.
Bill Neiman
Parallel Sysplex Development, IBM
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.
"Barbara Nitz" wrote in message
news:<9205233228045717.wa.nitzibmgmx@bama.ua.edu>...
> >>MR1026112735
> >>Title - Provide a utility to remove residual systems from the
sysplex CDS
> >
> >I am told that this request, pointed out by Barbara Nitz,
>>MR1026112735
>>Title - Provide a utility to remove residual systems from the sysplex CDS
>
>I am told that this request, pointed out by Barbara Nitz, had been
>answered incorrectly and that the response has been corrected to
>"recognized".
True. Today I rec
>MR1026112735
>Title - Provide a utility to remove residual systems from the sysplex CDS
I am told that this request, pointed out by Barbara Nitz, had been
answered incorrectly and that the response has been corrected to
"recognized".
Peter Relson
z/OS Core T
>Yes, sounds contradictory: IBM recommending a sysplex wide IPL, what was
>a sysplex intended for in the first place?
I didn't read that *IBM* recommends a sysplex-wide IPL. *I* do to get rid of
the junk that IBM accumulates in the sysplex CDS. I believe IBM frowns upon
sysplex-wi
d with this:
> "User Group Number - MR1026112735
>
> Title - Provide a utility to remove residual systems from the sysplex
CDS
> IBM believes that the request described has been solved with a current
> product / service / policy / etc.
>
> Please see apar OA37776"
>
>Barbara - I've asked our account team to add us as concurring with the
>requirement and to be added to the Interested Parties list.
The requirement has been rejected with this:
"User Group Number - MR1026112735
Title - Provide a utility to remove residual systems from the
in the same sysplex. In particular, I
would like to get the USERID and the JOBID. I have the jobname, system name, and ASID. I get this
information out of an ISGQUERY scan of ENQs. What I'm going for is a "monitor" command
which can scan ENQ information and output messages. The &q
IAZXJSAB has some nice output for executing address spaces. But it only returns
data from address spaces in the system it is running on. I was wondering if
there is any way to get some equivalent information from address spaces running
on other systems in the same sysplex. In particular, I
In <0486882064432540.wa.paulgboulderaim@bama.ua.edu>, on
12/21/2011
at 12:02 PM, Paul Gilmartin said:
>Hmmm... IIRC, there are certain authorized utilities that will run
>only in a single-step job. They check.
No. The check is before the ATTACH of the started program. I believe
that the
In
,
on 12/21/2011
at 05:39 PM, "Vernooij, CP - SPLXM" said:
>Yes, there is a light at the horizon: you cannot FREE a dataset
>allocated in JCL.
Wherever did you get that idea? Not only can you, but lots of
installations have logon clists that do just that.
--
Shmuel (Seymour J.) Metz
Paul
> ... IIRC ...
I'm a touch surprised you are not confidently familiar with this topic! Unless
it is I who am not quite as familiar as I might be, the point being that, when
"multi-step" is tried with a TSO user procedure, the reaction is *not* the more
familiar one, namely message "IEF188
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of David Andrews
> Sent: Wednesday, December 21, 2011 10:28 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: TSO "concern" - sysplex multisystem logon.
>
>
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Binyamin Dissen
> Sent: Wednesday, December 21, 2011 11:59 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: TSO "concern" - sysplex multisystem logon.
>
ama.ua.edu
>Sent: Wednesday, December 21, 2011 10:41 AM
>Subject: Re: TSO "concern" - sysplex multisystem logon.
>
>
>>
>> Curious as to why you wish to prevent it. If they can
>> arbitrarily choose to
>> logon to any system, why prevent concurrent l
On Wed, 21 Dec 2011 11:56:26 -0600, McKown, John wrote:
>
>Gee, I never saw a TSO logon proc with more than one step. Never would have
>occurred to me.
>
Hmmm... IIRC, there are certain authorized utilities that will
run only in a single-step job. They check. I don't know why
it matters. I do
"Paul Gilmartin" wrote in message
news:<8844286434605726.wa.paulgboulderaim@bama.ua.edu>...
> On Wed, 21 Dec 2011 19:22:31 +0200, Binyamin Dissen wrote:
>
> >On Wed, 21 Dec 2011 17:39:14 +0100 "Vernooij, CP - SPLXM" wrote:
> >
> >:>Yes, there is a light at the horizon: you cannot FREE a datas
On Wed, 21 Dec 2011 11:41:08 -0600 "McKown, John"
wrote:
:>> Curious as to why you wish to prevent it. If they can
:>> arbitrarily choose to
:>> logon to any system, why prevent concurrent logons?
:>Because my boss said so. He didn't say why. I don't argue any more. We are
"CPU poor" and our p
"McKown, John" wrote in message
news:.
..
>
> >
> > Curious as to why you wish to prevent it. If they can
> > arbitrarily choose to
> > logon to any system, why prevent concurrent logons?
> >
> > --
> > Binyamin Dissen
> > http://www.dissensoftware.com
> >
> > Director, Dissen Software, Bar
On Wed, 21 Dec 2011 11:42:15 -0600 Paul Gilmartin
wrote:
:>On Wed, 21 Dec 2011 19:22:31 +0200, Binyamin Dissen wrote:
:>>On Wed, 21 Dec 2011 17:39:14 +0100 "Vernooij, CP - SPLXM" wrote:
:>>:>Yes, there is a light at the horizon: you cannot FREE a dataset
:>>:>allocated in JCL. So this trick migh
sday, December 21, 2011 11:56 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: TSO "concern" - sysplex multisystem logon.
>
> > -Original Message-
> > From: IBM Mainframe Discussion List
> > [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin
> >
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Paul Gilmartin
> Sent: Wednesday, December 21, 2011 11:42 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: TSO "concern" - sysplex multisystem logon.
>
>
On Wed, 21 Dec 2011 19:22:31 +0200, Binyamin Dissen wrote:
>On Wed, 21 Dec 2011 17:39:14 +0100 "Vernooij, CP - SPLXM" wrote:
>
>:>Yes, there is a light at the horizon: you cannot FREE a dataset
>:>allocated in JCL. So this trick might well be the solution.
>
>You certainly can.
>
What if he were
>
> Curious as to why you wish to prevent it. If they can
> arbitrarily choose to
> logon to any system, why prevent concurrent logons?
>
> --
> Binyamin Dissen
> http://www.dissensoftware.com
>
> Director, Dissen Software, Bar & Grill - Israel
Because my boss said so. He didn't say why. I d
On Wed, 21 Dec 2011 17:39:14 +0100, Vernooij, CP - SPLXM wrote:
>>
>> Any other ideas?
>> --
>> John McKown
>
>Yes, there is a light at the horizon: you cannot FREE a dataset
>allocated in JCL. So this trick might well be the solution.
>
I thought I had done this routinely; now I must try it to pr
On Wed, 21 Dec 2011 17:39:14 +0100 "Vernooij, CP - SPLXM"
wrote:
:>Yes, there is a light at the horizon: you cannot FREE a dataset
:>allocated in JCL. So this trick might well be the solution.
You certainly can.
--
Binyamin Dissen
http://www.dissensoftware.com
Director, Dissen Software, Bar &
On Wed, 21 Dec 2011 10:06:21 -0600 "McKown, John"
wrote:
:>We are upgrading, finally, to z/OS 1.12 next month. One thing that I would
like to do is allow certain people the ability to logon to TSO on all systems
concurrently. It appears this is possible, for all users, simply by not
propagatin
McKown, John wrote:
>He likes the idea of us (Tech Services) and Production Control being able to
>do this. But he does not want any other TSO users to be able to do it.
You can do that. We do this trick for many years.
First look at Mark Zelden's hints about this.
We use GRS only for our tec
"McKown, John" wrote in message
news:.
..
> We are upgrading, finally, to z/OS 1.12 next month. One thing that I
would like to do is allow certain people the ability to logon to TSO on
all systems concurrently. It appears this is possible, for all users,
simply by not propagating the SYSIKJUA enqu
On Wed, 2011-12-21 at 11:06 -0500, McKown, John wrote:
> allow certain people the ability to logon to TSO on all systems
> concurrently. It appears this is possible, for all users, simply by
> not propagating the SYSIKJUA enqueue via the GRSRNL.
The SYSIKJUA RNAME appears to be the TSO userid:
le data set.By not using the
profile sharing and only allocating the system specific profile data sets for
those you want to allow, you will have as much control as you want.
I guess you could use automation - and assuming this is a sysplex use a
combination of "RO *ALL,D A,tsouser&quo
We are upgrading, finally, to z/OS 1.12 next month. One thing that I would like
to do is allow certain people the ability to logon to TSO on all systems
concurrently. It appears this is possible, for all users, simply by not
propagating the SYSIKJUA enqueue via the GRSRNL. In fact, I have tested
> From: Lizette Koehler
> Subject: Re: zFS parm sysplex=filesys
> Does this mean with z/OS V1.13 I will have to change to SYSPLEX(YES) in
> order to have zFS files mounted? Or will zFS still mount even with
> SYSPLEX(NO)
Lizette,
With SYSPLEX(NO) zFS address space wil
Hello Lizette and All,
Just to re-iterate what others had said (which has been correct)...
This sysplex=filesystem migration action is applicable if you use zFS *AND* if
you are in a shared file system environment. If you don't meet both of these
criteria, then you do not need to do
> > [ snip ]
> >
> > Sorry, I am still a little confused on this issue. So if I could get
> a little more clarification
> >
> > I am running with SYSPLEX(NO) in my BPXPRMxx member.
> >
> > Does this mean with z/OS V1.13 I will have to change
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Lizette Koehler
>
> [ snip ]
>
> Sorry, I am still a little confused on this issue. So if I could get
a little more clarification
>
> I am running with SYSPLEX(NO) in my BPXPRMxx member.
&g
ou, even if the message wording could
be improved.
Sorry, I am still a little confused on this issue. So if I could get a
little more clarification
I am running with SYSPLEX(NO) in my BPXPRMxx member.
Does this mean with z/OS V1.13 I will have to change to SYSPLEX(YES) in
order to have zFS file
Walter and John,
Thanks for the good suggestions for improved messages on a successful migration
health check run. I will pass them along.
The indication that the check did pass (I hope) would be enough to let you know
that the migration action didn't affect you, even if the message wording co
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Walter Marguccio
> > From: Marna WALLE
>
> > Subject: Re: zFS parm sysplex=filesys
>
> > look at the output from check ZOSMIGV1R13_ZFS_FILESYS (available on
> > R11 and R12), . .
> From: Marna WALLE
> Subject: Re: zFS parm sysplex=filesys
> look at the output from check ZOSMIGV1R13_ZFS_FILESYS (available on R11 and
> R12),
> then this check will tell you whether
> 1) this migration action is applicable to you and
> 2) if it is applicable t
ealth Checker for z/OS, and activate and look at the output from check
ZOSMIGV1R13_ZFS_FILESYS (available on R11 and R12), then this check will tell
you whether 1) this migration action is applicable to you and 2) if it is
applicable to you, whether you've correctly set sysplex=filesys on all t
On 12/13/11 04:55, Walter Marguccio wrote:
Q2: What observable effect(s), if any, would occur if we specify
sysplex=filesys in our 1.11 images without sharing file systems?
Honestly, I didn't tried. I would think that sysplex=no takes precedence over
sysplex=filesys, but again,
> From: "Chase, John"
> Subject: zFS parm sysplex=filesys
> Q1: Has anyone here IPLed a z/OS 1.13 system into a "supported
> back-level" sysplex WITHOUT shared file systems AND without having
> specified sysplex=filesys in the "back-level" members?
Currently studying the migration guide for z/OS 1.13 (we're running 1.11
now), and note that 1.13 delivers zFS with a default of sysplex=filesys.
...snippage
Q1: Has anyone here IPLed a z/OS 1.13 system into a "supported
back-level" sysplex WITHOUT shared file systems AND
I would expect that if you initiailize OMVS with SYSPLEX(NO) in BPXPRMxx
whatever you specify in IOEPRMxx for sysplex= would be ignored.
Mark Jacobs
On 12/12/11 11:18, Chase, John wrote:
Hi, All,
Currently studying the migration guide for z/OS 1.13 (we're running 1.11
now), and
Hi, All,
Currently studying the migration guide for z/OS 1.13 (we're running 1.11
now), and note that 1.13 delivers zFS with a default of sysplex=filesys.
Earlier releases default sysplex=off. We do NOT run any shared file
systems, and do not anticipate doing so in the foreseeable f
54 AM
To: IBM-MAIN@bama.ua.edu
Subject: Fixing a sysplex definition problem for the first system in a sysplex
- was: Re: CFRM Policy Number
>The danger is that if *anything* goes wrong before your first system comes
>up, you cannot log on to fix even the most trivial problem.
One way to be
>The danger is that if *anything* goes wrong before your first system comes
>up, you cannot log on to fix even the most trivial problem.
One way to be able to fix a sysplex problem that occurs for the first system is
the following and requires planning in advance:
1. Use the defa
From: Al Sherkow
To: IBM-MAIN@bama.ua.edu
Sent: Friday, November 18, 2011 11:33 AM
Subject: Frequency of Sysplex Verification Audits?
I'm curious about the actual frequency that sites are being asked to run IBM's
Sysplex Verification Package. (The I
: IBM-MAIN@bama.ua.edu
Date: 11/18/2011 08:41 AM
Subject:Frequency of Sysplex Verification Audits?
Sent by:IBM Mainframe Discussion List
I'm curious about the actual frequency that sites are being asked to run
IBM's Sysplex Verification Package. (The IBM Sysplex Ve
I'm curious about the actual frequency that sites are being asked to run IBM's
Sysplex Verification Package. (The IBM Sysplex Verification Package can be
found at http://ibm.com/systems/z/swprice/sysplex/verify.html .)
The Ts&Cs of the Attachment for IBM System z AWLC (th
-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@bama.ua.edu] On
> Behalf Of Barbara Nitz
> Sent: Wednesday, October 26, 2011 9:08 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: maxsystem in a sysplex - belated heads-up
>
> To finish this thread: There is now marketi
To finish this thread: There is now marketing requirement MR1026112735 that
describes the need for a cleanup utility and asks for a way to really
re-initialize the sysplex on the ixc405 message.
Barbara
--
For IBM-MAIN
uch less point the way in the right
direction.
>From a customer perspective, all I care about in such a situation is getting
>my sysplex back up, and that is almost impossible with the contradicting
>information I get. I don't really care what component is 'at fault'. I a
function. For many exploiters, that is tantamount to requiring that the
function CDS be accessible from every system in the sysplex. But it is not
a requirement that XCF imposes.
The XCF signalling service does NOT lie about establishing signalling
connectivity with other systems. If we
To clarify some technical issues that have been discussed in this thread:
On the second and subsequent systems to join the sysplex, XCF signaling
has a "chicken-and-egg" problem when it attempts to determine what signaling
connectivity exists with other systems. It may be tha
>How about expiring the data from slot not used for 30 days? An IPL
>after that would retrieve the needed info in a few seconds when it
>joins the sysplex?
I like that idea. But as I said in my (private) note to Bill, since the design
change from z/OS 1.9 isn't externally docu
How about expiring the data from slot not used for 30 days? An IPL
after that would retrieve the needed info in a few seconds when it
joins the sysplex?
On Thu, Oct 20, 2011 at 8:21 AM, Bill Neiman wrote:
> Barbara,
>
> If you were to open a requirement requesting a utilit
Barbara,
If you were to open a requirement requesting a utility of some kind
to report and delete residual system information from the sysplex couple data
set, we might be able to do something about this. I don't think it would be
hard to implement something similar to IXCMIAP
ay to find out *what* junk might have accumulated in the sysplex CDS over
the years. On the other hand, a D XCF,CPL would faithfully show an ARM CDS that
hasn't been around for years, and that isn't used. (Unless that has been
silently fixed since we experienced it.
Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: Barbara Nitz
To: IBM-MAIN@bama.ua.edu
Date: 10/18/2011 02:12 AM
Subject:Re: maxsystem in a sysplex - belated heads-up
Sent by:IBM Mainframe Discussion List
>The only thing I can
>The only thing I can do for you is check D XCF,S,ALL when one of the
>systems has been brought down, but I suppose you have a testplex
>yourself?
Yes, we do. I don't remember ever to have issued this command with the ALL parm
when one of the systems was down, but it will be easy to do that once
the current systens and ancient rubbish.
>
> maybe you can test for me if one can find out via simple display
commands what rubbish is kept in the sysplex CDS (I obviously cannot,
since I've cleaned up all sysplex CDSs with residual information):
>
> D XCF,S,ALL supposedly lists all
pt in the sysplex CDS (I obviously cannot, since I've cleaned up
all sysplex CDSs with residual information):
D XCF,S,ALL supposedly lists all systems in the sysplex. It would be
interesting to see if those are really all of them or only those that are
active. The book isn't r
n
Behalf Of Barbara Nitz
> Sent: Tuesday, October 11, 2011 11:53 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: maxsystem in a sysplex - belated heads-up
>
> When we migrated from a z9 to a z196 - big-bang swap - we had a lot of
trouble getting one sysplex up. The first system came up f
>-In an N lpar sysplex with each lpar running late level z/OS (lets
>say z/os 1.11 or higher) if a single lpar crashes (i.e. - an unscheduled
>termination of z/OS without performing normal shutdown procedures)will
>this affect the other systems?
Yes, at least to some extent.
&g
don't,
then things may get hairy with the offending system still holding locks, etc.
The whole area is called SFM (Sysplex Failure Management) and IBM has spent
considerable effort on it recently. There were several good Share presentations
that touched on the topic, including two from M
Congratulations you win!
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Arun Shanmugasundaram
Sender: IBM Mainframe Discussion List
Date: Thu, 13 Oct 2011 06:43:27
To:
Reply-to: IBM Mainframe Discussion List
Subject: Re: n lpars in a sysplex and one of the lpar
---Please excuse my brevity. I'm trying to win The Email Game!-Original
Message-
n lpars in a sysplex and one of the lpar systems crashes
From: Ray Overby <rayove...@comcast.net>To: ibm-m...@bama.ua.eduDate:
Thursday, October 13, 2011 at 7:11PM
- In an N lpar sysple
s
---Please excuse my brevity. I'm trying to win The Email Game!-Original
Message-
n lpars in a sysplex and one of the lpar systems crashes
From: Ray Overby <rayove...@comcast.net>To: ibm-m...@bama.ua.eduDate:
Thursday, October 13, 2011 at 7:11PM
- In an N lpar s
hi how are you
---Please excuse my brevity. I'm trying to win The Email Game!-Original
Message-
n lpars in a sysplex and one of the lpar systems crashes
From: Ray Overby <rayove...@comcast.net>To: ibm-m...@bama.ua.eduDate:
Thursday, October 13, 2011 at 7:11PM
- In an N l
On 10/13/11 09:41, Ray Overby wrote:
-In an N lpar sysplex with each lpar running late level z/OS (lets
say z/os 1.11 or higher) if a single lpar crashes (i.e. - an
unscheduled termination of z/OS without performing normal shutdown
procedures)will this affect the other systems?
-Can
-In an N lpar sysplex with each lpar running late level z/OS (lets
say z/os 1.11 or higher) if a single lpar crashes (i.e. - an unscheduled
termination of z/OS without performing normal shutdown procedures)will
this affect the other systems?
-Can this situation be simulated by having
AIN@bama.ua.edu
Subject: maxsystem in a sysplex - belated heads-up
When we migrated from a z9 to a z196 - big-bang swap - we had a lot of trouble
getting one sysplex up. The first system came up fine, but the second or third
system could not be ipl'd into that plex. It ended up on a GRS (!)
When we migrated from a z9 to a z196 - big-bang swap - we had a lot of trouble
getting one sysplex up. The first system came up fine, but the second or third
system could not be ipl'd into that plex. It ended up on a GRS (!) wait0A3
rsn9C. The accompanying ISG message would only have
>
> The "Merging Systems" is fairly comprehensive in covering the various
> subsystem *plex considerations, and should point to specific books where
> warranted (e.g. Unix System Services Planning, RACF System Programmers
> Guide, etc.). Another fine RedBook (System Progr
.). Another
fine RedBook (System Programmers Guide to Parallel Sysplex Aggregation) is
available here:
http://www.redbooks.ibm.com/abstracts/redp3967.html
Toward the end of this book, as should be so for "Merging Systems", there is a
list of related publications resources
Hello,
I am new to Parallel sysplex. I am trying to understand the
Parallel sysplex configured in our shop.
For this, I refereed below redbooks.
1) merging system into sysplex.pdf
2) MVS Setting Up a Sysplex.pdf
Do we have any other book or document available, which can
The "Setting Up a Sysplex" is *the* starting point, and should point you to
several other helpful resources, including:
http://www-03.ibm.com/systems/z/advantages/pso/index.html
You'll need to know about STP if you are on current (z9 and up) hardware, which
you can find o
The book Setting up a sysplex is part of the base z/OS documentation.
It is pretty good.
For z/OS 1.11 it is here
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/iea2f1a0/CCONTENTS?SHELF=EZ2ZBK0I&DN=SA22-7625-18&DT=20090604231538
Gadi
-Original Message-
From: IBM M
Hello,
I am interested in learning SYSPLEX environment. Can you please
guide me, which book can help me to setup SYSPLEX.
Any cookbook is available.
--
Thanks & Regards
Saurabh Khandelwal
--
For IBM-
nds can be issued from the VM console of
the guest.
:>On Tue, 2011-06-21 at 11:08 +0300, ??? ?? ??? wrote:
:>> Hi,
:>> Is it possible to create a BASIC sysplex between two VM guests?
:>> Both guests are running under the same physical machine.
--
Binyamin Dissen
http://www.
1 - 100 of 1010 matches
Mail list logo
