IBM VisualAge for COBOL for OS/2, Version 1, Release 1 Corrective Service CSD #1 (FixPak 1) Installation Instructions and Summary of Changes This CSD will available on CD-ROM by Feb 20, 1996. To order, call 1-800-992-4777 and request PTF XR21407 (part number GK2T-9052-01). This file contains information that will be useful to you when installing this CSD. It is divided into the following categories: A. INSTALLATION NOTES B. INSTALLATION INSTRUCTIONS C. CSD #1 SUMMARY OF CHANGES BY COMPONENT A. INSTALLATION NOTES 1. If you have installed the Remote Edit/Compile (beta) component, an additional 2.5 MB will be required on your hard disk to install the CSD. This is because new support for remote debugging has been added to this component. 2. The printable postscript files containing the VisualAge COBOL manuals have been updated for this CSD, and are available separately. They are available wherever this CSD is available. On ftp.software.ibm.com, they can be found in the directory ps/products/cobol/pubs/cob11ps1. On the CSD CD-ROM, the postscript files can be found in the PRINTABL directory. 3. After this CSD has been applied and the phase 2 install has run, projects on the desktop may appear as ordinary file icons. To restore the projects, shutdown and reboot your system again. 4. After installing this CSD, projects on the desktop may lose their inheritance (and thereby their actions in the Project menu). If this is the case after install: a) Click on the "View" menu bar choice b) Click on the arrow to the right of the "Settings" choice c) Click on "Inheritance" from the cascaded menu. The project's settings notebook opens. d) If a "?" entry appears in the "Inherit from:" list box, select it and click on the "Remove" push button e) Click on the "Add" push button f) In the "Select a project to inherit from" window, select the drive where your OS/2 desktop directory resides (for example, your C: drive) g) Then, double-click on the OS/2 desktop directory (for example, DESKTOP) h) Double-click on the directory for the VisualAge COBOL folder (for example, "VISUALAG" or "VISUALA1" on FAT systems, "VisualAge COBOL" on HPFS systems) i) Double-click on the directory for the Works folder (for example, "WORKS") j) In the list box on the left, select the entry for the master project that you require: For COBOL MVS projects, select "IWZVHPRJ" For COBOL default projects, select "IWZVMPRJ" For COBOL GUI Designer projects, select "COBOL_G1" on FAT systems and "COBOL GUI Designer Master Project" on HPFS systems. k) Click on the "Inherit" push button. The Inheritance page of the project settings notebook now displays the name of the master project you selected. l) Close the settings notebook to save reset inheritance. 5. All master projects and the Project Smarts catalog have been updated and full replacements are included in this CSD. If you have customized any of the master projects or Projects Smarts, you will need to make the same customizations after the CSD has been applied. You can save a copy of the customized projects and Project Smarts BEFORE applying the CSD to use as a reference when recustomizing the projects. To save a copy of the master projects and Project Smarts: a. Create and open a folder that will contain the saved copies. b. Click on a master project or Project Smarts icon with mouse button 2 and select "Copy" from the pop-up menu. c. In the Copy window, select the folder opened in step 1 and click on the "Copy" push button. 6. If you apply the CSD, and later want to add a VisualAge COBOL component which you haven't yet installed, use the product-level CD-ROM. Reboot, and ignore any messages you may receive from the WorkFrame phase 2 install. Now, reapply the CSD, and reboot. The WorkFrame phase 2 install will proceed with no errors. 7. If you are a LAN administrator and want to make the CSD available on a LAN drive, follow steps 1 and 2 below, unzipping the CSD to a directory on the LAN drive. Or if you have the CSD on CD-ROM, simply xcopy the entire CD-ROM to the LAN drive. The PRINTABL directory may be omitted if its not necessary to make the postscript files available. Your users will be able to install from the LAN directory using the instructions below. B. INSTALLATION INSTRUCTIONS: 1. If you have the CSD on CD-ROM, change to the root directory of the CD-ROM, and skip to step 3. If you are installing from a remote LAN directory where your LAN administrator has placed the CSD, change to that directory, and skip to step 3. If you have received this CSD as a series of ZIP files, you will need PKUNZIP2 or a compatible utility to unzip the CSD. PKUNZIP2 is a shareware product which is widely available. It is distributed with some versions of OS/2, so you may already have it on your system. If you do not have it, it can be obtained via internet ftp from hobbes.nmsu.edu in /os2/archiver/pkz102_2.exe. It is available on Compuserve in the PCVENC Forum, in Library 11 (PKWARE), as file pkz102_2.exe. 2. You must unzip all the files into a single directory, from which you will install the CSD. In order to do this, create a new directory, and move all the files from this CSD into it, including the COBUNZIP.CMD command file. Then change to the new directory and unzip all the files by running COBUNZIP. If disk space is limited, you can have COBUNZIP delete each ZIP file after unzipping it by using the /d option. For example: md cobcsd1 move cob*.zip cobcsd1 move cobunzip.cmd cobcsd1 cd cobcsd1 cobunzip 3. Run the CSD install program by entering INSTALL at the command line. The main VisualAge COBOL Installation window and the README.CSD window appear. 4. Select CONTINUE in the README.CSD window. The Update window appears, displaying product information. It also provides two checkboxes: Update CONFIG.SYS This box directs the install program to automatically update your CONFIG.SYS file. It also backs up CONFIG.SYS before making any changes. If you do not want the install program to update your CONFIG.SYS, remove the check mark by deselecting the box. In this case, a file called CONFIG.ADD will be created which contains the changes you will need to make manually to your config.sys. Note: We recommend you leave this box checked to update CONFIG.SYS automatically. Save a backup version? Select the "Save a backup version" check box in the Update window to save a backup version of any files that are replaced during the update. Selecting this option enables you to restore the current version of the product after the update is done. The backup version of the files are placed on the same drive that the product, VisualAge COBOL, is installed on. Do not select this option if disk space is not available to store these backup files. To restore the current version at a later time (i.e., to remove the CSD), run the Installation Utility in the Works folder, and select RESTORE from the ACTION pull-down menu. To delete the backup version, run the Installation Utility and select DELETE from the ACTION pull-down menu, making sure to use the "Delete only the backup versions" option on the Delete window. 5. When you have chosen the options you want, select OK to continue. The install program begins copying files to your hard drive. The Update progress window shows you the status of the installation. 6. A message window tells you when the installation is complete. Select OK to remove the message window, then select the Exit button to end the install program. 7. It is very important to shut down and restart your system after installing the CSD. After rebooting, CONFIG.SYS changes will take effect, and files which were in use during the install will be updated. If WorkFrame is installed, the installation program requires a second phase, which is automatically invoked from your Startup folder when you reboot. An OS/2 window with the title WorkFrame V3 Phase 2 Install appears after you have rebooted. Messages appear in the window to inform you of the install program's actions. When the installation is complete, the window disappears. If you want to verify that the installation completed successfully, look for IWZINST.LOG in your VisualAge COBOL directory (Visual Tools). The second phase of the install program creates this file and timestamps the entries in it. You have now successfully installed VisualAge COBOL CSD #1. C. CSD #1 SUMMARY OF CHANGES BY COMPONENT >>>>>>> COBOL COMPILER <<<<<<<< 1. When using Performance Analyzer, an unresolved reference was displayed due to profile hooks being generated for xxNewClass function. This has been corrected; profile hooks are not generated for xxNewClass function. 2. LENGTH OF special register will now reflect BINARY(S370). 3. Performance improvement for binary multiplication. 4. COBOL application now terminates with the value set in the RETURN-CODE special register when terminating with STOP RUN. 5. Now, SORT executes AT END code correctly when a program is compiled with the BINARY(S370) compilation option. 6. When the TMP environment variable does not specify the current dir ( SET TMP=. ), intrinsic functions with ALL subscripts are now executed. 7. Multiplication of fullword binaries when the receiver is floating point now gives expected results. 8. Fixed abend during compilation with message number 5201 and insert "CPGEN". 9. Following the read of a relative file, the user's relative key number is now updated as it should be. 10. Eliminated exception that occurred when a C++ (direct to SOM) program tries to invoke a method written in COBOL. 11. Eliminated exception that occurred when an item defined as PIC X is used as the object of a returning clause. 12. Corrected tallying results when the same subscripted data item is used with different subscripts in an INSPECT statement. 13. Now support more than 255 tallying clauses with different identifiers when used in one INSPECT statement. 14. Corrected messages issued when a binary data item, with PICTURE clause of PIC 999, is compared to the literal -12345. 15. Sort keys of USAGE COMP are now reflecting the BINARY(S370) option. 16. The VALUE clauses on data definitions of nested programs are now taking effect if there is a CALL identifier in the compilation unit. 17. EVALUATE now works correctly when the evaluating item is reference modified with identifiers. For example: EVALUATE A1(B1(I) : B1(I)) 18. ADATA and EXIT(,,,ADEXIT(IWZRMGUX)) are now installation default values. When these values are in effect and are not overridden at the command line, two sets of compiler error messages will be displayed. 19. LOW-VALUES and HIGH-VALUES values in Japanese are now correct. 20. Compare is now correct with Alternate Collating Sequence, where the alternate collating sequence is specified as STANDARD-1, when an ALL "literal" is compared to a variable length group data item, where the length of the data item is less than that of the initial "literal". 21. Addresses are now passed correctly to 16 bit routines. When the directive CALLINTERFACE FAR16 is used and the argument is passed by reference or content, the generated code is now correct. 22. When the VALUE clause literal is shorter than the length of the DISPLAY-1 item, the literal is being padded with ASCII spaces not with DBCS spaces. 23. Results computed when FUNCTION MAX appears within a COMPUTE statement are now correct. 24. Output created when the reference modification operands are non-integer data names or non-integer function results is now correct. 25. Corrected the results of the ORD/CHAR function when running with an EBCDIC collating sequence. The problem only appeared when the intrinsic function argument is a dataname. 26. Corrected failure of somNew of a class when invoked from a method within that class. 27. A new compiler option DYNAM has been added. (See README for details.) >>>>>>> COBOL RUNTIME LIBRARY <<<<<<<< 1. REWRITE now gets correct file status after WRITE. 2. Remote alternate index files can now be created. 3. A START GREATER THAN failure is fixed. 4. WRITE ADVANCING 0 is correct now for line sequential files. 5. ACCEPT now checks for I/O errors. 6. ADVANCING linage counter has been fixed. 7. ADVANCING now handles blank lines and spacing correctly. 9. Fixed the sign of the remainder for certain cases involving large floating point numbers. 10. START in the presence of duplicate keys now returns the correct FILES STATUS value of 02 instead of 22. 11. PRESENT-VALUE no longer fails. 12. Sign is no longer lost with "B" symbol in numeric-edited items. 13. DBCS and Kanji class test now return NOT DBCS and NOT KANJI correctly. 14. DBCS comparison now works for unequal string lengths. >>>>>>> WORKFRAME <<<<<<<< 1. Refreshed the COBOL Project Smarts. 2. Japanese version of the product built with correct code page. 3. Various NLS changes - changes to ipf/rc files for various languages; renamed Project Smarts NLS parts >>>>>>> COBOL EDITOR <<<<<<<< 1. COBOL Editor now recognizes COBOL directives. >>>>>>> WORKFRAME PROJECT SUPPORT <<<<<<<< 1. Compiler options dialog saves size and position after closing. 2. Compiler options are suppressed in the command line if they are the same as the compiler installation default. 3. New "Data Tools" action class for all projects includes: "DB2 Start" "DB2 Local Logon" "DB2 Local Logoff" "DB2 Stop" "Data Assistant Schema View" (previously in Browse) "Data Assistant Mapping View" (previously in Create) 4. Target of the "COBOL Compile" action defaults to the project target instead of the name of the first selected file + .EXE 5. Explicit inclusion of SOMTK.LIB and DB2API.LIB as a library in the compiler options dialog for GUI projects is no longer necessary. 6. New "Restore COBOL Master Project" object is added to the "Works" folder. It recreates the "COBOL Master Project" in the "Works" folder, the "COBOL Project" template in the OS/2 "Templates" folder, and the "COBOL Project" template shadow in the COBOL "Templates" folder. 7. Writes to IWZINST.LOG during phase 2 of installation are flushed line-by-line to provide a better trace in case of a system crash during phase 2. 8. New options dialog for the "Link" action. Uses the same interface as the "Link" page of the "COBOL Compiler" action options dialog. 9. Removed "Preprocess for CICS" option from the "Prep" page of the "GUI Compile" action options dialog in the "COBOL GUI Designer Master Project" 10. Changed "RC Compile" action default parameters to ".\%n.RES" to ensure that the target .RES file is placed in the working directory of the project, not in the source directory. 11. "COBOL Compile" and "GUI Compile" default options changed to ADATA and EXIT(ADEXIT(IWZRMGUX)) for compiles done under WorkFrame to ensure that error feedback functions correctly from the Monitor. This applies to projects created after installing the CSD. 12. Restriction on TEST and /DEBUG options for "GUI Compile" action options dialog was removed. Each option can now be specified separately. 13. Warning was added to Non-GUI COBOL Compile action options dialog when the user specifies both the PROFILE and TEST options in the Compiler Options notebook. 14. "Create" action class actions were reordered to place "Create New Text File with the COBOL Editor" before "GUI Project Create" in the COBOL and GUI Designer Master Projects. 15. The action to Create an empty GUI project has been removed from the GUI Master Project and the "Empty COBOL GUI Designer Project" entry has been removed from the COBOL Projects Smarts. 16. The COPYDLL GUI compile option (specified on the "Other" page of the Compiler Options notebook) now copies all executables for a GUI project. 17. For a GUI project, options can now be passed to the Resource compiler. These options are specified as RC(options) in the "Enter GUI compile options" entry field on the "Other" page of the Compiler Options notebook. 18. A GUI project build will now continue if there is a warning message from the linker. 19. GUI build has changed to eliminate a sporadic hang of the build when a number of background processes are also running. >>>>>>> GUI DESIGNER <<<<<<<< 1. New events are now inserted in the COBOL program alphabetically by entry point name. 2. GUI Designer now recognizes COBOL ENTRY points in apostrophes. 3. setContents routine for MLEs now supports 64K bytes. >>>>>>> GUI CODE ASSISTANT <<<<<<<< 1. The expressions in the MOVE dialogs are no longer restricted to 30 characters. 2. When there are multiple parts with the same name, unambiguous names are generated. >>>>>>> DATA ASSISTANT <<<<<<<< 1. Due to a change in the underlying model, files generated by Data Assistant prior to this CSD should be regenerated. This includes Data Assistant-generated files with the extension of .SM, .INI, .CPY and .RPT. By default these files are located in the \DA subdirectory of the path specified by the ICOBDIR environment variable. The old files should be deleted then regenerated with this current level of Data Assistant. 2. Fixed window position and size problems on VGA systems. 3. Changed product logo version numbers from 1.1.0 to 1.1.1. 4. Enhanced error handling. Messages include: a) Database not found. Previously would come up empty. b) Connect failed. Also suggests possible causes. Previously would occasionally hang. c) DBMS type not supported. Only OS/2 and MVS databases are supported. 5. Enabled remote database access. Included help information. 6. Fixed problem where selecting Show Links menu item would cause error message SYS3175. Data Assistant Schema view -------------------------- Database Information window displays correct dbms type: OS/2 or MVS. Data Assistant Mapping view --------------------------- 1. Corrected copy file generation problems - Generates correct COBOL data types based on SQL data type that data item is mapped to. - Generates COMP-5 or COMP-4 (where appropriate) depending on dbms type, OS/2 or MVS, respectively. - Generates correct structures for variable-length data types. 2. User informed if data item added is: - a COBOL reserved word, or - otherwise not a valid COBOL data item. 3. Enabled removal of tables and views. 4. User now prompted to save upon exiting. 5. ".SM" not required when specifying mapping filename upon invocation of Mapping view. 6. Message displayed if column selected has an unsupported data type. 7. Support for decimal scale. 8. Fixes to data item entry field includes: a) check for duplicate data items as they are entered b) No blanks allows (leading, trailing, containing) c) maximum characters in data item entry field : 30 9. Fixed problems with occasional overwriting of data items. 10. Maximum characters for cursor name entry field: 18 (SQL limitation) Data Assistant - SQL Construction view -------------------------------------- 1. Update and Insert windows now operational. 2. Condition window gives error message for invalid syntax. Previously would bring Mapping view down occasionally. 3. Will now accept colons in the Condition window. 4. Removed generation of continuation characters which were not necessary and sometimes caused problems. 5. Fixed problem with occasional generation of lines beyond column 72. 6. Adds spaces between all tokens generated. 7. Fetch Block generates CLOSE-CURSORNAME label in Area A. 8. When multiple values are entered for the SQL statements INSERT and POS. UPDATE, the system may appear to be hung. If this happens, press CTRL+ESC. When the message appears that the window is not responding, click on the Enter push button. 9. The workaround is to select fewer column values to insert or update. Generate the SQL statement, then manually add the additional columns and values to the SQL statement in the COBOL Editor. >>>>>>> TRANSACTION ASSISTANT <<<<<<<< 1. Dialog template is replaced by regular Frame Window. 2. Minimize button is added to the window. >>>>>>> LINKER <<<<<<<< 1. Using latest version 01.02.03. >>>>>>> APPLICATION PACKAGING UTILITY <<<<<<<< 1. Added facility for selective packaging of VisualAge COBOL runtime components. 2. 50 character limit on Application Title is now enforced. 3. Streamlined the online help index. 4. IWZCCPM.DLL (the COBOL runtime interface for CICS for OS/2) will be included with non-GUI VisualAge COBOL runtimes. No additional license agreement is required. >>>>>>> SMARTDATA UTILITIES <<<<<<<< 1. Conversion table files (*.CVT files) are opened in read only mode. This allows SdU to be installed on a LAN that is defined to have only read access. 2. Fix for the occurrence of an invalid record length condition when a DDMOpen request is issued for a sequential or direct file that is to be subjected to ADL translation. 3. DFM/2 now removes all leading backslashes before sending the file name to the remote target system. Previously, leading backslashes for a file name were passed to the remote target system which resulted into an invalid file name condition. 4. Enabled stream data conversion (client end). 5. Local VSAM prevents access violation when opening an index file. 6. Issue message EHN0123 only when both the ADL and DDF files are missing. >>>>>>> WARP SOM TOOLKIT <<<<<<<< 1. Include files moved from INCLUDE\SOM to INCLUDE, as required by SOMSTARS, SOMCORBA, SOMXH utilities. 2. All SOM DLL's moved to SOM directory. 3. Added files SOMSEC.DLL and SOMSA.DLL. >>>>>>> REMOTE EDIT/COMPILE (BETA) <<<<<<<< 1. A feature that supports remote debugging of host applications is included. (See README for more information.) >>>>>>> DB2 <<<<<<<< 1. When precompiling under WorkFrame, bind files now default to the name of the source. 2. When precompiling under WorkFrame, bind files are now placed in the working directory. >>>>>>> COBOL INFORMATION <<<<<<<< 1. Compiler Options dialog help file has been updated to describe the new options dialog for the Link action. 2. Application Packaging help file has been updated to describe selective packaging of run-time components. 3. The online files for the Getting Started book, including the PostScript file (.PS), have been updated to reflect the CSD changes and other corrections. 4. Information Notebook - Product Support information for IBM VisualAge for COBOL for OS/2 has changed. This version replaces the information contained in the hardcopy version of the Getting Started book. 5. Information Notebook - Host Programs information has been updated. Information on remote debugging has been included. This beta-type information helps you set up the environment needed to debug your host applications from your workstation using the IBM Debug Tool. This version replaces the information contained in Appendix C of the Getting Started manual. 6. Debug Tool User's Guide has been added to the Information Notebook. This book (SC09-2137-02) now includes information on how to debug host applications from your workstation. This edition of the book is in draft format and is not available in hardcopy. Information might change or be added before this edition is published. 7. No changes have been made to the Programming Guide, neither the printable nor viewable files. 8. In the Language Reference Manual: a. Added APARs PN76185 and PN72032 to Language Reference Manual. b. Corrected formatting problems with tables 9, 52, and 53. c. Included 'x' revision bars on the printable Postscript file (IWZILMST). The 'x' indicates an IBM extension is contained on the line with the 'x' revision bar. Note: The 'x' may override, be overridden, or combine with other revision bars, which indicate technical changes. d. Reformatted Postscript file to correctly print all fonts. Note: The viewable and printable versions of the COBOL Language Reference contained on this CSD are at the -02 level. The published hardcopy manual remains unchanged at SC26-4769-01. 9. The WorkFrame How Do I list of actions and priorities have been updated to reflect the changes in the COBOL Master Project. 10. In the information for the Sample Applications, instructions are included on how to build and run the sample applications. This version replaces the information contained in Appendix B of the Getting Started book. 11. The request for the OS/2 tutorial from the Information Notebook is now working on OS/2 3.0 (Warp). 12. In the Task Helper: a. Updated task information for "Building an OS/2 GUI Application" to reflect CSD changes, including changes to compile and link options, starting the GUI application, SQL considerations, and packaging information. b. Updated task information for "Building an OS/2 Application" to reflect CSD changes, including changes to compiling and linking information, SQL considerations, starting the non-GUI application, and packaging information. c. Updated task information for "Working with Host (MVS) Applications" to include instructions for debugging host programs on the workstation using the IBM Debug Tool. 13. In Data Assistant Help, documented new "Exit" menu item from "Data Structures Mapping View" menu, and added information about using Data Assistant with remote databases. >>>>>>> COBOL SAMPLE PROGRAMS <<<<<<<< 1. Added instructions on how to build and run the sample projects to the Samples Information located in the Samples folder. 2. Added a command file to create the DB2 database and table for Sample Project 3; added the VSAM files for Sample Project 6. 3. Improved the display of the GUI, the window sizings and placements, and eliminated the flashing when the MLE (multiline edit) field is filled for all sample projects.