![]() |
OVERVIEW If you have any of the OS/400 Integration for Novell NetWare
WHAT TO DO BEFORE THE UPGRADE You should delete your V3R1 Novell environment before you upgrade to V3R6: - Use the Delete Licensed Program (DLTLICPGM) command to delete licensed programs: -- DLTLICPGM LICPGM(5733SA1) -- DLTLICPGM LICPGM(5733SA2) -- DLTLICPGM LICPGM(5733SA3) - Use the Work with Network Server Descriptions (WRKNWSD) command to view and delete NWSDs of network server type *BASE and *NETWARE - Use the Work with Network Server Storage Spaces (WRKNWSSTG) command to view and delete client storage spaces that were associated with *BASE and *NETWARE NWSDs - Use the Work with IPX Descriptions (WRKIPXD) command to view and delete IPX descriptions - Use the Work with IPX Circuits (WRKIPXCCT) command to view and remove IPX circuits WHAT TO DO AFTER THE UPGRADE If you did not remove the Novell environment before you upgraded from V3R1 to V3R6, you should read this section. This section describes the objects associated with OS/400 Integration for Novell NetWare, how they are affected during the upgrade, and what to do about them after the upgrade. UPGRADE OVERVIEW There are two types of upgrade: 1) Replacing-a-release upgrade In this type of upgrade, the physical data storage of the AS/400 is moved to a new AS/400 system. All objects associated with V3R1 remain on the disks, including objects used with V3R1 OS/400 Integration for Novell NetWare. All objects associated with the SA1, SA2, and SA3 features can remain on V3R6 disk storage but are not functional. You can delete them. 2) Unload/reload method of upgrade, and the side-by-side method With these method, you save objects from the V3R1 system and restore them to the V3R6 system. You might choose to use a utility like Upgrade Assistant, or you might use existing Save/Restore commands to save and restore specific objects. Upgrade Assistant is a no-charge PTF that provides a menu-driven way to save and restore data. Most types of objects associated with the SA1, SA2, and SA3 features cannot be restored to V3R6; those that can be restored are not functional. WARNING: If either of the types of storage space that can be associated with SA2 and SA3 (a) server storage space objects (*SVRSTG objects) or (b) client storage space objects (NWS storage spaces) are linked to a LAN Server/400 NWSD it is possible to disrupt or damage that LAN Server/400 configuration with loss of data. You should DELETE SA2 and SA3 server or client storage space objects. UPGRADING OBJECTS Here are the objects associated with OS/400 Integration for Novell NetWare: Products/Features The features associated with NetWare are: - 5733-SA1, Network Extensions - 5733-SA2, Integration Services for FSIOP - 5733-SA3, OS/400 Integration for Novell NetWare If you used the replacing-a-release type of upgrade: - The SA2 feature appears on V3R6 and can be deleted - Use the Delete Licensed Program (DLTLICPGM) command to delete SA2 If you used the unload/reload method or the side-by-side type of upgrade: - SA1, SA2, and SA3 licensed programs cannot be installed on V3R6 Libraries Library (LIB) objects: - QFPNETE (5733-SA1, Network Extensions) - QFPINT (5733-SA2, Integration Services for FSIOP) - QFPNTWI (5733-SA3, OS/400 Integration for Novell NetWare) If you used the replacing-a-release type of upgrade: - The libraries are unusable on V3R6 and can be deleted If you used the unload/reload method or the side-by-side type of upgrade: - If you restored the libraries to V3R6, delete them Use the Delete Library (DLTLIB) command to delete the libraries. NWSDs Network Server Description (NWSD) objects: - *BASE (5733-SA2, Integration Services for FSIOP) - *NETWARE (5733-SA3, OS/400 Integration for Novell NetWare) If you used the replacing-a-release type of upgrade: - NWSDs are not distinguished by TYPE (*NETWARE versus *LANSERVER) on V3R6. - After the upgrade, *BASE or *NETWARE NWSDs are marked as DAMAGED and cannot be varied on. Use the Work with NWS Status (WRKNWSSTS) command to view, and the Delete Network Server Description (DLTNWSD) command to delete NWSDs formerly known as *BASE and *NETWARE on V3R1. If you used the unload/reload method or the side-by-side type of upgrade: - *BASE and *NETWARE NWSDs cannot be restored to V3R6 Server and client storage spaces Storage space objects: - Server storage spaces (object type *SVRSTG found in the QUSRSYS and QFPINT libraries) are created and linked by the system when you create a *NETWARE or *BASE NWSD. - Client storage spaces are created and linked by the system when you create a *NETWARE or *BASE NWSD. These client storage spaces hold the NetWare SYS volume; use WRKNWSSTG to see these storage spaces, linked as drive number 8. - Client storage spaces are created by you and linked to the appropriate *NETWARE or *BASE NWSD; use WRKNWSSTG to see these storage spaces. If you used the replacing-a-release type of upgrade: - Server storage spaces are deleted when you use DLTNWSD to delete the DAMAGED *BASE or *NETWARE NWSDs - Client storage spaces are not distinguished by FORMAT (*NETWARE, *FAT, or *HPFS) on V3R6 - You should delete all *NETWARE or *FAT client storage spaces If you used the unload/reload method or the side-by-side type of upgrade: - If you restored *SVRSTG objects formerly associated with *BASE or *NETWARE NWSDs, you should delete them from the QUSRSYS library - If you restored *NETWARE or *FAT client storage spaces to V3R6, you should delete them Use the Work with Network Server Storage Spaces (WRKNWSSTG) command to view and delete all client storage spaces formerly known as *NETWARE or *FAT, or *HPFS if you are certain the storage space was associated with a *NETWARE or *BASE NWSD. IPX objects If you used the replacing-a-release type of upgrade: - Use the Work with IPX Description (WRKIPXD) command to view and delete IPX descriptions If you used the unload/reload method or the side-by-side type of upgrade: - If you restored IPX descriptions to V3R6, use the Work with IPX Description (WRKIPXD) command to view and delete them DETAILS SECTION Storage Space Upgrade Problems Storage spaces assigned to a V3R1 Novell NetWare NWSD should NOT be restored to a V3R6 system. The following problems can occur: a) Restoring server storage spaces associated with a V3R1 *NETWARE NWSD onto V3R6, then reusing the *NETWARE NWSD name for a LAN Server for OS/400 NWSD will result in an error. For example, assume you restore onto a V3R6 system some *NETWARE server storage spaces (C and E drive are the *NETWARE server storage spaces). Then you create a LAN Server for OS/400 NWSD on the V3R6 system using the same name formerly used for a *BASE or *NETWARE NWSD on the V3R1 system. The new LAN Server for OS/400 NWSD will attempt to link the server storage spaces formerly associated with the *BASE or *NETWARE NWSD on the V3R1 system. Error messages will be logged when you attempt to vary on the NWSD. To recover, delete and recreate the NWSD which deletes and creates the correct server storage spaces (C and E drives). b) It is possible to LINK *NETWARE client storage spaces to a LAN Server for OS/400 NWSD, provided their drive letter mappings fall alphabetically AFTER any LAN Server for OS/400 storage space drive letter mappings. The NWSD can be varied on after the link occurs, but messages will be reported that errors occurred when formatting the storage space. WARNING: There exists a scenario that can result in complete LOSS of DATA from a LAN Server for OS/400 storage space. If you link a *NETWARE client storage space with a drive letter that alphabetically PRECEDES the drive letter mapping for a storage space formatted for LAN Server for OS/400, the LAN Server for OS/400 storage space can be rendered completely unusable with loss of data. For example, you inadvertently restore a *NETWARE client storage space to the V3R6 system. On the V3R6 system, you have a LAN Server for OS/400 NWSD with a client storage space mapped as the L drive. If you link the *NETWARE client storage space to the LAN Server for OS/400 NWSD as the K drive (K precedes L) alphabetically), the L drive will be damaged and rendered completely unusable with loss of data. To recover, you must perform these steps: 1) vary off the NWSD 2) use the Remove NWS Storage Link (RMVNWSSTGL) command to remove the K and L storage space links 3) restore the L drive from a backup 4) use the Add NWS Storage Link (ADDNWSSTGL) command to link the storage space to the NWSD as the L drive 5) vary on the NWSD c) Storage spaces assigned to a V3R1 *BASE NWSD can be of type *HPFS or *FAT. Storage spaces assigned to a LAN Server for OS/400 NWSD can be of type *HPFS (not *FAT). However, it is possible to incorrectly link a *FAT storage space to V3R6 LAN Server for OS/400 NWSD, and not receive an error message. IPX Circuit Configuration Information You are not allowed to start or end IPX support in V3R6; these commands are disabled. IPX is not supported in V3R6. If you upgrade to the V3R6 system, and you have IPX circuits defined on your V3R1 system, the V3R1 IPX circuit configuration files will be automatically upgraded to V3R6. These configuration files are AS/400 database files, and exist in the QUSRSYS library. These configuration files for IPX circuits, IPX circuit routes, and IPX circuit services have a different format for V3R1 as compared to V3R6. Other IPX configuration commands are supported in V3R6; however if you issue IPX commands against these IPX Circuits, you will see unsupported values in some of the detail fields. |