> Messages in z/OS do not wrap and are not formatted. In the nextt paragraph you say the opposite.
> 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. > z/OS messages and codes. The last time that there was a messages and codes manual was in OS/360; z/OS MVS System Codes is a separate manual. There is a z/OS MVS System Messages Volume 1 (ABA - AOM) that describes message formats and has a Directory of messages by prefix and component, but for explanations of specific message you must go to the appropriate volume. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon Perryman [jperr...@pacbell.net] Sent: Monday, May 18, 2020 6:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on wrapped JESMSGLG messages Messages in z/OS do not wrap and are not formatted. Messages are written using either WTO (single message) or MLWTO (multiple lines of a message). WTO allows you to write a single message which I think has a max length of somewhere around 128 bytes. Multi-line messages are multiple MLWTO's (one for each line) using the same token to relate the messages together (the number you mentioned from syslog). For syslog, joblog and programmer log message information documentation, look at the first volume of the z/OS messages and codes. As for Cobol display upon console, you can try displaying a 200 byte message to see if it's using multiple WTO's or multiple MLWTO's. In syslog, you may notice an actual line wrap but it will be on the next line. This occurs when the message will not fit in the space available. Jon. On Thursday, May 14, 2020, 06:57:01 AM PDT, Donald Johnson Jr. <000002ee771a0785-dmarc-requ...@listserv.ua.edu> wrote: I have a peculiar question and hope the answer is easily found in this group. Looking at these highlighted values 08.17.38 JOB57837 DJMU2DF:DB01900I - MUF DJMU2DF,99,NO 08.17.38 JOB57837 DJMU2DF:DB01909E - * - ASTERISK 682 682 POINTS NEAR ERROR 08.05.17 JOB57048 IEC161I 056-084,CICSABCD,$$$$$$@ $$$$$$@,DFHLCD,,, 571 571 IEC161I OMY.CICS.DFHLCD,OMY.CICS.DFHLCD.DATA, 571 IEC161I ICF.ABCD.USERCAT I know that the number is a cross-reference for continued lines in Syslog and the user joblog, and I have never thought twice about it before. However, I have someone asking about this, and I realized that I don't really know how it works. My questions are: 1. What drives this process? I assume it is part of JES message handling 2. Is the line length before wrapping a message held in a parameter somewhere? 3. What causes some messages to use the #, and others to just wrap. For example, if I write a COBOL program with DISPLAY...UPON CONSOLE, the lines just wrap in the Syslog, with no ### identifier. Other jobs or STCs write messages like the above, with the continuation number. 4. Is there some doc I can point to for my colleague to understand this? We all know what it is, and most of us probably don't care how it works, but I figure that someone knows what this is called, how it is configured, and how it works for different messages. Thanks all! Don Don Johnson Broadcom donald.johnso...@broadcom.com | broadcom.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
