IBM® TPF Toolkit for WebSphere® Studio – Interim Fix v2.0.10


 

Table of contents

1.0             Enhancements and fixes in Interim Fix v2.0.10

2.0             Enhancements and fixes in Interim Fix v2.0.9

3.0             Enhancements and fixes in Interim Fix v2.0.8

4.0             Enhancements and fixes in Interim Fix v2.0.7

4.1             IDE updates

4.2             Editor updates

4.3             Debugger updates

5.0             Enhancements and fixes in Interim fix v2.0.6

6.0             Enhancements and fixes in Interim fix v2.0.5

7.0             Enhancements and fixes in Interim Fix v2.0.4.1

8.0             Enhancements and fixes in Interim Fix v2.0.4

8.1             IDE updates

8.2             Editor updates

8.3             Menu Manager updates

8.4             TPFTool command line interface updates

8.5             Interim Fix install process updates

9.0             Enhancements and fixes in Interim Fix v2.0.3.1

9.1             Menu Manager updates

9.2             TPFTool command line interface updates

9.3             Interim Fix install process updates

10.0       Enhancements and fixes in Interim Fix v2.0.3

10.1       IDE updates

10.2       Editor updates

10.3       TPFTool command line interface updates

10.4       Migration tool updates

10.5       Help updates

11.0        Enhancements and fixes in Interim Fix v2.0.2

12.0        Enhancements and fixes in Interim Fix v2.0.1

13.0        Migrating to the latest Interim Fix

13.1       Migrating to Interim Fix v2.0.10

13.2       Migrating to Interim Fix v2.0.9

13.3       Migrating to Interim Fix v2.0.8

13.4       Migrating to Interim Fix v2.0.7

13.5       Migrating to Interim Fix v2.0.6

13.6        Migrating to Interim Fix v2.0.5

13.7        Migrating to Interim Fix v2.0.4.1

13.8        Migrating to Interim Fix v2.0.4

13.9        Migrating to Interim Fix v2.0.3.1

13.10   Migrating to Interim Fix v2.0.3

13.11   Migrating to Interim Fix v2.0.2

13.12   Migrating to Interim Fix v2.0.1

14.0        Installing the latest Interim Fix

15.0        Installing standalone features

 

 

1.0 Enhancements and fixes in Interim Fix v2.0.10

 

The following is the list of enhancements and fixes included in Interim Fix v2.0.10:

 

1.      The error message “An error has occurred.  See error log for more details.” no longer appears when a file is opened from the TPF Project Navigator view.  In Interim Fix v2.0.8, this error occurred after you opened a local file for editing.

2.      The error message “An error has occurred while activating this view” no longer appears when you open the TPF Toolkit Job Log view.

3.      If you are debugging without APAR PJ30134 applied, the following error message no longer appears continuously:

“The debug engine reported an error, but no error message text was provided.  The error return code was 303”

In Interim Fix v2.0.7, this error started to occur while debugging.

2.0 Enhancements and fixes in Interim Fix v2.0.9

 

Interim Fix v2.0.9 was intentionally skipped.

 

3.0 Enhancements and fixes in Interim Fix v2.0.8

 

The following is the list of enhancements and fixes included in Interim Fix v2.0.8:

 

4.      You can now filter error messages in the TPF Error List view to only display messages that satisfy criteria you set. Messages can be filtered based on host name, file location, message ID, message text, severity, and line number. To set the criteria for filtering, use the ‘Change Message Filter’ action available from the view menu in the TPF Error List view.

1.      When you open a file in the LPEX editor using the TPF HLAsm or TPF C/CPP parser, the commands that are specified on the parser preference pages are run. Now you can also use the project properties to specify commands to run when a file from the project is opened with one of the above mentioned parsers.  The commands are set on the ‘TPF HLAsm Parser’ and ‘TPF C/CPP Parser’ project properties pages. To invoke these properties pages, right-click a project and select ‘Properties’ from the pop-up menu.  The commands that are set on the properties pages are run in addition to commands set at the preference level.  The commands set at the preference level run before commands set at the project level.

2.      Auto comment commands can now contain user variables and project level substitution variables.  For example, if you want to invoke auto comment using the project name as the base auto comment, issue the following command:

autoComment on &N

3.      When you edit files with the TPF Toolkit LPEX editor, the 'Get File' action is available from the File menu in the menu bar.  Using the 'Get File' action, you can browse for a file that you want to insert into the file that you are currently editing.  The 'Get File' action now allows you to browse the remote file system and insert the contents of a remote file into the file being edited.

4.      When editing a file in the TPF Toolkit LPEX editor, you can invoke the LPEX compare action by selecting Edit > Compare > Compare from the main menu bar.  The 'Compare' action allows you to browse for a file that you want to compare with the file that you are editing.  The 'Compare' action now allows you to browse the remote file system and compare a remote file to the file being edited. 

 

 

4.0 Enhancements and fixes in Interim Fix v2.0.7

 

The following is the list of enhancements and fixes included in Interim Fix v2.0.7:

 

4.1 IDE updates

 

1.      The ‘Analyze Trace’ action that was previously only available from the menu bar is now available on the pop-up menu for .trc files.

2.      When you use the JCL submit action to submit a JCL where the length of the JCL output listing file name is 50 characters, an error no longer occurs.

3.      When specifying file types for Menu Manager actions, the file types are now case insensitive.  Previously, actions that were applied to .c files would not apply to .C files.

4.      Copy operations support files containing a ‘$’ in the file name.  All copy and paste operations now work with file names that have a ‘$’ in the file name.

 

4.2 Editor updates

 

1.      Previously, when using the TPF HLAsm parser to edit assembly files, the parser issued an error message when an equals sign was used in a quoted string within a positional parameter.  The parser has been fixed and allows you to use an equals sign in a quoted string within a positional.

