Re: Setting up a new parallel sysplex

a single sysplex or lose the PSLC discount. So we bolted the sysplexes together without attempting to resolve the myriad conflicts resulting from decades-long isolation: a jillion duplicate names and altogether different access rules and management policies. If that resembles your history, you

Re: Setting up a new parallel sysplex

AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Setting up a new parallel sysplex MVS "Setting up a SYSPELX" Redbook "merging systems into a sysplex. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Fred Glenlake Sent: Mon

Re: Setting up a new parallel sysplex

I believe there is a manual that comes with z/OS called Setting up a Sysplex? This is probably a good place to start - and I am sure there are numerous Share presentations on this as well. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU

Re: Setting up a new parallel sysplex

MVS "Setting up a SYSPELX" Redbook "merging systems into a sysplex. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Fred Glenlake Sent: Monday, February 5, 2018 11:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Setting up

Setting up a new parallel sysplex

I am looking for documentation on how to set up a full parallel sysplex from a "sham-plex". We are running all the usual cast of characters, IMS, DB2, CICS, MQ, etc. We have a basic sysplex in place to be able to qualify for IBM sysplex pricing. The management team has decided

Re: SYSPLEX distance

Hi Skip, One possible option for the survivability of a 24x7 z/OS environment would be to place the Primary DASD Control Unit(s) at a different site ( a 3rd site ) from the Mainframe CEC's. Then, if one or the other Mainframe CEC "glass house" is unusable, the other ( in theory ) continues to

Re: SYSPLEX distance

My recollection is that the term 'GDPS' was coined at a time when IBM had the *ambition* to run a single sysplex with members at a considerable distance apart. That ambition was too optimistic for the technology of the day, so 'GDPS' was redefined. A remnant of that shift is the difficulty

AW: Re: SYSPLEX distance

> I'm still not clear on how a 'geographically dispersed sysplex' (original > definition, not 'GDPS') would work. You say "original definition". I seem to remember, but might be wrong, that the term GDPS was coined when sysplexes were al contained within a single building or i

Re: SYSPLEX distance

Abstract: Asynchronous CF Lock Duplexing is a new enhancement to IBM’s parallel sysplex technology that was made generally available in October 2016. It is an alternative to the synchronous system managed duplexing of coupling facility (CF) lock structures that has been available for many years

Re: SYSPLEX distance

am Subject: Re: SYSPLEX distance If this helps: We run a parallel sysplex with sites at 16 - 18 km (2 separate routes with some difference in distance) with active systems and CFs at both sites, without problems. Most Sync CF Requests to the Remote CFs are converted to Async. To minimize

Re: SYSPLEX distance

technology was ESCON, and network technology was ISV CNT. Parallel sysplex synchronization was governed by external timers (9037). When we started with parallel sysplex, loss of timer connection would kill the member that experienced it first. Then IBM introduced a change whereby the entire sysplex

Re: SYSPLEX distance

> -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Rob Schramm > Sent: Thursday, January 11, 2018 9:01 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SYSPLEX distance > > SFM and planning for what your

Re: SYSPLEX distance

SFM and planning for what your surviving system should always be done. And yes early on there was a failure of one of the two dark fiber connections and the sysplex timers were not connected properly to allow for a continued service. Planning planning planning. On Thu, Jan 11, 2018 at 10:22 AM

Re: SYSPLEX distance

One company had data centers in Miami and New Orleans. Miami shut down for a hurricane, and wasn't back up before Katrina hit New Orleans. On Thu, Jan 11, 2018 at 6:44 AM, Timothy Sipples <sipp...@sg.ibm.com> wrote: > J.O.Skip Robinson wrote: >>Losing XCF connection to a syspl

Re: SYSPLEX distance

J.O.Skip Robinson wrote: >Losing XCF connection to a sysplex member would be a whole >nother level of impact that I've never been willing to sign >up for even though our network today is far more reliable >than it was 20 years ago. Isn't losing XCF connectivity something worth planni

Re: SYSPLEX distance

