[OT] Geezer Error-Message - cobol

LOL I think I resemble that code. I've written it and I've dropped
decks but only my own.

PatH...too old to be a geezer


docdwarf@panix.com wrote:
> My current client manages source code with Librarian; a program starts out
> in NODE1.NODE2.DEV.SOURCE(MEMBER), compiled to
> NODE1.NODE2.DEV.LOAD(MEMBER) gets a user sign-off, gets copied from there
> to NODE2.NODE3.XFER.SOURCE(MEMBER) and then Ops runs a job to copy it to
> NODE1.NODE2.PRD.SOURCE(MEMBER) and another job to compile it to
> NODE1.NODE2.PRD.LOAD(MEMBER)... and from there it is run as a Prod job.
>
> Something needed to be changed recently and I notified Ops that it was
> ready to roll... and just for laughs checked the SYSOUT to see what was
> happening.
>
> (I was given browse-authorisation to the Ops output jobs because Ops
> realised it would be a Very Good Thing if I were allowed to look at Prod
> runs so I could see what blew up from my own seat rather than having one
> of them wander over and log on or having me wander over to where they
> live.)
>
> The proc they ran to copy the job from XFER to PRD executed a program
> named ESCLIBR... and the messages a true glimpse Into The Past. Never
> mind that there was 'THE LIBRARIAN SOURCE MANAGEMENT SYSTEM IS LEASED FROM
> APPLIED DATA RESEARCH, INC.' and the Customer Support Information included
> a Telex number - browsing the load module revealed a 'short rec' ending
> with X'84110F' (19 Apr 1984) - but the last message in the job gave me
> cause to chuckle:
>
> 'WARNING: FINAL INPUT STATEMENT WAS NOT -END. MAKE SURE THAT LAST PART OF
> DECK WAS NOT DROPPED.'
>
> DD
>