We have been running GDPS for DR since around 2000. Currently on V3R12. My copy of Installation and Customization Guide ZG24-6704-25 contains no reference to IXGLOGR. I did a Google search on 'IXGLOGR GDPS' and found some (even quite old) hits that seem to imply that IXGLOGR is a no-no on GDPS K system. However, as I said, the address space is active on our K system. We do not actually manage any log streams because there is no ICF access in that sysplex, and we have never ventured into DASD-only log streams. But task IXGLOGR is active.
This issue may have less to do with GDPS release than with configuration. Our DR sysplex is isolated from production except for the 'invisible' mirrored volumes. When we IPL a DR image for testing, it is completely isolated from the K system, which continues to run mirroring in other LPARs on the same box. There is no overlap. I am just as confused and mystified as ever. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: Tuesday, January 10, 2017 11:16 PM To: [email protected] Subject: (External):Re: Confusing info about System Logger and GDPS K-systems Maybe it depends on the GDPS level you are running, but in the V3.13 (and several previous) manuals, appendix D states: "As a consequence, and to avoid use of the System Logger on the Controlling systems and any associated allocation of offload or staging data sets that must be PPRCed for recovery purposes, the System Logger address space (IXGLOGR) is cancelled on any Controlling system where it is found to be active. This is initially performed during GDPS initialization on any Controlling system. Then subsequently Monitor1 checks to ensure that the System Logger is not available on any Controlling systems. Again, if it is found to be active, it will be cancelled by GDPS." Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jesse 1 Robinson Sent: 10 January, 2017 18:22 To: [email protected] Subject: Re: Confusing info about System Logger and GDPS K-systems I'm confused and mystified. We run GDPS for DR on a standalone sysplex. I'm not sure what (if anything) we do with logger there, but the task is definitely running on the K system. IXG601I 09.19.25 LOGGER DISPLAY SYSTEM LOGGER STATUS SYSTEM SYSTEM LOGGER STATUS ------ -------------------- X1 ACTIVE . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vernooij, Kees (ITOPT1) - KLM Sent: Tuesday, January 10, 2017 4:28 AM To: [email protected] Subject: (External):Re: Confusing info about System Logger and GDPS K-systems Hi Steve, Thanks fort the hint. The 2 apars seem (to me) to solve a situation caused by the new ALLOWACCESS(NO) parameter. Kees. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Steve Horein Sent: 10 January, 2017 12:58 To: [email protected] Subject: Re: Confusing info about System Logger and GDPS K-systems These new function APARs may shed some light: OA50781 and OA50775 They talk about secondary controlling systems (KSYS) being present within the SYSPLEX, and IPL order. I hope this helps! On Tue, Jan 10, 2017 at 5:24 AM, Vernooij, Kees (ITOPT1) - KLM < [email protected]> wrote: > Hello, > > We run GDPS V3R13 and z/OS V2.2. > I am reading the GDPS recommendations (in the GDPS/PPRC V3R13 > Installation and Customization Guide) about System Logger, which, as > seems usual with each GDPS release, have changed again. > > Now I read some confusing and/or contradicting information (Ch 2.6). > > * The recommendation remains to not run System Logger on GDPS > K-systems. GDPS will kill it if found. > > * There is a new IXGCNFxx member with parameters for System Logger. > > * The GDPS manual recommends ("To prevent XCFAS on the Controlling > systems from allocating the LOGR CDS") to specify MANAGE > ALLOWACCESS(NO) in IXGCNFxx on GDPS K-systems. > > What is the use of the last recommendation? > > * IXGCNFxx is used by System Logger, which is not started there, > so it will never be processed. > > * Why would XCFAS access the LOGR CDS if not directed so by System > Logger? > > * If yet so, how would XCFAS know about the XCFCNFxx restriction? > > DISPLAY LOGGER,IXGCNF,MANAGE > IXG602I DISPLAY LOGGER COMMAND NOT PROCESSED, THE SYSTEM LOGGER IS NOT > ACTIVE. > > Am I missing something? > > Regards, > Kees. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
