Chapter 7. Administration Overview

Attention:
Some AS/400 displays for administration that you use with Integration for NetWare are different when Enhanced Integration for NetWare is installed. Differences are marked. In most cases, managing NetWare servers on an Integrated PC Server is similar to managing a remote (PC-based) server. You manage the NetWare server from the NetWare console or from workstation-based utilities such as RCONSOLE. However, with OS/400 Integration Products for NetWare, you can also manage the servers using the AS/400 interfaces. The most common administrative tasks are managing the disk storage used by the Integrated PC Server and starting and stopping the Integrated PC Server. 

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: 

Related topics include the following: 

Integrated PC Server and Remote Server Support Differences

There are differences in what you can manage on a remote server from what you can manage on a server that is running on an Integrated PC Server (also called a local server). There are also differences in what you can manage on NetWare 4.1 and NetWare 3.12 remote servers, but these differences are directly related to fundamental differences between 3.12 and 4.10. The differences are pointed out at appropriate places in the text of this book. Table 7-1 shows some of the differences. 

Note:
Remote Integrated PC Servers are included in the column with NetWare 4.1 Remote. AS/400 cannot tell whether a remote server is running on an Integrated PC Server or not.

Table 7-1. Differences in Enhanced Integration for NetWare Management Capabilities
 
Function  Local Integrated PC Server  NetWare 4.1 Remote  NetWare 3.12 Remote 
User propagation  yes  yes  yes 
Volume management
- CRT, DLT, CHG  yes  yes  yes 
- Display, print volume information  yes  yes  yes 
- Volume description  yes  yes  no 
Monitor job
- Automatic partitioning of disk storage device  yes  no  no 
- Monitor log files  yes  no  no 
Disk statistics  yes  no  no 
Submit Network Server Command (SBMNWSCMD)  yes  yes  no 


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:   SYSAS400 |
| 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:   SYSAS400 |
| 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                                                           |
+--------------------------------------------------------------------------------+


Attention:
All of these options may not be available on your menu. Some of the options are available only when Enhanced Integration for NetWare is installed. 

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. 

Network Server Attributes

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"

Changing the Command Defaults

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. 

Attention:
Table 7-2 contains commands that are applicable to both Integration for NetWare and Enhanced Integration for NetWare, or just to Enhanced Integration for NetWare. 

Table 7-2. Changing Command Default Values for NetWare
 
Command  Parameter 
Work with Network Server Status (WRKNWSSTS) SVRTYPE 
Create Network Server Description (CRTNWSD) TYPE 
Create Network Server Storage (CRTNWSSTG) FORMAT 
Submit Network Server Command (SBMNWSCMD)  SVRTYPE 
Display Network Server User (DSPNWSUSR)  SVRTYPE 
Work with NWS User Enrollment (WRKNWSENR)  SVRTYPE 


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 server. 


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: 

  • CMDTYPE(*LCLNTW) 

  • This command goes to the server over a NetBIOS communications path. This command type is useful for debugging problems when the AS4NW410 NLM cannot be loaded or when the Enhanced Integration for NetWare feature is installed, but the Enhanced Integration for NetWare NLM is not loaded on the local Integrated PC Server. You can use this command type only with local servers, (NWSDs running on Integrated PC Servers). 

  • CMDTYPE(*NETWARE) 

  • This command goes to the server over an authorized connection. You can also use this command type to submit commands to local and remote 4.1 servers. 

To submit a CMDTYPE(*NetWare) command from the AS/400, the following conditions must exist: 
  • An authorized connection must exist between your AS/400 session and the server. 
  • The AS4NW410 NLM must be loaded on the server. 
  • You must have Operator rights for the server. Use NWADMIN and view Details of the appropriate server object to determine whether your user object needs to be added as an operator. 
The command works the same way for remote servers, except: 
  • NetWare disk devices are used instead of storage spaces, and those devices start at device 0 rather than device 8 
  • SBMNWSCMD is supported only on NetWare 4.1 remote servers, not on NetWare 3.12 remote servers 
  • NetWare 3.12 remote servers use a bindery and not an NDS tree; therefore, NDS-related activities do not function with NetWare 3.12 remote servers 

SBMNWSCMD--Example

To see which NLMs are loaded on the server, enter the following: 

SBMNWSCMD CMD(MODULES) SERVER(server-name) SVRTYPE(*NETWARE)

          CMDTYPE(*NETWARE)


Note:
You can use SBMNWSCMD to load and unload NLMs on a NetWare server. However, note the following: 
  • Utilities such as INSTALL load, but you cannot manipulate their user interface panels from AS/400 
  • You cannot unload the AS4NW410 NLM; this operation may hang the server in an infinite loop, requiring a restart. 
You can also submit CMDTYPE(*OS2) commands to a local server. "Submit Network Server Command (SBMNWSCMD)" shows the use of OS/2 commands to assist in debugging problems when the NetWare server is not active on the Integrated PC Server. 

CMDTYPE(*OS2) commands flow over the NETBIOS communications path. 

See "Submit Network Server Command (SBMNWSCMD)" for more information about SBMNWSCMD. 


NetWare Monitor Job

When a *NETWARE NWSD is varied on, a batch job is submitted to run in the QSYSWRK subsystem that 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. 

Note:
If the QSYSWRK subsystem is not started at the time you vary on the NWSD, the monitor job is not submitted. The monitor job for any varied on NWSDs starts when the subsystem starts. 

Monitor Job Functions

