When you display the QSYSOPR message queue, you probably spend a lot of time trying to locate important messages. This is because everything is sent to this queue. You should consider creating an alternate message queue-QSYSMSG. Key in the following:
CRTMSGQ MSGQ(QSYS/QSYSMSG) + TEXT('Optional MSGQ to receive specific system messages') When this queue exists (in QSYS only), certain messages are directed to it instead of, or in addition to, the QSYSOPR message queue. You can then run DSPMSG QSYSMSG to view the messages. You can also write a break handling program to receive messages for which you can perform special actions. The program can send messages to the QSYSOPR message queue or another message queue. Disk unit failure messages, for instance, are sent to QSYSMSG. For a complete list of all the messages directed to QSYSMSG, and for an example of a break handling program, look at the AS/400 CL Programmer's Guide (SC41-8077, CD-ROM QBKA7102).
- Jean Jacques Risch
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online