2.      The syntax definition of the GETCC macro has been updated in tpfhlasm.dat.  The old definition caused error messages to be issued by the TPF HLAsm parser even when the GETCC macro was coded correctly.

 

4.3 Debugger updates

 

1.      The storage mapping with an XML file no longer incorrectly calculates the offset with a ‘BITMASK’ structure.

2.      A ‘change representation’ action is provided for storage mappings and custom tree memory renderings.  This new action allows you to switch between HEX, ASCII, and EBCDIC.

3.      EBCDIC values are now displayed correctly in the Storage Mapping view.

4.      The error message that previously displayed the text "No error message text available" has been changed to provide more details about the problem that has occurred.  The error message now includes an EPDC error return code.

5.      A check box to remember the previous decision has been added to the fork dialog.  If you choose to remember your decision, you are not prompted on subsequent forks.

 

 

5.0 Enhancements and fixes in Interim Fix v2.0.6

 

The following is the list of enhancements and fixes included in Interim Fix v2.0.6:

 

1.      Previously, the &U substitution variable was not resolved in all cases. For example, when used as an export variable in an action header file. The &U substitution variable is now substituted correctly with the action name.

2.      If the OBJLSC information is found in both the TPF build script file and the build script configuration (*.prof) file, the information in the TPF build script file is used. If an LSC file is specified in both the LLM wizard and the build script configuration (*.prof) file, the information from the wizard page is used.

3.       The F1 help for PUT 18 has now been linked to the TPF Toolkit LPEX editor. If you are using PUT 18, you must set the parser to use PUT 18. When you select a macro and press F1, the PUT 18 help for that macro is now displayed. To set the parser to use PUT 18, complete the following steps:

a.       Open an assembly file in the TPF Toolkit LPEX editor.

b.      In the workbench, select Window > Preferences  to open the Preferences window.

c.       In the left navigation pane, double-click the LPEX Editor node to expand it.

d.      From the list of LPEX Editor preferences pages, double-click the node that represents the path of the file you are editing to open the list of available file-level preferences pages.

e.       Click TPF HLAsm Parser to open the TPF HLAsm Parser preferences page.

f.        From the PUT level drop-down list, select PUT 18.

g.       Click Save as custom defaults.

h.       Click OK to save your changes in the preferences page.

 

 6.0 Enhancements and fixes in Interim Fix v2.0.5

 

The following is the list of enhancements and fixes included in Interim Fix v2.0.5:

 

1.      When you use the TPFTool command line interface to submit a JCL file, if you specify a remote location (-r) where the JCL file should be submitted from, that remote location will now always be used even if the specified JCL file is remote.

2.      The PUT level specific help are now being shipped as standalone features. In order to include PUT level specific documentation in the online help, you will now have to install the corresponding PUT level documentation feature.

Here is the list of available PUT level specific documentation that are now available as standalone features:

·        TPF Toolkit Document PUT 13

·        TPF Toolkit Document PUT 14

·        TPF Toolkit Document PUT 15

·        TPF Toolkit Document PUT 16

·        TPF Toolkit Document PUT 17

·        TPF Toolkit Document PUT 18

Note: When you upgrade to Interim Fix v2.0.5, you will no longer see any PUT level specific documentation in the online help. Refer to the Installing standalone features section for step-by-step instructions on installing the standalone feature(s) you might want.

 

7.0 Enhancements and fixes in Interim Fix v2.0.4.1

 

The following is the list of enhancements and fixes included in Interim Fix v2.0.4.1:

 

1.      When you register for debug using an IP address as the terminal, you can now specify a hostname with or without the domain information. For example, you can specify “hostname.my.company.com” as the terminal to register for debug. During the registration process, the hostname is converted into the corresponding IP address.

2.  You can now specify parameters for the launch user exit using the TPFCHECK environment variable.
For example, you set the TPFCHECK environment to:
C:\path to\my program.exe” parameter1 parameter2
When TPF Toolkit is started, it will run “
C:\path to\my program.exe” with parameter1 and parameter2 as the first two parameters; and the TPF Toolkit version number is passed as the last parameter.
Note: You have to surround the program name with quotes if there are spaces in the path or the program name. Do not include the parameter list in the quotes.

3.  When you right click on a file in TPF Toolkit Project Navigator that does not have the TPF Toolkit LPEX Editor as the default editor, you are now able to select the LPEX editor in the Open With sub-menu as the editor to use.

 

8.0 Enhancements and fixes in Interim Fix v2.0.4

The following is the list of enhancements and fixes included in Interim Fix v2.0.4:

 

8.1 IDE updates

 

1.      A filter creation user exit has been introduced. Use the User Variables and Exits preference page to specify the program you want to run when you create a new TPF project filter. The exit is called every time a new filter is created. The filter name is passed as the last parameter to the exit program.

2.      You can now use TPF substitution variables when you specify the location of an external tool.

The format to specify substitution variable is as follows: ${tpf_variable:<variable_name>}

For example, to specify the TPFSHARE environment variable, use ${tpf_variable:%TPFSHARE%}

To specify the user variable, USR_MYVAR, use ${tpf_variable:&USR_MYVAR&}

3.      A new substitution variable &VER has been introduced that returns the version number of TPF Toolkit in the V.R.M format. For example, 2.0.4. This version number is now sent as the last parameter to the Launch exit set using the TPFCHECK environment variable. A new TPFTool service called queryVariable has also been introduced that allows you to query the substituted value of substitution variables from the command line, including this new variable.

4.      When you specify an HFS directory to locate ADATA files during loadset generation, the loader no longer throws an error if there are no ADATA files found in the specified concatenation of the ADATA search directories. The loader now issues a warning message and continues with the loadset generation.

