10 More Discussions You Might Find Interesting
1. Solaris
Hi All,
We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup).
We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job).
What can be the possible reason for such... (1 Reply)
Discussion started by: kg_gaurav
1 Replies
2. UNIX for Advanced & Expert Users
Hi Experts,
I am new to Autosys. I created a Autosys box job to run at 10 AM daily. As scheduled, the job starts on time.
There is another box job inside the box. I have scheduled it to run at 11 AM but it kicks off automatically with the main job at 10 AM.
insert_job: Main-job ... (2 Replies)
Discussion started by: pk_bohra
2 Replies
3. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
Is there a way to schedule a job in Autosys to run every 5th Day of Month without using custom calendar?
Thanks. (1 Reply)
Discussion started by: vbhatnag
1 Replies
5. 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
6. Windows & DOS: Issues & Discussions
Hi, I have created an autosys job which calls an exe and updates its output files. The job is failing without updating the output and error files.
I if restart the usvmapgrnd01.pc.ml.com machine, the job runs successful for first time and fails rest of the time. Please let me know what might be... (0 Replies)
Discussion started by: sonaldewle
0 Replies
7. UNIX for Advanced & Expert Users
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (1 Reply)
Discussion started by: rgilan01
1 Replies
8. Solaris
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (2 Replies)
Discussion started by: rgilan01
2 Replies
9. Programming
I am looking to get a report on autosys jobs in RUNNING state b/w certain time frame (timeA and timeB).
What I am after is the list of all the jobs that ran between AND during timeA and timeB.
Jobs within the timeframe could either:
A: STARTING --> RUNNING --> SUCCESS/FAILURE etc..
B: ... (0 Replies)
Discussion started by: rgilan01
0 Replies
10. 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
qterm(8B) PBS qterm(8B)
NAME
qterm - terminate processing by a PBS batch server
SYNOPSIS
qterm [-t type] [server...]
DESCRIPTION
The qterm command terminates a PBS batch server. When a server receives a terminate command, the server will go into a terminating state.
While in this state, the server will not allow new jobs to be started or enqueued. By default, qterm will request a "quick" shutdown of
the PBS server. Other ways of shutting down the server (specified with the -t argument), and their impact on running jobs, are described
below. The qterm command will not exit until the server has completed its shutdown procedure.
In order to execute qterm, the user must have PBS Operation or Manager privilege.
OPTIONS
-t type Specifies the type of shut down. The types are:
immediate
All running jobs are to immediately stop execution.
If checkpoint is supported, running jobs that were submitted with "-c shutdown" are checkpointed, terminated, and
requeued. If checkpoint is not supported or the job cannot be checkpointed, running jobs are requeued if the rerunable
attribute is true. Otherwise, jobs are killed.
Normally the server will not shutdown until there are no jobs in the running state. If the server is unable to contact
the MOM of running job, the job is still listed as running. The server may be forced down by a second qterm -t immediate
command.
delay If checkpoint is supported, running jobs that were submitted with "-c shutdown" are checkpointed, terminated, and
requeued. If a job cannot be checkpointed, but can be rerun, the job is terminated and requeued. Otherwise, running jobs
are allowed to continue to run. Note, the operator or administrator may use the qrerun and qdel commands to remove run-
ning jobs.
quick This option is used when you wish that running jobs be left running when the server shuts down. The server will cleanly
shutdown and can be restarted when desired. Upon restart of the server, jobs that continue to run are shown as running;
jobs that terminated during the server's absence will be placed into the exiting state.
OPERANDS
The server operand specifies which servers are to shutdown. If no servers are given, then the default server will be terminated.
STANDARD ERROR
The qterm command will write a diagnostic message to standard error for each error occurrence.
EXIT STATUS
Upon successful processing of all the operands presented to the qterm command, the exit status will be a value of zero.
If the qterm command fails to process any operand, the command exits with a value greater than zero.
SEE ALSO
pbs_server(8B), qmgr(1B), pbs_resources_aix4(7B), pbs_resources_irix5(7B), pbs_resources_sp2(7B), pbs_resources_sunos4(7B), and
pbs_resources_unicos8(7B)
Local qterm(8B)
report of autosys job in RUNNING state