You can use file equations when you initiate with the following Report types using RIP:
Non-ROC Reports
ROC Direct Reports, provided file equation is not inhibited in the Report logic (by setting the built-in segment attribute Glb.FileInfo to N, which indicates that all your file values are to be set internally by logic).
Notes:
File equations for Print files should not be used with ROC Standard Reports. All file values must be set internally in your Report logic.
For ROC Direct Reports and non-ROC Reports, Glb.FileInfo defaults to Y if the Report is initiated by RIP.
Naming Conventions for Print and Extract Files
Before using File equations in RIP, you should be familiar with the naming conventions of Print Files and Extract Files in Agile Business Suite.
Print Files:
Print Files or Outstreams are attributes inherited from Glb.OutputStream.
In Enterprise Application, the outputstreams were created with their one character names in the range A to Z. When migrating an Enterprise Application model to Agile Business Suite, the outputstreams are automatically created with their one character names in the range of A to Z.
However, in Agile Business Suite, Print files (output stream attributes) can be named with one, two or more than two characters names. While naming the attributes, it is recommended to use a unique first one or two character mnemonic in the range A to ZZ followed by a logical name. For example, AAFinancials, ABTreasury. Builder uses the first two characters of the outputstream names if they are longer than two characters to form the Internal print file name. For example, PrintAA, PrintAB are the corresponding internal file names.
The first two character combination should be unique otherwise it refers to the same internal print file. For example, AAFinancials and AATreasury are two different outputstreams that refer to the same internal print file in a report, PrintAA.
Extract Files:
Extract files are attributes inherited from Glb.File. Extract files also have the same naming convention as Print files except for the following two differences:
The range is from A to ZZZZ (four characters). For example, A, AA, ABCD are the internal extract file names.
By default, the Alias name for the extract files is the same as the name of the Extract file. However, if you have entered your user-defined Alias name which is more than four characters long, only the first four characters are considered by the Builder, other characters are truncated.
File Equations
Use the letters A through ZZ for Extract files. Print files might be equated using internal name PRINT and PRINTA to PRINTZZ, as though RIP were the Report program being initiated.
Note: File equates must not exceed 1990 bytes. MCP imposes this limit with regard to limits of the COMS buffer. If file equates exceeding 1990 bytes are passed to RIP, it will P-DS with a message stating it cannot accept the file equate.
The file attributes recognized by RIP are shown in the following table.
Type of file | Attributes Recognized by RIP |
---|---|
Extract | All attributes |
GLI-INPUT | HOSTNAME, TITLE |
GLI-OUTPUT | HOSTNAME, TITLE |
OFFLINE-INPUT | BLOCKSIZE, KIND, MAXRECSIZE |
TITLE, UNITNO, UNITS | |
| All attributes |
REPORT | TITLE |
Notes:
Set BANNER to TRUE, and in the NOTE attribute, enter the text that you want to be displayed.
The only valid attributes for PRINTDISPOSITION when running your Reports in batch mode are CLOSE and EOJ.
The PRINTDISPOSITION for RP Reports cannot be changed.
If you want an Extract file to be retained with a specific name when a Report is initiated through RIP, then you must define the required name by using the TITLE attribute.
When using the USERBACKUPNAME attribute for a print file, use the FILENAME and FAMILYNAME attributes to specify the print file's name. Do not use the TITLE attribute for this purpose. AB Suite supports multiple extract files and print files in a report, making it impractical to verify each combination within RIP. However, RIP uses an MCP routine called DECODEATTLIST to manage the file equations. However, the consequence of using this routine is that the TITLE attribute is not separated into its FILENAME and FAMILYNAME components. This is an issue for the USERBACKUPNAME attribute, because it requires the FILENAME and FAMILYNAME settings. It is recommended that the FILENAME and FAMILYNAME attributes be used when utilizing the USERBACKUPNAME attribute. It is also permissible to include a usercode in the FILENAME.
Refer to the MCP file attribute documentation for more information on file attributes.
Examples
The following example shows file equations for different PRINT files:
FILE PRINT (FORMID = "INVOICES", PRINTCOPIES = 2) FILE PRINTAA (FORMID = "SALES", PRINTCOPIES = 5) FILE PRINTYZ (FORMID = "ACCOUNTS", PRINTCOPIES = 5)
The following example show file equations for different Extract files:
FILE A (TITLE = EXT/FILE/A, KIND = TAPE) FILE ABCD (TITLE = EXT/FILE/B, KIND = TAPE)
The following example shows the command for running a Report named THISDB/ SUMMARY under RIP, with file equations for the Report name and a default Print file.
Using FILE PRINT (TITLE = SALESANAL):
RUN $NGEN28/RIP ("LP"); FILE REPORT (TITLE=THISDB/SUMMARY);
FILE PRINT (TITLE=SALESANAL ON MYPACK, FORMID="DOUBLE")
The following example shows the command for running a Report named THISDB/ SUMMARY under RIP, with the report name as a parameter to RIP and file equations to the shadow reports PRINTA, PRINTB, PRINTC and PRINTD which use the USERBACKUPNAME attribute. There is no file equate for the default Print file.
RUN *NGENxx/RIP ("THISDB/SUMMARY LP"); %No file equate for PRINT FILE PRINTA(USERBACKUPNAME=TRUE); FILE PRINTB(USERBACKUPNAME=TRUE, FILENAME=PRINTFILES/SALESANAL/B); FILE PRINTC(USERBACKUPNAME=TRUE, FILENAME=PRINTFILES/SALESANAL/C, FAMILYNAME=MYPACK); FILE PRINTD(USERBACKUPNAME=TRUE, FILENAME=(MYUSER)PRINTFILES/SALESANAL/D, FAMILYNAME=MYPACK);
The following table shows the names assigned to the Print files in the above example.
Print file | Title | Pack |
---|---|---|
bdd/mix/file number\PRINT | backup-pack | |
PRINTA | PRINTA | backup-pack |
PRINTB | PRINTFILES/SALESANAL/B | backup-pack |
PRINTC | PRINTFILES/SALESANAL/C | MYPACK |
PRINTD | (MYUSER)PRINTFILES/SALESANAL/D | MYPACK |
Notes:
bdd – This is the backup disk designate value entered with the: BDD Administration command (default NGENGD).
mix – This is the mix number that the report was running under. It is represented as a 7-digit number in the file
file-number – This is a 12-digit number indicating the file number if multiple files were created from the same Print file.
backup-pack – This is the pack specified for BACKUP in Disk Location.