How do you disable "Use Collected Statistics" when triggering a BODS job using RUN_BATCH_JOB web service?

[Former Member]

I am triggering a BODS jobs using RUN_BATCH_JOB, how do you disable "Use Collected Statistics" for the job?

The issue I am having is it keeps changing the CACHE TYPE to IN-MEMORY when the dataflow is set to PAGEABLE because of not being able to tell the triggered job to not use collected statistics.

RUN_BATCH_JOB input parameters are:

     - jobName, repoName, jobServer, serverGroup, globalVariables

     - jobParameters: job_system_profile, sampling_rate, auditing, recovery, job_server, trace[], distribution_level, substitutionParameters

     There is no parameters for telling the triggered job to "use collected statistics" or not.

What i've tried:

1. I've set the job properties->Execution Options->User collected statistics to unchecked as the new default

2. When I trigger a job manually in the Data Services Designer or the Data Services Management Console the default value for "use collected statistics" is unchecked. When the job runs it uses Cache Type PAGEABLE

3. When I trigger the job using the BODS web service RUN_BATCH_JOB it says it's switching Cache Type to IN-MEMORY which means the job is still defaulting to use collected statistics.

So how do use the RUN_BATCH_JOB web service and tell it not to use collected statistics?

We are using version 14.0.3.451

Rob O.

[former_member211387]

Hi Rob,

Try the following.

Step 1. Stop the webservice

Step 2. On the BODS Designer window right click on the Realtime job that is used for the webservice and select properties. This will open the properties dialog box as shown below.

In the properties window, un-check the "Use Collected Statistics" checkbox. Click on OK and Save the job.

Step 3: Restart the webservice

This should prevent the job from using collected statistics.

Do let me know the outcome.

kind regards

Raghu

[Former Member]

Hi Raghu,

Can you provide details on how to stop/start the web service?

Do you mean from within the Data Service management Console that I need to select the RUN_BATCH_JOB web service, from the web services configuration tab, and remove it then re-add it, to stop and start it? 

Regards,

Rob O.

[former_member211387]

Hi Rob,

Yes. if your webservice is indeed called the RUN_BATCH_JOB, then stop and start this service. This will overwrite the parameters and I think will resolve your problem too.

kind regards

Raghu

[Former Member]

Hi Raghu,

FYI: The RUN_BATCH_JOB web service is part of BODS, provided by SAP. The parameter in question is part of the job I am trying to trigger using this web service. Each BODS job you create has execution options for setting the defaulting value for 'USE COLLECTED STATISTIC' when you manually trigger a job. We are not publishing specific job's as web services but rather using the RUN_BATCH_JOB web service for triggering BODS job. So Stopping this web service, changing the execution option, and then enabling the web service would have not affect on the RUN_BATCH_JOB web service as it is not associate with the jobs it triggers.

Regards,

Rob O.

[former_member211387]

Hi Rob,

I stand corrected. I can see two options in this case.

Option 1. Stop and Start the entire webserver service for the Data Services Management Console. This would re-initialise the services. However, the RUN_BATCH_JOB webservice has very little entries on the WSDL. So this options may not work.

Option 2. You can enable a batch job as a webservice in its properties as shown below.

You can make select the relevant execution properties for the batch job and then call this job which will appear as a webservice in the Management Console.

You can use this webservice instead of the run_batch_job service to call the job. Any execution properties you setup for this job should cascade through the WSDL.

I couldnt test this as I'm stuck with another issue work. So please have a go and let me know me know if this works.

kind regards

Raghu

[Former Member]

Hi Raghu,

Unfortunately this is not an option. We don't want to have to enable all our jobs as web services to run them. We want to be able trigger them dynamically by name from a control table.

Regards,

Rob O.

[former_member200473]

Hi Rob,

i assume for executing job through Webservices , you should be using .bat file which will be generated using export executing command.( as per my understanding).

Here while doing export execution command just uncheck use collected statistics and then do export execution command.

Please try and update the thread.

Regards,

Shiva Sahu

[Former Member]

Hi Shiva,

The RUN_BATCH_JOB webservice is different from export .BAT file. From what i've read the export does have the use collected statistics option. However, for webservices in BODS the WSDL does not contain the required setting option.

The WSDL only allows the following parameters to be supplied:

     - jobName, repoName, jobServer, serverGroup, globalVariables

     - jobParameters: job_system_profile, sampling_rate, auditing, recovery, job_server,

       trace[],distribution_level, substitutionParameters

Thank you for taking the time to offer a suggestion though...

Regards,

Rob O.