If this helps: We run a parallel sysplex with sites at 16 - 18 km (2 separate routes with some difference in distance) with active systems and CFs at both sites, without problems. Most Sync CF Requests to the Remote CFs are converted to Async. To minimize the Async/Remote CF delays, we

Re: SYSPLEX distance

My reservation about running a sysplex over a network (as opposed to direct link cables) is not merely latency. We went with XRC for DR because it's asynchronous and therefore fairly tolerant of network delays. For me the real problem is that an entire extended sysplex may be at risk in case

Re: SYSPLEX distance

I was part of a group that ran a parallel sysplex that was 13 miles apart. The time it takes the light to travel adds up. This was back in 2007. It worked. It ran that way for at least a few years. It was not a GDPS setup. I think it was EMC disk at the time. Rob Schramm On Sun, Jan 7

Re: SYSPLEX distance

Our DR site is >100KM from our production site. In the early days of serious mirroring for DR (mid/late 90s), running a single sysplex across that distance was out of the question. It wasn't just a timing issue--although that was enough reason not to try--but network technology of the

Re: SYSPLEX distance

:42 am Subject: Re: SYSPLEX distance Please make sure you take one recent (late 2016) innovation into consideration: Asynchronous CF Lock Duplexing. My understanding is that this recently introduced Coupling Facility feature offers performance improvements in many scenarios, including some distance

Re: SYSPLEX distance

> On Jan 3, 2018, at 7:55 PM, Mike Schwab wrote: > > Searched for ibm zos cryptography. First 10 results seemed useful. A > share expo, some intros, some PDF manuals. > https://www.google.com/search?q=ibm+zos+cryptography > (off list) I glanced through the google list

Re: SYSPLEX distance

lex" to satisfy Parallel Sysplex aggregation rules? (Those rules are becoming less relevant now, at least, but that's a separate point.) As another example, if the focus is on protecting and preserving data, then it might make sense to stretch the storage

Re: SYSPLEX distance

but was not privy to them). > > I am *still* unclear as to how cryptography works in any sysplex whether it > be local or remote. Is there a red piece on this somewhere? > > Ed > > -- > For IBM-MAIN subscribe

Re: SYSPLEX distance

hem). I am *still* unclear as to how cryptography works in any sysplex whether it be local or remote. Is there a red piece on this somewhere? Ed -- For IBM-MAIN subscribe / signoff / archive access instructions, send email

Re: SYSPLEX distance

It says global, but limited intercontinental links limit you to one continent. On Wed, Jan 3, 2018 at 3:31 PM, Edward Gould wrote: >> On Jan 3, 2018, at 2:51 AM, Mike Schwab wrote: >> >> https://www.ibm.com/it-infrastructure/z/technologies/gdps

Re: SYSPLEX distance

> On Jan 3, 2018, at 2:51 AM, Mike Schwab wrote: > > https://www.ibm.com/it-infrastructure/z/technologies/gdps > > >

Re: SYSPLEX distance

Also keep in mind if you are reading old Redbooks if they reference Sysplex timers. The change from Sysplex Timer to STP changed timer signalling from discrete ETR links to using CF links for timing signals. This may have influence on distances and latency planning. Dana On Wed, 3 Jan 2018

Re: SYSPLEX distance

are you trying to achieve by going over distance? Most customers I worked with equate multi-site parallel sysplex with even workload distribution to non stop operation. This may be or may not be true, and depending on your actual needs a slightly different configuration might do with less

Re: SYSPLEX distance

Some additional sources of info: System z Parallel Sysplex Best Practices: http://www.redbooks.ibm.com/redpieces/abstracts/sg247817.html Parallel Sysplex on IBM Z: https://www.ibm.com/it-infrastructure/z/technologies/parallel-sysplex

Re: SYSPLEX distance

anagement as to how far apart we can move > our production systems. I know there are limitations on how far the (in > this case) two systems (and two coupling facilities) can be apart and I've > dug up an old IBM Redbook on the issue where they did tests with a sysplex > at 0, 20, 40

SYSPLEX distance