5.      You can now use an environment variable to specify the location of the program for a message user exit. You can also now pass parameters to the exit program.

6.      When substitution variables are expanded for the search path during Remote Assemble or Remote Compile, a trailing “/” may cause the compile to fail. Search paths are now stripped of the trailing slashes.

7.      When you use &FILE to specify the search path concatenation, you can now specify a remote file that contains the search path list instead of a local file name.

For example:
   &FILE/u/userid/path/mysearchpath.cfg
   &FILE&R/mysearchpath.cfg
   &FILEC:\path\mysearchpath.cfg

   &FILE&DP\mysearchpath.cfg

8.      The Configuration File drop-down list in the Build Target wizards and properties pages now selects the first item in the list if there is no configuration file selected as the default in the Build Target preference pages.

9.      You can now create a loadset which only contains an ASM object. The loader no longer requires you to specify a DLM or DLL module when generating a loadset.

10.  The same remote file may be referenced by multiple filters in a project. Clicking on the Reload from project button in the Build List properties page now no longer adds the same file to the build list as duplicate entries.

11.  When collect name is used for an action, the collection of filenames that are gathered when the action is run is now quoted correctly. Each filename in the collection is now individually surrounded with quotes.

12.  The MakeTPF build tools for TPF 4.1 have been updated to support the same build environment as that of zTPF. This introduces the “single source” for makefiles and all related MakeTPF files in TPF 4.1 and zTPF. TPF Toolkit has been updated to support the latest version of the MakeTPF build tools for TPF 4.1. 
Note: You must download the latest MakeTPF Build Solution for TPF 4.1 v2 from the download site http://www.ibm.com/software/htp/tpf/download/maketpf.htm.

13.  Read-only files and folders are now decorated with a new read-only icon in the TPF Project Navigator.

14.  The user variable lookup problem has been fixed. The user variables are now picked up at the appropriate level, for example preference, project or file level.

15.  Several updates have been made to the product help.

16.  Several new FAQ entries have been added to the Support Information book in the online help (Support Information > TPF Toolkit support documents > TPF FAQ). These FAQs are also available on the Internet at: http://www.ibm.com/support/search.wss?rs=1068&tc=SSWHWV&dc=DB520&rankprofile=8

 

8.2 Editor updates

 

1.      You can now specify the autoComment command in the HLASM and C/CPP Parser preference pages. This will turn the autoComment feature on or off, as specified, when an ASM, C or CPP file is opened in the editor.

2.      When you use the C/CPP and HLASM parser preference pages to list the commands you want to run when the parser is invoked, and you use the proto command to define the expansion template, you can specify “\n” to indicate that you want new lines to be inserted during the template expansion

3.      A FAQ entry has been added to help you use the proto command in the LPEX editor. The proto command expands pre-defined templates and drops them in your source code. Refer to Support information > TPF Toolkit support documents > TPF FAQ > LPEX Editor > How can I use the proto command to expand templates?

4.      The parser settings for the tpfhlasm parser have now been fixed so that you can get a preview of the various style settings for the tpfhlasm parser in the Parser Settings preference page.

5.      The LPEX editor preferences are now persisted in the workspace instead of outside the workspace. When you apply Interim Fix v2.0.4, the update process will migrate all the LPEX preferences stored outside of the workspace to the appropriate location within your workspace. When you restart TPF Toolkit, the LPEX editor will use the migrated preferences in the workspace.

 

8.3 Menu Manager updates

 

1.      You can now run custom actions in the foreground. Running an action in the foreground locks up the main TPF Toolkit window until the action is finished running. To run an action in the foreground, select the Run action in foreground checkbox when you create or edit an action in the Menu Manager.

2.      The Menu Manager no longer saves the changes if you cancel out of the Menu Manager preference page.

3.      The Menu Manager uses a configuration file to determine the list of menu and action XML files to load. Three separate configuration files have now been introduced: an IBM configuration file residing in TPFSHARE that lists the XML files containing IBM actions and menus; an enterprise configuration file residing in TPFSHARE that lists the XML files containing enterprise level actions and menus; and a user configuration file residing in the workspace that lists the XML files containing user defined actions and menus. A new preference tab has been added to the Administration preference page that allows you to configure the content of these configuration files. Refer to Configuring > Setting preferences > TPF Toolkit preferences > Setting administration options > Viewing actions and menu files in the help for detailed information.

Note: When you apply the latest interim fix, the existing configuration file is automatically migrated for you. All the IBM XML files are migrated to the IBM configuration file in TPFSHARE. All non-IBM XML files listed in the configuration file are migrated to the user configuration file in the workspace. Use the Administration preference page to promote any custom actions and menu files to the enterprise level. You must install the TPF Toolkit Administrator feature to use the Administration preference page. Refer to the Installing standalone features section for step-by-step instructions on how to install the feature.

 

8.4  TPFTool command line interface updates

 

1.      A new service called Open has been introduced that allows you to open a file using the default editor in TPF Toolkit. You can use the File Associations preference page to assign a default editor for a file type.

2.      A new service called QueryVariable has been introduced that allows you to retrieve the value of a TPF substitution variable.

3.      The AddFilterString service has been updated so that you can now add filter strings for directories and files that do not exist.

4.      The asterisk (*) and the ampersand (&) characters are reserved characters in Microsoft® Windows. This poses a problem when you try to specify user variables containing & or a filter string containing * when you issue a TPFTool command. The following command line variables have been introduced to enable you to specify the asterisk and the ampersand character: %ast and %amp.

 

8.5 Interim Fix update process updates

 

