The fix is shipped as file IBM.HHOP700.UK24657.
Steps required to install the fix:
A sequential data set must be allocated on the z/OS system to receive the fix 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.
//ALLOC EXEC PGM=IEFBR14 //* //UK24657 DD DSN=hlq.IBM.HHOP700.UK24657, // DISP=(NEW,CATLG,DELETE), // DSORG=PS, // RECFM=FB, // LRECL=80, // UNIT=SYSALLDA, //* VOL=SER=volser, //* BLKSIZE=6160, // SPACE=(TRK,(50,10)) //*
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, 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 fix 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, time & date. 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:\IBM.HHOP700.UK24657 200 Port request OK. 125 Storing data set hlq.IBM.HHOP700.UK24657 250 Transfer completed successfully 2181840 bytes sent in 0.08 seconds ftp> quit 221 Quit command received. Goodbye.
SMP/E RECEIVE and APPLY the fix.
HOLD(UK24657) SYS FMID(HHOP700) REASON(ACTION) DATE(07121)
COMMENT(- projectcfg.properties
projectcfg.properties is a customizable configuration file
that will be updated.
Save your customized file before applying the service.
This file is located by default in /usr/lpp/wd4z/rse/lib.
- ADM
The Application Deployment Manager (ADM) provides a common
deployment approach and deployment API for other WebSphere
Developer components.
In addition ADM provides a CICS resource definition (CRD)
client which provides the following function:
* Allows application developers to define CICS resources in
a limited, controlled, and secure fashion.
- CICS resource definition defaults are supplied by
CICS system programmer and stored in the CRD server
repository on zOS
- Resource attribute update ability controlled by CICS
system programmer (update, protect, hidden)
- Limited to small set of resources typically needed
by application developers. These include DB2Tran,
Doctemplate, File, Mapset, Processtype, Program,
TDQ, and Transaction.
- Authorization to create CICS resource definitions is
controlled by RACF or other external security manager.
* Prevent CICS development access to unauthorized or
incorrect VSAM data sets by providing CICS system
programmer control of physical data set name attribute in
File definitions. This binding information is stored in
the CRD repository on zOS.
* Miscellaneous CRD server development aids
- New copy for programs and mapsets
- List CICS regions
- DFHRPL list
* CRD server, Web service development aids
- Perform Pipeline scan to autoinstall URIMAP and
WEBSERVICE definitions
- Provide pipeline and WSBind pickup directory list
- Provide WSDL file directory list
- Provide End Point URI list
The following steps must be performed in order to complete the
installation of the ADM CRD server. The SFEKSAMP directory on
MVS contains four ADM sample members. ADNVSAM, ADNPCCSD, and
ADNARCSD are JCL members. These members should be copied to
another library before being modified to fit your job card and
data set naming conventions. ADNTMSGH is a pipeline message
handler COBOL sample.
1. Modify and run job ADNVSAM to allocate and initialize the CRD
server repository VSAM file.
2. Modify and run job ADNPCCSD to update the CICS System
Definition (CSD) for the CICS primary connection region. This
is the region that will process Web service requests from
WebSphere Developer.
3. Use CEDA to install the ADM group for this region.
4. Modify and run job ADNARCSD to update the CSD for other
non-primary connection regions. These are usually Application
Owning (AOR) regions. It is not necessary to run this job if
CICSPlex SM is used to manage your CICS environment.
5. Use CEDA to install the ADM group for these regions.
6. Place ADM load modules ADNCRDS and ADNCRDR in a DFHRPL load
library in the CICS primary connection region.
7. Optionally place ADNCRDS in a DFHRPL load library in other
non-primary connection regions. These are usually Application
Owning (AOR) regions. It is not necessary to run this job if
CICSPlex SM is used to manage your CICS environment.
8. Modify (optionally) and compile the sample pipeline message
handler (ADNTMSGH).
9. Place the ADNTMSGH load module in a DFHRPL load library in
the CICS primary connection region.
Refer to WebSphere Developer for System z, IBM WebSphere
Developer for System z Version 7.0 - Release Notes for more
information on configuring and using ADM.
No customization is required for USS.
).
The following procedure should only be used as directed by the IBM Support Center. This procedure allows gathering of information needed to diagnosis Error Feedback problems.
ELAXMGUx test instructions:
//ELAXFCOC PROC LNGPRFX='COBOL.V3R3M0',
// CICSLOD='CICSTS.V3R1M0’,
// DB2LOD='DB2.V7R1M0',
// LODPRFX='FEK'
//COBOL EXEC PGM=IGYCRCTL,REGION=2048K,
//* PARM=('EXIT(ADEXIT(ELAXMGUX))',
// PARM=('EXIT(ADEXIT(''MAXTRACE'',ELAXMGUX))',
// 'ADATA',
// 'LIB',
// 'TEST(NONE,SYM,SEP)',
// 'LIST',
// 'FLAG(I,I)'&CICS&DB2&COMP)
//STEPLIB DD DSN=&LNGPRFX..SIGYCOMP,
// DISP=SHR
// DD DSN=&LODPRFX..SFEKLOAD,
// DISP=SHR
// DD DSN=&CICSLOD..SDFHLOAD,
// DISP=SHR
// DD DSN=&DB2LOD..SDSNLOAD,
// DISP=SHR
NOTE: you have to double the apostrophes around MAXTRACE. The option is now: EXIT(ADEXIT(''MAXTRACE'',ELAXMGUX))
LOGGINGLEVEL = 900 PASSED IN PARM = MAXTRACE SUCCESSFUL OPENING SYSXMLSD=DD:SYSXMLSD ABOUT TOO OPEN SIDEFILE1 - NAME = 'uid.DT021207.TT110823.M0000045.C0000000' SUCCESSFUL OPEN SIDEFILE1 - NAME = 'uid.DT021207.TT110823.M0000045.C0000000' ABOUT TOO OPEN SIDEFILE2 - NAME = 'uid.DT021207.TT110823.M0000111.C0000001' SUCCESSFUL OPEN SIDEFILE2 - NAME = 'uid.DT021207.TT110823.M0000111.C0000001' ABOUT TOO OPEN SIDEFILE3 - NAME = 'uid.DT021207.TT110823.M0000174.C0000002' SUCCESSFUL OPEN SIDEFILE3 - NAME = 'uid.DT021207.TT110823.M0000174.C0000002' ABOUT TOO OPEN SIDEFILE4 - NAME = 'uid.DT021207.TT110823.M0000236.C0000003' SUCCESSFUL OPEN SIDEFILE4 - NAME = 'uid.DT021207.TT110823.M0000236.C0000003' Entering the exit = 1 Entering the exit = 2 Entering the exit = 3 Entering the exit = 4 Entering the exit = 5
NOTE: Depending on your settings, SIDEFILE1 and SIDEFILE2 may be pointing to a DD statement (SUCCESSFUL OPEN SIDEFILE1 - NAME = DD:WSEDSF1). Refer to the JESJCL part of the output (which is located before the SYSOUT part) to get the actual data set name.
21 //COBOL.SYSXMLSD DD DSN=uid.ERRCOB.member.Z682745.XML, // DISP=MOD 22 //COBOL.WSEDSF1 DD DSN=uid.ERRCOB.member.SF1.Z682746.XML, // DISP=MOD 23 //COBOL.WSEDSF2 DD DSN=uid.ERRCOB.member.SF1.Z682747.XML, // DISP=MOD 24 //COBOL.SYSIN DD DSN=uid.IDE.COBOL(member),DISP=SHR