×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Evan Harris wrote:
I have to say that I prefer not to use ADDAJE to start jobs - a call to a
program or better yet a command to start a process always works better from
my point of view.
That's the way our server normally starts: with a command.
We have two job descriptions, one for the master server job, and one for
child-server jobs spawned off from it. That's an oversimplification, but
it will do for now.
Neither of these job descriptions have RQSDTA in them. They just define
how and where the master- and child-server jobs will run.
The normal way to start the server is with a command, which accepts
parameters of port-number and environment-library. Its CPP is a CL, that
launches the master-server with a SBMJOB command, specifying the
master-server job description.
Given this, how would I set this up to autostart with the subsystem it's
running in?
I tried setting up a model on our development box: a subsystem called
FOO, fed by a job queue called FOO, with an autostart job entry for a
copy of the master-server job description, altered to have the server
startup command as its RQSDTA.
But it doesn't work. I can start the FOO subsystem, and it starts all
right, but it doesn't start the server, either in itself, or anywhere
else. What's missing? Is it even worth pursuing?
--
JHHL
midrange.com
