Duplicate message was not something I did. It just occurred to me that there was a wave of Micro$oft updates. Is it possible that those updates included a requirement for greater than 40 bit cipher keys? Most of our workstations just let the updates land, install and reboot.
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Gibney, Dave > Sent: Monday, July 14, 2008 12:27 PM > To: [email protected] > Subject: Re: TN3270 SSL problem > > I have a problem I don't yet understand. I have 4 LPARS at z/OS 1.7. > I'm preparing to move to 1.9 and hopefully have only a short time (if > any) running 1.7 out of support. > I'm moving on a couple fronts in 1.7: > I am separating the TN3270 servers from the TCPIP address space. > I am moving to multiple TCPIP address spaces to comply with > institutional security direction. > I have the 1.7 system at RSU0803 and all PSP/HIPER at that time. > I have reviewed and modified the Serverpac RACFDRV job. It ran > without visible problems in the install sandbox and the system maint > sandbox. > > Last week I ran it on the Development Lpar and noticed no problems. > BUT, this weekend we Ipl'd the development Lpar and I have some behavior > I can't explain: > > 1. Our users of SSL TN3270 with emulators set at 40 bit (ya, I know) > encryption now need to specify 128 bit. > > 2. When I run NETSTAT CONN in the Development Lpar, I get only: > EZZ2586I ------- ---- ------------ -------------- > ----- > EZZ2586I ------- ---- ------------ -------------- > ----- > > Which doesn't occur in any of the other Lpars. > > Any help would be greatly appreciated (cross posting to IBM-MAIN, > IBMTCP-L, RACF-L) ---------------------------------------------------------------------- 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
