![]() |
Chapter 22. Analyzing Problems -- Integration for NetWare
![]()
Check our web site at http://www.as400.ibm.com/netware, Service and Support link for analyzing common problems. Before you try to analyze a particular problem, we suggest that you refer to "Problem Analysis Tools". Problem Analysis Tools A number of different tools provide problem information. Depending on the problem that occurred, you may use one of the tools described in this topic. The tools are described in the following topics:
The Submit Network Server (SBMNWSCMD) command is the tool that you will use most during problem analysis. You can use this command to submit an OS/2 command to the OS/2 side of the server such as: SBMNWSCMD CMD('DIR E:\') SERVER(xxxx) SVRTYPE(*NETWARE) CMDTYPE(*OS2)You can use this command to submit a server console command to the NetWare server such as: SBMNWSCMD CMD('CONFIG') SERVER(xxxxx) SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)Press PF10 to see the command output. If this command doesn't work, use CMDTYPE(*LCLNTW) instead. However, you can only use this parameter when you submit requests to NetWare servers on local Integrated PC Servers. The reason why this parameter works when *NETWARE does not is that a different communications path is used to send the request to the server. For each active network server description, there is a monitor job in the QSYSWRK subsystem of the AS/400. This job log may contain messages that are useful during problem analysis. By default, this job log holds the NetWare server console messages that are captured from the server's console screen 0. If the job log is filled with messages, it overlays the oldest messages logged. In addition, it contains messages related to the startup of the job and whether or not the server was contacted. You can also specify a message queue and library to contain the NetWare console messages that are logged. Access to NetWare console messages is essential for problem analysis, especially when you may have a problem accessing the server with remote console. See "NetWare Monitor Job" for more information about monitor job functions and creating and managing message queues.
![]()
If an Integrated PC Server does not appear to be functioning normally (not active or inconsistent behavior), you can check the monitor job log for any errors generated on the Integrated PC ServerThese errors may help you determine a course of action to correct them.
![]() WRKSPLF QSYS The Work with All Spooled Files display appears. This contains all spooled files associated with the QSYS user profile. If the monitor job log was retained on AS/400, it appears here. Look for the NWSD name specified under the User Data column of the Work with All Spooled Files display.
![]()
DSPMSG QSYSOPR The Display Messages display appears. Message CPIA41B is issued at the start of the monitor job and is sent to the QSYSOPR message queue and also to the monitor job's job log. This message contains the name of the NWSD that was varied on and also the fully-qualified job name of the associated monitor job.
WRKJOB number/QSYS/job where number and job are obtained CPIA41B message text. If the job is not found, the spooled file containing the monitor job log has not been retained. Continue with "What to Do If There Is No Monitor Job Log". If the job is found, continue with step 4 Whether the monitor job produces a job log depends on the value specified for the LOG keyword in the job description used to submit this job. If there is no job log, follow these steps to change the job description for the job that controls this monitor job:
DSPJOBD QGPL/QBATCH
Also, make sure the message logging level parameter is set to 4 and the message logging severity parameter is set to 00. A log file is created on AS/400 during installation. In addition to logging errors, this file records file transfers during the NetWare source copy operation. If you get an error during the NetWare source copy operation, the QFPILOG file contains more detailed messages and return codes. Figure 22-1 shows an example of the contents of this log file. To access this file, enter the WRKSPLF command in the job you were running the INSNTWSVR command from. Figure 22-1. History Log: QFPILOG +--------------------------------------------------------------------------------+ | DISPLAY SPOOLED FILE | | FILE . . . . . : QFPILOG PAGE/LINE 1/6 | | CONTROL . . . . . COLUMNS 1 - 78 | | FIND . . . . . . | | *...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+... | | COPY /qopt/nw410/NW410/INSTALL/NIHONGO/NETMAIN.ILS | | COPY /qopt/nw410/NW410/BOOT/NLS/9/CLIB.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/DOMAIN.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/ICMD.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/INSTALL.HLP | | COPY /qopt/nw410/NW410/BOOT/NLS/9/INSTALL.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/KEYB.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/NFS.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/NWSNUT.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/NWTIL.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/NWTILR.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/REMOTE.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/RS232.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/RSPX.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/SERVER.MSG | | COPY /qopt/nw410/NW410/BOOT/NLS/9/SHIM410.MSG | | MORE... | | F3=EXIT F12=CANCEL F19=LEFT F20=RIGHT F24=MORE KEYS | | | +--------------------------------------------------------------------------------+QFPNWRC and QFPNWAD Log Files Two logs are created when the NetWare RCONSOLE and NWADMIN utilities are installed:
Network Server Description Dump You can use the network server description dump tool to dump the different configuration files that are used with both OS/2 and your NetWare server. To call the program enter the following command from a user ID with *ALLOBJ special authority: CALL QFPDMPLS PARM(nwsdname)The program creates a database file QGPL/QFPNWSDMP with multiple members. Each database file member has the network server description name followed by two digits (01-99). Display the member to see the contents of the different configuration files associated with your server description. Different files are important for problem analysis, depending on which installation step is causing a problem. The following list is a reference between the member name and the file name and location. If a file is marked a 1, then refer to this first during problem analysis, 2 second, and 3 last. If a file is not marked at all, then the file is not relevant to installation, but may be relevant at other times. Some members are not created until the post-installation processing phase. *NETWARE NWSD ============= Post- Member File Name Location Install install Member 01: CONFIG.SYS - drive C, root dir 3 3 Member 02: STARTUP.NCF - drive E, root dir 2 2 Member 03: PROTOCOL.INI - drive E, IBMCOM subdir 3 3 Member 04: NODISP.LOG - drive E, OS2\SYSTEM subdir 1 1 Member 05: LANTRAN.LOG - drive E, IBMCOM subdir Member 06: QFPAADM.TRC - drive E, root dir Member 07: POPUPLOG.OS2 - drive E, root dir 3 3 Member 08: SERVICE.INI - drive E, root dir Member 09: STARTUP.CMD - drive E, root dir 1 1 Member 10: QFPADOWN.SYS - drive E, root dir 3 Member 11: NETINFO.CFG - drive E, root dir 3 3 Member 12: NET.CFG - drive C, root dir Member 13: AUTOEXEC.NCF - drive E, root dir 2 Member 14: AUTOEXEC.SYS - drive E, root dir 1 Member 15: DISTRTUP.NCF - drive E, root dir 2 Member 16: CONSOLE.LOG - drive E, root dir 2 Member 17: VOL$LOG.ERR - drive E, root dir 3 Member 18: TTS$LOG.ERR - drive E, root dir 3 Member 19: SYS$LOG.ERR - drive E, root dir 3 Member 20: QFPILOG - drive E, root dir 3 Member 21: E - drive E, root dir 1Important Problem Analysis Files This section reviews some of the important files that are used for problem analysis, that are captured with the network server description dump. E:\OS2\SYSTEM\NODISP.LOGThis file records messages from OS/2 and NetWare that are normally presented on the OS/2 workstation. In normal operation of the server, the file ends with the statements shown in Figure 22-2. This shows the contents of the file after a startup, any additional messages indicate an error on the server. If the NetWare server or OS/2 abnormally ends (ABEND), an entry is made to this file.Figure 22-2. E:\OS2\SYSYTEM\NODISP.LOG +--------------------------------------------------------------------------------+ | The Logging Facility device driver LOG$ is loaded. | | Buffer Size: 8 KB | | IBM OS/2 LANMSGDD 04/13/94 2.01 is loaded and operational. | | IBM OS/2 LAN Protocol Manager | | IBM OS/2 NETBEUI 2.20.1 | | NETBEUI: Using a 32-bit data segment. | | IBM OS/2 NETBIOS 4.0 | | ...... | | E:\NWOS2.EXE -ONF -OT 11 -sE:\STARTUP.NCF | | NetWare for OS/2 is loading . . . | | Message file not found. | +--------------------------------------------------------------------------------+E:\E This file is the error log that is used during the automated installation of the server during the first part of the installation. Figure 22-3 shows the contents of this file after a successful installation. Any other messages in this file indicate an installation error. Figure 22-3. E:\E file for AS/400 Installation +--------------------------------------------------------------------------------+ |The system volume (SYS:) either is not mounted or does not exist. (INSTALL 4.1) | | | +--------------------------------------------------------------------------------+ The STARTUP.CMD file starts OS/2 and NetWare in different ways according to how far the AS/400 installation process has completed. The problem analysis actions are different for AS/400 installation and post-installation processing. To view the contents of your STARTUP.CMD, enter the following AS/400 command: SBMNWSCMD CMD('TYPE E:\STARTUP.CMD') SERVER(xxxx) SVRTYPE(*NETWARE) CMDTYPE(*OS2)Figure 22-4 shows the STARTUP.CMD file for AS/400 during the installation phase. NetWare for OS/2 is started with a special startup file to initiate an automated installation of the server according to a predefined script. Figure 22-4. STARTUP.CMD for AS/400 +--------------------------------------------------------------------------------+ | E:\STARTUP.CMD | |COPY E:\STARTUP.NCF + F:\QFPNTWI\QFPINST1.TXT E:\DISTRTUP.NCF | |copy f:\nwos2\netmain.* e:\ | |copy f:\nwos2\langfs.ils e:\ | |copy f:\nwos2\install.nlm e:\ | |copy f:\nwos2\install.msg e:\ | |COPY F:\NWOS2\CLIB.* E:\ | |COPY F:\NWOS2\STREAMS.* E:\ | |COPY F:\NWOS2\SERVER.* E:\ | |COPY F:\QFPNTWI\NW410\NWOS2.* e:\ | |IF EXIST F:\QFPNTWI\LCONFIG.SYS COPY F:\QFPNTWI\LCONFIG.SYS E:\ | |E: | |CD \ | |NWOS2.EXE -ONF -OT 11 -sE:\DISTRTUP.NCF | +--------------------------------------------------------------------------------+Figure 22-5 shows the STARTUP.CMD file for AS/400 when the post-installation phase starts for NetWare for OS/2. This STARTUP process uses a standard startup file for the normal operation of your NetWare server. Note that the -ONF parameter for NetWare for OS/2 is used to start the server with the "Option for No Floppy"; that is, no diskette drive. Figure 22-5. STARTUP.CMD for AS/400 for Server Operation +--------------------------------------------------------------------------------+ | E:\STARTUP.CMD | | | |COPY F:\QFPNTWI\NW410\NWOS2.* e:\ | |E: | |CD \ | |NWOS2.EXE -ONF -OT 11 -sE:\STARTUP.NCF | +--------------------------------------------------------------------------------+E:\STARTUP.NCF This file is the startup file for the server that is held on the E: drive. This file contains NetWare system patches for the server and the AS/400 disk driver statement. You can edit this file from the remote console to add your own NetWare patches. Figure 22-6 shows part of the initial NetWare 4.1 STARTUP.NCF file. +--------------------------------------------------------------------------------+ | PATCH MANAGER AND PATCHES TO BE LOADED IN STARTUP.NCF | | ; 410PT1.EXE (NWOS2) | | LOAD F:\QFPNTWI\nw410\PM410 | | LOAD F:\QFPNTWI\nw410\AUDDIRFX | | LOAD F:\QFPNTWI\nw410\AUDNSPFX | | ....... | | LOAD F:\QFPNTWI\QFPLDISK.DSK | | SET AUTO TTS BACKOUT FLAG=ON | | Set Minimum Packet Receive Buffers = 400 | | Set Maximum Packet Receive Buffers = 2000 | | Set Maximum Physical Receive Packet Size=04202 | +--------------------------------------------------------------------------------+E:\AUTOEXEC.SYS This is a copy of your latest AUTOEXEC.NCF file, that is taken from the system volume during vary off processing. You can use this file to refer to any changes that you made to the AUTOEXEC while the server is down. This is the AUTOEXEC file that is used to start the server for the first time during the AS/400 installation process. After that time, the copy on the system volume is used. This is a copy of the NETINFO.CFG file that is taken from the system volume during vary off processing. This copy is changed during vary on processing according to the configuration changes you have made to line and IPX circuit configuration. The file is then copied back to the system volume during vary on processing, where it is used to initialize the system network configuration. You can also dump the memory of the OS/2 and the NetWare operating systems. This might be necessary if an SRC of 6506 6224 is reported by an Integrated PC Server. This error indicates that OS/2 running in the Integrated PC Server has detected a fatal fault. You would only create a dump if requested by IBM or Novell service. To link a dump disk to the server, you must vary off the network server description, then issue one of the following commands from a user ID with *ALLOBJ special authority. The syntax of the call is either: For an OS/2 dump: CALL QSYS/QFPDMPSS PARM(nwsdname *LINK 'size') For a NetWare dump: CALL QSYS/QFPDMPSS PARM(nwsdname *LINKNW 'size')where 'size' must be at least as large as the actual memory installed on the Integrated PC Server and can be one of the following values:
|
The program creates a server storage space object in library QUSRSYS
with a name based on the NWSD name (nwsdnameDP for OS/2 and nwsdnameNW
for NetWare). The program initializes the SVRSTG object and then links
it to the network server description as drive J: (OS/2) or drive I: (NetWare).
After you have linked the storage space, vary on the server and try to reproduce your problem. When a dump occurs it is then written to the storage space. You can verify that a NetWare dump file has been written to the storage space by entering: SBMNWSCMD CMD('DIR I:\') SERVER(xxx) SVRTYP(*NETWARE) CMDTYPE (*OS2)
![]()
To save the NetWare dump, use the Save Object (SAVOBJ) command and contact Novell service for additional assistance. The following is an example of using the SAVOBJ command: SAVOBJ OBJ(xxxNW) LIB(QUSRSYS) DEV(TAPyy) For an OS/2 dump: CALL QSYS/QFPDMPSS PARM(nwsdname *UNLINK) For an NetWare dump: CALL QSYS/QFPDMPSS PARM(nwsdname *UNLINKNW)When the second parameter is *UNLINK or *UNLINKNW, the program unlinks the server storage space object and deletes the SVRSTG object. Integrated PC Server Error Log and VLIC Log Entries When you encounter problems with your NetWare server or the Integrated PC Server, it may be useful to look into the Error log and VLIC log, especially if you do not get any other information in the job logs. You must have *SECOFR authority to use the System Service Tools. +--------------------------------------------------------------------------------+ | System Service Tools (SST) | | | | Select one of the following: | | | | 1. Start a service tool | | 2. Work with active service tools | | 3. Work with disk units | | 4. Work with diskette data recovery | | | | | | Selection | | 1 | | | +--------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------+ | Start a Service Tool | | | | Warning: Incorrect use of this service tool can cause damage | | to data in this system. Contact your service representative | | for assistance. | | | | Select one of the following: | | | | 1. Product activity log | | 2. Trace Licensed Internal Code | | 3. Work with communications trace | | 4. Display/Alter/Dump | | 5. Licensed Internal Code log | | 6. Main storage dump manager | | 7. Hardware service manager | | | | | | | | | | Selection | | 1 | | | | F3=Exit F12=Cancel F16=SST menu | | | +--------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------+ | Error Log Utility | | | | Select one of the following: | | | | 1. Display or print error log | | 2. Display or print by error log ID | | 3. Change error log sizes | | 4. Work with tape/diskette lifetime statistics | | 5. Display or print tape/diskette session statistics | | 6. Analyze error log | | 7. Reference code description | | | | | | | | | | | | | | | | | | Selection | | 1 | | | | F3=Exit F12=Cancel | +--------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------+ | Select Subsystem Data | | | | Type choices, press Enter. | | | | Error log . . . . . . 5 1=All error logs | | 2=Processor | | 3=Magnetic media | | 4=Local work station | | 5=Communications | | 6=Power | | 7=Licensed program | | 8=Licensed Internal Code | | | | | | From: | | Date . . . . . . . . 10/04/95 MM/DD/YY | | Time . . . . . . . . 18:52:42 HH:MM:SS | | | | To: | | Date . . . . . . . . 10/05/95 MM/DD/YY | | Time . . . . . . . . 18:52:42 HH:MM:SS | | | | F3=Exit F5=Refresh F12=Cancel | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Select Report Type for Subsystem | | | | Type choices, press Enter. | | | | Report type . . . . . . . 1 1=Display summary of error log | | 2=Print summary of error log | | 3=Print partial report | | 4=Print full report | | | | | | For choices 1 and 4: | | Include hexadecimal | | data . . . . . . . . y Y=Yes | | N=No | | | | Include information | | entries . . . . . . . . Y Y=Yes | | N=No | | | | | | | | F3=Exit F5=Refresh F12=Cancel | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Display Summary of Communications Entries | | | | From . . : 10/04/95 18:56:41 To . . : 10/05/95 18:56:41 | | | | Type options, press Enter. | | 5=Display report 6=Print report | | | | | | Option Resource Type Address Count | | NWHERMAN NETWORK 0460-FFFFFFFF 1 | | JDMCC07 NETWORK 0440-E000FFFF 1 | | TRNLINE LINE 0050-E000FFFF 1 | | 5 HARDWARE 2 | | | | | | | | | | | | | | | | | | | | F3=Exit F5=Refresh F12=Cancel | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Display Summary of Hardware Entries | | | | From . . : 09/01/95 10:20:12 To . . : 10/06/95 10:20:12 | | | | Resource Type Address Total Count | | HARDWARE 2 | | | | Type options, press Enter. | | 5=Display report 6=Print report | | | | Serial | | Opt Resource Type Model Number Address Count | | CHANNEL **** 00-00000 0000-00000000 1 | | 5 IOP 6506 001 10-4228011 0330-FFFFFFFF 1 | | | | | | | | | | | | More... | | F3=Exit F12=Cancel | | | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Display Partial Report for Resource | | | | From . . : 09/01/95 10:20:12 To . . : 10/06/95 10:20:12 | | | | Serial | | Resource Type Model Number Address Total Count | | IOP 6506 001 10-4237010 0260-FFFFFFFF 1 | | | | Type options, press Enter. | | 5=Display report 6=Print report | | | | Option Reference Code Error Type Count | | 5 1202 Permanent 1 | | | | | | | | | | | | | | | | F3=Exit F12=Cancel | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Display Detail Report for Resource | | | | Serial | | Resource Type Model Number Address | | IOP 6506 001 10-4237010 0260-FFF | | | | Error log ID . . . . . . : 0043D7A1 Sequence . . . . . . : 10296 | | Date . . . . . . . . . . : 10/02/95 Time . . . . . . . . : 10:50:22 | | Reference code . . . . . : 1202 Error code . . . . . : 00000000 | | Table ID . . . . . . . . : B006F060 IPL source . . . . . : B | | Error type . . . . . . . : Permanent | | Description . . . . . . . : | | Not valid condition in I/O Processor Licensed Internal Code | | | | | | | | | | | | | | Press Enter to continue. | | | | F3=Exit F6=Display hexadecimal report | | F10=Display previous detail report F12=Cancel | +--------------------------------------------------------------------------------+
Look for any Error Log Entry of B600 6506 xxxxwhere xxxx is equal to: +--------------------------------------------------------------------------------+ | Display Summary of Communications Entries | | | | From . . : 10/04/95 18:56:41 To . . : 10/05/95 18:56:41 | | | | Type options, press Enter. | | 5=Display report 6=Print report | | | | | | Option Resource Type Address Count | | 5 NWHERMAN NETWORK 0460-FFFFFFFF 1 | | JDMCC07 NETWORK 0440-E000FFFF | | TRNLINE LINE 0050-E000FFFF | | HARDWARE | | | | | | | | | | | | | | | | | | | | | | | | | | F3=Exit F5=Refresh F12=Cancel | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Display Summary of Network Interface Entries | | | | From . . : 10/01/95 10:20:12 To . . : 10/06/95 10:20:12 | | | | Resource Type Address Total Count | | NWHERMAN NETWORK 0460-FFFFFFFF 1 | | | | Type options, press Enter. | | 5=Display report 6=Print report | | | | Opt Resource Type Address Count | | 5 NWHERMAN NETWORK 0460-FFFFFFFF 1 | | | | | | | | | | | | | | | | | | | | | | | | F3=Exit F12=Cancel | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Display Partial Report for Resource | | | | From . . : 10/01/95 10:20:12 To . . : 10/06/95 10:20:12 | | | | | | Resource Type Address Total Count | | NWHERMAN NETWORK 0460-FFFFFFFF 1 | | | | Type options, press Enter. | | 5=Display report 6=Print report | | | | Option Reference Code Error Type Count | | 5 0000 Temporary 1 | | | | | | | | | | | | F3=Exit F12=Cancel | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Display Detail Report for Resource | | | | Resource Type Address | | NWHERMAN NETWORK 0460-FFFFFFFF | | | | Error log ID . . . . . . : 80000D00 Sequence . . . . . . : 10280 | | Date . . . . . . . . . . : 10/02/95 Time . . . . . . . . : 10:42:22 | | Reference code . . . . . : 0000 Error code . . . . . : BADDF00D | | Table ID . . . . . . . . : IPL source . . . . . : B | | Error type . . . . . . . : Temporary | | Description . . . . . . . : | | VMC Internal Product Data | | | | Protocol . . . . . . . . : | | | | | | | | | | | | Press Enter to continue. | | | | F3=Exit F6=Display hexadecimal report | | F10=Display previous detail report F12=Cancel | +--------------------------------------------------------------------------------+
OS/400 Feature Installation This section provides information on problems that might occur during the installation of the OS/400 features required to support NetWare on the file server I/O processor. Integration Services for FSIOP, 5769-SA2 Before installing Integration Services for FSIOP, 5769-SA2, verify that the system directory contains the user profile to be used. To verify, use the Work with Directory Entries (WRKDIRE) command. If you encounter a problem, look at the following:
OS/400 Integration for Novell NetWare, 5769-SA3 See Chapter 2. "Installing OS/400 Integration Products for NetWare" for information on how to install Integration for NetWare. If you encounter a problem, look at the following:
INSNTWSVR The INSNTWSVR command creates an NWSD the AS/400 system. This NWSD (network server) is automatically started and should change to Active status. Before you try to analyze a particular problem, you may want to look at the list of problem analysis tools that are available. Those tools are listed in "Problem Analysis Tools". The following problems are independent items, and should be considered individually. Message CPDA488 NetWare Source Not Copied If you receive message CPDA488 with reason code 1 or 2, the install process cannot find the file documented in the QFPILOG history file. The first part of the path is specified by the NTWSRCDIR parameter. The rest of the path is from the install program. Enter WRKSPLF and then option 5 to display the QFPILOG file. Most likely, the path to the CDROM image is not correct. Use the WRKLNK command to check the path name to the CDROM image. For example, if you have the NetWare CD-ROM in the AS/400 CD-ROM device, enter WRKLNK OBJ('/QOPT') and then use option 5 to display the volume name. In this example, the volume name is NW410_C, so you should specify /QOPT/NW410_C on the NTWSRCDIR parameter. For other reason codes for message CPDA488, read the second level help text of the message to determine what the problem is and how to recover. Message CPI947F Network Server Failed If you receive message CPI947F indicating that the IOP has failed or the lines have failed check that you have enough memory in your machine pool. Increase the machine pool size in increments of 2MB and try to vary on the network server after each increase. To increase the machine pool size, enter the following command WRKSYSVAL QMCHPOOL then select option 2 to change the machine pool size. Message CPIA426 IPX Not Started If you receive message CPIA426, this indicates the command default for the LCLIPXCNN parameter on the Create Network Description (CRTNWSD) command is *YES. When the INSNTWSVR command called the VRYCFG command to vary on the network server description, local AS/400 IPX support was not active. If you do not need local AS/400 IPX support, use the Change Network Description (CHGNWSD) command to change LCLIPXCNN to *NO. For subsequent installs of NetWare servers, change the command default of CRTNWSD of the LCLIPXCNN parameter to *NO. If you need local AS/400 IPX support, use the Start IPX (STRIPX) command. Once the server is active you connect to the server with remote console to add the NetWare license and configure NetWare Directory Services. Message CPI947F IOP Has Failed If you receive message CPI947F indicating that the IOP has failed or the lines have failed, increase the machine pool size in increments of 2000K. Attempt to vary on the network server after each increase. To increase the machine pool size, enter the following command WRKSYSVAL QMCHPOOL then select option 2 to change the machine pool size. Message CPI7E60 Network Server Failed If you receive message CPI7E60 indicating that the IOP has failed, you must look at the job log, VLIC log, and the error log for more specific information. Network Server Status Remains at FAILED You received an information message at the bottom of your screen that the server did not start. Look into your job log and search for messages such as CPD8E45, CPD8F79 and CPD8FFF. Follow the instructions of the second level text, corresponding to the reason code of your message. Network Server is ACTIVE, Line is Recovery Pending This is usually a hardware problem. Ensure that all connections are tight. Verify the port value for your line description for this network server description. (The lower port is port number one and the upper port is number two.) There may also be a bad cable, try swapping cables. Check the cable by attaching it to another port on the MAU or patch panel. Look for any messages in the QSYSOPR message queue. This could also indicate that there is not enough memory in the machine pool to vary on your line description. Try adding memory to the machine pool. Transferring Files Fails with RCONSOLE If you are in the process of copying utilities to your server from the NetWare CD-ROM and you encounter problems, ensure that you are running RCONSOLE outside Windows 3.1. RCONSOLE is known to have stability problems in a Windows 3.1 DOS Box and these problems can be seen during this file copy process. Cannot Add License with RCONSOLE If you are connected to the server with remote console, but do not see the F4 option to install a license from a remote workstation, you need to update your remote console to the latest version. This might occur if you were running NetWare 3.12 and had remote console installed on your PC, and did not use the new install diskette to install NetWare 4.1 remote console. If you do have the F4 option to install a license from a remote workstation, remember to use this for the NetWare file server I/O processor. You cannot install a license from the server's A: drive. Cannot Find Password for RCONSOLE If you are attached to the server with remote console, but cannot log in successfully, remember that the password is set to be the same as your network server description name. Remember to change this using the INETCFG utility. Cannot Attach to Server with RCONSOLE If you are installing your first NetWare server on a LAN, there is no other NetWare server to list available RCONSOLE servers. In this case, from the empty RCONSOLE active server list, press the insert key and enter its internal IPX number. You can find the IPX number in your NetWare server IPX description on the AS/400, the IPXD has the same name as your NWSD. If the network server description is active, but you cannot connect with remote console, check which LAN port you are using. If you have a two-port file server I/O processor, only the first port is activated in AS/400 post-installation processing. This is because the base server in AS/400 does not have enough licenses to bind the two ports. Ensure that you connect your PC to the LAN segment on port 1 and retry the RCONSOLE connection. A similar connection problem can occur if you have configured multiple frame types for your server. Again only the first frame type, 802.2 by default, is bound until you add your license with remote console. If you can use RCONSOLE and have installed your license, but cannot login from a client PC, check that you have installed NDS. Token-Ring IPX Routing Problems If you have an NWSD with two token-ring ports and each port is connected to a different token-ring segment, the NetWare server connects the segments using its routing support. This means that both token-ring ports must have the same IPX network number. The ROUTE.NLM is always loaded by the NetWare server. To disable routing, rename the ROUTE.NLM on the NetWare server. If you receive the message CPD8FAC, you have configured your network server description with two lines. But you have only one port on your file server I/O processor. Change your configuration so that only one line is defined.
![]() Post-Installation Processing When you vary off the server for the first time and then vary on again, the OS/2 STARTUP.CMD is changed for normal server operation starting NetWare for OS/2. The following topics address problems that apply during this post-installation processing. Users Cannot Attach after Vary On: IPX Bind Failure If you have been running the server successfully, then your users can no longer attach after a vary on, you should check the status of your server communications configuration by running the following command: SBMNWSCMD CMD('CONFIG') SERVER(xxxx) SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)
![]() You can look for this problem in the job log or message queue on the AS/400 where you direct the server console messages. Look for the following error: +--------------------------------------------------------------------------------+ | SYSINIT: Binding IPX to QFP_TOK_1_TOK. | | SYSINIT: Binding IPX to QFP_ETH_2_E82. | | SYSINIT: Binding IPX to QFP_ETH_2_E83. | | SYSINIT: Binding IPX to OS400_IPX_TOK. | | Bind failed because network address 68773793 | | is already used as an internal network address. | | Network number: | |SYSINIT: Bind failed: bad parameters. | +--------------------------------------------------------------------------------+To resolve this error, first vary off the network server description. Then use the command ENDIPX to end the OS/400 IPX support, before varying on the network server description. Finally, only use STRIPX if you are planning to use the OS/400 IPX support, say for IPX routing. It is not required for normal operation of the NetWare server on the file server I/O processor. If you do use the OS/400 IPX support, ensure that you use a separate IPX description. If the server abnormally ends during normal operation, users will no longer be able to connect to the server. If the server has abnormally ended you will not receive a response to a command submitted with SBMNWSCMD from AS/400. When an abnormal end occurs, an entry is written to the NODISP.LOG file. See Figure 22-2 for information on how to check this file, and "Memory Dump" for information on taking a dump if requested by IBM or Novell service. Monitor NLM Shows High CPU Utilization Note that the MONITOR NLM does NOT show the correct values for the CPU utilization of NetWare running on OS/2. You can use option 5 (Display details) on the Work with Network Server Status Display to see the correct CPU utilization. OS/2 and NetWare Active, But Cannot Login If you can connect to the server with RCONSOLE, but users cannot login, you should check that the system volume is mounted with the following command: SBMNWSCMD CMD('VOLUMES') SERVER(xxxxx) SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)
![]() SBMNWSCMD CMD('MODULES') SERVER(xxxxx) SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)If the disk driver, QFPLDISK.DSK, is not loaded, you probably have a corrupted STARTUP.NCF. This can be caused either by file corruption on the E: drive, usually a result of a problem with vary off processing. Or, it could be that you have added a NetWare patch or other statement in the STARTUP.NCF file that has caused the error. To view the file, use the following command: SBMNWSCMD CMD('TYPE E:\STARTUP.NCF') SERVER(NWRPL) SVRTYPE(*NETWARE) CMDTYPE(*OS2)Compare the file with the one shown in Chapter 5. "Configuration Objects and Files" and check for errors. To re-create the file either reset the network server description, which erases all your configuration changes, or just copy this file from the F: drive with the following command: SBMNWSCMD CMD('COPY F:\QFPNTWI\STARTUP.NCF E:STARTUP.NCF') SERVER(NWRPL) SVRTYPE(*NETWARE) CMDTYPE(*OS2)This restores the original STARTUP.NCF. Now vary off the network server description and then vary back on. If you followed the previous step and the disk driver was loaded, but your users could not connect to the server, you may have a damaged system volume. Use the VOLUMES command to check if the system volume is mounted. If it is not mounted, use the command MOUNT SYS to attempt to mount the volume. If this fails, run VREPAIR from your remote console session to repair the system volume. Server Does Not Start After Editing AUTOEXEC.NCF or STARTUP.NCF If you have made a change to the server's AUTOEXEC.NCF or STARTUP.NCF files and the server no longer starts, you may need to bring up the server with the original AUTOEXEC.NCF file and without the STARTUP.NCF file while you remove or correct your changes. Note that each time you vary off the server, a copy of your AUTOEXEC.NCF is copied from the system volume to the E: drive. The copy is renamed AUTOEXEC.SYS. A copy of your STARTUP.NCF is copied from the system volume to the E drive also. The copy is named STARTUP.NCF. You can reference these files to determine if you made a change that created the error condition. Use the following commands: SBMNWSCMD CMD('TYPE E:\AUTOEXEC.SYS') SERVER(xxxx) SVRTYPE(*NETWARE) CMDTYPE(*OS2)Use the following command to examine the STARTUP.NCF file: SBMNWSCMD CMD('TYPE E:\STARTUP.NCF') SERVER(xxxx) SVRTYPE(*NETWARE) CMDTYPE(*OS2)Use the following procedure to start the server without using the STARTUP.NCF file and using the original version of the AUTOEXEC.NCF file that is held on the server's E: drive:
CHGNWSD NWSD(XXXX) CFGFILE(QFPNTWI/QAFPNSCA)This configuration file modifies the OS/2 STARTUP.CMD file to start the server without a STARTUP.NCF file as follows: +--------------------------------------------------------------------------------+ | NWOS2.EXE -ONF -OT 11 -ns | +--------------------------------------------------------------------------------+
Load HIMOVE with the following command: SBMNWSCMD CMD('LOAD HIMOVE') SERVER(XXXX) SVRTYPE(*NETWARE)Load the AS/400 disk driver with the following command: SBMNWSCMD CMD('LOAD F:\QFPNTWI\QFPLDISK.DSK') SERVER(XXXX) SVRTYPE(*NETWARE)Mount the system volume with the following command: SBMNWSCMD CMD('MOUNT SYS') SERVER(XXXX) SVRTYPE(*NETWARE) SBMNWSCMD CMD('SYS:ETC\INITSYS') SERVER(XXXX) SVRTYPE(*NETWARE) ![]() ![]() CHGNWSD NWSD(XXXX) CFGFILE(*NONE) If you changed the NetWare server STARTUP.NCF file, for example to patch an NLM, and the server no longer starts, or becomes unpredictable, you can reset the file server I/O processor's configuration files. This operation resets both the STARTUP.NCF and the NETINFO.CFG to the original files used at installation. Note that in the case of the NETINFO.CFG file reset, this erases any changes that you have made to the file with INETCFG. This includes resetting the remote console back to the default of the network server description name. This command also resets all the associated OS/2 files, saving your configuration files with the extension .QRS. Resetting the files is performed with the following Vary Configuration (VRYCFG) command: VRYCFG CFGOBJ(xxxxxx) CFGTYPE(*NWS) STATUS(*ON) RESETCFGF(*YES) If you find message CPDA442 "Server storage space xxxx3 is partially damaged." in your job log, there was an error during the previous vary off processing. Normally this is only a warning message and OS/2 corrects your xxxx3 storage space which is the server's E: drive. VREPAIR & Name Spaces Not On Server Boot Drive (E:) The boot drive utilities, such as VREPAIR, and the name spaces are by default copied to the F:\NWOS2 drive during the install process. VREPAIR and the name space files are also copied to the E: drive when you vary on the NWSD if you install PTF 5716SA3 SF36056. Cannot Find Utilities (PCONSOLE) in Public Directory If you have started the server, but cannot find some of the DOS and Windows based utilities that you normally use from the Public directory of the system volume, you need to install these from your NetWare 4.1 CD-ROM. For more information see "Step 4--Install NetWare Client". Message CPI573F Network Server Failed If you receive message CPI573F indicating that the IOP has failed with RC=E1000005, you may have either a hardware or software error. To find out if you hvae a software error, do a CHKDSK of your E: drive. To do this, enter: SBMNWSCMD CMD('chkdsk e:') SERVER(server-name) SVRTYPE(*NETWARE) MDTYPE(*OS2)Then enter DSPJOBLOGand press F10 to display your job log. If errors were detected, follow the save/restore procedures as described in Chapter 11. "Saving and Restoring Network Data" Message CPD8F7D or CPD8F7E During Vary Off This message means that the server is busy, or a controller is active on one of the lines, or both. Vary off the controller, then vary off your network server description. Message CPD28CA During Vary Off This message indicates that a service task for your network server description has timed out. Try to vary off the NWSD asynchronously. Also check the QFPADOWN.NCF file on the server's system volume for any down processing commands that you added that might affect vary off processing. Message CPF2697 During Vary Off This message indicates there was not enough time left between the vary off of the NWSD and the vary on. All internal tasks were not closed. Controller or Device Created with the Line Description If you are using Client Access to connect to the AS/400 using the file server I/O processor and a controller or device description was not created, check the line description to determine if the Autocreate controller parameter is still set to the default of *NO. Change this value to *YES, or create a controller description manually. Cannot Start an APPC or TCP/IP Session to AS/400 If your APPC or TCP/IP session does not start, check your controller to determine if it is in a Vary on Pending status. Also verify that the Autocreate controller prompt value on the line description is *YES. *NO is the default. Message CPD8F97 Vary Off Line Fails You cannot vary off a line description that is attached to a network server description, without first varying off the NWSD. Network Server Status is DAMAGED Usually, you will not see a damaged network server description. If it occurs the only way to solve the problem is to recreate your NWSD. When you must delete the network server description, you should make a copy of the current NetWare NWSD configuration before deleting it. This can be done by using option 6 (Print) or option 9 (Retrieve Source) on the Work with Network Server Descriptions display. Use option 4 (Delete) to delete your NetWare server description. Re-create the deleted NetWare server description. If you used the retrieve option you can now use the same option to re-create the deleted server description. Otherwise, use option 1 (Create) to re-create your NWSD with the same values as before. Notice that you must specify the line description name for the port parameter. After creating the new NWSD, relink all the appropriate network server storage spaces. They were removed when you deleted the original network server description. When you use the NetWare SBACKUP utility or the ARCserve product from Cheyenne Software, Inc., you may encounter some error messages. If any of the following messages appear, use the following information to resolve the problem. Note that some errors will recommend that you reset the AS/400 tape device. If you are unsure how to do this, see the Local Device Configurationbook.
To recover, unload the ARCserve NLMs or SBACKUP, reload AS400TP.HAM, allocate a tape device, and then start the backup or restore process again.
This message appears if you try to deallocate the tape device during a backup or restore operation. If you unload AS400TP.HAM after this message appears, the session as well as the backup or restore operation will end and status or media errors will occur. To recover, unload the ARCserve NLMs or SBACKUP, reload AS400TP.HAM, allocate a tape device, and then start the backup or restore process again. If you install NetWare 4.1 on an OS/2 server or the Integrated PC Server, you must have the current version of several NLMs to operate properly with Enhanced Integration for NetWare. If connections to a NetWare 4.1 server running OS/2 fail with a NetWare return code of -333 (ERR_NO_CONNECTION), the following NLMs may need to be updated:
Starting *SAVRST connections to NetWare 4.1 on OS/2 servers may require
updated versions of the TSA NLMs (TSA410 and TSANDS.NLM).
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ] |