Two of my favorite features of RSE are the Outline View and the Program Verifier. One thing they both have in common is the fact that they use cached descriptions of any required externally described files. These cached descriptions are retrieved once and then stored in the RSE workspace for fast retrieval when required to refresh the Outline View or when Verifying the code in the editor.

Because both these features rely on those cached descriptions, they also have something else in common; when a file’s external description changes, neither of them will automatically catch on to that fact. Therefore

I had a problem last week. I was monitoring for error messages after an Add Physical File Member (ADDPFM) command in a CL program. Well, OS/400 sent two CPF messages when ADDPFM failed. MONMSG would only trap the second message, but I wanted to trap the first one because that’s the one that tells me what went wrong. What do I need to do?

–Chris

This seems like a good time to review some messaging fundamentals. Chris is not a newbie programmer, so if he doesn’t understand, there are probably others who don’t understand either.

When a CL command fails,

Your article of 01/01/05 says you can add tasks to a source member or to specific lines in a source member. In 7.0.0.6, I’m able to do the latter but not the former. Can you point me in the right direction?

–RJS

I haven’t switched to V7 of WDSc yet, but if things are the similar to what they are in V6, then the following should work:

• You must be using iSeries Projects perspective and have created a project for your source.
• Select (single-click) the source member that you want to add a task for.
• In the Tasks View, there