VS IWSCORE Version 1.80.01 Customer Software Release Notice 11th Edition -- January 2000 Copyright GetronicsWang Co., 2000 (This Document can be printed by running the DISPLAY Utility, Pressing PF(11) Report Mode and PF(15) Print.) Alliance is a registered trademark of Wang Laboratories, Inc. Lotus 1-2-3 and Symphony are trademarks of the Lotus Development Corporation. MS-DOS, MS EXCEL, MS Word For Windows, MS Windows For WorkGroups, MS ACCESS, and Multiplan are trademarks of Microsoft Corporation. PostScript is a registered trademark of Adobe Systems. PREFACE This Customer Software Release Notice (CSRN) contains information that you may need to install the VS IWSCORE, Release 1.80.01 software on your system. This document also describes the restrictions and special considerations relevant to the operation of the IWSCORE software, as well as the enhancements made to the software since the last release. Release 1.80.01 of IWSCORE includes several corrections to release 1.70.15 of IWSCORE. This document is written for VS system administrators. This CSRN refers to the following Wang documents: o VS IWSCORE Administration Guide (715-1306B) o VS Media, Transfer, and Device Utilities Reference (715-1716) o VS System Administration and Analysis Utilities Reference (715-1717) o VS System Operator's Guide (715-0418B) o Wang PC Local Integrated Services, Release 2.0, Operations Guide (715-1635) o WSN VS Network Configuration Guide (715-0165A) o Wang PC Redirector Operations Guide (715-1610A) o Wang PC Local Integrated Services Customer Software Release Notice (715-1888) CHAPTER 1 INTRODUCTION VS IWSCORE provides a set of software modules that perform all the VS support services needed to allow PCs (specifically, Wang Series PCs, and IBM PC and ATs and compatible) and the Wang 4450 workstation to use the VS as a print-, file-, or VS applications-server, or to act as VS workstations over Wang Local Connections (referred to as local coaxial connections in this document) and industry-standard 802.3 and 802.5 connections (referred to as LAN connections in this document). Additional PC software is required for client PCs to access VS-based services. The IWSCORE software consists of two software components: o Installation software, including the files necessary to install the IWSCORE components o IWSS (Intelligent Workstation Server) software, including the following components that enable PCs to access resources that are attached to the VS: - File and catalog routines - MS-DOS server - Print, Font, and Route server - DMPack server - Alliance server - PACE server subroutine (QLISRV) - InfoSharer server subroutine - VS support utility (IWSSAU) The QLISRV software (Query Language Interface Server) is the server used when you are accessing PACE databases. The InfoSharer server reads a data file as described in a VS control file, translates the file from WISCII to ASCII, then sends the file to the PC for processing through the InfoSharer application. The InfoSharer application is a data integration tool for the Wang PC 200/300 Series and the IBM PC/AT. This application is designed to easily convert information to and from PC and VS data types, and allows users to view directories and data prior to converting and moving the data. This application is also useful for transferring data to and from third-party applications (for example, Lotus 1-2-3 and dBASE III or IV). An optional InfoSharer component must be installed on your PC. The print server provided with IWSS is used by Wang applications and third-party external applications to manage the VS print queues. This server also contains procedures for packaging and submitting print files from print spool data that has been redirected to the print server by third-party external applications. In addition, the print server is used when printing VS files (for example, VS WP Plus files and VS data processing files) on a PC's local printer. CHAPTER 2 PREREQUISITES HARDWARE The hardware requirements for IWSCORE, Release 1.80.01, are as follows: o VS6, 6E, 65, 75E, 300, 5000, 6000, 7000, 8000, 9000, 10000, or 12000,16000. or VS85 or 100 with 16 MB of virtual address space, which includes a B-Bus board. Notes: These VS configurations must support 16 MB of virtual address space. Older CP4 equipment (VS85 and VS100) that lacks the necessary memory must be upgraded with a B-Bus board. For local coaxial connections, at least one 22V47 or 22V67 IOP must be configured on VS85 and VS100 systems. Although a 22V27 IOP at Revision 3 or higher may be used in place of the 22V47 or 22V67 IOP, there are some restrictions and special considerations associated with the use of the 22V27. These restrictions are described in Chapter 4. o Wang Series PC and IBM PC AT compatible (local coaxial connections) require the Wang Local Communications (WLOC) Option) o IBM PS/2 Models 50, 60, 70, and 80 Systems (local coaxial connections require the Micro Channel Local Office Connection) Note: For LAN connection requirements, refer to the documentation provided with your software. o Emulation modes and supported VS printers Emulation Modes Device Type Diablo 630 LCS15-2 and APTRE HP LaserJet Plus LCS15-2, LDP8, HPPCL5, PRTSYS30, LDP8E, and APTRE HP LaserJet Series II LCS15-2, LDP8, HPPCL5, PRTSYS30, LDP8E, and APTRE PostScript LCS15-2, PSPIB, APTRE HPGL HP-7550, HP-7580, HP-7585, HP-7586, HPPCL5, and APTRE EPSON EX1000 DM50/30E and APTRE EPSON LQ2500 HQPIB, LQPTRE, and APTRE NEC P5XL HQPIB, and APTRE ASCII Any VS System Printer IBM Extended ASCII Any VS Printer with Character Set Support for EASCII. SOFTWARE General Support o VS Operating System 7.21, 7.40, 7.42, or 7.50 or greater Notes: For CP7 machines containing UISIOs, microcode @MC25V67 must be Version 7.06.25 or greater. Version 05.07.30 or 55.07.30 or greater of the Serial IOC microcode @23V97W is recommended when running VS Operating System 7.40 or greater. Version 2.00.05 or greater is required for the Serial IOC microcode @MC50V67 & @50V97W. Version 1.00.08 or greater is required for the Serial IOC microcode @70V67. o VS NETCORE, Release 8.34 or greater for PC LAN/VS ACCESS File/Print Redirection only. o LCS-15 microcode (@MCLCS15@), Version 7.02.02 or greater is recommended o PC Local Integrated Services (PCLIS), Release 2.40.00 or greater (PC prerequisite, local environment only) with one of the following PC software products: WLOC (Wang Local Office Communications), Version 2.50.08 or greater (PC prerequisite, Wang Series PCs and IBM PC AT, local environment only) Wang Micro Channel Local Office Connection, Release 1.0 (PC prerequisite, IBM PS/2, Models 50, 60, 70, and 80 Systems) PCLIS provides redirection services and VS logon with VS WP/WP PLUS support; they do not support image processing. o VS/Local Connection, Release 1.10.00 or greater (VS and PC prerequisite; for local environments only). This software provides redirection services and VS logon with image support; it does not provide WP/WP PLUS support. o The VS/LAN CONNECTION product, Release 02.00 or greater (VS, ULC, and PC prerequisites; for LAN environments only). This product provides redirection services and VS logon with image support; it does not provide VS WP/WP PLUS support. VS Operating System(s) and Patches The following is REQUIRED to ensure valid Byte Range Locking Synchronization especially for Microsoft Applications EXCEL 5.0, ACCESS 2.0, LOTUS 1-2-3, and other DOS and Windows Applications that require accurate multiple Byte Range Locking. o VSOS 7.50.03 (No Patches necessary) o VSOS 7.50.01 Patch RSDP0880 o VSOS 7.50.02 Patch RSDP0889 o VSOS 7.42.00 Patch RSDP0858 o OS versions 7.21.09, 7.32.XX, and 7.40.02 DO NOT SUPPORT the REQUIRED Byte Range Locking Synchronization. See Chapter 5 MEDIA CONTENTS for files associated with VSOS and Patches for IWSCORE. VS WANG OFFICE modules o VS WANG OFFICE, due to IWSCORE changes to internal control blocks, during some MSDOS Redirected File processing e.g. External Copy to MSDOS Redirected File and OFFICE LINK, will CORRUPT the Byte Range Locking Database, very likely impacting NEGATIVELY all PC Client applications that utilize Byte Range Locking. o The following modules(5) should be replaced in library = WOLIB on the volume where VS WANG OFFICE is installed. DOSADMIN, DOSINPUT, DOSMPORT, DOSOUTPT, DOSXPORT ONLY Versions 2.05.87.07 or greater ( up to 3.01.00.01 currently ) will support this fix. PREVIOUS VERSIONS are NOT SUPPORTED. See Chapter 5 MEDIA CONTENTS for files associated with WANG OFFICE modules for IWSCORE. WP Support The following software is required for WP support: o WP, Release 4.60.10 or greater o WP Peripherals, Release 7.20.05 or greater WP Plus Support The following software is required for WP Plus support: o WP Plus, Release 3.0 or greater o WP Plus Peripherals, Release 3.0 or greater Printer Support To find out what printers are supported with your VS Operating System, refer to your VS Genedit Utility Reference, and your VS Device Support CSRN. PACE Support PACE, Release 2.00.80 or greater, is required to access PACE files using IWSCORE. CHAPTER 3 CORRECTIONS & ENHANCEMENTS The following Corrections are provided in Release 1.80.01 of IWSCORE: o IWSSRVR 2.00.00 will CORRECTLY assign the date stamp for IWSCORE MSDOS Redirected Files up to 01-01-2070, as seen in a) MSDOS 'dir' command b) Windows File Explorer c) and IWSCORE VS Program IWSSAU. The following Corrections are provided in Release 1.80.00 of IWSCORE: o Windows 95 Modification(W95MOD): (MSDOSSRV 102) Long File Names are not supported in IWSCORE. Any requests, e.g. Get File Attributes SMB=0x08, will be rejected with a Non-Successful Return Code for filenames greater than 8.3. o W95MOD: (MSDOSSRV 103) When Word 7.0 for Windows 95 Sends GETFILATRB with FilePath=NULLs Return ERRbadfile instead of ERRbadpath. o W95MOD: (MSDOSSRV 104) When Creating a Folder, Windows 95 eventually RENAMES a Directory. IWSCORE will NOW RENAME empty Directories(Folders). Non-empty Directories can not be RENAMED. o W95MOD: (MSDOSSRV 105) Support Word 7.0 for Windows 95 Request for Wildcard Directory Search for pathname=/xyz/abc/.def where ".def" means a wildcard search for all files with extension 'def' in subdirectory=/xyz/abc. The following Corrections are provided in Release 1.70.18 of IWSCORE: o Windows 95 modification: On SMB 0xC3 GetPrintQueue info return ZERO Print Queue entries instead of error code 0x0200FFFF. Although the information returned is incorrect, it allows Redirected Printing to function correctly. Previous to this modification the NET USE to Redirected Printing would fail. MSDOSSRV Footnote 100. o In conjunction with PCLIS 2.40.00 (version for Window 95 and WFW 3.11), the WFW 3.11 Client can now support PCLIS Redirected Printing without a NET START FULL. MSDOSSRV Footnote 101 o This fix allows IWSCORE to process NET USE to Redirected Printing for both Windows 95 and WFW 3.11 PC CLients MSDOSSRV Footnote (A,B)101 o This fix activates SMB commands LOCK & READ and WRITE & UNLOCK via smb flg bit 0. Previous NEGOTIATE PROTOCOLS would include the Dialect 1.03 where these commands were introduced. However, NEGOTIATE PROTOCOLS from WFW 3.11 and Win95 no longer offer Dialect 1.03, but have documented smb flg bit 0 as the mechanism to activate these commands. C101 The following Corrections are provided in Release 1.70.17 of IWSCORE: o Fix to M200023541. Installation when a Multi-Volume File Set is mounted would erroneously stop the Installation process. The Multi-Volume set would be incorrectly detected as a Remote Volume in a Resource Sharing Facility (RSF) cluster. o Fix to M200023542. Fix for Install-In-Place on SYSTEM Volume, i.e. don't RENAME IWSINC & IWSCSRC to XWSINC & XIWSCSRC. o Fix to M200023543. Fix for 'SSL probably not mapped' bug. Too much Modifiable Data Area will leave insufficient ADDRESS Space for mapping in the IWSSRVR SSL etc. for example running NETMAKE for a virgin IWSCORE VS Installation. The following Corrections are provided in Release 1.70.16 of IWSCORE: o Check for RSF attached, if so INSTALLATION of IWSCORE is halted. Using correct version of READVTOC program. o Process in WFW 3.11 the Directory entries . and ..; WinfoSharer could not click on the . and .. entries. o The CSRN has been updated to state version 2.05.87.07 for the Wang OFFICE modules. The following Enhancements are provided in Release 1.70.15 of IWSCORE: o The Maximum Number Redirected Files Per VS open concurrently has changed from 80 to 100. o The Maximum Number Locks Per File open concurrently has changed from 15 to 150. o The amount of User Modifiable Data Area required for these enhancements has changed from approximately 521K to approximately 600K. o The above enhancements with the VS OS Patches (described in Chapter 2 Software Prerequisites) are REQUIRED to ensure valid Byte Range Locking Synchronization especially for Microsoft Applications EXCEL 5.0, ACCESS 2.0, LOTUS 1-2-3, and other DOS and Windows Applications that require accurate multiple Byte Range Locking. The following corrections are provided in Release 1.70.15 of IWSCORE: o M2-23425 is addressed by the WANG OFFICE modules section in Chapter 2. Prerequisites. o M2-23374 and M41-12414 bugs are fixed in conjunction with the VSOS Patches in Chapter 2. Prerequisites. o M2-23499 WFWG 3.11 and EXCEL 5.0 bug is fixed. o M2-23480 The Incredible Shrinking Modifiable Data Area is mostly fixed. Search Directory requests from MSDOS 'Dir' and MS Windows FileMgr would consume about 368K (only in 1.70.12 - 1.70.14). Only about 15K is now consumed. Future fixes will properly manage the utilization of buffer space from the Modifiable Data Area. o Fix to IWSSPAR used in INSTALL and IWSSAU to MODIFY IWSCORE INTERNAL FPC. IWSSAU would cancel in IWSCORE versions 1.70.10-1.70.14. The following corrections are provided in Release 1.70.14 of IWSCORE: o In IWSSAU up to 32 Volumes can be displayed at any one time. Say there are 64 Volumes on the VS, when IWSSAU displays volumes 33-64 and the users attempts to process volume #33, e.g. PF(6) Recover Dir, the actual volume processed is #1. It appears IWSSAU incorrectly processes the volumes 32 modulo. Fixed. o The Selection of a volume on which to Install IWSCORE consumes an intolerable amount of time. This was observed on an RSF VS system and a NON-RSF VS system having 50-70 Volumes mounted. The INSTALL does a READVTOC for Locally Mounted Volumes only. However, only up to 64 Locally Mounted volumes can be processed. o Fix to IWSSAU 1.70.12 so IWSSAU can navigate subdirectories below the first level after the root o Fix to MSDOS Server so in NET START BASIC in Windows For WorkGroups 3.11 a DOS COPY or TYPE of a VS Redirected file will NOT get 'Access Denied'. The following corrections are provided in Release 1.70.12 of IWSCORE: o Fix to M2-22728; In WFWG 3.11/FileMgr the display of a VS IWSCORE redirected Drive was incomplete. The REFRESH option under the FileMgr Windows PullDown menu had to be selected to display the Redirected correctly. o The TREE CONNECT aka NET USE correctly returns smb wct, smb vww(0), smb vwv(1), and smb bcc if smb rcls and smb err is non-zero. o Fix to the Trailing Blanks bug observed in WFWG 3.11 FileMgr when attempting to COPY a file into an IWSCORE Redirected Drive when the Subdirectory name is less than 8 characters and/or less than 3 characters in the extension portion of the subdirectory pathname. o Fix to the '0' byte length for subdirectories bug in WFWG 3.11. This bug occurs only in WFWG 3.XX NET START FULL o Fix to the INVALID path DIALOG BOX MSG observed in WFWG 3.XX FileMgr when clicking on *.txt files NOTEPAD.EXE attempts to OPEN the redirected file with r/w/share format 0x80 which is invalid in IWSCORE. The fix is to return SMBERRFILENOTFOUND instead of SMBERRBADFRMAT. o Fix so IWSSAU Recovery functions correctly when the Redirected volume has more than 1510 libs/volume. The following correction is provided in Release 1.70.11 of IWSCORE: o The INSTALL program, a VS PROCEDURE Program file, would cancel attempting to install IWSCORE 1.70.10 on a VS that had NO PREVIOUS version of IWSCORE Installed. INSTALL of IWSCORE 1.70.00 did NOT have this problem. o Also, the version in IWSSAU is 1.70.11. There are NO other changes in IWSSAU. This was done for SUPPORT reasons. Running IWSSAU will reveal the current version of IWSCORE. The following enhancements and corrections are provided in Release 1.70.10 of IWSCORE: o The number of redirected resources (disks and/or printers) available through a single instance of LCXIWS has been increased from 64 to 256. o Corrected problem of LCXIWS crashing when performing logging with VS/LAN CONNECTION (M200022088). o Corrected problem of IWSLKMGR cancelling when VS/LAN CONNECTION clients performing redirected activity are logged off (M200022173). The following enhancements were provided in Release 1.70.00 of IWSCORE are included in this release: o The File Protection Class (FPC) of internal IWSCORE files can now be set by the system administrator either during the installation or by running IWSSAU. The FPC of internal files can be set to A-Z or blank. o Users can now only access MS-DOS redirected files and VS files accessed through the IWS APIs if they have user access rights to such files. Previous releases would grant access to these files if IWSCORE had program special access privileges to these files (even if the user did not have user access rights to the file). o IWSCORE now offers three configuration options for file access through the IWS APIs, and a fourth option that allows users to develop a program that grants access on a per-task basis. For compatibility with previous releases, this can be configured so unrestricted file access is allowed. These options are configured either during the installation or by running IWSSAU. o Users can now deny access to IWSCORE services and external program invocation on a per-task basis by writing User Extension Software. These options are configured either during the installation or by running IWSSAU. o Security logging can now log requests for access to files and services and whether the access was granted or denied. o (X)SMB tracing can now be turned on and off from the VS. Previously it could only be activated from the client PC. If activated from the VS, tracing occurs for all clients on all drivers (IWSPCLIS, IWSPCLAN, or IWSPCLOC) invoked after activation. o This release of IWSCORE allows the creation of install copies of IWSCORE with security defaults set by the system administrator. This is useful for central sites to set security defaults for remote sites, simplifying the installation at the remote sites (since remote administrators do not have to manually reset security defaults). The following options are available: - Use defaults with this release or defaults of a previously installed version of IWSCORE - File Access Security option of T (unrestricted), H (Higher of WP/WP PLUS and File System), W (WP/WP PLUS preferred over File System), or E (User Extension software determines which services are available) - IWSCORE service security option of All Services Available or User Extension software determined. - Run program access rights: All programs can run, No programs can run, User Extension determines which programs can run. - Set IWSCORE internal files FPC - Set Language option: English, Canadian, Dutch, German, Italian, Spanish, Swedish, World Languages. - Set network drivers installed (IWSPCLIS, IWSPCLAN, and/or IWSPCLOC). To make use of these options, edit the file INSTLCFG in library @IWSLIB@. Defaults not desired are commented out of the file by adding an asterisk to the first column of the line. Defaults desired are activated by removing the asterisk at the beginning of the line. o IWSSWSIO has been renamed as IWSPCLIS. A procedure called IWSSWSIO is included with IWSCORE for the convenience of customers calling IWSSWSIO from other procedures. IWSSWSIO now calls IWSPCLIS. o IWSCORE 1.70 does not support 802.3 Integrated Services or Open Server - VS. CHAPTER 4 RESTRICTIONS AND SPECIAL CONSIDERATIONS EXCEL 5.0 This is a MS EXCEL 5.0 problem. If the NOTIFY option is selected by User#2 and User#1 attempts to 'SAVE', User#2 may OWN the file before User#1 successfully SAVES and CLOSEs the file. (M2-23434) SECURITY IWSCORE, Release 1.70, contains new versions of the following software: - IWSPCLAN - IWSPCLOC These new versions must replace any previously installed versions of these programs in order to maintain security of IWSCORE, Release 1.70. IWSPCLAN, Release 2.20.00 and lower does not contain the IWSCORE security enhancements. IWSPCLOC, Release 1.00.01 and lower does not contain the IWSCORE security enhancements. In addition, the following software is no longer supported by IWSCORE and should be deleted from the VS system to ensure that security is maintained: - IWSSNETB - IWSOPENS INSTALLATION o The installer of IWSCORE must be a security administrator. o If you are installing Wang OFFICE for the first time or you will be upgrading from Wang OFFICE 1.60, you must install Wang OFFICE before installing IWSCORE. o Installation of IWSCORE in an RSF cluster: to prevent the deletion of IWSCORE software on other nodes of a Resource Sharing Facility (RSF) cluster, it is recommended that the RSF link be taken down before running the install program. The IWSCORE software should be installed on each node that requires IWSCORE services. The IWSCORE software does not support MS-DOS redirected files on remote volumes. CLOGON, therefore, is NOT SUPPORTED for installing IWSCORE. VS WANG OFFICE o VS WANG OFFICE, due to IWSCORE changes to internal control blocks, during some MSDOS Redirected File processing e.g. External Copy to MSDOS Redirected File and OFFICE LINK, will CORRUPT the Byte Range Locking Database, very likely impacting NEGATIVELY all PC Client applications that utilize Byte Range Locking . o The following modules(5) should be replaced in library = WOLIB on the volume where VS WANG OFFICE is installed. DOSADMIN, DOSINPUT, DOSMPORT, DOSOUTPT, DOSXPORT ONLY Versions 2.05.87.07 or greater ( up to 3.01.00.01 currently ) will support this fix. PREVIOUS VERSIONS are NOT SUPPORTED. Previous versions May Cancel with Error 0034 Reported by WV04 LINK-USER PROGRAM CONTAINS UNRESOLVED SSL REFERENCES. VSOS PATCHES for Byte Range Lock Synchronization The following is REQUIRED to ensure valid Byte Range Locking Synchronization especially for Microsoft Applications EXCEL 5.0, ACCESS 2.0, LOTUS 1-2-3, and other DOS and Windows Applications that require accurate multiple Byte Range Locking. o VSOS 7.50.03 (No Patches necessary) o VSOS 7.50.01 Patch RSDP0880 o VSOS 7.50.02 Patch RSDP0889 o VSOS 7.42.00 Patch RSDP0858 o OS versions 7.21.09, 7.32.XX, and 7.40.02 DO NOT SUPPORT the REQUIRED Byte Range Locking Synchronization. INTELLIGENT WORKSTATION SERVER o In order to add screen scrolling keys to the Select Function screen of the IWSSAU, the Create Directory function was changed from PF Key (5) to PF Key (10). o The IWSSAU Recovery function now recovers up to 1510 files per library and up to 1510 libraries per volume. The former recovery limits were 512 files per library and 512 libraries per volume. o RSF systems: there appears to be an OS related problem when trying to display DOS Directory contents on volumes located on Resource Shared Facility (RSF) clustered VS systems. The problem occurs when you do the following: execute a Show Directory of a DOS Directory located on a Remote volume. The directory entries display correctly. Then return to the Manage Volumes screen and select a Local volume. Execute a Show Directory of that DOS Directory. The message "No Entries in This Subdirectory" appears, even if there are file and directory entries in the @MSDOS@ file on that local volume. The IWSSAU crashes under these circumstances sporadically. There appears to be no problem when a Show Directory is executed on local volumes only. For this reason, Version 1.70.10 does NOT support redirected DOS volumes on REMOTE volumes of an RSF cluster. o The following message appears on the Create DOS Directory screen of the IWSSAU if a failure occurs during an attempt to create a DOS Directory: "An ERROR has occurred while attempting to CREATE DOS Directory File @MSDOS@." Possible causes for DOS Directory creation failure are: - The disk volume has been mounted as non-labelled. - The disk volume has been mounted in Protected or Exclusive mode. - The disk volume has bad blocks. - The disk volume has an unrecoverable VTOC error. - The disk drive has had its write-protect button pressed on. Memory is now dynamically allocated to store mounted volume and printer shortname information. The amount of memory that can be dynamically allocated is limited to the size of the User's Modifiable Data area. o Each intelligent workstation must have a minimum modifiable data area of 2816. A modifiable data area of 3300 is recommended for IWS-connected application users. o When using the IWS server on a WLOC communications link, a running IWSPCLIS task must be terminated and rerun if the intelligent workstation is powered off or workstation emulation restarted in any way. For example, if a printer hangs and you are required to power off the intelligent workstation, connections are refused when the workstation is rebooted, and it appears that the resource is unavailable. To clear this problem, terminate and restart the IWSPCLIS task. o Wang PC/APCs are not supported. o When @MSDOS@ files grow to the allowed extent limit, errors can occur. To avoid this, periodically back up volumes supporting @MSDOS@ files. o Maximum data transfer size (excluding header size) is 4 KB or 9 KB, depending on the workstation microcode and Wang NetBIOS version used. For PCLIS the @MCPCIWS microcode provides up to 9 Kb transfer. For LAN Connection up to 4 Kb Transfer. o The number of NetBIOS sessions per PC is limited by the network software in use on the PC. The number of sessions may be configured. For example, PCLIS 2.40 allows from 12 (default) to 255 sessions. Refer to your PC network software documentation for details. o When you are using third-party PC applications that are not network ready, the following special considerations apply: 1. If two applications are not using the shared mode, they may not have the same file open at the same time. For example, FCBOPEN mode prevents other users from opening the same file. 2. If a program residing on a network drive is run, and the program opens another file on the drive in exclusive mode, the program cannot be run by more than one user at the same time. 3. Programs that perform direct disk access (INT 13) cannot work against a network drive. 4. When copy-protected applications are copied to a network drive, they may not run at all. They may run only if a diskette is mounted on the PC, or they may run only when they are used on the PC used to install the application. 5. Different applications support different printer emulation modes. A shortname is associated with a logical printer device (for example, LPT2) via the NET USE command. The printer emulation mode of the shortname must match the type of printer that the application expects to find at that logical device. Two programs in different windows should not be allowed to print at the same time. If a program does not close a print request, you may have to exit from the program before the job can be queued on the VS. If you print several files on the same logical device (for example, LPT2), you must place a form-feed between consecutive files; otherwise, the files may be treated as a single file. 6. Some applications may not correctly calculate free space on large network drives (75-MB capacity or greater). For example, this is evident when an application reports that a drive has 135% free space. 7. Some applications do not send an EOF marker with print jobs. You can force an EOF by typing CTRL-ALT-*. Some of the third-party applications that these special considerations apply to are listed alphabetically in Table 4-1, along with the release number and special consideration that pertains to the application. Where applicable, the consideration numbers in the last column refer to the special considerations (1 through 7) listed in this section. Table 4-1. Special Considerations for Third-Party PC Applications Application Release Number Special Consideration Crosstalk XVI Not applicable This application is not network ready, since networks do not support modem pooling. dBase III Not applicable Consideration 5 DesqView 2.01 This application does not support redirected printing. Diagram-Master 5.02 Consideration 4 Displaywrite 4 Not applicable Considerations 1 and 2 Lotus 1-2-3 2.01 Considerations 4 and 7 WordStar 2000 Plus 2.0 Consideration 4 o IWSSAU can display only 1510 entries per directory. Anything beyond that is unreachable. However, from any client PC that can access the redirected drive all entries are accessible. o In earlier releases of IWSCORE, the BRIEF editor used the special character $ in the creating temporary filenames. The MS-DOS server did not correctly update the prologue in the VS file that served as the MS-DOS redirected file. Therefore, the file was not correctly recovered. This condition has been fixed. However, any MS-DOS redirected files that were edited with BRIEF before IWSCORE 1.60.00 have this corrupted prologue and cannot be recovered. To correct this, use the DOS copy command to copy all suspect files to another redirected file or use the DOS xcopy command to BACKUP from one shortname to another. o The following method is used to calculate the record length of the ASCII and EASCII emulation mode print spool files. The record length entered as part of the management screen of the IWSSAU utility is used to define the actual amount of ASCII data contained in the VS print file records created during redirection. The actual VS print file record length will be greater because of the other information (PCBs and other control bytes) contained in each record. Record lengths up to 999 may be used. o The print server will now reorganize and expand (if possible) its spool files to accommodate larger print jobs. o There is no provision for Recovering Subdirectories with special characters that were created prior to Release 1.65.15 of IWSCORE. o Subdirectories with Special Characters in only the name portion, and not in the extension will be stored in a Marker file without "###" appended to the VS library name. This is inconsistent with the VS file mapping of Redirected files, however, IWSSAU Recovery will RECOVER such subdirectories; for example, ### maps to VS Library.File $$000.425, whereas for consistency it should map to $$000###.425. o Subdirectories with Special Characters in the extension cannot be recovered in IWSSAU. IWSCORE 1.80.01 Restrictions and Special Considerations INSTALL o The INSTALL program will cancel when the current release is LESS than 1.65.15. The WORKAROUND is to copy the DATAEXCH file from library @IWSS@ to the current @IWSS@ library e.g. COPY IWSCORE 17015 VOL.@IWSS@.DATAEXCH to CURRENT IWSCORE VOL.@IWSS@, then run the INSTALL program. o If IWSSAU is used to modify the IWSCORE Internal File Protection Class (FPC) the Special Program Access Rights (SPAR) of all the Platform Drivers (IWSPCLIS, IWSPCLAN, IWSPCLOC, LCXIWS) are NOT correctly updated. The System Administrator must run SECURITY/VSSECURE to apply the appropriate SPARs. (M2-22012) o If SECURITY Logging is enabled, VS/LAN Connection invokes LCXIWS, and a System Administrator attempts to cancel the VS/LAN Connection task LCXREG, the VS may hang (M2-23388) o In Wang DPSW attempting to monitor the WPPLUS print queue may hang the PC. (M2-23448) o The IWSSAU PF(8) FIND key will position the entries beyond the desired/existing entry. (M2-23470) CHAPTER 5 MEDIA CONTENTS Library = @IWSLIB@ Protection Blocks File Version Class Allocated Description INSTALL 01.80.00 @ 53 Main installation procedure for IWSCORE PROCGEN 01.00.02 @ 61 Creates a procedure in the system library on the system volume to run a procedure located in another library INSTLCFG 01.80.00 @ 3 A procedure of defaults IWSPINST 00.00.01 @ 31 Locates the previous installation if any IWSRCFG 00.00.01 @ 33 Read the current configuration data IWSGSII 00.00.02 @ 39 Read or write the global structures and flags IFPCOFF 00.00.01 @ 33 Read the FPC for OFFICE if it is installed IFPCWPP 00.00.01 @ 33 Read the FPC for WP Plus if it is installed @VERSION 01.80.00 @ 1 Procedure containing the current IWSCORE release number TAPEREL 01.80.00 @ 4 Procedure to build a release tape IWSSPAR 00.00.01 @ 34 Updates SPARs for network drivers IWSMRKER 00.00.00 @ 41 Protects IWSCORE internal files PAUSE 06.00.03 $ 1 USERSUB utility to pause during execution FIND 07.30.10 $ 2 USERSUB utility to find files READVTOC 07.30.21 $ 4 VSSUB utility to find LOCAL VOLUMES Mounted. RENAME 06.00.03 $ 1 USERSUB utility to rename files EXTRACT 07.30.11 $ 2 USERSUB utility to extract system info IWSXVERS N/A @ 29 Determines previous IWSCORE version MANAGER 01.00.01 @ 329 VS File Manager Library = @IWSSUPT IWSPCLAN 02.21.00 blank 172 IWS Server for PCs connected by LANs via PC LAN/VS ACCESS IWSPCLOC 01.10.00 blank 219 IWS Server for PCs connected via VS Local Connection IWSPCLIS 01.80.00 @ 9 IWS server for PCs connected via PCLIS. Special Program Access Rights is WRITE (W) for FPC=Z (default). Library = IWSINC IWSACCH N/A blank 3 Include file for User Extension Software Library = IWSCSRC IWSUSRX N/A blank 4 Source code for User Extension Software Library = @IWSS@ IWSLKMGR 01.80.00 @ 33 Byte-range locking manager IWSSRVR 02.00.00 $ 399 Contains the file and catalog servers, MSDOS server, print server, DMPack server, and Alliance server; this is an SSL DATAEXCH 02.11.03 $ 230 Allows PC users to perform file exchange and file conversion with the VS; this is an SSL QLISRV 02.00.64 $ 449 PACE Query Language interface server; this is an SSL IWSSAU 01.80.00 @ 197 IWS System Resource Administration utility NETMAKE 01.80.00 @ 4 Program used for initial creation of @NETSHR@ file SAUFORM N/A $ 22 IWSSAU screen forms file IWSIMGSB 07.00.01 $ 2 LINKed to by the Print Server for VS multi-page image expansion IWSLOG 01.00.00 @ 5 The logging task OPERATOR 01.00.01 @ 7 Part of logging NOPORT 01.00.00 @ 7 Part of logging IWSNEWS 01.80.00 @ 3 News about this release of IWSCORE PCFORMAT 2.40.00 @ 5 Program for creating virtual disk files 4450DOS 1.00.00 @ 1 Virtual disk template 4450PART 1.00.00 @ 1 Virtual disk template SPARNEWS 01.80.00 @ 3 Procedure to display SPAR Update warning IWSACSSL Blank 7 SSL for User Extension Software Library = @ICEIW21 (International version of Data Exchange) ENGLISH 02.11.03US $ 230 Data Exchange for English, French, Swiss French, Canadian English CANADIAN 02.11.03CA $ 230 Data Exchange for Canadian French DUTCH 02.11.03NL $ 230 Data Exchange for Dutch GERMAN 02.11.03GE $ 230 Data Exchange for German, Swiss German ITALIAN 02.11.03IT $ 230 Data Exchange for Italian SPANISH 02.11.03SP $ 230 Data Exchange for Spanish SWEDISH 02.11.03SW $ 230 Data Exchange for Swedish WORLD 02.11.03WL $ 230 Data Exchange for World Languages Library = CSRNLIB (CSRN Library) CSRN 01.80.01 Blank 32 Customer S/W Release Notice Library = @PATCHS@ (VSOS patches) AUTOPAT 07.50.04 @ 9 WANG VS AUTOPATCH Program RSDP0889 Blank 2 VSOS 7.50.02 Patch RSDP0880 Blank 2 VSOS 7.50.01 Patch RSDP0858 Blank 2 VSOS 7.42.00 Patch Library = WANGOFFC (WANG OFFICE modules) DOSADMIN 03.01.01 @ 59 WANG OFFICE Overlay File DOSINPUT 03.01.01 @ 36 WANG OFFICE Overlay File DOSMPORT 03.01.01 @ 34 WANG OFFICE Overlay File DOSOUTPT 03.01.01 @ 23 WANG OFFICE Overlay File DOSXPORT 03.01.01 @ 101 WANG OFFICE Overlay File CHAPTER 6 OPERATIONS INFORMATION GENERAL OPERATION Follow these suggestions to increase system performance and capacity when using the Intelligent Workstation Server (IWSS) software: o IWSS is a large program. It is recommended that you use the POOLSTAT utility to set the page pool commitment ratio (memory commitment) to 400% (refer to the VS System Administration and Analysis Utilities Reference). You may want to adjust this number for your particular needs, based on system use, disk capacity, and so on. o Disk volumes that contain PC redirected files should be set so that at least 3 extents are allowed when opening a file and at least 13 extents are allowed per file (the higher this number, the better the performance). To set the extent limits, use the RELABEL function of the DISKINIT utility (refer to the VS Media, Transfer, and Device Utilities Reference). o @MSDOS@ files should be copied or reorganized frequently (via the COPY or BACKUP utility) if additions and deletions occur frequently. This improves system performance and consolidates file extents, allowing the @MSDOS@ and DOS files to grow. If many files are being added, a packing density of 25% may be needed; if few changes are expected, higher packing densities should be used. For information on the COPY utility and packing densities, refer to the VS Media, Transfer, and Device Utilities Reference. When specifying fields from the OUTPUT screen of the COPY utility, it is recommended that you increase the number of records by 20 to 100% to allow for increasing file size. o Before running IWSSAU to convert a virtual disk into MS-DOS server redirected format, verify that the disk is clean (not corrupted) by running the PC utility 'chkdsk' against it. IWSSAU does not convert corrupted virtual disks directly. o VTOC caching should be enabled if MS-DOS sharing is being used. The various IWS servers communicate the file size through FDR1 fields. The speed of IWS server communication can be increased if VTOC caching is allowed. o Drives with redirected files should set Tolerance = None for best performance. SETTING PROGRAM SPECIAL ACCESS RIGHTS o Set the Program Special Access Privileges for each of the network drivers by running the SECURITY utility and selecting PF9 (Set Program Special Access Privileges). Do this for IWSPCLIS, IWSPCLAN (if PC LAN/VS Access is installed), LCXIWS (if VS/LAN CONNECTION is installed) and IWSPCLOC (if VS Local Connection is installed). IWSCORE network drivers require Program Special Access Privileges to the WPPlus protection class in order to allow access to WPPlus documents to PC clients. o The system administrator must also manually apply Program Special Access Privileges to non-IWSCORE programs which need access to IWSCORE internal-data files. Wang OFFICE requires Program Special Access Privileges for IWSCORE's Protection Class in order to copy DOS files into a redirected drive. VS PACE can require similar access rights in order to output DOS-formatted query results. STARTING AND STOPPING IWSLKMGR o The IWSLKMGR should be a permanent background task. It should be cancelled before each IPL. When cancelling the IWSLKMGR, a menu will appear asking if you wish to create a dump, and if you want to resubmit the lock manager after the IPL. Enter NO for Provide DUMP, and YES for Restart at IPL. o The IWSLKMGR should always be displayed in the VS Procedure Queue. If it is deleted (which will happen if you change system volumes), you will need to resubmit it. From the Command Processor menu, select SUBMIT procedure. The next screen that appears is the Submit Procedure screen. Enter IWSLKMGR in the FILE field. Enter @SYSTEM@ in the LIBRARY field. Enter your system volume name in the VOLUME field. Enter R in the STATUS field. Enter Y in the PERM field, and N in the DUMP field. o IWSLKMGR should run with a minimum MDA of 1024KB. MOVING THE SYSTEM VOLUME o If you change system volumes, copy the @NETSHR@ file in the @MSDOS@ library from the old volume to the new. Do NOT copy the @MSDOS@ file in the @MSDOS@ library. CREATING IWSCORE VOLUMES o Whenever possible, the VTOC on volumes that will be used to store redirected files should be enlarged, as the average DOS file is much smaller than the average VS file. The VTOC is full when you get file creation errors from DOS and the volume still shows space available. To correct the problem, backup the volume, reset the VTOC size using DISKINIT, and restore the files. A VTOC that is approximately twice as big as the default supplied by DISKINIT is usually sufficient (approximately six blocks per megabyte of total disk capacity). LOGGING IWSCORE, Release 1.70 and greater, supports three separate logging features: o Security Logging. This service logs file and IWSCORE server access grantings and denials. It also logs the time when the User Extension takes control and when it returns control to IWSCORE. Security logging is set on a system wide basis. Activate Security Logging by performing the following procedures: a. Run SECURITY. b. Select PF4, Manage Event Logging. c. Select PF4, Select Events to be Logged. d. Change the values on System Logging to Y by pressing PF9, positioning the cursor, and pressing Y. e. Press ENTER to accept changes. f. Position the cursor to System Logging and press ENTER. g. Select PF9 to Modify values. h. Change the values on Application Logging to Y. i. Save the changes by pressing ENTER and exit SECURITY. j. Run IWSSAU. k. Select PF12 Manage Access. l. Position cursor next to IWSCORE Security Logging and change the value to Y by pressing PF5, Next Value. m. Press ENTER to accept changes. n. Exit IWSSAU. The system administrator determines the log file volume and library name. Security Logging is useful for security administrators who need to know which users are accessing or trying to access files. It also is useful in debugging User Extension software. If Security Logging is activated and the log file becomes full, all IWSCORE processing stops. The system administrator can then create a new log file by running SECURITY, pressing PF4 (Manage Event Logging), and pressing PF3 (Start New Log File). IWSCORE processing then continues. o FPC Logging. When the system administrator changes the File Protection Class of the IWSCORE internal files via either the install utility or the SAU, the successful or unsuccessful FPC change is logged on each volume in the @MSDOS@ library. The file name is MMDDHHMM, where MM is the month, DD is the day, HH is the hour, and MM is the minute. This log is useful for administrators keeping track of changes to the IWSCORE internal protection classes and can be used to verify that all files are successfully changed when updating the IWSCORE internal files protection classes. If system administrators change IWSCORE internal FPCs often, they should periodically delete FPC logging files in the @MSDOS@ library to save disk space. o (X)SMB Logging. This logging is used to debug NetBIOS communications between the client PC and the VS. With this release, (X)SMB logging can be turned on and off from the VS. When activated from the VS, all network drivers that start after activation will be logged. Previous releases could only be activated from the PC. When activated from the PC, only the specific client activated will be logged. See ROLogon and ROLogoff in the IWS API Toolkit Reference Manual for details. The log file is kept on the system volume in library IWSSLOG. The user id is used as the file name. If this file already exists, the new file overwrites it. VERIFYING DATA EXCHANGE TRANSLATION o To verify the language code of the Data Exchange translation table installed, display the installed file DATAEXCH and observe the two-character code following the version number. The codes correspond to the languages listed in Chapter 5. Each language file is renamed DATAEXCH when installed. ADDITIONAL PERFORMANCE SUGGESTIONS FOR REDIRECTED DISKS o Avoid the use of extensive batch files on redirected disks. DOS will open and close these files frequently, causing performance degradation. Whenever possible, copy and execute batch files from your local disk. o Place DOS-executable program overlays on local disks. Some DOS programs will page portions of themselves from overlay files. Program execution is faster when the overlay files are on a local rather than network disk. o File searching in the root directory is faster than in subdirectories. Performance will be better if heavily-accessed files are located in the root directory of a redirected disk. o For PCLIS use @MCPCIWS microcode for faster data transfer rates. This sacrifices MWS features (type ahead, multiple VS Windows, and so on) but provides faster data transfer. CHAPTER 7 INSTALLATION INSTRUCTIONS INSTALLATION OUTLINE VS Operating System(s) and Patches The following is REQUIRED to ensure valid Byte Range Locking Synchronization especially for Microsoft Applications EXCEL 5.0, ACCESS 2.0, LOTUS 1-2-3, and other DOS and Windows Applications that require accurate multiple Byte Range Locking. o VSOS 7.50.03 (No Patches necessary) o VSOS 7.50.01 Patch RSDP0880 o VSOS 7.50.02 Patch RSDP0889 o VSOS 7.42.00 Patch RSDP0858 o OS versions 7.21.09, 7.32.XX, and 7.40.02 DO NOT SUPPORT the REQUIRED Byte Range Locking Synchronization. See Chapter 5 MEDIA CONTENTS for files associated with VSOS and Patches for IWSCORE. ONLY a WANG Certified Representative should apply the patches described above. VS WANG OFFICE modules o VS WANG OFFICE, due to IWSCORE changes to internal control blocks, during some MSDOS Redirected File processing e.g. External Copy to MSDOS Redirected File and OFFICE LINK, will CORRUPT the Byte Range Locking Database, very likely impacting NEGATIVELY all PC Client applications that utilize Byte Range Locking. o The following modules(5) should be replaced in library = WOLIB on the volume where VS WANG OFFICE is installed. DOSADMIN, DOSINPUT, DOSMPORT, DOSOUTPT, DOSXPORT ONLY Versions 2.05.87.07 or greater ( up to 3.01.00.01 currently ) will support this fix. PREVIOUS VERSIONS are NOT SUPPORTED. Run BACKUP and BACKUP library = WANGOFFC to library = WOLIB on the volume where VS WANG OFFICE is installed, replacing the five modules. o The INSTALL program will cancel when the current release is LESS than 1.65.15. The WORKAROUND is to copy the DATAEXCH file from library @IWSS@ to the current @IWSS@ library e.g. COPY IWSCORE 17015 VOL.@IWSS@.DATAEXCH to CURRENT IWSCORE VOL.@IWSS@, then run the INSTALL program. You must have system administrator access rights to perform the installation procedure. IWSCORE software must be installed on the SYSTEM volume or a volume mounted SECURE. If you are installing PACE, OFFICE, Netcore, or Directory Services software, they must be installed before IWSCORE software. If you are installing IWSCORE over another IWSCORE, the IWSCORE libraries @IWSS@, @IWSCFG@, IWSINC, and IWSCSRC will be renamed to XIWSS@, XIWSCFG@, XWSINC, AND XWSCSRC. IWSCORE files in the @SYSTEM@ library (IWSLKMGR, IWSLOG, OPERATOR, NOPORT IWSPCLIS, IWSSWSIO, and IWSSAU) will also be renamed (as XWSLKMGR, XWSLOG, XPERATOR, XOPORT, XWSPCLIS, XWSSWSIO, and XWSSAU). Not all of these libraries and files will exist on all systems, some depend on what environment and what IWSCORE release is being replaced. If these "X" libraries and files already exist, the install procedure will ask if you want to delete them in order to continue with the installation. The security administrator can restore the previous version of IWSCORE by renaming the "X" libraries and files to their original names. If you are reinstalling, IWSCORE must not be in use and IWSLKMGR must be cancelled. Set the "Restart at IPL" field on the Operator Console Cancel Procedure screen to "NO." IWSLOG, OPERATOR, and NOPORT must also be cancelled. Use the following procedure to install IWS software: 1. If WSN and PC LAN/VS ACCESS are running, run WSNSTOP from the Run screen to shut down the network (refer to the WSN VS Network Control and Monitoring Guide). This step is not required for WLOC-only installations. 2. If your VS is connected via Resource Sharing Facility (RSF) to another VS with IWSCORE installed, you must detach from the other VS prior to installation. 3. If OPEN/server -VS is running, shut down server operations. If PC LAN/VS ACCESS is running, shut it down by running LANSTOP. If VS/Local Connection is running, shut it down by running LCNSTOP. If VS/LAN CONNECTION is running, shut it down by running LCXSTOP. 4. Restore the release media to a work disk by using the RESTORE option of BACKUP. 5. Run INSTALL in library @IWSLIB@ on the work volume. Change values in the highlighted (or underlined) field by pressing PF4 or PF5. Change the field highlighted by pressing PF6 or PF7. For convenience, the FPC may be typed in, if desired. When complete press PF9 to continue the install. If this is a reinstallation and a previous version has been already renamed as previously documented to "X" libraries and files then you will be asked to rename them or delete them by pressing PF8. After this step the installation must be started again by pressing PF9. 6. When the completion message appears, press PF16 to conclude the install. 7. Review the information provided at the end of the installation regarding Special Program Access Rights. If IWSCORE requires access to files from other programs (eg. WP Plus), the system administrator must manually add the proper FPC access rights to each installed network driver. Do this for IWSPCLIS, IWSPCLAN (if PC LAN/VS Access is installed), LCXIWS in LCXLIB (if VS/LAN CONNECTION is installed) and IWSPCLOC (if VS/Local Connection is installed). IWSCORE network drivers require Special Program Access Privileges to the WPPlus protection class in order to allow access to WP Plus documents to PC clients who do not have VS access rights to the WP Plus protection class. The system administrator must also manually apply Program Special Access Privileges to non-IWSCORE programs which need access to IWSCORE internal-data files. Wang OFFICE requires Special Program Access Privileges for IWSCORE's Protection Class in order to copy DOS files into a redirected drive. VS PACE can require similar access rights in order to output DOS-formatted query results. 8. If you shut down WSN in step 1, run WSNSTART from the Run screen to restart it. 9. If you shut down OPEN/server -VS to install IWSCORE, restart server operations now. If you shut down PC LAN/VS ACCESS to install IWSCORE, restart now by running LANSTART. If you shut down VS/Local Connection, restart it now by running LCNSTART. If you shut down VS/LAN CONNECTION, restart it now by running LCXSTART. Setting Custom Default Options This release of IWSCORE allows creation of install copies of IWSCORE with configuration defaults set by the system administrator. This is useful for central sites to set configuration defaults for remote sites, simplifying install at the remote sites (since remote administrators do not have to manually reset configuration defaults). The following options are available: Use defaults with this release or defaults of a previously installed version of IWSCORE File Access Security option of 1 (unrestricted), 2 (Higher of WP/WPPlus and File System), 3 (WP/WPPlus preferred over File System), or E (User Extension software determines which services are available). IWSCORE service security option of All Services Available or User Extension software determined. Run program access rights: All programs can run, No programs can run, User Extension determines which programs can run Set IWSCORE internal files FPC Set Language option: English, Canadian, Dutch, German, Italian, Spanish, Swedish, World Languages Set default network driver(s) installed (IWSPCLIS, IWSPCLAN, and/or IWSPCLOC To make use of these options, backup the release media to disk. Then edit the file INSTLCFG in library @IWSLIB@. Defaults not desired are commented out of the file by adding an asterisk to the first column of the line. Defaults desired are activated by removing the asterisk at the beginning of the line. Once the defaults are set as desired, run TAPEREL in library @IWSLIB@ to create a release tape with the new defaults.