How to config Zowe when z/OSMF is running with different hostname on the same image
Jing Ren 060001M6AM Visits (441)
How to configure Zowe when z/OSMF is running with a different hostname on the same image
Jing Ren |
Zowe is an open source project. Its purpose is to provide a modern interface to communicate and interact with a traditional z/OS system in a way that is similar to what you experience on a cloud platform today. This document will provide you with some user tips to run Zowe on a z/OS server with z/OSMF which has a restricted host name. For the whole process of installing Zowe on a zOS image, Zowe Docs contain a very comprehensive description on various related topics. For more details, please refer to Zowe Docs at http
To install Zowe, z/OSMF must already be available. We installed Zowe runtime in the same z/OS image where z/OSMF is running. In the z/OSMF configuration parmlib member IZUPRMxx, we set a specific HOSTNAME in it. This way, we can only use this HOSTNAME and port number to launch the z/OSMF page. Other hostnames or IPs for this image won’t work. For example,
Refer to this site for detailed information on parmlib member IZUPRMxx
If you have ever installed Zowe, then you should know that the Zowe installation script will automatically resolve some variables while running and using them in a number of places where micro services are talking to each other. There are two variables we should pay attention to:
ZOWE_EXPLORER_HOST will be set to the value of ‘hostname -c’, or you can manually specify it in the ~/.profile file before executing the installation script. ZOWE_IPADDRESS will be resolved as the IP of the current image. These two values will be copied to various places during the installation to generate scripts which will be used to run Zowe later. Here is where things got tricky. Since our z/OSMF can only be called by the HOSTNAME we specified in IZUPRMxx, neither value from variable ZOWE_EXPLORER_HOST nor ZOWE_IPADDRESS would work if Zowe is trying to communicate with z/OSMF by them. You will see errors in the joblog. For example,
Connect to 220.127.116.11:1234 [18.104.22.168] failed: EDC8128I Connection refused. (Connection refused)
We know this is the error when Zowe is trying to talk to z/OSMF because the port number 1234 is our port to access z/OSMF as specified in IZUPRMxx. However, it failed because z/OSMF was not reachable through this IP address. It can be accessed by - and only by - hostname SAMPLE.IBM.COM. If you are facing the same issue after the installation, you may have to update all the places that could specify a wrong IP address to connect to z/OSMF manually.
The first place to look are in the following files. They are used to start explorers.
Search for zosmf related set up. Here is what it looks like in our environment. You can see it’s using IP 22.214.171.124:1234 to connect to z/OSMF. This would fail if you have set HOSTNAME in IZUPRMxx.
So, we need to update Dzosmf.ipAddress to the same as in HOSTNAME in IZUPRMxx
Next, take a look at the zosmf.yml file located at
In our failure case, it was using the following link for z/OSMF.
Obviously, it wouldn’t work because our z/OSMF can only be accessed by
Therefore, we need to update the file to:
Recycle the Zowe server; then you should be able to use MVS explorer, USS explorer, JES explorer as well as logging on to the API catalog.
Please note that this document is not about the whole process of Zowe installation. You will have to complete all the installation steps mentioned in the Zowe Docs before using the tips in this blog to work around the issue when you have a specified z/OSMF HOSTNAME.
This work around is valid as of Zowe 1.2.0. A request has been raised to the Zowe team to provide an option to separate the z/OSMF hostname from the Zowe hostname. This will allow us to set variables in .profile instead of having to update the scripts after the installation.