This article is now available in our new Knowledge Base: Jobs will not start in subsystem ZENDPHP7 (or ZENDSVR6) at start up, but can be started individually from the menu
Issue
After a new installation, when Zend Server is started, no jobs start in subsystem ZENDPHP7 (or ZENDSVR6 for earlier versions), even though there are several jobs configured to autostart. However, it is possible to start the jobs individually from the management menu.
Environment
Zend Server 6 or higher on any supported version of IBM i.
Resolution
This can happen if the user message queues are not created when the Zend Server installer creates new user profiles. It is not clear why this sometimes happens, because the message queues should be created automatically by the CRTUSRPRF command. However, it is easy to correct.
Please log into a 5250 session as QSECOFR or some *SECOFR class user. From the command line:CRTMSGQ MSGQ(QUSRSYS/ZENDADMIN)
CRTMSGQ MSGQ(QUSRSYS/NOBODY)
If the message displays to tell you the message queue already exists for both queues, this is not your issue. If the message queues create successfully, please create this one as well:
CRTMSGQ MSGQ(QUSRSYS/ZS5250DEMO)
After successfully creating the ZENDADMIN and/or NOBODY message queue, please retry starting Zend Server to verify that the jobs now start up as expected in the ZENDPHP7 (or ZENDSVR6 for versions prior to 9) subsystem.
Thanks, Rod. In my case, the only queue missing was QUSRSYS/NOBODY. Its absence could possibly explain why ZSDAEMON didn't start.
Thanks, Alan. Modified the article to always include adding QUSRSYS/NOBODY.