You are on page 1of 4

AUTOSYS UNIX Commands.....

AutoSys on Unix Cd to the "autouser" ($AUTOUSER) directory and "." (or source) the "ksh" file. Ex: ". ./autosys.ksh.machine"After installing AutoSys, first make sure that the DB is up and running. Check the installation by running the command chk_auto_up to verify connection to the DB and event processor. Enter the KEYS through "gatekeeper", add keys Run the "autosys_secure" command to set the AutoSys Edit and Exec Super users (and also to enter NT users/passwords) Start the Event Processor by running the command "eventor" Shutdown AutoSys: "sendevent -E STOP_DEMON" To start the AutoSys GUI set your DISPLAY and run the command "autosc &". NOTE: Start AutoSys from start->programs->AutoSys-> administrator ->Graphical User Interface ->Command Prompt Autosys Command Line Commands: 1.gatekeeper: Allows you to enter the License Keys which allow you to run AutoSys. 2.eventor [-M machine_name] : Starts the event processor. 3.autorep -J [ALL Job_name] [-q] [> file_name], -d (detail), -r (run number), -o (override) Ex: autorep -J job_name -d autorep -J job_name -d autorep -J job_name -q > file_name queries the DB & save job Dfn. Into a file vi file_name When you want a report of a box use the -L0 option Autorep -J job_name -r -1 report on the job for the day -1 (prev day)

Autorep -J job_name -r -5 report on the job for last 5th run 4.sendevent -E STARTJOB -J job_name : Normally start Autosys job. sendevent -E FORCE_STARTJOB -J job_name : Forcefully starts Autosys job. [JOB_ON_ICE, JOB_OFF_ICE, JOB_ON_HOLD, JOB_OFF_HOLD, SET_GLOBAL, STOP_DEMON. . . .] sendevent -E STOP_DEMON - to stop AutoSys sendevent -E SET_GLOBAL -G "var_name=/home/mydir" : To set a variable in Autosys sendevent -E SET_GLOBAL -G "var_name=DELETE" : To delete Autosys variable that is declared/set 5.chk_auto_up: checks to see if event processor and the DB are both up. 6.autoping -m machine: verify that both client & server are correctly configured. 7.cron2jil -f cronfile [-d outdir] [-I incl_file] [-m machine] [-p prefix] 8.jil: To insert autosys job directly into the DB /* ----------------- template test.jil ----------------- */ insert_job: template job_type: c box_name: box1 command: machine: localhost owner: $jil < test.jil 9.autosyslog -e: same as tail -f autosys_log_file. This command must be run from the machine where the server resides if used with the -e option. Else it can be used with the J option to see that job's run log. 10.job_depends: -[cdt] -J jobname [-F "mm/dd/yy time"] [-T "mm/dd/yy time"] (Note: It will only print out the first occurrence found)

11.monbro -n monitor_name: Allows you to run from command line monitor/browser programs previously created using the monitor/browser GUI.exec superuser: AUTOSYS superuser 12.autocal_asc full_cal_name: prints, adds & deletes custom calendar definitions. 13.autostatus: Reports the current status of a specific job, or the value of an AutoSys global variable. Ex: autostatus -J job_name, -S instance 14.autotimezone -l : Allows additions, deletions, and queries to the timezones table (-l provides list). 15.autotrack: Tracks & report changes to the AutoSys DB. Ex: autotrack -l 2 (level 2) [sets the tracking level] autotrack -U sys -v (user sys: verbose) To start using the autotrack utility type: autotrack -u to set tracking level 1 or 2. By default it is set to 0. Autotrack -l will list the current tracking level. Options -[J, U, m, F, T, and t] are to request reporting on a specific Job, User, machine, time window (-F -T), and event type (t). Type is used in conjunction w/other parameters. autotrack w/no arguments retrieves information an all events omitting detail. -v option is for verbose. 16.autosys_secure: to change edit, exec superusers, change DB passwd, change remote authentication method. [-AE]: Makes sure that jobs claiming to be running in the client machine are running. The "-E" option restarts the job. 18.archive_events: to archive events in the DB which are older than x days to prev DB from becoming full. 19.clean_files: Deletes old remote agent log files. It does it by searching the DB for all machines which have had jobs started on them.

20.autostatad: to get the status of a PeopleSoft job. You can define one of the user definable buttons to view PeopleSoft job: Autocons*userButton1Label: Adapter Status.