Installation instructions for PTFs UQ75168, UQ77043 & UQ77441 for WebSphere Studio Enterprise Developer Options for z/OS

Selecting One Installation Path to Follow

These are the possible installation scenerios you may have. Select the one that best describes your environment and install the required PTFs. Instructions for installing the individual PTFs follows.

1. If you have previously installed and configured the WebSphere Studio Enterprise Developer Options for z/OS base product and PTFs UQ75168 & UQ75170 you now also need to install PTFs UQ77043 & UQ77441, as described in the section Step by Step Instructions for Installing PTFs UQ75168, UQ77043 & UQ77441.
2. If you have previously installed and configured the WebSphere Studio Enterprise Developer Options for z/OS base product, but no PTFs you now also need to install PTFs UQ75168, UQ77043 & UQ77441, as described in the section Step by Step Instructions for Installing PTFs UQ75168, UQ77043 & UQ77441.
3. If you are a new user of WebSphere Studio Enterprise Developer Options for z/OS, first follow the instructions in the program directory, to install and configure the base product. Then install PTFs UQ75168, UQ77043 & UQ77441, as described in the section Step by Step Instructions for Installing PTFs UQ75168, UQ77043 & UQ77441.

PTFs UQ75168, UQ77043 & UQ77441 provide several fixes. In particular:

• OC4 abend when starting the MVS build server.
• Change the SCLM host configuration process.
• A warning message is received when compiling message dlls whose source is generated from the message file.
• If the values of the input, output, dependent file paths contain DBCS characters, the paths are not processed correctly.
• Compile error does not appear in Task view when using code page IBM-930
• Remote build message catalogs for USS were shipped in ASCII format rather than EBCDIC format. Users setting environment variable CCU_CATALOG to the name of one of the message catalog data sets to cause build messages to be returned in a language other than English would still get messages in English.
• If the JES3 //*MAIN statement is added to the build request JCL (CCUMVS by default) in order to cause a build request to be executed on a particular partition of a sysplex, the statement is treated as a comment. This causes a message that IP address 127.0.0.1 cannot be resolved if the main build server job (CCURUNM by default) and the build request job are not assigned to the same partition.
• ELAXMGUX was shipped with back level contents in the GA release.

The general steps for installing and configuring these PTFs are shown in the step by step instructions below.

Step by Step Instructions for Installing PTFs UQ75168, UQ77043 & UQ77441

This material is intended for the system programmer responsible for installing and maintaining programs. It contains information about the material and procedures associated with the installation of PTFs UQ75168, UQ77043 & UQ77441. You should read all of this material before installing the PTFs and keep for future reference.

The PTFs are shipped as files WSED501\zos\heds500\IBM.HEDS500.UQ75168, WSED501\zos\heds500\IBM.HEDS500.UQ77043 and WSED501\zos\heds500\IBM.HEDS500.UQ77441.

Overview of the installation steps

Here are the steps required to install PTFs UQ75168, UQ77043 & UQ77441:

1. Allocate data sets for the PTFs you need to upload.
2. Upload the needed PTFs from your workstation to z/OS.
3. Perform SMP/E RECEIVE and APPLY.

Allocate data sets for the PTFs

Sequential data sets must be allocated on the z/OS system to receive the PTFs that you will upload from your workstation. You can do this by submitting the job below. Add a job card and modify the parameters to meet your site's requirements before submitting. Allocate only the data sets needed for your installation (you may not need the data set for UQ75168 if the PTF was previously installed).

//ALLOC1    EXEC   PGM=IEFBR14
//*
//FTPALLO  DD  DSN=hlq.IBM.HEDS500.UQ75168,
//         DISP=(NEW,CATLG,DELETE),
//         DSORG=PS,
//         RECFM=FB,
//         LRECL=80,
//         BLKSIZE=6160,
//         SPACE=(TRK,(10,4)),
//         UNIT=SYSALLDA
//*        VOL=SER=&TVOL1
//*
//FTPALL1  DD  DSN=hlq.IBM.HEDS500.UQ77043,
//         DISP=(NEW,CATLG,DELETE),
//         DSORG=PS,
//         RECFM=FB,
//         LRECL=80,
//         BLKSIZE=6160,
//         SPACE=(TRK,(12,6)),
//         UNIT=SYSALLDA
//*        VOL=SER=&TVOL1
//*
//FTPALL2  DD  DSN=hlq.IBM.HEDS500.UQ77441,
//         DISP=(NEW,CATLG,DELETE),
//         DSORG=PS,
//         RECFM=FB,
//         LRECL=80,
//         BLKSIZE=6160,
//         SPACE=(TRK,(50,12)),
//         UNIT=SYSALLDA
//*        VOL=SER=&TVOL1

Upload the PTFs from your workstation

Upload the files 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, commands or other information entered by the user are in bold, and the following values are assumed:

User enters:	Values
mvsaddr	TC P/IP address of the z/OS system
tsouid	Your TSO user ID
tsopw	Your TSO password
d:	Your drive containing the PTF files
hlq	High-level qualifier that you used for the data set that you allocated in the job above

C:\>ftp mvsaddr
Connected to mvsaddr.
220-FTPD1 IBM FTP CS V2R8 at mvsaddr, 04:43:52 on 2002-03-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 c:\WSED501\zos\heds500\ibm.heds500.uq75168 ibm.heds500.uq75168
200 Port request OK.
125 Storing data set hlq.ibm.heds500.uq75168
250 Transfer completed successfully.
307840 bytes sent in .38 seconds

ftp> put c:\WSED501\zos\heds500\ibm.heds500.uq77043 ibm.heds500.uq77043
200 Port request OK.
125 Storing data set hlq.ibm.heds500.uq77043
250 Transfer completed successfully.
429760 bytes sent in .60 seconds

ftp> put c:\WSED501\zos\heds500\ibm.heds500.UQ77441 ibm.heds500.UQ77441
200 Port request OK.
125 Storing data set hlq.ibm.heds500.UQ77441
250 Transfer completed successfully.
2398320 bytes sent in .42 seconds

ftp> quit
221 Quit command received. Goodbye.

Perform SMP/E RECEIVE and APPLY

RECEIVE and APPLY the PTFs as usual. NOTE: you must include all PTFs in one SMP/E APPLY run. There is customization needed to incorporate these changes into your system, as described in the following changes to the program directory.

Program Directory section 6.2.1.8.2, ISPF Configuration File

An ISPF configuration table ISPF.conf must be customized for ISPF data set allocations. Copy and rename the supplied sample configuration file ELAXWEBI to /etc/EnterpriseDeveloper/SCLM/ISPF.conf, if you use a different path name you will need to update CGI_ELAXPATH webserver environment variable (see 6.2.1.8.3 Configuring the Enterprise Developer/SCLM Webserver for further instructions on configuring a HTTP environment variable file). The sample HTTP webserver environment variable file will have by default : CGI_ELAXPATH = /etc/EnterpriseDeveloper/SCLM

NOTE : If the environment variable CGI_ELAXPATH is not included the program will look for the ISPF.conf file in the WSED/SCLM install path.

The provided sample ISPF.conf (ELAXWEBI) has instructions to complete customization and enables users to :

• Include the minimum ISPF data set allocations for SCLM plugin operation.
• Add additional DDNAME file allocations or concatenate additional ISPF data sets.
• Execute a customer defined allocation exec to provide further data set allocation by Project or userid.