MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

Re: SQL output to csv



fixed

On 04-Dec-2013 08:23 -0800, Pete Helgren wrote:
On 12/4/2013 9:06 AM, Birgitta Hauser wrote:

It is possible to perform any CL command (that does not need an
output screen).

So it is possible executing an OVRDBF command just before the
SELECT command. You simply have to prefix the CL command with CL:
and end it with semi colon (;), It is even possible prompting the
CL command with the F4 function key.

Does it support MONMSG? I can work around some of the overrides,
etc in the SQL script but MONMSG is a cheap way of ignoring errors. I
am seeing either that MONMSG is not supported or an error that the
parameter MSGID is invalid in the script I am attempting. Perhaps an
example where MONMSG is used?


Rather than "any CL command (that does not need an output screen)", perhaps better stated as "any CL command that is allowed in the *BATCH and *EXEC" environments.?

MONMSG is only allowed in compiled programs; i.e. the command definition has "Where allowed to run (ALLOW)" including just the special values (*BPGM *IPGM). Scripting environments [not compiled] typically operate according to a Severity Level; i.e. when an error that exceeds the maximum specified as-allowed error-severity, the script terminates.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact