Comments interspersed. <Original> -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Gilmore Sent: Monday, September 09, 2013 4:17 PM To: [email protected] Subject: Re: SORT? need.
Peter, To me 'experimental' is never pejorative. An experiment queries the environment to make date-driven decisions. </Original> Thank you. I do assume you also meant to say "data-driven". <Original> We do, however, disagree about the proper treatment of the INTRDR or, indeed, any other tool. If you do not want some job submitted via the INTRDR to update a file you protect that file and you do not interdict the use of the INTRDR. Another way to make the same point is to recall that the INTRDR is not a new facility. It is in fact a very old one, and a scheduling product or security scheme that is unaware of it is 1) poorly designed and 2) should not be used. In my now long experience shops that use scheduling products inflexibly, while they may meet their notional workload-control goals, in fact lose 1) control of what is really going on and 2) relevance. Decision-support and extrernal-reporting requirements are moved outside its purview. It is left with tight control over routine applications that are of interest only when they falter. There are no bureaucratic, 'management' solutions to technical problems that do not involve unacceptable abnegation. </Original> I was not *advocating* such INTRDR restrictions, nor the more-severe INTRDR interdiction to which you refer. Indeed, I frequently find myself in agreement with your positions on this and similar subjects. I was merely trying to report that in my experience such INTRDR restrictions are present in some places, and by implication that anyone wishing to use an INTRDR solution to a problem like the OP's needs to try to discover (if they can) whether and what kind of INTRDR restrictions are present in their operating environment, lest "surprises" occur in production. Many posters here like myself are, though technically savvy, neither sysprogs nor security admins, and thus have no control whatsoever over (and indeed, in some unfortunate environments, no way of legitimately querying) whether or not there are any locally defined restrictions that do or do not meet some particular definition of a "properly" configured security environment. We just have to live with whatever has been decreed by the powers that be. Peter -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
