Running SPUFI at remote systems

You can use SPUFI to connect to and then execute SQL statements at a remote location.

Procedure

Begin general-use programming interface information. To run SPUFI at a remote location:

Ensure that DDF is started on the Db2 subsystem where SPUFI runs.
Bind the SPUFI packages on each target remote location that is not a Db2 for z/OS server, or on each target remote Db2 for z/OS location where the SPUFI packages have not been bound.
For example, use the following commands:
```
BIND PACKAGE (location_name.DSNTIAP) MEMBER(DSNTIAP)
             ACTION(ADD) ENCODING(EBCDIC) LIB('prefix.SDSNDBRM')

BIND PACKAGE (location_name.DSNESPCS) MEMBER(DSNESM68)
             ACTION(ADD) ISOLATION(CS) ENCODING(EBCDIC) LIB('prefix.SDSNDBRM')

BIND PACKAGE (location_name.DSNESPRR) MEMBER(DSNESM68)
             ACTION(ADD) ISOLATION(RR) ENCODING(EBCDIC) LIB('prefix.SDSNDBRM')

BIND PACKAGE (location_name.DSNESPUR) MEMBER(DSNESM68)
             ACTION(ADD) ISOLATION(UR) ENCODING(EBCDIC) LIB('prefix.SDSNDBRM')
```
If a BIND PACKAGE command fails because the package already exists, verify that the time and date formats that are returned by the existing packages are satisfactory. If they are, the existing packages can be used without any change to the package list in the SPUFI plans. However, if you need to change the time and date formats that are returned by the existing packages, you must bind new packages with different collection identifiers that have been agreed to by the database server.
For example, if the collection identifiers are PRIVATCS and PRIVATRR, the commands for doing a remote bind are as follows:
```
BIND PACKAGE (location_name.PRIVATCS) MEMBER(DSNESM68)
             ACTION(ADD) ISOLATION(CS) LIB('prefix.SDSNDBRM')

BIND PACKAGE (location_name.PRIVATRR) MEMBER(DSNESM68)
             ACTION(ADD) ISOLATION(RR) LIB('prefix.SDSNDBRM')
```
Bind the SPUFI plans to include the packages for all target remote locations, including other Db2 for z/OS servers. To include all locations, use an asterisk as the location name of the collection ID.
For example, use the following commands:
```
BIND PLAN(DSNESPCS) -
     PKLIST(*.DSNESPCS.DSNESM68, -
            *.DSNTIAP.DSNTIAP) -
     ISO(CS) CURRENTDATA(YES) ENCODING(EBCDIC) ACTION(REPLACE)
BIND PLAN(DSNESPRR) -
     PKLIST(*.DSNESPRR.DSNESM68, -
            *.DSNTIAP.DSNTIAP) -
     ISOLATION(RR) ENCODING(EBCDIC) ACTION(REPLACE)
BIND PLAN(DSNESPUR) -
     PKLIST(*.DSNESPUR.DSNESM68, -
            *.DSNTIAP.DSNTIAP) -
     ISOLATION(UR) ENCODING(EBCDIC) ACTION(REPLACE)
```
The SPUFI plans at the Db2 system must be rebound because the location name parameter (which is usually optional) must be explicitly specified for the remote access functions to construct the correct package name. (SPUFI does not use the SQL statement SET CURRENT PACKAGESET.) The location name entry in the package list must precede any pattern-matching character entry. For example, the package list for the DSNESPCS plan is as follows:
```
PKLIST(location_name.PRIVATCS.DSNESM68, -
       *.DSNESPCS.DSNESM68, -
      *.DSNTIAP.DSNTIAP)
```
The package list for the DSNESPRR plan is as follows:
```
PKLIST(location_name.PRIVATRR.DSNESM68, -
       *.DSNESPRR.DSNESM68, -
      *.DSNTIAP.DSNTIAP)
```
The package list for the DSNESPUR plan is as follows:
```
PKLIST(location_name.PRIVATUR.DSNESM68, -
       *.DSNESPUR.DSNESM68, -
      *.DSNTIAP.DSNTIAP)
```