IBM Mainframe Forum

by **VGorbati** » Tue Nov 20, 2012 10:41 pm

Hello everyone, I'm currently participating in IBM zContest, and (I don't know how) I made it to the part 3, where I need to set up a new CICS region by providing defined CICS data sets. I am provided with JCL programs to create all this data sets. The problem occur whilst providing LOGGER data sets. The job returns with MAXCC=12, and in SDSF I see the following:

Select all

LINE # CONTROL CARDS
1 DATA TYPE(LOGR) REPORT(NO)
2
3 DEFINE LOGSTREAM NAME(STC.ZCON455.DFHLOG)
4 DASDONLY(YES)
5 MAXBUFSIZE(64000)
6 STG_SIZE(3000) RETPD(8)
7 LOWOFFLOAD(20) HIGHOFFLOAD(95)
8
9 DEFINE LOGSTREAM NAME(STC.ZCON455.DFHSHUNT)
10 DASDONLY(YES)
11 MAXBUFSIZE(64000)
12 STG_SIZE(5000) RETPD(8)
13 LOWOFFLOAD(0) HIGHOFFLOAD(80)
1ADMINISTRATIVE DATA UTILITY: MESSAGES DATA TYPE = LOGR
+_______________________________________________________________________________

IXG005I LOGR POLICY PROCESSING LINE# 3
IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES
IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=00000008 RSNCODE=00000823
IXG003I LOGR POLICY PROCESSING ENCOUNTERED AN UNEXPECTED ERROR. DIAGNOSIS INFO

I have already googled this return code, and I found this on IBM's site:

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.

