Did you every figure out how to make cc=1 a successful run? I need the CCF (Condition Code Failure) field to be NO for a CC=1. This is being counted as an unsuccessful execution, even though a CC 0 or 1 is considered successful for this FILE_TRIGGER WOB. I even tried to use CCCHK statements to make CC=1 acceptable, but YES still appears in the CCF field and this is counted as a failure in my reports. Here is the FILE_TRIGGER wob definition I used.
FILE_TRIGGER JOBNAME.FILECHK
RUN MON TUE WED THU FRI
CCCHK RC(0:1) OK
CCCHK RC(2:4095) FAIL
EARLYSUB 15:00
RELEASE ADD(JOBNAMEA) COND(RC(0))
RELEASE ADD(JOBNAMEA.BYPASS) COND(NOT RC(0))
AGENT AGENTNAME
USER USERID
MAXRUNTIME=0
FILENAME +
'\\SERVERNM\apps\ears\*.RPLY' EXIST
ENDJOB
JOBNAME WT APPL APPLGE
RC CCF AGENT START
NAME DATE
JOBNAMEA.FILECHK FM AMVRC01 3342
1 YES SERVERNM TUE 9JUL1
JOBNAMEA.BYPASS AMVRC01 3342
0 NO TUE 9JUL1
------------------------------
IT Systems Engineer Sr.
Progressive Insurance
Ohio
------------------------------
Original Message:
Sent: 12-10-2015 11:48 AM
From: Don Roberts
Subject: FILE_TRIGGER exitcode
How can I force a File Trigger to accept a Condition Code 1 and not be listed as failed?
EXITCODE 1 SUCCESS does not work.