Re: [Bulk] Generating the listing when compiling a command

On 03-May-2016 08:53 -0500, Mark S Waterbury wrote:

On 5/3/2016 9:30 AM, Darryl Freinkel wrote:

I have a situation where I need to rebuild a system which has a
number of command and programs. I am able to tell the compiler not
to print the listing however, there does not seem to be a parameter
on the create command to tell it not to print the command.

I could add a DLTSPLF command to do it, but I would prefer to
include it in the CRTCMD.

Is there a way to do this?

This is a V5R4 system.

You could do this:

CRTPF QTEMP/PRT133 RCDLEN(133) LVLCHK(*NO)
and
OVRPRTF FILE(QSYSPRT) TOFILE(QTEMP/PRT133)

Then, run your CRTCMD as usual. Instead of generating a spool file,
it will write the output into the QTEMP PRT133 file.

Hope that helps,

If the default for SIZE() remains other than *NOMAX, and too if the default is SIZE(*NOMAX), then either way, beware the problems for actually having written records using that method. Sadly there is not /special/ STMF '/null' to which data can be directed with the intention of that data going to the ether; nor is there an INHWRT parameter keyword on OVRPRTF :-(

Might I suggest instead then, the following, for which there is no concern for msg CPA5305 [or side effects]; the methodology utilizes Override With Database File (OVRDBF) [instead of Override With Printer File] of the printer file name, in order to utilize an effect of the alluded '/null' output, by using the Inhibit Write (INHWRT) feature that Common Data Management *does* provide with OVRDBF:

crtpf qtemp/bitbucket mbr(null) rcdlen(1) lvlchk(*no) allocate(*no)
ovrdbf qsysprt qtemp/bitbucket inhwrt(*yes) ovrscope(*calllvl)
dowhile (&notdone)
crtcmd ...
enddo
dltf qtemp/bitbucket
dltovr qsysprt lvl(*)