Hi, Absolutely right all my three LOGR contol dataset are running out of space. I just got to define a newer one.
Thanks Jake On Tue, Jul 10, 2012 at 12:09 PM, Mike Schwab <[email protected]>wrote: > > *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 IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