with a sysplex at 0, 20, 40, 60 and 80 kms apart. Physical limitations (eg. FICON) don't seem to be an issue. We are a CICS and DB2 shop so the manual certainly addressed issues that we might see but it is dated 2008 so has anything changed since then? CICS and DB2 have moved on a long way in that time. I

AW: Re: When was the *basic* sysplex introduced? MVS/ESA 4.1?

>I believe it was 4.1. Here's an interesting article: >>>http://2000clicks.com/links/Computers/IBMMainframeHistory/mvshist5.htm Indeed. Thanks for the link. -- Peter Hunkeler - -- For IBM-MAIN subscribe / signoff / archive

Re: When was the *basic* sysplex introduced? MVS/ESA 4.1?

W dniu 2017-10-04 o 15:25, Peter Hunkeler pisze: I do remember that MVS/ESA V5 (V5.1) introduced the *parallel* sysplex. But I don't remember exactly what MVS/ESA release introduced the *basic* sysplex. ISTR, it was MVS/ESA V4 (V4.1). Correct? Yes, it was a version 4. -- Radoslaw Skorupka

Re: When was the *basic* sysplex introduced? MVS/ESA 4.1?

To: IBM-MAIN@LISTSERV.UA.EDU Subject: When was the *basic* sysplex introduced? MVS/ESA 4.1? I do remember that MVS/ESA V5 (V5.1) introduced the *parallel* sysplex. But I don't remember exactly what MVS/ESA release introduced the *basic* sysplex. ISTR, it was MVS/ESA V4 (V4.1). Correct? -- Peter

When was the *basic* sysplex introduced? MVS/ESA 4.1?

I do remember that MVS/ESA V5 (V5.1) introduced the *parallel* sysplex. But I don't remember exactly what MVS/ESA release introduced the *basic* sysplex. ISTR, it was MVS/ESA V4 (V4.1). Correct? -- Peter Hunkeler -- For IBM

Re: DELETING DSN IN A SYSPLEX

LISTSERV.UA.EDU > Subject: DELETING DSN IN A SYSPLEX > > Gentle Readers, > I am trying to delete a dsn which is in a SYSPLEX. When I attempt to do so > (via ISPF 3.4) I receive the message that the dsn is in use.I hit PF1 to get > further information and then type HELP (as per prompt)

Re: DELETING DSN IN A SYSPLEX

esmie moo wrote: >I was able to delete the dsn by renaming it first and then deleting it because >I had the STGADMIN.**. authorization.  The dsn was SYS1.CICS2.MODINTR Thanks, I'm glad you could resolve your trouble, but your dataset is a SYS1 and is looking if it is used by a CICS system...

Re: DELETING DSN IN A SYSPLEX

UA.EDU Sent: Monday, July 10, 2017 8:36 AM Subject: Re: DELETING DSN IN A SYSPLEX Vernooij, Kees wrote: "Dsn in use" is not an security issue, it is a GRS issue. It is indeed so. Thanks. >Datasets are serialized by their dsname only. If you have different datasets &g

Re: DELETING DSN IN A SYSPLEX

Vernooij, Kees wrote: "Dsn in use" is not an security issue, it is a GRS issue. It is indeed so. Thanks. >Datasets are serialized by their dsname only. If you have different datasets >on different volumes with the same dsname, they will be serialized. Ah, yes, thanks for chiming in. I

Re: DELETING DSN IN A SYSPLEX

esmie moo wrote: >I am still unable to delete it.  I think I will need specific security >clearance. Careful, perhaps you should post the name of that dataset(s) and what users/jobs are grabbing it in a secure hold. Perhaps, with FACILITY Class profile STGADMIN.DPDSRN.** you can try to RENAME

Re: DELETING DSN IN A SYSPLEX

-Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of esmie moo > Sent: 10 July, 2017 14:18 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: DELETING DSN IN A SYSPLEX > > Elardus, > Thanks for the info on checking on

Re: DELETING DSN IN A SYSPLEX

ct: Re: DELETING DSN IN A SYSPLEX esmie moo wrote: >I am trying to delete a dsn which is in a SYSPLEX.  When I attempt to do so >(via ISPF 3.4) I receive the message that the dsn is in use.I hit PF1 to get >further information and then type HELP (as per prompt) and it shows that

