Topic
2 replies Latest Post - ‏2013-01-30T12:57:06Z by SystemAdmin
SystemAdmin
SystemAdmin
1086 Posts
ACCEPTED ANSWER

Pinned topic connection problem afte upgrade Rdz 7.6 to 8.5 on z/OS

‏2013-01-30T11:30:14Z |
Hi,

after upgrading RDz on z from 7.6 to 8.5 we've got a mysterios problem.
But first: IVP routines on z are running succesfully.

But, when conneting from a client, we got errors, which we got not with Version 7.6 on the host. Same Client (8.5.1) with same configuration (as 8.5. on z replaces the 7.6.)

MessageCode is RSE1242, with message;
RSEG1242 'Daemon failed to launch server on <our mainframe> using port 0', and as detail:
server failure: server failure: java.lang.NullPointerException.

In rseserver.log, I found just this:
Wed Jan 30 12:09:04 CET 2013
ERROR ServerThread: 66627: java.lang.NullPointerException
org.eclipse.dstore.core.server.ServerLogger.initialize (ServerLogger.java:103)
org.eclipse.dstore.core.server.ServerLogger.logInfo(ServerLogger.java:189)
Wed Jan 30 12:09:04 CET 2013
ERROR RseDaemon: getServerPort(): result=41807;server failure: java.lang .NullPointerException

com.ibm.etools.zos.server.ServerThread.run(ServerThread.java:122)
java.lang.Thread.run(Thread.java:769)

I guess, its something in configuration change while upgrading, but in the moment, I hav eno clue...

Thanks for help,
Ingo
Updated on 2013-01-30T12:57:06Z at 2013-01-30T12:57:06Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    1086 Posts
    ACCEPTED ANSWER

    Re: connection problem afte upgrade Rdz 7.6 to 8.5 on z/OS

    ‏2013-01-30T11:32:04Z  in response to SystemAdmin
    Just one additional info:

    Of course, I found this: https://www-304.ibm.com/support/docview.wss?uid=swg21460835

    But it doesn't help and right in the moment, I am guessing, its not a product problem (therfore: no PMR yet), but a problem on our side...
  • SystemAdmin
    SystemAdmin
    1086 Posts
    ACCEPTED ANSWER

    Re: connection problem afte upgrade Rdz 7.6 to 8.5 on z/OS

    ‏2013-01-30T12:57:06Z  in response to SystemAdmin
    After some in-deep research we found the problem:

    The LOG File directory was changed and the new directory had wrong permissions.

    Thanks for help (even thru just listing to me)

    Cheers,
    Ingo