Readme

This readme file provides late-breaking information and other information that supplements the online help for VisualAge PL/I, Refresh V2.1.12.

For more information about VisualAge PL/I Refresh V2.1.12, refer to the IBM PL/I Web site.

IBM PL/I Refresh V2.1.12 Enhancements/Fixes - July 2004

Refresh V2.1.12 combines the enhancements and changes in FixPak #11, FixPak #10, FixPak #9, FixPak #8, FixPak #7, FixPak #6, FixPak #5, FixPak #4, FixPak #3, FixPak #2 and CSD #1.

Installation information

VisualAge PL/I Component Updates

This file provides information about changes made for Version 2.1.12, Version 2.1.11 and Version 2.1.10 of VisualAge PL/I. It also describes changes to prerequisites, and known problems and limitations.

Changes in Version 2.1.12

VisualAge PL/I component Change
Foreign File System (FFS) For the FFS client, we have made several fixes, including:
  • Previously, when a user incorrectly attempted to read or write to a RECFM=U data set, FFS kept the data set allocated. This problem is now fixed.
  • Previously, the FFS server sometimes terminated when it read a large file. This problem is now fixed.
Job Monitor For Job Monitor, we have made several fixes, including:
  • Previously, Job Monitor issued OC4 abends when you tried to look at the spool data sets of a currently running job. This problem is now fixed.
  • Even though the documentation for the Job Monitor server says not to change the workstation code page value from UTF-8, the UTF-8 code page might not correctly reflect incoming ASCII text that contains NLS characters above x'7F', such as the British pound sterling. In that case, change the value CODEPAGE=UTF-8 to something like CODEPAGE=IBM-1252 in the Job Monitor configuration file.
  • Job Monitor restricts the use of CANCEL, HOLD, PURGE, and RELEASE to jobs for which you are the owner. This restriction was previously undocumented.

Changes in Version 2.1.10

VisualAge PL/I component Change
Foreign File System (FFS) For the FFS client, we have made several fixes, including:
  • FFS now tolerates a wider latitude in network configuration when it tries to connect to a host system. Previously, in certain circumstances, FFS would try only one of the gethost functions (gethostbyaddr or gethostbyname) before reporting a failure to connect.  Now it will always try both functions before reporting a failure.
  • Previously, in certain cases when you copied multiple files using a wildcard character from the host to the workstation, the copy ended prematurely without issuing an error. That is, the COPY command behaved as if it had copied all of the requested files when it had not.  This problem is now fixed.
  • Directories no longer fail to refresh after a failure to create a new file in that directory (such as attempting to copy a file with the wrong file extension into an MVS "directory" or PDS).
Foreign File System (FFS) and TSO Commands For the FFS server, PTF IP22587 provides several fixes. After the PTF is installed, the system programmer must make some changes to ensure that the TSO command server continues to work.

The TSO command server no longer requires the host COBOL or PL/I product.  Two new parts are now included in the PTF:

  • The sample JCL FBNFTPAD replaces IGYFTPAD (or IBMFTPAD).  FBNFTPAD has also been enhanced to include an example showing how to enable non-interactive ISPEXEC commands by using TSO commands.
  • The transaction FBNFSERV replaces IGYFSERV (or IBMFSERV)

Rename the APPC transaction IGYFSERV to FBNFSERV (or you can use FBNFTPAD plus any modifications that you have made to IGYFTPAD to create a new transaction named FBNFSERV).

Job Monitor For Job Monitor, we have made several fixes, including:
  • Job Monitor can now work on workstations that use firewalls to block incoming connections in the ephemeral port range. This feature changed both the workstation and host code. If you apply the changes to only the host, old versions of the workstation code will still function correctly. If you apply the changes to only the workstation, old versions of the host code will reject the connection, and the workstation code will fail with the message "Connection closed by server."
  • In z/OS 1.2, job identifiers changed from JOBnnnnn to Jnnnnnnn.  The Job Monitor Hold, Purge, Cancel, and Release functions were changed to recognize the new format of the job identifiers.
MVS Connections Manager Two additional EBCDIC Japanese code pages are now supported: IBM-1390 and IBM-1399. For them to be recognized, add them manually in the MVS Connection Manager. The identifiers of the code pages are case sensitive.
Program Editor There have been several fixes, including:
  • When you use Save as... to save a host file, the ISPF-style lock on the old file is released, and a new ISPF-style lock is obtained on the new file.
  • When Key behavior --> ISPF is selected, the tab key now behaves in the same way as the host tab key; that is, the cursor jumps to the line numbers, then to the first column of text, then to the next row of line numbers, and so forth.
