Tweet
I couldn't agree more with the previous post. We also have a home grown command with the same name and it is used extensively within our large commercial ERP application. We really need as many details about this as we can possibly get and can't wait until we can get our hands on the PTF's to research the impact. Can you possibly get your hands on more details and pass them along?
-
-
We also have our own RUNSQL command, but in place of the SQL parameter ours is called STM. No problem, I'll just amend all of the calls to our RUNSQL command to QUSRSYS/RUNSQL and we're back to normal again. Except that the IBM command doesn't allow a simple SQL Select statement.
By far the greatest use of RUNSQL is a quick command line RUNSQL followed by F4 then key in 'Select * from etc etc' and that's it. IBM's RUNSQL allows you to enter 'Select * from' but then doesn't seem to do anything. No screen output, no printed output, no anything. I've checked the IBM documentation ( http://publib.boulder.ibm.com/infoce...bafyrunsql.htm ) and, sure enough, 'Select from' isn't one of the usable SQL statements.
I'd hold back on the thank you cards for now. -
love the new command hate the name
** This thread discusses the article: The CL Corner: Introducing the New Run SQL Command **
There are lots of shops that have built their own version of RUNSQL ocmmand over the years.
The problem is that since IBM is late to the game they should not pick a command name that will most certainly interfere with years of development around user tools with the same name.
I know they cannot know the name of every command that exists but surely they should have thought this name was "taken".
Pardon me while I try and figure out what we are going to do about the name conflict before we load that DB group PTF.Comment
Comment