beautypg.com

Sources – HP Neoview Release 2.3 Software User Manual

Page 40

background image

EMP_ID = identity loader

Increments the source field VALUE_SOURCE by 10 and assigns the resulting value to the
target field VALUE_TARGET:

VALUE_TARGET = expression ":VALUE_SOURCE + 10"

Sources

The sources section describes the location of data source and target, and their provider options.

sources
{

source-definition [, source-definition ]...

}

source-definition:

specific-source [, options source-options ]

specific-source
sourcename file filename |
sourcename pipe pipename |
sourcename {odbc | jdbc} {sql sqltext|table tablename} |

sourcename jms jmsname

source-definition

One or more occurrences of source-definition, separated by a comma (,). The last
source-definition

should not use the comma separator.

sourcename

A name you create for the source. The name must be unique within the sources namespace.
sourcename

is case-insensitive and cannot exceed 64 bytes.

sourcename

file filename [options source-options]

Specifies a data file as the data source/target. filename specifies the location of the file,
including both the path and the file name.

Transporter assumes the data file is uncompressed.

Example:

Specify a plain data file, datafile_1.dat, in the current directory with source name
data1

:

data1 file "./datafile_1.dat"

sourcename

pipe pipename [options source-options]

Specifies a named pipe as the data source/target. pipename is the name of the pipe.

sourcename

{ odbc | jdbc } { sql sqltext | table tablename } [options source-options]

Specifies an SQL table or query accessed through an ODBC or JDBC data connection to
the Neoview system.

odbc, jdbc, sql, and table are keywords.

The Java client does not support ODBC sources.

Neoview SQL views and synonyms are not supported for JDBC table extracts.

tablename

is a one-part or two-part table name in the format [schema].table. For

a load operation, tablename can be a synonym or insertable view.

If schema or table is double-quoted (""), it is interpreted as an HP Neoview SQL
delimited identifier. If schema or table is not double-quoted, it is interpreted as an HP
Neoview SQL regular identifier.

Delimited identifiers differ from regular identifiers in many ways, including:

40

Control File Organization and Syntax