Project window (Workframe) We have made several fixes, including:
  • MVS directories that are displayed in a project window no longer fail to refresh after files have been created or deleted
  • An erroneous "no connection to host" message is no longer displayed when you create MVS projects on Windows 2000.
  • The help for the Tools Setup window has been improved.
  • You can now delete projects from the IBM VisualAge COBOL Projects window.
  • An hourglass mouse cursor is now displayed when a monitored action, such as a compile or build, is running. When the action completes, the workframe display is auto-refreshed.
IBM Distributed Debugger
  • Previously, the debugger was displaying incorrect characters instead of Kanji characters when Kanji business terms were used for data-names. This problem is now fixed.
  • Previously, when message MSGIWZ200S was displayed on a Japanese machine, its text was in incorrect characters and not the correct Kanji and Hiragana characters. The error occurred only on an OPEN verb. This problem is now fixed.

Changes to prerequisites for VisualAge PL/I V2.1.12

The following table summarizes the additional or changed requirements for the use of remote edit-compile-debug in Version 2.1.12.
Prerequisite product or component Requirement or change
Foreign File System server PTF IP22663 supersedes all previous FFS PTFs.
IBM Enterprise PL/I for z/OS and OS/390 Version 3 Release 2 With the installation of the new version of FFS that is provided with VisualAge PL/I 2.1.12 and the application of FFS PTF IP22663, there is no requirement for an additional Enterprise PL/I for z/OS and OS/390 PTF for the TSO Commands Server as in previous fixpaks.
IBM VisualAge PL/I for OS/390 Version 2 Release 2 With the installation of the new version of FFS that is provided with VisualAge PL/I 2.1.12 and the application of FFS PTF IP22663, there is no requirement for an additional VisualAge PL/I for OS/390 PTF for the TSO Commands Server as in previous fixpaks.

Changes to prerequisites for VisualAge PL/I V2.1.10

The following table summarizes the additional or changed requirements for the use of remote edit-compile-debug in Version 2.1.10.
Prerequisite product or component Requirement or change
Job Monitor Using JES2 and viewing the spool data sets of a running job using Job Monitor requires the following OS/390 Version 2 Release 10 APARs: OW49317 and OW49373. (Viewing the spool data sets of a running job is not supported prior to OS/390 Version 2 Release 10.)
IBM Enterprise PL/I for z/OS and OS/390 Version 3 Release 1 With the installation of the new version of FFS that is provided with VisualAge PL/I 2.1.10 and the application of FFS PTF IP22589, there is no requirement for an additional Enterprise PL/I for z/OS and OS/390 PTF for the TSO Commands Server as in previous fixpaks.
IBM VisualAge PL/I for OS/390 Version 2 Release 2 With the installation of the new version of FFS that is provided with VisualAge PL/I 2.1.10 and the application of FFS PTF IP22589, there is no requirement for an additional VisualAge PL/I for OS/390 PTF for the TSO Commands Server as in previous fixpaks.

Known problems and limitations

There are known problems and limitations for the following components: foreign file system (FFS), MVS connections manager, debugger, program editor, REXX product environment,project environment, PL/I projects, SOM compiler, and Information Center.

Foreign file system (FFS)

Problem or limitation Solution (if applicable)
You may need more information if you encounter problems while trying to access MVS files. For additional information about a problem, view the ffsuser.log file in WINNT\Profiles\userid\Application Data\IBM\FFS, where userid is your Windows user ID.
During system startup, an error may occur when your system tries to restore a network connection to the FFS server. Click OK and connect to the FFS server after system startup has finished.

MVS connections manager

Problem or limitation Solution (if applicable)
If you are using a version of Netscape earlier than 4.7 and you have opened the Information Center, and you attempt to open the Information Center again from the MVS connections manager, the following error may occur: Smart Browsing was unable to match your request. Click the X button at the far right of the title bar to close the second browser window, and use the first browser window instead. Or, you can download and install Netscape 4.7 to avoid the problem.

Distributed Debugger