1.      The Interim Fix update process has been updated. When you apply an Interim Fix, by default, any changed version of customizable files is copied to the refresh directory under TPFHOME. The list of customizable files to copy or delete has now been externalized. If you are redistributing a customized version of the Interim Fix from your internal update site, this setup helps you control the list of customizable files you wish to deploy and the destination directory they should be deployed to.

The following files control what files are copied or deleted when you apply an Interim Fix:

a.       IBM_workstation_copy_list.txt – lists the IBM customizable files that are copied to the workstations. For e.g., IBM action XML files. By default, these files are copied to the refresh directory.

b.      IBM_host_copy_list.txt – lists the IBM host modules that need to be transferred to the remote host. For e.g., as, tpfldr, RSE server, etc. By default, these files are copied to the refresh directory.

c.       IBM_delete_list.txt – lists the IBM files that should be deleted. By default, this file is empty.

d.      ENT_workstation_copy_list.txt – lists the enterprise level customizable files that need to be transferred to the workstations. For e.g., enterprise level action XML files. This file is left empty intentionally for your use.

e.       ENT_host_copy_list.txt – lists the enterprise level host files that need to be transferred to the remote host. For e.g., any host modules or executables that you wish to deploy to your users for them to upload to the remote host system. This file is left empty intentionally for your use.

f.        ENT_delete_list.txt – lists the enterprise level files that you wish to delete when a user applies an Interim Fix. For example, you can use this file to delete the PUT level help that you do not need. This file is left intentionally empty for your use.

2.      The Interim Fix update process will migrate all LPEX editor preferences that were persisted outside the workspace to the appropriate location in the workspace. When you restart TPF Toolkit, the LPEX editor will use the migrated preferences in the workspace.

3.      The feature that provides the Administration preference page is now a standalone feature which has to be installed separately. The Administration preference page allows you to control which feature you want to enable or disable in TPF Toolkit. In addition, it also allows you to control the list of action and menu XML files in the Menu Manager configuration files. If you want the Administration preference page to be enabled in TPF Toolkit, follow the step-by-step instructions in the Installing standalone features section to install the TPF Toolkit Administrator feature.

 


9.0 Enhancements and fixes in Interim Fix v2.0.3.1

The following is the list of enhancements and fixes included in Interim Fix v2.0.3.1:

 

9.1 Menu Manager updates

 

1.      In Interim Fix v2.0.3, the option to clear the console when an action is run was removed from the Menu Manager preference page. The option was pushed down to the individual action level so that you could control whether the console was cleared on an action-by-action basis. The global setting to clear the console when an action is run has been re-introduced. You can use the Menu Manager preference page to set the global setting for clearing the console when any action is run. However, you can override this global setting at individual action level.

Note: The action definition files %TPFSHARE%\tpf_base_file_actions.xml and %TPFSHARE%\tpf_file_actions.xml have been modified to remove the clear console option set for each individual action. The absence of the option at the action level will force each action to inherit the global setting by default. Refer to the section Migrating to Interim Fix v2.0.3.1 for more information.

 

9.2 TPFTool command line interface updates

 

1.      The JCL Submit service in TPFTool has been updated to make the user ID information optional.

 

9.3 Interim Fix install process updates

 

1.      The Interim Fix update process has been updated. When you apply an Interim Fix, the Interim Fix update process used to copy your version of the customizable files to a backup directory and install the latest version shipped with the Interim Fix. The process has been updated to place the latest version shipped in any Interim Fix into a directory called refresh under the %TPFHOME% directory, leaving your customized versions untouched. You can then follow the migration instructions outlined in this document to pick up the latest versions of these files.

 

10.0 Enhancements and fixes in Interim Fix v2.0.3

 

The following is the list of enhancements and fixes included in Interim Fix v2.0.3. Refer to the product help for a more detailed description of each individual fix.

 

10.1 IDE updates

 

1.      A new action called Compare has been added that allows you to compare two files. The comparison editor provides a side-by-side content comparison view that makes comparing and merging files intuitive and convenient.

2.      A new action called Create build script has been added that allows you to create a DLM, DLL, or LLM build script from an existing TPF build script file. By default, this action is only enabled for *.bsc files. You can change the action definition using the Menu Manager to enable the action for similar files with a different extension.

3.      The copy and paste commands no longer download and upload a file if the source and destination of the copy and paste are on the same remote host. This results in a significant improvement in performance.

4.      The User Variables and Exits preference page has been enhanced to automatically surround exit programs with double quotes when you browse for a program. The double quotes ensure that program names with spaces can be invoked successfully. You can now specify the parameters to be passed to your exit program separately.

5.      When creating a build script from an existing TPF build script (for example, *.bsc files), the wizard now shows the pre-defined list of configuration files that are defined in the preferences.

6.      The Loadset generation script wizard has been enhanced to use a default data file name based on the file name of the new .lset file.
For example, if you are creating a new loadset generation script called /u/userid/myproject/src/mylset.lset, the data file for storing the loadset inputs defaults to /u/userid/myproject/src/mylset.data.

7.      The Loadset generation build script properties page now preserves the setting for the loadset type (oldr, tldr or aldr).

8.      The Remote Assemble action has been enhanced to capture the return codes from both the ‘as’ tool and the ‘tpfsym’ tool. The return codes are stored in two separate environment variables for you to reference.

9.      You can now use the Menu Manager to set an option to clear the console on an action-by-action basis.

10.  Input dialogs have been updated to allow you to specify multiple inputs, where applicable. The browse dialogs have also been updated to allow you to browse and select multiple inputs. Some examples of such input dialogs are: DLM/DLL/LLM/Loadset input dialog, add filter string dialog, etc.

 

10.2 Editor updates

 

1.      F1 help for selected assembly macros is now case-insensitive.

