Problem solve Get help with specific problems with your technologies, process and projects.

Members comment on QSYSOPR tips

We asked for your comments to these tips, and boy did we get them. This time we did receive a blizzard -- 29 of you e-mailed us your comments, as well as even more alternatives.

The majority of you said the methods from Richard Nichols, Jack Flannery and Richard Mansell work fine, but there's a much easier and shorter method: Invoke the system request (shift / esc or set up a keyboard shortcut), enter a 6 and press enter. This way you can preserve the ATTN key for other purposes, and you don't need a CL to do the job.

As search400 member Steven Martinson wrote:
"Why bother with any of that stuff? If you don't keep track of changes or customizations residing in the Q libraries, you can easily blow them away during an upgrade.

I have always used the following key sequence from ANY AS/400 screen, even when a number of menus deep into an application:

(Upper Shift + SysReq/ATTN) and then enter "6" on the line, press Enter and Presto! There's your QSYSOPR message queue.

This is the same place that you would enter "2" to cancel your last request,"4" to get current job message queue, etc."

Reggie Ward wrote:
"Like Jack Flannery, We use the attention key for other purposes. What I do when I want to see QSYSOPR messages is press the SHIFT key and the ESC key to get a SYSTEM REQUEST line; type the number 6; then press the ENTER key. If you have not used the SYSTEM REQUEST line function before or are not familiar with the options, then don't key in any number and just press the ENTER key. The SYSTEM REQUEST menu will appear and will allow you to select an option."

Michael Acosta wrote:
"Unlike the other responses my alternative doesn't require programming.

From an AS/400 'green screen' (dumb terminal): Press the shift & system request keys, then enter a 6 for Qsysopr Messages.

From Client Access screen (PC): Press the shift & escape keys, then enter a 6 for Qsysopr Messages. "

And a couple of you submitted even other possibilities:

From Kevin Theeck:

Here's another method of displaying QSYSOPR messages. This method only requires you to create a command. Here's my example for displaying QSYSOPR messages (DQ):

            CMD        PROMPT('Display QSYSOPR Messages')            
            PARM       KWD(CMD) TYPE(*CHAR) LEN(29) +                
                            CONSTANT('DSPMSG QSYSOPR ASTLVL(*BASIC)')   
            PARM KWD(LEN) TYPE(*DEC) LEN(15 5) CONSTANT(29)     

Copy the above lines into a command source member. Please note that the length of both parms is 29, the length of the command string we entered in the constant parm. Also note that I set the assistance level to *BASIC so that you will see messages needing a reply first. This method makes it quick and easy to create other shortcuts. Compile the command as follows:

                            Create Command (CRTCMD)                
Type choices, press Enter.                                         
Command  . . . . . . . . . . . . . . . . . CMD         > DQ                 
  Library  . . . . . . . . . . .                                >       QGPL

Program to process command . . . PGM         > QCMDEXC            
  Library  . . . . . . . . . . . . . . . . . .
Source file  . . . . . . . . . . . . . . . . .SRCFILE        QCMDSRC

  Library  . . . . . . . . . . .                  *LIBL            
Source member  . . . . . . . . . . . . .SRCMBR         *CMD               
Threadsafe . . . . . . . . . . . . . . . . .THDSAFE        *NO      

From Mary C. Milliron:
Since I'm in PDM much of the time, I've just added two options to my PDM Options file:


The first option shows all the messages, and the second one only shows those needing a reply.

Dig Deeper on Performance