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 ID | QNETSPLF ( *ANY) |
ADDRESS | TARGET SYSTEM NAME |
USER DESCRIPTION | PRT 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 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 DESCRIPTION | PRT PASSTHRU- SOURCE LOCAL ENTRY |
USER PROFILE | QNETSPLF (must be QNETSPLF) |
SYSTEM NAME | *LCL |
4. Create a remote output queue.
CRTOUTQ
OUTPUT QUEUE | Name of this OUTQUEUE |
LIBRARY | Associated 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 autostart | 1-10 (*NONE) |
Queue for writers messages | Message queue for writer messages |
Library | *LIBL (Library name) |
Connection Type *SNA | Sent using SNADS |
*IP | Sent using TCP/IP (Requires TCP/IP to be configured on source and target system) |
Destination Type *OS400 | V3R1M0 or higher |
*OS400V2 | V3R0M5 or V2R3M0 and valid only if CNNTYPE *SNA |
*S390 | S/390 (ES9000) Mainframe, valid only if CNNTYPE *SNA |
*PSF2 | Sent to a PC running PSF/2, valid only if CNNTYPE *IP |
*OTHER | AS400 V1, S36, S38, RS6000 |
VM/MVS class | VM/MVS Sysout Class, valid only if CNNTYPE *SNA and DESTTYPE *S390 |
Forms Control Buffer | VM/MVS FCB, valid only if CNNTYPE *SNA and DESTTYPE *S390 |
Transform | Host Print Transform, valid only if CNNTYPE *IP |
MFRTYPMDL | Valid only if TRANSFORM *YES |
WSCST | Attributes table to customize and ASCII printer |
INTNETADR | Internet address, valid only with CNNTYPE *IP and RMTSYS *INTNETADR |
Text | Description 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 ID | QNETSPLF ( *ANY) |
ADDRESS | TARGET SYSTEM NAME |
USER DESCRIPTION | PRT 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) |
ADDRESS | LOCAL SYSTEM NAME |
USER DESCRIPTION | PRT PASSTHRU- SOURCE LOCAL ENTRY |
USER PROFILE | QNETSPLF (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
Historical Number
11855333
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1019700