Author: Robert Sample
Subject: Reply to: Search utility(3.14) using JCl and Cobol
Posted: Sun Jun 11, 2017 6:55 am (GMT 5.5)
So instead of waiting for the system utility to complete, you want to wait for YOUR utility to complete?
I assume you work for a company that is charging out your time -- no other explanation makes sense for the system resources and personal time you are wasting on this effort. Use ISPF 3.4 and the search function -- that is what it is for. Duplicating this functionality is NOT providing your company with any additional functionality.
Furthermore, your statement of what you are doing is so vague as to be useless. What if the PROC is stored in a PROCLIB? What if the control records are stored in a different data set than the JCL (which is usual for many sites)? Based upon what you have said, it appears you are going to HAVE to use a programming language to complete your task.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Subject: Reply to: Search utility(3.14) using JCl and Cobol
Posted: Sun Jun 11, 2017 6:55 am (GMT 5.5)
| Quote: |
| the time will be saved when we search using 3.14(search utility) as we need to wait till it completes. |
I assume you work for a company that is charging out your time -- no other explanation makes sense for the system resources and personal time you are wasting on this effort. Use ISPF 3.4 and the search function -- that is what it is for. Duplicating this functionality is NOT providing your company with any additional functionality.
Furthermore, your statement of what you are doing is so vague as to be useless. What if the PROC is stored in a PROCLIB? What if the control records are stored in a different data set than the JCL (which is usual for many sites)? Based upon what you have said, it appears you are going to HAVE to use a programming language to complete your task.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth