It summarizes the differences between ROC and non-ROC Reports.
Built-in Attributes
The built-in attributes in the following table are implemented differently for ROC and non-ROC Reports. Refer to the Agile Business Suite Programming Reference Manual for more information.
Glb.ASCPrtHost | Glb.Backupx | Glb.Devicex |
Glb.FileInfo | Glb.FormDepthx | Glb.FormIDx |
Glb.LineCountx | Glb.LineUpx | Glb.LineUpNamex |
Glb.NumCopiesx | Glb.PageCountx | Glb.Pitchx |
Glb.PrintAtx | Glb.PrintBannerx | Glb.PrintHostx |
Glb.Priv | Glb.SaveDaysx | Glb.Shadow |
Glb.Stnx | Glb.Titlex | Glb.TPGroup |
Glb.Userx |
Logic Commands
The logic commands in the following table are implemented differently for ROC and non-ROC Reports. Refer to the Agile Business Suite Programming Reference Manual for more information.
Advance Channel | Advance NEWPAGE | BeginPage |
CriticalPoint | EndNoPrint | PRINT;IF.PRESENT |
| Release |
Report Options
The properties in the following table are implemented differently for ROC and non-ROC Reports. Refer to the Agile Business Suite Developer User Guide for more information.
Video capable | Print line length | Extract pack |
ROC uses database | Sort memory size |
Report Method Performance Statistics Capture
AB Suite MCP provides the ability to capture report performance statistics for all methods invoked by the report that are Class, Segment and External Class (Library). This might be beneficial when tuning reports for optimum runtime performance or identifying poor performing methods.
When this feature is enabled (see “To enable report invoked method runtime statistics”) there will, naturally, be a slight runtime performance penalty associated with the statistics capture. For this reason, we do not recommend running reports with the method statistics enabled in a production environment unless it is for isolated or specific cases where the same testing cannot be achieved in a test environment.
To enable report invoked method runtime statistics: Modify the existing Taskstring associated with the NGENxxSYS/BLD utility to include SETMETHODS.
Modify the existing Taskstring associated with the NGENxxSYS/BLD utility to include SETMETHODS.
Note: Your NGENxxSYS/BLD might or might not have an existing TASKSTRING specified, it will only be present in the Epsilon installed AB Suite 7.08.0 Runtime. For example, wfl modify (rtuser)ngenxxsys/bld on rtpack;taskstring =”T=5 SETMETHODS“ (in this example, the T=5 indicates that this is an Epsilon runtime)
All reports generated while the SETMETHODS is present in the BLD taskstring will have the invoked method capture enabled.
The Generate log will inform you if the report method statistics are enabled for the report deployment and a display to the same affect is shown during report execution.
Example
Report Deployment:
26/03/17 @ 23:32:06 Report Compiles Started (Server Id 420-8886) [1-J 8431]
26/03/17 @ 23:32:06 Warning: Method Statistics Enabled
26/03/17 @ 23:32:08 Total Units to Compile 3
26/03/17 @ 23:32:08 Report Units Compiled (DMA) 1(33% Complete)
Report Execution:
23:32:33 8447 MSRDISP14:DISPLAY:** Method Statistics Enabled in CUSTLIST **.
The report methods statistics are written to a CSV file called <system>/<report>/TIMINGS/<report mix #>
Example
23:32:33 8447 MSRDISP14:DISPLAY:Timing Summary:
SAMPLEBLOB/CUSTLIST/TIMINGS/08447.
The statistics provided are:
Method name
Call frequency
CPU secs
CPU per call
Pbits
Pbits per call
Array resizes
This includes statistics for all invoked class, segment and external class (Library) methods. External Class methods are identified by a method name suffix of ‘(L)’.
Note: The captured statistics are cumulative, that is, if MethodA invokes MethodB which then invokes MethodC then the statistics reported for MethodA will include the counts for MethodB which will include the counts for MethodC.