Sorry, I was just curious about whether people thought having a message id on each line of the message would be useful. Who knows, someday I may have such a need and I'd like to have a good idea what would be useful for others. I am not suggesting that IBM or other vendor immediately start recoding their MLWTO messages! But perhaps it should become an "industry recommendation"? I'm on some steriods for a few days, and can't sleep, am "nervous" so I'm just blathering on. Sorry if it's a disruption. My bad.
-- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:ibm-m...@bama.ua.edu] On Behalf Of Vernooij, CP - SPLXM > Sent: Thursday, November 25, 2010 6:21 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Philosophy question: repeat message ID on each > line of an MLWTO? > > "McKown, John" <john.mck...@healthmarkets.com> wrote in message > news:<a6b9336cdb62bb46b9f8708e686a7ea005d5e05...@nrhmms8p02.ui > cnrh.dom>. > .. > > 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 > > What is your question? To change the message text of each and every > message in the system? I think we will end up in the same > discussion as > the 7 character TSO Userid discussion a few weeks ago. Very > interesing, > lots of pros and cons, but you can be sure of one thing: nothing will > change. > > Why can't you use operlog in a basic sysplex? Use a dasd-only > logstream. > On first thought I can't think of any reason why this is not possible. > > Kees. > ******************************************************** > For information, services and offers, please visit our web > site: http://www.klm.com. This e-mail and any attachment may > contain confidential and privileged material intended for the > addressee only. If you are not the addressee, you are > notified that no part of the e-mail or any attachment may be > disclosed, copied or distributed, and that any other action > related to this e-mail or attachment is strictly prohibited, > and may be unlawful. If you have received this e-mail by > error, please notify the sender immediately by return e-mail, > and delete this message. > > Koninklijke Luchtvaart Maatschappij NV (KLM), its > subsidiaries and/or its employees shall not be liable for the > incorrect or incomplete transmission of this e-mail or any > attachments, nor responsible for any delay in receipt. > Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM > Royal Dutch Airlines) is registered in Amstelveen, The > Netherlands, with registered number 33014286 > ******************************************************** > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
