Sorry for the late response as I am out for some personal emergency. Thanks for your help, I am reviewing this now and will update you soon. Thanks again.

---------- Post updated at 07:31 AM ---------- Previous update was at 07:03 AM ----------

Of this file you only need the lines containing "STATUS: STARTING" and some ending notification. This could perhaps be "STATUS: SUCCESS", but somehow i don't believe that all jobs end that way - what other possible ending codes do you have, because your script will need to cover them too.

Let us go on, assuming for the moment that the only endng condition is "SUCCESS", this can be corrected later.

Next we make up some "rules" what to do with the respective lines, because at some point we need to read our input line by line:

- When we encounter a "STARTING" line we need to remember two things, the job name and the timestamp.

- When we encounter a "SUCCESS"-line we need to read also two things: the job name and the timestamp. But we don't need to store ("remember") them: the job name should be searched in our list of remembered (=started) jobs. If it is found, the stored starting time, the end time and the job name is printed.

The last point begs two questions: what are we going to do if we encounter a job with a start but no end? And what are we going to do with jobs with an end but no start?

Here is the skeleton of a shell script that implements what i said above. Neither is it very clever nor very mature, its intention to make it obvious how to implement common reasing like above into code. It also won't take the raised questions into account and implicitly assume that all jobs end with success and every starting job also ends and vice versa.

We start by filtering and displaying only the lines we are interested in:

++++++++++++++++++++++++++
++++++++++++++++++++++++++

Your above reply is very much correct and matches the exact requirement.

I tried the above script but it searches STARTING and SUCCESS for all job, whereas I need for specific job.
Also could you please tell what junk means ?
Can I use job name as $1 (1st arguement), so that it can changes as per requirement

Code:

#! /bin/ksh

name=$1

typeset    infile="/home/sbehera/out/event_demon.ACE*"      # file we read from
typeset    cond="SUCCESS"                               # condition of the job, "STARTING" or "SUCCESS"
typeset -i count=1                               # counter for the newest element of the storage arrays
typeset -i i=1                                     # counter for searching the storage arrays

echo $infile $cond $name $count $i


zgrep ""STATUS: SUCCESS"  "STATUS: STARTING"" "$infile" |\
while read date time junk junk junk junk cond junk name junk ; do

     echo "name is: $name   condition is: $cond  time is: $date $time"       # we leave that in for now, to see what the script works on


case $cond in
          STARTING)
               typeset aname[$count]="$name"
               typeset atime[$count]="$date $time"
               (( count += 1 ))
               ;;

          SUCCESS)
               (( i = 1 ))
               while [ $i -lt ${#aname[@]} ] ; do               # walk though the array
                    if [ "${aname[$i]}" = "$name" ] ; then     # we found the corresponding entry
                         print "${aname[$i]} \t${atime[$i]} \t $date $time"
                    else
                         (( i += 1 ))
                    fi
               done
               ;;

     esac
done

exit 0




Output:

$ sh run.sh IOXXXXXMO_XXXILEO
/home/sbehera/out/event_demon.ACE 
/home/sbehera/out/event_demon.ACE.07092017.gz 
/home/sbehera/out/event_demon.ACE.07102017.gz 
/home/sbehera/out/event_demon.ACE.07112017.gz 
/home/sbehera/out/event_demon.ACE.07122017.gz 
/home/sbehera/out/event_demon.ACE.07132017.gz 
/home/sbehera/out/event_demon.ACE.07142017.gz 
/home/sbehera/out/event_demon.ACE.08102017.gz SUCCESS IOXXXXXMO_XXXILEO 1 1
SUCCESS  STATUS:.gz: No such file or directory
STARTING.gz: No such file or directory
/home/sbehera//out/event_demon.ACE*.gz: No such file or directory

Moderator's Comments:

Please use CODE tags as required by forum rules!