I am troubled. I didn't pay much attention to the beginning of the thread, but I would spend more time wondering how a vendor supplied module that isn't AC(1) when it should be (if indeed it should be) than on how to relink it AC(1). If it should have come AC(1) and is now not, how do I know it's even remotely related to the correct vendor module?
Dave Gibney Information Technology Services Washington State University > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Paul Gilmartin > Sent: Monday, April 11, 2011 4:40 PM > To: [email protected] > Subject: Re: AC (authorization code) change > > On Mon, 11 Apr 2011 20:49:44 +0000, john gilmore wrote: > > >Why do you think you cannot relink these modules with AC(1)? The binder > accepts its outputs, load modules or program objects, as inputs. The > operation is trivial. > > > ... Unless it was previously linked with the EDIT=NO option. > > -- gil > > ---------------------------------------------------------------------- > 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
