IBM VisualAge for COBOL

IBM VisualAge COBOL Enterprise for OS/2 V2.2 FixPak 1 Readme ------------------------------------------------------------ Welcome to IBM VisualAge COBOL Enterprise. Much of the information has changed since previous releases of VisualAge COBOL. For instance, we now provide an INSTALL.TXT file on the CD-ROM, which contains virtually all the information you will need to install the product. The information notebook, which is installed with the information component, now includes product highlight information - "What's New", a migration section for migrating from previous VisualAge COBOL offerings, and a trouble-shooting section for help in identifying and working around potential problems. It also includes online tutorials and other online documentation. VisualAge COBOL manuals are provided in Adobe Acrobat PDF form in the \PDF directory on the CDROM. You can print from the PDF files using either Adobe Acrobat Reader or Ghostview. The Adobe Acrobat Reader is provided in the PDF directory or you can download it from the Adobe web site. You can download Ghostview from the web at: http://www.cs.wics.edu/~ghost/index.html Viewing some information provided with this release requires an HTML browser. Netscape Navigator 2.02 dated 27 March 1997 is provided on the VisualAge COBOL CDROM in the \NETSCAPE directory. If you don't have a brower, or if your browser predates this version, install the copy from the CD. Thank you for choosing VisualAge COBOL Enterprise. If you have any questions, comments, or need assistance, the Getting Started manual has a list of phone numbers and addresses that will guide you to the appropriate department. APARs included in FixPak 1 (August 1998) ---------------------------------------- APAR IC21064: Invalid MOVE when overlapping MOVE with padding (PMR 46036) APAR IC21377: IDBUG shuts down displaying a variable from OO COBOL (PMR 30649,071,724) WORKING-STORAGE SECTION if inheriting from SOMClass APAR IC21280: DCZ_DATFLOW_LIMIT problem (PMR 45107,664,706) Version Notice -------------- Fifth Edition (August 1998) Information in this document applies to IBM VisualAge COBOL Enterprise Version 2.2 FixPak 1. =========================================================================== VisualAge COBOL Enterprise for OS/2 V2.2 Installation Notes =========================================================================== 1.0 Before You Install 2.0 Hints and Tips for Installing VisualAge COBOL 3.0 Trouble-Shooting for Installing VisualAge COBOL 4.0 Installing the Application Understanding Host JCL Scanner 5.0 Unattended Install 1.0 Before You Install ================== 1.1 To install the product: --------------------------- 1. Uninstall any previous versions of the product from the system. Important! If you have a previous release of VisualAge COBOL installed and have created projects on the desktop, move those projects into a folder on the desktop before uninstalling your current release of VisualAge COBOL. Projects left on the desktop will lose inheritance information, which may impact the ability to migrate them to VisualAge COBOL Version 2.2. 2. Insert the VisualAge for COBOL CD-ROM or access the LAN where the VisualAge COBOL image resides. 3. From the command line, change to the directory where the installation program is located (for the CD-ROM, it is the root directory). 4. For a basic installation, type: install from the command line. For a shared installation, enter: shrdinst from the command line. (If you're not sure which you should choose, read "Choosing Basic or Shared Installation" in the "Getting Started" (GC26-9051) manual. The main "VisualAge COBOL Installation" window and the "Instructions" window appear. 5. Follow the prompts to proceed with the installation. See section 2.0 "Hints and Tips for Installing VisualAge COBOL" in this file for more installation information. Some components require that other components get installed. When you select a certain component you may see others also selected. For example, the COBOL Editor requires WorkFrame. The installation utility automatically selects any other components required. Note: The "Update CONFIG.SYS" box directs the install program to automatically update your CONFIG.SYS file. A copy of your original unmodified CONFIG.SYS file is saved as the next unused file name in the ascending sequence of CONFIG.001, CONFIG.002, and so on. A higher number in the file name extention indicates a more recent copy. This box is checked by default. We recommend you leave this box checked to update CONFIG.SYS automatically. If you choose not to have the install program update your CONFIG.SYS, you must make the changes yourself before you run VisualAge COBOL. For the changes, see the CONFIG.ADD file in the same drive and path as CONFIG.SYS (this file is created by VisualAge COBOL following installation). 6. A message window tells you when the installation is complete. Shut down and restart your system to make the changes to your CONFIG.SYS file take effect. For information on hardware and software requirements, see "Hardware and Software Requirements" in the "Getting Started" manual. For more information on the product or to report problems, visit the following web site: http://www.software.ibm.com/ad/cobol 2.0 Hints and Tips for Installing VisualAge COBOL ================================================== The following is a list of items that you should be aware of during the install: 2.1) Be certain that the drive with your swapper file has enough space. The installation program could add 15MB to your swapper if your RAM is being used by other programs. 2.2) When transferring files to another computer, be aware that files for desktop objects (such as projects) have extended attributes, which are not supported on some file systems and file transfer utilities (for example: DOS, TCP/IP, PKZIP). Such files can be packed using EPFIPAK2 (which can be found in the directory \IBMCOBOL\CLIENTPK), transferred to the other computer and unpacked using EPFIUPK2 (which can be found in the directory \IBMCOBOL\CLIENTPK). 2.3) Using HPFS, you should not install VisualAge COBOL in a directory structure that has a blank as part of the directory name. For example: D:\VisualAge COBOL\PRODUCT The install itself works, however, some components do not run correctly. 2.4) If you do not install the full product, certain topics in the "Information Notebook" might not be available. 2.5) Determine if you need to place CONFIG.DFM in a directory: If you are using APPC for host/workstation communication, you must also install the SdU component. Remote E/C/D requires the CONFIG.DFM file (which VisualAge COBOL installs in the IBMCOBOL\SAMPLES\SDU directory). You need to copy the CONFIG.DFM file into the IBMCOBOL\MACROS directory. We suggest that you keep the original, unmodified version of CONFIG.DFM in the IBMCOBOL\SAMPLES\SDU directory for recovery purposes. 2.6) Update the COBLPATH4 environment variable in your CONFIG.SYS: If, before installing VisualAge COBOL, you had an LPATH or LPATH2 environment variable that pointed to private LPEX macros, then you need to append the contents of the LPATH or LPATH2 environment variable to the contents of the COBLPATH4 environment variable (which is created by VisualAge COBOL). For example, if LPATH or LPATH2 contained: D:\MYMACROS As a result of installing VisualAge COBOL assume the COBLPATH4 environment variable was set to: E:\IBMCOBOL\MACROS Then you should update the COBLPATH4 environment variable to: E:\IBMCOBOL\MACROS;D:\MYMACROS then your private macros that were in D:\MYMACROS are available. 2.7) If you are going to develop Object Oriented applications, you must install the Warp Toolkit development tools (to have SOM available). 2.8) The installation of VisualAge COBOL, by default, sets the LANG variable in your CONFIG.SYS to En_US. If, however, you already have the LANG variable set, the install does not attempt to change the LANG variable. 2.9) Product Incongruencies: The following products or components cannot co-exist on the same machine: - COBOL GUI Designer and VisualAge RPG - VisualAge COBOL and the workstation feature of CODE/370 (Remote Edit/Compile/Debug has equivalent function.) - Remote Edit/Compile/Debug and - CODE/400 - CODE/370 - VisualAge RPG Installation of VisualAge COBOL with products or components listed may result in failures of some functions in those products. 2.10) Remote E/C/D: The file MVSINFO.DAT, located in the MACROS directory, is deleted if you uninstall Remote E/C/D. This file contains user configuration information (like system name and userID) for Remote E/C/D. Copy MVSINFO.DAT to a user directory before uninstall so you do not lose your own configuration information. After a reinstall you can copy MVSINFO.DAT back to the MACROS directory. Note: There have been some minor changes to the MVSINFO.DAT file for the new release. An old MVSINFO.DAT file still works. You may choose to update the new MVSINFO.DAT file with the data from the old MVSINFO.DAT file. 2.11) SMARTdata UTILITIES: - Remote VSAM access to MVS alternate index files depends on the installation of two MVS DFSMS APARs: OW20884 and OW23571 (these APARs apply to DFSMS Version 1.4.0 and below). In addition, the DFM startup parameter MAX_CONV_LOCK in the DFM00 member of the MVS system parmlib should be set to the maximum number of 100. (The IEFPARM statement in the DFM procedure identifies the system parmlib.) - COBOL "Return Status = 02" when accessing remote MVS indexed files with alternate keys that allow duplicates depends on the installation of the MVS DFSMS APAR: OW26104 (this APAR applies to DFSMS Version 1.4.0 and below). This return status indicates an input-output statement was successfully executed but a duplicate key was detected. 2.12) Transaction Assistant: CICS Setup: To execute an application that contains code generated by Transaction Assistant requires the CICS Client to be installed. If both the CICS for OS/2 and the CICS Client are on the same machine, make sure that the CICS Client entries precede the CICS for OS/2 entries in the LIBPATH statement in CONFIG.SYS. 2.13) Only for LPEX on OS/2 Warp Version 4 with FixPak 5 applied: Under certain conditions when closing the last LPEX window, LPEX generates an exception. The exception occurs after LPEX has finished all critical processing, such as saving user data. If you are running with AUTOFAIL set to YES you probably will not be aware of the exception. If you are running with AUTOFAIL set to NO, a SYS3175 exception message box is displayed. AUTOFAIL is set in CONFIG.SYS. 3.0 Trouble-Shooting for Installing VisualAge COBOL ==================================================== 3.1 If Something Goes Wrong ---------------------------- This section describes what to do if you encounter a problem or an error when you run the install program. Online help is also available for error messages, both from the "Help" button on the message window, or from the index or contents of the online install help. Q: If you Get an Error Message A: Select the "Help" button for the error for information on how to correct it. Also note the message number and the file name where the error occurred, if one is indicated. If you cannot successfully complete the installation and have to call VisualAge COBOL Service and Support, this information may help identify your problem (see "Getting Support for Using VisualAge COBOL" in the "Getting Started" manual). Q: If You Select Stop A: If you select the "Stop" button on the Install progress window, the install program immediately stops and displays a window that asks if you want to back out of the installation so far. You cannot resume the install program from this point; you must end it and start again. In the confirmation window: - Select "Yes" to undo everything that the install program has done up to that point. We recommend you choose this option. Any desktop objects are deleted. - Select "No" to leave the files that have already been installed. Once the program has ended, you can restart it from the beginning. Q: If the Install Program Fails A: If the install program fails, it displays a window that asks if you want to back out of the installation: - Select "Yes" to undo everything that the install program has done up to that point. We recommend you choose this option. - Select "No" to leave the files that have already been installed. The most likely reason for the failure is that not enough disk space is available. To solve this problem: - Make more room on your target drive. - Choose a different target drive. - Select fewer components to install. If disk space is not a problem, run CHKDSK on the: - Drive where OS/2 is installed - Target drive to ensure there are no file system problems. If you are using a response file, make sure you specified responses for CFGUPDATE, DELETEBACKUP, FILE, SAVEBACKUP, and WORK, and at least one component name for COMP. If you do not give responses for these keywords, the install program may fail. Make sure that you specified the component names correctly. Also make sure that you specified the required command-line options as described in the "Unattended Install" section below, in "Installing Using Response Files". If you try the install program again with the response file, specify the command-line options: /L1:errorlog and /L2:historylog to create an error log and history log, respectively. Specify the path and file name for both. If the problem still occurs, these logs may help you determine the cause. If you have tried all of these suggestions and the install program still fails, contact VisualAge COBOL Service and Support (see "Getting Support for Using VisualAge COBOL" in the "Getting Started" manual). Q: If You Can't Delete an Object Because It's in Use A: When you delete a component, if any objects or files are in use, they are not deleted. A message informs you when this happens. The rest of the component and its desktop objects are deleted. After you shut down and restart your system, these objects should be deleted automatically. If they are not, run the delete action again. From an OS/2 command line, change to the directory containing the Compiler and Nonvisual Tools and type: epfinsts. If this fails, rename the subdirectory, shut down, and try to delete it again. Q: If VisualAge COBOL Doesn't Appear in the Installation Utility A: If you start the Installation Utility and VisualAge COBOL is not listed in the window, select "Installed Products" from the "View" menu to display it. Q: If You Can't Install Additional Components A: If you attempt to use the Installation Utility to install additional components and get an error of EPFIE114, you must select the drive where the install image resides. See step 2 in the "Reinstalling or Installing Components" section below, under "Method 2: Using the Installation Utility to Add or Delete Components". Q: If You've Tried Everything and It Still Doesn't Work A: If the install program continues to fail after you've tried everything suggested by the error message help and this section, contact VisualAge COBOL Service and Support (see "Getting Support for Using VisualAge COBOL" in the "Getting Started" manual). Be sure to inform them what error messages you see, and what file names,if any, are given in those messages. If you are using response files, tell them the contents of your error and history logs. 3.2 Reinstalling or Installing Components ------------------------------------------ To reinstall a component or the entire product, you must first delete the entire product. You can use one of three methods to add or delete components: 1. Run the original install program interactively (see "Method 1" below). 2. Use the Installation Utility icon from the main "VisualAge COBOL" window (see "Method 2" below). 3. Run the original install program with a response file. The steps for methods 1 and 2 are very similar, other than the initial interface. The steps for using a response file are described in the "Unattended Install" section below in "Adding or Deleting Components Using a Response File". Important: Before uninstalling Remote E/C/D, copy the file MVSINFO.DAT from the IBMCOBOL\MACROS directory into a separate user directory or diskette. When uninstalling Remote E/C/D, VisualAge COBOL deletes the MVSINFO.DAT file, which contains user customization information (such as the MVS system address and TSO userid). After you reinstall Remote E/C/D, copy the original MVSINFO.DAT file back into the IBMCOBOL\MACROS directory. Important Information for Shared Install! ----------------------------------------- If you are adding components, make sure you have access to the LAN directory where the VisualAge COBOL installation files reside. If not, VisualAge COBOL attempts to install on the drive where the local files from the shared install reside. VisualAge COBOL then issues an error message stating the drive is not ready. 3.2.1 Method 1: Using the Install Program to Add or Delete Components ---------------------------------------------------------------------- 1. Insert the VisualAge COBOL CD-ROM, or access the LAN where the VisualAge COBOL image resides. 2. From the command line, change to the directory where the installation program is located. (For the CD-ROM, it is the root directory; for the LAN directory name, ask your LAN administrator.) 3. On the command line: - For a basic installation, type: install - For a shared installation, type: shrdinst The main "VisualAge COBOL Installation" window and the "Instructions" window appear. 4. Select "Continue" in the Instructions window. The "Installation options" window appears showing the following options: - Update the currently installed components Do not use this option. It is provided to support corrective service (CSDs) for VisualAge COBOL. To reinstall a component, delete it first, then reinstall. - Delete the installed components and re-install Choose this option to delete the installed components, including their Desktop objects and entries in any .INI files. You can then reinstall them if you want. If you want to update components, but think you may have corrupted your Desktop objects or .INI entries, choose this option to delete the components entirely. Then reinstall them. 3.2.2 Method 2: Using the Installation Utility to Add or Delete ---------------------------------------------------------------- Components ---------- 1. From the task bar, select "VisualAge COBOL", then select the "Install/Uninstall Utility" icon. 2. To add components: a. From the "File" pull-down, select "Open Catalog". Select "Drive". The "Open drive catalog" window appears. In the "Drive" entry field, select the drive where the install image resides (CD-ROM or a LAN drive). In the "Filename" entry field, ensure that /IBMCOBOL.ICF is displayed. Click on "Open". b. From the "Action" pull-down, select "Install". 3.2.3 Updating Components for Corrective Service ------------------------------------------------- Once you have gone through the steps in "Reinstalling or Installing Components" above, and arrived at the Installation options window: 1. Choose "Update the currently installed components" and select "Continue". The Update window appears, displaying the product information. 2. When you've chosen the options you want, select "Update". For more trouble-shooting information, see the Product README file on the CD or click on the "Trouble-Shooting" button in the "Information Notebook". 4.0 Install the Application Understanding Host JCL Scanner =========================================================== If you want to use Application Understanding (AU) to scan JCL on a VSE host system, you need the VSE JCL Scanner, which will be available in the next release of VSE. The MVS JCL Scanner is shipped with VisualAge COBOL for OS/2. THESE HOST PARTS MUST BE MANUALLY UPLOADED TO MVS. These parts do not need to be uploaded to the host again once done successfully. The MVS subdirectory on the drive and under the main directory that you installed AU contains the following host parts: ARDV000.CLI Use this clist to submit the JCL scan FROM THE WORKSTATION. The Remote E/C/D component must be installed and setup to submit the JCL scans from the workstation. This sample clist must be modified for your installation and added as member ARDV000 to the userid.ARD.CLIST PDS, which must be available to the NFS transaction defined for VisualAge COBOL. The ARDV000.CLI datasets allocation (default) values are: Record Format=FB, Record Length=80, Block Size=6160, Primary Quantity=7, Secondary Quantity=24. ARDV000.JCL Use this JCL to run the JCL scan in batch on MVS. This sample JCL must be modified for your installation and added to a JCL PDS. The ARDV000.JCL datasets allocation (default) values are: Record Format=FB, Record Length=80, Block Size=6160, Primary Quantity=7, Secondary Quantity=24. ARDV00.LOD This file is a loadlib that has been unloaded into a sequential file using the MVS XMIT utility. It must be sent to your MVS system and transformed back into a loadlib. If you use the sample CLIST, ARDV000.CLI to run the JCL scan on MVS, the loadlib must then be made available to the NFS transaction defined for VisualAge COBOL. If you use the sample JCL, ARDV000.JCL, to submit the JCL scan on MVS, this loadlib must be available to the batch job running the JCL scan. You may want to use the batch job when scanning many JOBs (100s of members of a PDS) in a single run especially if your NFS transaction has a time limit measured in seconds. 4.1 Creating the ARDV000 LOADLIB --------------------------------- The steps to create ARDV000 LOADLIBs on your MVS system are: 1. On your MVS system Allocate a sequential file to receive ARDV000.LOD. This dataset has: Record Format=FB, Record Length=80, Block Size=3120, Space=250 blocks, Secondary Blocks=5. 2. On your workstation Send ARDV000.LOD to the file allocated on your MVS system. To do this, open a command window and position to the drive where ARDV000.LOD was installed by entering: d:, where "d" is the drive containing redevelopment tools. Then enter: cd ibmcobol\mvs This command makes MVS the current directory. Then enter: send ardv000.lod b:'userid.ardv000.lod' where: o send is the Communication Manager command o ardv000.lod is the part from the MVS directory o b: is your Communication Manager session for MVS o userid.ardv000.lod is the sequential dataset you allocated in step 1. 3. From your MVS system Create the loadlib from the sequential dataset. From the MVS ready prompt enter: receive indsn('userid.ardv000.lod') where: userid.ardv000.lod is the sequential dataset you allocated in step 1. At the prompt to enter the name to be used for loadlib, enter: dsn('<high-level-qualifiers>.ardv000.loadlib') The loadlib is allocated if it does not already exist and the sequential file is transformed into a loadlib and copied to it. If you wish to allocate the loadlib prior to issuing the receive, the attributes for a 3380 device are: Record Format=U, Record Length=0, Block Size =32760, Space=Tracks, Secondary=15 Tracks, Directory Blocks=10). 4.2 Allocating MVS Datasets ---------------------------- The following MVS datasets must be allocated before the JCL scan is run: Note: The value .yyyy used in the following instructions represents 0 or more qualifiers used in your MVS dataset names. CDIF PDS userid.yyyy.CDIF (VF, 255, 23476) Information extracted from the scanned JCL is placed in this dataset. The first time you run the Application Understanding JCL request you need to specify this PDS name. Size is determined by how many scans you wish to save. Each scan generates a member that can be several times larger than the JCL being scanned because the JCL is exploded to include the JCL from called PROCs.) Message Log PDS userid.yyyy.MSG (VB, 255, 23476) A list of the JCL member scanned and any error encountered during the scan is placed in this dataset. The first time you run the Application Understanding JCL Scan request you need to specify this PDS name. This is a relatively small PDS containing one member for each JCL scan that your run. ProcLib List userid.yyy.ARDLIB sequential data set (FB, 80, 3200) (1 track should be sufficient). If you are using the sample CLIST to run the JCL scan from the workstation, you must edit this dataset creating one line for each procedure library used by the JCL being scanned. The following is an example file: SYS1.ADPROC SYS1.PP.PROCLIB USERID.ABC.TESTPROC If you are using the sample JCL (found in ARDV000.JCL located in the directory \IBMCOBOL\MVS) to submit the JCL scan on MVS, you can EITHER: - Create one line for each proclib used (as described above) and provide the userid.yyy.ARDLIB data set name on the //ARDLIB DD statement in the sample JCL. - List the proclib data set names directly in the sample JCL on the //ARDLIB DD statement in the JCL. 5.0 Unattended Install ======================= This section describes the response file that you can tailor for unattended install, the different command-line options you can use and the values the install program returns. It also gives instructions on installing using Response files. 5.1 Response File Format and Parameters ---------------------------------------- The response file is a flat ASCII file that consists of a number of response lines and optional comment lines. Lines can be up to 255 bytes in length, and are separated by a new-line sequence. A comment line begins with an asterisk (*) or semi-colon (;). Response lines tell the install program how to install. Each response line has the format: keyword = response Keywords are not case sensitive. For the VisualAge COBOL install program, the keywords and the responses to specify for each are: __________________________________________________________________________ Keyword Response ------- -------- CFGUPDATE AUTO to automatically update CONFIG.SYS; MANUAL to not update CONFIG.SYS. If you choose not to update CONFIG.SYS automatically, you must update it yourself before you reboot (see the CONFIG.ADD file that VisualAge COBOL generates). The install program prompts you to confirm that this is what you want. COMP The name of a component to install. You must specify each component with its own COMP keyword. Note that many components require that other components be installed to work correctly. All the components are listed in UNATTEND.RSP; you can delete any you do not want. COPY The source and target files for a copy process outside of the install program. This parameter is useful if you are using an SDM to install VisualAge COBOL over a LAN, and you want to copy other files that are not part of VisualAge COBOL to the workstations. The format for COPY is: COPY = sourcefile targetfile If targetfile already exists, it is overwritten. If either file specification is incorrect, the copy is not done. DELETEBACKUP YES to delete a backup version along with the product when Delete is chosen; NO to keep the backup version. This setting is only used when you delete the product. See "Reinstalling or Installing Components" in "Trouble-Shooting for Installing VisualAge COBOL", section 3.0 in this file for details on deleting the product. FILE The directory where you want to install your COBOL product. INCLUDE The name of another response file to include. You can have up to five levels of nested response files. If you don't specify the fully-qualified file name, the install program looks for the response file using the following search order: 1. The current directory. 2. The path specified by the /G command-line option. 3. Directories specified by the PATH environment variable. 4. Directories specified by the DPATH environment variable. If the file name specified contains a wildcard character (* or?), the first matching file is used. SAVEBACKUP Yes to save a backup copy; NO to not save a backup. This setting is only used when you install corrective service (CSDs) for VisualAge COBOL. USEREXIT The name of a program that you want the install program to call. This is useful if you are installing VisualAge COBOL using an SDM, and want to perform additional tasks. If you do not specify the fully-qualified file name, the install program looks for the program file using the following search order: 1. The current directory. 2. Directories specified by the PATH environment variable. 3. Directories specified by the DPATH environment variable. If the file name specified contains a wildcard character (* or ?), the first matching file is used. WORK The directory where you want to install the Warp Toolkit. You must specify responses for the CFGUPDATE, DELETEBACKUP, FILE, SAVEBACKUP, and WORK keywords, and specify at least one component for the COMP keyword, for the install program to work correctly. 5.2 Command-Line Options ------------------------- You can specify a number of command-line options for the install command. If you run install or shrdinst interactively, you don't have to specify any options. If you run install with a response file, you must specify install2: /A /C /O /P /R /X All other options are optional. __________________________________________________________________________ The command-line options are: Option Description ------ ----------- /A:action Specifies the action to perform, action can be any of: D Delete. I Install. U Update. (Note that you should only use this action when you are installing corrective service (CSDs) to VisualAge COBOL. /C:<sourcedir>\IBMCOBOL.ICF Specifies the catalog file that contains the information about the VisualAge COBOL files. You must specify the drive and directory, which are the same as the install program. Note: <sourcedir> is the source directory where source files reside. /G:includepath Specifies the path the install program should use to locate response files. /L1:<targetdir>\errorlog Specifies the error log file. The install program logs the install events in this file and prefixes them with a time stamp. If you do not specify a path and file name, IWZINSTS.OUT is created in the temporary install directory (usually on the drive with the most available space). If you do not specify this option, messages are not logged. Note: <targetdir> is the target directory where you installed the product. /L2:<targetdir>\historylog Specifies the history log file. The install program logs the install events in this file and prefixes them with a time stamp. If you do not specify a path and file name, the history log is created in the temporary install directory (usually on the drive with the most available space). If you do not specify this option, the history is not logged. /O:DRIVE Specifies that the program files are being copied from a local or remote disk drive, not a mainframe host. /P:"VisualAge COBOL Enterprise for OS/2 V2.2" Specifies the name of the product to install. /R:<targetdir>\UNATTEND.RSP Specifies the response file to use. If you do not specify the fully-qualified file name, the install program looks for the response file using the following search order: 1. The current directory. 2. The path specified by /G, if any. 3. Directories specified by the PATH environment variable. 4. Directories specified by the DPATH environment variable. /S:<sourcedir> Specifies the directory where the source files reside. /T:<targetdir> Specifies the directory where the files should be installed. If you use this option, it overrides what is specified for FILE in the response file. /TU:<targetdir>\CONFIG.SYS Specifies the CONFIG.SYS file to be updated. /X Specifies that the install program runs unattended, using a response file. __________________________________________________________________________ 5.3 Return Codes ----------------- The install program returns a 2-byte hexadecimal value to the SDM, indicating success or failure, what steps should be taken next, and what type of messages, if any, were logged: o Successful installation. No other action required. 00 00 No messages were logged. o Successful installation. Restart the workstation operating system. Do not call the install program again. FE 00 No messages were logged. FE 04 Warning messages were logged. FE 08 Error messages were logged. FE 12 Severe error messages were logged. o Successful installation. Restart the workstation operating system and call the install program again. FF xx xx can be any value from 00 to FF. o Installation did not complete successfully; an unexpected condition was encountered. 16 00 The install program was invoked incorrectly. 16 04 Messages were logged. If you created user exits for the install program to call (as specified by the USEREXIT keyword in the response file), your user exit must return a 2-byte hexadecimal value to the install program as follows: 00 00 Your program completed successfully. FE 00 Your program completed successfully, and requires the workstation operating system to be restarted without calling the install program again. When you return this value, the install program displays a message to restart the operating system. FF xx Your program completed successfully, and requires the workstation operating system to be restarted and the install program to be called again. When you return this value, the install program displays a message to to restart the operating system and to try the action again. If your program is in REXX, you can use the REXX EXIT command and return the value in decimal instead of hexadecimal. If your program returns a different value to the install program, the install program displays a message that a product-specific error occurred, indicating the name of your program and the return code. 5.4 Installing Using Response Files ------------------------------------ If you are installing from a CD-ROM or LAN server, you can run the install program unattended, using a response file to specify what to install and where. You can use response files for either a basic or shared installation. To install using a response file: 1. Create a response file, or tailor the sample response file, UNATTEND.RSP, provided in the IBMCOBOL\EXTRAS directory of the CD-ROM. You can copy UNATTEND.RSP to your hard drive and change the appropriate responses. Make sure that: o FILE specifies the directory where you want to install the Compiler and Nonvisual Tools for a basic install. For a shared install, it is known as the local file directory. o WORK specifies the directory where you want to install the Warp Toolkit. o COMP keywords specify the components you want to install. Note: For shared install, you do not need WORK. For a list of all the parameters you can change, see "Unattended Install", section 5.0 in this file. 2. From an OS/2 command line, change to the CD-ROM or LAN directory where the install program resides. 3. Invoke the basic install program with the command: install2 /A:I /X /R:d:\UNATTEND.RSP /C:IBMCOBOL.ICF /P:"VisualAge COBOL Enterprise for OS/2 V2.2" /O:DRIVE where d:\UNATTENDED.RSP or <targetdir>\UNATTEND.RSP is your response file. For a description of the /A command-line option and other command-line options, see section 5.2, "Command-Line Options". See also section 5.0, "Unattended Install". 4. Or, invoke the shared install program with the command: install2 /A:I /X /R:d:\UNATTEND.RSP /P:"VisualAge COBOL Enterprise for OS/2 V2.2" /O:DRIVE /C:<sharedir>\IBMCOBOL\SHARED\IBMCOBOL.ICF /S:<sharedir>\ where <sharedir> is the base LAN directory where the source files reside. For the /S option, ensure that there is a back slash (\) at the end. Note: If you want to log any error messages that are generated, specify the /L1:errorlog option, where errorlog is the path and file name to use for the error log. This is usually a good idea because messages are not displayed during an unattended install; if you don't log them, you have no record of what errors occurred. For a description of the /A command-line option and other command-line options, see section 5.2, "Command-Line Options". See also section 5.0, "Unattended Install". 5. You can then leave the install program unattended. When it is complete, the OS/2 command prompt appears in the OS/2 session where you ran the install2 command. 6. If you choose not to have the installation program update your CONFIG.SYS, make the changes to it now BEFORE you reboot. (See the CONFIG.ADD file that VisualAge COBOL generates.) 7. Shut down and restart your system to make the changes to your CONFIG.SYS file take effect. You have now successfully installed VisualAge COBOL, and are ready to go! See the "Getting Started" manual for what to do next. 5.5 Adding or Deleting Components Using a Response File -------------------------------------------------------- To add or delete components using a response file: 1. Modify the appropriate parameters in your response file. If you are deleting components, make sure that: o COMP keywords specify the components to delete. o DELETEBACKUP specifies whether you want to delete backup files If you are adding components, make sure that: o FILE specifies the directory where you want to install the Compiler and Nonvisual Tools for a basic install. For a shared install, it is known as the local file directory. o WORK specifies the directory where you want to install the Warp Toolkit. o COMP keywords specify the components you want to install. Note: For shared install, you do not need WORK. 2. Change the CD-ROM or LAN directory where the VisualAge COBOL install program resides. 3. To delete or install components from a basic install: For example, to install, enter: install2 /A:I /X /R:<targetdir>\UNATTEND.RSP /C:IBMCOBOL.ICF /P:"VisualAge COBOL Enterprise for OS/2 V2.2" /O:DRIVE where d:UNATTEND.RSP or <targetdir>\UNATTEND.RSP is your response file For a description of the /A command-line option and other command-line options, see section 5.2, "Command-Line Options". See also section 5.0, "Unattended Install". Or, for a shared install program: For example, to install, enter: install2 /A:I /X /R:d:\UNATTEND.RSP /P:"VisualAge COBOL Enterprise for OS/2 V2.2" /O:DRIVE /C:<sharedir> \IBMCOBOL\SHARED\IBMCOBOL.ICF /S:<sharedir>\ where sharedir is the base LAN directory where the source files reside. For the /S option, ensure that there is a back slash (\) at the end. For a description of the /A command-line option and other command-line options, see section 5.2, "Command-Line Options". See also section 5.0, "Unattended Install". 4. You can then leave the install program unattended while the components are deleted or installed. 5. When the install program has finished, the OS/2 command prompt appears in the OS/2 session where you ran the install2 command. 6. If you added components and chose not to have the installation program update your CONFIG.SYS, make the changes to it now BEFORE you reboot. (See the CONFIG.ADD file that VisualAge COBOL generates.) 7. Shut down and reboot your workstation. ========================================================================== Copyright IBM Corporation 1998 - All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ========================================================================== Trademarks The following terms are trademarks of International Business Machines Corporation in the United States or other countries, or both: IBM VisualAge Other terms used in Installation Notes, which may be denoted by a double asterisk (**), are trademarks or service marks of others. ========================================================================== Installing VisualAge COBOL FixPak 1 ----------------------------------- The following scenarios describe how to install this FixPak, depending on how you initially installed VisualAge COBOL Version 2.2: 1) Basic Install - you typed INSTALL to install directly from ------------- the CD-ROM to your PC. To apply the fixpak from the CD-ROM, type: e:\service (where e is the CD-ROM drive). 2) Shared Install - you typed SHRDINST to have a shared install -------------- from the product CD-ROM. You cannot apply the FixPak for this type of shared install. You must deinstall Version 2.2, perform a basic install, and then apply the FixPak. 3) LAN Basic - you typed INSTALL from a LAN directory, where Install your LAN administrator has copied the VisualAge --------------- COBOL image. This is basically the same as a non-LAN basic install. You apply the FixPak to your installed Version 2.2 product. Your LAN administrator should do the following: 1) Create a directory on the server that LAN users can access (for example, COB22FP1). 2) Change to that LAN directory and use XCOPY to copy all the files under the FIXPAK directory of the VisualAge COBOL V2.2 FixPak 1 CD-ROM. The syntax for XCOPY is (where e is the CD-ROM drive): xcopy e:\fixpak\* /s 3) Notify LAN users of where the installation files are located and to type SERVICE from the LAN directory to install the FixPak. 4) LAN Shared - you typed SHRDINST to have a shared install Install from a LAN. ----------- You must deinstall VisualAge COBOL V2.2, reboot, and then install VisualAge COBOL 2.2 plus FixPak 1. To set up VisualAge COBOL V2.2 with FixPak 1, you LAN administrator should do the following: 1) Create a directory on the server that LAN users can access (for example, VACOB221). 2) Change to that LAN directory and use XCOPY to copy all the files from both the VisualAge COBOL V2.2 CD-ROM and the VisualAge COBOL V2.2 FixPak 1 CD-ROM. The syntax for XCOPY is (where e is the CD-ROM drive): For Version 2.2: xcopy e:\* /s For FixPak 1: xcopy e:\server\* /s 3) Notify LAN users of where the installation files are located and to type SHRDINST from the LAN directory to install the FixPak. Note: If you want a basic install instead of a shared install, type INSTALL. This will install all selected files to your PC.

