I have a message rule that fired but still shows a fire count (in the display) of 0. Has this happened to anyone else and if so what is the cause? This is the only rule that shows this.
RuleName Status AE TYP Log Last Fired Time Next Fire Time CountVPS9501R ENABLED Y MSG Y 2018/10/24 12:30:55 NONE NONE 0
Message from the log:
12:30:55 VPS9501R P062F EDRAINED P611909P(J0066396) TCPIP ERR=CONNECTION
12:30:55 TIMED OUT
Additional Columns just to show that the rule did indeed fire on the message:
PHNX ---------------- Display All Columns for MSG Event--------------------
| Job Name | Time | Date | ASID | MSF ID | MSF DEST | OJobname |
| VPS | 12:30:55 | 24OCT2018 | 0176 | PHNX | PHNX | VPS |
| MessageNum | Elapsed | SysID | AF | Flags | Disp | OPSF | Conid |
| 0000071335 | 0000062 | PH | 0A | 805000 | SUP | 2408 | M0000 |
| Release | Jobnm | Jobid | WTO ID | Token | Xconid |
| 12.03.00 | STC40015 | S40015 | 00DF2504 | | M00000000 |
| ConsName | IMSID | IMSType| CLS | RouteDesc | TimeStmp | SYSNAME |
| NONE | NONE | NON | NON | 0020 0000 | 12.30.55 | PHNX |
| Length | Special | DSP name | User | UserX | TermName |
| 067 | | NONE | NONE | 0000000000000000 | NONE |
| User ID | Event | Color | Autotokn | Hex Autotokn | Exit |
| MVSUSER | MSG | NONE | | 0000000000000000 | MVS |
| Ruleset.Rulename | Count | Ruleset.Rulename1 | Ruleset.Rulename2 |
| TECHSERV.SUPPRALL | 02 | TECHSERV.VPS9501R | TECHSERV.SUPPRALL |
| Ruleset.Rulename3 | Ruleset.Rulename4 | Ruleset.Rulename5 | Address |
| NONE.NONE | NONE.NONE | NONE.NONE | 02B8AF0 |
| Message ID | Event ID | Route Codes<-->64 65<-->96 97<->128 DESC |
| VPS9501R | VPS9501R | 00200000 00000000 00000000 00000000 0000 |
| ----+----1----+----2----+----3----+----4----+----5----+----6----+----7 |
| VPS9501R P062F EDRAINED P611909P(J0066396) TCPIP ERR=CONNECTION |
I checked our end, but don't see such instances. You'd probably better of reporting this to CA support.
Marcel van Ek
Regards Hennie Hermans (CA Technologies)
Please open a case at the CA support website..
We would like to see what has happened and research this problem.. We've no reported problem of such kind before...
Principal Support Engineer
Thanks. I figured that would be the response. I just wanted to make sure I wasn't doing something wrong. I just opened a ticket.
Just provide the answer to the original problem, the no fire count increase..
MLWTO rules only fire when the ENDLINE is detected. It appears from the OPSLOG no ENDLINE ever occurred. The message ID VPS9501R can be generated by various scenarios. During recreation of the scenario client was attempting to automate, the message doesnt create an ENDLINE.
Client will check with the vendor to fix.
Because there isnt an ENDLINE, the MLWTO rule request will be timed out and the storage reused. So nothing is left behind.
Hennie Hermans (CA Technologies)