Report Organizer Full Story
The Report Organizer enables spooling and archiving of your Open/36 reports to the PC environment. You can integrate the Report Organizer with Open/36 by configuring Open/36 printed IDs of type A (Archive), reports printed to those printer IDs, will automatically be transferred in the Report Repository (local or central) associated with the PC that generated the report. This report can then be viewed within the Report Organizer, categorized and/or printed via the Windows Spooler.
The Report Organizer eliminates the need of defining several printer IDs, it greatly reduces the complexity of printer administration by using pre-defined windows printer queues on the Windows environment. It eliminates the need for redundant definitions on both the Unix and Windows environments.
Open/36 provides new procedures that can be used in your application to interface with the Report Organizer. You can use QSPOOLRO to automatically archived applications' reports, you can optionally pre-categorize those reports, replace existing reports with more recent information, etc... The Report Organizer also integrates with the Thin Client in GUI mode by providing your applications with direct lookup capabilities through the Report Organizer. You can archive codes and descriptions in report form under the Report Organizer and add lookup buttons to your GUI screens to provide your users with increased usability without changing your application programs.
The Report Organizer spooler is based on the Windows spooler. By defining a printer ID of type A, for Archive, you can provide your users with full control on their reports, eliminate the need for Unix spooling and eliminate most of your several printer IDs. When using the spooling capability of the Report Organizer, one printer ID of type A, e.g. P1 could point to different physical printer, depending on the definition of individual users using such Printer IDs.
For example, in the Report Organizer of user JOHN; on his PC; P1 could be mapped to an HP LaserJet4, for NANCY, P1 could be mapped to a Lexmark Optra printer. In both cases, users print to P1 in Open/36, but depending the user that generated the report, it will be directed to the windows print queue associated with P1, for the user that generated the report.
For user JOHN, it's Report
Organizer and printer assignment for P1, would look like shown below.
Under Spooler, a printer ID called P1 exists, it is associated with the
windows printer queue of HP LaserJet 4. Reports printed to P1, by John,
will print to that print queue.
For user NANCY, the same
Open/36 printer ID, P1, could be associated to a totally different printer
as shown below. Nancy's reports printed to P1 will print to the print
queue associated with the Lexmark printer.
In Open/36, the only definition required to allow the above, is a printer ID of type "A" for archive with no specific relation with the actual printer. All printer specific operations and parameters are done on the PCs.
The Report Organizer combined with new Open/36 procedures enables you to automatically archived applications' reports. You can decide if the report is to be archived, printed as usual or both. QSPOOLRO, provides the main interface to the Report Organizer. It allows pre-categorization of reports, it allows archiving to the users' Local Repositories or you can specify a different repository like a departmental repository that can be accessed by selected users in the department so reports are located in a more central manner. You have the entire flexibility on where reports are re-directed for archiving.
In the following example, a simple procedure generates a report to be printed to P7 which is a printer associated with a unix print queue. The report is generated by the APVLIST program and printed.
// LOAD APVLIST
If you wished to have this procedure also archive the report to a repository, you would simply need to add a call to QSPOOLRO as shown below :
// LOAD APVLIST
The Report Organizer can be used to enhanced your applications by adding lookup controls in your S&D specifications when converting your screen formats to GUI for use with the Thin Client. A single D specification provides the ability to enhance the usability of an application by allowing data lookup within a report under the Report Organizer. The D specification also defines the information that is returned to the application program's input field when an item is selected in the Report Organizer window.
As an example, a D specification could be defined so a button triggers a lookup to a report containing a Chart of Accounts report, enabling the user to pick from a list and returning the selected account to the application.
The report being the object of the lookup would be a standard report, available in the report repository of the user, or stored in a central repository so multiple users can have access to it.
The lookup button, coded in the S&D specification, would automatically use the Report Organizer and display the report on the screen so the user can select from the available values.
In the above example, when the user selects a value, the account selected will be transferred in the G.L. # input field and the lookup window will automatically closed. The above can be accomplished without changing the program, you only need to add a lookup button in the S&D specifications of the screen format.