- Autosys Extended Calendar Definition
- Autosys Extended Calendar Conditions
- Autosys Extended Calendar Jil Example
- Autosys Extended Calendar Keywords
- Autosys Extended Calendar 2019
Are you interested in pursuing your educational dreams? Take the necessary admissions steps to make those dreams a reality at Clarion University. If you have an Autosys web portal that allows you to import a calendar from a file, you can define an extended calendar inside a file. For the condition attribute of the extended calendar, you can specify a day of the month with MNTHD#nn, where nn is the nnth day of the month. The extended calendar. Autosys Extended Calendar needed Is there any way to create an extended calendar in Autosys that will include the last Friday of the month AND the 8 business days before that Friday? I know that this will give me the last Friday of the months that I need. Fri#L AND (jan or apr or jul or oct). Autocalasc is the utility that helps maintain the calendars in Autosys Syntax. Administer Extended Calendar. 3 Administer Cycle. 4 List all Calendars. Unicenter AutoSys JM is an automated job control system for scheduling, monitoring, and reporting. These jobs can reside on any Unicenter AutoSys JM -configured machine that is attached to a network. These jobs can be a UNIX script, java program or any other program which can be invoked from shell.
This guide will be helpfull in giving basic idea about what autosys is, defining jobs to AutoSys, monitoring and managing jobs.
Introduction to Autosys:AutoSys is an automated job control system for scheduling, monitoring, and reporting. These jobs can reside on any AutoSys-configured machine that is attached to a network.
An AutoSys job is any single command, executable, script, or Windows batch file. Each AutoSys job definition contains a variety of qualifying attributes, including the conditions specifying when and where a job should be run.
An AutoSys job is any single command, executable, script, or Windows batch file. Each AutoSys job definition contains a variety of qualifying attributes, including the conditions specifying when and where a job should be run.
Defining Jobs :
There are the two methods you can use to create job definitions:
■ Using the AutoSys Graphical User Interface (GUI).
■ Using the AutoSys Job Information Language (JIL) through a command-line interface.
Autosys Jobs:
- Job Types and Structure :
There are three types of jobs: command, file watcher, and box.
As their names imply, command jobs execute commands, box jobs are containers that hold other jobs (including other boxes), and file watcher jobs watch for the arrival of a specified file.
In the AutoSys environment, the box job (or box) is a container of other jobs. A box job can be used to organize and control process flow. The box itself performs no actions, although it can trigger other jobs to run. An important feature of this type of job is that boxes can be put inside of other boxes.
Default Box Job Behavior:
Some important rules to remember about boxes are
Some important rules to remember about boxes are
- Jobs run only once per box execution.
- Jobs in a box will start only if the box itself is running.
- As long as any job in a box is running, the box remains in RUNNING state; the box cannot complete until all jobs have run.
- By default, a box will return a status of SUCCESS only when all the jobs in the box have run and the status of all the jobs is 'success.
- By default, a box will return a status of FAILURE only when all jobs in the box have run and the status of one or more of the jobs is 'failure.'
- Unless otherwise specified, a box will run indefinitely until it reaches a status of SUCCESS or FAILURE.
- Changing the state of a box to INACTIVE (via the sendevent command) changes the state of all the jobs in the box to INACTIVE.
- Job States and Status :
AutoSys keeps track of the current state, or status, of every job. The value of a job’s status is used to determine when to start other jobs that are dependent on the job. The job status is displayed in the job report generated by the autorep command, and in the job report you can view in the Job Activity Console
Following are the status of Autosys jobs:
- INACTIVE : The job has not yet been processed. Either the job has never been run, or its status was intentionally altered to “turn off” its previous completion status
- ACTIVATED :The top-level box that this job is in is now in the RUNNING state, but the job itself has not started yet.
- STARTING : The event processor has initiated the start job procedure with the Remote Agent.
- RUNNING : The job is running. If the job is a box job, this value simply means that the jobs within the box may be started (other conditions permitting). If it is a command or file watcher job, the value means that the process is actually running on the remote machine.
- SUCCESS : The job exited with an exit code equal to or less than the “maximum exit code for success.” By default, only the exit code “0” is interpreted as “success.” If the job is a box job, this value means that all the jobs within the box have finished with the status SUCCESS (the default), or the “Exit Condition for Box Success” evaluated to true
- FAILURE : The job exited with an exit code greater than the “maximum exit code for success.” By default, any number greater than zero is interpreted as “failure.” AutoSys issues an alarm if a job fails
- TERMINATED : The job terminated while in the RUNNING state. A job can be terminated if a user sends a KILLJOB event or if it was defined to terminate if the box it is in failed. If the job itself fails, it has a FAILURE status, not a TERMINATED status. A job may also be terminated if it has exceeded the maximum run time (term_run_time attribute, if one was specified for the job), or if it was killed from the command line through a UNIX kill command. AutoSys issues an alarm if a job is terminated.
- RESTART : The job was unable to start due to hardware or application problems, and has been scheduled to restart.
- QUE_WAIT : The job can logically run (that is, all the starting conditions have been met), but there are not enough machine resources available.
- ON_HOLD : This job is on hold and will not be run until it receives the JOB_OFF_HOLD event.
- ON_ICE : This job is removed from all conditions and logic, but is still defined to AutoSys. Operationally, this condition is like deactivating the job. It will remain on ice until it receives the JOB_OFF_ICE event.
The difference between 'on hold' and 'on ice' is that when an 'on hold' job is taken off hold, if its starting conditions are already satisfied, it will be scheduled to run, and it will run. On the other hand, if an 'on ice' job is taken 'off ice,' it will not start, even if its starting conditions are already satisfied. This job will not run until its starting conditions reoccur.
The other major distinction is that jobs downstream from the job that is 'on ice' will run as though the job succeeded. Whereas, all dependent jobs do not run when a job is on 'on hold'—nothing downstream from this job will run.
- Starting Parameters :
AutoSys determines whether to start or not to start a job based on the evaluation of the starting conditions (or starting parameters) defined for the job. These conditions can be one or more of the following:
■ Date and time scheduling parameters are met (it is or has passed the specified date and time).
■ Starting Conditions specified in the job definition evaluate to true.
■ For jobs in a box, the box must be in the RUNNING state.
■ The current status of the job is not ON_HOLD or ON_ICE.
Every time an event changes any of the above conditions, AutoSys finds all the jobs that may be affected by this change, and determines whether or not to start them.
sample jil code / Writing jil code:
Zero tolerance 2015 streaming. jil = Job information language
When using JIL to create a job definition, you enter the jil command to display the JIL prompt.
When using JIL to create a job definition, you enter the jil command to display the JIL prompt.
Runs the Job Information Language (JIL) processor to add, update, and delete AutoSys jobs, machines, monitors, and reports. Also used to insert one-time job override definitions.
-------------------------------------------------------------------------------------------------
/* ----------------- SAP_UAT_MU03_C ----------------- */
insert_job: SAP_UAT_MU03_C job_type: c
insert_job: SAP_UAT_MU03_C job_type: c
command: /local/SAP/processCheckUAT.sh Ppsspp gold emulator for pc 32 bit free download pc windows.
machine: MU03-UAT
owner: admin@MU03-UAT
permission: gx,wx,mx,me
days_of_week: all
start_times: '15:00, 14:00'
description: 'Job used for Run testing of process'
alarm_if_fail: 1
max_exit_success: 1
-------------------------------------------------------------------------------------------------
The above example is a simple jil code of autosys which we have to write if we want any particular job to be thru autosys.
-------------------------------------------------------------------------------------------------
The above example is a simple jil code of autosys which we have to write if we want any particular job to be thru autosys.
To Insert a new JIL code :
issue command 'jil'
bash-3.00$ jiljil>>1>
'The following prompt will appear' copy paste the jil code u have made example of jil code below......
At the end the 'C' or 'B' determines if the job is box job or child job.
if the jil is inserted properly successfull message will come if any errors are there the jil code contains some errors.
if successfull exit;
2. Other way is to create a temp file named temp.jil which contains jil code on autosys server: give command.
issue command 'jil'
bash-3.00$ jiljil>>1>
'The following prompt will appear' copy paste the jil code u have made example of jil code below......
At the end the 'C' or 'B' determines if the job is box job or child job.
if the jil is inserted properly successfull message will come if any errors are there the jil code contains some errors.
if successfull exit;
2. Other way is to create a temp file named temp.jil which contains jil code on autosys server: give command.
![Autosys extended calendar tutorial Autosys extended calendar tutorial](/uploads/1/1/9/7/119741239/901029516.png)
bash-3.00$ jil<>
Functional Listing of AutoSys Commands :
This section lists which AutoSys commands to use for specific tasks. All commands are for both Windows and UNIX, unless otherwise specified.
- Accessing Sybase : xql
- Checking System Status : autoflags
autoping
autosyslog
chase chk_auto_up - Converting cron to JIL (UNIX Only) : cron2jil
- Defining AutoSys Jobs or Machines : jil
- Defining Calendars : autocal, autocal_asc
- Reporting Job Status : autorep
autostatus - Starting AutoSys (UNIX Only) : eventor
- Stopping AutoSys : sendevent
Using Autorep command:
Function
Reports information about a job, jobs within boxes, machines, and machine status. Also reports information about job overrides and global variables.
Syntax
autorep {-J job_name -M machine_name -G global_name} [-s -d -q -o over_num] [-r run_num]
Reports information about a job, jobs within boxes, machines, and machine status. Also reports information about job overrides and global variables.
Syntax
autorep {-J job_name -M machine_name -G global_name} [-s -d -q -o over_num] [-r run_num]
autorep -J (job name here)
This will display a list of jobs with complete details with box/jobname, last/latest run date & time, status, exit code, etc.
Viewing JIL code for any Autosys job
Viewing JIL code for any Autosys job
autorep -J (job name here) -q
To obtain the underlying JIL (Job Interaction Language) source code for any Autosys job, run command:
To obtain the information of previous runs
autorep -J (job name here) -r (No of runs back) example : autorep -J (job name here) -r 1
would generate a report for the job run one runs back
-------------------------------------------------------------------------------------------------
Status Abbreviations
The following table lists the abbreviations used in the ST (status) column of the autorep report, and gives the status for each abbreviation.
AC - ACTIVATED
FA - FAILURE
IN - INACTIVE
OH - ON_HOLD
OI - ON_ICE
QU - QUE_WAIT
RE - RESTART
RU - RUNNING
ST - STARTING
SU - SUCCESS
TE - TERMINATED
Status Abbreviations
The following table lists the abbreviations used in the ST (status) column of the autorep report, and gives the status for each abbreviation.
AC - ACTIVATED
FA - FAILURE
IN - INACTIVE
OH - ON_HOLD
OI - ON_ICE
QU - QUE_WAIT
RE - RESTART
RU - RUNNING
ST - STARTING
SU - SUCCESS
TE - TERMINATED
-------------------------------------------------------------------------------------------------
sendevent:
sendevents to AutoSys for a variety of purposes, including starting or stopping AutoSys jobs, stopping the Event processor, and putting a job on hold. This command is also used to set AutoSys global variables or cancel a scheduled event.
sendevent is normally used with '-E' & -J option
-J job_name : Specifies the name of the job to which the specified event should be sent. This option is required for all events except STOP_DEMON, COMMENT, ALARM, or SET_GLOBAL
-E event :Specifies the event to be sent. This option is required. Any one of the following events may be specified:
- STARTJOB
- KILLJOB
- DELETEJOB
- FORCE_STARTJOB
- JOB_ON_ICE
- JOB_OFF_ICE
- JOB_ON_HOLD
- JOB_OFF_HOLD
- CHANGE_STATUS
- STOP_DEMON
- CHANGE_PRIORITY
- COMMENT
- ALARM
- SET_GLOBAL
- SEND_SIGNAL
Following are the example of sendevent command frequently used.
____________________________________________________________________
To start or force start a job manually using sendevent :
sendevent –E FORCE_STARTJOB -J 'Job Name Here'
sendevent -E STARTJOB -J 'Job Name Here'
To put jobs on OFF ICE or ON ICE :
sendevent -E OFF_ICE -J 'Job Name Here'
sendevent -E ON_ICE -J 'Job Name Here'
______________________________________________________________
autostatus: Reports the current status of a specific job, or the value of an AutoSys global variable. Ex: autostatus -J job_name, -S instance
This article explains how to manage calendars and cycles using Quick Edit.
This article explains how to manage calendars and cycles using Quick Edit.
You can create a standard calendar to define specified dates on which jobs should run.
- Select the appropriate server from the Server drop-down list and click the Calendar link.
- Define your calendar by performing the following actions:
- If using only CA AE 11.3.6 SP2 (and any later versions), the limit of up to 64 characters applies.
- Select the month or year from the drop-down lists and click Go to navigate the calendar and select days.
- Perform one of the following actions:
- Click individual days in the calendar to toggle between set and unset.
- Define and apply rules in the Generate Days section. The rules are used to determine the processing and blocked days and to resolve schedule conflicts.
- (Optional) Provide a description.
- A non-mandatory description that contains any text.Limits:Up to 1024 characters.The description is available only if AE 11.3.6 SP2 (and any later versions) is used.
- Click Commit. The calendar definition is saved.
You can use Quick Edit to find one or more AutoSys Workload Automation calendars residing on a specific server.
- Select the appropriate server from the Server drop-down list.
- Enter one of the following in the Name field and click Go:
- Valid calendar name -- Finds the specified calendar on the selected server.Asterisk (*), percent (%), or question mark (?) with a partial name, where the * or % represents zero or more characters and ? represents a single character -- Finds all calendars on the selected server that contain the partial name. For example, entering n* would find all calendars on the server that begin with the letter n, and entering *n would find all calendars on the server that end with the letter n.Asterisk (*) or percent (%) -- Finds all calendars on the selected server.
- (Optional) Enter search criteria in any of the optional fields to further refine your search.The Search Results section lists the calendar or calendars that meet your search criteria.
You can review the specific definitions for a calendar.
- Click the calendar name in the Search Results section.
- Click Go. The Search Results section is displayed.
You can edit a calendar to modify its properties. For a standard calendar, you can change the specific days on which a job may process by manually selecting them or setting the rules that control processing days. For an extended calendar, you can modify specific days on which a job may process.
- Click the calendar name in the Search Results section. The detailed properties for the calendar are displayed.
- The Name field is read-only when you edit an existing calendar.
- Click Commit. The changes are saved.
If you no longer have any jobs associated with a calendar, you can delete it.
![Autosys Autosys](/uploads/1/1/9/7/119741239/378469289.jpg)
- Do one of the following:
- Click the calendar name in the Search Results section and click Delete.
- Select the Select check box in front of the appropriate calendar, and click the Delete link.
You can delete multiple objects at one time by selecting the Select check boxes for all of the objects to be deleted and clicking the Delete link.
- Click OK. The calendar definition is deleted.
You can create an extended calendar to define processing days using any combination of holiday calendars, cycles, and conditions for scheduled jobs.
- Click Create. The Create Object dialog opens.
- Select the appropriate server from the Server drop-down list and click the Extended Calendar link.
- Define your extended calendar by performing the following actions:
- Enter a name for the extended calendar in the Name field.
- If using only CA AE 11.3.6 SP2 (and any later versions), the limit of up to 64 characters applies.
- (Optional) Enter date conditions for the extended calendar in the Conditions field. Examples:
- MON - Selects all Mondays after the current date
- FOMWEEK - Selects the first weekday of each month after the current date
- EOMWEEK - Selects the last weekday of each month after the current date
- XFOM - Selects all days except the first day of each month after the current date
- CYCLE - Selects any day within the date ranges, or periods defined in the cycle.
- (Optional) Enter the name of an existing cycle in the Cycle Name field or select a cycle from the Search Cycle dialog. Also, enter CYCLE in the Conditions field.
- Enter any integer in the Adjustment field to adjust the days generated by the other criteria to either a previous day or a specified number of days after the actual generated day.
- (Optional) Select a rule for holidays from the Reschedule rule list, and then enter the name of a standard calendar in the Calendar field or select a calendar from the Search Calendar dialog.
- (Optional) Select an action for non-workdays from the Non Workday Action list, and then select at least one workday from the Workdays panel.
- (Optional) Click Generate preview to open the Extended Calendar Preview dialog so you can preview the dates generated by the rules in the extended calendar.
- A non-mandatory description that contains any text.Limits:Up to 1024 characters.The description is available only if AE 11.3.6 SP2 (and any later versions) is used.
- Click Commit. The extended calendar definition is saved.If you create an extended calendar by entering a value in the Name field only and saving it, all days are selected from the current day forward, for a total of 366 days.
Example: Create an Extended Calendar Based on Field Adjustment
To create an extended calendar that processes associated jobs one day after each holiday, you would first create a calendar defining the holidays for the year, then create an extended calendar with the following options selected:
- Schedule only on a holiday in the Holiday Action list
You can copy an existing calendar to create a new calendar with the same properties. You must specify a different name for the new calendar; otherwise, the calendar you copied is simply updated.
- Do one of the following:
- Click located in the Actions column to the right of that calendar.
- Click the calendar name in the Search Results section. Next, select Copy from the Select and drop-down list, and click Go.
- Define your calendar by doing the following:
- If using only CA AE 11.3.6 SP2 (and any later versions), the limit of up to 64 characters applies.
- Edit the calendar definition as necessary.
- Click Commit. The new calendar definition is saved.
You can create a cycle to define date ranges to be used as input to an extended calendar.
- Select the appropriate server from the Server drop-down list and click the Cycle link.
- Define your cycle by performing the following actions:
- If using only CA AE 11.3.6 SP2 (and any later versions), the limit of up to 64 characters applies.
- (Optional) Select the Repeat every year check box to repeat the cycle every year.
- Select Add from the Select an action drop-down list and click Go to add periods to the cycle.
- You can optionally click to select the period dates. This is available only when the Repeat every year check box is not selected.
- At least one period must be added to the definition.
- (Optional) Select a period and select Add Before from the Select an action drop-down list. Click Go to add a new period before the selected period.
- (Optional) Select a period, select Move Up from the Select an action drop-down list, and click Go to move the selected period up one level.
- (Optional) Select a period, select Move Down from the Select an action drop-down list, and click Go to move the selected period down one level.
- (Optional) Select a period, select Delete from the Select an action drop-down list, and click Go to delete the selected period from the cycle.
- (Optional) Provide a description
- A non-mandatory description that contains any text.Limits:Up to 1024 characters.The description is available only if AE 11.3.6 SP2 (and any later versions) is used.
- Click Commit. The cycle definition is saved.
Example: Create a Cycle and Associate it with an Extended Calendar
To associate a cycle with an extended calendar, you first create the cycle with the periods defined. When you create the extended calendar, enter CYCLE in the Conditions field. Next, enter the name of the cycle calendar in the Cycle name field, and click Generate Preview. You can now view the processing dates that are selected. You can also click to the right of the Cycle name field to select a cycle from the Search Cycle dialog.
You can use Quick Edit to find one or more AutoSys Workload Automation cycles residing on a specific server.
- Select the appropriate server from the Server drop-down list.
- Enter one of the following in the Name field and click Go:
- Valid cycle name -- Finds the specified cycle on the selected server.
- Asterisk (*), percent (%), or question mark (?) with a partial name, where the * or % represents zero or more characters and ? represents a single character -- Finds all cycles on the selected server that contain the partial name. For example, entering n* would find all cycles on the server that begin with the letter n, and entering *n would find all cycles on the server that end with the letter n.
- Asterisk (*) or percent (%) -- Finds all cycles on the selected server.
4. (Optional) Enter search criteria in any of the optional fields to further refine your search.
Autosys Extended Calendar Definition
The Search Results section lists the cycle or cycles that meet your search criteria.
You can review the date ranges to be used as input to an extended calendar.
- Click the cycle name in the Search Results section.
- Click Go. The Search Results section is displayed.
You can copy an existing cycle to create a new cycle with the same properties. You must specify a different name for the new cycle; otherwise, the cycle you copied is simply updated.
Autosys Extended Calendar Conditions
- Do one of the following:
- Click located in the Actions column to the right of that cycle.
- Click the cycle name in the Search Results section. Next, select Copy from the Select and drop-down list, and click Go.
- Define your cycle by doing the following:
- If using only CA AE 11.3.6 SP2 (and any later versions), the limit of up to 64 characters applies.
- Edit the cycle definition as necessary.
- (Optional) Provide a description
- A non-mandatory description that contains any text.Limits:Up to 1024 characters.The description is available only if AE 11.3.6 SP2 (and any later versions) is used.
- Click Commit. The new cycle definition is saved.
Autosys Extended Calendar Jil Example
You can edit a cycle to modify existing periods and add or delete new periods.
Autosys Extended Calendar Keywords
- Click the cycle name in the Search Results section.
- The Name field is read-only when you edit an existing cycle.
- Click Commit. The changes are saved.
If you no longer need specific date ranges defined for use in an extended calendar, you can delete the cycle that defines these date ranges.
Autosys Extended Calendar 2019
- Do one of the following:
- Click the cycle name in the Search Results section, and then click Delete.
- Select the Select check box in front of the appropriate cycle, and click the Delete link.
You can delete multiple objects at one time by selecting the Select check boxes for all of the objects to be deleted and clicking the Delete link. - Click OK. The cycle is deleted.