0% found this document useful (0 votes)

414 views325 pages

Remote Work Station Support

IBM welcomes your comments. A form for readers' comments may be provided at the back of this publication. This edition applies to the licensed program IBM Operating System / 400 (Program 5769-SS1), Version 4 Release 1 Modification 0. When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.

Uploaded by

zlotek

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

414 views325 pages

Remote Work Station Support

Uploaded by

zlotek

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

AS/400 Advanced Series IBM

Remote Work Station Support

Version 4

SC41-5402-00
AS/400 Advanced Series IBM
Remote Work Station Support
Version 4

SC41-5402-00
Note

Before using this information and the product it supports, be sure to read the general information under “Notices” on page xvii.

First Edition (August 1997)

This edition applies to the licensed program IBM Operating System/400 (Program 5769-SS1), Version 4 Release 1 Modification 0,
and to all subsequent releases and modifications until otherwise indicated in new editions.

Make sure that you are using the proper edition for the level of the product.

Order publications through your IBM representative or the IBM branch serving your locality. If you live in the United States, Puerto
Rico, or Guam, you can order publications through the IBM Software Manufacturing Solutions at 1-800-879-2755. Publications are
not stocked at the address given below.

IBM welcomes your comments. A form for readers' comments may be provided at the back of this publication. You can also mail
your comments to the following address:

IBM Corporation
Attention Department 542
IDCLERK
3605 Highway 52 N
Rochester, MN 55901-7829 USA

or you can fax your comments to:

United States and Canada: 1-800-937-3430

Other countries: 1-507-253-5192

If you have access to the Internet, you can send your comments electronically to [email protected]; IBMMAIL,
to IBMMAIL(USIB56RZ).

When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes
appropriate without incurring any obligation to you.

 Copyright International Business Machines Corporation 1997. All rights reserved.

Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to
restrictions set forth in GSA ADP Schedule Contract with IBM Corp.
Contents
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

About Remote Work Station Support (SC41-5402) . . . . . . . . . . . . . . . xix

Who Should Use This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
| Information Available on the World Wide Web . . . . . . . . . . . . . . . . . . . xx

Part 1. Display Station Pass-Through

Chapter 1. Pass-Through Instructions for the End User . . . . . . . . . . . 1-1

Display Station Pass-Through Environment . . . . . . . . . . . . . . . . . . . . . 1-1
Choosing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Using Display Station Pass-Through Commands . . . . . . . . . . . . . . . . . 1-2
Starting Pass-Through (STRPASTHR Command) . . . . . . . . . . . . . . . 1-3
Going Back and Forth between Systems . . . . . . . . . . . . . . . . . . . . 1-5
Ending Pass-Through (ENDPASTHR Command) . . . . . . . . . . . . . . . . 1-5
Signing Off (SIGNOFF Command) . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Chapter 3. Configure Display Station Pass-Through . . . . . . . . . . . . . 3-1

Chapter 4. Starting and Using a Display Station Pass-Through Session . 4-1

Choosing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
The Remote Location Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Remote Location Name Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
The Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
The Local Location Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
The Remote Network Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
The Connection Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Connection Device Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Specifying Remote Location Name and Connection Device Together . . . . 4-8
Specifying Virtual Controllers and Virtual Devices . . . . . . . . . . . . . . . 4-9
Requesting Automatic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Virtual Controller (VRTCTL) Parameter . . . . . . . . . . . . . . . . . . . . . 4-9
Virtual Display Device (VRTDEV) Parameter . . . . . . . . . . . . . . . . . 4-10

Chapter 5. Going Back and Forth between Systems . . . . . . . . . . . . . 5-1

 Copyright IBM Corp. 1997 iii

Using the Transfer Pass-Through (TFRPASTHR) Command . . . . . . . . . . 5-5
Using System Request Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
AS/400 System Request Options . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Using the System Request Program (SRQ10PGM) Parameter . . . . . . . 5-7
System/38 System Request Options 10 and 11 . . . . . . . . . . . . . . . . . 5-8

Chapter 6. Work Management Considerations for Display Station

Pass-Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Control of Remote Sessions from Other Systems . . . . . . . . . . . . . . . . . 6-1
The QRMTSIGN System Value . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Remote Sign-On Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
QRMTSIGN Program Specifications . . . . . . . . . . . . . . . . . . . . . . . 6-2
QRMTSIGN Programming Considerations . . . . . . . . . . . . . . . . . . . . 6-7
Creating a Subsystem for Display Station Pass-Through . . . . . . . . . . . . . 6-8
Creating Default User Profiles for the Subsystem . . . . . . . . . . . . . . . 6-8
Creating Job Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Adding a Work Station Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Adding Communications Entries . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Adding Routing Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Chapter 7. Display Station Pass-Through Considerations . . . . . . . . . . 7-1

Security Considerations for Display Station Pass-Through . . . . . . . . . . . . 7-1
Pass-Through Use with System/36 . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Display Station Pass-Through Message Handling . . . . . . . . . . . . . . . . . 7-2
Automatic Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Using the STRPASTHR Command for AS/400 Automatic Sign-On . . . . . 7-3
Automatic Sign-On Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Automatic Sign-On Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Automatic Sign-On Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Pass-Through Sign-On Attempt Examples . . . . . . . . . . . . . . . . . . . . . 7-8
Sign-On Specifying Remote User Profile as *NONE—Example . . . . . . . 7-8
Sign-On Specifying Remote User Profile as *CURRENT—Example . . . . . 7-9
Sign-On Specifying an Individual Remote User—Example . . . . . . . . . . 7-9
APPC and APPN Considerations for Pass-Through . . . . . . . . . . . . . . . 7-11
Low-Entry Networking Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Printer Output from a Target System . . . . . . . . . . . . . . . . . . . . . . . 7-13
Remote Printer Pass-Through . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Chapter 8. Display Station Pass-Through Configuration Scenario . . . . . 8-1

APPN Configuration Scenario for Display Station Pass-Through . . . . . . . . 8-1
Denver Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Rochester Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Chicago Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Atlanta Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Boston Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Configuring a System/38 in an APPN Network—Example . . . . . . . . . . . . 8-9
System/38 Attached to an AS/400 System . . . . . . . . . . . . . . . . . . . 8-9
AS/400 System Attached to a System/38 . . . . . . . . . . . . . . . . . . . 8-10
Adding a Local Location to an AS/400 APPN Configuration . . . . . . . . . 8-11
Pass-Through in a Multiple Product Network . . . . . . . . . . . . . . . . . 8-12

Part 2. Configuring for 5250 Remote Control Units

iv Remote Work Station Support V4R1

Chapter 9. Configuring 5250-Type Controllers—Scenario . . . . . . . . . . 9-1
5250 Remote Work Station Communications . . . . . . . . . . . . . . . . . . . . 9-1
Configuration of Remote Devices and 5394 Remote Control Units . . . . . . 9-2
SDLC Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Configuration of the AS/400 System . . . . . . . . . . . . . . . . . . . . . . . 9-4
Configuration Using CL Commands . . . . . . . . . . . . . . . . . . . . . . 9-11
Configuration of Controller Descriptions for Automatic Connection . . . . . 9-12
Automatic Dialing to a Remote Work Station Controller—Example . . . . . 9-13
Attaching DBCS-Capable Devices to 5250 Controllers . . . . . . . . . . . . 9-14

Chapter 10. Configuring for the IBM 5394 Type 2.1 RPQ . . . . . . . . . 10-1
Overview of the AS/400 System 5394 Type 2.1 Support . . . . . . . . . . . . 10-1
5394 Remote Control Unit in an SNA Subarea Network Node . . . . . . . 10-1
5394 Remote Control Unit in an APPN Network Node . . . . . . . . . . . . 10-2
5394 Remote Control Unit in a Peer Network Node . . . . . . . . . . . . . 10-3
Setting Up the 5394 Type 2.1 Node Support . . . . . . . . . . . . . . . . . . . 10-4
Configuring the AS/400 System to Communicate With the 5394 Type 2.1
Remote Control Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Configuring the 5394 Remote Control Unit and Its Work Stations . . . . . 10-6
Using the 5394 Remote Control Unit . . . . . . . . . . . . . . . . . . . . . . . 10-8
Managing the 5394 Remote Control Unit . . . . . . . . . . . . . . . . . . . 10-8

Chapter 11. Configuring 5494 Remote Control Units . . . . . . . . . . . . 11-1

How the 5494 Remote Control Unit Works . . . . . . . . . . . . . . . . . . . . 11-1
Configuring the 5494 Remote Control Unit on the AS/400 System . . . . . . 11-3
Step 1: Configuring a Line to the Network . . . . . . . . . . . . . . . . . . 11-5
Step 2: Configuring a Controller Description . . . . . . . . . . . . . . . . . 11-5
Step 3: Configuring a Remote Work Station Controller . . . . . . . . . . . 11-7
Step 4: Configuring Dependent Work Stations . . . . . . . . . . . . . . . . 11-9
Changing Device Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
AS/400 Configuration Examples for the 5494 Remote Control Unit . . . . 11-10
Synchronous Data Link Control Configuration Example . . . . . . . . . . 11-11
SDLC Configuration Matching Parameters . . . . . . . . . . . . . . . . . . 11-11
X.25 Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
X.25 Configuration Matching Parameters . . . . . . . . . . . . . . . . . . 11-13
Token-Ring Attachment Configuration Example . . . . . . . . . . . . . . . 11-14
Token-Ring Attachment Configuration Matching Parameters . . . . . . . 11-15
Managing the 5494 Remote Control Unit . . . . . . . . . . . . . . . . . . . . 11-16
Active APPC Subsystem Required . . . . . . . . . . . . . . . . . . . . . . 11-17
System Reference Codes and the 5494 Remote Control Unit . . . . . . 11-17
| Changing the 5494 Remote Control Unit Password . . . . . . . . . . . . 11-18
| Retrieving Vital Product Data . . . . . . . . . . . . . . . . . . . . . . . . . 11-18

Part 3. Configuring for 3270 Remote Device Support

Chapter 12. Using 3270 Device Support . . . . . . . . . . . . . . . . . . . . 12-1

3270 Device Support—Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
5250 Data Stream Optimization Support . . . . . . . . . . . . . . . . . . . . . 12-1
Creating a Data Area for the 5250 Optimization Value . . . . . . . . . . . . 12-3
Creating and Changing the Controller Description . . . . . . . . . . . . . . 12-3
3270 Device Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Configuration of Keyboard Changes . . . . . . . . . . . . . . . . . . . . . . . . 12-5
3270 and 5250 Keyboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Contents v
Keyboard Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Corresponding 3270 Keys and 5250 Functions . . . . . . . . . . . . . . . . 12-7
3270 and 5250 Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Display Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Break Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Operator Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Operator Error Message Codes . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Field Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Blink, Reverse Image, and Underline Attributes . . . . . . . . . . . . . . . 12-13
3270-to-5250 Keyboard Mapping . . . . . . . . . . . . . . . . . . . . . . . 12-13

Chapter 13. 3270-Type Device Configuration Examples . . . . . . . . . . 13-1

3270 Remote Attachment—Scenario . . . . . . . . . . . . . . . . . . . . . . . 13-1
3270 Display Station Pass-Through—Scenario . . . . . . . . . . . . . . . . 13-2
3270-Type Remote Controllers in a Token-Ring Network . . . . . . . . . . . . 13-5
The Configuration Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Automatic Creation of 3270-Type Device Descriptions . . . . . . . . . . . . 13-8
Using the APPC Controller to Attach 3270-Type Devices . . . . . . . . . . 13-8
Attachment of DBCS-Capable Devices to 3270 Controllers . . . . . . . . 13-11

Chapter 14. Configuring SNA Pass-Through . . . . . . . . . . . . . . . . . 14-1

SNA Pass-Through—Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Upstream and Downstream Devices . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Configuring a Single AS/400 System for SNA Pass-Through
Support—Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Connection A: Configuring Upstream to the Target System . . . . . . . . 14-4
Connection B: Configuring Downstream to the Source Devices . . . . . . 14-5
Configuring SNA Pass-Through with an Intermediate AS/400 Node . . . . . 14-7
Connection A: Configuring Upstream to Target System . . . . . . . . . . . 14-8
Connection B: Configuring Downstream to the Source AS/400 System . 14-9
Connection C: Configuring Upstream to the Intermediate AS/400 System 14-9
Connection D: Configuring Downstream to Dependent Devices . . . . . 14-10
Several Intermediate AS/400 Systems . . . . . . . . . . . . . . . . . . . . 14-11
Configuring a Mixture of Supported and Nonsupported Devices . . . . . . . 14-11
Connection A: Configuring Upstream to the Target System . . . . . . . 14-12
Connection B: Configuring Downstream to the Source System . . . . . 14-12
Connection C: Configuring Upstream to the Intermediate System . . . . 14-12
Connection D: Configuring Downstream to Dependent Devices . . . . . 14-13
Connection E: Configuring Downstream to 5250 Devices . . . . . . . . 14-13
Configuring SNA Pass-Through to Support Several Source AS/400 Systems 14-13
Connection A: Configuring Upstream to Target System . . . . . . . . . . 14-14
Connection B: Configuring Downstream to Dependent Device 327x 1 . 14-14
Connection C: Configuring Attachment to Intermediate Node 2 . . . . . 14-14
Connection D: Configuring Attachment to Intermediate Node 1 . . . . . 14-15
Connection E: Configuring Upstream to Target System 2 . . . . . . . . 14-15
Connection F: Configuring Downstream to Dependent 327x Device 2 . 14-15
Grouping of Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
SNA Pass-Through Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16

Chapter 15. Distributed Host Command Facility . . . . . . . . . . . . . . . 15-1

vi Remote Work Station Support V4R1

Host System Requirements for a DHCF Session . . . . . . . . . . . . . . . 15-2
Host Command Facility—Benefits . . . . . . . . . . . . . . . . . . . . . . . . 15-2
HCF Network Node—Definition . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Display Stations in an HCF Network . . . . . . . . . . . . . . . . . . . . . . 15-4
How OS/400 DHCF Interconnects with Multiple Systems . . . . . . . . . . 15-4
Host System Programming Considerations for DHCF . . . . . . . . . . . . . . 15-5
VTAM/NCP Programming—Tips . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Host System Work Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
DHCF Configuration Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Line Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Controller Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Device Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Using DHCF for Remote Management . . . . . . . . . . . . . . . . . . . . . 15-10
Logging on the Host System . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-11
DHCF Logon Modes (via HCF) . . . . . . . . . . . . . . . . . . . . . . . . 15-11
Start the DHCF Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Ending the DHCF Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Summary of HCF Session Commands Relating to the AS/400 System . 15-13
HCF Host System 3270 Terminal Requirements . . . . . . . . . . . . . . . . 15-13
Extended Display Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Display Station Requirements for DHCF . . . . . . . . . . . . . . . . . . . . 15-14
3270 and 5250 Keyboard and Display Differences . . . . . . . . . . . . . 15-14
Messages in DHCF Sessions . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
DHCF Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Differences from System/36 DHCF Support . . . . . . . . . . . . . . . . . 15-15
Differences from System/38 DHCF Support . . . . . . . . . . . . . . . . . 15-15

Chapter 16. Network Routing Facility . . . . . . . . . . . . . . . . . . . . . 16-1

Network Routing Facility—Definition . . . . . . . . . . . . . . . . . . . . . . . . 16-1
How NRF Operates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Network Routing Facility Sessions . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Network Routing Facility—Benefits . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Passing Through an SNA Network to an AS/400 System . . . . . . . . . . 16-2
Adding Flexibility to an SNA Backbone Network . . . . . . . . . . . . . . . 16-3
Configuring the AS/400 System to Support Network Routing Facility . . . . . 16-4
Specifying Parameters for Network Routing Facility Support . . . . . . . . 16-5
Step 1: Configuring the Line to the Host Network . . . . . . . . . . . . . . 16-5
Step 2: Configuring the Host Controller to Support Network Routing
Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Step 3: Configuring the Device . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Using Network Routing Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
3270 Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
Customizing Your SNA 3270 Display Keyboard Map . . . . . . . . . . . . . 16-9
AS/400 Work Station Printing . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
Ending Network Routing Facility . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
VTAM Logon Mode and Definition Table Examples . . . . . . . . . . . . . . 16-10
Logmode Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Network Control Program Definitions . . . . . . . . . . . . . . . . . . . . . 16-13
VTAM Definitions for the AS/400 System . . . . . . . . . . . . . . . . . . 16-15
VTAM Definitions for the 3174 Controller . . . . . . . . . . . . . . . . . . 16-16

Chapter 17. SNA Primary LU2 Support . . . . . . . . . . . . . . . . . . . . 17-1

SNA Primary LU2 Support—Definition . . . . . . . . . . . . . . . . . . . . . . . 17-1
SNA Primary LU2 Support Performance—Tips . . . . . . . . . . . . . . . . 17-2

Contents vii
Differentiating SNA Primary LU2 Support from Similar Functions . . . . . . . 17-2
Benefits of SNA Primary LU2 Support . . . . . . . . . . . . . . . . . . . . . . . 17-3
Devices Supported by SNA Primary LU2 Support . . . . . . . . . . . . . . . . 17-4
Software Requirements for SNA Primary LU2 Support . . . . . . . . . . . . . 17-5
SNA Primary LU2 Support Sessions . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Configuring the AS/400 System for SNA Primary LU2 Support . . . . . . . . 17-6
Automatic Configuration of Devices . . . . . . . . . . . . . . . . . . . . . . . 17-6
Configuration Steps for SNA Primary LU2 Support . . . . . . . . . . . . . . 17-8
Starting SNA Primary LU2 Support Sessions . . . . . . . . . . . . . . . . . . 17-20
3270 Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Customizing Your SNA 3270 Display Keyboard Map . . . . . . . . . . . . 17-20
AS/400 Work Station Printing . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Creating a Printer Device Description for the Associated Printer . . . . 17-21
Ending SNA Primary LU2 Support Sessions . . . . . . . . . . . . . . . . . . 17-21
Examples of VTAM Logon Mode Tables and Definitions . . . . . . . . . . . 17-21
Logon Mode Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Network Control Program Definitions . . . . . . . . . . . . . . . . . . . . . 17-23
VTAM Definitions for the AS/400 System . . . . . . . . . . . . . . . . . . 17-24
VTAM Definitions for the 3174 Establishment Controller . . . . . . . . . . 17-26
Matching Parameters for an SDLC Line . . . . . . . . . . . . . . . . . . . . . 17-26
Matching Parameters for a Token-Ring Line . . . . . . . . . . . . . . . . . . 17-27

| Chapter 18. Dependent LU Requester Support . . . . . . . . . . . . . . . 18-1

| Dependent LU Requester Support—Definition . . . . . . . . . . . . . . . . . . 18-1
| Devices Supported by Dependent LU Requester . . . . . . . . . . . . . . . . 18-2
| Before You Begin Configuring the AS/400 System for Dependent LU
| Requester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
| Before You Begin Creating Device and Controller Descriptions . . . . . . . . 18-2
| AS/400 DLUR Session Activation . . . . . . . . . . . . . . . . . . . . . . . . 18-2
| Dependent Logical Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
| Error Recovery Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
| Configuration Steps for Dependent LU Requester . . . . . . . . . . . . . . 18-4
| Logon Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
| 3270 Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
| VTAM Cross-Domain Resource Definition . . . . . . . . . . . . . . . . . . . . 18-7
| VTAM Definitions for the AS/400 System for DLUR Support . . . . . . . . 18-8
| VTAM Definitions for the AS/400 System for APPN Connections . . . . . 18-8
| Matching Parameters for the AS/400 DLUR and VTAM . . . . . . . . . . 18-11
| Matching Parameters for the APPN Connection between the AS/400 and
| VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11

Part 4. Configuring for X.21 Short Hold Mode

Chapter 19. X.21 Short-Hold Mode Configuration Example . . . . . . . . 19-1

Multiple Port Sharing Configuration Example . . . . . . . . . . . . . . . . . . . 19-1
Configuring the AS/400 Line Description for Multiple Port Sharing . . . . . 19-1
3274 Control Unit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Configuring AS/400 Controller and Device Descriptions for the 3274 . . . 19-3
5294 Remote Control Unit Configuration . . . . . . . . . . . . . . . . . . . . 19-5
Configuring AS/400 Controller and Device Descriptions for the 5294 . . . 19-6
5394 Remote Control Unit Configuration . . . . . . . . . . . . . . . . . . . . 19-7
Configuring AS/400 Controller and Device Descriptions for the 5394 . . . 19-8

viii Remote Work Station Support V4R1

Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
AS/400 Communications Books . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
Other AS/400 Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
Non-AS/400 Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-2
Redbooks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-2

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-3

Contents ix
x Remote Work Station Support V4R1
Figures
1-1. Pass-Through Environment . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
| 2-1. WRKCFGSTS Display for APPC Devices . . . . . . . . . . . . . . . . 2-5
4-1. Networking Example for Location Names . . . . . . . . . . . . . . . . 4-3
4-2. Networking Using CNNDEV . . . . . . . . . . . . . . . . . . . . . . . . 4-7
5-1. Pass-Through and TELNET Home System and End System . . . . . 5-4
6-1. QRMTSIGN Example Sign On CL Program . . . . . . . . . . . . . . . 6-5
7-1. Low-Entry Network Nodes Example . . . . . . . . . . . . . . . . . . . 7-11
8-1. Pass-Through Configuration Example . . . . . . . . . . . . . . . . . . . 8-1
8-2. CL Program for Configuring Denver AS/400 System . . . . . . . . . . 8-2
8-3. CL Program for Configuring Rochester AS/400 System . . . . . . . . 8-3
8-4. CL Program for Configuring Chicago AS/400 System . . . . . . . . . 8-6
8-5. CL Program for Configuring Boston System/38 . . . . . . . . . . . . . 8-7
8-6. System/38 Attached to an AS/400 System Program Example . . . . 8-10
8-7. AS/400 System Attached to System/38 Program Example . . . . . . 8-11
8-8. Adding a Local Location to an AS/400 APPN Configuration . . . . . 8-12
8-9. Complex Example of Pass-Through Networking . . . . . . . . . . . . 8-14
9-1. Remote Work Station Communications Example . . . . . . . . . . . . 9-2
9-2. 5394 Configuration Display-Boston . . . . . . . . . . . . . . . . . . . . 9-3
9-3. Prompt Displays for SOXLINE SDLC Line Description . . . . . . . . . 9-5
9-4. Prompt Display for BOSTON Remote Work Station Controller
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
9-5. Prompt Display for CHICAGO Remote Work Station Controller
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
9-6. Prompt Display for BOSPRT Printer Device Description . . . . . . . . 9-9
9-7. Prompt Display for CHIPRT Printer Device Description . . . . . . . 9-10
9-8. Prompt Display for BOSDSP Display Device Description . . . . . . 9-10
9-9. Controller Description Specifying Automatic Connection When Varied
On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
9-10. Automatic-Dial Example CL Program . . . . . . . . . . . . . . . . . . 9-14
9-11. Configuration Example Using DBCS-Capable Devices . . . . . . . . 9-15
10-1. Subarea Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
10-2. APPN Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
10-3. Peer Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
10-4. Host Controller Description Example . . . . . . . . . . . . . . . . . . 10-5
| 11-1. 5494 Remote Control Unit in a Token-Ring Gateway Configuration 11-2
| 11-2. 5494 Remote Control Unit with AS/400 Token-Ring Attachment
| Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
11-3. APPC Controller Description Example . . . . . . . . . . . . . . . . . 11-6
11-4. SNA Host Controller Description Example . . . . . . . . . . . . . . . 11-7
11-5. Remote Work Station Controller Description Example . . . . . . . . 11-8
11-6. Device Description Example . . . . . . . . . . . . . . . . . . . . . . 11-10
11-7. SDLC Configuration Example . . . . . . . . . . . . . . . . . . . . . 11-11
11-8. SDLC Configuration Matching Parameters . . . . . . . . . . . . . . 11-12
11-9. X.25 Configuration Example . . . . . . . . . . . . . . . . . . . . . . 11-13
11-10. X.25 Configuration Matching Parameters . . . . . . . . . . . . . . . 11-14
11-11. Token-Ring Attachment Configuration Example . . . . . . . . . . . 11-15
11-12. Token-Ring Attachment Configuration Matching Parameters . . . 11-15
12-1. CL Program to Set Keyboard Map for DHCF, NRF, and SPLS
Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16

 Copyright IBM Corp. 1997 xi

12-2. CL Program to Set Keyboard Map for 3270 Remote Attach
Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
13-1. Configuration Example of 3270 Remote Attachment Support . . . . 13-1
13-2. Configuration Example of 3270 Display Station Pass-Through . . . 13-2
13-3. System Connection Status Symbol for 3270 Display Station . . . . 13-4
13-4. Job Connection Status Symbol for 3270 Display Station . . . . . . . 13-5
13-5. PU Type 2.0 Controller . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
13-6. PU Type 2.1 Controller . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
14-1. SNA Pass-Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
14-2. Grouping SNA Pass-Through Devices . . . . . . . . . . . . . . . . . 14-2
14-3. Upstream Devices Sharing a Downstream Printer . . . . . . . . . . 14-3
14-4. Crossing Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
14-5. SNA Pass-Through with Single AS/400 System . . . . . . . . . . . . 14-4
14-6. SNA Pass-Through Environment with an Intermediate AS/400
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
14-7. SNA Pass-Through Configured for a Mixture of Supported and
Nonsupported Devices . . . . . . . . . . . . . . . . . . . . . . . . . 14-11
14-8. SNA Pass-Through Support of Multiple-Source AS/400 Systems . 14-14
15-1. Several Host Users Remotely Operating an AS/400 System . . . . 15-3
15-2. Logical Connection to OS/400 DHCF . . . . . . . . . . . . . . . . . . 15-4
15-3. Using AS/400 3270 Emulation with OS/400 DHCF . . . . . . . . . . 15-5
15-4. SDLC Nonswitched Line Configuration . . . . . . . . . . . . . . . . 15-10
16-1. Passing through a System/370 Network to Access an AS/400
System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
16-2. NRF within an SNA Backbone Network . . . . . . . . . . . . . . . . . 16-4
16-3. Step 1: Configuring the Line to the System/370 Host Network . . . 16-6
16-4. Step 2: Configuring the Host Controller to Support NRF . . . . . . 16-7
16-5. Step 3: Configuring the Device to Controller . . . . . . . . . . . . . 16-8
16-6. Sample System/370 VTAM Logmode Tables . . . . . . . . . . . . 16-11
16-7. System/370 VTAM Tables Defining NCP on the SNA
Communications Controller . . . . . . . . . . . . . . . . . . . . . . . 16-14
16-8. System/370 VTAM AS/400 System Definitions . . . . . . . . . . . 16-16
16-9. System/370 VTAM Tables Defining the 3174 Controller . . . . . . 16-17
17-1. Configuration Example for Connecting a 3270 Display Station to an
AS/400 System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
17-2. Example of a 3174 Gateway Configuration for SPLS . . . . . . . . . 17-2
17-3. SPLS Configuration Example . . . . . . . . . . . . . . . . . . . . . . 17-3
17-4. Configuring the Line to the ES/9000 Host Network . . . . . . . . . . 17-9
17-5. Configuring the Host Controller to Support SPLS . . . . . . . . . . 17-10
17-6. Configuring a Display with an Application Type of *CTLSSN . . . 17-12
17-7. Configuring a Display with an Application Type of *DEVINIT . . . 17-14
17-8. Configuring a Printer with an Application Type of *APPINIT . . . . 17-17
17-9. Sample ES/9000 VTAM Logon Mode Tables . . . . . . . . . . . . 17-22
17-10. ES/9000 VTAM Tables Defining NCP on the SNA Communication
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-23
17-11. ES/9000 VTAM AS/400 System Definitions . . . . . . . . . . . . . 17-25
17-12. ES/9000 VTAM Tables Defining the 3174 Establishment Controller 17-26
| 18-1. DLUR - Multiple Paths Through the Network . . . . . . . . . . . . . . 18-1
| 18-2. Configuring the Host Controller to Support DLUR . . . . . . . . . . . 18-5
| 18-3. Configuring a Device Description Display . . . . . . . . . . . . . . . 18-6
| 18-4. VTAM CDRSC for Multihop Connection Example . . . . . . . . . . . 18-7
| 18-5. VTAM CDRSC CDRSC for Adjacent Connection Example . . . . . 18-7
| 18-6. Example of VTAM Initiating Connections . . . . . . . . . . . . . . . . 18-9
| 18-7. Example of VTAM with DLUR Initiating Connections . . . . . . . . 18-10

xii Remote Work Station Support V4R1

| 18-8. AS/400 as an Intermediate Node . . . . . . . . . . . . . . . . . . . . 18-8
| 18-9. VTAM AS/400 System Definitions for APPN Connections . . . . . . 18-8
| 18-10. Matching Parameters for AS/400 DLUR and VTAM . . . . . . . . . 18-11
| 18-11. Matching Parameter Between AS/400 and VTAM . . . . . . . . . . 18-12
19-1. 3274 Control Unit Configuration Displays . . . . . . . . . . . . . . . . 19-3
19-2. Prompt Display for SHM3274 Controller Description . . . . . . . . . 19-4
19-3. Prompt Display for SHM3274 Display Device Description . . . . . . 19-5
19-4. 5294 Remote Control Unit Configuration Display . . . . . . . . . . . 19-5
19-5. Prompt Display for SHM5294 Controller Description . . . . . . . . . 19-6
19-6. Prompt Display for SHM5294 Display Device Description . . . . . . 19-7
19-7. Configuration Display for 5394 Remote Control Unit . . . . . . . . . 19-8
19-8. Prompt Display for SHM5394 Controller Description . . . . . . . . . 19-9
19-9. Prompt Display for SHM5394 Display Device Description . . . . . . 19-9

Figures xiii
xiv Remote Work Station Support V4R1
Tables
3-1. Physical and Virtual Display Stations of Source and Target Systems 3-4
7-1. User Specifies RMTUSER(*NONE) . . . . . . . . . . . . . . . . . . . . 7-8
7-2. User Specifies RMTUSER(*CURRENT) . . . . . . . . . . . . . . . . . 7-9
7-3. User Specifies RMTUSER(Own Profile) . . . . . . . . . . . . . . . . 7-10
7-4. User Specifies RMTUSER(Other Profile) . . . . . . . . . . . . . . . . 7-10
8-1. Pass-Through Configuration Text . . . . . . . . . . . . . . . . . . . . . 8-1
9-1. Devices Attached to Boston 5394 Controller, Station Address = 04 . 9-4
9-2. Devices Attached to Chicago 5394 Controller, Station Address = 05 . 9-4
9-3. LOCADR Values for Devices Attached to 5394 Controllers . . . . . . 9-8
9-4. *LINKTYPE Values and Corresponding DIALINIT Values . . . . . . 9-13
11-1. LOCADR Values for Devices Attached to 5494 Controllers . . . . . 11-9
12-1. 3270 Device Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
12-2. Various 5250 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
12-3. 3270 Error Code Descriptions . . . . . . . . . . . . . . . . . . . . . 12-12
12-4. Attribute Combinations on the 5251 and the 3279 Display Stations 12-13
13-1. DBCS Feature Values for DBCS-Capable Devices Attached to
3270 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11
15-1. AS/400 Support VTAM/NCP Configuration Work Sheet . . . . . . . 15-8
15-2. HCF Command Descriptions . . . . . . . . . . . . . . . . . . . . . . 15-13
| 17-1. Device Type and Model Selection . . . . . . . . . . . . . . . . . . . 17-14

 Copyright IBM Corp. 1997 xv

xvi Remote Work Station Support V4R1
Notices
References in this publication to IBM products, programs, or services do not imply
that IBM intends to make these available in all countries in which IBM operates.
Any reference to an IBM product, program, or service is not intended to state or
imply that only that IBM product, program, or service may be used. Subject to
IBM's valid intellectual property or other legally protectable rights, any functionally
equivalent product, program, or service may be used instead of the IBM product,
program, or service. The evaluation and verification of operation in conjunction with
other products, except those expressly designated by IBM, are the responsibility of
the user.

IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
500 Columbus Avenue
Thornwood, NY 10594
U.S.A

Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact the software interoperability coordinator.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee. Address your questions to:

IBM Corporation
Software Interoperability Coordinator
3605 Highway 52 N
Rochester, MN 55901-7829
U.S.A.

This publication could contain technical inaccuracies or typographical errors.

This publication may refer to products that are not currently available. IBM makes
no commitment to make available any unannounced products referred to herein.
The final decision to announce any product is based on IBM's business and tech-
nical judgment.

This publication contains examples of data and reports used in daily business oper-
ations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

This publication contains small programs that are furnished by IBM as simple
examples to provide an illustration. These examples have not been thoroughly
tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, ser-
viceability, or function of these programs. All programs contained herein are pro-

 Copyright IBM Corp. 1997 xvii

vided to you “as is.” The implied warranties of merchantability and fitness for
a particular purpose are expressly disclaimed.

Trademarks
The following terms are trademarks of the IBM Corporation in the United States or
other countries or both:

ACF/VTAM
Advanced Peer-to-Peer Networking
Application System/400
APPN
AS/400
CICS
ES/9000
IBM
Intelligent Printer Data Stream
IPDS
MVS/ESA
Operating System/400
OS/2
OS/400
S/370
SAA
Series/1
System/36
System/370
System/38
Systems Application Architecture
VTAM
400

Microsoft, Windows, and the Windows 95 logo are trademarks or registered trade-
marks of Microsoft Corporation.

PC Direct is a trademark of Ziff Communications Company and is used by IBM

Corporation under license.

UNIX is a registered trademark in the United States and other countries licensed
exclusively through X/Open Company Limited

C-bus is a trademark of Corollary, Inc.

Java and HotJava are trademarks of Sun Microsystems, Inc.

Other company, product, and service names, which may be denoted by a double
asterisk (**), may be trademarks or service marks of others.

xviii Remote Work Station Support V4R1

About Remote Work Station Support (SC41-5402)
You can greatly expand the capabilities of the AS/400 system by using work
stations, devices, and controllers that are locally or remotely attached to the
system. Using remote work stations can enable you to access other facilities and
functions that are not available on the system on which you are currently working.

This book provides information to configure and use remote work stations to access
an AS/400 system. The sections in this book contain information about:
| Configuring and using the 5250 display station pass-through function (see Part
| 1. Display Station Pass-Through).
| This part describes how to set up and use the 5250 display station pass-
| through function to access other systems. The pass-through function allows you
| to pass through your system and sign on to another system without having to
| sign off your system.
| Configuring 5294, 5394, and 5494 controllers (see Part 2. Configuring for 5250
| Remote Control Units).
| This part discusses the 5250-type remote control units. It contains information
| about defining devices, configuring keyboards, and understanding error mes-
| sages. It also contains examples on configuring these controllers. The first
| chapter describes configuring general 5250-type devices, and the final two
| chapters describe configuring specific 5250-type devices: the 5394 type 2.1
| node, and the 5494 Remote Control Unit.
| Configuring an AS/400 system for using 3270 remote attachment support and
| the SNA pass-through support (see Part 3. Configuring for 3270 Remote
| Device Support).
| This part discusses the AS/400 3270 device support. Included in the discussion
| is information about defining devices, configuring keyboards, and understanding
| error messages for the 3270 remote work station controller. Also included is
| information about configuring and using 3270 remote attachment support and
| the SNA pass-through support. Also included is subarea connectivity using Dis-
| tributed Host Command Facility (DHCF), Network Routing Facility (NRF), SNA
| Primary LU2 Support (SPLS), and Dependent LU Requester (DLUR) support.
| Configuring X.21 short hold mode (SHM) (see Part 4. Configuring for X.21
| Short Hold Mode).
| This part contains examples on configuring X.21 short hold mode (SHM) config-
| uration.

Included in this book are examples that can be used as models when creating
applications on your system. For more information about configuring remote facili-
ties, see the Communications Configuration book.

Before using this book, you must be familiar with the use of the AS/400 system. A
knowledge of configuration concepts and networking is helpful.

You may need to refer to other IBM books for more specific information about a
particular topic. The Publications Reference provides information on all the books in
the AS/400 library. For a list of publications related to this book, see the
“Bibliography” on page X-1.

 Copyright IBM Corp. 1997 xix

Any mention of the 5394 Support as a type 2.1 node is a reference to Request for
Price Quotation (RPQ) 8Q0775 on the AS/400 system.

Who Should Use This Book

This book is intended for use by system users who want to configure the following
communications support:
| Display station pass-through
| 5250 and 3270 remote work station communications
| Dependent logical unit requester (DLUR)
| Distributed host command facility (DHCF)
| Network routing facility (NRF)
| SNA Primary LU2 Support (SPLS)
| SNA pass-through

You should be familiar with the general communications concepts and communi-
cations configuration on the AS/400 system. For more information on general com-
munications concepts, refer to the Discover/Education Introduction to Data
Communications course (course code DE004).

| Information Available on the World Wide Web

| More AS/400 information is available on the World Wide Web. You can access this
| information from the AS/400 home page, which is at the following uniform resource
| locator (URL) address:
| http://www.as4ðð.ibm.com

| Select the Information Desk, and you will be able to access a variety of AS/400
| information topics from that page.

xx Remote Work Station Support V4R1

Part 1. Display Station Pass-Through
Chapter 1. Pass-Through Instructions for the End User . . . . . . . . . . . 1-1
Display Station Pass-Through Environment . . . . . . . . . . . . . . . . . . . . . 1-1
Choosing the Target System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Using Display Station Pass-Through Commands . . . . . . . . . . . . . . . . . 1-2
Starting Pass-Through (STRPASTHR Command) . . . . . . . . . . . . . . . 1-3
Starting Display Station Pass-Through with APPN Support . . . . . . . . 1-3
Starting Display Station Pass-Through without APPN Support . . . . . . 1-4
Going Back and Forth between Systems . . . . . . . . . . . . . . . . . . . . 1-5
Ending Pass-Through (ENDPASTHR Command) . . . . . . . . . . . . . . . . 1-5
Signing Off (SIGNOFF Command) . . . . . . . . . . . . . . . . . . . . . . . . 1-6
End Connection Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

| Chapter 2. Using Server Jobs for Target Display Station Pass-Through . 2-1
| Automatic Startup of Communications Servers for Pass-Through . . . . . . . . 2-1
| Communications Server Commands . . . . . . . . . . . . . . . . . . . . . . . 2-1
| Setting the QPASTHRSVR System Value . . . . . . . . . . . . . . . . . . . . 2-2
| Pass-Through Server Considerations . . . . . . . . . . . . . . . . . . . . . . . 2-3
| Communications Server Jobs for Pass-Through . . . . . . . . . . . . . . . 2-3
| Job Descriptions for Pass-Through Servers . . . . . . . . . . . . . . . . . 2-3
| Default User Profiles for the Subsystem . . . . . . . . . . . . . . . . . . . 2-3
| Communications Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
| Using Status Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
| Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Chapter 3. Configure Display Station Pass-Through . . . . . . . . . . . . . 3-1

Configuration of Virtual Controllers and Devices . . . . . . . . . . . . . . . . . . 3-1
Virtual Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Automatic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Automatic Configuration Considerations . . . . . . . . . . . . . . . . . . . 3-2
Manual Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Matching Display Stations for Source and Target Systems . . . . . . . . 3-4
Using Personal Computers for Display Stations . . . . . . . . . . . . . . . 3-5
Using Utilities during Pass-Through . . . . . . . . . . . . . . . . . . . . . . 3-5
TELNET Automatic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Security Considerations for Virtual Controllers and Devices . . . . . . . . . . 3-6
Creating User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Chapter 4. Starting and Using a Display Station Pass-Through Session . 4-1

 Copyright IBM Corp. 1997

Virtual Display Device (VRTDEV) Parameter . . . . . . . . . . . . . . . . . 4-10

Chapter 5. Going Back and Forth between Systems . . . . . . . . . . . . . 5-1

Chapter 6. Work Management Considerations for Display Station

Pass-Through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Control of Remote Sessions from Other Systems . . . . . . . . . . . . . . . . . 6-1
The QRMTSIGN System Value . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Remote Sign-On Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
QRMTSIGN Program Specifications . . . . . . . . . . . . . . . . . . . . . . . 6-2
Input to the QRMTSIGN Program . . . . . . . . . . . . . . . . . . . . . . . 6-3
Output from the QRMTSIGN Program . . . . . . . . . . . . . . . . . . . . 6-4
QRMTSIGN Programming Considerations . . . . . . . . . . . . . . . . . . . . 6-7
Creating a Subsystem for Display Station Pass-Through . . . . . . . . . . . . . 6-8
Creating Default User Profiles for the Subsystem . . . . . . . . . . . . . . . 6-8
Creating Job Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Adding a Work Station Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Adding Communications Entries . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Adding Routing Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Chapter 7. Display Station Pass-Through Considerations . . . . . . . . . . 7-1

Security Considerations for Display Station Pass-Through . . . . . . . . . . . . 7-1
Pass-Through Use with System/36 . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Display Station Pass-Through Message Handling . . . . . . . . . . . . . . . . . 7-2
Automatic Sign-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Using the STRPASTHR Command for AS/400 Automatic Sign-On . . . . . 7-3
Automatic Sign-On Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Parameters That Can be Overridden by the Remote Sign-On Control
Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Automatic Sign-On Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Automatic Sign-On Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Pass-Through Sign-On Attempt Examples . . . . . . . . . . . . . . . . . . . . . 7-8
Sign-On Specifying Remote User Profile as *NONE—Example . . . . . . . 7-8
Sign-On Specifying Remote User Profile as *CURRENT—Example . . . . . 7-9
Sign-On Specifying an Individual Remote User—Example . . . . . . . . . . 7-9
APPC and APPN Considerations for Pass-Through . . . . . . . . . . . . . . . 7-11
Low-Entry Networking Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Printer Output from a Target System . . . . . . . . . . . . . . . . . . . . . . . 7-13
Remote Printer Pass-Through . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Chapter 8. Display Station Pass-Through Configuration Scenario . . . . . 8-1

Remote Work Station Support V4R1

AS/400 System Attached to a System/38 . . . . . . . . . . . . . . . . . . . 8-10
Adding a Local Location to an AS/400 APPN Configuration . . . . . . . . . 8-11
Pass-Through in a Multiple Product Network . . . . . . . . . . . . . . . . . 8-12

Part 1. Display Station Pass-Through

Remote Work Station Support V4R1
Chapter 1. Pass-Through Instructions for the End User
This chapter has instructions for an end user who is beginning to use the display
station pass-through function. These instructions assume the configuration is com-
plete. If your AS/400 system is not already configured for display station pass-
through, contact your system administrator or see Chapter 3, “Configure Display
Station Pass-Through” on page 3-1 for information on configuration.

Display Station Pass-Through Environment

Display station pass-through allows a user with a display station signed on to one
system to sign on to another system. The source system sends the request to
establish communications with the target system. The target system receives the
request to establish communications with the source system.

Figure 1-1 shows a typical pass-through environment. The AS/400 system user
working at Display Station 1 uses the display station pass-through function to
access System B through System A.

System A System B
┌─────────┬─┐ ┌─────────┬─┐
│┌────────┤ │ │┌────────┤ │
│├────────┤ │ │├────────┤ │
││ │ │ ││ │ │
│├────────┤ │ │├────────┤ │
┌───────────┐ │├┬──────┬┤ │ │├┬──────┬┤ │
│┌─────────┐│ │││ ││ │ │││ ││ │
││ ││ ││└──────┘│ │ ││└──────┘│ │
││ ││ ││┌──────┐│ │ ┌─────┤│┌──────┐│ │
│└─────────┘├────────┤│└──────┘│ ├────┘ ││└──────┘│ │
└─┬───────┬─┘ │├────────┤ │ │├────────┤ │
┌┴───────┴┐ ││ ┌─┐ │ │ ││ ┌─┐│ │
├─────────┤ ││ │ │ │ │ ││ │ ││ │
└─────────┘ ││ └─┘ │ │ ││ └─┘│ │
Display Station 1 ││ │ │ ││ │ │
│└────────┘ │ │└────────┘ │
└───────────┘ └───────────┘
Source System Target System
Figure 1-1. Pass-Through Environment

Your display station is attached, either locally or remotely, to the source system
(System A). You pass through the source system to the target system (System B).

Choosing the Target System

 Copyright IBM Corp. 1997 1-1

The remote location name is the name of a location defined at the target
system to which you want to pass through. The RMTLOCNAME parameter is
the only parameter you need to specify if all the following conditions are met:
– The entire route from the source system to the target system consists of
systems using APPN support.
– Both the target and source systems are located in the same APPN
network.
If the target and source systems are located in different APPN networks, the
target system network ID must be indicated in the remote network identifier
(RMTNETID) parameter.
Specify a list of nonnetworking advanced program-to-program communications
(APPC) devices that describe some or all of the route to the target system.
Specify a remote location name and a list of nonnetworking APPC devices.
Pass-through uses APPN support to find a route to the system containing the
specified remote location name. That system is then used as the first system to
do pass-through routing. The list of nonnetworking devices specifies the
remaining route to the target system.

The method you choose depends on how communications descriptions are defined
on your system. For more information on these methods, see “Choosing the Target
System” on page 4-1. To learn more about the capabilities and configuration of
APPN functions, see the APPN Support book.

Using Display Station Pass-Through Commands

The display station pass-through function uses the Start Pass-Through
(STRPASTHR), Transfer Pass-Through (TFRPASTHR), End Pass-Through
(ENDPASTHR), and Sign off (SIGNOFF) commands.

To start the display station pass-through function, type STRPASTHR on the command
line and press F4 (Prompt) to reach the Start Pass-Through prompt display, or type
GO CMDPASTHR and then press the Enter key to reach the Command Pass-Through
display, where you can choose the option to start a pass-through session.

If you need to specify additional parameters on the STRPASTHR command or want

to see more information on using this command, see Chapter 4, “Starting and
Using a Display Station Pass-Through Session” on page 4-1 or the CL Program-
ming book.

After the STRPASTHR command, sign on the target system and use that system
as if your work station were directly attached to the target system.

You can return to the source system by using the Transfer Pass-Through
(TFRPASTHR) command or the End Pass-Through (ENDPASTHR) command. The
TFRPASTHR command does not end the pass-through session; therefore, you can
return to the target system. Use the ENDPASTHR command to end your pass-
through session.

1-2 Remote Work Station Support V4R1

Starting Pass-Through (STRPASTHR Command)
The Start Pass-Through (STRPASTHR) command allows you to connect your
display station to another system in your network. Using Figure 1-1 on page 1-1 as
an example, System A must have information about your display station (Display
Station 1) and the target system (System B) in this example. This information
allows you to sign on the target system (System B) and use that system.

To start a pass-through session, type STRPASTHR on any command line and press
F4 (Prompt). The following display appears:

à ð
Start Pass-Through (STRPASTHR)

Type choices, press Enter.

Remote location . . . . . . . . _______ Name, \CNNDEV

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
You need to identify the remote location on the target system (System B in this
example). The following topics explain what to specify for the remote location,
which depends on whether or not you are using APPN support.

Starting Display Station Pass-Through with APPN Support

If you are using APPN support, specify the remote location name and then press
the Enter key. The following display appears:

Chapter 1. Pass-Through Instructions for the End User 1-3

à ð
Start Pass-Through (STRPASTHR)

Type choices, press Enter.

Remote location . . . . . . . . > SYSTEMB Name, \CNNDEV

Virtual controller . . . . . . . \NONE_____ Name, \NONE
Virtual display device . . . . . \NONE_____ Name, \NONE
+ for more values __________
Mode . . . . . . . . . . . . . . \NETATR_ Name, \NETATR
Local location . . . . . . . . . \LOC_____ Name, \LOC, \NETATR
Remote network identifier . . . \LOC_______ Name, \LOC, \NETATR, \NONE
System request program . . . . . \SRQMNU____ Name, \SRQMNU
Library . . . . . . . . . . . ___________ Name, \LIBL, \CURLIB

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Specify any other values you want and then press the Enter key.

Starting Display Station Pass-Through without APPN Support

If you are not using APPN support, specify *CNNDEV in the Remote location field
and then press the Enter key. The following display appears:

à ð
Start Pass-Through (STRPASTHR)

Type choices, press Enter.

Remote location . . . . . . . .> \CNNDEV_ Name, \CNNDEV

APPC device . . . . . . . . . . \LOC_____ Name, \LOC
+ for more values _________
Virtual controller . . . . . . . \NONE____ Name, \NONE
Virtual display device . . . . . \NONE____ Name, \NONE
+ for more values _________
System request program . . . . . \SRQMNU___ Name, \SRQMNU
Library . . . . . . . . . . . ________ Name, \LIBL, \CURLIB

Specify the APPC devices and any other values you want. Press the Enter key. For
more information about the APPC device field, see “The Connection Device” on
page 4-5.

For more information about the System request program field, see “ Using the
System Request Program (SRQ10PGM) Parameter” on page 5-7. For more infor-
mation about all the other fields, see Chapter 4, “Starting and Using a Display
Station Pass-Through Session” on page 4-1.

1-4 Remote Work Station Support V4R1

Going Back and Forth between Systems
You can use the following methods to go back and forth between systems.

Start Pass-Through (STRPASTHR) command

Transfer Pass-Through (TFRPASTHR) command
End Pass-Through (ENDPASTHR) command
Sign Off (SIGNOFF) command
System Request menu

For more information about going back and forth between systems, see Chapter 5,
“Going Back and Forth between Systems” on page 5-1.

In control language programs, use the TFRPASTHR command to suspend a job on

one system and go back to a job on another system. For details, see “Using the
Transfer Pass-Through (TFRPASTHR) Command” on page 5-5.

If you prefer using a menu, use the System Request menu to go back and forth
between systems. For details, see “Using System Request Options” on page 5-6.

Ending Pass-Through (ENDPASTHR Command)

You can return to the source system by using the End Pass-Through
(ENDPASTHR) command. Use this command when you are through working with
the job on the target system and want to return to the source system.

The End Pass-Through (ENDPASTHR) command runs on the target system. This
command signs you off the target job, and ends the pass-through session.

The only parameter on the ENDPASTHR command that you can specify is the
LOG parameter. If you specify LOG(*NOLIST), a job log is not produced. If you
specify LOG(*LIST), a job log is created at the target system.

The ENDPASTHR command fails if there is a secondary (alternate) job still running.
When you pass through to a System/38 or an AS/400 system, selecting option 1
(Display sign on for alternative job) on the System Request menu allows you to
sign on to a new job called the secondary or alternate job. If the first job that you
signed on to and the secondary job are both running, the ENDPASTHR command
does not end the pass-through session. To end the session, sign off one of the
sessions or use the ENDJOB command to end one of the jobs.
Note: The ENDPASTHR command uses the SIGNOFF command as part of its
process. If your system has a SIGNOFF command appearing in the library
list before QSYS/SIGNOFF, your SIGNOFF command is used by
ENDPASTHR.

The TFRPASTHR command and System Request options 10, 11, 13, 14, 15, and
80 do not end the pass-through session.

Chapter 1. Pass-Through Instructions for the End User 1-5

Signing Off (SIGNOFF Command)
If you are using the automatic sign-on function to sign on to the target system, the
SIGNOFF command ends the pass-through session and returns you to the original
session on the source system. If you are manually signed on to the target system,
the SIGNOFF command ends the current target job and you are returned to the
sign-on display of the target system.

End Connection Parameter

You can use the end connection (ENDCNN) parameter of the SIGNOFF command
to sign off the target system and end the pass-through session. For example,
entering SIGNOFF ENDCNN(*YES) returns you to your original job on the source
system. This works the same way whether or not you are using the automatic
sign-on function.

1-6 Remote Work Station Support V4R1

| Chapter 2. Using Server Jobs for Target Display Station
| Pass-Through
| This chapter provides information about communications servers for pass-through.

| In Version 4 Release 1, the target pass-through job structure was changed to elimi-
| nate the target pass-through communications user jobs. A set of server jobs now
| performs the functions of the communications job.

| Pass-through users will not see any functional changes. The pass-through server
| jobs simply take the place of the communications user jobs. System administrators
| will notice differences in the management of pass-through sessions. Using commu-
| nications servers for pass-through will result in better system performance during
| peak times (for example, when many PCs are starting or are ending).

| The communications servers for pass-through that are configured on your AS/400
| system are the default.

| Automatic Startup of Communications Servers for Pass-Through

| When the QSYSWRK subsystem starts, an autostart job in the subsystem starts
| the communications servers for pass-through.

| A system value, QPASTHRSVR, determines the number of communications server

| jobs for pass-through. The QPASTHRSVR system value has a default of *CALC
| which allows the system to determine the number of server jobs. When the
| QSYSWRK subsystem starts or ends, the system automatically starts and ends the
| communications servers for pass-through.

| Communications Server Commands

| There are two commands you can use to start and end the communications servers
| for pass-through.
| Start Communications Server (STRCMNSVR)
| This command starts the communications servers for pass-through.
| You can also use this command to increase or decrease the number of com-
| munications server jobs that are running at peak and non-peak times. To
| increase or decrease the number of server jobs, specify the new value in the
| NBRPASTHR parameter.
| See the online help for more information about this command.
| End Communications Server (ENDCMNSVR)
| This command ends the communications servers for pass-through. See the
| online help for more information about this command.
| Communications servers for pass-through end normally with the QSYSWRK
| subsystem. When the system is taken to a restricted state, the communications
| servers for pass-through and all pass-through sessions end. The communi-
| cations servers for pass-through detect and correctly process a controlled end
| as well as an immediate end of the subsystem. Therefore, the ENDCMNSVR
| command is not needed for normal operations.

 Copyright IBM Corp. 1997 2-1

| Use the ENDCMNSVR command only if you do not want to run pass-through
| by using communications server jobs.
| If you determine that you do not want pass-through to run using communi-
| cations server jobs, do the following steps:
| 1. Use the ENDCMNSVR command to end the communications servers for
| pass-through.
| 2. Change the system value QPASTHRSVR to 0. This tells the system that
| communications servers for pass-through should not start with the
| QSYSWRK subsystem.
| Note: You must have job control (*JOBCTL) special authority to use these com-
| mands.

| Setting the QPASTHRSVR System Value

| Use the Change System Value (CHGSYSVAL) command to change the value of
| the specified system value. The default for the QPASTHRSVR system value is
| *CALC. The system computes this value to be four communications server jobs for
| pass-through for each processor on your system. This may or may not be the
| optimum value for your system.

| If you have several PC clients running Client Access (DOS or Windows**) or OS/2
| Communications Manager 5250 emulation, you may be able to improve your client
| startup performance by increasing the number of communications server jobs for
| pass-through. However, you may see that increasing the number of pass-through
| server jobs has no effect or has a negative effect on the overall AS/400 system
| performance.

| You will have to determine the appropriate number of communications server jobs
| for pass-through to obtain the best performance for your system. If you leave this
| system value as *CALC, you should see an improvement in performance over
| using the communications user jobs as in previous releases. Only change the
| system value if you want to further optimize the performance of your system during
| peak times. Consider the following items when determining if you want to change
| the system value:
| Number of communications server jobs for pass-through
| Frequency of pass-through or work-station function (WSF) users connecting
| and disconnecting
| Maximum number of users that are connecting and are disconnecting at the
| same time
| Number of processors on the system and the size of the system

| If you are only using TELNET and VTM (virtual terminal manager), you will not
| need communications server jobs for pass-through.

| If you need to increase or decrease the number of servers, specify the number of
| servers you want active in the Number of servers field on the Change System
| Value display. The allowable values are 0 to l00.

| Changes to the system values take effect immediately, except when the following
| occurs:

2-2 Remote Work Station Support V4R1

| When you are going to 0, you will have to also use the ENDCMNSVR
| command.
| When you are going from 0, you will have to also use the STRCMNSVR
| command.

| Pass-Through Server Considerations

| Communications Server Jobs for Pass-Through

| There are two types of server jobs:
| QPASVRP - primary pass-through server job
| There is only one primary pass-through server job.
| QPASVRS - multiple secondary pass-through server jobs
| There can be 1 to 1000 secondary pass-through server jobs.

| The primary server job manages the secondary server jobs. Do NOT cancel this
| job. All pass-through users will lose their sessions if you cancel the job.

| The secondary server jobs do all of the work that was done by the communications
| jobs.

| The job logs for the secondary server jobs (QPASVRS) contain information that
| previously was in the job log for the communications job. When pass-through users
| encounter problems, you must check the secondary server job logs to determine
| the cause of the problem. Only one of the job logs will contain the cause.

| Unlike the TELNET server jobs, pass-through sessions are not assigned to any par-
| ticular secondary pass-through server job. There is no way to predict which server
| job will perform the function for any target pass-through session. Also, the pass-
| through servers are only involved in connecting and disconnecting. They are not
| involved in the data path.

| Job Descriptions for Pass-Through Servers

| The communications servers for pass-through have an IBM-supplied job
| description, QPASVR in library QSYS.

| Default User Profiles for the Subsystem

| Because there is no communications job, the communications entries in the sub-
| system descriptions are no longer used for target pass-through. Therefore, you
| cannot add a communications entry to a subsystem description to change the
| default user profile to something other than QUSER for pass-through. The default
| user profile that is used by the communications servers for pass-through is always
| QUSER and cannot be changed.

| Communications Entries
| Communications Entries for Automatic Signon: You cannot use *NONE for the
| default user profile to force pass-through users to always use automatic signon.
| Depending on the reason for a communications entry with a default user profile of
| *NONE, use one of the following options:
| If you want to prevent all communications programs from starting, this entry
| would still apply to other communications programs. To disable pass-through,

Chapter 2. Using Server Jobs for Target Display Station Pass-Through 2-3
| system value QRMTSIGN could be set to *REJECT which disables all pass-
| through to that system.
| If you want to force pass-through users to do automatic signon, the only option
| available is to write a user program for the QRMTSIGN system value. See
| Chapter 6, “Work Management Considerations for Display Station Pass-
| Through” on page 6-1 for more information.
| If you want to disable pass-through for only specific remote locations, you will
| have to write a user program for the QRMTSIGN system value. This program
| can interrogate the source location name and allow or reject pass-through. See
| Chapter 6, “Work Management Considerations for Display Station Pass-
| Through” on page 6-1 for more information.

| Communications Entries To Route the Communications User Jobs: Since

| there is not a communications job, you cannot route it. The only time this may be of
| significance is if communications entries were used to group remote users to sepa-
| rate subsystems that enable the target system to shut down certain remote sites by
| ending their subsystem.
| Note: If you use work station entries in subsystem descriptions to route the jobs,
| you do not have to change anything.
| If you want to route the interactive jobs into the same subsystem, add work
| station entries to the subsystem description.
| Note: Make sure that the other interactive subsystems do not have any
| generic work station entries. The entries in the other subsystems will
| pick up the jobs from the specific subsystem when it ends.

| Using Status Displays

| You will see some minor differences to certain status displays when the system is
| running target display station pass-through servers.
| The Work with Configuration Status (WRKCFGSTS) display for APPC config-
| uration shows all the target pass-through sessions as using the same job
| name, QPASVRP QSYS nnnnnn. This is normal. See .A/ in Figure 2-1 on
| page 2-5.
| The Work with Active Job (WRKACTJOB) display does not show any target
| pass-through communications user jobs. The display shows the primary server
| job and any secondary server jobs (QPASVRS QSYS nnnnnn). These are the
| communications server jobs for pass-through that always exist in the
| QSYSWRK subsystem.

| You also have the option of running target pass-through like you have prior to
| V4R1 by setting the system value QPASTHRSVR to 0. IBM recommends that you
| use the communications servers for pass-through since eliminating the communi-
| cations jobs offers better performance on the system.

| Performance Considerations
| The pass-through server implementation provides a performance improvement due
| to the elimination of the pass-through communications user jobs on the AS/400.
| The number of server jobs will also have an effect on the performance of the PC
| bringup time when many PCs are powering on or off at the same time.

| You will have to determine the optimum value for your system by trial and error. It
| depends on the concurrent number of PCs and pass-through users, as well as

2-4 Remote Work Station Support V4R1

| à ð
| Work with Configuration Status WASHSYS
| ð3/17/97 17:38:3ð
| Position to . . . . . __________ Starting characters

| Type options, press Enter.

| 1=Vary on 2=Vary off 5=Work with job 8=Work with description
| 9=Display mode status ...

| Opt Description Status -------------Job--------------

| Figure 2-1. WRKCFGSTS Display for APPC Devices

| when they start and end. It also depends on the other activity on the system and
| how much you want to affect the system. If you use *CALC, you should see an
| improvement. Additional tuning of your system will be at your discretion.

| Use the Change System Value (CHGSYSVAL) command to change the value of
| the QPASTHRSVR system value.

Chapter 2. Using Server Jobs for Target Display Station Pass-Through 2-5
2-6 Remote Work Station Support V4R1
Chapter 3. Configure Display Station Pass-Through
This chapter provides information for configuring your AS/400 system, virtual con-
trollers, and attached devices for use in the display station pass-through function.

Before you can use display station pass-through, you must configure and activate
advanced program-to-program communications (APPC). You must configure and
activate APPC between the local, remote, and intermediate systems in the network.
APPC is data communications support that allows programs on an AS/400 system
to communicate with programs on other systems with compatible communications
support.

The display station used for the pass-through session can be locally or remotely
attached to an AS/400 system. The user can sign on to a remote System/36,
System/38, or AS/400 system using the AS/400 APPC, with or without the
Advanced Peer-to-Peer Networking (APPN) extensions, in an interactive environ-
ment. APPN support routes data in a network between two or more APPC systems
that do not need to be adjacent.

Both the target system and the source system contain information describing a
display station. However, the display station information contained in the target
system describes a display station directly attached to the source system, not the
target system.

The network joining the source system and the target system can consist of many
objects and configurations. Users can tailor their network to use the objects and
configurations that best suit their application.

Configuration of Virtual Controllers and Devices

Virtual devices are used by the target system to direct output to devices on the
source system. The virtual devices are attached to virtual controllers. You can
allow the system to automatically configure these devices and controllers for you,
you can configure them yourself, or you can do both.

Virtual Devices
Virtual devices are created with ONLINE(*NO) specified to improve IPL perform-
ance. When the device is used for the first time, pass-through will automatically
vary on the device.

Pass-through will not normally vary off the device when the pass-through session
ends. Therefore, the vary on delay is encountered only the first time the device is
used after IPL. Specify ONLINE(*YES) if you want your devices varied on at IPL.

Virtual display devices are not varied on at IPL time. The devices are varied on
when they are first used.

 Copyright IBM Corp. 1997 3-1

Automatic Configuration
When the source system requests pass-through support to automatically configure
a device, the target system examines each of the virtual devices on the virtual con-
troller named QPACTLnn. If a device is available, the target system program con-
figures that device to match your physical device. If the target pass-through
program cannot find an available virtual device, it checks the QAUTOVRT system
value. If creating another device makes the number of devices attached to the
QPACTLnn virtual controllers greater than the QAUTOVRT system value, another
device is not created. Instead, the program ends the pass-through session. If cre-
ating another device keeps the number of devices less than or equal to the
QAUTOVRT value, a device is created.

To allow automatic configuration, use the Change System Value (CHGSYSVAL)

command to set the QAUTOVRT system value to the maximum number of devices
that can be automatically configured by the program. Use a value less than the
maximum allowed value of 9999 to avoid performance problems. To allow the
normal activity of your users to determine the best value for QAUTOVRT, set
QAUTOVRT to 9999 temporarily, then decrease the value after creating the appro-
priate number of devices.

For example, if you have never allowed automatic configuration of virtual devices
on your system, the QAUTOVRT value is specified as 0. An automatic configuration
attempt fails because the display station pass-through function will not create more
than the specified QAUTOVRT (0) devices. If you change the QAUTOVRT value to
10, the next pass-through attempt that requests automatic configuration causes
pass-through to create a virtual device. This virtual device is created because the
number of virtual devices on the controller (0) is less than the number specified in
the QAUTOVRT (10). Even if you change the system value to 0 again, the next
user attempting pass-through succeeds if a virtual device exists that is not being
used. If a free virtual device does not exist, pass-through will not create a new
device because the number of devices currently existing is greater than or equal to
the specified QAUTOVRT value.
Note: The creation of virtual devices for the work station function of Client Access
is not limited by the QAUTOVRT system value. Virtual devices for the work
station function are created as needed regardless of the value of
QAUTOVRT or the number of virtual devices already created.

Automatic Configuration Considerations

Consider the following when using automatic configuration of virtual devices by
pass-through:
Virtual devices that are automatically configured are owned by the user profile
running the pass-through programs on the target system. Therefore, when
automatic sign-on is used, the virtual devices that are created are owned by the
user specified in the RMTUSER parameter of the STRPASTHR command.
Pass-through does not delete virtual devices, even if the number of these
devices attached to automatically configured virtual controllers exceeds the
QAUTOVRT limit.
If you specify a QAUTOVRT value less than the number of devices attached to
QPACTLnn controllers and want the extra devices deleted, delete them manu-
ally.

3-2 Remote Work Station Support V4R1

Pass-through allows a maximum value of 250 virtual devices on a QPACTLnn
controller before it creates another QPACTLnn controller. For example, pass-
through allows 250 virtual devices on the QPACTL01 controller before it
creates QPACTL02. If you delete devices to enforce a smaller QAUTOVRT
value, begin by deleting the devices from the controller with the highest
QPACTLnn value.
If you do not specify a virtual controller or a list of virtual devices when you
issue the STRPASTHR command, the pass-through function uses the special
virtual controller named QPACTL00 to request automatic configuration support
from the target system.
If the target system does not support automatic configuration, a user requesting
automatic configuration can still pass through. However, the target system
operator must create a virtual controller named QPACTL00 on the target
system, and the QPACTL00 controller must have an appropriate virtual device
attached.
You also can request automatic configuration on a target AS/400 system that
does not support automatic configuration by specifying QPACTL00 on the
virtual controller parameter. This is useful if your source system is a System/38
or using Operating System/400 (OS/400).
System/36 users do not need to enter a virtual controller name when passing
through to an AS/400 system if automatic configuration of virtual devices is
enabled.
Note: If you are using OS/400 Version 1 Release 2.0 or later, do not create a
controller named QPACTL00 because the automatic configuration of virtual
devices fails if QPACTL00 is specified on the virtual controller parameter.

If a virtual controller named QPACTL00 does exist on a system, users

requesting automatic configuration to that system by specifying QPACTL00
in the virtual controller parameter cannot use automatic configuration.
Instead, these users must work with virtual devices attached to the
QPACTL00 virtual controller.

Manual Configuration
Even if you prefer pass-through to configure virtual devices, you may still want to
configure virtual controllers and devices manually. For example, you may want to
create a virtual controller with enough virtual devices for your security officer and
yourself to assure that you always get a virtual device, even if the number of active,
automatically configured virtual devices has reached its limit. You may also want
more control over who passes through to your system.

If you manually configure virtual controllers and devices, remember that virtual con-
trollers are only a method of grouping virtual devices. You can create one virtual
controller for each virtual device, one for each department of users, or for whatever
type of grouping that suits your system needs. Each virtual device can be associ-
ated with only one session.

You can configure a maximum of 255 virtual display stations for each virtual con-
troller.

Use the Create Controller Description (Virtual Work Station) (CRTCTLVWS)

command to configure virtual controllers. Each virtual controller can have a

Chapter 3. Configure Display Station Pass-Through 3-3

maximum of 255 associated virtual devices. In the following example, a virtual con-
troller named PASSCTL1 is created. One virtual work station (VDSP1) is added to
the virtual controller when the controller is created. VDSP1 must have already been
created.
CRTCTLVWS CTLD(PASSCTL1)
DEV(VDSP1)
TEXT('Virtual controller for pass-through use')

Note: For virtual controller configuration on a System/38, use the Create Control
Unit Description (CRTCUD) command. For more information about config-
uring for a System/38, see the System/38 Environment Programming book.

The following must be considered during configuration:

When the virtual controller and associated virtual devices are varied on, the
devices go to a vary on pending state.
Remotely attached 3270 controllers and devices are supported by display
station pass-through. They must be configured as remote 3270 displays at the
source system and as virtual 5251 displays at the target system.

Matching Display Stations for Source and Target Systems

The virtual display stations of the target system should match the type and model
parameters with the physical display stations of the pass-through source system.
Table 3-1 shows how the virtual display stations of the target system are matched
to the physical display stations of the source system. One of the alternative virtual
display stations may be selected if the following are both true:

The virtual controller (VRTCTL) parameter or virtual display device (VRTDEV)

parameter was specified on the STRPASTHR command.
A virtual display station with the appropriate type and model is not available.

If neither the VRTCTL parameter nor the VRTDEV parameter was specified on the
STRPASTHR command, pass-through chooses a device description that is not in
use. Then, pass-through changes the free device description to match the physical
device.

Table 3-1 (Page 1 of 2). Physical and Virtual Display Stations of Source and Target Systems
Physical Display Stations at Virtual Display Stations at Target Alternative Virtual Display
Source System System Stations at Target System
3179 Model 2; 3197 Models C1, 3179 Model 2; 3197 Models C1, C2; 5251 Model 111
C2; 5292 Model 1; 3476 Model EC 5292 Model 1; 3476 Model EC
3180 Model 2; 3197 Models D1, 3180 Model 2; 3197 Models D1, D2, 5251 Model 112
D2, W1, W2 W1, W2
3196 Models A1, A2, B1, B2; 3476 3196 Models A1, A2, B1, B2; 3476 5251 Model 11
Model EA Model EA
3277, 3278, or 3279 5251 Model 11 5251 Model 11
3477 Models FA, FD, FE, FG, FW 3477 Models FA, FD, FE, FG, FW 3180 Model 2 or equivalent
3477 Model FC 3477 Model FC 3477 Model FA or equivalent1
3486 Model BA 3486 Model BA 3196 Model A1 or equivalent3
3487 Models HA, HG, HW 3487 Models HA, HG, HW 5251 Model 11

3-4 Remote Work Station Support V4R1

Table 3-1 (Page 2 of 2). Physical and Virtual Display Stations of Source and Target Systems
Physical Display Stations at Virtual Display Stations at Target Alternative Virtual Display
Source System System Stations at Target System
3487 Model HC 3487 Model HC 3487 Model HA or equivalent1
5251 Model 11 5251 Model 11 NA
5291 Model 1, 2 5291 Model 1, 2 5251 Model 11
5292 Model 2 5292 Model 2 5251 Model 114
5555 Models B01, E01 5555 Models B01, E01 NA
5555 Model C01, F01 5555 Model C01, F01 5555 Model B015 or equivalent1
5555 Model G01 5555 Model G01 5555 Model B01 or equivalent6
5555 Model G02 5555 Model G02 5555 Model G01 or equivalent1
1 If this alternative virtual display station is used at the target system, the display station user has no
color capability during the pass-through session.
2 If this alternative virtual display station is used at the target system, the display station user has no
wide screen capability during the pass-through session.
3 If this alternative virtual display station is used at the target system, the display station user has no
extended character buffer or extended 5250 data stream during the pass-through session.
4 If this alternative virtual display station is used at the target system, the display station user has no
color or graphics capabilities during the pass-through session.
5 If the 5555 Model C01 is using software from Version 1 Release 3, Modification 0 or earlier, the Model
C01 will be viewed as a Model B01.
6 If this alternative virtual display station is used at the target system, the display station user has no
graphics capabilities during the pass-through session.

Using Personal Computers for Display Stations

Personal computers that function as display stations on AS/400 systems also have
virtual device descriptions. These device descriptions specify the type and model of
the physical device being emulated by the personal computers. Use the Display
Device Description (DSPDEVD) command to view these descriptions.
Note: Virtual printer device descriptions are supported on the AS/400 system, but
the device description is only used for supporting the printer session of the
work station function for Client Access.

Using Utilities during Pass-Through

To use certain utilities (such as 3270 device emulation) during pass-through, the
keyboard language type (KBDTYPE) parameters at the source and target systems
must match. The KBDTYPE parameter is part of the display device description.

The United States basic keyboard type KBDTYPE(USB) is used in the following
examples.

If you have a 5251 Display Station Model 11 attached to your source system, use
the following command at the target system to configure an appropriate virtual work
station:
CRTDEVDSP DEVD(VIRTDSP1) DEVCLS(\VRT) TYPE(5251) MODEL(ðð11)
ONLINE(\YES) CTL(PASSCTL1) KBDTYPE(USB)
TEXT('Example virtual display station')

Chapter 3. Configure Display Station Pass-Through 3-5

If you have a 5292 Color Graphics Display Station Model 2 attached to your source
system, you can use the following command from the target system:

CRTDEVDSP DEVD(VIRTDSP2) DEVCLS(\VRT) TYPE(5292) MODEL(ððð2)

ONLINE(\YES) CTL(PASSCTL1) KBDTYPE(USB)
TEXT('Example virtual display station')

Determine the number of physical display stations that will be active at the same
time with the same target system. This is the number of virtual display stations of
each type that you must configure at the target system. For example, if two 5251
Display Station Model 11s will do pass-through to a single target system, then the
target system must have two virtual display stations configured as 5251 Model 11.
These virtual display stations must have different names in the DEVD parameter.
Note: For virtual display configuration on a System/38, use the Create Device
Description (CRTDEVD) command.

TELNET Automatic Configuration

The AS/400 system supports the TELNET Transmission Control Protocol/Internet
Protocol (TCP/IP) application. TCP/IP is a set of vendor-independent communi-
cations protocols that support peer-to-peer connectivity functions for both local and
wide area networks. TELNET is similar to pass-through but runs on a TCP/IP
network rather than an APPC network. TELNET uses virtual devices to direct
output to the local devices just as pass-through does.

When using TELNET, the AS/400 system creates virtual devices automatically in
the same way that it does for pass-through unless you use network virtual termi-
nals. Therefore, the QAUTOVRT system value controls the number of automatically
configured virtual devices for both TELNET and pass-through.

With the QAUTOVRT system value, you can attach the source AS/400 system to a
target AS/400 system using pass-through or TELNET.

For more information about TELNET, see the TCP/IP Configuration and Reference
book.

Security Considerations for Virtual Controllers and Devices

If you allow automatic configuration of virtual devices, it is easier for users to
attempt to break in by using pass-through. Without automatic configuration, a user
attempting to break in has a limited number of attempts to sign on at each virtual
device. This limit is defined by the security officer using the QMAXSIGN system
value and by the number of devices available. With automatic configuration active,
the actual limit increases because the system limit for sign-on operations that are
not valid is multiplied by the number of virtual devices that can be created by the
automatic configuration support defined by the QAUTOVRT system value. For infor-
mation about restricting remote sign-on capability, see “Control of Remote Sessions
from Other Systems” on page 6-1.

3-6 Remote Work Station Support V4R1

Creating User Profiles
At the target system, create one or more user profiles for pass-through users from
other systems. These user profiles should only have authority appropriate to the
function being performed by each user. The following is an example user profile:
CRTUSRPRF USRPRF(CLERK1) PASSWORD(unique-password)
JOBD(CLERKLIB/CLERKL1)
TEXT('User profile for one group of clerks')

Note: You must create the user profiles of all System/36 users who pass through
to your AS/400 system if your AS/400 system is the target system in a
System/36 pass-through operation, and if you specify SECURELOC(*YES)
in your APPC device description or SECURELOC (*YES) in the APPN
remote location list entry. The System/36 Pass-Through (PASSTHRU) pro-
cedure fails if you try to pass through from a System/36 using a user profile
name that is not created on the AS/400 system and if your AS/400 devices
and locations are specified as SECURELOC(*YES).

For more information about APPC and APPN security, see the APPC Programming
book and the Communications Configuration book.

When the AS/400 system is shipped, a subsystem called QBASE is provided that
contains all the work station entries, job descriptions, default user profiles, commu-
nications entries, and routing entries (entries in a subsystem descriptions that
specify the program to be called to control a routing step) necessary for pass-
through. Another subsystem called QCMN contains only the communications
entries and routing entries necessary for pass-through.

To use pass-through, the subsystem (either QBASE or QCMN) that owns the work
station entries used by pass-through must be active.

If you want to configure how your subsystems are accessed by pass-through, follow
the steps shown in the Backup and Recovery book. These steps are not necessary
if you do not change your subsystems on your AS/400 system.

Chapter 3. Configure Display Station Pass-Through 3-7

3-8 Remote Work Station Support V4R1
Chapter 4. Starting and Using a Display Station
Pass-Through Session
This chapter discusses the details about starting and using a pass-through session.

Choosing the Target System

You can specify a target system for the pass-through session in one of the fol-
lowing ways, depending on the configuration of your system. For all of the fol-
lowing, you specify the target system as part of the Start Pass-Through
(STRPASTHR) command.
Specify a remote location name for the remote location (RMTLOCNAME)
parameter. This means pass-through uses APPN support to determine the
entire route through the network to the target system.
Specify a list of nonnetworking APPC devices that describe some or all of the
route to the target system.
Specify a remote location name and a list of nonnetworking APPC devices.
Pass-through uses APPN support to find a route to the system containing the
specified remote location name. That system is then used as the first system to
do pass-through routing. The list of nonnetworking devices specifies the
remaining route to the target system.

The method you choose depends on how your system’s communications

descriptions are defined. To learn more about the capabilities and configuration of
APPN functions, see the APPN Support book.

The Remote Location Name

The remote location name is the name of a location defined at the target system of
the pass-through session. The remote location name could be defined on the target
system in one of the following places:
APPN configuration list (local location list)
Default local location name
Local control point name

Use the Work with Configuration List (WRKCFGL) and the Display Network Attri-
butes (DSPNETA) commands while on the target system to determine which
location names are defined on that system.

You can also determine the local location names defined on the target system by
issuing the following command on the target system:
DSPAPPNINF \LCLNODE

APPN support chooses an appropriate route for your pass-through session if the
following conditions are met:
The specified remote location name is defined in the network.
An APPN route exists from the source system to the target system that con-
tains the location name.

 Copyright IBM Corp. 1997 4-1

For example, you can use the RMTLOCNAME parameter to pass through to a
system directly connected to your AS/400 system without intermediate systems in
the route. If you specify a location name that is the remote location name in one of
the devices associated with the line, pass-through can establish a session using
that line, even if the line connecting your AS/400 system to the target system is
configured with a controller and devices that are specified as APPN(*NO).

RMTLOCNAME is a required parameter. If the entire route from the source system
to the target system consists of systems using APPN support, RMTLOCNAME is
the only necessary parameter.

RMTLOCNAME values are:

location-name A location on the target system.
*CNNDEV Use the APPC device (CNNDEV) parameter to specify APPC devices if
any system en route to the target system requires pass-through to select
the route. APPN routing procedures are not used for this. If you specify
RMTLOCNAME(*CNNDEV), the system uses the first mode name speci-
fied for each APPC device on the CNNDEV parameter. For more infor-
mation about the CNNDEV parameter, see “The Connection Device” on
page 4-5.

Remote Location Name Scenario

Figure 4-1 on page 4-3 shows how the RMTLOCNAME parameter is used. All five
systems shown in the network have the following assumed characteristics:
All are configured as APPN network nodes.
All determine the route between any two locations in the network by using the
current network configuration.
All define one or more local locations that are represented by the smaller boxes
inside the system boxes. These location names can be used to specify the
target system in the RMTLOCNAME parameter.

4-2 Remote Work Station Support V4R1

System A System B System C
┌───────────────┐ ┌────────┐ ┌────────┐
│┌──────┐┌─────┐│ ┌───┤┌──────┐│ ┌───┤┌──────┐│
││ SYSA ││SYSA1│├────┘ ││ SYSB │├────┘ ││ SYSC ││
│└──────┘└─────┘│ │└──────┘│ │└──────┘│
└───────────────┘ └──┬─────┘ └───┬────┘
│ │
└─┐ └─┐
│ │
┌────────┴──────────────────┴┐
│ ┌───────┐┌───────┐┌───────┐│
System D │ │ SYSD ││ LOCD ││ LOCD1 ││
│ └───────┘└───────┘└───────┘│
└────┬───────┬───────────────┘
│ │
└─┐ └─┐
│ │
┌──┴───────┴┐
│┌─────────┐│
System E ││ SYSE ││
│└─────────┘│
└───────────┘

Figure 4-1. Networking Example for Location Names

If you are signed on to System A in Figure 4-1 and you want to use pass-through
to sign on to System B, you must specify STRPASTHR RMTLOCNAME(SYSB)
because the only location on System B is SYSB. In this example, only one route is
available from System A to System B. If this route satisfies the class of service,
APPN support chooses this route. Class of service is the link and node character-
istics that determine the quality of the route selected for the sessions. For more
information about class of service, see the Communications Configuration book or
the APPN Support book.

However, if you want to sign on to System D from System A, there are three local
location names on that system. The value you specify for the RMTLOCNAME
parameter can be SYSD, LOCD, or LOCD1. The current traffic in the network, the
status of the links, and the class of service specified determine the route chosen by
APPN support.

If you pass through to System E, APPN support determines which of the two com-
munications lines connecting System D and System E to use. The line APPN
support chooses depends on the state of the network when you issue the
STRPASTHR command. For example, APPN support considers such factors as the
speed of the communications lines and the relative cost of using those lines.

Three other parameters (mode, local location name, and remote network identifier)
are used only when the remote location name is specified. These parameters are
used by APPN support to determine the route of the pass-through session.

Chapter 4. Starting and Using a Display Station Pass-Through Session 4-3

The Mode
A mode describes the attributes of a group of APPC sessions. Before beginning a
conversation between the source and target systems, pass-through must know the
mode under which the conversation runs.

The MODE parameter allows you to specify the communications mode that must be
used when the pass-through session is established. The MODE parameter appears
only if RMTLOCNAME(*CNNDEV) is not specified.

If you specify a location name for the RMTLOCNAME parameter on the Start Pass-
Through (STRPASTHR) command, you can also specify a mode name. If you do
not specify a mode, pass-through attempts to use the system default mode defined
in the network attributes.

When specifying a mode, you can choose one of the IBM-supplied modes, or you
can choose a mode that you create by using the Create Mode Description
(CRTMODD) command to define enough sessions and conversations to allow all
users of that mode to run at the same time. For example, you can create a mode
that can be used by 10 pass-through users at one time by specifying MAXSSN(10)
and MAXCNV(10) on the CRTMODD command.

For example, in Figure 4-1 on page 4-3, if you pass through from SYSA to SYSE,
a mode on SYSE must match the mode you specify for the MODE parameter on
system A.

MODE values are:

*NETATR The default mode name specified in the network attributes. To display or
change this value, use the Display Network Attributes (DSPNETA)
command or the Change Network Attributes (CHGNETA) command.
This is the default value.
mode-name The name of a mode created with the Create Mode Description
(CRTMODD) command or provided with the system.
Note: If you specify RMTLOCNAME(*CNNDEV), the system uses the first mode
name specified for each APPC device on the APPC device (CNNDEV)
parameter. You cannot specify a mode. For example, in Figure 4-2 on
page 4-7, the mode used between System B and System A is the first
mode of the list of modes associated with the APPC D4 device on System
B. You must be certain that the mode that appears first on each APPC
device has a matching mode on the next system in the route to the target
system.

You can use the Display Device Description (DSPDEVD) command to display the
first mode listed for each device.

The Local Location Name

The local location (LCLLOCNAME) parameter is the name of a location defined at
the source system. You can specify any of the local location names defined on your
system. This parameter specifies the location of the source of the pass-through
session.

For example, to start a pass-through session on System A in Figure 4-1 on

page 4-3, specify LCLLOCNAME(*NETATR). If the default local location name is

4-4 Remote Work Station Support V4R1

SYSA, APPN support tries to establish a session using SYSA as the source
system. If the maximum number of sessions between SYSA and the remote
location is already running, the STRPASTHR command fails. However, you can
issue the STRPASTHR command with LCLLOCNAME(SYSA1) because sessions
may be available from SYSA1 to the location on the target system.

LCLLOCNAME values are:

*LOC The system selects the local location name. This is the default value.
*NETATR The default local location name specified in the network attributes. To
display or change this value, use the DSPNETA command or the
CHGNETA command.
location-name A location name on the source system. To determine which location
names are defined, use one of the following commands on the source
system:
Work with Configuration Lists (WRKCFGL)
Display Network Attributes (DSPNETA)
Display APPN Information (DSPAPPNINF)

The Remote Network Identifier

The remote network identifier (RMTNETID) parameter allows you to specify the
network that contains the target remote location. The RMTNETID parameter allows
you to pass through to a system on another APPN network that is connected to
your local network by using a system with APPN cross-network routing capability.
AS/400 system network nodes have this cross-network routing capability. For more
information on APPN cross-network routing, see the information on multiple network
connectivity in the APPN Support book.

RMTNETID values are:

*LOC The system selects the network ID. This is the default value.
*NETATR The remote location exists in the same network as the source system.
Use the DSPNETA command to determine the network ID.
*NONE The remote location does not support network identifiers.
remote-network-ID The network identifier of the remote network.

For more information about the basic concepts of the RMTLOCNAME, RMTNETID,
MODE, and LCLLOCNAME parameters, see the Communications Configuration
book. For more information about system association of these parameters with spe-
cific communications links, see the APPC Programming book.

The Connection Device

If your network consists of System/38 or AS/400 systems without APPN support
configured, use the APPC device (CNNDEV) parameter. Use this parameter to
specify the names of the APPC device descriptions that connect the systems in
your network. If you specifically choose some or all of the route from your source
system to the target system, you must know the name of the connection devices
on the route between the source system and the target system. APPC connection
devices are objects in a System/38 and an AS/400 system, each of which repres-

Chapter 4. Starting and Using a Display Station Pass-Through Session 4-5

ents a data link between systems. If you did not create these devices, ask the
system administrator or the user who created the devices for the correct names.

If you type \CNNDEV for the RMTLOCNAME parameter and press the Enter key, the
following parameters are displayed:

à ð
Start Pass-Through (STRPASTHR)

Type choices, press Enter.

Remote location . . . . . . . .> \CNNDEV_ Name, \CNNDEV

APPC device . . . . . . . . . . \LOC_______ Name, \LOC
+ for more values ___________
Virtual controller . . . . . . . \NONE______ Name, \NONE
Virtual display device . . . . . \NONE______ Name, \NONE
+ for more values ___________
System request program . . . . . \SRQMNU____ Name, \SRQMNU
Library . . . . . . . . . . . __________ Name, \LIBL, \CURLIB

The APPC device (CNNDEV) parameter accepts up to 16 names. These names

are used as names of APPC devices on the intermediate systems.

An intermediate system is a system through which a connection is made when a

direct route is not available for pass-through. When the CNNDEV parameter is
used, each intermediate system in which display station pass-through performs the
networking functions has a pass-through job for each pass-through session. The
display station pass-through job passes the data between adjacent systems. Inter-
mediate systems do not need virtual device descriptions.

If you specify a location name on the RMTLOCNAME parameter and omit the
CNNDEV parameter, all systems in the pass-through route must use APPN
support. Because APPN support routes the data through, pass-through jobs do not
exist on the intermediate systems.
Note: Only devices, not locations, can be used in the CNNDEV parameter. If
locations are used, the intermediate system attempting to use the location
as a device name ends the pass-through attempt because the device name
does not exist. To arrive at the target system, these APPC device names
must be listed in the order in which the intermediate systems are passed
through.

At any point in the route to the target system, one or more of the intermediate
systems can use its APPN routing capability to choose part of the route, depending
on how your network is configured. (For more information on configuring an APPN
network, see Figure 7-1 on page 7-11 and Figure 8-9 on page 8-14.)

When you specify a remote location name, you can specify connection devices for
additional routing purposes by using the APPC device (CNNDEV) parameter. This
parameter does not appear on the initial Start Pass-Through display. However, you
can view all of the parameters used by STRPASTHR, including CNNDEV, by
pressing F9 (All parameters). For more information about combining
RMTLOCNAME and CNNDEV parameters, see “Specifying Remote Location Name
and Connection Device Together” on page 4-8.

4-6 Remote Work Station Support V4R1

If the entire route to the target system consists of systems using APPN networking,
you do not need to specify the APPC device (CNNDEV) parameter. You can use
the default value (*LOC) for the APPC device (CNNDEV) parameter and specify the
target system using the RMTLOCNAME parameter.

Connection Device Scenario

In the configuration represented by Figure 4-2, there are four systems. System A
and System B may be either a System/38 or an AS/400 system for which the
APPC configuration is not configured to use APPN support.

System A
┌────────────┐
│ ┌──┐ │
┌────┤ │D2│ │
┌──┘ │ └──┘ │
┌────────────┐ │ │ ┌──┐ │
│ ┌──┐│ │ │ │D1│ │
│ │D1│├────┘ │ └──┘ │
│ └──┘│ └────────┬───┘
│AS/4ðð │ │
│System │ ┌─┘
│ ┌──┐│ │System B System/36
│ │D2│├────┐ ┌──────┴─────┐ ┌──────┐
│ └──┘│ │ │ ┌──┐ │ │ │
└────────────┘ │ │ │D4│ │ ┌───┤ │
└─┐ │┌──┐ └──┘ │ │ │ │
│ ││D3│ ┌──┐ ├────┘ │ │
└─────┤└──┘ │D5│ │ └──────┘
│ └──┘ │
└────────────┘
Figure 4-2. Networking Using CNNDEV

Three of the systems in this example contain objects describing the connection
between the system on which the object exists, and the system at the other end of
the connection. For example, D4 describes the connection between System B and
System A. These objects are the connection devices in the discussion of the
remote location name parameter. The connection devices must be nonnetworking
devices or you cannot specify your own route to the target system. For this
example, assume the names of the devices are the values shown inside each of
the small boxes. For example, System A has two devices, D1 and D2.

Notice that the names of the connection devices do not have to be unique
throughout the network, but they must be unique in a system. Also, notice the
System/36 does not have connection devices.

If you are signed on to a display station attached to the source system and you
want to pass through to System A, two routes are possible. Because D1 connects
the source system to System A, you can pass through directly to System A by
specifying:
STRPASTHR RMTLOCNAME(\CNNDEV) CNNDEV(D1)

The alternative is to specify CNNDEV (D2 D4) because D2 on the source system
connects to System B, and D4 on system B connects to System A. System B is an
intermediate system in this example.
Note: You may also use the RMTLOCNAME parameter to establish the pass-
through route. For example, if device D1 was created with the value SYSA

Chapter 4. Starting and Using a Display Station Pass-Through Session 4-7

(see Figure 4-1 on page 4-3) as its remote location name and if no other
devices use that remote location name, the following two commands
perform the same function:
STRPASTHR RMTLOCNAME(\CNNDEV) CNNDEV(D1)

STRPASTHR RMTLOCNAME(SYSA)

To pass through from the source system to the System/36, you can specify either
CNNDEV (D2 D5) or CNNDEV (D1 D1 D5). Notice the connection devices are
specified in a sequence beginning with the device on the source system and ending
with the device that connects to the target system. Both choices require at least
one intermediate system because a direct link does not exist between the source
system and the System/36.
Note: You can pass through from the source system to the System/36 by speci-
fying only a remote location name if the System/36 is configured as a low-
entry networking node and System B is configured as a network node.
(Low-entry networking nodes use the logical unit (LU) 6.2 node type 2.1
architecture without the APPN extension.)

The Communications Configuration book also contains information about location

names and networking. All devices specified on the CNNDEV parameter must be
varied on before you enter the STRPASTHR command. CNNDEV values are:
*LOC No connection devices are specified. Use the location name specified
with the remote location name parameter. This is the default value.
connection-device The name of the connection device or devices.

Specifying Remote Location Name and Connection Device Together

You can specify the APPC device (CNNDEV) parameter as an additional parameter
when you specify RMTLOCNAME. This allows you to use APPN support as far
through the network as possible. Then you can use pass-through routing through
more than one system to complete the path.

Refer to Figure 4-2 on page 4-7 for an example network where this routing can be
used. You can specify RMTLOCNAME(SYSA) with CNNDEV(D1 D5) or
RMTLOCNAME(SYSB) with CNNDEV(D5) to pass through from the source system
to the System/36. When you use the RMTLOCNAME and CNNDEV parameters in
this way, RMTLOCNAME does not identify the target system; it identifies the
system containing the first device in the CNNDEV device list.

To specify a remote location name and a connection device name together, type in
the remote location name on the Start Pass-Through display and press F9.

4-8 Remote Work Station Support V4R1

à ð
Start Pass-Through (STRPASTHR)

Type choices, press Enter.

Remote location . . . . . . . . > SYSB____ Name, \CNNDEV

APPC device . . . . . . . . . . > D5________ Name, \LOC
+ for more values __________
Virtual controller . . . . . . . \NONE_____ Name, \NONE
Virtual display device . . . . . \NONE_____ Name, \NONE
+ for more values __________
Mode . . . . . . . . . . . . . . \NETATR___ Name, \NETATR
Local location . . . . . . . . . \LOC______ Name, \LOC, \NETATR
Remote network identifier . . . \LOC______ Name, \LOC, \NETATR, \NONE
System request program . . . . . \SRQMNU___ Name, \SRQMNU
Library . . . . . . . . . . . __________ Name, \LIBL, \CURLIB

Additional Parameters

User profile . . . . . . . . . . \NONE_____ Name, \NONE, \CURRENT

User password . . . . . . . . . \NONE_____ Name, \NONE
More...
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

á ñ

Specifying Virtual Controllers and Virtual Devices

A virtual device description provides information about your physical display station
to the programs on the target system, just as the physical device description on
your source system provides information about your physical display station to the
programs on the source system.

When you specify the STRPASTHR command, the pass-through support on the
target system attempts to find a virtual device on the target system with a device
type and model similar to the device description on the source system. Use the
virtual controller (VRTCTL) parameter or the virtual display device (VRTDEV)
parameter if you want to indicate to the target system which device to use.

Requesting Automatic Configuration

To request that the target system automatically set up a virtual device, use the
default value (*NONE) for the VRTCTL and VRTDEV parameters.

If the target system does not allow automatic configuration of virtual devices, or if
you want to be more selective about which virtual device to use, you can use the
VRTCTL or the VRTDEV parameter.

Virtual Controller (VRTCTL) Parameter

The virtual controller parameter is the name of the virtual controller on the target
AS/400 system or System/38. During configuration on the System/38 and AS/400
system, virtual devices are grouped under virtual controllers. You can enter the
name of the virtual controller in the VRTCTL parameter. The target pass-through
support chooses the first available virtual device attached to that virtual controller
that has the appropriate type and model values.

To determine which virtual device types and models are appropriate for the physical
device types and models, see Table 3-1 on page 3-4. If you did not create these

Chapter 4. Starting and Using a Display Station Pass-Through Session 4-9

device names, ask the system administrator or the user who created these names
for the correct values. If your target system is a System/36, you can use the default
value for the VRTCTL parameter because virtual controllers do not exist on the
System/36. If you specify a value for this parameter, the target System/36 ignores
the value.

VRTCTL values are:

*NONE The VRTDEV parameter specifies the virtual device descriptions to
choose from. If this value is specified when the VRTDEV parameter is
*NONE, you are requesting pass-through to automatically configure a
virtual device for you. VRTCTL(*NONE) must be specified when the
VRTDEV parameter specifies a list of virtual device names. If no value
is specified for the VRTCTL parameter, the system defaults to *NONE.
virtual-controller-name The name of the virtual controller that exists on the target
system. For more information about virtual controllers, see “Configura-
tion of Virtual Controllers and Devices” on page 3-1.

Virtual Display Device (VRTDEV) Parameter

The virtual device list shows from 1 to 32 virtual device names on the target
AS/400 system or System/38. Use the VRTDEV parameter to specify this list. The
first available device listed with the appropriate type and model values is chosen.

To determine the virtual device types and models that are appropriate for the phys-
ical device types and models, see Table 3-1 on page 3-4.

Because System/36 does not have virtual devices, use the default value of the
VRTDEV parameter if your target system is a System/36. If you specify a value for
this parameter, the target System/36 ignores it.

VRTDEV values are:

*NONE The VRTCTL parameter specifies the virtual device descriptions to
choose from. If this value is specified when the VRTCTL parameter is
*NONE, you request pass-through to automatically configure a virtual
device for you. VRTDEV(*NONE) must be specified when the VRTCTL
parameter specifies a virtual controller name. If no value is specified for
the VRTDEV parameter, the system defaults to *NONE.
virtual-device-names The names of up to 32 virtual devices. If more than one virtual
device is listed, the first available virtual device that matches the type
and model of the physical device is chosen.

For more information about the virtual devices, see “Manual Configuration” on
page 3-3.

4-10 Remote Work Station Support V4R1

Chapter 5. Going Back and Forth between Systems
You can use pass-through functions to go back and forth between systems. This
chapter has an example of using pass-through to go back and forth between
systems. It also discusses the Transfer Pass-Through (TFRPASTHR) command
and the System Request options.

The example shows three systems with default local location names of Tokyo,
Chicago, and Geneva. All the necessary configuration has been done. The fol-
lowing commands and menu are used to go back and forth between the three
systems:
Start Pass-Through (STRPASTHR) command
Transfer Pass-Through (TFRPASTHR) command
End Pass-Through (ENDPASTHR) command
Sign Off (SIGNOFF) command
System Request menu

Number Diagram Description

1 Pass through from Tokyo to Chicago using
┌──────┐ ┌───────┐ the STRPASTHR command.
│Tokyo ├──────────5Chicago│
└──────┘ └───────┘
STRPASTHR CHICAGO
2 ┌──────┐ ┌───────┐ Return to the System Request menu at
│Tokyo %──────────┤Chicago│ Tokyo after passing through from Tokyo to
└──────┘ └───────┘
System Request TFRPASTHR TOJOB(\SRC) Chicago (which is shown in number 1).
menu or Any of the four methods shown can be
TFRPASTHR TOJOB(\HOME) used.
or
System Request option 1ð
or
System Request option 13

3 ┌──────┐ ┌───────┐ Go back to Chicago again after number 2

│Tokyo ├──────────5Chicago│ by pressing F3 on the System Request
└──────┘ └───────┘
System Request menu F3 menu or by using System Request option
or 15.
System Request option 15

4 ┌──────┐ ┌───────┐ Go to the alternate job at Tokyo after

│Tokyo %──────────┤Chicago│ number 1 or number 3. Any of the four
└──────┘ └───────┘
Alternate TFRPASTHR TOJOB(\ALT) methods shown can be used.
job or
TFRPASTHR TOJOB(\HOMEALT)
or
System Request option 11
or
System Request option 14

 Copyright IBM Corp. 1997 5-1

Number Diagram Description
5 ┌──────┐ ┌───────┐ Go back to Chicago again after number 4.
│Tokyo ├──────────5Chicago│ Any of the three methods shown can be
└──────┘ └───────┘
Alternate job used from the alternate job at Tokyo.
SIGNOFF
or
TFRSECJOB
or
System Request option 1

6 ┌──────┐ ┌───────┐ ┌───────┐ Pass through from Chicago to Geneva by

│Tokyo ├─ ─ ─5Chicago├──────5Geneva │ using the STRPASTHR command after
└──────┘ └───────┘ └───────┘
STRPASTHR GENEVA passing through from Tokyo to Chicago
(shown in numbers 1, 3, and 5).
7 ┌──────┐ ┌───────┐ ┌───────┐ Return to the Tokyo System Request
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ menu from Geneva after number 6 by
└───&──┘ └───────┘ └───┬───┘
└──────────────────────────┘ using either the TFRPASTHR command or
System TFRPASTHR TOJOB(\HOME) System Request option 13.
Request or
menu System Request option 13
8 ┌──────┐ ┌───────┐ ┌───────┐ Return to Geneva after number 7 by using
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ either F3 or System Request option 15.
└─┬─&──┘ └───────┘ └───┬─&─┘
│ └ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ │
└──────────────────────────────┘
System Request menu F3
or
System Request option 15
9 ┌──────┐ ┌───────┐ ┌───────┐ Return to the alternate job on Tokyo from
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ Geneva after number 6 or number 8 by
└───&──┘ └───────┘ └───┬───┘
└──────────────────────────┘ using either the TFRPASTHR command or
Alternate TFRPASTHR TOJOB(\HOMEALT) System Request option 14.
job or
System Request option 14
10 ┌──────┐ ┌───────┐ ┌───────┐ Return to Geneva after number 9. Any of
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ the three methods shown can be used
└─┬─&──┘ └───────┘ └───┬─&─┘
│ └ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─┘ │ from the alternate job at Tokyo.
└──────────────────────────────┘
Alternate job
SIGNOFF
or
TFRSECJOB
or
System Request option 1
11 ┌──────┐ ┌───────┐ ┌───────┐ Return to the Chicago System Request
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ menu from Geneva after numbers 6, 8, or
└──────┘ └────&──┘ └───┬───┘
└────────────┘ 10 by using either the TFRPASTHR
System TFRPASTHR TOJOB(\SRC) command or System Request option 10.
Request or
menu System Request option 1ð
12 ┌──────┐ ┌───────┐ ┌───────┐ Return to Geneva after number 11 by
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ using either F3 or System Request option
└──────┘ └──┬─&──┘ └───┬─&─┘
│ └ ─ ─ ─ ─ ─ ─┘ │ 15.
└────────────────┘
System Request menu F3
or
System Request option 15

5-2 Remote Work Station Support V4R1

Number Diagram Description
13 ┌──────┐ ┌───────┐ ┌───────┐ Return to the alternate job on Chicago
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ from Geneva after numbers 6, 8, 10, or 12
└──────┘ └────&──┘ └───┬───┘
└────────────┘ by using the TFRPASTHR command or
Alternate TFRPASTHR TOJOB(\ALT) System Request option 11.
job or
System Request option 11
14 ┌──────┐ ┌───────┐ ┌───────┐ Return to Geneva after number 13. Any of
│Tokyo ├─ ─ ─5Chicago├─ ─ ─5Geneva │ the three methods shown can be used
└──────┘ └──┬─&──┘ └───┬─&─┘
│ └ ─ ─ ─ ─ ─ ─┘ │ from the alternate job at Chicago.
└────────────────┘
Alternate job
SIGNOFF
or
TFRSECJOB
or
System Request option 1
15 ┌──────┐ ┌───────┐ ┌───────┐ End the job on Geneva and return to
│Tokyo ├─ ─ ─5Chicago%─────┤Geneva │ Chicago by using either the SIGNOFF
└──────┘ └───────┘ └───────┘
SIGNOFF ENDCNN(\YES) command or ENDPASTHR command.
or
ENDPASTHR

16 ┌──────┐ ┌───────┐ End the job on Chicago and return to

│Tokyo %─────┤Chicago│ Tokyo by using either the SIGNOFF
└──────┘ └───────┘
SIGNOFF ENDCNN(\YES) command or ENDPASTHR command.
or
ENDPASTHR

Notes:
In this example, the system request program (SRQ10PGM) parameter is
always allowed to be the default. Therefore, the System Request menu is dis-
played at the previous system after System Request option 10 is used.
To use the System Request options, use the System Request menu or the
System Request entry line.
– To use the System Request menu:
1. Press the System Request key.
2. Press the Enter key.
3. Enter the number of the option on the System Request menu.
– To use the System Request entry line:
1. Press the System Request key.
2. Type the option number on the System Request entry line.
3. Press the Enter key.
The pass-through function has no built-in limit to the number of systems you
can sign on by passing through from system to system.
You can mix pass-through and TELNET sessions. For example, you can go
from Tokyo to Chicago using pass-through and from Chicago to Geneva using
TELNET.

Chapter 5. Going Back and Forth between Systems 5-3

You can use the TFRPASTHR command only at a pass-through target system.
You cannot use it at a TELNET server system.
For more information about TELNET, see the TCP/IP Configuration and Refer-
ence book.
You can use the Transfer Secondary Job (TFRSECJOB) command to transfer
from an alternate job at a source system to the original job. Because the ori-
ginal job is running display station pass-through, you end up at the target
system. In number 5 of the example on page 5-2, the TFRSECJOB command
transfers you to your original job at Tokyo. Because your original job at Tokyo
is still running display station pass-through, you end up at Chicago.
You can have only one pass-through or TELNET session per job.
The system where you first use pass-through or TELNET is called the home
system as shown in Figure 5-1. The home system may be either a pass-
through source system or a TELNET client system.
The last pass-through target system or the last TELNET server system is called
the end system (see Figure 5-1).

Home System ┌─────────────────┐

│ │
│ System A │
│ │
└────────┬────────┘
Pass-through│
or TELNET │
┌───────6────────┐
│ │
│ System B │
│ │
└───────│────────┘
Pass-through│
Intermediate or TELNET │
Systems │
┌───────6────────┐
│ │
│ System C │
│ │
└───────│────────┘
Pass-through│
or TELNET │
6
End System ┌─────────────────┐
│ │
│ System D │
│ │
└─────────────────┘

Figure 5-1. Pass-Through and TELNET Home System and End System

The home system intercepts System Request options 13 and 14 when 13 or 14

is entered on the System Request entry line. This function may be helpful if you
pass through to a system to which you cannot sign on. You can end pass-
through to that system by doing the following:
1. Press the System Request key.

5-4 Remote Work Station Support V4R1

2. Enter 13 on the System Request entry line.
3. Enter 2 on the System Request menu.
All pass-through and TELNET sessions are stopped and you return to the
home system.
For pass-through, the home system and intermediate systems must be running
OS/400 Version 2 Release 3 or later. In Figure 5-1 on page 5-4, for example,
System A, System B, and System C must all be running OS/400 Version 2
Release 3 or later.
To pass through from an end system to another system, the end system must
be running OS/400 Version 2 Release 3 or later. For example, if System D in
Figure 5-1 is running OS/400 Version 2 Release 2 or earlier, you cannot pass
through from it.
To use System Request options 13, 14, and 15; the system must be running
OS/400 Version 2 Release 3 or later. System Request options 10 and 11 func-
tion differently on systems prior to OS/400 Version 2 Release 3.
You can also use group jobs to pass through to multiple systems from your
home system. For information about group jobs, see the Work Management
book.

Using the Transfer Pass-Through (TFRPASTHR) Command

You can return to the source system or the home system by using the
TFRPASTHR command. This command does not end your pass-through session. It
also does not end your session at the target system. Therefore, you can resume
your work on the target system when you finish working at the source or home
system.

To use the Transfer Pass-Through command, type TFRPASTHR and the appropriate
TOJOB parameter on the command line and press the Enter key. You can do this
when you are working on the target system and want to return to the source
system or to the home system. The TFRPASTHR command has the same func-
tions as System Request options 10, 11, 13, and 14. As the name implies, the
TFRPASTHR command works only for pass-through sessions and not for TELNET
sessions. (The System Request options work for both pass-through and TELNET
sessions.)

The options available on the TFRPASTHR command are:

TOJOB(*SRC)
This option suspends the job on the target system and transfers the user back
to the source system. The program specified by the SRQ10PGM on the Start
Pass-Through request is given control. By default, the SRQ10PGM parameter
specifies the System Request menu. The TFRPASTHR TOJOB(*SRC)
command is the same as System Request option 10.
When the SRQ10PGM program ends, pass-through returns you to the job on
the target system from which you transferred.

TOJOB(*ALT)
This option suspends the job on the target system and transfers the user back
to the source system. The alternate job at the source system is given control.

Chapter 5. Going Back and Forth between Systems 5-5

The TFRPASTHR TOJOB(*ALT) command is the same as System Request
option 11.
To go back to the suspended job at the target system, do one of the following:

Sign off the alternate job.

Use the TFRSECJOB command to transfer from the alternate job to the
original job. Because the original job is still running pass-through, it gives
control to the target system.

TOJOB(*HOME)
This option suspends the job on the system where the TFRPASTHR command
is entered and transfers control back to the home system. The job on the home
system runs the program specified by the system request program
(SRQ10PGM) parameter on the STRPASTHR command that you entered on
the home system. By default, the SRQ10PGM parameter specifies the System
Request menu. The TFRPASTHR TOJOB(*HOME) command is the same as
System Request option 13.
When the SRQ10PGM program ends, pass-through returns you to the job on
the system from which you transferred.

TOJOB(*HOMEALT)
This option suspends the job on the system where the TFRPASTHR command
is entered and transfers control back to the home system. The alternate job at
the home system is given control. The TFRPASTHR TOJOB(*HOMEALT)
command is the same as System Request option 14.
To go back to the suspended job at the system from which you transferred, do
one of the following:

Sign off the alternate job.

Use the TFRSECJOB command to transfer from the alternate job to the
original job. Because the original job is still running pass-through, it gives
control to the system from which you transferred.

Using System Request Options

When you press the System Request key on the target system, an entry line
appears at the bottom of the display. If you press the Enter key on a target
System/38 or an AS/400 system, a menu appears on which you can indicate the
options you want. If you press the Enter key on a target System/36, a System/36
system message appears: System Request Invalid at Command Display Station.
The System Request menu is not available on the System/36. To avoid this
message, enter a 10, 11, 13, or 14 on the system request entry line before
pressing the Enter key. This starts System Request option 10, 11, 13, or 14 at the
source system. This method can be used on any target system, not only on a
target System/36.

AS/400 System Request Options

You can use the following AS/400 system request options to go back and forth
between systems after passing through to them.

Option 10 (Start system request at previous system) takes you from an interme-
diate or end system to the previous system. The previous system is the source

5-6 Remote Work Station Support V4R1

system if pass-through was used or the client system if TELNET was used. The
program specified by the system request program (SRQ10PGM) parameter on the
STRPASTHR command that was entered at the previous system will be running.

Option 11 (Transfer to previous system) takes you from an intermediate or end

system to the alternate job on the previous system. The previous system is the
source system if pass-through was used or the client system if TELNET was used.

Option 13 (Start system request at home system) takes you from an interme-
diate or end system to the home system. The program specified by the system
request program (SRQ10PGM) parameter on the STRPASTHR command that was
entered at the home system will be running.

Option 14 (Transfer to home system) takes you from an intermediate or end

system to the home system. Control is given to the alternate job at the home
system.

Option 15 (Transfer to end system) takes you from an intermediate or home

system back to the system you came from. The system you came from is the
system where you used System Request option 10, 11, 13, or 14 to get to the
intermediate or home system. Using option 15, whatever job and program were
interrupted when you left the end system resume control when you return to the
end system.

Option 80 (Disconnect job) provides a function that disconnects some types of

interactive jobs. This allows you to sign off the job temporarily and return to the
same point in processing that you left. Even though this type of disconnection is not
currently possible for pass-through jobs, you can disconnect the job on the home
system.

If you pass through and then return to the System Request menu of the home
system, you can select option 80 (Disconnect job). (You can return to the System
Request menu of the home system by using System Request option 13 or System
Request option 10. If you use System Request option 10, you may need to do so
multiple times.) If you do this, remember your pass-through session is still active.
Using option 80 gives you the advantage of signing on to your source system again
to resume your operations on the target system. However, the cost of the communi-
cations connection is a disadvantage. You pay for the time your job is disconnected
from the source system because your pass-through connection remains active. For
more information about the disconnection option, see the System Operation for
New Users book and the Work Management book.

Using the System Request Program (SRQ10PGM) Parameter

System request program (SRQ10PGM) is a parameter on the STRPASTHR
command. You can use the SRQ10PGM parameter to specify the program to be
called when you select options 10 or 13 on the System Request menu on an inter-
mediate or end system. (Option 10 is Start system request at previous system,
and option 13 is Start system request at home system.) By default, the
SRQ10PGM parameter specifies the System Request menu.

If you want a program other than the System Request menu to be called, specify
that program on the SRQ10PGM parameter. SRQ10PGM values on the
STRPASTHR command are:

Chapter 5. Going Back and Forth between Systems 5-7

*SRQMNU: The System Request menu from the previous or home system is
displayed. This is the default value.
program-name: The name of the program to be called. If a library name is not
specified, the libraries in the library list (*LIBL) are searched for the program.
Note: This program runs when you transfer back to the system where you issued
the STRPASTHR command and specified this program. You can transfer
back to this system using one of the following methods:
System Request option 10
System Request option 13
TFRPASTHR TOJOB(*SRC)
TFRPASTHR TOJOB(*HOME)

If you press the System Request key and choose System Request option 15 while
this program is running, you return to this program and not the end system. When
you end this program, you transfer back to the system from which you came.

To return to your source job without ending pass-through, specify SRQ10PGM

(QSYS/QCMD) on the STRPASTHR command. Thereafter, when you select option
10 or 13 from the System Request menu, the Command Entry display on the pre-
vious (option 10) or home (option 13) system appears. To exit the Command Entry
display and return to the target system, press F3 (Exit).

System/38 System Request Options 10 and 11

On the target System/38, option 10 (Start system request at source system) allows
you to transfer back to the source system. After you transfer back to the source
system, you can use its System Request menu.

Option 11 (Transfer to source system) starts an alternate job on the source system.

5-8 Remote Work Station Support V4R1

Chapter 6. Work Management Considerations for Display
Station Pass-Through
When managing your system functions, it is important to know the extent of the
function's capabilities. This chapter discusses the capabilities and limitations you
should consider when configuring your system for the display station pass-through
function.

Control of Remote Sessions from Other Systems

If you are responsible for pass-through configuration or for the security of your
system, you must know the capabilities and limitations of the QRMTSIGN system
value. The pass-through support on your system examines this value each time a
user attempts to pass through to your system or attempts to use the work station
function of Client Access to attach to your system.

You can use the QRMTSIGN system value to do the following:

Prevent all pass-through and work station function sessions from starting on the
system.
Force all pass-through and work station function sessions requesting automatic
sign-on to use the same user profile they are currently using on the source
system, provided they specify the appropriate password. All other pass-through
and work station function sessions must use normal sign-on procedures.
Allow all pass-through and work station function sessions to start, and decide
which of those sessions requesting automatic sign-on will be allowed to do so,
providing they specify the appropriate password.
Use a program to decide which pass-through and work station function ses-
sions can automatically sign-on.
Allow all pass-through and work station function sessions to start, and decide to
which target user profile the user should sign on.

The QRMTSIGN System Value

Use the Change System Value (CHGSYSVAL) command or the Work with System
Value (WRKSYSVAL) command to specify the QRMTSIGN system value.
Note: Only a user with *ALLOBJ authority can change the QRMTSIGN system
value.

Valid values for QRMTSIGN are:

Force sign-on (*FRCSIGNON)

The force sign-on value requires all pass-through sessions started for this
system to go through normal sign-on procedures. This is the default value.

Same profile (*SAMEPRF)

The same profile value allows you to bypass the sign-on display by specifying
the target system use the same user profile that the source system is using.
Bypassing the sign-on display should be allowed for pass-through attempts only
if the user profile name on the source system and the user profile name on the
target system are identical.

 Copyright IBM Corp. 1997 6-1

Password verification occurs before the target pass-through program is used. If
a password that is not valid is sent on an automatic sign-on attempt, the pass-
through session always ends and an error message is sent to the user.
However, if the profile names are different, *SAMEPRF indicates that the
session ends with a security failure even if the user entered a valid password
for the remote user profile.
The sign-on display appears for pass-through attempts not requesting auto-
matic sign-on.

Verify (*VERIFY)
The VERIFY value allows you to bypass the sign-on display of the target
system if valid security information is used. Bypassing the sign-on display
should be allowed for any pass-through attempt that provides valid security
information. If the password is not valid for the specified target user profile, the
pass-through session ends with a security failure.
If this system has a QSECURITY value of 10, any automatic sign-on request
will be allowed.
The sign-on display appears for pass-through attempts not requesting auto-
matic sign-on.

Reject (*REJECT)
No pass-through is allowed. All pass-through attempts to this target system are
rejected.
Specifying QRMTSIGN(*REJECT) is the most effective method for preventing
users from passing through to a system. However, the batch jobs controlling
the pass-through sessions run briefly. If the security officer wants to prevent
this, the subsystem that handles pass-through requests should be ended or the
communications objects should be varied off.

program-library
The user can specify a remote sign-on control program name that meets the
input and output specifications described in “QRMTSIGN Program
Specifications.” This program runs at the beginning and end of every target
pass-through job. The security officer can tailor how the automatic sign-on
requests are handled and identify the users who have passed through to this
system by using this method.
The program name must precede the library name.

Remote Sign-On Considerations

This section discusses the capabilities and limitations you should consider when
configuring a remote location system for the display station pass-through function.

QRMTSIGN Program Specifications

By writing a program using the following specifications and specifying that program
in the QRMTSIGN system value, you can more closely control which pass-through
and work station function sessions are successful and which successful sessions
can automatically sign on. An example program, RMTSIGNEX2, is shown in
Figure 6-1 on page 6-5.

6-2 Remote Work Station Support V4R1

Input to the QRMTSIGN Program
The input to the QRMTSIGN program is a 128-character string containing the
following:
Source location — CHAR(8)
Source network ID — CHAR(8)
Source user profile — CHAR(10) If the source user is passing through from an
older system not providing the source user profile, this field will be filled
with blanks (X'40').
Target user profile — CHAR(10) If the source user has not requested automatic
sign-on, this field will be filled with blanks (X'40').
The user program determines by using this information if automatic
sign-on was requested. If this field is filled with blanks, a return code of
2 is not appropriate and that value is treated as 1 (See the topic “Output
from the QRMTSIGN Program” on page 6-4).
This value may be overridden by the program. To do so, put the new
value in this field and use return code 3.
Session start and stop indicator — CHAR(1) '1' (X'F1') indicates that this is a
pass-through session being started. '0' (X'F0') indicates that this pass-
through session is ending.
Target initial program — CHAR(10) If the source user has not requested auto-
matic sign-on or did not specify an initial program, this field is filled with
blanks (X'40').
This value may be overridden by the program. To do so, put the new
value in this field and use return code 3.
Target initial menu — CHAR(10) If the source user has not requested automatic
sign-on or did not specify an initial menu, this field is filled with blanks
(X'40').
This value may be overridden by the program. To do so, put the new
value in this field and use return code 3.
Target current library — CHAR(10) If the source user has not requested auto-
matic sign-on or did not specify a current library, this field is filled with
blanks (X'40').
This value may be overridden by the program. To do so, put the new
value in this field and use return code 3.
Virtual device name — CHAR(10) This is the name of the virtual device used by
this pass-through attempt.
Version/Release/Modification number — CHAR(6) This is the version, release,
and modification number for the operating system at the target system.
Allow pass-through indicator — CHAR(1) '1' (X'F1') indicates that the user
may pass through from this system, which is the target of the current
pass-through session, to another system. '0' (X'F0') indicates that the
user may not pass through from this system, which is the target of the
current pass-through session.
When this value is '1', it can be overridden by the QRMTSIGN
program. To do so, put the new value in this field and use any return
code. When this value is '0', it cannot be overridden by the

Chapter 6. Work Management Considerations for Display Station Pass-Through 6-3

QRMTSIGN program, and any new value assigned by the QRMTSIGN
program is ignored.
Reserved space — CHAR(44) All blanks (X'40').

Output from the QRMTSIGN Program

The output from the QRMTSIGN program is an 8-character string containing the
following:
Return code — CHAR(1) Value ignored if the pass-through start and stop indicator
is specified as '0' (Stop).
'0' - Reject Pass-through not allowed to progress further. A
QRMTSIGN value of *REJECT does this for all pass-through
attempts.
'1' - Reject, but show sign-on Do not allow automatic sign-on for this
pass-through, but let a blank sign-on display be shown. A
QRMTSIGN value of *FRCSIGNON does this for all pass-
through attempts.
'2' - Accept automatic sign-on attempt Allow automatic sign-on for
this pass-through attempt.
If you return this value when automatic sign-on has not been
requested, the pass-through support handles the pass-
through attempt as if the program returned with a '1' value.
When the target user profile name that is passed to the
program is blank, and the program returns this value, a blank
sign-on display appears.
'3' - Override the automatic sign-on information Allow this pass-
through attempt, but override the following values with the
override values specified by the QRMTSIGN program:
Target user profile
Target initial program
Target initial menu
Target current library
Reserved — CHAR(7) These characters are ignored by the current support, but
could be used in future support.

Figure 6-1 on page 6-5 is an example of a CL program that uses the QRMTSIGN
programming specification shown in “QRMTSIGN Program Specifications” on
page 6-2.

6-4 Remote Work Station Support V4R1

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ Program RMTSIGNEX2 \/
/\ \/
/\ This program is meant to be an example which shows how attempts \/
/\ to remotely sign on using AS/4ðð Display Station Pass-Through \/
/\ or Work Station Function can be handled using a program. The \/
/\ program, such as this one, would be compiled and then named in \/
/\ the QRMTSIGN system value. \/
/\ \/
/\ DESIGN: \/
/\ The program simply returns if it is called when pass-through is \/
/\ ending. \/
/\ \/
/\ The following remote sign on requests will be allowed to bypass \/
/\ normal sign on (automatically sign on) if they request it. \/
/\ This means that the program returns a '2' to its caller. \/
/\ Source User Source Location Target User Special Checks \/
/\ ----------- --------------- ----------- ------------------- \/
/\ QSECOFR SECUREL1 any none \/
/\ any SECUREL1 same none \/
/\ any any TIMECRDUSR INLPGM must be TIME \/
/\ any any 'PCxxxxxx' same none \/
/\ \/
/\ The following remote sign on requests will be disallowed; \/
/\ that is, they will not even be presented with a sign-on screen. \/
/\ This means that the program returns a 'ð' to its caller. \/
/\ Source User Source Location Target User Special Checks \/
/\ ----------- --------------- ----------- ------------------- \/
/\ PCHACKER any any none \/
/\ EXEMPLOYEE any any none \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ If the source user is FRED and FRED requests to pass-through, \/
/\ he is forced to sign-on as the target user, SERVICE. \/
/\ \/
/\ Source User Source Location Target User Special Checks \/
/\ ----------- --------------- ----------- ------------------- \/
/\ FRED any SERVICE source user must \/
/\ be FRED \/
/\ \/
/\ The remaining remote sign on requests will be forced through \/
/\ normal sign-on procedures (they must use the sign on display.) \/
/\ This means that the program returns a '1' to its caller. \/
/\ \/
/\ These remaining requests are not allowed to pass through from \/
/\ this system. \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

PGM PARM(&DATA &RTNCODE);

Figure 6-1 (Part 1 of 3). QRMTSIGN Example Sign On CL Program

Chapter 6. Work Management Considerations for Display Station Pass-Through 6-5

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ Parameter declares \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

DCL VAR(&DATA); TYPE(\CHAR) LEN(128) /\ Input information \/

DCL VAR(&RTNCODE); TYPE(\CHAR) LEN(8) /\ Return code \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ Variable declares \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

DCL VAR(&ZERO); TYPE(\CHAR) LEN(1) VALUE('ð') /\ End the +

passthru session \/
DCL VAR(&ONE); TYPE(\CHAR) LEN(1) VALUE('1') /\ Show the signon +
screen \/
DCL VAR(&TWO); TYPE(\CHAR) LEN(1) VALUE('2') /\ Allow automatic +
signon request \/
DCL VAR(&THREE); TYPE(\CHAR) LEN(1) VALUE('3') /\ Overrides the +
target user profile \/
DCL VAR(&WHENCALD); TYPE(\CHAR) LEN(1) /\ When this program is +
being called - +
'1' STRPASTHR command +
'ð' ENDPASTHR command \/
DCL VAR(&SRCPROF); TYPE(\CHAR) LEN(1ð) /\ Source user profile \/
DCL VAR(&TGTPROF); TYPE(\CHAR) LEN(1ð) /\ Target user profile \/
DCL VAR(&INLPGM); TYPE(\CHAR) LEN(1ð) /\ Initial program \/
DCL VAR(&SRCLOC); TYPE(\CHAR) LEN(8) /\ Source location \/
DCL VAR(&LOCPREF); TYPE(\CHAR) LEN(2) /\ Location Prefix \/
DCL VAR(&ENDPASTH); TYPE(\CHAR) LEN(1) VALUE('ð') /\ This program +
is being called +
because of the +
ENDPASTHR command \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ Includes user profile names and location names \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
DCL VAR(&QSECOFR); TYPE(\CHAR) LEN(1ð) VALUE('QSECOFR ')
DCL VAR(&TIMECRDUSR); TYPE(\CHAR) LEN(1ð) VALUE('TIMECRDUSR')
DCL VAR(&PCHACKER); TYPE(\CHAR) LEN(1ð) VALUE('PCHACKER ')
DCL VAR(&EXEMPLOYEE); TYPE(\CHAR) LEN(1ð) VALUE('EXEMPLOYEE')
DCL VAR(&TIMEPGM); TYPE(\CHAR) LEN(1ð) VALUE('TIME ')
DCL VAR(&SECLOC); TYPE(\CHAR) LEN(8) VALUE('SECUREL1')
DCL VAR(&PCPREFIX); TYPE(\CHAR) LEN(2) VALUE('PC')
DCL VAR(&SERVICE); TYPE(\CHAR) LEN(1ð) VALUE('SERVICE ')
DCL VAR(&FRED); TYPE(\CHAR) LEN(1ð) VALUE('FRED ')

Figure 6-1 (Part 2 of 3). QRMTSIGN Example Sign On CL Program

6-6 Remote Work Station Support V4R1

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ Start of program \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

CHGVAR &WHENCALD VALUE(%SST(&DATA 37 1)) /\ Indication of when +

this program is being +
called \/
IF (&WHENCALD = &ENDPASTH); RETURN /\ If being called +
because of ENDPASTHR +
command then return \/
CHGVAR &SRCPROF VALUE(%SST(&DATA 17 1ð)) /\ Source user profile \/
CHGVAR &TGTPROF VALUE(%SST(&DATA 27 1ð)) /\ Target user profile \/
CHGVAR &SRCLOC VALUE(%SST(&DATA 1 8)) /\ Source location \/
CHGVAR &INLPGM VALUE(%SST(&DATA 38 1ð)) /\ Initial program \/
CHGVAR &LOCPREF VALUE(%SST(&DATA 1 2)) /\ Location prefix \/

/\ \\\ Check for those not allowed at all \\\ \/

/\ PCHACKER returns ð \/
/\ EXEMPLOYEE returns ð \/
IF ((&SRCPROF = &PCHACKER); \OR +
(&SRCPROF = &EXEMPLOYEE)); DO
CHGVAR &RTNCODE VALUE(&ZERO);
RETURN
ENDDO

/\ \\\ Check for those who can do automatic sign-on \\\ \/

IF (((&SRCLOC = &SECLOC); \AND (&SRCPROF = &QSECOFR)); \OR +
((&SRCLOC = &SECLOC); \AND (&SRCPROF = &TGTPROF)); \OR +
((&INLPGM = &TIMEPGM); \AND (&TGTPROF = &TIMECRDUSR)); \OR +
((&LOCPREF = &PCPREFIX); \AND (&SRCPROF = &TGTPROF)); ) DO
CHGVAR &RTNCODE VALUE(&TWO);
RETURN
ENDDO

/\ \\\ Check for FRED \\\ \/

IF (&SRCPROF = &FRED); DO
CHGVAR &RTNCODE VALUE(&THREE);
CHGVAR %SST(&DATA 27 1ð) VALUE(&SERVICE);
RETURN
ENDDO

/\ Everyone else must go through normal sign on \/

CHGVAR &RTNCODE VALUE(&ONE);

/\ Disallow multiple pass-through. \/

CHGVAR %SST(&DATA 84 1) VALUE(&ZERO);
ENDPGM

Figure 6-1 (Part 3 of 3). QRMTSIGN Example Sign On CL Program

QRMTSIGN Programming Considerations

If a program is specified for the QRMTSIGN system value, that program is called
twice by every pass-through session: once to see if pass-through should be allowed
and once when the session ends. This allows system administrators to track the
users passing through to their systems.

The pass-through session ends and a job log is created on the system if any of the
following situations occur:
Program does not exist
Program creates an exception
Program returns with a value not defined in the programming specification

Chapter 6. Work Management Considerations for Display Station Pass-Through 6-7

User profile under which the pass-through job is running does not have
authority to use the program
Note: A message in the job log on the target system indicates the type of problem
found by the target pass-through programs. If an error was detected in your
QRMTSIGN program, the user of the STRPASTHR command receives a
CPF8935 message.

If your program returns a value of '2' in the return code field (indicating that it will
allow automatic sign-on for this pass-through attempt), automatic sign-on may not
necessarily occur. For example, if the user did not request automatic sign-on, the
sign-on display is shown. Also, if the user specified an initial menu, initial program,
or current library that does not exist or to which the user does not have authority,
the session could end, or the sign-on display could be presented. The results
depend on the type of error found during the automatic sign-on attempt.

Creating a Subsystem for Display Station Pass-Through

If you are using the AS/400 system as a target system, the instructions in the fol-
lowing sections are not necessary if your system uses the IBM-supplied subsys-
tems. If you do not use the IBM-supplied subsystems, you must perform the
instructions in the following sections. Using these subsystems is recommended.
Remember, a minor mistake can cause pass-through to have a time-out failure
after being started. If you find such an error after following these instructions, verify
each section again.

All the instructions discussed in this section are required on a System/38 if it is

used as a target system. For more information about using System/38, see the
System/38 Environment Programming book.

Follow these instructions for the AS/400 system only if you create your own subsys-
tems to control your pass-through environment.
Note: If you are using pass-through servers, go to “Adding a Work Station Entry”
on page 6-9.

Creating Default User Profiles for the Subsystem

| Note: This step is necessary only when you are NOT running pass-through
| servers. Pass-through servers always use QUSER as the default. The
| default cannot be changed.

You can create a default user profile with limited authority at the target system and
at each intermediate system, or you can choose to use an IBM-supplied user
profile, such as the QUSER profile. This user profile is used by the APPC jobs
started at remote systems that support pass-through. If a default user profile is not
available, and the source system sends either an undefined user ID or an empty
(null) user ID, an authorization error occurs.

The profile should have the authority:

To run the IBM-supplied program QPAPAST2, which is specified in the program
start request. The profile is used by the subsystem when a program start
request is received without a user ID request.

6-8 Remote Work Station Support V4R1

To use the device descriptions that are part of the APPC network through
which you plan to run pass-through.
To use the pass-through job description that you will create in the “Creating Job
Descriptions” step.
To use the pass-through virtual devices and virtual controllers that are
accessed.

To create the default user profile for the subsystem, use the Create User Profile
(CRTUSRPRF) command as shown in the following example:
CRTUSRPRF USRPRF(PTUSRPRF) JOBD(PTJOBD)
TEXT('Example pass-through user profile')

This command string causes an error message to be returned because you created
the profile for a job description not yet created. To create the job description or user
profile without error messages, create either one without referring to the other. After
the second description or profile is created, change one to refer to the other.

Creating Job Descriptions

| Note: This step is necessary only when you are NOT running pass-through
| servers. Pass-through servers always use QUSER as the default. The
| default cannot be changed.

You can create a job description to use at the target system and at each interme-
diate AS/400 system and System/38. On an AS/400 system, you may choose to
use an IBM-supplied job description. The job description must be in a library in the
default library list of an interactive subsystem description. The following example
shows a possible job description:
CRTJOBD JOBD(PTJOBD) USER(PTUSRPRF) LOG(4 1ð \SECLVL)
TEXT('Example pass-through job description')

Adding a Work Station Entry

At the target system, you can add a work station entry to the interactive subsystem
description that controls the virtual work station. This is not necessary if a correct
work station entry already exists.

To see if a correct entry exists, use the Display Subsystem Description (DSPSBSD)
command. To add a new entry, use the Add Work Station Entry (ADDWSE)
command as in the following example:
ADDWSE SBSD(USRSBS) WRKSTNTYPE(5291)

Type this command and then start the USRSBS subsystem using the Start Sub-
system (STRSBS) command. All 5291 devices, including all virtual devices of that
type that are varied on, will run under the USRSBS subsystem.
Note: You can also add work station entries by name. For example, you can add
an entry for the VDEV1 virtual device to the USRSBS subsystem by using
the following command:
ADDWSE SBS(USRSBS) WRKSTN(VDEV1)

If you control your virtual devices by using work station name entries, and if you
want to use the support for automatic configuration of virtual devices, you must add
the work station entries for the automatically configured virtual devices. For

Chapter 6. Work Management Considerations for Display Station Pass-Through 6-9

example, you must run the ADDWSE command for the QPADEV0001 and
QPADEV0002 entries.

Adding Communications Entries

| Note: This step is necessary only when you are NOT running pass-through
| servers. Pass-through servers always use QUSER as the default. The
| default cannot be changed.

Ensure a communications entry exists in the subsystem description for each APPC
device description at the target system and at each intermediate system. Use the
QCMN subsystem or a user-created subsystem to isolate interactive users from
APPC error recovery.

These communications entries enable users on the source system and each inter-
mediate system to request pass-through. The communications entry must specify a
default user profile that must exist on those systems. To add a new entry, use the
Add Communications Entry (ADDCMNE) command. For example, to add a commu-
nications entry, specify the following command on the target system:
ADDCMNE SBSD(USRSBS) DEV(DET)
JOBD(PTJOBD) DFTUSR(PTUSRPRF)

DET is the name of the APPC device description that connects that system to the
next system closer to the source system on the APPC network through which you
plan to run pass-through. PTUSRPRF is the name of the user profile created in the
first step of the work management configuration steps.

To change an existing entry, use the Change Communications Entry (CHGCMNE)

command.

Adding Routing Entries

| Note: This step is necessary only when you are NOT running pass-through
| servers. Pass-through servers always use QUSER as the default. The
| default cannot be changed.

The subsystem that receives the program start request requires a routing entry with
*RTGDTA specified as the program name. The IBM-supplied subsystems, QCMN
and QBASE, have routing entries that can be used for APPC.

Add the entry as follows:

ADDRTGE SBSD(USRSBS) SEQNBR(5ðð) CMPVAL('PGMEVOKE' 29) PGM(\RTGDTA)

After running the ADDRTGE command and starting the USRSBS subsystem by
using the Start Subsystem (STRSBS) command, the following occurs:
All communications work requests that come to the DET device are handled by
the USRSBS subsystem.
All pass-through program start requests are handled by the USRSBS sub-
system. The subsystem starts the job by using the PTUSRPRF, which in turn
runs the IBM-supplied program, QPAPAST2.

You may want to set up the target system and each intermediate system to reduce
the effect of sharing the same class for pass-through jobs as other jobs. To do this,
specify a class in the routing table at the target system and each intermediate

6-10 Remote Work Station Support V4R1

system using the Create Class (CRTCLS) command and add a routing entry to the
subsystem description.

The CRTCLS command contains parameters to control the run-time environment of

a job. For more information about using the parameters of the CRTCLS command,
see the Distributed Data Management book or the CL Reference book.

Chapter 6. Work Management Considerations for Display Station Pass-Through 6-11

6-12 Remote Work Station Support V4R1
Chapter 7. Display Station Pass-Through Considerations
The display station pass-through function can be used to accomplish tasks not
available on your system. To use the display station pass-through function effi-
ciently, you should be aware of all the functions available. This chapter discusses
the capabilities and limitations you should consider when using the display station
pass-through function.

Security Considerations for Display Station Pass-Through

A user with security officer (*ALLOBJ) authority must be explicitly authorized to use
devices on the following systems:
System/38.
Systems using an OS/400 release earlier than Version 1 Release 2.0 with a
system security level (QSECURITY) system value of 30 or greater.

For example, for each display device (local, remote, or virtual) that a security officer
wants to sign on to, that user must specify the following command:
GRTOBJAUT OBJ(display_name) OBJTYPE(\DEVD) AUT(\CHANGE)

Likewise, a remotely started job cannot start under a security officer profile unless
that profile has been granted specific authority to the communications device.

The OS/400 Version 1 Release 2.0 and later releases support the limit security
officer (QLMTSECOFR) system value. If the QLMTSECOFR value is set to 1, the
AS/400 system provides the same support as in previous releases. However, when
this value is set to 0, the system does not limit the devices that the security officer
can use to sign on.

QLMTSECOFR (limit security officer) system value devices is allowed. If the

QLMTSECOFR value is set to 0, all devices automatically configured by pass-
through can be used for the security officer. If the QLMTSECOFR value is set to 1,
the security officer may not have authority to use automatically configured virtual
devices. Therefore, if the QLMTSECOFR value is 1, consider manually creating a
virtual controller and devices for the specific use of your security officer.

Setting this value is also important when a security officer attempts to automatically
sign on. If the target system has theQLMTSECOFR value set to 1, a user with
*ALLOBJ authority must be granted specific authority to the APPC device used by
pass-through on the target system. If that authority is not granted, the automatic
sign-on attempt fails with a security error.

The QRMTSIGN system value is also an important security consideration. For infor-
mation about the QRMTSIGN system value, see “Control of Remote Sessions from
Other Systems” on page 6-1.

 Copyright IBM Corp. 1997 7-1

Pass-Through Use with System/36
Some special considerations are necessary when the AS/400 display station pass-
through is used to a System/36. These considerations are not included in this topic,
but are discussed in the System/36 Environment Programming book.

Pass-through from an AS/400 system to a System/36 is essentially the same as

pass-through to another AS/400 system or to a System/38 except for the following:
The virtual controller (VRTCTL) parameter is never used by the System/36,
even if the VRTCTL parameter is specified on the STRPASTHR command.
AS/400 system pass-through support does not send any control character bytes
on a read command to a target System/36 because System/36 does not
support the use of control characters on read commands.
When AS/400 user-defined data streams are sent to a System/36 using pass-
through, they should not include save and restore commands combined with
other data stream commands. Save and restore commands must be sent in a
separate data stream, or results may occur that are not predictable, such as
ending the pass-through session.
If you want to request automatic configuration when you use pass-through from
a System/36 to an AS/400 system, do not specify the virtual controller param-
eter on the System/36 PASSTHRU procedure or specify the special controller
name QPACTL00 in the virtual controller parameter.

In addition, if you pass through a locally attached display station on an AS/400

system to the System/36, there is a limitation of 127 input fields for any application
that is run. To avoid this limitation, either use the Expanded Workstation Feature on
the System/36 or use a remotely attached display station. The Expanded Work-
station Feature on the System/36 increases the number of input fields the
System/36 can handle.

Display Station Pass-Through Message Handling

If a message arrives at the target system and you are on the target system, the
message light flashes on and stays on until you use the Display Message
(DSPMSG) command to see the message.

When the first message arrives at the source system, the message light flashes on
briefly and then stays off as long as you are on the target system. The message
light does not flash for any other messages. When you return to the source system,
the message light appears again, until you use the Display Message (DSPMSG)
command to see the message. If a message was already on the message queue at
the target system, the message light does not flash again.

Automatic Sign-On
AS/400 display station pass-through allows you to request an automatic sign-on to
the target system. If you have the correct security authorization and if the target
system allows automatic sign-on, you can bypass the sign-on display on the target
system.

The following examples show some of the ways you can use automatic sign-on:

7-2 Remote Work Station Support V4R1

If you have the same user ID on all systems in a secure APPN network, you
can set up another version of the STRPASTHR command that requests the
current user ID be used to automatically sign on to the target system. For more
information about using these parameters, see the automatic sign-on examples
in this chapter. For more information about secure APPN networks, see the
APPN Support book.
If you write a menu and want a menu option to run a program on another
system, you can use the STRPASTHR command to request the target system
to automatically sign on by using a user ID especially created to run that
program. On the same STRPASTHR command, you can specify the target
system to sign the job off when the program ends.
If you have many users who must pass through to a single user ID on another
system, you may not want to tell them the new password each time it changes.
You can write a CL program to automatically retrieve the new password from a
data area and use the password to automatically sign the users on to the target
system.

Using the STRPASTHR Command for AS/400 Automatic Sign-On

You must explicitly specify the STRPASTHR command parameters used for auto-
matic sign-on. However, the defaults for these parameters can be changed. To
change the default values of the STRPASTHR command, the system operator
should follow these steps:
1. Create a duplicate STRPASTHR command.
2. Change the defaults in the duplicate command.
3. Place the duplicate command in a library that is located before the QSYS
library in the library list of the system.

For an example of the commands used to create a duplicate STRPASTHR

command, see “Automatic Sign-On Examples” on page 7-6.

To use automatic sign-on for pass-through, enter the remote location name on the
Start Pass-Through display and press F10 (Additional parameters).

Chapter 7. Display Station Pass-Through Considerations 7-3

à ð
Start Pass-Through (STRPASTHR)

Type choices, press Enter.

Remote location . . . . . . . . > SYSA___ Name, \CNNDEV

Virtual controller . . . . . . . \NONE____ Name, \NONE
Virtual display device . . . . . \NONE____ Name, \NONE
+ for more values _________
Mode . . . . . . . . . . . . . . \NETATR_ Name, \NETATR
Local location . . . . . . . . . \LOC____ Name, \LOC, \NETATR
Remote network identifier . . . \LOC____ Name, \LOC, \NETATR, \NONE
System request program . . . . . \SRQMNU___ Name, \SRQMNU
Library . . . . . . . . . . . __________ Name, \LIBL, \CURLIB

Additional Parameters

User profile . . . . . . . . . . \NONE____ Name, \NONE, \CURRENT

User password . . . . . . . . . \NONE____ Name, \NONE
Initial program to call . . . . \RMTUSRPRF Name, \RMTUSRPRF, \NONE
Initial menu . . . . . . . . . . \RMTUSRPRF Name, \RMTUSRPRF, \SIGNOFF
More...
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

á ñ
To continue to the next display, press the Page Up key.

à ð
Start Pass-Through (STRPASTHR)

Type choices, press Enter.

Current library . . . . . . . . \RMTUSRPRF Name, \RMTUSRPRF

Display option . . . . . . . . . \YES Character value, \YES, \NO

Automatic Sign-On Parameters

The STRPASTHR command parameters used for automatic sign-on are:

User profile (RMTUSER)

The user profile for automatic sign-on to the target system. Allowed values are:

*NONE: Automatic sign-on is not requested and will not occur unless the
system security officer uses the QRMTSIGN program to force auto-
matic sign-on to a specified target user profile. This is the default
value.
*CURRENT: User profile of the job using the STRPASTHR command is used.
You are automatically signed on if the target system allows auto-
matic sign-on, if the user profile exists on the target system, and if
the password specified in the RMTPWD parameter is valid for the
profile. Otherwise, a sign-on display appears on the target system or
a failure message appears on the source system, depending on the
configuration on the target system.
profile-name: Specify a profile name that you expect to exist on the target
system. You are automatically signed on if the target system allows
automatic sign-on, if the user profile exists on the target system, and
if the password specified in the RMTPWD parameter is valid for the

7-4 Remote Work Station Support V4R1

profile. Otherwise, either a sign-on display on the target system or a
failure message appears on the source system, depending on the
configuration of the target system. If a profile is specified, a pass-
word must also be specified, even if the profile specified is the same
as the current profile.

User password (RMTPWD)

| An encrypted password that is sent to the target system. Allowed values are:

| *NONE: The system does not send a password. If you specify a profile on
| the RMTUSER parameter, you cannot specify RMTPWD(*NONE). If
| you specify RMTUSER(*CURRENT) and the location specified in
| RMTLOCNAME is secure, this value is allowed. This value is the
| default.
| password: Specify a password to use on the target system to verify the sign-on
| of the user specified in the RMTUSER parameter. Unless the target
| system indicates it does not have a security manager, this password
| is not encrypted when it is sent over the communications line. On
| the AS/400 system, this indicates the target system has the
| QSECURITY system value specified as 10.

| Note: If you are not using automatic sign-on, the password you enter on the
| sign-on display of the target system is not encrypted before it is passed
| over the communications line. Therefore, no additional security expo-
| sure exists when using automatic sign-on support.

Parameters That Can be Overridden by the Remote Sign-On

Control Program
The following parameters can be overridden by the remote sign-on control program
on the target system. For more information about the remote sign-on control
program, see “The QRMTSIGN System Value” on page 6-1.

User profile (RMTUSER)

The user profile for automatic sign-on to the target system.

Initial program to call (RMTINLPGM)

The initial program started on the remote system after successful automatic
sign-on. The initial program always runs before the initial menu specified in the
RMTINLMNU parameter. Allowed values are:

*RMTUSRPRF: Use the initial program in the remote user profile. This value is
the default.
*NONE: No program will be called even if you specify a program in the
remote user profile. If automatic sign-on is not used, the same result
occurs if you enter *NONE in the Initial program field of the sign-on
display.
program: Specify the name of a program called as a part of automatic
sign-on.

Initial menu (RMTINLMNU)

The initial menu shown when automatic sign-on occurs on the target system,
after the program specified in the RMTINLPGM ends. Allowed values are:

*RMTUSRPRF: Use the initial menu in the remote user profile. This value is the
default.

Chapter 7. Display Station Pass-Through Considerations 7-5

*SIGNOFF: Use this value to sign off after the RMTINLPGM program runs.
Your job on the target system does not call a menu, even if you
specify a menu in the remote user profile. If automatic sign-on is not
used, almost the same effect occurs if you enter *SIGNOFF in the
Initial menu field on the sign-on display. However, if you specify
RMTINLMNU(*SIGNOFF) when you start the pass-through session,
the pass-through session ends when the RMTINLPGM ends
because all pass-through sessions established with automatic
sign-on end when the job ends.
menu: Specify a menu to appear immediately after the initial program, if
any, runs during automatic sign-on.

Current library (RMTCURLIB)

The name of the library that should become the current library in the library list
of the job as a part of the automatic sign-on. Allowed values include:

*RMTUSRPRF: Use the current library in the remote user profile. This value is
the default.
library: Specify the library that becomes the current library during the
process of automatic sign-on.

Automatic Sign-On Examples

These examples show how to use these parameters to request automatic sign-on:
To automatically sign on using your current user ID, specify:
STRPASTHR RMTLOCNAME(UNSECSYS) RMTUSER(\CURRENT) RMTPWD(MYPWD)

To automatically sign on to a secure location using your current user ID,

specify:
STRPASTHR RMTLOCNAME(SECSYS) RMTUSER(\CURRENT)

To automatically sign on to a secure location using your current user ID, run a
program, and return to the source system, specify:
STRPASTHR RMTLOCNAME(SECSYS) RMTUSER(\CURRENT)
RMTINLPGM(MYPGM) RMTINLMNU(\SIGNOFF)

To change the default value of one of the parameters, create a duplicate

STRPASTHR command, change the defaults in that duplicate command, and place
the duplicate command in a library located before the QSYS library in the system
library list. For example, you can issue the following commands:
CRTDUPOBJ OBJ(STRPASTHR) FROMLIB(QSYS) OBJTYPE(\CMD) TOLIB(yourlib)

CHGCMDDFT CMD(yourlib/STRPASTHR) NEWDFT('RMTUSER(\CURRENT)')

CHGSYSLIBL LIB(yourlib) OPTION(\ADD)

After these commands finish running, use either of the following commands to auto-
matically sign on to location SECSYS while using your current user ID:
STRPASTHR RMTLOCNAME(SECSYS)
QSYS/STRPASTHR RMTLOCNAME(SECSYS) RMTUSER(\CURRENT)

If you want this new command to be used by all the users on your system, use the
CHGSYSVAL command to change the QSYSLIBL system value and add the library
to the system library list.
Note: Do not change the IBM-supplied objects in the QSYS library.

7-6 Remote Work Station Support V4R1

Automatic Sign-On Requirements
Consider the following when using automatic sign-on support:
You cannot automatically sign on or off a system if it does not support the auto-
matic sign-on function. This function is not supported on systems at an OS/400
release earlier than Version 1 Release 2.0. Automatic sign-on is supported only
with either Release 5.1 or 6.0 of the System/36. Automatic sign-on is not sup-
ported for the System/38. If you attempt to pass through to a system that does
not support automatic sign-on, the target system ignores the automatic sign-on
data and the sign-on display appears.
If you specify security information that is not correct, the pass-through session
fails.
When you specify the RMTUSER value to request automatic sign-on to the
appropriate release (Version 1 Release 2.0 or later) with the correct security
information (RMTUSER and RMTPWD), automatic sign-on could still fail if the
target system rejects the sign-on attempt. If you are not successful, contact the
security officer of the target system to determine what you must change for
your automatic pass-through attempt to be accepted.
For more information about setting up the target system to allow automatic
sign-on using the QRMTSIGN system value, see Chapter 6, Work Manage-
ment Considerations for Display Station Pass-Through.
You cannot request automatic sign-on if you do either of the following:
– Specify more than one device on the APPC device (CNNDEV) parameter
– Specify a location name on the RMTLOCNAME parameter and any device
names on the CNNDEV parameter
If your session was established using the automatic sign-on support, the
SIGNOFF command works differently. When you are automatically signed on,
ending the job by using either the SIGNOFF command or another method
usually ends your pass-through session. This process occurs because pass-
through is intended to appear transparent to the user during automatic sign-on.
If you started an alternate job by using the TFRJOB command or a System
Request option 1 on the target system, your job becomes a part of a system
request pair. Using SIGNOFF does not end your session. If you end your ori-
ginal automatically signed-on session you are placed into the other job. When
this alternate job ends, your pass-through session ends, just as if you had auto-
matically signed on to that alternate job. For more information about alternate
jobs, see the discussion on using the ENDPASTHR command.

PASTHRSCN Parameter
If you want to design a menu with an option that requests a pass-through oper-
ation, such as one requesting the automatic sign-on function, you may want to
conceal the attempt to establish pass-through. The display option
(PASTHRSCN) parameter allows you to conceal the usual display that appears
when the pass-through session is being established. The PASTHRSCN param-
eter also allows you to conceal the informational messages sent to the display
before the pass-through session starts.
The allowed values of the PASTHRSCN parameter are:

Chapter 7. Display Station Pass-Through Considerations 7-7

*YES: The pass-through display and informational messages appear
before the pass-through connection occurs on the target system.
This value is the default.
*NO: The pass-through display and informational status messages that
usually appear before pass-through connection with the target
system occurs do not appear. Specify this value in the program to
achieve the transparent pass-through.

If you want to pass through to a secure location to simply run a program and
return to the source system, you could specify the following:
STRPASTHR RMTLOCNAME(SECSYS) RMTUSER(\CURRENT)
RMTINLPGM(MYPGM) RMTINLMNU(\SIGNOFF) PASTHRSCN(\NO)

Because you specified PASTHRSCN(*NO), neither the pass-through display

nor any informational messages usually sent by the pass-through programs
appear.

Pass-Through Sign-On Attempt Examples

The following sections present examples of pass-through attempts, with an
emphasis on automatic sign-on, and the results of those attempts. In these
sections, assume a user with a user profile named FRED has signed on to the
source system. Also assume that the target system is an AS/400 system with the
OS/400 Version 1 Release 2.0 program (or a later release) installed and the target
system verifies the password specified in the user password (RMTPWD) parameter.
For target systems with password security active, the password is valid only if it
matches the password specified for the remote user profile. (The target system
has password security active when it has a QSECURITY system value of 20 or
greater.) For target systems without password security active (with a QSECURITY
system value of 10), all passwords are considered valid.

Sign-On Specifying Remote User Profile as *NONE—Example

If FRED specifies RMTUSER(*NONE), the pass-through attempt does not request
automatic sign-on. Pass-through attempts from systems that cannot request auto-
matic sign-on have the same results as this example. The results depend on the
target system QRMTSIGN value.

If FRED specifies RMTUSER(*NONE), the following results occur for the specified
QRMTSIGN values:

Table 7-1 (Page 1 of 2). User Specifies RMTUSER(*NONE)

7-8 Remote Work Station Support V4R1

Table 7-1 (Page 2 of 2). User Specifies RMTUSER(*NONE)
QRMTSIGN Value Result
Program library The result depends on the program action.
Program Action Result
Return 0 No pass-through session occurs. A CPF8935 message is
sent to the user of the STRPASTHR command, and a job
log is created on the target system.
Return 1 User sees the sign-on display for the target system.
Return 2 User sees the sign-on display for the target system.

Sign-On Specifying Remote User Profile as *CURRENT—Example

If FRED specifies RMTUSER(*CURRENT), he can specify either
RMTPWD(*NONE) or RMTPWD(password). If FRED specifies RMTPWD(*NONE),
the remote location must be a secure location (with SECURELOC(*YES) specified
on the APPC device description), or he receives a CPD8905 error message. If
FRED specifies RMTPWD(password), the password must be valid for user profile
FRED on the target system, or FRED receives a CPF8936 error message. For
more information about the RMTUSER and RMTPWD parameters, see “Using the
STRPASTHR Command for AS/400 Automatic Sign-On” on page 7-3.

If FRED does not receive either error message, the following results occur for the
specified QRMTSIGN values:

Table 7-2. User Specifies RMTUSER(*CURRENT)

QRMTSIGN Value Result
*REJECT No pass-through session occurs. A CPF8935 message is sent to the user of the
STRPASTHR command, and a job log is created on the target system.
*FRCSIGNON User sees the sign-on display for the target system.
*SAMEPRF, *VERIFY User is automatically signed on.
Program library The result depends on the program action.
Program Action Result
Return 0 No pass-through session occurs. A CPF8937 message is
sent to the user of the STRPASTHR command, and a job
log is created on the target system.
Return 1 User sees the sign-on display for the target system.
Return 2 User is automatically signed on.

Sign-On Specifying an Individual Remote User—Example

If FRED specifies his own user profile, RMTUSER(FRED), he can specify either
RMTPWD(*NONE) or RMTPWD(password). If FRED specifies RMTPWD(*NONE),
he receives a CPF8905 error message because he must always specify a pass-
word when specifying a user profile name in the RMTUSER parameter. If he speci-
fies RMTPWD(password), the password must be valid for user profile FRED on the
target system, or FRED receives a CPF8936 error message.

Chapter 7. Display Station Pass-Through Considerations 7-9

If FRED does not receive either error message, the following results occur for the
specified QRMTSIGN values:

Table 7-3. User Specifies RMTUSER(Own Profile)

If FRED specifies RMTUSER(MARY), he can specify either RMTPWD(*NONE) or

RMTPWD(password). If he specifies RMTPWD(*NONE), he receives a CPF8905
error message because he must always specify a password when specifying a user
profile name in the RMTUSER parameter. If he specifies RMTPWD(password), the
password must be valid for the user profile MARY on the target system, or he
receives a CPF8936 error message.

If FRED does not receive either error message, the following results occur for the
specified QRMTSIGN values:

Table 7-4. User Specifies RMTUSER(Other Profile)

QRMTSIGN Value Result
*REJECT No pass-through session occurs. A CPF8935 message is sent to the user of the
STRPASTHR command, and a job log is created on the target system.
*FRCSIGNON User sees the sign-on display for the target system.
*SAMEPRF No pass-through session occurs. A CPF8936 message is sent to the user of the
STRPASTHR command and a job log is created on the target system.
*VERIFY User is automatically signed on.
Program library The result depends on the program action.
Program Action Result
Return 0 No pass-through session occurs. A CPF8937 message is
sent to the user of the STRPASTHR command, and a job
log is created on the target system.
Return 1 User sees the sign-on display for the target system.
Return 2 User is automatically signed on.

7-10 Remote Work Station Support V4R1

APPC and APPN Considerations for Pass-Through
This section discusses the capabilities and limitations of the display station pass-
through function when using advanced program-to-program communications
(APPC) and Advanced Peer-to-Peer Networking (APPN) support.

Low-Entry Networking Nodes

A low-entry networking node uses the node type 2.1 architecture without APPN
extensions. A type 2.1 node is a system, such as an AS/400 system, that supports
local users and system functions to allow participation in an APPN network.

A low-entry networking node can participate in an APPN network using the services
of an attached network node server (a system that provides services to other
systems). However, the user at the low-entry networking node must specifically
configure all the remote locations with which communications occur as if they exist
at the network node server. The ability of a low-entry networking node to use the
APPN network varies, depending on the specific use. Examples of a low-entry net-
working node are:
System/38
System/36 without the APPN feature
An AS/400 system configured not to use APPN support (APPN(*NO) specified
in the controller description)
A personal computer

Figure 7-1 provides an example of low-entry networking nodes. Three specific

systems are shown.

..........................................
. .
LEN1 . ┌───────────┐ .
┌────┐ . │ ND CD │ .
│D1 │ . │┌──┐ ┌────┐│ .
│┌──┐├────┐. ││ ├─┤\LEN││ ┌─── ... NNZ .
││L1││ └────┤│ │ │LEN1│├────┘ ┌────┐ .
││ ││ . │└──┘ └────┘│ . │┌──┐│ .
││N1││ . │ │ . ││N1││ .
│└──┘│ . │ RMTLOCLST │ . ││ ││ .
└────┘ . │ │ . ┌─── ... ─┤└──┘│ .
. │┌────┬────┐├─────┘ └────┘ .
. ││LOC │CP ││ .
. │├────┼────┤│ .
. ││L1 │LEN1││ .
. ││ │ ││ .
. ││ │ ││ .
. │└────┴────┘│ .
. │ │ .
. └───────────┘ APPN Network .
. .
..........................................

Figure 7-1. Low-Entry Network Nodes Example

The following discussion pertains to Figure 7-1.

Chapter 7. Display Station Pass-Through Considerations 7-11

System LEN1 is a low-entry networking system. LEN1 may be a System/38 or
an AS/400 system that is connected to the APPN network using a nonnet-
working APPC device, or may be a System/36 using an APPC subsystem con-
figuration. (If LEN1 is a System/36, then the device description D1 represents
the corresponding System/36 configuration objects.)
D1 is a device description, contained in LEN1, used for a nonnetworking APPC
device. This device description specifies that it is associated with a local
location name of L1, and connects to remote location named N1.
System NNA is a network node that is serving location L1 on LEN1. NNA
informs the remainder of the APPN network that any traffic intended for location
L1 should be directed to NNA. Both the System/36 and the AS/400 system can
be network nodes, but this example assumes that NNA is an AS/400 system.
The name LEN1 is not configured on the system named LEN1, but is actually
the control point name used in defining the locations on system LEN1. Specify
this control point name when you create the APPC controller on the serving
network node, system NNA. For more information about configuring control
point names and serving network nodes, refer to the APPN Support book.
To configure system NNA as the network node serving location L1 on system
LEN1, do the following:
1. Create the controller description that is named CD and is associated with
the communications line description named ND using the low-entry net-
working value on the node type (NODETYPE) parameter of the Create
Controller (APPC) (CRTCTLAPPC) command. (*LENNODE is represented
as *LEN in Figure 7-1 on page 7-11.)
2. Add an entry for location L1 (on the LEN1 control point) to the APPN
remote location configuration list. To add this entry, use the Add Configura-
tion List Entry (ADDCFGLE), the Work with Configuration List (WRKCFGL),
or the Change Configuration List (CHGCFGL) command.
If the APPN remote location configuration list does not already exist on the
system, you can create this list with the Create Configuration List
(CRTCFGL) command, specifying *APPNRMT for the TYPE parameter.
System NNZ is the system in the APPN network with the location name N1, or
serving location N1, if N1 is a location on another low-entry networking node.
System NNZ can be either a System/36 using an APPN subsystem configura-
tion or an AS/400 system.
To pass-through from LEN1 to NNZ, do the following:
– If LEN1 is an AS/400 system, specify CNNDEV(D1) with the Start Pass-
Through (STRPASTHR) command.
– If LEN1 is a System/38, specify CNNDEV(D1) with the Begin Pass-Through
(BGNPASTHR) command.
Note: If LEN1 is a System/38 or an AS/400 system connected to the
network using a nonnetworking device, a unique nonnetworking
device must be created on LEN1 for each location in the APPN
network you might want to pass through.
For example, to use pass-through between LEN1 and NNA, a new APPC
device must be created on LEN1 with one of the location names on NNA
specified as the remote location in that nonnetworking APPC device.

7-12 Remote Work Station Support V4R1

– If LEN1 is a System/36, specify N1 on the remote location prompt. Even if
there are many systems between LEN1 and NNZ, system NNA sets up the
route from itself to NNZ.
To pass through from NNZ to LEN1, do the following:
- If NNZ is a System/36, specify RMTLOCNAME(L1) on the System/36
PASSTHRU procedure.
- If NNZ is an AS/400 system, specify RMTLOCNAME(L1) with the
STRPASTHR command to use pass through from NNZ to LEN1.

The example programs in Configuring a System/38 in an APPN Network—Example

show the commands to create the configuration described in Figure 7-1 on
page 7-11. In these programs, system LEN1 is a System/38 and systems NNA and
NNZ are AS/400 systems.

Only the configuration commands needed to connect system LEN1 to system NNA
and to define location N1 on system NNZ are shown. Systems NNA and NNZ also
need configurations for attaching to the APPN network. NNZ needs to have a
virtual work station controller and at least one virtual display device created. For
more APPC configuration examples, see the APPN Support book and the APPC
Programming book. The System/38 Environment Programming book discusses con-
figuring for display station pass-through with more information for configuring your
system for these examples.

Printer Output from a Target System

To receive your printer output, use an object distribution spooled file. No specific
action, such as entering a command, is needed to receive a spooled file. When it
arrives at your system, the spooled file is placed on the output queue specified in
your user profile. Both the user sending the distribution and you are notified of the
arrival of a spooled file.

For more information about object distribution and spooled output, refer to the topic
about sending and receiving spooled files in the SNA Distribution Services book.

Remote Printer Pass-Through

The Start Remote Writer (STRRMTWTR) command starts a spooling writer that
sends spooled files from an output queue to a remote system.
If the output queue is configured for SNADS, the Send Network Spooled File
(SNDNETSPLF) command is used to transfer the data.
If the output queue is configured for TCP/IP, the Send TCP/IP Spooled File
(SNDTCPSPLF) command is used to transfer the data.

For more information about remote printer pass-through, see the Printer Device
Programming book.

Chapter 7. Display Station Pass-Through Considerations 7-13

7-14 Remote Work Station Support V4R1
Chapter 8. Display Station Pass-Through Configuration
Scenario
This chapter shows a configuration scenario for display station pass-through used
in an APPN network of five systems in five cities.

APPN Configuration Scenario for Display Station Pass-Through

Figure 8-1 is an illustration of the network and the systems used in each city.

C D E
AS/400
System/36 System/38 (Model)
System

A
AS/400
System SEC SEC SEC (Datalink Role)
B M M M
C1 D1 E1
AS/400
Point-to-point
System
Circuit
M M
Multipoint Circuit
NEG PRI
M A1 A2

NEG
B1

M=Modem
IBM 7861-015
9600 BPS, 1 Port
RV3P109-0

Figure 8-1. Pass-Through Configuration Example

Table 8-1 lists the vital statistics for each city and its system and how each system
is linked to the series.

Table 8-1 (Page 1 of 2). Pass-Through Configuration Text

System B A C D E
Location Denver Rochester Chicago Atlanta Boston
System name DENVER ROCHESTE CHICAGO ATLANTA BOSTON
Local location DENVER ROCHESTE CHICAGO ATLANTA BOSTON
name
Control point DENVER ROCHESTE CHICAGO ATLANTA BOSTON
name
Node type NETNODE NETNODE NETNODE NETNODE LENNODE
Exchange identi- 056000B1 056000A1 056000C1 03E000D1 022000E1
fier 056000A2
Line description PTP PTP MTPP MTPP MTPP
MTPP

 Copyright IBM Corp. 1997 8-1

Table 8-1 (Page 2 of 2). Pass-Through Configuration Text
System B A C D E
Location Denver Rochester Chicago Atlanta Boston
Controller ROCHESCTL DENVERCTL ROCHESCTL ROCHESCTL
description CHICAGOCTL
ATLANTACTL
BOSTONCTL

A point-to-point line is used between Rochester and Denver. A multipoint line is

used to connect Rochester, Chicago, Atlanta, and Boston with Rochester as the
central site.

The point-to-point line must carry a high volume of data traffic between Rochester
and Denver so a dedicated, non-switched line between them is necessary.

The multipoint line takes advantage of multipoint capabilities by allowing a single

circuit to go from Rochester to Chicago, Atlanta, and Boston.

Denver Configuration
Figure 8-2 is an example of a control language (CL) program that could be used to
configure the Denver AS/400 system in Figure 8-1 on page 8-1 for use in the
APPN network.

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ System: AS/4ðð system in Denver \/
/\ \/
/\ Configuration: \/
/\ Line(PTP): SDLC non-switched \/
/\ EXCHID ð56ðððB1 \/
/\ \/
/\ Controller(ROCHESTCTL) \/
/\ Remote control point name: ROCHESTE \/
/\ \NETNODE \/
/\ Attaches to EXCHID: ð56ðððA1 \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

PGM
/\ Create the LINE \/
CRTLINSDLC LIND(PTP) + /\ Call the line PTP \/
RSRCNAME(LINð11) + /\ Resource name of port \/
EXCHID(ð56ðððB1) + /\ System exchange ID \/
MODEM(\IBMLPDA2) + /\ Modem type \/
DUPLEX(\FULL) + /\ \/
TEXT('Point-to-point line to Rochester')

Figure 8-2 (Part 1 of 2). CL Program for Configuring Denver AS/400 System

8-2 Remote Work Station Support V4R1

/\ Create the CONTROLLER \/
CRTCTLAPPC CTLD(ROCHESTCTL) + /\ Controller Description \/
LINKTYPE(\SDLC) + /\ Link type \/
LINE(PTP) + /\ Attached nonswitched line\/
RMTCPNAME(ROCHESTE) +/\ Remote control point \/
EXCHID(ð56ðððA1) + /\ System exchange ID \/
STNADR(B1) + /\ Station address \/
NODETYPE(\NETNODE) + /\ APPN node type \/
TEXT('For the AS/4ðð system in Rochester')

ENDPGM

Figure 8-2 (Part 2 of 2). CL Program for Configuring Denver AS/400 System

Rochester Configuration
Figure 8-3 is an example of a control language (CL) program that could be used to
configure the Rochester AS/400 system in Figure 8-1 on page 8-1 for use in the
APPN network.

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ System: AS/4ðð system in Rochester \/
/\ \/
/\ Configuration: \/
/\ Line(PTP): SDLC non-switched \/
/\ EXCHID ð56ðððA1 \/
/\ \/
/\ Line(MTPP): SDLC non-switched \/
/\ EXCHID ð56ðððA2 \/
/\ \/
/\ Controller(DENVERCTL) \/
/\ Remote control point name: DENVER \/
/\ \NETNODE \/
/\ Attaches to EXCHID: ð56ðððB1 \/
/\ \/

Figure 8-3 (Part 1 of 3). CL Program for Configuring Rochester AS/400 System

Chapter 8. Display Station Pass-Through Configuration Scenario 8-3

/\ Controller(INDIANACTL) \/
/\ Remote control point name: INDIANA \/
/\ \NETNODE \/
/\ Attaches to EXCHID: ð56ðððC1 \/
/\ \/
/\ Controller(PITTSBUCTL) \/
/\ Remote control point name: PITTSBUR \/
/\ \NETNODE \/
/\ Attaches to EXCHID: ð3EðððD1 \/
/\ \/
/\ Controller(BOSTONCTL) \/
/\ Remote control point name: BOSTON \/
/\ \LENNODE \/
/\ Attaches to EXCHID: ð22ðððE1 \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

PGM
/\ Create the LINEs \/
CRTLINSDLC LIND(PTP) + /\ Call the line PTP \/
RSRCNAME(LINð12) + /\ Resource name of port \/
EXCHID(ð56ðððA1) + /\ System exchange ID \/
MODEM(\IBMLPDA2) + /\ Modem type \/
DUPLEX(\FULL) + /\ \/
TEXT('Point-to-point line to Denver')

CRTLINSDLC LIND(MTPP) + /\ Call the line MTPP \/

RSRCNAME(LINð22) + /\ Resource name of port \/
ROLE(\PRI) + /\ Data Link role \/
CNN(\MP) + /\ Connection type \/
EXCHID(ð56ðððA2) + /\ System exchange ID \/
MAXCTL(3) + /\ Maximum controllers \/
MODEM(\IBMLPDA2) + /\ Modem type \/
DUPLEX(\FULL) + /\ \/
TEXT('Multipoint line to Indianapolis, +
Pittsburgh, Bosto')

Figure 8-3 (Part 2 of 3). CL Program for Configuring Rochester AS/400 System

8-4 Remote Work Station Support V4R1

/\ Create the CONTROLLERs \/
CRTCTLAPPC CTLD(DENVERCTL) + /\ Controller Description \/
LINKTYPE(\SDLC) + /\ Link type \/
LINE(PTP) + /\ Attached nonswitched line\/
RMTCPNAME(DENVER) + /\ Remote control point \/
EXCHID(ð56ðððB1) + /\ System exchange ID \/
STNADR(A1) + /\ Station address \/
NODETYPE(\NETNODE) + /\ APPN node type \/
TEXT('For the AS/4ðð system in Denver')

CRTCTLAPPC CTLD(INDIANACTL) + /\ Controller Description \/

LINKTYPE(\SDLC) + /\ Link type \/
LINE(MTPP) + /\ Attached nonswitched line\/
RMTCPNAME(INDIANA) + /\ Remote control point \/
EXCHID(ð56ðððC1) + /\ System exchange ID \/
STNADR(C1) + /\ Station address \/
ROLE(\SEC) + /\ Data link role \/
TEXT('For the AS/4ðð system in Indianapolis')
CRTCTLAPPC CTLD(PITTSBUCTL) + /\ Controller Description \/
LINKTYPE(\SDLC) + /\ Link type \/
LINE(MTPP) + /\ Attached nonswitched line\/
RMTCPNAME(PITTSBUR) +/\ Remote control point \/
EXCHID(ð3EðððD1) + /\ System exchange ID \/
STNADR(D1) + /\ Station address \/
ROLE(\SEC) + /\ Data link role \/
NODETYPE(\NETNODE) + /\ APPN node type \/
TEXT('For the S/36 system in Pittsburgh')

CRTCTLAPPC CTLD(BOSTONCTL) + /\ Controller Description \/

LINKTYPE(\SDLC) + /\ Link type \/
LINE(MTPP) + /\ Attached nonswitched line\/
RMTCPNAME(BOSTON) + /\ Remote control point \/
EXCHID(ð22ðððE1) + /\ System exchange ID \/
STNADR(E1) + /\ Station address \/
ROLE(\SEC) + /\ Data link role \/
NODETYPE(\LENNODE) + /\ APPN node type \/
TEXT('For the S/38 system in Boston')

ENDPGM

Figure 8-3 (Part 3 of 3). CL Program for Configuring Rochester AS/400 System

Chicago Configuration
Figure 8-4 on page 8-6 is an example of a control language (CL) program that
could be used to configure the Chicago AS/400 system in Figure 8-1 on page 8-1
for use in the APPN network.

Chapter 8. Display Station Pass-Through Configuration Scenario 8-5

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ System: AS/4ðð system in Indianapolis \/
/\ \/
/\ Configuration: \/
/\ Line(MTPP): SDLC non-switched \/
/\ EXCHID ð56ðððC1 \/
/\ \/
/\ Controller(ROCHESTCTL) \/
/\ Remote control point name: ROCHESTE \/
/\ \NETNODE \/
/\ Attaches to EXCHID: ð56ðððA2 \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

PGM
/\ Create the LINE \/
CRTLINSDLC LIND(MTPP) + /\ Call the line MTPP \/
RSRCNAME(LINð11) + /\ Resource name of port \/
ROLE(\SEC) + /\ Data Link role \/
CNN(\MP) + /\ Connection type \/
EXCHID(ð56ðððC1) + /\ System exchange ID \/
MAXCTL(1) + /\ Maximum controllers \/
MODEM(\IBMLPDA2) + /\ Modem type \/
DUPLEX(\HALF) + /\ \/
TEXT('Multipoint line to Rochester')

/\ Create the CONTROLLER \/

CRTCTLAPPC CTLD(ROCHESTCTL) + /\ Controller Description \/
LINKTYPE(\SDLC) + /\ Link type \/
LINE(MTPP) + /\ Attached nonswitched line\/
RMTCPNAME(ROCHESTE) +/\ Remote control point \/
EXCHID(ð56ððA21) + /\ System exchange ID \/
STNADR(C1) + /\ Station address \/
ROLE(\PRI) + /\ Data link role \/
TEXT('For the AS/4ðð system in Rochester')

ENDPGM

Figure 8-4. CL Program for Configuring Chicago AS/400 System

Atlanta Configuration
The System/36 used in Atlanta in Figure 8-1 on page 8-1 does not support the use
of CL programs for configuration. This system instead uses a menu-driven inter-
face. For information on how to configure a System/36 in an APPN environment,
see the Using S/36 Communications Guide.

Boston Configuration
Figure 8-5 on page 8-7 is an example of a control language (CL) program that
could be used to configure the Boston System/38 in Figure 8-1 on page 8-1 for
use in the APPN network.

8-6 Remote Work Station Support V4R1

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ System: S/38 system in Boston \/
/\ \/
/\ Configuration: \/
/\ Line(MTPP): SDLC non-switched \/
/\ EXCHID ð22ðððE1 \/
/\ \/
/\ Controller(ROCHESTCTL) \/
/\ Control unit address: A22ð \/
/\ Attaches to EXCHID: ð56ðððA2 \/
/\ \/
/\ Device(ROCHESTDEV) \/
/\ Device address: ð1A22ð \/
/\ \/
/\ Device(DENVERDEV) \/
/\ Device address: ð2A22ð \/
/\ \/
/\ Device(CHICAGODEV) \/
/\ Device address: ð3A22ð \/
/\ \/
/\ Device(ATLANTADEV) \/
/\ Device address: ð4A22ð \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

PGM
/\ Create the LINE \/
CRTLIND LIND(MTPP) + /\ Call the line MTPP \/
LINNBR(2ð) + /\ Resource name of port \/
TYPE(\SDLCS) + /\ SDLC Secondary \/
CNN(\MP) + /\ Connection type \/
RATE(96ðð) + /\ Data rate \/
EXCHID(ð22ðððE1) + /\ System exchange ID \/
WIRE(4) + /\ 4-wire connection \/
STNADR(E1) /\ Station address \/

/\ Create the CONTROLLER \/

CRTCUD CUD(ROCHESTCTL) + /\ Controller Description \/
TYPE(\PEER) + /\ Using APPC \/
MODEL(ðððð) + /\ Model always ðððð w \PEER\/
CTLADR(A22ð) + /\ Unique address of CTL \/
LINE(MTPP) + /\ Attached nonswitched line\/
EXCHID(ð56ðððA2) /\ System exchange ID \/

Figure 8-5 (Part 1 of 3). CL Program for Configuring Boston System/38

Chapter 8. Display Station Pass-Through Configuration Scenario 8-7

/\ Create the DEVICE \/
CRTDEVD DEVD(ROCHESTDEV) + /\ Device Description \/
DEVADR(ð1A22ð) + /\ Unique address for device\/
DEVTYPE(\PEER) + /\ Using APPC \/
MODEL(ðððð) + /\ Model always ðððð w \PEER\/
CTLU(ROCHESTCTL) + /\ Attached to CTL UNIT \/
LCLLU(BOSTON) + /\ Local LU name \/
RMTLU(ROCHESTE) /\ Attached to remote LU nam\/

/\ Add a MODE to the device \/

ADDDEVMODE DEVD(ROCHESTDEV) + /\ Add a mode to device \/
MODE(\BLANK) + /\ The mode is \blank \/
MAXCNV(8) /\ Max concurrent conversati\/

/\ Create the DEVICE \/

CRTDEVD DEVD(DENVERDEV) + /\ Device Description \/
DEVADR(ð2A22ð) + /\ Unique address for device\/
DEVTYPE(\PEER) + /\ Using APPC \/
MODEL(ðððð) + /\ Model always ðððð w \PEER\/
CTLU(ROCHESTCTL) + /\ Attached to CTL UNIT \/
LCLLU(BOSTON) + /\ Local LU name \/
RMTLU(DENVER) /\ Attached to remote LU nam\/

/\ Add a MODE to the device \/

ADDDEVMODE DEVD(DENVERDEV) + /\ Add a mode to device \/
MODE(\BLANK) + /\ The mode is \blank \/
MAXCNV(8) /\ Max concurrent conversati\/

/\ Create the DEVICE \/

CRTDEVD DEVD(CHICAGODEV) + /\ Device Description \/
DEVADR(ð3A22ð) + /\ Unique address for device\/
DEVTYPE(\PEER) + /\ Using APPC \/
MODEL(ðððð) + /\ Model always ðððð w \PEER\/
CTLU(ROCHESTCTL) + /\ Attached to CTL UNIT \/
LCLLU(BOSTON) + /\ Local LU name \/
RMTLU(CHICAGO) /\ Attached to remote LU nam\/

/\ Add a MODE to the device \/

ADDDEVMODE DEVD(CHICAGODEV) + /\ Add a mode to device \/
MODE(\BLANK) + /\ The mode is \blank \/
MAXCNV(8) /\ Max concurrent conversats\/

Figure 8-5 (Part 2 of 3). CL Program for Configuring Boston System/38

8-8 Remote Work Station Support V4R1

/\ Create the DEVICE \/
CRTDEVD DEVD(ATLANTADEV) + /\ Device Description \/
DEVADR(ð4A22ð) + /\ Unique address for device\/
DEVTYPE(\PEER) + /\ Using APPC \/
MODEL(ðððð) + /\ Model always ðððð w \PEER\/
CTLU(ROCHESTCTL) + /\ Attached to CTL UNIT \/
LCLLU(BOSTON) + /\ Local LU name \/
RMTLU(ATLANTA) /\ Attached to remote LU nam\/

/\ Add a MODE to the device \/

ADDDEVMODE DEVD(ATLANTADEV) + /\ Add a mode to device \/
MODE(\BLANK) + /\ The mode is \blank \/
MAXCNV(8) /\ Max concurrent conversati\/

ENDPGM

Figure 8-5 (Part 3 of 3). CL Program for Configuring Boston System/38

Configuring a System/38 in an APPN Network—Example

This section provides example programs for configuring a System/38 in the fol-
lowing Advanced Peer-to-Peer Networking (APPN) networks:
System/38 connecting to an AS/400 system
AS/400 system connecting to and serving a System/38

This section also provides an example program for adding a local location to an
AS/400 system APPN local location configuration list.

System/38 Attached to an AS/400 System

Figure 8-6 on page 8-10 is a program that shows how to set up the configuration
on a System/38 that connects to an AS/400 system. An example of this configura-
tion is shown in Figure 7-1 on page 7-11.

Chapter 8. Display Station Pass-Through Configuration Scenario 8-9

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ System: System/38 (LEN1) \/
/\ \/
/\ Configuration: \/
/\ Line: SDLC non-switched secondary \/
/\ EXCHID ð22ðððð1 \/
/\ Control Unit: Attaches to AS/4ðð EXCHID ð56ðððð1 \/
/\ Device: Local LU L1 \/
/\ Remote LU N1 \/
/\ \/
/\ Note : You must add this device as a communication \/
/\ entry to the appropriate subsystem by \/
/\ using the ADDCMNE command. \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
PGM
/\ Create the line that connects S/38 (LEN1) to AS/4ðð system (NNA)\/
CRTLIND LIND(LEN1TONNA) + /\ Call the line LEN1TONNA \/
LINNBR(21) + /\ Operational Unit 21 \/
TYPE(\SDLCS) + /\ SDLC Secondary \/
CNN(\PP) + /\ Non-switched point-to-point \/
RATE(96ðð) + /\ Line speed 96ðð bps \/
WIRE(4) + /\ 4-wire connection \/
STNADR(ð1) + /\ Must match NNA CTL STNADR \/
EXCHID(ð22ðððð1) /\ Exchange ID for the system \/
/\ Create the CUD that attaches S/38 (LEN1) to AS/4ðð system (NAA) \/
CRTCUD CUD(LEN1TONNA) + /\ Call the ctl unit LEN1TONNA \/
TYPE(\PEER) + /\ Using APPC \/
MODEL(ðððð) + /\ MODEL always ðððð with \PEER \/
CTLADR(ð121) + /\ Unique address of the ctl unit\/
LINE(LEN1TONNA) + /\ Attach to line LEN1TONNA \/
EXCHID(ð56ðððð1) /\ Exchange ID remote controller \/
/\ Create the device connecting LU L1 (LEN1) to LU N1 (NNZ) \/
CRTDEVD DEVD(D1) + /\ The device is called D1 \/
DEVADR(ð1ð121) + /\ Unique address of the device \/
DEVTYPE(\PEER) + /\ Using APPC \/
MODEL(ðððð) + /\ MODEL always ðððð with \PEER \/
CTLU(LEN1TONNA) + /\ Attach to ctl unit LEN1TONNA \/
LCLLU(L1) + /\ Local LU name is L1 \/
RMTLU(N1) /\ Attach to remote LU name N1 \/
/\ Add a mode to the device description D1 \/
ADDDEVMODE DEVD(D1) + /\ Add a mode to device D1 \/
MODE(\BLANK) + /\ The mode is \BLANK \/
MAXSSN(8) + /\ Maximum concurrent sessions \/
PREBNDSSN(1) + /\ Number preestablished sessions\/
MAXSRCSSN(4) + /\ Maximum source sessions \/
MAXCNV(8) /\ Max concurrent conversations \/
ENDPGM

Figure 8-6. System/38 Attached to an AS/400 System Program Example

AS/400 System Attached to a System/38

Figure 8-7 on page 8-11 is a program that shows how to set up the configuration
on an AS/400 system that connects to and serves a System/38 that is acting as a
low-entry networking node. An example of this configuration is shown in Figure 7-1
on page 7-11.

8-10 Remote Work Station Support V4R1

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ System: AS/4ðð system (NNA) \/
/\ \/
/\ Configuration: \/
/\ Line: SDLC non-switched primary \/
/\ EXCHID ð56ðððð1 \/
/\ Controller : Attaches to S/38 EXCHID ð22ðððð1 \/
/\ APPN capable, supporting \LENNODE \/
/\ with remote control point name LEN1 \/
/\ on the default network. \/
/\ Devices : none; these are created dynamically by APPN support\/
/\ Mode: A mode must exist on this system which matches the \/
/\ mode on device D1 on the S/38. However, because the \/
/\ mode used for device D1 is \BLANK, and that mode \/
/\ matches the IBM-supplied mode BLANK on the AS/4ðð \/
/\ system, no mode description needs to be created. \/
/\ Configuration List: Add Remote Location L1 on \/
/\ Control Point LEN1 \/
/\ \/
/\ Note : If you are adding configuration \/
/\ list entries in an interactive \/
/\ environment, rather than in \/
/\ a program such as this, you \/
/\ may find that the "Change" \/
/\ option on the menu presented by \/
/\ the WRKCFGL command is easier \/
/\ to use than the ADDCFGLE command. \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
PGM
/\ Create the line that connects AS/4ðð system (NNA) to S/38 (LEN1)\/
CRTLINSDLC LIND(ND) + /\ Call the line ND \/
RSRCNAME(LINð11) + /\ Resource name of port \/
ROLE(\PRI) + /\ Assume primary role \/
EXCHID(ð56ðððð1) /\ System exchange ID \/
/\ Create the controller which will designate LEN1 a \LENNODE \/
CRTCTLAPPC CTLD(CD) + /\ Name controller CD \/
LINKTYPE(\SDLC) + /\ Attached to an SDLC line \/
LINE(ND) + /\ Attached to line ND \/
ROLE(\SEC) + /\ Remote side is secondary \/
STNADR(ð1) + /\ Remote station address \/
EXCHID(ð22ðððð1) + /\ Remote exchange ID \/
APPN(\YES) + /\ APPN support is being used \/
NODETYPE(\LENNODE) + /\ Remote system is a LEN node \/
RMTCPNAME(LEN1) + /\ Assign remote control point \/
RMTNETID(\NETATR) /\ Use the default network ID \/
/\ Add an entry to the APPN remote configuration list for location \/
/\ L1 in the default network served by system NNA. Define L1 to \/
/\ reside on control point LEN1, also in the default network. \/
ADDCFGLE TYPE(\APPNRMT) APPNRMTE((L1 \NETATR NNA LEN1))
ENDPGM

Figure 8-7. AS/400 System Attached to System/38 Program Example

Note: This program assumes the local location list exists on the system and need
not be created.

Adding a Local Location to an AS/400 APPN Configuration

Figure 8-8 on page 8-12 is a program that shows how to add a local location to an
AS/400 APPN local location configuration list. This example corresponds to the
example network in Figure 7-1 on page 7-11.

Chapter 8. Display Station Pass-Through Configuration Scenario 8-11

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ System: AS/4ðð system (NNZ) \/
/\ \/
/\ Configuration: \/
/\ Mode: A mode must exist on this system which matches the \/
/\ mode on device D1 on the S/38. However, because the \/
/\ mode used for device D1 is \BLANK, and that mode \/
/\ matches the IBM-supplied mode BLANK on the AS/4ðð \/
/\ system, no mode description needs to be created. \/
/\ Configuration List: Add Local Location N1 \/
/\ Notes : This ADDCFGLE would not be necessary if the \/
/\ control point name or the default local location \/
/\ name of system NNZ was N1. \/
/\ \/
/\ : This program assumes that location N1 is on \/
/\ system NNZ, not on a low-entry networking node \/
/\ served by NNZ. \/
/\ \/
/\ : If you are adding configuration list entries in an \/
/\ interactive environment, rather than in a program \/
/\ such as this, you may find that the "Change" \/
/\ option on the menu presented by the WRKCFGL \/
/\ command is easier to use than the ADDCFGLE command.\/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
PGM
/\ Add an entry to the APPN local configuration list for \/
/\ location N1. \/
ADDCFGLE TYPE(\APPNLCL) APPNLCLE((N1))
ENDPGM

Figure 8-8. Adding a Local Location to an AS/400 APPN Configuration

Note: This program assumes the local location list exists on the system and need
not be created.

Pass-Through in a Multiple Product Network

This section provides an example of a network of systems to clarify the effect of the
network configuration on the display station pass-through function used in that
network.

This example may be helpful in determining which method of configuration is the

easiest for the pass-through users to use. The pass-through user may also gain a
better understanding of how to specify device and location names on the various
pass-through commands to determine the route to the target system.

Figure 8-9 on page 8-14 shows a network of seven systems:

Two System/38s, labeled S38A and S38B
Two System/36s, labeled S36A and S36B
Two AS/400 systems, labeled AS400A and AS400B
One system, labeled SXX, whose system type is not important in this example,
except that it must be a System/36, System/38, or an AS/400 system
Note: Each system has many configuration objects not mentioned in the figure or
in the following examples. For example, for each APPC device in each
system in the figure, a corresponding APPC device in the system containing
the remote location is shown in the device.

8-12 Remote Work Station Support V4R1

Only the communications objects that are used in the example are discussed. Two
nonnetworking devices are shown on system S38A. Device DEV1 has a local
logical unit (LU) name (S38A) and a remote LU name (S38B). Device DEV2 has a
local LU name (S38A) and a remote LU name (AS400B1). An LU name on
System/38 corresponds to a location name on a System/36 and an AS/400 system.

There are no nonnetworking devices shown on system AS400A. It is a network

node in the APPN network with S36A and AS400B. System AS400A acts as the
serving network node for location S38A.

System S36A does not have any devices because it is a System/36. It is a network
node in the APPN network with AS400A and AS400B.

System AS400B shows a nonnetworking device. Device DEV4 has a local location
name AS400B1 and a remote location name S36B. System AS400B acts as the
serving network node for location S38B. AS400B2 is the name of another location
on system AS400B.

System S38B shows one nonnetworking device. Device DEV5 has a local LU name
S38B and a remote LU name SXX.

System S36B does not have any devices because it is a System/36. For the pur-
poses of this example, assume S36B is a System/36 that is not using an APPN
subsystem configuration. Based on these assumptions made about the network,
see Figure 8-9 on page 8-14 for some of the possible ways to pass through from
one system to another. (Only the parameters associated with choosing the target
system are specified.)

Chapter 8. Display Station Pass-Through Configuration Scenario 8-13

System/38
┌───────────────────────┐
│Local Location S38A │
System S38A │Devices │
│ DEV1 │
│ DEV2 │
└──────────┬────────────┘
│
└─┐
AS/4ðð System│
┌────────────┴───────────┐
System S36A │Remote Location Served │
│ S38A │
└─────────┬──────────────┘
│
└─┐
System/36 │
┌───────────┴────────────┐
System S36B │Remote Location Served │
│ None │
└──────────┬─────────────┘
│
└──┐
│
AS/4ðð System│
┌────────────┴────────────┐
│Local Locations │
│ AS4ððB1 │
│ AS4ððB2 │
System AS4ððB│Devices │
│ DEV4 │
│Remote Locations Served │
│ S38B │
└────┬────────────────────┤
│ │
└──┐ └───┐
System/38│ │ System/36
┌─────────┴─────────┐ ├──────────────────────┐
│Local LU Name S38B │ │Local Location S36B │
System S38B│Device │System S36B│Remote Location Served│
│ DEV5 │ │ None (not APPN) │
└──────────────┬────┘ ├──────────────────────┘
│ │
└──┐ └──┐
│ │
┌─┴────────────────┤
System SXX│Local Location SXX│
└──────────────────┘

Figure 8-9. Complex Example of Pass-Through Networking

From S38A to S38B, using the Begin Pass-Through (BGNPASTHR) command:

– CNNDEV(DEV1): DEV1 is the only device you need to specify because

DEV1 specifies the local location name S38A (served by system AS400A’s
APPN network node function) and specifies the remote location name S38B
(served by system AS400B’s APPN network node function), and because
S36A is an APPN networking node.
Notice that only one device is specified, but several systems are in the
route to the target system.
From AS400B to S38B, using the Start Pass-Through (STRPASTHR)
command:
– RMTLOCNAME(S38B): AS400B serves remote location S38B; therefore,
simply specifying the location name sets up the route. You can reach S38B
from any of the APPN-capable systems in the network (AS400A, S36A, and
AS400B) by specifying RMTLOCNAME(S38B) because a network node
serves that location.

8-14 Remote Work Station Support V4R1

From AS400B to S36B, using the STRPASTHR command:
– RMTLOCNAME(S36B): Specifying the location name sets up the route
because AS400B serves remote location S36B.
– CNNDEV(DEV4): You can specify this device because DEV4 is connected
directly to S36B, and DEV4 is a nonnetworking APPC device.
From AS400B to SXX, using the STRPASTHR command:
– RMTLOCNAME(S38B) CNNDEV(DEV5): APPN support finds the path to
S38B. Specify DEV5 to complete the path from S38B to SXX.
You cannot specify RMTLOCNAME(SXX) because SXX is not a location known
to any APPN network node in the network.
From S36A to SXX, using the Pass-Through (PASSTHRU) procedure:
– RMTLOCNAME(S38B) CNNDEV (DEV5): The remote location name S38B
in the node list member takes the route to system S38B, then DEV5 com-
pletes the route through S38B to SXX.

Chapter 8. Display Station Pass-Through Configuration Scenario 8-15

8-16 Remote Work Station Support V4R1
Part 2. Configuring for 5250 Remote Control Units
Chapter 9. Configuring 5250-Type Controllers—Scenario . . . . . . . . . . 9-1
5250 Remote Work Station Communications . . . . . . . . . . . . . . . . . . . . 9-1
Configuration of Remote Devices and 5394 Remote Control Units . . . . . . 9-2
SDLC Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Configuration of the AS/400 System . . . . . . . . . . . . . . . . . . . . . . . 9-4
Configuration Using the Command Prompt Displays . . . . . . . . . . . . 9-5
Creating the Line Description . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Creating the Controller Descriptions . . . . . . . . . . . . . . . . . . . . . . 9-7
The LOCADR Parameter Value Determination . . . . . . . . . . . . . . . . 9-8
Creating the Printer Device Descriptions . . . . . . . . . . . . . . . . . . . 9-8
Creating the Display Device Descriptions . . . . . . . . . . . . . . . . . . 9-10
Configuration Using CL Commands . . . . . . . . . . . . . . . . . . . . . . 9-11
Configuration of Controller Descriptions for Automatic Connection . . . . . 9-12
Automatic Dialing to a Remote Work Station Controller—Example . . . . . 9-13
Start Remote Display (STRRMTDSP) Command . . . . . . . . . . . . . 9-14
Attaching DBCS-Capable Devices to 5250 Controllers . . . . . . . . . . . . 9-14

Chapter 11. Configuring 5494 Remote Control Units . . . . . . . . . . . . 11-1

How the 5494 Remote Control Unit Works . . . . . . . . . . . . . . . . . . . . 11-1
Configuring the 5494 Remote Control Unit on the AS/400 System . . . . . . 11-3
Step 1: Configuring a Line to the Network . . . . . . . . . . . . . . . . . . 11-5
Step 2: Configuring a Controller Description . . . . . . . . . . . . . . . . . 11-5
Configuring an Advanced Program-to-Program Communications
Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Configuring an SNA Host Controller . . . . . . . . . . . . . . . . . . . . . 11-6
Step 3: Configuring a Remote Work Station Controller . . . . . . . . . . . 11-7
Step 4: Configuring Dependent Work Stations . . . . . . . . . . . . . . . . 11-9
Determining the LOCADR Parameter Value . . . . . . . . . . . . . . . . 11-9
Changing Device Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
AS/400 Configuration Examples for the 5494 Remote Control Unit . . . . 11-10
Synchronous Data Link Control Configuration Example . . . . . . . . . . 11-11
SDLC Configuration Matching Parameters . . . . . . . . . . . . . . . . . . 11-11
X.25 Configuration Example . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
X.25 Configuration Matching Parameters . . . . . . . . . . . . . . . . . . 11-13
Token-Ring Attachment Configuration Example . . . . . . . . . . . . . . . 11-14
Token-Ring Attachment Configuration Matching Parameters . . . . . . . 11-15
Managing the 5494 Remote Control Unit . . . . . . . . . . . . . . . . . . . . 11-16
Active APPC Subsystem Required . . . . . . . . . . . . . . . . . . . . . . 11-17

 Copyright IBM Corp. 1997

System Reference Codes and the 5494 Remote Control Unit . . . . . . 11-17
| Changing the 5494 Remote Control Unit Password . . . . . . . . . . . . 11-18
| Retrieving Vital Product Data . . . . . . . . . . . . . . . . . . . . . . . . . 11-18

Remote Work Station Support V4R1

Chapter 9. Configuring 5250-Type Controllers—Scenario
This chapter provides an example of a switched SDLC line used to connect an
AS/400 system to two 5394 Remote Control Units with several attached devices.
General considerations for using 5250-type controllers are discussed, including con-
siderations for attaching double-byte character set (DBCS) devices. See the Com-
munications Configuration book for more information about matching parameters
between the AS/400 system and these remote controllers.

5250 Remote Work Station Communications

Twinaxial, 5250-type remote controllers (5251-12, 5294, 5394, and 5494) can be
used to remotely attach display stations and printers to the AS/400 system. This
example describes the configuration shown in Figure 9-1 on page 9-2, using a
switched SDLC line to connect two 5394 Remote Control Units and several
attached devices to the AS/400 system.

The basic steps required for this configuration are:

1. Hardware setup and assignment of device addresses to the remote devices
2. 5394 configuration
3. AS/400 configuration, including:
Creating the line description (CRTLINSDLC command)
Creating the controller descriptions (CRTCTLRWS command)
Creating the device descriptions (CRTDEVDSP and CRTDEVPRT com-
mands)

This example assumes that all equipment is set up correctly. The discussion of the
configuration for the remote site is limited to describing dependencies shared
between the configuration of the remote controllers and the configuration of the
AS/400 system.

 Copyright IBM Corp. 1997 9-1

AS/400
System

Modem

Boston Chicago

Modem Modem

5394 5394

3196 4224 3180 4214

RV3P108-0

Figure 9-1. Remote Work Station Communications Example

Configuration of Remote Devices and 5394 Remote Control Units

Before configuring the 5394 Remote Control Units, the address of each of the
attached devices should be set. For example, 3180 display stations use the Setup
key and PF24 to set the device address; some types of display stations use
switches. The addresses of devices attached to the same port must be unique.

The 5394 Control Unit requires an attached display station for the configuration pro-
cedure. The configuration display for the 5394 Remote Control Unit located in
Boston is shown in Figure 9-2.

9-2 Remote Work Station Support V4R1

à ð
ð 1 2 3 4 5 6
---------------------------------------------------------------

ð/ . D . . . . .

1/ P . . . . . .

2/ . . . . . . .

AA-> ð BB->ð
1-> ðð 2-> ð4 3-> 1 ð 1 ð ð ð ð ð8-> ðA ð
P-> _ _
á ñ
Figure 9-2. 5394 Configuration Display-Boston

The top part of the display shows the device addresses (0-6) and the 5394 ports
(0-2) to which the devices are attached. Attached display stations are shown with a
D, printers with a P. For example, the configuration display for the 5394 controller in
Boston shows a display station with address 1 attached to port 0; a printer with
address 0 is attached to port 1.

The port assignments and device addresses shown on the 5394 configuration
display are used to determine the value specified for the LOCADR parameter on
the AS/400 CRTDEVDSP command later in the configuration procedure.

The fields shown at the bottom of the 5394 configuration display are used to
specify the type of communications to be used. The fields shown and the use of the
fields is dependent on the model of the controller and on the value specified for
Field AA. Field AA specifies whether the controller is to be used for SDLC, X.25, or
X.21 switched communications. In this example, Field AA is set to 0, indicating
SDLC communications.

Field BB specifies the operating mode of the 5394. If Field BB is 0, the controller
will be used in 5394 mode (for connections to the AS/400 system). Field BB
should be set to 1 (5294 emulation mode) for connections to System/36 or
System/38.

SDLC Communications
For SDLC communications, several values specified in Fields 2 and 3 must match
values specified in the AS/400 configuration.
Field 2 Field 2 contains the station address assigned to the controller. This
value must be matched in two parameters on the AS/400 CRTCTLRWS
command:

The STNADR parameter

Chapter 9. Configuring 5250-Type Controllers—Scenario 9-3

The last two digits of the 8-digit EXCHID parameter
Field 3 Field 3 contains seven subfields:
Subfield 1 determines whether the line is nonswitched (0), manual-
dial switched (1), or auto-dial switched V.25bis (2).
Subfield 2 indicates whether the communications line is half-duplex
(0) or duplex (1). This value must match the value specified by the
DUPLEX parameter on the CRTLINSDLC command.
Subfield 3 determines whether the line is multipoint (0) or point-to-
point (1). The combination of subfields 1 and 3 must be coordinated
with the connection type (CNN parameter) specified on the
CRTLINSDLC command. In this example, both subfields are set to 1
(manual-dial, switched point-to-point).
Subfield 4 indicates whether NRZI (0) or NRZ (1) data encoding is
used. This value must match the value specified by the NRZI
parameter on the CRTLINSDLC command.

The following tables show the port numbers and device addresses for devices
attached to the 5394 controllers in Boston and Chicago. The station addresses
assigned during the 5394 configuration (Field 2) are: 04 (Boston), 05 (Chicago).

Table 9-1. Devices Attached to Boston 5394 Controller, Station Address = 04

Attached Device Port Number Device Address
3196-A1 Display Station 0 1
4224 Intelligent Printer Data Stream* 1 0
(IPDS*) Printer

Table 9-2. Devices Attached to Chicago 5394 Controller, Station Address = 05

Attached Device Port Number Device Address
3180-2 Display Station 0 0
4214-2 Printer 2 0

The station addresses assigned to the 5394 controllers and the values shown in the
preceding tables will be used to configure remote work station communications on
the AS/400 system.

Configuration of the AS/400 System

The AS/400 configuration requirements for the connections shown in Figure 9-1 on
page 9-2 are as follows:
An SDLC line description (CRTLINSDLC command) to describe the switched
connection between the AS/400 system and the remote controllers in Boston
and Chicago.
Remote work station controller descriptions (CRTCTLRWS command) for each
of the 5394 Remote Control Units.
Device descriptions for each of the display stations and printers attached to the
5394 Remote Control Units (CRTDEVDSP and CRTDEVPRT commands).

9-4 Remote Work Station Support V4R1

The AS/400 configuration objects should be created in the order shown above (line,
controllers, devices); the controller and device descriptions contain parameters that
refer to their associated line and controller descriptions.

Before creating the line description, use the Work with Hardware Resources
(WRKHDWRSC) command to determine the system-assigned resource name for
the line you are going to use.

The following sections show how the configuration example can be created using
either the command prompt displays or CL commands.

Configuration Using the Command Prompt Displays

This section shows how the objects required for the remote work station communi-
cations configuration example shown in Figure 9-1 on page 9-2 can be created
using the command prompt displays.

Following each of the displays is a discussion of some of the more important

prompts.

Creating the Line Description

To create the switched SDLC line description, type CRTLINSDLC on the command
line and press F4. Fill in the prompt displays as shown below, then press the Enter
key to create the line description.

à ð
Create Line Desc (SDLC) (CRTLINSDLC)

Type choices, press Enter.

Line description . . . . . . . . > SOXLINE.1/ Name

Resource names . . . . . . . . . > LINð21.2/ Name
+ for more values ___________
Online at IPL . . . . . . . . . > \NO.3/ \YES, \NO
Data link role . . . . . . . . . > \PRI.4/ \NEG, \PRI, \SEC
Physical interface . . . . . . . \RS232V24 \RS232V24, \V35, \X21, ...
Connection type . . . . . . . . > \SWTPP.5/ \NONSWTPP, \SWTPP, \MP, \SHM
Vary on wait . . . . . . . . . . \NOWAIT \NOWAIT, 15-18ð (1 second)
Autocall unit . . . . . . . . . \NO \NO, \YES
Exchange identifier . . . . . . \SYSGEN ð56ððððð-ð56FFFFF, \SYSGEN
NRZI data encoding . . . . . . . \YES \YES, \NO
Line speed . . . . . . . . . . . 96ðð 6ðð, 12ðð, 24ðð, 48ðð...
Modem type supported . . . . . . \NORMAL \NORMAL, \V54, \IBMWRAP...
Switched connection type . . . . > \ANS.6/ \BOTH, \ANS, \DIAL
Autoanswer . . . . . . . . . . . \YES \YES, \NO
Autodial . . . . . . . . . . . . \NO \NO, \YES
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 9-3 (Part 1 of 2). Prompt Displays for SOXLINE SDLC Line Description

Chapter 9. Configuring 5250-Type Controllers—Scenario 9-5

à ð
Create Line Desc (SDLC) (CRTLINSDLC)

Type choices, press Enter.

Calling number . . . . . . . . . \NONE

Connect poll retry . . . . . . . 7 ð-64
Maximum frame size . . . . . . . 521 265, 521, 1ð33, 2ð57
Duplex . . . . . . . . . . . . . \HALF \HALF, \FULL
Nonproductive receive timer . . 32ð 16ð-42ðð (ð.1 seconds)
Idle timer . . . . . . . . . . . 3ð 5-3ðð (ð.1 seconds)
Connect poll timer . . . . . . . 3ð 2-3ðð (ð.1 seconds)
Poll cycle pause . . . . . . . . ð ð-2ð48 (ð.ððð1 seconds)
Frame retry . . . . . . . . . . 7 ð-64
Data Set Ready drop timer . . . 6 3-6ð (seconds)
Autoanswer type . . . . . . . . \DTR \DTR, \CDSTL
Remote answer timer . . . . . . 6ð 3ð, 35, 4ð, 45 (seconds)...
Text 'description' . . . . . . . > 'Switched line for Boston and Chicago RWS'.7/

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 9-3 (Part 2 of 2). Prompt Displays for SOXLINE SDLC Line Description

Considerations for specifying the CRTLINSDLC command:

.1/ Specifies the name of the line description. The name specified here is
also specified for the SWTLINLST parameter of both controller
descriptions to associate this switched line with the remote controllers.
.2/ This is the system resource name assigned to the communications port
to which the physical line is attached. Use the WRKHDWPRD or
WRKHDWRSC command to determine the resource name before cre-
ating the line description.
.3/ Specifies that this line description is not automatically varied on at IPL.
When all of the configuration objects have been created, each will have
to be varied on using the VRYCFG command or the WRKCFGSTS
command.
.4/ The default value, *NEG, can also be used; the AS/400 system will then
negotiate to take the primary (*PRI) role when communications with the
remote work station controller is started.
.5/ Specifies that the line is to be used for switched point-to-point communi-
cations.
.6/ *ANS indicates that this switched connection will be used to handle
incoming calls (from the remote controllers) only.
.7/ A brief description of the object of no more than 50 characters. When
the TEXT parameter is specified on a CL command, the description
must be enclosed in apostrophes; the apostrophes are optional when
using the prompt displays.

9-6 Remote Work Station Support V4R1

Creating the Controller Descriptions
To create the controller descriptions for Boston and Chicago, type CRTCTLRWS on
the command line and press F4. Fill in the prompt displays as shown below, then
press the Enter key to create the controller descriptions.

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > BOSTON.1/ Name

Controller type . . . . . . . . > 5394 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > 1___ ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \SDLC \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Switched connection . . . . . . > \YES \NO, \YES
Short hold mode . . . . . . . . \NO_ \NO, \YES
Switched line list . . . . . . . > SOXLINE.2/ Name
+ for more values _________
Maximum frame size . . . . . . . \LINKTYPE 265-1994, 256, 261, 265...
Exchange identifier . . . . . . > ð5Fðððð4.3/ ðð1ððððð-FFFFFFFF
Initial connection . . . . . . . > \ANS.4/ \DIAL, \ANS
Connection number . . . . . . . > 16172344567.5/
Station address . . . . . . . . > ð4.6/ ð1-FE
Text 'description' . . . . . . . > 'Boston 5394 RWS controller'

F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel

F13=How to use this display F24=More keys
á ñ
Figure 9-4. Prompt Display for BOSTON Remote Work Station Controller Description

Considerations for specifying the CRTCTLRWS command:

.1/ Specifies the name of the controller description. The name specified
here is also specified for the CTL parameter of all device descriptions
associated with this controller.
.2/ Specifies the name of the switched line description with which this con-
troller description is associated.
.3/ The exchange identifier specified for the 5394 Remote Control Unit must
be ð5Fððð followed by the 2-digit station address specified in Field 2 of
the 5394 configuration display.
.4/ *ANS indicates that the initial switched connection is made when the
AS/400 system answers an incoming call from the remote controller.
.5/ The connection number specifies the telephone number of the modem
to which the remote controller is attached.
.6/ This value must match the station address specified in Field 2 of the
5394 configuration display.

Considerations for creating the second controller description (CHICAGO) are the
same as for the first:

Chapter 9. Configuring 5250-Type Controllers—Scenario 9-7

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > CHICAGO___ Name

Controller type . . . . . . . . > 5394 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > 1 ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \SDLC \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Switched connection . . . . . . > \YES \NO, \YES
Short hold mode . . . . . . . . \NO_ \NO, \YES
Switched line list . . . . . . . > SOXLINE___ Name
+ for more values __________
Maximum frame size . . . . . . . \LINKTYPE 265-1994, 256, 261, 265...
Exchange identifier . . . . . . > ð5Fð_ \DIAL, \ANS
Connection number . . . . . . . > 13123455678
Station address . . . . . . . . ð5 ð1-FE
Text 'description' . . . . . . . > 'Chicago 5394 RWS controller'

F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel

F13=How to use this display F24=More keys
á ñ
Figure 9-5. Prompt Display for CHICAGO Remote Work Station Controller Description

The LOCADR Parameter Value Determination

Before creating the display and printer device descriptions, you should determine
the location addresses (LOCADR parameters) that will be specified for each device.

The value specified for the LOCADR parameter on the CRTDEVDSP and
CRTDEVPRT commands is based on the device address and 5394 port assign-
ment as shown in the following table. Note the similarity of the table to the 5394
configuration display shown in Figure 9-2 on page 9-3.

For example, as shown in Table 9-1 on page 9-4, the 5394 Remote Control Unit in
Boston has a display station attached to port 0 with device address 1 and a printer
attached to port 1 with device address 0. Using Table 9-3, the location addresses
specified will be 01 for the display station, 07 for the printer.

Table 9-3. LOCADR Values for Devices Attached to 5394 Controllers

Device Address
Port
Number 0 1 2 3 4 5 6
0 00 01 02 03 04 05 06
1 07 08 09 0A 0B 0C 0D
2 0E 0F 10 11 12 13 14

Creating the Printer Device Descriptions

To create the printer device descriptions, type CRTDEVPRT on the command line
and press F4. Fill in the prompt displays as shown below, then press the Enter key
to create the device description.

9-8 Remote Work Station Support V4R1

à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

Device description . . . . . . . > BOSPRT____ Name

Device class . . . . . . . . . . > \RMT_.1/ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > \IPDS.2/ 3287, 3812, 4ð19, 42ð1...
Device model . . . . . . . . . . > ð.3/ ð, 1, 2, 3, 4, 1ð, 13, 3ð1...
Advanced function printing\. . . \NO_ \NO, \YES
Local location address . . . . . > ð7.4/ ðð-FE
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Attached controller . . . . . . > BOSTON.5/ Name
Font:
Identifier . . . . . . . . . . > ð11.6/ 3, 5, 11, 12, 13, 18, 19...
Point size . . . . . . . . . . \NONE__ ððð.1-999.9, \NONE
Form feed . . . . . . . . . . . \TYPE__ \TYPE, \CONT, \CUT, \AUTOCUT
Separator drawer . . . . . . . . \FILE_ \FILE, 1, 2, 3
Separator program . . . . . . . \NONE___ Name, \NONE
Library . . . . . . . . . . . __________ Name, \LIBL, \CURLIB
Printer error message . . . . . \INQ_ \INQ, \INFO
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

Message queue . . . . . . . . . QSYSOPR Name, QSYSOPR

Library . . . . . . . . . . . \LIBL__ Name, \LIBL, \CURLIB
Pacing . . . . . . . . . . . . . 7______ 1-7
Text 'description' . . . . . . . > 'Boston 4224 IPDS printer'

Figure 9-6. Prompt Display for BOSPRT Printer Device Description

Considerations for specifying the CRTDEVPRT command:

.1/ The device class specified for remote work station communications must
be *RMT.
.2/ IPDS printers must specify *IPDS as the device type.
.3/ IPDS printers must specify 0 as the device model.
.4/ Use Table 9-3 on page 9-8 to determine the location address that
should be specified for the device.
.5/ Specifies the name of the controller to which the display station is
attached.
.6/ Font identifier is required for printer types 3812, 5219, or *IPDS.

Considerations for creating the second printer device description (CHIPRT) are the
same as for BOSPRT. Requirements for IPDS printers do not apply to the CHIPRT
printer device description.

Chapter 9. Configuring 5250-Type Controllers—Scenario 9-9

à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

Device description . . . . . . . > CHIPRT___ Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 4214 3287, 3812, 4ð19, 42ð1...
Device model . . . . . . . . . . > 2___ ð, 1, 2, 3, 4, 1ð, 13, 3ð1...
Local location address . . . . . > ðE ðð-FE
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Attached controller . . . . . . > CHICAGO___ Name
Form feed . . . . . . . . . . . \TYPE___ \TYPE, \CONT, \CUT, \AUTOCUT
Separator drawer . . . . . . . . \FILE_ \FILE, 1, 2, 3
Separator program . . . . . . . \NONE____ Name, \NONE
Library . . . . . . . . . . . __________ Name, \LIBL, \CURLIB
Printer error message . . . . . \INQ \INQ, \INFO
Message queue . . . . . . . . . QSYSOPR__ Name, QSYSOPR
Library . . . . . . . . . . . \LIBL____ Name, \LIBL, \CURLIB
Pacing . . . . . . . . . . . . . 7____ 1-7
Host print transform . . . . . . \NO_ \NO, \YES
More...

Figure 9-7. Prompt Display for CHIPRT Printer Device Description

Creating the Display Device Descriptions

To create the display device descriptions, type CRTDEVDSP on the command line
and press F4. Fill in the prompt displays as shown below, then press the Enter key
to create the device description.

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > BOSDSP___ Name

Device class . . . . . . . . . . > \RMT_.1/ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3196 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > A1___ ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ð1.2/ ðð-FE
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Attached controller . . . . . . > BOSTON.3/ Name
Drop line at signoff . . . . . . \YES \YES, \NO
Allow blinking cursor . . . . . \YES \YES, \NO
Printer . . . . . . . . . . . . > BOSPRT___.4/ Name
Text 'description' . . . . . . . > 'Boston 3196 display station'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 9-8. Prompt Display for BOSDSP Display Device Description

Considerations for specifying the CRTDEVDSP command:

.1/ The device class specified for remote work station communications must
be *RMT.

9-10 Remote Work Station Support V4R1

.2/ Use Table 9-3 to determine the location address that should be speci-
fied for the device.
.3/ Specifies the name of the controller to which the display station is
attached.
.4/ Specifies the name of an existing printer device description that identi-
fies the printer associated with this display device. If the printer device
description does not yet exist, you can use the CHGDEVDSP command
to specify this parameter after the printer device description has been
created.

Considerations for creating the second display device description (CHIDSP) are the
same as for BOSDSP.

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > CHIDSP___ Name

Device class . . . . . . . . . . > \RMT_ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 318ð_ 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > 2____ ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ðð ðð-FE
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Attached controller . . . . . . > CHICAGO___ Name
Drop line at signoff . . . . . . \YES \YES, \NO
Allow blinking cursor . . . . . \YES \YES, \NO
Printer . . . . . . . . . . . . __________ Name
Text 'description' . . . . . . . > 'Chicago 318ð display station'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

Configuration Using CL Commands

CL commands can be used instead of the prompt displays to create the configura-
tion objects, either by entering the commands interactively or by including the com-
mands in a CL program. The following commands can be entered on the Command
Entry display or can be included in a CL program to create the line, controller, and
device descriptions required for the remote work station communications configura-
tion.

Default values are used for all parameters not specified.

Chapter 9. Configuring 5250-Type Controllers—Scenario 9-11

CRTLINSDLC LIND(SOXLINE) RSRCNAME(LINð21) ONLINE(\NO) ROLE(\PRI)
CNN(\SWTPP) SWTCNN(\ANS) TEXT('Switched line for Boston and Chicago RWS')

CRTCTLRWS CTLD(BOSTON) TYPE(5394) MODEL(1) LINKTYPE(\SDLC)

ONLINE(\NO) SWITCHED(\YES) SWTLINLST(SOXLINE) EXCHID(ð5Fðððð4)
INLCNN(\ANS) CNNNBR('16172344567') STNADR(ð4)
TEXT('Boston 5394 RWS controller')

CRTCTLRWS CTLD(CHICAGO) TYPE(5394) MODEL(1) LINKTYPE(\SDLC)

ONLINE(\NO) SWITCHED(\YES) SWTLINLST(SOXLINE) EXCHID(ð5Fðððð5)
INLCNN(\ANS) CNNNBR('13123455678') STNADR(ð5)
TEXT('Chicago 5394 RWS controller')

CRTDEVPRT DEVD(BOSPRT) DEVCLS(\RMT) TYPE(\IPDS) MODEL(ð)

LOCADR(ð7) ONLINE(\NO) CTL(BOSTON) FONT(ð11)
TEXT('Boston 4224 IPDS printer')

CRTDEVDSP DEVD(BOSDSP) DEVCLS(\RMT) TYPE(3196) MODEL(A1)

LOCADR(ð1) ONLINE(\NO) CTL(BOSTON) PRINTER(BOSPRT)
TEXT('Boston 3196 display station')

CRTDEVPRT DEVD(CHIPRT) DEVCLS(\RMT) TYPE(4214) MODEL(2)

LOCADR(ðE) ONLINE(\NO) CTL(CHICAGO) TEXT('Chicago 4214-2 printer')

CRTDEVDSP DEVD(CHIDSP) DEVCLS(\RMT) TYPE(318ð) MODEL(2)

LOCADR(ðð) ONLINE(\NO) CTL(CHICAGO) PRINTER(CHIPRT)
TEXT('Chicago 318ð display station')

For information about how to use the Retrieve Configuration Source (RTVCFGSRC)
command to create a CL program using the configuration objects described in this
chapter, see the Communications Configuration book. CL programs can be used to
save configuration information for your system or to create configurations for other
AS/400 systems. For more information about using CL commands, see the CL Ref-
erence book.

Configuration of Controller Descriptions for Automatic Connection

When creating remote controller descriptions that will connect over switched links,
you can specify that you want the connection made automatically when you vary on
the controller, even when no application program is requesting a bind with the con-
troller.

Automatic connection is accomplished through the dial initiation (DIALINIT) param-

eter, which is only valid when *DIAL is specified for the initial connection (INLCNN)
parameter on remote work station, APPC, and host controller description objects.
DIALINIT supports these values:
*LINKTYPE This is the default value and is described Table 9-4 on page 9-13.
*IMMED This value causes the connection to the controller to be made imme-
diately.
*DELAY This value causes the system to wait for an application to be started
which requires the connection.
Note: The dial initiation (DIALINIT) parameter applies only to the initial connection
to the controller when you specify *DIAL on the Initial connection prompt.

9-12 Remote Work Station Support V4R1

Table 9-4. *LINKTYPE Values and Corresponding DIALINIT Values
*LINKTYPE default DIALINIT value
LAN (local area network) *IMMED
X.25 network *DELAY
SDLC: Short Hold Mode *IMMED
SDLC: Other *DELAY

Figure 9-9 shows a remote work station controller description configured to auto-
matically connect when varied on. Notice that the Initial connection prompt specifies
*DIAL and the Dial initiation prompt specifies *IMMED.

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > DIALIMMED_ Name

Controller type . . . . . . . . > 5294 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > ððð1 ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \SDLC \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . > \NO \YES, \NO
Switched connection . . . . . . > \YES \NO, \YES
Short hold mode . . . . . . . . \NO \NO, \YES
Switched line list . . . . . . . __________ Name
+ for more values __________
Exchange identifier . . . . . . > ð45ððððð ðð1ððððð-FFFFFFFF
Initial connection . . . . . . . \DIAL \DIAL, \ANS
Dial initiation . . . . . . . . > \IMMED \LINKTYPE, \IMMED, \DELAY
Connection number . . . . . . . > 123456789
Station address . . . . . . . . > ð1 ð1-FE
Text 'description' . . . . . . . \BLANK_________________

More...
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

á ñ
Figure 9-9. Controller Description Specifying Automatic Connection When Varied On

Automatic Dialing to a Remote Work Station Controller—Example

The following example uses V.25bis modems and the STRRMTDSP program to ini-
tiate a dial operation from an AS/400 system to a 5394 controller. The
STRRMTDSP program is a sample control language program and is shown in
Figure 9-10 on page 9-14. This program allocates a display device and opens the
QDSIGNON display file. This causes the system to attempt to dial the remote work
station controller.

Once the connection is established, a display record is sent to the remote work
station device. The device is then deallocated and the program ends. This allows
the device to be allocated by the subsystem, and a sign-on screen appears.
Note: This example does not work for 5494 controllers or for 5394 controllers with
type 2.1 support. Also, the device description needs to be configured as
DROP(*NO) for this function to work. If the device is configured as
DROP(*YES), the system disconnects the switched line when the
STRRMTDSP program completes. The drop parameter configured in the

Chapter 9. Configuring 5250-Type Controllers—Scenario 9-13

device description can be overridden by specifying DROP(*YES) when
signing off (SIGNOFF command) the work station device.
CRTLINSDLC LIND(RWS5394) RSRCNAME(LINð12) CNN(\SWTPP) EXCHID(ð56ð31ðð)
AUTODIAL(\YES) DIALCMD(\V25BIS) STNADR(ð1)
TEXT('5394 RWS switched line')

CRTCTLRWS CTLD(RWS5394) TYPE(5394) MODEL(1) LINKTYPE(\SDLC) ONLINE(\NO)

SWITCHED(\YES) SWTLINLST(RWS5394)
EXCHID(ð5Fðððð4) CNNNBR(555ðððð) STNADR(ð4)
TEXT('RWS 5394 controller')

CRTDEVDSP DEVD(RWS5394) DEVCLS(\RMT) TYPE(5291) MODEL(1) LOCADR(ð1)

ONLINE(\YES) CTL(RWS5394) DROP(\NO)
TEXT('5291 RWS device attached to 5394 controller')

Start Remote Display (STRRMTDSP) Command

CMD PROMPT('START REMOTE DISPLAY')
PARM KWD(DEVD) TYPE(\SNAME) LEN(1ð) MIN(1) +
PROMPT('DEVICE DESCRIPTION')

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ NAME: STRRMTDSP \/
/\ \/
/\ The following CL program will open the QDSIGNON \/
/\ display file and send a display record to a device. \/
/\ This will cause the system to dial out to the remote \/
/\ work station controller. For this program to work \/
/\ correctly, the device description needs to be \/
/\ configured as DROP(\NO), otherwise when this \/
/\ program ends, the system will attempt to drop the \/
/\ switched line. \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

PGM PARM(&DEVD);
DCL VAR(&DEVD); TYPE(\CHAR) LEN(1ð)
DCLF FILE(QSYS/QDSIGNON)

/\ Allocate the device and send the display record \/

/\ to the device. \/

ALCOBJ OBJ((&DEVD \DEVD \EXCLRD)) WAIT(1ð)

OVRDSPF FILE(QDSIGNON) DEV(&DEVD);
SNDF

/\ Deallocate the device to allow it to be \/

/\ allocated by the subsystem. \/

DLCOBJ OBJ((&DEVD \DEVD \EXCLRD))

ENDPGM

Figure 9-10. Automatic-Dial Example CL Program

Attaching DBCS-Capable Devices to 5250 Controllers

DBCS-capable devices (display stations and printers) can be attached to the
system in the same way as other devices are attached. Devices attached to
5250-type (twinaxial) remote work station controllers can be attached using any of
the following controllers:
5494 Remote Control Unit
5394 Remote Control Unit

9-14 Remote Work Station Support V4R1

The Remote 5250 Work Station Adapter. This optional adapter card for the IBM
Personal System/55 allows the PS/55 to be attached to the AS/400 system as
a remote work station without using a 5294 or 5394 Remote Control Unit. (An
adapter card is the electrical circuit on a logic card that connects one device to
another or to a computer.) When the Remote 5250 Work Station Adapter is
used, it should be configured as a 5394 Remote Control Unit.
5294 Model K01 Remote Control Unit (for Japanese devices only). If you attach
both Japanese DBCS-capable display stations and alphanumeric display
stations to the same 5294-K01, the alphanumeric display stations must have
either an attached Katakana keyboard or no attached keyboard.
The 5294 Model S01 Remote Control Unit (for Chinese and Korean devices)
must be configured as a 5294-K01.

AS/400 System

5555 5551 5553

5394 System Unit
Controller
RV3P107-0

Figure 9-11. Configuration Example Using DBCS-Capable Devices

The following prompt displays show examples of device descriptions created for a
PS/55 and a 5553 printer attached to a 5394 Remote Control Unit as shown in
Figure 9-11.

Chapter 9. Configuring 5250-Type Controllers—Scenario 9-15

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > DBCSDSP__ Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT
Device type . . . . . . . . . . > 5555_ 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > Bð1___ ð, 1, 2, 11, 12, 23, 31...
Local location address . . . . . > ð1 ðð-FE
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Attached controller . . . . . . > DBCSCTL___ Name
Drop line at signoff . . . . . . \YES \YES, \NO
Allow blinking cursor . . . . . \YES \YES, \NO
Printer . . . . . . . . . . . . __________ Name
DBCS feature: _
Device features . . . . . . . > 2424J4____ Character value
Last code point . . . . . . . > 68FE______ 4141-FFFE
Text 'description' . . . . . . . > 'DBCS display attached to 5394 controller'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

Device description . . . . . . . > DBCSPRT__ Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT
Device type . . . . . . . . . . > 5553 3287, 3812, 42ð1, 42ð2...
Device model . . . . . . . . . . > Bð1___ ð, 1, 2, 3, 4, 1ð, 13, 2ðð...
Local location address . . . . . > ð2 ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > DBCSCTL___ Name
Form feed . . . . . . . . . . . > \AUTOCUT \TYPE, \CONT, \CUT, \AUTOCUT
Separator drawer . . . . . . . . \FILE_ \FILE, 1, 2, 3
Separator program . . . . . . . \NONE____ Name, \NONE
Library . . . . . . . . . . . ________ Name, \LIBL, \CURLIB
Printer error message . . . . . \INQ_ \INQ, \INFO
Message queue . . . . . . . . . QSYSOPR Name, QSYSOPR
Library . . . . . . . . . . . \LIBL Name, \LIBL, \CURLIB
Pacing . . . . . . . . . . . . . 7____ 1-7

More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

DBCS feature:
Device features . . . . . . . > 2424J1 Character value
Last code point . . . . . . . > 68FE 4141-FFFE
Text 'description' . . . . . . . > 'DBCS printer attached to 5394 controller'

9-16 Remote Work Station Support V4R1

Chapter 10. Configuring for the IBM 5394 Type 2.1 RPQ
This chapter describes the support available on the AS/400 system for the IBM
5394 Remote Control Unit as a type 2.1 node. This chapter includes an overview of
the support available on the AS/400 system, an explanation of the AS/400 config-
uration descriptions that must be created to use the support, and an explanation of
how that support may be used.

Overview of the AS/400 System 5394 Type 2.1 Support

The 5394 Remote Control Unit can connect to the AS/400 system as a type 2.1
node:
As part of an SNA subarea network
Through an APPN network
Directly, as a peer network node

In each case, the automatic remote controller (QAUTORMT) system value causes
all 5394 Type 2.1 Remote Control Units attached to the AS/400 system to be auto-
matically configured. The QAUTORMT system value causes 5494 Remote Control
Units attached the the AS/400 system to be automatically configured. Program-
mable and nonprogrammable work stations that are attached to the 5394 Type 2.1
Remote Control Unit can be automatically created, also.
Note: If you do not want the 5394 Type 2.1 Control Unit automatically configured,
use the Change System Value (CHGSYSVAL) command to set the
QAUTORMT system value off.

5394 Remote Control Unit in an SNA Subarea Network Node

The 5394 Type 2.1 Remote Control Unit can be attached to an AS/400 system
through an SNA subarea network. A subarea network consists of type 4 or type 5
nodes on an SNA network. A type 4 node is a communications controller (for
example, 3720, 3725, or 3745 controller) running the Network Control Program
(NCP). A type 5 node is a System/370* host system running the Virtual Telecom-
munications Access Method (VTAM*) licensed program. The 5394 and the AS/400
system attach to the subarea network through a low-entry networking boundary
function that is provided by either the NCP or VTAM.

Figure 10-1 on page 10-2 shows a 5394 Remote Control Unit attached to an
AS/400 system through an SNA subarea network:

 Copyright IBM Corp. 1997 10-1

Subarea Network Node
┌────────────────────┐
│ System/37ð │
├────────────────────┤
│ VTAM │
└────────┬──┬────────┘
│ │
┌───────────┘ └─────────────┐
│ │
┌───────┴───────┐ ┌──────┴──────┐
│ 3745 │ │ 3745 │
│ Controller │ │ Controller │
├───────────────┤ ├─────────────┤
│ NCP │ │ NCP │
└───────┬───────┘ └──────┬──────┘
│ │
│ SDLC
┌────────────┴───────────┐ ┌──────┴──────┐
│ AS/4ðð │ │ 5394 Remote │
│ System │ │ Control Unit│
└────────────────────────┘ └─────────────┘
End Node End Node

Figure 10-1. Subarea Network

The advantages of using your 5394 controller from an SNA subarea network are:
Easier network management. Because sessions on the 5394 Type 2.1 Remote
Control Unit can be tracked through the host-central control network, people
managing the SNA network are able to control and monitor network use, and
help resolve problems on the 5394 controller.
Only one line into the AS/400system is required to both attach the AS/400
system to the SNA subarea network and the 5394 Type 2.1 Remote Control
Unit to the AS/400 system.

5394 Remote Control Unit in an APPN Network Node

The 5394 Type 2.1 Remote Control Unit can also attach to an AS/400 system
through an Advanced Peer-to-Peer Network (APPN) network. An APPN network
consists of type 2.1 nodes on an SNA network. Figure 10-2 on page 10-3 shows a
5394 Type 2.1 Remote Control Unit attached to an AS/400 system through an
APPN network.

10-2 Remote Work Station Support V4R1

┌────────────┐
│5394 Remote │
│Control Unit│
│ │
│ │
└─────┬──────┘
SDLC
│
┌─────────┴─────────┐
│ │
│ AS/4ðð │
│ System │
│ │
└─────────┬─────────┘
│
│
┌─────────┴─────────┐
│ │
│ AS/4ðð │
│ System │
│ │
└───────────────────┘

Figure 10-2. APPN Network

By connecting your 5394 Remote Control Unit to an AS/400 system through an

APPN network, the 5394 can be connected to one AS/400 system while the work
stations attached to that controller communicate with another AS/400 system in the
network.

5394 Remote Control Unit in a Peer Network Node

The 5394 Remote Control Unit that is directly attached to an AS/400 system acts
as a low-entry networking end node. An end node operates in a peer environment,
and can communicate directly with the AS/400 system. Figure 10-3 shows a 5394
Remote Control Unit directly connected to an AS/400 system as a peer network
node.

┌────────────┐
│5394 Remote │
│Control Unit│
│ │
│ │
└─────┬──────┘
SDLC
│
┌─────────┴─────────┐
│ │
│ AS/4ðð │
│ System │
│ │
└───────────────────┘

Figure 10-3. Peer Network

Directly connecting the 5394 Remote Control Unit as a type 2.1 node to an AS/400
system allows you to test new applications or configurations before they are
attached to a subarea network.

Chapter 10. Configuring for the IBM 5394 Type 2.1 RPQ 10-3
Setting Up the 5394 Type 2.1 Node Support
Before you can use the work stations attached to the 5394 Type 2.1 Remote
Control Unit, you must first create or change configuration information that is
located on both the 5394 controller and the AS/400 system. Instructions for
changing configuration information on the 5394 are located in the IBM 5394
Remote Control Unit Type 2.1 Node Support RPQ 8Q0775, SC30-3531, book.

The AS/400 configuration is done in two steps:

Creating configuration descriptions to allow communications between the
AS/400 system and the 5394 Type 2.1 Remote Control Unit on a subarea or
APPN network.
Creating configuration descriptions for the 5394 Remote Control Unit and its
work stations on the AS/400 system.

Configuring the AS/400 System to Communicate With the 5394 Type

2.1 Remote Control Unit
This first step involves configuring the AS/400 system to communicate with the
5394 Remote Control Unit. This needs to be done if the 5394 is to be attached to
the AS/400 system through an SNA subarea network, through an APPN network, or
if it is directly attached to the AS/400 system. Where possible, you should allow
automatic configuration to create your configuration descriptions for you.

To allow the AS/400 system to communicate with the 5394 Remote Control Unit,
create configuration descriptions for the line, communications controller, mode, and
configuration list by using the following commands:
Create Line Description: (CRTLINxxx, where xxx indicates the type of line used
to attach the AS/400 system with the network. This can be ETH, IDLC, SDLC,
TRN, or X25, depending on the line type).
Create Controller Description (APPC): (CRTCTLAPPC command when the next
node on the network on the subarea network is another type 2.1 node). To
create an APPC controller description, refer to “Step 2: Configuring a Con-
troller Description” on page 11-5. The instructions in that section also apply to
the 5394 Type 2.1 controller.
or
Create Controller Description (SNA Host): (CRTCTLHOST command when the
next node on the subarea network is a System/370* host system (type 4 or
type 5 node)). When using the CRTCTLHOST command, you should be aware
of the following fields on the display:

10-4 Remote Work Station Support V4R1

à ð
Create Ctl Desc (SNA Host) (CRTCTLHOST)

Type choices, press Enter.

Controller description . . . . . > CTLHOST__ Name

Link type . . . . . . . . . . . > \SDLC.1/ \IDLC, \FR, \LAN, \SDLC, \X25
Online at IPL . . . . . . . . . > \NO_ \YES, \NO
Switched connection . . . . . . \NO_ \NO, \YES
Switched network backup . . . . \NO_ \NO, \YES
APPN-capable . . . . . . . . . . \YES \YES, \NO
Attached nonswitched line . . . > IBMTPOUT__ Name
Maximum frame size . . . . . . . > 2ð57_____ 265-16393, 256, 265, 512...
Remote network identifier . . . > IBMMIN__ Name, \NETATR, \NONE, \ANY
Remote control point . . . . . . > \ANY.2/ Name, \ANY
Adjacent link station . . . . . \NONE___ Name, \NONE, \ANY
SSCP identifier . . . . . . . . ________ ð5ðððððððððð-ð5FFFFFFFFFF
Local exchange identifier . . . \LIND___ ð56ððððð-ð56FFFFF, \LIND
Station address . . . . . . . . > C1.3/ ð1-FE
APPN CP session support . . . . \YES \YES, \NO
APPN node type . . . . . . . . . \ENDNODE \ENDNODE, \LENNODE...
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 10-4. Host Controller Description Example

The following information will help you fill in the fields:

.1/ Link type: Use *SDLC or *X25. The value you use depends on the
type of line you created in the previous step. Use *SDLC if you
created an SDLC line and *X25 if you created an X.25 line. If you
created a token-ring line, use the value *LAN.
.2/ Remote control point: Use *ANY to have the system determine the
name of the remote control point used.
.3/ Station address: Enter the value of the station address used when
communicating with the controller. The value can be from 01 to FE.
Create Mode Description: (CRTMODD command). The IBM-supplied default
mode is QRMTWSC and need not be created.
Create Configuration List: (CRTCFGL command. You may need an entry in the
configuration list for the network. Consult your network manager for additional
information.).
Note: There is no need to create an APPC device description because it will be
created by automatic configuration when the 5394 Remote Control Unit
begins a session with the AS/400 system.

The APPN Support book contains the information needed to attach and configure
the AS/400 system to a subarea network, an APPN network, and directly to a peer
network node.

Chapter 10. Configuring for the IBM 5394 Type 2.1 RPQ 10-5
Configuring the 5394 Remote Control Unit and Its Work Stations
After you configure your AS/400 system to communicate, you need to change or
create configuration descriptions for the 5394 Remote Control Unit and the devices
that will attach to it.
Note: When the QAUTORMT system value is set on, you do not need to manually
configure the remote control unit and remote display stations. Therefore this
step is no longer necessary.

Use the Create Controller Description (Remote Work Station) (CRTCTLRWS)

command to create the controller description on the AS/400 system for the 5394
controller. There are special values you need to enter in this description to indicate
the use of the 5394 Type 2.1 Remote Control Unit node support.
Parameter Meaning
LINKTYPE Link type. The type of line to which this controller is attached. Enter
\NONE to indicate the type 2.1 node support. The controller description
will not be physically attached to a line description.
RMTLOCNAME Remote location name. The location name of the 5394 work
station controller. This value must match the logical unit (LU) name of
the 5394 Remote Control Unit.
LCLLOCNAME Local location name. The location name of the AS/400 system. You
can enter \NETATR to use the default local location. To display this value,
use the Display Network Attributes (DSPNETA) command.
RMTNETID Remote network identifier. The network ID of the network on which the
5394 is attached. You can enter \NETATR to use the default network
identifier. To display this value, use the Display Network Attributes
(DSPNETA) command.
ALCRTYTMR Allocation Retry Interval Timer. The amount of time in seconds the
AS/400 system will wait after an unsuccessful attempt to activate a
device before attempting to activate it again. Attempts to activate a
device will continue until the device is varied off, or the device is
powered off.
AUTOCRTDEV Automatic device creation. Use *ALL to allow all devices to be
automatically created for this controller.
SWTDST Switched disconnect. If you want the connection to the controller
dropped when the last user signs off, use *YES. If you have token-ring
or leased lines, use *NO. Then the connection is not dropped when the
last user signs off. For example, if you have a switched line, set this
parameter to *YES.

When you enter your information using the CRTCTLRWS command, your
description could look like this:

10-6 Remote Work Station Support V4R1

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > CTL5394__ Name

Controller type . . . . . . . . > 5394 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > 1 ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \NONE \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . \YES \YES, \NO
Remote location . . . . . . . . > R5394 Name
Local location . . . . . . . . . \NETATR Name, \NETATR
Remote network identifier. . . . \NETATR Name, \NETATR, \NONE
Autocreate device. . . . . . . . \ALL \ALL, \NONE
Switched disconnect. . . . . . . \YES \YES, \NO
Text 'description' . . . . . . . \BLANK

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

You also need to configure the devices that will attach to your 5394 Remote
Control Unit. Use the Create Device Description (Display) (CRTDEVDSP) command
or the Create Device Description (Printer) (CRTDEVPRT) command to create these
descriptions. This is done as though there is no intervening network between the
5394 Remote Control Unit and the AS/400 system.

Notes:
1. No device descriptions need to be created for programmable work stations.
Programmable work stations are already type 2.1 nodes, and therefore operate
independently of the 5394 controller. Programmable work stations configura-
tions are like APPC device descriptions attached to the APPC or host controller
descriptions. The programmable work stations are automatically configured.
2. If you set the AUTOCRTDEV (Autocreate device) parameter to *ALL on the
Create Controller Description (Remote WS) (CRTCTLRWS) command, the
display and printer device descriptions are automatically created.

For example, if you were trying to create a configuration description for a 3196
Display Station that was attached to the remote controller that was just configured,
your description could look like this:

Chapter 10. Configuring for the IBM 5394 Type 2.1 RPQ 10-7
à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > DSPð9__ Name

Device class . . . . . . . . . . > \RMT_ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3196_ 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > A1 ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ðE ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > CTL5394 Name
Drop line at signoff . . . . . . \YES \YES, \NO
Allow blinking cursor . . . . . \YES \YES, \NO
Printer . . . . . . . . . . . . ________ Name
Text 'description' . . . . . . . \BLANK

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

Using the 5394 Remote Control Unit

Before you can begin using the work stations attached to your controller, the config-
uration descriptions for the 5394 Remote Control Unit and the devices attached to it
must be active, varied on, or in a varied-on pending state. The configuration
descriptions needed for the AS/400 system to communicate with the SNA subarea
network or the APPN network also need to be active, varied on, or in a varied-on
pending state.

When the first device attached to the 5394 Remote Control Unit is powered on, the
5394 tries to attach to the AS/400 system. It attaches to the SNA subarea network
and sends a request to the AS/400 system to start sessions for all of the devices
attached to the controller that are powered on.

If, for some reason, the connection between the 5394 Remote Control Unit and the
SNA subarea network has been lost, a user at a device attached to the 5394 con-
troller need only press the System Request key, and then the Enter key, to begin
the connection process again. If the AS/400 system detects an error, it goes
through the normal remote work station recovery procedures.

Managing the 5394 Remote Control Unit

To manage your 5394 Type 2.1 Remote Control Unit, refer to “Managing the 5494
Remote Control Unit” on page 11-16. The suggestions described in that section
also apply to the 5394 Type 2.1 controller.

10-8 Remote Work Station Support V4R1

Chapter 11. Configuring 5494 Remote Control Units
This chapter discusses how to configure and manage the 5494 controller on the
AS/400 system. It includes information about configuring the AS/400 system for the
IBM 5494 Remote Control Unit Attachment to Subarea Network Request for Price
Quotation (RPQ). For information on how to configure the 5494 controller hardware,
see the 5494 Remote Control Unit User's Guide, GA27-3960, book. If applicable,
see also the 5494 Remote Control Unit Attachment to Subarea Network RPQ
8Q0932, SC30-3566, book.

How the 5494 Remote Control Unit Works

The 5494 controller performs all of the functions of the 5394 controller, with these
added functions:
| The 5494 Remote Control Unit can manage the operation of up to a total of 56
| twinaxial attached devices.
| The 5494 Remote Control Unit can attach to a token-ring network, with the fol-
| lowing token-ring configurations:
| – Token-ring gateway configuration, which supports up to 80 downstream
| devices. The 80 devices can be a combination of twinaxially attached
| devices (56 maximum) and independent work stations attached to a token-
| ring network.
| Note: The 5494 Remote Control Unit Release 2.0 supports up to 80
| devices. Earlier releases support fewer devices. Refer to the 5494
| Remote Control Unit Planning Guide Release 2.0 for the number of
| devices supported per release and recommendations.

 Copyright IBM Corp. 1997 11-1

| Figure 11-1. 5494 Remote Control Unit in a Token-Ring Gateway Configuration. Up to 80
| devices may be attached to the 5494 controller.

| – AS/400 token-ring attachment configuration, which allows you to connect

| the 5494 controller to an AS/400 system through a token-ring network. You
| can connect up to fifty-six 5250 devices in this configuration.

11-2 Remote Work Station Support V4R1

| Figure 11-2. 5494 Remote Control Unit with AS/400 Token-Ring Attachment Configuration.
| Up to 56 devices may be attached to the 5494 controller.

The 5494 Remote Control Unit is a logical unit 6.2 (LU 6.2) low-entry net-
working (LEN) node and, thus, can participate in any APPN network.
The 5494 Remote Control Unit Release 2.0 supports AS/400 applications that
bind LU 6.2 sessions on personal computer systems attached to the 5494.
Earlier 5494 releases do not have this support.
The automatic remote controller (QAUTORMT) system value causes all 5494
Remote Control Units and all 5394 Type 2.1 Remote Control Units attached to
the AS/400 system to be automatically configured.

Configuring the 5494 Remote Control Unit on the AS/400 System

The following information describes how to configure the line, controller, and device
descriptions on the AS/400 system for a 5494 controller. For the 5494 controller,
you need two controller descriptions.
An APPC or SNA host controller description to support 5494 control functions
and any local area network (LAN) attached devices.
A remote work station controller description to control twinaxially attached
devices.

To configure the AS/400 system, perform the following steps:

1. Configure a line description to the network using the Create Line Description
(CRTLINxxx) command where xxx is SDLC, X25, or TRN (described in “Step 1:
Configuring a Line to the Network” on page 11-5).

Chapter 11. Configuring 5494 Remote Control Units 11-3

2. Configure an APPC controller description using the Create Controller
Description (APPC) (CRTCTLAPPC) command if the next node in the network
is another type 2.1 node.
or
Configure an SNA host controller description using the Create Controller
Description (SNA Host) (CRTCTLHOST) command. Do this if the next node in
the network is a System/370 host system (type 4 or type 5 node).
3. Configure a 5494 controller description using the Create Controller Description
(Remote Work Station) (CRTCTLRWS) command.
Note: The QAUTORMT system value allows this controller description to be
automatically configured.
4. Configure dependent device descriptions using the Create Device Description
(Display) (CRTDEVDSP) and the Create Device Description (Printer)
(CRTDEVPRT).
Note: The Autocreate device (AUTCRTDEV) parameter on the 5494 remote
controller description allows devices attached to the controller to be
automatically created.

Check the Mode Description

The 5494 Remote Control Unit Release 1.1 or higher has a default mode of
QRMTWSC. The AS/400 system automatically creates a QRMTWSC mode
description that supports up to 57 sessions unless the QRMTWSC mode
description already exists. If the QRMTWSC mode description already exists,
change the following values using the Change Mode Description (CHGMODD)
command:
Maximum number of active sessions (MAXSSN) should be 57
Maximum number of active conversations (MAXCNV) should be 57
Minimum number of concurrent locally controlled sessions requested for this
mode (LCLCTLSSN) should be 56

The sessions and conversations needed are: one for each possible dependent
work station and one for a controller management session. (The twinaxially
attached devices are the dependent work stations.)

Prior to 5494 Release 1.1, the 5494 controller had a default mode of BLANK.
This mode description is automatically created by the AS/400 system, but it has
only seven sessions. If seven sessions are not enough, use the Change Mode
Description (CHGMODD) command to increase the number of sessions associ-
ated with mode BLANK. To make the change effective, vary off all of the APPC
devices that are using the BLANK mode, then vary them back on.

Note: For information about which AS/400 configuration objects need to match
which 5494 configuration fields, see the Matching Parameters sections on
pages 11-11, 11-13, and 11-15.

11-4 Remote Work Station Support V4R1

Step 1: Configuring a Line to the Network
This may already be done if the AS/400 system had previous communications with
the network.

The 5494 controller supports the following lines, which are created using the com-
mands shown.
| SDLC (Create Line Description (SDLC) (CRTLINSDLC))
| X.25 (Create Line Description (X.25) (CRTLINX25))
| Token-ring (Create Line Description (Token-Ring) (CRTLINTRN))
| Frame Relay (Create Line Description (Frame Relay Network) (CRTLINFR))
| Ethernet (Create Line Description (Ethernet) (CRTLINETH))
| X.21 short hold mode (SHM) (Create Line Description (SDLC) (CRTLINSDLC))

If the 5494 controller is not adjacent to the target AS/400 system, you can use any
line type that supports APPN traffic.

Step 2: Configuring a Controller Description

If the next node in the network is another type 2.1 node, configure an advanced
program-to-program (APPC) controller description. See “Configuring an Advanced
Program-to-Program Communications Controller.”

If the next node in the network is a System/370 host system (type 4 or type 5
node), configure an SNA host controller description. See Figure 11-4 on
page 11-7.

Configuring an Advanced Program-to-Program Communications

Controller
Configure an advanced program-to-program communications (APPC) controller
description using the Create Controller Description (APPC) (CRTCTLAPPC)
command. This description is used to connect the 5494 controller to the AS/400
system.
Note: The APPC controller description automatically creates the APPC device
description. To change the APPC device description, use the Change
Device Description (APPC) (CHGDEVAPPC) command. For example, enter
CHGDEVAPPC NYAPPC01, where NYAPPC01 is the name of the APPC
device description.

Chapter 11. Configuring 5494 Remote Control Units 11-5

à ð
Create Ctl Desc (APPC) (CRTCTLAPPC)

Type choices, press Enter.

Controller description . . . . . > NYAPPC___ Name

Link type . . . . . . . . . . . > \SDLC.1/ \FR, \IDLC, \LAN, \LOCAL...
Online at IPL . . . . . . . . . \YES \YES, \NO
Switched connection . . . . . . \NO \NO, \YES
Switched network backup . . . . \NO \NO, \YES
APPN-capable . . . . . . . . . . \YES____ Name
Maximum frame size . . . . . . . \LINKTYPE 265-16393, 256, 265, 512...
Remote network identifier . . . \NETATR Name, \NETATR, \NONE, \ANY
Remote control point . . . . . . > NY5494.2/ Name, \ANY
Exchange identifier . . . . . . > ð73ððððA.3/ ðððððððð-FFFFFFFF
Data link role . . . . . . . . . \NEG \NEG, \PRI, \SEC
Station address . . . . . . . . > ðA.4/ ðð-FE
APPN CP session support . . . . > \NO \YES, \NO
APPN node type . . . . . . . . . > \LENNODE \ENDNODE, \LENNODE...
APPN transmission group number 1 1-2ð, \CALC
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 11-3. APPC Controller Description Example

Enter your choices for this display. The following information will help you fill in the
prompts.
.1/ Link type: Use *SDLC, *X25, or *LAN. The value you use depends on
the type of line you created in Step 1. Use *SDLC if you created an
SDLC line and *X25 if you created an X.25 line. If you created a token-
ring line, use the value *LAN.
.2/ Remote control point: Use the 5494 control point name.
.3/ Exchange identifier: Use 073000xx, where xx is the station address
(which is explained in paragraph .4/).
.4/ Station address: Enter the value of the station address used when com-
municating with the controller. The value can be from 01 to FE.

Configuring an SNA Host Controller

Configure an SNA host controller description using the Create Controller
Description (SNA Host) (CRTCTLHOST) command. This description is used to
connect the 5494 controller to the AS/400 system. Figure 11-4 on page 11-7
shows an example of configuring an SNA host controller description.

11-6 Remote Work Station Support V4R1

à ð
Create Ctl Desc (SNA Host) (CRTCTLHOST)

Type choices, press Enter.

Controller description . . . . . > CTLHOST__ Name

Link type . . . . . . . . . . . > \SDLC.1/ \IDLC, \FR, \LAN, \SDLC, \X25
Online at IPL . . . . . . . . . > \NO \YES, \NO
Switched connection . . . . . . \NO \NO, \YES
Switched network backup . . . . \NO \NO, \YES
APPN-capable . . . . . . . . . . \YES \YES, \NO
Attached nonswitched line . . . > IBMTPOUT Name
Maximum frame size . . . . . . . > 2ð57 265-16393, 256, 265, 512...
Remote network identifier . . . > IBMMIN Name, \NETATR, \NONE, \ANY
Remote control point . . . . . . > NY5494.2/ Name, \ANY
SSCP identifier . . . . . . . . _______ ð5ðððððððððð-ð5FFFFFFFFFF
Local exchange identifier . . . \LIND ð56ððððð-ð56FFFFF, \LIND
Station address . . . . . . . . > C1.3/ ð1-FE
APPN CP session support . . . . > \NO \YES, \NO
APPN node type . . . . . . . . . > \LENNODE \ENDNODE, \LENNODE...
APPN transmission group number 1 1-2ð, \CALC
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 11-4. SNA Host Controller Description Example

Enter your choices for this display. The following information will help you fill in the
prompts.
.1/ Link type: Use *SDLC, *X25, or *LAN. The value you use depends on
the type of line you created in Step 1. Use *SDLC if you created an
SDLC line and *X25 if you created an X.25 line. If you created a token-
ring line, use the value *LAN.
.2/ Remote control point: Use the 5494 control point name.
.3/ Station address: Enter the value of the station address used when com-
municating with the controller. The value can be from 01 to FE.

Step 3: Configuring a Remote Work Station Controller

Using the Create Controller Description (Remote Work Station) (CRTCTLRWS)
command, configure a remote work station controller description for the 5494 con-
troller. Make sure the LINKTYPE parameter is specified *NONE, and the
RMTLOCNAME, RMTNETID, and LCLLOCNAME parameters match the values
specified on the 5494 controller. Figure 11-5 on page 11-8 shows an example of
configuring a remote work station controller description.

Notes:
1. The QAUTORMT system value allows the 5494 Remote Control Unit to be
automatically configured.
2. The 5494 remote work station controller automatically creates the remote
device descriptions.

Chapter 11. Configuring 5494 Remote Control Units 11-7

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > CTL5494__ Name

Controller type . . . . . . . . > 5494.1/ 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > 1.2/ ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \NONE.3/ \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . \YES \YES, \NO
Remote location . . . . . . . . > NY5494.4/ Name
Local location . . . . . . . . . \NETATR.5/ Name, \NETATR
Remote network identifier . . . \NETATR.6/ Name, \NETATR, \NONE
Autocreate device. . . . . . . . \ALL.7/ \ALL, \NONE
Switched disconnect. . . . . . . \YES.8/ \YES, \NO
Text 'description' . . . . . . . \BLANK

Figure 11-5. Remote Work Station Controller Description Example

.1/ Controller type: Use the value 5494.

.2/ Enter the model number of the 5494 controller. Enter 1 for a Model 001,
or enter 2 for a Model 002. The Model 002 has a port and cable for a
token-ring connection.
If you do not know the model number, enter either 1 or 2. This field is
for reference only; the AS/400 system does not use it.
.3/ Link type: Enter the value *NONE to indicate LU 6.2 attachment. The
controller description will not be physically attached to a line description.
.4/ Remote location: Enter the remote location value for this controller. The
remote location must match the logical unit (LU) name of the 5494 con-
troller.
.5/ Local location: Enter the local location value for this controller. The local
location must match the AS/400 LU name on the 5494 controller. A
value of *NETATR causes the local location name specified in the
network attributes to be used.
.6/ Remote network identifier: Enter the remote network identifier for this
controller. The remote network identifier must match the network identi-
fier that is specified on the 5494 controller. A value of *NETATR causes
the local network identifier specified in the network attributes to be used.
.7/ Autocreate device: Use *ALL to allow all devices to be automatically
created for this controller.
.8/ Switched disconnect: Use *YES if you want the connection to the con-
troller to be dropped when the last user signs off. If you have Token-
Ring or a leased line, specify *NO, the connection is not be dropped
when the last user signs off. If you have a switched line (SDLC or X.25)
you would want to set this value to *YES.
Notes:
1. If you use this parameter, you do not have to change the DROP
parameter on the device description.
2. This parameter defaults to *YES if the QAUTORMT system value is
set on.

11-8 Remote Work Station Support V4R1

Step 4: Configuring Dependent Work Stations
To configure a device description for each dependent work station attached to the
5494 controller, use the Create Device Description (Display) (CRTDEVDSP) or the
Create Device Description (Printer) (CRTDEVPRT) commands.

Notes:
1. If you have set the AUTOCRTDEV (Autocreate device) parameter on the
controllerdescription to *ALL, this step is already done for you.
2. Each independent work station is automatically configured as an APPC device
attached to the APPC controller.

Determining the LOCADR Parameter Value

Before creating the display and printer device descriptions,determine the location
addresses (LOCADR parameters) that need to be specified for each device.

The value specified for the LOCADR parameter on the CRTDEVDSP and
CRTDEVPRT commands is based on the device address and 5494 port assign-
ment. See Table 11-1.

Table 11-1. LOCADR Values for Devices Attached to 5494 Controllers

Device Address
Port
Number 0 1 2 3 4 5 6
0 00 01 02 03 04 05 06
1 07 08 09 0A 0B 0C 0D
2 0E 0F 10 11 12 13 14
3 15 16 17 18 19 1A 1B
4 1C 1D 1E 1F 20 21 22
5 23 24 25 26 27 28 29
6 2A 2B 2C 2D 2E 2F 30
7 31 32 33 34 35 36 37

Figure 11-6 on page 11-10 shows an example of creating a display device

description using the CRTDEVDSP command.

Chapter 11. Configuring 5494 Remote Control Units 11-9

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > DSP5494__ Name

Device class . . . . . . . . . . > \RMT.1/ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3179 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > 2 ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ðB ðð-FE
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . > CTL5494.2/ Name
Drop line at signoff . . . . . . \YES \YES, \NO
Allow blinking cursor . . . . . \YES \YES, \NO
Printer . . . . . . . . . . . . _______ Name
Text 'description' . . . . . . . > '3179 Device attached to 5494 controller'

Figure 11-6. Device Description Example

.1/ Device Class: Use the value *RMT to indicate that this device is
attached to a remote controller.
.2/ Attached controller: Enter the name of the remote work station controller
the device is attached to. This is the name of the controller you created
in Step 3.
Note: The maximum length of request unit (MAXLENRU) parameter is always
specified with the value *CALC for devices attached to 5494 controllers.
This parameter defaults to *CALC and can be viewed by pressing F9 (all
parameters) on the Create Device Description display.

Changing Device Descriptions

To change the device description for each dependent work station attached to the
5494 controller, use the Change Device Description (Display) CHGDEVDSP, or the
Change Device Description (Printer) CHGDEVPRT) commands

AS/400 Configuration Examples for the 5494 Remote Control Unit

Figure 11-7 on page 11-11 illustrates a programming example of an SDLC config-
uration with the 5494 controller. Figure 11-10 on page 11-14 illustrates an example
of an X.25 configuration with the 5494 controller. Figure 11-11 on page 11-15 is an
example of a token-ring attachment configuration with the 5494 controller. These
examples assume the following program levels:
OS/400 Version 2 Release 2 or higher for the AS/400 system.
DOS, PC Support/400, Version 1 Release 2 or higher (including Client Access)
for the independent work station.

The Matching Parameters diagrams (“SDLC Configuration Matching Parameters” on

page 11-11 , “X.25 Configuration Matching Parameters” on page 11-13, and
“Token-Ring Attachment Configuration Matching Parameters” on page 11-15) show
key parameters for configuring 5494 Remote Control Units. The diagrams repeat
some of the key parameters from the AS/400 commands that are shown for cre-
ating the line, controller, and device descriptions. They expand the scope of the
examples by showing the AS/400 network attributes, the 5494 parameters, Client

11-10 Remote Work Station Support V4R1

Access parameters, and the relationships among the parameters. The 5494 param-
eters are identified in two ways. The first is the dependent work station (DWS) con-
figuration screen field (for example, 11). The second is the Utility program
configuration text (for example, Default Local Network Name ).

For more information about 5494 controller parameters, see 5494 Remote Control
Unit Planning Guide, GA27-3936 or 5494 Remote Control Unit User's Guide,
GA27-3960. For more information about the Client Access parameters, see the
Client Access/400 for DOS with Extended Memory Setup book.

Synchronous Data Link Control Configuration Example

The following programming example shows a synchronous data link control (SDLC)
configuration to support the 5494 controller. Configure the SDLC line, controllers,
and device:

CRTLINSDLC LIND(NYLINE) RSRCNAME(LINð12) ONLINE(\NO) ROLE(\NEG) +

TEXT('SDLC line to 5494')

CRTCTLAPPC CTLD(NYAPPC) LINKTYPE(\SDLC) ONLINE(\NO) +

APPN(\YES) LINE(NYLINE) +
MAXFRAME(521) RMTNETID(\NETATR) +
RMTCPNAME(NY5494) EXCHID(ð73ðððð1) ROLE(\NEG) +
STNADR(ð1) NODETYPE(\LENNODE) +
TEXT(\BLANK)

Figure 11-7. SDLC Configuration Example

Notes:
1. Because APPN(*YES) is specified for the controller description, the APPC
device descriptions are automatically created as needed by AS/400 APPN
support.
2. Because the QAUTORMT system value is set on, the remote controller
description and the remote device descriptions are automatically created by the
system.

SDLC Configuration Matching Parameters

The following diagram shows the 5494, DOS Client Access, and AS/400 parame-
ters that need to match.

Chapter 11. Configuring 5494 Remote Control Units 11-11

AS/4ðð System 5494 Controller

Network Attributes DWS Configuration Screen 2 Network Information

┌───5 LCLLOCNAME S45P %─────────────┐ ┌────────────5 11 MYNET ────────────── Default local network name
│ ┌─5 LCLNETID MYNET%─────────┐ ┌─┼────┘ ┌─────────5 12 NY5494 ───────────── 5494 LU name
│ │ │ │ │ │ ┌─────5 13 NY5494 ───────────── 5494 CP name
│ │ │ │ │ │ │ 14 QRMTWSC ──────────── 5494 default mode name
│ │ │ │ ├───────┼──┼──5 H1 : 1 S45P ─────────────── AS/4ðð LU name
│ │ └─┼─┼───────┼──┼──5 H1 : 2 MYNET ────────────── AS/4ðð network name
│ │ │ │ │ │
│ │ Line Description │ │ │ │ DWS Configuration Screen 1 AS/4ðð connection
│ │ CRTLINSDLC %─────────────────┼─┼───┬───┼──┼──────5 AA = ð ──────────────── SDLC
│ │ │ │ │ │ │ DD = 1 ──────────────── Token-ring gateway
│ │ ┌─5 LIND NYLINE │ │ │ │ │ ┌───5 2 = ð1 ─────────────── 5494 station address
│ │ │ CNN \NONSWTPP %─────────┼─┼───┼───┼──┼───┼─────────┬───┐
│ │ │ DUPLEX \FULL %─────────────┼─┼───┼───┼──┼───┼─────────┼─┐ │
│ │ │ │ │ │ │ │ │ 6 6 6
│ │ │ │ │ │ │ │ │ 3 = ð 1 1 ð ð ð ð ──── Communications parameters
│ │ │ APPC Controller Description │ │ │ │ │ │ │ │ └───────────── Point-point
│ │ │ CTLD NYAPPC │ │ │ │ │ │ │ └─────────────── Duplex
│ │ │ LINKTYPE \SDLC %─────────┼─┼───┘ │ │ │ └───────────────── Nonswitched line
│ │ └── LINE NYLINE │ │ │ │ │
│ ├──── RMTNETID \NETATR %───────┼─┼───────┼──┼───┼─┐
│ │ RMTCPNAME NY5494 %───────┼─┼───────┼──┘ │ │
│ │ EXCHID ð73ðððð1 %──────┼─┼───────┼──────┤ │ K = 4ððð5494Eððð ───── 5494 token-ring address %─┐
│ │ ── │ │ │ │ │ │
│ │ STNADDR ð1 %────────────┼─┼───────┼──────┘ │ │
│ │ Automatically Created │ │ │ │ │
│ │ Remote Work Station │ │ │ │ Twinaxial independent work station │
│ │ Controller Description │ │ │ │ using DOS Client Access/4ðð │
│ │ ┌─5 CTLD NY549RMT │ │ │ │ │
│ │ │ TYPE 5494 │ │ │ │ CONFIG.PCS │
│ │ │ LINKTYPE \NONE │ │ │ │ │
│ │ │ RMTLOCNAME NY5494 %───────┼─┼───────┘ │ SFLR 1,I,,S45P │
│ │ │ │ │ ├───5 RTLN MYNET.DOSTWX1 │
└─┼─┼── LCLLOCNAME \NETATR │ │ │ ──── │
└─┼── RMTNETID \NETATR %───────┘ │ │ RTYP 525ð │
│ ├────────────────┼───5 EMLI S45P,2 │
│ │ │ ──── │
│ │ │ Token-ring independent work station │
│ │ │ using DOS PC Support/4ðð │
│ │ │ CONFIG.PCS │
│ │ │ │
│ │ │ SFLR 1,I,,S45P │
│ │ └───5 RTLN MYNET.DOSTRN1 │
│ │ ──── │
│ │ RTYP ITRN │
│ Automatically Created │ TRLI S45P,4ððð5494Eððð │
│ DWS Display Device Description │ & & │
│ DEVD NY54DSPðð └────────────────────────────┘ └───────────────────────────────┘
├── CTL NY549RMT
│ LOCADR ðð \ \ NY54DSPðð
│ Automatically created Port ð
│ DWS Printer Device Description Address ð
│ DEVD NY54PRT14
└── CTL NY549RMT
LOCADR 14 \\ \\ NY54PRT14
Port 2
Address 6
Figure 11-8. SDLC Configuration Matching Parameters

X.25 Configuration Example

The following programming example shows an X.25 configuration to support the
5494 controller. It configures the X.25 line, controllers, and device:

11-12 Remote Work Station Support V4R1

CRTLINX25 LIND(CHILINE) RSRCNAME(LINð21) +
LGLCHLE((ðð1 \PVC)(ðð2 \PVC)(ðð3 \SVCBOTH)) +
NETADR(111111111111111) CNNINIT(\LOCAL) +
ONLINE(\NO) X25DCE(\YES) +
TEXT('X.25 line for 5494')

CRTCTLAPPC CTLD(CHIAPPC) LINKTYPE(\X25) ONLINE(\NO) +

APPN(\YES) LINE(CHILINE) +
RMTNETID(\NETATR) RMTCPNAME(CHI5494) EXCHID(ð73ðððð1) +
NETLVL(1984) LGLCHLID(ðð2) +
NODETYPE(\LENNODE) +
TEXT('APPC controller for 5494')

Figure 11-9. X.25 Configuration Example

Notes:
1. Because APPN(*YES) is specified for the controller description, the APPC
device descriptions are created automatically by AS/400 APPN support.
2. Because the QAUTORMT system value is set on, the remote controller
description and the device descriptions are automatically created by the
system.

X.25 Configuration Matching Parameters

The following diagram shows the 5494, DOS Client Access, and AS/400 parame-
ters that need to match.

Chapter 11. Configuring 5494 Remote Control Units 11-13

AS/4ðð System 5494 Controller

Network Attributes DWS Configuration Screen 2 Network Information

┌──────5 LCLLOCNAME RCHAS218 %────────┐ ┌──────────5 11 CHINET ───────────── Default local network name
│ ┌────5 LCLNETID CHINET ────────┐ │ │ ┌────────5 12 CHI5494 ───────────── 5494 LU name
│ │ │ │ │ │ ┌─────5 13 CHI5494 ────────── 5494 CP name
│ │ │ │ │ │ │ 14 QRMTWSC ────────── 5494 default mode name
│ │ │ ├─────┼─┼──┼─5 H1 : 1 RCHAS218 ────────── AS/4ðð LU name
│ │ └──┼─────┼─┼──┼─5 H1 : 2 CHINET ───────────── AS/4ðð network name
│ │ │ │ │ │ H1 : 6 ðð1 ──────────────── AS/4ðð logical channel
│ │ │ │ │ │
│ │ Line Description │ │ │ │ DWS Configuration Screen 1 AS/4ðð connection
│ │ CRTLINX25 %──────────────────┼───┬─┼─┼──┼─────5 AA = 1 ──────────────── X.25
│ │ │ │ │ │ │ DD = 1 ──────────────── Token-ring gateway
│ │ ┌─5 LIND CHILINE │ │ │ │ │ ┌─5 2 = ð1 ─────────────── 5494 station address
│ │ ┌─┼─5 LGLCHLE ðð2 \PVC │ │ │ │ │ │ 4 = ð ð2 7 ─────────── X.25 subscription data
│ │ │ │ NETADR 111111111111111 │ │ │ │ │ │ ┌─────────┬───────────── Circuit type
│ │ │ │ │ │ │ │ │ │ │ 5 = 1 1 ð ð ð ───── X.25 configuration data
│ │ │ │ │ │ │ │ │ │ │ 6 = All defaults ──── X.25 software data
│ │ │ │ APPC Controller Description │ │ │ │ │ │ │ 7 = All defaults ──── Retry parameters
│ │ │ │ CTLD CHIAPPC │ │ │ │ │ │ │
│ │ │ │ LINKTYPE \X25 %──────────┼───┘ │ │ │ │ │
│ │ │ │ SWITCHED \NO %──────────┼─────┼─┼──┼─────┼─┘
│ │ │ └── LINE CHILINE │ │ │ │ │
│ ├──┼──── RMTNETID \NETATR %──────┐ │ │ │ │ │
│ │ │ RMTCPNAME CHI5494 ───────┼─┼─────┼─┼──┘ │
│ │ │ EXCHID ð73ðððð1 %─────┼─┼─────┼─┼────────┘ K = 4ððð5494Eððð ────── 5494 token-ring address %─┐
│ │ │ ── │ │ │ │ │
│ │ └──── LGLCHID ðð2 │ │ │ │ │
│ │ │ │ │ │ │
│ │ Automatically created │ │ │ │ │
│ │ Remote Work Station │ │ │ │ Twinaxial independent work station │
│ │ Controller Description │ │ │ │ using DOS Client Access/4ðð │
│ │ ┌─5 CTLD CHI54RMT │ │ │ │ │
│ │ │ TYPE 5494 └─┼─────┼─┼──┐ CONFIG.PCS │
│ │ │ LINKTYPE \NONE ┌────┼─────┘ │ │ SFLR 1,I,,RCHAS218 │
│ │ │ │ │ │ ├────5 RTLN CHINET.DOSTWX1 │
│ │ │ RMTLOCNAME CHI5494 ────┼────┼───────┘ │ ──── │
├─┼────┼── LCLLOCNAME \NETATR │ │ │ RTYP 525ð │
│ └────┼── RMTNETID \NETATR %───┘ ├──────────┼────5 EMLI RCHAS218,2 │
│ │ │ │ ─────── │
│ │ │ │ │
│ │ │ │ Token-ring independent work station │
│ │ │ │ using DOS Client Access/4ðð │
└──────┼───────────────────────────────┼──────────┤ CONFIG.PCS │
│ │ │ │
│ │ │ SFLR 1,I,,RCHAS218 │
│ │ └────5 RTLN CHINET.DOSTRN1 │
│ │ ─── │
│ │ RTYP ITRN │
│ Automatically created │ TRLI RCHAS218,4ððð5494Eððð │
│ DWS Display Device Description│ & & │
│ DEVD CHI5DSPðð └──────────────────────────┘ └────────────────────────────────┘
├── CTL CHI54RMT
│ LOCADR ðð \ \ CHI5DSPðð
│ Automatically created Port ð
│ DWS Printer Device Description Address ð
│ DEVD CHI5PRT14
└── CTL CHI54RMT
LOCADR 14 \\ \\ CHI5PRT14
Port 2
Address 6

Figure 11-10. X.25 Configuration Matching Parameters

Token-Ring Attachment Configuration Example

The following programming example is for an AS/400 token-ring attachment config-
uration (the 5494 controller is attached to the AS/400 system through a token-ring
network as in Figure 11-2 on page 11-3). It configures the token-ring line, control-
lers, and device:

11-14 Remote Work Station Support V4R1

CRTLINTRN LIND(DALTRLAN) RSRCNAME(LINð61) +
ONLINE(\NO) MAXFRAME(4ð6ð) +
ADPTADR(4ððððððððððð) +
AUTOCRTCTL(\YES) +
TEXT('Token-ring line for 5494')

Figure 11-11. Token-Ring Attachment Configuration Example

Notes:
1. Because the autocreate controller (AUTOCRTCTL) parameter is set to *YES,
the APPC controller will be created by the system. The APPN Support book
has more information about automatic configuration.
2. Because the QAUTORMT system value is set on, the remote controller
description and the device descriptions are automatically created by the
system.

Token-Ring Attachment Configuration Matching Parameters

The following diagram shows the 5494, DOS Client Access, and AS/400 parame-
ters that need to match.
AS/4ðð System 5494 Controller

Network Attributes DWS Configuratio n Screen 2 Network Information

┌───5 LCLLOCNAME RCHAS218 %─────────┐ ┌─────────────5 11 DALNET ───────────── Default local network name
│ ┌─5 LCLNETID DALNET─────────┐ │ │ ┌───────────5 12 DAL5494───────────── 5494 LU name
│ │ │ │ │ │ ┌────────5 13 DAL5494───────────── 5494 CP name
│ │ │ │ │ │ │ 14 QRMTWSC ──────────── 5494 Default mode name
│ │ │ │ │ │ │ ┌──────515 4ððð5494Eðð───────── 5494 Token-ring address
│ │ │ ├─────┼─┼──┼──┼─5 H1 : 1 RCHAS218 ─────────── AS/4ðð LU name
│ │ └───┼─────┼─┼──┼──┼─5 H1 : 2 DALNET────────────── AS/4ðð network name
│ │ ┌────┼─────┼─┼──┼──┼─5 H1 : 5 4ððððððððððð ─────── Token-ring address of AS/4ðð
│ │ │ │ │ │ │ │
│ │ Line Description │ │ │ │ │ │ DWS Configuration Screen 1 AS/4ðð connection
│ │ CRTLINTRN %──────────────┼────┼──┬──┼─┼──┼──┼───── AA = 4 ──────────────── Token-ring
│ │ ┌─5 LIND DALTRLAN │ │ │ │ │ │ │
│ │ │ ADPTADR 4ððððððððððð %──┘ │ │ │ │ │ │
│ │ │ AUTOCRTCTL \YES │ │ │ │ │ │
│ │ │ │ │ │ │ │ │
│ │ │ Automatically created │ │ │ │ │ │
│ │ │ APPC Controller Description │ │ │ │ │ │
│ │ │ LINKTYPE \LAN %───────────┼──┘ │ │ │ │
│ │ └── LINE DALTRLAN │ │ │ │ │
│ ├──── RMTNETID \NETATR %──────┐ │ │ │ │ │
│ │ RMTCPNAME DAL5494 ───────┼──┼─────┼─┼──┘ │
│ │ ADPTADR 4ððð5494Eððð %───┼──┼─────┼─┼─────┘
│ │ Automatically Created │ │ │ │
│ │ Remote Work Station │ │ │ │ Twinaxial independent work station
│ │ Controller Description │ │ │ │ using DOS Client Access/4ðð
│ │ ┌─5 CTLD DAL54RMT └──┼─────┼─┼──┐ CONFIG.PCS
│ │ │ TYPE 5494 │ │ │ │ SFLR 1,I,,RCHAS218
│ │ │ LINKTYPE \NONE │ │ │ └─────5 RTLN DALNET.DOSTWX1
│ │ │ RMTLOCNAME DAL5494%──────────┼─────┼─┘ RTYP 525ð
└─┼─┼── LCLLOCNAME \NETATR └─────┼──────────5 EMLI RCHAS218 ,2
└─┼── RMTNETID \NETATR %───────────────┘
│ Automatically created
│ DWS Display Device Description
│ DEVD DAL5DSPðð
├── CTL DAL54RMT
│ LOCADR ðð \ \ DAL5DSPðð
│ Automatically created Port ð
│ DWS Printer Device Description Address ð
│ DEVD DAL5PRT14
└── CTL DAL54RMT
LOCADR 14 \\ \\ DAL5PRT14
Port 2
Address 6

Figure 11-12. Token-Ring Attachment Configuration Matching Parameters

Chapter 11. Configuring 5494 Remote Control Units 11-15

Managing the 5494 Remote Control Unit
This section describes how to manage your 5494 controller once it is active.

For easier retrieval, use a common prefix for every line, controller, and device
description name you create that pertains to the 5494 Remote Control Unit. For
example, a user in New York could name the line description NYLINE, the APPC
controller description NYAPPC, the remote work station controller description
NYRWS, and the dependent work station description NYDWS.

For remote controller descriptions that are automatically created, the names are as
follows:
xxxxxRMTyy xxxxx is the first 5 characters of the remote location name. If the
remote location name is less than 5 characters, suppressed blanks are
used and yy is either blanks or 00-ZZ.

For remote display descriptions that are automatically created, the names are as
follows:
xxxxDSPyyz xxxx is the first 4 characters of the remote location name of the 5494
remote controller, yy is the location address, and z is the shared session
number for session 1, 2, or 3 on a shared session display. For the base
session on a shared session display and for displays not having shared
sessions, the z is blank. The 3488 Model V Display Station supports a
number of shared sessions.

For remote printer descriptions that are automatically created, the names are as
follows:
xxxxPRTyy xxxx is the first 4 characters of the remote location name of the 5494
remote controller and yy is the location address. If the remote location
name is less than 4 characters, the blanks are suppressed.
Note: This provides a way to associate the name of the 5494 remote controller
with the devices attached to it.

To take advantage of the automatic device creation for existing 5494 Remote
Control Unit descriptions, you need to use the Change Controller Description
(Remote WS) (CHGCTLRWS) command to set the AUTOCRTDEV parameter to
*ALL.

By naming configuration descriptions with the prefix NY throughout, the user can
easily check the status of the configuration through the Work with Configuration
Status (WRKCFGSTS) command. By entering the command WRKCFGSTS *LIN
NY* the user can check the status of the line, APPC controller, and APPC devices.
For example, if “Synchronous Data Link Control Configuration Example” on
page 11-11 was used to create the configuration for your 5494 and you used the
Work With Configuration Status command as suggested, the following display is
shown:

11-16 Remote Work Station Support V4R1

à ð
Work with Configuration Status WASHSYS
ð3/17/94 17:38:3ð
Position to . . . . . __________ Starting characters

Type options, press Enter.

1=Vary on 2=Vary off 5=Work with job 8=Work with description
9=Display mode status ...

Opt Description Status -------------Job--------------

__ NYLINE ACTIVE
__ NYAPPC ACTIVE
__ NY5494 ACTIVE
__ QRMTWSC ACTIVE/TARGET NY5494 QUSER ðð5832
__ QRMTWSC ACTIVE/SOURCE NY5494 QUSER ðð5832

To check which controller descriptions are related to the 5494 Remote Control Unit,
the user can enter WRKCFGSTS *CTL NY*. From this display, the user can check
the status of 5494 controller descriptions and work with related configuration
descriptions down to the APPC and remote work station devices.

à ð
Work with Configuration Status WASHSYS
ð3/17/94 18:49:16
Position to . . . . . ____________ Starting characters

Type options, press Enter.

1=Vary on 2=Vary off 5=Work with job 8=Work with description
9=Display mode status ...

Opt Description Status -------------Job--------------

__ NYAPPC ACTIVE
__ NY5494 ACTIVE
__ QRMTWSC ACTIVE/TARGET NY5494 QUSER ðð5832
__ QRMTWSC ACTIVE/SOURCE NY5494 QUSER ðð5832
__ NY549RMT ACTIVE
__ NY54DSPðð SIGNON DISPLAY

You can see the APPC device description that is associated with the device
description of the dependent work station. Do this by pressing F15 on the display of
the Display Device Description (DSPDEVD) command. Likewise, you can see the
APPC device description that is associated with a Remote Work Station controller
description. Do this by pressing F15 on the display of the Display Controller
Description (DSPCTLD) command.

Active APPC Subsystem Required

For APPC sessions between the 5494 controller and the AS/400 system, an APPC
subsystem (QCMN or QBASE) must be active. Furthermore, QBASE must not be in
restricted mode.

System Reference Codes and the 5494 Remote Control Unit

System reference codes (SRCs) are alphanumeric error messages that may
appear on your remote work station display or on the liquid crystal display (LCD) of
the 5494 controllers. On your remote work station display, these codes contain four
to six characters, and appear flashing in a corner of the display. For a list of SRCs,
their causes, and the action they require, refer to the 5494 Remote Control Unit
User's Guide, GA27-3960.

Chapter 11. Configuring 5494 Remote Control Units 11-17

| Changing the 5494 Remote Control Unit Password
| Use the Change RWS Controller Password (CHGRWSPWD) command to change
| the 5494 Remote Control Unit password. The password is required to use some
| functions of the 5494 Utility Program from a programmable work station (PWS).

| For more information about the CHGRWSPWD command, see the CL Reference.
| This function requires release 3 or later on the 5494 Remote Control Unit.

| Retrieving Vital Product Data

| Vital product data (VPD) is collected by OS/400 for the 5494 Remote Control Unit
| and attached nonprogrammable work stations (NWS) at the time the remote work
| station (RWS) controller is varied on. VPD, such as model, serial number, and
| release level, can be displayed or printed by using the Display Controller
| Description (DSPCTLD) command, specifying the RWS controller. In addition, VPD
| for the control unit and the attached nonprogrammable work stations may be
| retrieved by a program using the Retrieve Controller Description (QDCRCTLD) API
| format for the RWS controller category.

| See the System API Reference book for more information about the QDCRCTLD
| API.

11-18 Remote Work Station Support V4R1

Part 3. Configuring for 3270 Remote Device Support
Chapter 12. Using 3270 Device Support . . . . . . . . . . . . . . . . . . . . 12-1
3270 Device Support—Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
5250 Data Stream Optimization Support . . . . . . . . . . . . . . . . . . . . . 12-1
Creating a Data Area for the 5250 Optimization Value . . . . . . . . . . . . 12-3
Creating and Changing the Controller Description . . . . . . . . . . . . . . 12-3
Authority to the Data Area . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
3270 Device Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Configuration of Keyboard Changes . . . . . . . . . . . . . . . . . . . . . . . . 12-5
3270 and 5250 Keyboards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Keyboard Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Field Mark Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Field Exit Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Numeric-Only Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Reset Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Clear, System Request, and Test Keys . . . . . . . . . . . . . . . . . . . 12-7
Home and Erase Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Corresponding 3270 Keys and 5250 Functions . . . . . . . . . . . . . . . . 12-7
3270 and 5250 Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Display Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Characters and Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Extended Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Embedded Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-10
Printing Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Break Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Operator Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Operator Error Message Codes . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Field Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-12
Blink, Reverse Image, and Underline Attributes . . . . . . . . . . . . . . . 12-13
3270-to-5250 Keyboard Mapping . . . . . . . . . . . . . . . . . . . . . . . 12-13
Displaying a Keyboard Map . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Changing a Keyboard Map . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Keyboard Mapping for 3270—Tips . . . . . . . . . . . . . . . . . . . . . 12-17

Chapter 13. 3270-Type Device Configuration Examples . . . . . . . . . . 13-1

3270 Remote Attachment—Scenario . . . . . . . . . . . . . . . . . . . . . . . 13-1
3270 Display Station Pass-Through—Scenario . . . . . . . . . . . . . . . . 13-2
Using Start 3270 Emulation Command . . . . . . . . . . . . . . . . . . . 13-2
Selecting SNA 3270 Pass-Through Option . . . . . . . . . . . . . . . . . 13-3
3270-Type Remote Controllers in a Token-Ring Network . . . . . . . . . . . . 13-5
The Configuration Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Automatic Creation of 3270-Type Device Descriptions . . . . . . . . . . . . 13-8
Using the APPC Controller to Attach 3270-Type Devices . . . . . . . . . . 13-8
Attachment of DBCS-Capable Devices to 3270 Controllers . . . . . . . . 13-11
Configuration Examples for ISDN . . . . . . . . . . . . . . . . . . . . . 13-11

Chapter 14. Configuring SNA Pass-Through . . . . . . . . . . . . . . . . . 14-1

SNA Pass-Through—Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Upstream and Downstream Devices . . . . . . . . . . . . . . . . . . . . . . . . 14-1

 Copyright IBM Corp. 1997

Configuring a Single AS/400 System for SNA Pass-Through
Support—Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Connection A: Configuring Upstream to the Target System . . . . . . . . 14-4
Connection B: Configuring Downstream to the Source Devices . . . . . . 14-5
Grouping of SNA Pass-Through Devices . . . . . . . . . . . . . . . . . . 14-7
Additional Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Configuring SNA Pass-Through with an Intermediate AS/400 Node . . . . . 14-7
Connection A: Configuring Upstream to Target System . . . . . . . . . . . 14-8
Connection B: Configuring Downstream to the Source AS/400 System . 14-9
Connection C: Configuring Upstream to the Intermediate AS/400 System 14-9
Connection D: Configuring Downstream to Dependent Devices . . . . . 14-10
Several Intermediate AS/400 Systems . . . . . . . . . . . . . . . . . . . . 14-11
Configuring a Mixture of Supported and Nonsupported Devices . . . . . . . 14-11
Connection A: Configuring Upstream to the Target System . . . . . . . 14-12
Connection B: Configuring Downstream to the Source System . . . . . 14-12
Connection C: Configuring Upstream to the Intermediate System . . . . 14-12
Connection D: Configuring Downstream to Dependent Devices . . . . . 14-13
Connection E: Configuring Downstream to 5250 Devices . . . . . . . . 14-13
Configuring SNA Pass-Through to Support Several Source AS/400 Systems 14-13
Connection A: Configuring Upstream to Target System . . . . . . . . . . 14-14
Connection B: Configuring Downstream to Dependent Device 327x 1 . 14-14
Connection C: Configuring Attachment to Intermediate Node 2 . . . . . 14-14
Connection D: Configuring Attachment to Intermediate Node 1 . . . . . 14-15
Connection E: Configuring Upstream to Target System 2 . . . . . . . . 14-15
Connection F: Configuring Downstream to Dependent 327x Device 2 . 14-15
Grouping of Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
Configuring the Group Function . . . . . . . . . . . . . . . . . . . . . . 14-15
SNA Pass-Through Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16

Chapter 15. Distributed Host Command Facility . . . . . . . . . . . . . . . 15-1

Distributed Host Command Facility—Definition . . . . . . . . . . . . . . . . . . 15-1
The AS/400 System in an HCF Environment . . . . . . . . . . . . . . . . . . . 15-1
Host Command Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Host System Requirements for a DHCF Session . . . . . . . . . . . . . . . 15-2
Host Command Facility—Benefits . . . . . . . . . . . . . . . . . . . . . . . . 15-2
HCF Network Node—Definition . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Display Stations in an HCF Network . . . . . . . . . . . . . . . . . . . . . . 15-4
How OS/400 DHCF Interconnects with Multiple Systems . . . . . . . . . . 15-4
AS/400 3270 Emulation with OS/400 DHCF—Scenario . . . . . . . . . 15-4
Host System Programming Considerations for DHCF . . . . . . . . . . . . . . 15-5
VTAM/NCP Programming—Tips . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Physical Unit Definition Parameters . . . . . . . . . . . . . . . . . . . . . 15-6
Logical Unit Definition Parameters . . . . . . . . . . . . . . . . . . . . . . 15-7
Host System Work Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
DHCF Configuration Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Line Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-8
Controller Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Device Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Configuring the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Using DHCF for Remote Management . . . . . . . . . . . . . . . . . . . . . 15-10
Logging on the Host System . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-11
DHCF Logon Modes (via HCF) . . . . . . . . . . . . . . . . . . . . . . . . 15-11
SNA and Emulation Device Logon Modes . . . . . . . . . . . . . . . . 15-11
BSC-attached Device Logon Mode . . . . . . . . . . . . . . . . . . . . 15-11

Remote Work Station Support V4R1

Start the DHCF Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Ending the DHCF Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Summary of HCF Session Commands Relating to the AS/400 System . 15-13
Changing HCF Commands, Online Help Information, and Messages . 15-13
HCF Host System 3270 Terminal Requirements . . . . . . . . . . . . . . . . 15-13
Extended Display Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Display Station Requirements for DHCF . . . . . . . . . . . . . . . . . . . . 15-14
3270 and 5250 Keyboard and Display Differences . . . . . . . . . . . . . 15-14
Messages in DHCF Sessions . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
DHCF Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Differences from System/36 DHCF Support . . . . . . . . . . . . . . . . . 15-15
Differences from System/38 DHCF Support . . . . . . . . . . . . . . . . . 15-15

Chapter 16. Network Routing Facility . . . . . . . . . . . . . . . . . . . . . 16-1

Chapter 17. SNA Primary LU2 Support . . . . . . . . . . . . . . . . . . . . 17-1

SNA Primary LU2 Support—Definition . . . . . . . . . . . . . . . . . . . . . . . 17-1
SNA Primary LU2 Support Performance—Tips . . . . . . . . . . . . . . . . 17-2
Differentiating SNA Primary LU2 Support from Similar Functions . . . . . . . 17-2
Benefits of SNA Primary LU2 Support . . . . . . . . . . . . . . . . . . . . . . . 17-3
Devices Supported by SNA Primary LU2 Support . . . . . . . . . . . . . . . . 17-4
Software Requirements for SNA Primary LU2 Support . . . . . . . . . . . . . 17-5
SNA Primary LU2 Support Sessions . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Configuring the AS/400 System for SNA Primary LU2 Support . . . . . . . . 17-6
Automatic Configuration of Devices . . . . . . . . . . . . . . . . . . . . . . . 17-6
Reducing Automatic Creation Time . . . . . . . . . . . . . . . . . . . . . 17-7
Configuration Steps for SNA Primary LU2 Support . . . . . . . . . . . . . . 17-8
Step 1: Configuring the Line to the Host Network . . . . . . . . . . . . 17-8
Step 2: Configuring the Host Controller . . . . . . . . . . . . . . . . . . 17-9
Step 3: Configuring the Device . . . . . . . . . . . . . . . . . . . . . . 17-11
Step 4: Configuring the Host System . . . . . . . . . . . . . . . . . . . 17-19
Starting SNA Primary LU2 Support Sessions . . . . . . . . . . . . . . . . . . 17-20

Part 3. Configuring for 3270 Remote Device Support

3270 Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Customizing Your SNA 3270 Display Keyboard Map . . . . . . . . . . . . 17-20
AS/400 Work Station Printing . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Creating a Printer Device Description for the Associated Printer . . . . 17-21
Ending SNA Primary LU2 Support Sessions . . . . . . . . . . . . . . . . . . 17-21
Examples of VTAM Logon Mode Tables and Definitions . . . . . . . . . . . 17-21
Logon Mode Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Network Control Program Definitions . . . . . . . . . . . . . . . . . . . . . 17-23
VTAM Definitions for the AS/400 System . . . . . . . . . . . . . . . . . . 17-24
VTAM Definitions for the 3174 Establishment Controller . . . . . . . . . . 17-26
Matching Parameters for an SDLC Line . . . . . . . . . . . . . . . . . . . . . 17-26
Matching Parameters for a Token-Ring Line . . . . . . . . . . . . . . . . . . 17-27

| Chapter 18. Dependent LU Requester Support . . . . . . . . . . . . . . . 18-1

| Dependent LU Requester Support—Definition . . . . . . . . . . . . . . . . . . 18-1
| Devices Supported by Dependent LU Requester . . . . . . . . . . . . . . . . 18-2
| Before You Begin Configuring the AS/400 System for Dependent LU
| Requester . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
| Before You Begin Creating Device and Controller Descriptions . . . . . . . . 18-2
| AS/400 DLUR Session Activation . . . . . . . . . . . . . . . . . . . . . . . . 18-2
| Automatic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
| Dependent Logical Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
| Dependent PU Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
| Dependent Location Name . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
| Error Recovery Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
| Configuration Steps for Dependent LU Requester . . . . . . . . . . . . . . 18-4
| Step 1: Configuring the Host Controller for DLUR Support . . . . . . . 18-4
| Step 2: Configuring the Device . . . . . . . . . . . . . . . . . . . . . . . 18-6
| Logon Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
| 3270 Device Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
| VTAM Cross-Domain Resource Definition . . . . . . . . . . . . . . . . . . . . 18-7
| VTAM Definitions for the AS/400 System for DLUR Support . . . . . . . . 18-8
| VTAM Definitions for the AS/400 System for APPN Connections . . . . . 18-8
| Matching Parameters for the AS/400 DLUR and VTAM . . . . . . . . . . 18-11
| Matching Parameters for the APPN Connection between the AS/400 and
| VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
| Error Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12

Remote Work Station Support V4R1

Chapter 12. Using 3270 Device Support
| This chapter discusses how the AS/400 system uses Systems Network Architecture
| (SNA) communications to support remotely attached 3174 and 3274 controllers and
| attached 3270 display stations and printers. Because the 3270 data streams can be
| translated into 5250 data streams, the controller and attached printer can appear to
| the AS/400 system and application programs as a remote 5251 display and
| 5250-family remote work station printer.

3270 Device Support—Definition

The 3270 device support function supports the following devices:
3174 Establishment Controller
3274 Control Unit
3270 display stations and printers
All emulators conforming to 3274 Control Unit Model 31C protocol
3287 Printer
Personal computers using 3270 emulation
Note: Double-byte character set (DBCS) capable devices are supported.

The 3270 device support uses the following communications protocols (rules
controlling the communication and transfer of data between devices in a communi-
cations system):
Synchronous data link control (SDLC)
IBM Token-Ring Network
X.25 Network
Ethernet Network
Integrated Services Digital Network (ISDN)
| Note: When starting a session after processing the start-data traffic request, the
| AS/400 system cannot support a device that sends data first. The AS/400
| system must send data to the device first.

5250 Data Stream Optimization Support

In order to decrease line traffic for 3270 displays the OS/400 3270 device support
optimizes all 5250 data streams before they are converted into 3270 data streams.
For some applications this may be undesirable. To disable the 5250 data stream
optimization support, there is a new procedure that allows you to control whether or
not the 5250 data stream is optimized before it is converted into a 3270 data
stream.

5250 data stream optimization support is used by default for 3270 translated data
when the system communicates with 3270-type displays using the following com-
munications support:
3270 remote attach

 Copyright IBM Corp. 1997 12-1

Distributed host command facility (DHCF)
Network routing facility (NRF)
SNA Primary LU2 Support (SPLS)
TELNET

The 5250 optimization support for 3270 attached devices is a configurable value on
all controller descriptions that support 3270 attached devices. The value is set
according to information in a data area that has the same name as the controller
description. The value that is set in the object is only changed if a change controller
description command is used and the value in the data area is different from what
is set in the controller description object. The value is not changed if the data area
does not exist.

The 5250 optimization value affects the controller descriptions that support 3270
remote attachment. The controller types are:
APPC controller
Remote workstation controller
Retail controller
Finance controller
Host controller used for SNA Primary LU2 support (SPLS), Network Routing
Facility (NRF) support, Distributed Host Command Facility (DHCF)
Virtual workstation controller used for TELNET connections.

Because the information is being added to the controller description, each controller
description can have a different value for the 5250 data stream optimization
support. Some 3270 display stations attached to one AS/400 controller description
might be using the 5250 optimization support. Other 3270 displays attached to a
different AS/400 controller description might be suppressing the 5250 data stream
optimization support.

To change the 5250 optimization value that was set in the controller description,
change the data area (or create the data area if it does not exist) and change the
controller description using a Change Controller Description (CHGCTLxxx)
command. Every time a CHGCTLxxx command is used the system checks for a
data area containing the 5250 optimization value. If the data area exists, the 5250
optimization value is compared to what exists in the controller description object. If
the value is different, the value is changed in the controller description object. (If
the data area has been deleted, the value does not change from the previously set
value.)

The 5250 optimization value in the controller description object can only be
changed when the controller description is varied off. If an attempt to change a
different parameter on the controller description fails when the controller is varied
on (CPF2615 Controller xxx must be varied off for this operation) and the param-
eter being changed is usually successful even when the controller is varied on
(such as TEXT parameter), check for the existence of this data area.

If the data area exists, one of the following must be performed:

Vary off the controller description.

12-2 Remote Work Station Support V4R1

Delete the data area.
Change the value in the data area so that it matches what is configured in the
controller object. Then the device configuration code will not attempt to change
the 5250 optimization value in the controller description object.

Creating a Data Area for the 5250 Optimization Value

Use the Create Data Area (CRTDTAARA) command to create a data area to
contain the 5250 data stream optimization (OPTDTASTR) value. The value is asso-
ciated with controller descriptions that allow attachment of 3270 displays.
There can only be one data area for each controller description and one 5250
data stream optimization value for each data area.
The name of the data area must be the same name as the controller
description for which the 5250 data stream optimization value is to be updated.
The data area must be created in library QSYS.
The type of data must be character.
The length of the data area must be 15 characters.
The value must be OPTDTASTR(*YES) or OPTDTASTR(*NO). *YES specifies
that the 5250 data stream optimization should be enabled for 3270 devices
associated with the controller descriptions. *NO specifies that the 5250 data
stream optimization should be suppressed for 3270 devices associated with the
controller description.

See the following programming example to create the data area.

CRTDTAARA DTAARA(QSYS/CTLð1) TYPE(\CHAR) LEN(15)
VALUE('OPTDTASTR(\YES)')
TEXT('This is the 525ð optimization value for CTLð1.')

Creating and Changing the Controller Description

The 5250 data steam optimization value is associated with the following Create
Controller Description commands and the Change Controller Description
commands:
CRTCTLHOST (HOST) command and CHGCTLHOST (HOST) command
CRTCTLAPPC (APPC) command and CHGCTLAPPC (APPC) command
CRTCTLRWS (RWS) command and CHGCTLRWS (RWS) command
CRTCTLRTL (Retail) command and CHGCTLRTL (Retail) command
CRTCTLFNC (Finance) command and CHGCTLFNC (Finance) command
CRTCTLVWS (Virtual) command and the CHGCTLVWS (Virtual) command

The program that creates or changes the controller description looks for a data
area that has the same name as the controller. If the program finds a data area
with a valid format and a valid value, it is configured in the controller description.
When a CHGCTLxxx command is used, the 5250 optimization value is changed
only if the value in the data area is different from the value in the controller object.

Chapter 12. Using 3270 Device Support 12-3

Notes:
1. The Display Data Area (DSPDTAARA) command can be used to view the con-
tents of the data area. There is no method to display the 5250 data stream
optimization value associated with the controller description.
2. There is no message support available to call out the 5250 data stream opti-
mization value in the controller description if there is a problem with the config-
uration.
3. The following messages are displayed if the 5250 data stream optimization
value in the data area is not valid:
CPD0084 xxx not valid for parameter OPTDTASTR.
This message is sent if the value within the OPTDTASTR operand is not
*YES or *NO. Note that uppercase and lowercase characters are supported
within the data area. Embedded blanks cannot be used. The controller
description will not create or change if this error is encountered.
CPD2611 Parameter not valid.
This message is sent when the data within the data area is not recognized
as the 5250 data stream optimization value. This error does not stop the
create or change controller command. The data area might exist for a dif-
ferent reason than to affect the 5250 data stream optimization value of the
controller description object.

Once the change is made to the controller description, it remains in affect until the
controller description is changed again. Then the value is changed depending on
the value in the data area at that time, or it is not changed if the data area has
been deleted.

Use the CHGCTLxxx command after the data area has been changed to change
the 5250 data stream optimization value in the controller description.

Authority to the Data Area

You must have at least *USE authority to the data area object to use the create or
change controller command. The data area must be created with authority of *USE
(or higher). Every user who is using the create and change controller commands
must be given explicit authority to the data area object of *USE or higher.

The following message is displayed if the operator does not have the appropriate
authority to the data area object:
CPF9802 Not authorized to object xxxx in QSYS.
The controller description is not created or changed if this error is encountered.

3270 Device Capabilities

Use the following figure to determine the capabilities to specify when configuring a
3270 device:

12-4 Remote Work Station Support V4R1

Table 12-1. 3270 Device Capabilities
Device Type Device Capabilities
3277 This display station supports generic 3270 data stream. Extended
attributes, such as underlining, blink, reverse image, or color are not
supported.
| 3278 This display station supports extended attributes, such as blink,
| reverse image, and underlining if requested by the OS/400 DDS (data
| description specifications) keywords. The 3278 Model 4 supports a 43
| x 80 display size for no translation operations. The 3278 Model 5
| supports a 27 x 132 display size.
| 3279 This display station supports color attributes and the extended data
| stream attributes sent for a 3278 device. The color attributes are
| determined (in the same manner as a 5292 Full Color Display) by
| interpreting the DDS attributes as blink, high intensity, or the DDS
| color keywords.
| For more information about these attributes, see the topic “Field
| Attributes” on page 12-12 and the DDS Reference book.
| The 3279 Model 5 supports a 27 x 132 display size.
3287 This printer supports SNA character string (SCS) commands and
orders.
Note: Character options that cannot be printed are accepted but
ignored. The Copy to printer option is not supported. In addi-
tion, feature 9660 must be installed to support the SCS com-
mands and orders.

Configuration of Keyboard Changes

AS/400 utilities, source entry utility (SEU), and screen design aid (SDA), and some
user application programs for the 3270 may require operator keystroke changes on
the AS/400 system.

As an operator at a 3277, 3278, or 3279 keyboard, you can use most of the fea-
tures and functions available on a similarly configured and authorized 5250 work
station. You can also configure the keyboard to support the 5250 function and
command (CMD) keys. For a list of 5250 functions and their corresponding 3270
keys, refer to Table 12-2 on page 12-7.

3270 and 5250 Keyboards

This topic discusses the similarities and differences between the keyboards of the
5250 and 3270 display stations. Compensating for these keyboard differences is
also discussed.

3270 typewriter keyboards are fully supported. All other keyboards may be used,
but with limited function support. 3270 devices do not support magnetic stripe
reader and a selector light pen.

For more information about the 3270 and 5250 keyboards, see the 3270 Device
Emulation Support book.

Chapter 12. Using 3270 Device Support 12-5

Keyboard Differences
Specifically requested locking and unlocking of the 5250 keyboard cannot be done.
The 3270 keyboard is restored on each write operation to the display if a change-
of-direction command indicator is used for that write operation.

The locations of some keys on the 3277, 3278, and 3279 keyboards are different
than those of the 5251 keyboard. The online help information shows the differences
between the 5250 and 3270 keyboard layouts. To view a 3270 Help display at any
time, press PF2 (the default). Any data on the display is saved and then restored at
the end of the help procedure.

Field Mark Key

The 3270 Field Mark key is displayed as a semicolon with a line above it but is
printed as an asterisk (*). On the 5250 keyboard, this key is both displayed and
printed as a backslash (\).

Field Exit Fields

To emulate the field exit function required on the 5250 keyboard using the 3270
keyboard, specify that the ending attribute should not skip automatically. Then,
press the End of Field (EOF) key followed by the Field Advance or Forward Tab
keys.

The 3270 devices do not have Field Exit + or Field Exit - keys that will right-justify
the field and add the sign. Therefore, 3270 devices present a plus sign (+) in the
first position of the field.

If necessary, replace the plus sign with a minus sign (-), and type the numeric
value of the field. When the Enter key is pressed, the field is right-justified and filled
with necessary blanks.

Numeric-Only Field
The 3277 display station does not support the numeric lock feature. The 5250
numeric-only fields, allowing characters 0 through 9, period (.), plus sign (+), minus
sign (–), and space characters, have numeric and unprotected attributes on the
3270 device. If the numeric lock feature is installed on a 3278 or 3279 display
station, the combination of numeric and unprotected attributes causes the NUM
symbol to appear on these displays, and the only acceptable keys are the charac-
ters 0 through 9, period (.), plus sign (+), minus sign (–), and Dup. Any other char-
acter keys lock the keyboard, requiring it to be reset. Command keys (such as the
Tab and Enter keys) do not lock the keyboard. If either the + or space character is
required in a field, you can override the numeric lock by pressing the Shift key.

Reset Key
The 5250 Reset key functions cannot be performed by the 3270 Reset key.
However, you can specify a PF key to be assigned to the 5250 reset function. You
can also use the Enter key for the reset function.

When a message is sent requiring the Reset key to be pressed, the message con-
tains the 3 characters

_ \\

12-6 Remote Work Station Support V4R1

in columns 76, 77, and 78 of the message line. (The three characters are: 1 blank
followed by 2 asterisks.) These 3 characters indicate that the PF key assigned to
the 5250 reset function must be pressed before processing can continue. For
example, on a 5250 display, the user might see the message Command key not
valid. The same message appears on a 3270 display as:

Command key not valid _\\_

Clear, System Request, and Test Keys

The 3270 Clear, System Request (Sys Req), and Test keys all cause the loss of all
data on the display. Therefore, if the AS/400 3270 support detects the 3270 Clear
key, the system restores the display to the data on the last display sent by the
system.

To perform the 5250 system request function, press F11 (the default). You will
return to the previous display after the system request function ends.

The 5250 Sys Req key cannot be locked. However, if the 3270 keyboard is locked,
you cannot press the 3270 PF11 key for the 5250 system request function. For
example, if the application program is in a loop, the system operator must manually
cancel the job from another work station rather than use the 5250 system request
option. The 3270 keyboard does not acknowledge the PF11 key if pressed while a
command is running for an indefinite period of time.

Home and Erase Keys

The 3270 Home key places the cursor in the first unprotected position of the
display. If the display has no unprotected position, the 5250 Home key places the
cursor in row 1, column 1 unless there is an insert cursor (IC) address remaining
from the last write operation.

The 3270 Erase Input key clears all unprotected positions on the display to null
characters and places the cursor in the first unprotected position. The 5250 Erase
Input key clears only changed fields to null characters. The cursor is placed in row
1, column 1 unless there is an insert cursor (IC) address.

If an input field does not exist, the 5250 Tab, Back Tab, and New Line keys place
the cursor in row 1, column 2. This position is the home address.

Corresponding 3270 Keys and 5250 Functions

The following figure shows how to perform various 5250 functions with the corre-
sponding 3270 default PF keys:

Table 12-2 (Page 1 of 2). Various 5250 Functions

5250 Key Function Default 3270 Keys to Select Function
Help PF1
3270 Help PF2
Clear PF3
Print PF4
Display Embedded Attributes PF5

Chapter 12. Using 3270 Device Support 12-7

Table 12-2 (Page 2 of 2). Various 5250 Functions
5250 Key Function Default 3270 Keys to Select Function
Test Request PF6
Roll Down PF7
Roll Up PF8
Error Reset PF10 (System/38), PF10 or the Enter key
(System/36 and AS/400 system)
Sys Req PF11
Record Backspace PF12
F1 through F12 PA1, then PF1 through PF121
F13 through F24 PA2, then PF1 through PF12, or PF13
through PF24 (if present)
Field Exit Erase EOF, then Field Tab
Attention 3277 use Test Request then PA1
3278/3279 use Attn key
Note: 1For example, to start F3, press PA1, wait for the system to respond, and then press
PF3.

To display the active PF key assignments for your work station, issue the Display
Keyboard Map (DSPKBDMAP) command or press the PF key assigned the 3270
help function.

To specify different PF key defaults use the Set Keyboard Map (SETKBDMAP) or
the Change Keyboard Map (CHGKBDMAP) command. The key assignments that
you specify are in effect until you use these commands to specify key assignments
again or until you sign off the work station.

3270 and 5250 Displays

This topic discusses the similarities and differences of the 3270 and 5250 display
attributes and characters. Both types support extended binary-coded decimal inter-
change code (EBCDIC) and American National Standard Code for Information
Interchange (ASCII) transmissions.

Error messages always appear on line 24 of the display. The cursor is placed in the
field where the error occurred. If the error is located on line 24, the cursor is placed
in the error field.

For more information about error messages, see “Operator Error Messages” on
page 12-11.

Display Differences
A display having less than 1920 character positions (a minimum of 80 columns by
24 rows) cannot be supported by the 3270 remote attachment function.

The 3270 remote attachment function does not support the 3274 response time
monitor.

12-8 Remote Work Station Support V4R1

Characters and Symbols
The shift-out and shift-in characters associated with double-byte data streams are
passed as they are, if the display is a double-byte character set (DBCS) display
connected to a DBCS system.
Note: 3270 remote attachment does not provide 3270 display stations with graphic
data type support.

Depending on model and feature, the 3270 displays present different symbols for
undefined characters created by code in the range of hexadecimal 40 through FE.

Characters with a hexadecimal value less than 40 that are not display commands,
orders, or nulls (hexadecimal 00) are displayed as question marks (?).

When an application program running on a System/36 includes the hexadecimal

number FF in a 3270 data stream, the System/36 support for the 3270 data stream
changes the hexadecimal FF to a hexadecimal 40. In contrast to this, the AS/400
system support for the 3270 data stream does not change the hexadecimal FF.
Therefore, application programs that migrate from a System/36 to an AS/400
system need to be changed because not all 3270 display stations support
hexadecimal FF.

Fields
There are two types of fields: signed-numeric and numeric-only. Signed-numeric
fields used for negative numbers act differently on the 3270 than on the 5250. On
the 3270, if the operator types a negative number in the field, the sign occupies the
first position of the field followed by the number. This decreases the maximum size
of the field by one and should be considered when designing the displays and
fields. The data in a signed-numeric field is adjusted to appear to the application
program as if it were typed from a 5250 work station.

When data is typed in an input field that is included in a roll command and if any
lines included in the roll command are not the same type of field attributes and
location, results that cannot be predicted can occur.

Monocase, right-justify, and duplicate (Dup) fields appear on the 3270 display as
they are typed, but appear to the application program as if they were typed from a
5250 work station.

Field marks in the 3270 data stream are changed to blanks.

All nulls are suppressed by the 3270 when sending data to the primary or control-
ling computer, called the host system. Be aware that data may be different if the
cursor movement keys are used inside a field.

For example, if the operator enters character A in column 1 and then uses the
cursor key to move to column 8 of field 1 to enter character B, field 1 would be
returned to the application program as:

AB______

if blank-fill was specified by the user. In other words, the AB would have 6 blank
characters after it. Otherwise,
AB

Chapter 12. Using 3270 Device Support 12-9

is returned as field 1. In other words, the AB would not have any blank characters
after it.

The 5250 I/O and self-check field format functions are not supported on the 3270
display station. A message informs you that an unsupported function negative
response or an LU status (LUSTAT) is returned to the OS/400 licensed program.

The 5250 automatic cursor advance to the next input field that allows you to auto-
matically enter text is not supported on the 3270. You must press the Enter key
each time you want to advance to the next input field.

A 3270 with remote attachment cannot use the text assist function of Client Access
with Systems Application Architecture (SAA) OfficeVision functions.

Extended Attributes
Some 3279 work stations capable of graphics present the second and following
lines of a field that have extended attributes specified in reverse image when that
field spans more than one line.

No display attributes are shown on a 3270 when the field is defined as a nondis-
play field.

For more information about field attributes, see the topic “Field Attributes” on
page 12-12.

Embedded Attributes
To view the embedded attributes, press the PF key assigned the display embedded
attributes (DSPATR) function. The display attributes cannot be changed.

The 5250 display allows the creation, movement, or overwriting of embedded attri-
butes; the 3270 device does not.

Duplicate Characters: If embedded attributes are found in an input-capable field,

the following occurs on the 3270 device:
All embedded attributes are replaced with duplicate (Dup) characters, which
normally appear as an overscore (an asterisk with a line above it). The Dup
characters indicate the location of the display attributes. The actual characters
displayed are determined by the device and the configuration. Because the
Dup characters are used to hold the attribute position in the data stream, do
not use the Dup key in a field of this type. Differences could occur between
3270 and 5250 displays when running AS/400 utilities and some user pro-
grams.
By pressing any Attention Identifier (AID) key (for example, a function key or
the Enter key), you can restore the display with the Dup characters replacing
the attributes. Now the attributes can be changed, or you can delete, insert, or
change text in the fields.
Depending on the application program, you can have the changes sent to the
application program. When the display is shown again, the Dup characters
rather than the embedded attributes appear.
When the same number of Dup characters are received from the 3270 as were
sent, the Dup characters are replaced with the saved attributes in a left-to-right

12-10 Remote Work Station Support V4R1

sequence. The offset character in the input field of the attribute is also changed
at this time.
When fewer Dup characters are received from the 3270 than were sent to the
3270 and if Dup characters are returned at the same offset in the field as the
attributes were originally, the attributes replace the Dup characters. This con-
tinues until all Dup characters have been replaced or until a Dup character is
found at an offset in the current field where no attribute was before. If this
occurs, any remaining Dup characters are replaced in a left-to-right sequence.
When more Dup characters are received from the 3270 than were sent to the
display, and if the Dup-enabled attribute is on for the field, the Dup characters
are replaced by saved attributes from left to right and any trailing Dup charac-
ters are left in the data stream.
If the Dup-enabled attribute is not on for the field, the operator receives error
code 0019 indicating the Dup key is not enabled for that field.

Printing Locally
For printers shared between systems (or for printers that are the system printer)
3270 remote attachment may not fully support the local print function. This could
occur if the local print key was pressed while the printer was already printing a job.

Messages
This topic discusses break and operator error messages, as well how to access
them, and operator error message codes.

Break Messages
When the work station is in break mode (you must specify *BREAK), messages
appear on the 3270 device exactly as they appear on the 5250 display. When you
are not in break mode, message CPD4011 sends you this message on line 24: A
message has arrived on a message queue. To continue, press the function key
assigned the help function or the function key assigned the error reset function.
Then use the Display Message (DSPMSG) command or the function key assigned
the system request function followed by option 4 (Display message) to view the
waiting message. Set the work station message queue to break mode to see the
messages as they arrive. For more information about messages requiring the Reset
key to be pressed, see “Reset Key” on page 12-6.

Operator Error Messages

Operator error messages are created by the 3270 support on the AS/400 system. If
more than one error exists on a display, only the first error is detected and its
message is displayed. You must correct the first error before the other errors are
detected and their messages displayed. The error message replaces the contents,
if any exist, of line 24 of the display. The error line is restricted to line 24, regard-
less of where it is specified by DDS or the program.

After viewing the error message, you can continue your task by pressing either the
function key assigned the reset function, the function key assigned the help func-
tion, or the Enter key.
Note: During a write operation to the error line, the Enter key is defined as a
Reset key and cannot be mapped to any other function.

Chapter 12. Using 3270 Device Support 12-11

In addition, if a write operation is requested by the user application to display an
error message, a read operation should immediately follow the write operation in
order for the remote 3270 display to allow resetting of the error message. A read
operation following a write operation of an error message should be used by all
applications regardless of the type of target display. If a read operation does not
immediately follow the write error message requested by the user application,
remote 3270 displays may overlay the error message before it can be read by the
user.

When the Reset key is pressed, the cursor moves to the error field and allows cor-
rection. Press the Help key to view the help information. Then press the Enter key,
followed by the Reset key to correct the error field. After either action, the previous
contents of line 24 can be displayed again by pressing the Reset key.

Operator Error Message Codes

The 3270 error codes appear as existing 5250 operator error codes.

Table 12-3. 3270 Error Code Descriptions

Error Code Description
0003 Incorrect key followed the PA key.
0006 Only the Reset key (PF10) or the Enter key can follow the Sys Req
(PF11) key.
0007 Entry missing from a mandatory entry field.
0008 Nonalphabetic character is in an alphabetic field.
0009 Nonnumeric character is in a numeric-only field.
0010 Nonsigned numeric character is in a signed numeric field.
0011 Incorrect character is in the sign position of a signed numeric field.
0014 Unfilled mandatory fill field.
0019 A Dup key was pressed in a non-Dup field.
0024 Only characters 0 through 9 are allowed.

Field Attributes
The 3270 field attributes are supported by the AS/400 system. The 3278 and 3279
extended attributes (blink, reverse image, underline, and color) are supported with
the following limitations:
The 3279 displays white and the 3287 prints normally (black) for the same attri-
bute.
Blinking characters appear on the 3279 only if the red attribute is set on.
Blinking cursor cannot be set by using the DDS keywords.
Color keywords specified in OS/400 DDS are supported for 3279 Display
Stations. For more information about DDS color keywords, refer to the DDS
Reference book.

The following figure shows the attribute combinations for the 5251 display stations
and the corresponding color attributes for the 3279 display stations. For example, if

12-12 Remote Work Station Support V4R1

the 5251 display station uses the high intensity attribute, the corresponding color
appearing on the 3279 is white.

Table 12-4. Attribute Combinations on the 5251 and the 3279 Display Stations
5251 Column 5251
Separator 5251 High Inten- Blink 3279 Color Attri-
(CS) sity (HI) (BL) butes
No No No Green
No Yes No White
Yes No No Turquoise
Yes Yes No Yellow
No No Yes Red
No Yes Yes Blinking Red
Yes No Yes Pink
Yes Yes Yes Blue
Notes:

On 3278 and 3279 display stations, the 3270 underline character replaces the
5250 column separator if no conflict exists with other attributes.
DDS color keywords such as COLOR(RED) can be used to create colors on a
3279 in a manner consistent with a 5292 Model 1 Display Station.

Blink, Reverse Image, and Underline Attributes

Blink, reverse image, and underline attributes appear only if nondisplay is not
selected. These attributes are mutually exclusive and are set on in the following
order:
1. Blink (only 3278)
2. Reverse image
3. Underscore

For example, if both reverse image and underline attributes are selected, only the
reverse image attribute is used.

Blink, underline, and reverse image attributes are not supported by 3277, 3278, or
3279 devices without an extended attributes feature.

3270-to-5250 Keyboard Mapping

A 3270 display station being used to do work on an AS/400 system using 3270
support appears to be a 5250 display station to an AS/400 system. The 3270
display station keyboard has a 5250-equivalent keyboard map associated with it to
do the 5250-equivalent functions on the AS/400 system.

When a user first signs on using 3270 device support, the AS/400 system automat-
ically assigns the 3270 default keyboard map to the user’s 3277, 3278, or 3279
keyboard (unless a user-defined keyboard map has been set up to be automatically
included in the user’s AS/400 sign-on procedure). This supplies the mapping (or
translation) needed for the 3270 keyboards to do most of the same functions as
their 5250 keyboard equivalents.

Chapter 12. Using 3270 Device Support 12-13

If satisfied with the default keyboard mapping supplied at sign-on, the 3270 user
can skip the remainder of this section and go on to Table 8-1.

Displaying a Keyboard Map

To see the keyboard values currently in effect, the 3270 user should type the
Display Keyboard Map (DSPKBDMAP) command (after signing onto a 3270 device)
or press the 3270 Help (HLP3270) key.
Note: The type of processing for the DSPKBDMAP command should be limited to
MODE(*INTERACT *IPGM *EXEC).

To see a list of the keyboard mapping commands, you can select option 9 (Display
a menu) from the AS/400 Main Menu, type in CMDKBD (Keyboard Commands) for
the menu name from the GO display, and press the Enter key. A display similar to
the following is shown:

à ð
CMDKBD Keyboard Commands

Select one of the following:

Commands
1. Change Keyboard Map CHGKBDMAP
2. Display Keyboard Map DSPKBDMAP
3. Set Keyboard Map SETKBDMAP

A display similar to the following appears when you select the DSPKBDMAP
command:

à ð
Help for 327ð Keyboard Mapping

327ð Key 327ð Key

Sequence Function Sequence Function
PF1 525ð help text PF13 F13
PF2 327ð help text PF14 F14
PF3 F3 PF15 F15
PF4 F4 PF16 F16
PF5 F5 PF17 F17
PF6 F6 PF18 F18
PF7 Page up (Roll down) PF19 F19
PF8 Page down (Roll up) PF2ð F2ð
PF9 F9 PF21 F21
PF1ð F1ð PF22 F22
PF11 F11 PF23 F23
PF12 F12 PF24 F24

Display attributes = display imbedded attributes

Press Enter to continue.

More...
F3=Exit F12=Previous

á ñ
Only the keyboard mapping member currently being used can be displayed; no
other members can be specified. You can press the Page or Roll key to see addi-
tional information.

12-14 Remote Work Station Support V4R1

à ð
Help for 327ð Keyboard Mapping

327ð Key 327ð Key

Sequence Function Sequence Function
PA1 PF1 525ð help text PA2 PF1 F13
PA1 PF2 327ð help text PA2 PF2 F14
PA1 PF3 Clear display PA2 PF3 F15
PA1 PF4 Print display PA2 PF4 F16
PA1 PF5 Display attributes PA2 PF5 F17
PA1 PF6 Text request PA2 PF6 F18
PA1 PF7 F7 PA2 PF7 F19
PA1 PF8 F8 PA2 PF8 F2ð
PA1 PF9 Attention PA2 PF9 F21
PA1 PF1ð Error reset PA2 PF1ð F22
PA1 PF11 System request PA2 PF11 F23
PA1 PF12 Record backspace PA2 PF12 F24

Display attributes = display imbedded attributes

Press Enter to continue.

More...
F3=Exit F12=Previous

á ñ

à ð
Help for 327ð Keyboard Mapping

Function 327ð Key Sequence 525ð Key Sequence

Erase all input fields Not supported Erase Input
Field plus Not supported Field+
Field minus Not supported Field-
Erase end-of-field and Erase EOF,-->| Field Exit
exit field

To use the attention function (ATTN), do one of the following:

- Press Test Request, then press PA1 if using a 3277 display
attached to an SNA 3274 controller.
- Press ATTN if using a 3278 or 3279 display attached
to an SNA 3274 controller.
- Press the 327ð Key Sequence set by the user if
using a distributed host command facility, network routing
facility, or SNA Primary LU2 Support device.

Press Enter to continue.

Bottom
F3=Exit F12=Previous

á ñ
You can specify different PF key assignments by using the Change Keyboard Map
(CHGKBDMAP) command or the Set Keyboard Map (SETKBDMAP) command.
Table 12-2 on page 12-7 shows the default PF key assignments to perform the
various 5250 functions.

Chapter 12. Using 3270 Device Support 12-15

Changing a Keyboard Map
The Change Keyboard Map (CHGKBDMAP) and Set Keyboard Map
(SETKBDMAP) commands can be used to change the AS/400 system-supplied
keyboard map used by 3270 display station users. Key assignments made using
these commands remain in effect until the display station is signed off.

A CL program such as the one shown in Figure 12-1 can also be used to set up a
keyboard map for each 3270 user. To use the keyboard map described by the
program, use the Change User Profile (CHGUSRPRF) command to specify the
qualified name of the program as the initial program for each 3270 user profile that
will use the keyboard map. The keyboard map described by the program will then
be set each time a 3270 user signs on.

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ PROGRAM NAME: 327ðMAP LIBRARY: 327ðLIB \/
/\ \/
/\ LANGUAGE: CL \/
/\ \/
/\ FUNCTION: SETS A MORE USABLE KEYBOARD MAP FOR USERS OF 327ð \/
/\ DEVICES ATTACHED TO AS/4ðð SYSTEMS USING DHCF, \/
/\ NRF, OR SPLS. \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
BEGIN: PGM
/\ \/
/\ CHANGE THE KEYBOARD MAP. \/
/\ \/
A1: SETKBDMAP DEV(\REQUESTER) +
PF1(\F1) PF2(\F2) PF3(\F3) +
PF4(\F4) PF5(\F5) PF6(\F6) +
PF7(\DOWN) PF8(\UP) PF9(\F9) +
PF1ð(\F1ð) PF11(\F11) PF12(\F12) +
PF13(\F13) PF14(\F14) PF15(\F15) +
PF16(\F16) PF17(\F17) PF18(\F18) +
PF19(\F19) PF2ð(\F2ð) PF21(\F21) +
PF22(\F22) PF23(\F23) PF24(\F24) +
PA1PF1(\HELP) PA1PF2(\HLP327ð) +
PA1PF3(\CLEAR) PA1PF4(\PRINT) +
PA1PF5(\DSPATR) PA1PF6(\TEST) +
PA1PF7(\F7) PA1PF8(\F8) +
PA1PF9(\ATTN) PA1PF1ð(\RESET) +
PA1PF11(\SYSREQ) PA1PF12(\BCKSPC) +
PA2PF1(\F13) PA2PF2(\F14) +
PA2PF3(\F15) PA2PF4(\F16) +
PA2PF5(\F17) PA2PF6(\F18) +
PA2PF7(\F19) PA2PF8(\F2ð) +
PA2PF9(\F21) PA2PF1ð(\F22) +
PA2PF11(\F23) PA2PF12(\F24)
/\ \/
/\ MONITORS FOR CPF87ð1 MESSAGE TO CHECK FOR NON-327ð DEVICE. \/
/\ IF NOT A 327ð DEVICE, PROGRAM ENDS. \/
/\ \/
B1: MONMSG MSGID(CPF87ð1) EXEC(GOTO CMDLBL(NOMAP))
/\ \/
NOMAP: RETURN
ENDPGM
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

Figure 12-1. CL Program to Set Keyboard Map for DHCF, NRF, and SPLS Sessions

12-16 Remote Work Station Support V4R1

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ PROGRAM NAME: 327ðMAP LIBRARY: 327ðLIB \/
/\ \/
/\ LANGUAGE: CL \/
/\ \/
/\ FUNCTION: SETS A MORE USABLE KEYBOARD MAP FOR USERS OF 327ð \/
/\ DEVICES ATTACHED TO AS/4ðð SYSTEMS USING 327ð \/
/\ REMOTE ATTACH. \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
BEGIN: PGM
/\ \/
/\ CHANGE THE KEYBOARD MAP. \/
/\ \/
A1: SETKBDMAP DEV(\REQUESTER) +
PF1(\F1) PF2(\F2) PF3(\F3) +
PF4(\F4) PF5(\F5) PF6(\F6) +
PF7(\DOWN) PF8(\UP) PF9(\F9) +
PF1ð(\F1ð) PF11(\F11) PF12(\F12) +
PF13(\F13) PF14(\F14) PF15(\F15) +
PF16(\F16) PF17(\F17) PF18(\F18) +
PF19(\F19) PF2ð(\F2ð) PF21(\F21) +
PF22(\F22) PF23(\F23) PF24(\F24) +
PA1PF1(\HELP) PA1PF2(\HLP327ð) +
PA1PF3(\CLEAR) PA1PF4(\PRINT) +
PA1PF5(\DSPATR) PA1PF6(\TEST) +
PA1PF7(\F7) PA1PF8(\F8) +
PA1PF9(\F9) PA1PF1ð(\RESET) +
PA1PF11(\SYSREQ) PA1PF12(\BCKSPC) +
PA2PF1(\F13) PA2PF2(\F14) +
PA2PF3(\F15) PA2PF4(\F16) +
PA2PF5(\F17) PA2PF6(\F18) +
PA2PF7(\F19) PA2PF8(\F2ð) +
PA2PF9(\F21) PA2PF1ð(\F22) +
PA2PF11(\F23) PA2PF12(\F24)
/\ \/
/\ MONITORS FOR CPF87ð1 MESSAGE TO CHECK FOR NON-327ð DEVICE. \/
/\ IF NOT A 327ð DEVICE, PROGRAM ENDS. \/
/\ \/
B1: MONMSG MSGID(CPF87ð1) EXEC(GOTO CMDLBL(NOMAP))
/\ \/
NOMAP: RETURN
ENDPGM
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/

Figure 12-2. CL Program to Set Keyboard Map for 3270 Remote Attach Sessions

For example, to change the user profile for user JOE3270 to use the keyboard map
program shown in Figure 12-2, use the following command:
CHGUSRPRF USRPRF(JOE327ð) INLPGM(327ðLIB/327ðMAP)

Keyboard Mapping for 3270—Tips

Following are other considerations that affect how 3270 keyboard mapping is used.
The user must have successfully established an SNA connection to the AS/400
system and signed on the AS/400 system.
The keyboard map that is activated at a particular 3270 display station is in
effect for all the sessions that are active for that display station.
The PA1 and PA2 keys cannot be assigned a different value. These keys are
used for the special sequences PA1/PF1 through PF12 and PA2/PF1 through
PF12. The PA keys always signify that a PF key will follow, and that the
two-key sequence is to be interpreted as a group. The only exception is when
the keyboard has 24 PF keys and the PA1 or PA2 key is pressed, followed by

Chapter 12. Using 3270 Device Support 12-17

PF13 through PF24. In that case, the PA key is ignored and only the PF key is
interpreted.
The PF13 through PF24 keys are definable on all 3270 display stations.
However, because 3270 support on the AS/400 system has no way of deter-
mining whether the remote device actually has 24 PF keys, no function from
the minimum function set of four keys (HELP, HLP3270, ATTN, or SYSREQ)
can be assigned to PF13 through PF24 unless that function is also assigned to
PF1 through PF12, PA1/PF1 through PF12, or PA2/PF1 through PF12.
If desired, a 3270 user can assign the 3270 PF keys to map to function keys
that are defined to have specific meanings for his application programs. For
example, one function key could be defined to mean EOJ (end of job).
The application programs in which the special meanings are to be used must
be written so that they support the special function; that is, assigning the EOJ
function to a particular function key does not mean that 3270 support handles
the EOJ function when that key is pressed. 3270 support interprets the PF key
and return the appropriate command key function to the application. The appli-
cation must interpret any function key that is specific to the program and
provide that function. For more information about user-defined function keys,
see the appropriate programming language book.
A 3270 attention identifier (AID) generating key does not allow the generation
of a subsequent AID request until the first AID request is processed. A 3270
attention identifier (AID) is a character in a data stream indicating that the
display station user pressed a key (such as the Enter key) to request an action
by the system.

12-18 Remote Work Station Support V4R1

Chapter 13. 3270-Type Device Configuration Examples
This chapter provides examples of using a 3174 controller to attach 3270-type
devices to the AS/400 system, including considerations for DBCS-capable devices.
See the Communications Configuration book for more information about matching
parameters between the AS/400 system and these remote controllers.

3270 Remote Attachment—Scenario

Figure 13-1 shows a network configuration using the AS/400 remote attachment
support.

Devices SNA AS/4ðð System

Controller ┌─────────────┐
SNA │Remote │
┐ ┌──────────┐ ┌─────┤Attachment │
3277 │ SNA │ │ │ ├───────────┐ │
3278 ├───────┤ 3x74 ├─────┘ │ │ │
3279 │ │ │ │ │ │
3287 │ └────┬─────┘ SDLC │ │ │
┘ │ Token-Ring└──────┬────┴─┘
│ Network │
│ X.25 Network │
│ Ethernet Network │
│ ┌──────┴──────┐
┐ ┌────┴─────┐ ┌─┐ │Remote │
PCs using│ │ │ ┌┘ └┐ │Attachment │
327ð ├────┤ 3x74 ├───┤ ├───┼───────────┐ │
emulation│ │ │ └┐ ┌┘ │ │ │
┘ └──────────┘ └─┘ │ │ │
ISDN │ │ │
Network └───────────┴─┘

Figure 13-1. Configuration Example of 3270 Remote Attachment Support

For a configuration example for remotely attached 3270 devices, see “3270-Type
Remote Controllers in a Token-Ring Network” on page 13-5.

For changing and setup instructions for the 3274 Control Unit, see the 3270 Infor-
mation Display System–3274 Control Unit Description and Programmer’s Guide,
and the 3274 Configuration Level D Support. For customizing and setup
instructions about the 3174 Establishment Controller, see the 3174 Establishment
Controller Planning Guide.

For more information about using 3270 display station pass-through, see the topic
“3270 Display Station Pass-Through—Scenario” on page 13-2.

For other 3270 remote attachment information, see the DDS Reference book and
the 3270 Device Emulation Support book.

 Copyright IBM Corp. 1997 13-1

3270 Display Station Pass-Through—Scenario
3270 display station pass-through provides an end-point for two separate SNA ses-
sions. One session exists from the host system to the AS/400 system and the other
session exists from the AS/400 system to the 3270 display station. These sessions
run at the same time and move data between the host system and the 3270 display
station.

Figure 13-2 shows a network configuration using the 3270 display station pass-
through support.

┌───────────────────┐
│ │
│ System/37ð System │
│ │
│ │
└───────┬───────────┘
│
SNA └─┐
│
┌─────────┴─────────┐
│ 327ð Emulation │
├───────────────────┤
│ │
│ AS/4ðð System │
│ │
├───────────────────┤
│ Remote Attachment │
└───────┬───────────┘
│
SNA └─┐
│
┌──────┴───────┐
│SNA Controller│
│ 3x74 │
└──────┬───────┘
│
└─┐
│
┌────┴─┐
│ 3277 │
3278
3279

Figure 13-2. Configuration Example of 3270 Display Station Pass-Through

Using Start 3270 Emulation Command

Use the Start 3270 Emulation (STREML3270) command to begin 3270 display
station pass-through to an SNA host system. Type the STREML3270 command on
the Command Entry display and press F4 (Prompt) to receive prompting displays.

13-2 Remote Work Station Support V4R1

à ð
Start 327ð Display Emulation (STREML327ð)

Type choices, press Enter.

Emulation controller, or . . . . ________ Name

Emulation device, or . . . . . . _________ Name
Emulation location . . . . . . . ________ Name
Display device, batch only . . . \CURRENT Name, \CURRENT
Page Up (Roll Down) key . . . . \PA2 \PA2, \PA1, \PA3, \NONE...
Page Down (Roll Up) key . . . . \PA1 \PA1, \PA2, \PA3, \NONE...
Test Request key . . . . . . . . \DFT \DFT, \CLEAR, \ERASEINP
Cursor Select key . . . . . . . \NONE \NONE, \F1, \F2, \F3, \F4...

After you enter your choices and press the Enter key, the following 3270 Emulation
display appears for a few seconds to tell you that emulation is in progress, how to
obtain help information, and how to end the emulation session.

à ð
327ð Emulation

327ð emulation initialization in progress

Press the Attn key during emulation

to do the following:

o Display help
o Display emulation options
o End 327ð emulation

(C) COPYRIGHT IBM CORP. 1983, 1988.

á ñ

Selecting SNA 3270 Pass-Through Option

During an emulation session, when using a 3270 remote attachment display, the
Select 3270 Data Stream Pass-Through Option for SNA display appears after you
press the Attn key.

Chapter 13. 3270-Type Device Configuration Examples 13-3

à ð
Select 327ð Data Stream Pass-Through Option for SNA

Emulation device . . . . . . . : EMLDEVNAME

Select one of the following:

1. Transfer to secondary job

2. 327ð Attn key - Request for permission to send

99. End 327ð emulation

Selection
__

F3=Exit F12=Cancel Attn=Interrupt current task

á ñ
As an AS/400 user of the 3270 display station pass-through, you can move
between the AS/400 application and the host application. To suspend the 3270
session, press the Attention (Attn) key, wait until the AS/400 display appears, select
option 1 (Transfer to secondary job), and press the Enter key.

To end a 3270 display station pass-through session, press the Attn key, wait for the
Select 3270 Data Stream Pass-Through Option for SNA display to appear, and
select option 99 (End 3270 emulation). The session appears to the host system as
if the 3270 display station were turned off. This is the normal way to end 3270
emulation. The system display is restored to the display that was shown when you
requested the emulation session.

Because the Attn key is used to suspend and end the emulation session, data
received from the host system on the system services control point-secondary
logical unit (SSCP-SLU) data flow is sent to the 3270 display station on the logical
unit-to-logical unit (LU-LU) data flow. Thus, the Virtual Telecommunications Access
Method (VTAM) logon display will be emulated rather than passed to the display
without translation. The most noticeable effect of this emulation is a change in the
connection status symbol in the operator information area of the display.

Figure 13-3 shows the connection status symbol as it appears on the 3278 and
3279 display stations when you are attached directly to the host system. This
symbol shows the SSCP-SLU system connection status.

Figure 13-3. System Connection Status Symbol for 3270 Display Station

Figure 13-4 shows the connection status symbol as it appears on the 3278 and
3279 display stations when you are attached to the host system by the AS/400
system. This symbol shows the primary logical unit-secondary logical unit
(PLU-SLU) job connection status.

13-4 Remote Work Station Support V4R1

Figure 13-4. Job Connection Status Symbol for 3270 Display Station

While in STREML3270 emulation, you also receive any *BREAK messages that
may arrive from the AS/400 system.

The contents of the display are saved and restored for you when you are ready to
resume your session. When a STREML3270 session is suspended by a *BREAK
message or the user has switched to the AS/400 system, the STREML3270
session does not respond to the 3270 host system. To return to the display you
were using when the *BREAK message interruption occurred, press the Enter key.
Note: Because *BREAK messages can arrive at unexpected times, host applica-
tions should not use SNA or 3270 data stream capabilities beyond what the
AS/400 system can restore. If you have a blank display when you want to
resume your session, or if you lose the color and extended highlighting attri-
butes during the suspend-resume time, press the Clear or Enter key. Most
host applications respond to these keys by refreshing the display.

For more information about *BREAK messages, see the topic “Break Messages” on
page 12-11, and the book, 3270 Device Emulation Support.

3270-Type Remote Controllers in a Token-Ring Network

Coaxial, 3270-type remote controllers (3174 and 3274) can be used to remotely
attach display stations and printers to the AS/400 system. The following example
describes the configuration of a 3174 controller with attached 3270 devices and an
AS/400 system on a token-ring network. A token-ring network is a local area
network that sends data in one direction throughout a specified number of locations
by using the symbol of authority for control of the transmission line, called a token,
to allow any sending station in the network (ring) to send data when the token
arrives at that location.

The following display shows the token-ring network configuration display for a 3174
controller.

Chapter 13. 3270-Type Device Configuration Examples 13-5

à ð
____________ Token-Ring Network ____________
53R/TOKN

1ð6 - 4ððð 3174 ððð4 1ð7 - 4ððð ð324 ððð1 1ð8 - Q324ððð

11ð - ð 116 - ð

121 - ð1 125 - ðððððððð 127 - ð ð

132 - ð ð ð ð 136 - 1 1 1 1 137 - ð ð ð ð 138 - ð

141 - A 165 - 1 166 - C 168 - ð

173 - ðððððððð 175 - ðððððð 178 - ð

213 - 1 215 - ððððð 22ð - 3

38ð - 1994 381 - 7 382 - 1994 383 - 4

PF: 3=Quit 4=Default 7=Back 8=Fwd

á ñ
On the 3174 configuration display, configuration questions 106 and 107 must match
values specified in the AS/400 configuration:
106 Token-Ring Network Address of the 3174 must match the adapter
address (ADPTADR parameter) specified on the AS/400 controller
description (CRTCTLRWS command).
107 Token-Ring Network Address of the Gateway must match the adapter
address (ADPTADR parameter) specified on the AS/400 line description
(CRTLINTRN command).

The Configuration Display

The following displays show the prompts for creating the line, controller, and device
descriptions on the AS/400 system. Each display is shown by typing the name of
the command, then pressing F4 (Prompt).

13-6 Remote Work Station Support V4R1

à ð
Create Line Desc (Token-Ring) (CRTLINTRN)

Type choices, press Enter.

Line description . . . . . . . . > TRNLINE Name

Resource name . . . . . . . . . > LINð31 Name, \NWID, \NWSD
Online at IPL . . . . . . . . . > \NO \YES, \NO
Vary on wait . . . . . . . . . . \NOWAIT \NOWAIT, 15-18ð (1 second)
Maximum controllers . . . . . . 4ð 1-256
Line speed . . . . . . . . . . . 4M 4M, 16M, \NWI
Maximum frame size . . . . . . . 1994 265-16393, 265, 521, 1ð33...
Local adapter address . . . . . > 4ðððð324ððð1 4ððððððððððð-7FFFFFFFFFFF...
Exchange identifier . . . . . . \SYSGEN ð56ððððð-ð56FFFFF, \SYSGEN
SSAP list: _
Source Service Access Point . \SYSGEN ð2-FE, \SYSGEN, \HPR
SSAP maximum frame . . . . . . __________ \MAXFRAME, 265-16393
SSAP type . . . . . . . . . . ________ \CALC, \NONSNA, \SNA
+ for more values _
Text 'description' . . . . . . . > 'Token-ring network line'
Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > TULSA Name

Controller type . . . . . . . . > 3174 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > ð ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . .> \LAN \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . .> \NO \YES, \NO
Switched line list . . . . . . . > TRNLINE Name
+ for more values _______
Maximum frame size . . . . . . . \LINKTYPE 265-1994, 256, 261, 265...
Exchange identifier . . . . . . _________ ðð1ððððð-FFFFFFFF
Initial connection . . . . . . . \DIAL \DIAL, \ANS
Dial initiation . . . . . . . . \LINKTYPE \LINKTYPE, \IMMED, \DELAY
LAN remote adapter address . . . > 4ððð3174ððð4 ððððððððððð1-FFFFFFFFFFFF
Autocreate device . . . . . . . \ALL \ALL, \NONE
Text 'description' . . . . . . . > '3174 Controller on token-ring line'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

Chapter 13. 3270-Type Device Configuration Examples 13-7

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > TULSADSP_ Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3279 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ð2 ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > TULSA Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, BLI...
Drop line at signoff . . . . . . \YES \YES, \NO
Application type . . . . . . . . \NONE \NONE, \NRF, \CTLSSN...
Text 'description' . . . . . . . > 'Tulsa 3279 display station'

à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

Device description . . . . . . . > TULPRT___ Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3287 3287, 3812, 4ð19, 42ð1...
Device model . . . . . . . . . . > ð ð, 1, 2, 3, 4, 1ð, 13, 3ð1...
Local location address . . . . . > ð3 ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > TULSA Name
Separator program . . . . . . . \NONE Name, \NONE
Library . . . . . . . . . . . _________ Name, \LIBL, \CURLIB
Printer error message . . . . . \INQ \INQ, \INFO
Message queue . . . . . . . . . QSYSOPR Name, QSYSOPR
Library . . . . . . . . . . . \LIBL Name, \LIBL, \CURLIB
Application type . . . . . . . . \NONE \NONE, \NRF, \DEVINIT...
Text 'description' . . . . . . . > 'Tulsa 3287 printer'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

Automatic Creation of 3270-Type Device Descriptions

The Autocreate device (AUTOCRTDEV) parameter allows 3270 devices to be auto-
matically created. For 3270 device names, the system uses QNXDEV as the base
and then adds the numbers 000 through ZZZ.
Note: The AUTOCRTDEV parameter does not apply to the automatic creation of
APPC devices used by APPN.

Using the APPC Controller to Attach 3270-Type Devices

The following display shows the prompts used to create the APPC controller
description to attach 3270 display stations or printers. There are two ways to attach
3270-type devices to APPC controllers. The attachment is based on the capability
of the 3270 controller.
If the remote controller is not capable of using APPN support (a PU type 2.0
controller), configure it as APPN(*NO) and specify a controller type. For an
example of this configuration, see Figure 13-5 on page 13-9.

13-8 Remote Work Station Support V4R1

If the remote controller is a PU type 2.1 node and it is capable of using APPN,
configure it as APPN(*YES). The controller type is not allowed. For an example
of this configuration, see Figure 13-6 on page 13-10.

à ð
Create Ctl Desc (APPC) (CRTCTLAPPC)

Type choices, press Enter.

Controller description . . . . . appcctl Name

Link type . . . . . . . . . . . > \SDLC \ANYNW, \FAX, \FR, \IDLC...
Online at IPL . . . . . . . . . > \NO \YES, \NO
Switched connection . . . . . . > \NO \NO, \YES
Switched network backup . . . . > \NO \NO, \YES
APPN-capable . . . . . . . . . . > \NO \YES, \NO
Controller type . . . . . . . . > 3174 \BLANK, \FBSS, 3174, 3274...
Attached nonswitched line . . . > LINAPPC Name
Maximum frame size . . . . . . . > 265 265-16393, 256, 265, 512...
Remote network identifier . . . > \NETATR \NAME, \NETATR, \NONE, \ANY
Remote control point . . . . . . Name, \ANY
Exchange identifier . . . . . . ðððððððð-FFFFFFFF
Data link role . . . . . . . . . > \NEG \NEG, \PRI, \SEC
Station address . . . . . . . . > C1 ðð-FE
Autocreate device . . . . . . . > \ALL \ALL, \NONE

More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
à ð
Create Ctl Desc (APPC) (CRTCTLAPPC)

Type choices, press Enter.

Text 'description' . . . . . . . 'APPC Controller to attach 327ð devices'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 13-5. PU Type 2.0 Controller

Chapter 13. 3270-Type Device Configuration Examples 13-9

à ð
Create Ctl Desc (APPC) (CRTCTLAPPC)

Type choices, press Enter.

Controller description . . . . . > DETAPPC__

Name
Link type . . . . . . . . . . . > \SDLC
\ANYNW, \FAX, \FR, \IDLC...
Online at IPL . . . . . . . . . > \NO
\YES, \NO
Switched connection . . . . . . \NO
\NO, \YES
Switched network backup . . . . \NO
\NO, \YES
APPN-capable . . . . . . . . . . \YES
\YES, \NO
Attached nonswitched line . . . LINAPPC
Name
Maximum frame size . . . . . . . \LINKTYPE
265-16393, 256,265, 512...
Remote network identifier . . . NETATR
Name,\NETATR, \NO NE, \ANY
Remote control point . . . . . . Name, \ANY
> DETROIT
Exchange identifier . . . . . . ðððððððð-FFFFFFFF
Data link role . . . . . . . . \NEG . \NEG, \PRI, \SEC
Station address . . . . . . . > ð1 . ðð-FE
APPN CP session support . . . \YES . \YES, \NO
APPN node type . . . . . . . . \ENDNODE . \ENDNODE, \LENNODE...
APPN transmission group number 1 1-2ð, \CALC
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
à ð
Create Ctl Desc (APPC) (CRTCTLAPPC)

Type choices, press Enter.

Autocreate device . . . . . . . \ALL \ALL, \NONE

Autodelete device . . . . . . . 144ð 1-1ðððð, \NO
User-defined 1 . . . . . . . . . \LIND ð-255, \LIND
User-defined 2 . . . . . . . . . \LIND ð-255, \LIND
User-defined 3 . . . . . . . . . \LIND ð-255, \LIND
Text 'description' . . . . . . . APPC Controller to attach 327ð devices'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 13-6. PU Type 2.1 Controller

For 3270-type device naming considerations, see “Automatic Creation of 3270-Type

Device Descriptions” on page 13-8.

13-10 Remote Work Station Support V4R1

Attachment of DBCS-Capable Devices to 3270 Controllers
Some DBCS-capable display stations can be remotely attached to 3270-type
(coaxial) controllers by configuring the device as a 3279 Model 0 and specifying a
DBCS feature code (IGCFEAT parameter on the CRTDEVDSP command).

Table 13-1 shows the DBCS feature (IGCFEAT parameter) values that should be
specified for DBCS-capable work stations attached to 3174 and 3274 controllers.

Table 13-1. DBCS Feature Values for DBCS-Capable Devices Attached to 3270 Con-
trollers
IGCFEAT Parameter
Language/Device DBCS Device Type Value
Japanese PS/55 running 3270PC 2424J0
5578-001
3472-J Kanji work station
Korean PS/55 running 3270PC 2424K0
Traditional Chinese PS/55 running 3270PC 2424C0
Simplified Chinese PS/55 running 3270PC 2424S0

The following display shows the prompt display for configuring a PS/55 attached to
a 3270 controller. The PS/55 is configured as a 3279-0 display station with a DBCS
feature code specified.

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > PS55DSP__ Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3279 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ð4 ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > CTL3174 Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, BLI...
Drop line at signoff . . . . . . \YES \YES, \NO
Application type . . . . . . . . \NONE \NONE, \NRF, \CTLSSN...
DBCS feature:
Device features . . . . . . . > 2424Jð Character value
Last code point . . . . . . . ____ 4141-FFFE
Text 'description' . . . . . . . > 'DBCS display attached to 327ð controller'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys
á ñ

Configuration Examples for ISDN

This topic contains an overview of the commands necessary to configure ISDN
support with a 3270 controller on the AS/400 system. In addition to the line, con-
troller, and device descriptions configured for most communications, ISDN also
uses a network interface description and a connection list. Details on all commands
are provided in the Communications Configuration book.

Chapter 13. 3270-Type Device Configuration Examples 13-11

Before configuring ISDN support on an AS/400 system, you should obtain the fol-
lowing information from your network provider:
Network type.
Connection type. Whether a B-channel is switched or permanent is generally
determined by the network subscription. On some networks, it is possible to
have one switched B-channel and one permanent B-channel on the same basic
rate interface (BRI).
Local number and remote numbers of systems to call.
Some network types require additional information from your network provider.
Refer to the ISDN Support book for this information.

The following is a suggested order for creating the ISDN configuration objects:
1. Specify a default network type and default connection list using the Change
Network Attributes (CHGNETA) command. A default connection list is provided
on the system, so you do not need to change it.

à Change Network Attributes (CHGNETA)

ð
Type choices, press Enter.

System name . . . . . . . . . . \SAME Name, \SAME

Local network ID . . . . . . . . \SAME Name, \SAME
Local control point name . . . . \SAME Name, \SAME
Default local location name . . \SAME Name, \SAME
Default mode . . . . . . . . . . \SAME Name, \SAME
Node type . . . . . . . . . . . \SAME \SAME, \ENDNODE, \NETNODE
Data compression . . . . . . . . \SAME 1-2147483647, \SAME, \NONE...
Intermediate data compression . \SAME 1-2147483647, \SAME, \NONE...
Maximum intermediate sessions . \SAME ð-9999, \SAME
Route addition resistance . . . \SAME ð-255, \SAME
Network node servers:
Server network ID . . . . . . \SAME Name, \SAME, \NONE, \LCLNETID
Control point name . . . . . . Name, \ANY
+ for more values
Alert status . . . . . . . . . . \SAME \SAME, \ON, \OFF, \UNATTEND
Alert logging status . . . . . . \SAME \SAME, \NONE, \LOCAL, \RCV...
More...
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

á ñ

13-12 Remote Work Station Support V4R1

à Change Network Attributes (CHGNETA)
ð
Type choices, press Enter.

Alert primary focal point . . . \SAME \SAME, \NO, \YES

Alert default focal point . . . \SAME \SAME, \NO, \YES
Alert backup focal point:
Network ID . . . . . . . . . . \SAME Name, \SAME, \NONE, \LCLNETID
Control point name . . . . . . Name
Alert focal point to request:
Network ID . . . . . . . . . . \SAME Name, \SAME, \NONE, \LCLNETID
Control point name . . . . . . Name
Alert controller description . . \SAME Name, \SAME, \NONE
Alert hold count . . . . . . . . \SAME ð-32767, \SAME, \NOMAX
Alert filter . . . . . . . . . . \SAME Name, \SAME, \NONE
Library . . . . . . . . . . . Name, \LIBL, \CURLIB
Message queue . . . . . . . . . \SAME Name, \SAME
Library . . . . . . . . . . . Name, \LIBL, \CURLIB
Output queue . . . . . . . . . . \SAME Name, \SAME
Library . . . . . . . . . . . Name, \LIBL, \CURLIB
More...
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

á ñ
à Change Network Attributes (CHGNETA)
ð
Type choices, press Enter.

Network job action . . . . . . . \SAME \SAME, \REJECT, \FILE.. .

Maximum hop count . . . . . . . \SAME 1-255, \SAME
DDM request access . . . . . . . \SAME Name, \SAME, \REJECT, \ OBJAUT
Library . . . . . . . . . . . Name, \LIBL, \CURLIB
Client request access . . . . . \SAME Name, \SAME, \REJECT...
Library . . . . . . . . . . . Name, \LIBL, \CURLIB
Default ISDN network type . . . \SAME \SAME, \ATTG3, \ATT5E42 ...
Default ISDN connection list . . \SAME Name, \SAME
Allow ANYNET support . . . . . . \SAME \SAME, \NO, \YES
Network Server Domain . . . . . \SAME Character value, \SAME. ..

Bottom
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

á ñ
2. Create a network interface description using the Create Network Interface
Description (CRTNWIISDN) command.

Chapter 13. 3270-Type Device Configuration Examples 13-13

à Create Network Interface Desc (CRTNWIISDN)
ð
Type choices, press Enter.

Network interface description . > NWIISDN Name

Resource name . . . . . . . . . LINEð31 Name
Online at IPL . . . . . . . . . \YES \YES, \NO
Vary on wait . . . . . . . . . . \NOWAIT \NOWAIT, 15-18ð (1 second)
Network type . . . . . . . . . . \NETATR \NETATR, \ATTG3, \ATT5E42...
Call control . . . . . . . . . . \FIRST \FIRST, \THIRD
Channel entries:
Channel number . . . . . . . . \SWT2B 1-2, \SWT2B, \D
Channel connection . . . . . . \SWT, \NONSWT
Line description . . . . . . . Name
+ for more values
Protocol entries:
Protocol . . . . . . . . . . . \IDLCMAX \IDLCMAX, \X25MAX, \IDLC, \X25
Preload Licensed Internal Code \NOLOAD, \LOAD
Maximum switched channels . . 1-2, \MAX, \NONE
+ for more values
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
à Create Network Interface Desc (CRTNWIISDN)
ð
Type choices, press Enter.

Terminal endpoint identifier . . \AUTO ð-63, \AUTO

Service profile identifiers:
SPID number . . . . . . . . . 1-2
SPID value . . . . . . . . . .
+ for more values
Error threshold level . . . . . \OFF \OFF, \MIN, \MED, \MAX...

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
3. Create a Connection List using the Create Connection List (CRTCNNL)
command.

13-14 Remote Work Station Support V4R1

à ð
Create Connection List (CRTCNNL)

Type choices, press Enter.

Connection list . . . . . . . . > ISDNCNNL Name

Network type . . . . . . . . . . \NETATR \NETATR, \ATT5E42, \ATT5E5...
Text 'description' . . . . . . . \BLANK

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Connection list entries identify connection information or call information that
your AS/400 system uses to make outgoing calls and to accept incoming calls.
Connection list entries must be entered into the connection list.
Note: Depending on how you want your system to accept incoming calls, you
may not need to configure a connection list. A default connection list
(QDCCNNLANY) is provided with the system. If, however, your system
is to make outgoing calls or supervise incoming calls, you need to con-
figure a connection list and add connection list entries.
4. To add entries to a connection list, use the Add Connection List Entries
(ADDCNNLE) command.

à Add Connection List Entry (ADDCNNLE)

ð
Type choices, press Enter.

Connection list . . . . . . . . ISDNCNNL

Entry . . . . . . . . . . . . . MYLIST Name
Remote number . . . . . . . . . 333-4567
Text 'description' . . . . . . . \BLANK

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys
á ñ
5. Create an IDLC line description using the CRTLINIDLC command, or create an
X.25 line description using the CRTLINX25 command.

Chapter 13. 3270-Type Device Configuration Examples 13-15

à Create Line Desc (IDLC) (CRTLINIDLC)
ð
Type choices, press Enter.

Line description . . . . . . . . > ISDNLIN Name

Online at IPL . . . . . . . . . \YES \YES, \NO
Vary on wait . . . . . . . . . . \NOWAIT \NOWAIT, 15-18ð (1 second)
NWI connection type . . . . . . \SWT \SWT, \NONSWT
Switched NWI list:
NWI description . . . . . . . NWIISDN Name, \NONE
NWI channel type . . . . . . . \B \B
NWI channel number . . . . . . \CALC \CALC, 1-2
+ for more values
Switched connection type . . . . \BOTH \BOTH, \ANS, \DIAL
Incoming connection list . . . . \NETATR Name, \NETATR
Exchange identifier . . . . . . ð56Aðð36 ð56ððððð-ð56FFFFF, \SYSGEN
Error threshold level . . . . . \OFF \OFF, \MIN, \MED, \MAX...
Maximum frame size . . . . . . . 2ð48 265-8196
Switched NWI selection . . . . . \FIRST \FIRST, CALC

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
à Create Line Desc (IDLC) (CRTLINIDLC)
ð
Type choices, press Enter.

Text 'description' . . . . . . . 'Attach 327ð devices'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
6. Create a controller description using the Create Controller Description (Remote
Work Station) (CRTCTLRWS) command.

13-16 Remote Work Station Support V4R1

à Create Ctl Desc (Remote WS) (CRTCTLRWS)
ð
Type choices, press Enter.

Controller description . . . . . > ISDNRWS Name

Controller type . . . . . . . . > 3174 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > ð ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \IDLC \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . \YES \YES, \NO
Switched connection . . . . . . \YES \NO, \YES
Switched line list . . . . . . . ISDNLIN Name
+ for more values
Maximum frame size . . . . . . . \LINKTYPE 265-1994, 256, 261, 265...
Exchange identifier. . . . . . .
Initial connection . . . . . . . \DIAL \DIAL, \ANS
Dial initiation . . . . . . . . \LINKTYPE \LINKTYPE, \IMMED, \DELAY
Outgoing connection list . . . . ISDNCNNL Name
Connection list entry . . . . . MYLIST Name
Autocreate device . . . . . . . \ALL \ALL, \NONE
More . . .
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
à Create Ctl Desc (Remote WS) (CRTCTLRWS)
ð
Type choices, press Enter.

Text 'description' . . . . . . . 'Attach 327ð devices'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
7. Create device descriptions using the Create Device Description (Display)
(CRTDEVDSP) command.

Chapter 13. 3270-Type Device Configuration Examples 13-17

à Create Device Desc (Display) (CRTDEVDSP)
ð
Type choices, press Enter.

Device description . . . . . . . > ISDNDSP Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3279 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . ð2 ðð-FE
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . ISDNRWS Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, BLI...
Drop line at signoff . . . . . . \YES \YES, \NO
Application type . . . . . . . . \NONE \NONE, \NRF, \CTLSSN...
Text 'description' . . . . . . . '327ð device attach with ISDN'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
If you are using APPN support, device descriptions are automatically created.

13-18 Remote Work Station Support V4R1

Chapter 14. Configuring SNA Pass-Through
This chapter contains instructions on using Systems Network Architecture (SNA)
pass-through. SNA pass-through support is allowed for devices that are attached to
an AS/400 system with connections to an SNA backbone network (boundary-
attached). Users working on a 327x device or a retail or finance device can pass
through the AS/400 system and access primary applications on a System/370 or
System/390 host computer. SNA pass-through support can also be configured to
pass through intermediate AS/400 systems to reach the host application.

SNA Pass-Through—Definitions
The AS/400 system where the device is attached is referred to as the source
system. Attached to it are the display, printer, retail, and finance devices used to
pass through to the host application. The target system contains the host applica-
tions the devices need to reach. In a configuration with two or more AS/400
systems, any AS/400 systems between the source and the target systems are
referred to as intermediate nodes.

An SNA pass-through session is activated by configuring and varying on SNA pass-

through devices on the AS/400 systems.

Upstream and Downstream Devices

For each SNA pass-through session, you must configure two devices. There must
be a line, controller and device description created from the AS/400 system
upstream to the target system. In addition, line, controller, and device descriptions
need to be created from the AS/400 system downstream to the source devices.
Intermediate AS/400 systems require additional line, controller, and device
descriptions.

The following examples show the different relationships between upstream and
downstream devices. The arrows in the examples indicate the direction that a
session may be initiated. The arrows also show which SNA pass-through device is
associated with another device. In the basic method of connecting upstream and
downstream devices, there is one (and only one) upstream device for every down-
stream device. This simplifies the tasks of managing the network and correcting
problems.

 Copyright IBM Corp. 1997 14-1

Upstream ┌───┐ ┌───┐ ┌───┐ ┌───┐ ┌───┐
Devices │ │ │ │ │ │ │ │ │ │
└───┘ └───┘ └───┘ └───┘ └───┘
& & & & &
│ │ │ │ │
│ │ │ │ │
│ │ │ │ │
│ │ │ │ │
│ │ │ │ │
│ │ │ │ │
│ │ │ │ │
Downstream ┌───┐ ┌───┐ ┌───┐ ┌───┐ ┌───┐
Devices │ │ │ │ │ │ │ │ │ │
└───┘ └───┘ └───┘ └───┘ └───┘
Figure 14-1. SNA Pass-Through. One upstream device for each downstream device.

In addition, upstream devices may be grouped together by configuring them in a

configuration list. Users can then request to communicate with the first available
upstream device on the list. Grouping upstream devices may be done to reduce the
number of logical unit (LU) definitions required in the System/370 network. Also,
grouping may be done to provide an alternate line to the System/370 network. If
one of the upstream lines goes down, another line might be available.

Line 1 Line 2
┌──────┐ ┌──────┐
│ │ │ │
Group of ┌───┐ ┌───┐ ┌───┐ ┌───┐
Upstream Devices │ │ │ │ │ │ │ │
└───┘ └───┘ └───┘ └───┘
& & & &
│ │ │ │
└─────┴───┬─┴─────┘
│
Group
&
┌─────┬─────┼─────┬─────┐
│ │ │ │ │
│ │ │ │ │
Downstream ┌───┐ ┌───┐ ┌───┐ ┌───┐ ┌───┐
Devices │ │ │ │ │ │ │ │ │ │
└───┘ └───┘ └───┘ └───┘ └───┘
Figure 14-2. Grouping SNA Pass-Through Devices. Several upstream devices are grouped
together to support a number of downstream devices.

Note: Only upstream devices may be grouped together. Grouping downstream

devices is not supported.

If there are no upstream devices available when a downstream device tries to

connect, an error message could be displayed stating that the group requested is
not available. If this is a frequent occurrence, the following should be considered:
Increase the number of upstream devices configured in the group list. With
more upstream devices in the group list, there are more opportunities for an
upstream device to be available.
Change the inactivity timer to a lower number. When no activity is detected on
a device, the connection is broken quicker.

It is also possible to configure more than one upstream device to connect to a

single downstream device. For example, there might be several spool functions on

14-2 Remote Work Station Support V4R1

a System/370 network that need to share a single remote printer. In this case,
each upstream device must be capable of initiating a conversation with the down-
stream device.

Upstream ┌───┐ ┌───┐ ┌───┐

Devices │ │ │ │ │ │
└─┬─┘ └─┬─┘ └─┬─┘
│ │ │
│ │ │
│ │ │
│ │ │
└────┐│┌────┘
│││
│││
│││
666
Downstream ┌───┐
Devices │ │
└───┘
Figure 14-3. Upstream Devices Sharing a Downstream Printer

An upstream spool function may try to connect to a downstream printer that is

already connected to an upstream device. When this occurs, the printer is allocated
to the upstream spool function when it is no longer connected with the upstream
device.

When configuring your upstream devices and associated downstream devices, con-
sider which device can initiate a session. If an upstream device can initiate a con-
versation with a downstream device, then the downstream device needs to be listed
as an associated SNA pass-through device for the upstream device. In the same
manner, if a downstream device can initiate a conversation, then the upstream
device needs to be listed as an associated SNA pass-through device for the down-
stream device.

It is not necessary for an upstream or downstream device to list an associated SNA

pass-through device. The upstream or downstream device must either have an
associated SNA pass-through device or be an associated SNA pass-through
device. In addition, the upstream or downstream device can both have an associ-
ated SNA pass-through device and be an associated SNA pass-through device.
Problems can occur when you cross configurations.

Upstream ┌───┐ ┌───┐

Devices │ │ │ │
└───┘ └───┘
│ &
│ ┌┘
│ ┌┘
│ ┌┘
│ ┌┘
│ ┌┘
│ ┌┘
6 │
Downstream ┌───┐
Devices │ │
└───┘
Figure 14-4. Crossing Configurations. A downstream device associates a different
upstream device than the one that is associated with it.

Chapter 14. Configuring SNA Pass-Through 14-3

Figure 14-4 shows an example of crossing configurations. In this example, an
upstream device associates with a downstream device. The downstream device
however, associates with a different upstream device.This crossing of configura-
tions can lead to difficulty in network management and create potential problems in
session initiation and routing.

Configuring a Single AS/400 System for SNA Pass-Through

Support—Scenario
In Figure 14-5, the letters A and B illustrate a connection you need to configure for
the SNA pass-through function. Connection A represents the upstream connection
to the target system, while connection B represents the downstream connection to
the source devices. These connections are described in “Connection A: Config-
uring Upstream to the Target System” and “Connection B: Configuring Down-
stream to the Source Devices” on page 14-5.

┌────────────────┐
System/37ð │ ┌────────────┐ │
Target System │ │ Target │ │
│ │ Application│ │
│ └────────────┘ │
└────────────────┘
&
│ Upstream
6
┌────────────────┐
AS/4ðð │ (A) │
Source System │ │
│ │
│ (B) │
└────────────────┘
&
│
│ Downstream
6
┌────────────────┐
T2.ð or T2.1 │ │
Controller │ │
and Dependent │ │
Devices │ │
└────────────────┘
Figure 14-5. SNA Pass-Through with Single AS/400 System

Connection A: Configuring Upstream to the Target System

To configure the connection from the AS/400 system upstream to the target
system, configure a line, controller, and device description:
1. Configure a line using the Create Line Description (CRTLINxxx) command.
2. Configure a T2.0 or a T2.1 host controller using the Create Controller Host
Description (CRTCTLHOST) command.
3. Configure the SNA pass-through devices using the Create Device Description
(SNPT) (CRTDEVSNPT) command. For each device you configure, specify an
SNA pass-through class of *UP. Configure an SNA pass-through device for
each SNA pass-through session you need.

14-4 Remote Work Station Support V4R1

The following display shows an example of an upstream device description that can
be created in step 3. Some of the parameters are explained following the example.

à ð
Create Device Desc (SNPT) (CRTDEVSNPT)

Type choices, press Enter.

Device description . . . . . . . > UPDEVICE__ Name

Local location address . . . . . > ðA ðð-FE
SNA pass-through class . . . . . > \UP.1/ \UP, \DOWN
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . > HOSTCTL.2/ Name
Activation timer . . . . . . . . 17ð.3/ 1-255ð
SNA pass-through device desc . . > DOWNDEVICE.4/ Name, \NONE
Text 'description' . . . . . . . > 'Upstream device description for SNA pass-t
hrough'

.1/ SNA pass-through class: Enter \UP to indicate that this device is an
upstream SNA pass-through device.
.2/ Attached controller: Enter the name of the host controller that you
created in the previous step.
.3/ Activation timer: This parameter, used only with switched lines, sets the
amount of time SNA pass-through support waits for an upstream device
to respond to an activation request. If the upstream device does not
respond within this amount of time, it is considered unavailable. The
SNA pass-through downstream device then becomes available to other
upstream requester devices, and a message regarding the activation
attempt failure is issued to the QSYSOPR message queue. The default
for this parameter is 170 seconds. In networks with intermediate nodes,
additional time is required to activate all links and each AS/400 system
has the activate timer parameter configured. With no intermediate nodes
in this example, the default is used.
.4/ SNA pass-through device description: Specify the name of a down-
stream SNA pass-through device with which the upstream SNA pass-
through device wants to establish a connection. In the example, the
downstream device is called DOWNDEVICE. The downstream device is con-
figured in “Connection B: Configuring Downstream to the Source
Devices.”

Connection B: Configuring Downstream to the Source Devices

To configure the downstream connection from the AS/400 system to its dependent
devices:
1. Configure a line using the Create Line Description (CRTLINxxx) command.
2. Configure a T2.0 or T2.1 APPC controller using the Create Controller
Description APPC (CRTCTLAPPC) command. Configure an APPC controller
even if the downstream physical unit (PU) does not support an XID 3 exchange
or LU 6.2 SNA sessions. For example, configure an APPC controller even if the
downstream PU attached to the AS/400 system is a PU type 2.0 node.
3. Configure display, printer, retail, or finance devices with a device class of
*SNPT, using the Create Device Description (CRTDEVxxx) command. For
finance devices, specify a type of *FNCICF.

Chapter 14. Configuring SNA Pass-Through 14-5

The following display shows an example of a downstream device description (called
DOWNDEVICE) that can be created in step 3. Some of the parameters are
explained following the example.

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > DOWNDEVICE Name

Device class . . . . . . . . . . > \SNPT.1/ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3279 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ðB ðð-FE
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . _______ Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, BLI...
Activation timer . . . . . . . . 17ð 1-255ð
Inactivity timer . . . . . . . . \ATTACH.2/ 1-3ð, \ATTACH, \NOMAX...
SNA Pass-through device desc . . > UPDEVICE.3/ Name, \NONE
SNA Pass-through group name . . \NONE.4/ Name, \NONE
Host signon/logon command . . . > 'LOGON APPLID(CICS) LOGMODE(SD82) DATA(USER
DATA)'.5/

More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
.1/ Device class: Enter the value \SNPT to indicate that this device is an
SNA pass-through device.
.2/ Inactivity timer: Specify the amount of time for which a downstream
device remains connected to a host device in an unbound state before it
is considered inactive. The default is *NOMAX for retail and finance
devices, and *ATTACH for display and printer devices. In each case, the
device is considered active until it (or the upstream device associated
with it) is varied off or powered off. Change this value if you are:
Using switched lines. The lines should drop soon after no activity is
detected.
Using group devices. Make the limited number of upstream devices
available as soon as possible.
Sharing one downstream device between multiple upstream devices.
In these cases, change the default value for the inactivity timer. When
this period of time elapses and no activity is detected, the session is
ended and the host device is made available to other downstream
devices. A message is logged in QSYSOPR or at the display, indicating
that the inactivity timer has expired.
Note: On switched lines, the line-drop timer may be shorter than the
inactivity timer. The line may drop before the inactivity timer
elapses.
.3/ SNA pass-through device description: Specifies the name of an
upstream device with which this SNA pass-through device wants to
establish a session. In this example, the device with which a connection

14-6 Remote Work Station Support V4R1

is to be established is the same upstream device created in the previous
example, UPDEVICE.
Note: The SNA pass-through device description parameter cannot be
specified on the same command as the SNA pass-through group
name parameter.
.4/ SNA pass-through group name: Specifies the name configured for a
group of upstream devices in a configuration list. If specified, this param-
eter indicates that this device is attached to the first available device in
the group name configuration list. Priority is given to devices attached to
nonswitched lines.
Note: The SNA pass-through group name parameter cannot be speci-
fied on the same command as the SNA pass-through device
name parameter.
.5/ Host signon/logon command: This parameter is used only with display
and printer devices. When logon text is configured in the downstream
device, that text is sent to a host application after the downstream
device is paired with a host device. If configured, logon text is sent when
the device is powered on, or, if the device is already on, by pressing the
Enter key. This parameter is allowed only when *SNPT is specified for
the DEVCLS parameter. You should specify text that is sent to the host
system after starting SNA pass-through support. The text must be
enclosed in apostrophes if it contains blanks or other special characters.
All apostrophes in the text must be represented by two apostrophes. A
maximum of 256 characters can be specified.

Grouping of SNA Pass-Through Devices

Use the Change Configuration List Entry (CHGCFGLE) command to add or delete
device names in the configuration lists. Only one configuration list of type
*SNAPASSTHR is allowed on the system at one time. Host devices can belong
only to the groups. Use the Add Configuration List Entries (ADDCFGLE) command
to define SNA pass-through groups with the *SNAPASSTHR configuration list.

Additional Controllers
The controller attached to connection B can act as a gateway to other controllers.
The gateway controller requires the AS/400 system to activate any downstream
controllers and devices attached to the downstream controller. In this environment,
you configure the multiple controllers off the same line (multipoint line).

Configuring SNA Pass-Through with an Intermediate AS/400 Node

SNA pass-through support can be configured so that an end user on an AS/400
system can pass through to a System/370 host system, by way of an intermediate
AS/400 system. In this case, there are four connections that need to be configured:
Upstream connections from the source AS/400 system to the intermediate
AS/400 system
Upstream connections from the intermediate AS/400 system to the target
system
Downstream connections from the intermediate AS/400 system to the source
AS/400 system

Chapter 14. Configuring SNA Pass-Through 14-7

Downstream connections from the source AS/400 system to the dependent
devices

For each connection, you need to configure a line, controller, and device
description. When you create your device description, be sure you associate your
downstream devices with upstream devices and that you associate your upstream
devices with downstream devices. If you associate a downstream device with
another downstream device, or associate an upstream device with another
upstream device, a connection is not established. In Figure 14-6, letters A through
D each illustrate a connection you need to configure to use the SNA pass-through
function with an intermediate AS/400 system.

┌────────────────┐
System/37ð │ ┌────────────┐ │
Target System │ │ Target │ │
│ │ Application│ │
│ └────────────┘ │
└────────────────┘
&
│
6
┌────────────────┐
AS/4ðð │ (A) │
Intermediate │ │
Node │ │
│ (B) │
└────────────────┘
&
│
│
┌────────────────┐
AS/4ðð │ (C) │
Source System │ │
│ │
│ (D) │
└────────────────┘
&
│
│
6
┌────────────────┐
T2.ð or T2.1 │ │
Controller │ │
and Dependent │ │
Devices │ │
└────────────────┘
Figure 14-6. SNA Pass-Through Environment with an Intermediate AS/400 System

Connection A: Configuring Upstream to Target System

The upstream configuration for the intermediate AS/400 system to the target
system is the same as the configuration needed for configuring a single AS/400
system for SNA pass-through support, except for the SNA pass-through device
description parameter. In the example, INTERMDOWN is specified instead of
DOWNDEVICE for this parameter. The INTERMDOWN description is created in the
next step.

14-8 Remote Work Station Support V4R1

The following display shows an example of an upstream device description that can
be created.

à ð
Create Device Desc (SNPT) (CRTDEVSNPT)

Type choices, press Enter.

Device description . . . . . . . > INTERMUP__ Name

Local location address . . . . . > ðA ðð-FE
SNA pass-through class . . . . . > \UP \UP, \DOWN
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . > HOSTCTL Name
Activation timer . . . . . . . . 17ð 1-255ð
SNA pass-through device desc . . > INTERMDOWN Name, \NONE
Text 'description' . . . . . . . > 'Intermediate node upstream.'

Some of the parameters for this display are described in “Connection A: Config-
uring Upstream to the Target System” on page 14-4.

Connection B: Configuring Downstream to the Source AS/400 System

The steps for configuring the downstream connection from the intermediate node to
the source node are:
1. Configure the line using the Create Line Description (CRTLINxxx) command.
2. Configure a T2.1 APPC controller using the CRTCLTAPPC command.
3. Configure SNA pass-through devices with an SNA pass-through class of
*DOWN. Use the Create Device Description (SNPT) command:

à ð
Create Device Desc (SNPT) (CRTDEVSNPT)

Type choices, press Enter.

Device description . . . . . . . > INTERMDOWN Name

Local location address . . . . . > ðB ðð-FE
SNA Pass-through class . . . . . > \DOWN \UP, \DOWN
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . > CTLNAME Name
Activation timer . . . . . . . . 17ð 1-255ð
SNA Pass-through device desc . . > INTERMUP Name, \NONE
SNA Pass-through group name . . \NONE Name, \NONE
Text 'description' . . . . . . . > 'Intermediate node downstream.'

Connection C: Configuring Upstream to the Intermediate AS/400

System
The steps for configuring upstream to the intermediate node from the source node
are:
1. Configure the line using the Create Line Description (CRTLINxxx) command.
2. Configure a T2.1 APPC controller using the CRTCTLAPPC command.
3. Configure SNA pass-through devices with an SNA pass-through class of *UP:

Chapter 14. Configuring SNA Pass-Through 14-9

à ð
Create Device Desc (SNPT) (CRTDEVSNPT)

Type choices, press Enter.

Device description . . . . . . . > SOURCEUP_ Name

Local location address . . . . . > ðB.1/ ðð-FE
SNA Pass-through class . . . . . > \UP \UP, \DOWN
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . > CTLNAME Name
Activation timer . . . . . . . . 17ð 1-255ð
SNA Pass-through device desc . . > SOURCEDOWN Name, \NONE
Text 'description' . . . . . . . > 'Source AS/4ðð System upstream.'

.1/ Local location address: When creating SNA pass-through device

descriptions for devices that communicate between AS/400 systems, the
local location addresses of the device descriptions must match. In this
example, the SNA pass-through devices for connection B and C must
use the same local location address.

Connection D: Configuring Downstream to Dependent Devices

The steps for configuring the dependent devices on the source system with an
intermediate node are the same as the steps for configuring a single system for
SNA pass-through support, except for the SNA pass-through device description
parameter. Specify SOURCEUP instead of UPDEVICE for this parameter. The
SOURCEUP description is created in the previous step.

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > SOURCEDOWN Name

Device class . . . . . . . . . . > \SNPT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3279 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ðB ðð-FE
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . __________ Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, BLI...
Activation timer . . . . . . . . 17ð 1-255ð
Inactivity timer . . . . . . . . \ATTACH 1-3ð, \ATTACH, \NOMAX...
SNA Pass-through device desc . . > SOURCEUP Name, \NONE
SNA Pass-through group name . . \NONE Name, \NONE
Host signon/logon command . . . > 'LOGON APPLID(CICS) LOGMODE(SD82) DATA(USER
DATA)'

More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Some of the parameters for this display are described in “Connection B: Config-
uring Downstream to the Source Devices” on page 14-5.

14-10 Remote Work Station Support V4R1

Several Intermediate AS/400 Systems
SNA pass-through support can be configured so that an end user on an AS/400
system can pass through to a System/370 host system, by way of several interme-
diate AS/400 systems. In each case, a line, controller, and device must be config-
ured for each upstream and each downstream connection.

Configuring a Mixture of Supported and Nonsupported Devices

An SNA pass-through configuration can support a mixture of 5250 and 327x
devices. In networks with intermediate nodes, 5250 display users typically use
display station pass-through up to the boundary between an AS/400 system and
the System/370 system. 3270 device emulation is then used to communicate with
the System/370 system. This could create performance problems at the boundary
AS/400 system.

SNA pass-through support, however, can be configured so that the devices

attached to the host controller (such as emulated devices, SNA upline facility
devices, and remote job entry devices) can be moved downstream to other AS/400
systems. This is done by creating a host device description at connection C for the
downstream devices to communicate. Figure 14-7 illustrates this, with the trans-
lation for the 5250 devices moved downstream to the source node. Letters A
through E illustrate connections that must be configured to use such support.

┌────────────────┐
│ System/37ð │
│ │
└────────────────┘
&
│
6
┌────────────────┐
AS/4ðð │ Host (A) │
Intermediate │ │
Node │ APPC (B) │
└────────────────┘
&
│
│
6
┌────────────────┐ ┌───────┐
AS/4ðð │ Host (C) │ │525ð │
Source │ (E)│%─5│Devices│
Node │ │ │ │
│ APPC (D) │ └───────┘
└────────────────┘
&
│
│
6
┌──────────┐
│ 327x │
│ Devices │
└──────────┘
Figure 14-7. SNA Pass-Through Configured for a Mixture of Supported and Nonsupported
Devices

Chapter 14. Configuring SNA Pass-Through 14-11

Connection A: Configuring Upstream to the Target System
The steps for configuring the connection to the target system are the same as the
steps for configuring a connection from the source node to the target system. For
specific instructions, see “Connection A: Configuring Upstream to Target System”
on page 14-8.

Connection B: Configuring Downstream to the Source System

The steps for configuring the connection downstream from the intermediate node to
the source node are:
1. Configure the line using the Create Line Description (CRTLINxxx) command.
2. Configure a T2.1 APPC controller using the CRTCTLAPPC command.
3. Using the Create Device Description (SNA Pass-through) (CRTDEVSNPT)
command, configure SNA pass-through devices with an SNA pass-through
class of *DOWN (SNPTCLS parameter is *DOWN) on location addresses com-
municating with downstream AS/400 SNA pass-through devices.
4. Using the Create Device Description (CRTDEVxxx) command, configure
display, printer, retail, or finance devices with a device class of *SNPT. The
device descriptions you create here are used to communicate with device
descriptions that will be created in “Connection C: Configuring Upstream to the
Intermediate System,” step 4.

Connection C: Configuring Upstream to the Intermediate System

The steps for configuring the connection from the source node to the intermediate
node are:
1. Configure the line using the Create Line Description (CRTLINxxx) command.
2. To move the translation and emulation processes out to this source AS/400
system, configure a T2.0 or a T2.1 host controller using the Create Controller
Host Description (CRTCTLHOST) command.
3. Using the Create Device Description (SNA Pass-through) (CRTDEVSNPT)
command, configure SNA pass-through devices with an SNA pass-through
class of *UP (SNPTCLS parameter is *UP) for sessions to 327x devices
attached to APPC controller D. The devices you configure here are associated
with the upstream devices you configured in step 3 of “Connection B: Config-
uring Downstream to the Source System.”
4. Using the Create Device Description (Host) (CRTDEVHOST) command, create
host device descriptions that will be used by the various application types. For
example, you could be using remote job entry (RJE) or program-to-program
communications.
The following display shows an example of configuring an SNA host device
description. The value *EML is used for the application type parameter to move
the emulation processes out to the target AS/400 system. To move remote job
entry (RJE) or program-to-program communications out to the target AS/400
system, use the value *RJE or *PGM.

14-12 Remote Work Station Support V4R1

à Create Device Desc (SNA Host) (CRTDEVHOST)
ð
Type choices, press Enter.

Device description . . . . . . . > DEVSNAHST Name

Local location address . . . . . > ðA ð1-FF
Remote location . . . . . . . . > UPLOC Name
Online at IPL . . . . . . . . . \YES \YES, \NO
Attached controller . . . . . . > UPDEV Name
Application type . . . . . . . . > \EML \RJE, \EML, \PGM
Maximum length of request unit \CALC \CALC
Emulated device . . . . . . . . 3278 3278, 3284, 3286, 3287...
Emulated keyboard . . . . . . . \UPPER \UPPER, \LOWER
Emulated numeric lock . . . . . \NO \NO, \YES
Emulation work station . . . . . \ANY Name, \ANY
End session with host . . . . . \UNBIND \UNBIND, \RSHUTD
Text 'description' . . . . . . . \BLANK________________________

Connection D: Configuring Downstream to Dependent Devices

The steps for configuring connection D, from the source AS/400system downstream
to the dependent devices are:
1. Configure the line using the Create Line Description (CRTLINxxx) command.
2. Configure a T2.0 or T2.1 APPC controller using the Create Controller
Description (APPC) (CRTCTLAPPC) command.
3. Configure display, printer, retail, or finance devices with a device class of
*SNPT, using the Create Device Description (CRTDEVxxx) command.

See “Connection D: Configuring Downstream to Dependent Devices” on

page 14-10 for information about configuring these dependent devices.

Connection E: Configuring Downstream to 5250 Devices

The steps for configuring connection E, from the source AS/400system downstream
to the 5250 devices are:
1. Configure the line using the Create Line Description (CRTLINxxx) command.
2. Configure a local or remote work station controller using the Create Controller
Description (Local Work Station) (CRTCTLLWS), or the Create Controller
Description (Remote Work Station) (CRTCTLRWS) command.
3. Configure 5250 devices using the Create Device Display (CRTDEVDSP)
command. The descriptions you create here are associated with the host
device descriptions you configured in step 4 of “Connection C: Configuring
Upstream to the Intermediate System” on page 14-12.

Configuring SNA Pass-Through to Support Several Source AS/400

Systems
SNA pass-through support can be configured to support several source AS/400
systems attached to an SNA backbone network in different places. The dependent
devices attached to the AS/400 systems can be configured to access applications
on any target system on the network. For example, in Figure 14-8 on page 14-14,
327x Device 1 can use Application Y on the Target System 2. The AS/400 System
2 is treated as an intermediate node. Device 2 can use Application X on the Target
System 1, where AS/400 System 1 is treated as an intermediate node. The letters
A through F show the connections required to configure this support.

Chapter 14. Configuring SNA Pass-Through 14-13

┌────────────────┐ ┌───────────────┐
System/37ð │ ┌────────────┐ │ │ ┌───────────┐ │ System/37ð
Target │ │ Application│ │ │ │Application│ │ Target
System 1 │ │ X │ │ │ │ Y │ │ System 2
│ └────────────┘ │ │ └───────────┘ │
└────────────────┘ └───────────────┘
& &
│ │
6 6
┌────────────────┐ ┌───────────────┐
AS/4ðð │ (A) │ │ (E) │ AS/4ðð
Intermediate │ │ │ │ Intermediate
Node 1 │ (C)│%─────5│(D) │ Node 2
│ (B) │ │ (F) │
└────────────────┘ └───────────────┘
& &
│ │
6 6
┌──────────┐ ┌─────────┐
│ 327x │ │ 327x │
│ Device │ │ Device │
│ 1 │ │ 2 │
└──────────┘ └─────────┘
Figure 14-8. SNA Pass-Through Support of Multiple-Source AS/400 Systems

Connection A: Configuring Upstream to Target System

The steps for configuring AS/400 Intermediate Node 1 to the target system are the
same as the steps for configuring a boundary-attached node to a target system. For
specific instructions, see “Connection A: Configuring Upstream to the Target
System” on page 14-4.

Connection B: Configuring Downstream to Dependent Device 327x 1

The steps for configuring the connection from Intermediate Node 1 to 327x Device
1 are the same as the steps for configuring the connection between a source node
and its dependent devices. For specific instructions, see “Connection B: Config-
uring Downstream to the Source Devices” on page 14-5.

Connection C: Configuring Attachment to Intermediate Node 2

The steps to configure the connection from AS/400 Intermediate Node 1 to AS/400
Intermediate Node 2 are:
1. Configure the line using the Create line (CRTLINxxx) command.
2. Configure a T2.1 APPC controller using the CRTCTLAPPC command.
3. Using the CRTDEVSNPT command, configure SNA pass-through devices with
an SNA pass-through class of *DOWN (SNPTCLS parameter is *DOWN) on
location addresses communicating with upstream devices attached to APPC
controller D. These devices will help the communications between 327x Device
2 and Target Application X.
4. Using the CRTDEVSNPT command, configure SNA pass-through devices with
an SNA pass-through class of *UP (SNPTCLS is *UP) on location addresses
communicating with downstream devices attached to APPC controller D. These
devices will help the communications between 327x Device 1 and Target Appli-
cation Y.

14-14 Remote Work Station Support V4R1

Connection D: Configuring Attachment to Intermediate Node 1
The steps for configuring Intermediate Node 2 to Intermediate Node 1 are as
follows:
1. Configure the line using the Create line (CRTLINxxx) command.
2. Configure a T2.1 APPC controller using the CRTCTLAPPC command.
3. Using the CRTDEVSNPT command, configure SNA pass-through devices with
an SNA pass-through class of *UP (SNPTCLS is *UP) on location addresses
communicating with downstream devices attached to APPC controller C. These
devices will help the communications between 327x Device 2 and Target Appli-
cation X.
4. Using the CRTDEVSNPT command, configure SNA pass-through devices with
an SNA pass-through class of *DOWN (SNPTCLS is *DOWN) on location
addresses communicating with upstream devices attached to APPC controller
C. These devices will help the communications between 327x Device 1 and
Target Application Y.

For a list of SNA pass-through specific parameters that apply to this connection,
see “Connection B: Configuring Downstream to the Source Devices” on
page 14-5.

Connection E: Configuring Upstream to Target System 2

The steps for configuring Intermediate Node 2 upstream to Target System 2 are the
same as the steps to configure Intermediate Node 1 to Target System 1. For spe-
cific instructions, see “Connection A: Configuring Upstream to the Target System”
on page 14-4.

Connection F: Configuring Downstream to Dependent 327x Device 2

The steps for configuring Intermediate Node 2 to 327x Device 2 are the same as
“Connection B: Configuring Downstream to Dependent Device 327x 1” on
page 14-14. For specific instructions, see “Connection B: Configuring Downstream
to the Source Devices” on page 14-5.

Grouping of Devices
Grouping upstream devices can reduce the number of logical units (LU), can dis-
tribute the traffic load between lines or can be used for a backup solution. If you
want to use the grouping function, you need to create a configuration list using the
Create Configuration List (CRTCFGL) command. Make changes in your down-
stream device descriptions, also. In your downstream devices, use the names of
the group (SNPTGRP). It is not possible to use the SNA pass-through device-name
(SNPTDEV) and the SNA pass-through group name (SNPTGRP) in the same defi-
nition.

Configuring the Group Function

1. Create a configuration list entry.
2. Use the ADDCFGLE command to add the group names and the upstream
device name.
3. Change the downstream device description to use the SNA pass-through group
feature instead of the downstream SNA pass-through device.

Chapter 14. Configuring SNA Pass-Through 14-15

For a configuration example, see the book, AS/400 SNA Pass-Through Communi-
cations Definitions and Examples, GG24-3919.

SNA Pass-Through Messages

SNA pass-through support issues informational messages to the QSYSOPR
message log. If the active downstream device is a display, SNA pass-through
support also issues a single-byte message ID in the form of AS/4ðð CPIXXXX to the
display. When one of these messages is received, the user should search the
QSYSOPR message log for the appropriate informational message with the same
message ID.

Messages are issued for:

Downstream devices only when
– A downstream display sends data but has no associated device or group
name configured to receive the data
– A downstream display requests a host device that is unavailable
Upstream and downstream devices when
– A configuration error is detected
– An inactivity timer expires on a display
– An activation timer expires
– A session between two pass-through devices is abnormally ended
In environments with intermediate nodes, a message (CPI58E6) is sent to the
source system QSYSOPR message queue, indicating the system where the
error occurred.
Messages are not issued for the normal activating and ending of sessions.

14-16 Remote Work Station Support V4R1

Chapter 15. Distributed Host Command Facility
This chapter discusses the OS/400 distributed host command facility (DHCF)
support as part of a Host Command Facility (HCF) network.

Distributed Host Command Facility—Definition

With OS/400 DHCF support, one or more HCF host system users, using 3270
display stations1, can remotely operate and control the AS/400 system as though
they were using remote 5250 display stations2 attached to the AS/400 system.
Without additional hardware or special application programming, the host system
users can:
Interactively operate and control any AS/400 system that is in the HCF-DHCF
network. Several host system users can perform different operations on the
same AS/400 system at the same time. Each user can:
– Access and control applications that are on each AS/400 system in the
network. They can use any application program for which they have the
proper authority.
– Display, with the proper authority, any of the user files and libraries on any
AS/400 system.
– Look at and respond to unique system messages from the AS/400 system.
Use the operations and service functions of any AS/400 system in the
HCF-DHCF network to do problem analysis on any AS/400 system in the
network. This includes interactive examination of the system’s error log, and
running and displaying storage dumps and traces.

The operating requirements for such display stations are described under “3270
and 5250 Keyboards” on page 12-5 and “3270 and 5250 Displays” on page 12-8.

Additional information about HCF on the host system can be obtained from the
HCF books listed in the “Bibliography” on page X-1.

The AS/400 System in an HCF Environment

The host system (a System/370 or System/390 system, or a 43xx or 30xx
processor) for an HCF network must be operating under VTAM/NCP, or under the
Network Communications Control Facility (NCCF) if it has the Terminal Access
Facility (TAF) feature, with which VTAM/NCP is also used. The host system must
be using at least Version 2 of HCF (Program 5668-985). The use of any earlier
version or release of HCF with the AS/400 system may produce inaccurate results.

1 Any display station, attached by coaxial cable, that uses 3270 data streams.
2 Any display station, attached by twinaxial cable, that uses 5250 data streams.

 Copyright IBM Corp. 1997 15-1

Host Command Facility
HCF is a VTAM application program that operates with Release 3.8 or later
releases of OS/VS2 Multiple Virtual Storage (MVS), Release 7.0 or later of
OS/VS1, or Release 35 or later releases of DOS/VSE.

Host System Requirements for a DHCF Session

For host system considerations when preparing for and starting a DHCF session on
the AS/400 system, see Host System Programming Considerations for DHCF.

Host Command Facility—Benefits

Using HCF, host system users can perform remote management activities on the
AS/400 systems or other systems in the network. HCF allows the host system to
access at the same time different AS/400 systems, System/36s, System/38s,
Series/1 systems, and 8100 Information Systems that are defined as nodes in the
host system’s HCF network.

With OS/400 DHCF support, one or more host system users, using 3270 display
stations, can remotely operate and control the AS/400 system as though they were
using remote 5250 display stations attached to the AS/400 system.

HCF Network Node—Definition

An HCF network consists of the host system and one or more of the following
nodes (systems):
An AS/400 system with DHCF support
System/36 with DHCF support
Series/1 system with host system operator support
System/38 with DHCF support
8100 DPPX or DPCX with DHCF support

Figure 15-1 on page 15-3 illustrates several HCF system users operating an
AS/400 system with DHCF at the same time.

15-2 Remote Work Station Support V4R1

┌─────┐ Host System
│ │ ┌───────────────┐
│ ├────┐ │ │
├─────┤ └┐ │ │
└─────┘ │ │ │
┌─────┬─────┴───┐ ├──────┐ │
│ │ └────┼┐HCF │ │
│ │ ├┼─────┴────────┤
├─────┤ ┌─────────┼┴┐ VTAM │
└─────┘ ┌┘ ├─┴──┬────┬─────┤
┌─────┐ │ ┌┘ │ │ └┐
│ │ │ ┌┘ │ │ └┐
│ ├───┘┌───────┘ ┌─┘ └─┐ └──────┐
├─────┤ │ ┌─┘ └─┐ │
└─────┘ │ │ │ │
┌─────┴───┐┌─────┴───┐ ┌──────┴───┐ ┌────┴─────┐
│ DHCF ││ DHCF │ │ DHCF │ │ DHCF │
├─────────┤├─────────┤ ├──────────┤ ├──────────┤
│ AS/4ðð ││System/36│ │ Series/1 │ │System/38 │
│ System ││ │ │ │ │ │
└─────────┘└─────────┘ └──────────┘ └──────────┘

Figure 15-1. Several Host Users Remotely Operating an AS/400 System

Each AS/400 system must be connected to the host system through a Systems
Network Architecture (SNA) communications line that uses either synchronous data
link control (SDLC) or CCITT Recommendation 3 X.25 or is part of a local area
network. (CCITT Recommendation X.25 is a document that outlines standards for
the connection of processing equipment to a packet-switching data network.) Each
3270 display station that is to use DHCF on the AS/400 system can be attached to
the HCF host system directly as a locally attached device (either SNA or non-SNA)
or remotely using either Binary Synchronous Communications (BSC) or SNA/SDLC.

The following diagram illustrates the logical attachment of a 3270 display station
that is using HCF to an AS/400 system that is using DHCF.

3 International Telegraph and Telephone Consultative Committee (CCITT) is now called the Telecommunications Standardization
Sector (ITU-T).

Chapter 15. Distributed Host Command Facility 15-3

┌─────────────────────┐
│ │
┌───────────┐ │ ┌───────────────┐ │
│ │ SNA, BSC, │ │ │ │
│ 327ð │ or Direct │ │HCF Application│ │
│ │ │ │ │ │
└─────.─────┘ │ └───────┬───────┘ │
. │ │ │
. └──────────┼──────────┘
. │
. │
. │
. │
Apparent │
Logical │
Connection ┌─┘ SNA LU ð
. │
. │
. │
. AS/4ðð │
. System │
. ┌───────────┼────────────┐
. │ │ │
. │ ┌────────┴────────┐ │
. │ │ │ │
. │ │DHCF Application │ │
. │ │ │ │
. │ └─────────────────┘ │
.─(Remote 525ð)─ AS/4ðð Applications │
└────────────────────────┘
Figure 15-2. Logical Connection to OS/400 DHCF

OS/400 DHCF can support as many as 254 DHCF sessions on each host con-
troller.

Display Stations in an HCF Network

The HCF display stations function as 3277, 3278, or 3279 display stations attached
to the host system but they function as remote 5250 display stations to OS/400
DHCF.

For information on the 5250 optimization support for 3270 display stations, see
“5250 Data Stream Optimization Support” on page 12-1.

How OS/400 DHCF Interconnects with Multiple Systems

OS/400 DHCF support also allows an AS/400-to-AS/400interconnection. One
AS/400 system uses either 3270 emulation for SNA or 3270 emulation for BSC to
control, through HCF at the host system, another AS/400 system that is connected
to the host system with DHCF. That is, 3270 emulation is used on the source
AS/400 system, and DHCF is used on the target AS/400 system.

AS/400 3270 Emulation with OS/400 DHCF—Scenario

The arrows in Figure 15-3 on page 15-5 indicate the direction (of control) from
which DHCF sessions are started. Whether from 5250 users on the AS/400 system
using 3270 emulation, or from 3270 users using SNA or BSC at the host system,
all of the users’ input must first go through the host system HCF support before it
goes to the AS/400 system being controlled.

15-4 Remote Work Station Support V4R1

┌──────┐ Host System
│ │ SNA ┌───────────────────────┐ BSC ┌─3277
│ 3x74 ├────────────┼───────┐ ┌─────┼─────┼─3278
│ │ │ │ │ │ └─3279
└&─&──&┘ │ ┌────6─────────6──┐ │
│ │ │ │ │ │ │
3277┘ │ │ │ │ HCF │ │
│ │ │ │ │ │
3278──┘ │ │ └──&─────&─────┬──┘ │
│ └─────┼─────┼─────┼─────┘
3279─────┘ │ │ │
SNA 327ð │ │ │
Emulation │ │ │
┌───────────────┘ │ │
│ BSC 327ð │ │
│ Emulation │ │SNA LU ð
│ ┌──────────────┘ └─────────┐
│ │ │
│ │ AS/4ðð │
│ │ System 6
┌──────┼──────┼──────────┐ ┌────────────────────┐
│ │ │ │ │ │
│ ┌───┴──────┴──────┐ │ │ ┌──────────────┐ │
│ │ │ │ │ │ │ │
│ │ 327ð Emulation │ │ │ │ OS/4ðð DHCF │ │
│ │ │ │ │ │ │ │
│ │ │ │ │ │ │ │
│ └─────────────────┘ │ │ └──────────────┘ │
│ & & │ │ │
└──────┼───────┼─────────┘ └────────────────────┘
│ │
┌────┴──┐┌───┴────┐
│ ││ │
│ 525ð ││PC(525ð)│
│ ││ │
└───────┘└────────┘
Figure 15-3. Using AS/400 3270 Emulation with OS/400 DHCF

In the same manner, 5250 display station users on other systems (such as a
System/38, Series/1 system, System/34, or System/36) that can use 3270 emu-
lation can also operate an AS/400 system that has DHCF and is connected to an
HCF host system. Before you can use DHCF to communicate with a host system,
you must configure for DHCF.

Host System Programming Considerations for DHCF

The host system programmer should read the following summary of programming
considerations. This information should not be needed by the AS/400 programmer.
When the support is configured, the AS/400 programmer must be provided with
certain parameter values that were specified during host system generation.

Additional information about HCF and VTAM can be obtained from the books listed
in the “Bibliography” on page X-1.

Chapter 15. Distributed Host Command Facility 15-5

VTAM/NCP Programming—Tips
Before communications can occur between the HCF host system and OS/400
DHCF, VTAM/NCP generation must be done on the host system.
All AS/400 systems to be included in the network must be defined during the
VTAM/NCP generation.
Each AS/400 host controller represents a physical unit (PU) to VTAM/NCP.
Therefore, each AS/400 host controller that DHCF uses requires a PU definition
in the VTAM/NCP generation.
Because the DHCF session is considered an SNA logical unit (LU), the session
also requires an LU definition.

A description of all the parameters affecting DHCF definition types follows.

Physical Unit Definition Parameters

The following parameters on the physical unit (PU) macroinstruction definition apply
to the DHCF support:

ADDR = xx
Specifies the station address.

DISCNT = NO/YES
Specifies whether VTAM/NCP is to disconnect the physical unit when the last
logical unit session is ended. DISCNT=NO allows the AS/400 system to remain
connected when no sessions are active; the physical unit is deactivated when
the last device on the line is varied off. DISCNT=YES disconnects the AS/400
system when the last session ends; the DHCF support remains active until the
device is varied off.

IDBLK = 056
IDBLK must be specified as 056 for an AS/400 system. This parameter is spec-
ified only for a switched line.

IDNUM = number
The IDBLK and IDNUM parameters make up the SDLC exchange identifier.
This parameter is specified only for a switched line.

ISTATUS = ACTIVE/INACTIVE
Specifies whether the physical unit should be activated when its major node is
activated.

MAXDATA = 2057
Specifies the maximum amount of data, including the transmission header and
request/response header, that the physical unit can receive. This value must
match the maximum frame size (MAXFRAME) parameter of the line description
on the AS/400 system.

MAXOUT = 7
Specifies the number of path information units (PIUs) that VTAM/NCP will send
to the AS/400 system before requesting a response. For best performance, 7
should be specified.

PUTYPE = 2
The physical unit type must be 2.

15-6 Remote Work Station Support V4R1

SSCPFM = USSSCS
Specifies that the AS/400 logical units associated with this physical unit use
character-coded messages for communications with VTAM/NCP. The AS/400
system requires character-coded messages.

USSTAB = name
Specifies the name of a USS definition table.

Logical Unit Definition Parameters

The following parameters on the logical unit (LU) macroinstruction definition apply
to the DHCF support:

ENCR = NONE
Specifies the type of encryption to be used. Encryption is not supported by the
AS/400 system for DHCF support, so NONE must be specified.

LOCADDR = address
Specifies the local address of the session. The local address is equivalent to a
logical unit number and corresponds to the LOCADR parameter on the device
description of the AS/400 system.The host LOCADDR parameter is a decimal
value. The AS/400 LOCADR parameter is a hexadecimal value.

ISTATUS = ACTIVE/INACTIVE
Specifies whether the logical unit is to be activated when the physical unit is
activated.

PACING = count
Specifies the way pacing is to be handled between VTAM/NCP and the logical
unit. Pacing is used to control the rate of data flow between the OS/400
program and the host system. Pacing allows the receiver to control the rate at
which the sender sends requests.
Each OS/400 logical unit has both a sending and a receiving pacing value.
The AS/400 system supports all valid values for sending and receiving pacing
from 0 to 63. A value of 0 indicates pacing will not be enforced.

DLOGMOD = name
Specifies the logon mode table entry to be used in the bind command to this
LU.

Note: Devices configured for DHCF return an SNA negative response if they
receive user-defined logon messages defined by the USSMSG macroin-
struction with the MSG=10 operand.

Host System Work Sheet

The following work sheet should be used to coordinate the AS/400 subsystem con-
figurations and the VTAM/NCP host system generation.

It is recommended that you use this work sheet in one of the following ways:
Have the host system personnel fill out the work sheet and then use those
values to configure an AS/400 system for DHCF.
You configure the AS/400 system, fill out the work sheet, and then give the
work sheet to the host system personnel.

Chapter 15. Distributed Host Command Facility 15-7

Table 15-1. AS/400 Support VTAM/NCP Configuration Work Sheet
Host Configuration
Generation Parameter Description AS/400 Value Entry
The value specified for the IDNUM parameter of Line parameter EXCHID first 3
the PU macro during VTAM/NCP generation. characters=056 for an AS/400
system
The value specified for the ADDR parameter of Controller STNADR
the PU macro during VTAM/NCP generation.
The value specified in the START procedure for Controller SSCPID
VTAM/NCP as the SSCPID (system services
control point identifier).
The values specified for the LOCADDR parame- Device LOCADR
ters of the LU macros during VTAM/NCP gener-
ation. Up to 255 LU addresses can be assigned
to an AS/400 system under one physical unit
(but only 254 DHCF devices can be configured
on an AS/400 system).

DHCF Configuration Basics

The configuration of the AS/400 system for DHCF requires a line description, a
controller description, and a device description. A summary of each configuration
operation follows.
Note: If using a frame relay network, a network interface description is also
required along with the line description, the controller description, and the
device description.

For information on using the configuration displays and commands, see the Com-
munications Configuration book.

Line Description
Either an SNA SDLC line, a local area network line, or an X.25 data link line using
LU 1 must be created for DHCF. You can create the line descriptions for DHCF by
using the following commands:
Create Line Description (SDLC) (CRTLINSDLC) command
Create Line Description (Token-Ring) (CRTLINTRN) command
Create Line Description (Ethernet) (CRTLINETH) command
Create Line Description (X.25) (CRTLINX25) command
Create Line Description (DDI) (CRTLINDDI) command
Create Line Description (FR) (CRTLINFR) command

The DHCF line type can be either secondary or negotiable for SDLC on the line
description.

15-8 Remote Work Station Support V4R1

Controller Description
Configure your controller using the Create Controller Description (SNA Host)
(CRTCTLHOST) command. DHCF allows attachment of HCF-DHCF sessions on
the same SDLC secondary communications line, X.25 communications line, or local
area network line with the following sessions:
LU 0 (SNUF)
LU 1 (NRF, SPLS, and SNA Remote Job Entry (SRJE))
LU 2 (NRF and SPLS)
LU 2 and 3 (3270 emulation for SNA)
LU 6.2 (APPC)

There can be a total of 254 devices under a host controller. These 254 devices can
be any combination of the above device types.

Device Description
The device description should be created after the associated line and controller
descriptions have been created. This sequence is not required; however, the
system rejects any commands referring to names of descriptions not yet created.
The Create Device Description (Display) (CRTDEVDSP) command, with the param-
eter DEVCLS(*RMT) specified, creates a device description for a remote display
device.

The DHCF device type must be a 3270-type device with a model of *DHCF. 3277,
3278, and 3279 devices can all use this controller attachment. The actual dis-
tinction of device type is made by HCF with the **ACQUIRE. command. The
addressing (the way the sending or control station selects the station to which it is
sending data) of *DHCF devices is a unit address of 01-FE (digits 1-2).

The DHCF device description (DEVD) can be mixed on the controller with APPC,
SNUF, and host device descriptions (including 3270 emulation).

Configuring the System

The following control language (CL) commands are used to define the configuration
for the system in a program called CRTDHCF. This example shows these com-
mands used in a CL program; the configuration can also be defined using the con-
figuration menus.

Chapter 15. Distributed Host Command Facility 15-9

/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
/\ \/
/\ MODULE: CRTDHCF LIBRARY: RMTLIB \/
/\ \/
/\ \/
/\ LANGUAGE: CL \/
/\ \/
/\ FUNCTION: Configures an SDLC nonswitched line to a host with an \/
/\ attached host controller and attached DHCF display. \/
/\ \/
/\ SDLC nonswitched line MVSLIN \/
/\ 3274 Controller MVSCTL \/
/\ 3279 Display MVSDSP \/
/\ \/
/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/
PGM
/\ Create the line description for the nonswitched SDLC line to the \/
/\ host system
CRTLINSDLC LIND(MVSLIN) + /\ Call the line MVSLIN \/
RSRCNAME(LINð11) + /\ LINð11 assign by this system \/
ONLINE(\NO) + /\ Do not vary on automatically \/
ROLE(\SEC) /\ System is secondary station \/
/\ Create the controller description for the host controller \/
CRTCTLHOST CTLD(MVSCTL) + /\ Call the controller MVSCTL \/
LINKTYE(\SDLC) + /\ The line will be SDLC \/
ONLINE(\NO) + /\ Do not vary on automatically \/
APPN(\NO) + /\ Functions of APPN not needed \/
LINE(MVSLIN) + /\ The line will be MVSLIN \/
STNADR(C1) + /\ Primary polls secondary as C1\/
MAXFRAME(521) + /\ Max frame size is 521 bytes \/
RMTNETID(\NONE) /\ ID not needed when not APPN \/
/\ Create the device description for the DHCF display \/
CRTDEVDSP DEVD(MVSDSP) + /\ Call display device MVSDSP \/
DEVCLS(\RMT) + /\ Remote (not local or virtual)\/
TYPE(3279) + /\ DHCF type 3277, 3278, or 3279\/
MODEL(\DHCF) + /\ The model is \DHCF \/
ONLINE(\NO) + /\ Device should match CTL \/
LOCADR(ð1) + /\ The device location address \/
MAXLENRU(\CALC) + /\ Max frame size is \CALC bytes\/
CTL(MVSCTL) /\ Controller to which the \/
/\ device is attached \/
ENDPGM

Figure 15-4. SDLC Nonswitched Line Configuration

Using DHCF for Remote Management

You are ready to log on if you have completed the following:
Established a physical connection between the host system and the AS/400
system.
Performed the proper configuration requirements at the HCF host system and
DHCF nodes.
Started the OS/400 DHCF support using the Vary On Configuration (VRYCFG)
command.

15-10 Remote Work Station Support V4R1

Logging on the Host System
The HCF host system obtains the parameters for the bind command it sends to the
node from an entry in the logon mode table. The logon mode table in which the
entry is found is identified by the MODETAB parameter on the LU or PU macroin-
struction for the node. An entry within the logon mode table is defined by using the
MODEENT macroinstruction.

DHCF Logon Modes (via HCF)

Although various logon modes are valid on the host system, only two are recom-
mended for use when communicating with an AS/400 system using DHCF:

Use logon mode entry FPS1920 when the user display stations are communi-
cating with the host system across an SNA link (the host-to-HCF connection).
(In SNA, a link is the combination of the link connection (the transmission
medium) and two link stations.)
Use logon mode entry HCX3270 when the user display stations are directly
attached to the host system (non-SNA) or are communicating with the host
system across a BSC link (the host-to-HCF connection).

Notes:
1. These SNA and BSC links are not to be confused with the SNA-LU0 link that
must exist between the AS/400 system and the host system. However,
LOGMODE=FS1920 can also be specified on the LU macroinstruction for the
DHCF device-to-HCF connection.
2. When user display stations are non-SNA (directly or BSC-attached) to the host
system, extended data streams (reverse image, blink, underscore, or color) are
not supported to this display.

The following are examples of the two types of DHCF logon modes (identified by
the FPS1920 and HCX3270 logon mode tables).

SNA and Emulation Device Logon Modes

FPS192ð MODEENT LOGMODE=FS192ð,FMPROF=X'ð3',TSPROF=X'ð3',
PRIPROT=X'B1',SECPROT=X'9ð',
COMPROT=X'3ð8ð',RUSIZES=(see note),
PSERVIC=X'ð2ððððððððððððððððððð2ðð'

BSC-attached Device Logon Mode

HCX327ð MODEENT LOGMODE=CX327ð,FMPROF=X'ð2',TSPROF=X'ð2',
PRIPROT=X'71',SECPROT=X'4ð',
COMPROT=X'2ððð',RUSIZES=X'A8A8',
PSERVIC=X'ð2ððððððððððððððððððð2ðð'

Note: The recommended value for the RUSIZES parameter when using remotely
connected SNA terminals is X'A8A8'. The recommended value for locally
connected SNA terminals is X'C7C7'.

The LOGMODE parameter value (FS1920 or CX3270 in these tables) is specified

on the HCF LOGON command by the HCF user at a host terminal:
User: LOGON APPLID(HCF) LOGMODE(CX327ð)

HCF message: CHFððð4I HCF LOGON SUCCESSFUL

Chapter 15. Distributed Host Command Facility 15-11

Start the DHCF Process
HCF starts DHCF by sending a bind command. The parameters for this bind are
defined in the host PU or LU macroinstruction, in this example LU023A10, using
the DLOGMOD parameter. The HCF user at a host terminal specifies the logical
unit on which transmission is started on the HCF **ACQUIRE. command.
\\ACQUIRE.,LUð23A1ð,3277

The AS/400 sign-on display appears. The HCF user then types a user ID and pass-
word (if required). The DHCF session is then active on the AS/400 system and
treats the user as a remote 5250.

The LU name specified in the **ACQUIRE. command is the name as configured in

the host Network Control Program (NCP) generation. The LOCADDR parameter of
the host macroinstruction that applies to that LU name correlates with the LOCADR
parameter in the corresponding device description on the AS/400 system.

Ending the DHCF Process

Three distinct sessions are activated when a user on a System/370 host uses HCF
and DHCF to run an application on the AS/400 system. These sessions are acti-
vated in the following sequence:
1. The user starts a session between the host terminal and HCF by using the
HCF LOGON command.
2. The user starts a session between HCF on the host system and DHCF on the
AS/400 system by using the **ACQUIRE. command.
3. The user starts a third session between DHCF and the AS/400 application by
signing on to the AS/400 system.

The sessions are ended in the reverse order:

1. The user ends the session between DHCF and the AS/400 application by
typing the AS/400 Sign Off (SIGNOFF) command. The AS/400 sign-on display
appears.
2. From the sign-on display, the user ends the session between the host system
and the AS/400 system by using the **DROP. command. When that OS/400
DHCF session is ended, the user still has a session with HCF and can start
other DHCF sessions by using the HCF **ACQUIRE. command again.
AS/4ðð Sign-on display

User: \\DROP.

HCF message: CHFððð2I SESSION WITH LUð23A1ð

HAS TERMINATED

User: \\ACQUIRE.,LUname,327x (begins another

HCF-DHCF session)
3. If no other DHCF sessions are desired, the user ends the HCF session by
entering the **LOGOFF. command.
Note: You may also use the end connection (ENDCNN) parameter of the
SIGNOFF command. For example, type:
SIGNOFF ENDCNN(\YES)

15-12 Remote Work Station Support V4R1

and press the Enter key. This is equivalent to using the AS/400 SIGNOFF
command followed by the HCF **DROP. command (as explained in step 1 and step
2).

Summary of HCF Session Commands Relating to the AS/400 System

The following are the HCF commands to be used by a person at a 3270 display
station to start and end DHCF sessions, or to request help during a session.

Table 15-2. HCF Command Descriptions

Command Description
**ACQUIRE., lu-name, terminal Connects the HCF terminal user at the host system
type to a specific AS/400 system. Valid terminal types are
3277, 3278, and 3279. (HCF can also use the ter-
minal type configured on the AS/400 system.)
**DROP. Disconnects the HCF terminal user at the host
system from the AS/400 system, but maintains the
logical connection between the terminal and the HCF
application on the host system.
**LOGOFF. Disconnects the AS/400 system from the HCF host
system, if connected, and ends the user’s HCF
session.
**HELP. Provides help to the HCF terminal user at the host
system.

Changing HCF Commands, Online Help Information, and

Messages
HCF commands, online help information, and messages can be changed at the
host system to adapt to different situations and computer systems. The HCF com-
mands, online help information, and messages are discussed in the HCF books
listed in the “Bibliography” on page X-1.

HCF Host System 3270 Terminal Requirements

The HCF host system display stations can be either locally attached to the
System/370 system through a channel, or remotely attached through a controller.

The OS/400 DHCF support requires that the host display stations be IBM 3277,
3278, and 3279 devices (or devices able to emulate one of these models), with
1920-character display, typewriter keyboard, and at least 12 function keys. Severe
limitations exist with the use of a data entry keyboard if it does not have at least 12
function keys.

This same support is also supplied for any other display devices that are attached
to the host system through BSC or SNA 3270 device emulation. SNA 3270 device
emulation support allows an AS/400 system to appear as a 3274 Control Unit in a
BSC multipoint network or an SNA network. (A multipoint network allows two or
more stations to communicate with a single system on one line.)

User-defined keyboard assignments are supported by DHCF. For information

regarding assignable keys, see “3270-to-5250 Keyboard Mapping” on page 12-13.

Printers are not supported by HCF.

Chapter 15. Distributed Host Command Facility 15-13

Extended Display Attributes
The AS/400 system and its host system can send the extended attributes of 3278
and 3279 display stations (color, blink, reverse image, and underscore) by sending
the extended data stream for those display stations.

Display Station Requirements for DHCF

Because the host system and the AS/400 system have different types of display
stations attached to them, there are two major areas of consideration.

When DHCF is being used, the 3277, 3278, and 3279 display stations on the
host system must have their keyboards mapped to different values for some of
their function keys. These values are changed so that the 3270 keyboards can
appear to be 5250 keyboards when remotely attached to OS/400DHCF.
Other differences in the way that the keys and data in a 3270 data stream are
handled also exist. For more information, see Chapter 12, “Using 3270 Device
Support” on page 12-1.
Note: In this section, 3270 refers to the keyboards used by any 3277, 3278, or
3279 display station. Where there are specific differences among these
types, the correct number is used instead.

3270 and 5250 Keyboard and Display Differences

Most of the features that are available on a 5250 display station are also available
on a 3270 host system display station. There are, however, a number of differences
that the 3270 user should know about, such as how OS/400 DHCF handles the key
values and data field attributes sent in a 3270 data stream.

For information about the differences between the 3270 and 5250 keyboards and
displays, see “3270 and 5250 Keyboards” on page 12-5.

Messages in DHCF Sessions

When a message arrives for the DHCF work station, you see a Message waiting
message on line 24. To continue, you must press one of the following keys: ATTN
(PF9), Reset (PF10), Sys/Req (PF11), or the Enter key, all of which have reset
capability, or the Help (PF1). After this, you can review the waiting message by
entering the Display Message (DSPMSG) command or by pressing the Sys/Req
key (PF11), then selecting option 6 (Display system operator message).
Note: Sys/Req (PF11) and Help (PF1) reset the line but send another message to
line 24, which requires that you press the Reset key again.

For additional information on error messages, see “Messages” on page 12-11.

DHCF Differences
Following are the differences in DHCF support between the AS/400 system and the
System/36 and System/38.

15-14 Remote Work Station Support V4R1

Differences from System/36 DHCF Support
To specify a different arrangement of 3270-to-5250 keyboard mapping during a
System/36 DHCF session, you use the KEYS procedure to define and then select
the keyboard mapping version. On the AS/400 system, you use the Set Keyboard
Map (SETKBDMAP), Change Keyboard Map (CHGKBDMAP), and Display Key-
board Map (DSPKBDMAP) commands. The AS/400 system does not support the
KEYS procedure.

When an application program running on a System/36 includes the hexadecimal

Differences from System/38 DHCF Support

The System/38 supports the Define Keyboard Map (DEFKBDMAP) command. On
the AS/400 system, the Set Keyboard Map (SETKBDMAP) command replaces the
DEFKBDMAP command.

Chapter 15. Distributed Host Command Facility 15-15

15-16 Remote Work Station Support V4R1
Chapter 16. Network Routing Facility
This chapter discusses the network routing facility (NRF) support in the OS/400
licensed program.

Network Routing Facility—Definition

Network routing facility (NRF) support enables 3270 display station to AS/400
system connections. OS/400 NRF support requires the Network Routing Facility
(NRF) licensed program to be operating under the Network Control Program (NCP)
licensed program. NCP runs Systems Network Architecture (SNA) communications
controllers such as the IBM 3720 and 3745, providing controller support for single-
domain, multiple-domain, and interconnected network capabilities. SNA includes the
logical structure, formats, protocols, and operational sequences for transmitting
information units through networks, and controlling the configuration and operation
of networks.

How NRF Operates

NRF operates in much the same way as the host command facility (HCF). In both
NRF and HCF, users attached to the System/370 host computer can access an
AS/400 system as if they were 5250 display station users. NRF, however, differs
from HCF in that NRF supports printers and does not use System/370 host-system
processing unit time.

NRF allows a 3270 display station user or 3287-type printer to access an AS/400
system through an SNA communications controller. In performing this function, NRF
uses session partner routing to associate SNA logical units (LU) as a pair in a
System/370 SNA Virtual Telecommunications Access Method (VTAM) network. A
VTAM network is a set of programs that maintains control of the communication
between terminals and application programs running under DOS/VS, OS/VS1, and
OS/VS2 operating systems.

To perform this function, NRF is installed (under NCP) on an SNA communications

controller with network connections to both the AS/400 system and the display and
printer devices. NRF acts as the primary logical unit (PLU), which contains the
primary half-session for a logical unit to logical unit session. Both the AS/400 appli-
cation and the 3x74 controller act as secondary logical units (SLUs). SLUs
contain secondary half-sessions for a logical unit to logical unit session.

Primary logical units are normally associated with applications running under
VTAM, such as the CICS* product. Secondary logical units are normally associated
with devices attached to the network, such as sessions with displays. When NRF is
the primary logical unit, however, all other devices attached to it become secondary
logical units.

NRF appears as application PLU to SNA 3270 users. However, unlike traditional
VTAM PLUs, it resides in the SNA communications controller and not in the
System/370 host computer.

For information about the 5250 Optimization support for 3270 display stations, see
“5250 Data Stream Optimization Support” on page 12-1.

Network Routing Facility Sessions
During the operation of NRF sessions in this application, VTAM is involved in only
starting and ending the session. Once a pair of LUs are in session with each other,
VTAM is aware of the session, but is not aware of the actual data flowing on the
session. Data flows between the two LUs across the NCP backbone without going
to the VTAM hosts. Once in session, NRF no longer requires the hosts to be active.

VTAM is involved in starting and ending the session for the LU-to-LU session that
connects the application to NRF and is also involved in starting and ending the
LU-to-LU session that connects NRF to the display or printer. For the simplest
connection between an application and a device, VTAM must configure four LUs
and NRF must configure a connection between two LUs.
Note: AS/400 systems will only support Version 1 Release 5 or later releases of
NRF.

For additional information about NRF session definitions, session setup, and
session endings, refer to the book Network Routing Facility Migration, Resource
Definition, and Customization, SC31-6203.

Network Routing Facility—Benefits

NRF adds flexibility to a network and reduces overall line costs by giving the user
more options in accessing applications. The following are ways NRF can be used.

Passing Through an SNA Network to an AS/400 System

Basic network routing facility operation is used by a user working on a 327x display
attached to a System/370 backbone network through a 3x74 controller. The user
can pass through the SNA network and access an AS/400 system. In addition,
applications on the AS/400 system are able to print information on printers that are
attached to the System/370 backbone network through a 3x74 controller.

For an illustration of a user passing through a System/370 network to access an

AS/400 system, see Figure 16-1 on page 16-3.

16-2 Remote Work Station Support V4R1

ES/9000
System

3745 Controller
(NCP) and NRF)

3174
Controller
AS/400 System

3279 3287
Display Printer
RV3P104-0

Figure 16-1. Passing through a System/370 Network to Access an AS/400 System

Adding Flexibility to an SNA Backbone Network

An SNA backbone network may consist of many System/370 host computers, to
which an even larger number of controllers, AS/400 systems, displays, and printers
are attached. Because of this complexity, display and printer devices that are phys-
ically very close together (for example, in the same building) may be signed on to
applications in different parts of the network.

In Figure 16-2 on page 16-4, NRF provides the connection between display
DSP01 (or DSP02) and Application C or between Application C and printer PRT01.
Also, a single display (for example, DSP02) may access different applications on
the various systems at different times.
Note: Figure 16-2 on page 16-4 shows one copy of NRF on the network. Only
one copy of NRF is required on the network. All sessions using NRF will be
routed through that SNA communications controller. Consider installing
additional copies of NRF on other SNA communications controllers to
provide possible improvements in performance.

Chapter 16. Network Routing Facility 16-3

ES/9000 ES/9000
System System

3745 Controller 3745 Controller

(NCP) (NCP and NRF))

AS/400
System

3174
Application C Controller

AS/400
System

3279 3279 3287

Display Display Printer
DSP01 DSP02 PRT01 RV3P103-0

Figure 16-2. NRF within an SNA Backbone Network

Configuring the AS/400 System to Support Network Routing Facility

To configure the AS/400 system to communicate with NRF, perform these steps:
1. Configure a line description to the System/370 host network (see “Step 1: Con-
figuring the Line to the Host Network” on page 16-5).
2. Configure a host controller description (see “Step 2: Configuring the Host Con-
troller to Support Network Routing Facility” on page 16-6).
3. Configure a 32xx device with an application type of *NRF (see “Step 3: Config-
uring the Device” on page 16-7).
Note: If you are using a frame relay network, you need to create a network inter-
face description. For more information on creating a network interface
description, see the Communications Configuration book.

For information on how to configure the System/370 host to support NRF, refer to
the System/370 documentation.

16-4 Remote Work Station Support V4R1

Specifying Parameters for Network Routing Facility Support
The following parameters and values apply to AS/400 support of NRF for the com-
mands Create Device Description (Display) (CRTDEVDSP), Create Device
Description (Printer) (CRTDEVPRT), Change Device Description (Display)
(CHGDEVDSP) and Change Device Description (Printer) (CHGDEVPRT).

Device description (DEVD)

Specifies the name of the device description.

Device class (DEVCLS)

Specifies the class of the configured device. The value to use for the DEVCLS
parameter to support NRF is:

*RMT
The device is considered a remote device.

Device type (TYPE)

Specifies the type of remote 32xx printer or display device being configured.

Device model (MODEL)

Specifies the model number of the device being configured to support NRF.
For 32xx display devices, valid values are 0 or 4. For 3287 printer devices, only
0 is valid. *DHCF should not not be used as a value for the MODEL parameter.

Application type (APPTYPE)

Specifies the type of application for which this device is being used. Valid
values for the APPTYPE parameter can be:

*NONE
The device is not being used for any special applications. This is the
default.

*NRF
The device is being used for the network routing facility application.

Host signon/logon command (LOGON)

Specifies the logon string that will be sent to the system services control point
(SSCP) on the host network at file open time. Valid values for the LOGON
parameter can be:

*NONE
No logon string is specified.

logon string
A logon string of up to 256 characters. For more information on the logon
string, see “Step 3: Configuring the Device” on page 16-7 and “Using
Network Routing Facility” on page 16-9.

Step 1: Configuring the Line to the Host Network

Use one of the following commands to configure a line to the host system that will
support NRF:
Create Line Description (SDLC) (CRTLINSDLC)
Create Line Description (Token-Ring) (CRTLINTRN)
Create Line Description (Ethernet) (CRTLINETH)
Create Line Description (X.25) (CRTLINX25)

Chapter 16. Network Routing Facility 16-5

Create Line Description (Frame Relay) (CRTLINFR)
Create Line Description (DDI) (CRTLINDDI)
Note: If using a frame relay network, a network interface description is also
required along with the line description, the controller description, and the
device description.

This step may already have been performed if the AS/400 system has been com-
municating with the System/370 host for such functions as 3270 emulation or Host
Command Facility and distributed host command facility (HCF-DHCF).

Step 1: Configuring the Line to the Host Network is an example of an SDLC line
configured to the System/370 host to support NRF. In this example, the user has
chosen a line description name of HOSTLINE and a resource name of LIN012 to
describe the line to the host network. Note that the data link role parameter
describes the AS/400 system as *SEC, a secondary logical unit.

à ð
Create Line Desc (SDLC) (CRTLINSDLC)

Type choices, press Enter.

Line description . . . . . . . . > HOSTLINE Name

Resource names . . . . . . . . . > LINð12 Name
+ for more values
Online at IPL . . . . . . . . . > \NO \YES, \NO
Data link role . . . . . . . . . > \SEC \NEG, \PRI, \SEC
Physical interface . . . . . . . \RS232V24 \RS232V24, \V35, \X21, ...
Connection type . . . . . . . . \NONSWTPP \NONSWTPP, \SWTPP, \MP, \SHM
Switched network backup . . . . \NO \NO, \YES
Exchange identifier . . . . . . \SYSGEN ð56ððððð-ð56FFFFF, \SYSGEN
NRZI data encoding . . . . . . . \YES \YES, \NO
Line speed . . . . . . . . . . . 96ðð 6ðð, 12ðð, 24ðð, 48ðð...
Modem type supported . . . . . . \NORMAL \NORMAL, \V54, \IBMWRAP...
Maximum frame size . . . . . . . 521 265, 521, 1ð33, 2ð57
Duplex . . . . . . . . . . . . . \HALF \HALF, \FULL
Inactivity timer . . . . . . . . 3ðð \NOMAX, 15ð-42ðð (ð.1 sec)
Poll response delay . . . . . . ð ð-2ð48 (ð.ððð1 seconds)
More...
F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display
F24=More keys

á ñ
Figure 16-3. Step 1: Configuring the Line to the System/370 Host Network

Step 2: Configuring the Host Controller to Support Network Routing

Facility
Using the Create Controller Description (SNA Host) (CRTCTLHOST) command,
enter the controller description and the link type. Again, this may already have been
done if the AS/400 system has been communicating with the System/370 host for
such functions as 3270 emulation or Host Command Facility and distributed host
command facility (HCF-DHCF).

“Step 2: Configuring the Host Controller to Support Network Routing Facility” is an

example of a host controller description that supports NRF. Note that the attached
nonswitched line parameter specifies the line description (HOSTLINE) that was
created in “Step 1: Configuring the Line to the Host Network” on page 16-5. The

16-6 Remote Work Station Support V4R1

user chose to name the controller description HOSTCTL and the link type *SDLC to
designate that the line is an SDLC line.

à ð
Create Ctl Desc (SNA Host) (CRTCTLHOST)

Type choices, press Enter.

Controller description . . . > HOSTCTL__

. . Name
Link type . . . . . . . . . > \SDLC__
. . \IDLC, \FR, \LAN, \SDLC, \X25
Online at IPL . . . . . . . . .
> \NO \YES, \NO
Switched connection . . . . . .
\NO \NO, \YES
Switched network backup . . . .
\NO \NO, \YES
APPN-capable . . . . . . . . . .
> \NO \YES, \NO
Attached nonswitched line . . .
> HOSTLINE Name
Maximum frame size . . . . . . .
\LINKTYPE 265-16393, 256, 265, 512...
Remote network identifier . . .
\NETATR Name, \NETATR, \NONE, \ANY
Remote control point . . . . . .
________ Name, \ANY
SSCP identifier . . . . . . . .
________ ð5ðððððððððð-ð5FFFFFFFFFF
Local exchange identifier . . .
\LIND ð56ððððð-ð56FFFFF, \LIND
Station address . . . . . . .
> C1. ð1-FE
Recontact on vary off . . . . .
\YES \YES, \NO
Text 'description' . . . . . . .
\BLANK________________________________
Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 16-4. Step 2: Configuring the Host Controller to Support NRF

Step 3: Configuring the Device

To configure a 3270-type display, use the Create Device Description (Display)
(CRTDEVDSP) command. To configure a 3287-type printer, use the Create Device
Description (Printer) (CRTDEVPRT) command. On the CRTDEVDSP or
CRTDEVPRT display, enter the device description name, the device class (*RMT
for the AS/400 system), the 327x device type, and the device model. You also need
to fill in the application type parameter with a type of *NRF. Also, in some
instances, fill in the host signon/logon command (LOGON) parameter. For
DBCS-capable devices, fill in the DBCS feature (IGCFEAT) parameter. For informa-
tion about configuring the IGCFEAT parameter, see Table 13-1 on page 13-11.

There are four methods of initiating a session between the AS/400 LU and NRF.
Only one method of initiating the session should be used for each VTAM LU that is
defined. The four methods are:
1. LOGON text in the AS/400 device description
This is required for printer device descriptions.
2. AUTOINIT parameter on NRF session partner for the connection between NRF
and the AS/400 display device descriptions
The AUTOINIT parameter on NRF session partner for the connection between
NRF and the printer.
3. VTAM operator command
4. LOGAPPL parameter configured on the VTAM LU definition

Chapter 16. Network Routing Facility 16-7

Note: The AUTOINIT parameter on the NRF session partner or LOGON text on
the AS/400 device description is recommended. Using the LOGAPPL
parameter on the VTAM LU definition is not recommended.

The LOGON parameter is the logon string, which is sent to the VTAM system ser-
vices control point on the host system at file-open time.

The logon string must be sent if VTAM is configured such that the AS/400 system
must initiate the NRF-to-AS/400 session, or for *NRF printer devices. The logon
string is optional if only *NRF display devices are being used.

When the logon string is configured using the CRTDEVDSP or CRTDEVPRT com-
mands, the AS/400 NRF support automatically sends the logon string, and there is
no need for operator action other than varying on the *NRF device.

“Step 3: Configuring the Device” on page 16-7 shows a configuration for a 3279
*NRF display device with a device description name of DSP02, a device class of
*RMT, a device type of 3279, and a device model of 0. The attached controller
parameter shows the controller description HOSTCTL created in “Step 2: Config-
uring the Host Controller to Support Network Routing Facility” on page 16-6

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > DSPð2____ Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3279 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ðE ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > HOSTCTL___ Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, BLI...
Drop line at signoff . . . . . . \YES \YES, \NO
Application type . . . . . . . . > \NRF \NONE, \NRF, \CTLSSN...
Inactivity timer . . . . . . . . \ATTACH 1-3ð, \ATTACH, \NOMAX...
Host signon/logon command . . . \NONE

More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 16-5. Step 3: Configuring the Device to Controller

Note: Do not specify *YES for the Drop line at signoff parameter if you are using
switched lines with the LOGON text. If you want to end the session without
dropping the switched line, use the SIGNOFF ENDCNN(*YES) command.

16-8 Remote Work Station Support V4R1

Using Network Routing Facility
Users who want to access an AS/400 system using the session partner function of
NRF must issue an unformatted system services (USS) request to the VTAM
system services control point (SSCP) in the form of a logon string.

The logon string consists of three parts:

Application Identifier (APPLID)

Specifies the requested application.

SNA Logon Mode (LOGMODE)

Specifies the logon mode entry that is used to select a set of session parame-
ters for the session to be established.

Data Operand (DATA)

Specifies the user data that will be made available to the logon exit routine of
the application program.

The logon request may appear in either basic assembler language (BAL) or PL/I
format. However, the logon string must be entered in the same format as the logon
string configured in the USS VTAM table on the System/370 host. It is also recom-
mended that you enter the logon string entirely in uppercase characters.

An example of a full logon string written in PL/I could look like this:
LOGON APPLID(NRF1Að3) LOGMODE(SD82) DATA(USERDATA)

In this example, the application identifier (APPLID) is named NRF1A03, the SNA
logon mode is labeled SD82, and the data operand specifies the user data to be
made available to the logon exit routine of the application program.

3270 Device Support

For information on 3270 device support provided by the AS/400 system, see
Chapter 12, “Using 3270 Device Support” on page 12-1.

Customizing Your SNA 3270 Display Keyboard Map

For instructions on customizing your 3270 display keyboard to be mapped as a
5250 display keyboard, see “3270-to-5250 Keyboard Mapping” on page 12-13. The
instructions for customizing your keyboard using NRF are the same as for other
3270 support.

AS/400 Work Station Printing

Most installations require the remote 3270 work station printers to print from either
the System/370 host or the AS/400 system, depending on the application require-
ments. It is important to make sure the 3270 printer LU is not kept permanently
committed to either the System/370 host or the AS/400 system. If either system
keeps the LU, the other will not be able to use it. System/370 VTAM applications
should be reviewed to make sure that printer LUs are released after the printer
spool queues are cleared.

To allow printer sharing, the AS/400 printer device description must be configured
such that the session is unbound when there are no more spooled files. Use the
inactivity timer (INACTTMR) parameter on the Create Device Description (Printer)

Chapter 16. Network Routing Facility 16-9

(CRTDEVPRT) command. Specify a short length of time for the session to remain
bound after a spooled file has completed printing.

Because NRF allows the 3287 printers in the network to be shared by users on the
System/370 host and the AS/400 system, you may not always have immediate
access to the printer. A message is displayed indicating that the printer is unavail-
able. If you try to print, but find that the printer is already in use, wait a short while
and try again.

Ending Network Routing Facility

You may use either of the following two methods to end NRF:
1. Use the ENDCNN parameter of the SIGNOFF command to sign off the AS/400
system and end the session between your 3270 display station and the AS/400
system. For example, type:
SIGNOFF ENDCNN(\YES)

and press the Enter key.

2. Do the following:
a. Sign off the AS/400 system using the SIGNOFF command.
b. Press the 3270 system request key.
c. Log off VTAM using the LOGOFF command for VTAM.

If you sign off the system while using NRF without ending NRF, the session
remains bound even after you sign off. This prevents other users from using the
system and network resources used by this session.

VTAM Logon Mode and Definition Table Examples

This section contains sample System/370 VTAM logon mode (logmode) tables, and
AS/400 system and NCP definitions. These tables are configured on the
System/370 to allow the LU-to-LU connections necessary for NRF operation.

Logmode Tables
The following figure contains sample VTAM logon mode tables. These tables are
used to define the characteristics of the session established by NRF to the 3270
devices and to the AS/400 system. The characteristics defined must be compatible
with each other. That is, the characteristics of the session for an application on the
AS/400 system must be compatible with the characteristics of the session for the
3270 device. To test the compatibility of the characteristics of the session, complete
your configuration and send a break message to the NRF device. If the display is
restored when the break message is cleared, the values for the VTAM logon mode
tables are probably correct.

16-10 Remote Work Station Support V4R1

SD82 MODETAB
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ LOGMODE PAIR FOR 24 X 8ð TERMINAL -- PACING = ð, 256 BYTE RU \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SD82 MODEENT LOGMODE=SD82, 327ð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð8ð', BYTE ð6 - ð7
SSNDPAC=X'ðð', BYTE ð8
SRCVPAC=X'ðð', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð2ðððððððððð185ð185ð7Fðð', BYTE 14-25
RUSIZES=X'8585'
SD82HD MODEENT LOGMODE=SD82HD, AS/4ðð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ðð', BYTE ð8
SRCVPAC=X'ðð', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð2ðððððððððð185ð185ð7Fðð', BYTE 14-25
RUSIZES=X'8585' BYTE 1ð - 11
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ LOGMODE PAIR FOR 24 X 8ð TERMINAL -- PACING = ð, 256ð BYTE RU \
\ NOTE - PSERVIC CAN BE ANY ACCEPTABLE VALUE \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
TRNð MODEENT LOGMODE=TRNð, 327ð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'Bð', BYTE ð5
COMPROT=X'3ð8ð', BYTE ð6 - ð7
SSNDPAC=X'ðð', BYTE ð8
SRCVPAC=X'ðð', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð2ððððððððððððððððððð2ðð', BYTE 14-25
RUSIZES=X'A8A8'
TRNHDð MODEENT LOGMODE=TRNHDð, AS/4ðð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'Bð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ðð', BYTE ð8
SRCVPAC=X'ðð', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð2ððððððððððððððððððð2ðð', BYTE 14-25
RUSIZES=X'A8A8'

Figure 16-6 (Part 1 of 3). Sample System/370 VTAM Logmode Tables

Chapter 16. Network Routing Facility 16-11

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ LOGMODE PAIR FOR 24 X 8ð TERMINAL -- PACING = 7, 512 BYTE RU \
\ NOTE - RUSIZE AND PACING VALUES MUST CORRESPOND WITH 3X74 \
\ CONFIGURATION VALUES \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
TRN7 MODEENT LOGMODE=TRN7, 327ð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'Bð', BYTE ð5
COMPROT=X'3ð8ð', BYTE ð6 - ð7
SSNDPAC=X'ð7', BYTE ð8
SRCVPAC=X'ð7', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð2ððððððððððððððððððð2ðð', BYTE 14-25
RUSIZES=X'8686'
TRNHD7 MODEENT LOGMODE=TRNHD7, AS/4ðð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'Bð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ð7', BYTE ð8
SRCVPAC=X'ð7', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð2ððððððððððððððððððð2ðð', BYTE 14-25
RUSIZES=X'8686' BYTE 1ð - 11
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ \
\ LOGMODE PAIR FOR 328X PRINTER -- PACING = 1 (MINIMUM VALUE) \
\ 256 BYTE RU \
\ \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SCSPTR MODEENT LOGMODE=SCSPTR, 327ð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð8ð', BYTE ð6 - ð7
SSNDPAC=X'ð1', BYTE ð8
SRCVPAC=X'ð1', BYTE ð9
PSERVIC=X'ð1ððððððE1ðððððððððððððð', BYTE 14-25
PSNDPAC=X'ð1', BYTE 11
RUSIZES=X'8585'

Figure 16-6 (Part 2 of 3). Sample System/370 VTAM Logmode Tables

16-12 Remote Work Station Support V4R1

SCSPTRR MODEENT LOGMODE=SCSPTRR, AS/4ðð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ð1', BYTE ð8
SRCVPAC=X'ð1', BYTE ð9
PSERVIC=X'ð1ððððððE1ðððððððððððððð', BYTE 14-25
PSNDPAC=X'ð1', BYTE 11
RUSIZES=X'8585'
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ \
\ LOGMODE PAIR FOR 328X PRINTER -- PACING = 3, 512 BYTE RU \
\ \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SCSTRN MODEENT LOGMODE=SCSTRN, 327ð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð8ð', BYTE ð6 - ð7
SSNDPAC=X'ð3', BYTE ð8
SRCVPAC=X'ð3', BYTE ð9
PSERVIC=X'ð1ððððððE1ðððððððððððððð', BYTE 14-25
PSNDPAC=X'ð3', BYTE 11
RUSIZES=X'8686'
SCSTRNR MODEENT LOGMODE=SCSTRNR, AS/4ðð LOGMODE
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ð3', BYTE ð8
SRCVPAC=X'ð3', BYTE ð9
PSERVIC=X'ð1ððððððE1ðððððððððððððð', BYTE 14-25
PSNDPAC=X'ð3', BYTE 11
RUSIZES=X'8686'

Figure 16-6 (Part 3 of 3). Sample System/370 VTAM Logmode Tables

Network Control Program Definitions

The following tables define NRF virtual devices on the SNA communications con-
troller to the host system.

Chapter 16. Network Routing Facility 16-13

R4GEN OPTIONS NEWDEFN=YES,USERGEN=(CXRNRF,X25NPSI)
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
\ NRF VIRTUAL DEFINITIONS \
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
GRPNRF1 GROUP LNCTL=SDLC,VIRTUAL=YES,ISTATUS=INACTIVE,VPACING=ð,VIROWN\
ER=CXRNRF,PACING=ð,DIAL=NO
LNENRF1 LINE LINEFVT=CXRXFVT,PUFVT=CXRXFVT,LUFVT=(CXRXFVT,CXRXFVT),LIN\
ECB=CXRXLNK
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ FIRST GROUP USES SESSION PARTNER ROUTING \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\
NRF1PUA PU PUTYPE=2,PUCB=CXRPðððð
\
NRF1Að1 LU NRF.SESSPART=NRF1Bð1,LOCADDR=ð1,LUCB=(CXRLðððð,CXRSðððð)
NRF1Að2 LU NRF.SESSPART=NRF1Bð2,LOCADDR=ð2,LUCB=(CXRLððð1,CXRSððð2)
NRF1Að3 LU NRF.SESSPART=NRF1Bð3,LOCADDR=ð3,LUCB=(CXRLððð2,CXRSððð4)
NRF1Að4 LU NRF.SESSPART=NRF1Bð4,LOCADDR=ð4,LUCB=(CXRLððð3,CXRSððð6)
NRF1Að5 LU NRF.SESSPART=NRF1Bð5,LOCADDR=ð5,LUCB=(CXRLððð4,CXRSððð8)
NRF1Að6 LU NRF.SESSPART=NRF1Bð6,LOCADDR=ð6,LUCB=(CXRLððð5,CXRSðððA)
NRF1Að7 LU NRF.SESSPART=NRF1Bð7,LOCADDR=ð7,VPACING=1,LUCB=(CXRLððð6,CX\
RSðððC)
NRF1Að8 LU NRF.SESSPART=NRF1Bð8,LOCADDR=ð8,VPACING=3,LUCB=(CXRLððð7,CX\
RSðððE)
\
NRF1PUB PU PUTYPE=2,PUCB=CXRPððð1
\
NRF1Bð1 LU NRF.SESSPART=NRF1Að1,LOCADDR=ð1,LUCB=(CXRLððð8,CXRSððð1)
NRF1Bð2 LU NRF.SESSPART=NRF1Að2,LOCADDR=ð2,LUCB=(CXRLððð9,CXRSððð3)
NRF1Bð3 LU NRF.SESSPART=NRF1Að3,LOCADDR=ð3,LUCB=(CXRLðððA,CXRSððð5)
NRF1Bð4 LU NRF.SESSPART=NRF1Að4,LOCADDR=ð4,LUCB=(CXRLðððB,CXRSððð7)
NRF1Bð5 LU NRF.SESSPART=NRF1Að5,LOCADDR=ð5,LUCB=(CXRLðððC,CXRSððð9)
NRF1Bð6 LU NRF.SESSPART=NRF1Að6,LOCADDR=ð6,LUCB=(CXRLðððD,CXRSðððB)
NRF1Bð7 LU NRF.SESSPART=NRF1Að7,LOCADDR=ð7,VPACING=1,LUCB=(CXRLðððE,CX\
RSðððD)
NRF1Bð8 LU NRF.SESSPART=NRF1Að8,LOCADDR=ð8,VPACING=3,LUCB=(CXRLðððF,CX\
RSðððF)
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AS/4ðð USING SDLC LINE TO CONNECT TO NRF \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
R4ð82 LINE ADDRESS=(ð82,HALF),ETRATIO=25ð,ISTATUS=INACTIVE,RETRIES=(\
ð7,ð5,ð3),SPEED=96ðð,MAXDATA=265,OWNER=MVS,PACING=ð,VPAC\
ING=ð
SERVICE ORDER=(R4ð82A,R4ð82B)

Figure 16-7 (Part 1 of 2). System/370 VTAM Tables Defining NCP on the SNA Communi-
cations Controller

16-14 Remote Work Station Support V4R1

R4ð82A PU ADDR=C1,ISTATUS=INACTIVE
R4ð82Að1 LU LOCADDR=ð1,ISTATUS=INACTIVE
R4ð82Að2 LU LOCADDR=ð2,ISTATUS=INACTIVE,LOGAPPL=NRF1Að2,DLOGMOD=SD82HD
R4ð82Að3 LU LOCADDR=ð3,ISTATUS=INACTIVE,LOGAPPL=NRF1Að3,DLOGMOD=SD82HD
R4ð82Að4 LU LOCADDR=ð4,ISTATUS=INACTIVE
R4ð82Að5 LU LOCADDR=ð5,ISTATUS=INACTIVE
R4ð82Að6 LU LOCADDR=ð6,ISTATUS=INACTIVE
R4ð82Að7 LU LOCADDR=ð7,ISTATUS=INACTIVE,LOGAPPL=NRF1Að7,DLOGMOD=SCSPTR
R4ð82Að8 LU LOCADDR=ð8,ISTATUS=INACTIVE
R4ð82Að9 LU LOCADDR=ð9,ISTATUS=INACTIVE
R4ð82A1ð LU LOCADDR=1ð,ISTATUS=INACTIVE
R4ð82A11 LU LOCADDR=11,ISTATUS=INACTIVE
R4ð82A12 LU LOCADDR=12,ISTATUS=INACTIVE
R4ð82A13 LU LOCADDR=13,ISTATUS=INACTIVE
R4ð82A14 LU LOCADDR=14,ISTATUS=INACTIVE
R4ð82A15 LU LOCADDR=15,ISTATUS=INACTIVE
R4ð82A16 LU LOCADDR=16,ISTATUS=INACTIVE
R4ð82A17 LU LOCADDR=17,ISTATUS=INACTIVE
R4ð82A18 LU LOCADDR=18,ISTATUS=INACTIVE
R4ð82A19 LU LOCADDR=19,ISTATUS=INACTIVE
R4ð82A2ð LU LOCADDR=2ð,ISTATUS=INACTIVE
R4ð82A21 LU LOCADDR=21,ISTATUS=INACTIVE
R4ð82A22 LU LOCADDR=22,ISTATUS=INACTIVE
R4ð82A23 LU LOCADDR=23,ISTATUS=INACTIVE
R4ð82A24 LU LOCADDR=24,ISTATUS=INACTIVE
R4ð82A25 LU LOCADDR=25,ISTATUS=INACTIVE
R4ð82A26 LU LOCADDR=26,ISTATUS=INACTIVE
R4ð82A27 LU LOCADDR=27,ISTATUS=INACTIVE
R4ð82A28 LU LOCADDR=28,ISTATUS=INACTIVE
R4ð82A29 LU LOCADDR=29,ISTATUS=INACTIVE
R4ð82A3ð LU LOCADDR=3ð,ISTATUS=INACTIVE
R4ð82A31 LU LOCADDR=31,ISTATUS=INACTIVE
R4ð82A32 LU LOCADDR=32,ISTATUS=INACTIVE
R4ð82B PU ADDR=C2,ISTATUS=INACTIVE
R4ð82Bð1 LU LOCADDR=ð1,ISTATUS=INACTIVE
R4ð82Bð2 LU LOCADDR=ð2,ISTATUS=INACTIVE
R4ð82Bð3 LU LOCADDR=ð3,ISTATUS=INACTIVE
R4ð82Bð4 LU LOCADDR=ð4,ISTATUS=INACTIVE
R4ð82Bð5 LU LOCADDR=ð5,ISTATUS=INACTIVE
R4ð82Bð6 LU LOCADDR=ð6,ISTATUS=INACTIVE
R4ð82Bð7 LU LOCADDR=ð7,ISTATUS=INACTIVE
R4ð82Bð8 LU LOCADDR=ð8,ISTATUS=INACTIVE

Figure 16-7 (Part 2 of 2). System/370 VTAM Tables Defining NCP on the SNA Communi-
cations Controller

VTAM Definitions for the AS/400 System

The following figure contains VTAM-switched major mode definitions for the con-
nection between NRF and the AS/400 system:

Chapter 16. Network Routing Facility 16-15

SW744 VBUILD TYPE=SWNET, REQUIRED PARAMETER X
MAXNO=8, MAX OF 8 DIAL NUMBERS MAY BE DEFINED \
MAXGRP=5 MAX OF 5 LINE GROUPS MAY BE DEFINED
SW744A PU ADDR=C1, 8 BIT STATION UNIQUE ADDRESS X
DISCNT=NO, ACCEPT DISCONTACT FROM PU (DEFAULT) X
IDBLK=ð56, 12 BIT BLOCK NUMBER FOR AS/4ðð X
IDNUM=ð31ðð, 2ð BIT ID NUMBER FOR REMOTE SYSTEM X
MAXDATA=1994, AS/4ðð MAXDATA FOR TOKENRING X
MAXPATH=8, MAX OF 8 PATHS FOR CALL OUT X
NETID=RPC, AS/4ðð LOCAL NETID VALUE X
PACING=ð, ð PACING X
PASSLIM=7, 7 CONTIGUOUS PIUS MAX AT ONE TIME X
PUTYPE=2, VALID FOR TYPE 2 OR 2.1 SUPPORT X
ISTATUS=ACTIVE, ACTIVATE WITH MAJOR NODE X
MODETAB=LOGMOD38, VTAM LOGON MODE TABLE ON S/37ð \
SSCPFM=USSSCS, VTAM TO STRIP/ADD MEDIA CONTROL CHAR \
VPACING=ð ð VPACING
\
PATH1 PATH GRPNM=R3Gð92L,DIALNO=ð5ð44ððð31ðððððð
\

SW744Að1 LU LOCADDR=ð1, CORRESPONDS TO AS/4ðð LOCADDR ð1 X

ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW744Að2 LU LOCADDR=ð2, CORRESPONDS TO AS/4ðð LOCADDR ð2 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW744Að3 LU LOCADDR=ð3, CORRESPONDS TO AS/4ðð LOCADDR ð3 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW744Að4 LU LOCADDR=ð4, CORRESPONDS TO AS/4ðð LOCADDR ð4 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW744Að5 LU LOCADDR=ð5, CORRESPONDS TO AS/4ðð LOCADDR ð5 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW744Að6 LU LOCADDR=ð6, CORRESPONDS TO AS/4ðð LOCADDR ð6 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SW744Að7 LU LOCADDR=ð7,DLOGMOD=SCSPTRR,PACING=1,VPACING=1, X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW744Að8 LU LOCADDR=ð8,VPACING=3,PACING=3,DLOGMOD=SCSTRNR, X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE

Figure 16-8. System/370 VTAM AS/400 System Definitions

VTAM Definitions for the 3174 Controller

The following figure contains VTAM-switched major mode definitions for the con-
nection between NRF and the 3174 controller:

16-16 Remote Work Station Support V4R1

SQ324 VBUILD TYPE=SWNET, REQUIRED PARAMETER X
MAXNO=8, MAX OF 8 DIAL NUMBERS MAY BE DEFINED X
MAXGRP=5 MAX OF 5 LINE GROUPS MAY BE DEFINED
SQ324A PU ADDR=C1, 8 BIT STATION UNIQUE ADDRESS X
DISCNT=NO, ACCEPT DISCONTACT FROM PU (DEFAULT) X
IDBLK=ð17, 12 BIT BLOCK NUMBER FOR 3174 X
IDNUM=ððððð, 2ð BIT ID NUMBER FOR REMOTE SYSTEM X
MAXDATA=1994, AS/4ðð MAXDATA FOR TOKENRING X
MAXPATH=8, MAX OF 8 PATHS FOR CALL OUT X
PACING=ð, ð PACING X
PUTYPE=2, VALID FOR TYPE 2 OR 2.1 SUPPORT X
ISTATUS=ACTIVE, ACTIVATE WITH MAJOR NODE X
MODETAB=SD82, VTAM LOGN MODE TABLE ON S/37ð \
SSCPFM=USSSCS, VTAM TO STRIP/ADD MEDIA CONTROL CHAR \
VPACING=ð ð VPACING
\
PATH1 PATH GRPNM=R4Gð88L,DIALNO=ð1ð44ððð3174ððð4
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ USING NRF SESSION PARTNER ROUTING -- NRF1B.. IS PARTNER TO NRF1A.. \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SQ324Að2 LU LOCADDR=ð2, CORRESPONDS TO 3174 PORT ðð X
ISTATUS=ACTIVE,LOGAPPL=NRF1Bð2
SQ324Að3 LU LOCADDR=ð3, CORRESPONDS TO 3174 PORT ð1 X
ISTATUS=ACTIVE,LOGAPPL=NRF1Bð3
SQ324Að4 LU LOCADDR=ð4, CORRESPONDS TO 3174 PORT ð2 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SQ324Að5 LU LOCADDR=ð5, CORRESPONDS TO 3174 PORT ð3 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SQ324Að6 LU LOCADDR=ð6, CORRESPONDS TO 3174 PORT ð4 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SQ324Að7 LU LOCADDR=ð7, CORRESPONDS TO 3174 PORT ð5 X
ISTATUS=ACTIVE,LOGAPPL=NRF1Bð7, X
DLOGMOD=SCSPTR
SQ324Að8 LU LOCADDR=ð8, CORRESPONDS TO 3174 PORT ð6 X
ISTATUS=ACTIVE,VPACING=3,LOGAPPL=NRF1Bð8,PACING=3, X
DLOGMOD=SCSTRN

Figure 16-9. System/370 VTAM Tables Defining the 3174 Controller

Chapter 16. Network Routing Facility 16-17

16-18 Remote Work Station Support V4R1
Chapter 17. SNA Primary LU2 Support
This chapter discusses the SNA Primary LU2 Support (SPLS) with the OS/400
licensed program.

SNA Primary LU2 Support—Definition

SNA Primary LU2 Support (SPLS) allows 3270 display stations and 3287 printers
to communicate with AS/400 systems. These devices may be connected to the
AS/400 systems through a Systems Network Architecture (SNA) communication
controller such as the 3720 or 3745. They may also be connected through a 3174
gateway.

For example, a 3481 display connected to a 3174 controller, connected to a 3745

controller, connected to both an ES/9000 system1 and an AS/400 system (see
Figure 17-1).

ES/9000
System

3745
Controller

3174
Controller

AS/400
System

3481
Display
RV3P102-0

Figure 17-1. Configuration Example for Connecting a 3270 Display Station to an AS/400
System.

Another example is a personal computer connected to a 3174 gateway, connected

to an ES/9000 system, connected to another 3174 gateway configured with APPN
support, connected to an AS/400 system. Figure 17-2 on page 17-2 shows this
example.

1 ES/9000 system is used in this chapter to mean any system that can run the required level of the VTAM licensed program.

ES/9000
System

3174
3174 Gateway
Gateway with APPN

AS/400
System
RV3P100-0

Figure 17-2. Example of a 3174 Gateway Configuration for SPLS

The connection can be much more complex, however. The 3270 display station
and the AS/400 system do not need to be connected to the same SNA communi-
cations controller. For example, both of the 3270 display stations and the 3287
printer in Figure 17-3 on page 17-3 may have a session through SPLS with the
AS/400 system shown.

SPLS allows a 3270 display station to have a logical unit (LU) type 2 session with
an AS/400 system. The AS/400 system provides the primary LU (PLU), and the
3270 display station is the secondary LU (SLU). SPLS does not support file transfer
using the IND$FILE program.

SPLS allows a 3287 printer to have an LU type 1 SNA character string (SCS)
session. In this case, the AS/400 system provides the PLU, and the 3287 printer is
the SLU.

SNA Primary LU2 Support Performance—Tips

For general performance considerations regarding AS/400 communications, see the
Communications Management book.

Differentiating SNA Primary LU2 Support from Similar Functions

SPLS function is similar to the Network Routing Facility (NRF). SPLS function is
also similar to the combined function of the Host Command Facility (HCF) and the
distributed host command facility (DHCF). All these functions allow users attached
to an ES/9000 system to access an AS/400 system as if they were 5250 display
station users.

The AS/400 NRF support, however, requires the NRF licensed program to be
installed on the SNA communications controller. SPLS does not require the NRF
licensed program. Furthermore, SPLS does not require the communications con-

17-2 Remote Work Station Support V4R1

troller (3745, for example) processing time that is used by the NRF licensed
program for AS/400 NRF support.

SPLS differs from HCF-DHCF because:

SPLS supports printers.
SPLS does not require that the HCF licensed program be installed on the
ES/9000 host.
SPLS does not require the ES/9000 host-system processing unit time that is
used by the HCF licensed program.

ES/9000 ES/9000
System System

3745
Controller 3745
Controller

3147
Controller

3274
Contorller
AS/400
System

3481 3287
3279 Display Printer
Display RV3P101-0

Figure 17-3. SPLS Configuration Example. The two 3270 display stations and the 3287
printer can connect to the AS/400 system using SPLS.

Benefits of SNA Primary LU2 Support

SPLS enables 3270 users, who are connected to an SNA communications con-
troller, to use any AS/400 system that is connected to the SNA network. This
opens up the world of AS/400 applications to these users. SPLS does this with less
overhead than previous implementations. The NRF licensed program is not
required on the SNA communications controller, and the HCF licensed program is
not required on the ES/9000 system. Only normal host and SNA communications
controller resources are used. (The Virtual Telecommunications Access Method
(VTAM) licensed program uses the host resources. The Network Control Program
(NCP) licensed program uses the SNA communications controller resources.)
VTAM configuration for SPLS is simpler than VTAM configuration for NRF. VTAM
configuration for SPLSis also simpler than VTAM configuration for HCF-DHCF.

Chapter 17. SNA Primary LU2 Support 17-3

Devices Supported by SNA Primary LU2 Support
SPLS supports the following controllers, displays, and printers:
3174 Establishment Controller
3174 Establishment Controller with the Gateway feature:
SNA Primary LU2 Support requires that the 3174 Gateway between the AS/400
system and the VTAM host network is connected to the host network as a
downstream PU in one of the following ways.
– APPN support on 3174 with the following requirements:
- Microcode C3 with patch #AD2F or higher
- AS/400 controller descriptions must be configured with nodetype
*NETNODE and no CP-CP sessions
- Logmode must specify the primary send window and secondary receive
window as equal values. Zero is not an acceptable value.
– The T2.1 Passthru PRQ 8Q0800 on the 3174 controller
– Frame size used for the 3174 Gateway to VTAM connection must be
greater than or equal to the frame size for the connection between the
3174 Gateway and the AS/400 system. This ensures that the request units
(RUs) are not segmented between the 3174 and VTAM.
3274 Control Unit
3270 display stations
All emulators conforming to 3274 Control Unit Model 31C protocol
3287-type printers in LU 1 SCS mode
3720 Communication Controller
3745 Communication Controller

3270 remote attachment function supports the following list of devices. For more
information about the type of support provided, see Chapter 12, “Using 3270
Device Support” on page 12-1.
3174 and 3274 controllers
3270 display stations
Emulators conforming to 3274-31C controller protocol
3287-type printers

SPLS supports 3270 display stations that are capable of displaying double-byte
characters. SPLS supports 3287-type printers that are capable of printing double-
byte characters.

For information on the 5250 optimization support for 3270 display stations, see
“5250 Data Stream Optimization Support” on page 12-1.

17-4 Remote Work Station Support V4R1

Software Requirements for SNA Primary LU2 Support
SPLS requires:
The Advanced Communications Function for the Virtual Telecommunications
Access Method (ACF/VTAM) licensed program. Version 3, Release 4 or later is
recommended.
SPLS supports:
The Network Control Program (NCP) licensed program. Version 5, Release 4 or
later is recommended.

The ACF/VTAM licensed program maintains control of communications between

terminals and application programs.

NCP runs SNA communications controllers such as the IBM 3745, providing con-
troller support for single-domain, multiple-domain, and interconnected network
capabilities.

SNA Primary LU2 Support Sessions

SPLS sessions can be either device-initiated sessions or application-initiated ses-
sions.

The following information describes how a device-initiated session is established:

1. Device-initiated sessions begin with a request to log on to a VTAM applica-
tion. For SPLS, the VTAM application is actually a dependent LU defined for
the connection to the AS/400 system. The logon request is typically from a
3270 display station user. The request can also be from a LOGAPPL operand
configured on a VTAM LU definition statement.
2. The VTAM licensed program sends information about the 3270 display station
or printer to the AS/400 system. This information is sent through a session
between a system services control point (SSCP) and an LU. The LU is a
dependent LU and is represented on the AS/400 system by a display device
description attached to the host controller. This device description has an appli-
cation type of *CTLSSN (control session) and is used only when remote
devices request a session with the AS/400 system.
3. For each logon request, the AS/400 system selects (or in some cases creates)
another device description attached to the host controller. This latter device
description is used for the actual display or printer session, has an application
type of *DEVINIT, and is an independent LU.
4. After selecting the device description with an application type of *DEVINIT, the
system starts the session.

Application-initiated sessions begin when an AS/400 application opens a file

against a 3270 display station or printer. For example, a spool writer may send a
printout to a printer, which causes SPLS to start a session between the spool writer
and the printer. Or an order-entry application may send information to a display
station, which causes SPLS to start a session between the order-entry application
and the display station. The VTAM licensed program is involved in starting the
session, but that is the extent of VTAM's involvement. Application-initiated sessions
require independent device descriptions with an application type of *APPINIT. The

Chapter 17. SNA Primary LU2 Support 17-5

device descriptions must also have all the information needed to start a session to
the remote device.

For both kinds of sessions, data flows between the AS/400 system and the 3270
display station or printer without additional intermediate processing; only normal
SNA intermediate processing is needed. The VTAM licensed program cannot
observe or process the session data. There is no SSCP-to-LU session; the LU is
independent. Once a session is established, SPLS can continue to send and
receive data using the session. It does not matter whether or not the ES/9000 host
continues to be active and available as long as the communications controllers
between the AS/400 system and the 3270 display station are active.

Configuring the AS/400 System for SNA Primary LU2 Support

Before creating the line, controller, and device descriptions for SPLS, you should
decide whether or not to use automatic configuration. The following information
describes what you should consider when making your decision. After the auto-
matic configuration information, there are instructions about how to create the line
description, controller description, and device descriptions.

Automatic Configuration of Devices

You can save time by having the system automatically create display and printer
device descriptions with an application type of *DEVINIT. By using automatic con-
figuration, you do not have to figure out how many device descriptions you need.
You also do not have to figure out how many device descriptions of a particular
device type you need. However, automatic configuration uses system resources
and affects system performance. Nevertheless, you can set up your system to use
automatic configuration initially. Then, manually maintain the configuration there-
after to minimize your efforts while limiting any effects on performance to the initial
period of SPLS use. For details, see “Reducing Automatic Creation Time” on
page 17-7.

To use automatic configuration, specify the following values for the SNA host con-
troller description:
*YES for the APPN-capable (APPN) parameter
*ALL or *DEVINIT for the autocreate device (AUTOCRTDEV) parameter

When the AUTOCRTDEV parameter allows device descriptions with an application

type of *DEVINIT to be automatically created, the system creates those device
descriptions as needed. Specifically, a device description is created only when
there is not an appropriate device description available. If an appropriate device
description exists but is not varied on, the system varies it on automatically.

You may set the AUTOCRTDEV parameter to automatically create device

descriptions. Then, let the system run until enough device descriptions have been
created. After that, turn off automatic creation by changing AUTOCRTDEV to
*NONE. Finally, ensure that the device descriptions (that were automatically
created) are not deleted. To do so, do either of the following:
Change the device descriptions (any manual change to a device description
makes it ineligible for automatic deletion).

17-6 Remote Work Station Support V4R1

Change the autodelete device (AUTODLTDEV) parameter (for the host con-
troller) to *NO.
Note: The AUTOCRTDEV(*NONE) parameter does not affect the automatic cre-
ation of APPC devices when the APPN parameter is set to *YES. However,
the AUTODLTDEV(*NONE) parameter affects both *DEVINIT and APPC
device descriptions.

When the system automatically creates a device description with an application

type of *DEVINIT, the system copies some of the values for the device description.
The system copies the values from the associated display device description that
has an application type of *CTLSSN. The system copies the following parameters:
Keyboard language type (KBDTYPE)
DBCS feature (IGCFEAT)
Attached controller name (CTL)

When a device description with an application type of *DEVINIT is automatically

created, it is created with ONLINE(*NO). If AUTOCRTDEV is *NONE, the system
does not automatically vary on device descriptions with an application type of
*DEVINIT as they are needed. Therefore, if autodevice creation is not set on, you
must ensure that the right number of device descriptions are varied on. You can do
this by changing the device descriptions to ONLINE(*YES) or by manually varying
on the device descriptions.

Reducing Automatic Creation Time

The most obvious way to reduce the amount of resources used to create device
descriptions automatically is to minimize the need for automatic creation. You can
do this using one or more of the following methods:
Manually, create enough display or printer device descriptions with an applica-
tion type of *DEVINIT.
Let the system automatically create device descriptions with application type
*DEVINIT until the number of device descriptions equals the number of ses-
sions to be used. Then, use the Change Device Description (Display)
(CHGDEVDSP) command or the Change Device Description (Printer)
(CHGDEVPRT) command to change the device descriptions. (For example,
change the text description.) Changing the device descriptions makes them
ineligible for automatic deletion.
Set the AUTODLTDEV parameter on the host controller description to a high
number or to *NO. This prevents the system from deleting
APPTYPE(*DEVINIT) device descriptions that will need to be re-created. This
also prevents the system from deleting APPC device descriptions that are both
automatically created and are APPN capable (a side effect you may or may not
want).
If you set the AUTODLTDEV parameter to a high number, make sure it is high
enough to cover normal periods of inactivity. When the host controller is varied
on, the timer starts for all device descriptions that are eligible for automatic
deletion. The timer is canceled for a device description when that device
description is used for a session and is restarted when the session ends. You
may need to set the AUTODLTDEV parameter to around 6000 to keep device
descriptions from being deleted over a 3-day weekend. You may need to set it
even higher. The AUTODLTDEV parameter needs to be high enough to

Chapter 17. SNA Primary LU2 Support 17-7

prevent the deletion of device descriptions that you do not want deleted.
Therefore, it needs to cover periods when the host controller description is
varied on and device descriptions that you do not want deleted are inactive.

Another way to reduce the amount of resources used for the automatic creation of
device descriptions is to avoid name conflicts. If you have more than one display
device description with an application type of *CTLSSN, use names that are unique
for the first 7 characters to reduce the amount of time the system checks for con-
flicting names.

Configuration Steps for SNA Primary LU2 Support

To configure the AS/400 system to communicate with SPLS, perform these steps:
1. Configure a line description to the ES/9000 host network (described in “Step 1:
Configuring the Line to the Host Network”).
2. Configure a host controller description (described in “Step 2: Configuring the
Host Controller” on page 17-9).
3. Configure display device descriptions or printer device descriptions (described
in “Step 3: Configuring the Device” on page 17-11).
4. Configure the host system (described in Figure 17-6 on page 17-12).
Note: SPLS can share the line and controller descriptions with other AS/400 com-
munications functions that have the same line and controller requirements,
provided those functions can also share the line. For example, SPLS can
share line and controller descriptions with devices configured for NRF, SNA
upline facility (SNUF), DHCF, and advanced program-to-program communi-
cations (APPC). Therefore, you may have already configured the line and
controller descriptions.

For additional information about how to configure lines, controllers, and devices,
refer to the Communications Configuration.

Step 1: Configuring the Line to the Host Network

Use one of the following Create Line Description (CRTLINxxx) commands to con-
figure a line to the host system that supports an SNA host controller:
Create Line Description (SDLC) (CRTLINSDLC)
Create Line Description (Token-Ring) (CRTLINTRN)
Create Line Description (Ethernet) (CRTLINETH)
Create Line Description (DDI) (CRTLINDDI)
Create Line Description (Frame relay) (CRTLINFR)
Create Line Description (X.25) (CRTLINX25)

This step may already have been performed if the AS/400system has been commu-
nicating with the ES/9000 host for such functions as 3270 emulation, HCF-DHCF,
or NRF.
Note: If using a frame relay network, a network interface description is also
required along with the line description, the controller description, and the
device description.

17-8 Remote Work Station Support V4R1

Step 1: Configuring the Line to the Host Network is an example of an SDLC line
configured to communicate with the ES/9000 host to support SPLS. This example
uses HOSTLINE as the name of the line description and LIN012 as the resource
name.

à ð
Create Line Desc (SDLC) (CRTLINSDLC)

Type choices, press Enter.

Line description . . . . . . . . > HOSTLINE__ Name

Resource names . . . . . . . . . > LINð12____ Name
+ for more values __________
Online at IPL . . . . . . . . . > \NO \YES, \NO
Data link role . . . . . . . . . > \SEC \NEG, \PRI, \SEC
Physical interface . . . . . . . \RS232V24 \RS232V24, \V35, \X21, ...
Connection type . . . . . . . . \NONSWTPP \NONSWTPP, \SWTPP, \MP, \SHM
Switched network backup . . . . \NO \NO, \YES
Exchange identifier . . . . . . \SYSGEN ð56ððððð-ð56FFFFF, \SYSGEN
NRZI data encoding . . . . . . . \YES \YES, \NO
Line speed . . . . . . . . . . . 96ðð 6ðð, 12ðð, 24ðð, 48ðð...
Modem type supported . . . . . . \NORMAL \NORMAL, \V54, \IBMWRAP...
Maximum frame size . . . . . . . 521 265, 521, 1ð33, 2ð57
Duplex . . . . . . . . . . . . . \HALF \HALF, \FULL
Inactivity timer . . . . . . . . 3ðð \NOMAX, 15ð-42ðð (ð.1 sec)
Poll response delay . . . . . . ð ð-2ð48 (ð.ððð1 seconds)
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 17-4. Configuring the Line to the ES/9000 Host Network

Step 2: Configuring the Host Controller

Use the Create Controller Description (SNA Host) (CRTCTLHOST) command to
create the controller description. Again, this may already have been done if the
AS/400 system has been communicating with the ES/9000 host for such functions
as 3270 emulation, HCF-DHCF, or NRF.

“Step 2: Configuring the Host Controller” is an example of a host controller

description that supports SPLS. Note that the attached nonswitched line parameter
specifies the line description (HOSTLINE) that was created in “Step 1: Configuring
the Line to the Host Network” on page 17-8. This example uses HOSTCTL as the
name of the controller description and *SDLC as the link type, which indicates the
line is an SDLC line.

Chapter 17. SNA Primary LU2 Support 17-9

à ð
Create Ctl Desc (SNA Host) (CRTCTLHOST)

Type choices, press Enter.

Controller description . . . . . > HOSTCTL___ Name

Link type . . . . . . . . . . . > \SDLC \IDLC, \FR, \LAN, \SDLC, \X25
Online at IPL . . . . . . . . . > \NO \YES, \NO
Switched connection . . . . . . \NO \NO, \YES
Switched network backup . . . . \NO \NO, \YES
APPN-capable . . . . . . . . . . \YES.1/ \YES, \NO
Attached nonswitched line . . . > HOSTLINE Name
Maximum frame size . . . . . . . \LINKTYPE 265-16393, 256, 265, 512...
Remote network identifier . . . \NETATR.2/ Name, \NETATR, \NONE, \ANY
Remote control point . . . . . . > NVFY1.2/ Name, \ANY
SSCP identifier . . . . . . . . ____________ ð5ðððððððððð-ð5FFFFFFFFFF
Local exchange identifier . . . \LIND ð56ððððð-ð56FFFFF, \LIND
Station address . . . . . . . . > C1 ð1-FE
APPN CP session support . . . . \YES \YES, \NO
APPN node type . . . . . . . . . > \LENNODE.3/ \ENDNODE, \LENNODE...
APPN transmission group number 1.4/ 1-2ð, \CALC
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
à ð
Create Ctl Desc (SNA Host) (CRTCTLHOST)

Type choices, press Enter.

APPN minimum switched status . . \VRYONPND \VRYONPND, \VRYON

Autocreate device . . . . . . . \ALL.5/ \ALL, \DEVINIT, \NONE
Autodelete device . . . . . . . > 6ððð 1-1ðððð, 144ð, \NO
User-defined 1 . . . . . . . . . \LIND ð-255, \LIND
User-defined 2 . . . . . . . . . \LIND ð-255, \LIND
User-defined 3 . . . . . . . . . \LIND ð-255, \LIND
Recontact on vary off . . . . . \YES \YES, \NO
Text 'description' . . . . . . . > 'SPLS host controller'_____________________
____________

Figure 17-5. Configuring the Host Controller to Support SPLS

.1/ APPN-capable: May be either YES or NO.

When APPN-capable is *NO, device descriptions are not created auto-
matically.
.2/ Remote network identifier and remote control point: Specify values such
that these two parameters uniquely identify this controller.
SNA requires that the remote network identifier, remote control point,
and APPN transmission group number form a unique identifier. VTAM
Version 3 Release 4 only supports one transmission group number. For
pre-VTAM Version 4 Release 1, the transmission group number for all
host controller descriptions must have the same transmission group
number. Therefore, the remote network identifier and remote control
point must be a unique combination.
The remote network identifier and remote control point do not have to
match the host network identifier and control point name. This is
because the remote network identifier and remote control point are not
verified against the values the host sends on an XID exchange. The

17-10 Remote Work Station Support V4R1

controller description must have an APPN node type of *LENNODE to
ensure these values are not verified.
.3/ APPN node type: Specify *LENNODE.
.4/ APPN transmission group number: For pre-VTAM Version 4 Release 1,
the same value as all other host controllers connected to the same host.
.5/ Autocreate device: To have the system automatically create (as needed)
display and printer device descriptions with an application type of
*DEVINIT, specify *ALL or *DEVINIT. APPN-capable must be *YES for
the system to automatically create these device descriptions. To require
manual creation of device descriptions with an application type of
*DEVINIT, specify *NONE.
For more information about automatic creation of device descriptions,
see “Automatic Configuration of Devices” on page 17-6.

Step 3: Configuring the Device

If you create device descriptions with an application type of *DEVINIT, you must
also create a display device description with an application type of *CTLSSN. If you
do not create devices with an application type of *DEVINIT, you do not need a
device description with an application type of *CTLSSN.

To configure a 3270-type display, use the Create Device Description (Display)

(CRTDEVDSP) command. To configure a 3287-type printer, use the Create Device
Description (Printer) (CRTDEVPRT) command. On the CRTDEVDSP or
CRTDEVPRT display, enter the device description name, the device class (*RMT
value), the 327x device type, and the device model. You also need to specify the
application type (APPTYPE) parameter.

Generally, the APPTYPE parameter is *DEVINIT for displays and *APPINIT for
printers. You can, however, specify *APPINIT for a display if an application starts
the session with the display. Similarly, you can specify *DEVINIT for a printer if the
printer starts the session. The printer may start the session using the LOGAPPL
operand on the VTAM printer definition.

For information about configuring the DBCS feature (IGCFEAT) parameter, see
Table 13-1 on page 13-11.

Configuring a Display with an Application Type Parameter of *CTLSSN: A

display device description with an application type of *CTLSSN is used only while a
device-initiated session is being started. It is used for control and does not repre-
sent a physical display. It is configured as a display, however, because it is associ-
ated with device descriptions that have an application type of *DEVINIT, which
typically are displays.

Figure 17-6 on page 17-12 shows a configuration for a display with an application
type of *CTLSSN.

Chapter 17. SNA Primary LU2 Support 17-11

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > R4ð82Að.1/ Name

Device class . . . . . . . . . . > \RMT.2/ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3279.3/ 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð.4/ ð, 1, 2, 4, 5, 12, 23...
Local location address . . . . . > ð9.5/ ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > HOSTCTL.6/ Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, ALI...
Drop line at signoff . . . . . . > \NO \YES, \NO
Application type . . . . . . . . > \CTLSSN.7/ \NONE, \NRF, \CTLSSN...
Inactivity timer . . . . . . . . \ATTACH 1-3ð, \ATTACH, \NOMAX...
Local location . . . . . . . . . \NETATR.8/ Name, \NETATR
Text 'description' . . . . . . . > 'SPLS control session display'
_________________

Figure 17-6. Configuring a Display with an Application Type of *CTLSSN

.1/ Device description: Use the name of this dependent LU as it is defined

to VTAM (suggestion).
The first 7 characters of this name are the first 7 characters of the
names of any device descriptions that the AS/400 system automatically
creates for sessions that come in to this LU. Because the automatically
created device descriptions have an application type of *DEVINIT, it
would be confusing if they were named CTLSSNððð, CTLSSNðð1, and so
forth. Therefore, you should not use CTLSSN or any variation of control
session as the name of a device description with an application type of
*CTLSSN.
Similarly, the automatically created device descriptions may be a mixture
of 3277, 3278, 3279, and 3287 devices. Hence, it would be confusing if
they were named DEV3279, DEV3279ððð, DEV3279ðð1, and so forth. There-
fore, you should not include a device type in the name.
.2/ Device class: Must be *RMT.
.3/ Device type: May be 3277, 3278, or 3279.
.4/ Device model: May be 0 or (only if the device type is 3278) 4.
.5/ Local location address: Must be nonzero. The local location address cor-
responds to a dependent VTAM LU. The user logs on to this LU but is
connected to a different LU. See Figure 17-10 on page 17-23 for an
example of how the dependent VTAM LU can be defined.
.6/ Attached controller: The name of the SNA host controller description. In
this case, the controller description is HOSTCTL, which was created in
“Step 2: Configuring the Host Controller” on page 17-9.
.7/ Application type: Must be *CTLSSN.
.8/ Local location: Normally, you can specify *NETATR. However, if you
have multiple host lines, you should use explicit local location names
and definitely make the local location names unique.
The local location name is the name of the independent VTAM LU in the
SNA communications controller. The user is bound to this LU. See

17-12 Remote Work Station Support V4R1

Figure 17-10 on page 17-23 for an example of how the independent
VTAM LU can be defined.
The system does not display a message if you type the wrong local
location name.

Notes:
1. A host controller must have a display device description with application type
*CTLSSN if it has device descriptions with application type *DEVINIT.
2. When a physical display or printer starts a session, SPLS looks for a device
description with an application type of *DEVINIT to use for the session. SPLS
selects the device description based on its device type and model. Table 17-1
shows how SPLS selects the device type and model. In summary, SPLS
selects the device type and model based on the following values, which are
listed in priority order:
a. The device type and model of the display device description with an appli-
cation type of *CTLSSN to which the control initiate (CINIT) request came
b. The requested screen size
c. The value of the extended data stream supported bit (byte 2, bit 0) in the
PSERVIC parameter of the bind image in the CINIT request.
After SPLS selects the device type and model, it looks for an available, existing
device description with that device type and model. If that search fails, SPLS
attempts to automatically create the device description. If the automatic creation
is not allowed or fails, SPLS degrades the requested device type and model
(until the device type is 3277) and repeats the search until it either succeeds or
fails altogether. The following list shows the device types and models starting
with the most capable and ending with the least capable:
3279 or 3278 Model 4
3278 Model 0
3277
When SPLS must degrade the device type and model, it uses the preceding
list. For example, if a device description with a device type of 3279 is not avail-
able and cannot be automatically created, SPLS tries to find an available
device description with a device type of 3278 and a model of 0. If that fails,
SPLS moves down to a 3277.

Chapter 17. SNA Primary LU2 Support 17-13

| Table 17-1. Device Type and Model Selection
| Device Type Selected Device Type and Model
| and Model of
| Extended Data Stream Bit ON Extended Data Stream Bit OFF
| Display with
| APPTYPE Query Not Query
| *CTLSSN Not 43x80 43x80 27x132 Display2 43x80 43x80 27x132 Display2
| 3277 3277 3277 3277 3277 3277 3277 3277 3277
| 3278-0 3278-0 3278-4 3278-5 3278-5 3277 3278-4 3278-5 3277
| 3278-4 3278-41 3278-4 3278-5 3278-4 3277 3278-4 3278-5 3277
| 3278-5 3278-5 3278-4 3278-5 3278-5 3277 3278-4 3278-5 3277
| 3279 3279 3278-4 3279-5 3279-5 3277 3278-4 3279-5 3277
| 3279-5 3279-5 3278-4 3279-5 3279-5 3277 3278-4 3279-5 3277
| Note:
| 1 Even though a device type and model of 3278 Model 4 is selected, the primary screen size for the
| session is set to 24 by 80. If the PSERVIC parameter of the bind image in the CINIT request indicates that
| the device should be queried to find the alternate screen size, the alternate screen size for the session is
| set to 43 by 80. This is indicated when byte 10 of the PSERVIC parameter is X'03' (the byte numbers
| begin at zero). The PSERVIC parameter of the bind image in the CINIT request is set by the PSERVIC
| operand of the MODEENT macroinstruction. For more information about the PSERVIC operand, see the
| VTAM Resource Definition Reference.
| 2If byte 10 of PSERVIC parameter of BIND image is set to hex 03, and device description is 3278-5 or
| 3279-5, a query request will be sent to the display. The query reply will be available for the application use
| when binding the datastream.

Configuring a Display with an Application Type Parameter of *DEVINIT: “Step

3: Configuring the Device” on page 17-11 shows a configuration for a 3279 display
with an application type of *DEVINIT.

| à ð
| Create Device Desc (Display) (CRTDEVDSP)

| Type choices, press Enter.

| Device description . . . . . . . > DSPð2 Name

| Device class . . . . . . . . . . > \RMT.1/ \LCL, \RMT, \VRT, \SNPT
| Device type . . . . . . . . . . > 3279.2/ 31ð1, 3151, 3161, 3162...
| Device model . . . . . . . . . . > ð.3/ ð, 1, 2, 4, 5, 12, 23...
| Local location address . . . . . > ðð.4/ ðð-FE
| Online at IPL . . . . . . . . . > \NO \YES, \NO
| Attached controller . . . . . . > HOSTCTL.5/ Name
| Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, ALI...
| Drop line at signoff . . . . . . > \NO.6/ \YES, \NO
| Application type . . . . . . . . > \DEVINIT.7/ \NONE, \NRF, \CTLSSN...
| Inactivity timer . . . . . . . . \ATTACH.8/ 1-3ð, \ATTACH, \NOMAX...
| Text 'description' . . . . . . . > '3279 display device for using SPLS'
| _________________

Figure 17-7. Configuring a Display with an Application Type of *DEVINIT

.1/ Device class: Must be *RMT.

.2/ Device type: May be 3277, 3278, or 3279.
.3/ Device model: May be 0 or (only if the device type is 3278) 4.

17-14 Remote Work Station Support V4R1

.4/ Local location address: Must be 0 to indicate that this device is associ-
ated with an independent PLU.
.5/ Attached controller: The name of the SNA host controller description. In
this case, the controller description is HOSTCTL, which was created in
“Step 2: Configuring the Host Controller” on page 17-9.
.6/ Drop line at signoff: If you have a switched connection, specify *NO. For
switched and SPLS connections, the line should not be dropped
because sessions are started by a request that must come across the
line from the device.
.7/ Application type: Specify *DEVINIT.
.8/ Inactivity timer: The default value, *ATTACH, is suitable most of the
time.

Notes:
1. The following values for display device descriptions with an application type of
*DEVINIT are set by the system when the device description is in use. They
cannot be changed. To see these values, use the Display Device Description
(DSPDEVD) command or the Retrieve Device Description (QDCRDEVD) appli-
cation program interface (API). Use the DSPDEVD command or the
QDCRDEVD API when the device description is in use. For more information
about the QDCRDEVD API, see the System API Reference book.
Remote location The VTAM/NCP name of the 3277, 3278, or 3279 display.
Remote network identifier The VTAM/NCP network identifier. If the 3270
display is on the same network as the AS/400 system, the remote
network identifier may be *NONE.
Local location The name of the independent LU in the SNA communications
controller.
Control session device description The name of theisplay device description
with an application type of *CTLSSN that is associated with this
device for the current session
Associated printer The SLU name of the primary printer associated with this
3270 display station. A remote network identifier is also displayed for
this printer. The associated printer information is shown if it is
received on the CINIT request. In some cases, VTAM does not
resolve the remote network identifier to the name of the network that
has the printer LU definition. If you know the printer and display are
in the same network, use the display's remote network identifier to
configure an appropriate printer device description.
Alternate printer The SLU name of the alternate printer that is associated with
this 3270 display station. A remote network identifier is also dis-
played for this printer. The alternate printer information is shown if it
is received on the CINIT request. In some cases, VTAM does not
resolve the remote network identifier to the name of the network that
has the printer LU definition. If you know the printer and display are
in the same network, use the display's remote network identifier to
configure an appropriate printer device description.

Chapter 17. SNA Primary LU2 Support 17-15

2. When in use, all device descriptions with an application type of *DEVINIT are
associated with a display device description with an application type of
*CTLSSN.
3. If the system automatically creates a device description with an application type
of *DEVINIT, the value of the online at IPL (ONLINE) parameter is *NO.

Configuring a Display with an Application Type Parameter of *APPINIT: Con-

figuring display device descriptions with an application type of *APPINIT is not
recommended.

To successfully use a display device description with an application type of

*APPINIT, you must understand how to control displays using an application
program. For example, the device description should not be held by a subsystem,
or there will be no way to end the SPLS session. An application must start the
session with the display. VTAM does not inform the AS/400 system when the
display becomes available.

Use the CRTDEVDSP command to create the display device description with an
application type of *APPINIT. The key considerations are:
Device class: Must be *RMT.
Device type: May be 3277, 3278, or 3279.
Device model: May be 0 or (only if the device type is 3278) 4.
Local location address: Must be 0 to indicate that this device is associated with
an independent primary logical unit (PLU).
Application type: Specify *APPINIT.
Inactivity timer: The default value, *ATTACH, is suitable most of the time.
Remote location: Must be specified and should be unique. This is the name of
the LU in the network with which the AS/400 application communicates.
Local location: Normally, you can specify *NETATR. However, if you have mul-
tiple host lines, you should use explicit local location names, and definitely
make them unique.
The local location name is the name of the independent VTAM LU in the SNA
communications controller. The user is bound to this LU. See Figure 17-10 on
page 17-23 for an example of how the independent VTAM LU can be defined.

Notes:
1. The system does not automatically create device descriptions that have an
application type of *APPINIT.
2. Display device descriptions with an application type of *APPINIT do not use or
require a display device description with an application type of *CTLSSN.

Configuring a Printer with an Application Type Parameter of *APPINIT:

Figure 17-8 on page 17-17 shows a configuration for a printer device description
with an application type of *APPINIT.

17-16 Remote Work Station Support V4R1

à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

Device description . . . . . . . > APð2 Name

Device class . . . . . . . . . . > \RMT.1/ \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3287.2/ 3287, 3812, 4ð19, 42ð1...
Device model . . . . . . . . . . > ð.3/ ð, 1, 2, 3, 4, 1ð, 13, 3ð1...
Local location address . . . . . > ðð.4/ ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > HOSTCTL.5/ Name
Separator program . . . . . . . \NONE Name, \NONE
Library . . . . . . . . . . . _________ Name, \LIBL, \CURLIB
Printer error message . . . . . \INQ \INQ, \INFO
Message queue . . . . . . . . . QSYSOPR Name, QSYSOPR
Library . . . . . . . . . . . \LIBL Name, \LIBL, \CURLIB
Application type . . . . . . . . > \APPINIT.6/ \NONE, \NRF, \DEVINIT...
Inactivity timer . . . . . . . . > \SEC15.7/ 1-3ð, \ATTACH, \NOMAX...
Remote location . . . . . . . . > SQ324Að7.8/ Name
Local location . . . . . . . . . \NETATR.9/ Name, \NETATR
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 17-8. Configuring a Printer with an Application Type of *APPINIT

à ð
Create Device Desc (Printer) (CRTDEVPRT)

Type choices, press Enter.

Remote network identifier . . . . : \NETATR

Text . . . . . . . . . . . . . . . : \BLANK

.1/ Device class: Must be *RMT.

.2/ Device type: Must be 3287.
.3/ Device model: Must be 0.
.4/ Local location address: Must be 0 to indicate that this device is associ-
ated with an independent primary logical unit (PLU).
.5/ Attached controller: The name of the SNA host controller description. In
this case, the controller description HOSTCTL created in “Step 2: Con-
figuring the Host Controller” on page 17-9.
.6/ Application type: Must be *APPINIT.
.7/ Inactivity timer: Specify *SEC15. This allows the system to end the
session with the printer 15 seconds after the application's job has been
printed. (If the application sends another job to this printer within 15
seconds, the system does not end the session.) This allows various
applications on different systems around the network to share this
printer.

Chapter 17. SNA Primary LU2 Support 17-17

.8/ Remote location: Must be specified and should be unique. This is the
name of the LU in the network with which the AS/400 application com-
municates. See Figure 17-12 on page 17-26 for an example of how the
corresponding LU can be defined. If the remote location that you are
defining is for a VTAM printer, this remote location is the name of the
LU that VTAM uses to define the physical printer.
.9/ Local location: Normally, you can specify *NETATR. However, if you
have multiple host lines, you should use explicit local location names,
and you will probably want to make them unique. If your host lines
connect into separate networks, you definitely should make the local
location names unique.
The local location name is the name of the independent VTAM LU in the
SNA communications controller. The user is bound to this LU. See
Figure 17-10 on page 17-23 for an example of how the independent
VTAM LU can be defined.

Notes:
1. The system does not automatically create device descriptions that have an
application type of *APPINIT.
2. Device descriptions with an application type of *APPINIT do not use or require
a display device description with an application type of *CTLSSN.

Configuring a Printer with an Application Type Parameter of *DEVINIT: Con-

figuring printer device descriptions with an application type of *DEVINIT is unusual.
Printers with an application type of *DEVINIT should be dedicated to the AS/400
system to which they are logged on.

The easiest way to configure a printer device description with an application type of
*DEVINIT is to let the system configure it for you. See “Automatic Configuration of
Devices” on page 17-6 for information about automatic creation of device
descriptions with an application type of *DEVINIT. The following information may be
helpful if (for performance or other reasons) you choose to configure the device
description yourself.

The printer must start the session when the printer device description has an appli-
cation type of *DEVINIT. Using the LOGAPPL operand on the VTAM printer defi-
nition is one way the printer can start the session.

Use the CRTDEVPRT command to create the printer device description with an
application type of *DEVINIT. The key considerations are:
Device class: Must be *RMT.
Device type: Must be 3287.
Device model: Must be 0.
Local location address: Must be 0 to indicate that this device is associated with
an independent PLU.
Application type: Specify *DEVINIT.
Inactivity timer: The default value, *ATTACH, is suitable most of the time. For
printer device descriptions with an application type of *DEVINIT, *ATTACH
maps to *NOMAX. Therefore, the session between the AS/400 system and the
printer stays up regardless of its activity.

17-18 Remote Work Station Support V4R1

Notes:
1. The following values for printer device descriptions with an application type of
*DEVINIT are set by the system when the device description is in use. They
cannot be changed. To see these values, use the Display Device Description
(DSPDEVD) command or the Retrieve Device Description (QDCRDEVD) appli-
cation program interface (API). Use the DSPDEVD command or the
QDCRDEVD API when the device description is in use. For more information
about the QDCRDEVD API, see the System API Reference book.
Remote location The VTAM/NCP name of the 3287 printer.
Remote network identifier The VTAM/NCP network identifier. If the 3287
printer is on the same network as the AS/400 system, the remote
network identifier may be *NONE.
Local location The name of the independent LU in the SNA communications
controller.
Control session device description The name of the display device
description with an application type of *CTLSSN that is associated
with this device for the current session.
2. When in use, all device descriptions with an application type of *DEVINIT are
associated with display device descriptions with an application type of
*CTLSSN.
3. If the system automatically creates a device description with an application type
of *DEVINIT, the value of the online at IPL (ONLINE) parameter is *NO.

Step 4: Configuring the Host System

Only one independent LU definition is necessary in VTAM or NCP on the physical
unit (PU) for the AS/400 system. This independent LU can support many AS/400
independent device descriptions for LU 1 and LU 2 sessions. A dependent LU defi-
nition is also needed in VTAM or NCP for device-initiated sessions. This
dependent LU definition must match the AS/400 device description with an applica-
tion type of *CTLSSN. Up to 253 display and printer sessions may be established
across a subarea network using the following LU definitions.
One VTAM or NCP predefined dependent LU (for the device-initiated sessions)
One independent LU

A cross-domain resource (CDRSC) definition statement for the independent LU

must exist in both the source and target VTAM definitions (if there are multiple
domains). The CDRSC definition statement can be created dynamically by VTAM
or explicitly by the VTAM system programmer.

For information about how to configure the ES/9000 host to support dependent and
independent LUs, refer to the ES/9000 documentation. For example, for information
about VTAM definitions, see the VTAM Resource Definition Reference. For informa-
tion about NCP definitions, see the NCP, SSP, EP Resource Definition Reference
and the NCP, SSP, EP Resource Definition Guide. For some examples that may
help you, see “Examples of VTAM Logon Mode Tables and Definitions” on
page 17-21, “Matching Parameters for an SDLC Line” on page 17-26, and
“Matching Parameters for a Token-Ring Line” on page 17-27.

Chapter 17. SNA Primary LU2 Support 17-19

Starting SNA Primary LU2 Support Sessions
Users who want to access an AS/400 system can do so using VTAM and SPLS by
sending an unformatted system services (USS) request to the VTAM SSCP in the
form of a logon string.

The logon string consists of the following parts:

Application Identifier (APPLID)

Specifies the requested application. In this case, the APPLID is the name of the
dependent LU for the AS/400 system. The dependent LU has a matching
display device description with an application type of *CTLSSN.

SNA Logon Mode (LOGMODE)

Determines the session parameters to be used during the LU-to-LU session
and is defined in a USS table for the VTAM licensed program. You can use the
default value for this operand.

Data Operand (DATA)

SPLS currently ignores this operand.

Associated Printer (PRINTER1)

Indicates the name of the printer associated with the 3270 display station.

Alternate Printer (PRINTER2)

Indicates the name of the alternate printer for the 3270 display station.

An example of a full logon string written in PL/I could look like this:
LOGON APPLID(R4ð82Að9) LOGMODE(SD82HD) PRINTER1(PRT1) PRINTER2(PRT2)

The application identifier (APPLID) is named R4082A09. The SNA logon mode is
labeled SD82HD. The name of the associated printer is PRT1. The name of the
alternate printer is PRT2.

You can set up USS tables to supply defaults for all of the parameters except
APPLID. For more information about the LOGON command and USS tables, see
the VTAM Resource Definition Reference.

3270 Device Support

For information on AS/400 support for 3270 devices, see Chapter 12, “Using 3270
Device Support” on page 12-1.

Customizing Your SNA 3270 Display Keyboard Map

SPLS has the same considerations as other AS/400 3270 support for mapping a
3270 display station keyboard to a 5250 display station keyboard. For instructions
on customizing your keyboard, see “3270-to-5250 Keyboard Mapping” on
page 12-13.

17-20 Remote Work Station Support V4R1

AS/400 Work Station Printing
SPLS has the same considerations for remote 3270 work station printers as NRF.
See “AS/400 Work Station Printing” on page 16-9.

Creating a Printer Device Description for the Associated Printer

You can use the Create Printer for SPLS (TNXCRTPT) tool in the QUSRTOOL
library to create printer device descriptions for the associated and alternate printers.
Note: These printer device descriptions will not be automatically deleted after the
session has ended.

Ending SNA Primary LU2 Support Sessions

You may use either of the following two methods to end SPLS:
1. Use the ENDCNN parameter of the Sign Off (SIGNOFF) command to sign off
the AS/400 system and end the session between your 3270 display station and
the AS/400 system. For example, type:
SIGNOFF ENDCNN(\YES)

and press the Enter key.

2. Do the following:
a. Sign off the AS/400 system using the Sign Off (SIGNOFF) command.
b. Press the 3270 system request key.
c. Log off from the application using the LOGOFF command, which is a
VTAM command.

If you sign off the system while using SPLS without ending your SPLS session, the
session remains bound even after you sign off. This prevents other users from
using the system and network resources used by this session.

Examples of VTAM Logon Mode Tables and Definitions

This topic contains samples of ES/9000 VTAM logon mode (logmode) tables, and
AS/400 system and NCP definitions. These tables are configured on the ES/9000
host to allow the LU-to-LU connections necessary for SPLS operation.

Notes:
1. The VTAM that owns the SLU uses the Logon entry from the Logon Mode table
defined for the SLU to build the BIND image in the CINIT received by SPLS.
2. SPLS uses this BIND image to build the BIND operation that is sent to the
SLU.
3. The VTAM that owns the ILU verifies the BIND image against the Logon entry
having the same name in the Logon Mode table defined for the ILU. If the
logon mode entries contain incompatible values, this can cause the BIND oper-
ation to be unsuccessful.

Chapter 17. SNA Primary LU2 Support 17-21

Logon Mode Tables
The following figure contains sample VTAM logon mode tables. These tables are
used to define the characteristics of the session established between the 3270 dis-
plays and the AS/400 system. For these characteristics, see the Table 17-1 on
page 17-14.
Note: The 3277 model 1 is the only device type and model that can be selected
for logon mode (SD82HD) because the PSERVIC parameter does not
specify extended attributes.

SD82 MODETAB
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ LOGMODE PAIR FOR 24 X 8ð TERMINAL -- PACING = ð, 256 BYTE RU \
\ NO EXTENDED ATTRIBUTES
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SD82HD MODEENT LOGMODE=SD82HD,
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ðð', BYTE ð8
SRCVPAC=X'ðð', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð2ðððððððððð185ð185ð7Fðð', BYTE 14-25
RUSIZES=X'8585' BYTE 1ð - 11
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ LOGMODE PAIR FOR 24 X 8ð TERMINAL -- PACING = ð, 256ð BYTE RU \
\ WITH EXTENDED ATTRIBUTES
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
TRNHDð MODEENT LOGMODE=TRNHDð,
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'Bð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ðð', BYTE ð8
SRCVPAC=X'ðð', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð28ðððððððððððððððððð2ðð', BYTE 14-25
RUSIZES=X'A8A8'
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ LOGMODE PAIR FOR 24 X 8ð TERMINAL -- PACING = 7, 512 BYTE RU \
\ WITH EXTENDED ATTRIBUTES
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
TRNHD7 MODEENT LOGMODE=TRNHD7,
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'Bð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ð7', BYTE ð8
SRCVPAC=X'ð7', BYTE ð9
PSNDPAC=X'ðð', BYTE 12
PSERVIC=X'ð28ðððððððððððððððððð2ðð', BYTE 14-25
RUSIZES=X'8686' BYTE 1ð - 11

Figure 17-9 (Part 1 of 2). Sample ES/9000 VTAM Logon Mode Tables

17-22 Remote Work Station Support V4R1

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ \
\ LOGMODE PAIR FOR 328X PRINTER -- PACING = 1 (MINIMUM VALUE) \
\ 256 BYTE RU \
\ \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SCSPTRR MODEENT LOGMODE=SCSPTRR,
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ð1', BYTE ð8
SRCVPAC=X'ð1', BYTE ð9
PSERVIC=X'ð1ððððððE1ðððððððððððððð', BYTE 14-25
PSNDPAC=X'ð1', BYTE 11
RUSIZES=X'8585'
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ \
\ LOGMODE PAIR FOR 328X PRINTER -- PACING = 3, 512 BYTE RU \
\ \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SCSTRNR MODEENT LOGMODE=SCSTRNR,
FMPROF=X'ð3', BYTE ð2
TSPROF=X'ð3', BYTE ð3
PRIPROT=X'B1', BYTE ð4
SECPROT=X'9ð', BYTE ð5
COMPROT=X'3ð81', BYTE ð6 - ð7
SSNDPAC=X'ð3', BYTE ð8
SRCVPAC=X'ð3', BYTE ð9
PSERVIC=X'ð1ððððððE1ðððððððððððððð', BYTE 14-25
PSNDPAC=X'ð3', BYTE 11
RUSIZES=X'8686'

Figure 17-9 (Part 2 of 2). Sample ES/9000 VTAM Logon Mode Tables

Network Control Program Definitions

A logon mode table is used by VTAM for session parameters for the sessions
established through this physical unit. The MODETAB parameter can be specified
to name a specific logon mode table or the default table is used. For information on
how to specify the parameter and how VTAM uses the table and entries for session
initiation and verification. For more information about how to define the logon mode
parameter, see the VTAM Resource Definition Reference.

The following figure defines an SDLC connection on the SNA communications con-
troller to the host system:

\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ AS/4ðð USING SDLC LINE TO CONNECT TO AS/4ðð SPLS \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
R4ð82 LINE ADDRESS=(ð82,HALF),ETRATIO=25ð,ISTATUS=INACTIVE,RETRIES=(\
ð7,ð5,ð3),SPEED=96ðð,MAXDATA=521,OWNER=MVS,PACING=ð,VPAC\
ING=ð
SERVICE ORDER=(R4ð82A,R4ð82B)

Figure 17-10 (Part 1 of 2). ES/9000 VTAM Tables Defining NCP on the SNA Communi-
cation Controller

Chapter 17. SNA Primary LU2 Support 17-23

R4ð82A PU ADDR=C1,ISTATUS=INACTIVE,XID=YES,NETID=RPC
R4ð82Að1 LU LOCADDR=ð1,ISTATUS=INACTIVE
R4ð82Að2 LU LOCADDR=ð2,ISTATUS=INACTIVE
R4ð82Að3 LU LOCADDR=ð3,ISTATUS=INACTIVE
R4ð82Að4 LU LOCADDR=ð4,ISTATUS=INACTIVE
R4ð82Að5 LU LOCADDR=ð5,ISTATUS=INACTIVE
R4ð82Að6 LU LOCADDR=ð6,ISTATUS=INACTIVE
R4ð82Að7 LU LOCADDR=ð7,ISTATUS=INACTIVE
R4ð82Að8 LU LOCADDR=ð8,ISTATUS=INACTIVE
R4ð82Að9 LU LOCADDR=ð9,ISTATUS=INACTIVE
R4ð82A1ð LU LOCADDR=1ð,ISTATUS=INACTIVE
R4ð82A11 LU LOCADDR=11,ISTATUS=INACTIVE
R4ð82A12 LU LOCADDR=12,ISTATUS=INACTIVE
R4ð82A13 LU LOCADDR=13,ISTATUS=INACTIVE
R4ð82A14 LU LOCADDR=ðð,RESSCB=16,ISTATUS=INACTIVE
R4ð82A15 LU LOCADDR=ðð,RESSCB=16,ISTATUS=INACTIVE
R4ð82A16 LU LOCADDR=ðð,RESSCB=16,ISTATUS=INACTIVE
R4ð82B PU ADDR=C2,ISTATUS=INACTIVE,XID=YES,NETID=RPC
R4ð82Bð1 LU LOCADDR=ð1,ISTATUS=INACTIVE
R4ð82Bð2 LU LOCADDR=ð2,ISTATUS=INACTIVE
R4ð82Bð3 LU LOCADDR=ð3,ISTATUS=INACTIVE
R4ð82Bð4 LU LOCADDR=ð4,ISTATUS=INACTIVE
R4ð82Bð5 LU LOCADDR=ð5,ISTATUS=INACTIVE
R4ð82Bð6 LU LOCADDR=ð6,ISTATUS=INACTIVE
R4ð82Bð7 LU LOCADDR=ð7,ISTATUS=INACTIVE
R4ð82Bð8 LU LOCADDR=ð8,ISTATUS=INACTIVE

Figure 17-10 (Part 2 of 2). ES/9000 VTAM Tables Defining NCP on the SNA Communi-
cation Controller

VTAM Definitions for the AS/400 System

The following figure contains VTAM-switched major node definitions for the con-
nection between the NCP communications controller and the AS/400 system using
token ring:

17-24 Remote Work Station Support V4R1

SW722 VBUILD TYPE=SWNET, REQUIRED PARAMETER X
MAXNO=8, MAX OF 8 DIAL NUMBERS MAY BE DEFINED \
MAXGRP=5 MAX OF 5 LINE GROUPS MAY BE DEFINED
\
SW722A PU ADDR=C1, 8 BIT STATION UNIQUE ADDRESS X
DISCNT=NO, ACCEPT DISCONTACT FROM PU (DEFAULT) X
IDBLK=ð56, 12 BIT BLOCK NUMBER FOR AS/4ðð X
IDNUM=ð722A, 2ð BIT ID NUMBER FOR REMOTE SYSTEM X
MAXDATA=1994, AS/4ðð MAXDATA FOR TOKENRING X
MAXPATH=8, MAX OF 8 PATHS FOR CALL OUT X
NETID=RPC, AS/4ðð LOCAL NETID VALUE X
MAXOUT=7, 7 PIUS TO DEVICE BEFORE RESPONSE X
PACING=ð, ð PACING X
PASSLIM=7, 7 CONTIGUOUS PIUS MAX AT ONE TIME X
PUTYPE=2, VALID FOR TYPE 2 OR 2.1 SUPPORT X
ISTATUS=ACTIVE, ACTIVATE WITH MAJOR NODE X
MODETAB=LOGMOD38, VTAM LOGN MODE TABLE ON S/37ð \
SSCPFM=USSSCS, VTAM TO STRIP/ADD MEDIA CONTROL CHAR \
VPACING=ð ð VPACING
\
PATH2 PATH GRPNM=R4Gð88L,DIALNO=ð1ð44ððð7ð5F4512
\
RCHAS722 LU LOCADDR=ðð, INDEPENDENT LU X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Að1 LU LOCADDR=ðð, INDEPENDENT LU X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Að2 LU LOCADDR=ð2, CORRESPONDS TO AS/4ðð LOCADR ð2 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Að3 LU LOCADDR=ð3, CORRESPONDS TO AS/4ðð LOCADR ð3 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Að4 LU LOCADDR=ð4, CORRESPONDS TO AS/4ðð LOCADR ð4 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
\
SW722B PU ADDR=C1, 8 BIT STATION UNIQUE ADDRESS X
DISCNT=NO, ACCEPT DISCONTACT FROM PU (DEFAULT) X
IDBLK=ð56, 12 BIT BLOCK NUMBER FOR AS/4ðð X
IDNUM=ð722B, 2ð BIT ID NUMBER FOR REMOTE SYSTEM X
MAXDATA=1994, AS/4ðð MAXDATA FOR TOKENRING X
MAXPATH=8, MAX OF 8 PATHS FOR CALL OUT X
NETID=RPC, AS/4ðð LOCAL NETID VALUE X
MAXOUT=7, 7 PIUS TO DEVICE BEFORE RESPONSE X
PACING=ð, ð PACING X
PASSLIM=7, 7 CONTIGUOUS PIUS MAX AT ONE TIME X
PUTYPE=2, VALID FOR TYPE 2 OR 2.1 SUPPORT X
ISTATUS=ACTIVE, ACTIVATE WITH MAJOR NODE X
MODETAB=LOGMOD38, VTAM LOGN MODE TABLE ON S/37ð \
SSCPFM=USSSCS, VTAM TO STRIP/ADD MEDIA CONTROL CHAR \
VPACING=ð ð VPACING
\
PATH2 PATH GRPNM=R4Gð88L,DIALNO=ð1ð84ððð7ð5F4512
\
SW722Bðð LU LOCADDR=ðð, INDEPENDENT LU X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Bð1 LU LOCADDR=ðð, INDEPENDENT LU X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Bð2 LU LOCADDR=ð2, CORRESPONDS TO AS/4ðð LOCADR ð2 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Bð3 LU LOCADDR=ð3, CORRESPONDS TO AS/4ðð LOCADR ð3 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SW722Bð4 LU LOCADDR=ð4, CORRESPONDS TO AS/4ðð LOCADR ð4 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE

Figure 17-11. ES/9000 VTAM AS/400 System Definitions

Chapter 17. SNA Primary LU2 Support 17-25

VTAM Definitions for the 3174 Establishment Controller
The following figure contains VTAM-switched major node definitions for the con-
nection between NCP and the 3174 controller:

SQ324 VBUILD TYPE=SWNET, REQUIRED PARAMETER X

MAXNO=8, MAX OF 8 DIAL NUMBERS MAY BE DFINED \
MAXGRP=5 MAX OF 5 LINE GROUPS MAY BE DEFINED
SQ324A PU ADDR=C1, 8 BIT STATION UNIQUE ADDRESS X
DISCNT=NO, ACCEPT DISCONTACT FROM PU (DEFAULT) X
IDBLK=ð17, 12 BIT BLOCK NUMBER FOR 3174 X
IDNUM=ððððð, 2ð BIT ID NUMBER FOR REMOTE SYSTEM X
MAXDATA=1994, AS/4ðð MAXDATA FOR TOKENRING X
MAXPATH=8, MAX OF 8 PATHS FOR CALL OUT X
PACING=ð, ð PACING X
PUTYPE=2, VALID FOR TYPE 2 OR 2.1 SUPPORT X
ISTATUS=ACTIVE, ACTIVATE WITH MAJOR NODE X
MODETAB=SD82, VTAM LOGN MODE TABLE ON S/37ð \
SSCPFM=USSSCS, VTAM TO STRIP/ADD MEDIA CONTROL CHAR \
VPACING=ð ð VPACING
\
PATH1 PATH GRPNM=R4Gð88L,DIALNO=ð1ð44ððð3174ððð4
\
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
\ LUs SQ324Að2 through SQ324Að6 use the first entry in LOGMODE table \
\ SD82. \
\ LUs SQ324Að7 and SQ324Að8 use the logmode specified in the LU \
\ definition. \
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
SQ324Að2 LU LOCADDR=ð2, CORRESPONDS TO 3174 PORT ðð X
ISTATUS=ACTIVE
SQ324Að3 LU LOCADDR=ð3, CORRESPONDS TO 3174 PORT ð1 X
ISTATUS=ACTIVE
SQ324Að4 LU LOCADDR=ð4, CORRESPONDS TO 3174 PORT ð2 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SQ324Að5 LU LOCADDR=ð5, CORRESPONDS TO 3174 PORT ð3 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SQ324Að6 LU LOCADDR=ð6, CORRESPONDS TO 3174 PORT ð4 X
ISTATUS=ACTIVE ACTIVATE WITH MAJOR NODE
SQ324Að7 LU LOCADDR=ð7, CORRESPONDS TO 3174 PORT ð5 X
ISTATUS=ACTIVE, X
DLOGMOD=SCSPTRR
SQ324Að8 LU LOCADDR=ð8, CORRESPONDS TO 3174 PORT ð6 X
ISTATUS=ACTIVE,VPACING=3,PACING=3, X
DLOGMOD=SCSTRNR

Figure 17-12. ES/9000 VTAM Tables Defining the 3174 Establishment Controller

Matching Parameters for an SDLC Line

The following diagram shows which AS/400 values need to match which VTAM
values when using a nonswitched SDLC line:

17-26 Remote Work Station Support V4R1

AS/4ðð System VTAM Licensed Program

Network Attributes
┌─────────5 LCLLOCNAME R4ð82A14 %─────┐
│ LCLNETID RPC%─────────┐ │
│ │ │
│ │ │
│ Line Description │ │
│ ┌──────5 LIND HOSTLINE │ │
│ │ CNN \NONSWTPP │ │
│ │ EXCHID \SYSGEN │ │ R4ð82 LINE Line definition
│ │ LINESPEED 96ðð %────────┼─┼────────────────────── SPEED=96ðð,
│ ┌┼──────5 MAXFRAME 521 %─────────┼─┼────────────────────── MAXDATA=521,
│ ││ NRZI \YES │ │
│ ││ │ │
│ ││ │ │
│ ││ Host Controller Description │ │
│ ││ ┌────5 CTLD HOSTCTL │ │ R4ð82A PU
│ ││ │ LINKTYPE \SDLC │ │ ┌───────────────────── ADDR=C1, Station address
│ │└─┼───── LINE HOSTLINE └─┼─┼───────────────────── NETID=RPC AS/4ðð local network identifier
│ └──┼───── MAXFRAME \LINKTYPE │ │
│ │ STNADDR C1 %────────────┼─┘
│ │ │
│ │ │
│ │ Display Device Description │
│ │ DEVD R4ð82Að │
│ │ DEVCLS \RMT │ R4ð82Að9 LU Dependent LU name
│ │ LOCADR ð9 %────────────┼─────────────────────── LOCADDR=ð9, Dependent LU address
│ ├───── CTL HOSTCTL │
│ │ APPTYPE \CTLSSN │
├────┼───── LCLLOCNAME \NETATR │
│ │ │
│ │ │
│ │ Display Device Description │
│ │ DEVD DSPð2 │
│ │ DEVCLS \RMT │
│ │ LOCADR ðð │
│ ├───── CTL HOSTCTL │
│ │ APPTYPE \DEVINIT │
│ │ INACTTMR \ATTACH │
│ │ └──────── R4ð82A14 LU Independent LU name
│ │ LOCADDR=ðð, Independent LU address
│ │ Printer Device Description
│ │ DEVD APð2
│ │ DEVCLS \RMT
│ │ TYPE 3287
│ │ MODEL ð
│ │ LOCADR ðð
│ └───── CTL HOSTCTL
│ APPTYPE \APPINIT
│ INACTTMR \SEC15
│ RMTLOCNAME SQ324Að7
└────────── LCLLOCNAME \NETATR

Matching Parameters for a Token-Ring Line

The following diagram shows AS/400 values and the corresponding VTAM values
when using a token-ring line:

Chapter 17. SNA Primary LU2 Support 17-27

AS/4ðð System VTAM Licensed Program

Network Attributes
┌─────────5 LCLLOCNAME RCHAS722 %────┐
│ LCLNETID RPC %───────┼───┐
│ │ │
│ │ │
│ Line Description │ │ Switched Major Node Definition
│ ┌─────5 LIND TRNLINE │ │ SW722 VBUILD Switched major node name
│ │ ADPTADR 4ððð7ð5F4512 %─┼───┼─┬──┐
│ │ LINESPEED 4M │ │ │ │
│ ┌┼─────5 MAXFRAME 1994 %─────────┼───┼─│ │
│ ││ │ │ │ │
│ ││ │ │ │ │
│ ││ Host Controller Description │ │ │ │ SW722A PU
│ ││ ┌───5 CTLD TRNCTL1 │ ┌┼─┼──┼──────────────┬5 IDBLK=ð56, AS/4ðð block number
│ ││ │ LINKTYPE \LAN │ ││ │ │ └5 IDNUM=ð722A, AS/4ðð ID number
│ │├─┼──── LINE TRNLINE │ ││ │ ├───────────────5 MAXDATA=1994, AS/4ðð maxdata
│ ├┼─┼──── MAXFRAME \LINKTYPE │ ││ ├──┼───────────────5 NETID=RPC, AS/4ðð local network ID
│ ││ │ RMTNETID USIBMZP │ ││ │ │
│ ││ │ RMTCPNAME ANYVAL1 │ ││ │ │───────────────────────────┐
│ ││ │ LCLEXCHID ð56ð722A %─────┼──┘│ │ │ PATH2 PATH ├──────────┐
│ ││ │ DSAP ð4 │ │ │ │ DIALNO=ð1ð44ððð7ð544512
│ ││ │ SSAP ð4 %───────────┼───┤ │ │ ├┘
│ ││ │ APPN \YES │ ├─┼──┼───────────────────────┘
│ ││ │ NODETYPE \LENNODE │ │ │ │
│ ││ │ │ │ │ │
│ ││ │ Display Device Description │ │ │ │
│ ││ │ DEVD TRN722A │ │ │ │ SW722Að4 LU
│ ││ │ LOCADR ð4 %───────────┼───┼─┼──┼──┼───────────── LOCADDR=ð4, Dependent LU address
│ ││ ├──── CTL TRNCTL1 │ │ │ │
│ ││ │ APPTYPE \CTLSSN │ │ │ │
└──┼┼─┼──── LCLLOCNAME \NETATR └───┼─┼──┼ RCHAS722 LU Independent LU name
││ │ │ │ │ LOCADDR=ðð, Independent LU address
││ │ Display Device Description │ │ │
││ │ DEVD TRN722Aððð │ │ │
││ │ LOCADR ðð │ │ │
││ └──── CTL TRNCTL1 │ │ │
││ APPTYPE \DEVINIT │ │ │
││ │ │ │
││ │ │ │
││ Host Controller Description │ │ │ SW722B PU
││ ┌───5 CTLD TRNCTL2 ┌┼─┼──┼─────────────┬─ IDBLK=ð56, AS/4ðð block number
││ │ LINKTYPE \LAN ││ │ │ └─ IDNUM=ð722B, AS/4ðð ID number
│└─┼──── LINE TRNLINE ││ └──┼─────────────── MAXDATA=1994, AS/4ðð maxdata
└──┼──── MAXFRAME \LINKTYPE │└────┼─────────────── NETID=RPC, AS/4ðð local net ID
│ RMTNETID \NETATR │ │
│ RMTCPNAME ANYVAL2 │ └───────────────────────────┐
│ LCLEXCHID ð56ð722B %────────┘ PATH2 PATH ├──────────┐
│ DSAP ð4 DIALNO=ð1ð84ððð7ð544512
│ SSAP ð8 %───────────────┐ ├┘
│ APPN \YES └───────────────────────────────┘
│ NODETYPE \LENNODE
│
│ Display Device Description
│ DEVD TRN722B SW722Bð4 LU
│ LOCADR ð4 %────────────────────────────────────── LOCADDR=ð4, Dependent LU address
├──── CTL TRNCTL2
│ APPTYPE \CTLSSN
│ LCLLOCNAME SW722Bðð %──────────────────5 SW722Bðð LU Independent LU name
│ LOCADDR=ðð, Independent LU address
│ Display Device Description
│ DEVD TRN722Bððð
│ LOCADR ðð
└──── CTL TRNCTL
APPTYPE \DEVINIT

17-28 Remote Work Station Support V4R1

| Chapter 18. Dependent LU Requester Support
| This section discusses the Dependent LU Requester (DLUR) support included with
| the OS/400 licensed program.

| Dependent LU Requester Support—Definition

| DLUR allows dependent secondary logical units (LU 0, 1, 2, and 3) an entry point
| into the APPN network. DLUR support gives the appearance of having an adjacent
| connection to VTAM, but allows traversing the APPN network through intermediate
| nodes.

| The normal SSCP-PU and SSCP-LU flows for dependent LUs are encapsulated in
| a control point server (CP-SVR) pipe. This pipe consists of two LU 6.2 sessions:
| Send
| Receive

| At the primary end of the pipe is a Dependent LU Server (DLUS) and at the sec-
| ondary end of the pipe is a Dependent LU Requester (DLUR). DLUS and DLUR
| support the activation and deactivation of dependent physical units (PUs) and
| logical units (LUs) in the APPN network. The pipe consists of a pair of LU 6.2
| conversations where two APPC applications (DLUR and DLUS) exchange
| dependent SNA SSCP flows. The flows are encapsulated in a general data stream
| (GDS) variable and sent in LU 6.2 logical records. The pair of conversations used
| to transmit encapsulated SNA is called the CP-SVR Pipe.

| Sessions from upstream applications to the AS/400 are not tied to the route used
| by the DLUR and DLUS connection. These flows are not encapsulated. The data
| between the application and the AS/400 is known as the LU-LU session. Once the
| application is initiated by VTAM at the DLUS node, it individually locates the
| AS/400 LU (device) that is secondary for the session and sends data to it.
| Figure 18-1 shows the AS/400 with multiple links into the network. The DLUR
| CP-SVR session travels through network node B, but an LU-LU session between
| the application and the AS/400 LU could flow through network nodes A and C.
| Encapsulated
| SSCP flows
| ┌───────┐ ┌─────────┐ ┌─────────┐
| │ │ │ │ │ │
| │ SSCP │%─────5│Network │%───────────────5│AS/4ðð │
| └───────┘ │Node B │ │ │
| & └─────────┘ └─────────┘
| │ &
| │ │
| │ │
| │ Initiate │
| │ │
| │ │
| │ │
| 6 6
| ┌───── ─────┐ ┌─────────┐ LU-LU ┌──────────┐
| │Application│%────5│Network │ flows │Network │
| │ │ │Node A │%──────────────5│Node C │
| └───────────┘ └─────────┘ └──────────┘

| Figure 18-1. DLUR - Multiple Paths Through the Network

| Before You Begin Configuring the AS/400 System for Dependent LU

| Requester
| DLUR uses logmode CPSVRMGR. This is created internally as part of the APPN
| and DLUR support. If CPSVRMGR exists as a user-defined logmode on any of the
| systems in your network, it must be deleted. Use the Work with Mode Descriptions
| (WRKMODD) command and specify the option to delete CPSVRMGR.

| Before You Begin Creating Device and Controller Descriptions

| Before creating the controller and device descriptions for DLUR, you should con-
| sider the following configuration options:
| DLUR node activation or DLUS node activation
| Using automatic configuration of DLUS PUs and LUs (model definitions) or
| using predefined VTAM definitions
| Specifying logical names on the AS/400 device description and host controller
| description
| Error recovery options

| AS/400 DLUR Session Activation

| If the AS/400 DLUR host controller is configured to initiate the CP-SVR pipe (speci-
| fying the *DIAL value for the Initial Connection (INLCNN) parameter), AS/400 DLUR
| support will initiate a session to the remote DLUS node through an SNA request
| activate physical unit (REQACTPU) request. If this is a switched connection, the
| request will cause the line to be dialed.

| If the AS/400 DLUR host controller is configured to wait for the DLUS to initiate the
| CPSVR pipe (specifying the *ANS value for the INCLNN parameter), AS/400 DLUR
| support will wait for a predefined PU definition on the remote DLUS to drive a con-
| nection and issue an unsolicited SNA activate physical unit (ACTPU) request.

| Automatic Configuration
| The DLUS host can have preconfigured model definitions. These definitions can be
| used to generate PU and LU definitions on the DLUS node. When the AS/400
| DLUR node issues an SNA REQACTPU request, the DLUS node will automatically
| define the PU based on the model definition to which the request is issued.

18-2 Remote Work Station Support V4R1

| Similarly, if the DLUS node supports DDDLU (Dynamic Definition of Dependent
| LUs), the AS/400 DLUR support will provide information to the DLUS node to
| dynamically define the LUs. However, the DLUR architecture does not support
| sending the logical name of the LU from the DLUR node to the DLUS node to be
| used for DDDLU. If the name that is generated by the DDDLU support does not
| match the DEPLOCNAME specified on the AS/400 device description, the ACTLU
| will be rejected by the AS/400.

| Using model definitions eliminates much of the costly configuration maintenance

| involved in coordinating hard-coded definitions at both ends of the connection.
| Note: A sample model definition and sample exit program are provided by VTAM.
| If the sample model definition is activated and the exit program is installed
| on VTAM, then VTAM will use the information sent by the AS/400 to create
| PUs and LUs.

| Dependent Logical Names

| Dependent PU Name
| AS/400 device configuration requires that at least one of the following parameters
| be specified on the DLUR host controller definition: local exchange identifier
| (LCLEXCHID parameter) or dependent physical unit name (DEPPUNAME). These
| values must match the value defined on the DLUS or the activate physical unit
| (ACTPU) request will be rejected by the AS/400.

| The default value for AS/400 DLUR host controllers is *LIND for local exchange ID.
| Because the AS/400 DLUR host controller is not configured to a line, this defaults
| to zeroes. If using the default local exchange ID, the dependent PU name becomes
| a required parameter on the AS/400 DLUR host controller.

| Dependent Location Name

| The Dependent Location name is a logical name by which the DLUS LU knows the
| AS/400. Architecturally, location names are supported. Currently, VTAM DLUS does
| not contain location name processing in their model definition routines.

| If the Dependent Location name is not configured on the AS/400 device

| descriptions, then the DLUS and AS/400 DLUR will do local location address
| checking. The DLUS node will generate a dependent location name for that session
| only.

| Dependent Location names are registered with AS/400 APPN support. This allows
| a remote application to initiate a search to the AS/400 APPN support to find the LU
| (device). If the Dependent Location name is configured on the AS/400 device
| description, the Location name is registered when the device is created. If VTAM
| DLUS generates a dependent location name, it is registered at the AS/400 when
| the SNA ACTLU request is received.

| Error Recovery Options

| If you are configuring your network to automatically configure DLUS PUs and LUs
| through model definitions at the DLUS nodes, you must specify the following
| parameters when you are creating the DLUR controller:
| Initial connection (*DIAL)

Chapter 18. Dependent LU Requester Support 18-3

| Primary DLUS name

| If the VTAM connection is dropped, configurations built from model definitions are
| also deleted. The DLUR CP-SVR Pipe connection to the DLUS node is logical
| (encapsulated LU 6.2 sessions) rather than physical (adjacent link), so the
| Boundary Function in the NCPs does not store the XID information from the DLUR
| PUs. Therefore, it is nearly impossible for traditional SSCP takeover and giveback
| to recover node and network outages. The AS/400 DLUR support must initiate
| recovery.

| This configuration allows the AS/400 DLUR node to automatically (with no DLUS
| intervention) drive sessions to a backup (takeover) DLUS node when a session
| outage (due to node or network outage) is detected. It also allows the AS/400
| DLUR node to return to the primary DLUS node when a PU at the backup DLUS is
| varied inactive with the giveback option (SSCP giveback).

| If both DLUS nodes are configured to allow bound sessions to remain active during
| session outage/giveback (specifying the *ANS value for the Continuous parameter),
| the AS/400 devices can remain active through the entire recovery process because
| the AS/400 DLUR supports this DLUS node capability. This generally works well for
| DLUS node outages, but is less effective in network outages, because DLUR/DLUS
| sessions and bound sessions tend to take the same route through the network
| (although this is not always true).

| Configuration Steps for Dependent LU Requester

| To configure the AS/400 system to communicate with DLUS, perform these steps:
| 1. Configure a host controller description (described in “Step 1: Configuring the
| Host Controller for DLUR Support”).
| 2. Configure device descriptions (described in “Step 2: Configuring the Device”
| on page 18-6).
| 3. Verify that an APPN connection into the network exists (host or APPC con-
| troller with *YES specified for the APPN parameter).

| Step 1: Configuring the Host Controller for DLUR Support

| Use the Create Controller Description (SNA Host) (CRTCTLHOST) command to
| create the controller description. If you have already created a controller description
| for such functions as 3270 emulation or NRF, you must change the link type to
| *DLUR. Follow these steps:
| 1. Retrieve the configuration description for the DLUR controller description using
| the Retrieve Configuration Source (RTVCFGSRC) command.
| 2. Edit the member to change the link type to *DLUR.
| 3. Convert the source to a CL program.
| 4. Create the CL program using the CRTCLPGM command.
| 5. Delete the configuration using the DLTCTLD command.
| 6. Call the CL program to create the new configuration.

| Figure 18-2 on page 18-5 is an example of a host controller description that sup-
| ports DLUR. This example uses DA327AI as the name of the controller description
| and *DLUR as the link type.

18-4 Remote Work Station Support V4R1

| à ð
| CREATE CTL DESC (SNA HOST) (CRTCTLHOST)

| TYPE CHOICES, PRESS ENTER.

| CONTROLLER DESCRIPTION . . . . . > DA327AI NAME

| LINK TYPE . . . . . . . . . . . > \DLUR \DLUR, \FR, \IDLC, \LAN...
| ONLINE AT IPL . . . . . . . . . \YES \YES, \NO
| SWITCHED CONNECTION . . . . . . > \YES \NO, \YES
| APPN-CAPABLE . . . . . . . . . . \YES \YES, \NO
| MAXIMUM FRAME SIZE . . . . . . . \LINKTYPE 265-16393, 256, 265, 512...
| SSCP IDENTIFIER . . . . . . . . _________ ð5ðððððððððð-ð5FFFFFFFFFF
| LOCAL EXCHANGE IDENTIFIER . . . > ð56A3271 ð56ððððð-ð56FFFFF, \LIND
| INITIAL CONNECTION . . . . . . . \DIAL \DIAL, \ANS
| DIAL INITIATION . . . . . . . . > \IMMED \LINKTYPE, \IMMED, \DELAY
| CONNECTION NUMBER . . . . . . . _________
| APPN CP SESSION SUPPORT . . . . \YES \YES, \NO
| APPN NODE TYPE . . . . . . . . . \ENDNODE \ENDNODE, \LENNODE...
| APPN TRANSMISSION GROUP NUMBER 1 1-2ð, \CALC
| APPN MINIMUM SWITCHED STATUS . . \VRYONPND \VRYONPND, \VRYON
| AUTOCREATE DEVICE . . . . . . . \ALL \ALL, \DEVINIT, \NONE
| MORE...
| F3=EXIT F4=PROMPT F5=REFRESH F1ð=ADDITIONAL PARAMETERS F12=CANCEL
| F13=HOW TO USE THIS DISPLAY F24=MORE KEYS
| á ñ
| à ð
| CREATE CTL DESC (SNA HOST) (CRTCTLHOST)

| TYPE CHOICES, PRESS ENTER.

| AUTODELETE DEVICE . . . . . . . 144ð 1-1ðððð, 144ð, \NO

| USER-DEFINED 1 . . . . . . . . . \LIND ð-255, \LIND
| USER-DEFINED 2 . . . . . . . . . \LIND ð-255, \LIND
| USER-DEFINED 3 . . . . . . . . . \LIND ð-255, \LIND
| TEXT 'DESCRIPTION' . . . . . . . > 'DLUR to PU DA327A'
|
| Primary DLUS name:
| CONTROL POINT NAME . . . . . . > R5CDRM NAME, \NONE
| NETWORK IDENTIFIER . . . . . . > USIBMZP NAME, \NETATR
| Backup DLUS name:
| CONTROL POINT NAME . . . . . . > RSCDRM NAME, \NONE
| NETWORK IDENTIFIER . . . . . . > USIBMZP NAME, \NETATR
| Dependent PU name . . . . . . . > DA327A NAME, \NONE
| ACTIVATION TIMER . . . . . . . . 17ð 3ð-255ð (seconds)
| DSC/RECONNECT TIMER (T3ð9) . . . 17ð 1-255ð (seconds)

| BOTTOM
| F3=EXIT F4=PROMPT F5=REFRESH F1ð=ADDITIONAL PARAMETERS F12=CANCEL
| F13=HOW TO USE THIS DISPLAY F24=MORE KEYS

| á ñ
| Figure 18-2. Configuring the Host Controller to Support DLUR

| Local exchange identifier Matches the ID block and ID number parameters from
| the PU definition on VTAM.
| Dependent PU name Matches the name of the PU specified on the PU definition
| on VTAM.
| Note: If the local exchange identifier and the dependent PU name are
| specified, both must match the definitions on VTAM. If both
| parameter values do not match, the ACTPU will be rejected.
| If the *DIAL value is specified for the INLCNN parameter, the
| primary DLUS name (PRIDLUS) and either the local exchange

Chapter 18. Dependent LU Requester Support 18-5

| identifier (LCLEXCHID) or the dependent PU name
| (DEPPUNAME) must be specified.
| Control point name and network identifier for the primary DLUS name
| Matches the SSCP name and NETID parameters on the VTAM startup
| options.

| Step 2: Configuring the Device

| à ð
| CREATE DEVICE DESC (DISPLAY) (CRTDEVDSP)

| TYPE CHOICES, PRESS ENTER.

| DEVICE DESCRIPTION . . . . . . . > DA327A18HC NAME

| DEVICE CLASS . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
| DEVICE TYPE . . . . . . . . . . > 3277 31ð1, 3151, 3161, 3162...
| DEVICE MODEL . . . . . . . . . . > \DHCF ð, 1, 2, 4, 5, 12, 23...
| LOCAL LOCATION ADDRESS . . . . . 12 ðð-FE
| ONLINE AT IPL . . . . . . . . . \YES \YES, \NO
| ATTACHED CONTROLLER . . . . . . DA327AI NAME
| KEYBOARD LANGUAGE TYPE . . . . . \SYSVAL \SYSVAL, AGB, AGI, ALI...
| DROP LINE AT SIGNOFF . . . . . . \YES \YES, \NO
| TEXT 'DESCRIPTION' . . . . . . . HCF device description for DLUR support
|
| Dependent location name . . . . DA327A18 NAME, \NONE

| BOTTOM
| F3=EXIT F4=PROMPT F5=REFRESH F1ð=ADDITIONAL PARAMETERS F12=CANCEL
| F13=HOW TO USE THIS DISPLAY F24=MORE KEYS

| á ñ
| Figure 18-3. Configuring a Device Description Display

| Dependent location name Matches the LU name on the LU definition on VTAM.

| Note: This must match the VTAM LU name with the corresponding
| local location address (LOCADDR) on VTAM.

| Logon Sessions
| Users who want to access an AS/400 can do so using VTAM and DLUR by
| sending a request to the VTAM SSCP.

| 3270 Device Support

| For information on AS/400 support for 3270 devices, see the Remote Work Station
| Support book, and the 3270 Device Emulation Support book.

| For more information about SNUF, see the SNA Upline Facility Programming book.

| For more information about RJE, see the Remote Job Entry (RJE) Guide.

18-6 Remote Work Station Support V4R1

| VTAM Cross-Domain Resource Definition
| VTAM Cross-Domain Resource Definition (CDRSC) defines the control point name
| of the AS/400 providing DLUR function.

| Figure 18-4 and Figure 18-5 show examples of the definitions. These cross
| domain resource definitions define the same AS/400 DLUR as a multiple hop con-
| nection or as an adjacent connection.
| Note: The first definition is an example showing the DLUR to be multiple hops
| from the DLUS. The APPN connection is through SWDLUR2A, a PU on
| ASDLUR2. This is illustrated on Figure 18-8 on page 18-8.

| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| \ I/S CROSS DOMAIN APPLICATIONS AND RESOURCES \
| \ USING SWITCHED MAJOR NODES SWDLUR2 FOR MULTIHOP CONNECTION \
| \ FROM VTAM to ASDLUR THRU ASDLUR2.
| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| CDRDLUR VBUILD TYPE=CDRSC
| NETWORK NETID=APPN
| ASDLUR CDRSC ISTATUS=ACTIVE,ALSLIST=(SWDLUR2A)

| Figure 18-4. VTAM CDRSC for Multihop Connection Example

| Note: This definition is an example showing the DLUR adjacent to the DLUS. The
| APPN connection is through SWDLUR1A which is a PU on ASDLUR.

| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| \ I/S CROSS DOMAIN APPLICATIONS AND RESOURCES \
| \ USING SWITCHED MAJOR NODES SWDLUR1 FOR ADJACENT CONNECTION \
| \ FROM VTAM to ASDLUR \
| \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
| CDRDDLUR VBUILD TYPE=CDRSC
| NETWORK NETID=APPN
| ASDLUR CDRSC ISTATUS=ACTIVE,ALSLIST=(SWDLUR1A)

| Figure 18-5. VTAM CDRSC CDRSC for Adjacent Connection Example

Chapter 18. Dependent LU Requester Support 18-7

| VTAM Definitions for the AS/400 System for DLUR Support
| The following example shows definitions for VTAM (DLUS) initiating connections.
| The example shows the parameters required in the path statement in the switched
| major node definition. The statements define the AS/400 as a DLUR node con-
| taining an internal physical unit (INTPU) and the exchange identifier. These also
| map to the ID Block and ID Number. See “Matching Parameters for the AS/400
| DLUR and VTAM” on page 18-11 for more information.

| The following example shows definitions for VTAM (DLUS) with AS/400 (DLUR) ini-
| tiating connections. In this example, the PU statement specifies the PU name that
| must match the dependent PU name on the AS/400 controller description for
| DLUR. The ID Block and ID Number must match the local exchange identifier on
| the AS/400 controller description for DLUR.

| VTAM Definitions for the AS/400 System for APPN Connections

| Figure 18-8 shows the VTAM definition of the AS/400 that is an intermediate node
| between VTAM and the AS/400 DLUR. See “Matching Parameters for the APPN
| Connection between the AS/400 and VTAM” on page 18-11 for more information.

| AS/4ðð AS/4ðð VTAM

| ┌──────────┐ ┌──────────┐ ┌──────────┐
| │ │ │ │ │ │
| │ ASDLUR ├─────┤ ASDLUR2 ├─────┤ VTAM │
| │ │ │ │ │ │
| └──────────┘ └──────────┘ └──────────┘

| Intermediate
| Node
| Figure 18-8. AS/400 as an Intermediate Node

| Figure 18-9 contains VTAM definitions for the APPN connections for the AS/400
| systems using token ring lines.

| SWDLUR2 VBUILD TYPE=SWNET, REQUIRED PARAMETER X

| Figure 18-9. VTAM AS/400 System Definitions for APPN Connections

18-8 Remote Work Station Support V4R1

| Figure 18-6. Example of VTAM Initiating Connections

Chapter 18. Dependent LU Requester Support 18-9

| Figure 18-7. Example of VTAM with DLUR Initiating Connections

18-10 Remote Work Station Support V4R1

| Matching Parameters for the AS/400 DLUR and VTAM

| Figure 18-10. Matching Parameters for AS/400 DLUR and VTAM

| Matching Parameters for the APPN Connection between the AS/400

| and VTAM

Chapter 18. Dependent LU Requester Support 18-11

| Figure 18-11. Matching Parameter Between AS/400 and VTAM

| Error Recovery
| Note: If the DLUR attempt to initiate a CP-SVR pipe with the DLUS is unsuc-
| cessful, a message is sent to QSYSOPR. An informational message pro-
| vides information about the problem detected and recovery instructions. An
| inquiry message (CPA5D80 or CPA5D88) is also issued for the controller.
| After correcting the problem, responding with R (Retry) causes DLUR to try
| initiating the connection to DLUS. Responding with an I (Ignore) to either of
| the messages causes the controller to stop trying to initiate contact with that
| physical unit (PU) on the DLUS. The controller will wait and respond to
| incoming calls from the DLUS. If the CP-SVR pipe is disconnected after the
| DLUS makes contact, the AS/400 will retry the connection. If an incoming
| call is not received and you want the controller to initiate a call again, you
| must do the following:
| 1. Vary off the DLUR controller.
| 2. Vary on the DLUR controller.

18-12 Remote Work Station Support V4R1

Part 4. Configuring for X.21 Short Hold Mode
Chapter 19. X.21 Short-Hold Mode Configuration Example . . . . . . . . 19-1
Multiple Port Sharing Configuration Example . . . . . . . . . . . . . . . . . . . 19-1
Configuring the AS/400 Line Description for Multiple Port Sharing . . . . . 19-1
3274 Control Unit Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Configuring AS/400 Controller and Device Descriptions for the 3274 . . . 19-3
5294 Remote Control Unit Configuration . . . . . . . . . . . . . . . . . . . . 19-5
Configuring AS/400 Controller and Device Descriptions for the 5294 . . . 19-6
5394 Remote Control Unit Configuration . . . . . . . . . . . . . . . . . . . . 19-7
Configuring AS/400 Controller and Device Descriptions for the 5394 . . . 19-8

Remote Work Station Support V4R1
Chapter 19. X.21 Short-Hold Mode Configuration Example
This chapter contains an example configuration for X.21 short-hold mode (SHM). It
describes multiple port sharing with the AS/400 system serving as a primary station
managing a 2-port group with 3274, 5294, and 5394 remote work station controllers
as secondary stations. Detailed descriptions of the commands and parameters
used in this example can be found in the Communications Configuration book.

Multiple Port Sharing Configuration Example

The following example shows remote controller and AS/400 configurations for X.21
SHM using multiple port sharing. The AS/400 line description is shown first, fol-
lowed by the remote control unit configuration and the associated AS/400 controller
and device descriptions for each of the three (3274, 5294, and 5394) remote
control units.

Command prompt displays are used to show the AS/400 configuration objects.
These displays are shown by typing the name of the command, then pressing F4.
Only those displays required to specify nondefault values are shown.

Configuring the AS/400 Line Description for Multiple Port Sharing

The following prompt displays use the CRTLINSDLC command to create an AS/400
line description for X.21 SHM with multiple port sharing.

à ð
Create Line Desc (SDLC) (CRTLINSDLC)

Type choices, press Enter.

Line description . . . . . . . . > SHMRWS Name

Resource names . . . . . . . . . > LINð91.1/ Name
+ for more values > LINð92.1/
Online at IPL . . . . . . . . . > \NO \YES, \NO
Data link role . . . . . . . . . > \PRI.2/ \NEG, \PRI, \SEC
Physical interface . . . . . . . > \X21.3/ \RS232V24, \V35, \X21, ...
Connection type . . . . . . . . > \SHM.3/ \NONSWTPP, \SWTPP, \MP, \SHM
SHM node type . . . . . . . . . > \T2ð.2/ \T21, \T2ð
Vary on wait . . . . . . . . . . \NOWAIT \NOWAIT, 15-18ð (1 second)
Exchange identifier . . . . . . \SYSGEN ð56ððððð-ð56FFFFF, \SYSGEN
NRZI data encoding . . . . . . . > \NO \YES, \NO
Maximum controllers . . . . . . > 3.4/ 1-254
Line speed . . . . . . . . . . . 96ðð 6ðð, 12ðð, 24ðð, 48ðð...
Modem type supported . . . . . . \NORMAL \NORMAL, \V54, \IBMWRAP...
Switched connection type . . . . \BOTH \BOTH, \ANS, \DIAL
Autoanswer . . . . . . . . . . . \YES \YES, \NO
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

à ð
Create Line Desc (SDLC) (CRTLINSDLC)

Type choices, press Enter.

Autodial . . . . . . . . . . . . > \YES \NO, \YES

Dial command type . . . . . . . \NONE \NONE, \V25BIS
SHM call timer . . . . . . . . . \NONE \NONE, 1-6ð (minutes)
SHM maximum connect timer . . . 8 \NOMAX, 1-254 (seconds)
SHM answer delay timer . . . . . 11 \NOMAX, 1-254 (ð.1 seconds)
Calling number . . . . . . . . . > 976452ð.5/
Short timer . . . . . . . . . . 5ð 1ð-6ðð (ð.1 seconds)
Long timer . . . . . . . . . . . 6ðð 1ðð-6ððð (ð.1 seconds)
Short retry . . . . . . . . . . 7 ð-254
Long retry . . . . . . . . . . . 1 ð-254
Call progress signal retry . . . \CPS41, \CPS42, \CPS43...
+ for more values
Maximum frame size . . . . . . . 521 265, 521, 1ð33, 2ð57
Duplex . . . . . . . . . . . . . > \FULL \HALF, \FULL
Nonproductive receive timer . . 32ð 16ð-42ðð (ð.1 seconds)
Idle timer . . . . . . . . . . . 3ð 5-3ðð (ð.1 seconds)
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ

à ð
Create Line Desc (SDLC) (CRTLINSDLC)

Type choices, press Enter.

Connect poll timer . . . . . . . 3ð 2-3ðð (ð.1 seconds)

Poll cycle pause . . . . . . . . ð ð-2ð48 (ð.ððð1 seconds)
Frame retry . . . . . . . . . . 7 ð-64
Data Set Ready drop timer . . . 6 3-6ð (seconds)
Autoanswer type . . . . . . . . \DTR \DTR, \CDSTL
Remote answer timer . . . . . . 6ð 3ð, 35, 4ð, 45 (seconds)...
Text 'description' . . . . . . . > 'Short hold mode SDLC line'

Notes:
.1/ Two Resource names (RSRCNAME parameter) are specified to indicate
to the system which ports are used for multiple port sharing.
.2/ The Data link role (ROLE parameter) and SHM node type (SHM param-
eter) must be specified as shown for lines used with remote work station
controllers.
.3/ Physical interface (INTERFACE parameter) and Connection type (CNN
parameter) must be specified as shown for an X.21 SHM line.
.4/ The maximum number of controllers (MAXCTL parameter) is set to three
(for the attached 3274, 5294, and 5394 controllers).
.5/ The Calling number (CALLNBR parameter) represents the connection
number of the AS/400 system.

19-2 Remote Work Station Support V4R1

3274 Control Unit Configuration
The following displays show the configuration for a 3274 control unit with the 3274
X.21 short-hold mode RPQ 7H0497 installed.

à ð
ð33 ð1ðð
.1/ 9812 836F FFFF FFFF
FFFF FFFF FFFF FFFF
9ð3 - ð

Figure 19-1 (Part 1 of 2). 3274 Control Unit Configuration Displays

à ð
999 ð11ð
111 -
ðð 112 - 16 113 - DA 114 - ð 115 - ð 116 - ð
121 -
ð1 125 - ðð1ððððð 127 - ð ð
136 -
ð ð ð 137 - ð ð ð ð 138 - ð 139 - ð
141 -
A 151 - 61C
16ð -
1 161 - 1 165 - ð 166 - B
17ð -
ð 173 - ðððððððð 175 - ðððððð
213 - 1 .2/ 215 - ðððC3 22ð - ð
3ð2 - C3.3/
31ð - ð 311 - ð 313 - ð 314 - ð 317 - ð 318 - ð
331 - 1 342 - ð 343 - ð3 345 - ð 347 - ð
351 - 1 352 - ð .4/ 36ð - 15 361 - 7 362 - 11111ð11
9ðð - ð

Figure 19-1 (Part 2 of 2). 3274 Control Unit Configuration Displays

Notes:
.1/ Item 033 is used to enter RPQ information and specifies the connection
number of the 3274. The connection number (CNNNBR parameter)
must be matched in the AS/400 controller description.
.2/ Item 215 specifies the system name of the 3274. This value must match
the last 5 digits of the exchange identifier (EXCHID parameter) specified
for the AS/400 controller description.
.3/ Item 302 specifies the station address of the 3274. This value must
match the station address (STNADR parameter).
.4/ Items 360 and 361 set the retry limit to 15 with a 7-second delay.

Configuring AS/400 Controller and Device Descriptions for the 3274

The following prompt displays use the CRTCTLRWS and CRTDEVDSP commands
to create AS/400 controller and device descriptions for the 3274 control unit and
one attached 3278 display station.

Chapter 19. X.21 Short-Hold Mode Configuration Example 19-3

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > SHM3274 Name

Controller type . . . . . . . . > 3274 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > ð ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \SDLC \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . > \NO \YES, \NO
Switched connection . . . . . . > \YES.1/ \NO, \YES
Short hold mode . . . . . . . . > \YES.1/ \NO, \YES
Switched line list . . . . . . . > SHMRWS.2/ Name
+ for more values
Exchange identifier . . . . . . > ð17ðððC3.3/ ðð1ððððð-FFFFFFFF
Initial connection . . . . . . . \DIAL \DIAL, \ANS
Dial initiation . . . . . . . . \LINKTYPE \LINKTYPE, \IMMED, \DELAY
Connection number . . . . . . . > 9812836.4/
SHM disconnect limit . . . . . . 1ð 1-254, \NOMAX
SHM disconnect timer . . . . . . 5ð 2-3ððð (ð.1 seconds)
Station address . . . . . . . . > C3.5/ ð1-FE
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 19-2. Prompt Display for SHM3274 Controller Description

Notes:
.1/ Both Switched connection (SWITCHED parameter) and Short hold mode
(SHM parameter) must be specified as *YES for X.21 SHM controller
descriptions.
.2/ The Switched line list (SWTLINLST parameter) must include the name
of the line description to which the controller is attached (LIND param-
eter on the CRTLINSDLC command).
.3/ The Exchange identifier must include the correct block number used for
the controller type (017 for 3274 control units) plus the 5-digit system
name specified in item 215 of the 3274 configuration.
.4/ The Connection number (CNNNBR parameter) specifies the connection
number for the remote control unit. This value must match that specified
in item 033 of the 3274 configuration.
.5/ The Station address (STNADR parameter) must match the station
address specified in item 302 of the 3274 configuration.

19-4 Remote Work Station Support V4R1

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > SHM3274 Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 3278 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > ð ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ð2.1/ ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > SHM3274.2/ Name
Keyboard language type . . . . . \SYSVAL \SYSVAL, AGB, AGI, BLI...
Drop line at signoff . . . . . . > \NO \YES, \NO
Application type . . . . . . . . \NONE \NONE, \NRF, \CTLSSN...
Text 'description' . . . . . . . > '3278 display station attached to 3274 ctl'

Figure 19-3. Prompt Display for SHM3274 Display Device Description

Notes:
.1/ The Local location address (LOCADR parameter) must match the device
address set at the 3278 display station.
.2/ The Attached controller (CTL parameter) must specify the name of the
controller description to which the device is attached (CTLD parameter
on the CRTCTLRWS command).

5294 Remote Control Unit Configuration

The following display shows the configuration for a 5294 Remote Control Unit with
one attached 5291 display station at address 00.

à ð
ð 1 2 3 4 5 6
----------------------------------------------------------
ð/ D.1/ . . . . . .

1/ . . . . . . .

2/ . . . . . . .

3/ . . . . . . .

1-> ðð 2-> C2 9-> ð A-> 9734915AAAAAAAA B-> ðF 7 ð

.2/ .3/ .4/

á ñ
Figure 19-4. 5294 Remote Control Unit Configuration Display

.1/ The device address of the attached display station (00) must be
matched by the Local location address (LOCADR parameter) specified
on the CRTDEVDSP command. See “Configuration of Remote Devices

Chapter 19. X.21 Short-Hold Mode Configuration Example 19-5

and 5394 Remote Control Units” on page 9-2 for more information
about determining device addresses from the 5x94 configuration dis-
plays.
.2/ Field 2 specifies the station address of the 5x94. This value must match
the station address (STNADR parameter).
.3/ Field A specifies the connection number of the 5x94. This value must
match the Connection number (CNNNBR parameter) specified in the
AS/400 controller description.
.4/ Field B sets the retry limit to 15 (hex 0F) with a 7-second delay.

Configuring AS/400 Controller and Device Descriptions for the 5294

The following prompt displays use the CRTCTLRWS and CRTDEVDSP commands
to create AS/400 controller and device descriptions for the 5294 Remote Control
Unit and one attached 5291 display station.

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > SHM5294 Name

Controller type . . . . . . . . > 5294 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > 1 ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \SDLC \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . > \NO \YES, \NO
Switched connection . . . . . . > \YES.1/ \NO, \YES
Short hold mode . . . . . . . . > \YES.1/ \NO, \YES
Switched line list . . . . . . . > SHMRWS.2/ Name
+ for more values
Exchange identifier . . . . . . > ð45ðððC2.3/ ðð1ððððð-FFFFFFFF
Initial connection . . . . . . . \DIAL \DIAL, \ANS
Dial initiation . . . . . . . . \LINKTYPE \LINKTYPE, \IMMED, \DELAY
Connection number . . . . . . . > 9734915.4/
SHM disconnect limit . . . . . . 1ð 1-254, \NOMAX
SHM disconnect timer . . . . . . 5ð 2-3ððð (ð.1 seconds)
Station address . . . . . . . . > C2.5/ ð1-FE
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 19-5. Prompt Display for SHM5294 Controller Description

Notes:
.1/ Both Switched connection (SWITCHED parameter) and Short hold mode
(SHM parameter) must be specified as *YES for X.21 SHM controller
descriptions.
.2/ The Switched line list (SWTLINLST parameter) must include the name
of at least one line description to which the controller can be attached
(LIND parameter on the CRTLINSDLC command).
.3/ The Exchange identifier must be an 8-digit hexadecimal value including
the correct block number used for the controller type (045 for 5294
Remote Control Units, 05F for 5394s), followed by 3 zeros and the
station address specified in field 2 of the 5x94 configuration (045 + 000
+ C1, or 045000C1).

19-6 Remote Work Station Support V4R1

.4/ The Connection number (CNNNBR parameter) specifies the connection
number for the remote control unit. This value must match that specified
in field A of the 5x94 configuration.
.5/ The Station address (STNADR parameter) must match the station
address specified in field 2 of the 5x94 configuration.

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > SHM5294 Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 5291 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > 1 ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ðð.1/ ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > SHM5294.2/ Name
Drop line at signoff . . . . . . > \NO \YES, \NO
Allow blinking cursor . . . . . \YES \YES, \NO
Printer . . . . . . . . . . . . Name
Text 'description' . . . . . . . > '5291 display station attached to 5294 ctl'

Figure 19-6. Prompt Display for SHM5294 Display Device Description

Notes:
.1/ The Local location address (LOCADR parameter) must match the device
address set at the display station.
.2/ The Attached controller (CTL parameter) must specify the name of the
controller description to which the device is attached (CTLD parameter
on the CRTCTLRWS command).

5394 Remote Control Unit Configuration

The following display shows the configuration for a 5394 Remote Control Unit with
one 5292 display station attached at address 06. See “5294 Remote Control Unit
Configuration” on page 19-5 for information about configuration considerations for
both the 5294 and 5394 controllers.

Chapter 19. X.21 Short-Hold Mode Configuration Example 19-7

à ð
ð 1 2 3 4 5 6
----------------------------------------------------------
ð/ . . . . . . D

1/ . . . . . . .

2/ . . . . . . .

AA-> 2 BB-> ð
1-> ðð 2-> C1 A-> 9732978________ B-> ðF 7 ð
C-> __ __ __ __ __ __ __ __
P-> _ _
á ñ
Figure 19-7. Configuration Display for 5394 Remote Control Unit

Configuring AS/400 Controller and Device Descriptions for the 5394

The following prompt displays use the CRTCTLRWS and CRTDEVDSP commands
to create AS/400 controller and device descriptions for the 5394 Remote Control
Unit and one attached 5292 display station.

See “Configuring AS/400 Controller and Device Descriptions for the 5294” on
page 19-6 for information about specifying these commands for controller and
device descriptions associated with 5x94 controllers.

19-8 Remote Work Station Support V4R1

à ð
Create Ctl Desc (Remote WS) (CRTCTLRWS)

Type choices, press Enter.

Controller description . . . . . > SHM5394 Name

Controller type . . . . . . . . > 5394 3174, 3274, 5251, 5294...
Controller model . . . . . . . . > 1 ð, 1, ððð1, 2, ððð2, 12, ðð12
Link type . . . . . . . . . . . > \SDLC \IDLC, \LAN, \NONE, \SDLC...
Online at IPL . . . . . . . . . > \NO \YES, \NO
Switched connection . . . . . . > \YES \NO, \YES
Short hold mode . . . . . . . . > \YES \NO, \YES
Switched line list . . . . . . . > SHMRWS Name
+ for more values
Maximum frame size . . . . . . . \LINKTYPE 265-1994, 256, 261, 265...
Exchange identifier . . . . . . > ð5FðððC1 ðð1ððððð-FFFFFFFF
Initial connection . . . . . . . \DIAL \DIAL, \ANS
Dial initiation . . . . . . . . \LINKTYPE \LINKTYPE, \IMMED, \DELAY
Connection number . . . . . . . > 9732978
SHM disconnect limit . . . . . . 1ð 1-254, \NOMAX
SHM disconnect timer . . . . . . 5ð 2-3ððð (ð.1 seconds)
More...
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 19-8. Prompt Display for SHM5394 Controller Description

à ð
Create Device Desc (Display) (CRTDEVDSP)

Type choices, press Enter.

Device description . . . . . . . > SHM5394 Name

Device class . . . . . . . . . . > \RMT \LCL, \RMT, \VRT, \SNPT
Device type . . . . . . . . . . > 5292 31ð1, 3151, 3161, 3162...
Device model . . . . . . . . . . > 1 ð, 1, 2, 4, 11, 12, 23...
Local location address . . . . . > ð6 ðð-FE
Online at IPL . . . . . . . . . > \NO \YES, \NO
Attached controller . . . . . . > SHM5394 Name
Drop line at signoff . . . . . . > \NO \YES, \NO
Allow blinking cursor . . . . . \YES \YES, \NO
Printer . . . . . . . . . . . . Name
Text 'description' . . . . . . . > '5292 display station attached to 5394 ctl'

Bottom
F3=Exit F4=Prompt F5=Refresh F1ð=Additional parameters F12=Cancel
F13=How to use this display F24=More keys

á ñ
Figure 19-9. Prompt Display for SHM5394 Display Device Description

Chapter 19. X.21 Short-Hold Mode Configuration Example 19-9

19-10 Remote Work Station Support V4R1
Bibliography
The following books referred to in this book can be Ethernet, and distributed data interface (DDI) local
used for more information on the subject matter. These area networks.
books are listed with their full title and order number.
X.25 Network Support, SC41-5405, contains infor-
mation about using an AS/400 system in an X.25
packet-switched network.
AS/400 Communications Books
APPN Support, SC41-5407, provides the application
programmer with information about the Advanced Other AS/400 Books
Peer-to-Peer Networking (APPN) support provided
3270 Device Emulation Support, SC41-5408, pro-
by the AS/400 system. This guide provides informa-
vides display station operators and programmers
tion for configuring an APPN network and presents
with information about using 3270 device emulation,
considerations to apply when using APPN support.
configuring the device for 3270 device emulation,
APPC Programming, SC41-5443, provides the and creating system device configurations on the
application programmer with information about the host system.
advanced program-to-program communications
DDS Reference, SC41-5712, provides the applica-
(APPC) support provided by the AS/400 system.
tion programmer with detailed descriptions of entries
This is a guide for programming and defining the
and keywords needed to describe database files
communications environment for APPC communi-
and device files external to the user's programs.
cations.
System/36 Environment Programming, SC41-4730,
SNA Distribution Services, SC41-5410, provides the
provides programmers with information on config-
system operator or administrator with information
uring a System/36 and identifying the differences in
about configuring a network for Systems Network
the application process in the System/36 environ-
Architecture distribution services (SNADS) and the
ment on the AS/400 system.
Virtual Machine/Multiple Virtual Storage (VM/MVS)
bridge. CL Reference, SC41-5722, provides the application
programmer with a description of the AS/400 control
ISDN Support, SC41-5403, provides the system
language (CL) and its commands.
administrator, the system programmer, and service
personnel with information about configuring and System/38 Environment Programming, SC41-3735,
using ISDN. provides the programmer with the information
needed to configure a System/38, migrate from a
Communications Management, SC41-5406, pro-
System/38, convert to an AS/400 system, and
vides the system operator with communications
coexist in a network.
work management information, error handling infor-
mation, communications status information, and Work Management, SC41-5306, provides the pro-
communications performance information. grammer with information about how to create and
change a work management environment. This
Communications Configuration, SC41-5401, pro-
guide describes tuning the system, collecting per-
vides the application programmer with information
formance data, working with system values, and
on configuring line, controller, and device
how to evaluate system use.
descriptions to communicate within a network.
Additional configuration considerations are dis- System API Reference, SC41-5801, provides infor-
cussed. mation for the experienced programmer on how to
use the application programming interfaces (APIs)
TCP/IP Configuration and Reference, SC41-5420,
to such OS/400 functions as:
provides information for configuring and using the
AS/400 TCP/IP support. The applications included – Database files
are Network Status (NETSTAT), Packet InterNet – Message handling
Groper (PING), TELNET, File Transfer Protocol
(FTP), Simple Mail Transfer Protocol (SMTP), line – Security
printer requester (LPR), and line printer daemon – Spooled files
(LPD). The TCP and UDP Pascal application
program interface (API) is also discussed. – Network management

LAN and Frame Relay Support, SC41-5404, – User interface

describes the AS/400 support for IBM Token-Ring, – User object

– User-defined communications 3174 Establishment Controller Utilities Guide Con-
figuration Support A and S, Release 5, GA27-3853
– Work management
3270 Information Display System–3274 Control Unit
Some of the APIs provide an alternative to the CL
Description and Programmer’s Guide, GA23-0061
commands.
3274 Configuration Level D Support, GA23-0065
5394 Remote Control Unit User's Guide,
Non-AS/400 Books GA27-3852
VTAM Network Implementation Guide Version 4 5394 Remote Control Unit Type 2.1 Node Support
Release 1 for MVS/ESA, SC31-6419 RPQ 8Q0775, SC30-3531
VTAM Resource Definition Reference Version 4 5494 Remote Control Unit Attachment to Subarea
Release 1 for MVS/ESA, SC31-6427 Network RPQ 8Q0932, SC30-3566
NCP, SSP, EP Resource Definition Guide NCP 5494 Remote Control Unit Planning Guide,
Version 7 Release 1, SSP Version 4 Release 1, EP GA27-3936
Release 12, SC31-6223
5494 Remote Control Unit User's Guide,
ACF/VTAM General Information, GC38-0254 GA27-3960
ACF/VTAM System Programmer's Guide,
SC38-0258
Host Command Facility: Diagnostic Reference,
Redbooks
LY38-3061 Note: Books produced by the International Technical
Support Organization (books with form numbers
Host Command Facility: Guide and Reference,
GG24-xxxx) are not formally tested and are not
SC27-0455
updated. These manuals are written for a spe-
NCP, SSP, EP Resource Definition Guide, cific release of the OS/400 licensed program
SC30-3447 and may not discuss all of the functions avail-
NCP, SSP, EP Resource Definition Reference, able on your AS/400 system.
SC30-3448 AS/400 Communications Definitions Examples,
Network Program Products General Information, GG24-3449.
GC30-3350 AS/400 Communications Definitions Examples II,
Network Program Products Planning, SC30-3351 GG24-3763.

Network Routing Facility Migration, Resource Defi- AS/400 Communications Definitions Examples III,
nition, and Customization, SC31-6203 GG24-4386.

Using S/36 Communications Guide, SC21-9082 AS/400 Network Routing Facility, GG24-3918.

VTAM Resource Definition Reference, SC31-6412 AS/400 SNA Pass-Through Communications and
Examples GG24-3919.
3174 Establishment Controller Planning Guide Con-
figuration Support A and S, Release 5, GA27-3844 AS/400 SNA Primary LU Support Configuration
Guide GG24-4058.
3174 Establishment Controller Planning Guide Con-
figuration Support B, Release 3, GA27-3862 5494 and OS/2: Connectivity to AS/400
GG24-3828.

X-2 Remote Work Station Support V4R1

Index
3270 Remote Control Unit (continued)
Special Characters remote attachment 12-1
*APPINIT value 17-11 SNA pass-through 13-3
See also application type (APPTYPE) parameter System Request key 12-7
*CTLSSN value 17-11 transmission limitations 12-8
See also application type (APPTYPE) parameter twinaxial controllers 13-1
*DEVINIT value 17-11 3274 Control Unit
See also application type (APPTYPE) parameter configuration example 19-3
SNA support 12-1
3287 printer
Numerics 3270 remote attachment 12-4
3174 Establishment Controller
SCS (SNA character string) session 17-2
automatic configuration 13-8
SNA character string (SCS) session 17-2
DBCS-capable work stations 13-11
3720 Communication Controller 17-4
display configuration 13-6
3745 Communication Controller
example configuration 13-1
NCP definitions 16-13, 17-23
SNA support 12-1
5250 display station
VTAM definitions 16-16, 17-26
communications 9-1
3270 display emulation
configuration example 9-14
See also 3270 display station pass-through
definition 15-1
ending 13-4
5250 optimization
starting 13-2
3270 device support 12-1
3270 display station
Distributed Host Command Facility 15-4
definition 15-1
Network Routing Facility 16-1
DHCF use 15-13
SPLS 17-4
using 15-2
5250 pass-through
3270 display station pass-through
See display station pass-through
ending 13-4
5250 Remote Control Unit
starting 13-2
coaxial controllers 9-1
using 13-2
configuration examples 9-1
3270 remote attachment
functions 12-7
keyboard changes 12-5
5292 color graphics display station 3-5
messages 12-11
5294 Remote Control Unit
overview 12-1
emulation mode 9-3
3270 Remote Control Unit
Model K01 9-15
See also 3270 remote attachment
Model S01 9-15
AID (attention identifier) 12-18
5394 Remote Control Unit
configuration examples 13-1
attaching DBCS-capable devices 9-14
controllers 12-1
automatic configuration 10-1
data stream capabilities 13-5
configuration display 9-3
DBCS configuration example 13-11
configuring 9-2, 19-8
DBCS-capable device attachment 13-11
controller description 9-4
embedded attributes 12-10
SDLC connection 9-1
error message limitations 12-8
Type 2.1
error messages 12-11
APPN network 10-2
field attributes 12-12
configuring controller and its work stations 10-6
graphic display attributes 12-10
configuring the AS/400 system to
help support 12-11
communicate 10-4
Home and Erase keys 12-7
peer network 10-3
keyboard differences 12-5, 12-6
SNA subarea network 10-1
keyboard mapping 12-7, 12-13
using 10-8
message codes 12-12

5494 Remote Control Unit address (ADDR) parameter 15-6
APPC subsystem required 11-17 addressing
attaching DBCS-capable devices 9-14 definition 15-9
Attachment to Subarea Network RPQ ADDWSE (Add Work Station Entry) command 6-9
configuration instructions 11-4, 11-5 Advanced Peer-to-Peer Networking (APPN) support
automatic configuration 11-3 configuring a System/38 8-9
configuring definition 3-1
APPC controller description 11-5 network use 4-1
dependent work station 11-9, 11-10 pass-through commands 1-2
instructions 11-3 pass-through considerations 7-11
line description 11-5 advanced program-to-program communications (APPC)
remote work station controller description 11-7 active subsystem 11-17
SDLC example 11-11 configuring controller 11-5
SDLC matching parameters 11-11 connection devices 4-6
SNA host controller description 11-6 definition 3-1
subarea attachment 11-4, 11-5 mode 4-4
token-ring attachment example 11-14 pass-through considerations 7-11
token-ring attachment matching security 7-3
parameters 11-15 specifying devices 1-2
X.25 example 11-12 subsystem 11-17
X.25 matching parameters 11-13 AID (attention identifier) key 12-18
default mode 11-4 alternate job
managing 11-16 home system 5-6
mode previous system 5-7
BLANK mode 11-4 transferring from 5-4
default 11-4 transferring to 5-5
QRMTWSC mode 11-4 alternate printer 17-15
subsystem 11-17 API (application program interface)
system reference code 11-17 QDCRDEVD (Retrieve Device Description) 17-15,
token-ring attachment configuration 17-19
example 11-14 Retrieve Device Description (QDCRDEVD) 17-15,
illustration 11-3 17-19
matching parameters 11-15 APPC (advanced program-to-program communications)
token-ring gateway configuration active subsystem 11-17
illustration 11-2 configuring controller 11-5
5553 printer connection devices 4-6
5394 configuration 9-16 definition 3-1
device description 9-16 mode 4-4
8100 HCF network 15-2 pass-through considerations 7-11
security 7-3
specifying devices 1-2
A subsystem 11-17
adapter card APPC device (CNNDEV) parameter 4-5
PS/55 9-14 default 4-6
Remote 5250 Work Station Adapter 9-14 specifying 4-5
Add Communications Entry (ADDCMNE) value 4-8
command 6-10 application program interface (API)
ADD MASTER control statement 15-11 QDCRDEVD (Retrieve Device Description) 17-15,
Add Work Station Entry (ADDWSE) command 6-9 17-19
ADDCMNE (Add Communications Entry) Retrieve Device Description (QDCRDEVD) 17-15,
command 6-10 17-19
adding application type (APPTYPE) parameter
communications entry 6-10 *APPINIT value 17-16, 17-17
work station entry 6-9 *CTLSSN value 17-12
ADDR (address) parameter 15-6 *DEVINIT value 17-15, 17-18
*NRF value 16-5

X-4 Remote Work Station Support V4R1

application type (APPTYPE) parameter (continued) attribute (continued)
network routing facility (NRF) 16-5 3278 12-4
overview 17-11 3279 12-4
SNA Primary LU2 Support (SPLS) 17-11 blink 12-13
APPN (Advanced Peer-to-Peer Networking) support autoconfigure virtual device (QAUTOVRT) system
configuring a System/38 8-9 value 3-2
definition 3-1 autocreate
network use 4-1 See automatic creation
pass-through commands 1-2 autocreate device (AUTOCRTDEV) parameter
pass-through considerations 7-11 3270 devices 13-8
APPN connections 5250 devices 10-6, 11-9
VTAM definitions 18-8 SNA host controller description 17-11
APPN network SPLS considerations 17-6
configuring 8-9 AUTOCRTDEV (autocreate device) parameter
APPTYPE (application type) parameter 3270 devices 13-8
*APPINIT value 17-16, 17-17 5250 devices 10-6, 11-9
*CTLSSN value 17-12 SNA host controller description 17-11
*DEVINIT value 17-15, 17-18 SPLS considerations 17-6
*NRF value 16-5 autodelete device (AUTODLTDEV) parameter 17-7
network routing facility (NRF) 16-5 AUTODLTDEV (autodelete device) parameter 17-7
overview 17-11 automatic configuration 18-2
SNA Primary LU2 Support (SPLS) 17-11 5394 Type 2.1 Remote Control Unit 10-1
AS/400 system 5494 Remote Control Unit 11-3
3270 requirements 15-13 considerations 3-2
attached to a System/38 8-9 display station pass-through 3-2
configuring requesting 4-9
5394 Remote Control Unit support 9-4 requesting from System/36 7-2
5394 Remote Control Unit Type 2.1 security 7-1
support 10-4 TELNET 3-6
5494 Remote Control Unit subarea automatic creation
attachment 11-4 3174 Remote Control Unit 13-8
5494 Remote Control Unit support 11-1 3270 devices 13-8
display station pass-through 3-1 5250 devices 10-6, 11-9
distributed host command facility (DHCF) 15-8 device description 17-6, 17-11
network routing facility (NRF) 16-4 SPLS considerations 17-6
SNA pass-through 14-1 automatic remote controller (QAUTORMT) system
SNA Primary LU2 Support (SPLS) 17-8 value 10-1
X.21 short-hold mode (SHM) 19-1 automatic sign-on
connection device 4-5 considerations 7-7
differences from System/36 DHCF 15-15 examples 7-6
differences from System/38 DHCF 15-15 parameters 7-4
ending DHCF sessions 15-12 restriction 7-7
HCF definition 15-2 security officer 7-1
host system work sheet 15-7 target system 7-2
logging on host 15-10 using STRPASTHR 7-3
NCCF/TAF network 15-1 automatic startup
port sharing configuration 19-1 pass-through servers 2-1
remote system 15-1
starting DHCF sessions 15-12
VTAM/NCP support 15-6 B
associated printer 17-15 Begin Pass-Through (BGNPASTHR) command 7-12
attachment, 3270 remote 12-1 BGNPASTHR (Begin Pass-Through) command 7-12
attention identifier (AID) key 12-18 bibliography X-1
Attn key 13-4 BLANK mode 11-4
attribute blink attribute 12-13
3270 12-13

Index X-5
book list X-1 CNNDEV (APPC device) parameter 4-5
break mode 12-11 default 4-6
specifying 4-5
value 4-8
C command prompt 9-5
CCITT (International Telegraph and Telephone command, CL
Consultative Committee) 3270 keyboard mapping 12-13
Recommendation Add Communications Entry (ADDCMNE) 6-10
X.25 15-3 Add Work Station Entry (ADDWSE) 6-9
Change Communications Entry (CHGCMNE) ADDCMNE (Add Communications Entry) 6-10
command 6-10 ADDWSE (Add Work Station Entry) 6-9
Change Device Description (Display) (CHGDEVDSP) Begin Pass-Through (BGNPASTHR) 7-12
command 16-5 BGNPASTHR (Begin Pass-Through) 7-12
Change Device Description (Printer) (CHGDEVPRT) Change Communications Entry (CHGCMNE) 6-10
command 16-5 Change Device Description (Display)
Change Keyboard Map (CHGKBDMAP) (CHGDEVDSP) 16-5
command 12-7, 12-16 Change Device Description (Printer)
CHANGE MASTER control statement 15-11 (CHGDEVPRT) 16-5
Change Mode Description (CHGMODD) command Change Keyboard Map (CHGKBDMAP) 12-7,
5494 setup 11-4 12-16
Change RWS Controller Password (CHGRWSPWD) Change System Value (CHGSYSVAL) 3-2
command 11-18 CHGCMNE (Change Communications Entry) 6-10
Change System Value (CHGSYSVAL) command 3-2 CHGDEVDSP (Change Device Description
changing (Display)) 16-5
communications entry 6-10 CHGDEVPRT (Change Device Description
device description (display) 16-5 (Printer)) 16-5
device description (printer) 16-5 CHGKBDMAP (Change Keyboard Map) 12-7,
keyboard map 12-7, 12-16 12-16
QAUTOVRT (autoconfigure virtual device) system CHGSYSVAL (Change System Value) 3-2
value 3-2 configuration 9-11
system value 3-2 Create Class (CRTCLS) 6-11
CHGCMNE (Change Communications Entry) Create Control Unit Description (CRTCUD) 3-4
command 6-10 Create Controller Description (Remote Work Station)
CHGDEVDSP (Change Device Description (Display)) (CRTCTLRWS)
command 16-5 3270 controllers 13-7
CHGDEVPRT (Change Device Description (Printer)) 5394 configuration 9-7
command 16-5 5394 type 2.1 configuration 10-6
CHGKBDMAP (Change Keyboard Map) 5494 configuration 11-7
command 12-7, 12-16 X.21 short-hold mode (SHM) 19-3
CHGMODD (Change Mode Description) command Create Controller Description (SNA Host)
5494 setup 11-4 (CRTCTLHOST)
CHGRWSPWD (Change RWS Controller Password) 5394 type 2.1 configuration 10-4
command 11-18 5494 configuration 11-6
CHGSYSVAL (Change System Value) command 3-2 NRF configuration 16-6
class SPLS configuration 17-9
creating 6-11 Create Controller Description (Virtual Work Station)
class of service (CRTCTLVWS) 3-3
definition 4-3 Create Device Description (Display) (CRTDEVDSP)
Client Access 3270 controllers 13-8
work station function (WSF) 5394 configuration 9-10
automatic sign-on 6-2 NRF 16-5, 16-7
controlling sessions 6-1, 6-2 SNA pass-through 14-5
QAUTOVRT (autoconfigure virtual device) system SPLS 17-11
value 3-2 X.21 short-hold mode (SHM) 19-4
QRMTSIGN (remote sign-on) system value 6-1 Create Device Description (Printer) (CRTDEVPRT)
virtual printer device description 3-5 5394 configuration 9-8
NRF 16-5, 16-7

X-6 Remote Work Station Support V4R1

command, CL (continued) command, CL (continued)
Create Device Description (Printer) (CRTDEVPRT) DSPNETA (Display Network Attributes) 4-1
(continued) DSPSBSD (Display Subsystem Description) 6-9
SPLS 17-11 End Pass-Through (ENDPASTHR) 1-5
Create Line Description (SDLC) (CRTLINSDLC) ENDPASTHR (End Pass-Through) 1-5
5394 configuration 9-5 Set Keyboard Map (SETKBDMAP) 12-7, 12-16
NRF configuration 16-5 SETKBDMAP (Set Keyboard Map) 12-7, 12-16
SPLS configuration 17-9 Sign Off (SIGNOFF)
X.21 short-hold mode (SHM) 19-1 DHCF 15-13
Create Mode Description (CRTMODD) 4-4 display station pass-through 1-6, 7-7
Create User Profile (CRTUSRPRF) 6-9 NRF 16-10
CRTCLS (Create Class) 6-11 SPLS 17-21
CRTCTLHOST (Create Controller Description (SNA SIGNOFF (Sign Off)
Host)) DHCF 15-13
5394 type 2.1 configuration 10-4 display station pass-through 1-6, 7-7
5494 configuration 11-6 NRF 16-10
NRF configuration 16-6 SPLS 17-21
SPLS configuration 17-9 Start 3270 Display Emulation (STREML3270) 13-2
CRTCTLRWS (Create Controller Description Start Pass-Through (STRPASTHR) 1-3, 7-3
(Remote Work Station)) Start Subsystem (STRSBS) 6-9
3270 controllers 13-7 STREML3270 (Start 3270 Display Emulation) 13-2
5394 configuration 9-7 STRPASTHR (Start Pass-Through) 1-3, 7-3
5394 type 2.1 configuration 10-6 STRSBS (Start Subsystem) 6-9
5494 configuration 11-7 TFRPASTHR (Transfer Pass-Through) 5-5
X.21 short-hold mode (SHM) 19-3 Transfer Pass-Through (TFRPASTHR) 5-5
CRTCTLVWS (Create Controller Description (Virtual Work with Configuration Lists (WRKCFGL) 4-1
Work Station)) 3-3 Work with Hardware Resources
CRTCUD (Create Control Unit Description) 3-4 (WRKHDWRSC) 9-5
CRTDEVDSP (Create Device Description (Display)) WRKCFGL (Work with Configuration Lists) 4-1
3270 controllers 13-8 WRKHDWRSC (Work with Hardware
5394 configuration 9-10 Resources) 9-5
NRF 16-5, 16-7 command, VTAM
SNA pass-through 14-5 LOGON (logon) 17-20
SPLS 17-11 communications entry
X.21 short-hold mode (SHM) 19-4 adding 6-10
CRTDEVPRT (Create Device Description (Printer)) changing 6-10
5394 configuration 9-8 communications protocol 12-1
NRF 16-5, 16-7 configuration
SPLS 17-11 host controller 18-4
CRTLINSDLC (Create Line Description (SDLC)) configuration list
5394 configuration 9-5 working with 4-1
NRF configuration 16-5 configuring
SPLS configuration 17-9 3270 Remote Control Unit
X.21 short-hold mode (SHM) 19-1 attaching DBCS-capable devices 13-11
CRTMODD (Create Mode Description) 4-4 example 13-1
CRTUSRPRF (Create User Profile) 6-9 3274 Control Unit 19-3
Display Device Description (DSPDEVD) 5250 work station communications
*DEVINIT application type 17-15, 17-19 attaching DBCS-capable devices 9-14
virtual device description 3-5 automatic connection 9-12
Display Keyboard Map (DSPKBDMAP) 12-7, 12-14 controller description 9-7
Display Network Attributes (DSPNETA) 4-1 display device description 9-10
Display Subsystem Description (DSPSBSD) 6-9 line description 9-5
DSPDEVD (Display Device Description) overview 9-1
*DEVINIT application type 17-15, 17-19 printer device description 9-8
virtual device description 3-5 remote devices 9-2
DSPKBDMAP (Display Keyboard Map) 12-7, 12-14 remote work station controller 9-12
using CL commands 9-11

Index X-7
configuring (continued) configuring (continued)
5250 work station communications (continued) display station pass-through (continued)
using command prompts 9-5 instructions 3-1
5394 Remote Control Unit keyboard language type (KBDTYPE)
attaching DBCS-capable devices 9-14 parameter 3-5
automatic connection 9-12 manually 3-3
controller description 9-7 matching source and target display station 3-4
display device description 9-10 personal computer display station 3-5
line description 9-5 scenario 8-1
printer device description 9-8 security considerations 3-6
remote devices 9-2 subsystem 3-7
remote work station controller 9-12 system configuration example 4-6
using CL commands 9-11 virtual controller 3-1
using command prompts 9-5 virtual device 3-3
5394 Remote Control Unit and its work virtual display station 3-4
stations 10-6 virtual printer 3-5
5494 Remote Control Unit distributed host command facility (DHCF)
APPC controller description 11-5 control language example 15-9
attaching DBCS-capable devices 9-14 controller description 15-9
dependent work station 11-9, 11-10 device description 15-9
instructions 11-3 example 15-9
line description 11-5 host system work sheet 15-7
remote work station controller description 11-7 line description 15-8
SDLC example 11-11 keyboard changes 12-5
SDLC matching parameters 11-11 multiple port sharing 19-1
SNA host controller description 11-6 network nodes 7-12
subarea attachment 11-4, 11-5 remote work station controller
token-ring attachment example 11-14 5250-type controller 9-12
token-ring attachment matching 5394 configuration 9-12
parameters 11-15 X.21 short-hold mode (SHM) 19-3
X.25 example 11-12 short-hold mode (SHM) 19-1
X.25 matching parameters 11-13 SNA pass-through
APPN support 8-11 single AS/400 system 14-4
AS/400 system SNA Primary LU2 Support (SPLS)
5394 Remote Control Unit support 9-4 automatic device description creation 17-6,
5394 Remote Control Unit Type 2.1 17-11
support 10-4 controller description 17-9
5494 Remote Control Unit subarea device description 17-11
attachment 11-4 device description, APPTYPE(*APPINIT) 17-16
5494 Remote Control Unit support 11-1 device description, APPTYPE(*CTLSSN) 17-11
APPN support 8-11 device description, APPTYPE(*DEVINIT) 17-14
display station pass-through 3-1 display device description,
distributed host command facility (DHCF) 15-8 APPTYPE(*APPINIT) 17-16
network routing facility (NRF) 16-4 example display description,
SNA pass-through 14-1 APPTYPE(*CTLSSN) 17-12
SNA Primary LU2 Support (SPLS) 17-8 example display description,
X.21 short-hold mode (SHM) 19-1 APPTYPE(*DEVINIT) 17-14
automatic example host controller description 17-10
3174 13-8 example line description 17-9
5394 Type 2.1 Remote Control Unit 10-1 example printer description,
5494 Remote Control Unit 11-3 APPTYPE(*APPINIT) 17-17
device descriptions 19-3 host controller description 17-9
display device host system 17-19
X.21 short-hold mode (SHM) 19-4 line description 17-8
display station pass-through matching parameters 17-27
automatic 3-2, 4-9 matching parameters, SDLC 17-26
creating user profiles 3-7 overview 17-8

X-8 Remote Work Station Support V4R1

configuring (continued) considerations (continued)
SNA Primary LU2 Support (SPLS) (continued) 5494 Remote Control Unit (continued)
printer device description, APPC subsystem required 11-17
APPTYPE(*DEVINIT) 17-18 attaching DBCS-capable devices 9-14
shared controller 17-8 MAXLENRU (maximum length of request unit)
shared line 17-8 parameter 11-10
steps 17-8 mode description 11-4
TELNET configuration
automatic 3-6 automatic 3-2
virtual controller display station pass-through 3-4
automatically 3-1 NRF, testing 16-10
manually 3-3 SPLS, automatic device description
virtual device creation 17-6, 17-11
automatically 3-1 X.21 short hold mode (SHM), 3274 Control
manually 3-3 Unit 19-3
X.21 short-hold mode (SHM) 19-1 display station pass-through
configuring automatically 18-2 APPC 7-11
configuring ISDN 13-11 APPN support 7-11
connection device (CNNDEV) parameter 4-5 automatic configuration 3-2
See also APPC device (CNNDEV) parameter automatic sign-on 7-7
considerations capabilities 7-1
3270 remote attachment limitations 7-1
*BREAK messages 13-5 manual configuration 3-4
3270 and 5250 displays 12-8 QLMTSECOFR (limit security officer) system
3287 printer 12-4 value 7-1
attaching DBCS-capable devices 13-11 QRMTSIGN programming 6-7
fields 12-9 security 3-6, 7-1
keyboard differences 12-6 System/36 7-2
session start 12-1 work management 6-1
VTAM logon display, emulated 13-4 distributed host command facility (DHCF)
5250-type controller display station 15-14
attaching DBCS-capable devices 9-14 host system programming 15-5
CRTCTLRWS (Create Controller Description keyboard differences 15-14
(Remote Work Station)) command 9-7 keyboard mapping 12-17, 15-14
CRTDEVDSP (Create Device Description NCP generation 15-6
(Display)) command 9-10 starting 15-12
CRTDEVPRT (Create Device Description USSMSG macroinstruction 15-7
(Printer)) command 9-9 VTAM generation 15-6
CRTLINSDLC (Create Line Description (SDLC)) network routing facility (NRF)
command 9-6 ending 16-10
5394 Remote Control Unit LOGON (host signon/logon command)
attaching DBCS-capable devices 9-14 parameter 16-8, 16-9
CRTCTLRWS (Create Controller Description performance 16-3
(Remote Work Station)) command 9-7 printing 16-9
CRTDEVDSP (Create Device Description testing configuration 16-10
(Display)) command 9-10 performance
CRTDEVPRT (Create Device Description network routing facility (NRF) 16-3
(Printer)) command 9-9 SPLS 17-2
CRTLINSDLC (Create Line Description (SDLC)) security
command 9-6 display station pass-through 3-6, 7-1
5394 Type 2.1 Node Support QLMTSECOFR (limit security officer) system
APPC device description 10-5 value 7-1
CRTCTLRWS (Create Controller Description SNA pass-through
(Remote Work Station)) command 10-6 crossing configurations 14-4
programmable work stations 10-7 group list 14-2
5494 Remote Control Unit grouping upstream devices 14-2
APPC device description 11-5 inactivity timer 14-2

Index X-9
considerations (continued) Create Controller Description (SNA Host)
SNA pass-through (continued) (CRTCTLHOST) command (continued)
line-drop timer 14-6 5394 type 2.1 configuration 10-4
network management 14-4 5494 configuration 11-6
switched lines 14-6 NRF configuration 16-6
SNA Primary LU2 Support (SPLS) SPLS configuration 17-9
application type (APPTYPE) parameter 17-11 Create Controller Description (Virtual Work Station)
APPTYPE(*DEVINIT) 17-11 (CRTCTLVWS) command 3-3
automatic device description creation 17-6, Create Device Description (Display) (CRTDEVDSP)
17-11 command
display device, APPTYPE(*APPINIT) 17-16 3270 controllers 13-8
inactivity timer 17-15, 17-16 5394 configuration 9-10
keyboard map 17-20 5494 configuration 11-9, 11-10
multiple host lines 17-12, 17-18 NRF 16-5, 16-7
performance 17-2 SNA pass-through 14-5
printer device, APPTYPE(*DEVINIT) 17-18 SPLS 17-11
printing 17-21 X.21 short-hold mode (SHM) 19-4
starting 17-20 Create Device Description (Printer) (CRTDEVPRT)
work management command
display station pass-through 6-1 5394 configuration 9-8
X.21 short hold mode (SHM) 5494 configuration 11-9, 11-10
3274 Control Unit configuration 19-3 NRF 16-5, 16-7
CRTCTLRWS command 19-4, 19-6 SPLS 17-11
control session device description 17-15, 17-19 Create Line Description (SDLC) (CRTLINSDLC)
control statement command
ADD MASTER 15-11 5394 configuration 9-5
CHANGE MASTER 15-11 NRF configuration 16-5
control unit description (System/38) SPLS configuration 17-9
creating 3-4 X.21 short-hold mode (SHM) 19-1
controller Create Mode Description (CRTMODD) command 4-4
configuring 19-3 Create Printer for SPLS (TNXCRTPT) tool 17-21
creating descriptions 9-7 Create User Profile (CRTUSRPRF) command 6-9
twinaxial 9-1 creating
virtual 3-1 class 6-11
controller description controller description (APPC)
automatic configuration 9-12 5494 configuration 11-5
creating 16-6 controller description (remote work station)
controller description (Remote Work Station) 3270 controllers 13-7
creating 9-7 5394 configuration 9-7
controller description (Virtual Work Station) 5394 type 2.1 configuration 10-6
creating 3-3 5494 configuration 11-7
Create Class (CRTCLS) command 6-11 X.21 short-hold mode (SHM) 19-3, 19-6
Create Control Unit Description (CRTCUD) controller description (SNA host) 17-9
command 3-4 5394 type 2.1 configuration 10-4
Create Controller Description (APPC) (CRTCTLAPPC) 5494 configuration 11-6
command NRF configuration 16-6
5494 configuration 11-5 SPLS configuration 17-10
Create Controller Description (Remote Work Station) controller description (Virtual Work Station) 3-3
(CRTCTLRWS) command device description (display)
3270 controllers 13-7 3270 controllers 13-8
5394 configuration 9-7 5394 configuration 9-10
5394 type 2.1 configuration 10-6 5394 type 2.1 configuration 10-7
5494 configuration 11-7 5494 configuration 11-9
X.21 short-hold mode (SHM) 19-3 DBCS-capable 13-11
Create Controller Description (SNA Host) NRF configuration 16-5, 16-7
(CRTCTLHOST) command SNA pass-through configuration 14-5, 14-10
SPLS, APPTYPE(*CTLSSN) 17-12

X-10 Remote Work Station Support V4R1

creating (continued) CRTLINSDLC (Create Line Description (SDLC))
device description (display) (continued) command
SPLS, APPTYPE(*DEVINIT) 17-14 5394 configuration 9-5
X.21 short-hold mode (SHM) 19-4, 19-7 NRF configuration 16-5
device description (printer) SPLS configuration 17-9
3270 controllers 13-8 X.21 short-hold mode (SHM) 19-1
5394 configuration 9-8 CRTMODD (Create Mode Description) command 4-4
NRF configuration 16-5, 16-7 CRTUSRPRF (Create User Profile) command 6-9
SPLS, APPTYPE(*APPINIT) 17-17 current library (RMTCURLIB) parameter 7-6
device description (SNPT)
SNA pass-through configuration 14-4, 14-8
line description (SDLC) D
5394 configuration 9-5 DBCS (double-byte character set)
NRF configuration 16-5 configuration example 9-14
SPLS configuration 17-9 DBCS feature (IGCFEAT) parameter 13-11
X.21 short-hold mode (SHM) 19-1 DBCS-capable device
line description (token-ring) 3270 controller attachment 13-11
3270 controllers 13-6 attaching to 5250 controllers 9-14
mode description 4-4 Dependent LU Requester
user profile 6-9 definition 18-1
CRTCLS (Create Class) command 6-11 Dependent LU Requester support 18-1
CRTCTLAPPC (Create Controller Description (APPC)) DEVCLS (device class) parameter
command network routing facility (NRF) 16-5
5494 configuration 11-5 SNA Primary LU2 Support (SPLS)
CRTCTLHOST (Create Controller Description (SNA display device description 17-12, 17-14
Host)) command printer device description 17-17, 17-18
5394 type 2.1 configuration 10-4 DEVD (device description) parameter 16-5, 17-12
5494 configuration 11-6 device
NRF configuration 16-6 connection configuration 4-7
SPLS configuration 17-9 connection specification 4-5
CRTCTLRWS (Create Controller Description (Remote creating 3-2
Work Station)) command emulation 15-13
3270 controllers 13-7 manual configuration 3-3
5394 configuration 9-7 printer description 9-8
5394 type 2.1 configuration 10-6 security considerations 3-6
5494 configuration 11-7 sign-on security 7-1
X.21 short-hold mode (SHM) 19-3 TELNET configuration 3-6
CRTCTLVWS (Create Controller Description (Virtual virtual
Work Station)) command 3-3 configuring 3-1, 3-3
CRTCUD (Create Control Unit Description) virtual, specifying 4-9
command 3-4 device class (DEVCLS) parameter
CRTDEVDSP (Create Device Description (Display)) network routing facility (NRF) 16-5
command SNA Primary LU2 Support (SPLS)
3270 controllers 13-8 display device description 17-12, 17-14
5394 configuration 9-10 printer device description 17-17, 17-18
5494 configuration 11-9, 11-10 device description
NRF 16-5, 16-7 configuring
SNA pass-through 14-5 display 19-3
SPLS 17-11 remote work station 19-3
X.21 short-hold mode (SHM) 19-4 displaying
CRTDEVPRT (Create Device Description (Printer)) *DEVINIT application type 17-15, 17-19
command virtual 3-5
5394 configuration 9-8 retrieving 17-15, 17-19
5494 configuration 11-9, 11-10 device description (DEVD) parameter 16-5, 17-12
NRF 16-5, 16-7 device description (display)
SPLS 17-11 changing 16-5

Index X-11
device description (display) (continued) display station pass-through (continued)
creating configuring (continued)
5394 configuration 9-8, 9-10 instructions 3-1
NRF configuration 16-5, 16-7 keyboard language type (KBDTYPE)
device description (printer) parameter 3-5
changing 16-5 manually 3-3
device model (MODEL) parameter matching source and target display station 3-4
network routing facility (NRF) 16-5 personal computer display station 3-5
SNA Primary LU2 Support (SPLS) QAUTOVRT (autoconfigure virtual device) system
3287 printer 17-17, 17-18 value 3-2
display device description 17-12, 17-14 QMAXSIGN (maximum sign-on attempts allowed)
device type (TYPE) parameter system value 3-6
network routing facility (NRF) 16-5 QPACTL00 virtual controller 3-3
SNA Primary LU2 Support (SPLS) QRMTSIGN (remote sign-on) system value 6-1
3287 printer 17-17, 17-18 scenario 8-1
display device description 17-12, 17-14 security considerations 3-6
DHCF (distributed host command facility) subsystem 3-7
3270 requirements 15-13 virtual display station 3-4
AS/400 system and System/36 differences 15-15 virtual printer 3-5
AS/400 system and System/38 differences 15-15 considerations 7-1
configuration description 15-8 creating user profiles 3-7
display station considerations 15-14 end system
ending sessions 15-12 definition 5-4
environment description 15-2 end user instructions 1-1
host system operating requirement 15-1 ending
keyboard mapping 12-13 End Pass-Through (ENDPASTHR) 1-5
remote management 15-10 ENDPASTHR (End Pass-Through) 1-5
running 15-5 Sign Off (SIGNOFF) command 1-6
starting sessions 15-12 SIGNOFF (Sign Off) command 1-6
USSMSG macroinstruction 15-7 home system
MSG=10 operand not supported 15-7 definition 5-4
DISCNT (disconnect) parameter 15-6 illustration 1-1
disconnect (DISCNT) parameter 15-6 keyboard language type (KBDTYPE) parameter 3-5
display manual configuration 3-3
characters and symbols 12-9 matching source and target display station 3-4
Create Controller Description (SNA Host) 18-5 message handling 7-2
CRTCTLHOST 18-5 multiple product network 8-12
graphic attributes 12-10 non-APPN support use 1-4
Start Pass-Through 7-3 personal computer display station 3-5
Display Device Description (DSPDEVD) command program, option 10 (SRQ10PGM) 5-7
*DEVINIT application type 17-15, 17-19 QAUTOVRT (autoconfigure virtual device) system
virtual device description 3-5 value 3-2
Display Keyboard Map (DSPKBDMAP) QMAXSIGN (maximum sign-on attempts allowed)
command 12-7, 12-14 system value 3-6
display logon mode (DLOGMOD) parameter 15-7 QPACTL00 virtual controller 3-3
Display Network Attributes (DSPNETA) command 4-1 QRMTSIGN (remote sign-on) system value 6-1
display option (PASTHRSCN) parameter 7-7 rejection 6-2
display station security
considerations 15-14 automatic sign-on 7-6
display station pass-through considerations 3-6, 7-1
See also 3270 display station pass-through creating user profiles 3-7
automatic configuration 3-2 password verification 6-1
automatic sign-on 7-2 user profile 6-8
concepts 1-1 Sign Off (SIGNOFF) command 1-6
configuring end connection (ENDCNN) parameter 1-6
automatically 3-2 sign-on attempts, examples 7-8
creating user profiles 3-7

X-12 Remote Work Station Support V4R1

display station pass-through (continued) displaying (continued)
starting keyboard map 12-7, 12-14
APPN support, with 1-3 network attributes 4-1
APPN support, without 1-4 subsystem description 6-9
automatic sign-on 7-3 distributed host command facility (DHCF)
CNNDEV (APPC device) parameter 4-5 3270 requirements 15-13
current library (RMTCURLIB) parameter 7-6 AS/400 system and System/36 differences 15-15
display option (PASTHRSCN) parameter 7-7 AS/400 system and System/38 differences 15-15
example 4-7 configuration description 15-8
initial menu (RMTINLMNU) parameter 7-5 display station considerations 15-14
initial program to call (RMTINLPGM) ending sessions 15-12
parameter 7-5 environment description 15-2
LCLLOCNAME (local location) parameter 4-4 host system operating requirement 15-1
local location (LCLLOCNAME) parameter 4-4 keyboard mapping 12-13
MODE parameter 4-4 remote management 15-10
overview 1-3 running 15-5
PASTHRSCN (display option) parameter 7-7 starting sessions 15-12
remote location (RMTLOCNAME) parameter 1-1, USSMSG macroinstruction 15-7
4-1 MSG=10 operand not supported 15-7
remote network identifier (RMTNETID) DLOGMOD (display logon mode) parameter 15-7
parameter 4-5 DLUR
RMTCURLIB (current library) parameter 7-6 definition 18-1
RMTINLMNU (initial menu) parameter 7-5 example 18-11
RMTINLPGM (initial program to call) DLUR support 18-1
parameter 7-5 VTAM definitions 18-8
RMTLOCNAME (remote location) parameter 1-1, double-byte character set (DBCS)
4-1 configuration example 9-14
RMTNETID (remote network identifier) DROP (drop line at signoff) parameter 17-15
parameter 4-5 drop line at signoff (DROP) parameter 17-15
RMTPWD (user password) parameter 7-5 DSPDEVD (Display Device Description) command
RMTUSER (user profile) parameter 7-4, 7-5 *DEVINIT application type 17-15, 17-19
SRQ10PGM (system request program) virtual device description 3-5
parameter 5-7 DSPKBDMAP (Display Keyboard Map)
system request program (SRQ10PGM) command 12-7, 12-14
parameter 5-7 DSPNETA (Display Network Attributes) command 4-1
user password (RMTPWD) parameter 7-5 DSPSBSD (Display Subsystem Description)
user profile (RMTUSER) parameter 7-4, 7-5 command 6-9
virtual controller (VRTCTL) parameter 4-9 DSPT (display station pass-through)
virtual display device (VRTDEV) parameter 4-10 See display station pass-through
VRTCTL (virtual controller) parameter 4-9
VRTDEV (virtual display device) parameter 4-10
starting and ending 4-1 E
subsystem 3-7 embedded attribute
System Request 3270 12-10
using options 5-6 emulation
System/36 7-2 3270
using subsystems 6-8 ending 13-4
virtual display station 3-4 starting 13-2
virtual printer 3-5 5294 9-3
work management considerations 6-1 ENCR (encryption) parameter 15-7
Display Subsystem Description (DSPSBSD) encryption (ENCR) parameter 15-7
command 6-9 End Communications Server (ENDCMNSVR)
displaying command 2-1
device description end connection (ENDCNN) parameter
*DEVINIT application type 17-15, 17-19 DHCF 15-13
virtual 3-5 display station pass-through 1-6

Index X-13
end connection (ENDCNN) parameter (continued) example (continued)
NRF 16-10 pass-through 8-1
SPLS 17-21 configuration 8-1
End Pass-Through (ENDPASTHR) command 1-5 environment 1-1
end system programming specification 6-2
definition 5-4 PS/55 attached to 3270 controller 13-11
end user instruction 1-1 PS/55 attached to 5250 controller 9-14
ENDCNN (end connection) parameter remote work station communications 9-1
DHCF 15-13 SDLC configuration 11-11
display station pass-through 1-6 sign-on attempt 7-8
NRF 16-10 sign-on program 6-4
SPLS 17-21 SNA pass-through configuration 14-4
ending AS/400 system 14-13
3270 display emulation 13-4 intermediate AS/400 node 14-8
3270 display station pass-through 13-4 mixture of 5250 and 327x devices 14-11
DHCF session 15-12 SNA Primary LU2 Support (SPLS)
NRF (Network Routing Facility) 16-10 controller description 17-10
pass-through 1-5 display description, APPTYPE(*CTLSSN) 17-12
SNA Primary LU2 Support (SPLS) session 17-21 display description, APPTYPE(*DEVINIT) 17-14
SPLS (SNA Primary LU2 Support) session 17-21 host controller description 17-10
ENDPASTHR (End Pass-Through) command 1-5 line description 17-9
Erase key 12-7 printer description, APPTYPE(*APPINIT) 17-17
error message 12-11 SPLS (SNA Primary LU2 Support)
example controller description 17-10
3174 Establishment Controller 13-1 display description, APPTYPE(*CTLSSN) 17-12
3270-type remote work station display description, APPTYPE(*DEVINIT) 17-14
communications 13-1 host controller description 17-10
3274 Control Unit configuration 19-3 line description 17-9
5250 remote work station communications 9-1 printer description, APPTYPE(*APPINIT) 17-17
5494 configuration starting pass-through without APPN support 4-7
device description 11-10 system configuration 4-6
5494 Remote Control Unit System/38 configuration 8-9
SDLC configuration 11-11 token-ring attachment configuration 11-14
SDLC matching parameters 11-11 X.21 short-hold mode configuration 19-1
token-ring attachment configuration 11-14 X.25 configuration 11-12
token-ring attachment matching exchange identifier (XID) parameter 15-6
parameters 11-15
X.25 configuration 11-12
X.25 matching parameters 11-13 F
AS/400 system field
configuration 8-10 attributes, 3270 12-12
automatic sign-on 7-6 exit fields 12-6
CNNDEV network 4-7
configuration series 8-1
DBCS-capable device configuration 9-15
G
graphic display attributes, 3270 12-10
device description 18-6
DHCF keyboard map 12-16
display station pass-through 7-8
DLUR 18-11
H
hardware resources
host controller description 18-5 working with 9-5
job connection status symbol 13-4 HCF (Host Command Facility)
location name networking 4-2 command summary 15-13
logon mode table compared to NRF 16-1
Network Routing Facility 16-10 definition 15-1
SPLS 17-21 environment description 15-2
low-entry network nodes 7-11

X-14 Remote Work Station Support V4R1

HCF (Host Command Facility) (continued) INACTTMR (inactivity timer) parameter
host considerations 15-5 display device description 17-15, 17-16
introduction 15-1 printer device description 17-17, 17-18
network system types 15-2 initial menu (RMTINLMNU) parameter 7-5
network types initial program to call (RMTINLPGM) parameter 7-5
8100 15-2 intermediate node
Series/1 system 15-2 definition 14-1
System/38 15-2 intermediate system
running 15-5 definition 4-6
SNA Primary LU2 Support (SPLS) comparison 17-2 International Telegraph and Telephone Consultative
SPLS (SNA Primary LU2 Support) comparison 17-2 Committee (CCITT)
Home key 12-7 Recommendation
home system X.25 15-3
definition 5-4 ISTATUS (inactive status) parameter 15-6
Host Command Facility (HCF) ITU-T (Telecommunications Standardization Sector)
command summary 15-13 former CCITT (International Telegraph and Tele-
compared to NRF 16-1 phone Consultative Committee) 15-3
definition 15-1
environment description 15-2
host considerations 15-5 J
introduction 15-1 job
network system types 15-2 alternate
network types home system 5-6
8100 15-2 previous system 5-7
Series/1 system 15-2 transferring from 5-4
System/38 15-2 transferring to 5-5
running 15-5 control 5-5, 5-6
SNA Primary LU2 Support (SPLS) comparison 17-2 description, creating 6-9
SPLS (SNA Primary LU2 Support) comparison 17-2 logs 1-5
host controller description
configuring 18-4
example 18-5
K
KBDTYPE (keyboard language type) parameter 3-5
host signon/logon command (LOGON) parameter'
key
device description 16-5, 16-8
Attn 13-4
using 16-9
Home and Erase 12-7
host system
Reset 12-6
3270 requirements 15-13
Sys Req option 10 5-6
3270-5250 keyboard differences 15-14
System Request 12-7
configuration values 15-7
keyboard
definition 12-9
3270 remote attachment 12-5
HCF network considerations 15-5
changing 12-5
HCF version requirement 15-1
configuring 12-5
VTAM/NCP generation considerations 15-6
DHCF mapping 12-13
map setting 12-16
I mapping 12-7
IDBLK (identification block) parameter 15-6 mapping considerations 12-17
identification block (IDBLK) parameter 15-6 keyboard language type (KBDTYPE) parameter 3-5
identification number (IDNUM) parameter 15-6 keyboard map
IDNUM (identification number) parameter 15-6 displaying 12-7
IGCFEAT (DBCS feature) parameter 13-11 SNA Primary LU2 Support (SPLS) 17-20
inactive status (ISTATUS) parameter 15-6, 15-7 SPLS (SNA Primary LU2 Support) 17-20
inactivity timer (INACTTMR) parameter
display device description 17-15, 17-16
printer device description 17-17, 17-18

Index X-15
LU (logical unit) (continued)
L remote 8-12
LCLLOCNAME (local location) parameter secondary 13-4, 16-1
display station pass-through 4-4 type 1 17-2
SNA Primary LU2 Support (SPLS) type 2 17-2
display device description 17-12, 17-15 LU 3
printer device description 17-18, 17-19 See LU (logical unit)
limit security officer (QLMTSECOFR) system value 7-1
line description
configuration 15-8 M
considerations 9-6 macroinstruction
creating 16-5 station address 15-6
line description (SDLC) VTAM/NCP generation 15-7
creating 9-5 manual list X-1
link mapping
definition 15-11 3270-to-5250 12-13
LOCADDR (local address) parameter 15-7 keyboard 12-7
LOCADR (local location address) parameter keyboard considerations 12-17
DHCF configuration 15-7 matching parameters
SNA Primary LU2 Support (SPLS) 5494 Remote Control Unit
display device description 17-12, 17-15 SDLC example 11-11
printer device description 17-17, 17-18 token-ring attachment example 11-15
local address (LOCADDR) parameter 15-7 X.25 example 11-13
local location AS/400 DLUR and VTAM 18-11
adding 8-11 intermediate node and VTAM 18-11
specifying 4-4 SNA Primary LU2 Support (SPLS)
local location (LCLLOCNAME) parameter example 17-27
display station pass-through 4-4 SDLC example 17-26
SNA Primary LU2 Support (SPLS) SPLS (SNA Primary LU2 Support)
display device description 17-12, 17-15 example 17-27
printer device description 17-18, 17-19 SDLC example 17-26
local location address (LOCADR) parameter MAXDATA (maximum data) parameter 15-6
DHCF configuration 15-7 maximum data (MAXDATA) parameter 15-6
SNA Primary LU2 Support (SPLS) maximum output (MAXOUT) parameter 15-6
display device description 17-12, 17-15 maximum sign-on attempts allowed (QMAXSIGN)
printer device description 17-17, 17-18 system value 3-6
logical unit (LU) MAXOUT (maximum output) parameter 15-6
macroinstructions 15-7 message
primary 13-4, 16-1 *BREAK 13-5
remote 8-12 operator error 12-11
secondary 13-4, 16-1 system services control 13-4
type 1 17-2 message code, 3270 12-12
type 2 17-2 message handling
LOGMODE (logon mode) parameter 15-11 display station pass-through 7-2
LOGON (host signon/logon command) parameter mode
device description 16-5, 16-8 5494 Remote Control Unit
using 16-9 BLANK mode 11-4
LOGON (logon) command, VTAM 17-20 default 11-4
logon mode QRMTWSC mode 11-4
displaying 15-7 break 12-11
logon mode (LOGMODE) parameter 15-11 specifying attributes 4-4
logon mode table (MODETAB) parameter 15-11 values 4-4
low-entry networking node 4-8, 7-11 mode description
LU (logical unit) creating 4-4
macroinstructions 15-7 MODE parameter 4-4
primary 13-4, 16-1

X-16 Remote Work Station Support V4R1

MODEL (device model) parameter NRF (network routing facility) (continued)
network routing facility (NRF) 16-5 configuring the AS/400 system 16-4
SNA Primary LU2 Support (SPLS) definition 16-1
3287 printer 17-17, 17-18 ending 16-10
display device description 17-12, 17-14 how it performs 16-1
MODETAB (logon mode table) parameter 15-11 how it works 16-1
multiple port sharing 19-1 introduction 16-1
Multiple Virtual Storage (MVS) NCP definitions 16-13
HCF environment 15-2 network configuration 16-2
multipoint line 8-2 printing 16-9
multipoint network 15-13 sessions 16-2
MVS (Multiple Virtual Storage) SNA Primary LU2 Support (SPLS) comparison 17-2
HCF environment 15-2 SPLS (SNA Primary LU2 Support) comparison 17-2
using 16-9
version and release level 16-2
N VTAM 3174 definitions 16-16
NCCF (Network Communications Control Facility) VTAM AS/400 definitions 16-15
requirement for DHCF 15-1 VTAM logon mode table 16-10
NCP (Network Control Program) VTAM session awareness 16-2
definition 16-1 numeric-only field 12-6
definitions 16-13, 17-23
network attribute
displaying 4-1 O
Network Communications Control Facility (NCCF) off
requirement for DHCF 15-1 signing
Network Control Program (NCP) DHCF 15-13
definition 16-1 display station pass-through 1-6, 7-7
definitions 16-13, 17-23 NRF 16-10
network node SPLS 17-21
configuring 7-12 ONLINE (online at IPL) parameter 17-16, 17-19
server 7-11 online at IPL (ONLINE) parameter 17-16, 17-19
network routing facility (NRF) option 10 (SRQ10PGM) 5-7
compared to HCF 16-1
configuring the AS/400 system 16-4
definition 16-1 P
ending 16-10 PACING parameter 15-7
how it performs 16-1 parameter
how it works 16-1 ADDR (address) 15-6
introduction 16-1 application type (APPTYPE)
NCP definitions 16-13 *APPINIT value 17-16, 17-17
network configuration 16-2 *CTLSSN value 17-12
printing 16-9 *DEVINIT value 17-15, 17-18
sessions 16-2 *NRF value 16-5
SNA Primary LU2 Support (SPLS) comparison 17-2 SNA Primary LU2 Support (SPLS) 17-11
SPLS (SNA Primary LU2 Support) comparison 17-2 APPTYPE (application type)
using 16-9 *APPINIT value 17-16, 17-17
version and release level 16-2 *CTLSSN value 17-12
VTAM 3174 definitions 16-16 *DEVINIT value 17-15, 17-18
VTAM AS/400 definitions 16-15 *NRF value 16-5
VTAM logon mode table 16-10 SNA Primary LU2 Support (SPLS) 17-11
VTAM session awareness 16-2 autocreate device (AUTOCRTDEV) 17-6, 17-11
node AUTOCRTDEV (autocreate device) 17-6, 17-11
HCF network 15-2 autodelete device (AUTODLTDEV) 17-7
low-entry 4-8 AUTODLTDEV (autodelete device) 17-7
NRF (network routing facility) automatic sign-on 7-4
compared to HCF 16-1 CNNDEV (APPC device) 4-5

Index X-17
parameter (continued) parameter (continued)
DBCS feature (IGCFEAT) parameter 13-11 ENCR (encryption) 15-7
DEVCLS (device class) end connection (ENDCNN)
display device description, DHCF 15-13
APPTYPE(*APPINIT) 17-16 display station pass-through 1-6
display device description, NRF 16-10
APPTYPE(*CTLSSN) 17-12 SPLS 17-21
display device description, ENDCNN (end connection)
APPTYPE(*DEVINIT) 17-14 DHCF 15-13
NRF configuration 16-5 display station pass-through 1-6
printer device description, NRF 16-10
APPTYPE(*APPINIT) 17-17 SPLS 17-21
printer device description, host signon/logon command (LOGON)
APPTYPE(*DEVINIT) 17-18 device description 16-5, 16-8
DEVD (device description) 16-5, 17-12 using 16-9
device class (DEVCLS) IDBLK (identification block) 15-6
display device description, IDNUM (identification number) 15-6
APPTYPE(*APPINIT) 17-16 IGCFEAT (DBCS feature) parameter 13-11
display device description, inactivity timer (INACTTMR)
APPTYPE(*CTLSSN) 17-12 display device description 17-15, 17-16
display device description, printer device description 17-17, 17-18
APPTYPE(*DEVINIT) 17-14 INACTTMR (inactivity timer)
NRF configuration 16-5 display device description 17-15, 17-16
printer device description, printer device description 17-17, 17-18
APPTYPE(*APPINIT) 17-17 ISTATUS (inactive status) 15-6, 15-7
printer device description, KBDTYPE (keyboard language type) 3-5
APPTYPE(*DEVINIT) 17-18 LCLLOCNAME (local location)
device description (DEVD) 16-5, 17-12 display device description,
device model (MODEL) APPTYPE(*APPINIT) 17-16
display device description, display device description,
APPTYPE(*APPINIT) 17-16 APPTYPE(*CTLSSN) 17-12
display device description, display device description,
APPTYPE(*CTLSSN) 17-12 APPTYPE(*DEVINIT) 17-15
display device description, display station pass-through 4-4
APPTYPE(*DEVINIT) 17-14 printer device description,
NRF configuration 16-5 APPTYPE(*APPINIT) 17-18
printer device description, printer device description,
APPTYPE(*APPINIT) 17-17 APPTYPE(*DEVINIT) 17-19
printer device description, LOCADDR (local address) 15-7
APPTYPE(*DEVINIT) 17-18 LOCADR (local location address)
device type (TYPE) 16-5 5394 configuration 9-8
display device description, 5494 configuration 11-9
APPTYPE(*APPINIT) 17-16 DHCF configuration 15-7
display device description, display device description,
APPTYPE(*CTLSSN) 17-12 APPTYPE(*APPINIT) 17-16
display device description, display device description,
APPTYPE(*DEVINIT) 17-14 APPTYPE(*CTLSSN) 17-12
NRF configuration 16-5 display device description,
printer device description, APPTYPE(*DEVINIT) 17-15
APPTYPE(*APPINIT) 17-17 printer device description,
printer device description, APPTYPE(*APPINIT) 17-17
APPTYPE(*DEVINIT) 17-18 printer device description,
DISCNT (disconnect) 15-6 APPTYPE(*DEVINIT) 17-18
DLOGMOD (display logon mode) 15-7 local location (LCLLOCNAME)
DROP (drop line at signoff) 17-15 display device description,
drop line at signoff (DROP) 17-15 APPTYPE(*APPINIT) 17-16
display device description,
APPTYPE(*CTLSSN) 17-12

X-18 Remote Work Station Support V4R1

parameter (continued) parameter (continued)
local location (LCLLOCNAME) (continued) remote location (RMTLOCNAME) (continued)
display device description, display device description,
APPTYPE(*DEVINIT) 17-15 APPTYPE(*DEVINIT) 17-15
display station pass-through 4-4 display station pass-through 1-1, 4-1
printer device description, printer device description,
APPTYPE(*APPINIT) 17-18 APPTYPE(*APPINIT) 17-18
printer device description, printer device description,
APPTYPE(*DEVINIT) 17-19 APPTYPE(*DEVINIT) 17-19
local location address (LOCADR) remote network identifier (RMTNETID)
5394 configuration 9-8 display device description,
5494 configuration 11-9 APPTYPE(*DEVINIT) 17-15
DHCF configuration 15-7 display station pass-through 4-5
display device description, printer device description,
APPTYPE(*APPINIT) 17-16 APPTYPE(*DEVINIT) 17-19
display device description, RMTCURLIB (current library) 7-6
APPTYPE(*CTLSSN) 17-12 RMTINLMNU (initial menu) 7-5
display device description, RMTINLPGM (initial program to call) 7-5
APPTYPE(*DEVINIT) 17-15 RMTLOCNAME (remote location)
printer device description, display device description,
APPTYPE(*APPINIT) 17-17 APPTYPE(*APPINIT) 17-16
printer device description, display device description,
APPTYPE(*DEVINIT) 17-18 APPTYPE(*DEVINIT) 17-15
LOGMODE (logon mode) 15-11 display station pass-through 1-1, 4-1
LOGON (host signon/logon command) printer device description,
device description 16-5, 16-8 APPTYPE(*APPINIT) 17-18
using 16-9 printer device description,
matching APPTYPE(*DEVINIT) 17-19
5494 SDLC example 11-11 RMTNETID (remote network identifier)
5494 token-ring attachment example 11-15 display device description,
5494 X.25 example 11-13 APPTYPE(*DEVINIT) 17-15
SPLS example 17-27 display station pass-through 4-5
SPLS SDLC example 17-26 printer device description,
MAXDATA (maximum data) 15-6 APPTYPE(*DEVINIT) 17-19
MAXOUT (maximum output) 15-6 RMTPWD (user password) 7-5
MODE 4-4 RMTUSER (user profile) 7-4, 7-5
MODEL (device model) SRQ10PGM (system request program) 5-7
display device description, SSCPFM 15-6
APPTYPE(*APPINIT) 17-16 TYPE (device type) 16-5
display device description, display device description,
APPTYPE(*CTLSSN) 17-12 APPTYPE(*APPINIT) 17-16
display device description, display device description,
APPTYPE(*DEVINIT) 17-14 APPTYPE(*CTLSSN) 17-12
NRF configuration 16-5 display device description,
printer device description, APPTYPE(*DEVINIT) 17-14
APPTYPE(*APPINIT) 17-17 NRF configuration 16-5
printer device description, printer device description,
APPTYPE(*DEVINIT) 17-18 APPTYPE(*APPINIT) 17-17
MODETAB (logon mode table) 15-11 printer device description,
ONLINE (online at IPL) 17-16, 17-19 APPTYPE(*DEVINIT) 17-18
online at IPL (ONLINE) 17-16, 17-19 USSTAB (unformatted system services table) 15-7
overriding 7-5 VRTCTL (virtual controller) 4-9
PACING (pacing) 15-7 VRTDEV (virtual display device) 4-10
PASTHRSCN (display option) 7-7 XID (exchange identifier) 15-6
PUTYPE (physical unit type) 15-6 pass-through
remote location (RMTLOCNAME) See also display station pass-through
display device description,
APPTYPE(*APPINIT) 17-16

Index X-19
pass-through (continued) publications list X-1
beginning 7-12 PUTYPE (physical unit type) parameter 15-6
ending 1-5
starting
APPN support, with 1-3 Q
APPN support, without 1-4 QAUTORMT (automatic remote controller) system
automatic sign-on 7-3 value 10-1
overview 1-3 QAUTOVRT (autoconfigure virtual device) system
transferring 5-5 value 3-2
pass-through screen (PASTHRSCN) parameter 7-7 QDCRDEVD (Retrieve Device Description) API 17-15,
See also PASTHRSCN (display option) parameter 17-19
password verification 6-1 QMAXSIGN (maximum sign-on attempts allowed)
PASTHRSCN (display option) parameter 7-7 system value 3-6
performance QPACTL00 virtual controller 3-3
automatic creation 17-7 QPASTHRSVR system value 2-1, 2-2
SNA Primary LU2 Support (SPLS) 17-2 QRMTSIGN (remote sign-on) system value
SPLS (SNA Primary LU2 Support) 17-2 controlling remote sessions 6-1
performance considerations 2-4 function 6-1
Personal System/55 program
See also Personal System/55 example 6-2
AS/400 system attachment 9-14 specifications 6-2
device description 9-15 uses 6-1
Remote 5250 Work Station Adapter 9-14 valid value 6-1
physical unit QRMTWSC mode 11-4
macroinstruction 15-6 QSYSWRK subsystem 2-1
type 15-6 QUSRTOOL library 17-21
physical unit type (PUTYPE) parameter 15-6
PLU (primary logical unit)
AS/400 system 17-2
R
Recommendation
definition 16-1
X.25 15-3
point-to-point line 8-2
remote
primary logical unit (PLU)
printer pass-through 7-13
AS/400 system 17-2
remote device
definition 16-1
configuring 9-2
printer
remote location
alternate 17-15
defining 4-1
associated 17-15
specifying 1-1, 4-8
LU type 1 session 17-2
remote location (RMTLOCNAME) parameter
remote pass-through 7-13
display station pass-through 1-1, 4-1
session 3-5
SNA Primary LU2 Support (SPLS)
SNA Primary LU2 Support (SPLS) 17-2
display device description 17-15, 17-16
virtual 3-5
printer device description 17-18, 17-19
printer output 7-13
remote management
printing
description of DHCF 15-2
NRF (network routing facility) 16-9
remote network identifier (RMTNETID) parameter
SNA Primary LU2 Support (SPLS) 17-21
display station pass-through 4-5
SPLS (SNA Primary LU2 Support) 17-21
SNA Primary LU2 Support (SPLS) 17-15, 17-19
programming
remote printer pass-through 7-13
HCF host considerations 15-5
remote sign-on (QRMTSIGN) system value
QRMTSIGN considerations 6-7
controlling remote sessions 6-1
QRMTSIGN specifications 6-2
function 6-1
protocol
program
definition 12-1
example 6-2
PS/55
specifications 6-2
See Personal System/55
uses 6-1

X-20 Remote Work Station Support V4R1

remote sign-on (QRMTSIGN) system value (continued) secondary logical unit (SLU)
valid value 6-1 3270 display station 17-2
remote system definition 16-1
attachment, 3270 12-1 security
choices 3-1 automatic sign-on 7-6
controlling sessions 6-1 considerations 3-6, 7-1
management creating user profiles 3-7
description 15-1 password verification 6-1
HCF requirement 15-1 user profile 6-8
starting DHCF 15-12 X.21 19-1
using DHCF 15-10 Series/1 system
sign-on considerations 6-2 5250 users 15-5
specifying 4-1 HCF network 15-2
Request for Price Quotation (RPQ) server jobs 2-1
5494 Remote Control Unit Attachment to Subarea QPASVRP 2-3
Network QPASVRS 2-3
configuration instructions 11-4, 11-5 session
request/response header 15-6 application-initiated 17-5
Reset key 12-6 device-initiated 17-5
Retrieve Device Description (QDCRDEVD) API 17-15, ending DHCF 15-12
17-19 ending SNA Primary LU2 Support (SPLS) 17-21
retrieving ending SPLS (SNA Primary LU2 Support) 17-21
device description 17-15, 17-19 remote 6-1
return code 6-8 SCS (SNA character string) 17-2
reverse image attribute 12-13 SNA 13-2
RMTCURLIB (current library) parameter 7-6 SNA character string (SCS) 17-2
RMTINLMNU (initial menu) parameter 7-5 SNA Primary LU2 Support (SPLS) 17-5
RMTINLPGM (initial program to call) parameter 7-5 SPLS (SNA Primary LU2 Support) 17-5
RMTLOCNAME (remote location) parameter starting SNA Primary LU2 Support (SPLS) 17-20
display station pass-through 1-1, 4-1 starting SPLS (SNA Primary LU2 Support) 17-20
SNA Primary LU2 Support (SPLS) Set Keyboard Map (SETKBDMAP) command 12-7,
display device description 17-15, 17-16 12-16
printer device description 17-18, 17-19 SETKBDMAP (Set Keyboard Map) command 12-7,
RMTNETID (remote network identifier) parameter 12-16
display station pass-through 4-5 setting
SNA Primary LU2 Support (SPLS) 17-15, 17-19 keyboard map 12-7, 12-16
RMTPWD (user password) parameter 7-5 Sign Off (SIGNOFF) command
RMTUSER (user profile) parameter 7-4, 7-5 DHCF 15-13
routing ENDCNN (end connection) parameter
adding entries 6-10 DHCF 15-13
entries 3-7 display station pass-through 1-6
System/36 4-8 NRF 16-10
RPQ (Request for Price Quotation) SPLS 17-21
5494 Remote Control Unit Attachment to Subarea ending pass-through session 7-7
Network NRF 16-10
configuration instructions 11-4, 11-5 returning to source system 1-6
returning to target system 1-6
SPLS 17-21
S sign on
SCS (SNA character string) forcing 6-1
session 17-2 program example 6-4
SDLC (synchronous data link control) sign-on attempt
5494 configuration example 11-11 example 7-8
5494 matching parameters 11-11 signing off
controller use 9-3 DHCF 15-13
display station pass-through 1-6, 7-7

Index X-21
signing off (continued) SNA Primary LU2 Support (SPLS) (continued)
NRF 16-10 configuring (continued)
SPLS 17-21 shared controller 17-8
signing on shared line 17-8
display station pass-through 1-3 steps 17-8
SIGNOFF (Sign Off) command Create Printer for SPLS (TNXCRTPT) tool 17-21
DHCF 15-13 ending session 17-21
ENDCNN (end connection) parameter hardware 17-4
DHCF 15-13 HCF (Host Command Facility) comparison 17-2
display station pass-through 1-6 Host Command Facility (HCF) comparison 17-2
NRF 16-10 initiating sessions 17-20
SPLS 17-21 introduction 17-1
ending pass-through session 7-7 keyboard map 17-20
NRF 16-10 NCP definitions 17-23
returning to source system 1-6 Network Routing Facility (NRF) comparison 17-2
returning to target system 1-6 NRF (Network Routing Facility) comparison 17-2
SPLS 17-21 overview 17-1
SLU (secondary logical unit) performance 17-2
3270 display station 17-2 PLU (primary logical unit) 17-2
definition 16-1 primary logical unit (PLU) 17-2
SNA (Systems Network Architecture) printing 17-21
3270 pass-through 13-3 SCS (SNA character string) 17-2
definition 16-1 secondary logical unit (SLU) 17-2
remote attachment support 12-1 session
SNA character string (SCS) application-initiated 17-5
session 17-2 device-initiated 17-5
SNA pass-through SLU (secondary logical unit) 17-2
configuring SNA character string (SCS) 17-2
single AS/400 system 14-4 software 17-5
SNA Primary LU2 Support (SPLS) starting sessions 17-20
automatic creation 17-7 TNXCRTPT (Create Printer for SPLS) tool 17-21
benefits 17-3 VTAM 3174 definitions 17-26
configuring VTAM AS/400 definitions 17-24
automatic device description creation 17-6, VTAM logon mode table 17-21
17-11 SNUF (Systems Network Architecture upline facility)
controller description 17-9 device description 15-9
device description 17-11 LU 0 15-9
device description, APPTYPE(*APPINIT) 17-16 source system
device description, APPTYPE(*CTLSSN) 17-11 definition 1-1, 14-1
device description, APPTYPE(*DEVINIT) 17-14 illustration 1-1
display device description, passing through 4-8
APPTYPE(*APPINIT) 17-16 SPLS (SNA Primary LU2 Support)
example display description, automatic creation 17-7
APPTYPE(*CTLSSN) 17-12 benefits 17-3
example display description, configuring
APPTYPE(*DEVINIT) 17-14 automatic device description creation 17-6,
example host controller description 17-10 17-11
example line description 17-9 controller description 17-9
example printer description, device description 17-11
APPTYPE(*APPINIT) 17-17 device description, APPTYPE(*APPINIT) 17-16
host controller description 17-9 device description, APPTYPE(*CTLSSN) 17-11
host system 17-19 device description, APPTYPE(*DEVINIT) 17-14
line description 17-8 display device description,
matching parameters 17-27 APPTYPE(*APPINIT) 17-16
matching parameters, SDLC 17-26 example display description,
overview 17-8 APPTYPE(*CTLSSN) 17-12
printer device description, example display description,
APPTYPE(*DEVINIT) 17-18 APPTYPE(*DEVINIT) 17-14

X-22 Remote Work Station Support V4R1

SPLS (SNA Primary LU2 Support) (continued) Start 3270 Display Emulation (STREML3270)
configuring (continued) command 13-2
example host controller description 17-10 Start Communications Server (STRCMNSVR)
example line description 17-9 command 2-1
example printer description, Start Pass-Through (STRPASTHR) command
APPTYPE(*APPINIT) 17-17 APPC device (CNNDEV) parameter 4-5
host controller description 17-9 automatic sign-on 7-3
host system 17-19 changing defaults 7-3
line description 17-8 CNNDEV (APPC device) parameter 4-5
matching parameters 17-27 current library (RMTCURLIB) parameter 7-6
matching parameters, SDLC 17-26 display option (PASTHRSCN) parameter 7-7
overview 17-8 function 1-3
printer device description, initial menu (RMTINLMNU) parameter 7-5
APPTYPE(*DEVINIT) 17-18 initial program to call (RMTINLPGM) parameter 7-5
shared controller 17-8 LCLLOCNAME (local location) parameter 4-4
shared line 17-8 local location (LCLLOCNAME) parameter 4-4
steps 17-8 MODE parameter 4-4
Create Printer for SPLS (TNXCRTPT) tool 17-21 PASTHRSCN (display option) parameter 7-7
ending session 17-21 remote location (RMTLOCNAME) parameter 1-1,
hardware 17-4 4-1
HCF (Host Command Facility) comparison 17-2 remote network identifier (RMTNETID)
Host Command Facility (HCF) comparison 17-2 parameter 4-5
initiating sessions 17-20 RMTCURLIB (current library) parameter 7-6
introduction 17-1 RMTINLMNU (initial menu) parameter 7-5
keyboard map 17-20 RMTINLPGM (initial program to call) parameter 7-5
NCP definitions 17-23 RMTLOCNAME (remote location) parameter 1-1,
Network Routing Facility (NRF) comparison 17-2 4-1
NRF (Network Routing Facility) comparison 17-2 RMTNETID (remote network identifier)
overview 17-1 parameter 4-5
performance 17-2 RMTPWD (user password) parameter 7-5
PLU (primary logical unit) 17-2 RMTUSER (user profile) parameter 7-4, 7-5
primary logical unit (PLU) 17-2 SRQ10PGM (system request program)
printing 17-21 parameter 5-7
SCS (SNA character string) 17-2 system request program (SRQ10PGM)
secondary logical unit (SLU) 17-2 parameter 5-7
session user password (RMTPWD) parameter 7-5
application-initiated 17-5 user profile (RMTUSER) parameter 7-4, 7-5
device-initiated 17-5 virtual controller (VRTCTL) parameter 4-9
SLU (secondary logical unit) 17-2 virtual display device (VRTDEV) parameter 4-10
SNA character string (SCS) 17-2 VRTCTL (virtual controller) parameter 4-9
software 17-5 VRTDEV (virtual display device) parameter 4-10
starting sessions 17-20 Start Subsystem (STRSBS) command 6-9
TNXCRTPT (Create Printer for SPLS) tool 17-21 starting
VTAM 3174 definitions 17-26 3270 display emulation 13-2
VTAM AS/400 definitions 17-24 3270 display station pass-through 13-2
VTAM logon mode table 17-21 DHCF sessions 15-12
SRQ10PGM (system request option 10) handler pass-through
program 5-7 APPN support, with 1-3
SRQ10PGM (system request program) parameter 5-7 APPN support, without 1-4
SSCP (system services control point) automatic sign-on 7-3
FM parameter 15-6 overview 1-3
identifier value 15-7 subsystem 6-9
VTAM 16-9 station address macroinstruction 15-6
VTAM licensed program 17-20 STREML3270 (Start 3270 Display Emulation)
SSCPFM (system services control point FM) command 13-2
parameter 15-6

Index X-23
STRPASTHR (Start Pass-Through) command System Request (continued)
APPC device (CNNDEV) parameter 4-5 option 10 (SRQ10PGM) 5-7
automatic sign-on 7-3 option 10, System/38 5-8
changing defaults 7-3 option 10, using 5-6
CNNDEV (APPC device) parameter 4-5 option 11, System/38 5-8
current library (RMTCURLIB) parameter 7-6 option 11, using 5-7
display option (PASTHRSCN) parameter 7-7 option 13, using 5-7
function 1-3 option 14, using 5-7
initial menu (RMTINLMNU) parameter 7-5 option 15, using 5-7
initial program to call (RMTINLPGM) parameter 7-5 option 80, using 5-7
LCLLOCNAME (local location) parameter 4-4 pass-through program 5-7
local location (LCLLOCNAME) parameter 4-4 System/36 5-6
MODE parameter 4-4 System/38 5-6, 5-8
PASTHRSCN (display option) parameter 7-7 using options 5-6
remote location (RMTLOCNAME) parameter 1-1, System Request (Sys Req) key 12-7
4-1 system request program (SRQ10PGM) parameter 5-7
remote network identifier (RMTNETID) system services control point (SSCP)
parameter 4-5 FM parameter 15-6
RMTCURLIB (current library) parameter 7-6 identifier value 15-7
RMTINLMNU (initial menu) parameter 7-5 VTAM 16-9
RMTINLPGM (initial program to call) parameter 7-5 VTAM licensed program 17-20
RMTLOCNAME (remote location) parameter 1-1, system value
4-1 automatic remote controller (QAUTORMT) 10-1
RMTNETID (remote network identifier) changing 3-2
parameter 4-5 QAUTORMT (automatic remote controller) 10-1
RMTPWD (user password) parameter 7-5 QAUTOVRT (autoconfigure virtual device) 3-2
RMTUSER (user profile) parameter 7-4, 7-5 QLMTSECOFR (limit security officer) 7-1
SRQ10PGM (system request program) QMAXSIGN (maximum sign-on attempts
parameter 5-7 allowed) 3-6
system request program (SRQ10PGM) QRMTSIGN (remote sign-on) 6-1
parameter 5-7 System/36
user password (RMTPWD) parameter 7-5 automatic configuration 7-2
user profile (RMTUSER) parameter 7-4, 7-5 difference from AS/400 system DHCF 15-15
virtual controller (VRTCTL) parameter 4-9 HCF network 15-2
virtual display device (VRTDEV) parameter 4-10 routing to 4-8
VRTCTL (virtual controller) parameter 4-9 user profiles 3-7
VRTDEV (virtual display device) parameter 4-10 using display station pass-through 7-2
STRSBS (Start Subsystem) command 6-9 System/38
subsystem attached to AS/400 system 8-10
5494 Remote Control Unit 11-17 connection device 4-5
APPC 11-17 control unit description 3-4
creating 6-8 creating control unit description 3-4
starting 6-9 difference from AS/400 system DHCF 15-15
user profile defaults 6-8 HCF network 15-2
subsystem description parameters 4-9
displaying 6-9 Systems Network Architecture (SNA)
synchronous data link control (SDLC) 3270 pass-through 13-3
5494 configuration example 11-11 definition 16-1
5494 matching parameters 11-11 remote attachment support 12-1
controller use 9-3 Systems Network Architecture upline facility (SNUF)
system reference code device description 15-9
5494 Remote Control Unit 11-17 LU 0 15-9
System Request
AS/400 system 5-6
key 5-6
menu 5-6

X-24 Remote Work Station Support V4R1

TYPE (device type) parameter (continued)
T SNA Primary LU2 Support (SPLS)
target system 3287 printer 17-17, 17-18
automatic sign-on 7-2 display device description 17-12, 17-14
choosing 1-1, 4-1
defining 4-1
definition 1-1, 14-1 U
illustration 1-1 underline attribute 12-13
instructions 6-8 unformatted system services (USS) request
multiple product 8-12 issuing 16-9, 17-20
overriding parameters 7-5 table 16-9, 17-20
printer output 7-13 Unformatted System Services Table (USSTAB) param-
signing on 1-3 eter 15-7
switching 4-3 user password (RMTPWD) parameter 7-5
TCP/IP (Transmission Control Protocol/Internet Pro- user profile
tocol) changing 12-16
automatic configuration 3-6 creating 3-7, 6-9
definition 3-6 security considerations 7-1
end system 5-4 specifying name 6-1
home system 5-4 subsystem defaults 6-8
support 3-6 user profile (RMTUSER) parameter 7-4, 7-5
using with pass-through 5-3 user-assignable keyboard mapping commands 12-7
Telecommunications Standardization Sector (ITU-T) USS (unformatted system services) request
former CCITT (International Telegraph and Tele- issuing 16-9, 17-20
phone Consultative Committee) 15-3 table 16-9, 17-20
TELNET. USSMSG macroinstruction
automatic configuration 3-6 MSG=10 operand 15-7
definition 3-6
end system 5-4
home system 5-4 V
using with pass-through 5-3 value
TFRPASTHR (Transfer Pass-Through) command 5-5 CNNDEV parameter 4-8
This procedure is very important when automatic config- matching 15-7
uration of virtual 7-1 mode 4-4
TNXCRTPT (Create Printer for SPLS) tool 17-21 QLMTSECOFR 7-1
token-ring network QRMTSIGN (remote sign-on) 6-7
attachment configuration system
5494 matching parameters 11-15 changing 3-2
5494 Remote Control Unit example 11-14 QAUTOVRT (autoconfigure virtual device) 3-2
5494 Remote Control Unit illustration 11-3 QLMTSECOFR (limit security officer) 7-1
definition 13-5 QMAXSIGN (maximum sign-on attempts
gateway configuration allowed) 3-6
5494 Remote Control Unit illustration 11-2 QRMTSIGN (remote sign-on) 6-1
Transfer Pass-Through (TFRPASTHR) command 5-5 virtual controller 4-10
transferring virtual device 4-10
pass-through 5-5 virtual controller
Transmission Control Protocol/Internet Protocol configuring 3-1
(TCP/IP) parameter
automatic configuration 3-6 specifying QPACTL00 3-3
definition 3-6 using 4-9
end system 5-4 QPACTLnn 3-2
home system 5-4 security considerations 3-6
using with pass-through 5-3 specifying 4-9
twinaxial controller 9-1 TELNET configuration 3-6
TYPE (device type) parameter values 4-10
network routing facility (NRF) 16-5

Index X-25
virtual controller (VRTCTL) parameter VTAM definitions
specifying QPACTL00 3-3 APPN connections 18-8
using 4-9 DLUR support 18-8
virtual device VTAM/NCP (Virtual Telecommunications Access
250 per controller 3-2 Method/Network Control Program)
automatically configured 3-2, 7-1 generation considerations 15-6
controlling 6-9 HCF use 15-1
definition 3-1 LU macroinstruction 15-7
list 4-10
manually configured 3-3
matching physical device 3-4 W
not automatically deleted 3-2 work management 6-1
owner 3-2 work station entry
QAUTOVRT (autoconfigure virtual device) system adding 6-9
value 3-2 work station function (WSF)
specifying 4-9 Client Access
table 3-4 automatic sign-on 6-2
type determination 4-9 controlling sessions 6-1, 6-2
values 4-10 QRMTSIGN (remote sign-on) system value 6-1
virtual display station model and type table 3-4 virtual printer device description 3-5
virtual display device (VRTDEV) parameter 4-10 Work with Configuration Lists (WRKCFGL)
virtual display station 3-4 command 4-1
virtual printer Work with Configuration Status (WRKCFGSTS)
device description 3-5 command
Virtual Telecommunications Access Method (VTAM) 5494 management 11-16
(SSCP) system services control point 16-9, 17-20 Work with Hardware Resources (WRKHDWRSC)
3174 definitions 16-16, 17-26 command 9-5
AS/400 definitions 16-15, 17-24 working with
display 13-4 configuration lists 4-1
logon mode table 16-10, 17-21 configuration status 11-16
NCCF/TAF use 15-1 hardware resources 9-5
NCP definitions 16-13, 17-23 WRKCFGL (Work with Configuration Lists)
network 16-1 command 4-1
NRF session awareness 16-2 WRKCFGSTS (Work with Configuration Status)
system services control point (SSCP) 16-9, 17-20 command
Virtual Telecommunications Access Method/Network 5494 management 11-16
Control Program (VTAM/NCP) WRKHDWRSC (Work with Hardware Resources)
generation considerations 15-6 command 9-5
HCF use 15-1 WSF (work station function)
LU macroinstruction 15-7 Client Access
VRTCTL (virtual controller) parameter automatic sign-on 6-2
specifying QPACTL00 3-3 controlling sessions 6-1, 6-2
using 4-9 QRMTSIGN (remote sign-on) system value 6-1
VRTDEV (virtual display device) parameter 4-10 virtual printer device description 3-5
VTAM (Virtual Telecommunications Access Method)
(SSCP) system services control point 16-9, 17-20
3174 definitions 16-16, 17-26
X
X.21
AS/400 definitions 16-15, 17-24
controller use 9-3
display 13-4
security 19-1
logon mode table 16-10, 17-21
short-hold mode 19-3
NCCF/TAF use 15-1
configuring 19-3
NCP definitions 16-13, 17-23
multiple port sharing example 19-1
network 16-1
X.25
NRF session awareness 16-2
5494 configuration example 11-12
system services control point (SSCP) 16-9, 17-20
5494 matching parameters 11-13

X-26 Remote Work Station Support V4R1

X.25 (continued)
controller use 9-3
definition 15-3
XID (exchange identifier) parameter 15-6

Index X-27
Communicating Your Comments to IBM
AS/400 Advanced Series
Remote Work Station Support
Version 4
Publication No. SC41-5402-00

If you especially like or dislike anything about this book, please use one of the methods
listed below to send your comments to IBM. Whichever method you choose, make sure you
send your name, address, and telephone number if you would like a reply.

Feel free to comment on specific errors or omissions, accuracy, organization, subject matter,
or completeness of this book. However, the comments you send should pertain to only the
information in this manual and the way in which the information is presented. To request
additional publications, or to ask questions or make comments about the functions of IBM
products or systems, you should talk to your IBM representative or to your IBM authorized
remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute
your comments in any way it believes appropriate without incurring any obligation to you.

If you are mailing a readers' comment form (RCF) from a country other than the United
States, you can give the RCF to the local IBM branch office or IBM representative for
postage-paid mailing.
If you prefer to send comments by mail, use the RCF at the back of this book.
If you prefer to send comments by FAX, use this number:
– United States and Canada: 1-800-937-3430
– Other countries: 1-507-253-5192
If you prefer to send comments electronically, use this network ID:
– IBMMAIL(USIB56RZ)
– [email protected]

Make sure to include the following in your note:

Title and publication number of this book
Page number or topic to which your comment applies.
Readers' Comments — We'd Like to Hear from You
AS/400 Advanced Series
Remote Work Station Support
Version 4
Publication No. SC41-5402-00

Overall, how satisfied are you with the information in this book?
Very Very
Satisfied Satisfied Neutral Dissatisfied Dissatisfied
Overall satisfaction Ø Ø Ø Ø Ø

How satisfied are you that the information in this book is:
Very Very
Satisfied Satisfied Neutral Dissatisfied Dissatisfied
Accurate Ø Ø Ø Ø Ø
Complete Ø Ø Ø Ø Ø
Easy to find Ø Ø Ø Ø Ø
Easy to understand Ø Ø Ø Ø Ø
Well organized Ø Ø Ø Ø Ø
Applicable to your tasks Ø Ø Ø Ø Ø

Please tell us how we can improve this book:

Thank you for your responses. May we contact you? Ø Yes Ø No

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments
in any way it believes appropriate without incurring any obligation to you.

Name Address

Company or Organization

Phone No.
Cut or Fold
Readers' Comments — We'd Like to Hear from You

IBM
Along Line
SC41-5402-00


Fold and Tape Please do not staple Fold and Tape

NO POSTAGE
NECESSARY
IF MAILED IN THE
UNITED STATES

BUSINESS REPLY MAIL

FIRST-CLASS MAIL PERMIT NO. 40 ARMONK, NEW YORK

POSTAGE WILL BE PAID BY ADDRESSEE

IBM CORPORATION
ATTN DEPT 542 IDCLERK
3605 HWY 52 N
ROCHESTER MN 55901-7829

Fold and Tape Please do not staple Fold and Tape

Cut or Fold
SC41-5402-00 Along Line
IBM 

Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.

SC41-54ð2-ðð
Spine information:

IBM AS/400 Advanced Series Remote Work Station Support Version 4

Network Management
No ratings yet
Network Management
336 pages
AS400 System Operations
No ratings yet
AS400 System Operations
183 pages
Tape Drive SG 244503
No ratings yet
Tape Drive SG 244503
326 pages
Communications AS400
No ratings yet
Communications AS400
321 pages
Tdit-Srs 840 01 02 02
No ratings yet
Tdit-Srs 840 01 02 02
98 pages
Cics 400 Administration and Operations Guide
No ratings yet
Cics 400 Administration and Operations Guide
343 pages
Mod08 Amos
100% (2)
Mod08 Amos
90 pages
Mod08 Amos
No ratings yet
Mod08 Amos
90 pages
Os390 HCD Configuration Definition Planning
No ratings yet
Os390 HCD Configuration Definition Planning
116 pages
Administration PDF
67% (3)
Administration PDF
341 pages
PLC Quantum PLC NOE771xx User Manual v5.0
No ratings yet
PLC Quantum PLC NOE771xx User Manual v5.0
306 pages
Ipaso VR A5 GGS-000375-02E Cli command-SS1901
No ratings yet
Ipaso VR A5 GGS-000375-02E Cli command-SS1901
182 pages
HiPath 3000 - 5000 V8, Feature Usage Examples, Administrator Documentation, Issue 7
No ratings yet
HiPath 3000 - 5000 V8, Feature Usage Examples, Administrator Documentation, Issue 7
414 pages
System/38 Environment Programming
No ratings yet
System/38 Environment Programming
224 pages
Symmetricom Nts 200
100% (1)
Symmetricom Nts 200
140 pages
CURSO OJXE SG 9.a
No ratings yet
CURSO OJXE SG 9.a
582 pages
Netway Vision 3.8 .X: Software Solutions
No ratings yet
Netway Vision 3.8 .X: Software Solutions
89 pages
Rserver: User's Guide
No ratings yet
Rserver: User's Guide
84 pages
P550R
No ratings yet
P550R
756 pages
PlantPAX Display Elements Manual
No ratings yet
PlantPAX Display Elements Manual
554 pages
Tenor A Fuser Guide
No ratings yet
Tenor A Fuser Guide
70 pages
DCX 13.a R - LG
No ratings yet
DCX 13.a R - LG
216 pages
Delta V System Administration
80% (5)
Delta V System Administration
294 pages
Mediapdfsmodicon Ethernetmodule Userguide PDF
No ratings yet
Mediapdfsmodicon Ethernetmodule Userguide PDF
290 pages
GA19-5486-19 AS400 System Handbook V4R4 199908
No ratings yet
GA19-5486-19 AS400 System Handbook V4R4 199908
616 pages
DCX 13.a R - SG PDF
No ratings yet
DCX 13.a R - SG PDF
314 pages
Copy Services Implemantation Guide
No ratings yet
Copy Services Implemantation Guide
202 pages
Ux5000-Pbx Manual PDF
No ratings yet
Ux5000-Pbx Manual PDF
1,046 pages
Elance Central Service Manual - Rev L
No ratings yet
Elance Central Service Manual - Rev L
54 pages
Signaling Server: Installation and Configuration
No ratings yet
Signaling Server: Installation and Configuration
118 pages
Ex4200 Metro Ring With MX Series Head-End: Using Virtual Chassis Technology in The Wan
No ratings yet
Ex4200 Metro Ring With MX Series Head-End: Using Virtual Chassis Technology in The Wan
23 pages
SC 415443
No ratings yet
SC 415443
301 pages
Tdit-Srs 840 01 02 02
No ratings yet
Tdit-Srs 840 01 02 02
98 pages
Advantys STB Standart Ethernet Modbus TCPIP - Applications Guide - 02 - 2009
No ratings yet
Advantys STB Standart Ethernet Modbus TCPIP - Applications Guide - 02 - 2009
236 pages
System Commands
No ratings yet
System Commands
796 pages
GA19-5486-20 AS400 System Handbook V4R5
No ratings yet
GA19-5486-20 AS400 System Handbook V4R5
834 pages
Tenor As Voip Multipath/Gateway Switch: Product Guide
No ratings yet
Tenor As Voip Multipath/Gateway Switch: Product Guide
125 pages
AN30G6 XCoursehint
No ratings yet
AN30G6 XCoursehint
178 pages
User'S Guide: Inrow RD 100-Series Inrow RD 200-Series
No ratings yet
User'S Guide: Inrow RD 100-Series Inrow RD 200-Series
76 pages
Project Object Elemenst 4.0
No ratings yet
Project Object Elemenst 4.0
580 pages
Thinmanager 12 Thin Client Management Platform: User Manual
No ratings yet
Thinmanager 12 Thin Client Management Platform: User Manual
576 pages
Proces-Um001 - En-P PlantPax Distribuited Control System User Manual
No ratings yet
Proces-Um001 - En-P PlantPax Distribuited Control System User Manual
316 pages
Thin Manager
No ratings yet
Thin Manager
636 pages
CLI CMD Guideline
No ratings yet
CLI CMD Guideline
184 pages
HiPath 3000 5000 V9 Practical Examples Issue 8
No ratings yet
HiPath 3000 5000 V9 Practical Examples Issue 8
424 pages
Advantys STB: Standard Ethernet Modbus TCP/IP Network Interface Module Applications Guide
No ratings yet
Advantys STB: Standard Ethernet Modbus TCP/IP Network Interface Module Applications Guide
194 pages
Um MD ST
No ratings yet
Um MD ST
166 pages
06 PlantPAx Distributed Control System
No ratings yet
06 PlantPAx Distributed Control System
128 pages
Proces Rm014 en P
No ratings yet
Proces Rm014 en P
574 pages
Eaton Web SNMP Card PDF
No ratings yet
Eaton Web SNMP Card PDF
59 pages
i 35 Ex 2-21 IECEx Weighbridge Indicator
No ratings yet
i 35 Ex 2-21 IECEx Weighbridge Indicator
2 pages
Amazon - Web.services - Examcollection.saa C03.exam - Question.2022 Oct 09.by - Osborn.0q.vce
No ratings yet
Amazon - Web.services - Examcollection.saa C03.exam - Question.2022 Oct 09.by - Osborn.0q.vce
24 pages
Machine Learning PDF
No ratings yet
Machine Learning PDF
14 pages
Computer Science Exam Prep
No ratings yet
Computer Science Exam Prep
3 pages
The Bus Ticket App Plan
No ratings yet
The Bus Ticket App Plan
3 pages
"It's Dead, Jim" - Resurrecting An Obsolete File, Part 1 - The Signal - Digital Preservation
No ratings yet
"It's Dead, Jim" - Resurrecting An Obsolete File, Part 1 - The Signal - Digital Preservation
4 pages
Processor Architectures Overview
No ratings yet
Processor Architectures Overview
8 pages
Java MVC Architecture Explained
No ratings yet
Java MVC Architecture Explained
8 pages
Handbook Ericsson PUb 1 PDF
100% (1)
Handbook Ericsson PUb 1 PDF
264 pages
CourseNotes - Oracle Database 19c Basic SQL
No ratings yet
CourseNotes - Oracle Database 19c Basic SQL
12 pages
20Eepw601-Embedded Systems and Iot With Laboratory Assignment - 1
No ratings yet
20Eepw601-Embedded Systems and Iot With Laboratory Assignment - 1
13 pages
FMZ-SS Series: Scalable Management Software For Sony NSR Recorders
No ratings yet
FMZ-SS Series: Scalable Management Software For Sony NSR Recorders
2 pages
BC-6000 Series Service Training Guide
No ratings yet
BC-6000 Series Service Training Guide
49 pages
Digital Grid for Engineering Students
No ratings yet
Digital Grid for Engineering Students
15 pages
(IJCST-V7I3P25) :Dr.K.Sai Manoj, Ms. K. Mrudula, Mrs G.Maanasa, Prof.K.Phani Srinivas
No ratings yet
(IJCST-V7I3P25) :Dr.K.Sai Manoj, Ms. K. Mrudula, Mrs G.Maanasa, Prof.K.Phani Srinivas
5 pages
ECSE 2104 - L1 - Introduction To Microprocessors and Embedded Systems
No ratings yet
ECSE 2104 - L1 - Introduction To Microprocessors and Embedded Systems
13 pages
Hartron
No ratings yet
Hartron
5 pages
Serial Addition FSM Guide
No ratings yet
Serial Addition FSM Guide
8 pages
Peplink Balance: Load Balancing Multi-WAN Routers
No ratings yet
Peplink Balance: Load Balancing Multi-WAN Routers
30 pages
Keyence KV 10ar at PLC
No ratings yet
Keyence KV 10ar at PLC
17 pages
GCP CDL
100% (1)
GCP CDL
156 pages
Spring Associate Cart Application Guide
No ratings yet
Spring Associate Cart Application Guide
25 pages
Cache Mapping Practice Problems
No ratings yet
Cache Mapping Practice Problems
26 pages
Understanding Operating Systems Basics
No ratings yet
Understanding Operating Systems Basics
34 pages
Entry-Level Tech Job Seeker Profile
No ratings yet
Entry-Level Tech Job Seeker Profile
1 page
1.1 1 BPB-Cisco-CCNP-Switch-300-115-INTRO
No ratings yet
1.1 1 BPB-Cisco-CCNP-Switch-300-115-INTRO
9 pages
Tackling Security Vulnerabilities in VPN-based
No ratings yet
Tackling Security Vulnerabilities in VPN-based
5 pages
External Ludus Access Via Wireguard
No ratings yet
External Ludus Access Via Wireguard
4 pages
DTS Monaco Product Release Overview
No ratings yet
DTS Monaco Product Release Overview
50 pages
Managed Software Evolution Ralf Reussner ebook formatted for Kindle
No ratings yet
Managed Software Evolution Ralf Reussner ebook formatted for Kindle
45 pages

Remote Work Station Support

Uploaded by

Remote Work Station Support

Uploaded by

AS/400 Advanced Series IBM

Remote Work Station Support

First Edition (August 1997)

or you can fax your comments to:

United States and Canada: 1-800-937-3430

 Copyright International Business Machines Corporation 1997. All rights reserved.

About Remote Work Station Support (SC41-5402) . . . . . . . . . . . . . . . xix

Part 1. Display Station Pass-Through

Chapter 1. Pass-Through Instructions for the End User . . . . . . . . . . . 1-1

Chapter 3. Configure Display Station Pass-Through . . . . . . . . . . . . . 3-1

Chapter 4. Starting and Using a Display Station Pass-Through Session . 4-1

Chapter 5. Going Back and Forth between Systems . . . . . . . . . . . . . 5-1

 Copyright IBM Corp. 1997 iii

Chapter 6. Work Management Considerations for Display Station

Chapter 7. Display Station Pass-Through Considerations . . . . . . . . . . 7-1

Chapter 8. Display Station Pass-Through Configuration Scenario . . . . . 8-1

Part 2. Configuring for 5250 Remote Control Units

iv Remote Work Station Support V4R1

Chapter 11. Configuring 5494 Remote Control Units . . . . . . . . . . . . 11-1

Part 3. Configuring for 3270 Remote Device Support

Chapter 12. Using 3270 Device Support . . . . . . . . . . . . . . . . . . . . 12-1

Chapter 13. 3270-Type Device Configuration Examples . . . . . . . . . . 13-1

Chapter 14. Configuring SNA Pass-Through . . . . . . . . . . . . . . . . . 14-1

Chapter 15. Distributed Host Command Facility . . . . . . . . . . . . . . . 15-1

vi Remote Work Station Support V4R1

Chapter 16. Network Routing Facility . . . . . . . . . . . . . . . . . . . . . 16-1

Chapter 17. SNA Primary LU2 Support . . . . . . . . . . . . . . . . . . . . 17-1

| Chapter 18. Dependent LU Requester Support . . . . . . . . . . . . . . . 18-1

Part 4. Configuring for X.21 Short Hold Mode

Chapter 19. X.21 Short-Hold Mode Configuration Example . . . . . . . . 19-1

viii Remote Work Station Support V4R1

 Copyright IBM Corp. 1997 xi

xii Remote Work Station Support V4R1

 Copyright IBM Corp. 1997 xv

IBM Director of Licensing

This publication could contain technical inaccuracies or typographical errors.

 Copyright IBM Corp. 1997 xvii

PC Direct is a trademark of Ziff Communications Company and is used by IBM

C-bus is a trademark of Corollary, Inc.

Java and HotJava are trademarks of Sun Microsystems, Inc.

xviii Remote Work Station Support V4R1

 Copyright IBM Corp. 1997 xix

Who Should Use This Book

| Information Available on the World Wide Web

xx Remote Work Station Support V4R1

Chapter 3. Configure Display Station Pass-Through . . . . . . . . . . . . . 3-1

Chapter 4. Starting and Using a Display Station Pass-Through Session . 4-1

 Copyright IBM Corp. 1997

Chapter 5. Going Back and Forth between Systems . . . . . . . . . . . . . 5-1

Chapter 6. Work Management Considerations for Display Station

Chapter 7. Display Station Pass-Through Considerations . . . . . . . . . . 7-1

Chapter 8. Display Station Pass-Through Configuration Scenario . . . . . 8-1

Remote Work Station Support V4R1

Part 1. Display Station Pass-Through

Display Station Pass-Through Environment

Choosing the Target System

 Copyright IBM Corp. 1997 1-1

Using Display Station Pass-Through Commands

If you need to specify additional parameters on the STRPASTHR command or want

1-2 Remote Work Station Support V4R1

Type choices, press Enter.

Remote location . . . . . . . . _______ Name, \CNNDEV

Starting Display Station Pass-Through with APPN Support

Chapter 1. Pass-Through Instructions for the End User 1-3

Type choices, press Enter.

Remote location . . . . . . . . > SYSTEMB Name, \CNNDEV

Starting Display Station Pass-Through without APPN Support

Type choices, press Enter.

Remote location . . . . . . . .> \CNNDEV_ Name, \CNNDEV

1-4 Remote Work Station Support V4R1

 Start Pass-Through (STRPASTHR) command

In control language programs, use the TFRPASTHR command to suspend a job on

Ending Pass-Through (ENDPASTHR Command)

Chapter 1. Pass-Through Instructions for the End User 1-5

End Connection Parameter

1-6 Remote Work Station Support V4R1

Start Pass-Through (STRPASTHR) command

The virtual controller (VRTCTL) parameter or virtual display device (VRTDEV)