Back To LeighWeb Mainframe Utilities Page

 BINDCARD creates batch DB2 "bind plan" cards.  It "wraps" the cards in JCL for
 loading into ENDEVOR (it also generates the necessary ENDEVOR SCL to accomplish
 this).  The JCL is then submitted for backround processing with ENDEVOR.  It
 can take existing bind plan cards from ENDEVOR and update them with changes, or
 add a completely new set of bind plan cards into ENDEVOR.

 Syntax:

 COMMAND ===> tso bindcard

 When you invoke BINDCARD, you are presented with a screen.  On this screen, you
 may enter the name of the main program which "drives" this batch process.  You
 must enter this field.  The name of this application will be the name used to
 store the DB2 bind cards in ENDEVOR.

 You need to then indicate whether the main driving application uses DB2 or not.
 If so, it will be included in the package list associated with this plan, if
 not, the main application name will simply be used as the name of the plan.

 If this main application calls any other "non-common"/"client-specific"
 applications AND they use DB2, they should be listed (in any order) in one of
 the "Called" fields on the screen (currently there is room for 15 called
 applications).  Additionally, if a called module (DB2 or not) calls a program
 that does DB2, the DB2 module should be included in one of the "Called" fields.
 So, anywhere in the "calling hierarchy" that DB2 is used, that program name
 needs to be specified.  If an application is a called application for this
 driver program, but it does NOT use DB2, it should not be listed on this
 screen.

 Consequently, if the driver application does not use DB2 and none of its called
 applications use DB2, there is no need to request a DB2 batch plan bind for
 this application.  It is strictly for applications which use DB2 in SOME
 fashion.

 When you have finished entering the applications, you may choose to override
 the default DB2 plan parameter values.  In 99% of the cases, these defaults
 should NOT be overridden.  Any override needs should probably be discussed with
 the DBA team.

 Finally, you will need to enter an ENDEVOR CCID (Change Control Identifier) and
 an ENDEVOR comment.  These pieces of information are required in order to
 successfully load the bind cards into ENDEVOR.  They are not required on this
 panel until you actually change the GENERATE JCL flag from "N" to "Y".  Check
 with the ENDEVOR administrator to determine what CCID to use (typically this
 will be your PR number).  Use meaningful text to describe the nature of the
 change in the comment field.  The limit of the length of the comment field is a
 function of ENDEVOR limits

 If you are updating existing bind plan cards which are stored in ENDEVOR and
 you wish to start with the parameters of the existing bind plan cards, BINDCARD
 will extract the information from ENDEVOR and populate the screen for you.
 BINDCARD is triggered to perform this operation if it finds a "N" in the
 GENERATE JCL field.  If you press  when this field is set this way,
 BINDCARD will get the information for the BIND card element named the same as
 your "main" application.  It then parses this information and populates the
 screen with it.  You are then free to modify it in any way you wish.
1
 Alternatively, you may just replace whatever exists for an existing set of bind
 plan cards by setting the GENERATE JCL flag to "Y", entering your data and
 pressing .  In this case, BINDCARD will not attempt to extract the
 values of the bind plan cards to populate the screen.  It will just create the
 JCL from what you entered on the screen.

 BINDCARD will generate a step in the JCL to RETREIVE the element from ENDEVOR.
 This retreived version is thrown away, however, and what was on the screen is
 used to do the UPDATE back into ENDEVOR.  The RETRIEVE is only used to obtain
 SIGNOUT on the element.

 After you've generated, the GENERATE field returns the the value of "N", and
 you are ready to enter more data if necessary and generate another plan.  Your
 CCID and ENDEVOR comment are remembered during your ISPF session, so you can
 generate several plans under the same CCID if necessary.