Re: DELETING DSN IN A SYSPLEX

esmie moo wrote: >I am trying to delete a dsn which is in a SYSPLEX.  When I attempt to do so >(via ISPF 3.4) I receive the message that the dsn is in use.I hit PF1 to get >further information and then type HELP (as per prompt) and it shows that it is >in use by the folli

DELETING DSN IN A SYSPLEX

Gentle Readers, I am trying to delete a dsn which is in a SYSPLEX.  When I attempt to do so (via ISPF 3.4) I receive the message that the dsn is in use.I hit PF1 to get further information and then type HELP (as per prompt) and it shows that it is in use by the folliwng 2 user(s) and/or jobs(s

Re: Catalogs in a SYSPLEX

Ken, All SYSRES datasets, except for SYS1, are in the catalog on the SYSRES. Aliases are symbolics pointing to CATALOG.SOFTWARE. SYS1 datasets are in MCAT with a volser of **. MCAT is on a sysplex level volume and shared across the LPARs in the plex. Maintenance and upgrades are installed

Re: Catalogs in a SYSPLEX

8:59 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > " Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPARs in a single sysplex. The master catalogs > were not shared , I think I would put forth one b

Re: Catalogs in a SYSPLEX

-0595 Mobile > 626-302-7535 Office > robin...@sce.com > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of John Eells > Sent: Tuesday, November 29, 2016 9:33 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (Ext

Re: Catalogs in a SYSPLEX

in a SYSPLEX Jesse 1 Robinson wrote: > I have to admit that locating MCAT on sysres avoids one step that we need to > take. We run seven 'sysplexes' (some monoplex) that do not share any > resources including MCAT. When we install a new release, there are often new > sysres data se

Re: Catalogs in a SYSPLEX

Jesse 1 Robinson wrote: >The rule for IT is much like the rule for life: as soon as you delete/discard >something, you will need it the next day. ;-) Next day? Aw, come on! In IT it is wayayayayayaya too long in the future. I rather expect that need within 15 minutes ... ;-) ... or while

Re: Catalogs in a SYSPLEX

Jesse 1 Robinson wrote: I have to admit that locating MCAT on sysres avoids one step that we need to take. We run seven 'sysplexes' (some monoplex) that do not share any resources including MCAT. When we install a new release, there are often new sysres data sets that need to be cataloged on

Re: Catalogs in a SYSPLEX

: Catalogs in a SYSPLEX Agreed, way too much risk. We don’t swap master cat's at all either. No reason to, except maybe those shops that cannot fit the entire SYSRES on one volume, so you have the issue where DSN A is cataloged on the first volume of the set pre-upgrade, and post-upgrade

Re: Catalogs in a SYSPLEX

616.653.8429 f 616.653.2717 -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Monday, November 28, 2016 4:57 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX As noted earlier in this thread, sysres

Re: Catalogs in a SYSPLEX

Jesse 1 Robinson wrote: As noted earlier in this thread, sysres datasets should be cataloged with volser ** and unit . That tells the system to look on the currently IPLed sysres regardless of volume name. BTW I don't subscribe to the floating MCAT strategy. Our master catalog lives

Re: Catalogs in a SYSPLEX

in a SYSPLEX I like this approach! But I thought certain data sets used in NIP and early phases of IPL had to be in the master cat, e.g., SYS1.LPALIB which presumably is in your SYSRES cat? How does it work? Ken On Tue, Nov 22, 2016 at 11:28 AM, van der Grijn, Bart (B) < bvandergr...@dow.

Re: Catalogs in a SYSPLEX

to:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Allan Staller > Sent: Tuesday, November 22, 2016 8:59 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Catalogs in a SYSPLEX > > " Prior to this job I worked at a shop where we supported sysplexes from a > single system to up to 10 LPAR

Re: Couplexx values for sysplex - Query

I understand your point. Still suggest you look first at the system weight values in SFM. They establish a prioritized 'queue' of systems that will get partitioned out in case the sysplex hangs. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS

Re: Couplexx values for sysplex - Query

