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
Jake
On Tue, Jul 10, 2012 at 9:44 AM, Lizette Koehler <[email protected]>wrote:
> >
> > Dear List,
> >
> > Good Day.
> >
> > I am trying to Enable RRS facility for a DB2 related stuff. I am using
> the
> below JCL for
> > defining the Logstream :
> >
> >
> > DATA TYPE(LOGR)
> > DEFINE LOGSTREAM NAME(ATR.PLEX1.MAIN.UR)
> > LOWOFFLOAD(60)
> > HIGHOFFLOAD(80)
> > DASDONLY(YES)
> > HLQ(IXGLOGR)
> > LS_SIZE(1024)
> > LS_DATACLAS(VSAMLS)
> > STG_SIZE(1024)
> > DEFINE LOGSTREAM NAME(ATR.PLEX1.DELAYED.UR)
> > LOWOFFLOAD(60)
> > HIGHOFFLOAD(80)
> > DASDONLY(YES)
> > HLQ(IXGLOGR)
> > LS_SIZE(960)
> > LS_DATACLAS(VSAMLS)
> > STG_SIZE(960)
> > DEFINE LOGSTREAM NAME(ATR.PLEX1.ARCHIVE)
> > LOWOFFLOAD(0)
> > HIGHOFFLOAD(80)
> > DASDONLY(YES)
> > HLQ(IXGLOGR)
> > LS_SIZE(960)
> > LS_DATACLAS(VSAMLS)
> > AUTODELETE(YES)
> > RETPD(2)
> > STG_SIZE(2000)
> > DEFINE LOGSTREAM NAME(ATR.PLEX1.RM.DATA)
> > LOWOFFLOAD(60)
> > HIGHOFFLOAD(80)
> > DASDONLY(YES)
> > HLQ(IXGLOGR)
> > LS_SIZE(192)
> > LS_DATACLAS(VSAMLS)
> > STG_SIZE(192)
> > DEFINE LOGSTREAM NAME(ATR.PLEX1.RESTART)
> > LOWOFFLOAD(60)
> > HIGHOFFLOAD(80)
> > DASDONLY(YES)
> > HLQ(IXGLOGR)
> > LS_SIZE(960)
> > LS_DATACLAS(VSAMLS)
> > STG_SIZE(960)
> >
> >
> > Z/OS : 1.13
> > DB2 : 10.1
> >
> > But I am ending up with an error :
> >
> > IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES IXG002E LOGR POLICY
> > PROCESSING ENDED WITH RETCODE=00000008
> > RSNCODE=00000823
> >
> > All the definition starting with IXGLOGR.ATR.** are ACS controlled and
> they sit in a
> > dedicated LOGR volume "DEVLOG'. I can see DEVLOG volume is still
> > 94 % free and I still Get an error message as "NO SPACE IS AVAILABLE FOR
> > LOGSTREAM ENTRIES".
> >
> > Reviewing the Log I can see ATR.PLEX1.MAIN.UR and ATR.PLEX1.DELAYED.UR
> are
> > getting defined, but the other consecutive steps are abending with space
> issue. Is it
> > something I have to reduce the STG_SIZE for the next LOGSTREAM ? Reducing
> the
> > STG_SIZE will have any impact on the performance side ?
> >
> > Please advise me.
> >
> > Jake
> >
>
> Jake,
>
> Did you even try to look up the error message before posting? You seem to
> post without doing any research.
>
> Advise: Look up the error and see if that tells you what you need to know.
>
> Lizette
>
> ----------------------------------------------------------------------
> 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
