thanks Rob for your response. in answer to your questions:
the file system i am using under z/os 1.9 is the same as the one under z/os 1.7. the z/os 1.7 lpar that is working has a copy of the file system (originally copied from the failing lpar), not the same one. there were no error messages - i had JZOS tracing and debugging on and did not see anything. TOMCAT/JBOSS would always stop at the same point after the same message was issued about the last thing it was doing. i forgot exactly what the message was (something to do with jndi i think) and we would have to go back to z/os 1.7 on the lpar in order to reproduce the problem. We are running RACF but there were no RACF messages issued. anyway, things are working now so if crypto was the problem, it may have been due to whatever differences were made for z/os 1.9. thanks again for your response. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Rob Schramm Sent: Wednesday, February 06, 2008 5:45 PM To: [email protected] Subject: Re: I'm back Hi Eileen, I am sure that you got the same response from Steve and Kirk... "huh?!?" <vbg> That is a bit weird. The place I had it setup, was running z/OS 1.8 with ICSF implemented and locked down on the CSFSERV resource. If I had to guess, I would say it was a mount point/file system permission issue. I am sure you probably tried to rule permission bits out as a cause. You don't happen to have the errors that were issued when Tomcat was attempting to come up... do you? I made a fair amount of mistakes over the last couple of years with Tomcat/JSPWiki... so I have gained some experience with it. <vbg> I am curious which security product you are running? Were the file-systems: * separate? * moved between the lpars? * using shared files with USS (unix system services for those that might somehow attempt to confuse the reference) I can tell you that when I did have issues, I ran the JZOS with Trace level debug and it is also possible to setup Tomcat to debug as well. I also took advantage of running SAF traces and USS security traces. Both are verbose, but can illuminate hidden issues. Cheers, Rob ---------------------------------------------------------------------- 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