2.      F1 help is now enabled for custom user assembly macros and custom C/C++ keywords.

3.      If you have contributed customized help pages for assembly macros and C/C++ functions, you can use the Table of Contents (TOC) file from the custom help to enable the F1 help in the editor for these custom keywords instead of manually creating a mapping file.

4.      The syntax in the macro definition file (tpfhlasm.dat) has been simplified.
For example, you can now code the following macro
      TMACC     INPUT=YES|INPUT=NO
in a simpler format as:
      TMACC     INPUT={YES|NO}

5.      The editor now recognizes files with the following extensions:

o       .inl - associated with the C/C++ parser

o       .inc - associated with the SabreTalk parser

o       .incaf - associated with the SabreTalk parser

o       .sabr - associated with the SabreTalk parser

6.      You can now specify a list of LPEX commands to run each time a C/C++ file is opened in the editor.

 

10.3 TPFTool command line interface updates

 

1.      The following new services have been introduced:

o       CreatProject - creates a new project

o       CreateFilter - creates a filter in a specified project

o       CreateFolder - creates a new local or remote folder

o       CreateFile - creates a new local or remote file

o       AddFilterString - adds a filter string to a specified filter

o       Copy - copies local or remote files and folders

o       Upload - uploads a local copy of a remote file to the remote host

o       Download - downloads a remote file to the local workstation

o       Refresh - refreshes a project, filter, folder, or file in the TPF Project Navigator

o       Delete - deletes a file or folder

2.      You can now write your own TPFTool client to submit service requests using XML. For example, you may want o write your own client that runs in a non-Windows environment that will communicate with TPF Toolkit using XML. Refer to the Administering > TPFTool > TPFTool XML input section in the help for detailed information and sample client code.

3.      The JCL Submit service has been enhanced to support submission of a local JCL file.

4.      The TPFTool command line tool now supports user variables as arguments. However, since the ampersand character (&) is a reserved character in Windows, user variables specified as TPFTool command options must be surrounded by the % character instead. For example:
      tpftool -s createProject -p %USR_MYVAR_FOR_PROJECT_NAME%

5.      The TPFTool command line tool now prompts for userid and password information, as required.

 

10.4 Migration tool updates

 

1.      A new option has been introduced that allows you to migrate sub-containers in VisualAge TPF as filters. The default behaviour is to migrate all sub-containers as individual projects.

2.      The sequence number settings in the VisualAge TPF configuration file (bbsproj.cfg) are now correctly migrated using the vatpfmig migration tool.

 

10.5  Help updates

 

1.      When customizing the help, you can now add customized help pages that are hosted on a secure server (https).

2.      You can now search the help with keywords that contain a number.

3.      Several new FAQ entries have been added to the Support Information book in the online help (Support Information > TPF Toolkit support documents > TPF FAQ). These FAQs are also available on the Internet at: http://www.ibm.com/support/search.wss?rs=1068&tc=SSWHWV&dc=DB520&rankprofile=8

4.      Several updates have been made to the online help.

 

 

11.0 Enhancements and fixes in Interim Fix v2.0.2

 

The following fixes and enhancements are included in Interim Fix v2.0.2:

1.      The Remote Assemble action now names the ADATA file after the object file name, instead of the source file name. The loader searches for ADATA files based on the object deck names.

2.      A new preference option has been introduced to run REXEC in a single socket mode. This requires APAR PQ76782 to be applied on the remote z/OS host.

3.      The VATPFMIG migration tool now migrates the container build list that is exported as part of the container information from VisualAge TPF.

4.      On some machines, running the TPFTool command line interface tool resulted in the error message: "The filename, directory name, or volume label syntax is incorrect.". This has now been fixed.

5.      Validation has been added to limit the length of loadset names to a maximum of 8 characters. Additional validation can be switched on to verify that the loadset name is not less than 5 characters.

6.      Running MakeTPF on a single file now only sends the name of the selected file to the maketpf tool, which uses the APPL_ROOT and TPF_ROOT variables in the configuration file (maketpf.cfg) to determine the location of the source file.

7.      Remote commands can now handle user IDs with the # character.

8.      The Remote Compile action no longer fails if build errors are encountered in a PDS.

9.      Individual files can now inherit user variables defined at the parent project level and at the preferences level.

10.  The new DLM Build Script wizard now reads in the CSTRTD in the config file (*.prof) when creating .dlm scripts from existing build scripts (for example, *.bsc).

11.  The Loadset Generation Script File wizard now reads in the configuration file (*.prof) properly.

12.  The TPFTool command line interface now handles JCL submission properly.

13.  The syntax help for the TPFTool command line interface has been reorganized to present the help in the following four categories: Project Related Services, Filter Related Services, File Related Services, and Other Services.

14.  Miscellaneous updates have been made for drag and drop support.

15.  Several new FAQ entries have been added to the Support Information book in the online help (Support Information > TPF Toolkit support documents > TPF FAQ). These FAQs are also available on the Internet at: http://www.ibm.com/support/search.wss?rs=1068&tc=SSWHWV&dc=DB520&rankprofile=8

16.  Several updates have been made to the online help.

 

 

12.0 Enhancements and fixes in Interim Fix v2.0.1

 

The following fixes and enhancements are included in Interim Fix v2.0.1:

 

1.      The Remote Compile and Remote Assemble actions in the RSE perspective for USS files now supports substitution variables specified in the properties pages. Use the Properties panel for USS Files in RSE to set the Remote Compile and Remote Assemble properties.

2.      The CreateProject service for the TPFtool command line interface now invokes the project creation user exit, if specified. Use the User Variables and Exits preferences page (Window > Preferences > TPF Toolkit > User Variables and Exits) to set the project creation user exit.

