On Fri, Mar 4, 2011 at 8:22 AM, Chris Mason <[email protected]> wrote:
> Jim > > There are too many points of contact between what you describe and what > APAR "PQ92115: RSH CLIENT FAILS WHEN RESTRICTLOWPORTS IS CODED IN > TCPCONFIG" describes for it to be dismissed as "similar but not exactly the > same problem". I'm almost certain it *is* the same problem but there is a > mystery over the AC value. > > The authors of the APAR text state that going from V1R4 to V1R5 the > linkage > edit of the RSH client module changed from AC(1) to AC(0) but you are > reporting that in V1R11, it is back to AC(1) - undergarments are not > smooth! > > - > > - > > Chris Mason > > Chris, thanks for your detailed reply as usual. There is nothing wrong with the authorization of the program AFAIKS and we don't specify any INADDR* parameters. Given what you said about UNRESTRICTLOWPORTS, I'm going with that resolution. Thanks again Jim McAlpine ---------------------------------------------------------------------- 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
