autosys Client installation on SuSe

autosys Client installation on SuSe

autosys Client installation on Redhat 6.5

autosys Client installation on Redhat 6.5

autosys Client installation on Solaris 10

autosys Client installation on Solaris 10

autosys installation on Solaris 10

autosys installation on Solaris 10

autorep command

autorep command
Syntax : autorep -J job_name [ -d | -q | - r run_number ]
Description : autorep lists a variety of information about jobs
Options :
-J job_name : Indicates that a Job Report is desired. To report on all jobs, specify ALL. The % character may be used in the job name as a wildcard
-d Indicates a Detail Report is desired. For a Job Report, all events from the last run of the requested job will be listed.
-q Indicates a Query Report is desired, providing the current job or machine definition, in JIL format, as it exists in the AutoSys database.
-r run_num Indicates a report is desired for a specific job run (run_num). This option can only be used with the -s and -d options. If this option is omitted, or run_num is zero, the most current job run is reported. A minus sign (-) can be used before the run_num value to indicate a relative counter for a past job run, relative to the current run number. For example, the option r -2 would generate a report for the job run two runs back.

Meaning of AutoSys status

STATUS AUTO STATUS  Meaning
----------  ------------------   ---------
RU           RUNNING        Running
ST           STARTING        Starting
SU          SUCCESS        Success
FA           FAILURE          Failure
TE           TERMINATED   Terminated
OI            ON_ICE           On Ice
IN            INACTIVE         Inactive
AC          ACTIVATED       Activated
RE          RESTART          Restart
OH         ON_HOLD          On Hold
QW         QUE_WAIT       Queue Wait
RD          Refresh             Dependencies
RF          Refresh             Filewatcher

autosys notes

Notes on Autosys 4.5
System Components
The following are the main system components:
- Event server (database)
- Event processor
- Remote agent
In addition, AutoSys JM provides utilities to help you define, run, and maintain instances and jobs.
GUI and JIL are available to define, manage, monitor, and report on jobs.
Communication component
Windows client (Remove agent with jobs

autosys server (unix/win) which is event processor/ event server database.

Unix client (remove agent, unix job)



autorep command allows you to generate a variety of reports about job execution, and
sendevent command allows you to manually control job processing.


---------------------------------
job condition
(success(JobA) and success(JobB)) or (done(JobD) and done(Job E))
the above job will be evaluated from left to right and the result would be A and B or D and E.

This is the syntax for conditions based on job status:
status(job_name)
where:
status is one of the following:
success:  Indicates that the status condition for job_name is SUCCESS.
failure:  Indicates that the status condition for job_name is FAILURE.
done:   Indicates that the status condition for job_name is SUCCESS, FAILURE or TERMINATED.
terminated: Indicates that the status condition for job_name is TERMINATED.
notrunning: Indicates that the status condition for job_name is anything except RUNNING.
job_name: Is the job on which the new job is dependent.
You can abbreviate the status condition identifiers with the first letter, using s, f, d, t, and n. You can also abbreviate the dependency specification exit code with the letter e and VALUE (of a global variable) with the letter v. These abbreviations can be upper- or lowercase.
------------------------------

condition: success(jobA) AND success(jobB^PRD)
The success(jobB^PRD) condition specifies the successful completion of a job named “jobB” running on a different instance specified with the three-letter ID of “PRD.” If the dependency specification does not include a caret (^) and a different instance ID, the current instance will be used, by default.

For a job that runs only if the job named “DB_BACKUP” succeeds, the job dependency specification would be written as follows:
success(DB_BACKUP)
or:
s(DB_BACKUP)

------------------
You can specify more complex conditions by grouping the expressions in parentheses. The parentheses do not imply any sort of precedence; they are simply used for grouping. For example, if “JobC” should only be started when both “JobA” and “JobB” complete successfully or when both “JobD” and “JobE” complete, regardless of whether they failed, succeeded, or terminated, you would specify the following dependency in the job definition for “JobC”:
(success(JobA) AND success(JobB)) OR (done(JobD) AND done(JobE))
or:
(s(JobA)&s(JobB))|(d(JobD)&d(JobE))

exit code with the letter e
-----------
if “JobB” fails after processing only partially, you might want to call a routine titled “Backout” that backs out of the changes that were made. You would specify the following job dependency in the job definition for “Backout”:
failure(JobB)
or:
f(JobB)

-------------
You use the notrunning operator to keep multiple jobs from running simultaneously (that is, running one job is exclusive of any others). For example, it might be best not to run a database dump (“DB_DUMP”) and a file backup (“BACKUP”) at the same time. This would cause the hard disk to be accessed very frequently. However, you might have a smaller job that can run as long as both of these resource-intensive jobs aren’t running. You would specify the smaller job’s dependency like this:
notrunning(DB_DUMP) AND notrunning(BACKUP)
Note: If you have jobs that you want to run exclusively, use the virtual machine and job queuing feature described in the chapter “Load Balancing and Queuing Jobs,” in this guide.
---------

 

Force Starting Jobs in a Box

using command line,

sendevent -E FORCE_STARTJOB -J job_name
 
To inactive the job,
sendevent -E CHANGE_STATUS -S INACTIVE -J job_name

Start Job - STARTJOB Starts the job if the Dependencies starting conditions are met. This action ignores Date/Time starting conditions, but it does not ignore job dependency starting conditions, do not use it on jobs in boxes.

Kill Job - KILLJOB Kills selected job.

Force Start Job - FORCE_STARTJOB Starts the job regardless of whether the starting conditions have been met.

On Hold - JOB_ON_HOLD Places job on hold which mean job can not be started. If job is on STARTING or RUNNING state, you can not put job on HOLD.

Off Hold - JOB_OFF_HOLD takes the job off hold which mean if jobs starting conditions are met, job will start.

In Ice - JOB_ON_ICE bringing the job on deactivate state. You can not place job on ice if the state is on STARTING or RUNNING state.

Off Ice - JOB_OFF_ICE takes the job off ice which mean reactivating the job definition. The job on ice will start next time when starting conditions are met.