autocalasc is the utility that helps maintain the calendars in Autosys Syntax: autocalasc Export Calendar: autocalasc -E filename -s calendarname. Once testing is done with AutoSys one should change the default refresh interval for AutoSys. This is so there is less querying to the DB. When AutoSys goes from dual mode to single mode, always run the autobcp command before bringing AutoSys back to dual mode/High Availability. Default behavior for stdout is to always appends.
AutoSys Log Files Location Example
Any job you create in Autosys should specify values for std_out_file and std_err_file because it is important in case if something goes wrong with AutoSys jobs. If you don’t specify then AutoSys job sends anything to standard out or standard error, then the output will go to /opt/CA/r11/agent/out/univagent.out. As this is default location and not preferable because the /opt/CA file system on most of our servers has only 1 GB of space. When it fills up every Autosys job will fail and you will not see anything. These files are owned by root, so you will not be able to delete them without administrator assistance.
If you do not want to see any output and your job is running on a Unix server then you can use /dev/null to have the output discarded.
To have unique file generated each time when you run your job, you can use the following variables:
| value | Windows | Linux |
| job name | %AUTO_JOB_NAME% | $AUTO_JOB_NAME |
| instance id | %AUTORUN% | $AUTORUN |
Below are examples:
Linux:
- std_out_file: /opt/apps/dev/myTeam/log/$AUTO_JOB_NAME.$AUTORUN.stdout
- std_err_file: /opt/apps/dev/myTeam/log/$AUTO_JOB_NAME.$AUTORUN.stdout
Windows:
- std_out_file: D:optappsdevmyTeamlog%AUTO_JOB_NAME%.%AUTORUN%.stdout
- std_err_file: D:optappsdevmyTeamlog%AUTO_JOB_NAME%.%AUTORUN%.stdout
Sample JIL file with log files attached: