Hi all,

Has anyone executed a job using "Job Daemon or rc.startjob" instead of their currently used "Activate Job"?

I have tried executing Job Daemon or rc.startjob in our office but it seems not working.

The following were the steps I have done please advise if I missed anything here.

1. Run the session Maintain Calendar. Create entry on this session e.g. TIME
2. Run the session Maintain Dates by Calendar. Create entry for the date and time.
3. Run the session Maintain Job Data with the following entries.

Job: TEST
Desc: test job
User: bsp
Creation Date: 02-08-02
Periodical: yes
Job waiting after Execution: yes
Calendar: TIME
Period: 0
Finish Date:
Next excution date: same as Finish date
Maximum duration: 0
Status: Free
4. Make job for session to be executed:
I set the device to printer and also tried ASCIF (output to file)

5. On the command line I login as root and execute the command:
# rc.startjobdm.TEST

Please advise.

thanks,

julia

Julia,

Most of the time you have to edit both scripts before they work. You have to specify the user in which it has to work. THe users should have the company as default in which the jobs are specified.

Furthermore the jobdm is really a deamon. You only have to start it, all jobs will start automaticly if the have the status 'in queue'.

For rc.startjob you have to change the user as well. That one you have to pass the name of the job since it only runs one job. The status of the job should be 'free'.

With the jobdaemon you should see a bshell ttaad????m000 process running, it also creates a application lock.

If it doesn't work, check the scripts, they write some logfiles which you can check.

Han