Scott,
 
We must agree to disagree.  
 
What you judge prudential seems to me to be bureaucratic complication that 
provides the inexperienced with the illusion of security without its substance; 
and you view my suggestion as irresponsible.
 
I imagine that this is only one of our visceral differences.   Like CC I was 
reluctant to post in this thread, which was and has remained a discussion of a 
poorly understood issue among mostly uninformed people.  I did so only to make 
it clear that wrong-AC problems are easily remedied using the Binder.
 
These things said, I have no sympathy with the generic notion that arcane 
skills should be kept within the priesthood; and that I suspect is where we 
differ crucially.

John Gilmore Ashland, MA 01721-1817 USA


 
> Date: Tue, 12 Apr 2011 10:39:17 -0400
> From: [email protected]
> Subject: Re: AC (authorization code) change
> To: [email protected]
> 
> John,
> 
> I found your suggestion that one should just re-link the module in question
> rather irresponsible. It is not clear who you were replying to, so it would
> appear you are replying to the original poster. Suggesting that an apparent
> novice re-link a module is fraught with hazard, such actions have caused
> many problems in the past.
> 
> I agree with Dave Gibney, look to the status of the module as produced by
> SMPE, if AC=0 in the target library then don't mess with it unless the
> module owner indicates that it is in error. One should not attempt to fix
> something that is not broken.
> 
> Scott
> 
> On Tue, Apr 12, 2011 at 9:26 AM, Scott Rowe <[email protected]> wrote:
> 
> > What seems to have been missed in this whole discussion is that the module
> > in question isn't even the job step task program, it does not need AC=1, and
> > should not have the it's attributes changed.
> >
> >
> > On Tue, Apr 12, 2011 at 8:58 AM, john gilmore <[email protected]>wrote:
> >
> >> Peter Relson has had his say, and I am unconvinced by his flag waving:
> >> irresponsible modifications of IBM or ISV modules have, I suppose, occurred
> >> even in this OCO era; but they are about as likely as the impact craters of
> >> that purple call falling from the skies.
> >>
> >> John Gilmore Ashland, MA 01721-1817 USA
> >>
> >>
> >> ----------------------------------------------------------------------
> >> 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
> >>
> >
> >
> 
> CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains
> confidential and privileged information intended only for the addressee.
> If you are not the intended recipient, please be advised that you have
> received this material in error and that any forwarding, copying, printing,
> distribution, use or disclosure of the material is strictly prohibited.
> If you have received this material in error, please (i) do not read it,
> (ii) reply to the sender that you received the message in error, and
> (iii) erase or destroy the material. Emails are not secure and can be
> intercepted, amended, lost or destroyed, or contain viruses. You are deemed
> to have accepted these risks if you communicate with us by email. Thank you.
> 
> ----------------------------------------------------------------------
> 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
                                          
----------------------------------------------------------------------
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

Reply via email to