Академический Документы
Профессиональный Документы
Культура Документы
DNA111760
Version 5.4
Warranties and Liabilities
All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract,
and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or
amendment of such warranties.
The information and the software discussed in this document are subject to change without notice and should not be
considered commitments by Intergraph Corporation. Intergraph Corporation assumes no responsibility for any
error that may appear in this document.
The software discussed in this document is furnished under a license and may be used or copied only in accordance
with the terms of this license.
No responsibility is assumed by Intergraph for the use or reliability of software on equipment that is not supplied by
Intergraph or its affiliated companies.
Trademarks
InterAct, Intergraph, and RIS are registered trademarks of Intergraph Corporation. DIALOG, InterServe, and TD1
are trademarks of Intergraph Corporation. All other brands and product names are trademarks of their respective
owners.
Copyright
1996 Intergraph Corporation
All Rights Reserved
Including software, file formats, and audiovisual displays; may be used pursuant to applicable software license
agreement; contains confidential and proprietary information of Intergraph and/or third parties which is protected
by copyright and trade secret law and may not be provided or otherwise made available without proper
authorization.
Unpublished rights reserved under the copyright laws of the United States.
Intergraph Corporation
Huntsville, Alabama 35894-0001
Table of Contents
__________________________________________________________________________________________________________________________________________________
Table of Contents
__________________________________________________________________________________________________________________________________________________
Glossary ....................................................................................................................... GL - 3
Index ............................................................................................................................ IN - 3
Before You Begin 1 - 1
1.
__________________________________________________________________________________________________________________________________________________
The RIS Utilities Guide for 32-Bit Applications describes the RIS utilities.
1.2 Audience
This document was written for application users, application designers, and computer
software specialists.
This document assumes a basic understanding of your operating system, RDBMS software,
and RIS.
For information about SQL terms and database structure, refer to documents related to
specific relational database management systems (INFORMIX, ORACLE, DB2, SYBASE, or
Microsoft SQL Server).
1-4 Before You Begin
For additional information about RIS, see the following files delivered with the RIS software.
The default location for these files is the c:\Program Files\risdp directory.
product.def Lists all dependencies and related parts for the product.
Filenames and directory paths appear in italic typeface. However, the italic typeface is
also used for emphasis of new words or important phrases. For example:
c:\windows
Command names, menu names, tools, system prompts and messages, and keys may
appear in boldface type. For example:
File menu
OR
Press Enter
The word select means to select a command by pressing the left mouse button over a
menu command or by pressing the Alt key and the underlined character
simultaneously.
The word choose means to choose a button or icon by pressing the left mouse button
over a Toolbar button, or application icon.
The word reset means to terminate a command initiated with the mouse. Reset by
pressing the right mouse button.
The word identify means to define an area or place graphic elements in a graphics file.
For PCs, identify with the left mouse button.
The phrase key in generally means to enter data into a field on a dialog box. To
advance to the next field, use the Tab key.
Before You Begin 1 - 5
main ( )
OR
commit
Words that appear in angle brackets, < >, are identifiers or names that you must
supply, or dynamic information that can change for each error message. For example:
Curly braces contain several options (used in conjunction with a logical OR symbol ( | )
or phrases that can be repeated (used in conjunction with [, ...]). A comma followed by a
series of three periods in square brackets ([, ...]) indicates that the last phrase contained
within curly braces ({}), or the last item, can be repeated numerous times (separated by
commas).
For example: { <column> <data type> } [, ...] means that numerous column names and
associated data types can be specified (separated by commas).
The logical or symbol ( | ) separates phrases or keywords within curly braces ({}) that
can be used alone but not together.
For example: { user | database } means that either the user keyword or the
database keyword can be specified, but not both.
This symbol cautions about operations that can cause limited damage.
This symbol warns about operations that can cause severe damage.
1-6 Before You Begin
On-line Help is an on-line reference tool accessible at any time the application is in use. The
on-line Help contains a description for each command and tool and step-by-step procedures
for common tasks. For example, if you need to perform a certain task, search and display the
topic. You can move or resize your application and Help windows so that they are next to
each other. This lets you follow the procedures without having to search for the pages in the
documentation.
Before You Begin 1 - 7
To view the on-line Help, select Contents from the Help menu. To get more specific
information, select one of the major topics or perform a search on a specific topic.
1-8 Before You Begin
Use To
If the graphics in the on-line Help appear distorted, check your graphics driver.
If you are using an Intergraph TD1 machine, the S3 1024x768 256 color (Large
Font) distorts the graphics slightly. Changing to the (Small Font) version
corrects the display. If you are using other drivers, check with your PC manual
for information about available graphics drivers.
Getting Started 2 - 1
Getting Started
__________________________________________________________________________________________________________________________________________________
2-2 Getting Started
Getting Started 2 - 3
2.
__________________________________________________________________________________________________________________________________________________
Getting Started
The Intergraph Relational Interface System (RIS) is a generic interface to relational
database management systems (RDBMSs). RIS offers simultaneous connections to RDBMSs
from many vendors on dissimilar hardware platforms using numerous protocols. RIS makes
an entire network of databases available as if there were a single, local database.
During installation, the RIS utilities path is added to the system path
environment variable. By default, the utilities are loaded in c:\Program
Files\Common Files\Intergraph\ris05.nn\bin.
RIS Utilities:
Transfers data from specially formatted files into new or existing schemas.
Reads and executes files containing RIS commands generated by applications and
captured with the risrecrd utility.
2-4 Getting Started
Records all SQL statements and timing data into specially formatted files. Useful for
repeating long sequences when trying to uncover program problems.
Extracts data from a schema and places it into specially formatted files.
Converts a schema (dictionary and schema file) from RIS Version 4 to RIS Version 5.
Refer to the RIS Installation Guide for 32-Bit Applications for information concerning
products needed to use the RIS Utilities.
risbatch 3 - 1
risbatch
__________________________________________________________________________________________________________________________________________________
3-2 risbatch
risbatch 3 - 3
3.
__________________________________________________________________________________________________________________________________________________
risbatch
This utility is a simple, shell-callable program providing easy access to RIS and to underlying
databases. The primary purpose of this utility is batch execution of SQL statements.
Any SQL statement can be specified in an input file, provided that you have the proper
access.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Batch icon:
3-4 risbatch
Usage
______
risbatch [-?] [-V] [-i <infile>] [-o <outfile>]
Flags
_ ____
-i <infile> Specify the input file containing the RIS SQL statements. The
locate client command prompts for the client version.
Examples
_________
In this example, risbatch is invoked with the input file input.sql and the output file
output.sql:
Files
_____
Status Returns
______________
0 Normal termination.
other Abnormal termination.
risclnsr 4 - 1
risclnsr
__________________________________________________________________________________________________________________________________________________
4-2 risclnsr
risclnsr 4 - 3
4.
__________________________________________________________________________________________________________________________________________________
risclnsr
This interactive utility deletes all nonessential records from the RIS dictionary tables. This
utility is provided to clean up when the server process has not been able to do so. The server
fails to clean up when it is killed or the machine is shutdown or rebooted.
Do not run this utility while the schemas to be cleaned are being accessed.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Clean Server
icon:
4-4 risclnsr
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS Interactive
icon. Choose the Utilities... button from the RIS Interactive form; then choose the RIS
Clean Server... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the Restart
button before RIS Interactive is aware of any RIS parameter changes, or
creating or dropping of schemas.
Usage
______
risclnsr [-?] [-V] schema[.password] [user[.password]] [osuser[.password]]
The osuser[.password] option specifies the user and password for a secure schema. If the
schema specified is a secure schema, risclnsr prompts for the osusername and osusername
password (if one exists).
Flags
_ ____
<none> If you do not specify any command-line arguments, or if you start the
utility by selecting its icon from the Program Manager, the utility runs
interactively and prompts for the necessary information.
Files
_____
Status Returns
______________
0 Normal termination.
1 Abnormal termination.
risdcode 5 - 1
risdcode
__________________________________________________________________________________________________________________________________________________
5-2 risdcode
risdcode 5 - 3
5.
__________________________________________________________________________________________________________________________________________________
risdcode
This utility prints error messages for RIS error codes.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Decode icon:
5-4 risdcode
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS Interactive
icon. Choose the Utilities... button from the RIS Interactive form; then choose the RIS
Decode... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the Restart
button before RIS Interactive is aware of any RIS parameter changes, or
creating or dropping of schemas.
Usage
______
risdcode [-?] [-V] [<error code>]
Flags
_ ____
<none> If you do not specify any command-line arguments, or if you start the
utility by selecting its icon from the Program Manager, the utility runs
interactively and prompts for the necessary information.
Examples
_________
To get the error message corresponding to an error code of 100, key in one of the following:
risdcode
You are prompted to key in the value to be decoded. In this case, key in 100.
risdcode 5 - 5
Files
_____
Status Returns
______________
0 Always zero.
5-6 risdcode
risdtype 6 - 1
risdtype
__________________________________________________________________________________________________________________________________________________
6-2 risdtype
risdtype 6 - 3
6.
__________________________________________________________________________________________________________________________________________________
risdtype
This interactive utility lets you instruct RIS to interpret the data type of a column differently
and modify the size of a RIS_BLOB/RIS_TEXT data type.
The variety of data types in database systems permits multiple mappings of database data
types to ANSI standard data types. When a schema is created, or a table is included in a
schema, RIS chooses one interpretation of a data type. This utility lets you instruct RIS to
interpret the data type of a column differently by prompting you for the schema name,
username (for secure schemas), password (if one exists), table names, column names, and
new data types.
The environment variable RIS_LANGUAGE specifies the language that RIS uses for parsing
and error messages. The default is English. Consult the file c:\Program Files\Common
Files\Intergraph\ris05.nn\config\langs for other values.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Data Types
icon:
6-4 risdtype
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS Interactive
icon. Choose the Utilities... button from the RIS Interactive form; then choose the RIS
Data Types... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the Restart
button before RIS Interactive is aware of any RIS parameter changes, or
creating or dropping of schemas.
Example:
c:\risdtype
Enter schema (<CR> to exit):sch1
Enter a table or view name (or ? for a list of names):
>blob_table
Do you wish to modify this column? <y(es), n(o), d(one with table)>>yes
0 UNSUPPORTED
1 CHARACTER
2 RIS_BLOB
6 RIS_TEXT
Choose a data type from those listed (enter the number) >>2
Current maximum ris_blob length is:0
Current maximum ris_blob length is:10000
Current status for nullable is YES, nulls are allowed
Are null values allowed? <y(es), n(o)> >>yes
Column definitions modified for object sch1.blob_table:
risdtype 6 - 5
Usage
______
risdtype [-?] [-V]
Flags
_ ____
<none> If you do not specify any command-line arguments, or if you start the
utility by selecting its icon from the Program Manager, the utility runs
interactively and prompts for the necessary information.
Files
_____
Status Returns
______________
0 Normal termination.
1 Abnormal termination.
6-6 risdtype
risgui 7 - 1
risgui
__________________________________________________________________________________________________________________________________________________
7-2 risgui
risgui 7 - 3
7.
__________________________________________________________________________________________________________________________________________________
risgui
The risgui utility lets you interactively perform RIS queries. To start the risgui utility, do
one of the following:
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Interactive
icon.
7-4 risgui
2. Key an SQL statement into the Query field. You must terminate the SQL
statement with a semicolon character (;). The statement can wrap across several
lines.
If you need to change the entry, select the Clear button to clear the
Query field, then enter the statement again.
3. Select the Execute button. The results appear in the Results field.
If the query results do not completely fit in the Results field, the risgui utility can
display a screenful at a time. For more information see the section Options....
Select the Continue button to display the next screenful, or the Abort button to
stop the query.
risgui 7 - 5
To save the query results in a file, select the Save Results... button.
History File
When you execute a query, the risgui utility saves the SQL statement in the history
file. To determine the name of the history file, the ris utility uses the file:
3. ris.his in the directory from which you started the risgui utility, if the HOME
environment variable is not defined.
When risgui saves a query in the history file, you can go back to the same query later
and execute it again or edit the SQL statement to use it as the basis for a new query.
Select the Previous or Next buttons to display the queries in the history file.
To save the current query (shown in the Query field) to a file, select the Save... button.
To load a previously-saved query, select the Open... button.
To save the results of the current query, select the Save Results... button.
7.3 Options...
2. To specify the behavior for query results that do not fit in the Results field, select
one of the following:
3. Select the OK button to accept the settings or select the Cancel button to reject
them.
risgui 7 - 7
7.4 Utilities...
The Utilities... button lets you start the other RIS utilities from within the risgui
utility.
7.5 Restart
While you are running the RIS Interactive utility, you can run other RIS utilities;
however, if you modify the RIS parameters with the other utilities, or create or drop a
schema, the RIS Interactive utility is not aware of the changes.
Select the Restart button to restart risgui and make it aware of your changes. Your
selection of modes, enabled databases, and default schema is not altered.
7-8 risgui
7.6 Set...
The Set... button sets RIS modes and enables the databases.
ANSI Mode
Verify Mode
Autocommit
Autorename
Refer to the RIS SQL Users Guide for more information on the RIS modes.
Informix
Ingres
Rdb
ORACLE
DB2
SYBASE
MSSQL
risgui 7 - 9
7.7 Show...
The Show... button gives you additional information about RIS on your system.
rislod
__________________________________________________________________________________________________________________________________________________
8-2 rislod
rislod 8 - 3
8.
__________________________________________________________________________________________________________________________________________________
rislod
You must understand the risunlod utility before using the rislod utility.
The rislod utility permits the transfer of schema information between external ASCII
files and RIS schemas by loading schema information from external files into RIS
schemas.
rislod:
Reads schema information from the main external file and data files (if any) and
restores them in the form of RIS schemas.
Lets information about multiple schemas be stored in the same external main file.
May create two files to report the loading status: the log file reports successful
loading and the bad file reports unsuccessful loading.
The rislod and risunlod utilities are not designed for use as backup utilities. The
following are some reasons for not using rislod and risunlod as backup utilities:
If a view was created in the database (not with RIS), RIS cannot unload the
definition of the view.
If you drop a schema and then recreate the schema, and there were existing views,
RIS cannot load the definition of the view because RIS lost the definition when
you dropped the schema.
In certain cases data types are mapped slightly differently in ORACLE databases.
ORACLE uses numeric data types, and RIS uses integer, smallint, real, and
double. If you create a column of RIS data type real, it is mapped to a float(21)
ORACLE data type. If you drop the schema, then recreate the schema, RIS maps
the float(21) in ORACLE to a RIS double data type.
For these and further reasons, you should use the databases utilities to back up data
correctly.
The environment variable RIS_LANGUAGE specifies the language that RIS uses for
parsing and error messages. The default is English. Consult the file c:\Program
Files\Common Files\Intergraph\ris05.nn\config\langs for other values.
8-4 rislod
The following figure represents the functional mechanisms of rislod and shows the
input requirements and output generated.
Data for ris_blob and ris_text columns cannot be loaded; however, you can
have ris_blob and ris_text columns in a create table statement.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Loader
icon:
rislod 8 - 5
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS
Interactive icon. Choose the Utilities... button from the RIS Interactive form; then
choose the RIS Loader... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the
Restart button before RIS Interactive is aware of any RIS parameter
changes, or creating or dropping of schemas.
Usage
______
rislod [-?] [-V] [-n] [-p] [-e <db_list>]
[-m {w|a|e}] [-i <filename>] [-b <filename>] [-d <delimiter>]
[-c <commit>] [-s <schemas>] [-f <filename>]
Flags
_ ____
<none> If you do not specify any command-line arguments, or if you start the
utility by selecting its icon from the Program Manager, the utility runs
interactively and prompts for the necessary information.
-n Set ANSI mode off. ANSI mode is on by default. Refer to the set
mode statement in the RIS SQL Users Guide for 32-Bit Applications
for more information.
-e <db_list> Enable the database specified in the <db_list>. All databases are
enabled by default. Refer to the set enable database statement in
the RIS SQL Users Guide for 32-Bit Applications for more information.
8-6 rislod
-m {w|a|e} Specify the file mode for output files. The w overwrites an existing file,
the a appends to an existing file, and the e returns an error if an
output file with the specified name exists.
-i <filename> Specify the main input ASCII file from which RIS schema information
is loaded. The default main filename is ris.dmp.
-l <filename> Specify the log file into which RIS schema status information is
recorded. The default log filename is ris.log.
-b <filename> Specify the bad file into which rejected RIS schema information is
dumped. The default bad filename is ris.bad.
-d <delimiter> Specify the character for delimiting column values of character type
while loading rows in a table. A single quotation mark () is the default
delimiter character.
-c <commit> Specify the commit interval value that informs the loader to commit
after inserting <commit> number of rows for a table. The default
<commit> value is 25.
-f <filename> Specify the name of the specification file for <schemas>. This option
cannot be used with the -s option.
See the section Using rislod with the Command Line Interface for more detailed
information.
Files
_____
Status Returns
______________
0 Normal termination.
1 Abnormal termination.
rislod loads user-requested RIS schema objects (items) from external ASCII files into
RIS schemas. rislod can:
Delete records from the table before loading table data from external file
Overwrite or append the log and bad files or return error if files exist
The ANSI mode can be turned on or off, depending upon your requirements,
before starting the loading execution.
rislod lets you enable specific databases before starting the loading execution.
You can specify that rislod report errors while loading data into a table, if the
table already exists. You can also specify that rislod load data into existing tables
or delete data from existing tables before loading.
Not imposing the order of information stored in the main external file
There are three ways to interact with rislod: using the Interactive Interface, the
Command Line Interface, or the Embedded Programming Function Interface.
See the section Using rislod with the Interactive Interface for more information
about the meanings of these prompts and the corresponding actions taken by
rislod.
2. Command Line Interface. When rislod is invoked with arguments, the rislod
command line interface activates. This interface lets you specify, in a single
command, the responses to various prompts that would have been generated if
rislod had been invoked interactively. Errors encountered during parsing are not
reported in the log or bad file, and rislod terminates abnormally.
See the section Using rislod with the Command Line Interface for more
information about the syntax for constructing a rislod command and the
semantics of the command.
When rislod begins execution, it creates a log file. The default log filename is ris.log.
You can specify a different name for the log file. The log file can be opened in overwrite
or append mode. If rislod cannot create a log file, execution terminates.
The log file contains a detailed summary of the execution with several sections:
Section . . . Contains . . .
As it executes, rislod creates a file called the bad file. The bad file contains all schema
item definition statements that rislod attempted to load but could not. These
statements could be create schema, create table, insert, table field
definition, create index, create view, or grant statements. The default
name for the bad file is ris.bad, but you can specify a different name for the file.
Statements that fail to load are dumped to the bad file with appropriate error codes and
error messages. These error codes and messages are commented so the bad file can be
used again, after it is edited or corrected, to load rejected schema information.
For example, if rislod cannot load a schema statement, then all the schema information
pertaining to this schema is dumped to the bad file. Or, if the create table
statement fails, and data are to be loaded in this table, then all table data statements
such as create table, insert, table field definition, and data statements
are dumped to the bad file. The error messages are ignored by rislod.
8 - 10 rislod
Additionally, the status of each schema item being loaded is echoed to the screen in the
interactive and command line interfaces.
For an index to be loaded, the table it references must exist. Similarly, for a view to be
successfully loaded, all the tables and views it references must exist. To successfully
load a privilege definition (a grant statement), the grantee, relation, and access
privileges referenced in the statement must also exist. To take away the burden of
organizing information into a proper order for loading, rislod postpones the loading of
the index, view, or privilege definition until its references have been loaded.
When an index definition in a schema is fetched, rislod tries to load it. If rislod receives
an error message from RIS stating that the table on which the index is created does not
exist, the index definition is stored in a temporary file. After rislod has tried to load
every statement in the schema once, it attempts to load the indexes from the temporary
file again. The same thing happens to a view definition that could not be loaded the
first time because its references did not exist. rislod continuously loads these views in
the temporary file until all of them have been loaded or until no more views can be
loaded successfully.
When rislod fetches a privilege definition in a schema, it is broken down into several
grant statements, one for each grantee specified. rislod tries to load each of the new
grant statements. If RIS notifies rislod that the statement could not be loaded, the
grant statement is stored in a temporary file along with the information about the
schema to which it belongs. After rislod tries to load every statement in the files at
least once, rislod tries to load the grant statements in the temporary file again. rislod
continuously loads these grant statements until either all of them have been loaded or
no more grant statements can be loaded successfully. In this approach you may notice
the breakdown of a grant statement and notice that some of the grant statements are
loaded at the end of a rislod session.
Invoking rislod without any command line arguments displays interactive prompts.
Accepting Default Values. Most prompts have default values indicated in square
brackets ([]). Press the ENTER key to select these default values.
Specifying Other Information. Some prompts ask you to enter information, such as
filenames. Key in the information requested and press ENTER.
rislod 8 - 11
The default is set ANSI mode on. See the RIS SQL Users Guide for 32-Bit
Applications for more information.
This prompt lets you set the blankstrip mode. By default rislod strips trailing
blanks from character data.
Press ENTER to accept the default if you do not want to preserve trailing
blanks.
This prompt lets you enable databases during the loading of a schema.
4. File mode of all output files? overwrite(w) append(a) error out if exists(e) :[e] >
This prompt lets you set the file mode for log and bad files. The file mode affects
the log and bad files only. The default is e, error out mode.
Press ENTER to accept the default; when you are prompted for the log and
bad filenames, rislod prompts you to quit if the files you specify already
exist.
8 - 12 rislod
This prompt lets you specify the name of the main file for loading. The default
name for the main file is ris.dmp.
This prompt lets you specify the name of the log file for loading. The default name
for the log file is ris.log.
If you selected e for error out mode at the prompt File mode of all output files?,
and a file with the name you specify exists, the message Log File already exists is
displayed. You are prompted:
Press ENTER to accept the default. You are again prompted to enter a
name for the log file; key in a new filename.
This prompt lets you specify the name of the bad file for loading. The default
name for the bad file is ris.bad.
If you selected e for error out mode at the prompt File mode of all output files?,
and a file with the name you specify exists, the message Bad File already exists is
displayed. You are prompted:
Press ENTER to accept the default. You are again prompted to enter a
name for the bad file; key in a new filename.
This prompt lets you specify the delimiter to use for enclosing character values of
variable lengths to use in the main and data files.
The commit interval lets you commit the insertion of rows in a table after the
specified commit interval value. The default is 25 (commit after inserting 25 rows
in a table).
This prompt lets you choose between loading all the schemas or only selected
schemas from the main file. The default is a for all schemas.
8 - 14 rislod
Press ENTER to load all the schemas from the main file.
Prompts let you choose how to load tables, indexes, views, and privilege
definitions. These prompts appear once, after the prompt for the schema, if
you choose to load all the schemas in the main file.
Select p and rislod generates a list of schemas and prompts you before
loading each schema. (After each schema is selected, you are prompted for
how to load tables, indexes, views, and privilege definitions for that schema.)
Select y to load the specified schema. If you select p at the prompt Which
schemas should be loaded? and you select y at this prompt, you are
prompted to optionally load into another existing schema:
Enter the name of an existing schema. rislod then prompts for the
username, user password, and schema password, if necessary, for the
specified schema.
rislod lets you rename schemas only if the prompted (p) selection was
made at the Which schemas should be loaded? prompt.
If the schema is a secure schema, you are prompted for the database
username, the database username password, the operating system
username, and the operating system username password. If the
schema has a password, you are prompted for the schema password.
Press ENTER to accept the default and load all the tables in the schema.
If you select a or p at the prompt Which tables should be loaded? the following
prompt appears next:
This prompt lets you decide whether to load both the definitions and data of the
tables in the schema or load only the definitions.
Press ENTER to accept the default and load both table definitions and data.
If you select b at the prompt Both definitions and data(b) definitions only(o) the
following prompt appears:
Press ENTER to accept the default and data are not loaded into an
existing table.
Select y to delete all rows from this table before loading data from the
main file.
Press ENTER to accept the default and load all index definitions.
Select p and rislod generates a list of indexes and prompts for each index
definition:
Press ENTER to accept the default and load all privilege definitions.
Select p and rislod prompts for each table or view on which one or more
privileges are defined:
If you selected p at the prompt Which table should be loaded? the following prompt
is displayed.
Press ENTER to accept the default and load the specified table.
When all the necessary information has been specified, rislod processes the schema(s)
selected.
The command line can be used to specify which schemas in the main file should be
loaded. It can also be used to specify which information in the schemas should be
loaded. The syntax for constructing a rislod command is almost the same as the syntax
for constructing a risunlod command, except for a few additions and changes.
Examples
rislod -i \dir1\dir2\mainfile -d\" -l load.log -b load.bad
-f ..\dir3\specfile -n -mw -e rdb informix -c 15
Option Specifies
8 - 18 rislod
-d Delimiter. The default is a single quotation mark (). The delimiter in this
example is a double quotation mark. The backslash before the delimiter
causes the shell not to interpret the double quotation mark.
Option Specifies
-m Set the file mode (w, a, or e) for the output files (such as log and bad files).
-c Commit interval.
rislod lets you specify up to three passwords after a schema name (schema password,
osuser password, and user password). Passwords are necessary if they are not already
stored in the main file. For schema sch2, data is loaded only into newly created tables.
For schema sch3, data is loaded into tables t1 and t2 after deleting previously inserted
rows even if it already exists before loading. For schema sch4 all the following items
are loaded into existing schema sch5. No data is loaded into table t1, but index
definitions on table t1 and privilege definitions on table t1 and view view1 are loaded.
The specification file format is the same for both rislod and risunlod.
Backus Naur form (BNF) is a method of describing the syntax of a language. It is used
here to show the capabilities of the RIS command line interface.
The following is the BNF representation of the syntax for constructing a command line.
rislod 8 - 19
<file_mode> ::= w | a | e
w represents overwrite file mode
a represents append file mode
e represents return error
The following is the BNF representation of the format for a specification file.
rismgr
__________________________________________________________________________________________________________________________________________________
9-2 rismgr
rismgr 9 - 3
9.
__________________________________________________________________________________________________________________________________________________
rismgr
This utility creates, changes, and drops RIS schemas. You can also use it to display
information about existing schemas.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Schema
Manager icon:
9-4 rismgr
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS
Interactive icon. Choose the Utilities... button from the RIS Interactive form; then
choose the RIS Manager... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the
Restart button before RIS Interactive is aware of any RIS parameter
changes, or creating or dropping of schemas.
Usage
______
rismgr
Files
_____
Status Returns
______________
0 Normal termination.
1 Abnormal termination.
rismgr 9 - 5
9.1
__________________________________________________________________________________________________________________________________________________
Operating Sequence
2. Choose the button from the RIS Schema Manager dialog box for the function
you want to use. The RIS Schema Manager functions are described briefly in the
following list. See the section listed for a complete description.
Schema File Lets you review and manipulate schema files. See the
section Reviewing and Manipulating Schema Files.
Locate Client Lets you review and specify the location of a RIS client
process. See the section Locating RIS Client Processes.
Choose the Close button to end the RIS Schema Manager session.
9.2
__________________________________________________________________________________________________________________________________________________
Schema Definition
The Schema Definition dialog box lets you initiate functions to display schema
information, create and drop schemas, access secure schemas and dictionaries, and
modify schema passwords, node information, and DB2 passwords.
Operating Sequence
1. Choose the Schema Definition button from the RIS Schema Manager dialog
box.
The dialog box has eight buttons, each letting you initiate a particular function.
Choose the button from the Schema Definition dialog box for the function
you want to use. The Schema Definition functions are described briefly in
the following list. See the section listed for a complete description.
Modify Schema Password Modifies the schema password. See the section
Modifying Schema Passwords.
Modify DB2 Password Modifies the DB2 password. See the section
Modify DB2 Password Form.
Choose the Close button to dismiss the Schema Definition dialog box.
9.2.1
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Choose the Schema Information button from the Schema Definition dialog
box.
The Schema Information dialog box appears and displays information about the
selected schema (if one has been selected from the RIS Schema Manager dialog
box).
2. Do one of the following if the schema you want is not already the selected schema:
Select a schema from the Schema Name list on the RIS Schema Manager
dialog box.
9.2.2
__________________________________________________________________________________________________________________________________________________
Creating Schemas
The Create Schema dialog box creates new RIS schemas and corresponds directly to
the RIS create schema statement. The database-specific information on the Create
Schema dialog box can be entered in three ways:
By entering the information directly in the boxes. If the schema is being created
on a database unknown to RIS, this is the only alternative.
By selecting an existing schema from the RIS Schema Manager dialog box. The
database-specific information about that schema is entered into the Create
Schema dialog box. This method is particularly convenient when creating
additional schemas on a database.
By selecting the Display Databases button. A dialog box listing all the known
RIS databases appears. Selecting one of these databases enters information about
that database into the Create Schema dialog box.
Operating Sequence
1. Select the Create Schema button from the Schema Definition dialog box.
2. Enter the appropriate values for the DBMS-independent section of the dialog box.
The following list explains the DBMS-independent controls.
Schema Name Type a name for the schema you want to create.
Schema Type Click this button to toggle between Standard and Secure
schemas.
To change the order of the Network Protocol boxes, select one Network
Protocol box and its value is replaced with the value of the Network Protocol
box below it. The value that was originally selected is moved to the bottom
of the list.
Get Client Address Click this button to enter the addresses of the client
machine in the Nodename or Address boxes. This is useful when the RIS
client and the RIS data server are on the same machine.
OS Type From the list, select the operating system type on which the RIS
data server is running.
Select a database type from the Database Type list. If the selected
database type requires additional information, boxes to enter that
information are displayed when you select the database type.
INFORMIX
ORACLE
DB2
SYBASE
MSSQL
The Databases dialog box appears. Databases known to RIS are listed on
this dialog box. Select a database from the dialog box. Controls containing
information specific to the database selected are shown on the Create
Schema dialog box.
4. See the section specific to the type of database on which you are creating the
schema for instructions on filling in the DBMS-dependent boxes.
9.2.2.1
__________________________________________________________________________________________________________________________________________________
Operating Sequence
For the INFORMIX Standard Engine product, the <dbname> must be a full
pathname (for example, /usr2/informix/dbnam1). On UNIX systems, the
filename portion cannot be longer than ten characters because INFORMIX
adds a DBS suffix to it.
For the INFORMIX OnLine Engine product, the <dbname> needs only to be
the database name.
For the INFORMIX Standard Engine product, the <dbname> must be a full
pathname and must include the INFORMIX server name with the @
separator: </C=/dbs/dbname@servername>
9 - 16 rismgr
For the INFORMIX OnLine Engine product, the <dbname> must include only
the INFORMIX server name with the @ separator: <dbname@servername>
This parameter is not used when the RIS Data server resides
on a Windows NT node. If the RIS data server resides on a
Windows NT node this information is obtained from the
registry.
DBTEMP Enter the path where INFORMIX will create temporary files.
To drop previously created RIS dictionary objects (such as RIS tables, views,
indexes, and schema privileges) before creating the new schema, click the
Force button.
To dismiss the dialog box without creating a schema, click the Close button.
rismgr 9 - 17
9.2.2.2
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Enter the appropriate values for the ORACLE-dependent controls. The following
list explains these controls.
For a given ORACLE SID, all schemas created using that SID
must have the same operating system username and password
combination.
9 - 18 rismgr
To drop previously created RIS dictionary objects (such as RIS tables, views,
indexes, and schema privileges) before creating the new schema, click the
Force button.
To dismiss the form without creating a schema, click the Close button.
rismgr 9 - 19
9.2.2.3
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Enter the appropriate values for the DB2-dependent controls. The following list
explains these controls.
Group Name Enter the RACF group name for TCPIP protocol. The RACF
group name is passed to the RIS Transaction Processor security exit on the
IBM mainframe system for use during sign-on processing. (Optional.)
IBM Network Protocol From the list, select the network protocol that RIS
uses to access the IBM machine on which the DBMS resides. The protocol is
LU6.2.
The following controls are valid for LU6.2 network protocol only:
RIS LU Name Enter the SSI local LU name, either fully qualified or
local. This name is case sensitive.
Host LU Name Enter the SSI remote LU name, either fully qualified
or local. This name is case sensitive.
Host Program Name Enter the name the IBM System Administrator
assigned the RIS server when it was installed on the IBM machine. Also
enter the CES transaction name. This name is case sensitive.
To drop previously created RIS dictionary objects (such as RIS tables, views,
indexes, and schema privileges) before creating the new schema, click the
Force button.
To dismiss the dialog box without creating a schema, click the Close button.
9 - 22 rismgr
9.2.2.4
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Enter the appropriate values for the SYBASE-dependent controls. The following
list explains these controls.
Database Name Enter the name of the database the schema accesses.
DSQUERY Enter the database query listener. This value is the alias
given in the interfaces file. The default name is SYBASE. This information
is not required for all servers.
rismgr 9 - 23
IFILE Enter the name of the interfaces file for the schema. By default,
RIS uses the SYBASE interfaces file named interfaces. On 32-bit operating
systems the ifile is named sql.ini. This information is not required for all
servers.
To drop previously created RIS dictionary objects (such as RIS tables, views,
indexes, and schema privileges) before creating the new schema, click the
Force button.
To dismiss the dialog box without creating a schema, click the Close button.
9 - 24 rismgr
9.2.2.5
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Enter the appropriate values for the Microsoft SQL Server-dependent controls.
The following list explains these controls.
Database Name Enter the name of the database the schema accesses.
IFILE Enter the name of the interfaces file for the schema. By default,
RIS uses the SQL Server interfaces file named interfaces. This information
is not required for all servers.
rismgr 9 - 25
To drop previously created RIS dictionary objects (such as RIS tables, views,
indexes, and schema privileges) before creating the new schema, click the
Force button.
To dismiss the dialog box without creating a schema, click the Close button.
9 - 26 rismgr
9.2.3
__________________________________________________________________________________________________________________________________________________
Dropping Schemas
The Drop Schema dialog box drops schemas using the information you specify and
corresponds directly to the RIS drop schema statement.
Operating Sequence
1. Choose the Drop Schema button from the Schema Definition dialog box.
The Drop Schema dialog box appears and displays the name of the selected
schema (if one has been selected from the RIS Schema Manager dialog box).
2. Do one of the following, if the schema you want to drop is not already the selected
schema:
In the Schema Name box on the Drop Schema dialog box, type the
schema name.
From the Schema Name list on the RIS Schema Manager dialog box,
select a schema.
If the schema is a secure schema, a dialog box appears. Enter the database
username, database password, operating system username, and operating system
password in the dialog box, if displayed.
To drop previously created RIS dictionary objects (such as RIS tables, views,
indexes, and schema privileges), click the Force button.
To dismiss the Drop Schema dialog box without dropping the schema, click
the Close button.
9.2.4
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Select the Secure Schema Access button from the Schema Definition dialog
box.
If a schema has already been selected from the RIS Schema Manager dialog
box, this schema information appears on the Secure Schema Access dialog box.
2. Do one of the following, if the schema you want is not already the active schema:
Select a schema from the Schema Name list on the RIS Schema Manager
dialog box.
Enter a name into the Schema Name box to display information about a
schema.
3. Click the Action button to toggle between granting and revoking secure schema
access.
rismgr 9 - 29
4. Click the Privilege button to toggle between granting and revoking resource and
connect privileges.
To grant or revoke privileges to the secure schema, click the Apply button.
To dismiss the Secure Schema Access dialog box without altering schema
access, click the Close button.
Choose the Help button to obtain help with granting and revoking schema
access privileges.
9 - 30 rismgr
9.2.5
__________________________________________________________________________________________________________________________________________________
Operating Sequence
Select the Dictionary Access button from the Schema Definition dialog box.
1. Do one of the following, if the schema you want is not already the selected schema:
Select a schema from the Schema Name list on the RIS Schema Manager
dialog box.
2. Click the Action button to toggle between granting and revoking access.
Enter the name of the user to be granted or revoked access in the Selected
User box.
Choose the Help button to obtain help with granting and revoking
dictionary access privileges.
9 - 32 rismgr
9.2.6
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Select the Modify Schema Password button from the Schema Definition
dialog box.
2. Do one of the following, if the schema you want is not already the selected schema:
Select a schema from the Schema Name list on the RIS Schema Manager
dialog box.
If the schema is a secure schema, the Username Password dialog box appears.
To modify the schema password, click the Apply button. You must click the
Apply button after each session to alter the schema.
To dismiss the dialog box without altering the schema, click the Close
button.
To obtain help with modifying schema passwords, click the Help button.
rismgr 9 - 33
9.2.7
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Select the Modify Node Information button from the Schema Definition
dialog box.
2. Select a schema from the Schema Name list on the RIS Schema Manager
dialog box or type a schema name in the Schema Name box to display
information about a schema, if there is no selected schema.
3. Choose the Modify Node button from the dialog box. The current addresses
display in the Nodename or Address boxes.
Type the new names or addresses in the boxes. This action can also be used to
change the order of the protocols.
4. Choose the Modify DB User Password button. The database user associated
with the schema appears in the DB Username box. This is a read-only box.
5. Type the database user password in the Password box. The No Echo/Echo
button causes the password to not display (No Echo) or display (Echo) when it is
entered.
9 - 34 rismgr
This action does not change the users operating system account
password. It changes only the RIS product copy of the user
password. Typically this command is executed after users change
their operating system account passwords. Otherwise an error
occurs.
6. Choose the Modify OS User & Password button. The operating system user
associated with the schema appears in the OS Username box. Type a new
username.
7. Type the operating system user password in the Password box. The No
Echo/Echo button causes the password to not display (No Echo) or display (Echo)
when it is entered.
To alter the schema, click the Apply button. You must select the Apply
button after each session to alter the schema.
To dismiss the dialog box without altering the schema, click the Close
button.
To obtain help with modifying node information, click the Help button.
rismgr 9 - 35
9.2.8
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Choose the Modify DB2 Password button from the Schema Definition dialog
box.
2. Select a schema from the Schema Name list on the RIS Schema Manager
dialog box or type a schema name in the Schema Name box to display
information about a schema, if the schema you want is not already the selected
schema.
3. Type the original password into the Old DB2 Password box and the new
password into the New DB2 Password box. The Alternate LU62 Mode box
appears on the dialog box if this information is required. Enter the LU6.2 mode
value if the box displays. The No Echo/Echo buttons cause the passwords to not
display (No Echo) or display (Echo) when they are entered.
To alter the schema, click the Apply button. This action changes both the
MVS system password and the schema password. You must select the
Apply button after each session to alter the schema.
To dismiss the dialog box without altering the schema, click the Close
button.
9 - 36 rismgr
To obtain help with modifying the DB2 password, click the Help button.
rismgr 9 - 37
9.3
__________________________________________________________________________________________________________________________________________________
2. Creates tables
3. Drops tables
5. Includes tables, views, and indexes from the in-memory data dictionary
When you click the button for one of these actions, a dialog box associated with that
action appears.
Operating Sequence
1. Choose the Data Definition button from the RIS Schema Manager dialog box.
The Data Definitiondialog box appears.
2. If the schema you want is not already the selected schema, do one of the following:
From the RIS Schema Manager dialog box, select a schema from the
Schema Name list.
Click the button for the action you want to perform. See the section for the
action chosen for further instructions.
Click the Close button to dismiss the Data Definition dialog box.
Click the Help button to obtain further information about the Data
Definition dialog box.
rismgr 9 - 39
9.3.1
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Choose the Table Info button from the Data Definition dialog box.
2. To choose a table, type the table name in the Table Name box or select the table
from the Type/Name list on the Data Definition dialog box.
3. To dismiss the Table Information dialog box, click the Close button.
4. To obtain further information about the Table Information dialog box, click the
Help button.
9 - 40 rismgr
9.3.2
__________________________________________________________________________________________________________________________________________________
Creating Tables
The Create Table dialog box creates tables in the schema specified on the Data
Definition dialog box. If the name of an existing table is typed in the Table Name
box or selected from the Type/Name list on the Data Definition dialog box, the
definition of that table is loaded into the Create Table dialog box. This can be useful
when creating several similar tables.
The Create Table dialog box creates new tables. It cannot be used to
modify existing tables. The ability to load existing table definitions into
the dialog box exists only to provide a templateor starting pointfor
new tables.
Operating Sequence
1. Choose the Create Table button from the Data Definition dialog box.
2. The Create Table dialog box has two sets of control buttons. There is a set of
dialog box control buttons (across the bottom of the dialog box), and a set of mode
control buttons.
The mode control buttons are used to execute and reset the different modes of the
dialog box. The Create Table dialog box operates in three modes that are
represented by three buttons:
rismgr 9 - 41
Insert Column Click this button to add new columns to the table
definition. If a column is selected in the Column Name list, the new column
is inserted in front of the selected column. Otherwise the new column is
appended to the list. Click the mode Apply button to insert the column.
Drop Column Click this button to drop columns from the table definition.
Choose the column to drop by clicking the column in the Column Name list.
Click the Mode Apply button to drop the column.
Modify Column Click this button to modify column definitions. Choose the
column to modify by typing the column name in the Column Name Search
box, or by clicking the column in the Column Name list. Click the Mode
Apply button to modify the column.
Clicking the mode Cancel button clears the dialog box mode.
3. Type the table name in the Table Name box or select the table from the
Type/Name list on the Data Definition dialog box.
To dismiss the dialog box without creating the table, click the Close button.
To obtain further information about the Create Table dialog box, click the
Help button.
9 - 42 rismgr
9.3.3
__________________________________________________________________________________________________________________________________________________
Dropping Tables
The Drop Table dialog box drops tables from the schema specified on the Data
Definition dialog box. Dropping a table removes the table data, the table structure,
and any associated indexes. Once a table has been dropped, it no longer exists in the
database nor does it exist to RIS.
Operating Sequence
1. Click the Drop Table button on the Data Definition dialog box.
2. To choose the table to drop, type the table name in the Table Name box or select
the table from the Type/Name list on the Data Definition dialog box.
To dismiss the dialog box without dropping the table, click the Close button.
To obtain further information about the Drop Table dialog box, click the
Help button.
rismgr 9 - 43
9.3.4
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Click the Alter Table button on the Data Definition dialog box.
2. If the table you want to alter is not already the selected table, do one of the
following:
Select a table from the Type/Name list on the Data Definition dialog box.
3. Define the new column by entering the information in the controls of the Column
Definition to Append to Table group box. The following list explains these
controls.
dbms Column Name Type a column name for the underlying database.
By default, this name is the same as Column Name, but you can specify
another name.
Length Choose the data length. This box remains inactive unless the data
type you choose requires it.
Nulls Choose whether NULL values are allowed in the column. Toggle
between yes to allow NULL values or no.
To append the column to the table, click the Apply button. Repeat from
Step 2 to define another new column.
To clear the Alter table dialog box, click the Reset button.
To dismiss the Alter Table dialog box, click the Close button.
To obtain further information about the Alter Table dialog box, click the
Help button.
rismgr 9 - 45
9.3.5
__________________________________________________________________________________________________________________________________________________
Operating Sequence
From the dbms Table Names list, select the name you want to include.
To alter the schema, click the Apply button. You must click the Apply
button each time you include a table, view, or index.
To dismiss the dialog box without altering the schema, click the Close
button.
To obtain further information about the Include dialog box, click the Help
button.
rismgr 9 - 47
9.3.6
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Choose the Exclude button from the Data Definition dialog box.
From the Table Names list, select the name you want to exclude.
To alter the schema, click the Apply button. You must click the Apply
button after excluding each table, view, or index.
To dismiss the dialog box without altering the schema, click the Close
button.
To obtain further information about the Exclude dialog box, click the Help
button.
9 - 48 rismgr
9.4
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Click the Schema File button on the RIS Schema Manager dialog box.
2. Choose one of the buttons on the right side of the dialog box. If you click the
Locate Schema File button, all the controls become active, letting you enter the
appropriate values. The following list explains the buttons.
Locate Schema File Lets you rename your schema file or specify a
different protocol.
3. Enter the appropriate values on the dialog box when the Locate Schema File
button is clicked. The following list explains the controls on the Schema File
form.
Local, TCP Choose a network protocol for your schema file from the check
boxes. XNS and Decnet are not supported.
Schema File Name Type the name of a schema file. The full pathname for
the schema file must be specified unless the RIS HOME directory (the
default directory) is intended.
Username Type a system user name that has access to the schema file.
To obtain help with the Schema File dialog box, click the Help button.
9 - 50 rismgr
9.5
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Click the Locate Client button on the RIS Schema Manager dialog box.
2. Click the Show Client Location button to show the current location of the RIS
Client process.
OR
Click the Locate Client button to specify a new location for the RIS Client
process.
3. In the Nodename or Address box, type the nodename or address of the RIS
Client machine.
4. In the Username box, type the name of the operating system user for the RIS
Client machine.
5. In the Password box, type the user password, if any. The No Echo/Echo button
causes the password to not display (No Echo) or display (Echo) when it is entered.
6. Choose the Local or TCP network protocol. XNS and Decnet are not supported.
rismgr 9 - 51
To dismiss the Locate Client dialog box without relocating the client, click
the Close button.
To obtain help with the Locate Client dialog box, click the Help button.
9 - 52 rismgr
9.6
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1. Click the Set button on the RIS Schema Manager dialog box.
Setting any of these functions affects only the remainder of the RIS
Schema Manager session.
3. Click ANSI Mode check box to set ANSI on or off. The default is on.
If you set ANSI Mode to on, schema, table, column, view, and index names are
limited to 18 characters. Use this mode when creating names (for tables,
columns, and so forth) that should be ANSI compliant (18 characters or fewer.)
If you set ANSI Mode to off, names can be up to 31 characters, based upon the
underlying RDBMS. Remember, though, that these names may not be
portable.
4. If you set Blankstrip Mode to on, risunlod strips trailing blanks from character
data. Set this mode to off if you want to preserve trailing blanks.
rismgr 9 - 53
5. If you set Verify Mode to on, table and view definitions retrieved from the
database are validated against the definitions stored in the RIS dictionary tables.
Setting Verify Mode to off retrieves definitions from the database only, omitting
the validation. Omitting validation reduces the execution time when referencing a
table or view for the first time; however, if an application dynamically creates
tables and views, the definitions in the RIS dictionary tables and the DBMS may
become inconsistent if Verify Mode is off.
6. If you set Autocommit on, changes made to the Set form take effect
immediately. If Autocommit is off, the changes take effect only when you select
OK.
7. If you set Autorename on, schema, table, column, view, and index names that
are longer than the particular database limitation are automatically renamed to
comply with the shorter length. The default is on.
8. Click the Enabled Databases check boxes to choose RDBMSs that can be used.
Use this function when you want to create table or column names that conflict
with the keywords of other databases.
risplbck
__________________________________________________________________________________________________________________________________________________
10 - 2 risplbck
risplbck 10 - 3
10.
__________________________________________________________________________________________________________________________________________________
risplbck
This utility reads a <commandfile> that contains a list of the RIS commands executed
by an application and executes each of the RIS commands. The <commandfile> is
generated with the risrecrd utility.
RIS recording is controlled by the risrecrd utility. The risplbck utility reads a file
generated by a RIS application that is executed while RIS recording is on. This file
contains a list of all the RIS commands executed by the application. The risplbck utility
executes each of the RIS commands and compares SQLCODEs and times.
The risplbck utility can only read files generated with the risrecrd utility
of the same basic version. That is, if you generate a file with risrecrd
Version 4.3, then you can play back the file only with risplbck Version
4.x.x.x.
The risplbck utility compares the SQLCODEs of the recorded commands with the
SQLCODEs of the playback commands and reports if they are different. If they are
different, the action risplbck takes is specified in the action file. Each row of the action
file has three fields separated by colons(:): 1) the recorded results; 2) the playback
results; and 3) an action. Valid values for the two results fields are:
SUCCESS:END_OF_DATA:CONTINUE
The row indicates that if a command executed successfully at record time, but got an
end-of-data during playback, continue with the playback anyway.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Playback
icon:
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS
Interactive icon. Choose the Utilities... button from the RIS Interactive form; then
choose the RIS Playback... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the
Restart button before RIS Interactive is aware of any RIS parameter
changes, or creating or dropping of schemas.
risplbck 10 - 5
Usage
______
risplbck [-?] [-V] [-n] [-i] [-c] [-d]
[-t] [-f] [-v] [-a <actionfile>] [-o <outputfile>] [<commmandfile>]
Flags
_ ____
<none> If you do not specify any command-line arguments, or if you start the
utility by selecting its icon from the Program Manager, the utility runs
interactively and prompts for the necessary information.
-f Fetch blob/text files into same files as recorded session. The default is to
fetch blob/text files into temporary files.
-v Verbose mode.
Examples
_________
To play back the RIS commands previously recorded in the command file load.rap and
calculate command, delay, and total times, key in:
Files
_____
Status Returns
______________
0 Normal termination.
1 Abnormal termination.
risrecrd 11 - 1
risrecrd
__________________________________________________________________________________________________________________________________________________
11 - 2 risrecrd
risrecrd 11 - 3
11.
__________________________________________________________________________________________________________________________________________________
risrecrd
This utility controls RIS recording for the current user. RIS recording can be turned on,
turned off, and the status of recording can be queried with this utility. When RIS
recording is on, any RIS command executed by any of the current users applications
are recorded and placed in <outputfile>. These commands can then be re-executed by
the risplbck utility.
The risplbck utility can only read files generated with the risrecrd utility
of the same basic version. That is, if you generate a file with risrecrd
Version 4.3, then you can play back the file with risplbck Version 4.x.x.x.
The risrecrd utility affects only RIS applications executed by the current
user. If an application is run by a user other than the current user,
risrecrd has no effect.
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Record
icon:
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS
Interactive icon. Choose the Utilities... button from the RIS Interactive form; then
choose the RIS Record... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the
Restart button before RIS Interactive is aware of any RIS parameter
changes, or creating or dropping of schemas.
Usage
______
risrecrd 11 - 5
risrecrd [-?] [-V] [on <outputfile>] [-c] [-d] [-t] [-a] [off] [query]
Flags
_ ____
-c Record command times. Store how long each RIS command took
to execute.
-d Record delay times. Store the time between each RIS command.
-t Record total elapsed time. Store the total elapsed time from the
start of the application for each RIS command.
query Query the current status of RIS recording. The results are
displayed on stdout.
Examples
_________
The following risrecrd command turns record on and places the output in
c:\appl.rap.
risrecrd -c on risrecrd.out
Files
_____
Status Returns
______________
0 Normal termination.
1 Abnormal termination.
risunlod 12 - 1
risunlod
__________________________________________________________________________________________________________________________________________________
12 - 2 risunlod
risunlod 12 - 3
12.
__________________________________________________________________________________________________________________________________________________
risunlod
This utility retrieves information about one or more RIS schemas and stores it in one or
more external ASCII files. You can later reload the schemas from the ASCII files using
the rislod utility.
The risunlod utility is not designed for use as a backup utility. See the
rislod section for more specific information.
The environment variable RIS_LANGUAGE specifies the language that RIS uses for
parsing and error messages. The default is English. Consult the file c:\Program
Files\Common Files\Intergraph\ris05.nn\config\langs for other values.
The following figure represents the functional mechanisms of risunlod and shows the
input requirements and output generated.
You cannot unload ris_blob and ris_text data; however, you can unload the
table definition, which contains ris_blob or ris_text columns.
12 - 4 risunlod
Choose the RIS 05.nn icon from Program Manager; then choose the RIS Unloader
icon:
Choose the RIS 05.nn icon from the Program Manager; then choose the RIS
Interactive icon. Choose the Utilities... button from the RIS Interactive form; then
choose the RIS Unloader... button from the Utilities form.
If you use another utility within RIS Interactive, you must choose the
Restart button before RIS Interactive is aware of any RIS parameter
changes, or creating or dropping of schemas.
risunlod 12 - 5
Usage
______
risunlod [-?] [-V] [-p] [-m {w|a|e}]
[-o <filename>] [-s <schemas>] [-f <filename>]
Flags
_ ____
<none> If you do not specify any command-line arguments, or if you start the
utility by selecting its icon from the Program Manager, the utility runs
interactively and prompts for the necessary information.
-m {w|a|e} Specify the file mode for output files. The w overwrites an existing file,
the a appends to an existing file, and the e returns an error if an output
file with the specified name exists.
-o <filename> Specify the main output ASCII file into which RIS schema information is
to be unloaded. The default main filename is ris.dmp.
-f <filename> Specify the name of the specification file for <schemas>. This option
cannot be used with the -s option.
See the section Using risunlod With the Command Line Interface for more information.
Files
_____
Status Returns
______________
0 Normal termination.
1 Abnormal termination.
12 - 6 risunlod
The risunlod utility unloads user-requested RIS schema objects (items) into external
ASCII files from RIS schemas. The risunlod utility can unload:
Schema definitions
Table definitions
Table data
Index definitions
View definitions
The risunlod utility does not unload a view that has a NULL in the
RIS_VIEW_DEFS column in the RIS_VIEWS dictionary view. This
condition exists when a schema is created on a database that has an
existing view in the underlying database. Views created in RIS are not
NULL in the RIS_VIEW_DEFS column.
Privilege definitions
Table data in either fixed or variable format (See the section File Formats for
risunlod and rislod for more information.)
As discussed earlier, risunlod requires that all schema information be unloaded before
starting the actual unloading. The schema information is unloaded into the main
external file (the default is ris.dmp) and/or additional data files, if you want. Multiple
schema information can be unloaded in the same main file during a single risunlod
execution.
You can open the external main file and data files in overwrite or append mode.
An error is reported if files with the specified names already exist.
All the schema item statements (such as create schema, create table,
insert table, table field definition, create index, create view,
and grant) are unloaded into the main file. If the user wants, risunlod can
unload the table data into separate data files, one for each table.
The risunlod utility provides a risunlod extended where clause to unload partial
data from one table. The risunlod extended where clause has two parts:
risunlod 12 - 7
A join clause that lets the user provide powerful selection criteria to unload
partial data from one table while joining across different tables. The join
clause is optional.
A sql-where clause.
For example, the following risunlod extended where clause for table t1 unloads
partial data from table t1 while joining across table t2.
There are three ways to interact with risunlod: using the Interactive Interface, the
Command Line Interface, or the Embedded Programming Function Interface.
See the section Using risunlod with the Interactive Interface for more information
about the meanings of these prompts and the corresponding actions taken by
risunlod.
See the section Using risunlod With the Command Line Interface for more
information about the syntax for constructing a risunlod command and the
semantics of the command.
Invoking risunlod without any command line arguments displays interactive prompts.
Accepting Default Values. Most prompts have default values indicated in square
brackets([]). Press the ENTER key to select these default values.
Specifying Other Information. Some prompts ask you to enter information, such
as filenames. Key in the information requested and press ENTER.
12 - 8 risunlod
This prompt lets you set the blankstrip mode. By default risunlod strips trailing
blanks from character data.
Press ENTER to accept the default if you do not want to preserve trailing
blanks.
The file mode affects the main file and all the data files. By default risunlod
returns an error if the specified main file or data files already exist.
This prompt lets you specify the name of the main file for unloading. The default
name for the main file is ris.dmp.
If you selected e (for error out if exists) at the File mode of all output files? prompt,
and a main file already exists, risunlod prompts you to quit unloading or to key in
another filename.
If you select n, risunlod prompts you for a new name for the main file. Specify a
new filename at this prompt or key in y and risunlod exits.
Do not add the password at the end of the schema name. The
schema and user passwords in a schema definition are not unloaded
into the main file for security reasons. Instead, they are designated
by a period immediately after the schema and user names. If the
passwords are not added to the main file before loading, the user is
prompted for them when loading the schema.
Press ENTER without entering another schema name when you have
entered all the schema information you want to process. risunlod will
process the entered schemas.
Press ENTER without entering any schema names, and risunlod terminates.
This prompt lets you specify which table(s) to unload from the specified schema.
Select p and risunlod generates a list of tables and prompts you before
unloading each table:
Select y to unload the specified table or select n if you do not want to unload
the table.
Select n and risunlod does not unload any tables for the schema.
This prompt lets you decide whether to unload both the table definitions and the
data in the tables or only the table definitions.
Press ENTER to unload both table definitions and data and the following
prompt appears:
Definitions and data in the same file(s) data in a different file(d):[s] >
Press ENTER to store both the definitions and data in the main file, or select
d to store the definitions in the main file and the data in data files with one
data file per table.
The name of a data file is composed of the first three characters (or
fewer) of a schema name, followed by the first three characters (or
fewer) of a table name, followed by a number signifying the number
of data files generated so far in a risunlod session. The name of a
data file is terminated by .dmp. For example, the 100th data file
generated for storing the data in table, tab1, of schema, sch1, has the
name schtab100.dmp. All these files are placed in the current
directory. On the first line of a data file, risunlod specifies the table
and schema from which the data comes.
Press ENTER to unload the table data in fixed format and data that does not
fill the entire column is padded with spaces.
Select v and variable length data will be delimited by single quotation marks
(). This saves disk space, and lets you easily edit the data.
If you selected p or e at the prompt Which tables should be unloaded?, you are also
prompted for risunlods extended where clause for each table to unload partial
data.
risunlod 12 - 11
Partial data can be unloaded only from the current table, even when a
join clause is specified.
Press ENTER to unload all the indexes created in the current schema.
Select p and risunlod prompts for each table that has indexes:
Press ENTER to unload the indexes of that table or key in n if you do not
want to unload indexes.
The prompt for unloading views in a schema comes after the prompt(s) for
unloading the indexes.
Press ENTER to unload all the views created in the current schema.
Press ENTERto unload the view or key in n if you do not want to unload the
view.
The prompt for unloading privilege definitions comes after the prompt(s) for
unloading views.
Press ENTER to unload all the privileges created in the current schema.
Select p, and risunlod prompts for each table or view on which one or more
privileges are defined:
Press ENTER to unload the access privileges or key in n if you do not want to
unload the privileges.
Select e and risunlod prompts you to enter a table to unload all the
privileges defined:
The schemas to be unloaded and the places for storing them can be specified to risunlod
in a command line:
1. Level One
[-m{w|a|e}]
The -m option specifies the file mode of the output main and data files. The valid
characters suffixing this option are w, a or e representing overwrite, append,
or return error mode, respectively.
12 - 14 risunlod
If the main file or data files exist, and if the -me option is used,
risunlod exits.
[-o <filename>]
The -o option specifies the name to use for the main file. The absence of this
option causes the default main filename, ris.dmp, to be used.
[-s <schemas>]
The -s option is used to specify which schema and which information in the
schema is to be unloaded. More than one -s option can be used for multiple
schemas.
[-f <filename>]
2. Level Two
Storing data in the data file with table with var dfile data
variable format
The keywords index, view, and grant are used to specify the information they
represent. If the keyword all is used, then all the information in a schema is
unloaded, and the table data is stored in the main file.
The following example shows commands containing Levels One and Two
information.
The <level 3> in the examples represents information belonging to Level Three.
The middle two lines specify that only tables of schema sch2, and only tables and
privilege definitions of schema sch3, are unloaded.
3. Level Three
Level Three specifies the items of a particular type of information that should be
unloaded. The specification can be either the keyword all (all items) or the item
names.
4. Level Four
Level Four is valid for tables only. It specifies risunlods extended where clause
for a particular table.
12 - 16 risunlod
The where clause should be within double quotation marks (") for shell
interpretation. The character string within the where clause should be
in single quotation marks ().
For schema sch4, indexes created on the table t1 are also unloaded. Although t1 is
not specified for index, it was specified to be unloaded. Privilege definitions on
table t1 and view v1 are also unloaded.
When a command becomes too complicated, all the -s options can be moved into
a specification file. The specification of each schema is separated by a semicolon
and can occupy more than one line. The flag -s is invalid in the specification file.
Backus Naur form (BNF) is a method of describing the syntax of a language. It is used
here to show the capabilities of the RIS command line interface.
The following is the BNF representation of the syntax for constructing a command line.
<file_mode> ::= w | a | e
w represents overwrite file mode
a represents append file mode
e represents return error
risunlod 12 - 17
The following is the BNF representation of the format for a specification file.
Appendix A
__________________________________________________________________________________________________________________________________________________
Appendix A
__________________________________________________________________________________________________________________________________________________
RIS Version 5 supports UNION and UNION ALL operators with the select
statement. For example:
select c1, c2 from t1 union all select c21, c22 from t2;
UNION and UNION ALL are not supported in subqueries. See the RIS SQL Users
Guide for more information.
In RIS Version 4 a schema created by an RDBMS user contained only objects (tables,
views, and indexes) owned by that user. In RIS Version 5 a schema can contain objects
owned by multiple users. For example, schema S1, created by RDBMS user U1, can
contain objects owned by RDBMS users U2 and U3, as well as those owned by U1. This
capability:
Allows sharing of common objects among schemas. For example, table T1, created
by user U1, can be shared by schemas S1, S2, and S3, where S1 was created by
user U1, S2 by user U2, and S3 by user U3.
A-4 Appendix A: Changes to This Version of RIS
Since objects owned by different users can be included in the schema, the owner
information is maintained in the RIS dictionary. The dbms_owner value applies
to a table, view, or an index, and can be in upper or lowercase.
The access restrictions of the underlying RDBMS are encountered when using this
capability.
Most databases let two different users create tables/views/indexes with the same
name. However the names of tables/views/indexes within a schema are unique,
regardless of the dbms_owner. If both T1 owned by U1, and T1 owned by U2 need
to be included in a schema, one of the tables has to be aliased. See the section
Object Aliases for more information.
With RIS Version 5, any column or table name can be given an alias. For example,
table abc_123 with columns abc1, abc2, and abc3, can be included and referred to as
EMPLOYEES with columns FIRST_NAME, GENDER, and DATE_OF_BIRTH,
respectively. This capability:
Names in RIS can be longer than the underlying database supports. See the RIS
SQL Users Guide for more information.
Object names and keyword conflicts can be worked around. For example, if a
column name is a RIS keyword, such as t1(informix, oracle, db2), it can be
included as t1(col1, col2, col3).
Within RIS only the RIS names (aliases) are valid. The external/DBMS name is
not valid.
In RIS Version 5 two types of schemas are supported: the standard schema and the
secure schema. The standard schema is a single-user schema and the information
necessary for connecting to this schema is stored in the schema file (this is no different
from a RIS Version 4 schema). The secure schema has no username/password
combination stored for it. The RIS Version 4 (single user) schema is still supported and
still the default. This multi-user/secure schema capability:
Lets you use the same schema, but provide different RDBMS log-ins.
Individuals appear distinct to the RDBMS and are subject to RDBMS security
tracking.
The declare schema statement lets you specify a schema name and password, and
optionally, the user and password of the user who owns the schema, and the
operating system user and password in the RIS in-memory data dictionary cache.
This statement must be used to access secure schemas. It can also be used to
access standard schemas. See the RIS SQL Users Guide for more information.
This capability can be used by any site. It is most useful to those interested in
high levels of security (usually DB2, ORACLE, and so on).
The schema administrator (user who creates the schema) controls authority to
connect to a schema and to create tables on a schema, using:
In RIS Version 5 when a schema s1 is created and creates the dictionary as in RIS
Version 4, schemas s2, s3, s4, and so on can be created using the dictionary created by
schema s1. This capability:
Allows multiple schemas in databases that cannot have tables of the same name
(non-ANSI INFORMIX).
The system administrator must grant and revoke an RDBMS user the authority
to create a schema on a dictionary, using:
Creators of dictionaries cannot drop all their schemas while there are other
schemas in the dictionary.
An application based on RIS Version 4 must create a dictionary in order to use it.
Additional schemas can then be added to the dictionary and used by applications
based on RIS Version 5. Schemas s2, s3, and so on, cannot be accessed from RIS
Version 4.
Dictionary objects in RIS Version 5 are all renamed (ris5*). This capability:
In RIS Version 4 the internal RIS dictionary tables were documented with the note that
they are not intended for application use, and information about them was maintained
in the dictionary. In RIS Version 5, the internal tables are not documented and
information about them is not available in the dictionary. Only dictionary views can be
accessed from an application.
In RIS Version 4 the dictionary views showed information about only the user (or
application) objects and the base tables contained both application objects and RIS
dictionary objects. In RIS Version 5, since the base tables are not accessible from the
applications, the views show both user objects and RIS objects.
Considerations:
If only user objects need to be selected, the condition ris_object=N should be used
in the where clause.
A.9 RIS_BLOB/RIS_TEXT
RIS Version 5 allows long binary or long text data that lets you:
Use it for document or picture storage by INFORMIX OnLine and ORACLE. RIS
has no RIS_BLOB/RIS_TEXT support for INFORMIX Standard Engine, SYBASE,
Microsoft SQL Server, or DB2.
Access character strings with a length greater than 249 characters for other
RDBMSs not supporting RIS_BLOB.
To use RIS_BLOB/RIS_TEXT data, the client and data server versions must be at
least 05.01.01.xx.
The RIS_BLOB data type is for binary data; for example, GIF files, executables,
and so forth. RIS makes no attempt to convert or interpret the data.
The RIS_TEXT data type is for text data; for example, ASCII files. RIS does
convert the text data between different hardware platforms as it would for char
data.
The text data can be inserted into a RIS_BLOB column, but no blob data should
be inserted into a RIS_TEXT column.
The file_used field is required for inserting and retrieving. RIS uses the filename
or the memory array as the targeted user variable.
The text data and character data are converted for different hardware platforms.
The maximum size limit cannot be zero when retrieving data from the database.
The maximum size limit is zero when retrieving data from memory.
Tables with RIS_BLOB/RIS_TEXT are created through RIS and data is inserted
through RIS.
Currently, RIS uses the first 8 bytes (ORACLE only) of the RIS_BLOB/RIS_TEXT
column in databases to store the length of the data. Existing tables with data, when
included in a RIS schema, will result in incomplete data when retrieved from the
database. To manipulate RIS_BLOB/RIS_TEXT data, any tables with
RIS_BLOB/RIS_TEXT fields need to be created through RIS and the data inserted only
through RIS.
When the maximum size limit for a RIS_BLOB/RIS_TEXT column is zero, data cannot
be retrieved from the database to a file. This situation does not apply when the data is
retrieved into a memory array.
If a positive, non-zero value is used, RIS will use this value as the maximum size limit
for the RIS_BLOB/RIS_TEXT object. If the value is zero, or no value is specified (using
default of zero), then RIS does not impose a limit and the maximum size supported by
the underlying RDBMS can be used.
A table is excluded from the RIS schema and later included back into the schema
c:\risdtype
Enter schema (<CR> to exit) :sch1
Enter a table or view name (or ? for a list of names):
>blob_table
0 Unsupported
1 Character
2 RIS_BLOB
3 RIS_TEXT
Choose a datatype from those listed (enter the number) >>2
Current maximum ris_blob length is:0
Current maximum ris_blob length is:10000
Current status for nullable is YES, nulls are allowed
Are null values allowed? <y(es), n(o)> >>y
Column definitions modified for object sch1.blob_table:
Pos Column Name type type-string len prec scale null
1 c1 15 ris_blob 10000 null null Yes
In the above example, RC01 is the dictionary owner as shown in the schema file,
blob_table is the name of the table with a blob column, set to values other than 10000.
RIS limits the data size inserted into a RIS_BLOB/RIS_TEXT column if a size is
specified when the table is created.
For example:
would impose a limit of 100,000 bytes. If the table is created without specifying a size,
then the underlying RDBMSs maximum limit for RIS_BLOB/RIS_TEXT data will be
used.
For example:
A.10 Interoperability
RIS Version 5 lets multiple versions of RIS products be available on most systems. The
following figure details interoperability of RIS Version 4 and RIS Version 5.
This capability:
Lets you continue to use RIS Version 4 applications with minimal impact. Version
4 applications should continue to run.
The Sybase SQL Data Server requires the Version 5.02 Client.
Only RIS Version 5 applications can query RIS Version 5 dictionary objects. Only
RIS Version 4 applications can query RIS Version 4 dictionary objects.
A - 12 Appendix A: Changes to This Version of RIS
The RIS utilities are also applications and the previous restrictions apply.
The risdtype utility of RIS Version 4 cannot be used with the RIS Client Version 5
or the RIS Data Server Version 5.
Files generated by the RIS Version 4 risrecrd utility cannot be processed by the
RIS Version 5 risplbck utility. If an application is built with RIS Version 4, the
resulting record file can be processed only by the RIS Version 4 risplbck utility.
A utility to convert a schema (dictionary and schema file) from RIS Version 4 to RIS
Version 5 is delivered with the RIS Client.
While RIS Version 4 is not available for Solaris, the upgrade utility can be
used to upgrade a Version 4 schema file on another platform (for example,
CLIX).
This conversion should be applied to every existing schema when RIS Version 5
Data Servers are installed.
A.12 Utilities
The RIS Version 4 ad hoc utility ris has been renamed risbatch. There is now an ad hoc
query utility with a graphic user interface (GUI), called risgui.
The unloader unloads (or saves) RIS names (aliases) only, not the underlying
object names.
The unloader unloads (or saves) schema ownership only, not underlying RDBMS
ownership.
Appendix A: Changes to This Version of RIS A - 13
A.13 Parameters
A new parameter, CLIENT_VERSION, has been added with the default value set to
0.0, meaning that the application connects to a compatible client. When future versions
of RIS become available, Version 5 and higher applications will be able to use this
parameter to specify the client version.
Using this parameter causes Version 4 applications to fail; hence, for now,
leave it commented out. When the CLIENT_VERSION parameter is set,
Version 4 applications can no longer use that parameter file.
A.14 Internationalization
RIS for 32-bit applications (Version 5.3.1 and later) support 16-bit or multi-byte
languages. Most 16-bit languages are Asian. In the RIS documentation, the maximum
size allowed for table names, view names, index names, schema names, column widths,
and character data is specified as x characters, where x is an integer. For those using
multi-byte languages, the maximum number of characters should be interpreted as the
maximum size in bytes. RISMGR and RISGUI implement multi-byte character
support.
RIS schema and user names can be internationalized, but not passwords.
RIS is internationalized on NT only. The RIS application, RIS Client, and RIS
Data Server must be on NT to take advantage of the RIS internationalization.
The period (.) used between username and passwords must be 8-bit English.
Schemas, tables, views, columns, index names can be 8-bit or 16-bit characters.
RIS data dictionary tables and views are created using 8-bit English characters.
A - 14 Appendix A: Changes to This Version of RIS
The following components of a create schema statement are 8-bit and 16-bit characters:
Character columns are analyzed to make sure that they are wide enough to hold the
data. For example, a 10 character name in a 16-bit language requires a char(20)
column.
The maximum number of 8-bit characters in a column is 240. The maximum number of
16-bit characters in a column is 120.
A - 16 Appendix A: Changes to This Version of RIS
Appendix B: File Formats for risunlod and rislod B - 1
Appendix B
__________________________________________________________________________________________________________________________________________________
Appendix B
__________________________________________________________________________________________________________________________________________________
The main file contains the schema, table, index, view, and privilege definitions.
Table data, however, can be stored in either the main file or a data file.
The representation of the information in a schema starts with one or two statements
specifying the schema and ends with an end of schema indicator. In between, tables,
views, and privilege definitions are represented. As far as rislod is concerned, there is
no order of appearances defined for any two pieces of information in a schema.
However, because risunlod unloads tables before views, and views before privilege
definitions, information in a schema appears in that order ( if the main file is prepared
by risunlod ). The information in a schema is represented in the main file by:
SQL Statements
Field Definitions
Lines of Data
Dend Indicators
Item Meaning
field definition Specifies where in the main file or a data file the values of
each column of a table are located
end of table indicator Indicates where information from a table ends in the main
file
end of schema indicator Indicates where information from a schema ends in the
main file
Commented lines have two hyphens (--) as the first two characters in the
line. The loader ignores commented lines.
The default schema and create [secure] schema statements can appear by
themselves or together. Their presence marks the beginning of a schema, represented
in the main file. Because multiple schemas can exist in the main file, an end of schema
indicator is used to mark the end of a schema:
The items from create table through the end of table indicator in the preceding list
are used to represent tables. The order in the representation is:
field definition
Not all of the statements are needed to represent a table. The presence of these
statements is defined by three rules:
1. The create table statement and an end of table indicator are required.
2. The insert into statement and a field definition are required only when data
or a data file specification is present.
3. The insert into statement and a field definition are permitted even if data or
a data file specification is not present.
Rules 1 and 2 cover the situation where only the definition of a table is unloaded. Since
both the insert into statement and field definition are needed for loading
table data, Rule 2 covers situations where one or more rows of data are unloaded into
either the main file or a data file. Rule 3 covers the situation where a table is empty,
but risunlod is instructed to unload data from the table.
Appendix B: File Formats for risunlod and rislod B - 5
The number of statements representing a table may vary. For rislod to correctly
identify where the information of a table ends in the main file, an end of table indicator
is necessary:
The representation of index, view, and privilege definitions is much simpler than that of
a table. The definitions are represented by the create index, create view, and
grant statements, respectively.
If the schema or user clause has a password associated with it, and you do not want to
leave the password in the main file, the password should be designated by a period
right after the name. In loading a default schema or create [secure] schema
statement, when rislod finds a period alone after the schema or username, it prompts
for the missing password. The password keyed in is not echoed on the screen. Note
that rislod does not store either the schema or the user password in the main file.
The following are some sample default schema and create [secure] schema
statements that are accepted by rislod.
The rislod utility uses an insert into statement as a template for loading each row
of data into a table. This statement and a field definition are required only when data
or a data file specification for the table are present in the main file. The following is an
example of an insert into statement defined on table tab1, with seven columns,
accepted by rislod:
You should specify only the columns that need to be loaded after the table
name. The number of question marks in the values clause must match
the number of columns being specified. The columns decimal_col2 and
decimal_col3 of the table tab1 have been left out because only NULL
values are loaded into these columns.
The rislod utility can load fixed or variable table data. rislod determines whether table
data is fixed or variable by examining the line immediately following the insert
into statement. This line is referred to as a field definition. If rislod detects
***variable*** as the first 14 characters in the field definition, it assumes that the
table data following the field definition is in variable format. Otherwise, it assumes
that the table data is in fixed format.
For rislod to know where to get table data, table locations must be specified. rislod
assumes that:
Because of these assumptions, only the positions occupied by each column on a line
need to be specified in the field definition. Thus, a field definition is typically made up
of one or more components, one for each column, consisting of a column name and the
starting and ending positions of the column data on a line. In rislod, the combination of
a column name and its starting and ending positions is referred to as a field.
The following is an example of a field definition for table tab1 accepted by rislod:
The starting and ending positions of a field are constrained by the following
relation:
The starting and ending positions of a column should be separated by one or more
spaces.
risunlod uses a single blank to separate the starting and ending positions.
The absence of the keyword var after a character column name signifies that the
column values have the same length.
The values of a variable character column are represented differently from those
of a fixed character column. A variable character column value is always enclosed
by a delimitation, while the value of a fixed character column is assumed to
occupy the entire field.
The field definition for a table must include all the columns listed in the insert into
statement of that table. However, columns that are not listed in the insert into
statement may also appear in the field definition. The column decimal_col2 in this
example was not specified in the insert into statement for table tab1.
B-8 Appendix B: File Formats for risunlod and rislod
The conventions used by risunlod for determining the field width of a column are:
character The column length plus two extra spaces for delimitation
integer 11
small integer 6
double 23
real 14
risunlod can unload table data in variable format, and rislod can load the same variable
formatted data. The variable table data is identified by the string ***variable*** in
the field definition line. This string is sufficient to identify variable table data following
it. Starting and ending position does not make sense in this format. The column data
is separated (delimited) by a blank space, while the character data of a column is
delimited by default single quotation marks ().
The following is an example of a field definition line and several rows of variable data.
Notice the third row. The delimiter can be escaped from within the string by an extra
delimiter preceding it.
***variable***
1 nyz
23 nyzabc
246 nyzabc
***RIS*** End of Table ***RIS***
In the main file or a data file, each row of table data occupies one line. The following is
an example of a row of data for the table tab1:
This example is prepared according to the field definition for the table tabl1.
should be filled with blanks (not spaces). In this example, the value for smallint_col is
NULL.
Although in the previous example all the values begin at the first positions in their
fields, a column value can actually start anywhere within its field.
The following describes how rislod handles the values of different datatypes stored in a
file.
1. In the field of a variable character column, the first and last nonspace characters
must be delimiters. A delimiter is permitted among the character values. If there
are more characters within a pair of delimiters than the size of the column (n),
only the first n characters are loaded.
2. If the field width (m) is greater than the size of a fixed character column (n), only
the first n characters in the field are loaded. Otherwise, all m characters are
loaded with (m - n) trailing blanks.
3. A decimal value must have precision and scale no greater than that specified for
the column.
4. For an integer or small integer value to be loaded correctly, it must fall within the
ranges of -2,147,483,648 to 2,147,483,647 and -32,768 to 32,767, respectively.
A data file specification specifies the location of a data file. The following are some
examples of data file specifications:
risunlod specifies the complete pathname of a data file in a data file specification. Note
that a data file specification must start at the first column of a line.
B - 10 Appendix B: File Formats for risunlod and rislod
A data file may begin with an informative header in the form of:
This header is optional. The header is followed by zero or more lines of data. The
format for representing a line of data in a data file is the same as the format defined for
the main file. The header must start at the first column of the first line.
rislod is tolerant of the number of spaces (a blank or tab character) used to separate
two words or a word from a punctuation mark.
In the BNF representation, when a blank is used to separate two adjacent entities on a
line, the blank can be replaced by any number of spaces. This does not apply to a single
blank used in the end of schema and end of table indicators. When no blank is used to
separate two adjacent entities on a line of the BNF representation, then zero or more
spaces can be used to separate the entities.
End indicators, data file specifications, and data file headers must start at the first
column of a line. Other types of statements and rows of data can start at any column
on a line. A line must be terminated with a single new line character.
A line containing a row of table data is terminated by a new line character. If the data
line contains trailing blanks, these trailing blanks need not be specified. For instance,
if a row of data contains only NULL values (represented by blanks in the entire field),
the line where the row of data is stored may contain zero or more blanks terminated by
a new line character. A space is not necessary to separate any two consecutive column
values on a line.
Appendix B: File Formats for risunlod and rislod B - 11
For example:
--This is a comment.
--This is another comment.
These are also used to represent errors encountered during loading in the bad file. This
bad file is reprocessable by rislod.
For example:
The xxxx represents the error value, and ssss represents the corresponding error
message string.
The format of the main file is defined by <main_file_format>, and the format of a data
file is defined by <data_file_format> in the following BNF representation.
<main_file_format> ::=
<info_in_schema>[...]
<info_in_schema> ::=
<schema_def>[<table_index_view_grant>][...]<end_of_schema>
<table_index_view_grant> ::=
<table_def_data>|<index_def>|<view_def>|<grant_stmt>|<comments>
<schema_def> ::=
<default_schema>|<create_schema>
<default_schema> ::=
default schema <schema_passwd>
B - 12 Appendix B: File Formats for risunlod and rislod
<schema_passwd> ::=
<schema>|<schema>[.[<passwd>]]
<create_schema> ::=
create [secure] schema <schema_passwd> [on database (...)] user <user_passwd>
<user_passwd> ::=
<username>|<username>[.[<passwd>]]
<end_of_schema>::=
***RIS*** End of Schema ***RIS***
<table_def_data> ::=
<table_def><end_of_table>|
<table_def><insert_stmt><field_def>
[<table_data>|<file_name_spec>]<end_of_table>
<end_of_table> ::=
***RIS*** End of Table ***RIS***
<table_def> ::=
create table <table> ({<column> <type_def> [not null]}[,...])
<insert_stmt> ::=
insert into <table> (<column>[,...]) values (?[,...])
<field_def> ::=
{
{<column> [var ]<starting_posi> <ending_posi>}[ ...]
***variable***
}
<table_data> ::=
{<delimiter><var_len_char_val><delimiter>|<fix_len_char_val>|
<dec_value>|<int_val>|<small_int_val>|<double_val>|<real_val>|
<timestamp_val>} [...]
<file_name_spec> ::=
***RIS*** <file> ***RIS***
Appendix B: File Formats for risunlod and rislod B - 13
<index_def> ::=
create [unique] index <index> on <table> (<column> [,...])
<view_def> ::=
create view <view> [(<column>[,...])] as <select_statement>
<grant_def> ::=
grant <privileges> [<schema>.]<table_or_view> to <schema>[,...]
[with grant option]
<data_file_format> ::=
[<header>][<table_data>][...]
<header> ::=
***RIS*** Data in Table <table> of Schema <schema> ****RIS***
Glossary
__________________________________________________________________________________________________________________________________________________
GL - 2 Glossary
Glossary GL - 3
Glossary
__________________________________________________________________________________________________________________________________________________
absolute pathname Sequence of directories, beginning with the root directory (/)
that locates a file. See also pathname and relative pathname.
arrow keys Keys used to move from one field of a menu or form to
another.
attributes The features of an object, such as color, line width, font, and
font size.
GL - 4 Glossary
check box A small box that lets you select or unselect an option. When
the check box is selected, an X appears in the box.
command Software that interacts with the user, obtaining user input
and then acting in a specified way based on that input. Each
icon on the menu accesses a command, although there could
also be additional commands accessed only by key-in.
Glossary GL - 5
data dictionary Either a filed object space that contains information about the
classes that make up an application or a set of ASCII files
created by a utility called a data dictionary processor (ddp).
data point Point entered with the mouse or with a precision key-in,
which specifies a position in a drawing file.
dialog box A box that requests information about a particular task you
are performing.
document A file or many files that are handled as one entity to the
redlining software.
filed object space Set of objects filed away for subsequent retrieval. Filed object
spaces let objects be stored and retrieved, with their
connections intact.
grant option Relation privilege which gives a schema the ability to grant
relation privileges to other schemas.
Help window Form in which the Help topics are displayed by the Help
process.
indexing Extraction and sorting of all the indexable words in any new
or modified documents and updating the index files with the
new information.
integer Value in the set of all positive and negative whole numbers
and zero. Also, a data type which stores a range of integer
values. Storage requirement and range of values are
dependent on the computer and compiler.
local area network Computer networking scheme in which nodes that are
geographically local are connected to a network through
multiplexers, and networks of geographically remote nodes
are connected through routers.
log file File containing the direction of the translation, the command
line used, a count of elements processed, and any errors
encountered during the translation process.
on-line Help Set of on-line, context sensitive files, that provide information
to the user about the capabilities of an application.
raster data Generic term that refers to a group of pixels. Each of these
pixels has an associated color and together they form a
viewable image.
raster data file File containing raster data (pixels). Raster data files can be
generated by optical scanner, video frame grabber, digital
camera, interactive paint package, and so forth. Intergraph
raster data files are characterized by specific data formats
which are identified in the file headers.
scroll bar A gadget that lets you move vertically or horizontally through
displayed text symbols. Also, a numeric gadget you can use to
send numerical values to another gadget.
Index
__________________________________________________________________________________________________________________________________________________
IN - 2 Index
Index IN - 3
Index
__________________________________________________________________________________________________________________________________________________
T
table information dialog box 9-39
tables
creating logical groupings A-4
definitions, format B-6
with same name A-4
with same name in one schema A-4
text data A-8
transferring schema information 8-3
U
UNION A-3
UNION ALL A-3
unload 12-3
updating large data A-8
usernames, stored for schema A-5
using on-line Help 1-6
utilities
risalpha A-12
risbatch 3-3
risclnsr 4-3
risdcode 5-3
risdtype 6-3
risgui A-12, 7-3
rislod 8-8
utilities overview 2-3
V
values, dbms_owner A-4
IN - 8 Index