these systems isolated immediately when there is a problem using SSD or SFM . For now , we have specified lower weights for these systems . We are also looking at a plan to take these LPARS to another sysplex so the production systems are not impacted . Since we did not want to touch anything on existing

Re: Couplexx values for sysplex - Query

I had to dig into the doc to investigate some of the parameters you're asking about. Some thoughts: -- You do NOT want to use multiple COUPLExx members across the sysplex. Some of the parameters must be consistent across the plex. If you introduce multiple COUPLExx members, it's only a matter

Couplexx values for sysplex - Query

Hello Listers, We are doing a change to set values for INTERVAL ,CLEANUP and OPNOTIFY in COUPLExx different for few systems in our sysplex . I understand that INTERVAL can be set different for each system in the plex after you enable USER INTERVAL on the Functions statement . I would

Re: Catalogs in a SYSPLEX

, November 22, 2016 8:59 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Catalogs in a SYSPLEX " Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big r

Re: Catalogs in a SYSPLEX

" Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big reason for not sharing the master catalog, would be system upgrades, when we went th

Re: Catalogs in a SYSPLEX

On Mon, 21 Nov 2016 21:44:19 +, Nims,Alva John (Al) wrote: >I would put forth one big reason for not sharing the master catalog, >would be system upgrades, when we went through the z/OS upgrades, >there were times where SYS1. Level data sets location changed from >one release to the next

Re: EXTERNAL: Re: Catalogs in a SYSPLEX

All of my Sysplexes each have a shared single MCAT per plex. Setting up a Sysplex is probably where the recommendation to a single MCAT is located. In an emergency the LOADxx can be edited to point to any other MCAT and they will all serve to get a system up and running. Additionally in each

Re: Catalogs in a SYSPLEX

So what is the intent of your configuration? To take advantage of all the wonderfulness that is SYSPLEX :) Separate but equal? Or are they running from a common SYSRES Set? Other??? We will have 2 systems that are identical. They are going to have a common SYSRES with a secondary SYSRES

Re: Catalogs in a SYSPLEX

You can do either and will some associated issues. Here are some: If you have a MCAT for each LPAR you will have so many MCAT's + its backup to maintain and garbage in it piles up with time. If you have a shared MCAT, you need to maintain one MCAT/SYSPLEX and one backup.At the time of z/OS

Re: Catalogs in a SYSPLEX

By using INDIRECT CATALOG you can use different SYSRES Sets, but the same SYS1.** names. Lizette -Original Message- >From: Lizette Koehler <stars...@mindspring.com> >Sent: Nov 21, 2016 3:10 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Re: Catalogs in a SYSPLEX

Re: Catalogs in a SYSPLEX

21, 2016 1:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Catalogs in a SYSPLEX I was doing some research and I cannot seem to find any specific mention of using a single shared master catalog in the manuals. It doesn't mean I was looking in the correct manuals it just means that what

Re: Catalogs in a SYSPLEX

Separate but equal? Or are they running from a common SYSRES Set? Other??? Lizette -Original Message- >From: Travis <tbr...@aessuccess.org> >Sent: Nov 21, 2016 1:53 PM >To: IBM-MAIN@LISTSERV.UA.EDU >Subject: Catalogs in a SYSPLEX > >We are creating a SYSP

Re: Catalogs in a SYSPLEX

I was doing some research and I cannot seem to find any specific mention of using a single shared master catalog in the manuals. It doesn't mean I was looking in the correct manuals it just means that what I had been told may not be 100% accurate. The manuls do seem to IMPLY that a shared

Re: Catalogs in a SYSPLEX

We currently have a 2 LPAR sysplex and the master catalog in not shared. Prior to this job I worked at a shop where we supported sysplexes from a single system to up to 10 LPARs in a single sysplex. The master catalogs were not shared , I think I would put forth one big reason for not sharing

Re: Catalogs in a SYSPLEX

: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Travis Sent: Monday, November 21, 2016 12:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Catalogs in a SYSPLEX We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared

Re: Catalogs in a SYSPLEX

