Just installed PTDV and ran my frist PEX trace.
Now I'm trying to start PTDV in thin client mode.
First time through, I got the message saying theat the server didn't have the PTDV code and did I wish to upload. I said yes, but that error'd out do to authority issues in the /QIBM/ProdData/ directory.
So I told it to put the PTDV code someplace else. That seemed to work.
So then I'm looking at a screen saying trying to connect to PexDataMgr. After a long wait without change, I closed PTDV.
Looking at the server, I realized that there was a PTDVSERVER waiting on a job queue. I killed that one, restarted PTDV, and once it got to the trying to connect, I moved the PTDVSERVER job that had been submitted to QUSRNOMAX. Thought I'd be good to go, but it turns out not.
The waiting to connect dialog stayed on the screen for quite a while, and the little command prompt window kept getting new lines "Look up failed for //<iseriesIP>/PexDataMgr: trying again"
When I started this post, that's where it was at. Now however, the trying to connect dialog has gone away and there's a "Current Status - Initializing collection" message. It's been there for 10-15 minutes.
Looking the the server job, I see the following in QPRINT
Attaching Java program to /tmp/C1162332/iDoctor/PTDV/ptdv.jar.
Total memory: 13221888 free: 521861 used: 12700027
Performance Trace Data Visualizer for System i5 4.2.1 (C) Copyright IBM Corporation 1998,2006
Running with JDK 1.4.2
Total memory: 13535872 free: 561829 used: 12974043
Total memory: 13592960 free: 562853 used: 13030107
Total memory: 13866752 free: 596966 used: 13269786
Total memory: 14009472 free: 627622 used: 13381850
Total memory: 14209280 free: 607846 used: 13601434
Total memory: 14237824 free: 636390 used: 13601434
Total memory: 14323456 free: 610278 used: 13713178
Total memory: 14409088 free: 639846 used: 13769242
Total memory: 14437632 free: 612646 used: 13824986
Total memory: 14523264 free: 643814 used: 13879450
Total memory: 14637440 free: 647046 used: 13990394
Total memory: 14665984 free: 623174 used: 14042810
Total memory: 15795968 free: 686214 used: 15109754
Total memory: 15938688 free: 721222 used: 15217466
The PexDataMgr has been exported.
Starting server for use with client: PTDV-136338977
Trying to connect to port: 1099
RMI name is: //c00092a4.cintas.com/PexDataMgr
Total memory: 16694656 free: 7086512 used: 9608144
Apr 30, 2009 12:38:50 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(2)-10.24.0.187: [10.24.0.187: sun.rmi.registry.RegistryImpl
0:0:0, 0: java.rmi.Remote lookup(java.lang.
Apr 30, 2009 12:38:55 PM sun.rmi.runtime.Log access$200
FINE: RMI TCP Connection(2)-10.24.0.187:
http://10.24.0.187 exception:
java.rmi.NotBoundException: PexDataMgr
at java.lang.Throwable.<init>(Throwable.java:195)
at java.lang.Exception.<init>(Exception.java:41)
at java.rmi.NotBoundException.<init>(NotBoundException.java:45)
at sun.rmi.registry.RegistryImpl.lookup(RegistryImpl.java:106)
at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:342)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:207)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:534)
Apr 30, 2009 12:38:58 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(1)-10.1.4.64: [10.1.4.64: sun.rmi.registry.RegistryImpl
0:0:0, 0: void bind(java.lang.String, java.rmi.
Apr 30, 2009 12:39:03 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(3)-10.1.4.64: [10.1.4.64: sun.rmi.transport.DGCImpl
0:0:0, 2: java.rmi.dgc.Lease dirty(java.rmi.server.
PexDataMgr bound
PexDataMgr successfully bound
Total memory: 17008640 free: 5562944 used: 11445696
Apr 30, 2009 12:39:10 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(2)-10.24.0.187: [10.24.0.187: sun.rmi.registry.RegistryImpl
0:0:0, 0: java.rmi.Remote lookup(java.lang.
Apr 30, 2009 12:39:12 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(4)-10.24.0.187: [10.24.0.187: sun.rmi.transport.DGCImpl
0:0:0, 2: java.rmi.dgc.Lease dirty(java.rmi.ser
Apr 30, 2009 12:39:13 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(4)-10.24.0.187: [10.24.0.187: com.ibm.iseries.perf.pdv.pex.PexDataMgr[0]: public abstract boolean com.ib
Server user: C1162332 client user: C1162332 client key: PTDV-136338977 key: PTDV-136338977
Apr 30, 2009 12:39:13 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(4)-10.24.0.187: [10.24.0.187: com.ibm.iseries.perf.pdv.pex.PexDataMgr[0]: public abstract java.lang.Stri
Apr 30, 2009 12:39:13 PM sun.rmi.runtime.Log access$200
FINER: RMI TCP Connection(4)-10.24.0.187: [10.24.0.187: com.ibm.iseries.perf.pdv.pex.PexDataMgr[0]: public abstract com.ibm.iserie
Total memory: 17465344 free: 5091808 used: 12373536
So is PDTV working or is it stuck?
Thanks!
Charles Wilt
