PATHWORKS_V1.0G_for_OpenVMS_(NetWare)_________ Server Release Notes These Release Notes supplement the product documentation. Always read the release notes before you complete the product installation. August 1997 Revision/Update Information: This document supersedes PATHWORKS V1.0F for OpenVMS (NetWare), Release Notes Operating System: OpenVMS Alpha, Version 7.1 Software Version: PATHWORKS V1.0G for OpenVMS (NetWare) Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ First Published, August 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1997. Printed in U.S.A. The following are trademarks of Digital Equipment Corporation: DEC, DECnet-Plus, DECprint, DIGITAL, OpenVMS, PATHWORKS, PATHWORKS 32, and the DIGITAL logo. The following are third-party trademarks: AT&T is a registered trademark of American Telephone and Telegraph Corporation. Apple, LaserWriter, AppleShare, Macintosh, and TRUETYPE are registered trademarks of Apple Computer, Inc. Hewlett-Packard, HP, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company. IBM, OS/2, and NetView are registered trademarks of International Business Machines, Inc. Microsoft, MS-DOS, Windows, and Windows 95 are registered trademarks, and Windows NT is a trademark of Microsoft Corporation. Novell and NetWare are registered trademarks of Novell, Inc. MultiNet is a registered trademark of TGV, Inc. PostScript is a registered trademarks of Adobe Systems, Inc. All other trademarks and registered trademarks are the property of their respective holders. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. vii 1 Distribution Media 2 PATHWORKS V1.0G for OpenVMS (NetWare) Features 2.1 Optional DECprint Supervisor for OpenVMS Software Available........................... 2-1 2.2 New NVT Client Software...................... 2-2 2.3 Frame Type Support........................... 2-2 2.4 Native NetWare Printing Support.............. 2-3 2.5 Enhancements to GETLAN and SCONSOLE Utilities.................................... 2-3 2.6 Support for ISO-9660 and High-Sierra CD-ROM Formats...................................... 2-3 2.7 Print Queue Format Changes................... 2-4 3 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.1 Using PATHWORKS V1.0G for OpenVMS (NetWare) with PATHWORKS for OpenVMS Version 4.x....... 3-1 3.2 Upgrading Third-Party NetWare Server Products..................................... 3-1 3.2.1 Moving Bindery Information............... 3-1 3.2.2 Defining Volumes and Moving Programs and Data Files............................... 3-4 3.3 Installation on Multiple Members of a VMScluster................................... 3-5 3.4 Determining Channel Count.................... 3-6 3.4.1 File server example...................... 3-6 iii 3.4.2 NVT daemon example....................... 3-6 3.5 Files the NetWare File Server Cannot Write... 3-6 3.6 PSERVER Name................................. 3-7 3.7 STOP/ID on the NPS Daemon Process............ 3-7 3.8 Startup Requirements for Utilities........... 3-7 3.9 Saving and Restoring the Bindery............. 3-8 3.9.1 Running BINDDOWN with Active Connections.............................. 3-8 3.10 Configuring Print Services................... 3-8 3.10.1 How to Set Up a Print Server to Serve a Remote NetWare File Server............... 3-9 3.10.2 Error Creating Print Queues.............. 3-10 3.10.3 Error Creating Print Servers............. 3-11 3.11 Printing to Native NetWare Printers.......... 3-12 3.11.1 Management of the NetWare Print Queue.... 3-13 3.11.1.1 Configuring the NetWare Printer Queue.................................. 3-13 3.11.2 Troubleshooting the NetWare Print Queue.................................... 3-14 3.11.3 Using the NetWare Printer................ 3-15 3.11.3.1 Displaying NetWare Print Jobs.......... 3-15 3.11.3.2 Deleting NetWare Print Jobs............ 3-17 3.11.4 Accounting Information for NetWare Print Jobs..................................... 3-18 3.12 Portable NetWare Programming Examples........ 3-18 3.13 Terminal Screen Display Mode................. 3-18 3.14 Intruder Detection Error Message............. 3-18 3.15 IPX socket number x236....................... 3-19 3.16 Redirecting the Location of the NetWare Dump File......................................... 3-19 3.17 Deleting Files from a NetWare Volume......... 3-19 3.18 Installing Paradox........................... 3-19 3.19 Error Log Not Found.......................... 3-20 3.20 Unmounted OpenVMS Disks...................... 3-20 3.21 SLIST Output in a VMScluster................. 3-20 3.22 Required Privileges for Startup and Shutdown..................................... 3-21 3.23 Versions of the SYSCON Utility............... 3-21 3.24 Correct Number of Global Pages for Running NetWare...................................... 3-21 iv 3.25 Upgrading License Server State Files......... 3-22 3.25.0.1 Upgrading License Server State Files on a Node Not Previously Configured to Run the License Server..................... 3-23 3.25.1 Upgrading License Server State Files on a an OpenVMS Cluster....................... 3-24 3.26 Using the BINDFIX Utility.................... 3-25 3.27 Documentation Clarification.................. 3-25 3.28 OpenVMS Operating System Delta Time Restriction.................................. 3-26 4 Known Problems and Restrictions 4.1 User Disk and Volume Space Restrictions Unsupported.................................. 4-1 4.2 Hybrid User UIC.............................. 4-1 4.3 Accessing Files in a Cluster................. 4-2 4.4 Errors Returned from NetWare APIs............ 4-2 4.5 License server user interface displays "noname"..................................... 4-2 4.6 Client can consume two licenses.............. 4-2 4.7 Backing out of help screen may reset list.... 4-3 4.8 License Manager may crash when deassigning a client license............................... 4-3 4.9 Disk Quota and Available Blocks.............. 4-3 4.10 Accessing the Bindery on a Clustered System....................................... 4-4 4.11 SUPERVISOR password during BINDDOWN/BINDUP procedure.................................... 4-4 4.12 OpenVMS BACKUP/RESTORE and TRUSTEE Rights.... 4-4 4.13 Deleting an Active Job in a NetWare Queue.... 4-5 4.14 Associating NetWare Volumes and OpenVMS Disks........................................ 4-5 4.15 Help Error................................... 4-5 4.16 Error with FILER............................. 4-5 4.17 Server Startup Failure....................... 4-5 4.18 Moving the NetWare System-Specific Directory.................................... 4-6 4.19 VLM Client Pathname Restrictions............. 4-7 4.20 OpenVMS Logout During Reflections 4 for MS Windows Login................................ 4-7 4.21 Running More Than One Version of the License Server....................................... 4-7 v 4.22 License Manager Server Name Display.......... 4-7 4.23 Licensing Restrictions for NetWare Clients... 4-8 4.24 License Registrar Fails to Release PC Concurrent Licenses.......................... 4-9 4.25 Incorrect SYSCON Error Message............... 4-10 4.26 Using the DOS MOVE Command................... 4-10 4.27 Using CD-ROM Drives as NetWare Volumes....... 4-11 Figures 3-1 The NetWare Printer Configuration........ 3-13 Tables 3-1 OpenVMS Operating System Versions and ECO Kit Names................................ 3-27 vi ________________________________________________________________ Preface Purpose This document presents: o Features of this product o Guidelines for using this product o Known problems o Unsupported software Audience This manual is written for the system or network administrator who must install, configure, and manage the PATHWORKS for OpenVMS (NetWare) server software. Related Documents In addition to these notes, the PATHWORKS for OpenVMS documentation set includes the following manuals: Read This First Explains how to find information in the PATHWORKS for OpenVMS documentation set. PATHWORKS for OpenVMS Explains how to install the PATHWORKS for OpenVMS (NetWare) Installation and server software. Upgrade Guide Guide to Managing Describes how to use the license PATHWORKS Licenses management software to manage client licenses. vii NetWare Concepts Provides a detailed reference of PATHWORKS for OpenVMS (NetWare) topics and concepts. NetWare API Reference Consists of two documents, the NetWare Set API Reference and Differences Document, that provide reference information about NetWare APIs. NetWare Troubleshooting Provides troubleshooting information and System Messages for PATHWORKS for OpenVMS (NetWare) and describes NetWare server and client system messages. NetWare Utilities Provides reference information for NetWare commands and utilities. Planning and Setup Explains how to plan and set up the Guide PATHWORKS for OpenVMS (NetWare) server. Printer Administration Explains how to set up and manage a Guide print server. Server Administration Describes how to configure and manage Guide the PATHWORKS for OpenVMS (NetWare) file server. Server Master Index Provides a master index of the PATHWORKS for OpenVMS (NetWare) documentation. viii Conventions This manual uses the following conventions: Convention Meaning ---- --- While you hold down , press another key or a pointing device button. Press the key that executes commands or terminates a sequence. This key is labeled or , depending on your keyboard. "enter" Type all required text, spaces, and punctuation marks; then press or , depending on your keyboard. italics Italicized type indicates a variable in a command line. boldface In examples of dialog between you and the system, boldface type indicates information that you enter. Note Notes provide information of special importance. Caution Cautions provide information to prevent damage to equipment or software. ix 1 ________________________________________________________________ Distribution Media The software kit consists of the following backup savesets: __________________________________________________________ Saveset_Name__________OpenVMS_System______________________ PWRK060.A Alpha PWRK060.C Alpha PWRK060.E Alpha PWRK060.G Alpha PWRK060.H_____________Alpha_______________________________ Distribution Media 1-1 2 ________________________________________________________________ PATHWORKS V1.0G for OpenVMS (NetWare) Features This section describes highlights and features of the PATHWORKS V1.0G for OpenVMS (NetWare) product. The following OpenVMS operating system versions are supported: o OpenVMS Alpha Version 7.1 This release of PATHWORKS for OpenVMS (NetWare) is distributed as part of the PATHWORKS for OpenVMS software kit, which includes the following: o PATHWORKS V1.0G for OpenVMS (NetWare) software o PATHWORKS V6.0 for OpenVMS (Advanced Server) software o PATHWORKS license server software o DECprint Supervisor for OpenVMS software 2.1 Optional DECprint Supervisor for OpenVMS Software Available The PATHWORKS for OpenVMS distribution kit includes two kits for the DECprint Supervisor (DCPS) for OpenVMS: VAX and Alpha. DCPS is a family of layered products that runs on OpenVMS VAX and Alpha to provide access through the OpenVMS queuing system to selected PostScript printers. To use DCPS, you must install the kit for either VAX or Alpha accordingly. You do not need a separate license to use DCPS with NetWare clients. PATHWORKS V1.0G for OpenVMS (NetWare) Features 2-1 PATHWORKS V1.0G for OpenVMS (NetWare) Features 2.2 New NVT Client Software 2.2 New NVT Client Software In PATHWORKS V1.0 for OpenVMS (NetWare), NVT had its own driver and was implemented to run over IPX. In PATHWORKS V1.0G for OpenVMS (NetWare), there is no separate NVT driver; the NVT implementation runs over SPX. This implementation of NVT over SPX (also called NVT2) requires a new NVT client program. The following NVT client programs are available in the SYS:\PUBLIC directory: o NVT.EXE - Client TSR, to be used to communicate with the NVT server in PATHWORKS V1.0G for OpenVMS (NetWare) using NVT/SPX. This TSR works in both INT14 and INT6B interrupt modes. o NVT-V1.EXE - Client TSR, to be used to communicate with the NVT server in PATHWORKS V1.0G for OpenVMS (NetWare) using NVT/IPX. This TSR works in both INT14 and INT6B interrupt modes. o NVT.VLM - Client VLM, to be used to communicate with the NVT server in PATHWORKS V1.0G for OpenVMS (NetWare) using NVT/SPX. This VLM should be used by NetWare clients that are set up to use VLMs. This VLM works only in INT14 mode when using SETHOST as the terminal emulator. You must ensure that SETHOST is set up to use INT14 mode (that is, service type NVT in the Communications Setup) when using it with the VLM client. 2.3 Frame Type Support In addition to the ETHERNET_II (DIX) and the IEEE 802.3 with 802.2 SAP (E0), this release supports Ethernet Raw 802.3. This version of PATHWORKS V1.0G for OpenVMS (NetWare) supports the "802.3-Raw" frame-type for Ethernet media. The "802.3-Raw" frame-type is the original (earliest) frame type used by Novell. Since this frame type does not conform to IEEE recommendations, it is no longer recommended by Novell for new networks. However, this release supports 802.3-Raw for compatibility, because many existing systems are configured to use this older frame type. (For more information about configuring frame 2-2 PATHWORKS V1.0G for OpenVMS (NetWare) Features PATHWORKS V1.0G for OpenVMS (NetWare) Features 2.3 Frame Type Support types, refer to the PATHWORKS for OpenVMS Installation and Upgrade Guide. Because "802.3-Raw" does not conform to IEEE specs, it is inconsistent with some other products, specifically those that use 802.2/ISO protocols. One known example is DECnet- Plus. Do not configure this "802.3-Raw" frame-type on a LAN controller that is also configured to run DECNet-Plus. If you do, they will both attempt to claim 802.2 SAP "FE," and the product that starts first (normally DECnet-Plus) will claim it. The other product will fail during its startup with a "protocol-bind" error. For these types of LANs, you must choose one of the other frame types, such as Ethernet-II/DIX or IEEE 802.2/SAP-"E0." 2.4 Native NetWare Printing Support The PATHWORKS V1.0G for OpenVMS (NetWare) software allows OpenVMS users to print on native NetWare servers in the network. Refer to Section 3.11 for more information about using and managing this feature. 2.5 Enhancements to GETLAN and SCONSOLE Utilities "Media-type" and "Frame-type" fields have been added to the information displayed by the GETLAN utility and the SCONSOLE utility. This information can be helpful in understanding a server node's complete IPX-router configuration. 2.6 Support for ISO-9660 and High-Sierra CD-ROM Formats PATHWORKS V1.0G for OpenVMS (NetWare) provides support for the following CD-ROM formats as NetWare volumes: o ISO-9660 o High-Sierra OpenVMS operating system versions 6.2 and higher support mounting these two CD-ROM formats, using the 'F11CD' subsystem, which supports both locally- attached CD-ROM drives and Infoserver-based (LAN-connected) drives. Refer to Section 4.27 for recommendations on configuring these types of NetWare volumes. PATHWORKS V1.0G for OpenVMS (NetWare) Features 2-3 PATHWORKS V1.0G for OpenVMS (NetWare) Features 2.7 Print Queue Format Changes 2.7 Print Queue Format Changes The format of the print queue file has changed since V1.0 of PATHWORKS for OpenVMS (NetWare). If there are no print jobs in NetWare print queues when the NetWare server is installed, this change is transparent to the users. The installation procedure deletes all queue file information. The file server recreates it during the first startup after a successful installation. If there are jobs in a NetWare print queue during installation, the installation procedure gives the installer the option to either continue the installation and allow the installation procedure to delete all the queue files (all existing print jobs will be lost), or terminate the installation so that you can perform an orderly shut down of the print queues before you install the software. 2-4 PATHWORKS V1.0G for OpenVMS (NetWare) Features 3 ________________________________________________________________ Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) This chapter provides guidelines for using PATHWORKS V1.0G for OpenVMS (NetWare) that are not included in the product documentation. 3.1 Using PATHWORKS V1.0G for OpenVMS (NetWare) with PATHWORKS for OpenVMS Version 4.x If PATHWORKS for OpenVMS V4.x is running on the system on which you plan to install PATHWORKS V1.0G for OpenVMS (NetWare), you must stop and restart the PATHWORKS Version 4.x server after installation of PATHWORKS V1.0G for OpenVMS (NetWare) to avoid potential problems with the PCSA Mail Server. 3.2 Upgrading Third-Party NetWare Server Products When you upgrade your third-party NetWare server product to PATHWORKS V1.0G for OpenVMS (NetWare), you must: o Move bindery information, programs, and data files to the PATHWORKS directories o Define NetWare volumes The procedures for these operations are described in the following sections. 3.2.1 Moving Bindery Information Use the following procedure to move bindery information (users, groups, and trustees) from the old NetWare product directories to the new, PATHWORKS V1.0G for OpenVMS (NetWare) directories. o While your third-party product is running: 1. Determine the location of the NetWare SYS volume. In the following example, the NetWare SYS volume Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-1 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.2 Upgrading Third-Party NetWare Server Products is on disk USER1:, under the NETWARE_VMS_SYS_VOLUME directory. $ search sys$specific:[netware_vms_files]*.com netware_vms_sys_volume ****************************** SYS$SPECIFIC:[NETWARE_VMS_FILES]NW_DEF_CONFIG.COM;1 $ nwvms_def_sys_volume == "USER1:[NETWARE_VMS_SYS_VOLUME]" 2. Install PATHWORKS V1.0G for OpenVMS (NetWare). 3. Answer the question that asks where you want to put the NetWare SYS volume with a different location from the location of the third-party product. You can put the new SYS volume on the same disk as the old SYS volume, as long as the directory names are different. In the following example, the new NetWare SYS Volume will be placed on disk USER2:, under the PWVN$SYSVOL directory. * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]: user2: 4. After the installation is complete, go into the PATHWORKS V1.0G for OpenVMS (NetWare) SYS volume and search for BINDDOWN.EXE in the SYSTEM directory. $ direct user2:[pwvn$sysvol.system]binddown.exe Directory USER2:[PWVN$SYSVOL.SYSTEM] BINDDOWN.EXE;1 Total of 1 file. $ COPY/LOG USER2:[PWVN$SYSVOL.SYSTEM]BINDDOWN.EXE _To: USER1:[NETWARE_VMS_SYS_VOLUME.SYSTEM] %COPY-S-COPIED, USER2:[PWVN$SYSVOL.SYSTEM]BINDDOWN.EXE;1 copied to USER1:[NETWARE_VMS_SYS_VOLUME.SYSTEM]BINDDOWN.EXE;1 (202 blocks) 5. On a client system, log in to the SUPERVISOR account on the third-party server product. It will ask for the password to the SUPERVISOR account. In the following example, HYDRAM is the name of the third-party server. H:\LOGIN>login hydram/supervisor 3-2 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.2 Upgrading Third-Party NetWare Server Products 6. Download the third-party server's bindery into a data file on one of the client's local disks. Make sure this data file is not on a NetWare-served disk. The program will ask for the password to the SUPERVISOR account. In the following example, C:BINDDOWN.DAT is the data file, HYDRAM is the name of the third-party server, and DOWNLOAD is the command parameter. H:\SYSTEM>binddown c:binddown.dat hydram download 7. Shut down the third-party server, including the IPX /SPX transport. (It may be necessary to reboot the server in order to shut down the transport.) o While PATHWORKS V1.0G for OpenVMS (NetWare) is running: 1. Configure and start up the PATHWORKS V1.0G for OpenVMS (NetWare) server, if necessary. 2. Return to the same client system as before and log in as SUPERVISOR. The client system will ask for the password to the SUPERVISOR account. If this is the first time you are logging in, the password is blank, so press . In the following example, HYDRAM_PNW is the name of the PATHWORKS V1.0G for OpenVMS (NetWare) server. H:\LOGIN>login hydram_pnw/supervisor 3. Upload the server's bindery from the data file to the server. The program will ask for the password to the SUPERVISOR account. If you haven't set a password for the SUPERVISOR account yet, press . In the following example, C:BINDDOWN.DAT is the data file, HYDRAM_PNW is the name of the PATHWORKS V1.0G for OpenVMS (NetWare) server, and UPLOAD is the command parameter. H:\SYSTEM>binddown c:binddown.dat hydram_pnw upload Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-3 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.2 Upgrading Third-Party NetWare Server Products 3.2.2 Defining Volumes and Moving Programs and Data Files This section describes the procedure to recreate volumes that you had defined under the third-party server. The bindery does not contain volume information, so the volume definitions under the third-party server are not transferred during the binddown and bindup procedure. Use the SCONSOLE utility on the server system to create volume definitions. If you have other programs and data files stored under the third-party's SYS volume, those programs and data files are no longer automatically available after you upgrade to PATHWORKS V1.0G for OpenVMS (NetWare). However, you can create a volume to point to the old SYS volume. Create volumes, and move programs and data files from the old SYS volume to the new SYS volume, as follows: o On the server system: 1. Start SCONSOLE. $ @sys$startup:pwvn$commands $ sconsole 2. Create a volume that points to the old SYS volume. Call the volume something like OLDSYS. 3. Create any other volumes that you had defined under the third-party server. 4. Shut down the PATHWORKS V1.0G for OpenVMS (NetWare) server. 5. Start up the PATHWORKS V1.0G for OpenVMS (NetWare) server. 6. Exit SCONSOLE. o On any client system: 1. Log in to the SUPERVISOR account. Remember that restarting the server terminates all previous sessions. H:\LOGIN>login hydram_pnw/supervisor 3-4 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.2 Upgrading Third-Party NetWare Server Products 2. Map a drive to the old SYS volume. In the following example, O: is an available drive, and OLDSYS was the volume created to point to the top of the old SYS volume. H:\SYSTEM>map O:=OLDSYS: 3. Copy programs from the old SYS volume to the new SYS volume. In the following example, MYPROG.EXE is a program that was previously placed in the PUBLIC directory on the SYS Volume, and is not a part of the PATHWORKS V1.0G for OpenVMS (NetWare) distribution. H:\SYSTEM>copy O:\PUBLIC\MYPROG.EXE H:\PUBLIC 4. Copy data files from the old SYS volume to the new SYS volume. Note that you do not need to copy any programs or data files on volumes other than the SYS volume. 3.3 Installation on Multiple Members of a VMScluster When installing PATHWORKS V1.0G for OpenVMS (NetWare) on multiple members of a VMScluster, you must take special precautions when answering the following installation question: * NetWare SYS volume location [SYS$SYSDEVICE:[PWVN$SYSVOL]]: It is important that you specify the same answer on all members of the cluster. Using two different answers that refer to the same physical disk and directory is not enough. The specific text of the answer must be the same. Furthermore, if the answer contains a logical name, for example, SYS$SYSDEVICE, as in the default answer, then this logical name MUST translate to the same physical device on all members of the cluster. Failure to satisfy these requirements can result in one or more of the file servers failing to start. These file servers will have a log file entry that states "PNWError(0xFF, NWDMain()): Volume SYS not added." Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-5 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.3 Installation on Multiple Members of a VMScluster Digital recommends that you specify a physical device and directory in response to this question when installing on multiple members of a VMScluster. 3.4 Determining Channel Count The OpenVMS SYSGEN parameter CHANNELCNT governs the maximum number of channels available. The file server process and the NVT daemon process can create demands that require you to increase the value for CHANNELCNT. Some other products may have even higher requirements than this product. To ensure that these other applications do not fail because of a CHANNELCNT value that is too low, you should only increase the current value; do not decrease it. The following examples show how to compute the value of this parameter of the file server and the NVT daemon. Once you have the values for the file server and NVT, add these values to the current value of the CHANNELCNT parameter. 3.4.1 File server example Use the following formula to compute the minimum value for CHANNELCNT needed by the file server: CHANNELCNT = 32 + ((# clients) * (# unique files open per client)) 3.4.2 NVT daemon example The NVT subsystem allows interactive logins to an OpenVMS system from a PC-based client. Use the following formula to compute the minimum value of the SYSGEN channel count parameter needed by the NVT subsystem: CHANNELCNT = 1 + ((2) * (# of NVT clients)) 3.5 Files the NetWare File Server Cannot Write There are some types of files that the NetWare file server can read but cannot write. These files include the following types of organization: o Relative or index organizations o Sequential, record formats of variable length or variable length with fixed length control 3-6 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.5 Files the NetWare File Server Cannot Write o Sequential, record format of fixed length, and any one of the following types of files: - File in which carriage control is Control, FORTRAN, or Print. - Files where the record length is an odd number. - Files where the record length is not a power of two and the record attribute is Blocking (that is, data cannot space block boundaries). The NetWare file server is able to write only to files that can be considered a continuous stream of data bytes. The types of files listed above have implicit data bytes, such as CR/LF, that are not contained within the data, or contain bytes that are either RMS record control information or are unused bytes in the file. 3.6 PSERVER Name The PSERVER name is limited to 15 characters even though PCONSOLE states that the limit for the PSERVER name is 47 characters. 3.7 STOP/ID on the NPS Daemon Process Do not do a STOP/ID on the NPS daemon process. If you do a STOP/ID, it may cause a system crash. Use @SYS$STARTUP:PWVN$SHUTDOWN or the SCONSOLE utility to shut down the NPS Daemon process. 3.8 Startup Requirements for Utilities Host-based NetWare utilities, including SCONSOLE, do not work until you run SYS$STARTUP:PWVN$STARTUP to start NetWare. Once you have started the NetWare file server, SCONSOLE can continue to run even if the NetWare file server is shut down. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-7 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.9 Saving and Restoring the Bindery 3.9 Saving and Restoring the Bindery In general, the BINDDOWN procedure does not fully restore every bindery entry. For instance, bindery information added since the server was last started may not be preserved. Also, for some subsystems, some configuration information is stored in the bindery and some stored elsewhere. Also, some passwords may be lost or corrupted. For example, in the printing subsystem, after a BINDDOWN /BINDUP procedure, you may need to recreate your print queues and print servers. If the print queues and print servers have been restored from the bindery, use the PCONSOLE utility to fully restore printing capabilities as follows: 1. In the Print Server Information menu, restore your printer number. 2. In the Print Server Information menu, "Queues Serviced by Printer", restore the mapping from print server to print queue. 3. If your print servers had passwords, restore each password manually. For detailed configuration information, see the Printer Administration Guide. 3.9.1 Running BINDDOWN with Active Connections If the BINDDOWN procedure is run while there are some active connections to the file server, some bindery information may not be preserved. Therefore, it is strongly recommended that you run BINDDOWN only when there is no other active connection to the server. 3.10 Configuring Print Services Rule: Each PATHWORKS V1.0G for OpenVMS (NetWare) print server can serve only one queue. The NetWare print queue can be located on any NetWare file server on the LAN. If you want to serve multiple queues, you must define a PATHWORKS V1.0G for OpenVMS (NetWare) print server for each print queue. You can create multiple print servers on 3-8 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.10 Configuring Print Services the same OpenVMS system; each print server must serve only one print queue. You must use both PCONSOLE and SCONSOLE to define a NetWare print queue and associate the print queue with a PATHWORKS V1.0G for OpenVMS (NetWare) print server. You can define multiple print queues using PCONSOLE; however, the PATHWORKS V1.0G for OpenVMS (NetWare) print server serves only the NetWare print queue that you have assigned to the print server using SCONSOLE. The following sections explain how to set up a print server to: o Serve a PATHWORKS V1.0G for OpenVMS (NetWare) server on the same OpenVMS system (local file server) o Serve NetWare file servers that are located on systems other than the local OpenVMS system (remote file servers, can be PATHWORKS V1.0G for OpenVMS (NetWare) file servers or native NetWare file servers) 3.10.1 How to Set Up a Print Server to Serve a Remote NetWare File Server This section describes how to set up a print server to accept print jobs from a remote NetWare file server. For more details about the steps in this procedure, refer to the PATHWORKS for OpenVMS Printer Administration Guide. To set up a print server to serve a remote file server, you first use PCONSOLE and then SCONSOLE. 1. Log in to the remote NetWare file server (that which will be served by the new print server) as SUPERVISOR. Then run PCONSOLE and perform the following steps: a. Create a NetWare print queue. b. Create a NetWare print server. c. Define the printer. d. Assign the NetWare print queue to the printer. e. Exit PCONSOLE. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-9 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.10 Configuring Print Services 2. Log in to the OpenVMS system that provides the NetWare printing service, as an OpenVMS user with SYSTEM privileges. Then run SCONSOLE and perform the following steps: a. Assign the NetWare print server name to the remote NetWare file server name that you created with PCONSOLE. b. Assign the NetWare print server name to the NetWare print queue that you created with PCONSOLE. 3. Assign the NetWare print server to an OpenVMS print queue. 4. Assign any NetWare forms to OpenVMS forms names. 5. Shut down all print servers on the OpenVMS system. 6. Start up all print servers on the OpenVMS system. 3.10.2 Error Creating Print Queues If a print queue directory already exists for a print queue that you attempt to create using PCONSOLE, the following error message is displayed: ERROR REPORT SERVER ERROR CreateQueue return error 255. DESCRIPTION The description for this error is not available. SEVERITY The current operation cannot be completed. To correct this error: 1. Select "Print Queue Information" option from the "Available Option" of PCONSOLE menu. 2. If there are no print queues defined, then go to step 8. 3. Select the first print queue and press enter to display the "Print Queue Information" menu. 3-10 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.10 Configuring Print Services 4. Select the Print Queue ID to find out the print queue Object ID. The Object ID identifies the print queue in the bindery. 5. Write down the Object ID of the print queue. 6. Press the Escape key repeatedly until the Print Queue menu is displayed. 7. Repeat step 3-6 until you reach the end of the print queue list. 8. Change directory to SYS:\SYSTEM. 9. List all directories with "Q_*" names. 10.If any directories have name "Q_*" where * does not match any Object ID without zeros at the front, then delete the directories. 11.Repeat the normal operation to create a NetWare print queue. 3.10.3 Error Creating Print Servers You may be unable to create a print server, if the print server directory already exists. The following error message is displayed when you use PCONSOLE to create a print server: ERROR REPORT ERROR DOSCreateDirectory returned error 5. DESCRIPTION The system failed to create directory "\\SERVER_PNW\SYS\SYSTEM\00000C01" because access was denied. SEVERITY The current operation cannot be completed. To correct this error: 1. Select "Print Server Information" option from the "Available Option" of PCONSOLE menu. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-11 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.10 Configuring Print Services 2. If there are no print servers defined, then go to step 8. 3. Select the first print server and press enter to display the "Print Server Information" menu. 4. Select the Print Server ID to find out the print server Object ID. The Object ID identifies the print server in the bindery. 5. Write down the Object ID of the print server. 6. Press the Escape key repeatedly until the Print Servers menu is displayed. 7. Repeat step 3-6 until the end of the print servers list. 8. Change current drive and directory to SYS:\SYSTEM. 9. List all directories with 0000* names. 10.If any directory's name does not match any print server's Object ID, then delete the directory (only if the directory name begins with 0000). 11.Repeat the normal operation to create a NetWare print server. 3.11 Printing to Native NetWare Printers The PATHWORKS for OpenVMS (NetWare) software allows OpenVMS users to print on printers connected to native NetWare servers. The OpenVMS print queue is associated with a print queue on the NetWare server, and the DCL PRINT command allows user to submit print jobs just as they would print to an OpenVMS printer. As this figure shows, the printing system requires a print queue on the OpenVMS system (in the following examples, print queue NWPRINT on system OVMS8), which is associated with the print queue on the native NetWare server system (print queue HP_JET on system NW_SERVER). 3-12 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.11 Printing to Native NetWare Printers Figure 3-1 The NetWare Printer Configuration +-------------------+ +--------------------------------+ | User Workstation |-----------> | OpenVMS System (OVMS8::) | | Print job NWJOB | |--------------------------------| +-------------------+ | OpenVMS Print Queue (NWPRINT) | +--------------------------------+ | | | V +-----------+ +---------------------------------+ | HPIIIp | <-----------------| NetWare Print Queue (HP_JET) | | Printer | |---------------------------------| +-----------+ | NetWare Server (NW_SERVER) | +---------------------------------+ Use the DCL PRINT command to submit the print job (NWJOB) to the OpenVMS print queue (NWPRINT). The print job is automatically transferred to the print queue on the native NetWare server from the OpenVMS system, and printed on the printer (in this example, an HP LaserJet printer). The OpenVMS system must have the PATHWORKS for OpenVMS (NetWare) server installed, and the native NetWare server must be in the same network with the OpenVMS system. 3.11.1 Management of the NetWare Print Queue For the most part, managing a print queue on OpenVMS that is attached to a print queue on a NetWare server is identical to managing other OpenVMS print queues. To configure and initialize the print queue, use the following procedure. 3.11.1.1 Configuring the NetWare Printer Queue Use the provided NetWare print queue configuration file, installed as: PWVN$CONF_DIR:PWVN$NWPRINT.CFG Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-13 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.11 Printing to Native NetWare Printers This configuration file describes how to configure the print queue and shows an example of a properly configured NetWare print queue. Add the configuration information about the NetWare print queue at the end of the configuration file. You provide the following information in the configuration file: o Name of the OpenVMS print queue o Name of the NetWare server o Name of the print queue on the NetWare server o User name for logging in to the NetWare server o Password for the user name Initialize the NetWare print queue in the same startup procedure used to initialize the other OpenVMS print queues. Include the /PROCESSOR=PWVN$SMB qualifier to specify the NetWare print symbiont. For example, to initialize a print queue called NWPRINT for the NetWare printer, enter the following command: $ INITIALIZE/QUEUE/PROCESSOR=PWVN$SMB NWPRINT 3.11.2 Troubleshooting the NetWare Print Queue Error messages and events are recorded in the NetWare print queue log file. The log file name is as follows, where queue-name is the name of the OpenVMS print queue: PWVN$LOGFILES:PWVN$NSSP_queue-name.LOG For example, for the OpenVMS print queue NWPRINT, the log file name is PWVN$LOGFILES:PWVN$NSSP_NWPRINT.LOG. For more information about the status of the NetWare print queue, use the NSHOW command, as described in Section 3.11.3.1. 3-14 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.11 Printing to Native NetWare Printers 3.11.3 Using the NetWare Printer An OpenVMS user can print jobs to the NetWare printer using the DCL PRINT command, specifying the NetWare print queue. For example, to print NWJOB.TXT to the print queue that is associated with the printer on the native NetWare server (queue name NWPRINT), enter the following command: $ PRINT NWJOB.TXT/QUEUE=NWPRINT Job NWJOB (queue NWPRINT, entry 152) started on NWPRINT Limitations NetWare print queues do not have all the features of OpenVMS print queues, which imposes certain limitations on the functions of NetWare print queues. For example: o The /PARAMETERS qualifer to the PRINT command, which is used to specify PostScript printing options, is ignored if the NetWare printer is not a PostScript printer. o The /NOTIFY qualifier to the PRINT command reports the starting and completion of print jobs when the NetWare server recieves the print job, not when the printer actually starts printing and completes printing the job. 3.11.3.1 Displaying NetWare Print Jobs To see the print jobs in the NetWare print queue, use the DCL command NSHOW, which is provided with the PATHWORKS V1.0G for OpenVMS (NetWare) software. This command lists all the print jobs submitted on the OpenVMS system for the NetWare printer, regardless of whether the print job has been transmitted to the NetWare system or is still on the OpenVMS system. You must specify the OpenVMS queue name with the NSHOW command. For example, to display all the print jobs for the OpenVMS print queue NWPRINT, enter the following command: Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-15 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.11 Printing to Native NetWare Printers $ NSHOW NWPRINT Printer queue NWPRINT, paused, on OVMS8, mounted form DEFAULT Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 151 MAXLIMITS MEIER 1 Pending 150 PWVN$MSG MEIER 3 Pending NetWare printer queue HP_JET, stalled, on server NW_SERVER Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 152 NWJOB MEIER 9 Pending $ As this example shows, the NSHOW command displays the status of the print jobs in the OpenVMS print queue (NW_ OUTPUT1), as well as the print jobs in the NetWare server print queue (NWPRINT). The status of the print queue on the NetWare server may be one of the following: __________________________________________________________ Queue Status____Meaning_________________________________________ idle There are no jobs in the queue. busy There are one or more jobs in the queue. paused Servers have been disabled from servicing the jobs in the queue. This status is derived from the setting of the Servers Can Serve Jobs in Queue parameter under Operator Jobs under Queue Status in PCONSOLE. stalled No NetWare print server is currently servicing __________the_queue_______________________________________ The status of the print jobs in the print queue on the NetWare server may be one of the following: 3-16 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.11 Printing to Native NetWare Printers __________________________________________________________ Print Job Status____Meaning_________________________________________ Pending The job is ready to be printed. Printing The job is currently being printed Adding The job is in the process of being added to the print queue. Holding The job is set to HOLD by the user or the __________operator._______________________________________ 3.11.3.2 Deleting NetWare Print Jobs You can delete a print job that you submitted to the NetWare print queue, using the NDELETE command, which is only available if the PATHWORKS for OpenVMS (NetWare) software is installed on your OpenVMS system. The NDELETE command requires both of the following: o The name of the OpenVMS print queue assigned to the NetWare printer o The /ENTRY qualifier with the name of the print queue entry to delete For example, use NDELETE to delete the print job, specifying the name of the print queue on the NetWare server. Then use the NSHOW command to display the print jobs remaining in the print queue. $ NDELETE/ENTRY=152 NWPRINT %PWVN-I-DELETED, entry 152 aborting or deleted $ NSHOW NWPRINT Printer queue NWPRINT, paused, on OVMS8::, mounted form DEFAULT Entry Jobname Username Blocks Status ----- ------- -------- ------ ------ 151 MAXLIMITS MEIER 1 Pending 150 PWVN$MSG MEIER 3 Pending NetWare printer queue HP_JET, stalled, on server NW_SERVER $ A system manager, or a user with OPER privileges, can delete any print job in the NetWare print queue. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-17 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.11 Printing to Native NetWare Printers 3.11.4 Accounting Information for NetWare Print Jobs The OpenVMS accounting information is saved for NetWare print jobs as well as for OpenVMS print jobs. 3.12 Portable NetWare Programming Examples PATHWORKS V1.0G for OpenVMS (NetWare) provides a sample program that uses the Portable NetWare programming interface. For more information about this sample program, see the files located at PWVN$EXAMPLES:EXAMPLE.*. 3.13 Terminal Screen Display Mode When you start the PATHWORKS License Manager user interface (SYS$SYSTEM:PWRK$LICENSE_MANAGER.EXE), it sets the terminal's video settings to light text on dark background. If it changed the termin setting, it is not restored when you exit the application. To reset the video settings, exit the License Manager and reset the terminal attributes manually. 3.14 Intruder Detection Error Message A client may receive the following error message when trying to access the server: "Intruder detection has locked out this account" If this error message is displayed, check the following: 1. Does the client have a valid client license? To check for a valid client license, on the client, enter the following command: PWLICNW/SHOW 2. Are there sufficient concurrent (PWNWVMSCU01.00) licenses? To check for concurrent licenses, on the server, enter the following command: $SHOW LICENSE PWNWVMSCU01.00 3. Check the value of the parameter max_connections in the file PWVN$CONF_DIR:PWVN$NWCONFIG.CFG. Use the following formula to calculate the required value: 3-18 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.14 Intruder Detection Error Message max_connections = number of clients connecting with client licenses + number of clients connecting with concurrent licenses + number of print server connections + number of SCONSOLE sessions 3.15 IPX socket number x236 The IPX socket number 236 (hexadecimal) is reserved by Digital for the use of the PATHWORKS license software. 3.16 Redirecting the Location of the NetWare Dump File The dump file for the NetWare file server can be very large. By default, the dump file is stored in the directory defined by the logical name PWVN$LOGFILES. To change the location where the dump file, is stored, assign the system logical name PWVN$DUMPFILES to a new directory location before you start the PATHWORKS for OpenVMS (NetWare) server. For example: $ DEFINE/NOLOG/SYSTEM PWVN$DUMPFILES DKA200:[DUMPDIR]) 3.17 Deleting Files from a NetWare Volume When possible, files within a NetWare volume should be deleted from a client rather than from an OpenVMS process. When a file from within a volume is deleted directly from OpenVMS, the server continues to maintain a reference to that file, because it is unaware that it has been deleted. However, this leaves an unnecessary reference, and the reference must be bypassed for any wild card operations. If there are too many of these references, the performance of search operations may decrease. 3.18 Installing Paradox When you install the Paradox software to a network, the installation may fail if installed directly from the floppy kit. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-19 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.18 Installing Paradox To ensure a successful installation, copy the floppy disk contents to a local hard drive or network drive and install directly from the copy. The error message that appears when you install from floppy disks appears as a CRC failure while unzipping the compressed files. 3.19 Error Log Not Found If you are using SCONSOLE to view error logs and you select "View Print Server Error Log" on the Print Server Error Log Menu or "View Server Error Log" on the Server Error Log Menu, a message about an .ERR file in PWVN$LOGFILES: not found is displayed. This message can be ignored because these files are not written by PATHWORKS V1.0G for OpenVMS (NetWare). 3.20 Unmounted OpenVMS Disks If a volume resides on an OpenVMS disk that is not mounted when the server starts, the server does not make the volume available to NetWare users. However, SCONSOLE continues to list the volume information (VOLINFO does not.) The file server log file contains an entry similar to the following: PNWError(0xFF, NWDMain()): Volume not added. Before the volume can be available to NetWare users, the OpenVMS disk must be mounted and the file server must be stopped and restarted. 3.21 SLIST Output in a VMScluster When more than one file server is configured and running in a VMScluster, SLIST output from members of the VMScluster often lists one or more of the file servers twice. This behavior is erroneous, has no side effects, and can be ignored. 3-20 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.22 Required Privileges for Startup and Shutdown 3.22 Required Privileges for Startup and Shutdown SCONSOLE checks for a list of required privileges to execute full component startup and shutdown. If you select "Full Component Startup" and "Full Component Shutdown" and you have insufficient privileges, the message "%PWRK- F-NOPRIV, no privilege for attempted operation" is displayed and the full startup or shutdown will not execute completely. To perform full startup or shutdown with SCONSOLE, make sure that you have the additional privileges of GROUP, GRPNAM, OPER, PSWAPM and SETPRV. 3.23 Versions of the SYSCON Utility The current version of the NetWare SYSCON utility (V3.75) can not create user login scripts on the file server. An earlier version of the utility (V3.68) can create user login scripts. For this reason, both versions of the utility are supplied. SYS:\PUBLIC\SYSCON.EXE is the older version (V3.68), and SYS:\PUBLIC\SYSCON.NEW is the newer version (V3.75). 3.24 Correct Number of Global Pages for Running NetWare In the PATHWORKS for OpenVMS Installation and Upgrade Guide the minimum value for GBLPAGES during installation and configuration is listed as 7500 pages. The approximate number of global pages required to run the NetWare server is 9500 pages. You may see a message in the PWVN$SERVER.LOG file that indicates that global pages have been used up: 000002D7:00194BF0 PMM_mapmem: unexpected VMS status error! (000000C4) If you see this message, run AUTOGEN with FEEDBACK to increase the number of global pages. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-21 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.25 Upgrading License Server State Files 3.25 Upgrading License Server State Files When a new version of the license server is installed, it automatically upgrades earlier versions of the license server state file into the format used by the new version. This upgrade operation takes place the first time the new license server is started after installation. If a LAN Manager state file and a NetWare state file from previous versions of the servers are both found, the contents of both files are merged into a new license server state file. Any old state files that are used as part of an upgrade process are renamed so that further attempts to upgrade the old state files will not be made. At startup, the new license server checks to see if there are old state files to be merged or upgraded to form a new license server state file. The following are the file names of the old and new li- cense server state files that may be found in PWRK$LICENSE: New state file PWRK$LICENSE_SERVER_STATE.DAT Old LAN Manager PWRK$LICENSE_SERVER.DAT state file Old NetWare state PWL$SERVER_STATE.DAT file If a new state file and any old state file both exist in the PWRK$LICENSE directory, the license server fails to start, and posts both an operator message and a message to the license server log file, indicating that an illegal configuration of old and new state files was found. To start the license server, you must remove either the old state files or the new state file. For example, if you intend to use the old state files, delete the new state file. This allows the license server to upgrade the old state file into a new license server state file. On the other hand, if the contents of the old state files are not important, rename or delete the old state files. 3-22 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.25 Upgrading License Server State Files 3.25.0.1 Upgrading License Server State Files on a Node Not Previously Configured to Run the License Server The PATHWORKS for OpenVMS installation procedure places a template license server state file into the PWRK$LICENSE directory, if the template file is not already there. Even when the node is not configured to run the license server, the template state file is stored as: PWRK$LICENSE:PWRK$LICENSE_SERVER.DAT If you install PATHWORKS for OpenVMS and configure it to run the license server, the configuration procedure detects the presence of the template state file in PWRK$LICENSE, and attempts to upgrade it. This results in a partial license server name (for example, PWRK$L, instead of PWRK$Lnodename). Because the license server fails to form the license server name properly, clients are unable to connect to the node running the license server. The problem is made apparent by the announcement message in the license server log file, PWRK$LOGS:PWRK$LICENSE_ SERVER_nodename.LOG The announcement message is one of the first messages posted in the log file, and will look similar to the following, if the license server node name was constructed properly. In the following example, the license server node name is MYNODE: 17-FEB-1995 10:49:56.00 MESSAGE: License Server "MYNODE" is now processing LAN Manager license requests on node "MYNODE" If the license server upgraded a template file, the license server node name is missing from the message. For example: 17-FEB-1995 10:49:56.00 MESSAGE: License Server "" is now processing LAN Manager license requests on node "MYNODE" To fix this problem, rename or delete the template state file from the PWRK$LICENSE area, and shut down the license server. Stop the license server as described in the PATHWORKS for OpenVMS Installation and Upgrade Guide. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-23 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.25 Upgrading License Server State Files Then start the license server using the License Manager, as described in the Guide to Managing PATHWORKS Licenses. Specifically, follow these steps: 1. Rename the template license server state file from PWRK$LICENSE. For example: $ RENAME PWRK$LICENSE:PWRK$LICENSE_SERVER.DAT SYS$BACKUP:V50C_LICENSE_SERVER.DAT 2. Shut down the PATHWORKS servers and start them again, to restart the license server. The license server starts, creates a new state file, and remains disabled. 3. Run the License Manager utility, as follows: $ RUN SYS$SYSTEM:PWRK$LICENSE_MANAGER Choose Exit. The license server is automatically enabled. The clients should now be able to obtain licenses. 3.25.1 Upgrading License Server State Files on a an OpenVMS Cluster If you had previously run the PATHWORKS V1.0 for OpenVMS (NetWare) license server on one node of an OpenVMS cluster, you must configure that node using SYS$UPDATE:PWVN$CONFIG.COM and start PATHWORKS for OpenVMS (NetWare) before you start the license server. If you fail to configure and start the NetWare server, the license server will not start. The license server automatically upgrades the old license server state file to a new license server state file. If you want to ignore the data in the old license server state file, rename or delete the file PWRK$LICENSE:PWL$SERVER_STATE.DAT. Then you can start the new license server right away. For more information, refer to the Guide to Managing PATHWORKS Licenses. 3-24 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.26 Using the BINDFIX Utility 3.26 Using the BINDFIX Utility The BINDFIX.EXE utility, which resides in the SYSTEM directory of the SYS volume, should not be used against a PATHWORKS for OpenVMS (NetWare) server. This utility is not supported on implementations of NetWare for UNIX (portable NetWare). If the utility is run the following message appears in the server log file: PNWAlert: Bindery closed. This is not a problem. The bindery will be reopened the next time that access is required. 3.27 Documentation Clarification The PATHWORKS for OpenVMS (NetWare) Planning and Setup Guide contains some confusing information on page B-8, under "Usernames and Passwords." The corrected text reads as follows: User Names and Passwords If you attach to several file servers regularly, use the same username and password on each file server. Using the same user name and password enables you to place the ATTACH command in your login script without having to include your user name or password. For example, in your login script for file server FS1, you can enter the following ATTACH command: ATTACH FS2 The command ATTACH FS2 attaches your workstation to FS2 and logs you in using the user name and password that you specified for logging in to FS1. . . . The remaining portion of the appendix is correct as printed. Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-25 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.28 OpenVMS Operating System Delta Time Restriction 3.28 OpenVMS Operating System Delta Time Restriction Versions of the OpenVMS operating system prior to Version 7.1 have a documented delta-time restriction that may cause a serious error in the PATHWORKS for OpenVMS software, such as wrong file creation dates, beginning on or around 19-MAY-1997. Digital Equipment Corporation has provided ECOs (Engineering Change Orders) that remove the delta-time limit. Digital Equipment Corporation strongly recommends that all customers running the affected versions of OpenVMS install the appropriate ECO, as follows: 3-26 Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3.28 OpenVMS Operating System Delta Time Restriction Table 3-1 OpenVMS Operating System Versions and ECO Kit __________Names___________________________________________ For these versions of_OpenVMS:___________Install_this_ECO_kit:_______________ OpenVMS Alpha ALPLIBR05_070 Version 6.1 through Version 7.0 (inclusive): OpenVMS Alpha V6.1 V6.1-1H1 V6.1-1H2 V6.2 V6.2-1H1 V6.2-1H2 V6.2-1H3 V7.0 OpenVMS VAX Version VAXLIBR06_070 5.5 through Version 7.0 (inclusive): OpenVMS VAX V5.5 V5.5-1 V5.5-2 V5.5-2HW V5.5-2H4 V5.5-2HF OpenVMS VAX V6.0 OpenVMS VAX V6.1 OpenVMS VAX V6.2 OpenVMS_VAX_V7.0__________________________________________ ________________________Note ________________________ Systems running OpenVMS VAX Version 7.1 or OpenVMS Alpha Version 7.1 are not impacted and do not need to install the ECO. _____________________________________________________ Guidelines for Using PATHWORKS V1.0G for OpenVMS (NetWare) 3-27 4 ________________________________________________________________ Known Problems and Restrictions This chapter explains existing problems and restrictions in the PATHWORKS V1.0G for OpenVMS (NetWare) software. 4.1 User Disk and Volume Space Restrictions Unsupported You cannot restrict disk space or NetWare volume space on the OpenVMS system using NetWare utilities such as SYSCON or DSPACE. When you attempt to restrict a user's disk space usage using the SYSCON utility, you will see the following error on the screen: Error 0x89ff setting user Volume space restriction When the system displays this error message, the function you requested is not completed. If you use SYSCON to view the Volume/Disk restrictions submenu, you will see that Volume Space In Use is always 0. You may experience different behavior from a utility when attached to a native NetWare server as opposed to the PATHWORKS V1.0G for OpenVMS (NetWare) server, due to differences in NetWare versions. If possible, you should run the most recent versions of the utilities and update all out-of-date NetWare volumes accordingly. 4.2 Hybrid User UIC In the PATHWORKS V1.0G for OpenVMS (NetWare) Planning and Setup Guide, in the section called How to create user accounts, there is a note that states, "You cannot specify as hybrid user any user whose OpenVMS user identification (UIC) is less than 10." In fact, a member number can be any number. Known Problems and Restrictions 4-1 Known Problems and Restrictions 4.3 Accessing Files in a Cluster 4.3 Accessing Files in a Cluster To share files concurrently between multiple file servers running on separate VMScluster members, you must set the file attributes to RoSDiRi. If you assign any other type of file attributes to the files, some of the clients attempting to access the file through separate file servers on the VMScluster will fail to obtain access to the file. 4.4 Errors Returned from NetWare APIs On an error return from a NetWare API call, NWErrno contains an error code in the least significant octet. The error codes are listed in the PATHWORKS for OpenVMS (NetWare) NetWare API Reference Set. However, the documented list is incomplete, in that it does not describe the error code 0xFF. The FF error code indicates "some error" or "unknown error," or may represent any error. 4.5 License server user interface displays "noname" When the NWUSERNAME variable is not defined in the configuration template used by the client, the client licensing software may not be able to provide the client's user name when requesting a license from the license server. This causes the license server management interface to display clients with "noname" in the client name field. 4.6 Client can consume two licenses If the following sequence of events occurs, the client can consume two licenses: 1. The client is configured to use both LAN Manager and NetWare. The ClientID generated is a station address, for example: AA0004323323 2. The client's network login directory (for example, C:\PW) is deleted. 4-2 Known Problems and Restrictions Known Problems and Restrictions 4.6 Client can consume two licenses 3. The client is reconfigured for NetWare only. Then, the ClientID uses the network card hardware address, for example: 08002B323323 The same client may now consume two licenses from a license server because it is passing a different address when it is configured as NetWare-only client. This problem occurs only in the unique sequence of events described above. 4.7 Backing out of help screen may reset list After you have read the PATHWORKS License Manager online help on some selections, you are returned to the beginning of the list. The highlighted item is not the help item you just read. 4.8 License Manager may crash when deassigning a client license If you attempt to deassign or remove a client license from the PATHWORKS License Manager (PWRK$LICENSE_MANAGER) and the screen does not get updated, exit the License Manager and try again. If you do not exit the License Manager and you try to delete the same undeleted client in the same session, then the License Manager may crash. If this occurs, restart the License Manager and continue operations. 4.9 Disk Quota and Available Blocks If OpenVMS disk quotas are enabled on the NetWare SYS volume, and the available quota for the NetWare GUEST account (defined by the logical PWVN$GUEST_UIC) is less than 1000 blocks, the file server displays a message that it has insufficient quota and it does not start up. To correct this problem, disable OpenVMS disk quotas on the disk where the NetWare SYS volume is located. Or give the NetWare GUEST account an available OpenVMS disk quota of at least 1000 blocks on the disk where the NetWare SYS volume is located. Known Problems and Restrictions 4-3 Known Problems and Restrictions 4.10 Accessing the Bindery on a Clustered System 4.10 Accessing the Bindery on a Clustered System In a clustered environment, it is recommended that any additions to the bindery be made from a single client connected to the server. Heavy access to the bindery from multiple clients can produce BINDERY_LOCKED errors, or may produce the following error in the server log file: date time PWNError: RMS error 0xNNNN writing bindery; bindery may be corrupted now. If you see this error in the PWVN$LOGFILES:PWVN$SERVER.LOG file, you should stop the server and restore the bindery from a backup. 4.11 SUPERVISOR password during BINDDOWN/BINDUP procedure If you run BINDDOWN from server X and then run BINDUP on server Y, the SUPERVISOR password on server Y will be set to the SUPERVISOR password from server X (that is, the one saved in the BINDDOWN operation). 4.12 OpenVMS BACKUP/RESTORE and TRUSTEE Rights If you delete bindery objects using the DOS delete command, the trustee information about those objects is also erased. Trustee information is erased if you perform the backup procedure as follows: 1. Set trustee rights. 2. Back up bindery objects using OpenVMS. 3. Delete bindery objects using DOS. 4. Restore bindery objects using OpenVMS. In this process, the trustee information will not be restored, because the DOS delete command deletes the trustee entries too. To prevent the loss of trustee information, perform the following sequence of commands: 1. Set Trustee rights. 2. Back up bindery objects using OpenVMS. (Optionally, delete those objects using OpenVMS.) 3. Restore bindery objects using OpenVMS. 4-4 Known Problems and Restrictions Known Problems and Restrictions 4.12 OpenVMS BACKUP/RESTORE and TRUSTEE Rights 4. Do DIR/S command using DOS on the objects restored. 4.13 Deleting an Active Job in a NetWare Queue If you delete an actively printing job from the NetWare queue from a client, the print job in the OpenVMS queue is not aborted. The job in the OpenVMS queue continues to print to completion unless you manually delete the job from the OpenVMS queue. There is no problem deleting a job queued to a NetWare queue that has not yet started printing from the OpenVMS queue. 4.14 Associating NetWare Volumes and OpenVMS Disks The association between a NetWare volume and its location on an OpenVMS disk cannot be made using logical names or concealed device names. 4.15 Help Error In some cases, when ? is used to access online help in SCONSOLE, an incorrect HELP message, or the message "ERROR: Invalid character", is displayed. 4.16 Error with FILER If you attempt to set the directory attributes or inherited rights mask on a top-level directory with FILER, you get an error screen reporting that error 255 is unknown. In addition, the changes you attempted to make are not made. 4.17 Server Startup Failure In rare instances, the file server fails to start and the following error message is found in the file server logfile: GetFileServerNameLock; code : 0x9B8 This may occur when two or more file servers in an OpenVMS cluster do not share the same NetWare bindery. Configuring multiple SYS volumes in an OpenVMS cluster is unsupported and will result in a corrupted trustee database. See the PATHWORKS for OpenVMS Installation and Upgrade Guide for more information. Known Problems and Restrictions 4-5 Known Problems and Restrictions 4.18 Moving the NetWare System-Specific Directory 4.18 Moving the NetWare System-Specific Directory The NetWare configuration procedure (PWVN$CONFIG.COM) cannot be used to change the OpenVMS system-specific directory. To change the system-specific directory, use the following procedure: 1. Shut down the NetWare server, as follows: $ @SYS$STARTUP:PWVN$SHUTDOWN 2. Determine the location of the private area. This can be displayed with: $ SHOW LOGICAL PWVN$CONF_DIR The following example assumes this command translates into SYS$SPECIFIC:[PWVN$PRIVATE]. If it does not, substitute the correct translation. If you move the system specific directory to a shared device in an OpenVMS cluster, you should add your new directory name to the end of the node name, to ensure it remains node-specific. 3. Move the tree using BACKUP with the command: $ BACKUP SYS$SPECIFIC:[PWVN$PRIVATE...]*.*.* - target-disk:[PWVN$PRIVATE_NODEA]*.*.*/BY_OWNER=ORIGINAL/LOG 4. Run SYS$UPDATE:PWVN$CONFIG.COM, and answer NO to the following question: * Is this configuration satisfactory [YES]? 5. Answer the question: * System-specific directory [SYS$SPECIFIC:[PWVN$PRIVATE]]: with the root of the directory tree you created with BACKUP, for example: target-disk:[PWVN$PRIVATE_NODEA] 6. Restart the file server. After the file server is restarted successfully, delete the old directory tree located at SYS$SPECIFIC:[PWVN$PRIVATE]. 4-6 Known Problems and Restrictions Known Problems and Restrictions 4.19 VLM Client Pathname Restrictions 4.19 VLM Client Pathname Restrictions NetWare VLM clients have a problem dealing with path names that exceed 64 bytes. If you use a NetWare VLM client to work with a directory or a file with a path name that exceeds 64 bytes, you will get an error. 4.20 OpenVMS Logout During Reflections 4 for MS Windows Login When using NVT with Reflections 4 for MS Windows, the OpenVMS login prompt may time out before users can get to the Reflections 4 for MS Windows window and complete their login procedure. If this happens, on the OpenVMS host, change the value of the SYSGEN dynamic parameter LGI_ RETRY_TMO to 60 seconds, using the following procedure: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SET LGI_RETRY_TMO 60 SYSGEN> WRITE ACTIVE SYSGEN> WRITE CURRENT SYSGEN> EXIT 4.21 Running More Than One Version of the License Server If you upgrade to the most recent version of the file server, you should upgrade your license server as well. If you continue to use a license server component from a software kit earlier than PATHWORKS V1.0G for OpenVMS (NetWare), clients with TCP/IP transports may not be able to obtain licenses. Digital recommends that you use only one license server in the local area network. If you choose to run more than one license server, Digital recommends that you upgrade all license servers to PATHWORKS V1.0G for OpenVMS (NetWare) or later. 4.22 License Manager Server Name Display The License Manager server name display only displays one name. The name displayed is the node name portion of the license server name which the License Manager is communicating with. Known Problems and Restrictions 4-7 Known Problems and Restrictions 4.22 License Manager Server Name Display LAN Manager clients connect to license servers using the name "PWRK$Lnode". NetWare clients connect to license servers using the name "PWL_node_PNW". In the normal default case "node" is the node or cluster on which the license server is running for both the LAN Manager and NetWare names. There are some situations in which the node portion of the LAN Manager and NetWare license server names being used by a single license server are not the same. In this case the License Manager will still only display a single node name (the node which is part of the LAN Manager license server name). In other cases, the node name displayed may not be the name of the node on which the license server is executing. This can occur if the license server state file was moved from one node to another. If there is any question about the name that the license server uses, check the license server log file for the name being used by the license server. The license server logs this information when it starts up. The file specification for the PATHWORKS license server log file is PWRK$LOGS:PWRK$LICENSE_SERVER_node.LOG. 4.23 Licensing Restrictions for NetWare Clients In the following situations, NetWare clients may not be able to find the PATHWORKS License Server to verify a license: o If the license server is operating in an OpenVMS cluster and is enabled to run on more than one node in the cluster. o If the license server has been moved from one node to another but has retained the original license server name. When a PATHWORKS client license is issued to a client, most client software saves the name of the license server with the issued license, so the license server can be contacted to verify the license the next time the client boots. 4-8 Known Problems and Restrictions Known Problems and Restrictions 4.23 Licensing Restrictions for NetWare Clients Some PATHWORKS NetWare client licensing component software saves the address of the node on which the license server was running when it issued the license, instead of the license server name. In this case, if the node on which the license server is running changes after the license server has issued a license to a NetWare client, the NetWare client may not be able to find the license server even if the license server name has not changed. The simplest solution is to restrict the license server to running on a single node and not moving the license server to a different node. If PATHWORKS is being used in a VMScluster, and the license server is configured to run on the VMScluster, use the logical name PWRK$LICENSE_SERVER_INHIBIT to limit the license server to running on only one node of the VMScluster. Refer to "Tuning the License Software for OpenVMS" in the Guide to Managing PATHWORKS Licenses for details about how to use this logical name. If you move the license server, and the server has issued licenses to NetWare clients, delete the license data file (PWLICNW.DAT) on the clients and reboot them. This causes the clients to query the network and discover the new location of the license server. 4.24 License Registrar Fails to Release PC Concurrent Licenses Problem: The License Registrar fails to return server-based, concurrent-use licenses (FPS or PC Concurrent type (PAK Name = PWNWVMSCU01.00)) to the available pool after NetWare clients disconnect. Solution: If this occurs, please contact your DIGITAL support representative for further instructions. ________________________Note ________________________ PATHWORKS V1.0F for OpenVMS (NetWare) does not exhibit this behavior and can be used if you are Known Problems and Restrictions 4-9 Known Problems and Restrictions 4.24 License Registrar Fails to Release PC Concurrent Licenses not also running PATHWORKS for OpenVMS (Advanced Server) on the same system. _____________________________________________________ 4.25 Incorrect SYSCON Error Message If a WorkGroup Manager tries to grant Trustee Directory Assignments to a NetWare volume using the client utility SYSCON, but that WorkGroup Manager does not have access to the volume, an improper error message will be displayed: Error Report Error SetDrivePath returned error 3 Description The description for this error is not available. Severity The current operation cannot be completed The proper error message should be: You have insufficient rights to alter trustee assignments in PVA209C1: 4.26 Using the DOS MOVE Command Digital strongly recommends against using the DOS MOVE command with the PATHWORKS for OpenVMS (NetWare) file server, because it is possible to move a directory into itself, which will result in the loss of that directory and corruption of the underlying OpenVMS ODS2 file structures. For example: Q:\>dir Volume in drive Q is TEMP Volume Serial Number is 428A-7AED Directory of Q:\ 4-10 Known Problems and Restrictions Known Problems and Restrictions 4.26 Using the DOS MOVE Command A A 0 02-22-95 3:52p B B 0 02-22-95 3:52p C C 2 02-22-95 3:52p Z 02-22-95 5 files(s) 2 bytes 195,772,416 bytes free Q:\>move Z Z q:\z => q:z\z [ok] This would result in the loss of directory Z. Although it may seem unlikely that a user would move a directory into itself, consider the consequences of the following command: Q:\>move *.* Z q:\a.a => q:\z\a.a [ok] q:\b.b => q:\z\b.b [ok] q:\c.c => q:\z\d.d [ok] q:\z => q:\z\z [ok] This would result in the loss of directory Z. In addition, all the files that were in directory Z (A.A, B.B, C.C) would also be lost. 4.27 Using CD-ROM Drives as NetWare Volumes OpenVMS supports the 'F11CD' subsystem in OpenVMS Versions 6.2 and higher. In Version 6.2 of OpenVMS, an a patch is required for the 'F11CD' component, when using F11CD and PATHWORKS for OpenVMS (NetWare). In OpenVMS Versions 7.0 and higher, the patch is not needed because the problem is fixed in the OpenVMS operating system. To acquire this patch, request one of the following kits: __________________________________________________________ For this Request CPU_type__this_patch__Available_for_these_OpenVMS_Versions VAX VAXF11C01_ Version 6.2 062 Known Problems and Restrictions 4-11 Known Problems and Restrictions 4.27 Using CD-ROM Drives as NetWare Volumes __________________________________________________________ For this Request CPU_type__this_patch__Available_for_these_OpenVMS_Versions Alpha ALPF11C01_ Version 6.2 __________062_____________________________________________ Successful installation of this patch results in the following new images in the SYS$SYSTEM area: o F11CACP.EXE o F11DACP.EXE 4-12 Known Problems and Restrictions