Problem or limitation Solution (if applicable)
When you remotely debug an OS/390 PL/I program that contains graphic variables, an error may occur when you try to change the value of the variable in the Program Monitor. To change the value of a graphic variable for debugging, do the following:

1. Double-click the graphics variable in the Source pane. Right-click the variable and select Add to Program Monitor.

2. Double-click the value in the Monitors pane.

3. Remove the old value completely and then enter the new one.

4. Add a G in front of the first single quote (for example, G'X Y Z ') to indicate that this is a graphic value. Press Enter.

You may see some unexpected behavior if your program contains unprintable data. An unprintable character appears in the debugger as a box. Here are some examples of unexpected behavior: 

- If a statement in the program contains a literal string with unprintable characters, you may not be able to highlight variables in that statement.

- If you try to edit the value of a variable that contains unprintable data, the boxes are replaced by the tilde character. 

- You may not be able to see the end of a long string.

None
The Distributed Debugger shipped with VisualAge PL/I does not support debugging AS/400 applications. None
When you install products (such as VisualAge PL/I) that install the Distributed Debugger on your workstation, and then you uninstall those products, the Distributed Debugger does not uninstall. Check your workstation registry to ensure no products that use the Distributed Debugger are installed. Next, change the RefCount number in your workstation registry to 1. Finally, uninstall the Distributed Debugger. 

To check your workstation registry to ensure that no parent products are installed, do these steps: 

  1. Click Start -> Run, type regedit, and click OK. The Registry Editor opens.
  2. Double-click the following folders:
    HKEY_LOCAL_MACHINE
    SOFTWARE
    IBM
    IBM Distributed Debugger
    CurrentVersion
    install
    ParentProducts
  3. Check for parent products. If no parent product is installed, proceed to the next step. If a parent product is installed, do not uninstall the Distributed Debugger.
To decrement the RefCount in the workstation registry, do these steps:
  1. Double-click the install folder again.
  2. Right-click RefCount and select Modify.
  3. Change the number to 1 and click OK.
To uninstall the Distributed Debugger, do these steps: 
  1. Click Start -> Settings -> Control Panel.
  2. Click the Add/Remove Programs icon.
  3. On the Install/Uninstall page, click IBM Distributed Debugger in the list of installed products, then click OK.
  4. Shut down and reboot your workstation.

Program editor

Problem or limitation Solution (if applicable)
You may need more information if you encounter problems while using the program editor (LPEX). For additional information about a problem, view the editor's macro log. To get to the macro log, click Windows -> Macro log.
If you use Notepad and Wordpad to edit an MVS file, the file is not locked during the edit session. Similarly, if you invoke the program editor (LPEX) from the start menu, or in any way other than selecting MVS Edit from a project, the file is not locked during the edit session. To lock (ISPF style) an MVS file during an edit session, right-click the file in the project window and then select MVS edit
If you installed VisualAge PL/I as a client connected to a network server, you may not be able to change key behavior in the program editor. To correct this problem, do these steps:

1. Right-click the My Computer icon and select Properties

2. Click the Environment tab.

3. In the User Variables section, add the variable PLILPATH4 and give it a value that includes the client's MACROS directory for VisualAge PL/I. For example, if the VisualAge PL/I client portion is installed in c:\Ibmpliw, then the value of the new PLILPATH4 variable would be C:\IBMPLIW\MACROS;%PLILPATH4%.

Or, if you have administrator authority on the client workstation, you can add the client's MACROS directory path in front of the existing value for the PLILPATH4 variable in the System Variables section.

4. Click Apply and then click OK.

If you installed VisualAge PL/I as a client connected to a network server, F1 help will not be available in the program editor. None

REXX Product environment

Problem or limitation Solution (if applicable)
When you install other products that also provide REXX runtime files, the mix of files from different REXX versions can lead to an unstable REXX environment. Two REXX rename utilities have been added to the IBM VisualAge PL/I install image. These utilities are originally from the IBM VisualAge COBOL product but are still useful in correcting the REXX problem in an IBM VisualAge PL/I environment.

