IBM Support

Printer Passthrough or Remote Output Queues

Troubleshooting


Problem

This document contains basic configurations examples for Remote Output Queues.

Resolving The Problem

Printer passthrough or Remote Output Queues use the SNADS application to move the spool files from one system to the other. This document assumes that you have a working APPC/APPN and SNADS configuration between the two IBM System i systems.

For additional information, refer to document N1018347, Configure SNADS and Setting Up SNA Distribution Services. To link to document N1018347 immediately, click herehttp://www-01.ibm.com/support/docview.wss?uid=nas8N1018347

Step 1:

Verify that you have a APPC/APPN and SNADS configuration between both operating systems and the connection is working in both directions.

Step 2:

Start at the source system where the output is generated.

1. Add a directory entry for QNETSPLF/ remote system (or verify that you have a *ANY /remote system).

ADDDIRE

USER IDQNETSPLF ( *ANY)
ADDRESSTARGET SYSTEM NAME
USER DESCRIPTIONPRT PASSTHRU- SOURCE REMOTE ENTRY
USER PROFILE**DO NOT FILL IN**
SYSTEM NAMETARGET SYSTEM NAME- (type over the *LOC that may be here)

2. Verify that a user profile exists for QNETSPLF. If it does not exist, create one. Typically, the default entries for a user profile will work.

3. Add a directory entry for QNETSPLF/local system user.

ADDDIRE
USERID QNETSPLF (must be QNETSPLF)
ADDRESS LOCAL SYSTEM NAME
USER DESCRIPTIONPRT PASSTHRU- SOURCE LOCAL ENTRY
USER PROFILE QNETSPLF (must be QNETSPLF)
SYSTEM NAME*LCL

4. Create a remote output queue.

CRTOUTQ
OUTPUT QUEUEName of this OUTQUEUE
LIBRARYAssociated Library
REMOTE SYSTEM* PASTHR- (Use source system for passthrough user, if output was created during a passthrough session.)

*INTNETADR (Only if *IP is specified for CNNTYPE.)

*RMTSYSNAME (Name of the target system.)
REMOTE PRINTER QUEUE*USER (Output queue specified on user profile that created the spool file on the source system)

*SYSTEM (Default System Printer on the target system.)

PRTQNAME (Name of the print queue on the target system.)
Writers to autostart1-10 (*NONE)
Queue for writers messagesMessage queue for writer messages
Library*LIBL (Library name)
Connection Type *SNASent using SNADS
*IPSent using TCP/IP (Requires TCP/IP to be configured on source and target system)
Destination Type *OS400V3R1M0 or higher
*OS400V2V3R0M5 or V2R3M0 and valid only if CNNTYPE *SNA
*S390S/390 (ES9000) Mainframe, valid only if CNNTYPE *SNA
*PSF2Sent to a PC running PSF/2, valid only if CNNTYPE *IP
*OTHERAS400 V1, S36, S38, RS6000
VM/MVS classVM/MVS Sysout Class, valid only if CNNTYPE *SNA and DESTTYPE *S390
Forms Control BufferVM/MVS FCB, valid only if CNNTYPE *SNA and DESTTYPE *S390
TransformHost Print Transform, valid only if CNNTYPE *IP
MFRTYPMDLValid only if TRANSFORM *YES
WSCSTAttributes table to customize and ASCII printer
INTNETADRInternet address, valid only with CNNTYPE *IP and RMTSYS *INTNETADR
TextDescription for output queue

Target System Where the Output Is Printed

1. Add a directory entry for QNETSPLF/ remote system (or verify that you have a *ANY /remote system).

ADDDIRE
USER IDQNETSPLF ( *ANY)
ADDRESSTARGET SYSTEM NAME
USER DESCRIPTIONPRT PASSTHRU- SOURCE REMOTE ENTRY
USER PROFILE **DO NOT FILL IN**
SYSTEM NAME TARGET SYSTEM NAME- (type over the *LOC that may be here).

2. Verify that a USER PROFILE exists for QNETSPLF. If not, create one. Typically, the default entries for a user profile will work.

3. Add a directory entry for QNETSPLF/local system user.

ADDDIRE
USERID QNETSPLF (must be QNETSPLF)
ADDRESSLOCAL SYSTEM NAME
USER DESCRIPTIONPRT PASSTHRU- SOURCE LOCAL ENTRY
USER PROFILEQNETSPLF (must be QNETSPLF)
SYSTEM NAME*LCL

4. Verify that you have a destination output queue on the target system.

5. QMSF (ENDMSF) must be ended. Then, start QMSF (STRMSF) again on the source and target systems before the remote output queues work correctly.

Source System Where the Output Is Generated

1. Start the remote writer: STRRMTWTR

The system should now be automatically sending the output from the source spooled files, to SNADS, to the target system.

If errors are encountered, refer to Rochester Support Center knowledgebase document New, SNADS - Basic Troubleshooting Process. To link to New immediately, click herehttp://www-01.ibm.com/support/docview.wss?uid=nas8N1019679

[{"Product":{"code":"SWG60","label":"IBM i"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":"Communications-SNA","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"7.1.0;6.1.1;6.1.0;5.4.5;5.4.0","Edition":"","Line of Business":{"code":"LOB08","label":"Cognitive Systems"}},{"Product":{"code":"SSC52E","label":"IBM i 7.1"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":" ","Platform":[{"code":"","label":null}],"Version":"","Edition":"","Line of Business":{"code":"","label":""}},{"Product":{"code":"SSC3X7","label":"IBM i 6.1"},"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Component":" ","Platform":[{"code":"","label":null}],"Version":"","Edition":"","Line of Business":{"code":"","label":""}}]

Historical Number

11855333

Document Information

Modified date:
18 December 2019

UID

nas8N1019700