*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
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
Hi,
Allocate a new SYS1.LOGR.CDSXX(utility : IXCL1DSU) with larger
attribute,Use SETXCF COUPLE command to add the alternate CDS and change the
COUPLXX accordingly for next IPL.
Thanks
On Tue, Jul 10, 2012 at 1:22 PM, Vernooij, CP - SPLXM kees.verno...@klm.com
wrote:
Jake wrote Here in my
The same applies to Logstream
structures, you (at least I) don't want application department to mess
around uncontrolled in my CFs.
One of the first things I have always done in a new installation was to get the
permissions to define or change couple CDSs of any kind under the control of
one
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)
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
