Hello,
I just don't get this. :mad:
There is a report session created by someone. If the session is executed in a non-job mode, it will give the output. But, if the same session is executed through job (using job daemon), the status would change to Running from In Queue, and then hang. No change in status, no file generated, no error, nothing!! :confused:
Also, if I do not put the status into In Queue, and activate the session through baan session, then I'll get output. And, this user is able to execute all the jobs, except this one.
Any idea what am I overlooking!?

Regards

I'm not a big job user, but I would think the printer could cause such differences. The Job printers cannot be 'Windows' printers, as defined in Maintain Devices, as that uses the bw print. Bw print is not active when you are not running through the BW Client, such as Unix jobs, but the user would have no problem later trying to run this manually with a BW Client open.

Hey Lisa,
Thanks for the reply.
The device I am choosing is ASCIF, and the same device is used if executed in non-job mode. It works fine in the latter.

OK, well, I would not think the ASCIF would have an issue. I noticed you said it was a custom session. The sessions can hang if the coding is not correct for Job processes. The job process does not call the form sections as no form becomes active. This post may give some ideas:

Post on Job not running (http://www.baanboard.com/baanboard/showthread.php?t=8424&highlight=job+mode)

What are your setting within the job itself? Is periodical checked? What is the Period values and what is the value in the next execution date?

Sometimes the job will hang if the next execution date is too far in the future. Change the period to be every minute and change the next execution date to be today's date but a earlier than the actual time. For instance if it is 16:00, I will change the time to 15:55. This way when I schedule the job it should execute right away, as the next time it was supposed to run is past.

Hope that helps.

I have some incedences like these, some of customization sessions didn't ran because of above cause....

In case you are dumping the ASCIF file on a network drive, you might want to check if Baan has NT 'write' access to that folder/drive.

Cheers

Hey Folks,
Lisa: There is a form, but without any input field. The criteria is hard coded in the program script.

Amac: It is a periodical job, with the periodicity of 05 minutes. I changed it to 01 day also, but no success.

Mraguthu: What is the criteria which makes some of the sessions not work in job mode?

John: The same user is able to create the file if the session is executed in the non-job mode!!

I don't get this!! I finally created a new session with the same logic, and this is working fine now (in both the modes!!). :rolleyes: