Storing Output in the Database
Executive Summary
- To store Banner output files (reports, log files, data files, etc.) into
the Banner database itself, enter Banner keyword
databasein the Printer block on Process Submission Control Form GJAPCTL. - Use Saved Output Review Form GJIREVO to view output files that are stored in the database, entering the Process name, one-up Number, and File Name in the appropriate blocks, or double-click in an empty block to select from a list.
- To download a selected output file to a PC, click Save to File in the Options menu.
- Refer to the following for more information:
- Reference Section below
- Examples below
- Banner2000 General Release 3.0 Release Guide (on the network or hardcopy)
- Banner2000 General Release 3.0 User Manual (on the network or hardcopy)
- Banner2000 General Release 4.0 User Manual (on the network or hardcopy)
Reference Section
Please note that the Banner capability to store process output in the database has been enhanced at UNCG. These enhancements are subject to change based on suggestions made by UNCG administrative offices and by CIS technical staff.
In Banner Forms RunTime, Process Submission Control Form GJAPCTL and Saved Output Review Form GJIREVO are in the Job Submission, General System, and Products menus.
When using any storage option (database, noprint, etc. in the Printer block on GJAPCTL):
- If errors are detected when a job runs, an error message (.ERM) file is created containing solely the text of the error message. The presence of such a file in a list of output files pertaining to a job (whether at the dollar sign prompt or in a Banner Forms pop-up box) serves as a tip-off that something went wrong when the job ran. The .LOG file may then be viewed for more information.
- A .RCI file is created which contains only the Report Control Information page from the .LIS (report) file. This facilitates quick perusal of report summary information.
- A long .DAT file name is retained, so that the operating system DIRECTORY/DATE command alone will reveal the user name and database associated with the job. This .DAT file is never stored in the database.
- On Banner_Uservol, output file names are automatically shortened by removing the user name and database name from the file names.
When storing output in the database (database in the Printer block on GJAPCTL):
- Notifications of process (job) errors are sent via email (to vms-username@uncg.edu), with the log file (.LOG file) as the body of the email message, as long as the log file is not unusually large.
- Notifications of successful job completion are sent via email (to vms-username@uncg.edu) with the report control information page (.RCI file) as the body of the email message.
- It is not necessary to log onto a VMS account in order to receive notifications regarding errors and job completion or to view or print output files.
- Ouput files are reduntantly stored on Banner_Uservol; thus, ouput files may be managed interactively under a VMS account or from Saved Ouput Review Form GJIREVO.
- Output file names are automatically shortened (by removing the user name and database from the file names) to better fit the initial size of the pop-up windows on the output review form and are likewise shortened on Banner_Uservol to maintain consistency in file naming.
- Maximum allowable size of an output file to be stored in the database is one megabyte. If a file is too big to be stored in the database, a short explanatory text (.TXT) file is created and stored to the database instead. (See example RZRQA99 below.)
- Each job's .BQI (batch queue information) file is an informational file showing the status of the batch job at the time it is submitted from the Banner job submission form. This file is available on the output review form immediately following job submittal. An imminent UNCG modification involves deleting this .BQI file from the database and from Banner_Uservol upon job completion.
- In the Options menu on Saved Output Review Form GJIREVO:
- If Save to File is clicked, the selected file is saved (downloaded) to C:\Windows\Temp on your PC, where it may be printed, renamed, copied, etc.
- If Delete Output is clicked, the selected file is deleted from the database but not from Banner_Uservol or from your PC.
Examples
Below, files marked with an asterisk (*) were stored in the database and are thus available on Saved Output Review Form GJIREVO.
The following is the output from Banner report process SARADMS when the job is run with database entered in the Printer block on Process Submission Control Form GJAPCTL:
* 194295_SARADMS.BQI;1
* 194295_SARADMS.LIS;1
* 194295_SARADMS.LOG;1
* 194295_SARADMS.RCI;1
194295_SARADMS_DBANDREW_UGDEV1.DAT;1
In C:\Windows\Temp, the following are the files (exactly as they appear therein) after pulling up each .LIS, .LOG and .RCI file above into Banner Output Review Form GJIREVO and clicking Save to File in the Options menu:
SARADMS.lis
SARADMS.log
SARADMS.rci
The following is the output from Banner report process SARADMS when the job is run with noprint entered in the Printer block on Process Submission Control Form GJAPCTL:
194296_SARADMS.LIS;1
194296_SARADMS.LOG;1
194296_SARADMS.RCI;1
194296_SARADMS_DBANDREW_UGDEV1.DAT;1
The remaining examples pertain to a few unique UNCG processes which produce multiple output files of a single type, such as several .LIS files instead of just one.
The output files listed in the following paragraph were produced by UNCG financial aid program RZRQA99 when database is entered in the Printer block on Process Submission Control form GJAPCTL. Program RZRQA99 produces multiple output files. Note the following:
- The program was written to produce no 194293_RZRQA99.LIS file; thus, no .RCI file is produced.
- The .LIS files were automatically renamed to have the ".L--" extension. These can range from L01 through L99.
- The order and case of all items below are unedited.
- The .TXT file (available on the output review form) is a text file containing an explanation that the .RPT file was too big to store in the database.
The process output (as described in the paragraph above) on Banner_Uservol:
* 194293_RZRQA99.BQI;1
* 194293_RZRQA99.LOG;1
* 194293_RZRQA99_1.TXT;1
* 194293_RZRQA99_AM2.L01;1
194293_RZRQA99_AM4.RPT;1
* 194293_RZRQA99_CON.L02;1
194293_RZRQA99_DBANDREW_UGDEV1.DAT;1
* 194293_RZRQA99_SEL.L03;1
The process output (same job as above) as stored in the database and as listed on Saved Output Review Form GJIREVO:
194293_rzrqa99.bqi
194293_rzrqa99_am2.l01
194293_rzrqa99_1.txt
194293_rzrqa99_con.l02
194293_rzrqa99_sel.l03
194293_rzrqa99.log
In C:\Windows\Temp after pulling up each of the above files in Saved Output Review Form GJIREVO and clicking Save to File (in the Options menu) for each one:
RZRQA99.bqi
RZRQA99.l01
RZRQA99.l02
RZRQA99.l03
RZRQA99.log
RZRQA99.txt
The L01 through L99 extensions for extra .LIS files look a bit odd in the output review form and on a PC ("l01" looks like "101", etc.), so this UNCG naming convention may be changed at some point.
When job above is run with noprint in the Printer block on Process Submission Control Form GJAPCTL, the files look like this on Banner_Uservol:
228534_RZRQA99.LOG;1
228534_RZRQA99_AM2.L01;1
228534_RZRQA99_AM4.RPT;1
228534_RZRQA99_CON.L02;1
228534_RZRQA99_DBANDREW_UGDEV1.DAT;1
228534_RZRQA99_LAB.RPT;1
228534_RZRQA99_SEL.L03;1