3.      TPFpass password maintenance command line interface now support workspace location with spaces.

4.      The project build action using the MakeTPF build solution did not work if the remote build system is accessed via NFS or SMB mounts. This has now been fixed.

5.      Using the TPF Toolkit preferences pages, you can specify a default JCL file to submit when you build your project using the JCL Submit build mechanism. You can also specify a specific JCL file to use on a per project basis. However, when you build the project, it was always using the default JCL file specified in the preferences page. This has now been fixed. Each project now uses its customized JCL file, if one is specified.

6.      TPF Toolkit now supports dynamic stub generation for the MakeTPF build solution.

7.      When you specify the user exits in the User Variables and Exits preferences page, you could not specify additional parameters for the user exit programs, if the parameters had path information. For example, you could not specify 'C:\temp\my user exit program C:\this\is\my\additional\parameter\that\looks\like\a\path'. This has now been fixed. In addition, you can now also specify user variables (USR_XXX) as parameters for your user exits.

8.      When you work remotely over VPN or a dial-up connection, TPF Toolkit may not be able to query the secure (or tunneled) IP address associated with your workstation. The JCL Submit action requires the secure IP address to the send the job status information back to the workstation. Using the TPF Toolkit preferences page, you can now specify the secure IP address you want to use, which will be picked up by the JCL Submit action.

9.      If you specified multiple filter strings for your TPF project filter and one of them happened to be unresolvable, none of the other filter strings in that filter are resolved when the filter is expanded. This has now been fixed. A message is displayed in the TPF Console to indicate which filter string(s) could not be resolved.

10.  The Remote Assemble action assumed that the ASMAOPT value was always a PDS, which is not the case. This has now been fixed. The action now determines whether the value specified is a PDS or an HFS location and sends the appropriate information to the compiler.

11.  Several FAQ entries have been added in this interim fix. To view the FAQ entries, go to Support Information > TPF Toolkit support documents > TPF FAQ in the online help.

12.  Several updates have been made to the online help.

 

 

13.0 Migrating to the latest Interim Fix

 

Updated versions of customizable files may be shipped in an Interim Fix. If you have not changed any of the updated customizable files, you can simply copy the latest version of these files to the corresponding location under the %TPFHOME%\Config directory.

Note: If the same file has been updated in more than one Interim Fix, only the latest version of this file is shipped.

When you apply an Interim Fix, all of the changed customizable files (including the ones from all previous Interim Fixes) are installed under the %TPFHOME%\refresh directory. The names of the sub-directories indicate the Interim Fix level at which the files were changed. Since Interim Fixes are cumulative, you do not need to install all the intermediate Interim Fixes, but you do need to merge all the configuration files that were changed in each of the intermediate Interim Fixes that you skipped.

 

Example 1: If you are applying Interim Fix v2.0.3 on top of a v2.0.0 installation, you will need to merge all the files that have changed between v2.0.0 and v2.0.3. This includes all the files in the following directories:

            \refresh\Changed in 2.0.2

            \refresh\ Changed in 2.0.3

Note: No customizable files were changed in v2.0.1

Example 2: If you had previously applied Interim Fix v2.0.2, you only need to handle the files that have changed since Interim Fix v2.0.3. This includes all the files in the following directory:

            \refresh\Changed in 2.0.3

Note: No customizable files were changed in v2.0.3.1

 

13.1 Migrating to Interim Fix v2.0.10

 

 

No configuration files or host modules were changed in Interim Fix v2.0.10.

Note: If you skipped Interim Fix v2.0.8, you must follow the instructions in the Migrating to Interim Fix v2.0.8 section to pick up the configuration changes made in Interim Fix v2.0.8.

 

 

13.2 Migrating to Interim Fix v2.0.9

 

 

Interim Fix v2.0.9 was intentionally skipped.

 

13.3 Migrating to Interim Fix v2.0.8

 

 

The RSE server has been updated. The updated version of the server is copied to the %TPFHOME%\refresh directory when you install the Interim Fix. To update your RSE server on USS, do the following:

1.      Ftp the tar ball %TPFHOME%\refresh\Changed in 2.0.8\Config\host\dstore.zos.tar as binary to your USS host.

2.      From a command prompt, type tar -xvfo dstore.zos.tar to untar the tar ball on the USS host. A directory called dstore is created containing the files required to start the RSE host server.

Note:   It is recommended that you place one copy of the dstore directory on USS in a public location that all users can access through the PATH environment variable. Enable the read and execute permissions for all files contained in this directory (and the directory itself) to allow all users to access these files.

3.      Configure the setup.env.zseries file (located in the dstore directory), and update the JAVA_HOME variable to point to the location of the Java™ 1.3 runtime directory.

 

 

 

Note: If you skipped Interim Fix v2.0.7, you must follow the instructions in the Migrating to Interim Fix v2.0.7 section to pick up the configuration changes made in Interim Fix v2.0.7.

 

 

13.4 Migrating to Interim Fix v2.0.7

 

 

The following TPFSHARE configuration files have been updated. The updated version of these files are copied to the %TPFHOME%\refresh\Changed in 2.0.7 directory when you install the Interim Fix. If you customized these files, merge the refreshed copy with your current copies in TPFSHARE.

 

File name

What was changed

tpfhlasm.dat

The GETCC macro definition was changed.

tpf_file_actions.xml

The ‘Analyze Trace’ action was added as a generic menu action for .trc files.

 

 

The RSE server has been updated. The updated version of the server is copied to the %TPFHOME%\refresh directory when you install the Interim Fix. To update your RSE server on USS, do the following:

4.      Ftp the tar ball %TPFHOME%\refresh\Changed in 2.0.7\Config\host\dstore.zos.tar as binary to your USS host.

