Readme File for WebSphere Studio Enterprise Developer 5.0 EA Fix Pack 2

This document pertains to Fix Pack 2 for the early availability (EA) release of WebSphere Studio Enterprise Developer 5.0. The document contains the following information:

1. Product overview
2. Installing Enterprise Developer
3. Launching the workbench
4. Known problems and limitations
5. Problems fixed
6. Other updates and fixes
7. Where to find more information

1. Product overview

WebSphere Studio Enterprise Developer adds the following features to WebSphere Studio Application Developer:

• Struts tools
• Enterprise Generation Language
• z/OS application development tools
• XML enablement for the enterprise

For more information, see the WebSphere Studio Enterprise Developer 5.0 EA Readme File.

2. Installing Enterprise Developer

This section explains how to recover information lost during installation interrupted on a workstation and how to install Fix FIXPAK2 on a host system. For other information about installing Enterprise Developer, see the IBM WebSphere Studio Enterprise Developer Installation Guide.

2.1 Recovering from interrupted workstation installation

If the installation of Enterprise Developer Disk 2 is interrupted, information may be lost from your PATH environment variable. If this happens, see the WSEDoldPath variable. It will contain the value that PATH had before installation began.

2.2 Installing Fix FIXPAK1 on a host system

Before you install Fix FIXPAK1 on a host system, you need to install the FMID HEDS500 and configure the base product. FIXPAK1 is shipped as file HEDS500\IBM.HEDS500.FIXPAK1. The steps required to install the fix are as follows:

1. Allocate a data set for the fix.
2. Upload the fix from your workstation.
3. Run SMP/E RECEIVE and APPLY.

2.2.1 Allocate a data set for the fix

A sequential data set must be allocated on the z/OS system for the fix that you will upload from your workstation. You can do this by submitting the job shown below. Before you submit the job, add a job card and modify the parameters to meet your site's requirements.

//ALLOC1    EXEC   PGM=IEFBR14
//*
//FTPALLO  DD  DSN=hlq.IBM.HEDS500.FIXPAK1,
//         DISP=(NEW,CATLG,DELETE),
//         DSORG=PS,
//         RECFM=FB,
//         LRECL=80,
//         BLKSIZE=6160,
//         SPACE=(TRK,(4,2)),
//         UNIT=SYSALLDA

2.2.2 Upload the fix from your workstation

Upload the file in binary format from your workstation to the z/OS data set. On a Windows system, you can use FTP from a command prompt to upload the file. In the sample dialog shown below, bold text indicates user input, nonbold text indicates a system response, and italic text indicates variable values, as shown in the following table:

C:\>ftp mvsaddr
Connected to mvsaddr.
220-FTPD1 IBM FTP CS V2R8 at mvsaddr, 08:43:52 on 2002-11-15.
220 Connection will close if idle for more than 60 minutes.

User (mvsaddr:(none)): tsouid

331 Send password please.
Password: tsopw
230 tsouid is logged on.  Working directory is "tsouid.".

ftp> cd ..
250 "" is the working directory name prefix.

ftp> cd hlq
250 "hlq." is the working directory name prefix.

ftp> binary
200 Representation type is Image

ftp> put d:\dir\HEDS500\IBM.HEDS500.FIXPAK1 IBM.HEDS500.FIXPAK1
200 Port request OK.
125 Storing data set hlq.IBM.HEDS500.FIXPAK1
250 Transfer completed successfully.
1134400 bytes sent in .93 seconds (1218.47 Kbytes/sec)

ftp> quit
221 Quit command received. Goodbye.

2.2.3 Run SMP/E RECEIVE and APPLY

Run the SMP/E RECEIVE and APPLY commands on the fix as usual.

3. Launching the workbench

After installation, we recommend that you start the workbench from the Windows Start menu: Click Start > Programs > IBM WebSphere Studio Enterprise Developer.

For more information, see the WebSphere Studio Enterprise Developer 5.0 EA Readme File .

4. Known problems and limitations

4.1 General

See the WebSphere Studio Enterprise Developer 5.0 EA Readme File .

4.2 Struts tools

See the WebSphere Studio Enterprise Developer 5.0 EA Readme File .

4.3 Enterprise Generation Language

See the WebSphere Studio Enterprise Developer 5.0 EA Readme File .

4.4 z/OS application development tools

