AS/400e series
Client Access for Windows 95/NT
-Setup
Version 3 Release 2 Modification 0
SC41-3512-05
AS/400e series
Client Access for Windows 95/NT
-Setup
Version 3 Release 2 Modification 0
SC41-3512-05
Note
Before using this information and the product it supports, be sure to read the information in “Appendix H. Notices” on page 449.
Sixth Edition (September 1998)
This edition replaces SC41-3512-04. This edition applies to complex instruction set computer (CISC) systems and to reduced instruction set computer (RISC) systems.
Contents
About Client Access for Windows 95/NT — Setup (SC41–3512–05) . . . . . xiii
Who should read this book . . . xiii
Conventions and terminology that are used in this book . . . xiii
AS/400 Operations Navigator . . . xiv
Installing Operations Navigator subcomponents . . . xv
Accessing AS/400 Operations Navigator . . . xv
Prerequisite and related information . . . xv
How to send your comments . . . xvi
For more information about Client Access . . . xvi
Information APARs and faxes . . . xvi
Part 1. Getting Started
. . . .
1
Chapter 1. What You Need to Know Before You Start . . . 3
About Client Access for Windows 95/NT . . . 3
Migrating from Client Access for Windows 3.1 to Client Access for Windows 95/NT . 3 Functional Comparison Between Client Access for Windows 3.1 and Client Access for Windows 95/NT . . . 4
Important Information about Setting Up Client Access . . . 5
Sources of Information for Installing Client Access. . . 6
Books that contain related information. . . 7
Information Authorized Program Analysis Report (APAR) and PTFs . . . 8
Client Access for Windows 95/NT ReadMe File. . . 8
Service Packs. . . 8
Online User’s Guide for Client Access . . . 9
License Information . . . 9
Minimum PC Hardware Requirements. . . 13
PC5250 Emulation . . . 13
Miscellaneous Tips . . . 13
Chapter 2. Setup Checklist . . . . 15
Chapter 3. Installing Client Access on the AS/400 System . . . . 21
Operating System/400 Releases that Support Client Access for Windows 95/NT. . 21
AS/400 Storage Requirements . . . 22
AS/400 Disk Space for PowerPC AS (RISC) processor models: . . . 22
Installation Options on the LICPGM Menu . . . 23
Replacing Licensed Programs and OS/400 . . . 23
Adding Licensed Programs . . . 23
Installing Client Access for Windows 95/NT on AS/400 with GO LICPGM . . . . 24
Installing Client Access for Windows 95/NT with RSTLICPGM . . . 25
Saving Client Access for Windows 95/NT. . . 26
Verifying Your Installation . . . 27
Deleting Client Access for Windows 95/NT . . . 28
Part 2. AS/400 Information . . . 29
Chapter 4. Enrolling Client Access users on the AS/400 system . . . . 31
Chapter 5. Configuring TCP/IP LAN Connections on the AS/400 System 33 Before you start, please read. . . 33
Using Operations Navigator to start, stop, configure, and verify a TCP/IP connection . . . 34
Chapter 6. Configuring TCP/IP Asynchronous (SLIP) Connections on the AS/400 System . . . . 51
Before you start, please read. . . 51
Chapter 7. Configuring AnyNet - APPC over TCP/IP . . . . 61
Before you start, please read. . . 61
Chapter 8. Configuring Systems Network Architecture (SNA) Twinaxial Connections on the AS/400 System . . . . 67
Before you start, please read. . . 67
Chapter 9. Configuring SNA Token-Ring Connections on the AS/400 System 71 Before you start, please read. . . 71
Configure the connection. . . 71
Chapter 10. Configuring Systems Network Architecture (SNA) Ethernet Connections on the AS/400 System . . . . 75
Before you start, please read. . . 75
Ethernet Addresses . . . 75
Creating Ethernet Addresses . . . 76
Reverse Addressing. . . 76
Converting an Address . . . 77
When to Use the Converted Address . . . 78
Configuring Ethernet Connections on the AS/400 System . . . 79
Chapter 11. Configuring SNA SDLC & AutoSync Connections on the AS/400 System . . . . 83
Before you start, please read. . . 83
Chapter 12. Configuring SNA Asynchronous Connections on the AS/400 System . . . . 87
Before you start, please read. . . 87
Chapter 13. Configuring the Internetwork Packet Exchange (IPX) Support on the AS/400 System . . . . 91
Before you start, please read. . . 91
AS/400 Releases Supporting the IPX Protocol . . . 92
Determining if IPX is already configured . . . 92
Configuring AS/400 for IPX over token-ring . . . 95
Creating an Internetwork Packet Exchange (IPX) description . . . 95
Configuring a Line Description . . . 98
Adding an Internetwork Packet Exchange (IPX) Circuit . . . 102
Start the IPX Circuit . . . 105
Chapter 14. Configuring 5394 Remote Control Units . . . . 107
Before you start, please read. . . 107
Remote Workstation Location Address . . . 110
Chapter 15. Configuring 5494 Remote Control Units . . . . 113
Before you start, please read. . . 113
Configuring 5494 (SDLC) Connections . . . 114
Configuring an SDLC Line Description . . . 114
Configuring an APPC Controller for an SDLC Connection . . . 117
Configuring a Remote Workstation Controller for an SDLC Connection . . . . 120
Configuring 5494 (token-ring) connections . . . 122
Configuring a token-ring line description . . . 122
Configuring an APPC controller for a token-ring connection. . . 123
Configuring a remote workstation controller for a token-ring connection . . . . 127
Frame Relay - Token-Ring Bridge (Feature Code 1150) . . . 129
Other Support. . . 129
How to Order . . . 129
Part 3. Windows 95/NT Preparation . . . 133
Chapter 16. Windows 95 Network Information . . . . 135
If you are using a NS/Router 802.2 connection . . . 135
Windows 95 Network Configuration . . . 136
Network Adapter Driver . . . 137
Chapter 17. Windows NT Networking . . . . 143
If you are using an NS/Router 802.2 connection . . . 143
Network Adapter Driver . . . 144
Installation . . . 144
Chapter 18. Configuring SLIP Support on the PC . . . . 147
Before you start, please read. . . 147
Setting up to Connect to AS/400 . . . 147
Troubleshooting . . . 149
Chapter 19. Configuring Microsoft TCP/IP Support on the PC for Windows 95 151 Before you start, please read. . . 151
Checking for Physical Connectivity Between the PC and the AS/400 . . . 151
Setting up Windows TCP/IP . . . 152
Chapter 20. Configuring Microsoft TCP/IP Support on the PC for Windows NT 155 Before you start, please read. . . 155
Chapter 21. Configuring the PC for the IPX Protocol . . . . 161
Before You Start, please read. . . 161
Installing IPX on the PC . . . 161
Using Novell Netware . . . 162
Part 4. Installing and Upgrading Client Access . . . 163
Chapter 22. Migrating or Upgrading from a Previous Client Access Release 165 Migrating from Client Access for Windows 3.1 to Client Access for Windows 95/NT . 165 Client Access for Windows 3.1 vs Client Access for Windows 95/NT. . . 165
Upgrading from a Previous Client Access for Windows 95/NT Release . . . 166
Upgrading from V3R1M3 to V3R2M0 . . . 166
Chapter 23. Installing and Migrating Client Access on Your PC . . . . 169
Installation Media . . . 170
Installation and Migration Wizard . . . 171
Operations Navigator . . . 175
Operations Navigator Extensions - installation and use . . . 176
Welcome Wizard . . . 180
Installing From a Peer Server . . . 180
Automating Installation . . . 182
Silent Installation . . . 182
Selective Install/Uninstall . . . 184
Multiple computer install . . . 186
Remote Installation from a File Server. . . 187
Using RUNRMTCMD to Selectively Install New Components . . . 187
Client Access Service Packs . . . 188
Controlling Client Access Login Service Check . . . 188
Checking Version & Service Level . . . 188
Installing Client Access Service Packs. . . 189
Creating Client Access Installation and Service Pack diskettes . . . 189
Removing Client Access from your personal computer . . . 191
What Happens When You Migrate a Client . . . 192
Chapter 24. 16–bit Client Access Information . . . 195
Using 16–bit Client Access APIs . . . 195
Enabling 16–bit API Support . . . 195
Enabling 16–bit Client Access APIs . . . 196
PTFs for 16–bit API Support . . . 197
16-Bit ODBC Applications . . . 198
Connecting with TCP/IP or IPX . . . 198
Connecting with Systems Network Architecture (SNA) . . . 198
Part 5. Getting Connected . . . 199
Chapter 25. Client Access for Windows 95/NT: TCP/IP Connectivity Steps. 201 Before you start, please read. . . 201
Configure the connection . . . 202
Creating a Common Configuration with Multiple Users on Windows NT. . . 210
Considerations . . . 210
Chapter 26. Client Access for Windows NT: Twinax Connectivity Steps. 211 Before you start, please read. . . 211
Configure the connection . . . 211
Chapter 27. Client Access for Windows 95: Twinax Connectivity Steps. 225 Before you start, please read. . . 225
Configure the connection . . . 225
Chapter 28. Client Access for Windows 95/NT: 802.2 Token-Ring and Ethernet Connectivity Steps . . . . 247
Before you start, please read. . . 247
Configure the connection . . . 247
Advanced Configuration . . . 259
Sharing Local SAP Limitation . . . 259
Ethernet Converted Addresses . . . 259
Chapter 29. Client Access for Windows 95/NT: SDLC Connectivity Steps 261 Before you start, please read. . . 261
Configure the connection . . . 262
Chapter 30. Client Access for Windows 95/NT: Asynchronous Connectivity 275 Before you start, please read. . . 275
Configure the connection . . . 275
Chapter 31. Client Access for Windows 95/NT: AutoSync Connectivity . . . 287
Before you start, please read. . . 287
Configure the connection . . . 287
Chapter 32. Client Access for Windows 95/NT: AnyNet (APPC over TCP/IP) Connectivity . . . . 301
Before you start, please read. . . 301
Configure the connection . . . 301
Chapter 33. Client Access for Windows 95/NT: IPX Connectivity Steps . . . 315
Before you start, please read. . . 315
Configure the connection . . . 315
Testing Your Connection . . . 322
Chapter 34. Using Other SNA Providers . . . . 323
Part 6. Using Client Access . . . 325
Chapter 35. Getting to Know Client Access . . . . 327
Client Access Menu . . . 327
Online User’s Guide and Help Information . . . 330
The AS/400 Connections Window . . . 331
Using Environments. . . 332
Using View. . . 332
AS400 Operations Navigator . . . 333
Mapping a network drive from Windows 95/NT . . . 333
Chapter 36. Policy Management . . . . 335
AS/400 system configuration . . . 336
The Policy Editor. . . 337
Policy Files . . . 338
PC configuration - Windows 95 . . . 338
PC configuration - Windows NT . . . 340
Chapter 37. AS/400 Operations Console . . . . 341
Before you start, please read. . . 341
Requirements . . . 342
Installing Operations Console Cable . . . 343
Install Operations Console support . . . 351
Installing Windows 95 Console Support . . . 352
Windows 95 Local Controlling System (LCS) . . . 354
AS/400 setup . . . 354
PC setup . . . 356
Windows 95 Remote Controlling System (RCS) . . . 359
Installing Windows NT Console Support . . . 359
Windows NT Local Controlling System (LCS) . . . 365
AS/400 setup . . . 365
PC setup . . . 367
Windows NT Remote Controlling System (RCS) . . . 369
Preparing for IPL. . . 370
Chapter 38. PC5250 Information . . . . 373
AS/400 Client Access for Windows 95/NT PC5250 Console . . . 373
Overview . . . 373
Hardware Requirements and Software Requirements. . . 375
Installation Overview . . . 375
Hardware Installation . . . 375
Software Installation . . . 380
PC5250 Emulation . . . 381
Starting a 5250 Printer Emulation Session . . . 381
Starting a 5250 Display Session. . . 382
Chapter 39. Using Client Access ODBC with Windows NT Service . . . . . 383
Using Client Access ODBC with a Windows NT Service (User Account) . . . . 384
Using Client Access ODBC with a Windows NT Service (System Account) . . . 385
Considerations for Using ODBC with a Windows NT Service . . . 385
Chapter 40. Graphical Access . . . . 387
Restrictions . . . 389
System Value Recommendations . . . 389
Part 7. Additional Information . . . 391
Chapter 41. Techniques, Tips, and Commands . . . . 393
The ReadMe File . . . 393
Changing the Managing System . . . 393
Create or Change Hosts File . . . 393
Client Access Security Consideration . . . 395
Adapters . . . 395
PC local area network (LAN) Adapters . . . 395
Integrated PC Server Adapters . . . 395
Modems . . . 396
802.2 Link . . . 396
Enable Query Response . . . 396
Universal Naming Convention . . . 396
Starting the PC Organizer . . . 397
Using the Integrated PC Server for AS/400 with Client Access. . . 397
Using Client Access with Lan Server/400 . . . 397
SLIP Support on the PC . . . 397
Data Transfer Setup . . . 398
Starting Data Transfer . . . 398
ODBC Performance and Send Buffering . . . 398
Examples . . . 400
NT Roaming User Profiles . . . 401
Command Syntax . . . 402
SETUP.EXE . . . 403
Start PC5250 Session (PCSWS) . . . 404
Start Directory Update (CAUPDT) . . . 404
AS/400 Operations Navigator (CWBUNNAV) . . . 405
Work with Spooled Files (WRKSPLF) . . . 405
Work with Printers (WRKPRT) . . . 405
Work with Messages (WRKMSG) . . . 405
Work with User Job (WRKUSRJ) . . . 406
Appendix A. IBM AS/400 Support for Windows Network Neighborhood (AS/400 NetServer) Information . . . 407
AS/400 Information . . . 407
PC Information . . . 409
Appendix B. Using Client Access with Facsimile Support for AS/400 . . . . 413
Create a Fax Printer Device Description on the AS/400 System . . . 413
Set up a Network Printer on the Client Access Workstation . . . 414
Configure a Printer Port to use the Fax Printer Device Description . . . 414
Appendix C. Problems and Problem Reporting . . . . 417
AS/400 Directory Services and SSL . . . 417
Finding and Correcting TAPI Problems . . . 417
Obtaining a Log of Modem Commands . . . 418
Anynet Connection Problem . . . 419
Central Processing Unit (CPU) Utilization. . . 420
SNA Data Corruption using TCP/IP. . . 420
Overlayed Icons . . . 420
Dial-Up Networking Prompt . . . 420
Problem Reporting - Gathering Information for IBM Support . . . 421
Appendix D. PC5250 Language Support . . . . 423
Lao Support . . . 423
Installation of Fonts . . . 423
Configuring a PC5250 session for Lao Support. . . 423
Switching between Lao and Latin Keyboard . . . 423
Language Shift Status . . . 423
Lao Display Composed mode . . . 423
Lao-Scaleable (Truetype) Font for Printing . . . 424
Print Space Adjustment . . . 424
Configuring PC5250 for Thai (Thai only) . . . 425
Thai Display Mode Selection (Thai only) . . . 425
Switching between Thai and Latin Keyboard . . . 425
Language Shift Status (Thai only) . . . 425
Thai Display Composed mode (Thai only) . . . 425
Bidirectional Arabic Support . . . 426
Limitations . . . 426
Installation Tips . . . 426
Bidirectional Keyboard Components . . . 427
Operator Information Area Indicators . . . 428
Bidirectional Hebrew Support. . . 428
Limitations . . . 428
Installation Tips . . . 428
Bidirectional Keyboard Components . . . 429
Operator Information Area Indicators . . . 430
Appendix E. Information authorized program analysis report (APAR) . . . . 431
Appendix F. Incoming Remote Command . . . . 433
AS/400 RUNRMTCMD Command . . . 434
TCP/IP Environment . . . 436 Implementation - Windows 95 . . . 436 Implementation - Windows NT . . . 438 APPC Environment . . . 439 Implementation . . . 440 Description of Parameters. . . 441
Appendix G. Twinaxial Information . . . . 443
Setup Considerations . . . 443
Appendix H. Notices . . . . 449
Trademarks . . . 450
Index . . . 453
Readers’ Comments — We’d Like to Hear from You . . . . 465
About Client Access for Windows 95/NT — Setup (SC41–3512–05)
Before You Use This product
Client Access for Windows 95/NT provides several functions and Application Programming Interfaces (application program interfaces (application program interface (API))) that are used in a client-server environment. Client Access supports ODBC (Open Database Connectivity) in a multiuser environment like Windows NT Service.
Some of the screens in this book may not be the same if you are using Windows 95 OSR2 (Operating System Release 2) or newer service packs for Windows NT. Microsoft changes their screens periodically.
Use this book to install and configure Client Access on both the AS/400 system and the personal computer (PC). This book is a supplement to AS/400 software installation books and communications books.
Aptiva Users Take Note
The IBM AS/400 Client Access family of products does not support the IBM Aptiva Personal Computer since the Aptiva is exclusively designed and tested to be used in a home environment, not in a commercial, networked environment. IBM has specific PC products to fulfill the commercial market.
Who should read this book
You should read and use this book if you are responsible for installing and configuring AS/400 Client Access for Windows 95/NT.
Conventions and terminology that are used in this book
Several conventions are used throughout this book.
v The term PC is used throughout this book to refer to personal computer. v The term AS/400 NetServer is used throughout this book to refer to IBM AS/400
Support for Windows Network Neighborhood.
v Wherever you see Windows 95 mentioned in this book, you can substitute Windows
98.
AS/400 Operations Navigator
Note: To use AS/400 Operations Navigator, you must have Client Access installed on your Windows 95/NT PC and have an AS/400 connection from that PC. This book tells you how to install Client Access on both the AS/400 system and the PC. It also tells you how to configure a connection to the AS/400 system and contains general information about Client Access.
AS/400 Operations Navigator is a powerful graphical interface for Windows 95/NT clients. With AS/400 Operations Navigator, you can use your Windows 95/NT skills to manage and administer your AS/400 systems.
v You can work with basic operations (messages, printer output, and printers), job
management, system configuration, network administration, security, users and groups, database administration, file systems, and multimedia.
v You can schedule regular system backups, work with Interprocess Communication
through application development, and manage multiple AS/400 systems through a central system by using Management Central. You can also customize the amount of Operations Navigator function that a user or user group can use through application administration.
v You can create a shortcut to any item in the explorer view of Operations Navigator. For example, you can create a shortcut either to Basic Operations or to the items that are listed under Basic Operations (Messages, Printer Output, and Printers). You can even create a shortcut to an individual printer or use a shortcut as a fast way to open the item.
Figure 1 shows an example of the Operations Navigator display:
IBM recommends that you use this new interface. It has online help to guide you. While we develop this interface, you will still need to use either of the following to do some of your tasks:
v Graphical Access (which provides a graphical interface to AS/400 screens). Graphical Access is part of the base Client Access.
v A traditional emulator such as PC5250.
Installing Operations Navigator subcomponents
AS/400 Operations Navigator is packaged as separately installable subcomponents. If you are upgrading from a previous release of AS/400 Operations Navigator, only those subcomponents that correspond to the function that is contained in the previous release will be installed. If you are installing for the first time and you use the Typical or Minimum installation options, the following options are installed by default:
v Operations Navigator base support
v Basic operations (messages, printer output, and printers)
To install additional AS/400 Operations Navigator subcomponents, either use the Custom installation option or use selective setup to add subcomponents after Operations Navigator has been installed:
1. Display the list of currently installed subcomponents in the Component Selection window of Custom installation or selective setup.
2. Select AS/400 Operations Navigator and click Details.
3. Select any additional subcomponents that you want to install and continue with Custom installation or selective setup.
Accessing AS/400 Operations Navigator
To access Operations Navigator after you install Client Access and create an AS/400 connection, do the following:
1. Double-click the Client Access folder on your desktop.
2. Double-click the Operations Navigator icon to open Operations Navigator. You can also drag the icon to your desktop for even quicker access.
Prerequisite and related information
This book contains directions for installing Client Access on both the AS/400 and the PC. Checklists help you step through the steps that you need to complete to be able to use Client Access. You should know how to get around on both the AS/400 and on the Windows 95 or NT operating system.
Use the AS/400 Information Center as a starting point for your AS/400 information needs. It is available in either of the following ways:
v The Internet at this uniform resource locator (URL) address:
http://publib.boulder.ibm.com/html/as400/infocenter.html v On CD-ROM:AS/400e series Information Center, SK3T-2027-00.
The AS/400 Information Center contains browsable information on important topics such as Java, program temporary fixes (PTFs), and Internet security. It also contains
hypertext links to related topics, including Internet links to Web sites such as the AS/400 Technical Studio, the AS/400 Softcopy Library, and the AS/400 home page. If you have access to the Internet, see “Sources of Information for Installing Client Access” on page 6 for web page addresses related to Client Access for Windows 95/NT. You may need to refer to other IBM books for more specific information about a
particular topic. See “Books that contain related information” on page 7 for a list of books that contain related information.
How to send your comments
Your feedback is important in helping to provide the most accurate and high-quality information. If you have any comments about this book or any other AS/400 documentation, fill out the readers’ comment form at the back of this book.
v If you prefer to send comments by mail, use the readers’ comment form with the address that is printed on the back. If you are mailing a readers’ comment form from a country other than the United States, you can give the form to the local IBM branch office or IBM representative for postage-paid mailing.
v If you prefer to send comments by FAX, use either of the following numbers:
– United States and Canada: 1-800-937-3430 – Other countries: 1-507-253-5192
v If you prefer to send comments electronically, use this network ID:
– IBMMAIL, to IBMMAIL(USIB56RZ) – [email protected]
Be sure to include the following:
v The name of the book.
v The publication number of the book.
v The page number or topic to which your comment applies.
For more information about Client Access
Information APARs and faxes
Information APAR II09209 contains an index to the latest Client Access Family information (that includes program temporary fix (PTF) information). See “Information Authorized Program Analysis Report (APAR) and PTFs” on page 8 and “Appendix E. Information authorized program analysis report (APAR)” on page 431 for more information about Information APARs. If you have Internet access, you can get to the Client Access home page by using this address:
Go to the Information APARs section.
If you have access to a fax machine, you can request a list of available Client Access faxes by calling1-800-IBM-4FAX (1-800-426-4329)and requesting document number
4954.
Part 1. Getting Started
Chapter 1. What You Need to Know Before You Start . . . 3
About Client Access for Windows 95/NT . . . 3
Migrating from Client Access for Windows 3.1 to Client Access for Windows 95/NT . 3 Functional Comparison Between Client Access for Windows 3.1 and Client Access for Windows 95/NT . . . 4
Important Information about Setting Up Client Access . . . 5
Sources of Information for Installing Client Access. . . 6
Books that contain related information. . . 7
Information Authorized Program Analysis Report (APAR) and PTFs . . . 8
Client Access for Windows 95/NT ReadMe File. . . 8
Service Packs. . . 8
Online User’s Guide for Client Access . . . 9
License Information . . . 9
Minimum PC Hardware Requirements. . . 13
PC5250 Emulation . . . 13
Miscellaneous Tips . . . 13
Chapter 2. Setup Checklist . . . . 15
Chapter 3. Installing Client Access on the AS/400 System . . . . 21
Operating System/400 Releases that Support Client Access for Windows 95/NT. . 21
AS/400 Storage Requirements . . . 22
AS/400 Disk Space for PowerPC AS (RISC) processor models: . . . 22
Installation Options on the LICPGM Menu . . . 23
Replacing Licensed Programs and OS/400 . . . 23
Adding Licensed Programs . . . 23
Installing Client Access for Windows 95/NT on AS/400 with GO LICPGM . . . . 24
Installing Client Access for Windows 95/NT with RSTLICPGM . . . 25
Saving Client Access for Windows 95/NT. . . 26
Verifying Your Installation . . . 27
Deleting Client Access for Windows 95/NT . . . 28
Chapter 1. What You Need to Know Before You Start
This chapter contains critical information for AS/400 system administrators, local area network (LAN) administrators, and anyone else involved in installing Client Access. It does not contain complete setup information. Some information that is contained here is duplicated in the body of the book. This is intentional.
This chapter contains several information resources with examples of how to access these resources. Also included is information that you need to gather before you begin your installation. This information includes what you need to know about setup on both the AS/400 system and the PC.
About Client Access for Windows 95/NT
Client Access for Windows 95/NT allows you to connect a personal computer (PC) to an AS/400 system over a local area network, a twinaxial connection, or a remote link. It has a complete set of integrated functions that enable desktop users to use AS/400 resources as easily as their local PC.
Migrating from Client Access for Windows 3.1 to Client Access for Windows
95/NT
Windows 95 or Windows NT supplies much of the underlying communications support that is used by Client Access. This includes Transmission Control Protocol/Internet Protocol (TCP/IP), IPX/SPX, and many adapter drivers. Client Access for Windows 95/NT also includes the NS/Router for Systems Network Architecture (SNA) communications.
Client Access includes a migration wizard that helps convert configuration information from Client Access for Windows 3.1 into the format that is used by Client Access for Windows 95/NT. The information is taken from the files CONFIG.PCS, NSD.INI, and PCS.INI. The migration wizard starts automatically at the end of the Windows 95/NT Installation Wizard. The Windows 3.1 client is kept, and the existing configuration is not changed.
Note: SNA configurations are not migrated from the XK1 Windows 3.1 client.
If you want to remove Client Access for Windows 3.1 from the PC, in addition to removing the old code, you must remove old entries from the system files (such as CONFIG.SYS, AUTOEXEC.BAT, SYSTEM.INI, and WIN.INI). If these entries are not removed, you may see errors when you start Windows 95 or Windows NT. Client Access for Windows 95/NT does not include the RUMBA/400 emulator. Thus, RUMBA/400 profiles are converted to PC5250 profiles. The following items are not migrated from RUMBA/400:
v User-created macros
v Keystroke mappings that specify macros and special characters other than those that are supplied with RUMBA/400
Not all configuration information can be migrated for workstation profiles, printer profiles, and keyboards. Icons that were dragged or moved to the desktop (not copied) are not migrated.
Note: You cannot automatically migrate the XK1 (Enhanced Windows 3.1 client) SNA connection configurations.
Functional Comparison Between Client Access for Windows 3.1 and Client
Access for Windows 95/NT
The following tables show the networks, application program interfaces (APIs), communication programs, and LAN drivers that are supported by Client Access for Windows 95/NT versus Client Access for Windows 3.1.
Table 1. Functional Comparison Between Client Access for Windows 95/NT and Client Access for Windows 3.1
Functions Windows 3.1 Windows 95/NT
SNA Networks
Token-Ring X X
Ethernet X X
Twinax X X
synchronous data link control (SDLC)
X X
Asynchronous X X
X.25 X
AutoSync X
Communications Programs Supported
CA/400 NS/Windows (16-bit router) X
NS/Router (16-bit router) X
NetWare for SAA (16-bit router) X
NS/Router (32-bit router) X
NetWare for SAA (32-bit router) X
MS SNA Server X
IBM Personal Communications X
IBM Comm Server X
WINAPPC compatible X
Winsock 1.1 compatible X
Table 1. Functional Comparison Between Client Access for Windows 95/NT and Client Access for Windows 3.1 (continued)
Functions Windows 3.1 Windows 95/NT
LAN Support Program X
MS DLC (16-bit) X
MS DLC (32-bit) X
Communication APIs Provided
EHNAPPC (16–bit) X X EHNAPPC (32–bit) X CPI-C X X TCP/IP Networks Token-Ring XK1 only X Ethernet XK1 only X Asynchronous (SLIP) X X
PPP (Point to Point Protocol) X
Twinax X
TCP/IP Networks (AnyNet)
Token-Ring X X
Ethernet X X
Asynchronous (SLIP) X X
TCP/IP Stacks Supported
IBM DOS (V2.1.1) X
FTP OnNet 1.1 (Windows) X
Microsoft WFW (32-bit) X
Novell (V4.2) X
WRQ V4.01 (Windows) X
NetManage Chameleon (Windows V4.01)
X
Microsoft Windows 95 (32-bit) X
Microsoft Windows NT (32-bit) X
Important Information about Setting Up Client Access
Before you begin the installation, you should know which configuration you will be using. The communication configuration option you choose requires some setup on both your AS/400 system and the PC (client) you will be using.
Setting up Client Access involves four steps: __ 1. Configuring the AS/400 system.
__ 2. Setting up and preparing the PC (includes possible hardware configurations). __ 3. Installing Client Access software on the PC.
__ 4. Configuring communications on the PC.
This setup process involves both configuring the AS/400 and the PC. Therefore, you must have good communication between your AS/400 administrator and the person who configures the PC. The parameters necessary for setting up the PC are determined by the AS/400 setup.
If you are the person configuring both the AS/400 and the PC, you need to keep track of the choices you make as you configure the AS/400. You need this information when you configure the PC.
Note: The security level required for configuring the AS/400 is *SECOFR. (This is the highest level of security on the AS/400.) This security level is required for configuration, not for regular use of Client Access.
Sources of Information for Installing Client Access
There are several ways to get information about installing and configuring Client Access. You can find late-breaking information on the World Wide Web, in the ReadMe files that come with Client Access, and in Information APARS (see “Information Authorized Program Analysis Report (APAR) and PTFs” on page 8 for more information).
If you have browser access to the Internet, you can access information on the World Wide Web (WWW) from the Client Access folder. This folder is available after you install Client Access. Some of the places you may want to get information from are listed in the following table, along with their web page addresses.
Table 2. Web Page Addresses Related to Client Access for Windows 95/NT
Web Page Address Title
www.ibm.com IBM Home Page
www.as400.ibm.com IBM AS/400 Home Page
www.as400.ibm.com/clientaccess/ IBM AS/400 Client Access Home Page www.pc.ibm.com IBM Personal Computers Home Page www.software.ibm.com IBM Software Home Page
www.netmanage.com NS/Router Home Page
www.as400service.ibm.com IBM AS/400 Service Home Page www.networking.ibm.com/ IBM Networking Home Page
www.networking.ibm.com/525 IBM Headquarters for 5250 Emulation Software and Hardware
Books that contain related information
You may need to refer to other IBM books for more specific information about a particular topic. For a complete overview of the AS/400 system publications, see the Publications Reference, SC41-5003-02.
Client Access Family.
v Client Access for Windows 95/NT API and Technical Reference, SC41-3513-03 v AS/400 Client Access Family of Products, G325-6336-02
v AS/400 Client Access Host Servers, SC41-5740-02
Other Books That Contain Related Information:
v Inside Client Access for Windows 95, SG24-4748 v 5394 Remote Control Unit User’s Guide, GA27-3852 v 5494 Remote Control Unit Planning Guide, GA27-3936 v 5494 Remote Control Unit User’s Guide, GA27-3960 v AS/400 AnyNet Scenarios, GG24-2531
v AS/400 Road Map for Changing to PowerPC Technology, SA41-4150 v Communications Configuration, SC41-5401-00
v Integration Services for the Integrated PC Server, SC41-5123-00 v Internetwork Packet Exchange (IPX) Support, SC41-5400-00 v LAN, Frame-Relay and ATM Support, SC41-5404-01 v OS/2 Warp Server for AS/400 Administration, SC41-5423-00 v Integrating AS/400 with Novell NetWare, SC41-5124-01 v Physical Planning Reference, SA41-5109-02
v Remote Work Station Support, SC41-5402-00 v Software Installation, SC41-5120-02
v Security - Basic, SC41-5301-00 v Security - Reference, SC41-5302-02
v TCP/IP Configuration and Reference, SC41-5420-02 v TCP/IP Fastpath Setup, SC41-5430-00
v Work Management, SC41-5306-02
v System Operation for New Users, SC41-3200-00
Note: All the above books can be viewed at the Client Access web page:
http://www.as400.ibm.com/clientaccess/
Information Authorized Program Analysis Report (APAR) and PTFs
An Information Authorized Program Analysis Report (APAR) is an electronic document that is used to communicate information not found in publications, the Online User’s Guide, critical fix information, or other sources.
Information APARs for Client Access for Windows 95/NT are available on the Internet or from the IBM fax information service. If you have Internet access, the index to Client Access for Windows 95/NT Information APARs is available at the following address:
http://www.as400.ibm.com/clientaccess/
Go to the Information APARS section and look under Windows 95/NT Information APARs.
If you prefer to receive a fax copy of this APAR, call 1-800-IBM-4FAX (1-800-426-4329) and request document number 4954.
Program temporary fixes (PTFs) are available to ensure that you have the latest program fixes. Make sure that you have the latest PTFs for OS/400 and Client Access. You can also get the APARs and PTFs for Client Access by using the Electronic Customer Support feature on your AS/400 system. You need to have Electronic Customer Support configured and operational. At an AS/400 command line, type SNDPTFORD PTFID(xxxxxxx), where the xxxxxxx represents the Information APAR number that you are requesting.
For more information about Information APARs, see “Appendix E. Information authorized program analysis report (APAR)” on page 431.
Client Access for Windows 95/NT ReadMe File
The Client Access for Windows 95/NT ReadMe file (README.TXT) is on the CD-ROM. The ReadMe file can also be accessed through the Client Access folder on your desktop after you install Client Access.
Service Packs
Client Access for Windows 95/NT has expanded support offerings beyond what is available for other AS/400 Client Access clients.
Be sure you have the most recent PTFs and service packs. This helps you avoid unnecessary calls to service for problems that may already have fixes, and creates a more stable operational environment for the Windows 95/NT client. In addition, a service pack can be installed directly on a PC, which may be preferable to installing individual PTFs on the AS/400 and downloading the upgrade to the PC. Nonetheless, you should also install the service pack on AS/400.
Service Packs can be obtained from the Client Access home page or from the IBM FTP site. To download from the home page, type in this address:
http://www.as400.ibm.com/clientaccess/
Go to Service Packs.
The service pack can also be obtained via the IBM FTP site on the Internet. Point your web browser to this address:
ftp://ftp.software.ibm.com
Navigate down the AS/400 directory to one of the following:
v as400/products/clientaccess/win32/v3r1m0/servicepack (for mod 0) v as400/products/clientaccess/win32/v3r1m1/servicepack (for mod 1) v as400/products/clientaccess/win32/v3r1m2/servicepack (for mod 2) v as400/products/clientaccess/win32/v3r1m3/servicepack (for mod 3) v as400/products/clientaccess/win32/v3r2m0/servicepack (for mod 0)
Online User’s Guide for Client Access
After installing Client Access, you have a valuable resource at your fingertips: The Client Access Online User’s Guide. This guide helps you find and correct problems and contains how-to procedures. Use the index in the guide to search for a specific topic. The Online User’s Guide walks you through many complex situations and helps you resolve most problems.
License Information
IBM AS/400 Client Access for Windows 95/NT is a licensed program (5763-XD1). Note: Client Access can be installed without a license, but you must have a license to
be able to use the functions that require a license.
For V3R7 and later, the functions listed below require a Client Access license before you can use them:
v PC5250 Display and Printer Emulator v PC5250 Fonts
v Data Transfer
v NS/Router (which supports SNA links) – 802.2 (Local Area Network)
– AnyNet (advanced program-to-program communications (APPC) over TCP/IP) – Async
– Autosync
– NetWare for Systems Applications Architecture (SAA) – Synchronous Data Link Control (SDLC)
– Twinax
v 16–bit Client Access API Support
For V3R7 and later, the functions listed below DO NOT require a Client Access license before you use them:
v Base support (which includes AS/400 TCP/IP communications)
– Network Drives (shared folders) – Network Printers
– Client Access/400 APIs such as Data Queues, ODBC, Remote Command, and many other functions
v AS/400 Operations Navigator (Unity) v Graphical Access
v AFP Workbench Viewer v AFP Printer Driver v SCS Printer Driver
v Application Development Toolkit v Additional Languages
For V3R1, V3R2, and V3R6 a license is required for all functions.
The type of install you choose to perform determines which components are installed. Following are the types of installs you can choose and whether or not a component requires a license to install:
v The Typical install choice includes components that require a license.
v The Minimum install choice does not include components that require a license.
v With the Custom install choice, you can choose which components to install. Whether or not a license is required depends on the components you select. Components that require a license are identified.
v With the To Server install choice, you can choose which components to install on a server. You can then install Client Access from the server. None of the components require a license to install on a server.
Note: This choice is available in English only.
Version 3 Release 1 and later of Client Access is licensed by the number of
use. If a PC connects to more than one Version 3 or later AS/400 system, that PC requires a license on EACH AS/400 system to which it connects.
A PC uses only one Client Access license per AS/400 system regardless of the number of sessions that are established to that AS/400 system. For example, you can start many 5250 emulation, data transfer, or other sessions to the system, but the PC requires only one license. In addition to a Client Access license, you may also need an OS/400 license for each PC on each Version 3 AS/400 system.
Client Access licensing is done at the Client Access Family level, not at the individual client product level. Therefore, any combination of the Client Access products is allowable up to the license limit that is acquired. Customers who acquire a Version 3 Client Access license are entitled to use any of the Client Access family products in any combination.
To determine the Client Access Family usage limit:
__ 1. Type the WRKLICINF command on the AS/400 system to which you intend to connect. A list of products is shown.
__ 2. Type a 5 in the entry field to display details for the Client Access/400 Family -Base product. This panel displays information about the license, including the usage limit. If the usage limit value is set to *NOMAX, then you have unlimited use of the product.
TheSoftware Installation, SC41-5120-02book has information about determining the usage limit for the Client Access Family.
The type of installation you choose determines which components are installed and the amount of disk space required. The following table outlines the disk space required for different components of Client Access.
Note: The requirements listed in Table 3 are for English. Other NLVs have different requirements.
Table 3. Disk Space Requirements for Client Access for Windows 95/NT Components
Disk space required for different components of Client Access on your PC
Base Support 17,851K
Table 3. Disk Space Requirements for Client Access for Windows 95/NT Components (continued)
AS/400 Operations Navigator (Unity) Operations Navigator Base Support Basic Operations
Job Management System Configuration Network
Security
Users and Groups Database File Systems
Multimedia (Includes Ultimedia Systems Facility) Backup Application Development Management Central Application Administration 21543K 5923K 174K 52K 301K 5504K 1043K 848K 749K 19K 3137K 373K 274K 2929K 211K Graphical Access 4909K
Graphical Access Fonts Baltic Fonts Latin-2 Fonts Cyrillic Fonts Latin-1 Fonts Greek Fonts Turkish Fonts 1900K 1877K 1896K 1889K 1884K 1883K
AFP Workbench Viewer 3609K
Data Transfer 1352K
Table 3. Disk Space Requirements for Client Access for Windows 95/NT Components (continued) PC5250 Fonts Arabic Fonts Baltic Fonts Latin-2 Fonts Cyrillic Fonts Greek Fonts Hebrew Fonts Lao Fonts Thai Fonts Turkish Fonts Vietnamese Fonts 375K 632K 316K 316K 316K 677K 567K 611K 316K 632K Printer Drivers AFP printer driver
SNA character string (SCS) printer driver
1304K 656K
SNA Communications Support 7762K Application Development Toolkit 6796K
16–bit API Support 1718K
AS/400 Operations Console 829K
Minimum PC Hardware Requirements
To run Client Access from your PC, see the hardware requirements in Table 4 on page 15 and in Table 5 on page 15.
PC5250 Emulation
The PC5250 emulator cannot auto-reconnect over SNA connectivity.
Miscellaneous Tips
Below is a list of general tips and information about Client Access. These tips may help prevent problems during the installation.
__ 1. The IBM AS/400 Client Access/400 family of products does not support the IBM Aptiva Personal Computer. The Aptiva is exclusively designed and tested to be
used in a home environment, not in a commercial, networked environment. To see more information about hardware and software that CA/400 has tested, go to:
http://www.as400.ibm.com/clientaccess
and go to the Compatilbility Testing section.
__ 2. If you use an SNA SDLC connection between the AS/400 and a PC, be prepared to spend time configuring the hardware from within Windows 95. Windows 95 does not automatically recognize an SDLC adapter. You may need to remove other drivers or cards, such as sound cards or serial mouse drivers, in order to use your SDLC adapter. Additionally, you may need to reassign communication ports to get the driver to work properly. If you are using Client Access with Windows NT, you do not have to configure the SDLC hardware. The Client Access Windows NT SDLC driver automatically recognizes your SDLC adapter. __ 3. Prior to the V3R1M3 release of Client Access, Check Version (that is also known
as Client Access Login Service Check) was added to your Startup program group when you installed Client Access. It is no longer in the Startup program group. Now you can designate when you want Check Version to run on the Client Access properties tab. See “Controlling Client Access Login Service Check” on page 188.
__ 4. For Windows 95, the NS/Router 802.2 Link requires that the Microsoft 32-bit MS DLC protocol (MSDLC32.EXE) and the updated version of this protocol
(DLCUPD32.EXE) be installed. These files are both self-extracting files. You can get the MS DLC 32 driver from Microsoft’s web site at:
http://www.microsoft.com
Chapter 2. Setup Checklist
Setting up Client Access for Windows 95/NT consists of installing and configuring software on an AS/400 system and a personal computer. Use this checklist to guide you through the steps that are needed to set up Client Access.
Some steps refer you to a task in another topic. Return to this checklist when you have completed the task in the other topic.
__ 1. If you are migrating or upgrading from a previous release of Client Access, skip the rest of this checklist and go to “Chapter 22. Migrating or Upgrading from a Previous Client Access Release” on page 165, then to “Chapter 23. Installing and Migrating Client Access on Your PC” on page 169.
__ 2. Were you using the Beta Product? If your workstations were using the Client Access for Windows 95/NT beta product, remove the product from your workstations before you install this product.
To remove the beta code from the client: __ a. Click on the Start button.
__ b. Select Settings. __ c. Select Control Panel.
__ d. Select Add/Remove Programs.
__ e. Select IBM AS400 Client Access for Windows 95/NT. __ f. Click on the Add/Remove button.
__ g. Restart the PC before installing Client Access. __ 3. Verify that your PC meets the following requirements.
Table 4. PC requirements — Processor & Memory
Operating System Processor Memory
Windows 95 v 80486 DX2 66MHZ minimum v Pentium recommended 16 MB minimum Windows NT Pentium 100 MHZ recommended v 24 MB supported minimum v 32 MB recommended
Table 5. Other PC requirements
Disk Space - Install v Minimum - 28858K v Typical - 53032K v Maximum - 82360K
Table 5. Other PC requirements (continued)
Disk Space -Component
See Table 3 on page 11 for the disk space required for different Client Access components. (These values may change slightly when service packs are applied.)
Adapter Card A communications adapter card to support your connection type. See the notes in “Adapters” on page 395.
Certified PC Windows 95 or Windows NT installed and configured on a PC that is certified to run Windows 95/NT. To find out if your PC is certified to run Windows 95/NT, contact the PC manufacturer. Information about IBM Personal Computers can be found at the following url:
http://www.pc.ibm.com/support/dtw95.html
__ 4. Confirm that you have the PC configured for the communications software that you plan to use. Client Access can use either of the following:
v the TCP/IP or IPX or SPX stacks that come with Windows 95 or Windows NT v various Systems Network Architecture (SNA) stacks like the NS/Router
included with Client Access.
__ 5. Install the required Client Access licensed programs and options on the AS/400 system.
Make sure that you have the latest PTFs for the IBM Operating System/400 (OS/400) and for Client Access for Windows 95/NT.
See the following information APARs for more information.
v II09209 contains an index to the latest Client Access Family information (including program temporary fix (PTF) information).
v II09220 contains an overview of Client Access for Windows 95/NT including release specific information.
Go to “Chapter 3. Installing Client Access on the AS/400 System” on page 21. __ 6. If you want to use the Document Library Services file system (QDLS), go to
“Chapter 4. Enrolling Client Access users on the AS/400 system” on page 31. (You can skip this step if you have already enrolled users for another client.) Otherwise, go to the next step.
__ 7. Configure the AS/400 system for the type of communication you plan to use. Find your communication type in the following list and go to the topic that is listed.
Table 6. AS/400 Communications Configuration Table
TCP/IP Token-Ring or Ethernet Go to “Chapter 5. Configuring TCP/IP LAN Connections on the AS/400 System” on page 33 .
TCP/IP Asynchronous (SLIP) (V3R2, V3R7 or later)
Table 6. AS/400 Communications Configuration Table (continued)
TCP/IP PPP (point-to-point protocol) (V4R2 only),
see theTCP/IP Configuration and Reference, SC41-5420-02.
SNA Token-Ring Go to “Chapter 9. Configuring SNA Token-Ring Connections on the AS/400 System” on page 71 .
SNA Ethernet Go to “Chapter 10. Configuring Systems Network Architecture (SNA) Ethernet Connections on the AS/400 System” on page 75 .
SNA Twinaxial Go to “Chapter 8. Configuring Systems Network Architecture (SNA) Twinaxial Connections on the AS/400 System” on page 67.
SNA synchronous data link control (SDLC) Go to “Chapter 11. Configuring SNA SDLC & AutoSync Connections on the AS/400 System”
on page 83.
SNA AutoSync Go to “Chapter 11. Configuring SNA SDLC & AutoSync Connections on the AS/400 System”
on page 83.
SNA Asynchronous Go to “Chapter 12. Configuring SNA Asynchronous Connections on the AS/400 System” on page 87.
AnyNet (advanced program-to-program communications (APPC) over TCP/IP)
Go to “Chapter 7. Configuring AnyNet - APPC over TCP/IP” on page 61.
IPX Go to “Chapter 13. Configuring the Internetwork
Packet Exchange (IPX) Support on the AS/400 System” on page 91.
5394 Go to “Chapter 14. Configuring 5394 Remote
Control Units” on page 107.
5494 Go to “Chapter 15. Configuring 5494 Remote
Control Units” on page 113.
__ 8. Configure the PC for connections.
Find the connection type that you plan to use from the following list and go to the topic that is listed.
Table 7. PC Communications Configuration Table
If you are using the TCP/IP support supplied with Microsoft Windows 95/NT, configure that support.
Go to “Chapter 19. Configuring Microsoft TCP/IP Support on the PC for Windows 95” on page 151 or “Chapter 20. Configuring Microsoft TCP/IP Support on the PC for Windows NT” on page 155 .
If you are using SNA Token-Ring or Ethernet connection types and the NS/Router, configure that support.
Go to “Chapter 16. Windows 95 Network Information” on page 135 or “Chapter 17. Windows NT Networking” on page 143. If you are using IPX, install and configure the
IPX protocol on the PC.
Go to “Chapter 21. Configuring the PC for the IPX Protocol” on page 161.
Table 7. PC Communications Configuration Table (continued)
If you are using SLIP with Windows 95, go to “Chapter 18. Configuring SLIP Support on the PC” on page 147.
If you are using PPP, see the appropriate information in theTCP/IP Configuration and Reference, SC41-5420-02, then go to “Chapter 25. Client Access for Windows 95/NT: TCP/IP Connectivity Steps.” on page 201 to configure a Client Access TCP/IP connection.
If you are using an asynchronous connection, go on to step 9.
If you are using MSSNA or IBM PCOMM, these are not part of Client Access for Windows 95/NT. You must install and configure them to be able to use them.
__ 9. Install Client Access on the personal computer.
Go to “Chapter 23. Installing and Migrating Client Access on Your PC” on page 169 .
__ 10. Establish a new connection. Table 8. PC Configuration Table
If you are using TCP/IP, go to “Chapter 25. Client Access for Windows 95/NT: TCP/IP Connectivity Steps.” on page 201 .
If you are using a Twinax adapter and Windows 95,
go to “Chapter 27. Client Access for Windows 95: Twinax Connectivity Steps.” on page 225. If you are using a Twinax adapter and Windows
NT,
go to “Chapter 26. Client Access for Windows NT: Twinax Connectivity Steps.” on page 211. If you are using AnyNet, go to “Chapter 32. Client Access for Windows
95/NT: AnyNet (APPC over TCP/IP) Connectivity” on page 301.
If you are using SNA Token-Ring or Ethernet, go to “Chapter 28. Client Access for Windows 95/NT: 802.2 Token-Ring and Ethernet Connectivity Steps” on page 247.
If you are using SDLC, go to “Chapter 29. Client Access for Windows 95/NT: SDLC Connectivity Steps” on page 261. SNA Autosync Go to “Chapter 31. Client Access for Windows
95/NT: AutoSync Connectivity” on page 287. If you are using an asynchronous connection, go to “Chapter 30. Client Access for Windows
95/NT: Asynchronous Connectivity” on page 275 .
If you are using IPX, go to “Chapter 33. Client Access for Windows 95/NT: IPX Connectivity Steps” on page 315.
__ 11. You have completed the Client Access setup.
__ a. Double click on the IBM AS400 Client Access icon.
__ b. Find the Client Access User’s Guide and double click on it.
These appendices contain miscellaneous information that you may find helpful especially if you are an experienced user.
v “Appendix A. IBM AS/400 Support for Windows Network Neighborhood
(AS/400 NetServer) Information” on page 407
v “Appendix B. Using Client Access with Facsimile Support for AS/400” on
page 413
v “Appendix C. Problems and Problem Reporting” on page 417
v “Appendix D. PC5250 Language Support” on page 423
v “Appendix E. Information authorized program analysis report (APAR)” on
page 431
v “Appendix F. Incoming Remote Command” on page 433 v “Appendix G. Twinaxial Information” on page 443
Chapter 3. Installing Client Access on the AS/400 System
Client Access is a licensed program for AS/400 business computing systems. You need theSoftware Installation, SC41-5120-02 book for your level of Operating System/400 to install Client Access on AS/400. The information in this chapter supplements the information in that book. If you are installing a new release of Operating System/400, be sure to follow the instructions in that book first, before you continue installing Client Access.
Note: Changing your AS/400 from Complex Instruction Set Computing (CISC) technology to PowerPC Technology (V4R1 and beyond) You must follow the instructions inAS/400 Road Map for Changing to PowerPC Technology, SA41-5150-03 to install the Client Access licensed program on the AS/400 system.
After you install the licensed program on the AS/400 system, return to this book to configure Client Access and install the licensed program on the individual workstations.
Operating System/400 Releases that Support Client Access for Windows 95/NT
Client Access products run on several releases of Operating System/400.
You can install Client Access for Windows 95/NT on the following releases of Operating System/400 on AS/400 systems:
v For CISC processor models:
– Version 3 Release 2 (V3R2)
v For PowerPC AS (RISC) processor models: – Version 4 Release 1 (V4R1)
– Version 4 Release 2 (V4R2) – Version 4 Release 3 (V4R3)
For IBM Operating System/400 Version 4 (OS/400) releases V4R1 and beyond, the AS/400 system installation menus support Client Access for Windows 95/NT. To install Client Access for Windows 95/NT, refer to the Software Installation book for the appropriate release.
AS/400 installation menus do not support licensed programs or options that are newer than the installed release of Operating System/400 like V3R2. To install any such new Client Access product or component, see “Installing Client Access for Windows 95/NT with RSTLICPGM” on page 25.
Table 9 lists the programs that you need to install.
Table 9. Programs to Install for Client Access for Windows 95/NT Support
Program Option Description
57xx-SS1 12 Operating System/400 Host
Servers
5763-XD1 Base Client Access/400 Optimized
for Windows
57xx-XW1 Base Client Access/400 Windows
Family - Base
57xx-TC1 TCP/IP
Notes:
1. If your Operating System/400 level is V3R2, substitute 5763 for 57xx
2. If your Operating System/400 level is V4R1, V4R2, or V4R3, substitute 5769 for 57xx.
3. For 57xx-XW1, the Work with Licensed Program (LICPGM) menu contains two options. You do not need to install the PC tools folder option.
4. Install 57xx-TC1 if TCP/IP is your connectivity choice.
5. You can use 57xx-XW1 if you just want to use Client Access but you need 5763-XD1 for the following:
v Service Pack management
v Secondary Language support
v Selective Install (through the managing system)
v Creating Install Diskettes
v Third party plug-in installation (also known as Operations Navigator extensions)
Third Party Plug-in Support: This support lets users install software from different vendors that extends the function of the Operations Navigator.
AS/400 Storage Requirements
Your AS/400 system must have sufficient storage to install Client Access for Windows 95/NT, or the installation cannot complete.
AS/400 Disk Space for PowerPC AS (RISC) processor models:
Amount
Purpose
136K ODBC Files
7.12M Online help information, online user’s guide, messages (This size is for the 2924 national language version (NLV) version. Sizes are different for every other NLV.)
1494K Printer Files 858K Service
For information about how to check for the amount of storage your system has available, see theSoftware Installation, SC41-5120-02 book.
Installation Options on the LICPGM Menu
Client Access supports licensed programs at mixed-release levels. With mixed-release level support, a licensed program that does not renew with Operating System/400 continues to run with the newer level of Operating System/400.
When you work with licensed programs that are supported at mixed release levels, note what the most commonly used installation processes do. The most common installation processes:
v Replace licensed programs while you also replace a release of OS/400. v Replace a single licensed program.
v Add a licensed program. For the purpose of this description, replacing a single
licensed program is the same as adding a licensed program.
Replacing Licensed Programs and OS/400
The automatic and manual installation procedures within the Software Installation book replace OS/400 and licensed programs. To perform the manual procedure, select option 1 (Install all) from the Work with Licensed Programs menu and use the install option value of 1=Installed products. The system then begins to replace your existing licensed programs. When the system encounters a product that is supported at mixed-release levels, it first checks the level of the product. If the licensed program on the system is the same level as the product on the installation media, the system does not replace the installed product.
Although you do not select options when you use the automatic procedure, the system processes licensed programs by default as if you did select these options.
Adding Licensed Programs
The procedure to add a licensed program or replace a single licensed program is the same. You select option 11 (Install licensed programs) from the Work with Licensed Programs menu. (See list item number 4 on page 24). Select the product you want from a list. The installation media installs this product. The installation program replaces the licensed program if it already exists on the system. This is true even when the system and the media both have the same level of the licensed program.
When you use this menu option to replace a licensed program, any PTFs that existed on the system need to be applied again. Use the latest comulative PTF package and apply these PTFs to the newly installed licensed program.
Important
When you install a new level of a licensed program over the same licensed program, any PTFs you had applied are lost. Therefore, be sure to back up your licensed programs. Use the latest cumulative program temporary fix (PTF) tape or Compact Disc package to apply any needed PTFs to the new level of the
licensed program.
Installing Client Access for Windows 95/NT on AS/400 with GO LICPGM
If your AS/400 system is not yet running a supported version of Operating System/400, see theSoftware Installation, SC41-5120-02 book to upgrade to the desired release. Upgrading Operating System/400 replaces your previous level of PC Support with Client Access.
If your AS/400 system was not running Client Access, see the topic “Installing Additional Licensed Programs” inSoftware Installation, SC41-5120-02.
If the GO LICPGM menu does not list Client Access for Windows 95/NT, you can install with Restore Licensed Program (RSTLICPGM), see “Installing Client Access for Windows 95/NT with RSTLICPGM” on page 25.
__ 1. Sign off workstation users and end connections. Make sure that all Client Access users sign off and end their connection to the AS/400 system before you install the Client Access for Windows 95/NT on the AS/400 system.
__ 2. Sign on to the AS/400 system with *SECOFR authority.
__ 3. Type WRKLIB and make sure that QIWS is not in the Library List. __ 4. Install Client Access on AS/400.
Tip
For information about option 11, see the topic “Installing Additional Licensed Programs” in theSoftware Installation, SC41-5120-02 book for the appropriate release of AS/400. That book contains information like the following:
v If products 5763-XW1 and 5763-SS1 are already installed they do not have to be reinstalled or updated.
v AS/400 must be in restricted state to install the Operating System/400
— Host Servers option.
__ 5. Type a 1 next to each of the required licensed programs and any other licensed programs you want to install.
Note: On Power PC AS systems, the product identifiers can also begin with 5716. On CISC systems, the product identifiers always begin with 5763. For example, the base products that are shown below are 5763-XXX on CISC system.
Required licensed program options: 57xxSS1 OS/400 - Host Servers
57xxXW1 Client Access/400 Windows Family - Base 5763XD1 Client Access/400 Optimized for Windows Optional licensed program options:
57xxTC1 TCP/IP Connectivity Utilities/400
Install this product if TCP/IP is your connectivity choice. __ 6. Apply Client Access for Windows 95/NT Client PTFs.
Install the latest cumulative PTF package on the AS/400 system. If you have already installed the latest cumulative package, you still need to install all 5763-XD1 PTFs from the cumulative PTF package a second time. The first time the PTF package was applied, AS/400 could not apply PTFs to the 5763-XD1 product.
Apply any additional PTFs that are listed in Informational APARs. Go to the Client Access web page and look in the Service Packs section.
http://www.as400.ibm.com/clientaccess/
__ 7. Continue the installation by returning to the checklist in “Chapter 2. Setup Checklist” on page 15.
Installing Client Access for Windows 95/NT with RSTLICPGM
__ 1. Sign on to the AS/400 system with security officer (*SECOFR) authority. __ 2. TypeRSTLICPGMat the AS/400 command prompt.
Specify the following parameters and values; use the defaults for the other parameters.
Parameter Value
Product 5763XD1
Device Name of the save device, for example TAP01.
Part to be restored *BASE
Language for licensed program Type xxxx, where xxxx is the National Language Version (NLV) identifier. Ignore this field if the NLV is English.
Example of Restore Licensed Program display.
__ 3. Save the licensed program.
To save the Client Access for Windows 95/NT programs, go to “Saving Client Access for Windows 95/NT”.
Saving Client Access for Windows 95/NT
To save Client Access for Windows 95/NT:
__ 1. Sign on to the AS/400 system. Use a user ID that has security officer (*SECOFR) authority.
__ 2. Initialize a tape. Use theINZTAPcommand to initialize a tape to hold the saved version of the product feature.
__ 3. TypeSAVLICPGMat the AS/400 command prompt.
Specify the following parameters and values and use the defaults for the other parameters.
Parameter Value
Product 5763XD1
Restore Licensed Program (RSTLICPGM) Type choices, press Enter.
Product . . . 5763XD1 Character value Device . . . TAP01 Name, *SAVF
+ for more values
Optional part to be restored . . *BASE *BASE, 1, 2, 3, 4, 5, 6, 7... Type of object to be restored . *ALL *ALL, *PGM, *LNG
Language for licensed program . *PRIMARY Character value, *PRIMARY... Output . . . *NONE *NONE, *PRINT
Release . . . *FIRST Character value, *FIRST Replace release . . . *ONLY Character value, *ONLY, *NO
Parameter Value
Device Name of the save device, for example TAP01.
Language for licensed program Type xxxx, where xxxx is the National Language Version (NLV) identifier. Ignore this field if the NLV is English.
Example of a Save Licensed Program display.
Verifying Your Installation
To verify that Client Access for Windows 95/NT installed correctly:
__ 1. Sign on to the AS/400 system. Use a user ID that has security officer (*SECOFR) authority.
__ 2. TypeCHKPRDOPTat the AS/400 command prompt.
Specify the following parameters and values and use the defaults for the other parameters.
Parameter Value
Product 5763XD1
Example of a Check Product Option display.
Save Licensed Program (SAVLICPGM) Type choices, press Enter.
Product . . . 5763XD1 Character value Device . . . TAP01 Name, *SAVF
+ for more values
Optional part to be saved . . . *BASE *BASE, 1, 2, 3, 4, 5, 6, 7... Release . . . *ONLY Character value, *ONLY Language for licensed program . *PRIMARY Character value, *PRIMARY... Object type . . . *ALL *ALL, *PGM, *LNG
Figure 3. Save Licensed Program (SAVLICPGM) display
