Barbara, The IP configuration changes and RACF changes to meet operational environments were the obvious ones to me. Agreed, I would go that route unless you could find a complete inventory of all the load modules that shipped with ADCD..see if the module in error shipped worth 1.13 ...compare 1.10 or I have 1.12 I could compare also for you, if you like
Scott ford www.identityforge.com Tell me and I'll forget; show me and I may remember; involve me and I'll understand. - Chinese Proverb On Dec 31, 2012, at 1:14 PM, ibmmain <nitz-...@gmx.net> wrote: >> I use ADCD all time we had 1.10 up through 1.13 on z/Pdt. Ours wasn't >> customized per se,we did it ourselves, actually I had to do it. Did you >> system come pre-configured ? It sounds like it did. > > As far as I can tell, the 1.13 system was not changed other than for IP > setup. Any customization was done by me. I 'inherited' the 1.10 system, and > one of my tasks was cleaning up RACF. Applying the same cleanup to the 1.13 > system broke ftp due to that obsolete IMS usermod. > > Depending on your definition of 'customization', that 1.13 system was > 'customized' by ADCD development. I don't really consider it customization, > though. The provider 'customized' the IP setup to fit their firewall (we are > running on a z10). > > I'll see what a 1.13 ADCD system on z/PDT looks like in January. My guess is > that that will really be 'out of the box' as delivered. I don't expect the > RACF database to be much different from what we got, though. And I plan on > finding out which definition broke ftp. > > Barbara > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
