Hi Kees - While I don't have an answer for your question, I do see a very similar question posed to the "GDPS User Community" forum. Any GDPS questions I have, I ask there. You should be able to search for that community from here: https://apps.na.collabserv.com/communities It is restricted, so you would need to request access.
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 information, services and offers, please visit our web site: > http://www.klm.com. This e-mail and any attachment may contain > confidential and privileged material intended for the addressee only. If > you are not the addressee, you are notified that no part of the e-mail or > any attachment may be disclosed, copied or distributed, and that any other > action related to this e-mail or attachment is strictly prohibited, and may > be unlawful. If you have received this e-mail by error, please notify the > sender immediately by return e-mail, and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its > employees shall not be liable for the incorrect or incomplete transmission > of this e-mail or any attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch > Airlines) is registered in Amstelveen, The Netherlands, with registered > number 33014286 > ******************************************************** > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
