Micro Focus Enterprise Developer 3.0 for Eclipse > Programming > Mainframe Programming > SQL Option for DB2 > How to... > Bind Utility > To bind a DBRM to DB2 from the command line

To bind a DBRM to DB2 from the command line

Restriction: This topic applies to Windows environments only.

Use the command line if you:

Need to run a bind unattended (from a scheduler, for example)
Run a particular bind routinely
Wish to bind multiple programs in a single operation

Enter the following at your system command line:

BIND40N /d dbr-file /l location [option option option ...]

BIND40N /f transaction-file [option option option ...]

where:

dbr-file: The name of the DBRM you want to bind. If you do not specify a path, your DBRM must be in the current directory or in the XDB application path (as specified by Options). If you do not specify an extension, your DBRM must have a .DBR extension.
location: The name of the location to which the DBRM will be bound. (This is the name of the DB2 subsystem as it is registered with XDB Link.)
transaction-file: The name of the bind transaction file (.BND). Be sure to include a space between /f and the filename.

/c stop-status

stop-status can take one of the following values:

N: causes the bind to stop if an error occurs. This is the default.
Y: causes the bind to continue when an error occurs.

/s sqlID

sqlID is the ID used to set the current SQL ID at the time the package is bound.

/name=userID

userID is the user ID that will be used when the Bind Utility logs on the XDB Server.

If the /name option is not specified, you will be prompted for a user ID when the Bind Utility begins to execute.

/pass=password

password is the password that will be used when the Bind Utility logs on the XDB Server.

If the /pass option is not specified, you will be prompted for a password when the Bind Utility begins to execute.

/l location

location is the name of the remote location to which the DBRM will be bound. (This is the name of the DB2 subsystem as it is registered on the XDB Link.)

/existencechecking check-status

check-status can take one of the following values:

optional: creates a package even if the required database objects do not exist. This is the default.
required: creates a package only if the objects exist.

/grantexecute priviliges

priviliges can take one of the following values:

public: grants execute privileges to public. This is the default.
authid: grants execute privileges to authid.

/blocking block-mode

block-mode can take one of the following values:

FSR: Forced Single Row does not use block fetching regardless of cursor type.
SR: Single Row uses block fetching for read-only cursors and fetches a row at a time for ambiguous cursors.
LB: Limited Block uses block fetching for read-only and ambiguous cursors. This is the default.

/defaultchar subtype

subtype can take one of the following values:

BITS: specifies that the target relational database uses the FOR BITS DATA SQL character subtype for all new character columns for which an explicit subtype is not specified.
SBCS: specifies that the target relational database uses the FOR SBCS DATA SQL character subtype for all new character columns for which an explicit subtype is not specified.
DBCS: specifies that the target relational database uses the FOR MIXED DATA SQL character subtype for all new character columns for which an explicit subtype is not specified.
SYSDEFAULT: specifies that the target relational database uses the system default character subtype for all new character columns for which an explicit subtype is not specified. This is the default (and recommended) setting.

/d dbr-file

dbr-file is the name of the DBRM you want to bind. If you do not specify a path, the file must be in the current directory or in the XDB application path (as specified by Options). If you do not specify an extension, your DBRM must have a .DBR extension.

Note:

If you are running a bind unattended, be sure to include the /name and /pass options.