Troubleshooting
Problem
There is a Hold Action for UK73755 as follows: ++HOLD(UK73755) SYS FMID(H28N330) REASON(ACTION) DATE(11314) COMMENT(This PTF requires post-SMP/E action as follows: All customers should edit as appropriate and - run JCL member EDIJBUNL from EDI.V3R3M0.SEDIINS1 ). It creates a Plan with a DBRM in it, which is not possible under DB2 v10. Are there alternative instructions for binding DBRM into a package?
Resolving The Problem
First of all, WDI DB2 DBRM, EDIMUNL, is associated with a program of same name, and would only be run as part of the migration process from WDI 3.2.1 to WDI 3.3.0. This would be part of the EDIPUNL plan used only for unloading operational data from WDI 3.2.1 during migration via JCL EDIJMUNL. EDIMUNL is not part of the main, master WDI plan (EDIENU33). If you have already migrated to WDI 3.3, there would be no need to bind/rebind this DBRM. Hence, no need to convert this plan to use packages.
If you are in the process of migrating to WDI 3.3, then you can use the following sample JCL to bind the packages and create the plans needed for Migrating Operational Data From WDI V3.2 to WDI V3.3 on z/OS. See Appendix B of the WDI 3.3 Installation Guide for z/OS. The following will cover both plans; EDIPUNL (unload from 3.2) and EDIPLOD (load into 3.3)
B.1 Step 1. Binding the DB2 Plan for unload processing
//JOBCARD JOB (INSTALLATION DEPENDENCIES)
//*
//*********************************************************************
//* BIND VERSION 3 RELEASE 3 DI/MVS DB2 PACKAGE AND CREATE PLAN *
//* FOR MIGRATION JOB EDIJMUNL *
//*********************************************************************
//*
//JOBLIB DD DSN=DB2.DSNLOAD,DISP=SHR <--- DB2 LOAD LIBRARY
//*
//*********************************************************************
//* BINDS PACKAGE EDIMUNL TO THE WDI 3.2 DATABASE *
//*********************************************************************
//STEP0100 EXEC PGM=IKJEFT01,DYNAMNBR=20,REGION=2000K
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//LISTING DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DSN)
BIND PACKAGE (EDIPUNL) -
MEMBER (EDIMUNL) -
OWNER (EDIENU32) -
QUALIFIER (EDIENU32) -
LIBRARY ('EDI.V3R3M0.SEDIDBR1') -
ACTION (REP) -
VALIDATE (BIND) -
ISOLATION (CS) -
RELEASE (COMMIT) -
CURRENTDATA (NO) -
SQLERROR (NOPACKAGE) -
EXPLAIN (NO)
BIND PLAN (EDIPUNL) -
OWNER (EDIENU32) -
PKLIST (EDIPUNL.EDIMUNL) -
ACTION (REP) RETAIN -
VALIDATE (BIND) -
ISOLATION (CS) -
ACQUIRE (USE) -
RELEASE (COMMIT) -
CURRENTDATA (NO) -
EXPLAIN (NO)
END
/*
//
B.4 Step 4. Binding the DB2 Plan for Load Processing
//JOBCARD JOB (INSTALLATION DEPENDENCIES)
//*
//*********************************************************************
//* BIND VERSION 3 RELEASE 3 DI/MVS DB2 PACKAGE AND CREATE PLAN *
//* FOR MIGRATION JOB EDIJMLOD *
//*********************************************************************
//*
//JOBLIB DD DSN=DB2.DSNLOAD,DISP=SHR <--- DB2 LOAD LIBRARY
//*
//*********************************************************************
//* BINDS PLAN EDIMUNL TO THE WDI 3.2 DATABASE *
//*********************************************************************
//STEP0100 EXEC PGM=IKJEFT01,DYNAMNBR=20,REGION=2000K
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//LISTING DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(DSN)
BIND PACKAGE (EDIPLOD) -
MEMBER (EDIMLOD) -
OWNER (EDIENU33) -
QUALIFIER (EDIENU33) -
LIBRARY ('EDI.V3R3M0.SEDIDBR1') -
ACTION (REP) -
VALIDATE (BIND) -
ENCODING (UNICODE) -
ISOLATION (CS) -
RELEASE (COMMIT) -
CURRENTDATA (NO) -
SQLERROR (NOPACKAGE) -
EXPLAIN (NO)
BIND PLAN (EDIPLOD) -
OWNER (EDIENU33) -
PKLIST (EDIPLOD.EDIMLOD) -
ACTION (REP) RETAIN -
VALIDATE (BIND) -
ENCODING (UNICODE) -
ISOLATION (CS) -
ACQUIRE (USE) -
RELEASE (COMMIT) -
CURRENTDATA (NO) -
EXPLAIN (NO)
END
/*
//
Was this topic helpful?
Document Information
Modified date:
01 August 2018
UID
swg21625030