Search Job Log Using Wildcard (from SDSF Output)



TSO Programming, ISPF, SDF, SDSF and PDF, FTP, TCP/IP Concepts, SNA & SNA/IP etc...

Search Job Log Using Wildcard (from SDSF Output)

Postby msidoa » Sun Nov 16, 2014 6:09 am

How can I search SDSF output for JES2 Job Logs using a wildcard?

I want to execute a find command that works like this but I can't find the right syntax:
COMMAND INPUT ==> f 'REGISTER KEY (11111) <wildcard> success' next

Please avoid approaches that involve creating new datasets, I am hoping for just the right way to search the file if at all possible.

There are many REGISTER KEY values - but the example below shows only 4 different keys 11111, 22222, 33333, 44444.
I have no control over the output file, can't make changes to it.
I need find the date-stamps when there is "success" for a specific REGISTER KEY.
We don't care about client thread # but it being there prevents a simple search for a string that contains both key value & "success".

I want a search that finds lines like this:

<some datestamp> REGISTER KEY (11111) - client thread 2354123 success
<some datestamp> REGISTER KEY (11111) - client thread 3456345 success
<some datestamp> REGISTER KEY (11111) - client thread 0909733 success
<some datestamp> REGISTER KEY (11111) - client thread 1123433 success
<some datestamp> REGISTER KEY (11111) - client thread 9878333 success

COMMAND INPUT ==> f 'success' next
Takes a long time. That's a lot of <F5> commands to see them all because there are 1,000s of lines that match due to all the keys.

COMMAND INPUT ==> f '(11111)' next
Takes a long time. That's a lot of <F5> commands to see them all because many other output lines that refer to the same key.

<100s of lines>
<some datestamp> REGISTER KEY (11111) - client thread 2354123 success
<100s of lines>
<some datestamp> REGISTER KEY (11111) - client thread 2354123 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (22222) - - client thread 987987 doing success
<100s of lines>
<some datestamp> REGISTER KEY (11111) - client thread 2354123 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (22222) - client thread 987987 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (33333) - client thread 999998 fail
<100s of lines>
<some datestamp> REGISTER KEY (33333) - client thread 999998 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (11111) - client thread 123123123 success
<some datestamp> REGISTER KEY (22222) - client thread 2354123 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (11111) - client thread 123123123 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (44444) - client thread 345345 success
<some datestamp> REGISTER KEY (11111) - client thread 2355555 success
<some datestamp> REGISTER KEY (22222) - client thread 234236 success
<some datestamp> REGISTER KEY (33333) - client thread 2354123 success
<100s of lines>
<some datestamp> REGISTER KEY (33333) - client thread 2234235 fail
<some datestamp> REGISTER KEY (11111) - client thread 5555899 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (11111) - client thread 787777 success
<some datestamp> REGISTER KEY (44444) - client thread 2354123 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (22222) - client thread 111343254 fail
<some datestamp> REGISTER KEY (33333) - client thread 2354123 doing some stuff
<100s of lines>
<some datestamp> REGISTER KEY (22222) - client thread 111343254 success
<some datestamp> REGISTER KEY (22222) - client thread 987987 doing some stuff


This is my 1st post, here is some background on me:

I work in production support for a major bank - in my current position I supporting multiple messaging hubs that route real time financial transactions for over 100 internal enterprise financial apps. Our legacy MQ systems are deployed on the mainframes. This is my 1st exposure to mainframe work after 15 years working in IT. For compliance reasons my team has a very limited capabilities on z/OS & that is never going to change so I don't need a deep skill-set here.

I have worked for 2 years in this position & learned what I need in order to navigate, view job status & output, etc. I don't have time to dig in & really try to understand everything mainframe but it is not so easy to just go online & pull up answers for my questions compared to say Java, UNIX, or Oracle work. I typically spend an hour or so on any given day in z/OS. It's enough that I need to make an effort to be more efficient/effective at the tasks I do have, thanks in advance to any that offer help.
msidoa
 
Posts: 1
Joined: Sun Nov 16, 2014 3:00 am
Has thanked: 0 time
Been thanked: 0 time

Re: Search Job Log Using Wildcard (from SDSF Output)

 

Re: Search Job Log Using Wildcard (from SDSF Output)

Postby prino » Sun Nov 16, 2014 2:53 pm

If you can look at the SDSF output using the SB or SE commands, you can use the normal Edit and Browse find command, which supports picture strings:

f p'REGISTER KEY $11111$ = client thread ####### success'
Robert AH Prins
robert.ah.prins @ the.17+Gb.Google thingy
User avatar
prino
 
Posts: 536
Joined: Wed Mar 11, 2009 12:22 am
Location: Oostende, Belgium
Has thanked: 3 times
Been thanked: 21 times


Return to TSO & ISPF

 


  • Related topics
    Replies
    Views
    Last post