AutoSys Workload Automation

 View Only
  • 1.  Monitoring disk space

    Posted Jul 30, 2018 02:48 PM

    I have noticed autosys doesn't notify the used space unless it is 4% used over the lower_boundary attribute specified in the job.

     

    I created test jobs according to the lower_boundary value defined in the job, I forcestarted all the jobs and only the 55% job went to success and rest remain in running status, whereas the filesystem used space was 59%

     

    Filesystem Size Used Avail Use% Mounted on
    /dev/mapper/vgapps05-lvxtrdevseq
    411G 227G 164G 59% /apps/xtr/dev/seq

     

    AUTOSYSTEST_55_PERCENT 07/30/2018 12:25:55 07/30/2018 12:25:55 SU 9449380/1 0
    AUTOSYSTEST_56_PERCENT 07/30/2018 12:26:19 ----- RU 9449381/1
    AUTOSYSTEST_57_PERCENT 07/30/2018 12:27:25 ----- RU 9449382/1
    AUTOSYSTEST_58_PERCENT 07/30/2018 12:27:40 ----- RU 9449383/1
    AUTOSYSTEST_59_PERCENT 07/30/2018 12:28:10 ----- RU 9449384/1
    AUTOSYSTEST_60_PERCENT 07/30/2018 12:28:32 ----- RU 9449386/1

     

    sample jil:

    insert_job: AUTOSYSTEST_59_PERCENT job_type: OMD
    machine: test
    owner: test
    permission:
    date_conditions: 0
    description: "test job"
    job_terminator: 1
    alarm_if_fail: 1
    group: DEV
    application: AUTOSYS_TEST
    upper_boundary: 100
    lower_boundary: 59
    inside_range: 1
    disk_drive: /apps/xtr/dev/seq
    disk_format: PERCENT
    disk_space: USED
    monitor_mode: WAIT

     

    why are the job with lower_boundary 56,57,58,59 keep running? am I missing something



  • 2.  Re: Monitoring disk space

    Posted Jul 31, 2018 03:08 AM

    It appears the jobs are waiting for the change to occur since the time it started?

    Try adding the following to the jobs?

    no_change: 1




  • 3.  Re: Monitoring disk space

    Posted Jul 31, 2018 08:53 AM

    Hello Chandru,

     

    I did update the jobs with "no_change: 1" parameter and re-ran the jobs but no luck still the jobs with lower boundary 56,57,58,59 keeps running, whereas the file system utilization is already at 59 percent.

     

    Job Name Last Start Last End ST Run/Ntry Pri/Xit
    ________________________________________________________________ ____________________ ____________________ __ ________ _______
    AUTOSYSTEST_55_PERCENT 07/31/2018 08:46:11 07/31/2018 08:46:11 SU 9457321/1 0
    AUTOSYSTEST_56_PERCENT 07/31/2018 08:46:36 ----- RU 9457322/1
    AUTOSYSTEST_57_PERCENT 07/31/2018 08:47:00 ----- RU 9457323/1
    AUTOSYSTEST_58_PERCENT 07/31/2018 08:47:05 ----- RU 9457324/1
    AUTOSYSTEST_59_PERCENT 07/31/2018 08:47:16 ----- RU 9457325/1
    AUTOSYSTEST_60_PERCENT 07/31/2018 08:47:17 ----- RU 9457326/1
    AUTOSYSTEST_61_PERCENT 07/31/2018 08:47:26 ----- RU 9457327/1
    AUTOSYSTEST_62_PERCENT 07/31/2018 08:47:30 ----- RU 9457328/1
    AUTOSYSTEST_63_PERCENT 07/31/2018 08:47:34 ----- RU 9457329/1
    AUTOSYSTEST_64_PERCENT 07/31/2018 08:47:38 ----- RU 9457330/1



  • 4.  Re: Monitoring disk space

    Broadcom Employee
    Posted Aug 10, 2018 09:34 AM

    Hi,

    You can have the agent do the monitoring.  Please see this link for disk space monitoring.  

     

    Thank you,

    Nitin Pande

    CA Technologies



  • 5.  Re: Monitoring disk space

    Posted Aug 03, 2018 02:56 PM

    ok this is me wondering why you are using AutoSys to monitor disk space? don't your SAs monitor all that? They should.

    yeah i get cybermation has this neat little job_type. But why wouldn't you get your infrastructure guys to do their , um , job? unless you dont have server monitoring ... 

     

     

    Steve C.