Troubleshooting installation and startup of Zowe z/OS components
The following topics contain information that can help you troubleshoot problems when you encounter unexpected behavior installing Zowe z/OS components or starting Zowe's ZWESVSTC
started task.
#
Unable to create BPXAS instancesSymptom:
When you start ZWESVSTC
started task, either by running the zowe-start.sh
script or by launching the started task directly, you encounter the following error in the log:
You will also encounter the following messages in the SYSLOG:
Solution:
This problem occurs when the maximum number of BPXAS
instances have been reached.
This may be because when the Zowe instance directory was created, it was generated in the same location as the Zowe root directory. The Zowe instance directory is created by using the script <ROOT_DIR>/bin/zowe-configure-instance.sh -c <PATH_TO_INSTANCE_DIR>
. See Creating an instance directory. The Zowe runtime directory is replaced when new PTFs are applied and should be considered as a read-only set of files. Zowe instance directories are designed to live outside the directory structure and are used to start a Zowe runtime.
This problem will only occur with Zowe drivers prior to v1.10 and has been resolved in v1.10 where the zowe-configure-instance.sh
script will report error if it detects the -c
argument because the installation directory location is an existing Zowe runtime directory.
#
Errors caused when running the Zowe desktop with node 8.16.1Symptom:
When you start the ZWESVSTC
started task, you encounter the following error messages:
Solution:
This problem occurs when you use Node.js v8.16.1 which is not supported on Zowe. There is a known issue with node.js v8.16.1 and Zowe desktop encoding. Use a supported version of Node.js instead. For more information, see Supported Node.js versions.
#
Cannot start Zowe and UNIX commands not found with FSUM7351Symptom:
When you start the ZWESVSTC started task, you might encounter the following error message:
Solution:
Check that /bin is part on your PATH. Do echo $PATH
to check. If it is missing, make sure that it is appended to PATH in your profile, for example, in /etc/profile/
.