On Monday, May 18, 2020, 05:49:43 PM PDT, Seymour J Metz <sme...@gmu.edu> wrote: >> Messages in z/OS do not wrap and are not formatted. > In the nextt paragraph you say the opposite.
It's not the opposite. Consol address space builds a line that is destination dependent. Compare the same message in syslog versus joblog. If that line will not fit in the space available for that destination, then consol will split the line. Destinations such as TSO CONSOLE shouldn't split lines since the buffer should be large enough for the largest line. >> Multi-line messages are multiple MLWTO's > No, it's generally what its name suggests, a single WTO that specifies > multiple lines of text, > although there is a CONNECT parameter that allows > you to add a line to an outstanding WTO. WTO's don't add a line to an outstanding WTO. Each message in a WTO is presented to the SSI as a separate message. The OP wanted to know about multi-line message and how they are formatted. The op needs to understand that messages are not formatted in any way by WTO or CONSOL. In fact, each message is not validated and may contain invalid hex values. All formatting is performed prior to issuing the WTO. The op should also understand that the line wrap they see in syslog occurs because the line does not fit in the destination. The number added to the line identifies a group of messages (mlwto) because they may be interspersed with other messages. There are cases where messages have occurred days after the first line in an MLWTO. >> z/OS messages and codes. > There is a z/OS MVS System Messages Volume 1 (ABA - AOM) that describes > message formats. For the OP, this section may answer other questions. Jon. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
