I would love some software, preferable hosted on z/OS, which could do a "context sensitive" search of the syslog/operlog. Along with a __good__ repository. There may be such a thing already. I would know because we are a dying shop.
-- 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-MAIN@bama.ua.edu] On Behalf Of Skip Robinson > Sent: Friday, May 04, 2012 10:57 AM > To: IBM-MAIN@bama.ua.edu > Subject: Re: Comments on DFSMS verbose messages? > > I was in the ESP and joined the follow-on conversations about the > increased message traffic. The concern was not about a weightier > syslog/operlog, but about the even denser weed patch that one > has to wade > through in syslog/operlog in order to troubleshoot some other totally > unrelated problem. How many times do 'we' have to slog > through the same > explanation of essentially the mundane error? The verbose > explanation does > not tell a sysprog anything more useful than the ancient and > venerable > message itself: error code, return code, data set name, > volume. Why would > a sysprog need anything more than that? > > I like the solution. The installation can turn verbose on or > off globally. > The new 'filter' allows us to direct long explanations to just the > programmer--my preference--or to syslog/operlog. Why complain > about 'too > much control'? > > . > . > JO.Skip Robinson > SCE Infrastructure Technology Services > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > jo.skip.robin...@sce.com > > > > From: Edward Jaffe <edja...@phoenixsoftware.com> > To: IBM-MAIN@bama.ua.edu > Date: 05/04/2012 08:43 AM > Subject: Re: Comments on DFSMS verbose messages? > Sent by: IBM Mainframe Discussion List <IBM-MAIN@bama.ua.edu> > > > > On 5/3/2012 7:15 PM, Mark Zelden wrote: > > > > If the new MPFLSTxx option has it disabled by default or > enables the > verbose messages, what > > purpose does the OCE_ABEND_DESCRIP=YES serve in DEVSUPxx? > What if you > want the > > original behavior? I ask, because I like it. > > I also like the current behavior. Job logs come and go, but > the system log > is > forever. > > ESP for z/OS 1.13 began in late spring 2011. Some of the participants > probably > overreacted. People don't like change. > > The release went GA in September 2011. Many shops have > already migrated > and many > more are doing so. There was no 'blood in the streets'. I > can't recall > hearing > or reading any negative mention of this new functionality > until Kevin's > post. > > When I first read the ICN (Interface Change Notification) > about this new > 'verbose' message support, I thought "This is much ado about nothing." > > -- > Edward E Jaffe > Phoenix Software International, Inc > 831 Parkview Drive North > El Segundo, CA 90245 > 310-338-0400 x318 > edja...@phoenixsoftware.com > http://www.phoenixsoftware.com/ > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
