ZOSMIGV2R2_NEXT_IXG_REMOVE_DRXRC

Description:

Checks to see whether the DRXRC duplex mode option is specified for any log streams in your sysplex. Support for the log stream DRXRC duplex mode option is going to be withdrawn in a future IBM z/OS release.

If this check determines that there are any log streams defined with the DUPLEXMODE(DRXRC) option in the sysplex (defined in the LOGR CDS, for example), the check continues to report this fact for the duration of this IPL, or as long as this migration check is active.

When the check detects an exception condition, it issues system message IXGH013E. If this exception appears, identify all log streams with DUPLEXMODE(DRXRC) defined and update them as desired.

Reason for check:

Because the system logger log stream DRXRC duplex mode option will no longer be supported in a future IBM z/OS release, IBM recommends that anyone currently using or planning to use the DUPLEXMODE(DRXRC) option use a different logger duplex option along with the appropriate DASD mirroring capabilities and configurations.

z/OS® releases the check applies to:

z/OS V1R13, z/OS V2R1, and z/OS V2R2.

Type of check (local, remote, or REXX):

Local

User override of IBM values:

The following sample shows the defaults for customizable values for this check. Use this sample to make permanent check customizations in an HZSPRMxx parmlib member used at IBM Health Checker for z/OS startup. If you just want a one-time only update to the check defaults, omit the first line (ADDREPLACE POLICY) and use the UPDATE statement on a MODIFY hzsproc command. Note that using non-POLICY UPDATEs in HZSPRMxx can lead to unexpected results and is therefore not recommended. End of change

ADDREPLACE POLICY[(policyname)] [STATEMENT(name)]
UPDATE CHECK(IBMIXGLOGR,ZOSMIGV2R2_NEXT_IXG_REMOVE_DRXRC)
INACTIVE
SEVERITY(LOW)
INTERVAL(ONETIME)
DATE('date_of_the_change')
Reason('Your reason for making the update.')

Debug support:

Verbose support:

Reference:

For more information, see the DUPLEXMODE keyword on log stream define and update requests for the IXCMIAPU Administrative Data Utility program in z/OS MVS Setting Up a Sysplex.

Messages:

This check issues the following exception messages:

- IXGH013E

See the IXGH messages in z/OS MVS System Messages, Vol 10 (IXC-IZP).

SECLABEL recommended for MLS users:

SYSLOW

Output: The following shows output from ZOSMIGV2R2_NEXT_IXG_REMOVE_DRXRC:

Output for the no exceptions case:

CHECK(IBMIXGLOGR,ZOSMIGV2R2_NEXT_IXG_REMOVE_DRXRC)
SYSPLEX:    sysplex   SYSTEM: system
START TIME: 05/30/2016 13:12:11.109876
CHECK DATE: 20160530  CHECK SEVERITY: LOW

IXGH012I This sysplex does not contain any log streams with the
DUPLEXMODE(DRXRC) specification.

END TIME: 05/30/2016 13:12:13.678910  STATUS: SUCCESSFUL

Output for the check when some exceptions are found:

CHECK(IBMIXGLOGR,ZOSMIGV2R2_NEXT_IXG_REMOVE_DRXRC)
SYSPLEX:    sysplex   SYSTEM: system
START TIME: 05/30/2016 14:36:35.458411
CHECK DATE: 20160530  CHECK SEVERITY: LOW

* Low Severity Exception *

IXGH013E One or more log stream definitions in this sysplex has
the DUPLEXMODE(DRXRC) specification.

Explanation:  There are one or more log stream definitions in
the logger Couple Data Set (LOGR CDS) for this sysplex that
have the DUPLEXMODE(DRXRC) specification.

Because the system logger log stream DRXRC duplex mode
option will no longer be supported in a future IBM z/OS
release, IBM recommends that anyone currently using, or were
planning to use, the log stream DUPLEXMODE(DRXRC)
specification should instead make use of an existing,
alternative logger duplex option along with the appropriate
DASD mirroring capabilities/configurations.

Refer to system logger health check
ZOSMIGV2R2_NEXT_IXG_REMOVE_DRXRC.