/*-------------------------------------------------------*/ /* PROGRAM: COBUNZIP.CMD */ /* Unzip VisualAge COBOL 1.2 Refresh FixPak #2 ZIP files */ /* COPYRIGHT: Copyright (C) International Business */ /* Machines Corp. 1997 */ /*-------------------------------------------------------*/ basename = 'cob121' nfiles = 5 parse upper arg options if options == "?" | options == "/?" then do say "Usage: cobunzip [/d]" say " Unzip FixPak files." say " Use option /d to delete zip files after unzipping." say " Requires PKUNZIP2.EXE." exit end if options == "/D" then delete = TRUE else delete = FALSE do i = 1 to nfiles if i < 10 then num = "0" || i else num = i zipname = basename || num || ".zip" 'pkunzip2 -d -o' zipname if delete == TRUE then 'del' zipname end exit

/*------------------------------------------------------*/ /* PROGRAM: COBUNZIP.CMD */ /* Unzip VisualAge COBOL 1.1 CSD #1 ZIP files */ /* COPYRIGHT: Copyright (C) International Business */ /* Machines Corp. 1996 */ /*------------------------------------------------------*/ basename = 'cob111' nfiles = 9 parse upper arg options if options == "?" | options == "/?" then do say "Usage: cobunzip [/d]" say " Unzip CSD files." say " Use option /d to delete zip files after unzipping." say " Requires PKUNZIP2.EXE." exit end if options == "/D" then delete = TRUE else delete = FALSE do i = 1 to nfiles if i < 10 then num = "0" || i else num = i zipname = basename || num || ".zip" 'pkunzip2 -d -o' zipname if delete == TRUE then 'del' zipname end exit