Re: Quick question about DSPLY

On 16 Jan 2013 09:18, James H. H. Lampert wrote:

As I recall, when a DSPLY statement is run in a batch job, the
message normally goes to the QSYSOPR message queue.

Can this be suppressed, in a way that affects the entire job?

Why not just code the DPLY with the desired message queue; e.g. '*EXT' for the so-called "output-queue" argument [or Factor 2] so that "The message is sent to the external message queue" of the job?

Note that the output-queue can be specified as a variable which can be assigned as blank for the default behavior, or changed to *SYSOPR or *EXT, or changed to a 10-byte message queue name that should be in the library list; though any value other than a special value or QSYSOPR would increase the chances for error and thus a need to "handle DSPLY exceptions (program status code 333), either the operation code extender 'E' ...". Changing each use of DSPLY in a program to name that variable and assigning that variable once to define the behavior is probably the clearest means to effect the desired.
http://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/c092508302.htm#ToC_811

Depending on how the run-time is coded to effect the send message activity, there is possibly a way to get the message to go to a different queue named QSYSOPR for the job, but only by opening a potential for usage error; i.e. there is no support by the OS for an alternate message queue named QSYSOPR, and any use of such would be considered a usage error, esp. if for example there were any negative side effects.