Andreas
19th February 2002, 10:11
Hi,
i have the following problem when putting a self-developed session in a job.
The session creates an ASCII-file from a BAAN-Table.
I used the seq.* functions for creating this file.
When i put this Session to a job, the job works fine when i activate it via
ttaad5203m000, but when it is activated via jobdeamon the job hangs.
I think there is no Problem with authorizations.
Logged on as Jobuser i can run the job, and the file is created.
Any hints?
We are on AIX with Baan 5c.
Andreas
:confused:
victor_cleto
19th February 2002, 12:08
Are you using the correct user to start the jobdaemon?
Each jobdaemon must be started by a job user connected to the correct package combination and company, otherwise it doesn't work.
Andreas
20th February 2002, 09:14
That's not the problem.
The Jobuser has the right package combination.
When I'm logged on as this User I can start the job via ttaad5203 and it works.
Adastra
20th February 2002, 17:58
Sorry to be persistant about jobdeeamon, have you verified that you can run other sessions with the jobdeamon?
Depending on how you start the jobdeamon, you could end up with an other user - if that is the case you have to remove the commments for
USER=job_user; export USER
to get Baan to understand which user to start as.
Regards,
John
:)
shah_bs
20th February 2002, 18:20
I would advise checking UNIX directory permissions to make sure they allow creation of the ASCII file.
Andreas
21st February 2002, 10:13
Originally posted by Adastra
Sorry to be persistant about jobdeeamon, have you verified that you can run other sessions with the jobdeamon?
:)
Yes, I tried with some other sessions like normal print-sessions.
They are executed by jobdaemon.
Originally posted by shah_bs
I would advise checking UNIX directory permissions to make sure they allow creation of the ASCII file.
Thats not the Problem, because when I'm logged on as the Job-User, the ASCII-File is created.
In program script I used the seq.* functions to create the ASCII-File. In Tools Help there is a hint under the Header 'Context' that these functions are bshell functions.
Is it possible that the jobdeamon don't 'know' these functions because there is no bshell used (think I read this somewhere).
Regards,
Andreas