CA Workload Automation ESP Edition

FILE_TRIGGER JOBA CONDITIONAL - statement usage

  • 1.  FILE_TRIGGER JOBA CONDITIONAL - statement usage

    Posted 08-20-2019 01:58 PM

    The addition of ptf RO92035 makes it possible to bypass an ESP file trigger by adding the "CONDITIONAL" verb at  the end of the file trigger statement (see examples below).

    This is an important feature as we do not always have a file available for a file trigger.  When this happens, we set an abandon sub to the successor job that uses the file and continue the job stream.  The file_trigger bypasses at the end of the proc conclusion.
    The dueout exec stops the file_trigger going into overdue status.

    Paul O'Flaherty - State of Connecticut - Technical Analyst 2.

    860-622-2468


    FILE_TRIGGER DCT4501T CONDITIONAL       
    /* DESC=Utility to monitor a creation of a file.
    RUN ANY
    AGENT IMPACTSTAG1
    FILENAME E:\readmeX.txt   

    DUEOUT EXEC 23:59
    RELEASE ADD(DCT4501A)
    ENDJOB
    JOB DCT4501A
      CCCHK RC(1:4095) FAIL
      ABANDON SUB 14:25          
      EARLYSUB 14:27
      RUN ANY
      RELEASE ADD(DCT4501B)
    ENDJOB
    JOB DCT4501B
      CCCHK RC(1:4095) FAIL
      ABANDON SUB 14:25               
      EARLYSUB 14:27
      RUN ANY
    ENDJOB

    48     0 DCT4501A                     11.45 TODAY COMPLETED AT 11.45 20 A

    48     0 DCT4501B                     11.45 TODAY COMPLETED AT 11.45 20 A

    48     0 DCT4501T                     11.45 TODAY COMPLETED(F) AT 11.47 2          without the conditional statement, the file_trigger has to be force completed.

    49     0 DCT4501A                     11.47 TODAY COMPLETED AT 11.47 20 A

    49     0 DCT4501B                     11.47 TODAY COMPLETED AT 11.47 20 A

    49     - DCT4501T                     11.47 TODAY BYPASSED                                        with the conditional statement, it bypasses at the end of the event proc.

    Hope this helps.