Offline storage for "text-based" report images made easy.
Normally on the AS/400, all printer output is placed into files for later processing. Known as print spooling, this is a great feature which makes report management on the system quite easy. However, these spooled files cannot be directly saved to offline storage.
The two sister commands from QUSRTOOL library presented here can help you with this problem.
The Copy from Output Queue Command
The Copy from Output Queue (CPYFRMOUTQ) command allows the user to copy spooled files from a selected output queue and store those files in database file members. The database file can be saved offline and restored, and the spooled files made ready for printing again with the Copy to Output Queue (CPYTOOUTQ) command.
The CPYFRMOUTQ command supports spooled files with record lengths of 210 bytes or shorter. The command cannot be used to copy spooled files that contain graphics or advanced printer function output.
When you execute the command, CPYFRMOUTQ adds a member to the OUTFILE for each spooled file found. The members are named MBR001, MBR002, and so on. The member text provides identification for the spooled file, and includes the original spooled file name and the qualified job name that created the spooled file.
Because all spooled files for an output queue which are restored by the CPYTOOUTQ command are restored with the same attributes (CPI, LPI, etc.), you should avoid mixing spooled files with different attributes in the same output queue.
Required Parameters
OUTQ Specify the qualified name of the output queue to copy. All spooled files within the output queue, with the exception of open spooled files, are copied to the database file specified in OUTFILE. The possible library values are:
*LIBL: The library list is used to locate the output queue.
library-name: Specify the name of the library where the output queue is located.
output-queue-name: Specify the name of the output queue containing the spooled files to be copied.
OUTFILE Specify the qualified name of the database file to contain the copies of the spooled files from the output queue specified in OUTQ. The OUTFILE must not exist before executing this command. If the OUTFILE exists, an escape message is sent and the command does not execute. The possible library values are:
*CURLIB: The output file is created in the current library.
library-name: Specify the name of the library where the output file is to be created.
output-file-name: Specify the name of the output file to be created to contain copies of the spooled files.
Optional Parameters
DLTSPLF Specify whether or not the spooled files are to be deleted after they are copied to the database file specified in OUTFILE.
*NO: The spooled files are not to be deleted. They remain in the output queue specified in OUTQ after being copied to the database file specified in OUTFILE.
*YES: The spooled files are deleted from the output queue specified in OUTQ after being copied to the database file specified in OUTFILE.
Example
CPYFRMOUTQ OUTQ(MYLIB/MYOUTQ) + OUTFILE(MYLIB/MYFILE) DLTSPLF(*YES)
This command copies all spooled files (except those that are currently open) from output queue MYOUTQ located in library MYLIB to database file MYFILE in library MYLIB. The database file is created by this command. After the spooled files are copied to the database file, they are deleted from the output queue.
Source Members
INFO: CPYFRMOUTQ (QATTINFO) CDO: TAASPLM (QATTCMD) CPP: TAASPLMC (QATTCL)
Prerequisites
The following QUSRTOOL tools must exist on your system:
CVTOUTQ EDTVAR
The Copy to Output Queue Command
The Copy to Output Queue (CPYTOOUTQ) command is used to copy spooled files created with the CPYFRMOUTQ command from a database file to the specified output queue. This command prepares the saved spooled files for printing.
When spooled files are restored with this command, the user must be aware of the spooled file attributes that were in effect when the spooled files were originally created. Because the spooled files are saved as database file members, no information is kept about the attributes of the spooled file, such as CPI, LPI, and so forth. Upon restoration of the spooled files, a printer file is specified that is used to determine which attributes to use. The printer file attributes used in the restore should match the printer file attributes used when the spooled files were originally created.
Required Parameters
DBFILE Specify the qualified name of the database file containing the saved spooled file members. This file must have been created by the CPYFRMOUTQ command for this command to work properly. The possible library values are:
*LIBL: The library list is used to locate the database file.
library-name: Specify the name of the library where the output file is located.
file-name: Specify the name of the database file that contains the saved spooled files.
OUTQ Specify the qualified name of the output queue that is to contain the restored spooled files. The possible library values are:
*LIBL: The library list is used to locate the output queue. library-name: Specify the name of the library where the output queue is located.
output-queue-name: Specify the name of the output queue.
Optional Parameters
PRTFILE Specify the qualified name of the printer file to be used to restore the spooled files. The spooled file attributes of the printer file should match the attributes of the saved spooled files; otherwise, unpredictable printing results may occur. The possible library values are:
*LIBL: The library list is used to locate the printer file.
library-name: Specify the name of the library containing the printer file to be used.
The possible printer file values are:
QSYSPRT: The system-defined printer file QSYSPRT is used to restore the spooled files.
printer-file: Specify the name of a printer file to be used to restore the spooled files. An externally described printer file cannot be used.
MBR
Specify whether all members in DBFILE are to be restored, or if a specific member is to be restored.
*ALL: Restore all members contained in DBFILE to output queue OUTQ.
member-name: Specify the name of a member in DBFILE to be restored.
PRTWIDTH Specify the record width of the printer file used.
*PRTF: Use the record width of the printer file specified in the PRTF parameter. The record width of file QSYSPRT is 132.
print-record-width: Specify the printer file record width, up to 210 bytes wide. If a value is specified in this parameter, a printer file other than QSYSPRT may need to be specified in the FILE parameter.
Example
CPYTOOUTQ DBFILE(MYLIB/MYFILE) + OUTQ(MYLIB/MYOUTQ) PRTFILE(PRT15)
This command restores all members saved in file MYFILE located in library MYLIB to output queue MYOUTQ located in library MYLIB. The printer file PRT15 is used to print the spooled files.
Source Members
INFO: CPYFRMOUTQ (QATTINFO) CDO: TAASPLM2 (QATTCMD) CPP: TAASPLMC2 (QATTCL)
Prerequisites
The following QUSRTOOL tool must exist on your system:
EDTVAR
The foregoing article was adapted from Midrange Computing's QUSRTOOL Command Reference. The manual contains explanations and syntax diagrams for more than 250 useful, yet poorly documented tools.
The Copy from Output Queue (CPRFRMOUTQ) ->*LIBL/--------- | |--output-queue-name--------> CPYFRMOUTQ---OUTQ--| | --library-name/-- ->*CURLIB/------- | |--output-file-name---------> >---OUTFILE--------| | --library-name/-- Required __________________________________________________________________ Optional ->*NO----- | |--------------------|P|------------ >---DLTSPLF--------| | --*YES---- Job: B,I Pgm: B,I REXX: B, I Exec The Copy to Output Queue (CPRTOOUTQ) ->*LIBL/--------- | |--file-name--------------> CPYTOOUTQ----DBFILE--| | --library-name/-- ->*LIBL/------- | |--output-queue-name------> >---OUTQ-------------| | --library-name/-- Required __________________________________________________________________ Optional ->*LIBL/--------- ->QSYSPRT------- | |--| -----------> >--PRTFILE-----| | | | --library-name/-- --printer-file-- ->*ALL------- ->PRTF-------------- | |--PRTWIDTH--| |------|P|- >---MBR---| | | | -member-name- -print-record-width- Job: B,I Pgm: B,I REXX: B, I Exec
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online