Converting Your Program Data Declarations. Robelle HP 3000 Qedit, HP 3000 Suprtool, ELOQUENCE

STExport lets you define the format of numeric data, including leading zeros and the position of the sign.

!COMMENT *** PREPARE DATA FOR ORACLE SQL-LOADER ***

!RUN STEXPORT.PUB.ROBELLE

IN DMRTABHM

ZERO LEADING

QUOTE NONE

COLUMNS FIXED

SIGN TRAILING

OUTPUT ABHMDATA

XEQ

EXIT

E

The resulting files are sent using the HP 3000's FTP client to the target computer with the Oracle database and are then imported with SQL*Loader.

!COMMENT *** FTP OUTPUT FILES TO DATAMART ***

!RUN FTP.ARPA.SYS open 123.456.789.012 user <<login string and password>> ascii exitOnError cd /isdmdata cd macsdata_in put ABHMDATA.pub.hsmacs ABHMDATA.txt dir quit

In SQL*Loader, use the Load Data command with the FIELDS TERMINATED BY

"," clause to insert the data into your table. This is just one example, with fixedlength fields. STExport and SQL*Loader also have options to use variable-length fields.

Converting Your Program Data Declarations

However, what about converting our code that is written in COBOL and Fortran?

For that, you must understand the concept of External Datatypes.

An External Datatype is the way an Oracle data value is presented to a user program. Since COBOL and Fortran cannot understand the internal format in which

Oracle stores numbers, Oracle allows you to specify how you would like the data returned to your program.

But, Oracle only supports the External Datatypes that are common to most computer platforms. Unusual data types are not supported.

For character type fields, you normally select CHAR unless you want nullterminated STRING for C.

For numeric fields, here are the Oracle 7 choices that make sense for fields converted from TurboIMAGE:

Migrating a 3000 Application

• 263

HP 3000 Evolution