Job Message Queue
From: Vern Reeve
To: All Programmers
I've noticed that when I do a CHAIN to a subfile with a relative record number which doesn't exist in the subfile, it adds a message to my job message queue which says subfile record doesn't exist. Is there any way to prevent these low-severity messages from being added to the job message queue?
From: Ernie Malaga
To: Vern Reeve
You can probably do what you want with the LOG parameter in the Change Job (CHGJOB) command. The second element in the LOG parameter indicates the minimum severity needed before a message is logged. I think this element defaults to 00, which is why all messages are logged. If you change it to one level higher than the severity of the message you want to avoid, the message won't appear. Check the severity level of the pesky message with the Display Message Description (DSPMSGD) command.
From: John Clark
To: Vern Reeve
Sometimes I receive unwanted messages in my program message queue, but I do a CALL to a CL program that does a RMVMSG PGMQ(*PRV) CLEAR(*ALL) that clears them out.
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