|
On 18th July, Mr.AS400@ibm.net wrote: >What local IPX support do you need for your 400? Is it interacting >with the Novell servers or routing for them? I'm trying to get AS/400 to interact with the Novell servers. I'm using the licensed program Enhanced Integration for Novell NetWare for this purpose. With this program, AS/400 users are able to log-in to NetWare servers, perform administrative tasks like creating volumes, printing and others. In order for this to happen, AS/400 uses the IPX protocol to communicate with the NetWare servers on the network. So the first step is to activate this protocol on the AS/400 and the second step is to install and load the Enhanced Integration for NetWare NLM on the NetWare servers I want the AS/400 to communicate with. In my case, the NetWare server is the IPCS on the AS/400 (it could be any ordinary PC server attached to the same network as the AS/400). If you refer to the manual "OS/400 Integrating AS/400 with the NetWare V3R7" SC41-4124-01 Chapter 15 the section on Deciding to what to configure, you will find there are 3 possible ways of configuring the Enhanced Integration for NetWare depending on the current setup. 1. An IPCS and the OS/400 Integration for Novell NetWare is installed. 2. An IPCS, the OS/400 Integration for Novell NetWare and Enhanced Integration for NetWare is installed. 3. Enhanced Integration for NetWare is installed but no IPCS is installed. As you can see, my current setup is #2. The manual says that to run Enhanced Integration for NetWare over the IPCS, I can use one of the IPX descriptions ALREADY on AS/400 (or create a new one); and the circuit that was created when OS/400 Integration for Novell NetWare was configured. So, I created a new IPX description and tried to reuse the circuit created previously. It turns out that the circuit is an FSIOP circuit and it cannot be started with Option 9 at the Work with IPx Circuits display. So, now I'm confused - what does the manual mean? I then tried to create a new circuit with a different name, same line description and same external IPX network number but got error that a circuit (i.e. the FSIOP circuit) already exists with the same external IPX network number. Since I was getting anywhere with setup#2, I tried setup#3. Hence, I wrote on 18th July: > Currently, I have set it up in such a way that my AS/400 is > connected to the LAN via an Ethernet card. The IPCS on the AS/400 is > connected to the same LAN as well. I created a new ipx description, > a line description for the Ethernet line and a new ipx circuit for > setting up as/400 local IPX support. The new ipx circuit has a different name, different line description BUT the SAME external IPX network number. On 18th July, Mr.AS400@ibm.net wrote: >By the way, I haven't been able to dig up anything on using SBACKUP >via the 400s tape drive. I can't find a book on it. Did you get any >further with that? All I see is how to back up the Network Storage >Spaces with standard backup. I would like to be able to use SBACKUP or >use the AS/400 tape drives via Novell, but ADSM is the only thing I >know of for that. I installed the latest Novell NetWare patches on the NetWare server running on the IPCS. Now, I can load SBACKUP just fine, but the AS/400 tape drive can't be deallocated after use with SBACKUP. BTW, what do you mean by standard backup and ADSM? Thanks. Adelaine * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.