Note:  The dstore.zos.tar file was also changed in Interim Fix v2.0.8.  Use the latest version in Interim Fix v2.0.8.


5.      At a command prompt, type tar -xvfo dstore.zos.tar to untar the tar ball on the USS host. A directory called dstore is created containing the files required to start the RSE host server.

Note: It is recommended that you place one copy of the dstore directory on USS in a public location that all users can access through the PATH environment variable. Enable the read and execute permissions for all files contained in this directory (and the directory itself) to allow all users to access these files.

6.      Configure the setup.env.zseries file (located in the dstore directory), and update the JAVA_HOME variable to point to the location of the Java™ 1.3 runtime directory.

 

 

 

Note: If you skipped Interim Fix v2.0.6, you must follow the instructions in the Migrating to Interim Fix v2.0.6 section to pick up the configuration changes made in Interim Fix v2.0.6.

 

 

 

13.5 Migrating to Interim Fix v2.0.6

 

The following TPFSHARE configuration files have been updated. The updated version of these files will be copied to the %TPFHOME%\refresh\Changed in 2.0.6 directory when you install the Interim Fix. If you have customized these files, you need to merge the refreshed copy with your current one in TPFSHARE.

 

File name

What was changed

Comments

tpfhlasm.dat

PUT 18 macro definitions were added.

This file was updated in Interim Fix v2.0.7.  Use the latest version in Interim Fix v2.0.7

 

 

 

Note: If you skipped Interim Fix v2.0.5, you must follow the instructions in the Migrating to Interim Fix v2.0.5 section to pick up the configuration changes made in Interim Fix v2.0.5.

 

 

13.6 Migrating to Interim Fix v2.0.5

 

No configurations files or host modules were changed in Interim Fix v2.0.5.

 

Note: If you skipped Interim Fix v2.0.4.1, you need to also follow the instructions in the section Migrating to Interim Fix v2.0.4.1 to pick up the configuration changes made in Interim Fix v2.0.4.1.

 

13.7 Migrating to Interim Fix v2.0.4.1

 

No configurations files or host modules were changed in Interim Fix v2.0.4.1.

 

Note: If you skipped Interim Fix v2.0.4, you need to also follow the instructions in the section Migrating to Interim Fix v2.0.4 to pick up the configuration changes made in Interim Fix v2.0.4.

 

 

13.8 Migrating to Interim Fix v2.0.4

 

This section lists the configuration files that have changed in Interim Fix v2.0.4 and the instructions on how to pick up the changes.

 

Note: If you skipped Interim Fix v2.0.3.1, you need to also follow the instructions in the section Migrating to Interim Fix v2.0.3.1 to pick up the configuration changes made in Interim Fix v2.0.3.1

 

The following host modules have been updated. The updated version of these files will be copied to %TPFHOME%\refresh\Changed in 2.0.4 directory when you install the Interim Fix. Upload these files in binary mode to your z/OS host.

 

File name

TPFLOAD        

tpfldr   

 

 

13.9 Migrating to Interim Fix v2.0.3.1

 

This section lists the configuration files that have changed in Interim Fix v2.0.3.1 and the instructions on how to pick up the changes.

 

Note: If you skipped Interim Fix v2.0.3, you need to also follow the instructions in the section Migrating to Interim Fix v2.0.3 to pick up the configuration changes made in Interim Fix v2.0.3.

 

The following TPFSHARE configuration files have been updated. The updated version of these files will be copied to the %TPFHOME%\refresh\Changed in 2.0.3.1 directory when you install the Interim Fix. If you have customized these files, you need to merge the refreshed copy with your current one in TPFSHARE.

 

File name

What was changed

Comments

tpf_base_file_actions.xml

The option to clear console for individual actions was cleared so that each action will use the global clear console setting by default.

 

 

tpf_file_actions.xml

The option to clear console for individual actions was cleared so that each action will use the global clear console setting by default.


This file was also updated in Interim Fix v2.0.7.  Use the latest version in v2.0.7.

 

 

 

13.10 Migrating to Interim Fix v2.0.3

 

This section lists the configuration files that have changed in Interim Fix v2.0.3 and the instructions on how to pick up the changes.

 

Note: If you previously applied Interim Fix v2.0.3 and picked up all the configuration changes, you do not need to apply the changes recommended in this section. If you skipped Interim Fix v2.0.3, you need to complete the following instructions to pick up the configuration changes made in Interim Fix v2.0.3.

 

Note: If you skipped Interim Fix v2.0.2, you need to also follow the instructions in the section Migrating to Interim Fix v2.0.2 to pick up the configuration changes made in Interim Fix v2.0.2.

 

The following TPFSHARE configuration files have been updated. The updated version of these files will be copied to the %TPFHOME%\refresh\Changed in 2.0.3 directory when you install the Interim Fix. If you have customized these files, you need to merge the refreshed copy with your current one in TPFSHARE.

 

File name

What was changed

Comments

tpf_base_file_actions.xml

·        New action called Compare has been added

This file was also updated in Interim Fix v2.0.3.1. Use the latest version in Interim Fix v2.0.3.1

tpf_file_actions.xml

·        New action called Create build script has been added

·        All remote action definitions have been updated to surround the export variables in single quotes

This file was also updated in Interim Fix v2.0.7. Use the latest version in Interim Fix v2.0.7

tpf_remote_actions.xml

All remote action definitions have been updated to surround the export variables in single quotes

 

 

The following host modules have been updated. The updated version of these files will be copied to %TPFHOME%\refresh\Changed in 2.0.3 directory when you install the Interim Fix. Upload these files in binary mode to your z/OS host.

 

File name

ld              

 