The two utilities can be found in the \service directory and are named:

  1. IWZFREXX.EXE
    This utility is run first. It will search your hard drives and find all of your REXX installations. It then presents you with four choices:
    1. "Use the REXX installation from VA COBOL (Recommended, but may break other programs)."
      This option should not be chosen when in an IBM VisualAge PL/I environment. It looks for COBOL-specific information and will return an error.
    2. "Use the REXX files with the most recent date."
      Choose this option to use the most recent REXX environment installed on your machine. It generates a report file that can be used by the IWZUREXX.EXE utility to undo the changes made to your system.
    3. "List the most recent files that will be used."
      Choose this option to list the files that would be used if Option 2 were chosen.
    4. "Exit without making an changes."
      Choose this option if you wish to do nothing. It generates a report that lists all of the REXX files from all the REXX installations on your hard drives. This report would be useful should you decide to do the selecting and renaming of the REXX files by hand.

  2. IWZUREXX.EXE
    This utility will undo the changes that were made if Option 2 from the IWZFREXX.EXE utility were chosen. It requires the generated report file from Option 2 as input.


Project environment

Problem or limitation Solution (if applicable)
When you add a new tool using Actions -> Tools Setup in the IBM VisualAge PL/I Projects window, you cannot specify the ToolGroup to which the new tool belongs. Without a ToolGroup, the tool will not be available to the project. To specify a ToolGroup for a newly added tool (making the tool available to a project), look in the project's definition file for the ToolGroup that is associated with the project. Add that ToolGroup to the tool definition in the solution configuration file. For detailed instructions, follow these steps:

1. Click Start -> Programs -> IBM VisualAge PL/I -> IBM VisualAge PL/I Projects.

2. In the list of projects, find the project that you want to make the new tool available to. Write down the entire directory path, followed by the project name, followed by .iwp. For example, c:\winnt\profiles\longwell\application data\ibm\vapli\projects\test.iwp, where test is the project name and test.iwp is the name of the project definition file.

3. Click Start -> Programs -> IBM VisualAge PL/I -> Tools -> Program Editor. In the Editor window, open the definition file for the project, using the information that you wrote down in the previous step.

4. In the project definition file, find the +toolGroup= key and its value (for example, +toolGroup=mvs). This value is the name of the ToolGroup to which the new tool must belong if it is to be available to the project.

5. In the Editor window, open the solution configuration file VAPLIV3.IWS, which is typically in the c:\WINNT\Profiles\username\Application Data\IBM\VAPLI\MainPrj folder.

6. Make a copy of VAPLIV3.IWS to safeguard against errors.

7. In VAPLIV3.IWS, find the definition of the tool that you added (the +title= key will match the name you gave the tool).

8. Add a line in the body of the tool definition, and enter the +toolGroup=  key and the value that you found in step 4 above (for example, +toolGroup=mvs). Save and close the file. If a +toolGroup statement already exists but the value does not match the value you found in step 4 above, you can add your value after the existing value, separating the values with a blank (for example, +toolGroup=ws mvs).

9. Close the IBM VisualAge PL/I Projects window, if it is still open.

PL/I projects

Problem or limitation Solution (if applicable)
When you click Start -> Programs -> IBM VisualAge PL/I -> IBM VisualAge PL/I Projects, your monitor screen may appear to flicker or lose its vertical synchronization. Change either the color palette or refresh frequency settings for your monitor. To change these settings, do these steps:

1. Right-click your desktop. Click Properties.

2. Click the Settings tab. 

3. Decrease the number of colors or the refresh frequency. Click OK.

The PLI_Projects folder is not automatically created on your desktop when you create a project, contrary to several places in the online help that describe the creation of a PLI_Projects folder on the desktop as the default behavior. If you prefer, you can access your PL/I projects from your desktop rather than from the Start menu. To do so, follow these steps:

1. Click Start -> IBM VisualAge PL/I -> IBM VisualAge PL/I Projects.

2. Click the Create New Project tab.

3. Enter the information requested until you are prompted to specify the location and name of the folder that will hold your project definition files.

4. Click the Browse button to the right of the input field.

5. Click c:\WINNT\Profiles\<user name>\Desktop.

6. Click the Create a new folder icon in the upper right corner of the Browse for a Project Definition File Folder window.

7. Enter PLI_Projects as the name of the new folder and press Enter. Click OK to close the window. Click Yes if prompted to create the folder. Click OK when prompted to accept the new default path.

8. Click Finish. The PLI_Projects folder is created on your desktop.

Job Monitor

Problem or limitation Solution (if applicable)
If you close the JobMonitor without having moved the split-bar, you may find that the next time JobMonitor is opened, the split-bar has moved to the far left. None