Login or Register to Ask a Question and Join Our Community


Shell Programming and Scripting

How to find job runtime using Autorep

Login to Discuss or Reply to this Discussion in Our Community

 
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

LEARN ABOUT X11R4

systemd-debug-generator

SYSTEMD-DEBUG-GENERATOR(8)				      systemd-debug-generator					SYSTEMD-DEBUG-GENERATOR(8)

NAME

       systemd-debug-generator - Generator for enabling a runtime debug shell and masking specific units at boot

SYNOPSIS

       /lib/systemd/system-generators/systemd-debug-generator

DESCRIPTION

       systemd-debug-generator is a generator that reads the kernel command line and understands three options:

       If the systemd.mask= option is specified and followed by a unit name, this unit is masked for the runtime, similar to the effect of
       systemctl(1)'s mask command. This is useful to boot with certain units removed from the initial boot transaction for debugging system
       startup. May be specified more than once.

       If the systemd.wants= option is specified and followed by a unit name, a start job for this unit is added to the initial transaction. This
       is useful to start one or more additional units at boot. May be specified more than once.

       If the systemd.debug_shell option is specified, the debug shell service "debug-shell.service" is pulled into the boot transaction. It will
       spawn a debug shell on tty9 during early system startup. Note that the shell may also be turned on persistently by enabling it with
       systemctl(1)'s enable command.

       systemd-debug-generator implements systemd.generator(7).

SEE ALSO

       systemd(1), systemctl(1), kernel-command-line(7)

systemd 237														SYSTEMD-DEBUG-GENERATOR(8)