-------------------------------------<snip>------------------------------------
Management may know something you don't. Management may know that very
few of their staff knows BAL. And if a program blows up in the middle of
the night (or any other time) no one may be available to debug it. I
have seen this happen myself as I was the one that was called in. For
support. I lobbied after that for no more assembler and was successful
at getting this approved.
--------------------------------------<unsnip>----------------------------------
Been in a similar situation myself. Made appropriate corrections and
notified the progrmmer what the problem was and how to fix it. When he
ignored that advice and the problem recurred, he got called "on the
carpet". After several more occurences, requiring me to come in and
affect the fix, he was promoted to the sidewalk and I became responsible
for the program. End of problem. Aft4er that, management would accept
any BAL program, providing that I wrote it and was willing to provide
assistance if it failed.
Track records mean a lot! :-)
Rick
----------------------------------------------------------------------
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