The monitor job can provide either basic functions or enhanced functions. Basic functions are provided when: 

  • Enhanced Integration for NetWare is not installed 
  • Enhanced Integration for NetWare is installed and a *NETWARE NWSD is varied on for the first time. 

  • Note:
    The first time a *NETWARE NWSD is varied on and Enhanced Integration for NetWare is installed, the Enhanced Integration for NetWare NLM is not loaded. Therefore, the monitor job makes no attempt to contact the NLM. 

  • Integration for NetWare is installed and a *NETWARE NWSD is varied on (after the first vary on) and the Enhanced Integration for NetWare NLM is not installed or not loaded. 

The basic functions provided by the NetWare monitor job include: 

  • Sending the date and time to the OS/2 administration application. 
  • Sending the initialize NetWare request to the OS/2 administration application. 
  • Receiving the "server started" notification. When this notification is received, the monitor job sets the NWS status to "Active". 

  • To determine if the server has reached this state, enter the following command: 

    WRKNWSSTS SVRTYPE(*NETWARE)
    
    
    
    A corresponding message is also logged in the monitor job's job log. 
  • Receiving NetWare console log activity. NetWare console log activity is directed to the *JOBLOG or message queue specified by the MSGQ value on the NWSD. 

  • Use the DSPNWSD command to determine where NetWare console log activity is to be placed on the AS/400 system. 

The monitor job attempts to provide enhanced functions during subsequent vary on requests for a *NETWARE NWSD with Enhanced Integration for NetWare installed. To provide enhanced functions, the monitor job establishes communication with the Enhanced Integration for NetWare NLM.   Enhanced functions are provided in addition to the basic functions. 

The enhanced functions provided by the NetWare monitor job include: 

  • Contacting the Enhanced Integration for NetWare NLM. When this occurs a message is sent to QSYSOPR indicating that enhanced functions are available for the server. 
  • Issuing the requests necessary to automatically format (partition) the drives if any new storage spaces have been linked to the NWSD. 

  • Messages are sent to QSYSOPR indicating when the partition operation has started and when it has completed. You cannot create a volume on a storage space until the partition operation has completed. NetWare does not recognize the storage space as a valid device until the monitor job has completed formatting the storage space. 

  • Notification of excessive CPU usage by an NLM on the server   

  • To receive notification of excessive CPU usage by a particular NLM, you must: 

    1. At the console, enter LOAD SERVMAN 
    2. Choose Server parameters 
    3. Choose Miscellaneous 
    4. Change Display Relinquish Control Alerts to On 
    If you want to keep this value, select the option to update the NCF files when you leave the SERVMAN utility. 
  • Logging messages in the files to SYS$LOG.ERR, TTS$LOG.ERR, VOL$LOG.ERR and DSREPAIR.LOG. 

  • Note:
    The messages logged to VOL$LOG.ERR are for the SYS: volume only. 

  • Logging NLM-detected errors.   

  • In all cases, messages are logged to the *JOBLOG or the message queue based on the value specified for the NWSD. If the value specified is *NONE, then no messages are logged on the AS/400 system. 

  • Obtaining disk statistics for each attached storage space every 30 minutes. 
  • Placing the network server in Restricted state if the monitor job or QSYSWRK subsystem is ended while the NWSD remains varied on. While in Restricted state, user storage spaces may be saved or restored. 

To determine if the monitor job will proceed with enhanced functions, look for message CPIA42B: 

Contact successful with

Enhanced Integration for NetWare NLM on server &1.


in the QSYSOPR message queue or the job log of the monitor job. 

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. 

Tip:
If you want to check the monitor job log, display the spooled files associated with the QSYS user profile, or use the job ID of the monitor job to locate the job log, see "Checking the Monitor Job Log"

Restarting the Monitor Job

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 message queue at any time, and the changes take effect immediately. 

Tips 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: 

  • Install NetWare Server (INSNTWSVR) 
  • Create Network Server Description (CRTNWSD) 
  • Change Network Server Description (CHGNWSD) 
  For more information on checking the NetWare server monitor job log, see "Checking the Monitor Job Log"

To collect NetWare server messages so that you can easily display them later, you can do one of the following: 

  • Create a message queue in library QGPL for each server. 

  • Use the NWSD name for the message queue name. For example, to display the messages for server1: 

    DSPMSG server1
    
    
    
  • Create one message queue in library QGPL for use by multiple NetWare NWSDs. 

  • Each message logged to the message queue is prefixed by the NWSD name to help identify the server for which the message was logged. 

If you use a message queue for NetWare server messages, the information is kept even after the monitor job has ended or the NWSD is varied off. However, the message queue can become full. When the message queue is full, AS/400 logs the messages in the monitor job log until you clear the message queue. When the monitor job log becomes full, it wraps. Plan to clear your message queues periodically to keep AS/400 from logging messages in the monitor job log. 

Coexistence with IBM LAN Server for OS/400

AS/400 supports NetWare, FAT, and HPFS storage space formats. IBM LAN Server for OS/400 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 IBM LAN Server for OS/400 and storage spaces formatted for IBM LAN Server for OS/400 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. IBM LAN Server for OS/400 does not support read-only drives because it uses *LANSERVER drives. 

Client Coexistence

If you are using both Integration for NetWare and IBM LAN Server for OS/400, refer to the LAN Server for OS/400 Administration book, SC41-3423 for information about how to configure the Windows 3.1 clients for IBM LAN Server for OS/400 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