RULNestedOverFlowProc

Use this form level rule to nest overflow within overflow. The nested overflow can occur on as many levels as necessary. This lets you use the system as a reporting tool. The only requirement is that the data occur in order.

This rule lets you create groups that contain group headers (lead sections), subordinate sections (list sections), and group footers (following sections).

Syntax

;RULNestedOverFlowProc;;;

Insert this rule in the AFGJOB.JDT file just after the RunSetRcpTbl rule.

To specify how the nesting occurs, you must create a file named OVERFLOW.DAT. You can create this file using any ASCII editor. By default, the system looks for this file in the DefLib directory, however, you can specify a different path and file name as the second parameter. Here is an example:

;RULNestedOverFlowProc;;c:\fap\dll\newfile.dat;

OVERFLOW.DAT file format

The file format for the OVERFLOW.DAT file is as follows:

;LeadIMG;LeadMask;ListIMGInfo;ListMask;FollIMGInfo;

Before this rule is called, the lead section should already be in the form set—either through normal section triggering or by placing another call to this rule on a previous line.

The system begins by reading the OVERFLOW.DAT file line by line. The system finds the first occurrence of the lead section in the form set and then finds the first occurrence of the lead mask in the extract file.

It then counts the number of list masks between the first and second lead mask. Next, the system inserts the number of list sections after the first lead section and then inserts the follow section.

The system continues going through the form set inserting the number of list sections in between the nth and (n+1)th lead sections, according to the number of list masks in the extract file in between the (n)th and (n+1)th lead masks.

When it reaches the last lead section, the system counts the remaining list section masks after the last lead mask and inserts the appropriate number of list sections. Lastly, it inserts the following section, if specified.

Example

This example shows how to generate list sections subordinate to lead sections. In this example Record1 is the lead mask, and Record2 is the list mask.

LeadImage is the lead section and ListImage is the list section. The rule would count three Record2s between the two Record1s. If Record1 is actually the fifth Record1 in the extract file for the current transaction, the system would find the fifth LeadImage in the form set and insert three ListImages after this LeadImage.

Also, there is only one recipient, Recip1.

.

.

.

000000001RECORD1 data1

000000001RECORD2 data2

000000001RECORD2 data3

000000001RECORD3 data4

000000001RECORD4 data5

000000001RECORD4 data6

000000001RECORD2 data7

000000001RECORD1 data8

. . . .

. . . .

. . . .

The example below shows the line in the overflow file. In the first example, the corresponding line in the overflow file for the previous example would appear as shown here:

;LEADIMAGE;10,RECORD1;LISTIMAGE|DS<RECIP1(1)>;10,RECORD2;;

The next example shows how to add a following section. If a following section was needed, the line from the file would look as shown here. Assume the following section is named FOLLOWIMAGE:

;LEADIMAGE;10,RECORD1;LISTIMAGE|DS<RECIP1(1)>;10,RECORD2;FOLLOWIMAGE|DS<RECIP1(1)>;

This following example shows how to add another recipient. If a second recipient (with copy count of 3) was specified for the list section but not for the following section, the line would appear as shown here. Assume the second recipient is Recip2:

;LEADIMAGE;10,RECORD1;LISTIMAGE|DS<RECIP1(1),RECIP2(3)>;10,RECORD2;FOLLOWIMAGE|DS<RECIP1(1)>;

This example shows how to change the section attributes. So far the section attributes were set as DS—data entry and print and same page. If the list section was dynamic, you must add the W (can grow) attribute. The line would now look as shown here:

;LEADIMAGE;10,RECORD1;LISTIMAGE|DSW<RECIP1(1),RECIP(2)>;10,RECORD2;FOLLOWIMAGE|DS<RECIP1(1)>;

The example also shows nested/recursive functionality by iteration because this rule builds upon previous lines. This lets you have unlimited amounts of overflow within overflow.

Here are some points to consider concerning insertion logic:

• Reverse insertion logic when inserting different list sections after the same lead section.

Because of the nature of insertions, if two lines in the overflow file use the same lead section, the list section in the second line is inserted before the list section on the first line. This requires a sort of reverse logic when creating the overflow.

• In order insertion below the lead section.

Consider two different sections triggered by two different masks that occur in the extract file and the overflow file in the following manner:

(extract file)

000000001LEADREC

000000001LISTREC1

000000001LISTREC2

000000001LISTREC1

(overflow file: note reverse insertion logic)

;LEADIMAGE;10,LEADREC;LISTIMAGE2|DSW<RECIP(1);;

;LEADIMAGE;10,LEADREC;LISTIMAGE1|DSW<RECIP(1);;

The sections would be inserted after LEADIMAGE in the following order:

LISTIMAGE2…LISTIMAGE1…LISTIMAGE1

However the POLFILE.DAT file would look as follows:

…/LEADIMAGE|DSW<RECIP>/LISTIMAGE1|DSW<RECIP>/LISTIMAGE1|DSW

<RECIP>/LISTIMAGE2|DSW<RECIP>/...

This excerpt demonstrates that the sections are not inserted in the order of list search masks in the extract file but in the reverse order of the occurrence of list sections in the overflow file.

See also

• RunSetRcpTbl

© Copyright 2014, Oracle and/or its affiliates. All rights reserved. Legal notices.

Open table of contents

Open table of contents