09-10-2011
Quote:
Originally Posted by
itkamaraj
If you want to execute the scripts in different time, then you need to create 7 autosys jobs and in the command, you need to pass the arugument for clean.sh
That's my requirement. Can you help me give me one example of JIL where i can pass any parameter to my "./clean" script like
./clean 3
or
./clean 5
One parameter for one execution at a given time.
Can you help with JIl c0mmand for the same?
I will forward your JIL to my Autosys team.
Regards
Last edited by shifahim; 09-11-2011 at 09:11 AM..
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
now, I tried looking at the User manuals I can find on the internet concerning autosys but these manuals seem to be quite confusing to me.
My question is, does anyone have a straight forward explanation on how to modify and/or create jobs in autosys??? (3 Replies)
Discussion started by: TRUEST
3 Replies
2. UNIX for Dummies Questions & Answers
I need to search for a failed status of 2 autosys jobs which write to the same logfile. Is there any way to do that on one line? I already know the following doesn't work, but is there a way to get it to work, or will I have to do a loop?
RUN_STATUS=autorep -J jobname jobname
if
then
... (1 Reply)
Discussion started by: tekster757
1 Replies
3. Shell Programming and Scripting
post deleted ... (2 Replies)
Discussion started by: Data469
2 Replies
4. Shell Programming and Scripting
hello There,
I am pretty much new to Shell Scripting and also to AutoSys. I would like to know how to list the Autosys jobs in FA status using shell scripting. I would like to get an email alert as and when any Autosys job fails. Also, it should give the path of the Log file.
Could you please... (0 Replies)
Discussion started by: supragna
0 Replies
5. Shell Programming and Scripting
I need to list out all the AutoSys jobs that are referencing a particular AutoSys global variable.
I know the autorep command will definitely need to be used here, and maybe grep as well, but I can't figure out exactly how it's to be done. For example, "autorep -q -J %jobnamewildcard% | grep... (1 Reply)
Discussion started by: dazzwater
1 Replies
6. UNIX for Advanced & Expert Users
Hi
I have 2 autosys jobs (JobA and JobB) both are in different boxes but part of one big box. I want to make them mutually exclusive so that when JobA is running then JobB should not run and wait for jobA to finish/fail/terminate and vice versa.
Both jobs have their own starting conditions... (1 Reply)
Discussion started by: SPJ47
1 Replies
7. UNIX for Dummies Questions & Answers
Can anyone please tell me how to refresh the jobs in Autosys Scheduler?
---------- Post updated at 03:19 PM ---------- Previous update was at 03:18 PM ----------
I need a command to refresh it. (2 Replies)
Discussion started by: Lakme Pemmaiah
2 Replies
8. Shell Programming and Scripting
I have been working on to neatly present the job dependency lineage in autosys through ksh/perl and I am having trouble in recursively finding the dependency.
it will be great if anyone could share their thoughts on this. (2 Replies)
Discussion started by: Vhunt
2 Replies
9. Shell Programming and Scripting
I have been working on to neatly present the job dependency lineage in autosys through ksh/perl and I am having trouble in recursively finding the dependency.
it will be great if anyone could share their thoughts on this.?
I know that job_depends in autosys will help me give first level of... (0 Replies)
Discussion started by: Vhunt
0 Replies
10. Shell Programming and Scripting
Hi Gurus,
below list is autosys job output stats, it includes boxes, sub-boxes and detail jobs. detail jobs are most right indented ones in each box. the requests is to get all these detail jobs list.
the only way to identify the "detail job", is intend.
auto_job ... (2 Replies)
Discussion started by: green_k
2 Replies
LEARN ABOUT ULTRIX
pfm_cleanup
pfm_cleanup(3ncs) pfm_cleanup(3ncs)
Name
pfm_cleanup - establish a clean-up handler
Syntax
#include <idl/c/base.h>
#include <idl/c/pfm.h>
status_$t pfm_$cleanup(cleanup_record)
pfm_$cleanup_rec *cleanup_record;
Arguments
cleanup_record A record of the context when is called. A program should treat this as an opaque data structure and not try to alter
or copy its contents. It is needed by and to restore the context of the calling process at the clean-up handler entry
point.
Description
The routine establishes a clean-up handler that is executed when a fault occurs. A clean-up handler is a piece of code executed before a
program exits when a signal is received by the process. The clean-up handler begins where is called; the routine registers an entry point
with the system where program execution resumes when a fault occurs. When a fault occurs, execution resumes after the most recent call to
There can be more than one clean-up handler in a program. Multiple clean-up handlers are executed consecutively on a last-in/first-out
basis, starting with the most recently established handler and ending with the first clean-up handler. The system provides a default
clean-up handler established at program invocation. The default clean-up handler is always called last, just before a program exits, and
releases any system resources still held, before returning control to the process that invoked the program.
Diagnostics
When called to establish a clean-up handler, returns the status pfm_$cleanup_set to indicate the clean-up handler was successfully estab-
lished. When the clean-up handler is entered in response to a fault signal, effectively returns the value of the fault that triggered the
handler.
This section lists status codes for errors returned by this routine in
pfm_$bad_rls_order Attempted to release a clean-up handler out of order.
pfm_$cleanup_not_found
There is no pending clean-up handler.
pfm_$cleanup_set A clean-up handler was established successfully.
pfm_$cleanup_set_signaledl
Attempted to use pfm_$cleanup_set as a signal.
pfm_$invalid_cleanup_rec
Passed an invalid clean-up record to a routine.
pfm_$no_space Cannot allocate storage for a clean-up handler. Clean-up handler code runs with asynchronous faults inhibited. When
returns something other than pfm_$cleanup_set indicating that a fault has occurred, there are four possible ways to
leave the clean-up code:
o The program can call to start the next clean-up handler with a different fault signal.
o The program can call to start the next clean-up handler with the same fault signal.
o The program can continue with the code following the clean-up handler. It should generally call to reenable
asynchronous faults. Execution continues from the end of the clean-up handler code; it does not resume where
the fault signal was received.
o The program can reestablish the handler by calling before proceeding.
Files
See Also
intro(3ncs), pfm_signal(3ncs)
pfm_cleanup(3ncs)