10 More Discussions You Might Find Interesting
1. Infrastructure Monitoring
Hello- I am currently researching on an autosys command that can be invoked via command line that can clean-up alerts.
The reason I ask is because we have jobs that activate on a daily basis. The job polls whether it needs to run or not (via filewatcher or some database check). If the job isn't... (0 Replies)
Discussion started by: cec_can
0 Replies
2. UNIX for Advanced & Expert Users
I have submitted an autosys job and force start it. Autosys hit the job 4 times to restart but it did not start and finally I terminate the job. Any idea why the job did not start. Below is the code I executed.
1214 missun0ap /export/home/bzn97r/develop/dswi/jil$ sendevent -E FORCE_STARTJOB... (0 Replies)
Discussion started by: jnrohit2k
0 Replies
3. UNIX for Advanced & Expert Users
hi all
would like to know a list of job in the my autosys .
which is the command for extract it?
thanks a lot
regards
FrancescoIt (1 Reply)
Discussion started by: FrancescoIt
1 Replies
4. Shell Programming and Scripting
I need to know the list of autosys job that run between given time.
I have the following command.
job_depends -t -J abc% -F "12/25/2010 03:00" -T "12/26/2010 05:00"
Above command will give the list of job that run between time 3 AM and 5 AM.
But the it gives me in random order how to... (1 Reply)
Discussion started by: diehard
1 Replies
5. UNIX for Dummies Questions & Answers
Hi Can any one tell me free online good book for autosys job.
Also whats the basic difference between Autosys job and cron job.
Thanks in advance. (2 Replies)
Discussion started by: diehard
2 Replies
6. Shell Programming and Scripting
We need to configure autosys that when a job fails continously for 3 times, we need to call another job.
Is this possible in Autosys, or can anyone advice on the alternative. (2 Replies)
Discussion started by: sangea
2 Replies
7. Shell Programming and Scripting
Hi,
I am trying to schedule an autosys job for weblogic server reboot. When i run the job it is failing with the following error:
/bin/sh: /path/stop_wls instancename: not found
The following is my jil and i dont refer to /bin/sh at all
update_job: mgd_shutdown_cmd.jil job_type: c ... (3 Replies)
Discussion started by: userscript
3 Replies
8. UNIX and Linux Applications
Hello!
I will be working with Autosys and I am looking for individuals that have knowledge of this UNIX application.
Thank-you! (3 Replies)
Discussion started by: preshe79
3 Replies
9. UNIX for Advanced & Expert Users
My project uses Autosys.
I am new to this product and I don't know where to start from.
Q1. Please provide me the link where I can get Autosys documentation
Q2. Please refer a good book on Autosys. (Beginner/Intermediate Level) (0 Replies)
Discussion started by: gram77
0 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I have done kill-9 xxx for a job which is running in Autosys.
But when i use autorep -j xxx it is showing the job is in run status.
How to kill a job in Autosys which is in running status..
Thanks
Arun (3 Replies)
Discussion started by: arunkumar_mca
3 Replies
job(n) Tnm Tcl Extension job(n)
__________________________________________________________________________________________________________________________________________________
NAME
job - Invoke Tcl procedures at regular intervals.
_________________________________________________________________
DESCRIPTION
The job command provides a convenient mechanism to implement Tcl procedures that are invoked at regular intervals. Jobs are activated from
the Tcl event loop. Every job can have arbitrary attributes to store job specific state information between two invocations. These
attributes help to avoid global variables in order to keep the Tcl name-space clean.
The job scheduler itself relies heavily on the Tcl timer interface which itself depends on the system clock. Moving the system clock back-
wards can have the effect that jobs are not activated for the amount of time the system clock was moved backwards. Similarly, moving the
system clock forward can have the effect that jobs are activated earlier for the amount of time the system clock was moved forward.
JOB COMMAND
The job command allows to create new jobs and to wait for jobs to complete. The job command can also be used to retrieve status information
from the job scheduler.
job create [option value ...]
The job create command creates a new job object. The options can be used to configure the behaviour of the new job. See the config-
ure command below for the details.
job current
The job current command returns the name of the currently running job. An empty string is returned if no job is running.
job info
The job info command returns a list of all job names. The list will be empty if there are no jobs known in this Tcl interpreter.
job schedule
The job schedule command invoke the scheduler. This is usually done automatically from the event loop. This command may be used dur-
ing long computations since the scheduler is not preemptive. Note, this command can cause arbitrary side effects and should be used
with care.
job wait
The job wait command blocks until all existing jobs have been finished. The command will wait infinitely if there is at least one
job left. Events are processed while waiting for the jobs to finish which can have arbitrary side effects.
JOB INSTANCE COMMAND
Every job is represented by a job object command which allows to manipulate the job.
job# attribute [name [value]]
The job# attribute command allows to save job specific data in job attributes. If called without any arguments, all existing
attribute names for this job will be returned. If called with a name argument, the current value of the attribute will be returned.
Non-existing attributes do not produce an error. Instead, an empty string is returned. Calling the option with a name and a value
causes the value to be saved in the job attribute.
job# cget option
The job# cget command returns the current value of a configuration option. See the description of supported options below.
job# configure [option value ...]
The job# configure command manipulates configuration options. See the description of supported options below. A list describing all
current options is returns if the options argument is missing.
job# destroy
The job# destroy command destroys the job object. This command forces the object to change into the expired state. The scheduler
will cleanup this object the next time it is active.
job# wait
The job# wait command blocks and processes events until the current job changes into the expired state.
JOB OPTIONS
Every job has associated configuration options which control when a job is activated and which Tcl command is bound to the job.
-command command
The -command option defines the Tcl command that is evaluated whenever the job is activated.
-interval time
The -interval option defines the time interval between two job activations in milliseconds.
-iterations number
The -iterations option defines the total number of times that a job is activated. If this value reaches 0, the job will change its
state to expired. Note, if the iterations options is never used, it will also have the value 0 but nothing special happens to the
job object.
-status state
The -status option provides access to the current job state. A job is always in one of the states waiting, suspended, running and
expired. A job in the expired state will be removed from the system once the scheduler gets activated again. Suspended jobs are not
activated by the job scheduler. A suspended job can be resumed by changing its state to running.
-time time
The -time option returns the number of milliseconds until this job is activated the next time. This option is read-only.
SEE ALSO
scotty(1), Tnm(n), Tcl(n)
AUTHORS
Juergen Schoenwaelder <schoenw@cs.utwente.nl>
Tnm job(n)