As part of the September AS/400 announcements, IBM is once again releasing a new, enhanced version of Client Access/400 for Windows 95/NT. The new version number is V3R2M0; it supports OS/400 V3R2 and later. IBM’s major focus in this modification was to improve the AS/400’s ability to manage and control networked PCs. The highlights of this refresh include the following:
• Support for Microsoft Windows 98
• Support for Microsoft’s System Policy Editor
• AS/400 SDK for OLE DB and ActiveX
• 32-bit AFP Workbench Viewer
• NS/Router enhancements for SNA/Advanced Program-to-Program Communications (APPC) connectivity
• Enhancements to Operations Navigator Also being enhanced at this time is the Client Access/400 Enhanced Windows client. It now has full TCP/IP connectivity support for PC5250 printer emulation, device ID support, and automated logon support. See information APAR II 11226 for PTF availability.
The V3R2M0 version of the Windows 95/NT client will be available on September 11, 1998 for AS/400 systems running OS/400 V4R3 and September 25, 1998 for AS/400 systems running OS/400 V4R2, V4R1, and V3R2.
Windows 98 Support
The Client Access for Windows 95/NT client name is now something of a misnomer, because CA/400 V3R2 also supports Windows 98. If you are running the V3R1M3 client, it also can be used with Windows 98, provided you install Service Pack
SF48155 first. For more details, read the Information APAR II11274, which is available on the Client Access home page at http://www.as400. ibm.com/clientaccess.
Support for Microsoft System Policies
The CA/400 V3R2 client can help ease your PC administration load with newly added policy templates. These policy templates work with the Microsoft System Policy Editor to let AS/400 administrators pick and choose which Client Access functions are available to PC users. Administrators can create, edit, and change policy information. They can, for example, restrict the use of Operations Navigator or control user access to the Client Access Data Transfer function. Policies templates can be created for specific users and user groups; they can even be tied to specific PCs so that anyone who signs onto a particular PC will only have the capabilities assigned to that PC. With CA/400 V3R2, these policies can all be centrally controlled and downloaded into the Microsoft Policy Registry at logon time.
AS/400 SDK for ActiveX and OLE DB
OLE DB is a Microsoft specification that provides a single interface to data, no matter what format the data is stored in, e.g., in a database, document, spreadsheet, or electronic mail file. The OLE DB architecture supports everything from full database management systems (DBMS), such as that found on the AS/400, to Indexed Sequential Access Method (ISAM) files and PC text files. Accessing data is easier if one interface—which encompasses many types of data—is used, rather than a specific API for each data source. This area is where OLE DB works especially well. (Visit the Microsoft Universal Data Access Web site at http://www.microsoft.com/data to learn more about this architecture.)
Client Access first delivered an AS/400 OLE DB provider (a runtime driver) in the V3R1M3 client. The Client Access OLE DB provider allows 32-bit Windows client/ server
applications that are written to the OLE DB specifications to access AS/400 information via record-level access, PC programs, AS/400 commands, data queues, SQL, and stored procedures. These enablers work transparently across both SNA/APPC- and TCP/IP-based networks.
In this newest release, a software developer’s kit (SDK), called the AS/400 SDK for ActiveX and OLE DB, is included on the Client Access product family CD-ROM with the Windows 95/NT client. The SDK contains snap-in wizards for Visual Basic to make it easy to generate code to link to AS/400 data and services.
Documentation and user tool samples are also included for Delphi, PowerBuilder, Visual C++, Lotus 1-2-3, Microsoft Excel, and Internet Explorer, as well as other applications. Programmers like the GUI that Windows tools provide, but find it difficult to build client/server applications with good overall performance. Client Access provides the link to AS/400 services—by incorpor-ating the integral 32-bit Microsoft technology of OLE DB and ActiveX—so that programmers can easily take advantage of the trend toward network-based distributed computing solutions.
There are enhancements to ODBC in the new release, as well. The Client Access ODBC driver provides a viable option for using SQL to access the AS/400 database. The Microsoft ODBC Driver Manager version 3.0 is now shipping with the Client Access ODBC driver, which means that applications written to either ODBC 2.0 or 3.0 can access AS/400 database information over any supported connectivity method. This capability lets client/server applications take advantage of the new functions provided by the Microsoft ODBC 3.0 specification, but does not force shops to undertake rewrites of current applications that were programmed to the previous Microsoft ODBC 2.0 specification.
32-bit AFP Workbench Viewer
Prior to CA/400 V3R2, a light version of the 16-bit AFP Workbench product was included with many of the Client Access products. Users who wanted the full-function version needed to purchase it separately from IBM. Now the AFP Workbench Viewer has been rewritten as a 32-bit application, and the full-function version is included with the Windows 95/NT client (see Figure 1). The AFP Workbench Viewer can be used to allow a PC to display information stored in AS/400 spooled files (AFP and SNA Character Stream, or SCS). It can also be used to view image files on your PC (such as those stored in GIF,
TIFF, or JPEG formats). The AFP Workbench Viewer provides many user productivity aides, such as the ability to zoom in or search for specific portions of a stored document.
The Client Access Network Print program has also been enhanced. New parameters have been added in the Device Settings panel that is used with the AFP driver so that output can be sent as text rather than graphics. This capability will reduce the size of the printed output file, reducing the time it takes to send large print documents from your PC. Second, enhancements have been made in the print buffering technique to improve the performance for applications that make small-write AS/400 print requests to redirected PC printers, i.e., LPTs. By small-write, I mean applications that send one character at a time. The new enhancement means that these requests now will be buffered and sent as one request.
NS/Router Enhancements for SNA/APPC Connectivity
The Client Access NS/Router now supports the AutoSync I protocol, which was developed by Hayes Microcomputer Products, Inc. This protocol enables PCs using any asynchronous modem that supports AutoSync I to dial in to an AS/400 communications controller, such as the Electronic Customer Support (ECS) port. This eliminates the need for ASCII workstation controllers on the AS/400 or SDLC multiprotocol adapters on the PC side.
Panels were added to the NetManage Router (formerly the NS/Router) configuration screens so that users can specify a telephone number, location, and modem type.
The NS/Router now provides a new option for users who connect to an AS/400 over an asynchronous line. When a connection is started, the user is prompted to specify where the call is originating.
A user can define different dial-from parameters for each location (as shown in Figure 2). For example, one location may require that the user dial 9 to get an outside line, while another location may not. This is particularly useful for people who call in from different telephone numbers, such as laptop users, where the dialing string may change from location to location.
In OS/400 V4R2, the 5250 data stream was enhanced to enable twinax-connected PCs to run over TCP/IP protocols. This is accomplished by using IBM 5250 Express twinax adapter cards and other selected IBM twinax adapter cards with special twinax device drivers. Client Access now supports these environments; see Informational APAR II11022 for detailed information on this support
Operations Navigator Enhancements
Operations Navigator is rapidly evolving to become the interface for operating and administering AS/400 systems. It also provides many useful functions to sim-plify user access to AS/400 resources.
Operations Navigator has added some productivity aides such as the ability to drag and drop printer output to various printers or to the PC desktop and the ability to send and view AS/400 messages. You can also add Windows desktop shortcuts to specific Operations Navigator items—such as printers, messages, or jobs—by right-clicking on that item in Operations Navigator and selecting the option to create a shortcut (see Figure 3). Shortcuts let your users perform exactly the functions they want without bringing up the entire Navigator screen to perform one action.
Operations Navigator has been repackaged into multiple subcomponents so administrators can specify which functions a user can access. IBM has also added a new feature called Application Administration that allows an administrator to control which Operations Navigator functions are available to specific users (for example, system configuration and network security). The Application Administration information is stored in the AS/400 user profile. (This capability requires OS/400 V4R3.) APIs for Application Administration are also available so that administrators can control which other applications (besides Operations Navigator) users can access.
Operations Navigator V4R3 Enhancements
Although the focus of this article is the new Client Access/400 for Windows 95/NT client, it would not be complete without a discussion of OS/400 V4R3. Many of the functions that were added to the new client are only enabled if you are running V4R3. Operations Navigator provides the graphical interfaces and wizards needed to use these new functions. I will tell you about a few of the most important ones.
The Security Configuration wizard steps administrators through general security questions about their AS/400 environment, recommends security level and system value settings, and will change the system to reflect the recommended settings. This wizard allows customers to secure their AS/400 environments even though they may not be well- versed in AS/400 security issues.
Management Central is a methodology that is being developed for V4R3. It will make it easier to manage multiple AS/400 systems from a single location. It provides the ability to group AS/400 systems together in different views. In this release, it includes a tool called Performance Monitor. In the future, it will address other areas, such as the installation of PTFs, remote commands, and the ability to create packages of files and distribute them.
Performance Monitor combines AS/400 performance monitoring and data collection with real-time PC graphics. You can define monitors and thresholds for each monitor. If a defined threshold is reached, an AS/400 command or PC program can be started. The command or program may tell the system to hold jobs or page the system operator; you choose the action that is taken.
Database administration is made easier with Operations Navigator, as it now allows data to be updated within a table. Tables can be copied and moved between AS/400 systems, aliases can be created to any database object, and journals can be managed remotely.
The following AS/400 servers (some of which are new this release) have been added to the list of applications which can be set up and managed through Operations Navigator: NetServer (SMB) enhancements, Network File Server (NFS), Lightweight Directory Access Protocol (LDAP) Directory Server, and the Distributed Computing Environment (DCE) Server.
Other V4R3 Enhancements
Other new functions are available for OS/400 V4R3 machines that are built upon the Client Access Windows 95/NT client. For example, EZ Setup and Welcome
Center are companion programs that are delivered with new AS/400 hardware. EZ Setup guides users through the installation and configuration tasks involved in setting up a new AS/400 system. Wizards are provided to connect a PC to the AS/400; set the AS/400 system name, date, time, and security values; create AS/400 security and system operator profiles; define LAN connections for Token-Ring, Ethernet, and Integrated PC Server (IPCS) adapters; define TCP/IP interfaces; start TCP/IP and host servers; create shortcuts to AS/400, Technical Studio, and Service home pages; and install the Netscape Browser if it is needed. Welcome Center provides some of the same capabilities as EZ Setup does, but it is tailored to people who are familiar with are familiar with AS/400 setup. It provides browser-based information that guides users through the installation and configuration of a new AS/400.
Client Access has provided a function called PC Console (or Asynchronous Console) in many of its clients, including the clients for Windows 3.1, Enhanced Windows
3.1, OS/2, and Windows 95/NT. It enables PC5250 display emulation to be used as the AS/400 system console. This feature enables administrators and operators to manage their AS/400 systems from a PC. The PC is directly connected to an AS/400 system’s serial port via a special cable that is available from IBM. This function can be used with any release of OS/400.
Operations Console is an enhanced version of PC Console. It provides an AS/400 system console session and a graphical control panel application for improved operation of
AS/400 systems. Additionally, if you use a Windows NT workstation as the Operations Console (or local controlling system), you will gain support for modem connections from remote PCs (or remote controlling systems), enabling remote AS/400 system operations and service over TCP/IP networks. Operations Console requires OS/400 V4R3.
TCP/IP Connectivity for 5250 Emulators
The V3R1M3 version of Client Access for Windows 95/NT delivered native PC5250 TCP/IP support for printer emulation, workstation device ID naming, and the ability to bypass the OS/400 sign-on screen. These functions can now be used with OS/400 V3R2, V3R7, and V4R1 machines and later. See Information APAR II10918 for a list of
OS/400 PTFs needed to enable this support. TCP/IP capabilities were previously available in all supported single-byte character set (SBCS) national language versions (NLVs) and Japanese double-byte character sets (DBCSs). The V3R2M0 version of CA/400 completes this support by adding DBCS NLVs for traditional Chinese, simplified Chinese, and Korean. (This support is available only if you are running Client Access/400 V3R2.) Graphical Access for AS/400 now also supports native TCP/IP connectivity to designate a specific 5250 workstation device ID for display sessions and the ability to bypass the AS/400 sign-on screen if you are running V3R2.
To Order CA/400 V3R2
Customers who currently have the AS/400 Client Access for Windows family product can obtain the enhanced version by contacting their IBM representative. Here are details you’ll need to order the new version:
• If you have 5769-XW1 with OS/400 V4R1 or V4R2 and Software Subscription, you should order a copy of Feature 2640 of 5755-AS5.
• If you have 5763-XW1 with OS/400 V3R2, you will need to order a copy of Feature 1721 of 5755-AS3 and charge Feature 3100 of 5763-XW1.
• If you have 5716-XW1 with OS/400 V3R7, you will need to need to upgrade to OS/400 Version 4.
Figure 1: The full-function AFP Workbench Viewer—which was a separate product in earlier releases—is included with the Client Access for Windows 95/NT V3R2 refresh.
Figure 2: The NS/Router now provides an option to change the modem dialing string when calling your AS/400 from different locations.
Figure 3: A number of features have been added to the AS/400 Operations Navigator, including the ability to create desktop icons for AS/400 printers, jobs, and messages.
LATEST COMMENTS
MC Press Online