In Part 1 of this tip, I talked about getting started with RDi’s Source Call diagram. Now let’s continue on the journey.

I’ll first cover the basics of the second type of diagram, the Program Structure Diagram. Then I’ll cover some notes that apply to both types about customizing, saving, and using your Application Diagrams for your own documentation.

The Program Structure diagram shows relationships between application objects, such as programs that call other programs or reference Service Programs. An example of a very simple Program Structure diagram is shown below.

GRAPHIC1

This diagram shows the relationships between three programs

I have an RPG question. Now that indicators are verboten, how does an RPG program distinguish between record types when reading a multi-format logical file? That is, what do I use instead of record identifying indicators?

–Tricia

Define a file information data structure for the logical file. The system will place the record format name in positions 261-270. Here’s some sample source code to get you started.

CODE1

–Ted

                     Post this story to del.icio.us
               Post this story to Digg
    Post this story to Slashdot

My i5/OS partition disk storage is filling up and it hit 85 percent utilization today. How do I tell how much temporary storage space my system is using? If there’s a lot of temporary storage, what can I do about it? I heard that if you IPL a partition, you can reduce disk usage.

–Mick

While an IPL can reclaim temporary storage space, it’s wise to first check out how much temporary space is being used on the system, just to see if it’s worth your while to IPL. Since iSeries, System i, and Power i machines generally run for