First, check that the name server is running.
Note: To start
tnameserv on
the local host, enter the following command at the UNIX System Services or
Windows NT command prompt:
tnameserv -ORBInitialPort 2809
This
causes
tnameserv to listen for connections on TCP/IP port
2809.
Next, run the IVP client program from your UNIX System Services working
directory by typing ./runEJBIVP.
On your UNIX System Services terminal, you should see messages similar
to the following:
CICS EJB IVP: Querying the Java SDK level
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM z/OS Persistent Reusable VM build
cm142-yyyymmdd (JIT enabled: jitc))
CICS EJB IVP: Starting the EJB client program
HelloWorld client program started
Performing JNDI lookup using CosNaming
Testing the following location: samples/HelloWorld
Located home interface for HelloWorld bean
You said: Hello from CICS EJB IVP client
HelloWorld client program ended
CICS EJB IVP: Completed successfully
Note: - In the above messages, yyyymmdd is the date on
which the SDK was built.
- In this example, a COS Naming Server has been used. If you use an LDAP
name server, similar messages are produced.
- If you get a javax.naming.CommunicationException, it
may be because the MVS™ hostname is incorrect in your tcpip.data file.
You may be able to fix the problem by adding an entry for the MVS system to
your /etc/hosts file. For guidance, see the MVS manuals.
In your JVM stdout file, you should see the following message:
CICS EJB hello world sample called with string: Hello from CICS EJB IVP client
If you re-run the client, you will probably notice a performance improvement.
This is because the JVM should be reused.
When you have finished running the IVP, you should:
- Discard the resource definitions that you created in mygroup.
- If you turned off EJB role-based security before running the IVP, turn
it back on. To do this, restart CICS® with the XEJB system initialization
parameter set to 'YES'.