In <listserv%[email protected]>, on 11/20/2010
at 12:09 PM, Paul Gilmartin <[email protected]> said:
>Properly; I understand an excess of implementation detail is an
>obstacle to fulfillment of a requirement: "While we otherwise favor
>the requirement, your specific proposed solution is unworkable; ergo,
>rejected!"
ObCatch-22 The flip side is when you take out the suggested
implementation and they claim that the problem description is too
vague. Or this isn't a TSO issue, it's a JES2 issue. Some of the old
timers may recall being jerked around until finally the JES2, JES3 and
TSO projects each submitted essentially the same requirement, each
referencing the requirements from the other projects.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
