How to find job runtime using Autorep


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting How to find job runtime using Autorep
# 1  
Old 12-10-2008
How to find job runtime using Autorep

Hey guys,

Is there an autorep option to find out the current runtime of a job..
Or do you have to work it out using machine time and start time?

What I'm trying to do is create a script that will email out the autosys job details. I was hoping there would be an autorep command that would return the jobs runtime.. Can't find anything on the cheatsheet or on the net about this..

Is there any other way around this? Am experimenting with the date function and trying to work out the run time that way but its not working out too well.. This is what I've tested with so far..

#! /bin/ksh -x
#
start=`date +%H%M`
#
sleep 120
#
end=`date +%H%M`
#
result=(($end - $start))
#
echo $result

But its coming back with:
date.ksh[9]: syntax error at line 9 : `(' unexpected



Thanks,
Jaz

Last edited by Jazmania; 12-10-2008 at 07:17 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to find the job outside the box?

Hi gurus, below file is job list, the records without s( in the begining is job name in the box, the records with s() is the job depends on them (some of them in the box, some of them not in the box). I need to use script to find the job name not in the box. sname-pname-cprexa... (6 Replies)
Discussion started by: ken6503
6 Replies

2. Shell Programming and Scripting

Autorep not found problem

Hi All, I am using a putty session to login a server in which autosys is installed. we get the GUI by entering . /opt/CA/UnicenterAutoSysJM/autouser/autosys.ksh.server and then jobscape. when i tried autorep -j jobname it gives me autorep not found. Please help me with this. (1 Reply)
Discussion started by: mahesh300182
1 Replies

3. Shell Programming and Scripting

How to find stack size at runtime?

hi, I just wondering is there any way that I can record the stack size of shell script at runtime. (2 Replies)
Discussion started by: yc962frank
2 Replies

4. Shell Programming and Scripting

Using awk with autosys autorep

Hi, How to get correct field/column from autosys autorep command. I'm using GNU/Linux I'm trying to get the difference of last end and last start and the status (ST). In awk, i get the following excluding the heading part $1 - jobname $2 - Last Start date $3 - Last Start time $4 - Last... (1 Reply)
Discussion started by: bobbygsk
1 Replies

5. Shell Programming and Scripting

autorep command in the script

I have created UNIX script for getting information for the autosys jobs using autorep command. Job_name=temp_job1 echo $Job_name autorep -j $job_name -l0 After running the script I am getting the below error Error while loading shared libraries: libautoeac_api.so: cannot share object... (1 Reply)
Discussion started by: onesuri
1 Replies

6. Red Hat

From where Machine name is taken in autorep report

Hi, When i tried to run a job on autosys which has to run a command on sys1 but its giving some other Machine name (sys56) , attempts ten times and fails. I would like to know from where this Machine column of autorep command gets input so that i can change to correct Host Machine (sys1) and... (4 Replies)
Discussion started by: Ishakarthi
4 Replies

7. Shell Programming and Scripting

How to find the job and its location

Guys; I first I thank you for helping me few times in the past; A job runs every day at 8AM and looks for a file “abcd.txt” in directory “/usr/task/tmp”. How to find the job and its location. I need to change the file name to “abcd.dat”. it is UNIX environment. (2 Replies)
Discussion started by: clem2610
2 Replies

8. Shell Programming and Scripting

autorep command in autosys

hi, i have autosys installed on unix. i use "autorep -j t8i%" command to see the scheduled jobs. now i have changed some of the jobs and saved them too. i gave the command jil< filename.jil to again insert the jobs. but my problem is what is the command to run all the jobs again so that i... (8 Replies)
Discussion started by: tejasingaraju17
8 Replies

9. Linux

Plz Help me to find GNU C++ Runtime Library

Hi, I am working with red hat Linux and i want to install one program but I am getting the error This product requires the GNU C++ Runtime Library (libstdc++-libc6.2-2.so.3) or later. Your system must be upgraded before installation can proceed. So please tell me how can i remove this... (2 Replies)
Discussion started by: smartgupta
2 Replies

10. Shell Programming and Scripting

autorep command cut longer jobnames. Anybody into autosys / autorep?

Hi there, my problem is, that i need to get all jobs with status from a autosys instance. If I use autorep -J ALL -d >joblist.txt longer Jobnames will be cut and the end will be replaced by 3 points like this "ThisIsALongerJobNameAnd..." If i try a single job query like ... (7 Replies)
Discussion started by: drmaniac
7 Replies
Login or Register to Ask a Question
DH_INSTALLINIT(1)						     Debhelper							 DH_INSTALLINIT(1)

NAME
dh_installinit - install upstart jobs or init scripts into package build directories SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [-O] [--params] DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing upstart job files or init scripts with associated defaults files into package build directories, and in the former case providing compatibility handling for non-upstart systems. It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ and to start and stop the init scripts. FILES
debian/package.upstart If this exists, it is installed into etc/init/package.conf in the package build directory. debian/package.init Otherwise, if this exists, it is installed into etc/init.d/package in the package build directory. debian/package.default If this exists, it is installed into etc/default/package in the package build directory. OPTIONS
-n, --noscripts Do not modify postinst/postrm/prerm scripts. -o, --onlyscripts Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it. If no upstart job file is installed in the target directory when dh_installinit --onlyscripts is called, this program will assume that an init script is being installed and not provide the compatibility symlinks or upstart dependencies. -R, --restart-after-upgrade Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which stops the script in the prerm, and starts it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. -r, --no-restart-on-upgrade Do not stop init script on upgrade. --no-start Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts. -d, --remove-d Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ , or for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.) -uparams --update-rcd-params=params -- params Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8). --name=name Install the upstart job file or the init script (and default file) using the filename name instead of the default filename, which is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.upstart, debian/package.name.init and debian/package.name.default, instead of the usual debian/package.upstart, debian/package.init and debian/package.default. --init-script=scriptname Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file, if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks like package.scriptname and if so will install it as the init script in preference to the files it normally installs. This parameter is deprecated, use the --name parameter instead. This parameter will be ignored completely for upstart jobs. --upstart-only Only install an upstart job file, and do not include maintainer script code to replace an init script with that upstart job. This parameter is intended for use when the "package.upstart" file is new and only to be used on Upstart-based systems. --error-handler=function Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts, before the #DEBHELPER# token. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHORS
Joey Hess <joeyh@debian.org> Steve Langasek <steve.langasek@canonical.com> Scott James Remnant <scott@canonical.com> 8.9.0ubuntu2.1 2012-06-12 DH_INSTALLINIT(1)