Home

Install Problems / Issues

This wiki is to capture the problems we find from Zowe users who are unable to successfully install and successfully start the Zowe server started task. Anyone who encounters a problem with a Zowe environment should check whether it is something that's already known and if not add to the wiki. This is to help us build more automated scripts into Zowe to troubleshoot as well as update the documentation.

Problem Determination script

Zowe is being extended to include problem determination scripts.

zowe-preinstall.sh

In the install/scripts folder this script will check: CSF is up and running.

z/OS is V2R2 with PTF UI46658 or V2R3

z/OS USS is enabled and ICSF is configured and started

Ports in the zowe-install.yaml file are available

RACF or other SAF security settings are correct

Enough free space exists in the target install folder specified in zowe-install.yaml

Verify Zowe runtime

/scripts/zowe-verify.sh can be run from inside a Zowe runtime and will report on the health of that instance, whether it's not started and can be started successfully, whether it's healthy and all of the endpoints are available, and well as the in-between states. https://github.com/zowe/zowe-install-packaging/issues/118 >p> ZOWESVR PROC is in a JES PROCLIB

Check APF authorized and program bits for ZLUX and Atlas

If ZOWESVR is active then check;

Number of STEPS Ports allocated for each step match the ports defined in the static definitions

Runtime problems

LOCAL_HOST not mapped causing the explorer-server to be unable to locate z/OSMF. APF Authorized and Program bits not set successfully on the explorer-server/wlp/usr/Atlas/ Unable to allocate the ports