AutoSys Workload Automation

Text File Reading and Monitoring job

  • 1.  Text File Reading and Monitoring job

    Posted Mar 11, 2019 04:25 PM

    Hi,

    Currently we have an issue where we sporadically miss a run of an interval application that runs every 1 hour. It only happens to 1 application. CA said this is fixed so we should upgrade.  We are starting to plan our upgrade to R12.2 but in the meantime to catch the error I would like to set up a Text File Reading and Monitoring job to look for the error.

     

    DI_ODS_RTA runs every 1 hour

    errors.txt log has several days of information so when we miss a run the error is in the log for days. 

    tracelog.txt - typically has a few hours of data

     

    Text File Reading and Monitoring job

    • I cannot simply watch for the whole errors.txt or tracelog.txt files because of the amount of data in the files. If we miss 1 run the next hour the error is still going to be in the file from the prev run.
      • Date/time – I don’t know how to make this option work.
        • I want to be able to tell if we get ‘is invalid and was ignored’ this error on the top of every hour HH:00.
      • Line – first and last line - I would really need to be able to search last x lines. Not a specific line range.
      • ALERT - execTrigger("C80001.XX_SHARON6","add"," ","NOHOLD");     - in prod this would trigger the DI_ODS_RTA flow
      •  
      • When I found the error in the errors.txt log I found I can only grep on ‘is invalid and was ignored’, if I grep on appl.gen it isn’t found. 
      • ERROR

        uxprd080:/opt/dseries/WA/logs

        c80001> grep 'is invalid and was ignored' errors.txt

        20190212 09:00:09.778 [essential] [ERROR] DM: [2019-02-12_09:00:09.778] The AFM . . WA_PROD SCHEDULER /MAIN/DI_ODS_RTA.50121/# Appllump .  Userid(node.SCHEDULER) AFMCount(30)
      • DB53BA783F8EFC1E9806FB5586F45DD66BFD37B38F864A121E93782409038431C08C6E0941E04B is invalid and was ignored.