Installation instructions for PTFs UQ84053, UQ85374, UK00136

Installation instructions for PTFs UQ84053, UQ85374, UK00136 for WebSphere Studio Enterprise Developer Options for z/OS

PTFs UQ84053, UQ85374, UK00136 supercedes all prior maintenance for WebSphere Studio Enterprise Developer Options for z/OS

If you have previously installed and configured the WebSphere Studio Enterprise Developer Options for z/OS base product you now need to install UQ84053, UQ85374, UK00136. by following Step by Step Instructions for Installing PTFs UQ84053, UQ85374, UK00136.
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 UQ84053, UQ85374, UK00136, as described in the section Step by Step Instructions for Installing PTFs UQ84053, UQ85374, UK00136.

UQ84053, UQ85374, UK00136 resolves several known problems and adds new functions. In particular:

Adds sample JCL procedures which will be used for the JCL generation, remote project builds and remote syntax check features of COBOL, PLI and Assembler programs using WebSphere Studio Enterprise Developer.
Catalog errors may be returned as SCLM project names on retrieved project list.
Data set allocation error caused by Build Server job specifying UNIT=VIO for temporary data set allocation.
The sample ELAXWEBI in SCCUSAMP contains comments pointing to an incorrect default location.
Corrects call to invalid program, CONCATD.
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.

Step by Step Instructions for Installing UQ84053, UQ85374, UK00136

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 PTF UQ84053, UQ85374, UK00136. You should read all of this material before installing these PTFs and keep for future reference.

If you have previously installed the DB2 Stored Procedures Technical Preview, CCUTP01 you must remove it prior to installing these PTFs.

The PTFs are shipped as files WD4Z60\heds500\service\ibm.heds500.UQ85374, WD4Z60\heds500\service\ibm.heds500.UQ84053 and WD4Z60\heds500\service\ibm.heds500.UK00136.

Overview of the installation steps

Steps required to install the PTF:

Allocate host data sets for the PTFs.
Upload the PTFs from your workstation to z/OS.
Perform SMP/E RECEIVE and APPLY.
Perform Customization tasks.

Allocate host data set for the PTF

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. Before submitting 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.UQ84053,
//         DISP=(NEW,CATLG,DELETE),
//         DSORG=PS,
//         RECFM=FB,
//         LRECL=80,
//         BLKSIZE=6160,
//         SPACE=(TRK,(45,10)),
//         UNIT=SYSALLDA
//*        VOL=SER=&TVOL1
//*
//FTPALL1  DD  DSN=hlq.IBM.HEDS500.UQ85374,
//         DISP=(NEW,CATLG,DELETE),
//         DSORG=PS,
//         RECFM=FB,
//         LRECL=80,
//         BLKSIZE=6160,
//         SPACE=(TRK,(55,10)),
//         UNIT=SYSALLDA
//*        VOL=SER=&TVOL1
//*
//FTPALL1  DD  DSN=hlq.IBM.HEDS500.UK00136,
//         DISP=(NEW,CATLG,DELETE),
//         DSORG=PS,
//         RECFM=FB,
//         LRECL=80,
//         BLKSIZE=6160,
//         SPACE=(TRK,(55,10)),
//         UNIT=SYSALLDA
//*        VOL=SER=&TVOL1

Upload the PTF from your workstation to z/OS

Upload the files in binary format from your workstation to the z/OS data sets. 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
`hlq`	High-level qualifier that you used for the data set 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 d:\WD4Z60\heds500\service\ibm.heds500.UQ84053 ibm.heds500.UQ84053
200 Port request OK.
125 Storing data set hlq.ibm.heds500.UQ84053
250 Transfer completed successfully.
2111040 bytes sent in .01 seconds

ftp> put d:\WD4Z60\heds500\service\ibm.heds500.UQ85374 ibm.heds500.UQ85374
200 Port request OK.
125 Storing data set hlq.ibm.heds500.UQ85374
250 Transfer completed successfully.
2609120 bytes sent in .01 seconds

ftp> put d:\WD4Z60\heds500\service\ibm.heds500.UQ85374 ibm.heds500.UK00136
200 Port request OK.
125 Storing data set hlq.ibm.heds500.UK00136
250 Transfer completed successfully.
238160 bytes sent in .01 seconds

ftp> quit
221 Quit command received. Goodbye.

Perform SMP/E RECEIVE and APPLY

Using SMP/E perform Receive/Apply.

Perform Customization tasks

There is customization needed to incorporate these changes into your system, as described in the ++HOLD comments in the PTF cover letter.

Additionally the following customization is needed to incorporate the DB2 Stored Procedures into your system.

After the SMP/E Apply, the sample library hlq.SCCUSAMP contains the following members:

ELAXMREX REXX code of the PL/I and COBOL Stored Procedure Builder.
ELAXMJCL Sample JCL for defining the PL/I and COBOL Stored Procedure Builder to DB2
ELAXMSAM Sample JCL procedure of the WLM address space for the PL/I and COBOL Stored Procedure Builder.

Copy ELAXMSAM, to the DB2 Proclib and customize the JCL as described in its comment. Make sure that the SYSEXEC DD card points to the library where the REXX code of the PL/I and COBOL Stored Procedure Builder resides.
Use the workload management panels to associate an application environment with the JCL procedure of the WLM address space for the PL/I and COBOL Stored Procedure Builder. See OS/390 MVS Planning: Workload Management for information on how to do this.
Copy ELAXMJCL to a private JCL library, customize as described in its comments and execute the job. Make sure the WLM ENVIRONMENT clause in the CREATE PROCEDURE statement specifies the name of the WLM environment which has been defined for the PL/I and COBOL Stored Procedure Builder.

All customization must be completed for the fixes contained in the PTFs to become effective.

Late Breaking News

Sample proc, 'hlq.SCCUSAMP(ELAXFCOC)', line 65, defaults to: 'TEST',

We recommend changing the default to: 'TEST(NONE,SYM,SEP)',