H Skip,
Since I never tripped it, that check came in (whenever it did) and I forgot
about
it. With the 186 checks I see on my system, I don't know or remember
all of them that run these days (unless they trip of course). :-)
There is another related check which states the ROT I quoted in my post:
CHECK(IBMXCF,XCF_MAXMSG_NUMBUF_RATIO)
CHECK PARM: 30
IXCH0428I All inbound signal paths that can be checked from <sys>
currently support at least as many messages as the owner specified
minimum of 30.
STATUS: SUCCESSFUL
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:[email protected]
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/
On Wed, 26 Jun 2013 07:27:37 -0700, Skip Robinson <[email protected]>
wrote:
>The text of health check XCF_DEFAULT_MAXMSG says this:
>
>CHECK PARM: 2000
>
>IXCH0426I The XCF transport class MAXMSG value is currently equal to or
>larger than the owner specified value 2000.
>
>.
>.
>JO.Skip Robinson
>Southern California Edison Company
>Electric Dragon Team Paddler
>SHARE MVS Program Co-Manager
>626-302-7535 Office
>323-715-0595 Mobile
>[email protected]
>
>
>
>From: Mark Zelden <[email protected]>
>To: [email protected],
>Date: 06/26/2013 07:20 AM
>Subject: Re: XCF MAXMSG
>Sent by: IBM Mainframe Discussion List <[email protected]>
>
>
>
>On Wed, 26 Jun 2013 08:59:27 -0400, Richards, Robert B.
><[email protected]> wrote:
>
>>Okay, I am feeling little dense this morning/week.
>>
>>I am trying to decode how to determine the best value to set for MAXMSG.
>Having read and re-read applicable sections of "Setting Up A Sysplex", I
>am still not "getting it".
>>
>>Reason for being there? From the SR:
>>
>>EZZ4338I ERROR REPORTED ON INTERFACE EZ6XCFID - CODE 80100044
>>DIAGNOSTIC CODE 03
>>EZZ4310I ERROR: CODE=80100044 REPORTED ON DEVICE VTAMF. DIAGNOSTIC
>>CODE: 03
>>EZZ4337I ATTEMPTING TO RECOVER INTERFACE EZ6XCFID
>>EZZ4309I ATTEMPTING TO RECOVER DEVICE VTAMF
>>IST1504I XCF CONNECTION WITH WDPC.VTAMF IS INOPERATIVE 664
>>IST1501I XCF TOKEN = 0300013600270003
>>IST1578I DEVICE INOP DETECTED FOR ISTTCDID BY ISTTSCBX CODE = 001
>>IST314I END
>>IST1578I SOFT INOP DETECTED FOR ISTTCDID BY ISTTSC8X CODE = 005
>>.
>>These messages indicate an XCF buffer shortage as described in
>>Technote SWG21244665 which reads as follows:
>>For ISTXCF, the MAXMSG parameter for PATHIN and PATHOUT
>>should be tuned to its upper limit value.
>>The higher value of MAXMSG parameter does not cause XCF
>>to use more storage. Therefore, you can raise the value
>>of your MAXMSG parameter to resolve this problem.
>>
>>Any advice on how to decode the manual and come up with a "happy value"
>would be appreciated. Which maxmsg?
>>
>
>Hi Bob,
>
>Here is a note I have in my COUPLExx members. The advise probably comes
>from a Mark Brooks SHARE presentation or whitepaper.
>
>/* MAXMSG should be high enough for at least 30 messages/buffers */
>/* default MAXMSG was 750 (chg in os/390 r2 from 500) */
>/* default MAXMSG is currently 2000 (chg in z/os 1.7 from 750) */
>
>My MAXMSG is set to 2000 (the z/OS 1.7 default) in CLASSDEF for all
>of my transport classes.
>
>Cheers,
>
>Mark
>
>
>----------------------------------------------------------------------
>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
