Re: what was the single mgmt decision made in mid-1990s. period

You do have some points there Albert. But the conversion is a good time
to review the current method.
For example I was looking at some code in a backup program that had to be
interrupted and left a lot of crud. I was seeing code like this:
C Do QueCnt Q
C Move JobQues(Q) QueNam 10
C MoveL JobQues(Q) QueLib 10
and I was thinking how differently I would do that. Like a data structure
array or some such animal. But the real solution would have been to drop
the array altogether and use a file (not in QTEMP). Why? Well, this
process did this:
For all job queues in a group of library, attempt to hold them.
If you can hold that job queue then store it in an array.
Save the libraries.
For all entries in the array release the job queue.

If you interrupt that process then how do you differentiate between the
job queues that are normally held, and those that were held because of the
backup? Remember, job cancelled, array gone. 40+ pages of job logs just
listing the HLDJOBQ's.
Well, one answer is to have the programmer who wrote this to pour through
the joblog and release them all and make a suggestion to him to consider
restart steps.

But, Albert, getting back on subject, one should not always be target
blinded on a move versus how you would have done it versus the process as
a whole. And, yes, I would never write a new line of code using move.

Rob Berendt