![]() |
Chapter 7. Administration Overview
![]() Enhanced Integration for NetWare provides additional capabilities for managing your local servers on the Integrated PC Server and remote servers from AS/400 interfaces (CL commands and AS/400 panels). This chapter highlights differences between managing NetWare on a local Integrated PC Server and managing NetWare on a remote server. Then this chapter provides an overview of the NWSADM administration menu, a good starting point for managing NetWare servers. Finally this chapter includes various topics that can help you manage your NetWare servers more efficiently. The major topics in this chapter are as follows:
A listing of the NetWare 4.1 documentation is provided in the Appendix F. "Bibliography". Integrated PC Server and Remote Server Support Differences
![]()
![]()
|
Network Server Administration Menu To more easily work with the AS/400 objects that are used with NetWare 4.1, you can use the Network Server Administration menu. You can use this menu as a starting point to configuring and managing the AS/400 objects needed for OS/400 Integration Products for NetWare. You can get to this menu by typing GO NWSADM. You can also use the command grouping menus (GO CMDNWS and GO CMDNTW) to see a list of commands related to administering network servers, including NetWare servers. The CMDNWS and CMDNTW menus have options to reference each other. Figure 7-1. Network Server Administration Menu +--------------------------------------------------------------------------------+ |NWSADM Network Server Administration System: SYSTEMA | |Select one of the following: | | 1. Configure a network server | | 2. Start a network server | | 3. Stop a network server | | 4. Work with network server storage spaces | | | | 10. Change network server attributes | | 11. Change network server user attributes | | 12. Work with network server user enrollment | | | | 20. Work with network server status | | 21. Work with network server aliases | | | | 30. Submit a network server command | | More... | | Selection or command | | ===> | | | | F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant | | F16=AS/400 Main menu | | (C) COPYRIGHT IBM CORP. 1980, 1996. | +--------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------+ | NWSADM Network Server Administration | | System: SYSTEMA | | Select one of the following: | | | | 40. Work with configuration status | | 41. Work with user profiles | | | | 50. Install NetWare server | | 51. Work with NetWare volumes | | 52. Work with NetWare connections | | 53. Change NetWare Directory Services context | | 54. Work with NetWare authentication entries | | | | 70. Related commands | | | | | | | | Bottom | | Selection or command | | ===> | | | | F3=Exit F4=Prompt F9=Retrieve F12=Cancel F13=Information Assistant | | F16=AS/400 Main menu | +--------------------------------------------------------------------------------+
![]() Changing Defaults If you are primarily using NetWare support (rather than mostly IBM LAN Server for OS/400) you can change a number of defaults to be more appropriate for NetWare. You can use CHGNWSA, CHGNWSUSRA, or CHGCMDDFT reset options to save yourself time when entering command strings, and to tailor how AS/400 displays information. You can specify *NETWARE for the server type using the CHGNWSA command to have a change take effect for the whole system. "Step 9--Define Network Server Attributes (Optional)" contains specific examples that discuss how to take advantage of this function. Network Server User Attributes The Change Network Server User Attributes command changes defaults for an individual user. CHGNWSUSRA overrides the defaults that are set by the CHGNWSA command. For most of the commands that ask for server type, the default is *NWSUSRA. You can use the CHGNWSUSRA command to change the default values on an individual user profile basis instead of changing the command defaults. For more information about user attributes, see "Network Server User Attributes". To change the command defaults, use the Change Command Default (CHGCMDDFT) command. Table 7-2 shows a number of commands for which you may want to change the value to *NETWARE. The parameters to change are listed.
![]()
|
Changing the Name of Your Server You can change the name of your server by editing your AUTOEXEC.NCF file from the NetWare INSTALL utility. This allows you to specify a longer name than the eight characters allowed for the name of your network server description. If you use WRKNWSSTS to access your storage spaces, you do not need
to remember the NWSD name. AS/400 finds and displays all available NWSDs.
If you use WRKNWSSTG to access the storage spaces for the server you just
renamed, you need to know the NWSD name. You can get the matching NWSD
name for the NetWare server by using option 5 (display details) from the
WRKNWSSTS panel.
Varying Off or Downing the NetWare Server The process to take down a NetWare server on the Integrated PC Server differs from a PC-based server. When using a PC-based NetWare server, you use the DOWN command to stop the server. When using an Integrated PC Server, you must vary off the network server description using the Vary Configuration (VRYCFG) command. During the vary off procedure, the QFPADOWN.NCF file is processed. Processing
QFPADOWN copies files from the SYS: volume back to the E: drive. These
files include NETINFO.CFG and AUTOEXEC.NCF. The NetWare administrator can
add statements to this file, if needed, to run additional console commands.
Powering Down the AS/400 System When you use the PWRDWNSYS command to power down the system, ensure
that all of your NWSDs are varied off. If you specify the PWRDWNSYS command
with OPTION(*IMMED) or OPTION(*CNTRLD) with too small of a DELAY value,
there may not be enough time for the servers to vary off in a successful
manner, and damage to the NWSD can occur. The safest method is to vary
off your NWSDs before you power down the AS/400 system.
Submit Network Server Command (SBMNWSCMD) This command provides the option to run NetWare commands on the NetWare console from AS/400. It provides an alternative to going to the server or to using RCONSOLE. The results from the commands you run on the NetWare console are reported back to AS/400 where you can view the results in the detailed messages. You can submit NetWare commands a couple of different ways:
To see which NLMs are loaded on the server, enter the following: SBMNWSCMD CMD(MODULES) SERVER(server-name) SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)
![]() CMDTYPE(*OS2) commands flow over the NETBIOS communications path.
NetWare Monitor Job When a *NETWARE NWSD is varied on, a batch job is submitted to run in the QSYSWRK subsystem which communicates with the network server. The job is called the NetWare monitor job. The job remains active until the NWSD is varied off or until the job or subsystem is ended using the ENDJOB or ENDSBS command. For each active network server description, AS/400 starts a monitor job in the QSYSWRK subsystem for each network server description that is varied on. If the QSYSWRK subsystem is not active at the time the NWSD is varied on, the monitor job is not submitted. If the QSYSWRK subsystem is subsequently started, the monitor job for the varied on NWSD is started at that time.
![]() The monitor job can provide either basic functions or enhanced functions. Basic functions are provided as follows:
![]()
WRKNWSSTS SVRTYPE(*NETWARE)A corresponding message is also logged in the monitor job's job log.
![]()
![]()
![]()
In the three preceding cases, messages are logged to the *JOBLOG or the message queue based on the MSGQ value specified for the NWSD. If the value specified is *NONE, then no messages are logged on the AS/400 system. Contact successful with Enhanced Integration for NetWare NLM on server &1;Once the monitor job has contacted the Enhanced Integration for NetWare NLM, enhanced functions will be provided for the duration of the monitor job or until an unrecoverable communication error occurs. If the monitor job is unable to contact the Enhanced Integration for NetWare NLM, or if an unrecoverable communication error occurs after the NLM has been contacted, the monitor job will send message CPFA444 "Enhanced functions unavailable for server &1"; to the QSYSOPR message queue and to the monitor job's job log and the monitor job will continue to run at the basic function level.
![]() If a communication error occurs that prevents the monitor job from performing enhanced functions, you must correct the error and (re-)establish communications with the Enhanced Integration for NetWare NLM. This reactivates the enhanced functions provided by the monitor job. To establish communications with the Enhanced Integration for NetWare NLM, follow the recovery procedures outlined in message CPFA444. Restart the monitor job by selecting option 14 (Restart server) on the WRKNWSSTS SVRTYPE(*NETWARE) display (shown in Figure 17-1). Directing Messages to a Message Queue On the INSNTWSVR or CRTNWSD commands, you can specify where NetWare console and other NetWare message activity should be directed using the MSGQ keyword. The default setting is MSGQ(*JOBLOG) which indicates any NetWare console log messages and other NetWare message log activity will be directed to the monitor job's job log. This value can be changed to specify MSGQ(*NONE) indicating that no messages will be logged on the AS/400 system. In addition, the name of a particular message queue can be specified. If using the INSNTWSVR command, the message queue will be created automatically if it does not already exist. Be advised that NetWare console log activity has the potential to be voluminous. In either case, logging messages to the monitor job's job log or to a particular message queue, the message queue can become full. If messages are logged to the *JOBLOG and the job message queue becomes full, the job log will wrap overlaying the oldest messages logged. If messages are logged to a message queue and the queue becomes full, the monitor job will not be able to log any other messages to that queue until the queue has been cleared. Use the CLRMSGQ CL command to periodically clear messages from the queue. While the queue remains full, any message activity will be diverted to the monitor job's job log. Creating and Managing Message Queues When you create a network server description, a message queue option is specified to receive server console messages. The default on the INSNTWSVR and CRTNWSD commands is *JOBLOG. You can specify a specific message queue instead. If you specify a message queue, use the Display Messages (DSPMSG) command to view the server console messages. You can change the NWSD (CHGNWSD command) at any time, and the changes take effect immediately. Hints for Setting Up Message Queues To restrict access to the console log information on AS/400, create a message queue to contain the console log activity using AUT(*EXCLUDE). You can grant explicit authority to the message queue for any users who need access to the NetWare console log. Grant the authority using the Grant Object Authority (GRTOBJAUT) command. Specify this message queue for the server message queue (MSGQ parameter) on the command you are using:
To collect NetWare server messages so that you can easily display them later, you can do one of the following:
DSPMSG server1
Coexistence with OS/2 Warp Server for AS/400 AS/400 supports NetWare, FAT, and HPFS storage space formats. OS/2 Warp Server for AS/400 (Warp Server) uses the HPFS storage space format. Storage spaces are identified with a storage space format when they are created (with the CRTNWSSTG command) and this format cannot be changed later. Therefore, storage spaces formatted for NetWare cannot be used later for Warp Server and storage spaces formatted for Warp Server cannot be used later for NetWare. To view a list of storage spaces and their format types, display Work with Network Server Storage Spaces as described in Figure 8-1. The AS/400 ADDNWSSTGL command supports the ability to link storage spaces as read-only for *NETWARE drives. Warp Server does not support read-only drives because it uses *LANSERVER drives. If you are using both Integration for NetWare and Warp Server, refer to the OS/2 Warp Server for AS/400 Administration book, for information about how to configure the Windows 3.1 clients for Warp Server and for NetWare to coexist. For Windows 95, the Microsoft LAN client and the NetWare client can
coexist with no difficulty.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ] |