Sometimes the Zend Server Daemon can stop responding, which can cause various issues in the Zend Server User Interface. The logs may indicate that a record cannot be updated or accessed from the database. This article does not tell how to determine if the zsd.db database needs to be reset. It just tells how to do it. You may be directed to this article by Zend Support, or from another article describing a symptom that requires this procedure to correct.
Zend Server for IBM i version 6 or higher, running on any supported version of IBM i.
Please end the Zend Server Daemon job. From the 5250 command line:
This brings you to the ZS Daemon Management Menu.
Please use option "2. Stop Zend Server Daemon".
Verify the daemon is stopped. From the command line at the bottom of the menu:
Verify that there are no jobs named ZSDAEMON running. If there are any, use F5 a few times until they go away. It is OK if this takes a few minutes, depending on what the job is doing.
In Navigator, please find this file:
Rename the file to something like zsd.db.bak. To rename the file in Navigator, right click it and use the Rename option from the context menu.
Return to the menu and use option "1. Start Zend Server Daemon". Then, from the command line at the bottom of the menu:
Verify the Zend Server Daemon job is started by looking for these two entries:
ZSDAEMON QTMHHTTP BCI .0 PGM-watchdog
ZSDAEMON QTMHHTTP BCI .0 PGM-zsd
At first there may be more than two ZSDAEMON jobs. Please continue to use F5 every once in a while until just the two jobs named ZSDAEMON appear as shown above.
Now, please refresh the display in Navigator and verify a new file /usr/local/zendsvr6/var/db/zsd.db has been created.