Try This:
//STEP01 EXEC PGM=IXCMIAPU
//* STEPLIB DD DSN=OSV2R6.SYS1.MIGLIB,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DATA TYPE(LOGR) REPORT(YES)
DEFINE LOGSTREAM NAME(HAWCICS1.HAWCICS1.DFHLOG)
LS_DATACLAS(LOGRCLAS)
LS_STORCLAS(NONSMS)
STG_DATACLAS(STAGCLAS)
STG_STORCLAS(NONSMS)
STG_SIZE(20000)
LS_SIZE(40000)
MODEL(NO)
HLQ(CICSTS55)
DASDONLY(YES)
LOWOFFLOAD(40)
HIGHOFFLOAD(80)
Matthew
On Tue, 28 Jan 2025 18:11:22 +0000, Steely.Mark <[email protected]> wrote:
>It has been quite some time since I last worked with a similar setup, and I am
>reaching out for guidance.
>I have an LPAR defined in the COUPLExx parmlib member as COUPLE
>SYSPLEX(LOCAL), and I am attempting to bring up a CICS region that requires
>log streams to be defined.
>
>However, I am encountering the following errors:
>
>IXG002E LOGR POLICY PROCESSING ENDED WITH RETCODE=00000008 RSNCODE=00000814
>IXG003I LOGR POLICY PROCESSING ENCOUNTERED AN UNEXPECTED ERROR.
>DIAGNOSIS INFORMATION: 00000000 00000000 00000000 00000000
>
>The Reason Code (0814) indicates the following:
>
>Reason: "The log stream structure size is not sufficient to accommodate the
>request."
>Cause: This typically occurs when the structure size in the Coupling Facility
>is too small to support the defined log streams.
>
>The challenge here is that I do not have a Coupling Facility (CF), so no CF
>structures are defined.
>
>In the past, I worked in an environment that did not utilize a CF, yet we
>successfully defined log streams. Unfortunately, I cannot recall how the
>COUPLExx parmlib member was configured or what additional parmlib members were
>required to achieve this.
>
>Would anyone with experience in setting up log streams in a non-CF environment
>be able to provide guidance or examples of the required configurations?
>
>Specifically, I am looking for:
>
>A sample COUPLExx member configuration for a DASD-only setup.
>Any relevant LOGR policy or staging dataset definitions.
>
>Any assistance or samples you can provide would be greatly appreciated.
>
>Thank you in advance for your help!
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
