Or put DMPCLPGM [optionally DSPSPLF ¿QPPGMDMP? and DLTSPLF] in the source [perhaps conditioned on a InDebug() test], or precede the OPNQRYF with the prompt request character to make it ?OPNQRYF [perhaps adding a MONMSG CPF6801 EXEC(goto skip) so it exits nice].

Regards, Chuck

vhamberg@xxxxxxxxxxx wrote:
Or running debug and put a breakpoint just after the variable is done
being constructed

Mark S. Waterbury" wrote:

It often helps to insert a line similar to the following, just
prior to issuing the OPNQRYF statement:

SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA(&SELECT) + TOPGMQ(*PRV (*)) MSGTYPE(*DIAG)

That way, you can see in the job log exactly what the selection
criteria actually looked like.

You can also add this statement:

SNDPGMMSG MSGID(CPF9898) MSGF(QCPFMSG) MSGDTA(&SELECT) + TOPGMQ(*EXT) MSGTYPE(*STATUS)

Then, you will see it on the message line when run interactively.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.