Autosys Self Help

Autosys Prod GUI: https://autosys.oit.umn.edu/wcc/ui/Login.html

Autosys TST/QAT GUI: https://autosys-tst.oit.umn.edu/wcc/ui/Login.html

To access the GUI, you must be on Cisco Any Connect VPN, or on campus behind the firewall.

Autosys Job Statuses Index

• Failure: Job or box has failed.
• Success: Job or box has completed successfully.
• Running: Job or box is currently running.
• Starting: Only flashes briefly on the screen as job transition from activated to running.
• Activated: When a box starts running, the jobs contained in the box go to the Activated status before they start.
• Terminated: Job or box was manually killed or set to terminate box if a job fails.
• Inactive: Job or box is new and does not have a previous run status, or the box was terminated, and the job was activated losing its previous run status. This will not prevent the job from running the next scheduled run.
• Restart: This option is to rerun the job upon failure set in Autosys/PeopleSoft.
• On Hold: This is a hard stop, preventing the job from running until the job or box is removed from the hold status. If the job or box passes its scheduled time, it will start immediately.
• On Ice: Bypasses the scheduled time. Autosys sees this as a success for dependent jobs or boxes. (Do not use inside a box because it messes up the dependency sequence. Do not use it on a box, if the box has a start condition on another box and has a dependent box.)
• On No Execution: This is the preferred use if you do not want a box or job to run (When setting a box on no execution, the jobs inside the box will also go on no execution. If you try to take a job inside a box that is On No Execution or Off No Execution, it will not come off until the entire box is taken Off No Execution).
• Pending Machine: The Autosys agent is offline meaning that Autosys cannot connect to server to initiate job updates.

Autosys

Autosys Production uses a red GUI login.

Autosys TST/QAT uses a yellow GUI login.

Autosys is laid out the same in all environments. The following screenshots are mostly from TST/QAT.

The first screen you will see after logging in is the Dashboard. This view will allow you to access predefined monitoring settings.

If you double-click on any name in the view, then Autosys will navigate to the Monitoring tab.

Navigate from the Summary tab to the Jobs and Alerts tab, so you can view the jobs that coincide with the Views' settings that you are looking at.

If you double-click on a job or box in the monitoring screen, then a popup window will open with that job's information.

Please note that beyond the main screen you will lose the color borderson the GUI that denote what environment you are in. If you double-click on a specific job in a box, you can see Job Details, DependentJobs, and Starting Conditions. If you click select on the job you are interested in, you can use the Action dropdown to see details about the Log File, Trace File, or Error Logs.

Changing Job Statuses

Most of our inspection and updating batch jobs statuses work is done in the Quick View tab.

Access your departmental Self-Help training job. Remember, all job names are case sensitive. The first four characters are your departmental group. In this demonstration, we are using CSSR. The fifth character will be the environment code such that T stands for Test, Q stands for QAT, and P stands for Production. The next sequence that follows is the job time to schedule and order that the job should run in. The next section is the name of the job that your department requested. The final portion of the naming convention is as follows: .BX for boxes, .PS for PeopleSoft jobs, .CJ for Command Jobs, .FT for File Transfers or Watches, and .WF for Boomi Work Flows. So, for this demonstration we are using the name CSSRT.000.SelfHelp_Training.BX. You can use % or * as wild cards. You can also use ? as an individual character wild card.

Select the box or job you want to update and use the dropdown to select the action you want to perform. See the Autosys Job Statuses Index above, and then click Go.

This will popup a confirmation screen that will show what action is performed and what jobs are being affected. If the information is correct click Yes. If the wrong job names are listed or there are jobs that you do not want to update, click No. From here you can redo your jobs selection and action requested.

After the task has been completed, you will need to click the blue Refresh tab in the top right corner of the screen to see if the actions were performed correctly.

The Actions you can select are:

• Start: not typically used since if the job did not start per schedule or something is wrong.

• Force Start: causes the job or box to start running even if the start time or condition has not been met.

• On Hold: causes any job not currently running to be held. This is a hard hold meaning the job cannot run until Off Hold.

• Off Hold: any job currently On Hold will come Off Hold. If the start time or conditions have been met, then jobs will run immediately.

• On Ice: box will ignore the schedule and the job will not run; however, anything dependent on the box or job will treat this as a success and can cause other boxes or jobs to run out of sequence.

• Off Ice: box will return to being back in the schedule. If the box has passed its normal start time, then it will run on its next scheduled day. If processes are needed for the current day, then the box will need to be Force Started.

• On No Execution: box will go through the jobs in sequence but will not trigger PeopleSoft or Command jobs. These jobs will not process but will run in 1 second for each step and claim they are successful. (This is the preferred way to [NOT]{.underline} run most boxes or jobs since it prevents the selected jobs from making any batch updates.) If you take a box off of No Execution passed its normal start time you will need to Force Start it to run the day's processes.

• Off No Execution: returns the box or job back to normal processing. (If a box is On No Execution, none of the individual jobs inside the box can be taken Off No Execution).

• Kill: this will terminate the box or job that you select regardless whether it is running or not.

• Send Event: this will allow users to do any of the previous actions listed or Change Status. For example, if you have manually run a failed job in PeopleSoft, you can now update the failed Autosys job to success. This would allow downstream jobs to continue their batch flow. This is also how you can force a stuck job status, that killing will not change or you cannot place on hold. (This occasionally happens in TST/QAT with boxes set On No Execution, a job will stick as running.) Changing the status to Inactive will allow you to remove the stuck status.

• Comment: not being used.

• Set Global: not being used.

Calendar Updates

There are 3 types of calendars in use.

Standard Calendars: use the same name as the Autosys box name but instead of ending in .BX it ends in .SC. This is the standard and preferred way of controlling jobs' schedules. This is the calendar you have access to update through Self-Help. These need to be continuously updated to stay correct and can extend for up to ten years into the future. JST will continue to be responsible for creating or deleting Standard Calendars and business teams will continue to be responsible for maintaining their Standard Calendars.

Extended Calendars: use an abbreviated command to force a job to run on a set day, such as the Xth day of the month, 1^st, 3^rd, or last. JST set these up per departmental request. Business teams will need to open a TDX ticket to request changes to their Extended Calendars.

Exclusion Calendars: turn off scheduled jobs to allow for planned outage windows. JST maintains these calendars in accordance with university policy and leadership directives.

To update calendars, click the Quick Edit tab. In the Type dropdown, select the Calendar option. In the Name field, enter the case-sensitive name you are looking for and click Go.

Calendars are set up to display 24 months at a time. You do need to set and confirm the Starting Month and Starting Year in the Calendar. Finally, then click Go.

For simple updates you can click on the days you would like to schedule. (Green means the day was already scheduled. The date will turn light blue as you select them.) If something has been scheduled and you click on it again, you can de-select it. In the month, clicking on Mo column will select all Mondays in the month. Once you have the days selected, click on Commit to save.

The selected days will then turn green and you will have a confirmation message on the top of the screen.

If you need to do a prolonged schedule scroll down to Generate Days section. You can change the Date Range from All days in year to All days in range in the dropdown menu. Update the Start and End fields so that the jobs will run in that range. Select the Occurrence button. (Typically, the Every option is the standard workflow.) Next select the Any Day option from the Days dropdown menu. If the job runs 7 days a week, you can select Weekday for Monday through Friday, or choose the Specific day option to select the days you want.

Once you have the settings you want, click Apply Rules to generate a popup display named Generate Days. Check the settings to confirm the month and starting year that you are looking at.

If it is correct in the popup, then select Apply to move those dates up to your calendar. Verify all dates are correct. Click Commit to save.