Some MVS message ids are heavill]y overloaded. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
________________________________________ From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf of Jon Perryman <jperr...@pacbell.net> Sent: Saturday, August 30, 2025 12:05 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Subject: Re: Is HLASM efficient WAS: Telum and SpyreWAS: Vector instruction performance External Message: Use Caution On Sat, 30 Aug 2025 11:39:11 +0100, Martin Ward <mar...@gkc.org.uk> wrote: >That is not an SNMP message. It looks more like a human-readable >log entry. SNMP is an internet protocol. As such it requires a client to receive those messages and decide how it wants to present / format the information. I'm not saying this was the best formatting of SNMP data but yes, it is an SNMP message. I chose this message because it conveyed the complications of Unix messages. Unlike MVS messages, message ids go a long ways in dealing with message and mixed case data. > Why would you need regular expressions to parse this message As I said before, MVS automation doesn't need regexp. It has message ids that make simple *abc* pattern matching sufficient. MVS has message IDs with well defined messages. Look at any product messages manual. Look at messages in Quikref. Automation events on other platforms are far less predictable. It's important to realize when I say automation events, I'm talking about multiple sources (e.g. syslog, CICS, IMS, MQ, DB2 and more). This is true for other platforms. In MVS, we tend to receive events from the source but other platforms often use messages from a program. If you were given a random message that is rarely documented properly, could you adequately select an event using only * and + as your wildcard characters? Would you be confident that you are dealing with the expected event? I've only seen a couple non-MVS automation products but they used some form of regexp. > when every field has a specified length? MVS automation gives you direct access to fields. With non-MVS automation potentially dealing with thousands of products, do you think they usually deal with fields or do you think they are dealing with a single message.
