ADDBNDDIRE (Add Binding Directory Entry)

ADDBNDDIRE Command syntax diagram

 

Purpose

The Add Binding Directory Entry (ADDBNDDIRE) command adds an entry to the binding directory.

 

Restrictions

1. You must have *USE authority for the library where the binding directory is being updated.
   
2. You must have object operational and *ADD authority to the binding directory.
   
3. You must have *EXECUTE authority to the specified library when using generic processing.

 

Required Parameters

BNDDIR

Specifies the binding directory to which an entry is added.

The name of the binding directory can be qualified by one of the following library values:

*LIBL: All libraries in the job's library list are searched until the first match is found.

*CURLIB: The current library for the job is searched. If no library is specified as the current library for the job, the QGPL library is used.

*USRLIBL: Only the libraries in the user portion of the job's library list are searched.

library-name: Specify the name of the library to be searched.

binding-directory-name: Specify the name of the binding directory to be updated.

OBJ

Specifies the object name to be added to the binding directory.

Element 1: Name of the Object to be Added

The name of the binding directory can be qualified by one of the following library values:

*LIBL: All libraries in the job's library list are searched until the first match is found.

library-name: Specify the name of the library to be searched.

*ALL: All objects of the specified type residing in the specified library are added.

object-name: Specify the object to be added.

generic*-object-name: Specify the generic name of the object. A generic name is a character string of one or more characters followed by an asterisk (*); for example, ABC*. The asterisk substitutes for any valid characters. A generic name specifies all objects with names that begin with the generic prefix for which the user has authority. If an asterisk is not included with the generic (prefix) name, the system assumes it to be the complete object name. See generic names for additional information.

Element 2: Type of Object to be Added

*SRVPGM: Indicates the object to be added is a service program.

*MODULE: Indicates the object to be added is a module.

POSITION

Specifies the position in the binding directory where the list of objects is added.

*LAST: The list of objects is added to the end of the binding directory entries.

*FIRST: The list of objects is inserted prior to the first binding directory entry.

Element 1: Object Position

*AFTER: The list of objects is added to the binding directory after the binding directory entry specified on this parameter. The entry specified must currently exist in the binding directory.

*BEFORE: The list of objects is added to the binding directory before the binding directory specified on this parameter. The entry specified must currently exist in the binding directory.

*REPLACE: The object specified on the OBJ parameter replaces the binding directory entry specified on this parameter. The entry specified must currently exist in the binding directory. Only one entry can be specified on the OBJ parameter.

Element 2: Binding Directory Entry Name

The name of the binding directory can be qualified by one of the following library values:

*LIBL: All libraries in the job's library list are searched until the first match is found.

library-name: Specify the name of the library to be searched.

binding-directory-entry-name: Specify a binding directory entry name that exists in the specified binding directory.

Element 3: Binding Directory Entry Type

*SRVPGM: Indicates the directory entry is a service program.

*MODULE: Indicates the directory entry is a module.

Examples for ADDBNDDIRE

Example 1:

ADDBNDDIRE   BNDDIR(TESTBNDDIR)
  OBJ((TESTOBJ))  POSITION(*LAST)

This command adds a binding directory entry for service program TESTOBJ in library *LIBL to the end of the list of binding directory entries found in the binding directory TESTBNDDIR.

Example 2:

ADDBNDDIRE   BNDDIR(TESTBNDDIR)
  OBJ((TESTLIB/TESTOBJ *MODULE))  POSITION(*FIRST)

This command adds a binding directory entry for module TESTOBJ in library TESLIB to the beginning of the binding directory entries found in the binding directory TESTBNDDIR.

Example 3:

ADDBNDDIRE   BNDDIR(TESTBNDDIR)
  OBJ((TESTLIB/TESTOBJ *MODULE)  (TESTOBJ2))
  POSITION(*FIRST)

This command adds a binding directory entry for module TESTOBJ in library TESTLIB followed by an entry for service program TESTOBJ2 in the library list to the beginning of the binding directory entries found in the binding directory TESTBNDDIR.

Example 4:

ADDBNDDIRE   BNDDIR(TESTBNDDIR)
  OBJ((TESTLIB/TESTOBJ *MODULE) (TESTOBJ2))
  POSITION(*BEFORE  TESTMOD *MODULE)

This command adds a binding directory entry for module TESTOBJ in library TESTLIB, followed by an entry for service program TESTOBJ2 in library *LIBL prior to the binding directory entry for module TESTMOD in library *LIBL found in the binding directory TESTBNDDIR.

The binding directory entry for module TESTMOD in library *LIBL must be found in the binding directory TESTBNDDIR for this operation to be successful.

Error messages for ADDBNDDIRE

*ESCAPE Messages

CPF5D01

Binding directory &1 in library &2 is not usable.

CPF5D09

Object &2/&1 type &3 was not found in binding directory &4 in library &5.

CPF980F

Binding directory &1 in library &2 not found.

CPF9801

Object &2 in library &3 not found.

CPF9802

Not authorized to object &2 in &3.

CPF9803

Cannot allocate object &2 in library &3.

CPF9820

Not authorized to use library &1.

CPF9830

Cannot assign library &1.