04-20-2011
We run Autosys here, but I'm sure it's not the conventional way. One daemon that might be in common is 'auto_remote'. Grep for this process and see if that is running.
If this is different, then I would first try to find out what user Autosys runs as. Then grep on that user and see if you can find a process that appears to be from Autosys.
Sorry about not being able to help you further. Hope that helps you though.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am having problems running a script from AutoSys. The script runs fine when I run it manually, but errors out when run from AutoSys.
Error:
db2: not found
In the script, we are directing a query to db2.
Query1.sql 01/01/2004 | db2 +p >> sql.out 2>&1
where Query1.sql is an... (2 Replies)
Discussion started by: ramsi_ece
2 Replies
2. 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
3. Shell Programming and Scripting
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
4. 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
5. 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
6. 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
7. 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
8. 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
9. Shell Programming and Scripting
Hi,
Is there any specific command to use to check only say Running jobs via autorep or similar command for Autosys? (0 Replies)
Discussion started by: sidnow
0 Replies
10. Shell Programming and Scripting
How can I check if "Autosys" is installed on my Linux and Solaris servers ?
I prefer Autosys instead of Crontab. (4 Replies)
Discussion started by: mohtashims
4 Replies
LEARN ABOUT HPUX
serialize
serialize(2) System Calls Manual serialize(2)
NAME
serialize() - force target process to run serially with other processes
SYNOPSIS
DESCRIPTION
The system call is used to force the target process referenced by the pid value passed in to run serially with other processes also marked
for serialization. If the value of pid is zero, then the currently running process is marked for serialization. Once a process has been
marked by the process stays marked until process completion, unless is reissued on the serialized process with timeshare set to 1. If
timeshare is set to 1, the process specified in pid will be returned to normal timeshare scheduling algorithms.
This call is used to improve process throughput since process throughput usually increases for large processes when they are executed seri-
ally instead of allowing each program to run for only a short period of time. By running large processes one at a time, the system makes
more efficient use of the CPU as well as system memory, since each process does not end up constantly faulting in its working set, to only
have the pages stolen when another process starts running. As long as there is enough memory in the system, processes marked by behave no
differently from other processes in the system. However, once memory becomes tight, processes marked by are run one at a time with the
highest priority processes being run first. Each process runs for a finite interval of time before another serialized process is allowed
to run.
RETURN VALUE
returns zero upon successful completion, or nonzero if the system call failed.
ERRORS
If fails, it sets (see errno(2)) to the following value:
The pid passed in does not exist.
WARNINGS
The user has no way of forcing an execution order on serialized processes.
AUTHOR
was developed by HP.
SEE ALSO
serialize(1), privileges(5).
serialize(2)