On 12/30/2024 11:33 AM, Art Gutowski wrote:
I'm hoping to hear from Mark or someone in XCF/CFRM (and/or someone in Heath 
Checker development), but in the meantime, I'll ask a couple of pedantic questions. 
 What is your policy definition for this structure - InitSize, Size, and MinSize?  
Just for G&G, what do your Logger definitions look like for the structure and 
the log stream?

Art,

It's good to hear from you brutha. SHARE hasn't killed you yet... ;-)

Originally, my HZS logstream was variable size i.e., INIT(9M) and SIZE(12M) so I changed both values to 9M. No difference in behavior. Since our IPL on Sunday, we've seen the IXC534I for OPERLOG only four times while it appeared 38 times for Health Checker over that same time frame.

I set the following SLIP to catch the IXLALTER call in the act and examined the dump in IPCS:

SLIP SET,IF,ID=EEJ1,NUCMOD=IXLCSALT,DATA=(1R?+8,EQ,C8E9E26D),A=SVCD,SDATA=(PSA,NUC,RGN,CSA,SQA,LPA,TRT),END

I found that Health Checker was writing to its logstream (BALR/BAKR to IXGW1TSK) and that led to a PC to XCF (IXLC1ALT) to alter the structure. LOGGER simply decided it was time to ALTER the structure as a result of the current IXGWRITE request.

It appears my assumption about which logstream is used more heavily is just flat-out wrong. Both structures are roughly the same size. Health Checker must be writing ~10 times as much data to its logstream as MVS is writing to OPERLOG. It's the only explanation.

I did notice one difference between the two structure definitions. HZS_HEALTHCHKLOG defaults to FULLTHRESHOLD(80) whereas OPERLOG explicitly specifies FULLTHRESHOLD(0). I don't know how much that matters when there is no automatic altering going on in either case.

STRUCTURE NAME(OPERLOG)               /* OPERATIONS LOG      */
          SIZE(8M)                    /*                     */
          PREFLIST(CF01,CF02)
          FULLTHRESHOLD(0)

STRUCTURE NAME(HZS_HEALTHCHKLOG)    /* HEALTH CHECKER        */
          SIZE(9M)
          INITSIZE(9M)
          PREFLIST(CF01,CF02)

Thanks and Happy New Year!

--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/


--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to