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
robin...@sce.com


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Vernooij, Kees (ITOPT1) - KLM
Sent: Tuesday, January 10, 2017 4:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Steve Horein
Sent: 10 January, 2017 12:58
To: IBM-MAIN@LISTSERV.UA.EDU
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 < 
kees.verno...@klm.com> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to