08-20-2010
Try adding in jobA:
condition: notrunning(job_B)
In jobB:
condition: notrunning(job_A)
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. UNIX for Dummies Questions & Answers
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... (5 Replies)
Discussion started by: supragna
5 Replies
6. 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
7. UNIX for Dummies Questions & Answers
Hi,
I have a script that take one parameter as an input.
for example:
./clean.sh <foldername>
There are 7 different folder names that we can provide to my script and my script would delete the contents of that folder that was passed as an argument.
Inorder to have this script... (3 Replies)
Discussion started by: shifahim
3 Replies
8. 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
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 HPUX
pthread_cond_init
pthread_cond_init(3T) pthread_cond_init(3T)
NAME
pthread_cond_init(), pthread_cond_destroy() - initialize or destroy a condition variable
SYNOPSIS
PARAMETERS
cond Pointer to the condition variable to be initialized or destroyed.
attr Pointer to the attributes object that defines the characteristics of the condition variable to be initialized. If the
pointer is NULL, default attributes are used.
DESCRIPTION
The function initializes the condition variable cond with the attributes attr. If attr is NULL, the default condition variable attributes
are used to initialize the attributes object. See pthread_condattr_init(3T) for a list of the default condition variable attributes.
After successful initialization, the condition variable may be used in condition variable operations. A condition variable should be ini-
tialized only once or the resulting behavior is undefined. The function provides a way to ensure that a condition variable is only ini-
tialized once.
The macro can be used to initialize condition variables that are statically allocated. These condition variables will be initialized with
default attributes. The function does not need to be called for statically initialized condition variables.
If the process-shared attribute in the condition variable attributes object referenced by attr is defined as the condition variable must be
allocated such that the processes sharing the condition variable have access to it. This may be done through the memory-mapping functions
(see mmap(2)) or the shared memory functions (see shmget(2)).
destroys the condition variable cond. This function may set cond to an invalid value. The destroyed condition variable can be reinitial-
ized using the function If the condition variable is used after destruction in any condition variable call, the resulting behavior is unde-
fined.
A condition variable should be destroyed only when there are no threads currently blocked on it. Destroying a condition variable that is
currently in use results in undefined behavior.
RETURN VALUE
Upon successful completion, and return zero. Otherwise, an error number is returned to indicate the error (the variable is not set).
ERRORS
If any of the following occur, the function returns the corresponding error number:
The system does not have the available resources (other than memory)
to initialize the condition variable.
The specified condition variable is an already initialized condition
variable. However, getting for reinitializing the condition variable cannot be expected all the time since the
behavior of reinitializing the condition variable is undefined.
The cond parameter points to an illegal address.
The value specified by
cond or attr is invalid.
There is insufficient memory available in which to initialize
the condition variable.
If any of the following occur, the function returns the corresponding error number:
An attempt to destroy
cond while it is in use by another thread.
cond is not a valid condition variable.
WARNINGS
The space for condition variable must be allocated before calling Undefined behavior will result if the process-shared attribute of attr is
and the space allocated for the condition variable is not accessible to cooperating threads.
AUTHOR
and were derived from the IEEE POSIX P1003.1c standard.
SEE ALSO
pthread_cond_signal(3T), pthread_cond_wait(3T).
STANDARDS CONFORMANCE
Pthread Library pthread_cond_init(3T)