Edit the IPLINPUT.TXT File

The DEV Statement

This section provides the DEV statement syntax needed to establish a connection between Thoroughbred products and ODBC-compliant databases, and a sample specification.

Syntax for an ODBC server device

DEV DX,type,param-1,server-flag,param-3,param-4,param-5,server-ID:arguments

DEV: begins the DEV statement. The statement begins in the leftmost column.
D: X is the device ID, which Thoroughbred Basic uses to reference the ODBC server. Valid values range from D0 through D9 and DA through DZ. You can specify up to 36 logical and physical devices.

ODBC server specifications do not have to follow a set order. For example, you can specify the D0 disk after you specify the D1 disk.

type: specifies the device type. For an ODBC server, the only valid value is 1.
param-1: is a positional parameter. For ODBC servers do not specify a value for this parameter.
server-flag: is a positional parameter. It specifies that the disk directory is located on a server, and specifies the server type. For ODBC servers, the only valid value is 3.
param-3: is a positional parameter. For ODBC servers do not specify a value for this parameter.
param-4: is a positional parameter. For ODBC servers do not specify a value for this parameter.
param-5: is a positional parameter. For ODBC servers do not specify a value for this parameter.
server-ID: [:arguments] is a positional parameter. It specifies the ODBC, and any information needed to establish a connection to the ODBC-compliant database. Valid values are:
server-ID: is the two-character specification assigned to the ODBC server. The server-ID specification in the DEV statement must match an entry in the SERVER.MAP file.

The :arguments syntax element varies depending upon the server-ID. Some ODBC-compliant databases require only a valid server-ID specification.

:: separates server-ID from the arguments specification.
arguments: vary depending upon the server-ID. Some databases do not require arguments.

Some databases may require arguments that take the form of login/password:

login: is the login used to connect to the database. The login/password specification is optional.
/: separates ID from password.
password: is the password used to connect to the database. The login/password specification is optional.

For more information on arguments, please refer to the documentation for the relevant ODBC-compliant database management system.

Example

An example of a DEV statement for an ODBC server follows

DEV D8,1,,3,,,,S1

DEV: Begins the DEV statement.
DEV D8: Specifies that the device is called D8.
DEV D8,1: Specifies the device type for D8. Valid values are:
1: logical disk directory 4 standard dot matrix, character printer, or laser printer 5 terminal that uses Thoroughbred Basic Windows 6 terminal that uses a video card 7 terminal that does not use Thoroughbred Basic Windows 8 ghost task
D8: is defined as a logical disk directory.
DEV D8,1,,3: Specifies that the disk directory is located on an ODBC server.
DEV D8,1,,3,,,,S1: Specifies that the server-ID is S1. No further arguments are required.

The CNF Statement

The CNF statement specifies configuration information. An IPL file contains only one CNF statement, which must occupy the first line of the file.

Syntax for the CNF Statement

The CNF statement has the following format:

CNF: numparts,numdevs,numtasks,numofiles,progerr,traceflag,ofilesflag,datefrmt,dfrmtsep, strtJulday,endJulday

For the purposes of this supplement, only one parameter is important:

numdevs: is the number of device definition lines that follow. You must specify a value for this parameter.

For more information on the CNF statement, please refer to the Thoroughbred Basic Customization and Tuning Guide.

Example

This system file contains specifications Thoroughbred products need to function under the operating system. It is located in the Thoroughbred root directory. The following is an example of a small IPLINPUT.TXT file:

CNF 1,6,1,50
PTN 1,300000
PRM NOBANNER
PRM READONLY
PRM DEBUG=OOZ00
DEV D0,1,,,,,,IDL4
DEV D1,1,,,,,,WORK
DEV D9,1,,,,1,,
DEV LP,4,,,,1,,LPT1
DEV T0,5,,,,,,CON
DEV T1,7,,,,,,TTY1
IPL 1,2,T0,ID
END

To establish a connection between Thoroughbred products and ODBC-compliant databases, specify a device that requires the ODBC driver, such as:

DEV D8,1,,3,,,,S1

The 3 specifies an ODBC-compliant database that will be accessed through TS ODBC DataServer. The S1 is a server-ID that matches the entry specified in the SERVER.MAP file.

Change the CNF specification to reflect the addition of a new DEV statement.

CNF 1,7,1,50

The 6 has been changed to 7 because there are now seven DEV statements. In this example, no other changes are required.

After these edits, the sample IPLINPUT.TXT file contains the following specifications:

CNF 1,7,1,50
PTN 1,300000
PRM NOBANNER
PRM READONLY
PRM DEBUG=OOZ00
DEV D0,1,,,,,,IDL4
DEV D1,1,,,,,,WORK
DEV D8,1,,3,,,,S1
DEV D9,1,,,,1,,
DEV LP,4,,,,1,,LPT1
DEV T0,5,,,,,,CON
DEV T1,7,,,,,,TTY1
IPL 1,2,T0,ID
END

For more information on the DEV statement, please refer to the relevant chapter in this supplement and to the Basic Customization and Tuning Guide. For more information on the IPLINPUT.TXT file and the CNF statement, please refer to the Thoroughbred Basic Customization and Tuning Guide.

This operating system file defines attributes that enable Thoroughbred products to function within an operating system environment. The IPLINPUT file is an initial program load (IPL) file. By default, it is loaded into memory whenever a user starts a Thoroughbred product.

This supplement only describes the DEV statement and CNF statement needed to establish a connection between Thoroughbred products and ODBC-compliant databases. For more information on the IPLINPUT.TXT file, the DEV statement and the CNF statement, please refer to the Thoroughbred Basic Customization and Tuning Guide.

From the ODBC Client Capability Supplement, version 8.9.1. Open this page in the PDF