×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Fri, Jan 23, 2015 at 3:47 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:
You can store your executable CL commands in a source file and issue a
SBMDBJOB. It will read each command and execute until the job ends. It just
has to be executable at the command line.
That's pretty neat. If I understand correctly, you're saying you have
a "CL script" in some source file, and SBMDBJOB is basically an
interpreter for that script. (And with a slight bit of digging, there
is the extremely similar STRDBRDR.) While kind of interesting to
know, just because knowing stuff is cool, it seems these are horribly
limited, though. They strike me as offering very little value over
(1) on-the-fly CLP compilation or (2) Rexx.
Interestingly, Thomas Raddatz asked for ideas on
comp.sys.ibm.as400.misc back in July 2000 about ways to write a "CL
interpreter". He had already written his own command called RUNCLSCT,
but he wasn't completely satisfied with it. He also explained why
STRREXPRC, STRDBRDR, and SBMDBJOB were all very close, but did not
quite suit his purposes.
John Y.
As an Amazon Associate we earn from qualifying purchases.