The following text lists error messages you might encounter while accessing the database on the ClearPath MCP server and lists possible corrective actions.
The control file for your database cannot be found.
Use the Relational Design Center to update your database.
No message; you get no response.
The server task SYSTEM/SQL/WORKER might be waiting. Perform the following steps to respond to this situation:
1. Log on to CANDE using the usercode with which you were trying to connect. 2. Enter the following command to determine whether the SQL Query Processor
system files are installed on the secondary family:
FAM*
3. If the secondary family is not in the proper location, change the family statement in the USERDATAFILE.
4. If the secondary family is not an issue, check for waiting entries to try to resolve the problem.
5. Contact the Unisys Support Center if you cannot resolve this problem.
Another possible cause for this error condition is that the SYSTEM/SQL/CONFIG file is waiting on a “NO FILE” condition for the SQL Query Processor configuration file (DMSQL/CONFIG).
Run the *SYSTEM/SQL/CONFIG program from CANDE to determine the title of the file for which the worker is looking and to verify the syntax of the statements in the file.
java.net.ConnectException: Connection refused: connect
The specified port number might be incorrect.
Execute the following command on the ClearPath MCP server to identify the correct port number:
NA DMSQL STATUS
java.net.UnknownHostException: eccsxx
The specified server name is incorrect. Identify the correct name of the server.
Unable to connect to data source
The user-specified resource or database name is incorrect. Use the Query Design Center to check the catalog of available resources.
A
access point for network, 5-7 access rights, 7-2
assigning in Relational Design Center, 4-42 accesscode, Query Design Center, 3-2 accesses
SQL, 4-23
adding a server, Relational Design Center, 4-30
ALPHA data items modeled in SQL, 4-24
with ccsversion specifications, modeling, 4-23
Analyze Query window, 3-3, 3-11 commands, 3-13
results pane, 3-12 text pane, 3-11
applying schema modifications, Relational Design Center, 4-37
assigning access rights to database structures, in Relational Design Center, 4-42
assigning library function names, 2-4 associating users with software, 6-7
attribute type, modeled from data item types (table), 4-23
authentication, setting up Kerberos, A-1 automating SQL Query Processor server
initialization, 5-7
B
BACK command, 5-15
base release identifier, denoting in the SQL Query Processor configuration file, 6-6
base tables, SQL views of, 4-23
batch mode, running DMQUERY utility, 8-7
benefits, SQL Query Processor, 1-4 bit vector
physical organization sets mapped in SQL, 4-23
subsets not modeled in SQL, 4-23 BLOCKEDTIMEOUT value, 2-7, 5-8 BYE command, DMQUERY utility, 8-2
C
CANCEL command, DMQUERY utility, 8-2 CANDE RUN statement, 7-7
CARD file, 7-4
case-sensitive passwords, limitations, B-1 Catalog window, 3-3, 3-6
CCS clause, 6-11, 6-13
ccsversion specification in SQL, 4-23 changing name and location of configuration
file, 2-6
chargecode, Query Design Center, 3-2 ClearPath MCP environment
installing SQL Query Processor in the Windows environment, 2-11 ClearPath MCP servers, terminology, 1-1 CLOSE command, DMQUERY utility, 8-2 closing the trace file, 5-14
column attributes, query table pane, 3-20 column properties, Catalog window, 3-8 Command and Edit (CANDE) message control
system (MCS) RUN statement, 7-7
Command and Edit (CANDE), running DMQUERY utility, 8-7 command interface LIST command, 7-3 reporting on descriptions, 7-8 results file, 7-3 SQLVIEW command, 7-6 commands
Analyze Query window, 3-13 BACK, 5-15
CLOSE, 8-2 COMMIT WORK, 8-2 DEFINE, 8-3 DIAGNOSE, 8-3 DMSQL, 5-5 DMSQL HELP, 5-6 DMSQL SHOW STATUS, 5-10 DO, 8-3 HELP, 5-6 LIST, 7-3, 7-8 LOG, 5-11 MODIFY in WFL, 5-7 OPEN, 8-3 PARSE, 8-3 QD, 8-4 REPEAT, 8-4 ROLLBACK WORK, 8-4 SAVEPOINT, 8-4 SET, 8-4 SHOW, 8-6 SHOW STATUS, 5-10 SQLVIEW, 7-6 TRACE, 5-14
COMMIT WORK command, DMQUERY utility, 8-2
components, SQL Query Processor, 1-4 configuration
*DMSQL/SERVER/CONFIG file, creating, 5-7
process for resource, 5-2
SQL Query Processor server, 5-5 starting, 5-5
stopping, 5-5
configuration control facility, SQL Query Processor, 6-2
configuration file (See SQL Query Processor configuration file)
configuring
distributed systems services (DSS), 2-8 server resources, 5-2
conflicting names, handling, 4-9
connection status, Query Design Center, 3-5 control file, 7-2
controlling SQL Query Processor server, 5-5 conventions for terminology, 1-1
conventions for usercode and password, Query Design Center, 3-2 creating
*DMSQL/SERVER/CONFIG file, 5-7 dump file, 5-15
integrity constraints in Relational Design Center, 4-45
server configuration file, 2-6 SQL database in Relational Design
Center, 4-32
SQL dates in Relational Design Center, 4-44
SQL Query Processor configuration file, 6-4
SQL views in Relational Design Center, 4-47
customizing, Query Design Center, 3-24
D
Data and Structure Definition Language (DASDL)
example
embedded data set in SQL, 4-21 embedded data set mapped in
SQL, 4-17
occurring item mapped in SQL, 4-17, 4-19
data item properties, Relational Design Center, 4-4
data items defaults, 4-23
modeled as SQL attribute types, 4-23 occurring, mapped in SQL, 4-15 options, modeled in SQL, 4-24 data set properties, Relational Design
Center, 4-4 data sets disjoint, modeled in SQL, 4-10 embedded mapped in SQL, 4-17, 4-19 modeled as SQL tables, 4-14 occurring items example, 4-14 restart, modeled in SQL, 4-25 variable-format
deleting table rows, 4-13 example, 4-13
mapping in SQL, 4-10
SQL mapping example, 4-10, 4-11 data sources, 5-2, 5-4
database entities (table), 4-28
database properties, Relational Design Center, 4-4
databases
access mode, 5-3, 6-11
Enterprise Database Server, 5-4 list, 6-12
resource preparation, 5-4 SQL, 5-4
title, 6-12
date construct, SQL, 4-26 DDLRESULTS file, 7-3
default properties, Query Design Center, 3-24 default release specification, 6-4, 6-10
defaults access, 4-23 data item, 4-23 disjoint data set, 4-10 embedded data set, 4-14 global data, 4-10
group, 4-25 link, 4-25
occurring item, 4-14 physical option, 4-25 restart data set, 4-25 set, 4-23
SQL names, 4-9 subset, 4-23
DEFINE command, DMQUERY utility, 8-3 defining
data source, 5-2
release identifiers in the SQL Query Processor configuration file, 6-6 repository, 5-2
resources, 5-2, 5-3
SQL Query Processor configuration file, 6-4
deleting rows from variable-format table, 4-13 description file, 7-2
descriptions
generating SQL, 7-6
reviewing results of generating SQL, 7-3 Design Query window, 3-3, 3-20
join pane, 3-20
query table pane, 3-20 results pane, 3-22 text pane, 3-22
designating users in the SQL Query Processor configuration file, 6-7 designing a query, Query Design Center, 3-22 determining connection status, Query Design
Center, 3-5
DIAGNOSE command, DMQUERY utility, 8-3 diagnostics
gathering dump information, 5-15 gathering information, 5-11, 5-13 trace information, 5-13
modeled as SQL tables, 4-10 displaying the dump file, 5-15 distributed systems services (DSS)
configuration, 2-8 DMQUERY utility, 8-1 commands, 8-2 BYE, 8-2 CANCEL, 8-2 CLOSE, 8-2 COMMIT WORK, 8-2 DEFINE, 8-3 DIAGNOSE, 8-3 DO, 8-3 OPEN, 8-3 PARSE, 8-3 QD, 8-4 REPEAT, 8-4 ROLLBACK WORK, 8-4 SAVEPOINT, 8-4 SET, 8-4 SHOW, 8-6 files, 8-9
running in batch mode, 8-7 running through CANDE, 8-7 using SQL statements, 8-1 DMSQL command, 5-5 DMSQL HELP command, 5-6
DMSQL SHOW STATUS command, 5-10 DMSQL/CONFIG file, creating, 2-5 DMSQL/SERVER/CONFIG, server
configuration file, 2-6
DO command, DMQUERY utility, 8-3 DSS (distributed systems services)
configuration, 2-8 dump file, 5-15
E
editing SQL Query Processor configuration file, 5-2, 6-4, 6-11
embedded data sets
mapped in SQL, 4-14, 4-17, 4-19, 4-23 modeled as SQL tables, 4-14
embedded subsets, not modeled in SQL, 4-23
embedded table, 4-17 deletions, 4-15
for DASDL duplicates, SQL example of, 4-19
manual commit mode, Query Design Center, 3-15
SQL access, 7-5
trace facility on SQL Query Processor server, 5-13
enabling tracing, Query Design Center, 3-26 Enterprise Database Server
base tables, SQL views of, 4-23 data item types, modeled in SQL
(table), 4-23 databases, 5-4
updating with SQL queries, 2-22 names used in SQL description, 4-9 restart data set, modeled as SQL
table, 4-25
subsets, default modeling, 4-23 Enterprise Database Server data set
updating with SQL queries, 2-22 error messages, B-2
F
file compression, 5-8 files displaying dump, 5-15 DMQUERY utility, 8-9 input, 7-4 program dump, 5-15 results, 7-3SQL Query Processor configuration, 5-2, 5-3, 6-11 (See also SQL Query Processor configuration file) type required for the SQL Query Processor
configuration file, 6-4
fixed-length strings, from occurring items in global data, 4-15
function names, manually assigning, 2-4
G
generating a QDump, Query Design Center, 3-19
generating a QGraph, Query Design Center, 3-18
generating SQL description, 7-6
getting the SQL schema, Relational Design Center, 4-36
global data defaults in SQL, 4-10 global tracing, 5-13
grants, 4-29
purpose, 4-13 group defaults, 4-25
applied to SQL occurring items, 4-25
H
handling naming conflicts in SQL, 4-9 hardware requirements, 2-2
HELP command, 5-6
help information, obtaining, 5-6
I
icons
Catalog window, 3-6
Relational Design Center, 4-3 identifier, base release, 6-6 identifier, resource, 6-11 identifier, worker, 5-10 identifying server log, 5-11
importing a relational schema, Relational Design Center, 4-31
index properties, Relational Design Center, 4-5
initial values in SQL mapping, 4-22 initialization of SQL Query Processor
server, 5-7
INITIALVALUE data item option, modeled in SQL, 4-24
input file, 7-4
installation tasks, optional, 2-9 installing the SQL Query Processor
MCP environment, 2-3 troubleshooting, 2-16 Windows environment, 2-11 integrity constraints
creating in Relational Design Center, 4-45 modifying in Relational Design
Center, 4-46 interface
Query Design Center, 3-3 Relational Design Center, 4-2 internationalization, 6-11
IP address worker, 5-10
isolation levels, setting in Query Design Center, 3-16
J
join pane, Design Query window, 3-20
K
Kerberos authentication, setting up, A-1 keys foreign, 4-26 primary, 4-26 column, 4-14
L
limit clause, 6-13linear search of master table, 4-16 links, defaults in SQL, 4-25 LIST command, 7-8
listing status of the SQL Query Processor server, 2-21
loading the schema, Relational Design Center, 4-37
LOG command, 5-11
logging diagnostic information, 5-11 logical database, 6-11, 7-6, 7-8
title, 6-12, 7-6, 7-9
M
maintenance options for occurrence indexes in SQL, 4-16
making the SQL Query Processor configuration file, 6-4
manual commit mode, enabling in Query Design Center, 3-15
manual subsets, not modeled in SQL, 4-23 mapping
accesses, 4-23
bit vector physical organization sets, 4-23 DASDL embedded data set, 4-17
DASDL example duplicates, 4-19
embedded data set in SQL, 4-21 occurring items, 4-17
embedded data sets, 4-14, 4-17, 4-19, 4-23 Enterprise Database Server
initial values, 4-22 nonoccurring groups, 4-25 occurrence index, 4-15 occurring groups, 4-25 occurring item, 4-15, 4-17 physical options, 4-25 relational, 4-8
restart data set, 4-25 sets, 4-23
simple data items (table), 4-23 SQL example of variable-format data
sets, 4-11 subsets, 4-23
unordered list physical organization sets, 4-23
variable-format data sets, 4-10 master rows
deleting, 4-15
row additions and, 4-22 master table, linear search, 4-16 MCP environment
hardware requirements, 2-2
installing the SQL Query Processor, 2-3 reinstalling SQL Query Processor, 2-15 removing SQL Query Processor, 2-13 software requirements, 2-2
uninstalling SQL Query Processor, 2-13 menu bar
Query Design Center, 3-4 Relational Design Center, 4-7 migrating from an earlier release, 2-12 mix number, worker, 5-10
mode, database access, 5-2, 6-11, 6-12 modeling
embedded data sets, 4-14 embedded levels, example, 4-14 embedded tables, 4-14
nonoccurring items, 4-15 occurring items, 4-14
physical set organizations, 4-23
REQUIRED and INITIALVALUE data item options, 4-24
MODIFY, WFL command, 5-7 modifying resource definitions, 5-3 modifying, in Relational Design Center
access rights to database structures, 4-43 data items, 4-41
data sets, 4-39 indexes, 4-41
SQL views, 4-47
variable-format items, 4-40
N
names
defaults in SQL, 4-9 handling conflict of, 4-9 SQLVIEW results file, 7-3 naming the SQL Query Processor
configuration file, 6-3, 6-4 network access point, 5-7 automatic initialization, 5-7 specification, 5-7 SQL Query Processor, 5-8
nonoccurring groups in SQL mapping, 4-25 nonoccurring items, modeled in SQL, 4-15
O
occurrence indexes, mapped in SQL, 4-15
occurring groups in SQL mapping, 4-25 occurring item properties, Relational Design
Center, 4-5 occurring items
in global data, modeled in SQL, 4-15 in SQL, initial values and, 4-22 mapped in SQL, 4-15, 4-17, 4-19 modeling, 4-14
occurring table, 4-17
SQL example of for DASDL duplicates, 4-19
OPEN command, DMQUERY utility, 8-3 opening a database, Relational Design
Center, 4-34
opening a query, Query Design Center, 3-15 opening tables, Query Design Center, 3-9 optimizer, 4-14
SQL query, 4-18
optional installation tasks, 2-9
options for maintaining occurrence indexes in SQL, 4-16
output view, Relational Design Center, 4-6
P
password conventions, starting Query Design Center, 3-2
physical option defaults, mapped in SQL, 4-25 physical set organizations, modeled in
SQL, 4-23
port number, TCP/IP, 5-8
preparing and executing a query, Query Design Center, 3-14
preparing database as resource, 5-4 primary key column, 4-14
primary key properties, Catalog window, 3-8 printer backup file, for program dump, 5-15 program dump, 5-15
program specification, 6-8 properties view
Catalog window, 3-7
Relational Design Center, 4-3
Q
QD command, DMQUERY utility, 8-4 QDump, generating in Query Design
Center, 3-19
QGraph, generating in Query Design Center, 3-18
Query Design Center, 1-4
Analyze Query window, 3-3, 3-11 Catalog window, 3-3, 3-6
creating a savepoint, 3-17 customizing, 3-24
default properties, 3-24 described, 3-1
Design Query window, 3-3, 3-20 designing a query, 3-22
determining connection status, 3-5 enabling manual commit mode, 3-15 enabling tracing, 3-26 generating a QDump, 3-19 generating a QGraph, 3-18 interface, 3-3 menu bar, 3-4 opening a query, 3-15
opening tables in Catalog window, 3-9 preparing and executing a query, 3-14 rolling back to a savepoint, 3-17 saving a query, 3-14
saving query results, 3-15
setting isolation level for transaction, 3-16 setting row limit for queries, 3-17
viewing column results in Catalog window, 3-10
viewing table results in Catalog window, 3-9
query optimizer, 4-18
query table pane, Design Query window, 3-20 query, designing in Query Design
Center, 3-22
R
referential integrity constraints, SQL, 4-25 refreshing a database, Relational Design
Center, 4-35
reinstalling SQL Query Processor in the MCP environment, 2-15 in the Windows environment, 2-15 Relational Design Center, 1-4
adding a server, 4-30
applying schema modifications, 4-37 assigning access rights, 4-42
creating
integrity constraints, 4-45 SQL database, 4-32 SQL dates, 4-44 SQL views, 4-47 data item properties, 4-4 data set properties, 4-4 database properties, 4-4 described, 4-1
getting the SQL schema, 4-36 icons, 4-3
importing a relational schema, 4-31 index properties, 4-5
interface, 4-2
loading the schema, 4-37 menu bar, 4-7
modifying
access rights to database structures, 4-43 data items, 4-41 data sets, 4-39 indexes, 4-41 integrity constraints, 4-46 occurring items, 4-40 SQL database, 4-37 SQL dates, 4-45 SQL views, 4-47 variable-format items, 4-40 output view, 4-6 properties view, 4-3 refreshing a database, 4-35 removing a database, 4-35 removing a server, 4-30 restoring a database, 4-36 saving the schema, 4-36 starting, 4-2
tree view, 4-3
user assistance view, 4-6
variable-format item properties, 4-6 working with databases, 4-34 working with schemas, 4-39 working with servers, 4-30 relational mapping, SQL, 4-8
release identifier, denoting in the SQL Query Processor configuration file, 6-5 release level, associating with users, 6-7 release specification, 6-4
default, 6-4 syntax for, 6-5
removing a database, Relational Design Center, 4-35
removing a server, Relational Design Center, 4-30
removing SQL Query Processor from the MCP environment, 2-13 from the Windows environment, 2-15 REPEAT command, DMQUERY utility, 8-4 report
server log, 5-11
SQL Query Processor server status, 5-10 reporting on an SQL description, 7-8 repository, 5-2
attributes, 5-2
REQUIRED data item option, modeled in SQL, 4-24
requirements hardware, 2-2
MCP environment software, 2-2 software, 2-2
updating Enterprise Database Server data set with SQL queries, 2-22 updating Enterprise Database Server
database with SQL queries, 2-22 Windows environment software, 2-3 resolving naming conflicts, 4-9
resource, 5-2 configuration, 5-2
resource specification, 6-11 restart data set defaults, 4-25
restoring a database, Relational Design Center, 4-36
results file accessing, 7-3 contents, 7-3
default name with Schema Administrator command interface, 7-3
results pane
Analyze Query window, 3-12 Design Query window, 3-22
ROLLBACK WORK command, DMQUERY utility, 8-4
rolling back to a savepoint, Query Design Center, 3-17
row additions in relation to master row, 4-22 row limit, setting in Query Design
Center, 3-17
S
savepoint
creating in Query Design Center, 3-17 rolling back to in Query Design
Center, 3-17
SAVEPOINT command, DMQUERY utility, 8-4 saving
query results, Query Design Center, 3-15 query, Query Design Center, 3-14 schema, Relational Design Center, 4-36 Schema Administrator command
interface, 7-8
generating SQL description, 7-6 LIST command, 7-8
schema, viewing SQL, 7-3 security
accesses and permissions, 4-28 SQL grants, 4-29
SQL views, 4-29 views and grants, 4-28 server configuration file
DMSQL/SERVER/CONFIG, 2-6 server resources, 5-2
SET command, DMQUERY utility, 8-4 sets, defaults in SQL, 4-23
setting
look and feel, Query Design Center, 3-5 row limit, Query Design Center, 3-17 timeout intervals, SQL Query Processor
server, 5-9
transaction isolation level, Query Design Center, 3-16
setting up Kerberos authentication on Windows, A-1
SHOW command, DMQUERY utility, 8-6 SHOW STATUS command, 5-10
SL/CONFIG file (See SQL Query Processor configuration file)
software
associating with users, 6-7
identifying location in the SQL Query Processor configuration file, 6-6 software release
denoting in the SQL Query Processor configuration file, 6-5
software requirements, 2-2
specifying users in the SQL Query Processor configuration file, 6-7
SQL (See Structured Query Language) SQL catalog, 7-2
SQL dates
creating in Relational Design Center, 4-44 modifying in Relational Design
Center, 4-45 SQL queries
updating Enterprise Database Server data set with, 2-22
updating Enterprise Database Server database with, 2-22
SQL Query Processor benefits, 1-4
closing trace files, 5-14 components, 1-4 described, 1-3
enabling trace facility, 5-13 hardware requirements, 2-2 installing in MCP environment, 2-3 installing in Windows environment, 2-11 network, 5-8
optional installation tasks, 2-9 overview, 1-1
Query Design Center, 1-4 reinstalling in the Windows
environment, 2-15 reinstalling on MCP system, 2-15 Relational Design Center, 1-4
removing from the MCP environment, 2-13 removing from the Windows
environment, 2-15 resource specification, 6-11 resources, configuring, 5-2 server
closing trace files, 5-14 configuration, 5-5 controlling, 5-5
enabling trace facility, 5-13 log, 5-11
setting timeout intervals, 5-9 starting, 5-5
status, 5-10 stopping, 5-5
task, SYSTEM/DMSQL/WORKER, 5-4 terminating, 5-6
trace information, identifying trace file, 5-13
trace information, viewing, 5-13 troubleshooting, 2-16
server log contents, 5-12 identifying, 5-11
software requirements, 2-2 uninstalling from the MCP
environment, 2-13 uninstalling from the Windows
environment, 2-15
SQL Query Processor configuration control facility, 6-2
SQL Query Processor configuration file, 5-2, 5-3, 6-2
base release identifier, 6-6 CCS clause, 6-13
changing name and location, 2-6 constructing release identifiers, 6-6 contents of, defining, 6-4
creating, 2-5, 6-4
default release specification, 6-10 determining the name of, 6-3 editing, 5-2, 6-4, 6-11 limit clause, 6-13 program specification, 6-8 release identifier, 6-5 release specification, 6-4 resource specification, 6-11 samples of, 6-16
software location and, 6-6 syntax for, 6-4
user specification, 6-7
SQL schema, getting in Relational Design Center, 4-36
SQL statements, using in DMQUERY utility, 8-1
SQL views
SQL-capable data sources, 5-4 SQLColumns command, 3-10 SQLForeignKeys command, 3-10 SQLPrimaryKeys command, 3-10 SQLStatistics command, 3-10 SQLVIEW command, 5-4, 7-6 starting
Query Design Center, 3-1 Relational Design Center, 4-2 SQL Query Processor server, 5-5 statistics, retrieving, 3-10
status of SQL Query Processor server, 5-10 stopping the SQL Query Processor
server, 5-5
Structured Query Language (SQL) data construct, 4-26
data item defaults, 4-23 databases, 5-4
default modeling of Enterprise Database Server data item types (table), 4-23 default names, 4-9
disjoint data set defaults, 4-10 embedded data set defaults, 4-14 enabling access for, 7-5
example
embedded table, 4-17 embedded table for DASDL
duplicates, 4-19
mapping of DASDL duplicates, 4-19 mapping of DASDL embedded data
sets, 4-17
mapping of DASDL occurring items, 4-17
modeling of variable-format data sets, 4-10, 4-11
occurring items, 4-14 occurring table, 4-17 occurring table for DASDL
duplicates, 4-19 variable-format table, 4-13 global data defaults, 4-10 grants, 4-29
group defaults, 4-25 initial values, 4-22 link defaults, 4-25
maintenance options for occurrence indexes, 4-16
modeling ALPHA data items, 4-24 naming conflicts, resolving, 4-9 naming rules, 4-9
referential integrity constraints, 4-25 restart data set defaults, 4-25 set and access defaults, 4-23 subset defaults, 4-23
tables
modeled from disjoint data sets, 4-10 modeled from embedded data
sets, 4-14
modeled from occurring items, 4-22 modeling, 4-16 viewing schema, 7-3 views, 4-29 subsets defaults, 4-23 not modeled in SQL, 4-23 SYSTEM/DMSQL/WORKER task, 5-4 SYSTEM/SIM/CONFIG library
determining the name of the SQL Query Processor configuration file, 6-3
T
table properties, Catalog window, 3-7 tables, modeled in SQL, 4-16
from disjoint data sets, 4-10 from embedded data sets, 4-14 from occurring items, 4-14 TCP/IP
distributed systems services (DSS), configuring, 2-8
IP address of worker, 5-10 port number, 5-8
syntax, 2-6
terminating the SQL Query Processor server, 5-6
terminology conventions, 1-1 text pane
Analyze Query window, 3-11 Design Query window, 3-22 TIMEOUT specification, 5-7
timeout specification, TCPIP syntax, 2-6 title of the SQL Query Processor
configuration file, determining, 6-3 TRACE command, 5-14 trace file closing, 5-14 creating, 5-13 trace information diagnostic, 5-13 enabling, 5-13 viewing, 5-13 tree view Catalog window, 3-6
Relational Design Center, 4-3 troubleshooting, B-1
troubleshooting SQL Query Processor server, 2-16
listing server status, 2-21 verifying
configuration file contents, 2-19 configuration file location, 2-18 distributed systems services (DSS)
information, 2-20 release identifiers, 2-16
SCode compiler system library, 2-17 server code file, 2-19
server provider, 2-20
SL configuration system library, 2-16 SQL driver system library, 2-18 TPC/IP endpoint, 2-21
U
uninstalling SQL Query Processor in the MCP environment, 2-13 in the Windows environment, 2-15 unordered list
physical organization sets mapped in SQL, 4-23
subsets, not modeled in SQL, 4-23 updating
Enterprise Database Server data sets with SQL queries, 2-22
Enterprise Database Server database, 2-12 Enterprise Database Server databases with
SQL queries, 2-22 SQL database definition, 2-12 USAGE KANJI, modeled in
SQL, 4-24
user assistance view, Relational Design Center, 4-6
user specification, 6-4, 6-7 usercode, 5-10
usercode conventions, starting Query Design Center, 3-2
V
value
BLOCKEDTIMEOUT, 5-8 DIALOGCHECKINTERVAL, 5-8
variable-format data sets mapping in SQL, 4-10
SQL example of mapping, 4-10, 4-11 variable-format item properties, Relational
Design Center, 4-6 variable-format table
deleting rows, 4-13 example, 4-13 verifying
contents of the configuration File, 2-19 distributed systems services (DSS)
information, 2-20
existence of SQL Query Processor configuration file, 2-18 release identifiers, 2-16
SCode compiler system library, 2-17 server code file, 2-19
server provider, 2-20
SQL driver system library, 2-18 SQL Query Processor configuration
system library, 2-16 TCP/IP endpoint, 2-21 viewing
column results in Query Design Center, 3-10
log information, 5-11
results of generating an SQL description, 7-8
table results in Query Design Center, 3-9 views, 4-29
views and grants, 4-28
W
WFL job, 7-8
what’s new in guide, 1-2 Windows environment
hardware requirements, 2-2
installing from ClearPath MCP server, 2-11 installing SQL Query Processor, 2-11 reinstalling SQL Query Processor, 2-15 removing SQL Query Processor, 2-15 setting up Kerberos authentication, A-1 software requirements, 2-3
uninstalling SQL Query Processor, 2-15 Work Flow Language (WFL)
job, using, 7-8 MODIFY command, 5-7 worker identifier, 5-10 IP address, 5-10 mix number, 5-10 usercode, 5-10 working with
databases, Relational Design Center, 4-34 schemas, Relational Design Center, 4-39 servers, Relational Design Center, 4-30
© 2010 Unisys Corporation. All rights reserved.