Autosys :

1) On Ice , On hold
On Ice : Placing a job ON-ICE will release any job that depends on that job's success
completion.
On hold : Placing the job on hold will hold the batch or cycle which next to it.

2) What will happen when you Off ice and Off hold
Off Ice – the job will run in the next schedule
Off hold - release the job(start to run) if its dependent job is in a success.

3) future send events

Using future send even we can do all the actions with the particular time given.

4) How to check is everything (Primary , event server and the database) are fine ?

Using command chk_auto_up on the command line. It will give you like this :

bash:ftwpsauto:PRD-> chk_auto_up

Attempting (1) to Connect with Database: ASYSPRDS

*** Have Connected successfully with Database: ASYSPRDS. ***

----------------------------------------------------------------------------------------------------------------------------

Connected with Event Server: ASYSPRDS

Attempting (1) to Connect with Database: ASYSPRDP

*** Have Connected successfully with Database: ASYSPRDP. ***

Connected with Event Server: ASYSPRDP

Checking Machine: ftwpsauto

Primary Event Processor is RUNNING on machine: ftwpsauto

_____________________________________________________________________________

Checking Machine: livpsauto

 Shadow Event Processor is RUNNING on machine: livpsauto

5) To check the machine pingable from Autosys?

autoping –m machinename

6) To check database available on that machine ?

autoping –m machinename –D
7) To check the autosys session logs :

Autosyslog –e

8) To check who handled the last action of a particular job – for ex: who force started the job?
autotrack –J jobname

9)Diff between Start and Force start :

Start : it will start the job once the job met its requirement.

Force start : It will start the job immediately regardless of the requirements.

9) Be sure with some basic Unix commands : for ex : to get error logs from the particular path.
Here is the location where we get the error logs for our autosys jobs :

std_out_file: >/export/home/autobtch/produser/$AUTO_JOB_NAME.out
std_err_file: >/export/home/autobtch/produser/$AUTO_JOB_NAME.err

10) Actions to take when On Ice a job :

Make sure there is no dependent jobs
If there is the on ice them also.

Let them know that you always follow process and procedures of your company.

For ex:

Will not execute a adhoc request without a proper approved change.

Perfect in incident management – will input all the details in the tickets.

What do you do when high critical job fails ?

Call the application team within 15 minutes and send them an email. If you are not able to get the
first person then move on to next up to the manager until you speak to some one.
 Using command line in Unix

to force start jobs, to kill job , On ice , Off ice , set to success……… using Alias

1 ) aj jobname

To find the status of a job

ex :

bash:ftwpsauto:PRD-> aj OMEGA_MIGUPLOAD_D

Job Name Last Start Last End ST Run Pri/Xit

____________________________ ____________________ ____________________ __ __

OMEGA_MIGUPLOAD_D 08/28/2012 22:15:13 ----- RU 28928017/1

2 ) ale

to display autosys logs

3) aping machinename which is same as autoping –m machinename

To check the machine is pingable..

Ex :

bash:ftwpsauto:PRD-> aping livlpsaiu202.r1-core.r1.aig.net

AutoPinging Machine [livlpsaiu202.r1-core.r1.aig.net]

AutoPing WAS SUCCESSFUL!

4) fsj jobname

To force start a job

5) fkj jobname

To kill a job
 6) fij jobname

To On ice a job

7) foij jobname

To Off ice a job

8) fohj jobname

To off hold a job

9) css jobname

Mark the job to success.

10) autorep –j jobname –q

To get the jil of the job (JIL –Job information language)

Ex :

bash:ftwpsauto:PRD-> autorep -j OMEGA_MIGUPLOAD_D -q

/* ----------------- OMEGA_MIGUPLOAD_D ----------------- */

insert_job: OMEGA_MIGUPLOAD_D job_type: c

command: sh /opt/apps/was61/omega/MigrationUtility/MigrationUtility.sh UPLOAD

machine: livlpsaiu202.r1-core.r1.aig.net

#owner: usradmin

permission:

date_conditions: 1

days_of_week: mo,tu,we,th

start_times: "22:15"

description: "HIGH - Incident-OMEGA - Restart-Rerun - Contact-139.5"

std_out_file: >/export/home/autobtch/produser/$AUTO_JOB_NAME.out

std_err_file: >/export/home/autobtch/produser/$AUTO_JOB_NAME.err

alarm_if_fail: 1