I have a CL program that calls another CL program and monitors for specific escape messages. No big deal. I put multiple Monitor Message (MONMSG) commands after the CALL. Suppose I want to call the second CL program from an RPG program. How do I monitor for the different errors?

–Ray

OK, Ray, let’s set this up for the readers. Let’s suppose your program, which we’ll call SOMEPGM, can return escape messages MYM2101 and MYM2105. A CL caller monitors for those messages like this:

CALL       PGM(SOMEPGM) PARM(&whatever) 
MONMSG     MSGID(MYM2101)  EXEC(DO)
/* do something */
ENDDO
MONMSG     MSGID(MYM2105)  EXEC(DO)
/* do 

Over the years, iSeries Access virtual printer emulation sessions have been used to successfully print a variety of spool file reports from System i and AS/400 systems to a local PC printer. Regardless of the report’s page attributes (page orientation, lines per inch, characters per inch, number of columns, etc.), the printer emulator will often successfully and automatically correct the output and automatically adjust the spool file’s page settings to print successfully to a local printer. However, in other cases it seems like it takes quite a bit of tinkering to get various spool files to print correctly to a

Part 2

In the last issue, I discussed some tricks for monitoring your system to detect storage problems. Today, I want to shift the focus from determining when your disk storage is filling up to what you can do to increase available drive space. I’ll do this by providing a checklist of several different techniques you can perform to retrieve system storage space that you might have thought was lost forever.

Finding the Right Cure for Your Storage Woes

Disk drive capacity issues can cause system problems when i5 storage usage passes the 90 percent level. Performance degradation starts