On thing that comes to mind is that the port may not 9443.  If you have or had other WebSphere applications installed it will change.
The ports are listed in a file called AboutThisProfile.txt under the CLM profile in the logs directory
I have not worked much with zOS but here's where it is by default on a typical Unix machine.
/OPT/IBM/WebSphere/AppServer/profiles/<TheProfile>/logs/

You will want to check the "HTTPS transport port" value

You can also look through the logs in that directory to get some clues.
(I would stop the profile delete all the logs and restart the profile just to have a fresh set of logs.)


Also in regards to Lauren's answer I would make sure you restarted the profile after you installed jts, ccm etc.
Just restarting the application from the WAS console does not always work.
You would run:
stopServer.sh server1  -username username -password password
startServer.sh server1
Found under:
/OPT/IBM/WebSphere/AppServer/profiles/<TheProfile>/bin/

Hi Ingo,

Have you started the server?  Details on how to do so are available at https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/t_s_server_installation_start.html&scope=null. 

If you have started the server, does going to :9443/jts or :9443/ccm work?

Hi Ingo,

Assuming that JTS has started and is listening on the port, I would recommend dumping the core from WebSphere to see what classes are in use.

We saw a similar situation recently where a system environment variable was pointing to a FlexLM license manager which was not accessible. The kind of variables to check are LM_LICENSE_FILE, RATIONAL_LICENSE_FILE and TELELOGIC_LICENSE_FILE.    If that is the case, you will see classes referencing the FLEX server in the WebSphere core file.  Validating that any remote license servers are available to the server host, may resolve the problem.  Even if it's not the exact same problem, the WebSphere core may give you some clues.

Regards,

John