You need to run your system as a monoplex, not in XCFLOCAL mode
PLEXCFG=XCFLOCAL
Specifies that the system is to be a single, stand-alone MVS system that is
not a member of a sysplex and cannot use couple data sets. The COUPLExx parmlib
member cannot specify a sysplex couple data set, and, therefore, other couple
data sets cannot be used. Thus, functions such as using System Logger to write
data to log streams, which require a couple data set, are not available.
In XCF-local mode, XCF does not provide signaling services between MVS
systems. However, multi-system applications can create groups and members, and
messages can flow between group members on this system. If signaling paths are
specified, they are tested for their operational ability, but they are not used.
Use XCF-local mode for a system that is independent of other systems. In
XCF-local mode, XCF services (except permanent status recording) are available
on the system and you can do maintenance, such as formatting a couple data set
or changing the COUPLExx parmlib member. The IBM-supplied default parmlib
member COUPLE00 and the COUPLE=** system parameter are intended to be used to
bring up the system in XCF-local mode.
PLEXCFG=MONOPLEX
Specifies that the system is to be a single-system sysplex that must use a
sysplex couple data set. Additional couple data sets, such as those that
contain policy information, can also be used. XCF coupling services are
available on the system, and multi-system applications can create groups and
members. Messages can flow between members on this system (but not between this
system and other MVS systems) through XCF signaling services. If signaling
paths are specified, they are not used.
You must specify a COUPLExx parmlib member that gives the system access to
a sysplex couple data set to be used only by this system. When a system IPLs
into a single-system sysplex, no other system is allowed to join the sysplex.
Use MONOPLEX when you want only one system in the sysplex (for example, to
test multi-system applications on one system) or when you want to use a
function, such as WLM, that requires a couple data set.
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get&[email protected]
On Tuesday, January 28th, 2025 at 1:11 PM, 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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
