Known issues and workarounds
Conditional statements slicing issue
When using PL/I features with Z Understand version prior to 6.1.4, the slicing of conditional statements results in the END statement not being included in some scenarios. After generating the PL/I service code, manually add the END statements as required.
Restarting Z Understand containers
- Run
./stop.shto stop the running Z Understand containers. - Run
./start.shto start Z Understand again.
./stop.sh
--all first and then run ./start.sh to perform a fresh start.Getting errors in the Z Understand Web UI after it has been left unused
If you leave the Z Understand unused for a while, the authentication token might get expired and then you will see errors in the UI. To resolve the errors, go to the login page and log in again.
The same errors occur when you open Z Understand in multiple browser tabs at the same time. Because opening multiple browser tabs interferes with the ability of Z Understand to refresh the authentication token. You must open Z Understand only in one browser tab at all times.
Getting a bad gateway error when trying to access Z Understand
If you get a bad gateway error when trying to access Z Understand, check and make sure that the
PROTOCOL in config.properties is set correctly. For example, if
Z Understand is not configured to use
https, the value needs to be changed to http.
Operation failures for no apparent reason
If operations fail for no apparent reason and cannot be recovered through the user responses as described in the Messages section, it's possible that the number of database connections has been exhausted. In such cases, try reloading the browser page to trigger a recovery process and then try the operation again.
Timeout error
360 seconds):- In the
config.propertiesfile, add the following entry:
ReplaceRA_API_TIMEOUT=<seconds><seconds>with the timeout length that you want to set, for example,720 seconds. - Restart Z Understand.
Key Conditions view disappears while using Action Menu
The Key Conditions view might be empty after you click a key condition’s Action
Menu icon (
) while using Visual Studio Code version 1.88.0 or later. This happens because focus is
moved away from the active text editor that is responsible for populating the Key Conditions view.
To fix the problem and prevent focus from shifting to the other editor group, close any open editors or views that are in Editor Groups next to the active text editor that contains your program source.
Secure communication issues
ad.crtfor the Z Understand certificatedb.crtfor the database certificate
config.properties
file.