Page 1 of 1

ZENDCORE started in development AND production

Posted: Fri Oct 28, 2011 9:19 pm
by dalalvak
I took the following steps in DEVELOPMENT

restarting APACHE server

•Sign on to your System i.
•Enter the command GO ZENDCORE/ZCMENU.
•Take option 5 Service Management menu.
•Take option 9 End i5_COMD service. Wait for the messages.
•Take option 5 Stop Apache server instances. Wait for messages.
•Take option 2 Stop Zend Core Subsystem. Wait for messages.
•Take option 1 Start Zend Core Subsystem. Wait for messages.
•Take option 4 Start Apache server instances. Wait for messages.
•Take option 8 Start i5_COMD service. Wait for messages.

Suprisingly they said I started the one in PRODUCTION. Is taht possible ?

Keith

Re: ZENDCORE started in development AND production

Posted: Mon Oct 31, 2011 9:14 am
by shlomov
There is an Auto start jobs that set upon installation to run at IPL time.
Check the subsystem QSYSWRK for the ZEND products auto start up jobs.

DSPSBSD QSYSWRK and select option 3. Autostart job entries

look for the entry:
Job Job Description Library
ZC_STR_SBS ZCOREJOBDX ZENDCORE

If this is the case than you need to control all the Zend environment manually and remove the auto start job.

check the following article:
http://kb.zend.com/index.php?View=entry&EntryID=300

Re: ZENDCORE started in development AND production

Posted: Tue Dec 20, 2011 9:13 pm
by alishia
very helpful, thanks!

Re: ZENDCORE started in development AND production

Posted: Sun Dec 25, 2011 6:10 pm
by ambit_energy
Using the Work Management Facility to setup Automatic Start Up Jobs. Change the IPL start-up program, the autostart job in the controlling subsystem transfers control to the program that is specified in the start-up program to set up system (QSTRUPPGM) system value.

with the automatic start up from the QSYSWRK Subsystem Auto Startup Jobs (ZC_STR_SBS) entry. Consider the possibility that the TCP/IP server jobs submitted by the same QSYSWRK subsystem Auto StartUp Jobs entry options, have not completed loading and while running NO TCP/IP dependent job can start.

The problem with the above setup for the ZEND start up, occur if TCP/IP jobs fail to complete the load of all TCP/IP components and servers.

Server components required for the startup of the ZEND Daemon and Services.




:8
George Shelter
Ambit Energy, Sales Consultant
Carthage, Missouri