10 More Discussions You Might Find Interesting
1. 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
2. UNIX for Dummies Questions & Answers
All the autosys jobs are on server-1 and server-1 has been crashed due to some reason, Now I have to run 5 autosys jobs on server-2 (failover server) which are on server 1.
How to do with Autosys command (which command needs to fired on JIL) (0 Replies)
Discussion started by: tp2115
0 Replies
3. UNIX for Advanced & Expert Users
I have an autosys job say "job12345" . it has a a time dependacy. it does not depend on any other job. Once i put the job on HOLD. then after some time i directly marked it to INACTIVE after its normal run time is past. i didnt not off HOLD it but made directly to INACTIVE.
I can see the next... (2 Replies)
Discussion started by: Kaniska
2 Replies
4. Shell Programming and Scripting
Hi All,
I have trying to schedule an autosys job and it is failing. The shutdown script runs fine by itself from the UNIX box but fails when i try to schedule it through autosys.
I have compared user.env with auto.env (variables obtained through an autosys script) and updated my profile... (1 Reply)
Discussion started by: userscript
1 Replies
5. 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
6. Shell Programming and Scripting
#!/usr/bin/sh
read file
#exec 3<&0
exec 0<$file
while read line
do
if
then
BOUND=$line
break
fi
count=`expr $count + 1`
done
#exec 0<&3
echo $BOUND
sh check.sh (4 Replies)
Discussion started by: skyineyes
4 Replies
7. AIX
when try to unzip a very big file facing an error of disk full.
can any body help me to unzip this file .
$ unzip abc.zip
Archive: abc.zip
inflating: abc.zrp
abc.zip write error (disk full?). Continue? (y/n/^C) $ n
Thanks & Regards (2 Replies)
Discussion started by: suman_jakkula
2 Replies
8. Solaris
I have another Hdd problem with Ultra 1 machine
the hdd is segate (+-)17560 MB and when I start installtion of sun solaries 2.6 the system sees the hdd correctly, and the installtion goes fine with partioning the disk as follows
/ 150 MB
swap 500 MB
/user 1000 MB
/user1 100MB
/usr3 5500 MB... (4 Replies)
Discussion started by: adol3
4 Replies
9. UNIX for Dummies Questions & Answers
i accedently "deleted" all workspaces
I have a black screen and dont know what to do
solaris common desktop enviroment (1 Reply)
Discussion started by: ssshakir
1 Replies
10. UNIX for Advanced & Expert Users
Hi all,
In Tru64 UNIX,there is a command ulimit which sets or reports a resource limit.
-d option specifies number of Kilobytes for data area.
But when i give same man ulimit in HP-UX, it does shows some ulimit function.
I want to replace ulimit -d command in .profile file which... (1 Reply)
Discussion started by: informshilpa
1 Replies
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)
A problem in autosys-- very urgent