Why myself doing Package Bind always for DB2 programs?

Susanta · Active User Joined: 17 Nov 2009 Posts: 126 Location: India

Hi
In our mainframe project, we always do a package bind for cobol-db2 program. and run the program using Jcl by IKJEFT01 step.

I got this doubt as we know that only plan is executable.
Then how my jobs running fine with just package BInd. Please help.

Thanks

daveporcelan · Posted: Thu Mar 02, 2017 11:10 pm

Although you execute the Plan, it refers to the package, either explicitly, or to the collection where the package resides.

Someone at your shop should explain to you how the Plans and Packages are organized.

Susanta · Active User Joined: 17 Nov 2009 Posts: 126 Location: India

The SYSTSIN CARD is

DSN SYSTEM(SSNID)

RUN PROGRAM(XYZPROG) PLAN(CREATORB)

END

'understood ,you said plan CREATORB points to a collection where package of XYZPROG gets added by the package bind command.

Now my query is when exactly we go for a Plan bind.
in my project 'never did a plan bind.

-
Please let me know, Thanks

daveporcelan · Posted: Fri Mar 03, 2017 6:28 pm

Plan CREATORB is probably a shared plan used by all programs/packages in the COLLECTIONB collection.

All the packages in this collection probably refer to SCHEMAB.

It was probably set up by your DBA staff, and should not be touched.

You see I said probably several times. This is because....

Someone at your shop should explain to you how the Plans and Packages are organized.[/b]

Susanta · Active User Joined: 17 Nov 2009 Posts: 126 Location: India

Thanks for the infos...@dave.

don.leahy · Posted: Tue Mar 07, 2017 7:09 pm

For an excellent explanation of the PLAN/Package relationship see this article by Bonnie Baker: www.ibm.com/developerworks/data/library/dmmag/DMMag_2011_Issue3/Programmers/