Beruflich Dokumente
Kultur Dokumente
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.
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of
The Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or subparagraphs (c) (1) and
(2) of Commercial Computer Software Restricted Rights at 48 CFR 52.227-19, as applicable.
Unpublished rights reserved under the copyright laws of the United States.
Intergraph Corporation
Huntsville, Alabama 35894-0001
Table of Contents
__________________________________________________________________________________________________________________________________________________
Table of Contents
__________________________________________________________________________________________________________________________________________________
1.
1-3
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1-3
1-3
1-3
1-3
1-4
1-4
1-6
1.7.1
1-6
2-3
2.1
2-4
3.
risbatch .................................................................................................................
3-3
4.
risclnsr ..................................................................................................................
4-3
5.
risdcode .................................................................................................................
5-3
6.
risdtype .................................................................................................................
6-3
7.
risgui .....................................................................................................................
7-3
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7-4
7-4
7-6
7-7
7-7
7-8
7-9
rislod ......................................................................................................................
8-3
2.
8.
8.1
8.2
8.3
8.4
8.5
8.6
8-8
8-9
8 - 10
8 - 10
8 - 17
8 - 18
9.
rismgr ....................................................................................................................
9-3
9.1
9.2
9-5
9-7
9-9
9 - 11
9.2.2.1
9.2.2.2
9.2.2.3
9.2.2.4
9.2.2.5
9 - 15
9 - 17
9 - 19
9 - 22
9 - 24
9 - 26
9 - 28
9 - 30
9 - 32
9 - 33
9 - 35
9 - 37
9.3.1
9.3.2
9.3.3
9.3.4
9.3.5
9.3.6
9 - 39
9 - 40
9 - 42
9 - 43
9 - 45
9 - 47
9 - 48
9 - 50
9 - 52
10.
risplbck ................................................................................................................
10 - 3
11.
risrecrd ................................................................................................................
11 - 3
12.
risunlod ...............................................................................................................
12 - 3
9.2.3
9.2.4
9.2.5
9.2.6
9.2.7
9.2.8
9.3
9.4
9.5
9.6
12.1
12.2
12.3
Appendix A:
A.1
A.2
A.3
A.4
12 - 7
12 - 13
12 - 16
A-3
A-3
A-3
A-3
A-4
A.5
A.6
A.7
A.8
A.9
A.10
A.11
A.12
A.13
A.14
Appendix B:
A-5
A-6
A-6
A-7
A-8
A - 11
A - 12
A - 12
A - 13
A - 13
B-3
B-5
B-6
B-6
B-6
B-8
B-9
B - 10
B - 10
B - 10
B - 11
Glossary .......................................................................................................................
GL - 3
Index ............................................................................................................................
IN - 3
B.1
B.2
B.3
B.4
B.5
B.6
B.7
B.8
B.9
B.10
__________________________________________________________________________________________________________________________________________________
1-2
1.
__________________________________________________________________________________________________________________________________________________
1.2 Audience
This document was written for application users, application designers, and computer
software specialists.
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
product.def
MANIFEST.TXT
OR
commit
In actual usage, keywords can be in either upper or lowercase.
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:
ERROR: Error opening the file <filename>
Phrases in square brackets, [ ], are optional phrases.
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 notes important information.
This symbol cautions about operations that can cause limited damage.
This symbol warns about operations that can cause severe damage.
1-6
1-8
Use
To
Contents
Search
Back
History
Find
<<
>>
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:
1.
2.
3.
4.
5.
6.
7.
8.
2-4
9.
Getting Started
10.
11.
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.
All SQL statements must be terminated with a semicolon (;).
The RIS_PARAMETERS environment variable is used to specify the location of the
parms file.
Output is directed to stdout when the -o option is not used.
To start the risbatch utility, do one of the following:
Type risbatch in a Command Prompt window.
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
_ ____
<none>
-?
-V
-i <infile>
Specify the input file containing the RIS SQL statements. The
locate client command prompts for the client version.
-o <outfile>
Examples
_________
In this example, risbatch is invoked with the input file input.sql and the output file
output.sql:
risbatch -i input.sql -o output.sql
Files
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\risbatch
c:\Program Files\Common Files\Intergraph\ris05.nn\parms
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
Status Returns
______________
0
other
Normal termination.
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>
-?
-V
Files
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\risclnsr
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
Status
Returns
______________
0
1
Normal termination.
Abnormal termination.
risdcode 5 - 1
risdcode
__________________________________________________________________________________________________________________________________________________
5-2
risdcode
risdcode 5 - 3
5.
__________________________________________________________________________________________________________________________________________________
risdcode
This utility prints error messages for RIS error codes.
To start the risdcode utility, do one of the following:
Type risdcode in a Command Prompt window.
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>
-?
-V
<error code>
Examples
_________
To get the error message corresponding to an error code of 100, key in one of the following:
risdcode 100 (Using decimal.)
risdcode Ox64 (Using hexadecimal.)
risdcode 0144 (Using octal.)
risdcode
You are prompted to key in the value to be decoded. In this case, key in 100.
risdcode 5 - 5
Files
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\risdcode
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
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.
To start the risdtype utility, do one of the following:
Type risdtype in a Command Prompt window.
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
Pos Column Name
- -
1
c1
Do you wish to modify this column? <y(es), n(o), d(one with table)>>yes
0
1
2
6
UNSUPPORTED
CHARACTER
RIS_BLOB
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
Pos
YES
Column Name
- - - 1
type
type-string
c1
Usage
______
risdtype [-?] [-V]
Flags
_ ____
<none>
-?
-V
Files
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\risdtype
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
Status
Returns
______________
0
1
Normal termination.
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:
Type risgui in a Command Prompt window.
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:
1.
2.
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.
Select the Search... button to perform a search in the history file.
1.
2.
7-6
risgui
3.
7.3 Options...
The Options... button modifies the behavior of query results.
1.
2.
To specify the behavior for query results that do not fit in the Results field, select
one of the following:
Fetch by screenful (Append) fetch one screenful of results. When you
select the Continue button, append the next screenful to the results.
Fetch by screenful (Overwrite) fetch one screenful of results. When you
select the Continue button, discard the results and get the next screenful.
Fetch all rows fetch all results without pausing.
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.
1.
2.
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.
1.
2.
3.
risgui 7 - 9
7.7 Show...
The Show... button gives you additional information about RIS on your system.
1.
2.
7 - 10
risgui
rislod 8 - 1
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.
Restores only user-requested schema information into 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
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.
To start the rislod utility, do one of the following:
Type rislod in a Command Prompt window.
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>
-?
-V
-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.
-p
-e <db_list>
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>
-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.
-s <schemas>
-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
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\rislod
c:\Program Files\Common Files\Intergraph\ris05.nn\parms
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
Status
Returns
______________
0
1
Normal termination.
Abnormal termination.
rislod loads user-requested RIS schema objects (items) from external ASCII files into
RIS schemas. rislod can:
Load schema definitions
Load table definitions
Load table data
rislod 8 - 7
8-8
rislod
Not imposing the order of information stored in the main external file
For an index, view, or privilege definition to be loaded successfully, all its
references must exist. rislod does not impose a strict order on the information
stored in the main file because it often postpones the loading of an index, view, or
privilege until its references are loaded.
There are three ways to interact with rislod: using the Interactive Interface, the
Command Line Interface, or the Embedded Programming Function Interface.
1.
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.
3.
Contains . . .
Header
rislod 8 - 9
Schema Information
Grants Summary
Miscellaneous
8 - 10
rislod
Additionally, the status of each schema item being loaded is echoed to the screen in the
interactive and command line interfaces.
The bad file can be opened in overwrite or append mode.
rislod 8 - 11
2.
3.
4.
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.
Do one of the following:
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
6.
7.
rislod 8 - 13
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:
Quit risload? (y/n):[n] >
Do one of the following:
Press ENTER to accept the default. You are again prompted to enter a
name for the bad file; key in a new filename.
Select y to quit rislod.
8.
9.
10.
8 - 14
rislod
rislod 8 - 15
Press ENTER to accept the default and load all the tables in the schema.
Select p if you want to be prompted for each table.
Select n if you do not want to load any tables.
If you select a or p at the prompt Which tables should be loaded? the following
prompt appears next:
Both definitions and data(b) definitions only(o):[b] >
This prompt lets you decide whether to load both the definitions and data of the
tables in the schema or load only the definitions.
Do one of the following:
Press ENTER to accept the default and load both table definitions and data.
Select o to load table definitions only.
rislod loads either fixed or variable formatted table data.
If only the definitions exist for some or all of the tables in a
schema, choosing to load both definitions and data does not
cause any problem to rislod. These tables are created without
data in them. Similarly, if both the definitions and data exist
for some or all of the tables in a schema, choosing the second
selection does not cause problems. These table data are
discarded and the string only definitions is placed in the log file.
8 - 16
rislod
13.
rislod 8 - 17
14.
When all the necessary information has been specified, rislod processes the schema(s)
selected.
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
-i
-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.
-l
-b
Specifies
-n
-e
-m
Set the file mode (w, a, or e) for the output files (such as log and bad files).
-c
Commit interval.
rislod -s sch1.create_sch_passwd1.user_passwd1 all
-s sch2 .create_sch_passwd2 .user_passwd2 new table with data all
-s sch3 clear table with data t1 t2 grant all
-s sch4 rename sch5 .sch5pass table t1 index t2 view v1
grant t2 v2 sch.t3 sch.v3
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.
rislod 8 - 19
| a | e
overwrite file mode
append file mode
return error
table
[{new | clear}] table with data
<table_tobe_load>
]
[view <view_tobe_load>]
[index <index_tobe_load>]
[grant <grant_tobe_load>]
}
<table_tobe_load> ::= all | {<table>[ ...]}
<view_tobe_load>
[<schema>.]<table>|[<schema>.]<view>
[ ...]
8 - 20
rislod
The following is the BNF representation of the format for a specification file.
<spec_file_format> ::= {<schema> [.<create_sch_passwd>] [.<user_passwd>]
<info_tobe_load>}[;<new_line>...]
rismgr 9 - 1
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.
To start the rismgr utility, do one of the following:
Type rismgr in a Command Prompt window.
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
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\rismgr
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\forms\v5forms\*
c:\Program Files\Common Files\Intergraph\ris05.nn\parms
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
Status
Returns
______________
0
1
Normal termination.
Abnormal termination.
rismgr 9 - 5
9.1
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
9-6
rismgr
2.
3.
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.
Button Name
Function
Schema Definition
Data Definition
Schema File
Locate Client
Set
rismgr 9 - 7
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.
Function
Schema Information
Create Schema
Drop Schema
9-8
rismgr
Dictionary Access
rismgr 9 - 9
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:
In the Schema Name box, type a schema name.
Select a schema from the Schema Name list on the RIS Schema Manager
dialog box.
The schema information is displayed.
The following information is displayed:
Schema Name Displays the schema name.
9 - 10
rismgr
rismgr 9 - 11
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.
9 - 12
rismgr
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 Name) Password Enter a password for the schema. The No
Echo/Echo button causes the password to not display (No Echo) or display
(Echo) when it is entered.
Schema Type Click this button to toggle between Standard and Secure
schemas.
Network Protocol Select the type of network protocol to use to
communicate with the RIS data server. Only the top (#1) protocol is used in
the create schema statement. When you select a protocol, it moves to the
bottom (#4). ISO, XNS and DECNET are not currently supported.
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.
Nodename or Address Specify a nodename, an Internet address, or an
address appropriate for the protocol of the machine where the RIS data
server is located. Enter a value or click the Get Client Address button.
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.
Database Username Type the database username.
(Database Username) Password Type a password for the database
username. The No Echo/Echo button causes the password to not display (No
Echo) or display (Echo) when it is entered.
Include Database Users Tables/Views Click this button to toggle between
Yes to include the database users tables and views, or No not to include the
database users tables and views.
OS Type From the list, select the operating system type on which the RIS
data server is running.
Use Existing Dictionary Click this button to toggle between No (the
default) and Yes. You must already have permission from the dictionary
owner to use an existing dictionary.
rismgr 9 - 13
9 - 14
rismgr
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.
For more information, see these sections:
Creating Schemas (INFORMIX)
Creating Schemas (ORACLE)
Creating Schemas (DB2)
Creating Schemas (SYBASE)
Creating Schemas (Microsoft SQL Server)
rismgr 9 - 15
9.2.2.1
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
9 - 16
rismgr
For the INFORMIX OnLine Engine product, the <dbname> must include only
the INFORMIX server name with the @ separator: <dbname@servername>
Database Management System Location Enter the path where the
INFORMIX RDBMS software is installed.
SQLEXEC Specifies whether INFORMIX OnLine or INFORMIX
Standard Engine is being used. Enter this information if both the Standard
Engine and Online exist on the machine; otherwise, INFORMIX defaults to
Online. For the INFORMIX Database Management System located in
$INFORMIXDIR:
If using INFORMIX OnLine Engine, enter $INFORMIXDIR/lib/sqlturbo
If using the INFORMIX Standard Engine, enter
$INFORMIXDIR/lib/sqlexec
For the INFORMIX Database Management System located in
c:\win32app\informix on a Windows NT node:
If using INFORMIX OnLine Engine, enter,
c:\win32app\informix\bin\sqlturbo.exe
If using the INFORMIX Standard Engine, enter,
c:\win32app\informix\bin\sqlexec.exe
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.
TBCONFIG Enter the path of the TBCONFIG file used by INFORMIX
OnLine. This file permits INFORMIX OnLine to be configured so that a
large number of tables can be used with joins. Also, table structures and
limits can be varied with this file. Refer to your INFORMIX documentation
for more information on the TBCONFIG file.
2.
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.
Database Name Enter the system identifier (SID) of the ORACLE
database. The SID should be in the correct format for ORACLE.
Database Management System Location Enter the ORACLE home path
(where ORACLE is installed).
OS Username Enter a valid operating system log-in name on the server
machine.
Password Enter the operating system log-in password, if any.
For a given ORACLE SID, all schemas created using that SID
must have the same operating system username and password
combination.
9 - 18
2.
rismgr
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.
Database Name Enter a DB2 database name accessible by the schema.
The name is case sensitive and must have from one to eight alphanumeric
characters.
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.)
OS Username Enter a valid operating system log-in name on the server
machine.
Password Enter the operating system log-in password, if any. The No
Echo/Echo button causes the password to not display (No Echo) or display
(Echo) when it is entered.
For LU6.2 protocol, the Group Name box is ignored in this
version of RIS.
TCP/IP is not supported.
9 - 20
rismgr
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.
LU62 Mode Name Enter the name the Intergraph System
Administrator assigned to the node that permits communication to the
RIS program on an IBM machine. The mode assigns attributes to the
connection and must be predefined by the Intergraph System
Administrator. The mode name is defined when LU6.2 is configured.
This name is case sensitive.
rismgr 9 - 21
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.
2.
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.
Database Management System Location Enter the path where SYBASE is
installed. See the README.TXT file delivered with the RISSYBDS product
for more information. This information is not required for all servers.
OS Username Enter a valid operating system log-in name on the server
machine.
Password Enter the operating system log-in password, if any. The No
EchoEcho button causes the password not to display (No Echo) or to display
(Echo) when it is clicked.
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.
2.
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.
Database Management System Location Enter the path where SQL
Server is installed. See the README.TXT file delivered with the
RISMSFDS product for more information. This information is not required
for all servers.
OS Username Enter a valid operating system log-in name on the server
machine.
Password Enter the operating system log-in password, if any. THe No
Echo/Echo button causes the password not to display (No Echo) or to display
(Echo) when it is clicked.
DSQUERY Currently this field is not used.
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
2.
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.
3.
rismgr 9 - 27
To dismiss the Drop Schema dialog box without dropping the schema, click
the Close button.
Choose the Help button to obtain Drop Schema help.
9 - 28
rismgr
9.2.4
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Select the Secure Schema Access button from the Schema Definition dialog
box.
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.
A dialog box appears. Enter the database username, database password,
operating system username, and operating system password in the dialog box.
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.
5.
6.
9 - 30
rismgr
9.2.5
__________________________________________________________________________________________________________________________________________________
Operating Sequence
Select the Dictionary Access button from the Schema Definition dialog box.
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.
Type a name in the Schema Name box to display information about 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 necessary.
2.
Click the Action button to toggle between granting and revoking access.
3.
rismgr 9 - 31
Enter the name of the user to be granted or revoked access in the Selected
User box.
Select a name from the Access Users list.
Select a name from the All Users list.
4.
9 - 32
rismgr
9.2.6
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Select the Modify Schema Password button from the Schema Definition
dialog box.
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.
Type a name in the Schema Name box to display information about a
schema.
3.
4.
rismgr 9 - 33
9.2.7
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Select the Modify Node Information button from the Schema Definition
dialog box.
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.
8.
rismgr 9 - 35
9.2.8
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Choose the Modify DB2 Password button from the Schema Definition dialog
box.
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.
4.
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
4.
5.
Includes tables, views, and indexes from the in-memory data dictionary
6.
When you click the button for one of these actions, a dialog box associated with that
action appears.
If the selected schema requires a password, or a database
username/password and operating system username/password, the
information must be entered before the dialog boxes can accept
information.
9 - 38
rismgr
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.
In the Schema Name box, type a name.
3.
rismgr 9 - 39
9.3.1
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Choose the Table Info button from the Data Definition dialog box.
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.
The table information appears on the Table Information 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.
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.
4.
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.
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.
3.
rismgr 9 - 43
9.3.4
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Click the Alter Table button on the Data Definition dialog box.
If the table you want to alter is not already the selected table, do one of the
following:
Type a table name in the Table Name box.
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.
Column Name Type the name for the new column.
9 - 44
rismgr
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.
Column Type Choose the data type for the column.
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.
4.
rismgr 9 - 45
9.3.5
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
3.
4.
9 - 46
rismgr
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.
3.
4.
9 - 48
rismgr
9.4
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Click the Schema File button on the RIS Schema Manager dialog box.
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.
Show Schema File Location Produces read-only information on the
specified schema file.
Locate Schema File Lets you rename your schema file or specify a
different protocol.
Checksum Schema File Recomputes the checksum for the specified
schema file.
Checksum is a mechanism used to verify that the schema file
has not been corrupted. If you manually edit the file (instead of
making changes through the RIS Schema Manager), the
checksum is no longer accurate.
rismgr 9 - 49
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.
Nodename or Address Type the nodename or address where the schema
file is located. If the complete path is not specified, the file is assumed to be
located where RIS was installed.
Username Type a system user name that has access to the schema file.
A schema file must be readable by all users permitted to access
the schemas. A schema file must be readable and writable by
all users authorized to create, alter, or drop schemas. The
users permitted to create, alter, and drop schemas must be able
to create and delete files in the directory where the schema file
is located.
Password Type a system password associated with Username. The No
Echo/Echo button causes the password to not display (the default, No Echo)
or display (Echo) when it is entered.
4.
9 - 50
rismgr
9.5
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Click the Locate Client button on the RIS Schema Manager dialog box.
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
7.
9 - 52
rismgr
9.6
__________________________________________________________________________________________________________________________________________________
Operating Sequence
1.
Click the Set button on the RIS Schema Manager dialog box.
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.
9.
9 - 54
rismgr
risplbck 10 - 1
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.
This utility is for debugging purposes only.
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
ERROR
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.
By default, risplbck continues on all results.
10 - 4
risplbck
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>
-?
-V
-n
-i
-c
-d
-t
-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.
-a
<actionfile>
-o
<outputfile>
Examples
_________
To play back the RIS commands previously recorded in the command file load.rap and
calculate command, delay, and total times, key in:
risplbck -cdt -o load.out load.rap
10 - 6
risplbck
Files
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\risplbck
c:\Program Files\Common Files\Intergraph\ris05.nn\parms
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
Status
Returns
______________
0
1
Normal termination.
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.
This utility is for debugging purposes only.
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.
When specifying the <outputfile>, the characters $$ have special
meaning; they are replaced with the process ID of the RIS application.
This produces unique output files every time the RIS application is run.
To use the $$ characters, the <outputfile> name must be placed in single
quotation marks; otherwise, the shell interprets the $$. For example, an
<outputfile> name of risrap.$$ will generate filenames such as,
risrap.1252, risrap.1323, and so forth.
To start the risrecrd utility, do one of the following:
Type risrecrd in a Command Prompt window.
11 - 4
risrecrd
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
_ ____
<none>
-?
-V
on <outputfile>
-c
Record command times. Store how long each RIS command took
to execute.
-d
Record delay times. Store the time between each RIS command.
These values are used by risplbck to reproduce the commands in
real time.
-t
Record total elapsed time. Store the total elapsed time from the
start of the application for each RIS command.
-a
off
query
Examples
_________
The following risrecrd command turns record on and places the output in
c:\appl.rap.
risrecrd -c on risrecrd.out
Files
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\risrecrd
11 - 6
risrecrd
Status
Returns
______________
0
1
Normal termination.
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 representation of information must comply with the format defined in
the section File Formats for risunlod and rislod.
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>
-?
-V
-p
-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.
-s <schemas>
-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
_____
c:\Program Files\Common Files\Intergraph\ris05.nn\bin\risunlod
c:\Program Files\Common Files\Intergraph\ris05.nn\parms
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\ris.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\net.msg
c:\Program Files\Common Files\Intergraph\ris05.nn\config\english\messages\utl.msg
Status
Returns
______________
0
1
Normal termination.
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
Partial table data using risunlods extended where clause
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
Multiple above items in a single run
Table definition only without table data
Table data in separate data file (one for each table)
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.
Enhanced features of risunlod include:
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.
join t2 where t1.c1 = t2.c1 and t1.c2 > t2.c2
There are three ways to interact with risunlod: using the Interactive Interface, the
Command Line Interface, or the Embedded Programming Function Interface.
1.
2.
3.
12 - 8
risunlod
2.
3.
4.
risunlod 12 - 9
12 - 10
risunlod
Select n and risunlod does not unload any tables for the schema.
If you selected a, p, or e at the Which tables should be unloaded? prompt, the
following prompt appears:
Both definitions and data(b) definitions only(o): [b] >
This prompt lets you decide whether to unload both the table definitions and the
data in the tables or only the table definitions.
Do one of the following:
Select o to unload table definitions only.
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.
If you selected a, p, or e at the prompt Which tables should be unloaded? and
selected b to unload both definitions and data, risunlod prompts you for a fixed or
variable data format for unloading table data.
Data in fixed (f) or variable (v) format: [f]>
Do one of the following:
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
12 - 12
risunlod
8.
risunlod 12 - 13
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:
Enter table or view for unloading access privilege:[<return>] >
Enter a table or view name and press ENTER.
Select n, and risunlod will not unload any privileges.
In a schema, privileges may be granted on a table or view owned by
the schema or by another schema. Privileges granted on a table or
view owned by another schema are illustrated in the following
example.
Schema sch1 grants select privilege on its table tab1 to another
schema sch2 with grant option. Schema sch2 can then grant the
select privilege on sch1.tab1 to yet another schema sch3. Thus in
schema sch2, a privilege on the table (tab1) belonging to another
schema (sch1) is defined. The following command line option
illustrates the previous example:
risunlod -s sch2 grant sch1.tab1
When specifying a table or view on which privileges have been
granted, only the name of the relation is needed if it is owned by the
current schema. Otherwise, the relation name must be preceded by
a schema name in the form of <schema>.<relation>.
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>]
The command line interface permits information specified by -s options to be
stored in a specification file. The -f option is used to specify a specification file.
The -s and -f options are mutually exclusive.
risunlod 12 - 15
2.
Level Two
Level Two specifies the types of schema information to be unloaded. The
specification is mainly composed of keywords.
To specify:
Use keyword(s):
table
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.
risunlod -s sch1 .sch1_passwd all
-s sch2 table with var dfile data <level 3>
-s sch3 table with data <level 3> grant <level 3>
-s sch4 table <level 3/4> index <level 3> view <level 3>
grant <level 3>
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.
The following example shows a level 1/2/3 command.
risunlod -s sch1 .sch1_passwd all
-s sch2 table with var dfile data all
-s sch3 table with data t1 t2 grant all
-s sch4 table t1 index t2 view v1 grant t2 v2
sch.3 sch.v3
4.
Level Four
Level Four is valid for tables only. It specifies risunlods extended where clause
for a particular table.
12 - 16
risunlod
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.
The following example shows the contents of a specification file.
sch1 .sch1_passwd all
sch4
table t1 join t2 where "t1.c1 = t2.c1"
index t2
view v1
grant t2 v2 sch.t3 sch.v3
| a | e
overwrite file mode
append file mode
return error
risunlod 12 - 17
The following is the BNF representation of the format for a specification file.
<spec_file_format> ::= {<schema> [.<password>] <info_tobe_unload>}[;<new_line>...]
12 - 18
risunlod
Appendix A
__________________________________________________________________________________________________________________________________________________
A-2
Appendix A
__________________________________________________________________________________________________________________________________________________
A-4
Within RIS only the RIS names (aliases) are valid. The external/DBMS name is
not valid.
A-6
A-8
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.
Insert, update, or retrieve large data.
Access character strings with a length greater than 249 characters for other
RDBMSs not supporting RIS_BLOB.
Considerations when using this capability:
To use RIS_BLOB/RIS_TEXT data, the client and data server versions must be at
least 05.01.01.xx.
This feature is available only through the programming interface; no interactive
access is available.
The application should track the data length.
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.
To create a table with a column of RIS_BLOB/RIS_TEXT data type
create table emp (name char(25), id int, picture ris_blob (50000))
A - 10
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:
create table blob1 (c1 ris_blob(100000))
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:
create table blob2 (c2 ris_blob)
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.
Considerations when using this capability:
RIS Client and Data Servers should be upgraded to RIS Version 5.
Multiple versions are available remotely through TCP only.
The ORACLE 7 Data Server requires the RIS Version 5 Client.
The Sybase SQL Data Server requires the Version 5.02 Client.
A RIS Version 4 application attempts to start up a RIS Version 4 Client. Only if
the RIS Version 4 Client is absent does it start up a RIS Version 5 Client.
Removing the entry 04.03 in the registry under
HKEY_LOCAL_MACHINE/SOFTWARE/Intergraph/RIS will force the RIS
Version 4 applications to start the RIS Version 5 Client. The same is true for
Client/Server.
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
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.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.
Considerations when using the Version 5 loader/unloader:
The loader/unloader provides no BLOB support.
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.
A.13 Parameters
The parameter file generated by a Version 5 application or utility is compatible with
Version 4 applications. In Version 4, if a parameter file existed, all parameters were
expected to be set. Unlike Version 4, Version 5 is more tolerant with respect to
parameter files: any number of parameters can be left unspecified and RIS uses the
default values.
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 limitations and guidelines:
RIS schema and user names can be internationalized, but not passwords.
Only alpha-numeric characters can be internationalized.
Setup is not fully internationalized.
RIS does not localize dialogs, gadgets and error messages.
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.
All punctuation, keywords, column datatype definitions, timestamp data,
statements 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
The following components of a create schema statement are 8-bit and 16-bit characters:
create schema
schema name
schema pass
db type
dbname
db dir
osuser
ospass
ostype
db user
remote clause
8-bit English
8-bit and 16-bit English
8-bit English
8-bit English
8-bit and 16-bit English
8-bit and 16-bit English
16-bit English
8-bit English
8-bit English
8-bit and 16-bit English
8-bit English
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 B
__________________________________________________________________________________________________________________________________________________
B-2
Appendix B
__________________________________________________________________________________________________________________________________________________
Meaning
default schema
Specifies a schema
Defines a schema
create table
Defines a table
insert into
field definition
line of data
B-4
create index
Defines an index
create view
Defines a view
grant
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:
***RIS*** End of Schema ***RIS***
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:
create table statement
insert into statement
field definition
lines of data or a data files specification
end of table indicator
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.
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:
***RIS*** End of Table ***RIS***
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.
B.1
1.
2.
3.
4.
B-6
B.2
B.3
B.4
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:
char_col1 1 12 char_col2 14 23 int_col 25 35
smallint_col 37 42 double_real_col 44 66 real_col 68 81
decimal_col1 83 94 decimal_col2 95 109
The starting and ending positions of a field are constrained by the following
relation:
10,000 >= ending position >= starting position >= 1.
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 keyword var following a column name distinguishes a character column
having variable-length values from a character column having fixed-length values.
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.
Because a character column supported by RIS can store values of different
lengths, it is always unloaded as a variable character column.
The delimitations used by risunlod are two single quotation marks.
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
The conventions used by risunlod for determining the field width of a column are:
Column Data Type
character
decimal
integer
11
small integer
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***
B.5
-123.456
This example is prepared according to the field definition for the table tabl1.
In this example, the column char_col1 is a character column with variable-length
values. Thus, its value, xxxx, is enclosed in a delimitation (two single quotation
marks). The column char_col2 is a character column with fixed-length values. There is
no delimitation surrounding its values, and these values are assumed to occupy the
entire fields. In this example, the value for the column char_col2 is a string of four ys
followed by six blanks. NULL value is not represented by the keyword NULL in the
format. Instead, if a column value is NULL, the entire field for storing that value
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.
B.6
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.
5.
6.
B - 10
B.7
B.8
B.9
<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
<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***
<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***
<comments> ::= -- [<string>]
B - 14
Glossary GL - 1
Glossary
__________________________________________________________________________________________________________________________________________________
GL - 2
Glossary
Glossary GL - 3
Glossary
__________________________________________________________________________________________________________________________________________________
absolute pathname
accept
access
activate
ad hoc query
address
alias
ANSI
application
array
arrow keys
ASCII
association
attribute
attributes
GL - 4
Glossary
bit
BLOB
button
cabinet
cache
catalog
char
character
check box
checklist
choose
clicking
client
CLIX
collection
column
command
Glossary GL - 5
command file
command line
CPU
CRT
data dictionary
data point
data structure
data type
database
DB2
decimal
default
default schema
delete
delimiter
device
GL - 6
Glossary
dialog box
dimmed
disk
document
double
drop
edit
EMACS
enter
entity
environment variable
error message
Ethernet
executable
exit
field
file
Glossary GL - 7
filename
flag
float
floppy disk
font
form
ftr
full pathname
function
gadget
grant option
graphic
group
Help
Help window
hierarchy
GL - 8
Glossary
horizontal
icon
ID
identify
index
indexing
INFORMIX
int
integer
interactive
interface
I/ORL
item
job
joining
key-in
Glossary GL - 9
keyword
library
Collection of subroutines.
linear
link
local
log file
log in
log-in
memory
menu
Microsoft Windows
mode
mouse
MSSQL
network
GL - 10
Glossary
node
nodename
NULL
Indicates no value.
on-line Help
operating system
operator
ORACLE
ORL
See I/ORL.
overview
pair
parameter
Parametric
Programming
Language
password
path
pathname
place
portable
PPL
Glossary GL - 11
privilege
process
Program Manager
prompt
query
A search in a database.
query criteria
quit
raster
raster data
RDBMS
real
record
relation
Table or view.
GL - 12
Glossary
relation privilege
relational database
Relational Interface
System
relative pathname
report
requester
See client.
resize
resolution
RIS
root
routine
row
run
scale
schema
scripts
scroll
Glossary GL - 13
scroll bar
search term
select
server
set
shell
site
slider
smallint
SNA
specification file
SQL
statement
states
stop
string
Sequence of characters.
GL - 14
Glossary
Structured Query
Language
SUN/OS
SUN/SOLARIS
Sybase
syntax
system
table
tap
TCP/IP
template library
text
text editor
timestamp
toggle
transaction
translation
tuple
Record or a row.
type
unit
Glossary GL - 15
UNIX
user
user interface
value
variable
VAX/VMS
version
vi
view
window
Windows NT
workstation
XNS
GL - 16
Glossary
Index IN - 1
Index
__________________________________________________________________________________________________________________________________________________
IN - 2
Index
Index IN - 3
Index
__________________________________________________________________________________________________________________________________________________
A
accessing
dictionary views A-7
aliases
exclude/include sequences A-4
object A-4
within RIS A-5
ASCII files
loading schema information from 8-3
B
bad file 8-9
batch execution of SQL statements 3-3
binary data A-8
BLOBS
programming interface A-8
C
changing
columns data type 6-3
schemas 9-3
choose 1-4
clean servers 4-3
client
locate 9-50
command line interface 8-17
command line syntax 8-18
commandfiles 10-3
commands
recording 11-3
connecting to tables
granting and revoking authority A-5
create index B-4
create schema dialog box
DB2 9-19
INFORMIX 9-15
Microsoft SQL Server 9-24
ORACLE 9-17
SQL Server 9-24
SYBASE 9-22
create [secure] schema B-3
create table B-3
create table dialog box 9-40
IN - 4
Index
field definitions
format B-6
file
bad 8-9
files
ASCII, loading schema information from
8-3
data B-3
log, creating 8-8
main B-3
outputfile 11-3
format
data file specifications B-9
data files B-10
field definitions B-6
index definitions B-10
insert into B-6
privilege definitions B-10
schema definitions B-5
table definitions B-6
view definitions B-10
G
getting started 2-3
grant B-4
GRANT CONNECT TO A-5
GRANT RESOURCE TO A-5
GRANT SCHEMA TO A-6
H
Help
using on-line 1-6
I
identify 1-4
include sequences A-4
including data owned by privileged accounts
A-3
index definitions
format B-10
loading 8-10
indexes
with same name A-4
INFORMIX
create schema dialog box 9-15
insert into B-3
format B-6
inserting large data A-8
interactive interface
using rislod with 8-10
using risunlod 12-7
Index IN - 5
K
key in 1-4
L
line of data B-3
load 8-3
loading
index, view, and privilege definitions
8-10
schema information 8-3
loading queries 7-6
locate client 9-50
log files, creating 8-8
long binary data A-8
long text data A-8
M
main file B-3
Microsoft SQL Server, create schema dialog
box 9-24
modify DB2 password dialog box 9-35
modify node information dialog box 9-33
modify schema password dialog box 9-32
mouse 1-4
N
names, aliases A-5
new line characters B-10
O
objects
aliases A-4
dictionary A-6
of different owners within a schema A-3
ownership A-3
sharing among schemas A-3
on-line Help 1-6
operators
UNION and UNION ALL A-3
ORACLE
create schema dialog box 9-17
outputfile 11-3
overview of utilities 2-3
ownership of objects A-3
P
parts of the Help window 1-6
passwords
RIS A-5
stored for schema A-5
IN - 6
Index
schema
administrator
granting and revoking authority A-5
definitions, format B-5
schema manager 9-3
activating 9-5
create schema dialog box 9-11
DB2 9-19
INFORMIX 9-15
Microsoft SQL Server 9-24
ORACLE 9-17
SQL Server 9-24
SYBASE 9-22
data definition dialog box 9-37
alter table dialog box 9-43
create table dialog box 9-40
drop table dialog box 9-42
table information dialog box 9-39
dictionary access dialog box 9-30
drop schema dialog box 9-26
exclude dialog box 9-47
include dialog box 9-45
locate client dialog box 9-50
modify DB2 password dialog box 9-35
modify node information dialog box 9-33
modify schema password dialog box 9-32
schema definition dialog box 9-7
schema file dialog box 9-48
schema information dialog box 9-9
secure schema access dialog box 9-28
Schema Manager
Set dialog box 9-52
Schema Manager dialog box 9-5
schemas
adding to dictionary A-6
changing 9-3
creating 9-3
definition in RIS 5 A-3
dictionary creation A-6
displaying information 9-3
dropping A-6, 9-3
granting and revoking authority A-5
multiple in databases A-6
multi-user A-5
objects of different owners within A-3
passwords stored for A-5
retrieving information 12-3
secure A-5
sharing objects among A-3
transferring information 8-3
usernames stored for A-5
Index IN - 7
view definitions
format B-10
loading 8-10
viewing on-line Help 1-6
views
including data without A-3
with same name A-4
W
WHERE clause A-7
ris_object condition A-7
IN - 8
Index