In this technote, you can find additional information on the following topics:
Installation - The "Working with Installation Manager" section in "Chapter 5: Installing Developer for System z" of the Installation Guide indicates that the first panel of the Installation Manager Install Packages wizard will display Developer for System z and any bundled offerings in the list of available packages. This is true only if Installation Manager version 1.2 is already installed on the system.
If Installation Manager is not installed, or if it is at a version prior to 1.2, the first panel of the Install Packages wizard will only display Installation Manager 1.2 in the list of available packages.
Follow the prompts in the Install Packages wizard to install Installation Manager 1.2. When the installation completes, click "Restart Installation Manager." Installation Manager will restart automatically and will display Developer for System z and any bundled offerings in the list of available packages. From there you can follow the steps outlined in the Installation Guide.
- When installing Rational Developer for System z 7.5 from CDs, the Launchpad product document links will only work if the Launchpad CD is the current CD.
- When starting Rational Developer for System z 7.5 on Simplified Chinese after installation, some broken Chinese characters in a temporary file path may stop the workbench from starting. To solve this problem, you will need to manually delete all files under the .eclipse folder.
- If Rational Developer for System z v7.5 is installed into the same package as either Rational Application Developer (RAD) 7.5 or Rational Business Developer (RBD) 7.5 and then Rational Developer for System z v7.5 is uninstalled, RAD and RBD will no longer be functional. In this case, the user must uninstall and reinstall the affected products.
Migration - AIX Connections When you attempt to use a Rational Developer for System z v7.1 workspace with AIX connections in Rational Developer for System z v7.5, the AIX connections will not be seen and will have to be recreated as UNIX connections. A Windows->Reset will not cause the AIX connection to appear.
To see the z/OS connections, issue a File->Restart after Rational Developer for System z v7.5 selects and uses the Rational Developer for System z v7.1 created workspace.
Migration - Push to Host Currently "Push to Host" project properties do not migrate properly from a Rational Developer for System z v7.1.x client to a Rational Developer for System z v7.5 client. If you try to access the property group associated with the "Push to Host" project you will receive an error message stating "The Currently Displayed Pages contain invalid values". You must create a new property group with the correct properties for syntax checking and associate the property group with the "Push to Host" project.
Missing Start menu shortcut for Installation Manager on 64-bit systems On 64-bit systems, the Start menu shortcut for Installation Manager may be missing after Installation Manager version 1.2 is installed. Installation Manager is installed by default into the "C:\Program Files (x86)" directory. You can launch Installation Manager by browsing to that directory and running the IBMIM.exe executable file.
To create a Start menu shortcut, open Windows Explorer and browse to the "C:\Program Files (x86)\IBM\Installation Manager\eclipse" directory. From there you can do one of the following:
- Right-click the IBMIM.exe executable file and then click "Pin to Start menu." When you click the Start menu, you will see the Installation Manager shortcut pinned to the top of the menu.
- Alternatively, you can put the shortcut in a new folder in the Start > All Programs menu:
- Right-click the IBMIM.exe executable file and then click Create Shortcut. A shortcut to the IBMIM.exe executable file will be created in the same directory. Note that if you are not running with Administrator access on Windows Vista or Windows 2008 the shortcut will be created on your desktop.
- Right-click the Start menu icon and click Explorer All Users. Windows Explorer will open.
- Double-click the Programs folder to open it.
- Create a new folder to contain the Installation Manager shortcut by clicking Organize > New Folder (for Windows Vista and Windows 2008) or File > New > Folder (for earlier versions of Windows). Enter the name of the folder you want to use, for example "IBM Installation Manager".
- Drag the shortcut you created for the IBMIM.exe executable into the new Programs folder you created to put the shortcut in that folder. You will now have a shortcut for IBM Installation Manager on the Start > All Programs menu, under the folder name you created.
Use the Start menu shortcut you created anytime you want to start Installation Manager.
CICS Explorer resource filtering Each CICS® Explorer resource tab has a filter text box located on the upper right corner of the view. This filter is intended to display a filtered list of resources.
Note: The filtering mechanism is not operational at this time.
Debug The following problems occur when using the new v7.5 Default Editor support:
- Default editor support uses the language sensitive editor to display source during a debug session
1) Breakpoints do not indicate state:
Breakpoints shown in the default editor may not indicate the state of the breakpoint. If a breakpoint is disabled, the icon that appears in the vertical ruler of the editor will not change. The Breakpoint view may be used to see the correct state of the breakpoint.
2) Setting breakpoints in COBOL code containing SKIP/TITLE/EJECT may not work:
The default editor line numbers may not match the actual COBOL statement numbers if the COBOL code contains directives such as SKIP, TITLE, and EJECT. As a result, when setting a breakpoint in the Editor view, the breakpoint may not be set or may be set on the wrong line. The Breakpoint view may be used to enter the breakpoint on the correct statement number. Alternatively, the default editor can be disabled. (See item #3 for instructions for disabling the default editor.)
3) Disassembly code may not be visible:
The default editor does not display disassembly code. To view disassembly code, disable the default editor by performing the following steps: (1) Select Window->Preferences
(2) In the filter field at the top of the left pane of the Preferences dialog, enter: Compiled Debug
(3) In the resulting list, click "Compiled Debug" under "Run/Debug"
(4) In the Compiled Debug preference page, select the "Always use Debugger Editor while debugging" check box.
(5) This will disable the default editor support and use the Debugger Editor for all source/listing debugging.
(6) If the disassembly code does not display, click the stack frame entry in the Debug view to refresh the editor view.
To enable default editor support, select the "Always use Debugger Editor while debugging" check box so that it is not checked.
- Local COBOL and PLI debugging does not work on Windows Server 2008
The debug engine required to debug local COBOL and PLI programs will not start on Windows Server 2008
Advanced COBOL Editor DBCS and BIDI Characters The Validation without compilation parser will flag all DBCS and BIDI Characters as invalid. To avoid these errors please disable the advanced tooling when working with DBCS and BIDI files.
Documentation - In the Prerequisites Document, under Additional Software Requirements, the information for IBM CICS® TXSeries® is incorrect . The correct prerequisite level is IBM CICS TXSeries for Multiplatforms v6.2 with no PTF required. The program number is 5724-B44. The related product web site is: http://www.ibm.com/software/htp/cics/txseries/
- In the Prerequisites Document, under Additional Software Requirements, the information for AIX is missing. AIX v5.3 or greater is required.
Problem compiling COBOL applications with the co-processor When executing SQL statements COBOL applications may receive an SQL code -30020 which indicates that there is a problem in the communication data stream. This is due to a problem with the generation of the SQLA_PROGRAM_ID generated by the DB2® v9.5 co-processor.
Please refer to the DB2 APAR IZ35049. This problem will be fixed in the next DB2 fixpack.
|