This section describes known problems and limitations that pertain to the z/OS application development tools.

4.4.1 Installing z/OS host components

When you install the z/OS host components needed to support Enterprise Developer, if you are using the z/OS application development tools, you need to install PTF IP22615 for the Foreign File Server (FFS). PTF IP22615 supersedes IP22527, whose code is on CD 4 for Release 5.0 EA. You can obtain PTF IP22615 from the Enterprise Developer Fix Pack 2 CD.

If you have previously installed FFS on z/OS, you must obtain and install PTF IP22615 before using WSED. Download the PTF zip file to your desktop, unzip the file, and follow the instructions contained in the readme that is available with the PTF. IP22527 on CD 4 is not usable. If you need PTF IP22527, it is also available from this Web site. However IP22527 is not needed if you install IP22615. IP22615 contains a later version of all the parts that are in PTF IP22527.

4.4.2 Important migration considerations

Due to significant changes in the workspace structure, you will need to start with a new workspace. You cannot use workspaces created with Enterprise Developer z/OS aspects before this fix pack.

Also, before you use Enterprise Developer with this fix pack, rename the file ffs_sys.xml to ffs_sys.xml.old. This should be found in the following directory: C:\Documents and Settings\Administrator\Application Data\IBM\FFS (on Windows 2000) or C:\WINNT\Profiles\userid\Application Data\IBM\FFS (on Windows/NT)

4.4.3 Restrictions

The following restrictions apply to the z/OS application development tools:

• For a syntax check of a remote file, using a construct that includes source from a specific library is not fully supported. For example:
       PL/I: %include LIBRARY(MEMBER);
       COBOL: COPY MEMBER OF LIBRARY.
  However, as a work-around you can enter a SET statement in the Environment Variables entry field on the COBOL or PL/I Settings property page for this file. The SET statement for the examples above would be as follows:
       PL/I: SET IBM.LIBRARY=dir_path
       COBOL: SET LIBRARY=dir_path
       dir_path is the path name of the include directory.
  If the files are remote and the data set appears in the workspace, you can specify the path of the remote file. To find the path of the remote include library or the copy library, right-click on the folder that contains the library in your workspace and select the properties you want. On the Info page, the "Location:" entry contains the value of the folder location.
• You must specify each data-set name level fully. For example:

  A.*

  Show me all of the data sets that match the high-level qualifier of A.

  B.C.*

  Show me all of the data sets that match the high-level qualifiers of B.C.

  PART.OF.A.Nam*

  This is not supported, because NAM is not a complete part. It must end in .*.

• To compile a program in a local project, you must specify at least one compiler option.
• If you specify more than one compiler option for a local project, you must separate them with commas, not spaces.

4.4.4 Specifying the copy and include libraries to the compiler

Local files with local libraries

Local libraries are specified in the SYSLIB field of the COBOL Settings or PL/I Settings on the Properties page for the file. For local files, multiple local library names are separated by a semicolon.

Remote files with local libraries

Local libraries are specified in the SYSLIB field of the Local Build Options tab of the COBOL Settings or PL/I Settings on the Property page for the file. This is useful for local syntax checking of a remote file. There may be libraries that the local compiler is expecting to carry out the syntax check. For instance, for a CICS program you may choose to use the DFHAID.cpy that comes with VA CICS. Multiple library names are separated by a semicolon.

Remote files with remote libraries

Remote libraries are specified on the Copy Libraries or Include Libraries field of the Compile Options tab. Multiple library names are separated by a space.

In all cases, you need to specify explicitly the copy or include files for the files that use them.

4.4.5 Connecting to new z/OS system from Windows NT

On Windows NT, when you define a new z/OS System and request to connect to the system from the wizard pages, a modal dialog that prompts for your password is hidden behind the main Enterprise Developer window. You can avoid this by not connecting to the system through the New System wizard dialog but by completing the following steps:

1. Connect explicitly by highlighting the system name in the System Navigator.
2. Right-click.
3. Select Connect.

If you find yourself in the situation where you requested to connect immediately from the New System wizard dialog, you can type your password even though the dialog is not visible.

4.4.6 How property values cascade

Until Defect 31216 is fixed, property values will not cascade as described in the Getting Started Guide. At present, when you change the properties on a project or a folder, there are no confirmation messages that ask whether you want to change the properties on subordinate folders or files that are "distinguished" (have already had their properties changed). Instead, those distinguished folders or files are simply not changed.

