Paul G wrote <snip> Or one might call it invalid. </snip> FWIW, a message ID is good practice but (depending on the target of the message) is not required.
Paul G wrote <snip> Message processing should enforce the documented conventions in order to preclude such downstream surprises. </snip> You would generally not enforce a "convention"; you might enforce a "rule". Not every application supports every possible thing. For example, while you can create a PDS member with pretty much any character using STOW, you might not be able to use that name within various system commands or in an application such as ISPF. One would hope that commands and applications support all the "normal" things. Colin P wrote <snip> First 3 letters = allocated to the product. Starting with A to H is for IBM products ... Last message type I,W,E,A,T </snip> That would be "A to I" (and SYS) for IBM. And not limited to "messages". The message types for console messages are very well documented; it's unfortunate that the conventions for applications are different (so we have "W" for wait state on one side, "W" for warning on the other). Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
