|
If you are not going to name the actual types and languages "DB2CLIST" and "DB2OUT",
do the following steps:
- Copy the sample language translators to your own source library
with the names you choose.
Modify the LANG values on the FLMLANGL
macro for the DB2CLIST and DB2OUT language translators and the DFLTTYP
and LANG values on the FLMALLOC macros in the DB2CLIST translators
to reflect your naming conventions.
For example if you are
using separate translators for binding plans and packages, and the
DB2CLIST and DB2OUT members are stored in different SCLM types for
plans and packages, the FLMALLOC statements might look like this:
Figure 1. DB2CLIST example for plansFLMLANGL LANG=PLNCLIST
⋮
FLMALLOC IOTYPE=O,DDNAME=ISRDB2OT,KEYREF=OUT3,LANG=PLNOUT, C
RECNUM=5000,LRECL=80,RECFM=FB,DFLTTYP=PLNOUT
Figure 2. DB2CLIST example for packagesFLMLANGL LANG=PKGCLIST
⋮
FLMALLOC IOTYPE=O,DDNAME=ISRDB2OT,KEYREF=OUT3,LANG=PKGOUT, C
RECNUM=5000,LRECL=80,RECFM=FB,DFLTTYP=PKGOUT
Remember to change the LANG values on the DB2OUT translator,
so that LANG=PLNOUT and LANG=PKGOUT.
- Modify the DBRMTYPE values in the OPTIONS parameter on the FLMTRNSL
macros in the language definitions to reflect your naming conventions.
This tells SCLM which DBRM libraries to allocate during the bind step
to the DBRMLIB DD. Be sure to make this change in both the DB2CLIST
and DB2OUT translators.
Figure 3. Defining DBRMTYPE
in DB2CLIST translator* BUILD TRANSLATOR(S)
*
FLMTRNSL CALLNAM='DB2 BIND', C
FUNCTN=BUILD, C
COMPILE=FLMCSPDB, C
PORDER=1, C
GOODRC=4, C
CALLMETH=LINK, C
OPTIONS=(FUNCTN=BUILD, C
OPTION=BIND, C
SCLMINFO=@@FLMINF, C
PROJECT=@@FLMPRJ, C
ALTPROJ=@@FLMALT, C
DBRMTYPE=DBRM, C
GROUP=@@FLMGRP, C
MEMBER=@@FLMMBR)
|