If you want to take advantage of a printer attached to the AS/400, but don’t want to install Client Access/400 on your PC, what can you do? If you are running OS/400 V4R2 or later, you can take advantage of file and print services without Client Access/400. With the new and exciting AS/400 Support for Windows Network Neighborhood (AS/400 NetServer), you can share AS/400 Integrated File System (AS/400 IFS) directories and AS/400 output queues without any additional software installed on the client’s personal computer. For more information about the AS/400 NetServer, see IBM’s Web site at http://www.as400.ibm.com/ NetServer.
If you simply need basic file and print services, you no longer need Client Access/400 installed on every client. Instead, you can use the Windows 95, Windows NT, or Windows for Workgroups operating systems. This support runs on top of TCP/IP, so TCP/IP needs to be configured on both the AS/400 and the desktop clients. Once TCP/IP support is configured, the client will see the AS/400 NetServer as just another TCP/IP computer in the Windows Network Neighborhood. A simple mouse click or a DOS network (net) command request will let you access what the AS/400 administrator has shared with the network.
If you still require the richer functions provided by Client Access/400, AS/400 NetServer allows you to install the Client Access/400 program across the network from the AS/400 system. The Client Access/400 and AS/400 NetServer programs are separate servers and can coexist on the same AS/400 systems and workstations.
All administration is performed with either AS/400 Operations Navigator or AS/400 NetServer APIs. Using AS/400 Operations Navigator, you can share AS/400 IFS directories and output queues with the network. All the access to these shared directories and output queues complies with the Common Internet File System (CIFS) standard currently being drafted, so future interoperability will be achieved with the AS/400 NetServer support.
The Universal Naming Convention (UNC) is used to identify the AS/400 NetServer in the network. The UNC name consists of serverNameshareName; where
serverName is the AS/400 NetServer server name and the shareName is the name of the shared resource. A share name is a unique name assigned to either an AS/400 IFS directory or an output queue that enables access to the resource for remote network users and applications. Individual network commands may require the serverName or the shareName. Examples of network commands that AS/400 NetServer will handle include the following:
• net view—This command lists the servers in your domain.
• dir qas400qca400—This command lists the files in the directory for the qca400
• net print qas400printer—This command lists the spooled files in the AS/400 output queue for the printer shared resource.
• net view 1.2.3.4—This command lists the shares for AS/400 NetServer with this IP address. Using the IP address in this way is only possible from within Windows NT.
• net view qas400.tcpip.domain—This command lists the shares for AS/400 NetServer using the fully qualified TCP/IP domain. Using the fully qualified name is only possible from within Windows NT.
AS/400 NetServer User
In order to communicate with AS/400 NetServer, both the Client for Microsoft Windows and TCP/IP must be properly configured on the user’s machine. Figure 1 shows the Network properties dialog box you use to configure both of these components. You can reach this screen by right-clicking on the Network Neighborhood icon and choosing Properties from the pop-up menu. You can also click on the Windows Start button, and choose Settings, Control Panel, then Network.
Be sure that the local PC client is configured with either Domain Name System (DNS) Windows Internet Name Service (WINS) or an LMHOSTS file so that your client is able to resolve the AS/400 NetServer server name to an IP address. If you are using a DNS or WINS server, it will need to be updated with an AS/400 NetServer entry.
• DNS—If a DNS server exists on your network, you can configure it to provide address resolution for your AS/400 NetServer.
• WINS—If an NT server exists on the network, it may provide the computer name-to-IP address resolution service.
• LMHOSTS or HOSTS file—This static configuration file can be configured to find computers, but these files may be difficult to administer in a larger network.
Double-click on your AS/400 NetServer icon from the Windows Network Neighborhood (as shown in Figure 2) to display the shared IFS directories and output queues. By clicking on Start, then Find, and then Computer and typing in the name of the AS/400 NetServer you wish to find, you can also use the Windows Find feature to access the AS/400 NetServer shared IFS directories and output queues. Windows Network Neighborhood is available through Windows Explorer, so AS/400 NetServer shares can be accessed in this way, as well.
The AS/400 NetServer shared resources are created with names that may or may not be different from the actual directory or output queue names. However, any operation you request on the shared object is really performed on the AS/400. For example, if you pause or purge a printer that is mapped to an AS/400 output queue, you are pausing or purging the AS/400 output queue, not the printer on the desktop client. Figure 3 contains an example of what an AS/400 output queue would look like when viewed through a Windows NT client.
Client Access/400 versus AS/400 NetServer
In the past, Client Access exposed the AS/400 IFS directories and AS/400 output queues to the network; there was no concept of shares. By default, AS/400 NetServer shares only the /QCA400 IFS directory with the users. This directory contains the Client Access/400 install images and standalone AFP and SNA Character String (SCS) printer
share.
drivers. This setup provides more control over what is shared with the network, with additional directories shared by the administrator as needed. AS/400 NetServer shares may be hidden from the network by ending the share name with a dollar sign ($). The share will not show up in Windows Network Neighborhood, and it will not show up in the list of shares. However, when the share is mapped to a network drive, Windows will show the share name, including the ending $ sign, in Windows Explorer.
You can also hide the AS/400 NetServer from the network by setting its browsing interval to zero. When the browsing interval is set to zero, the AS/400 no longer announces itself and its services to the network, so the AS/400 NetServer icon will no longer show up in the Network Neighborhood. Although AS/400 NetServer is hidden from the Network Neighborhood, you may still take advantage of the file and print services by clicking on Start, then Find, and then Computer. You can also use the AS/400 NetServer UNC name.
Shares for directories may be added with either read-only or read/write access, giving the administrator additional security choices for those users connecting through AS/400 NetServer. For example, a directory named PUBLIC could be shared with read/write access, while the AS/400 directory authority for group PUBLIC would have read-only access. This configuration would ensure that users could not make alterations to the directory. Of course, you will want to give the administrator full access to the directory.
AS/400 NetServer lets desktop clients take advantage of the file and print services of the AS/400 without even having an AS/400 user profile. Guest support allows you to take advantage of AS/400 IFS directories (including databases, stream files, and CDROMs) and AS/400 output queues without the additional administration of an individual user profile for each user. Of course, users acting as guests should not be able to access anything that requires secure support or special access. However, the guest support feature does allow instant file and print services access to an entire network.
Client Access/400 has richer functionality than AS/400 NetServer. Client Access/400 provides support for AS/400 terminal emulation, ODBC, and data transfer (which provides ASCII-to-EBCDIC translation) capabilities. The Server Message Block (SMB) protocol, which is an XOpen Standard that has been adopted by both Windows and AS/400 NetServer, does not handle ASCII-to-EBCDIC file data conversion. Client Access/400 does ASCII-to-EBCDIC conversion of the file data on the fly, which the AS/400 NetServer does not support at this time.
AS/400 NetServer Administrator Set Up
The administration of the AS/400 NetServer can be accomplished via AS/400 APIs; the same administration options are available through AS/400 Operations Navigator, which uses a GUI. You may use the AS/400 System API Reference as a guide when implementing AS/400 NetServer administration through your CL, COBOL, RPG, C, and C++ programs. With Client Access/400, you can access the AS/400 NetServer configuration through the following paths inside the AS/400 Operations Navigator:
• V3R1M3—AS/400 Network-AS/400 System-Network-Servers-NetServer
• V3R2M0—AS/400 Network-AS/400 System-Network-Servers-TCP/IPNetServer
Note that AS/400 System should be replaced by the name of the AS/400 system you are working with.
Figure 4 shows the AS/400 NetServer properties accessed through AS/400 Operations Navigator. You reach this screen by highlighting NetServer in Operations Navigator, right-clicking and selecting Properties from the context menu. The Server name is the name used on the network to access AS/400 resources; this is different than the AS/400 system name listed in the AS/400 network attributes. The AS/400 NetServer server name is defaulted to Q plus the system name, qas400, but does not change when the system name changes, so be sure to verify the correctness of this name. The domain should match the domain (workgroup) configured for the PCs in the network that will take advantage of AS/400 NetServer.
AS/400 NetServer configuration changes can only be carried out if the user has *IOSYSCFG (System Configuration) authority. Changes will not take effect until the AS/400 NetServer is restarted. Extra authority, namely *SECADM (Security Administrator), is needed if the guest user profile is changed. Remember that the AS/400 NetServer guest user profile is a untrusted user and must have no special authority. The guest user profile allows AS/400 file and print sharing by users who otherwise would not require an AS/400 user profile.
In addition to the AS/400 NetServer properties, you can also add AS/400 NetServer shares, both file and print, from the AS/400 NetServer icon in Operations Navigator. A special option to include the AS/400 NetServer print share recommended printer driver (as shown in Figure 5) is included for each print share, because the hardest part of printing is to match the client printer driver type with the actual printer type.
Complex Environment Considerations
AS/400 NetServer uses TCP/IP to participate in the Windows Network Neighborhood, since there is no native NetBIOS stack on the AS/400. This adds some complexity to the networking process used to make the AS/400 NetServer appear in the Windows Network Neighborhood. The Windows implementation of Network Neighborhood was originally designed to operate directly on top of the NetBIOS protocol, which forwards computer announcement messages across routers. Think of an announcement message containing text such as “I’m here in the network and I have services available.” However, if you are using TCP/IP for AS/400 NetServer, or other TCP/IP-based systems, these announcement messages are usually not forwarded across routers, in order to reduce network traffic. Unfortunately, depending on the complexity of your network topology, this may result in your AS/400 NetServer not showing up in the Network Neighborhood. There are several possible solutions, some listed here, that avoid the loss of this information.
• Contain your domain in a single subnet, so announcements do not have to be forwarded to another subnet.
• Use the Windows Internet Name Service (WINS) for your network computer name-TCP/IP address resolution strategy. WINS was created specifically for network topologies like this one.
• Configure TCP/IP routers so that broadcast datagrams are forwarded across subnets in the same way they are forwarded for NetBIOS.
In any case, the AS/400 NetServer and client PCs should be configured for the same domain (workgroup).
You may rest assured that the Start/Find/Computer button sequence on your Windows desktop (shown in Figure 6) will work in all situations, regardless of whether you implement one of the solutions listed.
The AS/400 NetServer uses the services of the AS/400 Network Print Server (NPS) to handle all print requests. Because of this fact, NPS must be active to process AS/400 NetServer print requests. Use the Start Host Server (STRHOSTSVR *NETPRT) command to start NPS.
Simple Setup
While there are many options available to you, if you want to get up and running with just the basic AS/400 NetServer support, you can follow these simple steps.
AS/400 Steps
• Ensure TCP/IP is configured and active.
• Verify the correctness of the AS/400 NetServer server and domain names using AS/400 Operations Navigator.
• Verify that the QSERVER subsystem is active.
• Verify that the Network Print Server is active.
• Make sure that needed resources are shared with the network. Client Steps
• Ensure that you have TCP/IP and Clients for Microsoft Networks configured.
• Verify that you can resolve the IP address of your AS/400 NetServer using DNS, WINS, or a PC’s local LMHOSTS file.
• Enjoy.
Lots of Service, Little Footprint
By using AS/400 NetServer, you can give your users desktop file and print services without burdening them with Client Access/400’s large footprint. It is very simple to get up and running with NetServer. Troubleshooting is also simple. Use the more detailed information at http://www.as400.ibm.com/NetServer to make the most of your AS/400 NetServer support. You’ll find a setup document, a command-line API mini-guide, tips and techniques, presentations, and other support documents.
Remember that Client Access/400 is still available for richer functions such as ODBC, terminal emulation, and ASCII-to-EBCDIC conversion. Client Access/400 and AS/400 NetServer can coexist, so users can take advantage of both.
Figure 1: To communicate with AS/400 NetServer, you must configure Client for Microsoft Windows and TCP/IP in your Windows 95 or Windows NT Network properties box.
Figure 2: You can display your AS/400 NetServer shares by using the Windows Network Neighborhood function.
Figure 3: AS/400 NetServer allows you to access AS/400 printer output queues through a Windows 95 or NT client.
Figure 4: You can access your AS/400 NetServer properties through the AS/400 Operations Navigator.
Figure 5: You can also add print shares to your AS/400 NetServer configuration. A separate option allows you to add file shares.
Figure 6: You can use Windows’ Find feature to locate an AS/400 NetServer on the network in the same way that you would locate a file on your PC.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online