At our shop we have three master catalogs in the same sysplex. We run three "levels" of lpars and the master catalogs are by level. Our three tech lpars share a master catalog. Our three application test lpars share a different master catalog. Our 6 production lpars share a differ

Catalogs in a SYSPLEX

We are creating a SYSPLEX of two systems and there seems to be some debate about using a single shared master catalog or multiple master catalogs on each system. The IBM manuals recommend a single shared master catalog but our CE has been advocating multiple catalogs. What are the pros and cons

Re: Splitting a sysplex in two

There is potentially an IBM Software Pricing issue with splitting a sysplex. IBM pricing, since parallel sysplex was introduced, has allowed machines to be aggregated together for pricing. There are some complicated rules and a red paper which describes the rules is available at <ht

Re: Splitting a sysplex in two

@LISTSERV.UA.EDU Subject: Re: Splitting a sysplex in two By far the easiest--if least elegant--method is to copy the entire sysplex and restore whatever you need to make the second one work. It's untidy because you'll have lots of stuff in each plex that's meaningless. For example, production volumes

Re: Splitting a sysplex in two

By far the easiest--if least elegant--method is to copy the entire sysplex and restore whatever you need to make the second one work. It's untidy because you'll have lots of stuff in each plex that's meaningless. For example, production volumes will not be accessible from DEV and vice versa

Re: Splitting a sysplex in two

x, WLMplex -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Jesse 1 Robinson Sent: Tuesday, November 15, 2016 11:41 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Splitting a sysplex in two (This time with content.) In my experience, splitting a

Re: (External):Re: Splitting a sysplex in two

-Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 15, 2016 7:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: Splitting a sysplex in two You might also try "merging systems into a sy

Re: Splitting a sysplex in two

(This time with content.) In my experience, splitting and merging a sysplex are two very different activities. Merging is by far the more difficult because you likely have resolve name conflicts of all kinds, especially data set names. Are two like DSNs copies of the same data? If not, do you

Re: Splitting a sysplex in two

Thanks Allan...reviewing it now. Bob -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Allan Staller Sent: Tuesday, November 15, 2016 10:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Splitting a sysplex in two You might also try

Re: Splitting a sysplex in two

You might also try "merging systems into a sysplex. It should be the same checklist, just operated in reverse. Redbook SG24-6818-00 HTH. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Richards, Robert B. Sent: Tuesday, Novemb

Splitting a sysplex in two

I am in the process of planning for the splitting of a single sysplex into one PROD and one DEVL. Does anyone have a good checklist for this? The last time I did this was quite some time ago. I probably have most of the tasks identified, but can no longer find that old documentation I thought

Re: SAD testing in sysplex

ies. >... Depending on system use, this may all occur without operator awareness(!) This is the reason why we don't have AUTOIPL defined. Even the Health Checker check for AUTOIPL is turned off. Also thanks for this note 'SYSPLEX' means 'using XCF'. It is indeed very true! Thanks again. Groete / Gre

Re: SAD testing in sysplex

(Maybe more than you wanted to hear about SAD) 1. 'SYSPLEX' means 'using XCF'. You may or not use CF structures. If so, it's parallel sysplex. If not, it's basic sysplex. There is a difference in how ‘system down’ works, but it's still sysplex. 2. SAD is designed to dump a running

Re: SAD testing in sysplex

Hello, Is there a IPCS commands that can show me that SAD was written completely ? On Tue, Aug 30, 2016 at 5:28 PM, Elardus Engelbrecht < elardus.engelbre...@sita.co.za> wrote: > Nathan Astle wrote: > > >I am creating a SAD test for one of our sandbox system which is part o

Re: SAD testing in sysplex

Nathan Astle wrote: >I am creating a SAD test for one of our sandbox system which is part of >sysplex shared with other production LPAR. >So as a SAD testing, I am bringing down the LPAR and leaving with just few >task up. Just a few tasks? This is not SAD. >My question is when

Re: SAD testing in sysplex

If you vary the system out of the sysplex first it'll be put in a non-recoverable wait state. Your SAD test will certainly work, but you're testing it in a non-realistic scenario. A really good test of your total system environment would be to simulate a hard system crash and see how

