John, A lot of the messages that use different message ids are setup to display the various messages conditionally and construct the WTO parameter list dynamically.
Philosophically, I think that the approach that I would take would be that if a multi-line message incorporates all lines unconditionally, then use the same message id on all lines, and if the multi-line message incorporates some lines conditionally, then use different message ids on different lines, as illustrated below -- ABC0001I Unconditional line 1 ABC0001I Unconditional line 2 ABC0001I Unconditional line 3 ABC0001I Unconditional line 4 ABC0011I Unconditional line 11 ABC0012I Unconditional line 12 ABC0013I Conditional line 13 ABC0014I Conditional line 14 ABC0015I Unconditional line 15 In the 1st example, above, message ids ABC0002I, ABC0003I, and ABC0004I are to be reserved. This provides that the message ids can be appropriated in the case that ABC0002I or ABC0003I is changed to conditional incorporation at some future time. There is a second argument to be made in favor of using different message ids where the message lines contain variable data, which may require a detailed explanation in a messages guide. John P. Baker Chief Software Architect HFD Technologies -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of McKown, John Sent: Thursday, November 25, 2010 7:08 AM To: [email protected] Subject: Philosophy question: repeat message ID on each line of an MLWTO? I have no life. That's why I'm working from home on the major holiday here in the U.S. But I have noticed that some multiple line WTO messages repeat the message id at the start of every line of the message, such as DFHSM's ARC0833I message, whereas other, such as IEC205I, do not have any message id on subsequent lines. I've even noticed that VTAM puts a __different__ message number at the front of each line of the message, depending on the content of that particular line. I just never noticed this before. I think I prefer eithe DFHSM or VTAM's method. It makes it easier to do an edit EXCLUDE and FIND to find all of the message when I'm looking at SYSLOG either via SE on *MASTER* or our disk resident holding area. We don't use OPERLOG because we are a __basic__ sysplex. John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
