Does Dataservice 4.0 scheduler jobs create windows task scheduler like 3.2 BODS

[Former Member]

I am using 3.2 Dataservices whene ever i schedule a job it is creating a task under windows scheduler.

Here on 4.0 version baed on windows 2008, will it create the same way. Or it has its own task scheduler?

I am having issues with a job on the mgmt console under scheduled jobs it says ACTIVE= "YES"

but the job isn't getting triggered, been manually running the task.

Please kindly provide details, i know many of you here has solid expertise on DS.

Thank you very much for the helpful info.

[Former Member · Accepted solution]

Hi Guy,

DS 4.0 work in the same for the own scheduler using the Windows task scheduler.

It could be some Windows permission issue causing your problem.

Are you able to execute the task manually or form the command line (

Locate the job .bat job  and execute)?

Check also the log  AL_RWJobLauncher for error.

thanks

Nawfal

[Former Member · Accepted solution]

Nawfal, thank you for  the response.

Could you please tell me how to check the log for AL_RWJobLauncher for error.

Can you please provide steps.

Thanks.

[Former Member · Accepted solution]

Find AL_RWJobLauncherLog.txt by default it's in %LINK_DIR%\log (like: C:\Program Files (x86)\SAP BusinessObjects\Data Services\log)

regards

Nawfal

[Former Member · Accepted solution]

Nawfal, I checked Al_RWLauncherlog.txt file.

I see exactly at 2:30 a job got triggered that is my job and immedeately RWJL_EXIT getting called.

11_28_2012 02:30:00 CRWJobLauncherApp::InitInstance called.

11_28_2012 02:30:01 *** RWJL_EXIT called.

What is RWJL_EXIT?

Since last one month my scheduled tasks aren't gettign triggered.

Checking on windows 2008 task scheduler, it is a pain they compl;etely changed teh scheduler.

Please need your advice.

Thank you.

[former_member275696 · Accepted solution]

Hi Guy,

Are there any error details below the line of '*** RWJL_EXIT called'?

And do you see a non-0-kb error log file of the job created around 02:30:01 in %LINK_DIR%\log\<JobServer>\<Repository>? The job may failed ...

Regards,

George

[Former Member · Accepted solution]

Hi Guy,

I can't tell much from that log, as I expected to see more lines/info.

Can you run the job batch file  from command line?

Can you create a new basic job using just with a print function in a script (no variable, no datastore, just the minimum). Schedule it and see if you get any different results.

What version are you working on including the patch level and can you think of anything that has changed in your system (may be a  new Windows security patch was applied, DS was upgraded, etc...).

Can you also monitor the windows event log for errors.

thanks

Nawfal

[Former Member · Accepted solution]

Thank you George & Nawfal,

All i see is just these lines, nothign else below. Also i was able to see windows task schedulers, windwos 2008 has a total diff interface. I also tried manually running the task via windows task scheduler, nothing happened. i see in the log as completed next second itself. This problem started since last one month. before was ok. ON dev box i have 7 jobs they all run fine except this:

I am on version 14.0.2.275 ds designer. as you have suggested will create a simple task and try to schedule it and see.

Also checked table al_sched_info i see active flag 1, that job is active job is getting triggered right on time as per launcher log. but immedeately the RWJL_EXIT call happening. I see lot of them reported that RWJL_EXIT issue, but no where i see a resolution. at some point of time that issue is starting.

here are the log details, no specifics below.

--------------------------
11_29_2012 02:30:00 CRWJobLauncherApp::InitInstance called.

11_29_2012 02:30:01 *** RWJL_EXIT called.

--------------------------
11_29_2012 04:52:26 CRWJobLauncherApp::InitInstance called.

11_29_2012 04:52:27 *** RWJL_EXIT called.

--------------------------
11_29_2012 04:54:24 CRWJobLauncherApp::InitInstance called.
11_29_2012 04:54:26
11_29_2012 04:56:26 *** RWJL_EXIT called.

--------------------------
11_29_2012 04:56:26 CRWJobLauncherApp::InitInstance called.
11_29_2012 04:56:28
11_29_2012 05:03:58 *** RWJL_EXIT called.

--------------------------
11_29_2012 05:03:58 CRWJobLauncherApp::InitInstance called.
11_29_2012 05:04:00

--------------------------
11_29_2012 05:10:00 CRWJobLauncherApp::InitInstance called.

11_29_2012 05:10:01 *** RWJL_EXIT called.
11_29_2012 05:14:00 *** RWJL_EXIT called.

--------------------------
11_29_2012 05:14:00 CRWJobLauncherApp::InitInstance called.
11_29_2012 05:14:03

Thank you all really.

[Former Member · Accepted solution]

Nawfal,

I created a new job with just one print statement, that job is triggered without issues.

So these are old jobs runnign for last 9 months.

What may be the reason why this job isn't gettign triggered.

Could you please me how can i handle this one, i mean should i create a whole complete new job and create a new schedule to see how it works?

Thanks.

[Former Member · Accepted solution]

Guy,

Can you attach the content of .bat &.txt from one of the old problematic jobs and the same for the new job. I want to compare to the difference.

Files can be found in the %LINK_DIR/Log/<job_server>Schedues

or check the path of your jobs in the Windows Task Scheduler>settings

thanks

[Former Member · Accepted solution]

Hello Nawfal, Thank you very much sir.

here is the bat file and txt file of both problem one and teh test one, the test one has nothign just a simple print statement, what i observed is there is a email variable within txt file of problematic one. do you think that may be the cause?

Problematic bat file:
E:\Program Files (x86)\SAP BusinessObjects\Data Services\log\PPHDWP01_01\e0c45a21_0430_425d_9294_f6f14e4151f7_2.bat