SAD testing in sysplex

Hello I am creating a SAD test for one of our sandbox system which is part of sysplex shared with other production LPAR. So as a SAD testing, I am bringing down the LPAR and leaving with just few task up. My question is when I load the SAD IPL and once I confirm the SAD IPL with the VOLUMES

Re: Sysplex Timer issue

anging between 0 and 31. Kieron Hinds z/OS Integration Test / System z Platform Evaluation Test IBM Systems and Technology Group From: Nathan Astle <tcpipat...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Date: 06/15/2016 09:28 AM Subject:Re: Sysplex Timer issue Sent by

Re: Sysplex Timer issue

f the IXL160E as well as the > IEA386I from the D ETR of active system[s] in the sysplex to know for > sure, but if it the case then you'll need to get the CTNIDs to match. > > Is this the first attempt to activate the CF - if so was STP configured on > the CF CPC? Versus if it w

Re: Sysplex Timer issue

the D ETR of active system[s] in the sysplex to know for sure, but if it the case then you'll need to get the CTNIDs to match. Is this the first attempt to activate the CF - if so was STP configured on the CF CPC? Versus if it was after a configuration change made to an existing CF, do you expect

Re: MCS console sharing in a sysplex

On Wed, 8 Jun 2016 20:27:21 +0530, linda golding wrote: >Thanks Curt ... For shared DASD devices , UCW is same in HSA which is used >to serialize when IO requests from multiple LPARS arrives to the same >device . > >I was expecting something similar for console

Re: MCS console sharing in a sysplex

Hi Linda , While searching through the archives , i was able to find this post https://www.mail-archive.com/ibm-main@bama.ua.edu/msg88192.html This has got a similar discussion On Wed, Jun 8, 2016 at 8:27 PM, linda golding wrote: > Thanks Curt ... For

Re: MCS console sharing in a sysplex

Thanks Curt ... For shared DASD devices , UCW is same in HSA which is used to serialize when IO requests from multiple LPARS arrives to the same device . I was expecting something similar for console devices . But it appears that that is not the case for consoles . I hope the hardware gurus in

Re: MCS console sharing in a sysplex

On Jun 8, 2016, at 5:22 AM, linda golding wrote: > > For every device , there has to be a UCW in HSA . If the ports can be > shared between lpars , how are they going to be physically different ? > > Agree that they are unique logical devices (UCB ) on each LPAR . But

Re: MCS console sharing in a sysplex

lly different devices . > > > > > On Wed, Jun 8, 2016 at 2:09 AM, Pew, Curtis G < > curtis@austin.utexas.edu> > wrote: > > > On Jun 7, 2016, at 3:08 PM, baby eklavya <baby.ekla...@gmail.com> wrote: > > > > > > To my understanding , when sh

Re: MCS console sharing in a sysplex

n 7, 2016, at 3:08 PM, baby eklavya <baby.ekla...@gmail.com> wrote: > > > > To my understanding , when sharing MCS consoles in a sysplex , one thing > > which matters is the console name which has to be unique for each LPAR > even > > though the UCB can be the same

Re: MCS console sharing in a sysplex

On Jun 7, 2016, at 3:08 PM, baby eklavya <baby.ekla...@gmail.com> wrote: > > To my understanding , when sharing MCS consoles in a sysplex , one thing > which matters is the console name which has to be unique for each LPAR even > though the UCB can be the same . Then again ,

Re: MCS console sharing in a sysplex

On Tue, Jun 7, 2016 at 3:08 PM, baby eklavya <baby.ekla...@gmail.com> wrote: > Hi Listers , > > To my understanding , when sharing MCS consoles in a sysplex , one thing > which matters is the console name which has to be unique for each LPAR even > though the UCB can be t

MCS console sharing in a sysplex

Hi Listers , To my understanding , when sharing MCS consoles in a sysplex , one thing which matters is the console name which has to be unique for each LPAR even though the UCB can be the same . Then again , console uses EXCP to write the screen of data each time . Since the UCB is shared , how

<    1   2   3   4   5   6   7   8   9   >