Autosys CheatSheet (Reposted)

1、autosys cheatsheet (reposted)autosys: unix cd to the "autouser" ($autouser) directory and "." (or source) the "ksh" . ex: ". ./autosys.ksh.machine" after installing autosys, first make re that the db is up and running. check the installation by running the com

2、mand chk_auto_up to verify connection to the db and event processor. enter the keys through "gatekeeper", a keys run the "autosys_secure" command to the autosys edit and exec super users (and ao to enter nt users/passwords) start the event processor by running the command "e

3、ventor" shutdown autosys: "sendevent -e stop_demon" to start the autosys gui set your display and run the command "autosc ". nt: start autosys from start- programs- autosys- adminisator - graphical user interface - command prompt command line commands: gatekeeper: allows you

4、 to enter the license keys allow you to run autosys. eventor -m machine_name : starts the event processor. autorep -j all | job_name -q file_name, -d (detail), -r (run number), -o (overre), jil file_na -g (global var report), -m -q for machine definitions.ex: autorep -j job_name -d autorep -j job_na

5、me -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 -l1 report on the job for the day -1 (prev day) sendevent -e startjob -j job_name, sendevent -e force_startjob -j job_name, job_on_ice,

6、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 var) (ex: sendevent -e set_global -g "var_name=delete" to delete a var) chk_auto_up: checks to see if even

7、t processor and the db are both up. auto -m machine: verify that both client server are correctly configur. cron2jil -f cronfile -d outdir -i il_file -m machine -p prefix jil cr to insert a job directly into the dbinsert_job: job.id job_type: cmachine: machine_namecommand: echo testing jilgo | ; (de

8、pending on the db you are using)template example: /* - template - */ insert_job: template job_type: c box_name: box1command: ls -lmachine: localhostowner: lyota01tant-a01peission: gx,ge,wx,we,mx,me_conditions: 1days_of_week: allstart_s: "15:00, 14:00"run_window: "14:00 - 6:00"con

9、dition: s (job1)description: "description field"n_retrys: 12term_run_time: 60box_terminator: 1job_terminator: 1std_out_file: /tmp/std_outstd_err_file: /tmp/std_errmin_run_alarm: 5max_run_alarm: 10alarm_if_fail: 1max_exit_success: 2chk_files: /tmp 2000profile: /tmp/.profilejob_load: 25prior

10、ity: 1auto_delete: 12 autosyslog -e: same as tail -f autosys_log_file. this command must be run from the machine where the server resides if u with the -e option. else it can be used with the -j option to see that job's run log. job_depends: -c|d|t -j jobname -f "mm/dd/yy time" -t &quo

11、t;mm/dd/yy time" (note: it will only print out the first occurrence found) 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 autocal_asc full_cal_name: prints, adds deletes cust

12、om calendar definitions. autous: reports the current status of a specific job, or the value of an autosys global variable. ex: autostatus -j job_name, -s instance autotimezone -l : allows additions, deletions, and queries to the timezones table (-l provides list). autotrack: tracks report changes to

13、 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, an

14、d 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. autosys_secure: to change edit, exec superus

15、ers, change db , change remote authentiion method. chase -a|e: makes sure that jobs claiming to be running in the client machine are running. the "-e" option restarts the job. archive_events: to archive events in the db which are older than x days to prev db from becoming full. clean_files

16、: deletes old remote agent log files. it does it by searching the db for all machines which have had jobs started on them. 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 user defina

17、ble buttons: there are user definable buttons in the operator's console. how to configure: autocons*userbutton1command: /autosys/bin/autostatad -j $job -g (which allows you to have a command button on the operator's console.) dependencies: success (job) and s(job_b)failure(job_a) or f (job_b

18、)notrunning (job)terminated(job)exitcode(job) 5 and exitcode(job_b) != 10value(global_name)=100done(job) hostscape: schele a job to run every x minutes then go into forecasting. make that job fail. solid black line: hostscape can communicate with the remote agent in the client machine. solid red lin

19、e: hostscape can't communicate with the remote agent but it can communicate with the internet daemon (inetd) running on that machine. dashed red line: hostscape can't communicate with the client machine at all. client is probably down. accessing a variable name: $global_var_name (un used in

20、dependency condition with a job definition. if used in the "command" field, you must use the $) tunable parameters: $autouser/config.ace $autouser/autosys.ksh.xxx /etc/file /etc/inetd.conf /etc/services notify.ace: the alarms to notify on are:(there is an example in $autosys/instal

21、l/data/notify.ace). db_rollover db_problem ep_high_availability ep_rollover ep_shutdown where to go to the errors: $autouser/out/event_demon.$autoserv($autouser/out/event_demon.ace) output from the job definition output error files /tmp files created for job_run at client machine $autosys/out/dbmain

22、t.out for db problems $sybase/install/errorlog_$dsquery when event server will not start. nt: autonutclib/x11app-defaultsxpert autosys maintenance: dbmaint $autosys/bin once a day the database goes into a maintenance cycle. every day at 3:00am it runs a program called dbmaint. this is user configura

23、ble. the program runs dbstatistics which is found in $autosys/bin. app-defaults file: /usr/openwin/lib/app-defaults directory. autocons, xpert, etc. ( or: /usr/lib/x11/app-defaults, /autosys/bin/x11/app-defaults) environment file: /etc./filec programs: $autosys/code where to change autosys s

24、creen fonts: /usr/openwin/lib/app-defaultswhere to for troubleshooting: chapter 15summary of commands: appendix c $auto_job_name: when naming a file dynamically using as prefix autosys's job name.$autorun: ue identifier for the run of that job$autopid: unique identifier for that job's run nu

25、mber (pid)$joid: db identifier for a job. to extract from the db: select joid from job where job_name=" " creating a virtual machine: insert_machine: virtualtype: v /* default, not required */machine: real_1machine: real_2max_load: 100factor: 0.5 /* used to describe the relative processing

26、 power of a machine. usually between 0.0-1.0*/machine: real_2max_load: 60 /* this is designed to limit the loading of a machine */ load balancing, queuing, priorities: insert_job: test_loadmachine: localhostcommand: echo "test load balancing"job_load: 50priority: 1 /* this only affects que

27、ues */ note: for 5.0 we will be using information from servervision's towards our load balancer which is composed of 26 categories such as i/o usage, disk usage, cpu usage, etc. testing: zql zql -u autosys -p autosys notes: when a job is stuck in the starting condition this means that the event

28、processor communicated with the remote agent and passed all the information the remote agent ran the job but was not able to communicate to the db. once testing is done with autosys one should change the default refresh interval for autosys. this is so there is less querying to the db. when autosys goes from dual mode to single mode, always run the autob command before bringing autosys back to dual mode/high availability. default behavior for stdout is to always appends. if you want to over the file enter the following,