Joel:

I wrote a small OPM COBOL/400 program with a DISPLAY statement to reproduce this, compiled it, and called it, and then placed the cursor on the message that appeared on my interactive screen and pressed F1=Help, then F9=Message details, and there I saw the name of the program that sent this message was QSYS/QLRADRTN ... So, I issued:

DSPPGM QSYS/QLRADRTN

and paging down reveals that this program has just one parameter.

So, next, I wrote this little CL program, also named QLRADRTN:

/* COBOL/400 runtime routine to ignore DISPLAY statements */
/* Nota bene: must be placed in a library ahead of QSYS */

PGM PARM(&MSG)
DCL VAR(&MSG) TYPE(*CHAR) LEN(255)
RETURN
ENDPGM

I compiled it into a test library and added that library to my session *LIBL ahead of QSYS, by issuing:

CHGSYSLIBL TESTLIB1 *ADD

(/NOTE: you may need to get a sys. admin. to grant you access to use the CHGSYSLIBL//command.)/

Then, I called my little test COBOL program with the DISPLAY statement again, and nothing showed up this time.

Hope that helps,

Mark S. Waterbury

> On 1/17/2017 12:24 PM, Stone, Joel wrote:
Working on an OPM COBOL prod pgm, that has many DISPLAY commands that write messages to the job log.

Is there a CL command that will inhibit the writing of these messages?

For testing, it slows down the time dramatically.

I know I can wrap IF statements around the dozens of display statements. Is there a simpler way in CL?

Something like:

OVRDBF FILE(X) INHWRT(*NO)
But for COBOL display messages?


Thanks!



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2021 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.