The following table has four rows. Each row describes one of the locations in the Host On-Demand user interface (and the corresponding location in the Database On-Demand user interface) where a list of available schemas and tables can be specified:
Who can modify: | Location (Host On-Demand client): | Location (Database On-Demand client): | Valid contents: |
---|---|---|---|
1. Host On-Demand administrator | The Table Filter input field on the Tables tab of the Data Transfer Defaults window in the session properties window of a 3270 Display, 5250 Display, or VT Display session. | The Table Filter input field on the Tables tab of the Database On-Demand Group/User Options window in the Administration Utility. | A comma-separated list of schema names, schema filters, table names, and table filters |
2. User (If the option is enabled by the Host On-Demand administrator) | The Table Filter input field on the Tables tab of the Data Transfer Defaults window in the session window of a 3270 Display, 5250 Display, or VT Display session. | The Table Filter input field on the Tables tab of the Database On-Demand User Options window launched from the Database On-Demand desktop. | A comma-separated list of schema names, schema filters, table names, and table filters |
3. User (If the option is enabled by the Host On-Demand administrator) | The Table Filter input field on the Logon tab of the SQL Wizard and on the Logon tab of the File Upload Wizard. | A comma-separated list of schema names, schema filters, table names, and table filters | |
4. User |
The table name filter input field:
|
One table name or one table filter |
The locations described in the second and third rows of the above table are available to the user only if permitted by the administrator. To make these functions available to the user:
The location described in the fourth row is always available to the user.
For the locations described in the first three rows of the table above:
*USRLIBL
on the iSeries.)
SQL Assist Exception
SQL Assist Exception
in the following circumstances:
*USRLIBL
)
in the Table Filter field.
%
,
signifying all tables.
For the location described in the fourth row of the table above:
%
).
%
) by itself
signifies all tables
(literally, every table whose name contains 0 or more characters).
The last column of each row in the table at the top of this help file shows, for the specified location, what are the valid contents of the list of available schemas and tables. More specifically:
For example:
QIWS, IBMTEST%, MYSCHEMA.TEST01, MYSCHEMA.%TEST, %R.%
For an explanation of this example, see the last row of the table of examples in the next subsection (Examples).
For example:
%TEST
For an explanation of this example, see the table of examples in the next subsection (Examples).
Special rules for the location described in the fourth row of the table above: |
---|
|
The following paragraphs describe how to specify each type of element. For an explanation of the examples, see the table of examples in the next subsection (Examples).
QIWS
, MYSCHEMA
%
) signifies 0 or more occurrences
of any character. (Therefore a percent sign by itself
signifies every schema whose name contains 0 or more characters, that is, all schemas.)
_
) signifies 1 occurrence
of any character.
IBMTEST%
, %TEST
, MYSCHEM_
.
),
followed by a table name.
Examples: IBMTEST.TEST01
Use this format only in the locations described in the first three rows of the table at the top of this help file.
TEST01
Use this format only in the location described in the fourth row of the table at the top of this help file.
%
) or underline ( _
).
These special characters have the same meanings in a table
filter as they do in a schema filter.
Use the appropriate format:
MYSCHEMA.%TEST
, %.R%
%TEST
, R%
The following table contains examples of how to specify schema names, schema filters, table names, and table filters. The table includes both the examples mentioned in preceding subsections of this help file and also other examples.
Example: | Meaning: | ||||
---|---|---|---|---|---|
% | All schemas. (Literally, every schema whose name contains 0 or more characters.) | ||||
*USRLIBL,MYSCHEMA | All schemas (iSeries "libraries") in the user portion of the iSeries library list, plus the schema named MYSCHEMA. | ||||
_ | All schemas whose names have exactly one character. | ||||
QIWS |
The schema named QIWS .
|
||||
MYSCHEMA |
The schema named MYSCHEMA .
|
||||
IBMTEST% |
All schemas with names beginning with IBMTEST
(such as IBMTESTSUITE , IBMTEST01 , and so on).
|
||||
%TEST |
All schemas with names ending with TEST
(such as IBMTEST , INITIALTEST , and so on).
|
||||
MYSCHEM_ |
All schemas with names beginning with MYSCHEM
and having exactly eight characters
(such as MYSCHEMA , MYSCHEMB , and so on).
|
||||
__TEST |
All schemas with names ending with TEST
and having exactly six characters
(such as RETEST , MYTEST , and so on).
|
||||
%ES% |
All schemas with names containing the character sequence ES
(such as IBMTEST , ESPY , TRIES , and so on).
|
||||
_ES_ |
All schemas with names containing the character sequence ES
and having exactly one character before and one character after
(such as TEST , REST , and so on).
|
||||
IBMTEST.TEST01 |
Table TEST01 in schema IBMTEST .
|
||||
%.TEST01 |
Table TEST01 in all schemas (that is,
table TEST01 in schema IBMTEST ,
and table TEST01 in schema MYSCHEMA ,
and table TEST01 in schema MYSCHEMB ,
and so on).
|
||||
TEST01 |
Table TEST01 .
|
||||
MYSCHEMA.%TEST |
All tables in MYSCHEMA with names ending in TEST
(such as MYSCHEMA.MYTEST ).
|
||||
MYSCHEMA._TEST |
All tables in MYSCHEMA with names ending in TEST
and having exactly five characters.
(such as MYSCHEMA.XTEST ).
|
||||
%TEST |
All tables with names ending in TEST
(such as MYTEST , RETEST ).
|
||||
%.R% |
All tables with names beginning with R , in all schemas.
|
||||
QIWS, IBMTEST%, MYSCHEMA.%TEST, %.R% |
The schema QIWS , all schemas with names beginning with IBMTEST ,
all tables in MYSCHEMA with names ending in TEST ,
and all tables beginning with R in all schemas.
|
The meaning of an entire list is the sum of the meanings of the individual elements. In more technical terms, the meaning of a entire list is arrived at by logically adding together (using logical OR) the meanings of the individual elements.
For example the following list:
R%, MYSCHEMA.TEST01, A%means that the following schemas and tables are available:
R
, plus
A
.