topic Re: DataFlux job fails to run in windows batch file in SAS Data Management

DataFlux job fails to run in windows batch file

anioannides — Thu, 02 Aug 2018 13:16:41 GMT

Hi,

We are trying to deploy a windows batch file to schedule a dataflux job. We followed the guide and answers from similar threads and we are using the command:

call C:\SAS\SASHome\DataFluxManagementStudio\2.7\bin\dmpexec.cmd -j "C:\SAS\SASData\ProductionRepository\Files\batch_jobs\Profiling_Master_Job.djf" -l "C:\Users\1000154\Desktop\Test.log"

However we are receiving the following error shown in the attached screenshot.

Could anyone please help us understand what is the error and why we get it?

Thank you in advance,

Andreas Ioannides

Re: DataFlux job fails to run in windows batch file

RonAgresta — Mon, 06 Aug 2018 11:44:46 GMT

I'm going to assume that when you run the job interactively it works OK. Have you considered looking at what username is being used to run from the command line? It could be that one or more directories used or referenced by the job are available to the user running interactively but not to the user whose credentials are being used for the batch call.

Ron

Re: DataFlux job fails to run in windows batch file

anioannides — Tue, 07 Aug 2018 07:04:53 GMT

Hi thank you for your reply. The same user who runs the jobs interactively, is also running the batch file.

Re: DataFlux job fails to run in windows batch file

audrey — Tue, 07 Aug 2018 07:32:30 GMT

Hi,

Can you send the full text of the ERROR messag ein the log file?

Thanks,

Audrey

Re: DataFlux job fails to run in windows batch file

anioannides — Wed, 08 Aug 2018 08:42:42 GMT

Hi,

I'm posting a screenshot as unfortunately i cannot copy any text from the server.

Re: DataFlux job fails to run in windows batch file

VincentRejany — Mon, 20 Aug 2018 08:08:13 GMT

According to the screenshot, your job is running a data profiling node. Therefore you need to specify the Repository in which the data profiling has to take place with the following option:

-b "REPOSITORY=TestingRepos" i.e., the repository in which the job should run

You can find more info here.

Regards

Vincent