cancel
Showing results for 
Search instead for 
Did you mean: 

batch job - doesn't start

Former Member
0 Kudos

Hi,

I'm using DS 4.0 SP3 and have problem with batch job.

In DataServices Management Console in section where we create schedule for jobs I'm creating new schedule with some job.

But this shcedule doesn't want to execute. When I execute job in DS I can see it in DS Management Console, but when I create schedule - I don't.

Any idea?

Accepted Solutions (0)

Answers (1)

Answers (1)

DayaJha
Active Contributor
0 Kudos

Hi Rad,

Please check this Query in below thread.

Links:

http://scn.sap.com/thread/3235300

http://scn.sap.com/thread/3181220

Data Services and Data Quality: SAP BODS- Running & Scheduling BODS Jobs from Linux Command Line using Third party Scheduler:

Links:

http://scn.sap.com/community/data-services/blog/2012/12/11/data-services-and-data-quality-sap-bods-r...
command-line-using-third-party-scheduler

Hope this will help you as well.

Thanks,

Daya

Former Member
0 Kudos

Hi Daya,

thank you for your help but my situation is a little diffrent.

I created two batch jobs: first one without option 'use password file', and second with 'use passwor file'.

And both of them I can see in task scheduler in windows and the .bat files is in 'C:\Program Files (x86)\SAP BusinessObjects\Data Services\log\JobServerName\Schedules\RepositoryName'

But no one was executed.

In file: 

for first batch job I got: 'CRWJobLauncherApp::InitInstance called.'

for second batch job I got: '

*** RWJL_EXIT called.

*** ERROR: RWJobLauncher failed to connect to CMS. (BODI-1250220)

*** RWJL_EXIT called <180009 : Invalid command line syntax. (BODI-1250107)>

*** ERROR: RWJobLauncher failed to get the repository information. (BODI-1250216)

JOB LAUNCHER ERRORS:

  180002 : Network failure. (BODI-1250100)

  180003 : Schedule service has not been started. (BODI-1250101)

  180004 : Link_Dir is not defined. (BODI-1250102)

  180005 : Trace Message file could not be created. (BODI-1250103)

  180006 : Error Message file could not be created. (BODI-1250104)

  180007 : GUID not found.  Status cannot be returned. (BODI-1250105)

  180008 : No command line arguments were found (causing this dialog). (BODI-1250106)

  180009 : Invalid command line syntax. (BODI-1250107)

  180010 : Can't open command file (see -C option). (BODI-1250108)'

but I think it caused by chacking option with usuing password file (what for we use password file?)

I have sql database on server with instance so I can't use directly IP adress.

My bat file is:

"C:\Program Files (x86)\SAP BusinessObjects\Data Services/bin/AL_RWJobLauncher.exe"  "C:\Program Files (x86)\SAP BusinessObjects\Data Services/log/LPCZ_BO0002_JobServer/" "inet:LPPLBO0002:3501"  -C "C:\Program Files (x86)\SAP BusinessObjects\Data Services/log/LPCZ_BO0002_JobServer/Schedules/DI_LOCAL_REPO_PROD_4_LPCZ/6718435b_5d41_4849_be6d_519129ca947a_12.txt" " -ScheduleID 12 "

DayaJha
Active Contributor
0 Kudos

Hi Rad,

Please refer the below URL regarding batch Job Scheduling.

Links:

http://scn.sap.com/community/data-services/blog/2012/08/22/sap-bods--running-scheduling-bods-jobs-fr...

Or You can also refer the below thread regarding Data Services 4.1 repository schedules:

Links:

http://scn.sap.com/thread/3235300

Hope this will help you as well.

Thanks,

Daya