How many different types of BIND cards have you seen so far ? Your answer will be directly proportional to your experiences with DB2 versions. Most of them would say 2 ?
Type 1 -
Packages ( programs ) bound to a PLAN - The most adopted BIND card in today's DB2 for z/OS world. Here is a sample BIND card incorporating this methodology -
Type 2 -
PLAN based DBRM bind card, where the PLAN is directly bound to the DBRM - You will miss these if you are migrating to DB2 V10. Here is how it looks -
Well I have seen some more, check these out -
Type 3 -
This one, is a combination of PLAN based DBRM and Package bound to the same PLAN. Here the package(s) defined as a collection in the PKLIST are being called by the module defined in the MEBMER parameter of the BIND card. If I don't include the PKLIST parameter for this call scenario, the application program will encounter a -805 ( CL.PROG003 not found in PLAN003 ) during execution.
Type 4 -
Check this BIND card, it's a plan based DBRM bind card with two member names - The second member is a subprogram being called by the first member. In case I don't include the second member during the BIND and run the program, I will encounter a -805 ( PLAN0005 not found in PLAN0004 )
I am not sure if these are being used by others, but I incorporated these BIND cards at work which solved these -805's ( since the subprogram is not mapped on to the plan ) as few subprograms were defined as PLAN based DBRM's and few had their subprograms as packages and their calling program as a PLAN - directly bound to the DBRM
BIND's are awesome to play with at work !
