Pre- installation Notes

• This doc covers a virgin 7.4.7 D3 Install and also covers a D3 upgrade from 7.2.1 to 7.4.7
• If this is an upgrade or re-install on an existing system do not touch D3 folder. All the data is there.
• When upgrading D3 on a multiple location install, ALL locations must be using the same version of software (in other words, all 7.2.1 or all 7.4.7).
• Before starting on any machine, get a list of existing accounts (LF MDS on a reload, or look it up in U CUST.PM on a new install) to determine if the customer is distributed.  Basically, if there is a PM.DIST account on the machine in question, it is distributed and PM.DIST will need to be loaded.
• Make sure you have a known working system with the latest Service Pack loaded, which boots up with no errors. TCP/IP and a NIC are also necessary. If there is no physical adapter installed, the MS Loopback Adapter can be used instead as a virtual adapter.
• Close all applications before proceeding.
• Check available disk space (Enough for programs as well as data. D3 = 1000 MB bare minimum)

Operating System Requirements

Non-certified environments cannot be supported and should not be installed in end-user environments.

* D3 NT 7.4 is certified for usage in these environments

• As a server over Windows 2000 Pro, Server and Advanced Server with SP 4, Windows XP Pro 1a,

and Windows Server 2003 Enterprise, Standard, and Web editions recommended.

• As a client over Windows 2000 and Windows XP Professional.

*D3 NT 7.4 is not certified for usage in these environments

• As a server in conjunction with .NET Enterprise Server technologies.

• As a server over Windows 95, Windows 98, or Windows ME, Windows NT Server 4.0, Windows 2000 Datacenter Server, or Windows 2003 Datacenter Edition.

• As a client over Windows 95, 98, Windows ME, Windows NT Server 4.0, or Windows XP Home.

Before Upgrading

NOTE— You must have administrative privileges to complete an installation or upgrade. Log on to the system as ADMINISTRATOR or as a user with administrative privileges.