System Action:  The system continues processing.

Operator Response:  Report this problem to the system
programmer.

System Programmer Response:  You should identify all possible
log streams that may need attention and take the steps
necessary to get them updated as desired.  Consider taking
one or more of the following actions:

1.  What to look for:
A.  Use the IXCMIAPU utility for DATA TYPE(LOGR)
REPORT(YES), and identify any logstreams with the
STG_DUPLEX(YES) DUPLEXMODE(DRXRC) attributes.

Sample report job:
//LOGRPT  JOB
//STEP1 EXEC PGM=IXCMIAPU
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DATA TYPE(LOGR) REPORT(YES)
/*

After running the IXCMIAPU utility, if there are no
log streams with the DUPLEXMODE(DRXRC) option
identified, then you have no impact, and you can skip
the next steps.

B.  For each logstream identified in step 1.A as having
the DRXRC attribute, you can enter a

DISPLAY LOGGER,LOGSTREAM,LSN=log-stream-name

command and review the IXG601I display message output
to determine if there are any connections to the log
stream in the sysplex.

If there are no connections, then the following shows
a sample of the IXG601I display message output:

D LOGGER,L,LSN=log-stream-name
IXG601I   15.14.13  LOGGER DISPLAY   FRAME LAST  F  E  SYS=SY1
INVENTORY INFORMATION BY LOGSTREAM
LOGSTREAM                  STRUCTURE        #CONN  STATUS
---------                  ---------        ------ ------
log-stream-name            LIST02           000000 AVAILABLE

NUMBER OF LOGSTREAMS:  000001

If there are any connections to the logstream, then
the IXG601I message output will indicate which systems
are connected and the duplex options (including
"STAGING DRXRC").  The following shows a sample of the
IXG601I display message output for this case:

D LOGGER,L,LSN=log-stream-name
IXG601I   15.14.13  LOGGER DISPLAY   FRAME LAST  F  E  SYS=SY1
INVENTORY INFORMATION BY LOGSTREAM
LOGSTREAM                  STRUCTURE        #CONN  STATUS
---------                  ---------        ------ ------
log-stream-name            LIST01           000001 IN USE
SYSNAME: SY1
DUPLEXING: LOCAL BUFFERS, STAGING DRXRC
GROUP: PRODUCTION

NUMBER OF LOGSTREAMS:  000001

2.  What to do:
A.  If there are no log streams with the DRXRC duplex mode
identified, then you have no impact.

B.  If the DRXRC duplex mode option is specified and the
identified log streams have no connections, then
update the log stream to use a different duplex mode
option.  You can simply run the IXCMIAPU utility to
update the log stream by specifying either
DUPLEXMODE(COND) or DUPLEXMODE(UNCOND).
Alternatively, you can set option STG_DUPLEX(NO) so a
staging data set will not be used to duplex the log
stream data.

C.  For any identified log streams with the DRXRC duplex
mode option that have connections, you can either:

(1) cause the log stream to be disconnected and then
update the log stream definition as in step 2.B
above, or

(2) make the updates to the log stream definition,
which will go pending (assuming you are using at
least an HBB7705 format level LOGR CDS), and then
take the steps necessary to have the pending
updates become effective for the log stream.

See topic "Updating a log stream's attributes" in
z/OS MVS Setting Up a Sysplex on how to modify a
log stream DUPLEXMODE or STG_DUPLEX attribute
while there is an existing connection.

D.  After correcting any log stream definitions, consider
running the check again so it is no longer displayed
as an exception.  For example, use system modify
command:

F HZSPROC,RUN,CHECK(IBMIXGLOGR,ZOSMIGV2R2_NEXT_IXG_REMOVE_DRXRC)

See the IBM Health Checker for z/OS User's Guide for
details on manually requesting a check run or for
changing the check's INTERVAL to allow for more
automatic runs.

Check Reason:  Logger DUPLEXMODE(DRXRC) use should be
investigated since it will no longer be
supported in a future IBM z/OS release

END TIME: 05/30/2016 14:36:35.464384  STATUS: EXCEPTION-LOW