OPS/MVS

 View Only
  • 1.  Wildcard message rules with MLWTO

    Posted Mar 29, 2023 06:29 AM
    Edited by Steve Ives Mar 29, 2023 09:07 AM

    So according the manual regarding the WLWTO keyword on a message rule "Wildcarding is not allowed if utilizing this keyword.".

    Now I'm trying to forward all MQ error messages to another LPAR (so they get forwarded to Splunk) and have coded:

    )MSG CSQX*E MLWTO
    )PROC
    temp = OPSSEND("<target_lpar>","C")

    Now the rule is definitely firing for messages that are MLWTOs so I'm wondering how that clause "Wildcarding is not allowed if utilizing this keyword." is being applied - is the keyword ignored, so that every line of the MLWTO is being treated as a separate message or are the non- MLWTO WTO that match thinds mask being ignored (which doesn't make much sense).

    I only started to look at this as it appears some of my CSQX***E messages aren't being forwarded to the other system.

    Yes - I could set up a test but thought I'd get a discussion going. :-)



  • 2.  RE: Wildcard message rules with MLWTO

    Posted Mar 29, 2023 08:53 AM
    Edited by Steve Ives Mar 29, 2023 09:03 AM

    Well that was interesting. I set up  a test rule on our test LPAR:

    )MSG SIMLWT* MLWTO 

    and Ops/MVS wouldn't even let me enable it, saying that "No valid rule header found in rule MSGUKI.SITEST2 (MLWTO spec excludes wildcards)" (which is what the manual says). But I'd already created a wildcard rule with a MLWTO, except the MSGID spec was CSQX*E - the '*' wasn't at the end.

    So I changed this test rule to:

    )MSG SIMLWT*X MLWTO

    and then I could enable it. 

    Further testing using "Address WTO" with a stem var to create an MLWTO reveals that the rule does fire once per MLWOR, with the MSG.TEXT.n variables populated as expected. 

    So I'm not quite sure what restriction there is on wildcarding MLWTO message rules. 




  • 3.  RE: Wildcard message rules with MLWTO

    Posted Mar 30, 2023 01:51 AM

    I can confirm that wildcards anywhere but as last char will work in a MLWTO msg rule.

    We have several JES2 rules that read )MSG *HASP... MLWTO that works just fine and have so for years



    ------------------------------
    Automated Operations
    Atos
    Netherlands
    ------------------------------



  • 4.  RE: Wildcard message rules with MLWTO

    Posted Mar 30, 2023 03:33 AM

    Yep - the behaviour with wildcarded MLWTOs (if the message spec doesn't end in an * so that they enable) seems to be exactly as expected.  

    OPSSEND though doesn't work with MLWTOs, only sending the last line - I've raised a case with CA support for this. I'll run a test today that uses ADDRESS WTO to forward the WTO to another system, using the MSG.TEXT.n variables, although I think I'm going to lose the original system name so will have to add that into the message somewhere.