I have some jobs that are "in queue" which indicates they are run via the job deamon. They ran yesterday which successfully. They reside in our company 300. Now I do not understand how they are running.

I do see the rc.starjobdm.300 which is in the /etc dir.
When I do a "ps -ef | grep rc.starjobdm.300" I get nothing.

When I do a "ps -ef | grep rc.startjob" I get nothing.

In my rc.start script, the start_all_jobs script is started, in the start_all_jobs script it starts the rc.starjobdm.300.

So what is running to activate the jobs ??

Nick,

You have to look up in - $BSE/etc/rc.startjob scripts.

>tail rc.startjob
DS_SERVER=ba ;export DS_SERVER
BSH_JOB=$1 ;export BSH_JOB

if [ $# -gt 1 ];then
BSH_JOBOK=$2 ;export BSH_JOBOK
echo $BSH_JOBOK
fi

ba6.2 ttaad5203m000 2>${BSE_TMP}/rc.startjoberr &

To check the jobs currently executing -

>ps -ef | grep ttaad5203m000
bsp 7470 13821 1 13:21:18 pts/tx 0:00 grep ttaad5203m000
bsp202d 28934 1 0 Feb 1 ? 0:00 ba6.2 -- -nodebug ttaad5203m000
bsp202d 28933 1 0 Feb 1 ? 0:00 ba6.2 -- -nodebug ttaad5203m000

or you can also look up for ba6.2 if any 3-GL scripts are being called in jobs.

Nick,

I took a look at the rc.startjobdm script and it calls 'ba6.1 ttaad5206m000'. The normal rc.startjob calls 'ba6.1 ttaad5203m000'... so the 5206 session must be a session that just runs forever and starts other jobs that are in the queue.

As a note, rc.stopjobdm calls 'ba6.1 ttaad5207m000' ... so it must go in and tell 5206 to shut itself down.

You should probably be able to grep on ttaad5206m000 to find your job daemon process.

Cheers,

-Dennis

yes I see the ttaad5206m000 constantly running, which explains it for me. Thanks Dennis.