D3 Service Pack 713 Upgrade Installation ==================== - Before selecting Install, make sure D3 is stopped.

- If upgrading a release older than 7.1.1.216: With the registry editor REGEDIT.EXE, open the key: HKEY_LOCAL_MACHINE\Software\PickSystems\D3 Select the key 7.1. Right click and select Rename. Rename the key to CurrentVersion. This must be done before D3 is restarted. - To have the option of uninstalling the service pack, check the Uninstall option. - Select Install. Note: If an incident occurs while registering the controls, see the the note at the end of this document. - After the installation is complete, select Close. Please read carefully any additional notes below.

Monitor Upgrade ================= There is no special step for this Service Pack. VME ABS Upgrade =============== There is no special step for this Service Pack. VME Data Set Upgrade ==================== The following steps should be done on all the VMEs on the network: - Start the VME. - Logon to the DM account. - Type (note the period '.' after the colon): copy dos:. nt_upgrade (o <ENTER> to: (md <ENTER> - Type: nt_upgrade <ENTER>

When prompted, type 'c', without a carriage return, twice, to continue. - At the end of the upgrade, the system logs you off. The system is then ready.

The Service Pack installation is complete.

Incident while registering controls =================================== If a problem occurs while registering the controls, manually run the batch file _PATCH.BAT which has been copied to the directory c:\Program Files\D3\D3programs (or the directory specified in the Destination edit box in the D3 Upgrade dialog).

This document contains short notes about significant changes in the most recent Service Packs. 7.1.2 ===== 1. Online File Resizing 2. FSI File Of Files 3. New FlashBASIC Compiler Option 4. DEV-MAKE PICKREMOTE Type 5. Converse Changes 6. Restoring Accounts to the FSI 7. Users File 8. TELNET Automatic Disconnect 9. MOVE-FILE, RENAME-FILE 10. Executing FlashBASIC from DOS 11. Full Restore and FILELOAD 12. D3 and Windows 95 13. SQL Accounts 14. Resizing Files from the D3 File Manager 15. TCL Access from DOS 16. Incremental Save Not Supported 17. Stopping and Restarting OSFI TCP Servers 7.1.3 ===== 18. TELNET Pibs Selection 19. Logging on in Single User Mode 20. FlashCONNECT Support 21. INPUTERR FlashBASIC Statement 22. Activation Code Changes 23. Power Saving Feature and Windows 98 24. Potential Upgrade Remote File System Error ====================================================================== 1. Online File Resizing

This section describes briefly the online FSI file resizing. Also,see Section 14 in this document about resizing files from the D3 File Manager. The resizing process works by extending the primary space of the file and re-hashing all items. While this process is running, access to the file may be slower, but the file is otherwise normally available. If the system is rebooted while files are being resized, the resizing process is restarted automatically by the servers. The resizing is done in background by system threads, running on the servers where the file is located. The current version has the following limitations which will be addressed in future releases: o The modulo of a file can only be increased. Note: If the modulo is not changed, the resizing does file compaction instead. o After resizing, the overflow space is not relinquished to the underlying host file system. The D3 File Manager will report lower overflow usage, but Explorer will still show the .D3O overflow spaces. o There is no command to stop the resizing. It is paused automatically when a sequential access is performed. o The d-pointer does not reflect the new modulo. The command nt_file-info will report the new modulo correctly. o The number of overflow frames reported by the D3 File Manager is actually the combination of the number of frames used by large items and the number of frames used by overflowing groups. It is therefore pessimistic. This version corrects this problem, but a full save of the FSI is required to correct these counters. It is not a critical problem, but it makes determining poorly sized files difficult. A new D3 File Manager option allows finding poorly sized files more accurately. The TCL commands to manage the resizing are: nt_resize: nt_list-resizing: nt_list-jobs: nt_file-info: nt_resize --------nt_resize -f {dict} file.spec -m modulo {-p prio} {-t} {-i} where: -f {dict} file.spec File to be resized. Specified as {account,}dict{,data}. -m modulo Start the resizing. List the files being resized. List the background system threads File information.

New file modulo, in decimal. -p prio Resize priority (LOWEST, LOW, NORMAL, HIGH, HIGHEST). (See Notes) -t Add traces to the Windows NT event log. -i Start the resizing in immediate mode (see Notes). Notes: o The account must be an FSI account. If 'account' is not specified, the command must be issued from an FSI account. o This version does not support reducing the modulo. o If the modulo is equal to the current modulo, the file is compacted, removing empty cells in the file. o Prefer specifying a priority option equal to NORMAL or maybe LOW. When started with a LOW option, resizing will take much longer, but will have no performance impact on the system. Specifying LOWEST would make it extremely slow. Avoid using HIGH and a fortiori, HIGHEST, since it will cripple the system. These options should be used only when the system can be dedicated to the resizing and no other activity will take place. o The option -i starts the resizing in immediate mode: the process issuing the command does the resizing. The resizing cannot be stopped. This command must be issued on the server on which the file is located, else it fails. This option should normally not be used. nt_list-resizing ---------------List the files being resized or which have been resized. The following information is displayed: File: File name

Server: The computer name where the file is located. This is the server on which the system thread doing the resizing is running. OldMod: Old modulo, in decimal. NewMod: New modulo, in decimal. CurGrp: Current group, in decimal, being rehashed. Date,Time: Time at which the resizing restarted. Note: This is not necessarily the time the resize command was issued. If the server was rebooted, this will be the time at which the system thread resumed resizing the file.

State: Displaya current state: Running, Paused, Done. The state is set to 'Paused' when a sequential access is attempted on the file. Resizing is paused whenever this type of access is done to prevent duplicates and missing items. After the sequential access is complete, the system thread resumes the resizing process within 5 minutes of the end of the sequential process. nt_list-jobs -----------This command lists the system threads running on the server since it was rebooted. The following information is displayed: Module: FlashBASIC module name being run.

ThreadId: System thread Id, in hexadecimal. Start: Internal system starting time.

Time/Pri: Either the elapsed time hh:mm:ss if the job is complete, or the priority it is currently running at. UserCpu: CPU usage in user mode, if the thread is still running. SysCpu: CPU usage in system mode, if the thread is still running.

====================================================================== 2. FSI File Of Files The FILE-SAVE TCL command now creates file statistics in the FSI:DM,FileOfFiles, file. They can be examined with the D3 File Manager or from TCL, by doing: sort FsiDm,FileOfFiles, by FileName (i Notes: o The (S) option is not necessary. The file statistics are built by every save, including ACCOUNT-SAVES and dummy SAVE, contrary to the VME file statistics. o The file statistics are also built by a restore operation. It is therefore not necessary to do a FILE-SAVE after a restore just to get the file statistics. o The FILE-SAVE operation now refreshes the 'estimated' count returned by the 'Count File' option in the D3 File Manager. Note: After a restore, the estimated count is wrong until the next save. This will be corrected in a future release. o If the FILE-SAVE utility is not run, there is a internal tool NT_MAKEFOF which will build the FileOfFiles. Make sure to run this utility as part of any custom backup procedure. o Currently, this file is never cleared. It may contain statistics for files no longer on the system. This file can be cleared at any time without affecting the system.

====================================================================== 3. New FlashBASIC Compiler Option The (G) option has been added to the FlashBASIC Compiler to produce object code which is stored as a DOS file with the extension '.D3F'. See later in this document about how to use these modules from DOS. ====================================================================== 4. DEV-MAKE PickRemote type A new DEV-MAKE type "-t PickRemote" has been added to support Pick Remote Output to another VME in general. The main purpose of the PickRemote device is to allow sharing dedicated printers across mutiple VMEs. Syntax: -----dev-make -t PickRemote -n <pib1> -a "<compname>,<pib2>,<delay>" where: <pib1> <compname> <pib2> <delay> pib number of the source machine remote VME computer name pib# of the master process on the remote machine connect timeout in milliseconds

Example: ------To send output listing from "computer1" to a printer that has been installed on "computer2", the following commands need to be executed: Computer 1 ---------1. dev-make -t PickRemote -n 5 -a "computer2,10,1000" 2. startptr 1,1,1,s5 (s 3. sp-assign f1 All listings assigned to form queue 1 will be directed to the printer "printername" installed on the remote machine "computer2" Computer 2 ---------1. dev-make -t NTPrinter -n 10 -a "printername" OR dev-make -t Serial -n 10 -a "com2,9600,8,1,n" 2. startptr 0,0,1,s10 (s Printer 0 is started as usual. ====================================================================== 5. Converse Changes Converse has been enhanced to store the pib number of the port being conversed to, in attribute 17 of the pibs file. This information will help track down the converse ports that have been logged off.

====================================================================== 6. Restoring Accounts to the FSI The option to restore accounts to the FSI has been changed from (F) to (R) (Problem 20508). ====================================================================== 7. Users File Starting with patch 0263 (build 0241), the users file *must* be a q-pointer to the 'FSI:DM,USERS,' file to be able to use Visual Basic or to compile from the D3 File Manager. This is required because these tools now update the users file automatically to create a user with a name identical to the Windows user name. The QS.UPD utility, which is run automatically when the VME is booted, transfers the USERS file to the FSI (unless it is a q-pointer to another file, specifically set by the system administrator). Note that the original USERS file is renamed to 'USERS.<datestamp>'. Where "datestamp" is the actual date. To disable this mechanism, rename the file USERS to USERS.VME, for example, and set the USERS item to be a q-pointer to "DM,USERS.VME,". However, this will prevent VB from logging on to the VME. The system also creates internal users as follows: - 'name$x$' where 'x' is a decimal number This user id is used by triggers when doing an EXECUTE for example. 'name' is the user id as found in the users file. - 'name_' This user id is used by client applications, like the file manager or Visual Basic, when logging on to the VME. 'name' is the Windows user name the application is currently logged on as. The password to these users is generated automatically and may be different from session to session. ====================================================================== 8. TELNET automatic disconnect This option allows an automatic disconnect of the TELNET session if the user does not log on within one minute. See the D3 Books On Line, 'TelnetDisc'. ====================================================================== 9. MOVE-FILE, RENAME-FILE Implemented MOVE-FILE from FSI files to FSI files and from VME files to VME files. Note that the MOVE-FILE from FSI files to VME files or from VME files to FSI files is not implemented. Moving an account is not implemented either. To move an account, use rename database from the File Manager.

RENAME-FILE allows renaming a file from an FSI file to an FSI file and a VME file to VME file. ====================================================================== 10. Executing FlashBASIC from DOS This version includes the capability of running a FlashBASIC module from DOS and to make an EXE from a FlashBASIC module. See the D3 Books On Line, 'Running FlashBASIC from DOS'. ====================================================================== 11. Full Restore and FILELOAD The VME service has an additional option, /FILELOAD, which erases all FSI files before doing a file restore. Without this option files in the FSI are not modified. After the /FILELOAD or file /RESTORE, the console remains active and can be used as the line 0. ====================================================================== 12. D3 and Windows 95 Because the D3 NT implementation stores its files inside the FAT file system on Windows 95, any unexpected Windows halt may cause significant damage to Windows files and therefore D3 data files. Also, due to a problem in Windows memory mapped files, a massive data update (like an account restore) may cause Windows 95 to hang and therefore cause data loss. These Windows 95 problems are not corrected on Windows 98. For these reasons, using Windows should be surrounded by adequate UPS, no non-Windows 95 certified cause Windows instability. Avoid etc.). 95 in a production environment precautions (regular backups, hardware or software which could using disk compression software,

The effect of another Windows 95 bug is that shutting down Windows does not shut down D3 properly. Always shutdown the D3 VME using the TCL command SHUTDOWN. It is preferable to use Windows NT Server or Workstation and its native file system, NTFS, which does not suffer from these limitations. ====================================================================== 13. SQL Accounts The NT_UPGRADE procedure moves the accounts SQL and SQLDEMO to the FSI, where it is safer. After moving the accounts, the old VME accounts are renamed SQL.VMEBAK and SQLDEMO.VMEBAK, respectively. Once it has been verified that the migration proceeded successfully, these old accounts can be safely removed. Note: The indexes in the SQL account are always rebuilt by the NT_UPGRADE procedure. Since these indexes are normally

small, this should not take too long. IMPORTANT: The SQL account should never be modified manually. For instance doing a SEL-RESTORE or ACCOUNT-RESTORE from an older tape, otherwise some SQL tables may become inaccessible. Also, because the SQL account is now in the FSI, restoring the VME from an old tape or from the original data set, will bring a SQL account inside the VME. If it becomes necessary to restore the VME in this manner, this VME SQL account must be deleted with DELETE-ACCOUNT and the utility QS.UPD must be re-run. ====================================================================== 14. Resizing Files from the D3 File Manager To find files that require resizing, select the Tables node in the database to be examined. Right-click, and then select the option Check Overflow File. The File Manager will examine all files in the database and display a list of color coded icons, where files marked yellow and red may need resizing. Click on a file to be resized. The property sheet of the file is shown. Select: o 'Hash' This option shows the current state of the file and allows it to test various hash values. Note that when examining large files, only a sample (10% if the file has a modulo larger than 10,000) is taken. This causes the hash test to return approximate results. After experimenting with various modulos, it may be necessary to set the sample size to 100% to get a more exact result of hash test. o 'Resize' This option allows the resizing to start. Notes: o The Properties sheet for any file can be accessed directly by right clicking on it and selecting Properties. o The modulo can be changed directly in the Properties sheet. o Even though the hash test dialog allows testing a non prime modulo, the resizing will always adjust to the highest closest prime number before starting the resizing. o If the resizing is already in progress, the 'Resize' dialog on the property sheet shows the current status only. ====================================================================== 15. TCL Access from DOS The command D3Tcl has been added to allow starting a Pick

'process' from the DOS command line. This tool can be used in batch files to perform operations in the VME. Note this command supersedes the D3Exec script which was mentioned in earlier betas. Note also that this command allows connecting to PIB 0. See the D3 Books On Line for more details about this command. The -U option allows logging on as a user other than the user the PC is currently logged on as. This version does not support commands like TANDEM to a D3Tcl process. Please note that this utility is still evolving and may change in future releases to address problems and missing functionality. ====================================================================== 16. Incremental Save Not Supported This version does not support the incremental save or restore of FSI accounts. Use only account saves or full saves. ====================================================================== 17. Stopping and Restarting OSFI TCP Servers When stopping the OSFI TCP servers with the NETWORK-SETUP TCL command, the servers are not stopped properly, preventing restarting them. Only a shutdown of D3 can clear the TCP/IP interface when this problem occurs. ====================================================================== 18. TELNET Pibs Selection The registry value TelnetPibs in the key Pick0 allows the user to define a valid range of PIBS to be used for TELNET, which will avoid conflicts with other PIB-required functions. See the D3 Books On Line for more details. ====================================================================== 19. Logging on in Single User Mode When in single user mode, it is now possible to allow certain users, based on the user id, to log on. Add the option 'S' to attribute 9 of the selected user items in the USERS file. This is useful to permit system administration while still preventing normal users from accessing the system. Note: DM, by default, does *not* have this option. It is the System Administrator's responsibility to add this option, if desired. ====================================================================== 20. FlashCONNECT Support This version now supports FlashCONNECT. Note: A special activation code is required.

====================================================================== 21. INPUTERR FlashBASIC Statement The INPUTERR FlashBASIC statement allows displaying a message box and soliciting user input from a Visual Basic rule module and a trigger. See the D3 Books On Line for more details. IMPORTANT: When running a FlashBASIC rule module through an ODBC connection, the rule module is executed on the *server*. Therefore, an INPUTERR will display the message box on the server, not on the client. Using a RPC connection, the rule module runs on the client and the message box is displayed on the client, as expected. ====================================================================== 22. Activation Code Changes Problem # 22633. Some systems with more than one network card or with a defective network card may experience a loss of activation code, forcing the user to reboot several times. When this situation occurs, this Service Pack will request a new activation code and take the problem into account. When such a system encounters this problem, the system reverts to single user mode (non activated). Do the following: o o o o Shutdown the D3 services. Start the D3 Activation application (in the D3 Utilities group). Contact Pick Systems to obtain a new activation code. Restart the D3 services.

The new activation should now be in place. On systems where the problem is known to occur, add the following value in the registry key before the first activation: Key -----------------------HKEY_LOCAL_MACHINE + Software + PickSystems + D3 + Activation Name Data ------------ ----------

Options0

"16"

====================================================================== 23. Power Saving feature and Windows 98 On some systems, when Windows 98 goes into power saving mode and shuts itself down, whether D3 is running or not, it will not be possible to start D3 again once Windows is reactivated. To correct this situation, it is necessary to shut down Windows 98 and restart it.

This problem does not occur on Windows NT. Note: There is no problem when the hard drives are powered down after being inactive for some time. The issue is with Windows 98 turning itself off. ====================================================================== 24. Potential Upgrade Remote File system error During the NT_UPGRADE procedure, it is possible to get an error *** Remote file system error *** while compiling some utilities in FSI:DM,BP, If this occurs, type Q to quit the upgrade. Back at TCL, do: clear-file dict fsi:dm,bp, compile fsi:dm,bp, (of and restart the NT_UPGRADE procedure. The error may also occur during a FILE-SAVE. If so, follow the same procedure, and then restart the FILE-SAVE.