|
View previous topic :: View next topic
|
| Author |
Message |
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
We can submit 'Request For Enhancements' to IBM using it's developerworks site. You can submit a request to IBM and then other users may vote for it. The more votes a request gets, the more likely it will be that IBM implements the suggestion.
My suggestion, 59845, is about providing a SRCHFOR primary command in the SDSF job queue display. It should work in a similar fashion as SRCHFOR in the Data Set List. It should read the entire contents of each job and identify the jobs that contain the search text. Please vote for this RFE. See www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=59845 Sorry, you have to register for a user id to vote.
Another suggestion, 59846, is very similar. It is about providing a SRCHFOR primary command in SDSF job step display, when you open a job using the '?' line command. It should work in a similar fashion as SRCHFOR in the Data Set List. It should read the entire contents of each job step and identify the steps that contain the search text. Please vote for this RFE. See www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=59846 Sorry, you have to register for a user id to vote.
"Vote for Pedro" |
|
| Back to top |
|
 |
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
Pedro, Thats Great!
For 59846-->
However, I always do "SE" and "XDC" in case to do what you have just pointed out. So I am not sure if others as well do the same. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
When you use XDC, SDSF will both read from the spool and write to a data set, then you will read it again from the data set so you can search. What I am asking for is to read it only from the spool... a 66% improvement in I/O.
Plus, there is a likelyhood that you will use XDC on jobs that were not really of interest to you.
BTW: The SJ, SE and XDC line commands of SDSF, as well as the rexx api of SDSF were my suggestions from several years ago. Also, SRCHFOR in the data set list and in the member list were my suggestions. |
|
| Back to top |
|
|
Terry Heinze
JCL Moderator
Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA
|
|
|
|
| Great idea -- I voted. |
|
| Back to top |
|
|
Rohit Umarjikar
Global Moderator
Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA
|
|
|
|
| Quote: |
| The SJ, SE and XDC line commands of SDSF, as well as the rexx api of SDSF were my suggestions from several years ago. |
Nice to know this fact.
| Quote: |
| When you use XDC, SDSF will both read from the spool and write to a data set, then you will read it again from the data set so you can search. What I am asking for is to read it only from the spool... a 66% improvement in I/O. |
I understand this XDC would be having more I/O. But when we know the job name and job number then if I do SE then would it also be having same I/O's ( as per it is just opening in edit mode instead of view mode)? and in this case would SRCHFOR is a better choice vs SE?
Thanks for the explaination in advance.
I voted too. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Quote: |
| when we know the job name and job number |
SRCHFOR would be for the case where you do not know which job it is. I anticipate that you would use SRCHFOR to identify the jobs, then follow that with use of S or SE to open the jobs of interest.
You can probably do SE then issue FIND commands to accomplish something similar to SRCHFOR. But if you have hundreds of jobs, using SE and FIND commands is tedious. Having SRCHFOR would be a nice useability improvement. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| thanks for voting Terry. |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
| Pedro wrote: |
When you use XDC, SDSF will both read from the spool and write to a data set, then you will read it again from the data set so you can search. What I am asking for is to read it only from the spool... a 66% improvement in I/O.
Plus, there is a likelyhood that you will use XDC on jobs that were not really of interest to you.
BTW: The SJ, SE and XDC line commands of SDSF, as well as the rexx api of SDSF were my suggestions from several years ago. Also, SRCHFOR in the data set list and in the member list were my suggestions. |
Dude! I owe you a beer.  I use all of those commands every day. I have used the rexx api also, most notably to automate the XDC command.
I have voted for your latest enhancement request. |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
| Don, thanks for the offer. If I am ever in that area, I will take you up on it. :-) |
|
| Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006
Posts: 2547
Location: Silicon Valley
|
|
|
|
FYI. IBM closed this requirement as 'already delivered' because you can write your own SRCHFOR with the SDSF API for REXX.  |
|
| Back to top |
|
|
don.leahy
Active Member
Joined: 06 Jul 2010
Posts: 765
Location: Whitby, ON, Canada
|
|
|
|
Sorry to hear that.
I was hoping that IBM would deliver. I will probably end up creating my own search function. |
|
| Back to top |
|
|
|
|
