×
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.
IBM's RUNSQL command came out with certain PTF's.
It exists in QSYS
DSPCMD RUNSQL
Command . . . . . . . : RUNSQL Library . . . . . . . : QSYS
Program to process command . . . . . . : QSQSCHEM
Library . . . . . . . . . . . . . . : QSYS
There's two major issues with it, and the third party products that came
out.
The first being the parameter names have changed. This is the #1 killer
with imbedded versions of RUNSQL. The first parameter in the IBM version
is SQL. The first parameter in other versions may be REQUEST or some such
thing.
The second major issue is that the IBM one will not let you do a simple
SELECT.
RUNSQL SQL('select * from routines/dskdtl')
SQL statement not allowed.
Another issue is that the IBM version defaults to running under some sort
of commitment control so you often have to
RUNSQL SQL(...) COMMIT(*NONE)
If you're not journalling, or you do not want to forget to 'commit' your
changes.
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
