On 8/18/20, 9:57 AM, "CMSTSO Pipelines Discussion List on behalf of Alan
Altmark" <[email protected] on behalf of [email protected]>
wrote:
But I don't think this is a Pipe thing.
At least from an outside IBM perspective, this seems to be the first place new
CMS function is being actively developed, so it made sense to ask here first.
I would rather enhance the
NAMEFIND command to allow ADD, REPLACE, and DELETE operations. It knows
how to find an entry, and where an entry begins and ends in the file.
Rather than complicate the already baroque syntax of NAMEFIND even further, I'd
prefer it to be a separate new application, say NAMEUTIL. It's new function,
and probably shouldn't be lumped in with the decades of cruft that NAMEFIND has
accumulated.
I agree with your proposed functionality, though. I'd even add an APPEND
function if you know in advance that the entry does not exist so you could skip
the scan of the file for the keytag that would probably be needed for ADD. I'd
also really like to skip using the stack now that we can manipulate REXX
variables directly. Just set up or return a REXX stem and be done with it.
The ADD function might seem unnecessary, but in the context of NAMEFIND a
new entry would only be added if it didn't already exist.
It's also more logically consistent for the average end user to explicitly ask
for what you want to happen. I keep meaning to port sqlite to CMS, but ...
