At one job I was on the standards committee and ended up writing quite a few COBOL/JOB/JCL standards. One of the first was that no COBOL (no other languages were permitted) could not have any WTORS. Some programmers objected to it and we got in a nice discussion about operators priorities and I just happened to have a days syslog listing handy and showed everybody the amount of traffic and they really didn’t have a clue that ended that argument. Another argument I had with the committee was of the “block contains” clause. The conversation went something like this do you really want to have to get a programmer involved when an external company makes a change to one of their files (we had literally 100’s of companies sending us files every day/night. and they seemed to change block sizes on the fly. When shown how many external files were created every night they rapidly backed down on their argument. Of course the biggest fight I had was was when a programmer wanted to change the standards because he wanted to code a program in assembler. I turned the request around and asked the manager how many of their programmers knew assembler and he answered only one. I said then who is going to support the programmer when that one is sick. He got the message. Essentially myself and him were the only assembler coders in the company. I told him I wasn’t going to help them out as it was out of my comfort zone and responsibility. The company was a company that was responsible for clearing trades and we were on serious deadlines.
Ed > On Jun 3, 2016, at 11:24 PM, Edward Gould <[email protected]> wrote: > >> On Jun 2, 2016, at 1:53 PM, Zahir Hemini <[email protected]> wrote: >> >>> We had jobs with an outstanding WTOR that would last for 2 or so weeks. >>> Never an issue. >>> >>> Ed >> >> Did you allow them to stack up on the console? or did you K E,? them? and if >> so how did you keep track of which reply numbers were outstanding hidden off >> the console? > > The op k e,1’d them. They did a d r,l to get the message number. I wasn’t > watching the console that closely but the only time a op had to reply to the > message was to bring down the job for a planned IPL. > Sometimes (if the system stayed up for that long) the jobs would run for 2-3 > weeks and we had multiple jobs running concurrently and there would be 4 or > more wtor’s outstanding. Since the jobs were submitted by production control > they did most of the care and feeding. BTW these were really multitasking > jobs I looked at a dump for one of the bugs and found 31 tcb’s. I was > flabbergasted that they did so many attach’s. > > Ed > >> >> ---------------------------------------------------------------------- >> 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
