The longer it takes to figure out the problem, the more likely it will be 
bloody obvious once it is found :(

Dave Gibney
Information Technology Services
Washington State University

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Gross, Randall [PRI-1PP]
> Sent: Monday, March 18, 2013 11:48 AM
> To: [email protected]
> Subject: Re: Query for Destination z article -- mainframes back to the future
> 
> We used to call this the "any idiot" theory of debugging:
> 
> After working a trans-finite amount of time trying to debug a program,
> any idiot will walk up and immediately point out your error.
> 
> 
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On
> Behalf Of Richards, Robert B.
> Sent: Monday, March 18, 2013 10:19 AM
> To: [email protected]
> Subject: Re: Query for Destination z article -- mainframes back to the
> future
> 
> I have to echo your last line from personal experience:
> 
> If you have looked at a bug for 30 or more minutes, get that second set
> of eyes to look at it pronto.
> 
> Chances are they will spot it in under 30 seconds!  :-)
> 
> Bob
> 
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On
> Behalf Of Elardus Engelbrecht
> Sent: Monday, March 18, 2013 9:21 AM
> To: [email protected]
> Subject: Re: Query for Destination z article -- mainframes back to the
> future
> 
> Shmuel Metz (Seymour J.) wrote:
> > Have a plan B.
> 
> And C and D, etc... ;-D
> 
> > Document first, then keep your documentation up to date.
> 
> And have someone else review it.
> 
> And document all and every exits. (source, logic flow and installation
> methods)
> 
> > Don't update the running system.
> 
> Some people did that - at their own risk.
> 
> And P L E A S E Don't INIT a live IPL volser!
> 
> > Use vendor-provided mappings rather than rolling your own.
> 
> Good suggestion, that is, if supplied mapping is available in the first
> place. Think OCO.
> 
> (It took me a long time to obtain SMF mappings from IBM for a certain
> product for which I need to extract accounting info for usage
> analysis... So I ended used both version - vendor and my own.)
> 
> >A few coding techniques for newbies to learn:
> > The use of UNPK and TR for converting to hexadecimal.
> 
> And do that in RENT and REUS modes too. ;-)
> 
> I wish to add something too: If you're having trouble debugging
> something, an extra pair(s) of eyes is a welcome investment.
> 
> 
> ----------------------------------------------------------------------
> 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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to