View Single Post
Old 04-20-2018, 03:24 PM   #295
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Quote:
Originally Posted by Ralph Sir Edward View Post
This will be meaningless to any non-mainframe programmer, but. . .
This is not unique to the mainframe world. I see similar instances all over.

What was the host language for the program? What are you using as a code repository?

Backing out the change in the repository should not result in a land mine. A backed out change shouldn't be presented to the compiler if someone does another build.

I assume you properly commented the commit statement that specified why you backed out the change...

What I get from this talke of woe is that the user couldn't be bothered to test, and the QA analyst is an idiot. Again, not at all unique to mainframes.
______
Dennis
DMcCunney is offline   Reply With Quote