I am getting an error using the delete_rule property in a JDL script.
It looks like from the trace that it is treating this property like
a command (like the DEL command?), since the log says that the job
"ELETE_RULE=D" does not exist.

Can you shed any light on this.

Can you post your script? It is hard to figure out what is causing this problem without seeing the code.

: I am getting an error using the delete_rule property in a JDL script.
: It looks like from the trace that it is treating this property like
: a command (like the DEL command?), since the log says that the job
: "ELETE_RULE=D" does not exist.

: Can you shed any light on this.

: Can you post your script? It is hard to figure out what is causing this
: problem without seeing the code.

here is the code, thanks for your help...

; Sample JDL

;
ADD

NAME=HLP523

COMMAND=acuthread.exe -C \\app1\dev\config\batchobj.cfg +E \App1\dev\traces\hlp523.log hlp523.acu

JOB_TYPE=P

ASYNC=Y

SCHEDULE_TYPE=F

FILE=\\APP1\DEV\TRIGGERS\HLP523.TXT

POLLING_INTERVAL=1

DELETE_RULE=D

timeout=1

START_IN=C:\ACUCORP\ACUCBL510\ACUGT\BIN

DESCRIPTION=HLP523 Documentation Consumer
;
SAV

This is weird, I found out that it finds that DELETE_RULE line begins with DEL and so it treats the line as a DEL command instead of a parameter value.

So far I didn't find a good workaround. I've added this as bug report, it should be fixed in the next build.

: here is the code, thanks for your help...

: ; Sample JDL

: ;
: ADD

: NAME=HLP523

: COMMAND=acuthread.exe -C \\app1\dev\config\batchobj.cfg +E
: \App1\dev\traces\hlp523.log hlp523.acu

: JOB_TYPE=P

: ASYNC=Y

: SCHEDULE_TYPE=F

: FILE=\\APP1\DEV\TRIGGERS\HLP523.TXT

: POLLING_INTERVAL=1

: DELETE_RULE=D

: timeout=1

: START_IN=C:\ACUCORP\ACUCBL510\ACUGT\BIN

: DESCRIPTION=HLP523 Documentation Consumer
: ;
: SAV