Running jobs in command prompt

omario76

Hello,

I'm creating a script to run jobs in command prompt but I can

fin the good sytax to call the jobs. Please fin below the command line

for each job I m trying to run in command line.

dm_DMFilescan :

C:\Documentum\product\7.0\bin\dmbasic

-fC:\Documentum\product\7.0\install\admin\mthd1.ebs -eDMFilescan -h

-docbase_name OCI_INT.OCI_INT -user_name svc_install_xcp -job_id

080016d380000727 -method_trace_level 0

dm_DataDictionaryPublisher :

C:\Documentum\product\7.0\bin\dmbasic

-fC:\Documentum\product\7.0\install\admin\mthd7.ebs -e

eDataDictionaryPublisher  -- -docbase_name OCI_INT.OCI_INT -user_name

svc_install_xcp -job_id 080016d38000074c -method_trace_level 0

dm_QueueMgt :

C:\Documentum\product\7.0\bin\dmbasic

-fC:\Documentum\product\7.0\install\admin\mthd2.ebs -eQueueMgt --

-docbase_name OCI_INT.OCI_INT -user_name svc_install_xcp -job_id

080016d38000072b -method_trace_level 0

dm_LogPurge :

C:\Documentum\product\7.0\bin\dmbasic

-fC:\Documentum\product\7.0\install\admin\mthd2.ebs -eLogPurge  --

docbase_name OCI_INT -user_name svc_install_xcp -job_id 080016d380000728

-trace_level 0

Here is an example of the error message I got each time I try to run a job, I tried different combinations of the commands:

Connected To OCI_INT.OCI_INT

There was a problem, and the program aborted...

QueueMgt Tool was aborted at 9/30/2013 13:02:20.  View the job's report for deta

ils.

Calling SetJobStatus function...

--- Start C:\Documentum\dba\log\000016d3\sysadmin\QueueMgtDoc.txt report output

----

QueueMgt Report For DocBase OCI_INT As Of 9/30/2013 13:02:20

You have one or more bad method argument(s), aborting...

Report End  9/30/2013 13:02:20

--- End C:\Documentum\dba\log\000016d3\sysadmin\QueueMgtDoc.txt report output --

-

Can you give the correct sytax for all the jobs asap.

Regards

Alvaro_de_Andres

Syntax look fine to me, in fact I've just tried running datadictionary on a 6.6 and it works... It is the user you're passing as argument the installation owner? are you running the commands with that user?

Have you checked the method server log? (You should find it in C:\Documentum\dba\log\000016d3\MethodServer)

Try also turning the trace on so you can see where it breaks...