═══ 1. Installation ═══ JBA Open ToolCASE Installation Installation of the JBA Open ToolCASE consistes of three stages: 1. Installation of the software onto the AS/400 via cartridge. 2. Installation of the Guidelines and Client/Server software onto the PC from the AS/400 via PC Support. 3. Configuration of Communications Manager and Guidelines to use the Client/Server Support facilities. These instructions assume at least an operating knowledge of AS/400 and PC commands and procedures. For example, the use of the cartridge drive on an AS/400 and the use of a diskette drive on a PC, as well as OS/400 and OS/2 commands which enable you to operate an AS/400 and a PC. Note: OS/400 version 2.2 or above and OS/2 version 2.1 or above are required to load this software. You must also ensure that you have loaded appropriate C++ compiler(s), OS/2 PC Support and Communications Manager or CM/2, and that you have started PC Support and have configured a shared folder drive on the AS/400 onto which the JBA Open ToolCASE shared folder will be restored. Select a topic below for more information:- o Installation on the AS/400 o Installation on the PC o Specifying the Translation Table ═══ 1.1. Installation on the AS/400 ═══ Installation on the AS/400 1. Sign onto the AS/400 as QSECOFR. 2. If you have previously installed the JBA Open ToolCASE library set on the AS/400 the following libraries may already exist on your machine: GUIDED1 GUIDEF1 GUIDEP1 Rename these libraries as follows: RNMOBJ OBJ(GUIDED1) OBJTYPE(*LIB) NEWOBJ(GUIDED1OLD) RNMOBJ OBJ(GUIDEF1) OBJTYPE(*LIB) NEWOBJ(GUIDEF1OLD) RNMOBJ OBJ(GUIDEP1) OBJTYPE(*LIB) NEWOBJ(GUIDEP1OLD) 3. If you have previously installed the JBA Open ToolCASE shared folder on the AS/400 then rename it as follows: RNMDLO DLO(GUI_INST.ALL) NEWDLO(GUI_INST.OLD) 4. Insert the supplied cartridge into your AS/400 tape drive. It is assumed throughout this document that the cartridge drive name is TAP01. If you are using a drive with a different name then substitute the name you are using. 5. Restore the JBA Open ToolCASE library set from the distribution cartridge with the following commands: RSTLIB SAVLIB(GUIDED1) DEV(TAP01) ENDOPT(*LEAVE) RSTLIB SAVLIB(GUIDEF1) DEV(TAP01) ENDOPT(*LEAVE) RSTLIB SAVLIB(GUIDEP1) DEV(TAP01) ENDOPT(*LEAVE) Check that all objects were restored for the library after each command. 6. Restore the JBA Open ToolCASE shared folder from the distribution cartridge with the following command: RSTDLO DLO(*ALL) SAVFLR(GUI_INST.ALL) DEV(TAP01) ENDOPT(*REWIND) NEWOBJ(*NEW) Check the resulting messages. The last message should say how many objects were restored. Note: There should be zero objects not installed. 7. To set up the library list on the AS/400 when PC sessions connect, the commands SETGUILIBL and RTVGUILIB must be available. To ensure that they are accessible, they should be copied to a library which is in all users library list. For example to duplicate the commands into QUSRSYS (which is part of QSYSLIBL), type the following: CRTDUPOBJ OBJ(SETGUILIBL) FROMLIB(GUIDEP1) OBJTYPE(*CMD) TOLIB(QUSRSYS) CRTDUPOBJ OBJ(RTVGUILIB) FROMLIB(GUIDEP1) OBJTYPE(*CMD) TOLIB(QUSRSYS) 8. If you have previously installed the Guidelines libaries, you can restore the host applications, library lists and authorisation codes by copying the appropriate files from the renamed files library as follows: CPYF FROMFILE(GUIDEF1OLD/CMP10) TOFILE(GUIDEF1/CMP10) MBROPT(*REPLACE) CPYF FROMFILE(GUIDEF1OLD/CMP11) TOFILE(GUIDEF1/CMP11) MBROPT(*REPLACE) CPYF FROMFILE(GUIDEF1OLD/CMP12) TOFILE(GUIDEF1/CMP12) MBROPT(*REPLACE) CPYF FROMFILE(GUIDEF1OLD/CMP91) TOFILE(GUIDEF1/CMP91) MBROPT(*REPLACE) 9. If this is a new installation or additional AS/400 products have been installed, to enable the AS/400 communications programs to operate correctly, you must enter an authorisation code. Enter the command: GUIDEP1/SETGUIAUT and enter the authorisation codes provided by your software supplier and press Enter. ═══ 1.2. Installation on the PC ═══ Installation on the PC 1. If you have previously installed Guidelines on the PC then: a. Move all your .GUI files, and any other user files, from directory Guide and its subdirectories. You should also use this opportunity to back these files up. b. Move all your .H files, and any other user files, from directory Css and its subdirectories. c. Drop the Guide and Css directories into the shredder. Delete the Guidelines and JBA Open ToolCASE folders. Delete the Guidelines Template from the Templates folder. d. Delete all references to Guide and Css and their subdirectories in your Config.Sys and remove any environment variables set up by previous installations of Guidelines and/or Css. These include SET JBAxxxx=, SET GUE=, SET BINDPATH=, SET HOSTTYPE=, SET CSSXLAT=, SET CSSSYN=, SET CSSLOC=, SET CSSPROFILE=. More environment variables may be listed in ReadMe.1st 2. If installing Guidelines from floppy disks, insert disk 1 into the drive and in an OS/2 session on the PC, enter the following commands: a. A: (Change to floppy drive). b. INSTALL (This starts up the main Guidelines installation program). 3. If installing Guidelines from an AS/400 shared folder, in an OS/2 session on the PC, enter the following commands: a. I: (Change to PC support drive, PC support must be up and running). b. CD \GUI_INST.ALL (Shared folder restored from tape). c. INSTALL (This starts up the main Guidelines installation program). 4. The following window will be displayed: 5. Select the Directories item from the Install menu pull down. The following window will be displayed: The Install from path will default to the directory from which you have run the install program. Set the Install to path to the directory into which you want to install Guidelines. Do not leave the Install to path the same as the Install from path. Set the Install to path to D:\Guide (where D: is a drive of your choice). Press the OK button. If the specified Install to directory does not exist, you will be prompted to create it. Note: This is the ONLY time that the Install to path is used. DO NOT use it to specify the Install to directories when installing extensions. It is explained below how to do this. 6. Select the Install Guidelines item from the Install menu pull down. The following window will be displayed: In this window you can customize your installation. Unless you need to conserve disk space, accept the defaults. If your disk space is at a premium, you can choose not to install support for certain PC platforms and compilers. The installer can be instructed to ignore any sample applications and/or documentation. You may also select to install either the Guidelines design-time support, or the run-time support, or both. However, note that if you disable both of these options, Guidelines will be unusable! 7. Make your selections and press the OK button. The following window will be displayed: In this window you can specify which drives the install program will search for C++ compilers and tools. By default, all the local hard disk drives will be selected. You can select additional drives to search, such as non-local drives, or deselect drives which you know do not contain any compilers. Note: Selecting potentially large drives such as a network drive or a CD-ROM drive could cause the search portion of the install process to take considerably longer than usual. 8. Make your selections and press the OK button. The following window will be displayed: If your name and company are displayed and your registration number has not changed since the previous instalation, there is no need to re enter the registration number. Else, enter the registration number (obtained from Agent Support) and your name and company. 9. Press the OK button. to start the install process. During this the following window will be displayed which indicates the progress of the installation: If installing from floppy disks, insert disks as requested. After the installation has completed, a message will be displayed advising you that Guidelines was installed successfully. Note: If you intend to continue on with these instructions, it is not necessary to re-boot the PC as suggested. 10. If installing Extension Packs from floppy disks, only one pack can be installed at a time. Insert an Extension Pack disk 1 and follow the procedure for installing from a shared folder, inserting floppy disks as requested. Repeat this process for each Extension Pack to be installed. Note that there is no need to reboot until all packs have been installed. 11. Select the Install Extensions option from the Install menu pull down. The following window will be displayed which contains a list of all the packs found in the Install from directory: By default all the found packs will be selected for installation. The target paths at the bottom of the dialog default to Guide and Css on the boot drive. Change the drives if required, accept these directories and press the OK button. If the Css directory does not exist, you will be prompted to create it. You will be presented with the window which allows you to customize the installation, followed by the registration number window. Note: There is no need to re-enter the registration number again, even if the entry field is empty. It will default to the number entered when installing the Guidelines base product. 12. When all the packs have been installed, select the Exit option from the Install menu pull down. 13. The installation is now complete, shut down OS/2 and reboot the PC. The Guidelines desktop folder will allow you to start up Guidelines, run the Install program (for installing new packs) access sample GUIs and executables, gain access to help text and view installed products and their versions. Startup Guidelines. If the Css directory is not on the boot drive, you will initially receive error messages to the effect that some Css header files have not been found. To overcome this, select the Environment option from the Output menu, and for each compiler that you intend to use, select Edit then Paths. A window similar to that shown below will be displayed: Do the following: For OS/2 platforms, either:- Click the Use Config.Sys checkbox so that it is checked. or:- 1. Modify the INCLUDE statement D:\Css\Inc, plus any other paths where application database or Guidelines DLL header files occur. 2. Modify the LIB statement to include D:\Css\OS2\Lib, plus any other paths where user library or Guidelines DLL library files occur. Note: D:\Css is the drive and directory into which you installed the Client/Server Support packs. For Windows platforms:- 1. Modify the INCLUDE statement to include D:\Css\Inc, plus any other paths where application database or Guidelines DLL header files occur. 2. Modify the LIB statement to include D:\Css\Win\Lib, plus any other paths where user library or Guidelines DLL library files occur. Note: D:\Css is the drive and directory into which you installed the Client/Server Support packs. Exit Guidelines, electing to Save Settings. Note: When you next start Guidelines, all the header files should be found successfully. Existing users will need to re enter server and database definitions using the Css Configuration Utility in the JBA Open ToolCASE folder. Before attempting to use any Client/Server functions to access an AS/400 check: 1. You have configured your local Css configuration files using the Css configuration utility. 2. The Workstation Profile has the translation table entry filename specified as JBAGTAB.DAT, and this file exists in your Communications Manager directory. See Specifying the Translation Table 3. You can start up a 5250 workstation session and log in with a valid username and password. ═══ 1.3. Specifying the Translation Table ═══ Specifying the Translation Table A new Communications Manager translation table must be set up, and the Communications Manager configuration must be changed to refer to it. These changes only need to be done once for any one Communications Manager configuration file, and may have been made when Communications Manager was set up. If you are not sure, follow these instructions to make the changes: 1. Open an OS/2 window or full-screen session. In the following commands, C:\CMLIB is assumed to be path that Communications Manager was installed to. If Communications Manager was installed to a different drive or directory, substitute that name instead. Enter the following command: DIR C:\CMLIB\JBAGTAB.DAT If the file was found, skip the next step. If not, enter the following command: COPY d:\css\DATA\JBAGTAB.DAT C:\CMLIB\JBAGTAB.DAT Where d:\css is the drive and directory into which you installed Client/Server Support. 2. For Communications Manager Version 1 a. From the Communication Manager Main Menu, press F10 and select Advanced from the menu bar. b. Select option 4 Configuration and press Enter to confirm the name of the configuration file you wish to modify. c. Select option 1 Workstation Profile and then select option 2 Change to change the profile. d. The workstation profile details are displayed. Ensure that the Translation Table option is specified as JBAGTAB.DAT. e. Press Enter four times to save the changes. Press F10 and select option 1 Run Verify from the Verify menu to verify your changes. The verification should complete without error. If errors do occur, consult your network administrator or your software supplier. The changes to Communications Manager 1 are now complete. 3. For Communications Manager Version 2 (CM/2) a. Open the Communications Manager/2 folder and double-click on the Communications Manager Setup icon. b. Press OK then Setup. c. Select the configuration file you wish to change from the right-hand list box and press OK d. Select Change Workstation Information... from the Options menu. e. Enter JBAGTAB.DAT into the field labelled ASCII/EBCDIC translation table file name and press OK f. Press Close and then answer Yes to the question 'Would you like to dynamically update your SNA resources?' g. Press Close The changes to Communications Manager 2 are now complete.