Jake wrote "Here in my case I am not defining the Couple dataset so Just defining the Logstream to DASD."
If the Couple datasets are controlled by different departments, I am glad I have all Sysplex constructs under my control. I have read more problems from sites where Couple datasets, CFs and Logstreams are controlled by different departments. Even the IBM Logstream examples contain simple JCL to allocate Couple datasets, update SYS1.PARMLIB etc. As if this is really as simple as this and a site does not have policies to comply with. If I were to write those manuals, I would say: ask the responsible department to allocate / enlarge etc. your Couple datasets. The same applies to Logstream structures, you (at least I) don't want application department to mess around uncontrolled in my CFs. Kees. "Mike Schwab" <[email protected]> wrote in message news:<CAJTOO5-M57=njx-sbngf+jwmxifetvv5f5otacuukgonp0p...@mail.gmail.com >... > > *Explanation:* The system logger couple data set defined by the LOGR policy > > has no free space for the type of entry you are trying to define. > > Logstreams are tracked within the coupling dataset, and you have run > out of that type of entries. Change the coupling dataset to have more > entries for that type of entry. > > On Mon, Jul 9, 2012 at 11:30 PM, Jake anderson <[email protected]> wrote: > > lizette, > > > > Probably I missed saying that I referred the LOOKAT ibm. LOOKAT explanation > > says : > > > > *IXG010E* *NO* *SPACE* *IS* *AVAILABLE* *FOR* type *ENTRIES* > > > > *Explanation:* The system logger couple data set defined by the LOGR policy > > has no free space for the type of entry you are trying to define. > > > > Here in my case I am not defining the Couple dataset so Just defining the > > Logstream to DASD. > > > > *IXG002E* *LOGR* *POLICY* *PROCESSING* *ENDED* *WITH* *RETCODE=* > > retcode *RSNCODE=* > > rsncode > > IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=00000008 RSNCODE=00000823 > > > > Jake > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ******************************************************** 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
