AutoSys Workload Automation

  • 1.  UI not displaying data that is actually there

    Posted Oct 30, 2015 03:54 PM

    We recently migrated from an old Autosys version to 11.3

     

    I use a script to copy a schedule from our production environment to our dev environment.

     

    I basically use autorep to retreive job definitions corresponding to a search pattern from the DEV environment. Then I keep only the first line of each:  insert_job:AAAAAAAAAA job_type: AAA

    Once this is done I replace insert by delete and jil < the results to delete everything in the DEV environment. This is done to ensure the schedule is deleted from the dev environment completely.

     

    Then I use a *.jil file that contains the production environment definitions (produced daily), I search and replace the relevant bits so the schedule runs on the dev servers and to respect job name nomenclature. Once this is done I now jil < replaced.jil

     

    On the surface this seems to work. Using the CA Workload Automation UI I can do a quick search to find all relevant boxes and command/filewatcher jobs. However when I click many of the box names I get a No matches for the search criteria message and no data is available for that box nor its children.

     

    In some cases even if I manage to display a command job name in the UI by searching for it using wildcards when I click the job name I get the same result: No matches for the search criteria

     

    This is happening from a UNIX environment and uses a character set that supports accented characters.

     

    I don't know what's causing the problem.



  • 2.  Re: UI not displaying data that is actually there
    Best Answer

    Posted Nov 11, 2015 06:59 PM

    Can you get the same relevant information via autorep? Ex: "autorep -J <box_name>"

     

    Also be sure to check that your WCC is up to date: CA Workload Control Center Solutions & Patches - CA Technologies

    If autorep displays the information, but WCC does not, then it might be helpful to open a support issue.

    If autorep also does not display the information, then there is likely something wrong with your jil input file.