bat file content of problematic file:

"E:\Program Files (x86)\SAP BusinessObjects\Data Services/bin/AL_RWJobLauncher.exe"  "E:\Program Files (x86)\SAP BusinessObjects\Data Services/log/PPHDWP01_01/"  "inet:PPHDWP01:3500"  -C "E:\Program Files (x86)\SAP BusinessObjects\Data Services/log/PPHDWP01_01/e0c45a21_0430_425d_9294_f6f14e4151f7_2.txt" " -ScheduleID 2 "
txt file content of problematic file:
-SPPHBOD01 -NsecEnterprise -QBODS_LOCAL -UAdministrator -PQk9hZG1pbjIwMTE  -G"e0c45a21_0430_425d_9294_f6f14e4151f7" -r64000 -T14 -ncollect_cache_stats  -GV"$GV_EMAIL=J01DSEVEV0BtY2guY29tJw;"  -CtBatch -CmPPHBOD01 -CaAdministrator -CjPPHDWP01 -Cp3500
------------------------

Test job empty just print statement within job which is triggered successfully on the same box:
E:\Program Files (x86)\SAP BusinessObjects\Data Services\log\PPHDWP01_01\6045b450_e88d_4c49_9aa9_b404fbe7b95d_5.bat

Bat file content of test job:
"E:\Program Files (x86)\SAP BusinessObjects\Data Services/bin/AL_RWJobLauncher.exe"  "E:\Program Files (x86)\SAP BusinessObjects\Data Services/log/PPHDWP01_01/" "inet:PPHDWP01:3500"  -C "E:\Program Files (x86)\SAP BusinessObjects\Data Services/log/PPHDWP01_01/6045b450_e88d_4c49_9aa9_b404fbe7b95d_5.txt" " -ScheduleID 5"

txt file content of test job which is good:
-R"BODS_LOCAL.txt"  -G"6045b450_e88d_4c49_9aa9_b404fbe7b95d" -r1000 -T14 -nCollectCacheSize    -CtBatch -CmPPHBOW01 -CaAdministrator -CjPPHDWP01 -Cp3500

Please kindly need your advice.

Thanks a lot for the help.

[Former Member · Accepted solution]

Guy,

The difference between the two :

The problematic job has the following extras

-SPPHBOD01 -NsecEnterprise -QBODS_LOCAL -UAdministrator -PQk9hZG1pbjIwMTE  - -r64000 -GV"$GV_EMAIL=J01DSEVEV0BtY2guY29tJw;"

  I think the  problem might be here :

You are using

-NsecEnterprise for  (-NAuthentication Type) this this wrong.

It should be -N<DatabaseType> : Repository database type (ie:  -NOracle).

Perhaps the developer was following an old version of  the admin guide which incorrectly refered to 

-AuthType

[Former Member · Accepted solution]

Nawfal, Thank you boss....

But the repository is sql server based not oracle.

BODS_LOCAL is the repository name on which these jobs are running.

But the jobs are based on multiple datastores db2, oracle and as400.

Kind Regards.

[Former Member · Accepted solution]

Hi,

Please try the following:

Reschedule the problematic job without use password file (un-tick this option) in the "Select job execution parameters"

.

and reschedule the simple job with use password file.

run manually and monitor the log.

thanks

[former_member275696 · Accepted solution]

Guy,

In the command txt file of the test job which is good, there is a '-R' flag. It indicates that the command file is using a password file (BODS_LOCAL.txt) instead of the hard-coded repository connection values for -S, -N, -U, -P.

______

-R: The location and name of the password file.

So have you tried the 'Use password file' option to add the job schedule?

Thanks,

George

[Former Member · Accepted solution]

Hello Nawfal and George, thank you to both of you for providing awsome support on the board.

This job was running since last 8 months, this job only uses a script file, within teh script it is calling various jobs .bat files.

which were created using export execution command option. You are right our repo name is BODS_LOCAL.

There are two jobs: one ini load, second incremental load, if we get any issues with incremental load, we deactivate incremental and then activate initial load... thats how they setup.

Now we had to at somepoint deactivated incremental load and then again reactivated incremental load , in this process, now this scheduler isn't working properly. when i reactivated, may be i should change the string to use password file -R"BODS_LOCAL.txt"  which i didn't do i believe.

I verified within al_sched_info table active flag=1

also verified teh job under task scheduler which is intact and being called, the moment job gets triggered, within the next second

RWJobLauncherApp::InitInstance called. 

11_29_2012 05:10:01 *** RWJL_EXIT called.
11_29_2012 05:14:00 *** RWJL_EXIT called.

and not working.

One problem we have is "use password file check box" is also greyed out, the guys mentioned it was fine until last month since then the use password file chk box is greyed out.

we are in the process of calling consultants to install updates / patches.

I will try today replacing as you suggested the

I am going to replace this:
-SPPHBOD01 -NsecEnterprise -QBODS_LOCAL -UAdministrator -PQk9hZG1pbjIwMTE 

with the following:
-R"BODS_LOCAL.txt" 

and will do a test to night.

Really thank you to both of you.

Kind Regards.

[Former Member · Accepted solution]

Hello George,

Can i replace the following:
-SPPHBOD01 -NsecEnterprise -QBODS_LOCAL -UAdministrator -PQk9hZG1pbjIwMTE 

With this: what is -PLocaleUTF8 this is their for other jobs.

-PLocaleUTF8 -R"BODS_LOCAL.txt"

Thanks.

[Former Member · Accepted solution]

Hello George,

I confirm it is working now. the job triggerdd after i used the -R block use pwd on file.

Thank you George.