Last week I had to stop and start BaaN to clear a table lock and now I have a problem with some of my print queues. When I try to repeat the request, I get a message because the status states "Removed". I noted the delete delay was set to zero so I modified the user and the delete delay has been set to 168. This has not corrected the problem.

The user that is at issue is the user that drives my nightly jobs and the report in question is the result of a session in the job. These set ups are not new and up till last Friday morning, following a rc.stop and rc.start, the status in the device queue was done and I was able to repeat the request.

Any help will be appreciated. Thanks in advance. - Joy

Hi,

I think another factor is the temp. files created in your
{BSE}\temp folder, if those are removed then also you can't run through Device Queue.

Regards

Learner

The temp file is not there but the job did execute.

Joy -

Often, rc.stop or rc.start has something like rm $BSE/tmp/*

It sounds like that's the case here..

Dave

Often, rc.stop or rc.start has something like rm $BSE/tmp/*
$BSE/tmp/pd_lock which is used by the $BSE/bin/pdaemon6.2 (or your BaaN tools version)

Originally posted by NPRao
$BSE/tmp/pd_lock which is used by the $BSE/bin/pdaemon6.2 (or your BaaN tools version)

It may do that... but a lot of people actually have it wipe out the whole $BSE/tmp directory.

Dave

Some people also put entries in a particular user's cron file (ex. bsp) to periodically remove files in $BSE/tmp older than a certain number of days. So you may want to check this as well.

Today we were advised to BaaN to disable pdaemon6.1. Apparently the restart of BaaN last week started the pdaemon6.1.