>> By parallel run, I mean letting the current, split-up behaviour remain the >> canonical way/source,
> This is referred to as multi-tasking which has nothing to do with messages. > A program needing multi-tasking must be designed using multi-tasking > philosophy. Yes, I understand multi-tasking. There wasn't any doubt or question there. I was imagining a way to "write to" both targets, and having a provision to switch over. If it's just a presentation issue, it's safe to then change the IE something to wide col count? It won't affect what automation tools see? Sent with Proton Mail secure email. On Thursday, July 24th, 2025 at 22:02, Jon Perryman <[email protected]> wrote: > On Thu, 24 Jul 2025 02:25:02 +0000, kekronbekron [email protected] > wrote: > > > This'll allow automation tools to switch over piece by piece (if & where > > needed), > > > No automation product (Netiview, AutoOperator, Ops z/OS, ...) will ever > switch to OPERLOG because it's too slow, causes problems and doesn't provide > any benefit. > > > and then default to the wide records format. > > > There is no "wide record format" and continuations are a presentation issue. > Messages are intact prior to being presented to the user. TN3270 allows you > to set your screen size and default to 80 characters wide. If the message is > presented to an 80-character wide console, then wrapping will occur but if > 200 characters wide then it will never wrap (I believe primary message max is > 128, secondaries 80 and specifying all possible message options will max out > around 40). > > Messages presented to TSO CONSOLE command will not have a continuation. > > Messages presented to SYSLOG will have a continuation around 132 characters. > No one has complained enough to cause IBM to increase this size. > > Automation products receive events from several sources and are capable of > handling much larger than system messages. In fact, system messages include a > lot more information than presented to users. Consult your automation > documentation for the information available with a message event. > > OPERLOG is like the automation products in that it retains detailed records > of each message instead of presenting the message. > > Zowe uses OPERLOG and decides how best to present each message. > > > By parallel run, I mean letting the current, split-up behaviour remain the > > canonical way/source, > > > This is referred to as multi-tasking which has nothing to do with messages. A > program needing multi-tasking must be designed using multi-tasking philosophy. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
