Baanboard.com

Go Back   Baanboard.com > Forum > Baan Quick Support: Functional & Technical > Tools Administration & Installation

User login

Frontpage Sponsor

Main

Poll
For ERP LN feature pack upgrade, what method of install are you using?
Installation Wizard into existing VRC
37%
Installation Wizard into new VRC
39%
Manual into existing VRC
3%
Manual into new VRC
21%
Total votes: 38

Baanboard at LinkedIn


Reference Content

Closed Thread
 
Thread Tools Display Modes
  #1  
Old 22nd August 2017, 18:34
litrax's Avatar
litrax litrax is offline
Member
 
Join Date: Sep 2005
Location: Germany
Posts: 95
litrax is on a distinguished road
Baan: ERP LN (FP8) - DB: Oracle10g (10.2.0.1.0) - OS: Solaris
Unhappy Job Scheduling Problems Linux
Baan: ERP LN 6.1 FP8 (Infor ERP 10.2)
DB: Oracle 10.2.0.x
OS: Solaris 10 (SunOS 5.10)
C/S: None/Unknown

Hi there,

I'm having an issue with the job-scheduling when I start a job via shell and I'm hoping somebody can give me some tips or had this issue before:

I'm changing the server from Solaris to Linux.
On solaris a job was started in the following way:
Job Data:
Code:
Job = IMPORT_DATA
Use external Sched = No
Periodical = Yes
Suspend Job Until Next Execution = Yes
Period = 1 Minute
Next Execution Date = a date/time in the future 
Status = Free
Now to start the job and let it run forever we used the shell script
root> su - job100
job100> $BSE/rc.startjob_job100 import_data
(Note: In this script the job is started via the session ttaad5203m000)

The job started, was then shortly in the state "Running" and then updated the last and next runtime and was in the state "Waiting" for the next minute, cause this is the given period for this job.
And the job ran every minute and in between it was in the "Waiting" state. Everything was as expected.

Now on the new Linux server the job runs once, updates the times, then is in the state "Waiting" but runs never again!? It remains in "Waiting"- state forever.
This way to start a periodically job cannot longer be used in our new environment. But why?

I checked some logs and the processes but nothing unusual.
Shure we can set it up as job daemon but the question remains:
Why is this mechanism broken?


The help of the field "Suspend Job Until Next Execution" clearly states:
Quote:
Indicates whether the periodical job must be executed automatically after last execution. After execution of a periodical job, the next execution date is automatically updated according to the given period and/or calendar date.

If this check box is selected, the job is suspended until the next execution date. For jobs started by the Activate Job (ttaad5203m000) session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat, the job’s status is set to Waiting. The job is automatically restarted at every next execution date that is defined in the calendar or by the interval.

If this check box is cleared, the job runs once and is then stopped. For jobs started by the Activate Job (ttaad5203m000) session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat, the job’s status is set to Free. To restart the job, you must manually start the Activate Job (ttaad5203m000) session, the UNIX shell program rc.startjob, or the Windows batch file startjob.bat.
Any suggestions where to find the bug. Why the running job- bshell doesn't start the job again at the next execution interval?


[UPDATE]
Out of curiosity I changed the field "Suspend Job Until Next Execution" from "Yes" to "No". Then I set the next running date in the near future. Then I started the job via the script.
Normaly it should execute the job at the given time, then it should set the job status to "Free" and update the next running time according to the interval and then exit the bshell.
But it also remains in the state "Waiting" and never executes anything. The bshell process never ends. !?!? Very curious...
__________________
Have a lot of fun...

Please look at this before asking wholes in the stomach ;-)
http://www.baanboard.com/programmers_manual_baanerp

Last edited by litrax : 22nd August 2017 at 18:52. Reason: updated the second use case
  #2  
Old 23rd August 2017, 08:07
günther günther is offline
Guru
 
Join Date: Jan 2002
Location: Ehingen, Germany
Posts: 573
günther is on a distinguished road
Baan: IVc4 - DB: Informix - OS: HP-UX
Hi litrax,

we're on HP-UX and we use 'cron' to start our Jobs instead of the baan scheduler. Maybe that's an option for you?

Regards
Günther
Sponsored Links
  #3  
Old 23rd August 2017, 08:14
litrax's Avatar
litrax litrax is offline
Member
 
Join Date: Sep 2005
Location: Germany
Posts: 95
litrax is on a distinguished road
Baan: ERP LN (FP8) - DB: Oracle10g (10.2.0.1.0) - OS: Solaris
Yeah. I forgot to say that because I wanted to hold it short,
but I sure use the cron to start all jobs.

Even for the one I mentioned with interval 1 minute and external planing turned off. So in case of an error I only have to make sure the old process is gone and the status is free again. The cron will restart the job the next minute and I don't have to take care of it.

I did crawl through inforxtreme too, but just tips how to debug or to create dbs.logs .
__________________
Have a lot of fun...

Please look at this before asking wholes in the stomach ;-)
http://www.baanboard.com/programmers_manual_baanerp

Last edited by litrax : 23rd August 2017 at 15:16.
  #4  
Old 4th September 2017, 16:59
litrax's Avatar
litrax litrax is offline
Member
 
Join Date: Sep 2005
Location: Germany
Posts: 95
litrax is on a distinguished road
Baan: ERP LN (FP8) - DB: Oracle10g (10.2.0.1.0) - OS: Solaris
Thank you all for your self-sacrificing help.
Appreciate that
__________________
Have a lot of fun...

Please look at this before asking wholes in the stomach ;-)
http://www.baanboard.com/programmers_manual_baanerp
Closed Thread


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Baan Functional application development CV......job job job job job job prabhakar5676 Jobs and Resumes 0 11th May 2016 20:41
Are there efficient ways of JOB scheduling baan_player Tools Administration & Installation 3 25th January 2010 09:28
chart manager: display daily job runtime pconde Code & Utilities 3 7th November 2008 12:48
Problems with relative date in Job Mgmt j. streun Tools Administration & Installation 0 30th September 2004 21:00
Linux and Baan: library problems patvdv Operating Systems & Databases 3 16th January 2002 11:41


All times are GMT +2. The time now is 09:53.


©2001-2017 - Baanboard.com - Baanforums.com