I have what I hope is a simple question. A CL program that runs in batch mode calls an RPG program, passing parameters to it. If the RPG program finds a certain error, it sets one of those parameters to a certain value, sets on the LR indicator, and ends. At this point, the CL program ends, but the message that it generates gives the caller the impression that the job ran OK. How do I make the program end abnormally?

–Mike

That’s a good, basic question, Mike, and I understand why you bring it up. This phenomenon drove me

In the article, iSeries Security Journal Receiver Management, Part 1, I described how the OS/400 operating system logs security events that occur on your system in journal receivers associated with the QAUDJRN journal in library QSYS when iSeries security monitoring is activated. Also recall from Part 1 that you can set these audit journal receivers to record different types of security events, such as a change to a system value or user profile, or an unsuccessful attempt to access an object.

The journal information can then be used:

• To detect security errors and violations
• To plan migration to a

There are so many valuable printing options in i5/OS and OS/400 that it’s easy to miss some techniques for improving spooled file processing. I discovered that this week when I found two tricks that allowed me to automatically suppress printer load form messages and to segregate printer output so that I can print different sets of reports that should not be mixed on the same printer. Here are the techniques I found and how they can help in your shop.

Trick #1: An Easier Way to Suppress Printer Load Form Messages

In an earlier column, I presented a technique for