Reprint automatically archives spooled files as they arrive in your output queues and allows each user to view and/or reprint their own reports by selecting them from a list.
Latest Release: 1.00
Last Update: New Product
Source Code: Available
There are many reasons to use Reprint to complement your existing spooled file archival procedures. Unlike long-term, off-line spooled file archival solutions, Reprint requires no
system operator assistance or intervention for the archival and restoration of spooled files. Once set-up is complete, Reprint automatically archives spooled
files as they arrive in your output queues. User's are able to view and/or reprint their own reports at any time by executing a single command and selecting the desired report from a list.
Many AS/400 (iSeries) installations address the short-term spooled file archival issue by leaving spooled files in output queues in a held or saved status. This is a bad idea for two reasons.
First, in the event of a disk failure (and sometimes OS/400 upgrades), those spooled files are lost. Second, by leaving a spooled file in an output queue, you are keeping an old and
otherwise dead job alive. This unnecessarily eats up system resources. Reprint provides the same benefits as leaving a spooled file in an output queue without the costs associated with
keeping the old job alive. Reprint frees up system resources for jobs that are truly active. By including the Reprint library in your normal backup, you can also eliminate the risk of losing
those spooled files to a disk failure or OS/400 upgrade.
Reprint works by attaching a special data queue to each output queue that you wish to have
monitored. The output queues to be monitored are identified during the setup process and can be modified at any time. When a spooled file arrives in a monitored output queue, OS/400
sends an entry to the special data queue. Reprint uses the information in the data queue entry to determine whether or not the spooled file meets your criteria for archival. The spooled file
criteria for archival is also specified during the setup process and can be modified at any time. If criteria is met, the spooled file is immediately archived and processed as usual. Otherwise, Reprint
ignores the spooled file and it is processed as usual.
Even if you already have a data queue attached to your output queues, Reprint will work for you. This is because Reprint
is adaptable and will recognize existing output queue / data queue relationships. If an output queue / data queue relationship exists at the time Reprint is started, Reprint
will attach its own data queue to the output queue and echo all data queue entries to the original data queue. When Reprint is ended, the original data queue is re-attached to the
output queue so that normal processing may continue.
Users can view and/or reprint their reports by executing the REPRINT command. This
command can be placed in a CL program or on a user's menu if command line access is not available. When the REPRINT command is executed, the user is presented with a list
containing only their spooled files that have been archived by Reprint. Any spooled file can be selected from the list for immediate viewing or reprinting.
is flexible. The list of output queues to be monitored by Reprint can be modified at any time by adding new output queues or removing existing output queues. Once an output
queue is identified to be monitored, you control which spooled files are archived from the output queue by entering spooled file criteria. The spooled file criteria that can be specified
include spooled file name, job name, user name, printer file name, user data, and forms type. Each of these criteria can be entered as a specific value, a generic value, or as the special value,
*ALL. For each set of criteria, you can also indicate a unique number of days to retain the archives for spooled files that met the criteria.
is self-maintaining. Self maintenance is accomplished via the use of an auto-purge feature. The auto-purge feature will automatically delete spooled file archives once their
retention days have been exceeded. The auto-purge feature also deletes aged archive deletion and reprint history. While the auto-purge feature of Reprint can be turned off, we strongly
recommend leaving it on. This feature makes Reprint truly maintenance-free and helps minimize the amount of disk space used by Reprint.
is also self-contained. Other than four commands optionally copied to the QGPL library during installation, Reprint is totally isolated in its own library. This includes all
programs, files, commands, and spooled file archives.
Reprint's extensive reporting capabilities keep you well informed of all Reprint activity. All reports can be requested via the
Reprint Reports Menu or via special commands provided with Reprint. Reprint commands can even be included in a job scheduler for automated
reporting. Reports available include the following:
- Disk Usage Analysis Report
- Directory Analysis Report
- Deletion History Analysis Report
- Reprint History Analysis Report – By Archived Spooled File
- Reprint History Analysis Report – By Reprinting User
- Configuration Analysis Report
- Exception Report