The RSE server has been updated. The updated version of the server will be copied to the %TPFHOME%\refresh directory when you install the Interim Fix. To update your RSE server on USS, do the following:

7.      Ftp the tar ball %TPFHOME%\refresh\Changed in 2.0.3\Config\host\dstore.zos.tar as binary to your USS host.

Note:  The dstore.zos.tar file was also changed in Interim Fix v2.0.8.  Use the latest version in Interim Fix v2.0.8.

8.      At a command prompt, type tar -xvfo dstore.zos.tar to untar the tar ball on the USS host. A directory called dstore is created containing the files required to start the RSE host server.

Note: It is recommended that you place one copy of the dstore directory on USS in a public location that all users can access through the PATH environment variable. Enable the read and execute permissions for all files contained in this directory (and the directory itself) to allow all users to access these files.

9.      Configure the setup.env.zseries file (located in the dstore directory), and update the JAVA_HOME variable to point to the location of the Java™ 1.3 runtime directory.

 

 

13.11 Migrating to Interim Fix v2.0.2

 

This section lists the configuration files that have changed in Interim Fix v2.0.2 and the instructions on how to pick up the changes.

 

Note: If you previously applied Interim Fix v2.0.2 and picked up all the configuration changes, you do not need to apply the changes recommended in this section. If you skipped Interim Fix v2.0.2, you need to complete the following instructions to pick up the configuration changes made in Interim Fix v2.0.2.

 

The following host modules have been updated. The updated version of these files will be copied to %TPFHOME%\refresh\Changed in 2.0.2 directory when you install the Interim Fix. Upload these files in binary mode to your z/OS host.

 

File name

Comments

libi

 

lmcp

 

ld          

This module was also updated in Interim Fix v2.0.3. Use the latest version in Interim Fix v2.0.3.

tpfldr

This module was also updated in Interim Fix v2.0.4. Use the latest version in Interim Fix v2.0.4.

as           

 

DLLLOAD

 

TPFLOAD  

This module was also updated in Interim Fix v2.0.4. Use the latest version in Interim Fix v2.0.4.

DLMLOAD            

 

LLMLOAD  

 

 

 

13.12 Migrating to Interim Fix v2.0.1

 

No configuration files or host modules were changed in Interim Fix v2.0.1.

 

 

14.0 Installing the latest Interim Fix

 

Use the Update Manager included in TPF Toolkit for WebSphere Studio to find and install the latest Interim Fix.  Follow these instructions to apply the latest Interim Fix.

 

1.      Click Help > Software Updates > New Updates. This will contact the web sites associated with the product’s features to discover what versions of those features are available. The potential upgrades are presented in an Available Updates page.

2.      Select the feature versions that you wish to upgrade, and click Next.
Tip: Click More Info to view the list of fixes.

3.      Carefully review the license agreements for the upgraded features. If the terms of all of these licenses are acceptable, select the I accept the terms in the license agreements check box and click Next. Do not proceed to download the features if the license terms are not acceptable.

4.      Feature versions can be digitally signed by the company that provides them. This allows the user to more easily verify that the features and plug-ins that are about to be downloaded and installed are coming from a trusted supplier.
Warning: Because of the possibility of harmful or even malicious plug-ins, you should only download features from parties that you trust.
The digital signature for IBM TPF Toolkit for WebSphere Studio is not yet available, so the Interim Fix appears as unsigned. Click Install to allow the downloading and installing to proceed.

5.      Once all of the features and plug-ins have been downloaded successfully and their files installed into the product on the local computer, a new configuration that incorporates these features and plug-ins will be formulated. Click Yes when asked to exit and restart the Workbench for the changes to take effect.

6.      If you want to install additional standalone features, refer to Installing standalone features.

 

 

15.0 Installing standalone features

 

Note: You can install the standalone feature if you have installed Interim Fix v2.0.4 or higher. Refer to Installing the latest Interim Fix for step-by-step instructions on how to apply the latest Interim Fix.

 

TPF Toolkit Administrator feature is now shipped as a standalone feature. The TPF Toolkit Administrator feature enables the Administration preference page in TPF Toolkit. The Administration preference page allows you to control which feature you want to enable or disable in TPF Toolkit. In addition, it also allows you to control the list of action and menu XML files in the Menu Manager configuration files.

 

The various TPF PUT level specific documentation is also shipped as standalone features. To display PUT level specific documentation in the online help, install the PUT level documentation feature of your choice.

 

Follow these instructions to install the standalone feature.

 

1.      Click Help > Software Updates > Update Manager to open the Install/Update perspective.

2.      In the Features Updates view, expand the Sites to Visit node.

3.      Expand the TPF Toolkit Standalone Features node.

4.      Expand and select the feature you want to install. Information about the feature appears in the Preview pane.

5.      Click Install Now to install the feature.

6.      The Feature Install Wizard confirms the details of the feature you are about to install. Click Next.

7.      Carefully review the license agreements for the upgraded features. If the terms of all of these licenses are acceptable, select the I accept the terms in the license agreements check box and click Next. Do not proceed to download the features if the license terms are not acceptable.

8.      Click Finish to allow the downloading and installing to proceed.

9.      Feature versions can be digitally signed by the company that provides them. This allows the user to more easily verify that the features and plug-ins that are about to be downloaded and installed are coming from a trusted supplier.
Warning: Because of the possibility of harmful or even malicious plug-ins, you should only download features from parties that you trust.
The digital signature for TPF Toolkit Administration feature is not yet available, so the feature appears as unsigned. Click Install to allow the downloading and installing to proceed.

10.  Once all of the features and plug-ins have been downloaded successfully and their files installed into the product on the local computer, a new configuration that incorporates these features and plug-ins will be formulated. Click Yes when asked to exit and restart the Workbench for the changes to take effect.