Gathering information to troubleshoot Zowe Application Framework
Gather the following information to troubleshoot Zowe Application Framework issues:
- z/OS release level
- Zowe version and release level
- Zowe application configuration
- Zowe Application Server Ports
- Log output from the Zowe Application Server
- Error message codes
- JavaScript console output (Web Developer toolkit accessible by pressing F12)
- Screen captures (if applicable)
- Other relevant information (such as the version of Node.js that is running on the Zowe Application Server and the browser and browser version)
#
z/OS release levelTo find the z/OS release level, issue the following command in SDSF:
Check the output for the release level, for example:
#
Zowe version and release levelOutput:
Displays zowe version
#
Zowe application configurationConfiguration file helps customize the Zowe app server, and is important to look at while you troubleshoot.
Read more about the Zowe app server configuration in the Zowe User Guide.
#
Zowe Application Server ports#
Log output from the Zowe Application ServerThere are two major components of Zowe application server: ZLUX
and ZSS
. They log to different files.
The default location for logs for both zlux and zss is folder zlux-app-server/log
. You can customize the log location by using the environment variable.
Read more about controlling the log location here.
Output:
List of files by most recent timestamp for both nodeServer as well ZSS.
#
Error message codesIt is advisable to look into log files for capturing error codes.
#
Javascript console outputWeb Developer toolkit is accessible by pressing F12.
Read more about it here.
#
Screen capturesIf possible, add a screen capture of the issue.
#
Other relevant informationNode.js – v6.14.4 minimum for z/OS, elsewhere v6, v8, and v10 work well.
npm – v6.4 minimum
Java – v8 minimum