Well, here come my questions:
1. Can it be, that someone just misconfigured my profile (cause in "Part3.pdf" there isn't any mention about this problem, it looks like everything should work just fine)?
2. If no, can you please give me more or less detailed explanation how to use this "IXCL1DSU utility"?

by **VGorbati** » Tue Nov 20, 2012 10:53 pm

3. Or maybe there is easier way to fix this problem?

by **enrico-sorichetti** » Tue Nov 20, 2012 11:04 pm

what happened when you looked at the messages manual...

done the searching on Your behalf

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.

In the message text:

type
is the type of entry trying to be defined.
System action:
The entry is not defined.

User response:
None.

Operator response:
None.

Application Programmer Response:
None.

System programmer response:
Delete unneeded entries of this type or define a new couple data set for the LOGR policy, specifying a larger number of records for the type of entry you are trying to define. If you define a new couple data set, make it the primary data set for the LOGR policy using the SET command.

Source:
System logger (SCLOG)

Detecting Module:
MANY

the chances of getting help on a forum are really slim ...
we do not know the setup, nor what You have done before, nor, nor, nor, ...

unfortunately ( for the specific problem )
a forum is for quick and dirty questions, not for long debugging sessions
as would be needed in this case.

if You have followed exactly the instructions given.
and you received the error message the first time You ran the job probably
the best place to ask for clarifications is the contest <help desk>

by **VGorbati** » Tue Nov 20, 2012 11:41 pm

Did I get it correctly, that some system data set (created before) is already full with LOGSTREAM's entries, hence I can't add new ones? But what if I just "Delete unneeded entries of this type" from this data set? Or it can lead to some bad consequences?

by **Robert Sample** » Tue Nov 20, 2012 11:44 pm

What do you get when you run this job?

Select all

//LOGRLIST EXEC PGM=IXCMIAPU
//STEPLIB DD DSN=SYS1.MIGLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DATA TYPE(LOGR) REPORT(YES)
LIST LOGSTREAM NAME(STC.ZCON455.DFHLOG) DETAIL(YES)
LIST LOGSTREAM NAME(STC.ZCON455.DFH$HUNT) DETAIL(YES)
/*

This is, most likely, the same JCL you are running to create your logstreams but listing instead of defining data.

by **VGorbati** » Wed Nov 21, 2012 3:18 pm

Robert Sample wrote:What do you get when you run this job?
This is, most likely, the same JCL you are running to create your logstreams but listing instead of defining data.

So, I executed the JCL you gave (except I corrected 'DFH$HUNT' to 'DFHSHUNT'), and this is what I get:

Select all

XG005I LOGR POLICY PROCESSING LINE# 2
IXG405I NO LOGSTREAM RECORDS FOUND THAT MATCH PATTERN STC.ZCON455.DFHLOG
IXG005I LOGR POLICY PROCESSING LINE# 3
IXG405I NO LOGSTREAM RECORDS FOUND THAT MATCH PATTERN STC.ZCON455.DFHSHUNT

LOGR Inventory Record Summary:

LOGR COUPLE DATA SET FORMAT LEVEL: HBB6603

/* Functional Items: */
/* SMDUPLEX(0) */

Type Formatted In-use
------------------- --------- ------
LSR (Log Stream) 1,500 1,500

LSTRR (Structure) 64 0

DSEXTENT (Data Set Extent) 24 0

LOGSTREAM NAME(CICSTS.BCMP005.DFHLOG) STRUCTNAME() LS_DATACLAS()
LS_MGMTCLAS() LS_STORCLAS() HLQ(IXGLOGR) MODEL(NO) LS_SIZE(0)
STG_MGMTCLAS() STG_STORCLAS() STG_DATACLAS() STG_SIZE(3000)
LOWOFFLOAD(20) HIGHOFFLOAD(95) STG_DUPLEX(YES) DUPLEXMODE(UNCOND)
RMNAME() DESCRIPTION() RETPD(8) AUTODELETE(NO) OFFLOADRECALL(YES)
DASDONLY(YES) DIAG(NO) LOGGERDUPLEX() EHLQ(NO_EHLQ) GROUP()
MAXBUFSIZE(64000)

LOGSTREAM NAME(CICSTS.BCMP005.DFHSHUNT) STRUCTNAME() LS_DATACLAS()
LS_MGMTCLAS() LS_STORCLAS() HLQ(IXGLOGR) MODEL(NO) LS_SIZE(0)
STG_MGMTCLAS() STG_STORCLAS() STG_DATACLAS() STG_SIZE(5000)
LOWOFFLOAD(0) HIGHOFFLOAD(80) STG_DUPLEX(YES) DUPLEXMODE(UNCOND)
RMNAME() DESCRIPTION() RETPD(8) AUTODELETE(NO) OFFLOADRECALL(YES)
DASDONLY(YES) DIAG(NO) LOGGERDUPLEX() EHLQ(NO_EHLQ) GROUP()
MAXBUFSIZE(64000)

Then, there are a lot of similar records: basically, only LOGSTREAM NAME change to CICSTS.BCMP006.DFHLOG, CICSTS.BCM006.DFHSHUNT, CICSTS.BCMP007.DFHLOG, CICSTS.BCM007.DFHSHUNT and so on up to number 20 or so. After that, come similar records but for other LOGSTREAM names, and finally, the records with names CICSTS.ZCONxxx.DFHLOG(DFHSHUNT) are coming. So, I scrolled it all the way down to my user ID (ZCON455), and this is how it goes:
First, some kind of header:

Select all

LS_MGMTCLAS() LS_STORCLAS() HLQ(IXGLOGR) MODEL(NO) LS_SIZE(0)
STG_MGMTCLAS() STG_STORCLAS() STG_DATACLAS() STG_SIZE(3000)
LOWOFFLOAD(20) HIGHOFFLOAD(95) STG_DUPLEX(YES) DUPLEXMODE(UNCOND)
RMNAME() DESCRIPTION() RETPD(8) AUTODELETE(NO) OFFLOADRECALL(YES)
DASDONLY(YES) DIAG(NO) LOGGERDUPLEX() EHLQ(NO_EHLQ) GROUP()
MAXBUFSIZE(64000)

Then come the records for ZCON443 and ZCON444, and finally the records with my ID:

Select all

LOGSTREAM NAME(CICSTS.ZCON445.DFHLOG) STRUCTNAME() LS_DATACLAS()
LS_MGMTCLAS() LS_STORCLAS() HLQ(IXGLOGR) MODEL(NO) LS_SIZE(0)
STG_MGMTCLAS() STG_STORCLAS() STG_DATACLAS() STG_SIZE(3000)
LOWOFFLOAD(20) HIGHOFFLOAD(95) STG_DUPLEX(YES) DUPLEXMODE(UNCOND)
RMNAME() DESCRIPTION() RETPD(8) AUTODELETE(NO) OFFLOADRECALL(YES)
DASDONLY(YES) DIAG(NO) LOGGERDUPLEX() EHLQ(NO_EHLQ) GROUP()
MAXBUFSIZE(64000)

LOGSTREAM NAME(CICSTS.ZCON445.DFHSHUNT) STRUCTNAME() LS_DATACLAS()
LS_MGMTCLAS() LS_STORCLAS() HLQ(IXGLOGR) MODEL(NO) LS_SIZE(0)
STG_MGMTCLAS() STG_STORCLAS() STG_DATACLAS() STG_SIZE(5000)
LOWOFFLOAD(0) HIGHOFFLOAD(80) STG_DUPLEX(YES) DUPLEXMODE(UNCOND)
RMNAME() DESCRIPTION() RETPD(8) AUTODELETE(NO) OFFLOADRECALL(YES)
DASDONLY(YES) DIAG(NO) LOGGERDUPLEX() EHLQ(NO_EHLQ) GROUP()
MAXBUFSIZE(64000)

by **VGorbati** » Wed Nov 21, 2012 3:44 pm

So, I should probably delete this LOGSTREAM entries, and then re-run the JCL, that defines STC.ZCON455.DFHLOG and STC.ZCON455.DFHSHUNT entries, shouldn't I?

by **Robert Sample** » Wed Nov 21, 2012 5:19 pm

So, I should probably delete this LOGSTREAM entries, and then re-run the JCL, that defines STC.ZCON455.DFHLOG and STC.ZCON455.DFHSHUNT entries, shouldn't I?

Why? Once you've deleted the entries, the logstreams are already defined so unless you delete the definitions, attempting to redefine them is going to fail because they are already defined.

by **VGorbati** » Wed Nov 21, 2012 5:58 pm

So what can I do?:)

by **VGorbati** » Wed Nov 21, 2012 6:02 pm

So what can I do?:) Is it possible to tell new CICS region to use not LOGSTREAM entries at path STC.ZCON455 but at path CICSTS.ZCON455?

IBM Mainframe Forum

IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.

Re: IXG010E NO SPACE IS AVAILABLE FOR LOGSTREAM ENTRIES.