> > 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,
Had you searched the internet you would have come across the following link http://publib.boulder.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ib m.zos.r12.ieaa900%2Fiea2a9b0783.htm With the following details for 823 08 xxxx0823 Equate Symbol: IxgRsnCodeNoInvrecSpace Explanation: Environment error. The LOGR couple data set cannot be updated because the maximum number of entries for the specified type has already been reached. Action: Format a new LOGR couple data set using the IXCL1DSU utility. In the new LOGR couple data set either delete unused entries or increase the allowed number of entries on the LSR parameter (for log stream entries) or the LSTRR parameter (for coupling facility structure entries). PSWITCH the current alternate LOGR couple data set to primary. Add the new LOGR couple data set as alternate. PSWITCH the new LOGR couple data set from alternate to primary. If you received this reason code from IXCMIAPU, see message IXG010E. As others have pointed out, you should have a single area to handle these datasets. IMHO you may have issues at Disaster Recovery Process if you do not control these items in your shop. Who would know what to rebuild and why if there are problems? Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
