KB: 7995114

Page 1 of 2

Home Select a country

| Products & services | Support & downloads | My account

iSeries and AS/400 Technical Support Technical Databases

APARs Preventive Service

Planning - PSP

Document Survey

PTF Cover Letters Software Knowledge

Base

IBM Software Technical Document

__________________________________________________________________ Document Information __________________________________________________________________ Document Title Creating a Dummy Device Description to Use with a Remote Output Queue (RMTOUTQ)

Registered Software
Knowledge Base

Related links: Register Web Assistance/ Feedback

Document Description Note: This document was previously entitled, Using TCP/IP Remote Print Writers with Applications Requiring a Device Description.

This document contains instructions for creating a dummy device description to use with a remote outp queue (RMTOUTQ). Dummy device descriptions are typically used when printing from applications tha not support printing directly to an output queue but only to a printer (including Query/400 and the Syste Environment). They are also useful when moving spooled files from one printer to another from the Wo with Output Queue (WRKOUTQ) or Work with Spooled Files (WRKSPLF) commands or when using Operations Navigator to drag and drop spooled files from one printer to another.

Caution: If dummy device descriptions are used with RMTOUTQs and a system save is performed a later a system restore is performed, the dummy device description will be restored as a *VRT 3812 pr device description with a normal output, but the RMTOUTQ will not be restored. This occurs because output queue will already exist as a normal output queue at the time that the RMTOUTQs would norm be restored. When using RMTOUTQs with dummy device descriptions, it is recommended that the RMTOUTQs be fully documented so they can be re-created correctly after performing a system resto

Creating a Dummy Device Description to Use with a Remote Output Queue Use the following steps to create a dummy device description: 1

Before a dummy device description can be created, the remote output queue (RMTOUTQ) must r in the QUSRSYS library. If not, creating the dummy device description will cause you to have two queues of the same name -- one in the current library for the RMTOUTQ and one in QUSRSYS. U following Work with Objects (WRKOBJ) command to verify that the RMTOUTQ is in library QUSR

WRKOBJ OBJ(*ALL/output-queue) OBJTYPE(*OUTQ) To move the RMTOUTQ to library QUSRSYS, first use the End Writer (ENDWTR) command with When to end writer (OPTION) parameter set to *IMMED to end the writer immediately: ENDWTR WTR(output-queue) OPTION(*IMMED) Then issue the following Move Object (MOVOBJ) command:

MOVOBJ OBJ(outq-library/output-queue) OBJTYPE(*OUTQ) TOLIB(QUSRSYS) Use the following Create Device Desc (Printer) (CRTDEVPRT) command to create a device desc with the same name as the RMTOUTQ:

CRTDEVPRT DEVD(output-queue-name) DEVCLS(*VRT) TYPE(3812) MODEL(1) + ONLINE(*NO) FONT(011) Creating the dummy device description should result in MSGCPI2611, Output queue HP5SILPR QUSRSYS already exists. This indicates that the printer device description is associated with the Remote Output Queue (RMTOUTQ) that has already been created.

http://www-912.ibm.com/s_dir/slkbase.NSF/f99348d94b68f8708625661300765a6c/7... 03-04-2003

KB: 7995114

Page 2 of 2

If this message is not received, it most likely means that the RMTOUTQ was not in library QUSRS and the Create Device Desc (Printer) (CRTDEVPRT) command has created a second output que not a RMTOUTQ) with the same name in library QUSRSYS. The problem with this is that applicat typically send spooled files to the output queue in library QUSRSYS; however, because this is not RMTOUTQ, the spooled files are not sent to the printer. If working in the System/36 Environment, use the Display System/36 Configuration (DSPS36 to check the System/36 printer IDs. The Change System/36 Configuration (CHGS36 used to change the System/36 printer IDs or to assign a new System/36 printer ID to point to the n dummy device description.

Note: When a printer is specified in the //PRINTER OCL statement, you are using the System/36 ID for that printer. The System/36 Environment then uses a print file in library #LIBRARY that has same name as the printer ID. If the output is not going to the correct printer, specify the output que name on the //PRINTER OCL status or use the Change Printer File (CHGPRTF) command to poin printer file directly to the remote output queue: CHGPRTF FILE(#LIBRARY/system-36-printer-id) OUTQ(outq-library/output-queue)

Notes: 1 Do not use the Vary Configuration (VRYCFG) or the Work with Configuration Status ( commands to vary on the printer device description. 2 Do not use the Start Print Writer (STRPRTWTR) command or Option 1 (Start) from the Work with W (WRKWTR) command to start the writer. Use the Start Remote Writer (STRRMTWTR to start a writer using the Remote Output Queue (RMTOUTQ). 3 Remote Output Queues (RMTOUTQs) use remote writers, not printer writers. However, the command defaults to WTR(*PRT) which will only show all of the active and inactive printer writers. Therefore, using the WRKWTR command without any parameters will show the writer to be in END status, even when the remote writer is started. 4 To determine if the remote writer is started, use the Work with Writers (WRKWTR) command with t Writer (WTR) parameter set to *ALL. For example. the WRKWTR WTR(*ALL) command shows all writers rather than showing only all active and inactive printer writers.

__________________________________________________________________ PMR Number: Related APARs: Related Public Documents:

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implie warranties of merchantability and fitness for a particular purpose. By furnishing this document, grants no licenses to any related patents or copyrights. Copyright (c) 1996,1997,1998, 1999, 20 2001, 2002, 2003 IBM Corporation. Any trademarks and product or brand names referenced in document are the property of their respective owners. Consult the Legal link, and select the Copyright and trademark information link from the left navigation bar for trademark informat
About IBM

| Privacy | Legal | Contact

http://www-912.ibm.com/s_dir/slkbase.NSF/f99348d94b68f8708625661300765a6c/7... 03-04-2003