WARNING— Starting with rel 7.4, the frame size changed from 2 KB to 4 KB. (7.2 is 2KB) Before uninstalling any previous releases of D3 NT, you must do a file-save because you will need to do a restore-accounts. For example, if you are upgrading from a system with a 2 KB frame size, like D3 7.2.1 to D3 7.4, you would enter restore-accounts (fxxxx, where xxxx is the frame size of the file-save.

When selecting a device to do the file-save to, do not select device 1 (device 1 is a reserved device).

• Third-party products that use assembly code must be updated if you are coming from a D3 7.3 or earlier

release because of the frame size change and the new virtual assembler using VC 6.0.

NOTE— (For 7.2.1 and later with service packs only.) Features that are not installed in your copy of D3 NT 7.2.1 or later, will not be installed by this upgrade.

1. In PM at a TCL prompt, do a SYSFILES (S ONLY if this is an Upgrade. This backs up pibs, user-coldstart, users, and mds entries.

2.  Perform a file-save.

3. Shut down the D3VME.

Making a pm.programs file

NOTE: Standard Procedure is to cut the pm.programs file on the local machine at TECHNTW.

**BETA Sites will be cut from Perf2k. This is not the norm. You should clear it through Steve for each install. Perf-NT is his development server, and he may be in the middle of something

At TECNNTW  in Tech room, log to an AccuTerm session on the local  config, then go to the TCL prompt in PS.

NOTE: It is normal to get a message of:  Not supported on this implementation.  It is not an error, but a statement that PS is not completely supported in ths instance

1. Type T-SELECT and choose     Pseudo Floppy  …   d:\saves\pmprograms.upg    ( it should be # 6 )
2. Type T-REW and then MAKE.UPGRADE.TAPE.
3. Enter the customer number and check to make sure that the customer information is correct. If the customer information does not appear then you will have to enter it into PERF #1 (steps 5– 13) and then start back on step  # 1. If the customer information is there and correct , then CTRL X then F, then skip to step 14.

NOTE: When editing U CUST PM, On NEW customers, You will enter the info. On Add-Ons, You can enter it, but show the results to Steve. If there is anything unclear, show Steve.

4. To enter in a new customer, log into a terminal, in the PS account at the TCL prompt type: U  CUST.PM  (I.
5. Enter in the customer number.
6. Enter down to SW Sup and type: Y. In Upgrade type Y.
7. Enter in floppy type: 3.5,  and the type of tape drive: If TAND.SLR5 use SLR5. If HP use 4MM-DDS3
8. For Loclist enter in 1  if one loc on a new install. ( Some older customers are using a non-standard loc # from when they were sold in the past. In this case leave the loc # as it is. )
9. Enter the total number of users.
10. If this is an upgrade or add-on there will be a PERF.MANAGEMENT line there already.

In this case, leave the existing row(s) and Control-V to add a row, then enter the number of add on users in the number of users space in that new row.

The total for all rows should be the amount of total users. The last row needs to have a D3 entry in it.

11. If this is a new customer, enter in PERF.MANAGEMENT, EACH (for unit), number of users, D3 (for d3), A (for active), and today’s date.
12. Press CTRL X then F.     Then press Enter
13. Enter C to make the tape. At end it asks to type I for Invoice. Press enter instead
14. Enter OFF to log off
15. In Windows Explorer, Copy D:\Saves\pmprograms.upg,  paste it to \\TEK2K\C:\pmprog CD image folder

Cut the PM.DIST upgrade (optional – only if Distributed)

AT PER2K, log to PM.DIST account

TCL <enter>

T-SELECT

Choose c:\saves\pmdist.as ( it should be # 7 )

T-REW

ACCOUNT-SAVE PM.DIST

After it finishes, enter T-DET

Burning a pm.programs CD

** NOTE: When cutting a CD for a Distributed customer, all locations must be upgraded to the same version number, all at the same time. This will help avoid incompatibilities between versions.

1. At TEK2K  in Tech room, insert a blank CDR disk into drive D and load it into drive.

Start > Burn CD and DVD’s with Roxio. Roll the mouse over Data Cd and choose Format CD. Enter a descriptive name that is less than 9 characters. Press Okay to confirm CD is farmatted.

2. Open Windows Explorer and drag and drop contents of PM Programs CD image folder to drive D. When finished copying, right lick on D: and choose Eject. Choose the option to read in any CD drive.

Uninstalling D3 NT

WARNING— Before uninstalling any D3 NT 7.2.1 and later, you must perform a file-save because you will need to do a restore-accounts. When selecting a device to do the file-save to, do not select device 1 (device 1 is a reserved device).

Verify that a file-save has been completed. It is recommended that you uninstall any D3 NT 7.2.1 and later before installing D3 NT 7.4.

? To uninstall a previous version of D3 NT Server

1. Select Administrative Tools, then Services from the Control Panel.

2. Select D3 ODBC Server, if installed, and any other application(s) using D3, then select Action > Stop from the Services menu. Also stop the D3VME.

3. Open a command prompt and navigate to the location where D3 NT is installed (the default path is Program files\D3\D3Programs).

4. Remove the VME. Type: D3vme /remove.

5. Remove the ODBC (if installed). Type: D3odbcsv /remove.

6. Select Add/Remove Programs from the Control Panel.

7. Select D3 7.4 Patch, then click Remove.

8. Select D3 7.4 Server, and click Remove. Click Next, check Remove and Next.

9. (This step only for 7.2.1 or later) Select  Standard option to remove the D3 NT program, but not the data files.

(VME data is removed, but not the FSI.)

10. Click Remove, then respond to the prompts accordingly.

11. Start > Run > REGEDT32 >  HKEY-LOCAL MACHINE, Software, and delete the Raining Data folder.

12. Close all applets, empty the Recycle Bin, and reboot before trying to reinstall.

About Installing D3 NT 7.4 as Server vs. Client

D3 NT can be installed as Server or Client. Both Server and Client offer Typical and Custom installations.

• Server—This is suitable for a single system using a VME for backward compatible applications, an FSI server, Visual Basic, ODBC, or COM compliant applications.

• Client—Installs a workstation that acts exclusively as a client (D3 File Manager or RPC application). This option is not necessary for ODBC applications. Client install is at the bottom of this document

Installing the D3 NT Server

Installing D3 NT Server as a standalone server is the same as installing it as a peer to peer server. The default folder location for the D3 NT Server is C:\Program Files\D3\ and includes these folders:

• D3Programs • D3Virtual • D3Database • D3Help

NOTE: You will need administrative privileges to complete an installation or upgrade.

     Log on to the system as ADMINISTRATOR or as a user with administrative privileges.

To start installing

1. Insert the PM Programs CD,  D3 Installation will not auto run.

       Start > Run > D:\D3NT 74\Releases\740S.exe

2. Enter the password of 5n3l2k

3. If this is an upgrade, a warning message will display on upgrading to a new version, and that all data will be lost. Click Yes if you want to continue.

4. Read the license agreement, select the I accept option, then click Next.

To set the D3 NT Server and D3Database directories

1.  Install using the default folders for D3 Server and the D3Database. Click Next.

2. Select Typical for server installation setup type

3. Select Automatic StartUp so the VME will start when Windows is restarted.

4. NOTE: This step is very important!        Set Log On As options to This Account and user name to Administrator, with a password of perf, then click Next.

6. Confirm the settings, then click Install. After installing new files, you will be prompted to activate system.

Activating D3 NT 7.4 1. Click OK. In the D3NT 7.4.0 Activation dialog box enter the SID. Enter your 8-digit System ID and click Apply.Two 8 digit Magic Numbers are displayed. Contact Raining Data Customer Support via their web page or telephone to obtain activation codes.

2. Enter the activation codes in User Activation and Server Activation text boxes and verify your information.

3. Right click desktop, New > Shortcut, command line is CMD, Next, change name to CMD, Finish. Right click on CMD icon, Properties, click on Shortcut tab, change Start in: to: “c:\program files\d3\d3programs”

( “ marks are needed ), click Apply, then OK

4. Click Activate and click Finish. The installation procedure continues.

NOTE: The activation will likely fail because of an incorrect login username or password here, but could possibly fail because of incorrect magic numbers, and possibly many other reasons.

   If the activation is completed, please move to the next section.

   If the activation fails, you may need to install the VME and ODBC manually, and set the password

Click on the CMD icon, then do a d3vme/install and a d3odbcsv/install

Open up SERVICES applet in Control Panel.

Right click D3 ODBC Server, Properties, on General tab, set Startup Type to Manual.

Right click D3VME, Properties.

On the Log On tab set This account to Administrator and enter perf into the password boxes.

On the General tab set Startup type to Automatic, click OK to close applet. Click OK at granted rights, and OK at the stop and restart service warning.

Install SP7 for D3 NT 7.4

1. Start > Run > Browse to D:\D3NT 74\Patches\747s.exe, accept the EULA, then click Install

2. Click OK after being prompted to activate system.

    NOTE: If this is a re-activation, you may need to restart the VME manually.

    Select Launch the Program to start the D3 File Manager.

3. Select the option(s) that you prefer from the list above, then click Finish.

Upgrading the VME Data Set

After upgrading to 7.4, the VME data set must be restored, otherwise proceed to Restoring Data Files.

To complete the upgrade

1. Start a Telnet session by selecting telnet localhost from the D3 NT menu.

2. Press any key for the logon prompt.

3. Log on to the dm account as the user dm.

4. At a TCL prompt:        copy dos:. nt_upgrade (o (Note the period (.) after the colon.)

                          to:(md

                        nt_upgrade

    This prompt displays: "In order to complete this upgrade, all other D3 processes must be

  logged off. Press ’C’ to continue with the upgrade, or any other key to stop:"

   Type: C   (no enter key)

  "Insert data files #1 and press ’c’"

   Type: C   (no enter key)

5. Log to DM, DM, then perform a shutdown on the VME, then Reboot the computer

6. Log to DM, DM. At  command prompt, do a WHICH CD.  The screen should say, among other things:

Boot Monitor. . . . . . . . 7.4.7.0391    03/06/06

Boot ABS. . . . . . . . . . . 7.4.7.A16    23 Feb 2006

Boot ABS Data File. . . 7.4.7.A16     23 Feb 2006

First 3 lines add up to:             423

Restoring Data Files  (not req’d on new install, our accounts are in the FSI, not the VME, so frame size is not an issue)

CAUTION—At least 16 MB of overflow should be available.

After upgrading to D3 NT 7.4, restore your data files from the device to which they were saved.

To restore your data files

1. Select the device where your data files were saved using the set-device command.

2. Restore the accounts with the restore-accounts (fxxxx command, where xxxx is the frame size of the file-save.

For example, if you are upgrading from a system with a 2 KB frame size, like D3 7.3.x, to D3 7.4 or later, enter: restore-accounts (f2000

3. Update the MDs with the update-md command. The data files are restored.

Setup VME tape devices, adjust phantom ports and VME size (optional)

NOTE: If there is a tape drive, ensure Windows drivers have been loaded.

If no tape drive, omit VME tape device setup.

1. Start > Programs > D3 7.4 > D3 Device Manager, click on VME Tape Devices tab
2. To the right,  the 4th line should say \\.\Tape0  4mm DAT 16KB label If it does, then skip to next  step. If it does not, then on the left you should see something that looks like this on the 4th line --        \\.\Tape0. Highlight this line.At the bottom of the screen select the appropriate tape density and        label size for your device (on SLR5 use ¼ SCT)  (for HP 4mm DDS-2   8gig use 4mm DAT,d) (on VXA drives use 8mm,v). Then to the right select the device number you want your tape device to be. Highlight first empty line ( in most cases 3 ) and click Add Tape, then click Exit
3. At a telnet prompt, type shutdown, Y, then X to close.
4. Start > Programs > D3 7.4 > D3 Device Manager, click on D3NT Settings tab.
5. Click on Increase total number of PIBs. Click Yes to accept that you must do a file restore.

If less than 10 users, set Number of PIBS to 100. If 10 or more users, set Number of PIBS to 160.

*Set Number of Phantoms to Total Number of Users Plus 6.

If less than 10 users, set VME Disk Size to 160, If more than 10 users, set VME Disk Size to 175 `

(NOTE: The upgrade process pushed this 175 up to 358.4).  Click Update, then Exit

Restore the VME

In PM at a TCL prompt, do a SYSFILES (S ONLY if this is an Upgrade. This backs up pibs, user-coldstart, users, and mds entries.

Shutdown the VME.

Click on CMD icon. This should leave you at a prompt at: X:\program files\d3\d3programs.

D3VME /RESTORE <enter>

Enter Y to proceed.

Take option 1 <Enter>

Press <Enter> twice.

N <enter> at Restore from incremental save tape, and N <enter> at Restore from Transaction log tape.

Once completed log to DM.

COPY   DOS:.   NT_UPGRADE (O <Enter>

TO:(MD

Type NT_UPGRADE <enter> and press <C> twice. ( Do not press <enter> with the C key here )

Once complete log back in to DM. Then do a shutdown., and restart the VME in Services.

Go back into PM at a TCL prompt, and do a SYSFILES (R ONLY if this is an Upgrade to restore the pibs, user-coldstart, users, and mds entries.

Create user-coldstart (optional - only necessary on a new install)

This is only necessary on a new install. Upgrades should already have a user-coldstart.

From the  DM account: U MD USER-COLDSTART to create user-coldstart.

Copy and paste from C:\tech\docs\user-coldstart.txt. Ctrl X, then F to file

NOTE:  The   ]   characters may not copy correctly. Double check them after creating user-coldstart.

Add PM as a user (optional - only necessary on a new install)

If not logged on, then logon as DM, DM. At the prompt: DELETE MD PM, then, U USERS PM

name PM

address

zip

phone

keys

password

privilege SYS2

option  d

macro term-type

010 sp-assign

011 brk-level

012 esc-data

013 set-sym gsym

014 speller-off

015 TO PM

Press CTRL X then F to file the item.

Edit USERS DM (optional - only necessary on a new install)

From DM, enter U USERS DM

Ctrl + U or <enter> down to option and insert the setting:    options  d

Press CTRL X then F to file the item.

Loading pm.programs file (optional - only necessary on a new install)

1. Put PM.PROGRAMS CD in new system,  open Windows Explorer. Click on CD drive to ensure file can be read.
2. Open an AccuTerm session in DM. At TCL prompt, type the following: ( this is assuming D is the CD drive )        dev-make –t tape –a “d:\pmprograms.upg,p”           and press enter
3. Enter T-SELECT,  choose the above mentioned device.
4. Next type T-REW then T-LOAD  MD  (O.  as in Overight
5. Then type UPGRADE.PM and press ENTER.
6. Enter SQL for account on the next screen unless PM account already exists. ( On virgin install , enter SQL )
7. Press ENTER at error messages about logon
8. Type OFF
9. Log on as DM, DM

Restore PM.DIST (optional – only necessary on a new Distributed install)

1. Enter T-SELECT and choose e:\pmdist.as
2. Type T-REW
3. Type ACCOUNT-RESTORE PM.DIST
4. Press < enter > at account name on tape
5. Enter N at restore from incremental save tape and restore from transactional log tape
6. Enter T-DET

Compile (optional)

NOTE: If perf upgrade was cut from PerfNT, you may have to compile.

If the upgrade originated from Steve’s beta machine, the upgrade may be for a higher Pick version than what is currently used in production.

1. Go to a TCL prompt.
2. TO PM.PROGRAMS      -          COMPILE.ALL
3. to PM, do a  BUILD.FILES          -    Log back into PM        -    PM.INDEXES   -   Choose A for ALL

Optional: for Distributed:     TO PM.DIST        -        COMPILE-CATALOG DIST.PGM                

CATALOG DIST.PGM * (G to Globally catalog these programs.    -        log off, then back on

Miscellaneous cleanup

1. After Data is loaded, in DM do a SYSFILES (S
2. Create a folder C:\saves
3. Make sure to copy the Sys Internals folder to C:\tech\.  Also be sure to copy SYNC.EXE to the root of the C:\ drive

NOTICE: do a CT MD SYNC   to view the sync command in PM. This will show where it is looking for SYNC. If there is no file, create one with U MD SYNC:

001 N

002 !C:/SYNC

003 !C:/TECH/SYSINTERNALS/SYNC

then ctrl X – F to file

4. In the DM account: Make sure the dev-make command (ex: dev-make –t tape –a “c:\saves\fs,p”) is created in the USER-COLDSTART
5. Create a shortcut on the desktop for command prompt to C:\Program Files\D3\D3PROGRAMS (Right click desktop, command line is CMD, save it, right click, properties, shortcut tab, start in: “c:\program files\d3\d3programs” [ “ marks are needed ] )
6. Create a shortcut to the D3TCL prompt (right click desktop, new, shortcut, browse to c:\program files\d3\d3programs\D3TCL).
7. This step cannot be done until after PM is loaded Open D3TCL, then do a TO FSI:PM, then FLUSH.SYNC.SLEEP. It should go through a flush, sync, then sleep.  Open another D3TCL, LU, then LOGOFF the user that is sleeping.

Do a shutdown on the VME and reboot. Sync will then come up in the user-coldstart

From PM, at TCL, do a SYNC to test

8. This step cannot be done until after data is loaded. In a new install the installer will do this onsite. Go to PM at the TCL prompt, enter: CT MD MAX

You should get back the amount of PM users

9. Setup the NT Backup using Windows 2003 Backup for D3 document

Troubleshooting

This section offers suggestions for possible problems installing D3.

This list is by no means complete. Please check other resources for help. See the Raining Data Web site

• If the VME will not start after a bombed activation,

     try running d3vme/install and d3odbcsv /install from a command prompt

• If D3 does not install properly, you may have to remove all existing exponents before installing again:

• In Services stop the VME
• At CMD prompt, cd c:\program files\d3\d3programs and do D3VME/REMOVE and D3ODBCSV/REMOVE
• Next, go into Control Panel under Add/Remove Programs and remove all references to D3
• Go into  Start, Run, REGEDT32, go into HKEY-LOCAL MACHINE, Software, and delete Pick Systems. Empty Recycle Bin.

• If this is a re-install on an existing system and you are having extreme difficulty, you may copy the C: or

     D:\Program Files\D3 folder to a different location. After copying the folder, install form scratch.

     Please do not delete this folder the D3 folder. All the data is there. 

     Finally, reboot before trying to reinstall

The rest of this document is optional

Connecting to the D3Database

Connect to the D3Database via the VME, D3 File Manager, or ODBC Client.

Connecting via the VME

Use Telnet to connect to the Virtual Machine Environment and run green screen applications. Select telnet localhost from the D3 NT menu.

Connecting via the D3 File Manager

The D3 File Manager provides a GUI application for viewing D3 files and starts automatically if you select Launch the Application at the end of the installation.

Connecting via ODBC Client

ODBC is installed separately and can also access D3 data.

To use ODBC, select ODBC from the VME Server options in the Custom Installation during Server setup. To use ODBC connectivity, install the D3 ODBC Client driver on the client system. Go to the Raining Data connectivity page at: http://www.rainingdata.com/products/connect/index.html

Navigate to the ODBC driver on the FTP site.

To review the documentation, go to: http://www.rainingdata.com/support/documentation/d3sup.html

NOTE— Ensure that D3 ODBC service has started.

Installing the D3 NT Client (optional)

The default folder location for the D3 NT Client is C:\Program Files\D3\.

To start installing D3 NT 7.4

1. Insert the D3 NT Installation CD into the CD-ROM drive. If AutoPlay is enabled, the D3 Installation dialog box displays. If AutoPlay is not enabled, do the following:

a. Select Start > Run from the Start menu. The Run dialog box displays.

b. Type D:\setup.exe (where D: is your CD-ROM drive) in the Open text box.

The D3 NT 7.4 Installation dialog box displays.

2. Select the Client installation. The InstallShield Wizard Displays.

3. Read the license agreement, select the I accept option, then click Next.

To set the D3 NT Client directory

1. Do one of the following:

• Install using the default directory for the D3 Client. Click Next.

• Change the default directory. Click Change to open the Change Current Destination Directory dialog box.

     Enter the destination directory, then click OK. Click Next.

2. Select a Client installation type: Typical or Custom.s.

NOTE— The D3 component run times have been tested with Visual Basic 6 and later.

    Visual Basic 5.0 is not recommended.

To perform a Typical Client installation

1. Select one of the following Setup options from the Client Setup dialog box:

• Domain (This is not used by default. This section is left here for the few customers in Domains)

    Select this option when the client obtains the location of the MDS Server through the Microsoft Location

    Name Service. Use this option only when the MDS Server has been configured in this manner and is

    located in the same Windows NT Domain.

• Peer to Peer

    Select this option if the MDS Server is installed in this mode or if you want to access the MDS Server

    directly. This option is best for configurations with a small number of clients. The network computer

     name of the MDS Server must be provided. The MDS Server can be another system installed

    using the D3 NT Server Setup.

2. Click Next.

3. Confirm the settings, then click Install.

NOTE— If server domain is required, use the D3 Device Manager on the D3 Server to update Network and MDS configuration to NT Domain.

To perform a Custom Client installation

1. Select the program features to install from the Custom Setup dialog box, then click Next.

    The Client Setup dialog box displays.

2. Select one of these Client Setup options:

• Domain (This is not used by default. This section is left here for the few customers in Domains)

     Select this option when the client obtains the location of the MDS Server through the Microsoft Location

     Name Service. Use this option only when the MDS Server has been configured in this manner and is

     located in the same Windows NT Domain.

• Peer to Peer

     Select this option if the MDS Server is installed in this mode or if you want to access the MDS Server

     directly. This option is best for configurations with a small number of clients.

    NOTE— Click Space to verify the disk space required and disk space available for the selected options.

    The network computer name of the MDS Server must be provided. The MDS Server can be another

    system installed using the D3 NT Server Setup.

3. Click Next.

4. Confirm the settings, then click Install.

    NOTE— • If server domain is required, use the D3 Device Manager on the D3 Server to update Network

    and MDS configuration to NT Domain.

• The D3 component run times have been tested with Visual Basic 6.0 and later.

     Visual Basic 5.0 is not recommended.