4.4.7 Help system not yet updated

Except for the Getting Started Guide, the Enterprise Developer help content has not been updated to reflect z/OS application development fix pack code updates.

4.4.8 Limitations

In this fix pack the z/OS application development tools have the following limitations:

• When the build server is running on a system with multiple LPARs, the /* JOBPARM card is needed in both the build server startup job and the worker job that is started by the build server job so that they both run on the same machine.
• You should not have a file open in the LPEX editor when your are transitioning from connect to disconnect or vice versa. If you do this, you will lose all unsaved editing changes.
• Bugs exist in the disconnect dialog: select all does not yet work, and selecting a data set does not automatically select all the data set members contained by it.
• Expanding or accessing a PDS with 100 members takes approximately 30 seconds, regardless of the size of each member. This is a problem we are working on.
• An extraneous blank record is added to files saved with the z/OS LPEX editor.
• For text files, the editor does not currently check for LRECL settings for the containing data set. The save may fail if the file has a line that is too long, even if most of the line comprises spaces.
• The data-set allocation wizard hangs if the host system name has any uppercase characters. When you add a system to Enterprise Developer, make sure that you choose a short name with only lowercase characters.

4.4.9 Other known problems and limitations

For more information, see the WebSphere Studio Enterprise Developer 5.0 EA Readme File .

5. Problems fixed

This section describes sections or portions of sections in the WebSphere Studio Enterprise Developer 5.0 EA Readme File or the Readme File for WebSphere Studio Enterprise Developer 5.0 EA Fix Pack 1 that no longer apply. Sections 5.2 onward pertain to fixes for problems documented in the Fix Pack 1 readme file.

5.1 Other known problems

In Section 4.4.10.5 of the 5.0 EA readme file the following items no longer apply:

• The Explorer window may pop up unexpectedly. This window can be minimized to remove it from view. Also, closing the Distributed Build (Command Prompt) window causes a JVM error. Note: If JDK 1.4 or higher is installed and is set in the PATH, neither of these errors will occur.
• When you create new directories, only high level qualifiers are permitted; for example, HLQ is permitted, but HLQ.MLQ is not.
• After you submit JCL from the workbench to an MVS system, wait a few seconds before you click the Get Job Output menu item. If you click Get Job Output too quickly, the Job Monitor may hang.

5.2 Rebuilding an MVS project

Section 4.4.3 of the Fix Pack 1 readme file no longer applies. The problem with the Rebuild Project... option, which is invoked from the z/OS Projects view, has been fixed.

5.3 Restrictions

The second bullet item in Section 4.4.4 of the Fix Pack 1 readme file no longer applies. The problem with the Open Include File / Open Copy Member operation has been fixed.

5.4 Creating data sets with nondefault values

Section 4.4.5 of the Fix Pack 1 readme file no longer applies. Fix Pack 2 enhances the PDS creation wizard to let you create data sets with nondefault values.

6. Other updates and fixes

6.1 z/OS application development tools

This section describes major updates made to the EA release. Subsections 6.1.1 through 6.1.5 describe updates made in Fix Pack 1. Subsections 6.1.6 onward describe updates made in Fix Pack 2.

6.1.1 Properties and preferences

The behavior of z/OS-specific properties and preferences have changed. When defining a new MVS system to Enterprise Developer, you are able to establish the set of default properties that will be used for a z/OS project definition. These defaults include items such as the name and location of various compilers (COBOL and PL/I) and the compile-time, link-edit, and run-time options.

You may alter these values when defining a new project, and these values will be used for all of the applicable application artifacts within the project. If a value is altered at the project level, all of the application artifacts will assume this new value. An example of this is the change of a compile-time option from NOTEST to TEST. After the change, all of the compilations will use the TEST option.

Individual application artifacts may override the property values of the project. For example, you may have one COBOL source file that requires the compiler option of CMPAT(V2).

6.1.2 Separate workspaces

Eclipse supports the notion of separate workspaces. This concept is supported within Enterprise Developer with some restrictions. Each workspace may have a set of systems that will be used by projects within the workspace. (It is the logical name of the system that must be unique. The actual IP address may be referenced multiple times with different user-defined names.)

The following restrictions apply when you are using multiple workspaces:

• You cannot specify the same system name at the system creation time, if the system name already exists in a different workspace. For example, suppose that the user has two workspaces: Workspace1 and Workspace2. In Workspace1, you have defined system foobar with foo.bar.myco.com as the host name. In Workspace2, you cannot specify "foobar" as the system short name with foo.bar.myco.com as the host name, but you could specify foo2bar instead.
• If you delete a workspace that still contains some system definitions, those system names cannot be reused.
• If you have two instances of Enterprise Developer executing on your workstation with two different workspaces, changes to system definitions in one workspace (such as an addition or deletion) may force you to reconnect to systems in the second workspace.

6.1.3 Syntax checking

Syntax checking has been upgraded as follows:

• Remote files (residing physically on z/OS) can be syntax-checked by using the z/OS-resident compiler--either COBOL or PL/I.
• Remote files (residing physically on z/OS) can be syntax-checked by using the workstation-resident local compiler--either COBOL or PL/I.
• Local files (residing physically on the workstation) can be syntax-checked by using the workstation-resident local compiler--either COBOL or PL/I.

In all three configurations above, the support for include files, macro files, or COPYBOOK files is supported from one library.

6.1.4 Data sets

When a program connects to a z/OS system, the data sets are mapped to a logical workstation directory structure. An enhanced filtering capability is provided when a program connects to the z/OS system so that you can view only a subset of the data sets on the z/OS system. This filtering can be accomplished on the multipart qualified data-set name.

6.1.5 Other updates in Fix Pack 1

Other significant updates are as follows:

• Terminology has been updated to be more consistent with z/OS terminology.
• When adding a PDS, a PDS member, or a sequential file into a project from the Systems navigator, the data-set representation is not removed from the Systems Navigator.
• When you edit a data set by using the z/OS LPEX editor, a lock is placed against the data set so that a second user is unable to edit the file with ISPF simultaneously.
• German characters are handled better during remote access of data sets.
• If you double-click on compile-time error messages that are posted to the task list, an edit session is invoked within the source file that experienced the error. If the error was found in an included source file or COPYBOOK, the edit session will be directed to the included source.
• Previously, if you requested job output prior to the job completion, the output was empty and you could not obtain the output. This has been fixed. Now the job returns a message that indicates that the job is still in progress.

6.1.6 Added function for z/OS LPEX editor

For files containing valid sequence numbers on all lines in columns 73 - 80, the z/OS LPEX editor maintains the sequence numbers. If you use an LPEX profile such as XEDIT or ISPF which displays a prefix area, the sequence numbers are displayed in the prefix area. You can turn sequence numbers off in the z/OS LPEX editor preferences.

6.1.7 Other updates in Fix Pack 2

The following enhancements were made to the z/OS application development tools in Fix Pack 2:

• Lifted restrictions for syntax checking with a SYSLIB.
• Added syntax checking from within the z/OS LPEX editor for a local or remote (on z/OS) syntax check.
• Added the ability to work on a z/OS Project while disconnected from the z/OS host. You can select which artifacts to move to the workstation.
• For the z/OS LPEX editor, added code assist for COBOL source, including COBOL verbs, user-defined data elements, and EXEC CICS commands, and made usability enhancements.
• Increased the stability of the z/OS workspaces.
• Added the ability to dynamically allocate data sets by similarity, target use, or completely specify all parameters.
• Fixed bugs related to populating the task list.
• Added support for HLASM files for JCL generation and build.
• Added support for mixed language projects (COBOL, PL/I, HLASM).
• Fixed the file-locking bug (the z/OS LPEX editor and the ISPF editor use the same file-lock mechanism).
• Fixed some of the performance problems, specifically, involving the local syntax check of a PL/I file with many %include statements.

7. Where to find more information

To access online documentation for Enterprise Developer, click on Help > Help Contents > Enterprise Developer information.

For information about installing Enterprise Developer, see the IBM WebSphere Studio Enterprise Developer Installation Guide (document number SC31-6316-00) in HTML or PDF format.

To access the IBM WebSphere Studio Enterprise Developer Getting Started Guide (document number SC31-6317-00), access the online documentation as described above. There is an HTML version in the help system and a link to a PDF version of the document.

For more information about WebSphere Studio Enterprise Developer, see the WebSphere Studio Enterprise Developer 5.0 Readme File.