SESAM/SQL-Server V3.2A Database Operation

SESAM/SQL-Server V3.2A Database Operation
1 Preface
The functions and architectural features of the SESAM/SQL-Server database system meet
all the demands placed on a powerful database server in today's world. These characteristics are reflected in its name: SESAM/SQL-Server.
SESAM/SQL-Server is available in a standard edition for single-task operation and in an
enterprise edition for multitask operation.
For the sake of simplicity, we shall use the name SESAM/SQL throughout this manual to
refer to SESAM/SQL-Server.
1.1 Brief product description
SESAM/SQL is the relational database server for BS2000/OSD systems. SESAM/SQL
combines the advantages of the relational data model with all the characteristics expected
of a system which is subject to high loads in productive operation. On the one hand, this
offers simple operation and data which is independent of the physical storage method used
and, on the other, it means that the system is suitable for high transaction rates and large
volumes of data and possesses outstanding security and availability characteristics.
The SQL interface implemented in SESAM/SQL has been based across the board on the
ISO/IEC 9075:1992 standard. This standardized SQL interface means that SESAM/SQL
allows you to create portable, future-proof database applications which can be transferred
to different database systems and operating systems.
SESAM/SQL fulfils all the demands placed on a modern database system in today's world:
●
SESAM/SQL uses SQL, a uniform language and a consistent set of terms for defining,
structuring and maintaining a relational database and for creating application programs.
●
SESAM/SQL runs on all BS2000/OSD systems and can be used as a powerful SQL
server for clients of BS2000/OSD, Reliant UNIX, Solaris, Linux and MS Windows.
●
SESAM/SQL excels in terms of high availability, security and data integrity.
●
SESAM/SQL supports modern parallel processing techniques for multi-user operation
and multi-database processing.
U22418-J-Z125-6-76
1
Target group
Preface
●
The Universal Transaction Monitor openUTM and the SESAM/SQL database system
together form a powerful DB/DC system including fully coordinated transaction
processing and restart facilities for online applications.
●
The product SESAM/SQL-DCN allows transparent, efficient and trusted access to
distributed databases in BS2000/OSD networks.
●
The release unit SESAM-DBAccess (JDBC) included in SESAM/SQL and known as
SESDBA for short permits access to SESAM/SQL databases from Java programs or
Java applets, regardless of platform.
●
A large range of add-on products considerably increases the range of application of
SESAM/SQL. These products range from database design tools, programming
languages and third and fourth generation software development environments through
to easy-to-use products for database end users and the use of SESAM/SQL in World
Wide Web applications.
1.2 Target group
This manual describes the means that can be used to control and monitor database
operation. It is therefore aimed at system administrators responsible for starting and terminating database operation and for overseeing the current session. It is also aimed at
programmers who create SESAM/SQL applications with the linked-in version of the Data
Base Handler (DBH).
Users should know the basic principles, concepts and interrelationships of the SESAM/SQL
database system, as described in the “Core Manual”. In particular, they should be familiar
with the contents of the chapter entitled “Database operation” in this manual. Knowledge of
the fundamentals of the BS2000 operating system and the Universal Transaction Monitor,
openUTM, is also advantageous.
2
U22418-J-Z125-6-76
Preface
Summary of the contents of the manuals
1.3 Summary of the contents of the manuals
The documentation for the SESAM/SQL database system can be found in the following
manuals:
●
Core Manual
●
SQL Reference Manual, Part 1: SQL statements
●
SQL Reference Manual, Part 2: Utilities
●
CALL DML Applications V3.0A
●
Database Operation
●
Utility Monitor
●
Messages
●
Glossary
The following additional documentation is also available:
●
Migrating SESAM Databases and Applications to SESAM/SQL-Server
●
Performance
The following manual describes how to create ESQL-COBOL programs:
●
ESQL-COBOL User Guide
The following manuals describe remote access with SESAM-DBAccess:
●
SESAM-DBAccess (JDBC) V3.1A
If you are searching for information on a specific topic, you can use the table of contents,
the index or the running headers. References to other documents are given in abbreviated
form in the text. The complete title of the document referenced is included under “Related
Publications” at the back of the manual.
U22418-J-Z125-6-76
3
Summary of the contents of the manuals
Preface
1.3.1 Summary of the contents of this manual
This manual covers the following topics:
●
starting and terminating the Data Base Handler (DBH)
●
the DBH start statements and options, by means of which you parameterize the DBH
when starting the session
●
starting, parameterizing and terminating the SESDCN distribution component
●
the options available for administering the DBH and the SESDCN distribution
component during the session
●
the utilities available for database operation
●
error recovery
Where the linked-in DBH differs from the independent DBH, the differences are described
at the appropriate points in the text.
In addition to the parts describing database operation, the manual also contains important
alphabetically arranged reference sections:
chapter 3 contains all the DBH start statements and options,
chapter 4 contains all the SESDCN control statements,
and chapter 5 contains all the administration statements for the DBH and SESDCN.
All the SESAM/SQL messages, including those that concern database operation, are
described in the “Messages” manual.
4
U22418-J-Z125-6-76
Preface
Summary of the contents of the manuals
1.3.2 Guide to the SESAM/SQL manuals
Core Manual
This manual provides an overview of the database system and describes basic principles,
concepts and interrelationships. It provides the basis for understanding all the other
SESAM/SQL manuals.
SQL Reference Manual,
Part 1: SQL Statements and Part 2: Utilities
The “SQL Reference Manual, Part 1” deals with the embedding of programs and describes
the syntax and semantics of the SQL language constructs in alphabetical order.
The utility statements are not included in this alphabetical list and are dealt with separately
in the “SQL Reference Manual, Part 2: Utilities”.
Both simple and complex examples are used to clarify the functions of the SQL language
constructs.
The “ESQL-COBOL User Guide” explains how to create ESQL-COBOL programs.
CALL DML Applications
This manual is aimed at CALL DML programmers and describes the language elements
used in the CALL DML interface and explains how to create CALL DML programs.
Database Operation
This manual is aimed at the system administrator and covers database operation. It
includes details on starting and terminating the DBH and SESDCN and the associated load
options and administration statements. The manual also describes the utilities required for
database operation.
Utility Monitor
This manual describes how to use the utility monitor and the functions it provides. The utility
monitor is a component part of SESAM/SQL and provides a menu-driven interface for
creating, loading, backing up and reconstructing a database using SQL statements. The
utility monitor also provides simple methods of querying the metadata.
U22418-J-Z125-6-76
5
README file
Preface
Messages
The message manual contains information relating to the structure and invocation of
messages for the SESAM/SQL server database system and the distribution component
SESAM/SQL-DCN. The SQLSTATEs and CALL-DML status messages are listed in full
here.
Glossary
This manual contains the glossary for all the SESAM/SQL manuals.
Migrating SESAM Databases and Applications to SESAM/SQL-Server
This manual gives an overview of the underlying concepts and functions contained in
SESAM/SQL-Server V2 and higher compared to those employed in predecessor versions
SESAM-SQL V1.X. The manual focuses on migrating data stocks and applications to the
current version of SESAM/SQL-Server.
Performance
This manual is aimed at experienced SESAM/SQL users. It describes how users can
identify performance bottlenecks and indicates which parameters can be used to influence
system performance.
1.4 README file
Information on any functional changes and additions to the current product version
described in this manual can be found in the product-specific README file.
You will find the README file under the name SYSRME.SESAM-SQL.032.E.
The user ID under which the README file is located can be obtained from your systems
support staff. With IMON you can also find out the file name using the following command:
/SHOW-INSTALLATION-PATH INSTALLATION-UNIT=SESAM-SQL,LOGICAL-ID=SYSRME.E
You can view the README file with the /SHOW-FILE command or in an editor, and print it on
a standard printer using the following command:
/PRINT-DOCUMENT $<userid>.SYSRME.SESAM-SQL.032.E,
LINE-SPACING=*BY-EBCDIC-CONTROL
6
U22418-J-Z125-6-76
Preface
Changes in V3.2 made since V3.1
1.5 Changes in V3.2 made since V3.1
A list of the most important changes made in SESAM/SQL-Server V3.2 compared with V3.1
is contained in table 1. The table also shows the manual and chapter/section in which you
will find a description of each change. If a topic is described in more than one manual, the
one which contains a complete description is listed first. The entries in the “Manual” column
have the following meanings:
Core
Core manual
RM P1
Reference Manual, Part 1
RM P2
Reference Manual, Part 2
DBO
Database Operation
Perform
Performance
Utilmon Utility Monitor
Topic
Manual
Section
RM P1
Perform
Sec.8.2.2
Sec.3.1.3
Core
Sec.4.1.4
Sec.4.3.14
Sec.7.2
Sec.6.1.1
Extensions to SESAM-SQL-Server V3.1B
–
–
New CLI function SQL_BLOB_OBJ_CLONE
Pragma IGNORE/USE INDEX extended
SQL language description
–
–
The INSERT statement has been extended so that multiple value
lines can now be specified with a single statement
The CREATE VIEW statement can be used to create constant
tables with literals
RM P1
Perform
New CLI function SQL_DIAG_SEQ_GET for outputting the primary key Core
values assigned by SESAM/SQL
RM P1
Sec.4.6.5
Sec.8.2
A lexicographical comparison of rows in the predicates is possible.
Core
RM P1
Sec.4.3.9
Sec.5.3.1
New Pragma LIMIT ABORT_EXECUTION for request-specific setting of RM P1
the DBH option ABORT-EXECUTION value
Sec.3.3.4
Utility functions
Utility function CHECK FORMAL:
– Now includes checking for replication
– Improved space checking
RM P2
Utilmon
Sec.3.2
Sec.3.3
Sec.5.4
Utility function COPY:
– Backup of data on additional mirror units using the
“HSMS Concurrent Copy with additional mirror units” method;
new BY-ADD-MIRROR-UNIT parameter for COPY
– The SESAM online backup with HSMS uses the
“HSMS Concurrent Copy with work file” method
Core
RM P2
Sec.9.6.2
Sec.2.5
Sec.3.2
Sec.2.4
Sec.5.4
Sec.8.2
Table 1: Changes in V3.2 made since V3.1
U22418-J-Z125-6-76
Utilmon
Perform
(part 1 of 4)
7
Changes in V3.2 made since V3.1
Preface
Topic
Manual
Section
Utility function LOAD:
– The option ONLINE/OFFLINE enables highly efficient control of
data loading to tables.
Core
Sec.7.5.4
Sec.9.3.1
Sec.3.2
Sec.5.4
Sec.8.1
Utility function RECOVER:
– RECOVER of user spaces and of the catalog space is also possible
using a replication.
– RECOVER from a foreign copy is now also available for space lists
– RECOVER SPACE USING ... TO TIMESTAMP can be used to reset
a user space to the specified mark of an earlier backup copy
– SCOPE PENDING can now also be specified when repairing
spaces
– In RECOVER CATALOG, the options SCOPE PENDING and
GENERATE INDEX ON NO LOG INDEX SPACE can be specified at
the same time
– In RECOVER, resetting to old catalog backups is possible
(from SESAM/SQL V2.0 onwards)
– Multiple RECOVER statements can run in parallel thus shortening
RECOVER runs
Core
RM P2
Utilmon
Perform
RM P2
Utilmon
Perform
Sec.5.2.1
Sec.7.5.6
Sec.9.6.2
Sec.9.8.3
Sec.9.8.5
Sec.3.2
Sec.5.4
Sec.8.3
Utility functions REFRESH REPLICATION and REFRESH SPACE:
Core
– REFRESH REPLICATION enables updating a replication subset of
spaces from the logging files
RM P2
– REFRESH SPACE enables spaces to be added to a replication
Utilmon
Sec.7.6.3
Sec.9.7.2
Sec.3.2
Sec.5.4
Utility function REORG:
Core
– Defines if the reorganized work file is to be copied back to the space RM P2
or renamed (option COPY/RENAME)
Utilmon
– Releases spare storage space (option MINIMIZE)
Sec.9.6.1
Sec.3.2
Sec.5.4
Utility function UNLOAD:
– Improved use of output files
RM P2
Sec.3.2
Core
DBO
Sec.9.8.1
Sec.5.2.3
Administration statements
Administration statement PREPARE-FOREIGN-COPY:
– Special input for spaces to be closed
– Activating logging
New administration statement SET-SAT-SUPPORT
Co-ownership
Use of co-ownership to create files and job variables for a user ID which Core
is not the DBH user ID (SECOS function co-ownership protection). A list
of the relevant statements and functions is given in the “Core manual”. RM P1
RM P2
DBO
Table 1: Changes in V3.2 made since V3.1
8
Sec.7.5.1
Sec.8.5.4
Sec.7.2
Sec.3.2
Sec.5.2.3
(part 2 of 4)
U22418-J-Z125-6-76
Preface
Changes in V3.2 made since V3.1
Topic
Manual
Section
Core
DBO
Sec.2.4
Sec.5.1.3
Sec.7.2.1
Sec.3
Sec.6
removed
WebTA access for SESAM/SQL
–
–
Access to SESADM, SESMON and utility monitor via a unified
access from the World Wide Web with the aid of the software
product WebTransactions (WebTA)
SDF-DOORS and FHS-DOORS access removed
Utilmon
Output via SNMP to a management platform
New SESAM-MON subagent for outputting SESMON performance
monitor data
Core
DBO
Sec.2.10
Sec.8.9.5
Sec.7.2
Sec.7.7
Security
–
–
–
–
Logging of security-relevant events with SAT
Extension of DBH option SECURITY
New administration statement SET-SAT-SUPPORT
Structure of the SAT log records
Core
DBO
Sec.2.4
Sec.6.6
Sec.3.2.2
Sec.5.2.3
Sec.9.5
Message length
–
–
Message length has been extended to 64000 bytes in the DCAMand UTM-specific connection modules
Modification of the CAPACITY mask in SESMON
Core
DBO
Perform
Sec.8.2.2
Sec.10.1.5
Sec.4.4
Sec.7.4
Sec.3.3.1
Sec.6.1.1
Logging set in request logging
–
–
–
Control of the logging set via the administration statement
SET-TUNING-TRACE, operand PROTOCOL=*STD/*LONG
SESCOSP output dependent on PROTOCOL operands
Printable output of in-descriptors and output in SESCOSP
DBO
Sec.5.2.3
Sec.6.3.2
Output configuration file
F6 function key to display the configuration file in utility monitor
Utilmon
Sec.3.2.3
Sec.4.1.3
DBO
Utilmon
Sec.2.5.2
Sec.3.6
Sec.3.9
Job variables
–
–
Monitor job variables for DBH job monitoring
New job variable #SESAM.SESUTI.JV for the utility monitor
Table 1: Changes in V3.2 made since V3.1
U22418-J-Z125-6-76
(part 3 of 4)
9
Notational conventions
Topic
Preface
Manual
Section
Core
Utilmon
Sec.8.5.2
Sec.3.2.2
DBO
Sec.8.5.3
Core
Perform
Sec.9.9
Sec.5.12.4
DBO
Sec.10.1.2
Core
Sec.8.3
Core
Sec.3
Comment lines
Comment lines in configuration files
Error handling
DB-DIAGAREA of openUTM supplied by SESAM/SQL
Reorganization with SPACEOPT
Notes about disk reorganization with SPACEOPT
SESAM/SQL and UTM
Extension of KDCDEF statement DATABASE
SESAM/SQL and virtual hosts
Notes about communication with virtual hosts
Demonstration database
The demonstration database has been updated to the latest version.
New statement file INSTR.AUFTRAGKUNDEN.032 in the library
SIPANY.SESAM-SQL.032.MAN-DB with
– INSERT statement with multiple value lines
– LOAD ONLINE application
– REFRESH REPLICATION / REFRESH SPACE application
Table 1: Changes in V3.2 made since V3.1
(part 4 of 4)
1.6 Notational conventions
Different sets of notational conventions are used in this manual:
10
●
conventions for emphasizing parts of the main text of the manual, and conventions for
describing the syntax of commands and statements that are not in SDF format, both of
which are referred to here as non-SDF notational conventions
●
SDF notational conventions for describing the syntax of commands and statements in
SDF format
U22418-J-Z125-6-76
Preface
Notational conventions
1.6.1 Non-SDF notational conventions
This manual uses the following notational conventions:
Syntax definitions. Continuation lines within syntax definitions are
intended.
UPPERCASE
Keywords
underscored
Default values
bold
Used for emphasis in running text. Text to be entered in examples.
italics
Variables in syntax definitions and running text.
Fixed-space font Program text in examples.
Text to be entered in examples of statement sequences.
[]
Optional specifications in syntax definitions.
The brackets are metacharacters and must not be entered in the
statement.
{||}
Alternative specifications in syntax definitions.
The available operands are separated by a horizontal bar.
()
Mandatory specifications in syntax definitions. Parentheses enclose
the operand and form part of it. They must be entered in the
statement.
variable : : =
Introduces a definition of the variables occurring in the preceding
syntax definition.
...
or
.
.
In syntax definitions, an ellipsis means that you can repeat the
preceding specification any number of times. In examples, the ellipsis
means that the rest of the statement is of no significance to the
example.
The ellipsis is a metacharacter and must not be entered in a
statement.
i
Indicates notes that are of particular importance.
!
Indicates warnings.
U22418-J-Z125-6-76
11
Notational conventions
Preface
1.6.2 SDF syntax representation
The example below gives the representation of the syntax of a command in a manual. The
command format consists of a field with the command name. All operands with their
permitted values are then listed. Operand values which introduce structures and the
operands dependent on these operand values are listed separately.
HELP-SDF
Alias: HPSDF
GUIDANCE-MODE = *NO / *YES
,SDF-COMMANDS = *NO / *YES
,ABBREVIATION-RULES = *NO / *YES
,GUIDED-DIALOG = *YES (...)
*YES(...)




SCREEN-STEPS = *NO / *YES
,SPECIAL-FUNCTIONS = *NO / *YES
,FUNCTION-KEYS = *NO / *YES
,NEXT-FIELD = *NO / *YES
,UNGUIDED-DIALOG = *YES (...) / *NO
*YES(...)



SPECIAL-FUNCTIONS = *NO / *YES
,FUNCTION-KEYS = *NO / *YES
This syntax description is valid for SDF version 4.5A. The syntax of the SDF
command/statement language is explained in the following three tables.
Table 2: Metasyntax
The meanings of the special characters and the notation used to describe command and
statement formats are explained in table 2.
Table 3: Data types
Variable operand values are represented in SDF by data types. Each data type represents
a specific set of values. The number of data types is limited to the data types described in
table 3.
The description of the data types is valid for the entire set of commands/statements.
Therefore only deviations (if any) from the attributes described here are explained in the
relevant operand descriptions.
12
U22418-J-Z125-6-76
Preface
Notational conventions
Table 4: Suffixes for data types
Data type suffixes define additional rules for data type input. The suffixes contain a length
or interval specification, limit the set of values (suffix begins with without), extend the set of
values (suffix begins with with) or explain a certain specification regarding a mandatory
input (suffix begins with mandatory). The following short forms are used in this manual for
data type suffixes:
cat-id
completion
construction
correction-state
generation
lower-case
manual-release
odd-possible
path-completion
separators
temporary-file
underscore
user-id
version
wildcard-constr
wildcards
cat
compl
constr
corr
gen
low
man
odd
path-compl
sep
temp-file
under
user
vers
wild-constr
wild
The description of the 'integer' data type in table 4 contains a number of items in italics. The
italicized items are not part of the syntax and are only used to make the table easier to read.
table 4 contains items in italics (see the special suffix) that are not part of the syntax for
special data types that are checked by the implementation.
The description of the data type suffixes is valid for the entire set of commands and statements. Therefore only deviations (if any) from the attributes described here are explained
in the relevant operand descriptions.
U22418-J-Z125-6-76
13
Notational conventions
Preface
Metasyntax
Representation
Meaning
Examples
UPPERCASE
Uppercase letters denote keywords
(command names, statement
names, operand names, keywords)
and constant operands. Keywords
begin with *
HELP-SDF
Uppercase letters printed in
boldface denote guaranteed or
suggested abbreviations of
keywords.
GUIDANCE-MODE = *YES
=
The equals sign connects an
operand name with the associated
operand values.
GUIDANCE-MODE = *NO
< >
Angle brackets denote variables
whose range of values is described
by data types and suffixes (see
Tables 3 and 4).
SYNTAX-FILE = <filename 1..54>
Underscoring
Underscoring denotes the default
value of an operand.
GUIDANCE-MODE = *NO
/
A slash serves to separate
alternative operand values.
NEXT-FIELD = *NO / *YES
(…)
Parentheses denote operand
values that initiate a structure.
,UNGUIDED-DIALOG = *YES (...) / *NO
[ ]
Square brackets denote operand
values which introduce a structure
and are optional. The subsequent
structure can be specified without
the initiating operand value.
SELECT = [*BY-ATTRIBUTES](...)
LETTERS
UPPERCASE
LETTERS
in boldface
Table 2: Metasyntax
14
SCREEN-STEPS = *NO
(part 1 of 2)
U22418-J-Z125-6-76
Preface
Notational conventions
Representation
Meaning
Examples
Indentation
Indentation indicates that the
operand is dependent on a higherranking operand.
,GUIDED-DIALOG = *YES (...)


,
list(n):
Alias:
Table 2: Metasyntax
U22418-J-Z125-6-76
A vertical bar identifies related
operands within a structure. Its
length marks the beginning and
end of a structure. A structure may
contain further structures. The
number of vertical bars preceding
an operand corresponds to the
depth of the structure.
A comma precedes further
operands at the same structure
level.
The entry “list” signifies that a list of
operand values can be given at this
point. If (n) is present, it means that
the list must not have more than n
elements. A list of more than one
element must be enclosed in
parentheses.
The name following this is
guaranteed to be an alias of the
command or statement name.
*YES(...)


SCREEN-STEPS = *NO /
*YES
SUPPORT = *TAPE(...)
*TAPE(...)





VOLUME = *ANY(...)
*ANY(...)

...
GUIDANCE-MODE = *NO / *YES
,SDF-COMMANDS = *NO / *YES
list-poss: *SAM / *ISAM
list-poss(40): <structured-name 1..30>
list-poss(256): *OMF / *SYSLST(...) /
<filename 1..54>
HELP-SDF
Alias: HPSDF
(part 2 of 2)
15
Notational conventions
Preface
Data types
Data type
Character set
Special rules
alphanum-name A…Z
0…9
$, #, @
cat-id
A…Z
0…9
command-rest
freely selectable
Not more than 4 characters and must mot begin
with the string “PUB”.
composed-name A…Z
0…9
$, #, @
hyphen
period
catalog ID
Alphanumeric string that can be split into
multiple substrings by means of a period or
hyphen.
If it is also possible to specify a file name, then
the string can also begin with a catalog ID in the
format: cat: (see the filename data type).
c-string
EBCDIC character
Must be enclosed within single quotes;
the letter C may be prefixed; any single quotes
occurring within the string must be entered
twice.
date
0…9
Structure identifier:
hyphen
Input format: yyyy-mm-dd
device
A…Z
0…9
hyphen
Character string, max. 8 characters in length,
corresponding to a device available in the
system. In interactive prompting, SDF displays
the valid operand values. For notes on possible
devices, see the relevant operand description.
fixed
+, 0…9
period
Input format: [sign][digits].[digits]
yyyy: year; optionally 2 or 4 digits
mm: month
dd: day
[sign]: + or [digits]: 0...9
must contain at least one digit, but may
contain up to 10 characters (0...9, period) apart
from the sign.
Table 3: Data types
16
(part 1 of 6)
U22418-J-Z125-6-76
Preface
Notational conventions
Data type
Character set
Special rules
filename
A…Z
0…9
$, #, @
hyphen
period
Input format:
file
file(no)
group
:cat:$user.
(*abs)
group (+rel)
(-rel)
:cat:
optional entry of the catalog identifier;
character set limited to A...Z and 0...9;
maximum of 4 characters; must be enclosed
in colons; default value is the catalog
identifier assigned to the user ID, as
specified in the user catalog.
$user.
optional entry of the user ID;
character set is A…Z, 0…9, $, #, @;
maximum of 8 characters; first character
cannot be a digit; $ and period are
mandatory;
default value is the user' s own ID.
$. (special case)
system default ID
file
file or job variable name;
can be separated by periods into several
subnames: name1[.name2[...]]
namei cannot contain a period and must not
begin or end with a hyphen;
file is a maximum of 41 characters long,
must not begin with $ and must include at
least one character from the range A...Z.
Table 3: Data types
U22418-J-Z125-6-76
(part 2 of 6)
17
Notational conventions
Data type
Preface
Character set
filename
(continued)
Special rules
#file
(special case)
@file (special case)
# or @ used as the first character indicates
temporary files or job variables, depending
on system generation.
file(no)
tape file name
no: version number;
character set is A...Z, 0...9, $, #, @.
Parentheses must be specified.
group
name of a file generation group
(character set: as for “file”)
(*abs)
group (+rel)
(-rel)
(*abs)
absolute generation number (1-9999);
* and parentheses must be specified.
(+rel)
(-rel)
relative generation number (0-99);
sign and parentheses must be specified.
integer
0…9, +, -
+ or -, if specified, must be the first character.
name
A…Z
0…9
$, #, @
Must not begin with 0...9.
Table 3: Data types
18
(part 3 of 6)
U22418-J-Z125-6-76
Preface
Notational conventions
Data type
Character set
Special rules
partial-filename
A…Z
0…9
$, #, @
hyphen
period
Input format: [:cat:][$user.][partname.]
:cat: see full-filename
$user. see full-filename
partname
optional entry of the initial part of a name
common to a number of files or file
generation groups in the form:
name1.[name2.[...]]
namei see filename.
The final character of “partname” must be a
period.
At least one of the parts: cat:, $user. or
partname must be specified.
posix-filename
A...Z
0...9
special characters
posix-pathname A...Z
0...9
special characters
structure characters:
slash
Table 3: Data types
U22418-J-Z125-6-76
String that is a maximum of 255 characters long.
Consists of one or two periods or of alphanumeric characters and special characters.
Special characters are to be escaped using the
'\ ' character. The '/' character is not allowed.
Must be enclosed in single quotes when alternative data types are permitted, separators are
used or the first character is ?, ! or ^.
Case-sensitive.
Input format: [/]part1[/.../partn]
where parti is a posix-filename,
maximum of 1023 characters.
Must be enclosed in single quotes when alternative data types are permitted, separators are
used or the first character is ?, ! or ^.
(part 4 of 6)
19
Notational conventions
Preface
Data type
Character set
Special rules
product-version
A...Z
0...9
period
single quote
Input format:
[[C]' ][V][m]m.naso[' ]
correction status
release status
where m, n, s and o are digits and a is a letter.
Whether or not the release and correction status
must or may be specified is determined by the
suffix of the data type (see the suffixes withoutcorr, without-man, mandatory-man and
mandatory-corr in table 4).
product-version can be enclosed within single
quotes where the letter C can be prefixed. The
specification of the version may begin with the
letter V.
structured-name A...Z
0...9
$, #, @
hyphen
Alphanumeric string which may comprise a
number of substrings separated by a hyphen.
First character: A...Z or $, #, @
text
freely selectable
For the input format, see the relevant operand
descriptions.
time
0...9
structure identifier:
colon
Time-of-day entry:
hh:mm:ss
Input format:
hh:mm
hh
hh:hours
Leading zeros may be
mm:minutes
omitted
ss:seconds
vsn
a) A…Z
0…9
a) Input format: pvsid.sequence-no
max. 6 characters
pvsid:
2-4 characters; PUB must
not be entered
sequence-no: 1-3 characters
b) A…Z
0…9
$, #, @
b) Max. 6 characters;
PUB may be prefixed, but must not be
followed by $, #, @.
Table 3: Data types
20
(part 5 of 6)
U22418-J-Z125-6-76
Preface
Notational conventions
Data type
Character set
Special rules
x-string
Hexadecimal:
00…FF
Must be enclosed in single quotes; must be
prefixed by the letter X.
There may be an odd number of characters.
x-text
Hexadecimal:
00…FF
Must not be enclosed in single quotes;
the letter X must not be prefixed.
There may be an odd number of characters.
Table 3: Data types
U22418-J-Z125-6-76
(part 6 of 6)
21
Notational conventions
Preface
Suffixes for data types
Suffix
Meaning
x..y unit
With data type “integer”: interval specification
x..y special
x
minimum value permitted for “integer”. x is an (optionally signed)
integer.
y
maximum value permitted for “integer”. y is an (optionally signed)
integer.
unit
with “integer” only: additional units. The following units may be
specified:
days
byte
hours
2Kbyte
minutes
4Kbyte
seconds
Mbyte
milliseconds
With the other data types: length specification
For data types catid, date, device, product-version, time and vsn the length
specification is not displayed.
x
minimum length for the operand value; x is an integer.
y
maximum length for the operand value; y is an integer.
x=y
the length of the operand value must be precisely x.
special Specification of a suffix for describing a special data type that is
checked by the implementation. “special” can be preceded by other
suffixes. The following specifications are used:
arithm-expr
arithmetic expression (SDF-P)
bool-expr
logical expression (SDF-P)
string-expr
string expression (SDF-P)
expr
freely selectable expression (SDF-P)
cond-expr
conditional expression (JV)
symbol
CSECT or entry name (BLS)
with
Extends the specification options for a data type.
-compl
When specifying the data type “date”, SDF expands two-digit year specifictions in the form yy-mm-dd to:
20jj-mm-tt
if jj < 60
19jj-mm-tt
if jj Ï 60
-low
Uppercase and lowercase letters are differentiated.
-pathcompl
For specifications for the data type “filename”, SDF adds the catalog and/or
user ID if these have not been specified.
Table 4: Data type suffixes
22
(part 1 of 7)
U22418-J-Z125-6-76
Preface
Notational conventions
Suffix
Meaning
with (contd.)
-under
Permits underscores (_) for the data type “name”.
-wild(n)
Parts of names may be replaced by the following wildcards.
n denotes the maximum input length when using wildcards.
Due to the introduction of the data types posix-filename and posixpathname, SDF now accepts wildcards from the UNIX world (referred to
below as POSIX wildcards) in addition to the usual BS2000 wildcards.
However, as not all commands support POSIX wildcards, their use for data
types other than posix-filename and posix-pathname can lead to semantic
errors.
Only POSIX wildcards or only BS2000 wildcards should be used within a
search pattern. Only POSIX wildcards are allowed for the data types posixfilename and posix-pathname. If a pattern can be matched more than once
in a string, the first match is used.
BS2000
wildcards
Meaning
*
Replaces an arbitrary (even empty) character string. If the
string concerned starts with *, then the * must be entered twice
in succession if it is followed by other characters and if the
character string entered does not contain at least one other
wildcard.
TerminaPartially-qualified entry of a name.
ting period Corresponds implicitly to the string “./*”, i.e. at least one other
character follows the period.
/
Replaces any single character.
<sx:sy>
Replaces a string that meets the following conditions:
– It is at least as long as the shortest string (sx or sy)
– It is not longer than the longest string (sx or sy)
– It lies between sx and sy in the alphabetic collating
sequence; numbers are sorted after letters (A...Z, 0...9)
– sx can also be an empty string (which is in the first position
in the alphabetic collating sequence)
– sy can also be an empty string, which in this position stands
for the string with the highest possible code (contains only
the characters X'FF' )
<s1,…>
Replaces all strings that match any of the character combinations specified by s. s may also be an empty string. Any such
string may also be a range specification “sx:sy” (see above).
Table 4: Data type suffixes
U22418-J-Z125-6-76
(part 2 of 7)
23
Notational conventions
Suffix
Preface
Meaning
with-wild(n) -s
(contd.)
Replaces all strings that do not match the specified string s.
The minus sign may only appear at the beginning of string s.
Within the data types filename or partial-filename the negated
string -s can be used exactly once, i.e. -s can replace one of
the three name components: cat, user or file.
Wildcards are not permitted in generation and version specifications for file
names. Only system administration may use wildcards in user IDs.
Wildcards cannot be used to replace the delimiters in name components cat
(colon) and user ($ and period).
POSIX
wildcards
Meaning
*
Replaces any single string (including an empty string). An *
appearing at the first position must be duplicated if it is followed
by other characters and if the entered string does not include
at least one further wildcard.
?
Replaces any single character; not permitted as the first
character outside single quotes.
[cx-cy]
Replaces any single character from the range defined by cx
and cy, including the limits of the range. cx and cy must be
normal characters.
[s]
Replaces exactly one character from string s.
The expressions [cx-cy] and [s] can be combined into
[s1cx-cys2].
[!cx-cy]
Replaces exactly one character not in the range defined by cx
and cy, including the limits of the range. cx and cy must be
normal characters. The expressions [!cx-cy] and [!s] can be
combined into [!s1cx-cys2].
[!s]
Replaces exactly one character not contained in string s. The
expressions [!s] and [!cx-cy] can be combined into [!s1cx-cys2].
Table 4: Data type suffixes
24
(part 3 of 7)
U22418-J-Z125-6-76
Preface
Notational conventions
Suffix
Meaning
with (contd.)
wildconstr(n)
Specification of a constructor (string) that defines how new names are to be
constructed from a previously specified selector (i.e. a selection string with
wildcards). See also with-wild. n denotes the maximum input length when
using wildcards.
The constructor may consist of constant strings and patterns. A pattern
(character) is replaced by the string that was selected by the corresponding
pattern in the selector.
The following wildcards may be used in constructors:
Wildcard
Meaning
*
Corresponds to the string selected by the wildcard * in the
selector.
TerminaCorresponds to the partially-qualified specification of a name in
ting period the selector;
corresponds to the string selected by the terminating period in
the selector.
/ or ?
Corresponds to the character selected by the / or ? wildcard in
the selector.
<n>
Corresponds to the string selected by the n-th wildcard in the
selector, where n is an integer.
Allocation of wildcards to corresponding wildcards in the selector:
All wildcards in the selector are numbered from left to right in ascending
order (global index).
Identical wildcards in the selector are additionally numbered from left to right
in ascending order (wildcard-specific index).
Wildcards can be specified in the constructor by one of two mutually
exclusive methods:
1. Wildcards can be specified via the global index: <n>
2. The same wildcard may be specified as in the selector; substitution
occurs on the basis of the wildcard-specific index. For example:
the second “/” corresponds to the string selected by the second “/” in the
selector
Table 4: Data type suffixes
U22418-J-Z125-6-76
(part 4 of 7)
25
Notational conventions
Suffix
Preface
Meaning
with-wildThe following rules must be observed when specifying a constructor:
constr(n)
– The constructor can only contain wildcards of the selector.
(contd.)
– If the string selected by the wildcard <...> or [...] is to be used in the
constructor, the index notation must be selected.
–
The index notation must be selected if the string identified by a wildcard
in the selector is to be used more than once in the constructor. For
example: if the selector “A/” is specified, the constructor “A<n><n>” must
be specified instead of “A//”.
–
The wildcard * can also be an empty string. Note that if multiple asterisks
appear in sequence (even with further wildcards), only the last asterisk
can be a non-empty string, e.g. for “****” or “*//*”.
–
Valid names must be produced by the constructor. This must be taken
into account when specifying both the constructor and the selector.
–
Depending on the constructor, identical names may be constructed from
different names selected by the selector. For example:
“A/*” selects the names “A1” and “A2”; the constructor “B*” generates
the same new name “B” in both cases.
To prevent this from occurring, all wildcards of the selector should be
used at least once in the constructor.
–
If the constructor ends with a period, the selector must also end with a
period. The string selected by the period at the end of the selector
cannot be specified by the global index in the constructor specification.
Table 4: Data type suffixes
26
(part 5 of 7)
U22418-J-Z125-6-76
Preface
Notational conventions
Suffix
Meaning
with-wildExamples:
constr(n)
(contd.) Selector
A//*
Selection Constructor
New name
AB1
AB2
A.B.C
D<3><2>
D1
D2
D.CB
C.<A:C>/<D,F>
C.AAD
C.ABD
C.BAF
C.BBF
G.<1>.<3>.XY<2>
G.A.D.XYA
G.A.D.XYB
G.B.F.XYA
G.B.F.XYB
C.<A:C>/<D,F>
C.AAD
C.ABD
C.BAF
C.BBF
G.<1>.<2>.XY<2>
G.A.A.XYA
G.A.B.XYB
G.B.A.XYA
G.B.B.XYB
A//B
ACDB
ACEB
AC.B
A.CB
G/XY/
GCXYD
GCXYE
GCXY. 1
G.XYC
1
without
The period at the end of the name may violate naming conventions (e.g. for fully-qualified
file names).
Restricts the specification options for a data type.
-cat
Specification of a catalog ID is not permitted.
-corr
Input format: [[C]'][V][m]m.na[']
Specifications for the data type product-version must not include the
correction status.
-gen
Specification of a file generation or file generation group is not permitted.
-man
Input format: [[C]'][V][m]m.n[']
Specifications for the data type product-version must not include either
release or correction status.
-odd
The data type x-text permits only an even number of characters.
-sep
With the data type “text”, specification of the following separators is not
permitted: ; = ( ) < > Ë (i.e. semicolon, equals sign, left and right parentheses, greater than, less than, and blank).
-tempfile
Specification of a temporary file is not permitted (see #file or @file under
filename).
Table 4: Data type suffixes
U22418-J-Z125-6-76
(part 6 of 7)
27
Notational conventions
Suffix
Preface
Meaning
without
(contd.)
-user
Specification of a user ID is not permitted.
-vers
Specification of the version (see “file(no)”) is not permitted for tape files.
-wild
The file types posix-filename and posix-pathname must not contain a
pattern (character).
mandatory
Certain specifications are necessary for a data type.
-corr
Input format: [[C]'][V][m]m.naso[']
Specifications for the data type product-version must include the correction
status and therefore also the release status.
-man
Input format: [[C]'][V][m]m.na[so][']
Specifications for the data type product-version must include the release
status. Specification of the correction status is optional if this is not
prohibited by the use of the suffix without-corr.
-quotes
Specifications for the data types posix-filename and posix-pathname must
be enclosed in single quotes.
Table 4: Data type suffixes
28
(part 7 of 7)
U22418-J-Z125-6-76
2 Working with the SESAM/SQL DBH
The SESAM/SQL Data Base Handler (DBH) is the central component for the control,
execution and monitoring of database operation. The DBH:
●
analyzes the statements from the application programs, ascertains the best access
method in each case, and executes the statements
●
returns the results of database operations to the application program
●
monitors all database activities
●
controls the service tasks for utility functions
●
logs important information on database activities in DBH-specific log files
●
reports errors
User
task n
User
task 2
Service
task 1
Service
task 2
Service
task n
User
task 1
DBH
task 1
DBH
task 2
.......
DBH
task n
System administrator
terminal
Log files
Database
1
Database
2
Database
n
Figure 1: Tasks of the SESAM/SQL DBH
U22418-J-Z125-6-76
29
Working with the SESAM/SQL DBH
The “Core Manual” (see the chapter entitled “Database operation”) explains the fundamentals of the DBH, its functions and interfaces. You will also find an explanation in the
“Core Manual” of how the DBH supports the security concept of SESAM/SQL (see the
chapter entitled “Backup concept”).
This chapter covers the following topics:
30
●
start commands
●
starting the SESAM/SQL DBH and entering the start parameters
●
terminating the SESAM/SQL DBH
●
restarting the DBH
●
job variables
●
maximum values for working with the SESAM/SQL DBH
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting via start commands
2.1 Starting SESAM/SQL programs via start commands
All SESAM/SQL programs are started using SESAM start commands.
It is assumed that you have installed SESAM/SQL and CRTE (CRTE=Common Run Time
Environment) with IMON or you have stored the CRTE and SESAM libraries under the
standard filenames described on page 35.
i
For reasons of compatibility, the earlier command START-PROGRAM may also be
used. You can find information on this in the section “Starting SESAM programs with
/START-PROGRAM” on page 539.
With SESAM/SQL-Server you can use different correction delivery statuses in parallel. For
specific information on this, refer to page 36.
2.1.1 Overview of the start commands
The start commands for all the SESAM/SQL programs are defined in the SDF syntax file
shipped with the SESAM/SQL server. They are described in the respective descriptions for
starting the programs.
Start command and aliases
Program
START-SESAM-DBH
SESAM-DBH
START-SESAM
SESAM
SESAM
START-SESAM-DCN
SESAM-DCN
START-SESDCN
SESDCN
SESDCN distribution component
START-SESAM-ADMINISTRATION
SESAM-ADMINISTRATION
START-SESADM
SESADM
SESADM administration program
START-SESAM-PERF-MONITOR
SESAM-PERF-MONITOR
START-SESMON
SESMON
SESMON
Table 5: Start commands
U22418-J-Z125-6-76
(part 1 of 2)
31
Starting via start commands
Start command and aliases
Program
START-SESAM-TUNING-TRACE-EVAL
SESAM-TUNING-TRACE-EVAL
START-SESCOSP
SESCOSP
SESCOSP
START-SESAM-RETRIEVAL-DIALOGUE
SESAM-RETRIEVAL-DIALOGUE
START-SEDI61
SEDI61
SEDI61
START-SESAM-CDML-DIALOGUE
SESAM-CDML-DIALOGUE
START-SEDI63
SEDI63
SEDI63
START-SESAM-LOG-FILE-EVAL
SESAM-LOG-FILE-EVAL
START-SEDI70
SEDI70
SEDI70
START-SESAM-UTILITY-MONITOR
SESAM-UTILITY-MONITOR
START-SESUTI
SESUTI
SESUTI Utility Monitor
START-SESLK-UTILITY-MONITOR
SESLK-UTILITY-MONITOR
START-SESUTIL
SESUTIL
SESUTIL Utility Monitor
START-SESAM-CDML-AUTHORIZATION
SESAM-CDML-AUTHORIZATION
START-SEPA
SEPA
SEPA
START-SESLK-RETRIEVAL-DIALOGUE
SESLK-RETRIEVAL-DIALOGUE
START-SEDI61L
SEDI61L
SEDI61L
START-SESLK-CDML-DIALOGUE
SESLK-CDML-DIALOGUE
START-SEDI63L
SEDI63L
SEDI63L
Table 5: Start commands
32
Working with the SESAM/SQL DBH
(part 2 of 2)
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting via start commands
2.1.2 Operands of the start commands
The essential operands of the start commands are described below, using START-SESAMDBH as an example:
START-SESAM-DBH
VERSION = *STD / <product-version 6..10>
,MONJV = *NONE / <filename 1..54 without-gen-vers>
,CPU-LIMIT = *JOB-REST / <integer 1..32767>
,RESIDENT-PAGES = *PARAMETERS (...)
*PARAMETERS(...)



MINIMUM = *STD / <integer 0..32767 4Kbyte>
,MAXIMUM = *STD / <integer 0..32767 4Kbyte>
Operand description
VERSION =
Specifies the program version to be started.
VERSION = *STD
No explicit product version specification. The product version is selected as follows:
1. The version specified with the command SELECT-PRODUCT-VERSION.
2. The highest version of the program that was installed using IMON.
3. The highest version of the program that exists in the SESAM module library.
VERSION = <product-version 6..10>
Selected version in the form: ['] [V] [m] m.naso ['] (e.g. 3.2A20).
MONJV = *NONE / <filename 1..54 without-gen-vers>
Name of the JV that is to monitor the program.
The system then sets the JV to the appropriate values during the program run:
$R
$T
$A
Program is running
Program terminated normally
Program terminated abnormally
This operand is only available to users with the JV software product (see also the
“Job Variables” manual).
U22418-J-Z125-6-76
33
Starting via start commands
Working with the SESAM/SQL DBH
CPU-LIMIT = *JOB-REST / <integer 1..32767>
Maximum CPU- time in seconds that the program may utilize during its run.
This operand corresponds to the CPU-LIMIT operand of the START-PROGRAM command.
The time monitored depends on the operand RESOURCES=*PARAMETERS(CPULIMIT=...) in the SET-LOGON-PARAMETERS command.
If the job was started without a time limit specification (CPU-LIMIT=*NO), then the program
also runs without a time limit (the limit specified is ignored)!
CPU-LIMIT = *JOB-REST
Default setting:
Assigns the remaining CPU time available to the task to the program run as the maximum
CPU time.
CPU-LIMIT = <integer 1..32767>
Explicit specification of the CPU time in seconds.
RESIDENT-PAGES = *PARAMETERS(...)
Number of resident memory pages required for the program run, see section “Using
FASTPAM for SESAM/SQL” on page 537.
MINIMUM = *STD / <integer 0..32767 4Kbyte>
Minimum number of resident memory pages required.
MAXIMUM = *STD / <integer 0..32767 4Kbyte>
Maximum number of resident memory pages required.
2.1.3 Tasks of the start commands
The start commands have the following tasks:
–
to ascertain and assign the system files
–
to determine the operating mode
Ascertaining and assigning the system files
The start commands ascertain the system files required to start the program and assign the
files by means of corresponding link names.
The names of the required system files are ascertained using IMON on the basis of the
following algorithm:
–
SESAM/SQL searches for the files of the recent version.
–
CRTE searches for the most recent version.
If this is unsuccessful, the default names of the files are used (see next table).
34
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting via start commands
If you have stored the CRTE and SESAM/SQL libraries with the default names specified in
the table, you can also use the start commands without the need to install SESAM/SQL and
CRTE with IMON.
The following list shows the files affected and their default names:
File
Link name
Default name
CRTE library
BLSLIBxx
$.SYSLNK.CRTE for business servers
with /390 architecture and SR2000;
$.SPULNK.CRTE for business servers
with SPARC64 architecture
SESAM module library
SESAMOM
L
$.SYSLNK.SESAM-SQL.032 for business servers
with /390 architecture and SR2000;
$.SPULNK.SESAM-SQL.032 for business servers
with SPARC64 architecture
Procedure for CONNECTSESAM-CONFIGURATION
command
$.SYSSPR.SESAM-SQL.032.RUN-CFG
Procedure for the start
commands
$.SYSSPR.SESAM-SQL.032.RUN-STA
FHS format library for
SESMON
MAPLIB
$.SYSFHS-SESAM-SQL.032.MON.E
FHS format library for the
utility monitor
(German/English)
MAPLIB
$.SYSFHS-SESAM-SQL.032.UTI.D
MAPLIB
$.SYSFHS-SESAM-SQL.032.UTI.E
Help text file for the utility
monitor (German/English)
SEEHELP
$.SYSMAN-SESAM-SQL.032.UTI.D
SEEHELP
$.SYSMAN-SESAM-SQL.032.UTI.E
Table 6: Default names of the system files
The procedures for all commands are available in compiled form and can be run in a
BS2000/OSD environment that has SDF-P-BASYS V2.0B or higher installed.
i
U22418-J-Z125-6-76
The CONNECT-SESAM-CONFIGURATION command is contained in the SYSTEM
syntax file supplied (but not in the user syntax file supplied). This command is
executable if SESAM/SQL was installed with IMON or if the run procedure is stored
under the default name $.SYSSPR.SESAM-SQL.032.RUN-CFG.
The installation procedure SIPPRC.SESAM-SQL.XXX.INS-CFG is not supplied any
more as of SESAM/SQL V3.0.
35
Starting via start commands
Working with the SESAM/SQL DBH
Determination of the operating mode
The programs are started in the interactive mode when the started via the start commands.
If the user wants to run a program in the batch mode, then the user must call the start
command in an ENTER procedure.
2.1.4 Specifying the correction delivery status with the start command
The IMON installation monitor permits parallel administration of different correction
statuses of a software product on a single computer system. This means, you can also use
multiple SESAM/SQL versions in parallel.
Points to note when starting a SESAM/SQL program
When you start a SESAM/SQL program by means of the start commands, you can specify
the correction delivery status with which the program is started by means of the VERSION
parameter (see page 33). If you do not specify this at startup, the most recent version of the
LLM in the module library is loaded by default.
Points to note about the SESAM DBH in 24-hour operation
If a SESAM DBH is running in 24-hour operation, and if a new correction delivery status is
loaded into the SESAM module library during operation, the DBH continues to work with the
old correction status. When the DBH starts a new service task after the new correction
delivery status is loaded, this service task is started with the appropriate correction status
for the DBH.
If one or more subsystems of SESAM are loaded when a new correction delivery status is
loaded, the SESAM subsystems do not automatically load the new correction delivery
status. In this case, terminate all tasks associated with the SESAM subsystems, and use
the following command to terminate the subsystems themselves, as well:
/STOP-SUBSYSTEM SUBSYSTEM-NAME=<structured name 1..8>
You then have to start the SESAM subsystems again with the following command:
/START-SUBSYSTEM SUBSYSTEM-NAME=<structured name 1..8>
SESAM can then restart the tasks, and the tasks will load the new correction delivery status.
36
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting via start commands
Points to note when starting the performance monitor
If you want to start the SESAM performance monitor in this situation, note that it has to be
started with the correction status of the SESAM DBH. In other words, you have to specify
the correction status of the SESAM DBH to be monitored for the VERSION parameter of
the start command for the performance monitor (e.g. VERSION=3.2A00).
As a result, some DBHs in a configuration may be working with the new correction status
while others are still working with the old one. If you want all the DBHs in a configuration to
be monitored by the performance monitor in this situation, you have to start a separate
performance monitor for each correction status.
U22418-J-Z125-6-76
37
Starting the SESAM/SQL DBH
Working with the SESAM/SQL DBH
2.2 Starting the SESAM/SQL DBH
The SESAM/SQL DBH is a link and load module (LLM) called SESAM. When you start the
SESAM LLM using the START-SESAM-DBH command or the START-PROGRAM
command, this initializes the DBH session.
It makes it easier to use the SESAM/SQL Data Base Handler if you use IMON to install the
product. If you do not do this, the files specified in the table “Default names of the system
files” on page 35 must exist under the $TSOS user ID with the default names specified in
the table.
You parameterize the DBH at startup using DBH start statements and options.
i
The section “Specifying the correction delivery status with the start command” on
page 36 describes the points to note when starting the SESAM DBH with different
correction delivery statuses.
This section describes how to start the DBH and pass the start parameters. The syntax and
functions of the various start parameters are described in detail in a separate chapter (see
chapter “DBH start statements and options” on page 63).
The following topics are dealt with in this section:
–
startup requirements
–
starting the independent DBH
–
starting the linked-in DBH
–
starting multiple DBHs
–
SESAM/SQL share modules
i
38
The following always applies:
Output sent to SYSOUT and SYSLST is not upwardly compatible.
Output layout may vary depending on the version used.
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting the SESAM/SQL DBH
2.2.1 Startup requirements
Before starting the SESAM/SQL DBH with START-SESAM-DBH or START-PROGRAM, you
assign files to the DBH and specify options for it by means of the following commands:
[/MODIFY-MSG-FILE-ASSIGNMENT ADD-FILE=$TSOS.SYSMES.SESAM-SQL.032] —————
[/MODIFY-SDF-OPTIONSSYNTAX-FILE=USER (NAME=$TSOS.SYSSDF.SESAM-SQL.032.USER)] —————
[/MODIFY-TEST-OPTIONS DUMP=YES] ————————————————————————————————————————
[/ASSIGN-SYSDTA TO-FILE = *SYSCMD] ————————————————————————————————————
[/ADD-FILE-LINK LINK-NAME=SESAMCID,FILE-NAME=file] —————————————————————
(1)
(2)
(3)
(4)
(5)
(1)
To be able to use the SESAM/SQL messages, you need to activate the
SESAM/SQL message file if this file is not available system-wide.
(2)
SESAM/SQL uses the SDF (System Dialog Facility) dialog interface of BS2000 for
entering the DBH start statement and options, among other things. The
SESAM-SDF syntax file must therefore be contained in the system or group SDF
syntax file.
You must activate the SDF user syntax file and may need to change the settings for
the SDF options.
(3)
You use this command to output each memory dump and issue a corresponding
message to SYSOUT in order to obtain the diagnostic documentation required in
the event of a malfunction.
(4)
Assigns the SYSDTA system file to the SYSCMD procedure file.
This assignment is not necessary if you enter the DBH start statements and options
in an S procedure (structured SDF procedure, see the SDF-P manual
“Programming in the Command Language”).
(5)
You use this command to assign the DBH a CATID list by means of a link name. file
must have the access type SAM and can contain a maximum of 50 CATIDs (see
page 249). The CATID that you assign by means of the ADD-FILE-LINK command
becomes effective at startup of the DBH.
The SESAM/SQL DBH requests virtual address space when started. If there is not enough
virtual address space available, loading is aborted and a corresponding error message
appears. In this case, the BS2000 system administrator must increase the virtual address
space for the user ID. If this is not possible, then you can try to reduce the amount of
memory required by limiting the values of some DBH options (see the higher-order DBH
option STORAGE-SIZE).
The requirements for the DBH restart are described in the section “Restart requirements”
on page 54.
U22418-J-Z125-6-76
39
Starting the SESAM/SQL DBH
Working with the SESAM/SQL DBH
2.2.2 Starting the independent DBH
The independent DBH is implemented as a separate program system and runs in
BS2000/OSD with one or more DBH tasks. It is to be started in batch mode in order to avoid
interruptions.
It is not recommended to start the DBH using several tasks in the same dialog as not all
DBH tasks run in the same job class.
i
SESAM/SQL only established communication with the applications after all DBH
tasks are ready for operation. If this state is not achieved after a waiting period of
30 minutes, then the initialization is aborted with an appropriate error message. The
start task outputs a message every 5 minutes until this time.
The independent DBH attempts to reserve the TP task category. For this reason the TP
category should be authorized for the start user ID of the DBH as well as for the job class
in which the DBH is started.
2.2.2.1
Command sequence for starting the independent DBH in batch mode
You start the DBH as a batch job by means of the command
/ENTER-PROCEDURE NAME=filename.PROC-PAR=NO,LISTING=YES,LOGGING=YES
where filename is the name of an SDF-P procedure created by the user and in which the
user enters the command sequence for starting the DBH:
/START-SESAM-DBH ———————————————————————————————————————————————————————
[//start-parameters] ———————————————————————————————————————————————————
[//END] ———————————————————————————————————————————————————————————————
(1)
(2)
(3)
(1)
Starts the DBH using the special start command START-SESAM-DBH (see section
“Starting SESAM/SQL programs via start commands” on page 31).
(2)
You can enter the start parameters of the DBH here (see chapter “DBH start statements and options” on page 63). You do this when you do not want to accept the
default values and do not assign the start parameters via an input file (see page 42).
(3)
The last END statement concludes entry of the DBH start parameters. This
statement is necessary only if you do not enter the DBH start parameters via an
input file.
Before the actual start command in the start procedure you can assign files to the DBH and
change its options using the commands described on page 39. You will find an example of
a procedure on page 46.
40
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
2.2.2.2
Starting the SESAM/SQL DBH
Entering the DBH start parameters for the independent DBH
There are two ways to enter the DBH start parameters:
–
You can pass them in the sequence of commands for starting the DBH.
–
You can also pass them via an input file.
The parameters entered are logged to SYSLST. You can use the LOGGING parameter of
the MODIFY-SDF-OPTIONS statement to specify the extent of the logging to be carried out
(see the BS2000 manual “Commands, Volumes 1 - 5”). It is advisable to select
LOGGING=ACCEPTED-FORM. If you do this, only the start parameters you enter are
logged, not the default values.
DBH start parameters in the sequence of commands for starting the DBH
You can enter the start parameters in the sequence of commands for starting the DBH in
the procedure.
To do this, you must assign the SYSDTA system file to SYSCMD before the STARTSESAM-DBH command.
The start parameters must come immediately after the start command.
When entering the DBH start parameters, you must follow the rules on page 45.
U22418-J-Z125-6-76
41
Starting the SESAM/SQL DBH
Working with the SESAM/SQL DBH
Passing the DBH start parameters via an input file
Before you start the DBH by means of the START-SESAM-DBH command, you have to
assign the input file. There are a number of ways to do this. You can assign the input file:
–
as a DBH configuration file using the link name SESCONF
–
as a SYSDTA system file
–
as a global configuration file using the CONNECT-SESAM-CONFIGURATION
command (see page 44)
It is possible in interactive mode as well as batch mode to pass the DBH start parameters
to the DBH by means of an input file (see page 48).
Assigning a DBH configuration file
You assign the DBH configuration file with the following command:
ADD-FILE-LINK LINK-NAME=SESCONF,FILE-NAME = input-file
Assigning a SYSDTA system file as the input file
ASSIGN-SYSDTA TO-FILE = input-file
Assigning a global configuration file
This global configuration file can contain configuration parameters for several components
of the SESAM/SQL system (see page 48). The file must have the following structure:
CONFIGURATION-LINK = linkname-1 —————————————————————————
dbh-option | dcn-option | dbcon-option ————————————————————————————————
CONFIGURATION-LINK = linkname-2 ———————————————————————————————————————
dbh-option | dcn-option | dbcon-option
CONFIGURATION-LINK = linkname-n
dbh-option | dcn-option | dbcon-option
.
.
42
(1)
(2)
(3)
(1)
This string must begin in column 1.
(2)
The DBH options are not checked until the various tasks are executed. They can be
separated by „//REMARK“ comment lines.
(3)
The link names must be unique in the file.
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting the SESAM/SQL DBH
Example of a global configuration file
//REMARK LOAD OPTIONS FOR THE DBH************************************
CONFIGURATION-LINK=SESDBB1
//SET-DBH-OPTIONS//
DBH-IDENTIFICATION=*PARAMETERS(//
CONFIGURATION-NAME=Z//
,DBH-NAME=X//
)//
,ADMINISTRATION=*PARAMETERS(//
ACCOUNTING=*PARAMETERS(.
.
.
//REMARK K_2_DBH_NEW_1 ***********************************************
//ADD-SQL-DATABASE-CATALOG-LIST//
ENTRY-1=*CATALOG(//
CATALOG-NAME=ORDERCUST//
,USER-ID=ID1//
).
.
.
//REMARK LOAD OPTIONS FOR APPLICATION PROGRAMS **************************
CONFIGURATION-LINK=SESDBB2
REMARK CONFIGURATION DATA ****************************************
CNF=Z
NAM=X
PUF=64000
TOTAL-USERS=00128
REMARK A DB PROCESS IS ASSIGNED SPECIFICALLY TO A UTM PROCESS *****
UTMVG=JA
VT
U22418-J-Z125-6-76
43
Starting the SESAM/SQL DBH
Working with the SESAM/SQL DBH
You can assign this file only with the following command:
CONNECT-SESAM-CONFIGURATION
TO-FILE = <filename 1..54> / *LIBRARY-ELEMENT(...)
*LIBRARY-ELEMENT(...)




LIBRARY = <filename 1..54>
,ELEMENT = <composed-name 1..64>(...)

VERSION = *HIGHEST-EXISTING / <composed-name 1..24>
,TYPE = S / <alphanum-name 1..8>
,CONFIGURATION-LINK = <alphanum-name 1..8>
Operands
TO-FILE = <filename 1..54>
You specify the name of the global configuration file here.
TO-FILE = *LIBRARY-ELEMENT(...)
If the configuration file is in a library, you make the appropriate entries here.
*LIBRARY-ELEMENT(...)
LIBRARY = <filename 1..54>
You specify the library name here.
ELEMENT = <composed-name 1..64>(...)
You specify the element name here.
VERSION = *HIGHEST-EXISTING / <composed-name 1..24>
You specify a version of the element here.
TYPE = S / <alphanum-name 1..8>
You specify the type of the element here.
CONFIGURATION-LINK = <alphanum-name 1..8>
You specify here the link name to which the options for the DBH to be started are
assigned in the global configuration file.
The options for the selected configuration are stored locally in a configuration file with the
following name:
tSESCONF.tsn
t
44
Temporary identifier: # or @
If no temporary identifier is assigned at system startup, a permanent SESCONF.tsn
file is assigned.
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting the SESAM/SQL DBH
Notes on entering the start parameters
When entering the DBH start parameters, you must observe the following rules regardless
of whether you enter them in a procedure or an input file:
–
Each line must begin with the escape symbol (//).
–
Each start statement must begin on a new line.
–
If a start statement and its parameters take up several lines, each line except the last
must be concluded with the continuation character (-).
–
The continuation character (-) is not permitted at the end of a line if there is a new start
statement or an END statement on the next line.
–
The parameters must be entered in a specific sequence (see chapter “DBH start statements and options” on page 63).
–
The SET-DBH-OPTIONS statement must be followed by either another start statement
or the END statement.
–
The DBH start statements ADD-SQL-DATABASE-CATALOG-LIST and ADD-OLDTABLE-CATALOG-LIST must both be followed by the END statement (see section “DBH
start statements” on page 64).
–
If ADD-SQL-DATABASE-CATALOG-LIST is not followed by the ADD-OLD-TABLECATALOG-LIST start statement, you must enter an END statement instead. This END
statement can only be omitted when the DBH is started with the default setting for the
DBH option OLD-TABLE-CATALOG, which is OLD-TABLE-CATALOG =0 (see
page 102).
If one of the DBH start parameters is incorrect, the DBH aborts and you receive an error
message.
These rules apply in interactive mode as well as batch mode.
U22418-J-Z125-6-76
45
Starting the SESAM/SQL DBH
2.2.2.3
Working with the SESAM/SQL DBH
Example of a procedure for starting the independent DBH
The following example shows a procedure for starting the independent DBH. A DBH with
the DBH name x and the configuration name z is started as a batch job under the identifier
$ID1. During the DBH session, SQL and CALL DML statements are to be executed. The
DBH start parameters are entered in an S procedure called STARTP.SESDBH.ENTER.
Example
The command for initializing the batch job is:
/ENTER-PROCEDURE NAME=STARTP.SESDBH.ENTER,PROC-PAR=NO,LISTING=YES,LOGGING=YES
The S procedure called STARTP.SESDBH.ENTER has the following structure:
/SET-PROCEDURE-OPTIONS
/ASSIGN-SYSLST TO-FILE=LST.SESDBH.E.DBH.IND
/MODIFY-MSG-ATTRIBUTES TASK-LANGUAGE=E
/MODIFY-TEST-OPTIONS DUMP=YES
/START-SESAM-DBH
//SET-DBH-OPTIONS//
DBH-IDENTIFICATION=*PARAMETERS(//
CONFIGURATION-NAME=Z //
,DBH-NAME=X //
)//
,ADMINISTRATION=*PARAMETERS(//
ADMINISTRATOR=*ANY(//
PASSWORD=C'XXX'//
)//
)//
,SYSTEM-LIMITS=*PARAMETERS(//
SQL-DATABASE-CATALOG=10//
,OLD-TABLE-CATALOG=5 //
)//
,SQL-SUPPORT=*YES(//
INTERNAL-SORT-LIMIT=5000 //
,INACTIVITY-TIME=1 //
)
// ADD-SQL-DATABASE-CATALOG-LIST //
ENTRY-1=*CATALOG(CATALOG-NAME=ORDER_CUST) //
,ENTRY-2=*CATALOG(CATALOG-NAME=CALL_COMPANY)
//END
46
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting the SESAM/SQL DBH
// ADD-OLD-TABLE-CATALOG-LIST //
ENTRY-1=*CALL-DML-TABLE(CALL-DML-TABLE-NAME=SALES //
,CATALOG-NAME=CALL_COMPANY //
,SCHEMA-NAME=SALES_SCH //
,TABLE-NAME=SALES) //
,ENTRY-2=*CALL-DML-TABLE(CALL-DML-TABLE-NAME=COMPANY //
,CATALOG-NAME=CALL_COMPANY //
,SCHEMA-NAME=COMPANY_SCH //
,TABLE-NAME=COMPANY)
//END
/ASSIGN-SYSLST TO-FILE=*PRIMARY
/EXIT-PROCEDURE
2.2.3 Starting the linked-in DBH
SESAM/SQL-LINK is a chargeable add-on product of the SESAM/SQL database system.
It consists of the following components:
–
the linked-in DBH
–
the SEDI61L utility (which outputs responses to CALL DML retrieval statements to a
SAM file)
–
the SEDI63L utility (which checks CALL DML statements).
You can use SESAM/SQL-LINK whenever a single application program is to have access
to one or more databases. The linked-in DBH then processes the requests of this application program exclusively. It is linked to the application program directly; the program and
the linked-in DBH belong to the same task.
SESAM/SQL-LINK is not available for business servers with SPARC64 architecture.
Application program and linked-in DBH
The linked-in DBH is loaded and started by the connection module linked to the application
program.
Application programs that work with the linked-in DBH must also be linked to the SESLINK
connection module (see the “Core Manual”). When the first statement is executed, the
SESLINK connection module automatically and dynamically loads the modules of the
linked-in DBH from the SESAM/SQL module library, provided the module library was
assigned appropriately before the application program started.
To ensure that all SESAM/SQL external references are resolved, the application program
and SESLINK should be linked statically. SESLINK is already integrated in the SEDI61L
and SEDI63L utilities.
U22418-J-Z125-6-76
47
Starting the SESAM/SQL DBH
Working with the SESAM/SQL DBH
The “ESQL-COBOL for SESAM/SQL-Server” and “CALL DML Applications” manuals
describe how an application program is linked and started.
Passing the start parameters
Users who want to use values other than the defaults can parameterize the linked-in DBH
by means of the DBH configuration file (see the “Core Manual”).
The configuration file for the DBH start parameters is a SAM file with a freely definable
name in which the user enters the DBH start statements and options. The same rules apply
to the entry of the DBH start statements and options as apply to the entry of the DBH start
parameters in an input file of the independent DBH (see page 45).
Before starting the application program, you must assign the configuration file of the DBH:
–
either with the following BS2000 command:
ADD-FILE-LINK LINK-NAME = SESCONF, FILE-NAME = configuration-file
–
or with:
CONNECT-SESAM-CONFIGURATION TO-FILE = global-configuration-file
(see page 44)
When the linked-in DBH starts, the start parameters are passed to it.
If one of the configuration-file parameters to be evaluated contains syntax errors, the file is
closed and the associated application program receives an error message.
If a configuration file is not assigned before the application is started, the linked-in DBH
outputs a system prompt (//). The user can then enter the DBH start statements and options
directly on screen.
48
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Starting the SESAM/SQL DBH
2.2.4 Starting several SESAM/SQL DBHs
You can start more than one DBH on a single computer, regardless of whether they are
independent or linked-in, and manage parts of the DBH as share modules.
i
It is important to differentiate between the ability to start several DBHs from a multitasking operation. The first option refers to starting several databases and then
having processes from different DBHs run. The second option provides the ability
to use several DBH tasks running in parallel for task runs from one and the same
database. See the “Core Manual” for more detailed information.
Assigning and naming a DBH
To avoid conflicts, you should group related applications into configurations, thus separating
them from those in other configurations (see the “Core Manual”). You place a DBH in a
configuration by assigning it the configuration name (see the description of the DBH option
CONFIGURATION-NAME on page 86). The configuration name must be unique on the
computer.
You use the DBH option DBH-NAME (see page 91) to assign the DBH name. The DBH
name must be unique in the configuration. If it is not, name conflicts can occur between
DBH-specific files that include the DBH name and configuration name in their names (the
TA-LOG files, WA-LOG file and cursor files).
U22418-J-Z125-6-76
49
Starting the SESAM/SQL DBH
Working with the SESAM/SQL DBH
2.2.5 SESAM/SQL share modules
To reduce loading times or main-memory requirements, you can make use of BS2000
functions that allow you to administer parts of SESAM/SQL as share modules. You can load
LLMs as subsystems.
Loading LLMs as subsystems
The dynamic subsystem management facility (DSSM) of BS2000 regards share modules
as subsystems and manages them accordingly.
Parts of the SESAM/SQL DBH, some communication modules and parts of SESDCN can
be loaded into class 4 memory as subsystems under DSSM. DSSM controls the dynamic
loading, initialization, suspension, continuation and termination of the subsystems (see the
“Subsystem Management (DSSM/SSCM)” manual).
i
With SESAM/SQL-Server, several correction delivery statuses can be used in
parallel. If one or more subsystems of SESAM/SQL are already loaded when a new
correction delivery status is loaded, the SESAM subsystems do not automatically
load the new correction delivery status. In this case, you have to terminate all tasks
associated with the SESAM subsystems and then start the SESAM subsystems
again. SESAM/SQL can then restart the tasks, which load the new correction
delivery status (see also section “Specifying the correction delivery status with the
start command” on page 36).
Lists of the SESAM/SQL share modules
The tables below list the available SESAM/SQL share modules. The column entitled “DSSM
subsystem” indicates the subsystems into which the LLMs are grouped when loaded with
DSSM.
In the LLM names, “xx” is a placeholder for the digits in the version number of SESAM/SQL.
50
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
LLM name
Starting the SESAM/SQL DBH
Comment
DSSM subsystem
DBH share module
SESDBH
1
SECDHxx
SECSTxx
SEDKFxx
SEDLGxx
SEFKBxx
SEGTRxx
SEINTxx
SEOPTxx
SESDMxx
SESKFxx
SEUUIxx
Table 7: DBH and SESDCN share modules
1
LLM of the independent DBH
LLM name
Meaning
DSSM subsystem
SECDNxx
SESDCN share module
SESKOMMD
Table 8: Share module of SESDCN,
the distribution component for distributed processing with SESAM/SQL-DCN
LLM name
Meaning
DSSM subsystem
SECLAxx
Communication LLM for non-distributed processing
SESKOMOD
SECVAxx
Communication LLM for distributed processing
SESKOMMD
SERTSxx
SQL runtime system
SESSQLRT
Table 9: communication share modules
LLM name
Task types that use the share module
SEZCSxx
DBH, SESDCN and independent communication in
the application program
SEJSVxx
DBH and independent communication in the
application program
SECCSxx
Independent communication in the application
program
SECSVxx
Independent communication in the application
program
DSSM subsystem
SESKOM for
business servers with
/390 architecture
SESKOM for
business servers with
SPARC64 architecture
Table 10: Share modules used by several task types
U22418-J-Z125-6-76
51
Terminating the SESAM/SQL DBH
Working with the SESAM/SQL DBH
2.3 Terminating the SESAM/SQL DBH
This section describes how to terminate the SESAM/SQL DBH and thus the DBH session,
depending on the operating mode.
2.3.1 Terminating the independent DBH
You terminate the independent DBH by means of:
–
the SESADM administration program with the STOP-DBH administration statement
–
or the STOP-DBH administration command (see page 337).
In the case of CALL DML applications, you can also terminate the DBH by means of a CALL
DML administration statement issued from a TIAM application or a UTM program unit.
However, to do this, you must be authorized by means of the system user ID of the system
administrator entered in the DBH option ADMINISTRATOR to use the CALL interface for
the purpose of administration (see page 82).
In a SESAM/SQL UTM application, you should always terminate the DBH with the following
administration statement (or the corresponding administration command):
STOP-DBH UTM-SESSION-INFO=KEEP
The parameter UTM-SESSION-INFO=KEEP (default value) causes the log files of the DBH
to remain active and the restart information they contain to be preserved.
2.3.2 Terminating the linked-in DBH
The linked-in DBH can be terminated only by means of the STOP-DBH administration
command.
In the case of the linked-in DBH, the administration command does not take effect until the
next statement is issued to the DBH in the application program and control is thus passed
to the DBH.
If no further statements are issued during the program run, the linked-in DBH is terminated
when the application program is terminated.
52
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Restarting a DBH session
2.4 Restarting a DBH session
The SESAM/SQL DBH carries out a restart when operation resumes after interruptions
caused by malfunctions (see the “Core Manual”).
During a restart, all logically inconsistent databases are opened and their consistency is
restored. The DBH obtains information on the processing status of the database transactions from the transaction log files (TA-LOG files) and the restart log file (WA-LOG file).
Depending on whether or not the current DBH session is interrupted, the DBH carries out
an external or internal restart:
–
It carries out an external restart when it is started after an aborted session.
–
It carries out an internal restart without interrupting operation after internal errors of
lesser importance.
Both the independent DBH and the linked-in DBH can carry out a restart.
In a UTM application, the SESAM/SQL DBH and openUTM carry out a synchronized restart
(see the “Core Manual”).
U22418-J-Z125-6-76
53
Restarting a DBH session
Working with the SESAM/SQL DBH
2.4.1 Restart requirements
Before the DBH can carry out a restart, the following requirements must be met:
–
The DBH must be running with transaction management, which is the default mode.
Transaction management can be turned off by means of the DBH option
TRANSACTION-SECURITY.
–
The TA-LOG files (transaction log files) must be available.
Its default name is:
SESAMcn.TA-LOG1 and SESAMcn.TA-LOG2 for the independent DBH and
SESLKcn.TA-LOG1 and SESLKcn.TA-LOG2 for the linked-in DBH.
–
The WA-LOG file (restart log file) must be available.
Its default name is:
SESAMcn.WA-LOG for the independent DBH and
SESLKcn.WA-LOG for the linked-in DBH.
The TA-LOG files and WA-LOG file include in their names the configuration name (c) and
the DBH name (n) defined by means of the DBH option DBH-IDENTIFICATION when the
aborted session was started.
If the TA-LOG files and WA-LOG file are not available, the DBH cannot carry out the restart.
The database administrator then has to use the appropriate utility statements to repair
logically inconsistent databases (see the “SQL Reference Manual Part 2: Utilities”).
54
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Restarting a DBH session
2.4.2 Controlling the duration of the restart
The duration of the restart essentially depends on the duration of the physical repair and
the logical resetting of the open transactions. The aim is to reduce the duration of the restart
to a minimum. The following sections explain the options provided to you for this purpose
by the DBH.
Reducing the duration of physical repair
In physical repair, the afterimage blocks are written from the TA-LOG files to the databases.
The more often the afterimage blocks are saved during normal operation, the fewer data
blocks have to be written in the event of a restart. This reduces the time required before
normal operation can be resumed after an interruption. You can increase the frequency with
which the afterimage blocks are written during the session by means of the BUFFER-LIMIT
and TALOG-LIMIT parameters of the DBH option RESTART-CONTROL (see page 106).
However, too much saving during normal operation can affect performance. You should
therefore use the performance monitor to keep track of the I/O rates and make changes, if
necessary, to the BUFFER-LIMIT and TALOG-LIMIT parameters during operation using the
MODIFY-RESTART-CONTROL administration statement (see page 256).
Delaying logical resetting in normal operation
In a logical reset, the transactions that were open at the last consistency point are reset on
the basis of the logical beforeimages.
When LOGICAL-ROLLBACK = *DELAYED is set with the DBH option RESTARTCONTROL (see page 106), this reset can be delayed until normal operation begins after a
restart. The reset operations then run parallel to the normal transactions and requests of
users and are synchronized accordingly as in normal operation.
Delaying of the logical reset is suppressed in the following cases, even if the option
described in the previous paragraph is used:
–
In the event of a restart because of a bottleneck affecting the transaction log files, since
the removal of the bottleneck is not to be expected before the open transactions are
reset.
–
In the event of a restart because of a bottleneck affecting a DA log file. In this situation,
it is only possible to read the databases. The open transactions therefore have to be
reset here as well before a restart.
–
In the event of a restart because of a defective catalog space. In this case, too, the
transactions have to be reset immediately, since the repaired data and index spaces are
physically closed at the end of the restart on account of the missing catalog space.
U22418-J-Z125-6-76
55
Restarting a DBH session
Working with the SESAM/SQL DBH
2.4.3 Carrying out an external restart
After an aborted session, you start the DBH in the usual way. However, when passing the
DBH start parameters, note the following:
–
The configuration name and DBH name of the aborted and restarted sessions must be
the same (see the DBH options “CONFIGURATION-NAME” on page 86 and “DBHNAME” on page 91). An external restart is only carried out if you start a DBH with the
same configuration name and DBH name as the aborted session. Only in this case can
the DBH evaluate the restart information in the corresponding TA-LOG files and WALOG file.
–
If you do not want to use the default values for one or more parameters, you have to
enter the DBH option MEDIA-CATALOG (see page 94).
–
The DBH adopts the other DBH start parameters from the WA-LOG file. Any additional
start parameters you enter are ignored.
The LOGICAL-ROLLBACK = IMMEDIATELY / DELAYED parameter of the RESTARTCONTROL administration statement is an exception to this because you can also
change its value subsequently.
If one of the relevant databases or a space is not available, you receive a message to this
effect. The DBH expects one of the following responses:
R
to attempt to open it again
I
to skip the database or space and resume processing
H
to abort the restart
Even when databases or spaces cannot be made available to the DBH, it still tries to
complete the restart successfully. These databases or spaces can then be repaired by
means of the RECOVER utility statement (see the “SQL Reference Manual Part 2:
Utilities”).
During the restart, the DBH does not process any requests; administration statements or
commands cannot be executed during this phase.
Once the restart has been successfully completed, the databases remain open and application programs can again work with them.
56
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Job variables
2.5 Job variables
Where necessary SESAM-DBH operates with the following types of job variables:
–
job variables for controlling requests and programs
–
monitor job variables for job monitoring
2.5.1 Job variables for controlling requests and programs
SESAM/SQL allows job variables to be used in a DBH session to control requests and
programs. The software product JV (BS2000) Job Variables must be installed for this
purpose (see the “JV (BS2000/OSD)” manual). If JV is not available, the creation and
definition of job variables are refused without warning.
To indicate the readiness of the DBH for communication, you can use job variables to
document the following statuses:
–
the beginning of the DBH session
–
the end of the DBH session
–
errors during the DBH session
–
current status of the DBH session
–
WA-LOG and TA-LOG status
–
creation of a replication.
If the replication is located in a BS2000 user ID that is not the same as the DBH user
ID, an attempt is made to create the job variable also in the replication ID or use a job
variable already created under this name. SESAM can only create the job variable in
the replication ID when the DBH user ID is entered as a co-owner for the job variable.
If the job variable cannot be created in the replication ID, or if it is not created there, it
is created in the DBH user ID.
The overview given below indicates the times at which the SESAM/SQL DBH sets the job
variables.
The DBH always creates job variables as shared job variables (USER-ACCESS=*ALLUSERS). If other attributes are to be used, the job variables must be suitably set up
manually by the database administrator beforehand.
The job variables SESAM.START.cn, SESAM.END.cn and SESAM.ERROR.cn are not used
since SESAM/SQL V3.0.
U22418-J-Z125-6-76
57
Job variables
Working with the SESAM/SQL DBH
Time
Job variable name
Between the
SESAM.SESDBH.cn
start and end of c means: configuration name
(see page 86)
the DBH session
n means: DBH name
(see page 91)
Job-variable contents
Date YYYY,MM,DD
Time hh,mm,ss
DBH-STARTED
DBH_NORMAL_END|
DBH_ABNORMAL_END|
DBH_ENDED_WITH_WARNINGS
TA-LOG ACTIVE | NOT ACTIVE
System error: CC XX/YY/ZZ | IW xxx
Termination: IW xx
Message: yyyyyyy
The following mean:
CC XX/YY/ZZ: Consistency Check with
number, weight and subnumber
IW xxx: The interrupt weight
yyyyyyyy: The message code
(see the “Messages” manual)
The first update SICHERUNGSINFORMATION.cn Status of the files
in the DBH
SESAMcn.TA-LOG1
session, or when
SESAMcn.TA-LOG2
the session is
SESAMcn.WA-LOG
ended correctly
SESLKcn.TA-LOG1
SESLKcn.TA-LOG2
SESLKcn.WA-LOG
Status of the transaction management files:
o.k.
Restart
UTM information
When creating a userid.SESAM.
replication
replication.NEXT-REPL-LOG
The oldest CATLOG and DALOG file required
for the first REFRESH REPLICATION
(see the “Core Manual”)
Table 11: Job variables
i
58
The job variable SESAM.SESDBH.cn does not contain “System error: IW xx” any
more for STXIT events of class ABEND and TERM, rather it contains “Termination:
IW xx” (xx: STXIT interrupt weight) because these STXIT events are not system
errors. You will find the meanings of the STXIT interrupt weights in the manual
“Executive Macros” in the description of the STXIT macro.
If an internal transaction restart (e.g. due to a logging bottleneck) cannot be
executed and the session must be terminated, then the job variable
SESAM.SESDBH.cn contains “Message: yyyyyyy” (yyyyyyy: message code) where
the corresponding message contains the cause of the failed restart.
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Job variables
If necessary, you can use predefined macros to change names and explanatory texts in the
job variables. The predefined macros are in the SEZTXT.ASS source file which is shipped
as part of the SIPANY.SESAM-SQL.032.SPEZ library.
The SEZTXT.ASS source file contains the following macros:
–
JOBV name[,[length][,MONJV]]
This macro declares a job variable called name.
–
name
The name of the job variable (maximum length: 54 characters)
length
The length of the job-variable name's suffix
MONJV
This defines the job variable as a monitoring job variable, in which case the
text is not stored until position 128 (i.e. after the system part) in the job
variable.
TEXT text
This macro generates contents in the form of a text for the job variable called name.
text
–
A text string consisting of any characters (C'...') or hexadecimal characters
(X'...') and with a maximum length of 54 characters. Several text strings can
refer to a single job variable.
INSRT length
This macro generates an insert with a length of length for the job variable called name.
As a result, a text of the specified length is subsequently inserted dynamically. The
macro can be specified several times for a single job variable.
length
The length of the insert (maximum length: 256 characters)
You can change the name of the job variable in the JOBV macro, and you can change the
name of the text string in the TEXT macro. The entries in the INSRT macro cannot be
changed.
Note that the total length of all texts and inserts for a job variable cannot be more than
256 characters.
After each change, you have to assemble the source file and enter it in the SESAM/SQL
module library under the module name SEZTXT.ASS. You will find the source module in the
SESAM/SQL library with special elements.
U22418-J-Z125-6-76
59
Job variables
Working with the SESAM/SQL DBH
2.5.2 Monitor job variables for job monitoring
SESAM-DBH supplies an existing monitoring job variable at the same time, with the job
variable SESAM.SESDBH.cn.
The content of the monitoring job variable is described in the manual “JV (BS2000/OSD)”,
section entitled “Request/program monitoring with JVs”.
SESAM/SQL supplies the following fields:
60
–
“Name of the application to be monitored” (Bytes 53-60) with “SESDBHcn”
–
“Application-specific information” (bytes 71-128) is supplied with the content of the job
variable SESAM.SESDBH.cn without “date” and “time” (see the table “Job variables” on
page 58).
U22418-J-Z125-6-76
Working with the SESAM/SQL DBH
Maximum values for working with the SESAM/SQL DBH
2.6 Maximum values for working with the SESAM/SQL DBH
You can use DBH start statements and options to set limit values for certain parameters.
The following table lists the maximum values for important parameters in a DBH session.
Maximum values
Number
Entries in the SQL database catalog
254
Entries in the CALL DML table catalog
254
Simultaneously accessible spaces
50,800
Concurrent users
32,767
Concurrent SQL access plans in the plan buffer
999,999
Concurrent SQL cursors
999,999
Concurrent suborders
(scans in the case of SQL and logical files in the case of CALL DML)
262 143
DBH tasks
16
Service tasks in the case of the independent DBH
64
CO-LOG files
9,999
Sorted rows in an SQL cursor table
2,147,483, 647
Spaces per database
200
Threads in the case of the independent DBH
1024
Write threads in the case of the independent DBH
512
Maximum values
Size
Area for retrieval statements (in columns)
1024
Cursor buffer (in Kbytes)
1,000,000
System-data buffer (in Kbytes)
1,000,000
Transfer container (in Kbytes)
1,000,000
User-data buffer (in Kbytes)
1,000,000
Work container (in Kbytes)
1,000,000
Table 12: Maximum values
U22418-J-Z125-6-76
61
Eine Dokuschablone von Frank Flachenecker
by f.f. 1992
3 DBH start statements and options
This chapter describes the syntax and functions of the DBH start parameters and includes
notes on how to enter them.
The chapter is divided into the following sections:
●
Overview and notes on entry
●
Descriptions in alphabetical order
The different ways of passing the DBH start statements and options when starting the DBH
are described in section “Starting the SESAM/SQL DBH” on page 38.
U22418-J-Z125-6-76
63
Overview and notes on entry
DBH start statements and options
3.1 Overview and notes on entry
The purpose of DBH start statements and options is to parametrize the DBH. You use them
to specify the resources, operating rules and limit values of the current DBH session.
You enter DBH start statements and options in SDF format. You can enter them in a
prompted or nonprompted dialog, from procedure files or in batch mode. You will find a
detailed description of the SDF dialog interface (System Dialog Facility) in the “Introductory
Guide to the SDF Dialog Interface”.
In this section, the DBH start statements and options are arranged in different tables,
depending on their contents. The section also contains information on entering the start
parameters.
3.1.1 DBH start statements
The DBH start statements initiate the parametrization of the DBH.
The following table lists the DBH start statements in the order in which they are entered:
DBH start statement
Function
1. SET-DBH-OPTIONS
Causes the DBH options to be read in.
2. ADD-SQL-DATABASE-CATALOG-LIST
Inserts entries in the SQL database catalog.
3. ADD-OLD-TABLE-CATALOG-LIST
Inserts entries in the CALL DML table
catalog.
Table 13: The DBH start statements
You must enter the SET-DBH-OPTIONS statement first, followed by the DBH options you
want to use.
The other two start statements are optional, since you can also make entries in the SQL or
CALL DML table catalog using administration statements (see section “ADD-OLD-TABLECATALOG-ENTRY” on page 215 and section “ADD-SQL-DB-CATALOG-ENTRY” on
page 218). However, if you want to insert entries in the CALL DML table catalog by means
of the ADD-OLD-TABLE-CATALOG-LIST start statement when starting the DBH, you must
first issue the ADD-SQL-DATABASE-CATALOG-LIST start statement.
64
U22418-J-Z125-6-76
DBH start statements and options
Overview and notes on entry
The END statement
When entering the DBH start statements, you must always use the END statement to
conclude parameter input.
The END statement is required at the following points during parameter input:
–
after the SET-DBH-OPTIONS statement, if this statement concludes parameter input
–
after the ADD-SQL-DATABASE-CATALOG-LIST start statement
–
after or instead of the ADD-OLD-TABLE-CATALOG-LIST start statement; you can only
omit this END statement when the DBH is started with the default setting for the lowerlevel DBH option OLD-TABLE-CATALOG, which is OLD-TABLE-CATALOG=0 (see
page 102).
Example 1
The END statement concludes parameter input after the SET-DBH-OPTIONS
statement.
//SET-DBH-OPTIONS ...
//END
Example 2
The first END statement concludes the ADD-SQL-DATABASE-CATALOG-LIST start
statement. The second concludes all parameter input.
//SET-DBH-OPTIONS ...
//ADD-SQL-DATABASE-CATALOG-LIST ...
//END
//ADD-OLD-TABLE-CATALOG-LIST ...
//END
Example 3
The first END statement concludes the ADD-SQL-DATABASE-CATALOG-LIST start
statement. The second concludes all parameter input. The ADD-OLD-TABLECATALOG-LIST start statement is not included.
//SET-DBH-OPTIONS ...
//ADD-SQL-DATABASE-CATALOG-LIST ...
//END
//END
U22418-J-Z125-6-76
65
Overview and notes on entry
DBH start statements and options
3.1.2 DBH options
DBH options parametrize the DBH and define the essential characteristics of a session.
They are subdivided into higher- and lower-level DBH options.
–
Higher-level DBH options, such as ADMINISTRATION or STORAGE-SIZE, relate to a
particular subject area.
–
Lower-level DBH options each deal with part of the subject area of their higher-level
option.
All the higher-level DBH options are assigned one or more lower-level options.
You enter the DBH options after entering the DBH start statement SET-DBH-OPTIONS.
There are default settings for all DBH options so you only need to enter those options for
which you want to specify values other than the defaults. However, before you can specify
your own values for one or more lower-level options, you must first enter the associated
higher-level option.
The following overview shows the DBH options that are available.
Overview of the DBH options
Higher-level option
Lower-level option
Brief description
CONFIGURATION-NAME
DBH-NAME
Identifies the DBH
Defines the configuration name
Defines the DBH name
ACCOUNTING
ADMINISTRATOR
MSG-OUTPUT
SECURITY
Administers the DBH
Activates accounting
Assigns administration authorization
Controls the outputs of the DBH
Changes security settings
DBH-IDENTIFICATION
ADMINISTRATION
CPU-RESOURCES
DBH-TASKS
SERVICE-TASKS
FILE-RESOURCES
MEDIA-CATALOG
SESSION-LOGGING-ID
Table 14: Higher- and lower-level DBH options
66
Controls the CPU utilization
Specifies the number of the DBH tasks
Specifies the number of tasks for service
requests
Specifies settings for files
Creates a media catalog
Identifies session-specific files
(part 1 of 2)
U22418-J-Z125-6-76
DBH start statements and options
Higher-level option
Overview and notes on entry
Lower-level option
Brief description
CURSOR-BUFFER
SYSTEM-DATA-BUFFER
TRANSFER-CONTAINER
USER-DATA-BUFFER
WORK-CONTAINER
Sets buffer and container sizes
Sets the cursor-buffer size
Sets the system-data buffer size
Sets the transfer-container size
Sets the user-data buffer size
Sets the work-container size
STORAGE-SIZE
SYSTEM-LIMITS
Specifies limit values
Enlarges the area for retrieval statements
Specifies the maximum number of entries
permitted in the CALL DML table catalog
SPACES
Specifies the maximum number of simultaneously accessible spaces
SQL-DATABASE-CATALOG Specifies the maximum number of entries
permitted in the SQL database catalog
SQL-SUPPORT
Specifies limit values for the SQL interface
SUBORDERS
Makes SQL scans or logical files available
SYSTEM-THREADS
Specifies the number of concurrent system
threads
THREADS
Specifies the maximum number of
concurrent threads
USERS
Specifies the maximum number of
concurrent users
COLUMNS
OLD-TABLE-CATALOG
SYSTEM STRATEGIES
Defines the processing strategy
Activates priority control
Controls the duration of availability in the
event of a restart
RETRIEVAL-CONTROL
Influences the search strategy of the DBH
TRANSACTION-SECURITY Activates transaction management
REQUEST-CONTROL
RESTART-CONTROL
Table 14: Higher- and lower-level DBH options
U22418-J-Z125-6-76
(part 2 of 2)
67
Descriptions in alphabetical order
DBH start statements and options
3.2 Descriptions in alphabetical order
This section contains descriptions of the DBH start statements and options in alphabetical
order.
3.2.1 Description format
The descriptions of the different DBH start statements and options are all structured in the
same way. There is an entry for each start statement or option. In each case, the name of
the statement or option is the entry's heading.
Each entry consists of several sections.
Sections that are not relevant to a specific statement or option are not included. The most
important sections are described overleaf.
Name of the start statement or option
Brief description
Definition
This section indicates whether the entry describes a DBH start statement or an option.
In the case of start statements, you will see the text “The n-th DBH start statement” here.
This means that you can immediately identify that this is a description of a start statement
and what position this start statement occupies in the input sequence.
In the case of DBH options, the text will be either “A higher-level DBH option” or “A lowerlevel DBH option of higher-level dbh option”.
This means that you can immediately identify which category the option belongs to and
which option (if any) is superordinate to it.
Function
This section provides a detailed description of the statement or option. As well as telling you
what the statement or option does, it provides other important information and explanations
relating to it.
68
U22418-J-Z125-6-76
DBH start statements and options
Descriptions in alphabetical order
The description is followed by a syntax diagram of the statement or option.
Name of the start statement or option
Operands
Operand descriptions
The various operands are described in this section in the order in which they occur in the
syntax diagram.
Subheading
Sections containing additional information on the statement or option may follow the
operand descriptions.
Special feature of the descriptions of higher-level DBH options
The SDF syntax diagrams in the descriptions of higher-level DBH options differ from those
in the other descriptions.
The following example shows the SDF syntax diagram of the higher-level DBH option
ADMINISTRATION.
ADMINISTRATION
= *STD / *PARAMETERS(...)
*PARAMETERS(...)




ACCOUNTING = *OFF
,ADMINISTRATOR = *NONE
,MSG-OUTPUT = *STD
,SECURITY = *STD
In the *PARAMETERS(...) line and the lines below it, all the lower-level DBH options of the
DBH option ADMINISTRATION are listed as operands, but only the default operand values
are given; you do not find all the permitted operand values here.
The list of all the associated lower-level DBH options with their default values is intended to
facilitate orientation; if you select *PARAMETERS(...) rather than *STD for a higher-level
option, you have to take the listed DBH options with all their operands into consideration.
U22418-J-Z125-6-76
69
Descriptions in alphabetical order
DBH start statements and options
3.2.2 Alphabetical reference section
The syntax of the DBH start statements and options corresponds to the SDF syntax (see
section “SDF syntax representation” on page 12).
The DBH start statements and options can be abbreviated in accordance with the SDF
conventions.
70
U22418-J-Z125-6-76
DBH options
ACCOUNTING
ACCOUNTING
This statement activates accounting.
Definition
A lower-level DBH option of ADMINISTRATION
Function
The DBH option ACCOUNTING activates logging of the accounting of services provided in
the different user sessions for BS2000's accounting procedure.
SESAM/SQL generates an accounting record (DBS1 record, see section “Layout of the
accounting information” on page 529) for each user session.
At the end of the user session, the accounting record is made available in the accounting
buffer:
–
–
–
In the case of SESAM/SQL UTM applications, SESAM/SQL is notified immediately by
the openUTM when the conversation is terminated at openUTM. This generates the
DBS1 record.
In the case of TIAM or DCAM CALL DML applications, the conversation is terminated
at the DBH by means of the appropriate CALL DML statements and the DBS1 record
is generated.
In the case of TIAM applications the process is terminated at the end of the program
run and the DBH is notified. The DBH generates the DBS1 record.
The contents of the accounting buffer are written to the BS2000 accounting file and can be
further processed by the RAV accounting procedure.
To make it possible to write to the BS2000 accounting file, the system administrator must
ensure that the following requirements are met:
–
–
MAX-ACCOUNT-RECORDS=*NO-LIMITS must be specified for the DBH user ID.
The record type DBS1 must be enabled in BS2000 accounting.
In SESAM/SQL UTM applications, the accounting procedure also supplies the UTM
accounting fields (UTMK record).
U22418-J-Z125-6-76
71
ACCOUNTING
DBH options
ACCOUNTING
= *OFF / *ON(...)
*ON(...)

CPU-TIME = *NO / *YES
Operands
ACCOUNTING = *OFF
Account logging is inactive initially. However, you can activate it during the DBH session.
The SET-ACCOUNTING-PARAMETER administration statement is provided to carry out
this function (see page 284).
ACCOUNTING = *ON(...)
RAV account logging is activated immediately.
CPU-TIME = *NO / *YES
Switches CPU-time counting on/off
72
U22418-J-Z125-6-76
DBH options
ADD-OLD-TABLE-CATALOG-LIST
ADD-OLD-TABLE-CATALOG-LIST
This statement inserts entries in the CALL DML table catalog.
Definition
The third DBH start statement
Function
You use the DBH start statement ADD-OLD-TABLE-CATALOG-LIST to supply the CALL
DML table catalog with entries. You only have to enter this start statement if CALL DML
applications are to run during the DBH session.
You enter in the CALL DML table catalog all the CALL DML tables that the DBH can access
during the session. You assign each CALL DML table to a database. You also assign the
table name used in the CALL DML Open statement to the name of a base table.
The DBH can use the CALL DML table catalog to assign the CALL DML tables addressed
in an application to the appropriate databases.
There must be an entry in the SQL database catalog for each database to which a CALL
DML table is assigned (see page 76).
You use the DBH option OLD-TABLE-CATALOG to specify the maximum number of entries
permitted in the CALL DML table catalog. Its default value is 0, but you can specify a value
of up to 254 (see page 102). If you enter more databases than the maximum number
permitted, an error message appears.
You can enter up to 100 CALL DML tables in a single start statement. If you want to enter
more than 100 tables, you have to enter the DBH start statement ADD-OLD-TABLECATALOG-LIST as many times as is necessary. However, the total number of all entered
CALL DML tables must not exceed the limit value specified by the DBH option OLD-TABLECATALOG.
You can also use several ADD-OLD-TABLE-CATALOG-LIST statements to enter the
required databases in groups.
You conclude parameter input for ADD-OLD-TABLE-CATALOG-LIST with the END
statement. This END statement simultaneously concludes input of all DBH start statements.
U22418-J-Z125-6-76
73
ADD-OLD-TABLE-CATALOG-LIST
DBH options
You can enter fewer CALL DML tables than specified by the DBH option OLD-TABLECATALOG. Free entries can be reserved by means of administration. You can use the ADDOLD-TABLE-CATALOG-ENTRY administration statement (see page 215) to enter
additional CALL DML tables during the session, but these entries apply only to this session.
ADD-OLD-TABLE-CATALOG-LIST
ENTRY-1 = *NONE / *CALL-DML-TABLE(...)
*CALL-DML-TABLE(...)




CALL-DML-TABLE-NAME = <text 1..17>
,CATALOG-NAME = <filename 1..18-without-all>
,SCHEMA-NAME = <c-string 1..31-with-lowercase> or <text 1..31>
,TABLE-NAME = <c-string 1..31-with-lowercase> or <text 1..31>
,ENTRY-2 = *NONE / *CALL-DML-TABLE(...)
.
.
,ENTRY-100 = *NONE / *CALL-DML-TABLE(...)
Operands
ENTRY-1 = *NONE
No CALL DML table is entered in the CALL DML table catalog.
ENTRY-1 = *CALL-DML-TABLE(...)
First CALL DML table entered in the CALL DML table catalog
CALL-DML-TABLE-NAME = <text 1..17>
Name of the CALL DML table, as used in the CALL-DML Open statement.
You must enter this name in full (17). It must be unique; i.e. you can enter it only once
in a DBH session.
CATALOG-NAME = <filename 1..18-without-all>
Logical name of the database to which the CALL DML table is to be assigned.
The logical database name must be entered in the SQL database catalog.
SCHEMA-NAME = <c-string 1..31-with-lowercase> or <text 1..31>
Name of the schema to which the CALL DML table is to be assigned
TABLE-NAME = <c-string 1..31-with-lowercase> or <text 1..31>
Base-table name corresponding to the CALL-DML-TABLE-NAME
74
U22418-J-Z125-6-76
DBH options
ADD-OLD-TABLE-CATALOG-LIST
ENTRY-2 = *NONE
No further CALL DML table is entered in the CALL DML table catalog at this point.
ENTRY-2 = *CALL-DML-TABLE(...)
Opening line of the second CALL DML table entered in the CALL DML table catalog.
The operands of ENTRY-2 are identical to those in the operand description for ENTRY-1.
You can enter up to 100 CALL DML tables in an ADD-OLD-TABLE-CATALOG-LIST
statement. You begin each entry with ENTRY-x = ... The placeholder x can have any value
from 1 to 99, but it must have a different value for each entry. The associated operands in
each case are identical to those in the operand description for ENTRY-1.
ENTRY-100 = *NONE / *CALL-DML-TABLE(...)
Opening line of the 100th CALL DML table entered in the CALL DML table catalog. You
cannot enter more than 100 CALL DML tables in one ADD-OLD-TABLE-CATALOG-LIST
statement. If you want to include more than 100 CALL DML tables in the session, you have
to enter this start statement again.
U22418-J-Z125-6-76
75
ADD-SQL-DATABASE-CATALOG-LIST
DBH options
ADD-SQL-DATABASE-CATALOG-LIST
This statement inserts entries in the SQL database catalog.
Definition
The second DBH start statement
Function
You use the DBH start statement ADD-SQL-DATABASE-CATALOG-LIST to supply the SQL
database catalog with entries. You enter in the SQL database catalog the databases that
the DBH can access during a DBH session. During a session, the DBH can only access
databases that are entered in the SQL database catalog.
Each database in the SQL database catalog is identified by its logical name. The logical
database name is the name by which an application program addresses a SESAM/SQL
database. If there is no SESAM/SQL database with this logical name, an existing database
is assigned by means of the physical database name. The physical database name is the
name of the physical SESAM/SQL database.
When you make an entry, you assign a BS2000 user ID (DB user ID) to each database,
enter the appropriate BS2000 password, assign the physical database name to the logical
database name, and regulate access to the database. For each entry, SESAM/SQL inserts
the valid status of the database during the current DBH session (see also the section on the
SHOW-SQL-DB-CATALOG-ENTRIES administration statement on page 324).
You use the DBH option SQL-DATABASE-CATALOG (see page 122) to specify the
maximum permitted number of database entries. The default is 1, but you can specify a
value of up to 254. If you enter more databases than the maximum number permitted, an
error message appears.
You can enter up to 100 databases in a single start statement. If you want to enter more
than 100 databases, you have to enter ADD-SQL-DATABASE-CATALOG-LIST as many
times as is necessary.
You can also use several ADD-SQL-DATABASE-CATALOG-LIST statements to enter the
required databases in groups.
You must always conclude parameter input for the ADD-SQL-DATABASE-CATALOG-LIST
statement with the END statement. You can then enter the END statement again. The
second END statement concludes input of the DBH start statements. Do not enter the
second END statement at this point if you want to use the ADD-OLD-TABLE-CATALOGLIST start statement to insert entries in the CALL DML table catalog.
76
U22418-J-Z125-6-76
DBH options
ADD-SQL-DATABASE-CATALOG-LIST
You can enter fewer databases than specified by the DBH option SQL-DATABASECATALOG. SESAM/SQL reserves unused entries for administration. You can use administration statements to add or delete database entries during the session, but these additions
and deletions apply only to this session.
Note that the CREATE CATALOG utility statement requires a free entry in the SQL database
catalog.
ADD-SQL-DATABASE-CATALOG-LIST
ENTRY-1 = *NONE / *CATALOG(...)
*CATALOG(...)











CATALOG-NAME = <filename 1..18-without-all>
,USER-ID = *DBH-USER-ID / <name 1..8>
,PASSWORD = *NONE / <c-string1..4> / <x-string 1..8> / <integer -2147483648..+2147483647>
,PHYSICAL-NAME = *STD / <filename 1..18-without-all>
,COPY-NUMBER = *NONE / <integer 1..9999>
,ACCESS = *ALL / *PARAMETERS(...)
*PARAMETERS(...)




READ = *YES / *NO
WRITE = *YES / *NO
CAT-ADMINISTRATION = *YES / *NO
REPLICATION = *YES / *NO
,ENTRY-2 = *NONE / *CATALOG(...)
.
.
,ENTRY-100 = *NONE / *CATALOG(...)
Operands
ENTRY-1 = *NONE
No database is entered in the SQL database catalog at this point.
ENTRY-1 = *CATALOG(...)
First database entered in the SQL database catalog. You must at least enter the CATALOGNAME operand, otherwise the entry in the SQL database catalog is invalid.
CATALOG-NAME = <filename 1..18-without-all>
Logical name of the database to be entered. The logical database name is the name by
which a database is addressed in the application program. You must enter the logical
database name, otherwise the entry in the SQL database catalog is invalid. The logical
database name must be unique; you cannot assign this name more than once.
U22418-J-Z125-6-76
77
ADD-SQL-DATABASE-CATALOG-LIST
DBH options
USER-ID = *DBH-USER-ID / <name 1..8>
DB user ID of the database.
The default value of USER-ID corresponds to the DBH user ID.
PASSWORD = *NONE / <c-string1..4> / <x-string 1..8> /
<integer -2147483648..+2147483647>
BS2000 password that protects the files in the database against unauthorized access.
If the files in the database are protected by a BS2000 password, you must enter it here.
The default, *NONE, means that the files in the database are not password protected.
PHYSICAL-NAME =
Physical name of the database.
The physical database name assigns the logical database name used by the application program to the name of a physical database. The physical database name must
be unique; you cannot assign this name more than once.
PHYSICAL-NAME = *STD
The physical database name corresponds to the logical database name you assigned
under CATALOG-NAME.
PHYSICAL-NAME = <filename 1..18-without-all>
You must enter the physical database name when it differs from the logical database
name.
The physical database name is derived from the BS2000 file name of a database's
catalog space. The .CATALOG suffix is omitted. The BS2000 file name of a database's
catalog space is: :catid:user-id.name.CATALOG
COPY-NUMBER =
SESAM backup copy of the specified database.
The SESAM backup copy of the catalog space must be complete and must be created
with the COPY CATALOG utility statement.
COPY-NUMBER = *NONE
The default value *NONE means that you only work with the original database.
COPY-NUMBER = <1..9999>
Four-position number of a SESAM backup copy of the specified catalog space. If you
specify COPY-NUMBER, read access to the database is entered automatically (see
ACCESS = *PARAMETERS(...)).
ACCESS =
Specifies which access functions can be used on the database.
ACCESS = *ALL
Access to the database is unrestricted. Read and write access are permitted to both
user data and metadata. The parameter *ALL only refers to the original database.
78
U22418-J-Z125-6-76
DBH options
ADD-SQL-DATABASE-CATALOG-LIST
ACCESS = *PARAMETERS(...)
Access to the database is restricted. The parameters are arranged in a hierarchical
structure. If CAT-ADMINISTRATION is permitted, so, implicitly, are WRITE and READ.
In the same way, if WRITE is permitted, so is READ.
At least one parameter must be specified with *YES.
If you specified COPY-NUMBER, the value READ = *YES is set automatically. An
implicit or explicit ACCESS = *ALL specification is then ignored.
WRITE=*NO and CAT-ADMINISTRATION=*NO must be specified explicitly when
ACCESS=*PARAMETERS() is used to specify the access privileges in detail, and
READ=*YES and REPLICATION=*NO must also be set (implicitly or explicitly),
otherwise an error message will result.
You are not permitted to specify the parameters WRITE and CAT-ADMINISTRATION for
backup copies.
READ = *YES
Permits read access to user data and metadata. The data can be queried but not
modified.
READ = *NO
Prevents read access to user data and metadata. Write access is not permitted
either. You cannot select READ = *NO if you have set *YES (the default) for either
CAT-ADMINISTRATION or WRITE.
WRITE = *YES
Permits read and write access to user data. Metadata can be read but not modified.
WRITE = *NO
Prevents write access to user data and metadata. You cannot select WRITE = *NO
if you have set *YES (the default) for CAT-ADMINISTRATION.
CAT-ADMINISTRATION = *YES
Permits read and write access to both user data and metadata.
CAT-ADMINISTRATION = *NO
Prevents you from changing the metadata in the database's catalog space. Thus,
the following statements are not permitted:
– SQL statements for schema definition and management and memory-structure
management
– utility statements
REPLICATION = *YES
Access to a replication of the specified database. You cannot access a normal
catalog with this database entry. Only read access and the utility statement
REFRESH REPLICATION are permitted for a replication.
REPLICATION = *NO
No access to a replication.
U22418-J-Z125-6-76
79
ADD-SQL-DATABASE-CATALOG-LIST
DBH options
ENTRY-2 = *NONE / *CATALOG(...)
Opening line of the second database entered in the SQL database catalog. The operands
of ENTRY-2 are identical to those of ENTRY-1.
You can enter up to 100 databases in an ADD-SQL-DATABASE-CATALOG-LIST statement.
You begin each entry with ENTRY-x = ... The placeholder x can have any value from 1 to 99,
but it must have a different value for each entry. The associated operands in each case are
identical to those of ENTRY-1.
ENTRY-100 = *NONE / *CATALOG(...)
Opening line of the 100th database entered in the SQL database catalog.
You cannot enter more than 100 databases in one ADD-SQL-DATABASE-CATALOG-LIST
statement. If you want to include more than 100 databases in the DBH session, you have
to enter this start statement again.
80
U22418-J-Z125-6-76
DBH options
ADMINISTRATION
ADMINISTRATION
This statement administers the DBH.
Definition
A higher-level DBH option
Function
ADMINISTRATION is the higher-level option for all DBH options that are important for
SESAM/SQL system administration.
ADMINISTRATION
= *STD / *PARAMETERS(...)
*PARAMETERS(...)




ACCOUNTING = *OFF
,ADMINISTRATOR = *NONE
,MSG-OUTPUT = *STD
,SECURITY = *STD
Operands
ADMINISTRATION = *STD
Default values apply to all the parameters of ADMINISTRATION. These are described
under the relevant lower-level DBH options.
ADMINISTRATION = *PARAMETERS(...)
The various parameters of ADMINISTRATION are DBH options. Their operands are
described in each case under the relevant DBH option.
U22418-J-Z125-6-76
81
ADMINISTRATOR
DBH options
ADMINISTRATOR
This statement assigns administration authorization.
Definition
A lower-level DBH option of ADMINISTRATION
Function
You use the DBH option ADMINISTRATOR to define a password that prevents the unauthorized issue of administration statements via the CALL interface and the SESADM administration program. You can also specify that only one user is authorized to issue administration statements, namely the system administrator. To do this, enter the system user
identification of the system administrator.
You must also specify the system administrator's system user identification if certain utility
statements are to be issued during the DBH session. The system user identification entered
here is required at the authorization check for the CREATE CATALOG,
CREATE REPLICATION, RECOVER CATALOG, RECOVER CATALOG_SPACE,
REFRESH REPLICATION and UNLOAD ... FROM COPY_FILE utility statements
(see the “SQL Reference Manual Part 2: Utilities”).
During the DBH session, the system administrator can modify the entries for
ADMINISTRATOR to suit requirements by using the MODIFY-ADMINISTRATION administration statement (see page 243).
ADMINISTRATOR
= *NONE / ANY(...) / *TIME-SHARING-USER(...) / *APPLICATION-USER(...)
*ANY(...)

PASSWORD = <c-string 3..3> / <x-string 5..6>
*TIME-SHARING-USER(...)



PASSWORD = <c-string 3..3> / <x-string 5..6>
,HOST-NAME = <name 1..8>
,USER-ID = <name 1..8>
*APPLICATION-USER(...)




82
PASSWORD = <c-string 3..3> / <x-string 5..6>
,HOST-NAME = <text 1..8>
,APPLICATION-NAME = <text 1..8>
,CUSTOMER-NAME = <text 1..8>
U22418-J-Z125-6-76
DBH options
ADMINISTRATOR
ADMINISTRATOR = *NONE
Administration using the CALL interface and SESADM is not possible. The MODIFYADMINISTRATION administration statement is also rejected.
ADMINISTRATOR = *ANY(...)
Users who are not system administrators can also issue administration statements using
the CALL interface and SESADM.
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password that prevents unauthorized administration using the CALL interface and
SESADM
ADMINISTRATOR = TIME-SHARING-USER(...)
Only the system administrator can issue administration statements using the CALL
interface and SESADM. The system administrator is a timesharing user and is identified by
the system user identification, i.e. host name and BS2000 user ID.
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password that prevents unauthorized administration using the CALL interface and
SESADM
HOST-NAME = <name 1..8>
Name of the host from which administration is to be carried out
USER-ID = <name 1..8>
BS2000 user ID of the system administrator
ADMINISTRATOR = APPLICATION-USER(...)
Only the system administrator can issue administration statements using the CALL
interface and SESADM. The system administrator is an application user and is identified by
the system user identification, i.e. the host name, the name of the UTM application and the
name of the user (customer name).
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password that prevents unauthorized administration using the CALL interface and
SESADM
HOST-NAME = <text 1..8>
Name of the host from which administration is to be carried out
APPLICATION-NAME = <text 1..8>
Name of the application from which administration is to be carried out
CUSTOMER-NAME = <text 1..8>
Name of the user. If the system administrator is working under openUTM, the KDCSIGN
name must be specified here. If the system administrator is working under DCAM, the
name used by the system administrator at the programming interface must be specified.
U22418-J-Z125-6-76
83
COLUMNS
DBH options
COLUMNS
This statement enlarges the area for retrieval statements.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
The DBH option COLUMNS allows you to enlarge the area for retrieval statements.
The area for retrieval statements is normally limited to 256 columns. In the case of large
retrieval statements that address more than 256 columns, you must increase the size of this
area. You can increase it to anything up to 1024 columns.
COLUMNS
= 256 / <integer 256..1024>
Operands
COLUMNS = 256 / <integer 256..1024>
Area size in columns for retrieval statements.
Calculating the length of a retrieval statement
You base your entry for the COLUMNS option on the length of the longest retrieval
statement in an application. This is determined by the number of columns (attributes in the
case of CALL DML) or the number of conditions attached to columns. In the case of SQL
applications, the number of operators in arithmetic expressions is also included in the calculation.
To calculate the length of a retrieval statement, proceed as follows:
84
–
Count each column whenever it is addressed in the retrieval statement.
–
In the case of SQL applications, count also the operators in arithmetic expressions.
–
In the case of multiple columns, add the number of occurrences addressed in the
retrieval statement.
–
If one or more conditions are attached to one and the same column, add the number of
conditions for this column.
U22418-J-Z125-6-76
DBH options
COLUMNS
In the case of CALL DML, the value calculated corresponds to the area specified in the
COLUMNS option. In the case of SQL DML, the calculated length of the longest retrieval
statement represents a maximum value for the area specified in the COLUMNS option. As
a result of internal optimization, the optimal value can be lower than the calculated value.
Space required to save the temporary work file
The space required to store internal statement formats in the temporary work file depends
on the COLUMNS option. The space required can be seen in the following list (see also the
description of WORK-CONTAINER on page 141f).
COLUMNS =
Space required for storing average internal statement formats
(Kbytes)
Up to 260
28
Up to 325
32
Up to 366
36
Up to 408
40
Up to 449
44
Up to 512
48
Up to 553
52
Up to 594
56
Up to 636
60
Up to 1024
64
Table 15: Space required for storing internal statement formats
U22418-J-Z125-6-76
85
CONFIGURATION-NAME
DBH options
CONFIGURATION-NAME
This statement assigns the DBH to a configuration.
Definition
A lower-level DBH option of DBH-IDENTIFICATION
Function
You use the DBH option CONFIGURATION-NAME to specify the configuration name of the
DBH.
By specifying a configuration name, you assign the DBH to a configuration. Each configuration has a unique name on its host system.
Like the DBH name (see the DBH option DBH-NAME on page 91), the configuration name
identifies the following DBH-specific files: the cursor files and the files for transaction
management. When several SESAM/SQL DBHs are loaded, these files must be uniquely
identified by a configuration name and a DBH name in each case.
If the configuration and/or DBH name have the default value *BLANK, the character “Ë” in
the file names is replaced by the character “@”. For example, if you specify
CONFIGURATION-NAME = 7 and DHB-NAME = *BLANK, the file name of the WA-LOG file
of the independent DBH is:
SESAM7@.WA-LOG
If you specify CONFIGURATION-NAME = 7 and DHB-NAME = 8, the file name of the
WA-LOG file is:
SESAM78.WA-LOG
CONFIGURATION-NAME
= *BLANK / <alphanum-name 1..1>
Operands
CONFIGURATION-NAME = *BLANK
The blank is used as the configuration name.
CONFIGURATION-NAME = <alphanum-name 1..1>
Configuration name assigned by the system administrator.
The characters #, @ and $ are not permitted as configuration name.
86
U22418-J-Z125-6-76
DBH options
CPU-RESOURCES
CPU-RESOURCES
This statement controls the use of CPU resources.
Definition
A higher-level DBH option
Function
CPU-RESOURCES is the higher-level option of DBH options with which you can control the
use of CPU resources.
CPU-RESOURCES
= *STD / *PARAMETERS(...)


DBH-TASKS = 1
,SERVICE-TASKS = *STD
Operands
CPU-RESOURCES = *STD
Default values apply to all the parameters of CPU-RESOURCES. These are described in
the description of the lower-level DBH option SERVICE-TASKS.
CPU-RESOURCES = *PARAMETERS(...)
CPU-RESOURCES has the DBH options DBH-TASKS and SERVICE-TASKS as its
parameter.
U22418-J-Z125-6-76
87
CURSOR-BUFFER
DBH options
CURSOR-BUFFER
This statement sets the size of the cursor buffer.
Definition
A lower-level DBH option of STORAGE SIZE
Function
Cursor files are DBH-specific work files that are available for processing retrieval statements. The DBH stores intermediate results of retrieval statements in them.
Access to internal cursor files is via the cursor buffer, provided it is large enough.
You can use the DBH option CURSOR-BUFFER to set the size of the cursor buffer so as to
minimize the number of accesses to internal cursor files. You specify the size of the cursor
buffer in units of 1 Kbyte.
CURSOR-BUFFER
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


BUFFER-SIZE = *STD / <integer 72..1000000>
,FRAME-SIZE = 4 / <integer 4..32>
Operands
CURSOR-BUFFER = *STD
The default values for the size of the cursor buffer are described under *PARAMETERS(...).
CURSOR-BUFFER = *PARAMETERS(...)
Modifies the cursor buffer settings.
BUFFER-SIZE = *STD / <integer 72..1000000>
Sets the size of the cursor buffer in units of 1 Kbyte.
The default value of CURSOR-BUFFER depends on the maximum permitted number
of concurrent active threads that you specify using the DBH option THREADS and the
number of system threads required. A minimum of 32 Kbytes is required per thread.
If you specify a value for BUFFER-SIZE that is smaller than the product of the minimum
size per thread and the number of threads (THREADS option plus the number of
system threads), then it is rounded up to the minimum size.
88
U22418-J-Z125-6-76
DBH options
CURSOR-BUFFER
FRAME-SIZE = 4 / <integer 4..32>
Sets the size of the cursor buffer frame in units of 1 Kbyte.
The default value is 4. Other valid specifications in the range of <integer 4..32> are
always rounded off to a number that is a multiple of 4.
i
The minimum size of CURSOR-BUFFER per thread depends on the value of
FRAME-SIZE and must be 8 times the value of FRAME-SIZE at all times. If the
user specifies a greater value, then the value specified by the user is applied,
but this value is always rounded off to be a multiple of the value in FRAME-SIZE.
Information on cursor files
The operational statistics of the SESAM/SQL utility SESMON provide useful information on
cursor files.
The “SYSTEM INFORMATION” form displays the number of cursor files that are currently
open (see page 416).
The cursor buffer should be large enough to keep to a minimum the number of times internal
cursor files are accessed. The “I/O” form (see page 403) helps you set the optimum size for
the cursor buffer. It displays the number of logical and physical accesses of the cursor files.
The “Performance” manual describes the cases in which it is advisable to modify the size
of the cursor buffer the next time the DBH starts up.
U22418-J-Z125-6-76
89
DBH-IDENTIFICATION
DBH options
DBH-IDENTIFICATION
This statement names a DBH and assigns it to a configuration.
Definition
A higher-level DBH option
Function
DBH-IDENTIFICATION is the higher-level DBH option for DBH options that allow you to
identify the DBH you want to start rather than any other DBH.
DBH-IDENTIFICATION
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


CONFIGURATION-NAME = *BLANK
,DBH-NAME = *BLANK
Operands
DBH-IDENTIFICATION = *STD
Default values apply to all DBH-IDENTIFICATION parameters. These values are described
under the relevant lower-level options.
DBH-IDENTIFICATION = *PARAMETERS(...)
The DBH-IDENTIFICATION parameters are DBH options. Their operands are described in
each case under the relevant option.
90
U22418-J-Z125-6-76
DBH options
DBH-NAME
DBH-NAME
This statement defines the DBH name.
Definition
A lower-level DBH option of DBH-IDENTIFICATION
Function
You use the DBH option DBH-NAME to define the name of the DBH.
The DBH name indicates that this DBH is to be started rather than any of the other DBHs
belonging to the same configuration.
There cannot be two DBHs with the same DBH name in a single configuration.
You must remember this when you load a number of SESAM/SQL DBHs (independent
DBHs and/or linked-in DBHs). It is always advisable to assign a DBH name other than the
default, even if the DBH is initially to be loaded only once. This prevents collisions when, for
test purposes, for example, another DBH is loaded.
Like the configuration name, the DBH name identifies the cursor files and the files for transaction management. When several SESAM/SQL DBHs are loaded, these files must be
uniquely identified by a configuration name and a DBH name in each case (see the section
on the DBH option CONFIGURATION-NAME on page 86).
If the configuration and/or DBH name has the default value *BLANK, then the character “Ë”
is replaced by the “@” character in the file name (see the DBH option
CONFIGURATION-NAME).
DBH-NAME
= *BLANK / <alphanum-name 1..1>
Operands
DBH-NAME = *BLANK
The blank is used as the DBH name.
DBH-NAME = <alphanum-name 1..1>
DBH name assigned by the system administrator.
The characters #, @ and $ are not permitted as DBH name.
U22418-J-Z125-6-76
91
DBH-TASKS
DBH options
DBH-TASKS
This statement defines the DBH tasks.
Definition
A lower-level DBH option of CPU-RESOURCES
Function
You use the DBH option DBH-TASKS to specify the number of DBH tasks.
After the first DBH task, additional DBH tasks are started via ENTER. All DBH tasks are
assigned the same job class.
In a linked-in DBH the option DBH-TASKS is ignored because this kind of DBH generally
only consists of one TASK.
If a value greater than 1 was specified and SESAM/SQL is only licensed for one task, an
informational message is output stating that the license is only valid for one task and the
DBH can therefore only be started with one task.
DBH-TASKS
= 1 / <integer 1..16>
Operand
DBH-TASKS = 1 / <integer 1..16>
Specifies the number of DBH tasks in a session. The default value is 1.
92
U22418-J-Z125-6-76
DBH options
FILE-RESOURCES
FILE-RESOURCES
This statement specifies settings for files.
Definition
A higher-level DBH option
Function
FILE-RESOURCES is the higher-level option of all DBH options with which you specify
settings for session-specific files.
FILE-RESOURCES
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


,SESSION-LOGGING-ID = *STD
,MEDIA-CATALOG = *STD
Operands
FILE-RESOURCES = *STD
Default values apply to all FILE-RESOURCES parameters. These values are described
under the relevant lower-level DBH options.
FILE-RESOURCES = *PARAMETERS(...)
The FILE-RESOURCES parameters are DBH options. Their operands are described under
the relevant DBH option in each case.
U22418-J-Z125-6-76
93
MEDIA-CATALOG
DBH options
MEDIA-CATALOG
This statement creates a media catalog.
Definition
A lower-level DBH option of FILE-RESOURCES
Function
The media catalog contains storage information for certain DBH-specific files: the transaction log files (TA-LOG files), the restart log file (WA-LOG), the temporary work files and
the cursor files. The media catalog defines the volumes on which these files are to be
stored. The media catalog does not exist in the form of a file. It is kept in the DBH's memory
and is only valid for one DBH session.
The DBH option MEDIA-CATALOG allows you to specify the storage information in the
media catalog.
The DBH does not store this information on the files of the media catalog in the transaction
log file. The information is therefore not failproof. In the event of an external restart, you can,
if required, specify other volumes for media-catalog files.
There are 2 transaction log files (TA-LOG files) in SESAM/SQL V3.0 and higher. The
operand TALOG-SUPPORT applies to both of these files.
i
94
These specifications only have an effect if the corresponding file does not yet exist.
U22418-J-Z125-6-76
DBH options
MEDIA-CATALOG
(part 1 of 2)
MEDIA-CATALOG
= *STD / *PARAMETERS(...)
*PARAMETERS(...)



































TALOG-SUPPORT = *PUBLIC-DISK(...) / *PRIVATE-DISK(...)
*PUBLIC-DISK(...)



CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
*PRIVATE-DISK(...)





CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
,DEVICE-TYPE = <structured-name 1..8>
,VOLUME = list(6): <alphanum-name 1..6>
,WALOG-SUPPORT = *PUBLIC-DISK(...) / *PRIVATE-DISK(...)
*PUBLIC-DISK(...)



CAT-ID = *STD / <cat-id
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
*PRIVATE-DISK(...)





CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
,DEVICE-TYPE = <structured-name 1..8>
,VOLUME = list(6): <alphanum-name 1..6>
,CURSOR-MEDIA = *STD / *PARAMETERS(...)
*PARAMETERS(...)











SUPPORT-1 = *PUBLIC-DISK(...) / *PRIVATE-DISK(...)
*PUBLIC-DISK(...)



CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
*PRIVATE-DISK(...)





CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
,DEVICE-TYPE = <structured-name 1..8>
,VOLUME = list(6): <alphanum-name 1..6>
Continued ➠
U22418-J-Z125-6-76
95
MEDIA-CATALOG
DBH options
(part 2 of 2)






















, SUPPORT-5 = *PUBLIC-DISK(...) / *PRIVATE-DISK(...)
*PUBLIC-DISK(...)



CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
*PRIVATE-DISK(...)





CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 0..32767>
,DEVICE-TYPE = <structured-name 1..8>
,VOLUME = list(6): <alphanum-name 1..6>
Operands
MEDIA-CATALOG = *STD
All the files in the media catalog are created on a public disk.
MEDIA-CATALOG = *PARAMETERS(...)
TALOG-SUPPORT =
Defines the volume for the TA-LOG files.
There are a total of two TA-LOG files (TA-LOG1, TA-LOG2) that are written to one after
the other in rotation.
TALOG-SUPPORT = PUBLIC DISK(...)
Causes the TA-LOG files to be created on a public disk.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the files are to be stored. The default is the DBH
catalog ID.
PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
Number of PAM pages for the initial allocation of space.
The specified number of PAM pages is reserved immediately. It should correspond
to the expected file size. The DBH calculates the default value internally. If you enter
a value lower than the calculated default, the DBH uses the default.
SECONDARY-ALLOCATION = *STD / <integer 0..32767>
Number of PAM pages for subsequent extensions to the file.
The DBH calculates the default internally. If you enter a value lower than the calculated default, the DBH uses the default.
96
U22418-J-Z125-6-76
DBH options
MEDIA-CATALOG
TALOG-SUPPORT = *PRIVATE DISK(...)
The TA-LOG files are to be created on a private disk. You must specify the device type
by making an entry for DEVICE-TYPE.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the files are to be stored. The default is the DBH
catalog ID.
PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
Number of PAM pages for the initial allocation of space.
The specified number of PAM pages is reserved immediately. It should correspond
to the expected file size.
The DBH calculates the default value internally. If you enter a value lower than the
calculated default, the DBH uses the default.
SECONDARY ALLOCATION = *STD / <integer 0..32767>
Number of PAM pages for subsequent extensions to the file.
The DBH calculates the default value internally. If you enter a value lower than the
calculated default, the DBH uses the default.
DEVICE-TYPE = <structured-name 1..8>
BS2000 device type to which the required disks are allocated.
If you make an incorrect entry, the DBH aborts the start procedure.
VOLUME = list(6): <alphanum-name 1..6>
VSNs of the disks on which the files are to be created. Up to 6 VSNs are permitted.
You can specify each VSN only once. VOLUME is not evaluated unless the DEVICE
parameter is specified.
WALOG-SUPPORT =
Defines the volume for the WA-LOG file.
The operands are identical to those in the operand descriptions for TA-LOG-SUPPORT.
CURSOR-MEDIA =
Defines the volume for cursor files.
Files that have been created are reused when they are unlocked. This applies both to
internal cursor files and CALL DML-specific cursor files.
CURSOR-MEDIA = *STD
The DBH creates the cursor files on a public disk.
U22418-J-Z125-6-76
97
MEDIA-CATALOG
DBH options
CURSOR-MEDIA = *PARAMETERS(...)
SUPPORT-n =
n = 1...5
You can define the volumes for the two cursor files SESAMkn.CURSOR.0001 and
SESAMkn.CURSOR.0002 (or for the linked-in DBHs SESLKkn.CURSOR.0001 and
SESLKkn.CURSOR.0002) yourself. Up to five different specifications are permitted
(SUPPORT-1... SUPPORT-5).
SESAM/SQL creates a maximum of two cursor files.
The values entered for SUPPORT-1 determine which medium the first required
cursor file with the suffix “0001” or “0002” will be created on.
The values entered for SUPPORT-2 determine which medium the second required
cursor file with the suffix “0001” or “0002” will be created on.
The values entered for SUPPORT-3 to SUPPORT-5 are evaluated only if the media
specified for SUPPORT-1 or SUPPORT-2 are not available or if there is insufficient
space.
The media are used in the specified order. The operands are identical with those in
the operand description for TA-LOG-SUPPORT.
After the entry with number 5 has been used, the cycle begins again with 1 if 1 has
not yet been attempted for this file.
98
U22418-J-Z125-6-76
DBH options
MSG-OUTPUT
MSG-OUTPUT
This statement controls the outputs of the DBH.
Definition
A lower-level DBH option of ADMINISTRATION
Function
You can use the DBH option MSG-OUTPUT to request SESAM/SQL DBH outputs to
SYSOUT or the console of the BS2000 system administrator or to SYSLST. Specific output
can be suppressed.
You can completely suppress OPEN and CLOSE messages for logical files.
When using the linked-in DBH, it can be a good idea to request that DBH outputs only be
written to SYSOUT so that outputs of the application program to SYSLST are not interspersed with DBH outputs.
Consistency checks and the end-of-program message are always output to the console and
cannot be suppressed.
MSG-OUTPUT
= *STD / *ALL / *PARAMETERS(...)
*PARAMETERS(...)


MSG = *ALL / list-(2): *SYSOUT / *SYSLST
,OPEN-CLOSE-MSG = *NONE / *ALL / list(2): *SYSOUT / *SYSLST
Operands
MSG-OUTPUT = *STD
The DBH output, except for OPEN and CLOSE messages, is sent to SYSOUT or the
console and SYSLST. OPEN and CLOSE messages are completely suppressed.
This default setting always applies during the initialization of the DBH or until completion of
an external restart. DBH output cannot be redirected during this time.
This corresponds to specifying
MSG-OUTPUT=*PARAMETERS(MSG=*ALL,OPEN-CLOSE-MSG=*NONE).
U22418-J-Z125-6-76
99
MSG-OUTPUT
DBH options
MSG-OUTPUT = *ALL
The DBH output, except for OPEN and CLOSE messages, is sent to SYSOUT or the
console and SYSLST.
This corresponds to specifying
MSG-OUTPUT=*PARAMETERS(MSG=*ALL, OPEN-CLOSE-MSG=*ALL).
MSG-OUTPUT = *PARAMETERS(...)
MSG =
Controls the output of messages.
MSG = *ALL
The DBH output, except for OPEN and CLOSE messages, is sent to SYSOUT or the
console and SYSLST.
MSG = list(2): *SYSOUT / *SYSLST
The DBH output, except for OPEN and CLOSE messages, is sent to SYSOUT or the
console or SYSLST. Output sent to an unspecified destination is suppressed.
OPEN-CLOSE-MSG =
The output of OPEN and CLOSE messages from SES1001, SES1011, SES1201,
SES2015 and SES2023 can be partly or completely suppressed within the framework
defined by the MSG= parameter.
OPEN and CLOSE messages for databases are not affected by this.
OPEN-CLOSE-MSG = *NONE
This is the default. Suppresses OPEN and CLOSE messages completely.
OPEN-CLOSE-MSG = *ALL
The DBH outputs the OPEN and CLOSE messages as specified by the MSG=
parameter.
OPEN-CLOSE-MSG = list(2): *SYSOUT / *SYSLST
The DBH outputs OPEN and CLOSE messages only to SYSOUT or SYSLST, provided
the parameter MSG= permits it.
i
100
When running in the batch mode, the DBH output is sent to the console when
*SYSOUT is specified.
U22418-J-Z125-6-76
DBH options
MSG-OUTPUT
Example
If OPEN and CLOSE messages are only to be output to *SYSLST, the DBH option could
contain the following values:
MSG-OUTPUT=*PARAMETERS(MSG=*ALL,OPEN-CLOSE-MSG=*SYSLST)
Within the framework defined by MSG=*ALL, it is possible to restrict the output of OPEN
and CLOSE messages to *SYSLST.
Output of OPEN and CLOSE messages to *SYSLST is not possible if the DBH option
contains the following values:
MSG-OUTPUT=*PARAMETERS(MSG=*SYSOUT,OPEN-CLOSE-MSG=*SYSLST)
In this case, MSG=*SYSOUT defines a framework that does not permit output to
SYSLST.
U22418-J-Z125-6-76
101
OLD-TABLE-CATALOG
DBH options
OLD-TABLE-CATALOG
This statement limits the number of entries in the CALL DML table catalog.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
You use the DBH option OLD-TABLE-CATALOG to specify the maximum number of entries
permitted in the CALL DML table catalog.
You edit the CALL DML table catalog using the DBH start statement ADD-OLD-TABLECATALOG-LIST (see page 73). You can enter as many CALL DML tables in the catalog as
specified by the DBH option OLD-TABLE-CATALOG.
You can also enter fewer tables. During the DBH session you can use an administration
statement to enter more CALL DML tables, as required, up to the maximum number of
permitted entries.
OLD-TABLE-CATALOG
= 0 / <integer 0..254>
Operand
OLD-TABLE-CATALOG = 0 / <integer 0..254>
Maximum number of table entries in the CALL DML table catalog.
The default is 0. This means that CALL DML tables cannot be edited during the DBH
session. However, you can enter a different value and permit up to 254 entries for CALL
DML tables.
102
U22418-J-Z125-6-76
DBH options
REQUEST-CONTROL
REQUEST-CONTROL
This statement activates priority control for the independent DBH.
Definition
A lower-level DBH option of SYSTEM-STRATEGIES
Function
You use the DBH option REQUEST-CONTROL to specify whether the independent DBH is
to work with priority control. You can also modify the default values for priority control.
Priority control is not effective with the linked-in DBH.
During a DBH session, requests from tasks with different BS2000 priorities usually have to
be processed concurrently. The DBH processes the individual requests in accordance with
their BS2000 priority in the order in which they arrive.
The priority control of the independent DBH allows you to qualify the BS2000 priority for
requests and modify it to suit the requirements of the DBH session. To do this, you subdivide
the whole range of BS2000 priorities into three priority classes: Queue-1, Queue-2 and
Queue-3. By assigning a weight to each priority class, you can influence the speed at which
the requests of the different classes are processed.
The assignment of a request to the DBH priority classes is based on the request's BS2000
priority.
The priority classes are defined as follows:
Queue-1:
30 Î BS2000 priority of the request < LOW-LEVEL
Queue-2:
LOW-LEVEL Î BS2000 priority of the request < HIGH-LEVEL
Queue-3:
HIGH-LEVEL Î BS2000 priority of the request Î 255
The highest priority (30) and the lowest priority (255) represent the limits between which the
three priority classes for requests to the DBH are spread. LOW-LEVEL and HIGH-LEVEL
values define the limits between Queue-1 and Queue-2 and between Queue-2 and
Queue-3. Their default values are 180 and 240. You can modify them using the DBH option
REQUEST-CONTROL.
During processing the requests are deactivated internally after N logical block accesses
according to their priority class. N is set according to the priority class weighting. This allows
requests with a higher weighting to be processed faster than requests with a lower
weighting.
U22418-J-Z125-6-76
103
REQUEST-CONTROL
DBH options
REQUEST-CONTROL
= *NONE / *STD / *PARAMETERS(...)
*PARAMETERS(...)
,QUEUE-PRIORITY = *PARAMETERS(...)
*PARAMETERS(...)



QUEUE-1 = 3 / <integer 1..99>
,QUEUE-2 = 2 / <integer 1..99>
,QUEUE-3 = 1 / <integer 1..99>
,QUEUE-RANGE = *PARAMETERS(...)
*PARAMETERS(...)


LOW-LEVEL = 180 / <integer 30..255>
,HIGH-LEVEL = 240 / <integer 30..255>
Operands
REQUEST-CONTROL = *NONE
Priority control is not activated. This is the default when the DBH starts up.
REQUEST-CONTROL = STD
Activates priority control for the independent DBH. Default values apply to the various
priority-control parameters. These defaults are described under *PARAMETERS(...).
During the DBH session, you can turn priority control on or off using the appropriate administration statement (see page 254).
REQUEST-CONTROL = *PARAMETERS(...)
QUEUE-PRIORITY = *PARAMETERS(...)
Specifies the weights for the different priority classes. You can also change the weights
subsequently using an administration statement (see page 254).
QUEUE-1 = 3 / <integer 1..99>
Specifies the weight for the first priority class, Queue-1. The default weight is 3.
QUEUE-2 = 2 / <integer 1..99>
Specifies the weight for the second priority class, Queue-2. The default weight is 2.
QUEUE-3 = 1 / <integer 1..99>
Specifies the weight for the third priority class, Queue-3. The default weight is 1.
104
U22418-J-Z125-6-76
DBH options
REQUEST-CONTROL
QUEUE-RANGE = *PARAMETERS(...)
Specifies the limit values between the priority classes Queue-1 and Queue-2 or
Queue-2 and Queue-3.
You can modify the limit values during the DBH session using the appropriate administration statement (see page 254).
LOW-LEVEL = 180 / <integer 30..255>
Specifies the limit value between the first and second priority classes, Queue-1 and
Queue-2. The LOW-LEVEL value must be lower than the HIGH-LEVEL value. The
default for LOW-LEVEL is 180.
HIGH-LEVEL = 240 / <integer 30..255>
Specifies the limit value between the second and third priority classes, Queue-2 and
Queue-3. The HIGH-LEVEL value must be higher than the LOW-LEVEL value. The
default for HIGH-LEVEL is 240.
Considerations when assigning weights
In order to achieve optimal weight assignment for the priority classes, you should ask the
following questions:
–
How many users of each priority class are working concurrently?
–
Which priority class is to receive preferential treatment, and which requests hinder it?
–
Is the load distribution dependent on the time of day or date? Must the weighting be
changed at specific times?
You should take the answers to these questions into consideration when assigning the
weights.
If the load distribution shifts dramatically and unforseeably, you can change the weights
dynamically using appropriate administration statements (see page 254).
U22418-J-Z125-6-76
105
RESTART-CONTROL
DBH options
RESTART-CONTROL
This statement controls how long it takes until the DBH becomes available in the event of a
restart.
Definition
A lower-level DBH option of SYSTEM-STRATEGIES
Function
You can use the DBH option RESTART-CONTROL to optimize the time it takes for the DBH
to become available again after a system failure. You will find general information on
restarting in the section “Restarting a DBH session” on page 53.
You can influence how long a restart takes in two different ways:
–
The BUFFER-LIMIT and TALOG-LIMIT parameters affect the frequency of write
accesses to the database. The lower the values for BUFFER-LIMIT and TALOG-LIMIT,
the more afterimages are written to the database during operation. This reduces the
time required for physical repair in the event of a restart. However, if very low values are
selected, the increased number of read and write accesses during normal operation
lead to loss of performance. It therefore makes sense to monitor the number of
accesses in the “I/O” DBH form of the SESAM/SQL utility SESMON (see page 403). If
necessary, you can adjust the values of the parameters during the DBH session by
means of the MODIFY-RESTART-CONTROL administration statement (see page 256).
–
LOGICAL-ROLLBACK allows you to delay the logical reset until the start of normal
operation. The transactions that were open when the system failed are thus not reset
until after the restart. This reduces the time required until the system is available again.
RESTART-CONTROL
= *STD / *PARAMETERS(...)
*PARAMETERS(...)






106
BUFFER-LIMIT= *PARAMETERS(...)
*PARAMETERS(...)


SYSTEM-DATA-BUFFER = 50 / <integer 10..90>
,USER-DATA-BUFFER = 50 / <integer 10..90>
,TALOG-LIMIT = 512 / <integer 128..524288>
,LOGICAL-ROLLBACK = *IMMEDIATELY / *DELAYED
U22418-J-Z125-6-76
DBH options
RESTART-CONTROL
Operands
RESTART-CONTROL = *STD
The default values are used. The default values are described under *PARAMETERS.
RESTART-CONTROL = *PARAMETERS(...)
You can change the values set for BUFFER-LIMIT and TALOG-LIMIT to suit requirements
during the DBH session by means of the MODIFY-RESTART-CONTROL administration
statement (see page 256). You must specify the BUFFER-LIMIT and TALOG-LIMIT parameters before a system crash. Specifying them at the time of the external restart has no
effect. The LOGICAL-ROLLBACK parameter, on the other hand, is evaluated at the restart.
It can therefore also be set immediately before an external restart.
BUFFER-LIMIT = *PARAMETERS(...)
These parameters specify the limit as a percentage for the occupation of the two buffers
by writable blocks. As of this limit, the buffers are written to the database.
SYSTEM-DATA-BUFFER = 50 / <integer 10..90>
Specifies a percentage limit for the writing of afterimages to the database for system
access data. If the share of the total buffer space occupied by the buffers to be
written exceeds the percentage specified for SYSTEM-DATA-BUFFER, afterimages
are written to the database.
USER-DATA-BUFFER = 50 / <integer 10..90>
Specifies a percentage limit for the writing of afterimages to the database for user
data. If the share of the total buffer space occupied by the buffers to be written
exceeds the percentage specified for USER-DATA-BUFFER, afterimages are
written to the database.
TALOG-LIMIT = 512 / <integer 128..524288>
Specifies the upper limit for the part of the TA-LOG file taken up by afterimages. In the
event of physical repair, this part of the TA-LOG file must be read. If its size exceeds the
specified limit, the afterimages are written to the database. TALOG-LIMIT is specified
in units of 4 Kbytes.
LOGICAL-ROLLBACK =
Influences the time at which transactions are logically reset in the event of a restart.
LOGICAL-ROLLBACK = *IMMEDIATELY
As in SESAM/SQL V3.0, the transactions are reset before the resumption of normal
operation.
U22418-J-Z125-6-76
107
RESTART-CONTROL
DBH options
LOGICAL-ROLLBACK = *DELAYED
Delays transaction resetting until the resumption of normal operation. This reduces the
time required until the system becomes available again. However, if too many updates
have to be performed at the beginning of normal operation, this can result in loss of
performance and the growth in size of the TA-LOG file. In certain cases, delaying the
logical reset is not effective (see the section “Controlling the duration of the restart” on
page 55).
The LOGICAL-ROLLBACK parameter cannot be changed during DBH operation.
108
U22418-J-Z125-6-76
DBH options
RETRIEVAL-CONTROL
RETRIEVAL-CONTROL
This statement influences the processing strategy of the DBH.
Definition
A lower-level DBH option of SYSTEM-STRATEGIES
Function
The DBH option RETRIEVAL-CONTROL allows you to influence the processing strategy of
the DBH.
In a sequential search, the RETRIEVAL-CONTROL option causes the DBH under certain
conditions to divide the processing of retrieval statements into sections, and interrupt or
even completely abort them. Interrupted retrieval statements are placed in a queue until
processing continues. The tasks that are released during the interrupts or after being
aborted become available for other requests.
If the search involves secondary indexes, RETRIEVAL-CONTROL causes the DBH to
continue the search sequentially when it is appropriate in view of the set of records
expected to be found. The DBH can then interrupt or abort the sequential processing, as
described above.
RETRIEVAL-CONTROL
= *STD / *PARAMETERS(...)
*PARAMETERS(...)





U22418-J-Z125-6-76
INTERRUPT-EXECUTION = *PARAMETERS(...)
*PARAMETERS(...)


USER-DATA-ACCESS = 1000 / <integer 1..2147483647>
,INDEX-EVALUATION = 2147483647 / <integer 16..2147483647>
,ABORT-EXECUTION = 2000 / <integer 1.. 2147483647>
109
RETRIEVAL-CONTROL
DBH options
Operands
RETRIEVAL-CONTROL = *STD
The search strategy of the DBH changes in the case of retrieval statements that take a long
time to process. Under what conditions and how the search strategy is influenced is defined
by default values. These are described under *PARAMETERS.
RETRIEVAL-CONTROL = *PARAMETERS(...)
INTERRUPT-EXECUTION = *PARAMETERS(...)
Under certain conditions, the DBH interrupts the processing of retrieval statements that
take a long time to process.
USER-DATA-ACCESS = 1000 / <integer 1..2147483647>
Sequential processing is divided into sections if the number of logical accesses of
blocks of user data exceeds a defined limit value. Processing is interrupted on
completion of each section. The default for this limit value is 1000.
If necessary, you can change the value specified here during the DBH session by
means of the MODIFY-RETRIEVAL-CONTROL administration statement.
INDEX-EVALUATION = 99999999 / <integer 16..2147483647>
Processing with secondary indexes is continued sequentially if the set of records
expected to be found exceeds a defined limit value. The default for this limit value is
99,999,999.
Based on the statistical data kept for each column or attribute, the DBH determines
the set of records expected to be found for the subquestion processed first.
If the set of records found exceeds the limit value, the DBH continues sequential
processing. As of this point, the processing strategy of the DBH follows the rules for
sequential processing.
If the set of records found does not exceed the limit value, the DBH processes
further subquestions using secondary indexes.
If necessary, you can change the value specified here during the DBH session by
means of the MODIFY-RETRIEVAL-CONTROL administration statement (see
page 258).
ABORT-EXECUTION = 2000 / <integer 1.. 2147483647>
Sequential processing is aborted completely when the number of failed logical
accesses of user data exceeds a defined limit value. The default limit value is 2000.
If necessary, you can change the value specified here during the DBH session by
means of the MODIFY-RETRIEVAL-CONTROL administration statement.
It can also be changed in relation to a request with the pragma LIMIT
ABORT_EXECUTION <integer 1.. 2147483647>, see the “SQL Reference Manual Part
1: SQL Statements”, section “Pragmas”.
110
U22418-J-Z125-6-76
DBH options
SECURITY
SECURITY
This statement prevents unauthorized access and controls SAT logging.
Definition
A lower-level DBH option of ADMINISTRATION
Function
CALL DML tables can be protected by password.
Security relevant events can be logged with SAT.
You can use the DBH option SECURITY to specify the following for users who are working
in the interactive mode:
–
how many password violations a CALL DML user can commit
–
whether security relevant events are to be logged with SAT
If a user exceeds the specified number of permitted violations, he or she is prevented from
sending any further requests to the DBH during this DBH session. The system administrator
can use the RELEASE-USER-RESOURCES administration statement to reset the user's
resources and lift the lock (see page 268).
If a CALL DML user has already opened a logical file, it is not necessary for the system
administrator to lift the lock. The CALL DML can carry out a user-close and subsequently
work with the DBH again. If the user-close is carried out during a transaction, the user
cannot send any more requests to the DBH until after the end-of-transaction statement.
SECURITY
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


U22418-J-Z125-6-76
PRIVILEGE-VIOLATIONS = 10 / <integer 1..99>
,SAT-SUPPORT = *OFF / *ON
111
SECURITY
DBH options
Operands
SECURITY = *STD
The standard values are used. The standard values are described in *PARAMETERS.
SECURITY = *PARAMETERS(...)
PRIVILEGE-VIOLATIONS = 10 / <integer 1..99>
The number of attempts permitted to an SQL user to access a table or the number of
permitted password violations in the case of CALL DML OPEN statements.
The default value for PRIVILEGE-VIOLATIONS is 10 (for users working in the interactive mode).
With application programs in batch mode, only one password violation or access
attempt is permitted.
SAT-SUPPORT = *OFF / *ON
Controls the SAT logging. In the case of SAT-SUPPORT=*ON security relevant events
are transmitted to SAT for logging. See also the “Core Manual“, section “Logging of
security relevant events with SAT”.
112
U22418-J-Z125-6-76
DBH options
SERVICE-TASKS
SERVICE-TASKS
This statement specifies the number of tasks for service requests.
Definition
A lower-level option of CPU-RESOURCES
Function
CPU-intensive activities, such as the sorting of intermediate results and some utility
functions, can last a very long time. To avoid being blocked during this time, the
SESAM/SQL DBH can relocate these CPU-intensive activities as separate tasks, which are
then available for service requests.
At the end of the session, the DBH terminates all service tasks. Service requests that are
still open or running are aborted.
You use the DBH option SERVICE-TASKS to specify how many service tasks are to be
available at the beginning of the DBH session and the maximum number of service tasks
that can be started in the course of the session.
You can also specify whether the DBH is to use the multitask sorting facility of the software
product SORT.
i
U22418-J-Z125-6-76
To ensure that the service tasks can also be started, the following points must be
observed:
–
There must be no read password to the module library from which SESAM/SQL
is started.
–
When SESAM/SQL is started, no temporary file must be used as a module
library.
–
The module library must be available for the entire duration of the DBH session.
–
All files assigned with the link name BLSLIBnn, where nn = 00 to 99, when
SESAM/SQL is started must be accessible for the entire duration of the DBH
session.
113
SERVICE-TASKS
DBH options
SERVICE-TASKS
= *STD / *PARAMETERS(...)
*PARAMETERS(...)















INITIAL = 1 / <integer 0..32>
,MAXIMUM = *STD / <integer 0..64>
,JOBCLASS = *STD / *DBH-JOBCLASS / <name 1..8>
,WORK-FILES = *PUBLIC-DISK(...) / *PRIVATE-DISK(...)
*PUBLIC-DISK(...)



CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 1..32767>
*PRIVATE-DISK(...)





CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
,SECONDARY-ALLOCATION = *STD / <integer 1..32767>
,DEVICE-TYPE = <structured-name 1..8>
,VOLUME = list(6):<alphanum-name 1..6>
,RECORDS-PER-CYCLE = *STD / <integer 1..2147483647>
Operands
SERVICE-TASKS = *STD
The number of service tasks is determined by default values. These are described under
*PARAMETERS.
SERVICE-TASKS = *PARAMETERS(...)
INITIAL = 1 / <integer 0..32>
Number of service tasks started at the beginning of the DBH session. The default value
for INITIAL is 1, which means that when the DBH is loaded, at least one service task is
started and immediately available for service requests. When using the linked-in DBH,
no more than one service task can be started.
114
U22418-J-Z125-6-76
DBH options
SERVICE-TASKS
MAXIMUM = *STD / <integer 0..64>
Maximum number of service tasks that can be started during the DBH session.
The default value for MAXIMUM is the greater of the following two values (with a
maximum of 64):
1. the maximum number of concurrent active threads, specified by means of the DBH
option THREADS (see page 133)
2. the value assigned to the INITIAL parameter
– In the case of the independent DBH, note the following:
if you enter 0 for MAXIMUM, this value is automatically set to 1. If you specify a
value for MAXIMUM that is greater than 0 but less than that for INITIAL, you
receive an error message.
– In the case of a linked-in DBH, note the following:
no more than one service task is started, even if you specify a value greater than
1 for MAXIMUM. If you specify MAXIMUM = 0, no service task is started. In this
case, the DBH can carry out the sorting of intermediate result sets as a
subroutine in its own task. Other service requests, such as the utility statements
COPY, LOAD and RECOVER, are rejected.
JOBCLASS = *STD / <name 1..8>
Name of the BS2000 job class.
The batch job is to run in the default job class or in a job class that you specify after
making your selection.
The default job class is the default for batch jobs of the DBH user ID. It is taken from the
JOIN entry of the ID.
JOBCLASS = *DBH-JOBCLASS
The name of the BS2000 job class is the job class of the DBH when the service task is
started as long as the DBH is started as a batch job. In the interactive mode, a
*DBH-JOBCLASS specification is ignored and processed just like for
JOBCLASS=*STD.
WORK-FILES =
Temporary SORT work files created in a service task are created before each sort run
and deleted after it.
WORK-FILES = *PUBLIC-DISK(...)
Temporary SORT work files are stored on a public disk.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the temporary SORT work files are to be stored.
The default is the DBH catalog ID.
U22418-J-Z125-6-76
115
SERVICE-TASKS
DBH options
PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
Number of PAM pages for the initial assignment of storage space.
The default is 120.
SECONDARY-ALLOCATION = *STD / <integer 1..32767>
Number of PAM pages for subsequent file extensions. The default is 120.
WORK-FILES = *PRIVATE-DISK(...)
Temporary SORT work files are stored on a private disk.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the temporary SORT work files are to be stored.
The default is the DBH catalog ID.
PRIMARY-ALLOCATION = *STD / <integer 1..16777215>
Number of PAM pages for the initial assignment of storage space.
The default is 120.
SECONDARY-ALLOCATION = *STD / <integer 1..32767>
Number of PAM pages for subsequent file extensions. The default is 120.
DEVICE-TYPE = <structured-name 1..8>
BS2000 device type to which the required disks are assigned. If you make an
incorrect entry in interactive mode, the system requests you to enter DEVICE-TYPE
again (see the BS2000 manual “Commands, Volumes 1 - 5” , device type table).
VOLUME = list(6): <alphanum-name 1..6>
VSNs of the disks on which the file is to be set up. Up to 6 VSNs are permitted, each
of which can be specified only once. VOLUME is not evaluated unless the DEVICE
parameter is specified.
RECORDS-PER-CYCLE = *STD / <integer 1..2147483647>
Number of records to be sorted per cycle by a sort subtask during multitask sorting.
SESAM/SQL passes this value to the BS2000 utility SORT in the CYCLE parameter
(see also the SORT manual “SDF Format”). The “Performance” manual describes the
criteria on the basis of which the RECORDS-PER-CYCLE value should be assigned.
The total number of records to be sorted divided by CYCLE is the optimal number of
work files to be created. However, no more than 9 temporary work files can be created.
The number of work files determines the number of sort subtasks started by the SORT
utility (number of sort subtasks = number of work files minus 1). In single-task sorting,
work files are not created unless one of the following parameters is specified:
CAT-ID, PRIMARY-ALLOCATION or DEVICE-TYPE.
*STD means that the DBH does not use the multitask sorting facility.
Information on service tasks
The SESAM/SQL utility SESMON provides information in its “SERVICE TASKS” form on
the utilization of the service tasks in the current session (see page 409).
116
U22418-J-Z125-6-76
DBH options
SESSION-LOGGING-ID
SESSION-LOGGING-ID
This statement identifies session-specific log files.
Definition
A lower-level DBH option of FILE-RESOURCES
Function
The session-specific log file CO-LOG contains in its name a session identification whose
default is the BS2000 task sequence number (TSN). The CO-LOG file is also identified by
a file counter whose default value at the beginning of the DBH session is 1. The default file
name of the request log file (CO-LOG), for example, is SESAM.CO-LOG.ssss.iiii, where ssss
stands for the session identification and iiii for the initial value of the file counter.
The DBH option SESSION-LOGGING-ID allows you to specify different values for the
session identification and the initial file-counter value.
SESSION-LOGGING-ID
= *STD / PARAMETERS(...)
*PARAMETERS(...)


U22418-J-Z125-6-76
SESSION-ID = *STD / <alphanum-name 4..4>
,START-NUMBER = 0001 / <integer 1..9999>
117
SESSION-LOGGING-ID
DBH options
Operands
SESSION-LOGGING-ID = *STD
The session identification and file counter have default values. These are described under
*PARAMETERS(...).
SESSION-LOGGING-ID = PARAMETERS(...)
SESSION-ID =
Specifies the session identification for the CO-LOG file.
SESSION-ID = *STD
The default value for the session identification corresponds to the BS2000 task
sequence number (TSN).
SESSION-ID = <alphanum-name 4..4>
Session identification that you yourself can specify.
START-NUMBER =
Specifies the initial value of the file counter for the CO-LOG file.
START-NUMBER = 0001
Sets the file counter to the default value of 1 at the beginning of the DBH session.
START-NUMBER = <integer 1..9999>
Initial file-counter value that you yourself can specify.
The four-digit value is used in filenames (e.g. 0003).
118
U22418-J-Z125-6-76
DBH options
SET-DBH-OPTIONS
SET-DBH-OPTIONS
This statement causes the DBH options to be read in.
Definition
The first DBH start statement
Function
The DBH start statement SET-DBH-OPTIONS causes the DBH options to be read in and
initiates the parametrization of the DBH.
SET-DBH-OPTIONS is the first start statement you have to enter. You can follow it with the
END statement, which concludes input of the DBH start statements.
Do not enter the END statement after SET-DBH-OPTIONS if you want to enter another start
statement.
You can enter the SET-DBH-OPTIONS statement only once at each DBH startup.
SET-DBH-OPTIONS
DBH-IDENTIFICATION=*STD/*PARAMETERS(...)
,ADMINISTRATION=*STD/*PARAMETERS(...)
,SYSTEM-LIMITS=*STD/*PARAMETERS(...)
,FILE-RESOURCES=*STD/*PARAMETERS(...)
,CPU-RESOURCES=*STD/*PARAMETERS(...)
,STORAGE-SIZE=*STD/*PARAMETERS(...)
,SYSTEM-STRATEGIES=*STD/*PARAMETERS(...)
Operands
The operands of the DBH start statement SET-DBH-OPTIONS are higher-level DBH
options. If you do not want to use the defaults, enter the relevant higher-level DBH options
here with the values you want to use for the lower-level DBH options.
The DBH options are described in detail in this reference section. You will find a brief
description of the DBH options as of page 66.
U22418-J-Z125-6-76
119
SPACES
DBH options
SPACES
This statement specifies the number of simultaneously accessible spaces.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
A space is a BS2000 file. Each database has one catalog space, which contains the
metadata with the database schemas, and up to 199 user spaces, in which tables and
indexes are stored.
You use the DBH option SPACES to specify the total number of spaces to be concurrently
accessible during the DBH session. It does not matter whether or not the spaces really are
accessed. If database A consists of 10 spaces, for example, you have to specify a value
Ï 10 for the SPACES option even if only 5 spaces are accessed concurrently in this case.
Note that the number of simultaneously accessible spaces affects the number of possible
CREATE SPACE statements.
SPACES
= *STD / <integer 1..50800>
Operands
SPACES = *STD / <integer 1..50800>
Specifies the maximum number of simultaneously accessible spaces during the DBH
session.
The default for SPACES depends on the maximum number of entries the SQL database
catalog can contain (see the DBH option SQL-DATABASE-CATALOG on page 122).
It is 10 times the value of SQL-DATABASE-CATALOG.
The maximum value for SPACES is 200 times the value of SQL-DATABASE-CATALOG,
since a database can contain a maximum of 200 spaces.
If a value < 2 ∗ (DBH option SQL-DATABASE-CATALOG) is specified, it is corrected
automatically to 2 ∗ (DBH option SQL-DATABASE-CATALOG).
120
U22418-J-Z125-6-76
DBH options
SPACES
Information on the number of space accesses
You obtain information on the total number of space accesses during the DBH session from
the “I/O” form of the SESAM/SQL monitor SESMON (see page 403). SESCOSP, which
permits the evaluation of request logging (see page 341ff), also provides information on the
number of times individual spaces are accessed.
U22418-J-Z125-6-76
121
SQL-DATABASE-CATALOG
DBH options
SQL-DATABASE-CATALOG
This statement limits the number of entries in the SQL database catalog.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
You use the DBH option SQL-DATABASE-CATALOG to specify the maximum number of
entries the SQL database catalog can contain.
You edit the SQL database catalog by means of the DBH start statement ADD-SQLDATABASE-CATALOG-LIST (see page 76). You cannot enter more databases in the
catalog than specified in the DBH option SQL-DATABASE-CATALOG, but you can enter
fewer. If more databases are required during the DBH session, you can enter them using
the appropriate administration statement until the maximum permissible number of entries
is reached.
SQL-DATABASE-CATALOG
= 1 / <integer 1..254>
Operands
SQL-DATABASE-CATALOG = 1 / <integer 1..254>
Maximum number of database entries in the SQL database catalog. The default is 1, but
the SESAM/SQL DBH can handle up to 254 databases simultaneously.
i
122
Note that a free entry in the SQL database catalog is required for each CREATE
CATALOG and each CREATE REPLICATION statement.
U22418-J-Z125-6-76
DBH options
SQL-SUPPORT
SQL-SUPPORT
This statement supports the SQL interface and specifies limit values.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
You use the DBH option SQL-SUPPORT to specify whether the DBH is to support the SQL
interface. If necessary, you can also specify limit values for important SQL-specific
resources.
If the DBH supports the SQL interface, users can use both CALL DML statements and SQL
and utility statements, provided that transaction management is activated
(see the DBH option TRANSACTION-SECURITY on page 134).
SQL-SUPPORT
= *YES(...) / *NO
*YES(...)




INACTIVITY-TIME = 0 / <integer 0..999>
,CURSORS = 70 / <integer 0..262143>
,INTERNAL-SORT-LIMIT = 200 / <integer 1..2147483647>
,PLANS = 70 / <integer 1..999999>
Operands
SQL-SUPPORT = *YES(...)
INACTIVITY-TIME = 0 / <integer 0..999>
Maximum permitted inactivity time in minutes at the DBH's inactivity check. The
inactivity time is the time during which an SQL conversation does not have a transaction
open. If the inactivity time exceeds the specified limit value, the resources of the SQL
conversation are reset when there is a bottleneck.
The default value for INACTIVITY-TIME is 0; i.e. an inactivity check is not carried out,
and inactive conversations are not eliminated.
You can modify the permissible inactivity time to suit requirements during the DBH
session using the SET-USER-INACTIVE-TIME administration statement (see
page 303).
U22418-J-Z125-6-76
123
SQL-SUPPORT
DBH options
CURSORS = 70 / <integer 0..262143>
Number of concurrent cursors that can be declared in the DBH session.
INTERNAL-SORT-LIMIT = 200 / <integer 1..2147483647>
Maximum number of records that a cursor table can contain if the records are to be
sorted in accordance with the cursor declaration.
If the number of records found during sorting exceeds the specified limit value,
processing of the statement is aborted.
You can modify the value of INTERNAL-SORT-LIMIT to suit requirements during the
DBH session using the MODIFY-SQL-SORT-LIMIT administration statement (see
page 260).
PLANS = 70 / <integer 1..999999>
Minimum number of concurrently available SQL access plans.
SQL-SUPPORT = *NO
The DBH does not support the SQL interface. As a result, the DBH does not require so
many Mbytes of virtual address space.
You cannot specify SQL-SUPPORT=*NO unless only CALL DML applications are to run in
the DBH session. Utility statements are not permitted in this session either.
Size of the plan buffer
The plan buffer is an area of main memory reserved by the DBH exclusively for SQL access
plans.
The size of the plan buffer depends essentially on the size of the area for retrieval statements. This is set by means of the DBH option COLUMNS. In the case of the default values
PLAN=70, COLUMNS=256 and USERS=24, the size of the plan buffer is approximately
1.1 Mbytes.
The “Performance” manual describes when it makes sense to modify the size of the plan
buffer the next time the DBH is started up.
124
U22418-J-Z125-6-76
DBH options
STORAGE-SIZE
STORAGE-SIZE
This statement sets buffer and container sizes.
Definition
A higher-level DBH option
Function
STORAGE-SIZE is the higher-level option of DBH options with which you can set the size
of buffers and containers.
STORAGE-SIZE
= *STD / *PARAMETERS(...)
*PARAMETERS(...)





CURSOR-BUFFER = *STD
,TRANSFER-CONTAINER = *STD
,WORK-CONTAINER = *STD
,SYSTEM-DATA-BUFFER = 208
,USER-DATA-BUFFER = 80
Operands
STORAGE-SIZE = *STD
Default values apply to all STORAGE-SIZE parameters. They are described under the
entries for the relevant lower-level DBH options.
STORAGE-SIZE = *PARAMETERS(...)
The parameters of STORAGE-SIZE are DBH options. Their operands are described under
the entries for the relevant options.
U22418-J-Z125-6-76
125
SUBORDERS
DBH options
SUBORDERS
This statement makes SQL scans and logical files available.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
You use the DBH option SUBORDERS to specify the number of suborders for which
resources are to be provided during the DBH session. This restricts main-memory requirements.
The meaning of suborders differs depending on whether it applies to an SQL or a CALL
DML application:
–
In the case of an SQL application, suborders are SQL scans, i.e. subareas of an SQL
access plan, the evaluation rule for an SQL statement.
–
In the case of a CALL DML application, suborders are logical files for CALL DML
requests.
SUBORDERS
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


INITIAL = 24 / <integer 6..262143>
,MAXIMUM = *STD / <integer 6..262143>
Operands
SUBORDERS = *STD
The default numbers of SQL scans or logical files (suborders) permitted apply. These
defaults are described under *PARAMETERS.
126
U22418-J-Z125-6-76
DBH options
SUBORDERS
SUBORDERS = *PARAMETERS(...)
INITIAL = 24 / <integer 6..262143>
Initial value for the number of concurrent suborders for which resources are to be
available.
The default value for INITIAL is 24.
An internal comparison ensures that the permissible number of suborders is at least as
high as the maximum number of concurrent users (see the DBH option USERS on
page 140). If the maximum number of concurrent users is greater than the value
specified here, the initial value is increased automatically.
MAXIMUM = *STD / <integer 6..262143>
Maximum permissible number of concurrent suborders.
If the initial value specified for the INITIAL parameter is not high enough, SESAM/SQL
allows resources to be made available dynamically for additional suborders.
The default value for MAXIMUM is the initial value for the permissible number of
concurrent suborders specified by means of the INITIAL parameter.
You can change the maximum value for the permissible number of concurrent
suborders during the DBH session by means of the MODIFY-SUBORDER-LIMIT
administration statement (see page 261).
Information on suborders
You will find the number of used suborders and the maximum number of available suborders
in the “SYSTEM INFORMATION” form of the SESAM/SQL monitor SESMON (see
page 416).
The “Performance” manual describes the cases in which it makes sense to modify the
number of available resources for suborders at the next DBH startup.
U22418-J-Z125-6-76
127
SYSTEM-DATA-BUFFER
DBH options
SYSTEM-DATA-BUFFER
This statement sets the size of the buffer for system-access data.
Definition
A lower-level DBH option of STORAGE-SIZE
Function
The SESAM/SQL DBH has two separate buffers: one for blocks with system-access data
and one for blocks with user data. Each block is 4 Kbytes in size. All users use both buffers
together for all connected databases.
You use the DBH option SYSTEM-DATA-BUFFER to set the initial size of the buffer for
system-access data, i.e. data required by the system for the physical organization of
memory.
The final size of the buffer for system-access data depends on the DBH option THREADS
(see page 133) and the system threads dependent on this. The minimum value for the
buffer size is 96 Kbytes per thread. If the specified value is smaller than the minimum value,
then the value is automatically increased to the minimum value as long as the specified
value is within the permitted range of values (see below). Otherwise the DBH is terminated.
SYSTEM-DATA-BUFFER
= 208 / <integer 80..1000000>
Operands
SYSTEM-DATA-BUFFER = = 208 / <integer 80..1000000>
Initial size of the buffer for system-access data in units of 1 Kbyte. The default value for
SYSTEM-DATA-BUFFER is 208 Kbytes.
Information on input/output behavior
The “I/O” form of the SESAM/SQL monitor SESMON contains information on input/output
behavior. This information is helpful for setting the optimum size of the buffer for systemaccess data (see page 403).
The “Performance” manual describes the cases in which it makes sense to modify the size
of the buffer for system-access data at the next DBH startup.
128
U22418-J-Z125-6-76
DBH options
SYSTEM-LIMITS
SYSTEM-LIMITS
This statement specifies limit values.
Definition
A higher-level DBH option
Function
SYSTEM-LIMITS is the higher-level option of all DBH options with which you can specify
limit values for the DBH session.
SYSTEM-LIMITS
= *STD / *PARAMETERS
*PARAMETERS(...)









COLUMNS = 256
,SQL-SUPPORT = *YES(...)
,SUBORDERS = *STD
,SYSTEM-THREADS = *STD
,THREADS = 1
,USERS = *STD
,SQL-DATABASE-CATALOG = 1
,OLD-TABLE-CATALOG = 0
,SPACES = *STD
Operands
SYSTEM-LIMITS = *STD
Default values apply to all the parameters of SYSTEM-LIMITS. They are described under
the relevant lower-level DBH options.
SYSTEM-LIMITS = *PARAMETERS(...)
The various parameters of SYSTEM-LIMITS are DBH options. Their operands are
described under the relevant DBH options.
U22418-J-Z125-6-76
129
SYSTEM-STRATEGIES
DBH options
SYSTEM-STRATEGIES
This statement defines a processing strategy.
Definition
A higher-level DBH option
Function
SYSTEM-STRATEGIES is the higher-level option of DBH options with which you can define
a processing strategy.
SYSTEM-STRATEGIES
= *STD / *PARAMETERS(...)
*PARAMETERS(...)




REQUEST-CONTROL = *NONE
RESTART-CONTROL = *STD
,RETRIEVAL-CONTROL = *STD
,TRANSACTION-SECURITY = *YES(...)
Operands
SYSTEM-STRATEGIES = *STD
Default values apply to all the parameters of SYSTEM-STRATEGIES. They are described
under the relevant lower-level DBH options.
SYSTEM-STRATEGIES = PARAMETERS(...)
The parameters of SYSTEM-STRATEGIES are DBH options. Their operands are described
under the relevant options.
130
U22418-J-Z125-6-76
DBH options
SYSTEM-THREADS
SYSTEM-THREADS
This statement specifies the number of concurrent system threads.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
System threads are created in order to deal with internal system requests to the spaces.
The lower-level DBH option SYSTEM-THREADS specifies the number of these system
threads.
In the case of the linked-in DBH, the DBH option SYSTEM-THREADS is ignored; the default value of 1 applies to WRITE-THREADS.
SYSTEM-THREADS
= *STD / *PARAMETERS(...)
*PARAMETERS(...)

WRITE-THREADS = *STD / <integer 1..512>
Operands
SYSTEM-THREADS = *STD
Specifies the maximum number of concurrently active system threads. The default values
are given under *PARAMETERS.
SYSTEM-THREADS = *PARAMETERS(...)
WRITE-THREADS =
Specifies the maximum number of concurrent system threads that deal with open write
requests to the spaces. These system threads are known as write threads.
WRITE-THREADS = *STD / <integer 1..512>
You can specify the number of write threads independently of the number of threads
specified by means of the DBH option THREADS.
However, the default value is obtained from the number of threads divided by 32. If this
calculation does not produce an integer, the figure is rounded up to the next integer.
U22418-J-Z125-6-76
131
SYSTEM-THREADS
DBH options
The size of the value specified for the WRITE-THREADS parameter has the following
effects:
–
If a very low number is selected, the TA-LOG files will be larger than expected and
the CPU requirements will be considerably increased. As a result the writing of the
after-images, as specified in the option RESTART-CONTROL, may no longer be
guaranteed.
–
A very high value, on the other hand, affects the address space requirements rather
than the CPU requirements.
Information on system threads
You will find information on the number of concurrent system threads in the “SYSTEM
THREADS” form of the SESAM/SQL monitor SESMON (see page 421).
132
U22418-J-Z125-6-76
DBH options
THREADS
THREADS
This statement specifies the number of concurrent threads.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
In multithread mode, the DBH processes several requests simultaneously. Each request is
stored in a thread.
You use the DBH option THREADS to specify how many threads are to be available in the
DBH session for requests from applications, thus restricting indirectly the number of
concurrent requests.
You will avoid system bottlenecks by specifying a number of threads that is less than or
equal to the number of tasks of all the application programs. You should also count applications such as the SESUTI utility monitor or the SESADM administration program for this
purpose. If a system bottleneck occurs because the value specified for the THREADS
option is too low, it is removed by rolling back the transaction. This ensures that not all
threads are blocked by blocked requests.
For an independent DBH an internal comparison is carried out so that the value for
THREADS is greater than or equal to twice the value of the DBH-TASKS option. For a
linked-in DBH the DBH option THREADS is ignored, i.e. the value 1 is the default value for
threads.
THREADS
= 1 / <integer 1..1024>
THREADS = 1 / <integer 1..1024>
Specifies the maximum number of concurrently active threads.
Information on thread utilization
You can obtain information on the current utilization of the threads from the “SYSTEMINFORMATION” form of the SESAM/SQL monitor SESMON (see page 416).
The “Performance” manual describes the cases in which it makes sense to modify the
number of threads at the next DBH startup.
U22418-J-Z125-6-76
133
TRANSACTION-SECURITY
DBH options
TRANSACTION-SECURITY
This statement activates transaction management.
Definition
A lower-level DBH option of SYSTEM-STRATEGIES
Function
Transaction management coordinates concurrent database accesses. In the event of an
error, it guarantees data consistency by means of rollback mechanisms.
By default, every DBH session runs with transaction management.
The DBH option TRANSACTION-SECURITY allows you to modify the rollback criteria for
transactions locking other transactions to suit the requirements of the DBH session. If you
want to run the DBH without transaction management, you can deactivate it. Note that, if
you do this, the DBH cannot support the SQL interface (see the DBH option SQLSUPPORT on page 123).
You can change the LOCK-TIME, INACTIVITY-TIME and LOCK-ESCALATION parameters
during the DBH session by using the MODIFY-TRANSACTION-SECURITY administration
statement (see page 262).
TRANSACTION-SECURITY
= *YES(...) / *NO
*YES(...)








134
LOCK-TIME = 4 / <integer 1..999>
,INACTIVITY-TIME = *STD / <integer 1..999>
,MAX-ISOLATION-LEVEL = *STD / *REPEATABLE-READ
,LOCK-ESCALATION = *STD / *PARAMETERS(...)
*PARAMETERS(...)



NUMBER-RECORDS = 4000 / <integer 1..2147483647>
,PERCENTAGE-RECORDS = 50 / <integer 0..100>
,NUMBER-INDEX-VALUES = 1000 / <integer 1..2147483647>
U22418-J-Z125-6-76
DBH options
TRANSACTION-SECURITY
Operands
TRANSACTION-SECURITY = *YES(...)
The DBH runs with transaction management.
If the DBH is to support the SQL interface (specified by means of the DBH option SQLSUPPORT), the use of transaction management is mandatory.
LOCK-TIME = 4 / <integer 1..999>
Specifies the number of minutes after which an inactive transaction locking other transactions is to be rolled back. The default is 4 minutes.
INACTIVITY-TIME = *STD / <integer 1..999>
Specifies the number of minutes after which an open but inactive transaction is to be
rolled back. The value for INACTIVITY-TIME must be greater than or equal to that for
LOCK-TIME. The default value is 10 times the value for LOCK-TIME.
MAX-ISOLATION-LEVEL = *STD / *REPEATABLE-READ
The maximum isolation level for access to user tables is defined. If *STD is specified,
access occurs under the isolation level SERIALIZABLE.
If you specified the value *REPEATABLE-READ, all attempts of applications to access
data under the isolation level SERIALIZABLE are rejected with SQLSTATE in the DBH
session.
If *REPEATABLE-READ is specified, no transaction locks are used by the DBH on index
values, provided the index is not a unique index nor an index of a reference condition.
If an SQL statement is to work with a DBH for which the value *REPEATABLE-READ is
specified for MAX-ISOLATION-LEVEL, you must either execute a SET TRANSACTION
in the application before each transaction, or set the option
ISOL-LEVEL=REPEATABLE-READ in the user configuration file.
LOCK-ESCALATION =
Specifies what happens when there are transaction locks. If a specified number of
locked values in an index or number of locked records in a table is exceeded,
SESAM/SQL attempts to lock the entire index or table. This is referred to as lock
escalation.
A change to the settings for LOCK-ESCALATION can have a considerable effect on the
behavior of the DBH as regards storage space requirements and the probability of
transaction conflicts:
–
If low values are selected, an attempt is made at a very early stage to lock the entire
table or index. This saves storage space, since the locks do not have to be managed
individually. However, it increases the probability of transaction conflicts occurring.
–
Higher values reduce the risk of transaction conflicts. In this case, however, the
storage space requirements increase because the locks have to be managed
individually.
U22418-J-Z125-6-76
135
TRANSACTION-SECURITY
DBH options
The current number of records as of which the entire table is to be locked is obtained
from PERCENTAGE-RECORDS and compared with the value of NUMBERRECORDS. The lower value is used as the limit.
If lock escalation is not successful immediately, only the directly affected record or index
value is locked. After this unsuccessful escalation attempt, the next attempt is not
started for another 100 locks.
LOCK-ESCALATION = *STD
The default values for the size of the escalation parameters are indicated under
*PARAMETERS(...).
LOCK-ESCALATION = *PARAMETERS(...)
NUMBER-RECORDS = 4000 / <integer 1..2147483647>
Specifies the number of records in a table that a requesting user can lock. If more
records are locked, an attempt is made to lock the entire table.
PERCENTAGE-RECORDS = 50 / <integer 0..100>
Specifies as a percentage of all the records in a table how many records a
requesting user can lock. If a higher percentage is locked, an attempt is made to
lock all the records of the table. If 0 is selected as the percentage, an attempt is
made to lock the entire table immediately.
NUMBER-INDEX-VALUES = 1000 / <integer 1..2147483647>
Specifies the number of values that can be locked by a requesting user in an index.
If a greater number is locked, an attempt is made to lock the entire index rather than
individual values.
TRANSACTION-SECURITY = *NO
Specifies that the DBH is to be used without transaction security.
If you want to run the DBH session without transaction security, you must specify this option
explicitly. If you do this, only CALL-DML is permitted; the SQL interface is not supported
without transaction security.
136
U22418-J-Z125-6-76
DBH options
TRANSFER-CONTAINER
TRANSFER-CONTAINER
This statement sets the size of the transfer container.
Definition
A lower-level DBH option of STORAGE SIZE
Function
When SQL access plans are processed, SQL scans are produced. These are subareas of
an evaluation rule for an SQL statement.
During the processing of CALL DML applications, inquiry and response areas are
requested for each logical file by means of the OPEN statement.
The SESAM/SQL DBH reserves the above areas in the transfer container, where they are
available for further processing.
You use the DBH option TRANSFER-CONTAINER to set the size of the transfer container.
The size of the transfer container is specified in units of 1 Kbyte.
The storage space requirements for the transfer container depend on the maximum number
of concurrent scans or logical files in existence and their question-and-answer requirements.
TRANSFER-CONTAINER
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


INITIAL = 64 / <integer 64..1000000>
,MAXIMUM = 16000 / <integer 64..1000000>
Operands
TRANSFER-CONTAINER = *STD
The default values for the size of the transfer container are described under
*PARAMETERS(...).
U22418-J-Z125-6-76
137
TRANSFER-CONTAINER
DBH options
TRANSFER-CONTAINER = *PARAMETERS(...)
Changes the size of the transfer container.
INITIAL = 64 / <integer 64..100000>
Sets the size of the transfer container at the beginning of the DBH session. The default
is 64 Kbytes.
i
The initial value for TRANSFER-CONTAINER is compared to the initial value of
SUBORDERS. This results in the following minimum value for the initial value
of TRANSFER-CONTAINER:
(initial value of SUBORDERS + x) * 4 [Kbytes]
The following applies to x:
– in an independent DBH: x = 1 + 2 * min(10, [SQL-DATABASE-CATALOG/4])
– in a linked-in DBH: x = 3
MAXIMUM = 16000 / <integer 64..100000>
Sets the maximum size of the transfer container. The default is 16000 Kbytes.
i
If the maximum value is smaller than the specified value for INITIAL, then the
value of MAXIMUM is adjusted according to the value of INITIAL.
The maximum value for TRANSFER-CONTAINER is also compared to the
maximum value of SUBORDERS in the same manner as for the initial value.
This results in the following maximum value for TRANSFER-CONTAINER:
(maximum value of SUBORDERS + x) * 4 [Kbyte]
The following applies to x:
– in an independent DBH: x = 1 + 2 * min(10, [SQL-DATABASE-CATALOG/4])
– in a linked-in DBH: x = 3
Information on the transfer container
You can obtain information on the transfer container and its extensions from the operational
statistics of the SESAM/SQL monitor SESMON.
You will find information in the “SYSTEM-INFORMATION” form (see page 416) on the size
of the container and its extensions.
The “Performance” manual describes the cases in which it makes sense to modify the
container size at the next DBH startup.
138
U22418-J-Z125-6-76
DBH options
USER-DATA-BUFFER
USER-DATA-BUFFER
This statement sets the size of the user-data buffer.
Definition
A lower-level DBH option of STORAGE-SIZE
Function
The SESAM/SQL DBH administers two separate buffers: one for blocks with systemaccess data (see the DBH option SYSTEM-DATA-BUFFER on page 128) and one for
blocks with user data. The blocks are each 4 Kbytes in size. All users use both buffers
together for all connected databases.
You use the DBH option USER-DATA-BUFFER to set the initial size of the buffer for user
data.
The final size of the buffer for user data depends on the DBH option THREADS and the
system threads depending on THREADS. The minimum value of the buffer size is 96
Kbytes per thread. If the specified value is smaller than the minimum value, then the value
is automatically set to the minimum value as long as the specified value is in the permitted
range of values (see below), otherwise the DBH is terminated.
USER-DATA-BUFFER
= 80 / <integer 80..1000000>
Operands
USER-DATA-BUFFER = 80 / <integer 80..1000000>
Initial size of the buffer for user data in units of 1 Kbyte. The default is 80 Kbytes.
Information on input/output behavior
The “I/O” form of the SESAM/SQL monitor SESMON contains information on input/output
behavior. This information helps you set the optimal size of the buffer for user data (see
page 403).
The “Performance” manual describes the cases in which it makes sense to modify the size
of the buffer for user data at the next DBH startup.
U22418-J-Z125-6-76
139
USERS
DBH options
USERS
This statement specifies the number of users.
Definition
A lower-level DBH option of SYSTEM-LIMITS
Function
You use the DBH option USERS to specify how many parallel users you want to permit in
the DBH session.
A user of the DBH in timesharing mode is an interactive or batch program, identified in each
case by a TSN (task sequence number). In transaction mode (openUTM/DCAM), a user is
defined by an active terminal or by a user ID and terminal together (in the case of UTM, by
means of the LTERM or TPOOL control statement). In openUTM with conversation stacking
and asynchronous conversations, each conversation is a user of the SESAM/SQL DBH.
USERS
= *STD / <integer 1..32767>
Operands
USERS = *STD / <integer 1..32767>
Maximum number of concurrent users.
The default value for the total number of concurrent users is 24.
An internal comparison ensures that the number of available SQL scans or logical files
specified using the INITIAL parameter of the DBH option SUBORDERS is taken into
account.
If this value is greater than 24, then the default value for the total number of concurrent
users is automatically adjusted according to this value.
The upper limit for the number of concurrent users depends on how many users your
license for the SESAM/SQL database system permits.
140
U22418-J-Z125-6-76
DBH options
WORK-CONTAINER
WORK-CONTAINER
This statement sets the size of the work container.
Definition
A lower-level DBH option of STORAGE-SIZE
Function
The SESAM/SQL DBH checks that each statement is lexically, syntactically and semantically correct. Based on a correct statement or subarea of a statement, the DBH generates
an optimized format known as the internal statement format.
Based on a CALL DML statement, the DBH generates the internal statement format directly.
Based on an SQL statement, the DBH initially generates an SQL access plan, i.e. an evaluation rule for the SQL statement. An SQL access plan consists of at least one but usually
several subareas known as SQL scans. The optimized format of a scan forms the internal
statement format.
The internal statement formats are stored for further processing in the work container so
that follow-up statements can refer back to them.
The DBH option WORK-CONTAINER allows you to adjust the size of the work container to
the requirements of the application. The size of the work container is specified in units of
1 Kbyte.
WORK-CONTAINER
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


U22418-J-Z125-6-76
INITIAL = *STD / <integer 24..1000000>
,MAXIMUM = *STD / <integer 24..1000000>
141
WORK-CONTAINER
DBH options
Operands
WORK-CONTAINER = *STD
The default value for the size of the work container is described under
*PARAMETERS(...).
WORK-CONTAINER = *PARAMETERS(...)
Changes the size of the work container.
INITIAL = *STD / <integer 24..1000000>
Initial size of the work container in Kbytes.
DBH carries out an internal comparison with the initial value of SUBORDERS when an
initial value is specified:
Minimum value (or default value if no value was specified explicitly) for INITIAL for
WORK-CONTAINER:
(Initial value of SUBORDERS + x) * 4 Kbyte
The additional amount x is calculated in the same manner as the additional amount “x”
for the initial value of TRANSFER-CONTAINER (see page 137).
MAXIMIUM = *STD / <integer 24..1000000>
Maximum size of the work container in Kbytes.
DBH carries out an internal comparison with the maximum value of SUBORDERS
when a maximum value is specified:
Minimum value (or default value if no value was specified explicitly) for
MAXIMUM for WORK-CONTAINER:
(Maximum value of SUBORDERS+ x) * 4 Kbyte
The additional amount x is calculated in the same manner as the additional amount “x”
for the maximum value of TRANSFER-CONTAINER (see page 137).
Space required to store the internal statement format in the WORK-CONTAINER
A resource bottleneck can be prevented for WORK-CONTAINER if its maximum size is the
product of the maximum number of SUBORDERS and the space required to store an
average internal statement format. The space required to store an average internal
statement format can be derived from the following table. It depends on the DBH option
COLUMNS (see page 84f).
142
U22418-J-Z125-6-76
DBH options
WORK-CONTAINER
Average number of COLUMNS in the
internal statement format
Space required to store internal statement
formats in Kbytes
up to 1
12
up to 28
16
up to 63
20
up to 93
24
up to 122
28
up to 151
32
up to 210
40
up to 268
48
up to 327
56
up to 385
64
up to 438
72
up to 502
80
up to 561
88
up to 619
96
up to 736
112
up to 853
128
up to 970
144
up to 1024
152
Table 16: Space required to store internal statement formats
Information on the work container
You can obtain information on the work container and its extensions from the operational
statistics of the SESAM/SQL monitor SESMON.
The “SYSTEM-INFORMATION” form indicates the size of the container, the percentage of
its capacity being used, the number of area requests made, and the number of times the
container has been accessed (see page 416).
The “Performance” manual describes the cases in which it makes sense to modify the
container size at the next DBH startup.
U22418-J-Z125-6-76
143
Eine Dokuschablone von Frank Flachenecker
by f.f. 1992
4 Distributed processing with SESAM/SQL-DCN
SESAM/SQL-DCN is a chargeable add-on product for the SESAM/SQL-Server database
system.
In distributed processing with SESAM/SQL-DCN, an application program can work with
more than one SESAM/SQL DBH during a single session. The interaction between the
application program and the various DBHs can take place within the same configuration,
across configurations on the same machine, or across different machines.
The central component of the product SESAM/SQL-DCN is the distribution component
SESDCN. This component must be started in all configurations involved in distributed
processing.
The principles of distributed processing are described in the “Core Manual”.
This chapter describes how to start, parametrize and terminate SESDCN. It covers the
following:
●
starting the SESDCN distribution component
●
the SESDCN control statements
●
terminating SESDCN
●
the SESDCN restart
●
the maximum values for working with SESAM/SQL-DCN
The dynamic administration of SESDCN is described in chapter “DBH and SESDCN administration” on page 173ff.
If the add-on product SESAM/SQL-DCN is not available, all SESDCN-specific commands
and statements are rejected.
U22418-J-Z125-6-76
145
Starting the SESDCN distribution component
Distributed processing with SESAM/SQL-DCN
4.1 Starting the SESDCN distribution component
Like the independent DBH, SESDCN runs in BS2000 as a separate task and should
preferably be started as a batch job.
The execution phase of SESDCN exists as a link and load module (LLM) called SESDCN
and is started with the START-SESAM-DCN command (see section “Starting SESAM/SQL
programs via start commands” on page 31).
The SESDCN distribution component is parametrized at startup by means of SESDCN
control statements. These contain the DCN options and the distribution rule for SESDCN.
The SESDCN control statements are not described in this section. You will find a detailed
description of them in a separate section of this chapter (see section “SESDCN control
statements” on page 156).
SESAM/SQL-DCN share modules
You can administer parts of SESAM/SQL-DCN as share modules and load them on a
shareable basis or as subsystems. You will find information on this in section “SESAM/SQL
share modules” on page 50.
4.1.1 Startup requirements
General requirements
The prerequisites for starting SESDCN are similar to those for starting the SESAM/SQL
DBH (see page 38). The section on the sequence of commands for starting SESDCN
indicates the files you have to activate and the assignments that are necessary before
SESDCN is started (see page 147).
In addition, the application programs involved in distribution must not yet be loaded, since
only application programs loaded after SESDCN is started can access data in the network.
The prerequisites for restarting SESDCN are described in section “SESDCN restart
requirements” on page 152.
146
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
Starting the SESDCN distribution component
4.1.2 Starting SESDCN in batch mode and passing control statements
In batch mode, you start SESDCN as a batch job with the command
ENTER-PROCEDURE FROM-FILE=filename
where filename is the name of an SDF-P procedure created by the user in which he or she
enters the sequence of commands for starting SESDCN.
Sequence of commands for starting
[/MODIFY-TEST-OPTIONS DUMP=YES] ————————————————————————————————————————
[/ASSIGN-SYSDTA TO-FILE = *SYSCMD] —————————————————————————————————————
/START-SESAM-DCN ———————————————————————————————————————————————————————
[//control statements] —————————————————————————————————————————————————
[//END] ————————————————————————————————————————————————————————————————
(1)
(2)
(3)
(4)
(5)
(1)
Causes each requested memory dump to be output and a message issued to
SYSOUT. You should enter this statement in order to receive the diagnostic
documentation required in the event of an error.
(2)
Assigns the SYSDTA system file to the SYSCMD procedure file. This assignment
is not necessary if you enter the SESDCN control statements in an S procedure.
(3)
Starts the SESDCN distribution component with the start command
START-SESAM-DCN (see also section “Starting SESAM/SQL programs via start
commands” on page 31).
(4)
You must enter the SESDCN control statements here (see section “SESDCN
control statements” on page 156). You enter them if you do not want to use the
defaults or do not assign the control statements via an input file.
(5)
The END statement concludes input of the SESDCN control statements.
Entering the SESDCN control statements
There are two ways to enter the SESDCN control statements:
1. You can enter the control statements in the procedure in the sequence of commands
for starting SESDCN. In this case, you must assign the SYSDTA system file to
SYSCMD before the START-SESAM-DCN command.
The start parameters must come immediately after the start command STARTPROGRAM.
2. You can pass the control statements via an input file (see section “Passing control statements by means of an input file” on page 149).
U22418-J-Z125-6-76
147
Starting the SESDCN distribution component
Distributed processing with SESAM/SQL-DCN
In both cases, you must conclude input of the control statements with the END statement.
In the event of an invalid control statement, SESDCN aborts. A distribution rule is not
generated if this happens.
4.1.3 Starting SESDCN in interactive mode and passing control statements
When you start the SESDCN distribution component in the interactive mode, the terminal
remains busy throughout the SESDCN session. You can only start other programs from this
terminal by means of batch jobs. To avoid interrupting the SESDCN session, you should
therefore start SESDCN in batch mode.
You can start SESDCN for the interactive mode either directly on screen or by means of a
procedure; accordingly, you enter the SESDCN control statements either directly on screen
or in the procedure. The control statements must come immediately after the start
command START-SESAM-DCN .
Alternatively, you can enter the SESDCN control statements via an input file (see
page 149).
Parameter input is logged to SYSLST. You can specify the extent of logging by means of
the MODIFY-SDF-OPTIONS statement's LOGGING parameter (see the BS2000 manual
“Commands, Volumes 1 - 5”). It is advisable to specify LOGGING=ACCEPTED-FORM here
so that only the entered start parameters are logged, not the default values.
The sequence of commands for starting SESDCN is described on page 147. You will find
information on entering the SESDCN control statements on page 149.
Starting SESDCN and entering control statements interactively
When you start SESDCN directly on screen in the interactive mode, the SYSDTA system
file must be assigned to the terminal.
Once the START-SESAM-DCN command has been entered, SESDCN requests the control
statements interactively.
If one of the control statements is invalid, you receive an error message. You can then
correct it, but the corrected version of the control statement is not logged to SYSLST.
148
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
Starting the SESDCN distribution component
Starting SESDCN and entering start statements in a procedure
When you start and parametrize SESDCN in a procedure, you must assign the SYSDTA
system file to the SYSCMD procedure file:
Example
In the interactive mode, you enter the SESDCN control statements in an SESDCN start
procedure.
/SET-PROCEDURE-OPTIONS
.
.
/START-SESAM-DCN
//control-statements
.
.
//END
.
.
/EXIT-PROCEDURE
4.1.4 Passing control statements by means of an input file
You can pass the SESDCN control statements to SESDCN via an input file in either the
batch or interactive mode.
Before starting SESDCN, you must assign the input file. There are several ways to do this.
You can assign the input file:
–
–
–
as a SESDCN configuration file using the link name SESCONF
as a SYSDTA system file
as a global configuration file using the CONNECT-SESAM-CONFIGURATION
command.
Assigning a SESDCN configuration file
You assign the SESDCN configuration file with the following command:
ADD-FILE-LINK LINK-NAME=SESCONF,FILE-NAME=input-file
Assigning a SYSDTA system file as the input file
ASSIGN-SYSDTA TO-FILE=input-file
In section “Examples of SESDCN parametrization” on page 168, you will find some
examples of SESDCN input files.
U22418-J-Z125-6-76
149
Starting the SESDCN distribution component
Distributed processing with SESAM/SQL-DCN
Assigning a global configuration file
This global configuration file can contain configuration parameters for several components
of the SESAM/SQL system (see page 42).
Notes on entering control statements
When entering SESDCN control statements, you must comply with a number of rules
(which apply regardless of whether you are entering them in an input file, a procedure or
interactively):
–
Each line must begin with the escape symbol (//).
–
Each control statement must begin on a new line.
–
If a control statement takes up more than one line, you must conclude each line with the
continuation character (-); the last line of a control statement must not be concluded
with the continuation character (-).
–
The parameters must be entered in a fixed order (see section “SESDCN control statements” on page 156).
–
The last line must contain an END statement; this END statement concludes input of
the SESDCN control statements.
If one of the SESDCN control statements is invalid, SESDCN aborts and you receive an
error message. A distribution rule is not generated.
150
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
Starting the SESDCN distribution component
4.1.5 Starting several SESDCNs
In most cases, the SESDCN distribution component need only be loaded once per configuration. However, a large number of remote accesses of an SESDCN can have a negative
effect on runtime behavior.
You can increase total throughput of remote accesses by starting several SESDCNs.
Remote requests are then processed concurrently by more than one SESDCN.
A DBH can only ever be assigned to one SESDCN.
(A DBH may occur in several entries of the ADD-DISTRIBUTION-RULE-LIST statement if
this DBH has several catalogs. The same LINK-NAME must be used in all these DBH
entries and then describes the route via a DCN in the ADD-NETWORK-LINK-LIST
statement. If this condition is not met, the statement is rejected with message SEN1003.)
Several DBHs can be assigned to a single SESDCN.
The SESDCN started first in a configuration assumes the function of the master DCN.
When necessary, the master DCN carries out the SESDCN restart.
When starting the master DCN, you must define the distribution rule by means of the appropriate control statements. You can start the other SESDCNs in a configuration without
defining the distribution rule, i.e. without supplying information on databases.
U22418-J-Z125-6-76
151
Terminating SESDCN
Distributed processing with SESAM/SQL-DCN
4.2 Terminating SESDCN
You terminate SESDCN with the STOP-DCN administration statement (see page 339).
An SESDCN that has been terminated can no longer act as a remote DCN. Remote
accessing of databases to which the SESDCN is assigned by the distribution rule as the
remote DCN is no longer possible.
The loaded distribution rule is retained until all SESDCNs, DBHs and application programs
belonging to the same configuration are terminated.
4.3 Restarting an SESDCN session
After a system crash, SESDCN must be restarted to preserve transaction consistency (see
the “Core Manual”). SESDCN is responsible for coordinating, executing and monitoring the
restart. If SESDCN has been loaded several times in the configuration, the SESDCN loaded
first assumes this task. The SESDCN that carries out the restart is called the master DCN.
A SESDCN restart is the logical continuation of the previous SESDCN session. All the DCN
options and distribution-rule entries of the previous session therefore apply.
4.3.1 SESDCN restart requirements
If an SESDCN restart is to be carried out, the following requirements must be met:
To ensure that the master DCN can access the backup file of the aborted session during a
restart, you must make the backup file available before starting the master DCN. There are
two ways to do this:
–
You can catalog the backup file with its default name under the identifier where the
master DCN is started; the default name of the backup file is SES.DLGc, where c stands
for the name of the configuration to which the master DCN belongs.
–
You can assign the backup file to the master DCN under the link name SESDLG.
To ensure that the restart can be carried out for all configurations on a backup computer,
the configuration names must be unique throughout the network. You assign the configuration name by means of the DCN option DCN-IDENTIFICATION (see section “SET-DCNOPTIONS” on page 158).
152
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
Restarting an SESDCN session
4.3.2 Restarting SESDCN on a backup computer
SESDCN can be restarted on the computer on which SESDCN was originally started (the
cold-start computer) or on a different computer, the backup computer.
To restart an SESDCN on a backup computer, the whole SESDCN configuration must be
on the restart computer. You must therefore move all the components of this configuration
to the backup computer. These can be:
–
–
–
–
–
application programs
SESDCNs
DBHs
the SES.DLGc backup file
DBH-specific files
The DBHs involved must be able to access all the databases assigned to them, and all the
required tasks must be restartable on the new computer.
Updating the distribution rules
If the SESDCN restart is executed on a backup computer, the location of the restart configuration in the network changes for the other configurations. The master DCN of the restart
configuration therefore automatically replaces the name of the original computer with the
name of the backup computer in the distribution rules of the remote computers known and
accessible to it. This ensures that communication is still possible with the configurations on
these machines.
If not all the remote computers in the network are accessible to the master DCN at the time
of the SESDCN restart, the master DCN cannot change all the distribution rules automatically. In this case, you have to update the distribution-rule entries yourself using the
MODIFY-DISTRIBUTION-RULE-ENTRY administration statement (see page 252).
If several configurations execute their SESDCN restart on a backup computer after a crash,
the associated master DCNs again cannot update all the distribution rules. They can update
the distribution rules of configurations that have remained in the same position and are
accessible, but not those of configurations that have moved to another computer. In this
case too, you have to update some of the distribution-rule entries manually using the
MODIFY-DISTRIBUTION-RULE-ENTRY administration statement.
The master DCN updates the distribution rules only in the memory pool and the log file. Any
input files that exist are not affected.
U22418-J-Z125-6-76
153
Restarting an SESDCN session
Distributed processing with SESAM/SQL-DCN
4.3.3 Synchronization of DBH, SESDCN and UTM restarts
To guarantee an error-free restart of a distributed database system in a UTM environment,
all the systems involved are started with restart data (warm start).
A cold start of one of the systems after a system failure is not permitted and usually not
possible, but it can be triggered by deleting the backup files, for example.
The following table indicates what happens if one of the systems involved is cold started:
Start of
Cold start Warm start Consequence
DBH
x
SESDCN
x
The UTM application is aborted.
openUTM
x
DBH
x
SESDCN
x
Restart information for openUTM is lost as a result
of the cold start; data consistency is not
guaranteed.
x
Transactions in the state PTC are not known to the
DBH and can be rolled back by means of administration statements. The session can be continued,
but data consistency is not guaranteed.
openUTM
x
DBH
SESDCN
x
DBH
x
The databases are not consistent and must be
repaired.
Table 17: Consequences of a DBH, SESDCN or openUTM restart
Start sequence
The systems involved in a restart forward information on their current processing status to
their partners. On the basis of this information the transactions affected by the system
failure are rolled back or terminated. To guarantee complete consistency, you must start the
systems in the following order:
1. DBHs
2. SESDCNs
3. UTM applications
4. other application programs
If you start a UTM application before the DBH or before SESDCN, it is aborted.
154
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
Maximum values
4.4 Maximum values for working with SESAM/SQL-DCN
The following list provides an overview of the maximum values. These are based on the
system limits valid for distributed processing with SESAM/SQL-DCN:
Maximum values
System limits
Number of applications in a configuration
128
Maximum message length in bytes (as of SESAM/SQL V3.2)
Still valid for cross-version distributed processing:
64000
32000
Number of databases in the distribution rule
340
Number of DBHs in a distributed transaction
13
Number of DBHs for which requests from a user task can be active
concurrently
170
Number of DBHs that can be addressed per configuration for users
working in a distributed system
25
Number of remote configurations that can be known in a configuration 406
Number of SQL scans or logical files that a user can work with simul- Approximately
taneously
USERS ∗ 0.751
Table 18: Maximum values based on the system limits
1
USERS = permitted number of users in the SESDCN session (DCN option)
With dynamic memory management, in exceptional cases it is possible that the maximum
number of SQL scans or logical files that a user can work with simultaneously is never
reached.
U22418-J-Z125-6-76
155
SESDCN control statements
Distributed processing with SESAM/SQL-DCN
4.5 SESDCN control statements
SESDCN control statements are for parametrizing the SESDCN distribution component.
They contain the options and the definition of the distribution rule. The distribution rule
defines the associated access path for every database involved in the distributed system.
SESDCN uses the BS2000 dialog interface SDF (System Dialog Facility). SDF supports
statement input in a form-driven dialog, analyzes the syntax of the statements entered and
passes them to SESDCN for processing. You will find a detailed description of the SDF
dialog interface in the “Introductory Guide to the SDF Dialog Interface”.
4.5.1 Entering SESDCN control statements
You enter the SESDCN control statements when you start SESDCN (see section “Starting
the SESDCN distribution component” on page 146).
The following table provides an overview of the SESDCN control statements in the order in
which they are entered:
SESDCN control statement
Function
1. SET-DCN-OPTIONS
Causes the options to be read in.
2. ADD-DISTRIBUTION-RULE-LIST
3. ADD-NETWORK-LINK-LIST
Defines the distribution rule.
Table 19: SESDCN control statements
The first SESDCN control statement is SET-DCN-OPTIONS (see page 158). You enter this
statement once and once only.
It is followed by the ADD-DISTRIBUTION-RULE-LIST control statement (see page 164).
You use this statement to enter the databases to be included in the distributed system. You
must enter this statement at least once for the master DCN. The master DCN is the first
SESDCN started in a configuration. If you start additional SESDCNs in the configuration of
the master DCN, you need not enter the ADD-DISTRIBUTION-RULE-LIST statement for
these SESDCNs. You can enter the required databases using a single statement, or you
can enter them in groups using several ADD-DISTRIBUTION-RULE-LIST statements. You
can enter a total of 340 databases.
Finally, you can enter the ADD-NETWORK-LINK-LIST statement (see page 166). You use
this to assign the logical link names of the databases to their respective physical access
paths, thus defining the network for the distribution component.
156
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
SESDCN control statements
You can enter the associated network for a total of 340 databases. You can do this using a
single statement, or you can enter the databases in groups using several ADD-NETWORKLINK-LIST statements.
You need not enter the ADD-NETWORK-LINK-LIST statement if the ADD-DISTRIBUTIONRULE-LIST statement contains only databases stored on the home system that belong to
the same configuration as the SESDCN to be started.
The END statement
The END statement concludes input of SESDCN control statements.
Example 1
The END statement concludes input of the SESDCN control statements after the information on the structure of the distribution rule.
//SET-DCN-OPTIONS ...
//ADD-DISTRIBUTION-RULE-LIST ...
//ADD-NETWORK-LINK-LIST ...
//END
Example 2
The END statement concludes parameter input immediately after the SET-DCNOPTIONS statement.
//SET-DCN-OPTIONS ...
//END
U22418-J-Z125-6-76
157
SET-DCN-OPTIONS
Distributed processing with SESAM/SQL-DCN
4.5.2 Syntax and functions of the SESDCN control statements
This section describes the SESDCN control statements in the order in which they are
entered.
The syntax of the SESDCN control statements corresponds to that of SDF (see section
“SDF syntax representation” on page 12).
The SESDCN control statements can be abbreviated in accordance with the SDF conventions.
Most of the parameters of the SESDCN control statements have defaults. When entering
the SESDCN control statements, you need only include those parameters to which you
want to assign values other than the defaults.
SET-DCN-OPTIONS
This statement reads in DCN options.
Function
The SESDCN control statement SET-DCN-OPTIONS causes the DCN options to be read
in.
DCN options parametrize the SESDCN distribution component and thus define the
essential properties of SESDCN operation. SESAM/SQL-DCN recognizes the following
options:
DCN-OPTION
Short description of function
ADMINISTRATOR
Assigns administrator authorization
COLDSTART
Requests a cold start.
DCN-IDENTIFICATION Assigns a DCN name and configuration name.
REMOTE-ACCESS
Permits access from a remote computer.
SESDLG-PASSWORD
Assigns a password.
SYSTEM-LIMITS
Specifies limit values for the permitted number of users and transaction
applications, and defines reset criteria for transactions.
Table 20: Functions of the DCN options
You can modify some DCN options dynamically using administration statements (see
section “SESDCN administration statements” on page 198).
158
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
SET-DCN-OPTIONS
You must enter the SET-DCN-OPTIONS statement once and once only.
SET-DCN-OPTIONS
DCN-IDENTIFICATION = *STD / *PARAMETERS(...)
*PARAMETERS(...)


CONFIGURATION-NAME = *BLANK / <alphanum-name 1..1>
,DCN-NAME = *BLANK / <alphanum-name 1..1>
,SYSTEM-LIMITS = *STD / *PARAMETERS(...)
*PARAMETERS(...)




USERS = 128 / <integer 1..16000>
,APPLICATIONS = 64 / <integer 1..128>
,LOCK-TIME = 8 / <integer 1..999>
,INACTIVITY-TIME = 12 / <integer 1..999>
,COLDSTART = *NO / *YES
,REMOTE-ACCESS = *ALLOWED / *NOT-ALLOWED
,SESDLG-PASSWORD = *NONE / <c-string 1..4> / <x-string 1..8> / <integer -2147483648..2147483647>
,ADMINISTRATOR = *NONE / *ANY(...) / *TIME-SHARING-USER(...) / *APPLICATION-USER(...)
*ANY(...)

PASSWORD = <c-string 3..3> / <x-string 5..6>
*TIME-SHARING-USER(...)



PASSWORD = <c-string 3..3> / <x-string 5..6>
,HOST-NAME = <name 1..8>
,USER-ID = <name 1..8>
*APPLICATION-USER(...)




PASSWORD = <c-string 3..3> / <x-string 5..6>
,HOST-NAME = <text 1..8>
,APPLICATION-NAME = <text 1..8>
,CUSTOMER-NAME = <text 1..8>
Operands
DCN-IDENTIFICATION =
Identifies the SESDCN distribution component to be parametrized.
DCN-IDENTIFICATION = *STD
The SESDCN distribution component is identified by default values. These are described
under PARAMETERS(...).
U22418-J-Z125-6-76
159
SET-DCN-OPTIONS
Distributed processing with SESAM/SQL-DCN
DCN-IDENTIFICATION = *PARAMETERS(...)
CONFIGURATION-NAME = *BLANK / <alphanum-name 1..1>
Name of the configuration to which the SESDCN component is assigned.
The configuration name must be unique throughout the network so that, if necessary, it
is possible to execute a restart on a machine other than the cold-start computer (see
page 153).
DCN-NAME = *BLANK / <alphanum-name 1..1>
Name of the distribution component to be parametrized.
The default is a blank.
SYSTEM-LIMITS =
Specifies limit values for the SESDCN session.
SYSTEM-LIMITS = *STD
The default limit values of the SESDCN session apply. These are described under
PARAMETERS(...).
SYSTEM-LIMITS = *PARAMETERS(...)
USERS = 128 / <integer 1..16000>
Maximum number of permitted users in the session.
In timesharing mode, the users are the interactive or batch programs that run simultaneously. In transaction mode, they are the simultaneously open transaction conversations defined by the active terminals. In openUTM with conversation stacking and
asynchronous conversations, each conversation is a user.
The default value for USERS is 128. The upper limit for the number of concurrent users
depends on the total number of users your SESAM/SQL-DCN license permits. The
license specifies the total number of DCN option USERS of all master DCNs in a
hardware installation.
You cannot change the number of permitted users specified here in the current session;
you first have to restart SESDCN. Note that you cannot restart SESDCN until all the
application programs involved and all the SESAM/SQL-DBHs and SESDCNs have
been terminated.
SESDCN sets up the number of areas specified by USERS for user tables in the
common memory pool. The common memory pool is created by the first SESDCN in a
configuration to be loaded, the master DCN. The entry for USERS is ignored by subsequently loaded SESDCNs of the same configuration.
You should therefore assign the same value for USERS to all master DCNs in the
session.
APPLICATIONS = 64 / <integer 1..128>
Maximum number of transaction applications that can participate in the SESDCN
session. The default is 64.
160
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
SET-DCN-OPTIONS
LOCK-TIME = 8 / <integer 1..999>
Specifies the time in minutes after which an inactive transaction locking another transaction is rolled back.
Default: 8 minutes.
INACTIVITY-TIME = 12 / <integer 1..999>
Specifies the time in minutes after which an inactive open transaction is rolled back.
Transactions locked by other transactions are not affected by this. The value for
INACTIVITY-TIME must be greater than or equal to that for LOCK-TIME.
Default: 12 minutes.
COLDSTART =
Requests a cold start.
COLDSTART = *NO
This is the default.
When a restart is executed on a backup computer (see page 153), the host names in the
distribution rules of the remote DCNs are updated only in the memory pool and in DCN LOG.
Any input files of the remote DCNs are therefore not affected by this updating. The next cold
start would cancel the updating.
The default is therefore that a warm start is executed when the SESDCN acting as the
remote DCN is started again after a distribution rule has been updated (because a
SESDCN has been restarted on a backup computer). When a warm start is executed,
SESDCN evaluates the updated distribution rule backed up in DCN LOG.
COLDSTART = *YES
Causes a cold start to be executed even if the distribution rule of this SESDCN has been
updated (because of a SESDCN restart on a backup computer). When a cold start is
executed, SESDCN evaluates the SESDCN control statements in the input or procedure
files. Any entries in DCN LOG that contradict these are ignored.
You cannot force a cold start if there are still transactions in the PTC state. If this is the case,
SESDCN carries out a warm start.
Note that the host names in the ADD-NETWORK-LINK-LIST statement must be up to date.
REMOTE-ACCESS =
Specifies whether or not access is permitted from a remote computer.
REMOTE-ACCESS = *ALLOWED
This is the default.
Access from a remote computer is permitted.
REMOTE-ACCESS = *NOT-ALLOWED
Remote access is not permitted. SESDCN does not accept requests from remote
computers.
U22418-J-Z125-6-76
161
SET-DCN-OPTIONS
Distributed processing with SESAM/SQL-DCN
SESDLG-PASSWORD =
Gives the distribution components the password with which you can access the SESDCN
backup file. The password protection applies to write and read accesses. At the same time,
this also protects the file from being deleted.
If there is not a SESDCN backup file at the time when the SESDCN session is started, the
file is generated by SESDCN and is password-protected if a password is specified in the
SESDLG-PASSWORD operand.
SESDLG-PASSWORD = *NONE
No password is specified.
SESDLG-PASSWORD = <c-string 1..4> / <x-string 1..8> /
<integer -2147483648..2147483647>
Gives the specified password to the distribution components.
i
Password protection is only set by SESDCN when generating the SESDLG file.
If there is already a SESDCN backup file without password protection at the time
when SESDCN is started under the name assigned with the link name SESDLG or
under the default name, then this file will not be protected by a password from
SESDCN even when the SESDLG-PASSWORD operand contains a value.
If an existing SESDCN backup file is assigned a password later or a password is to
be changed, you must do this using the SDF command MODIFY-FILEATTRIBUTES.
ADMINISTRATOR =
Specifies the user or user group authorized to issue administration statements using the
CALL interface and SESADM.
ADMINISTRATOR = *NONE
Administration using the CALL interface and SESADM is not possible. The MODIFYADMINISTRATION administration statement is also rejected.
ADMINISTRATOR = *ANY(...)
Users who are not system administrators can also issue administration statements using
the CALL interface and SESADM.
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password providing protection against unauthorized administration using the CALL
interface and SESADM.
162
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
SET-DCN-OPTIONS
ADMINISTRATOR = *TIME-SHARING-USER(...)
Only the system administrator can issue administration statements using the CALL
interface and SESADM. The administrator is a timesharing user and is identified by the
system user identification.
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password providing protection against unauthorized administration using the CALL
interface and SESADM
HOST-NAME = <name 1..8>
Name of the computer from which administration is to be carried out
USER-ID = <name 1..8>
User ID of the system administrator
ADMINISTRATOR = *APPLICATION-USER(...)
Only the system administrator can issue administration statements using the CALL
interface and SESADM. The administrator is an application user and is identified by the
system user identification.
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password providing protection against unauthorized administration using the CALL
interface and SESADM
HOST-NAME = <text 1..8>
Name of the computer from which administration is to be carried out
APPLICATION-NAME = <text 1..8>
Name of the application from which administration is to be carried out
CUSTOMER-NAME = <text 1..8>
Name of the user. If the system administrator is working under openUTM, the KDCSIGN
name must be specified here. If the system administrator is working under DCAM, the
name by which the system administrator identifies himself or herself at the program
interface must be specified.
U22418-J-Z125-6-76
163
ADD-DISTRIBUTION-RULE-LIST
Distributed processing with SESAM/SQL-DCN
ADD-DISTRIBUTION-RULE-LIST
This statement adds databases to the distribution rule.
Function
The SESDCN control statement ADD-DISTRIBUTION-RULE-LIST describes which
databases are added to the distribution rule and via which logical connections the different
databases can be accessed.
You must use this statement to enter all databases that are to be involved in distributed
processing and accessible from the configuration to which the SESDCN to be loaded
belongs. This also applies to base tables processed by CALL DML application programs.
You can use the statement once or several times (see page 156) and enter a total of
340 databases.
You can use the ADD-DISTRIBUTION-RULE-ENTRY administration statement to enter
additional databases in the distribution rule during the SESDCN session (see page 213).
The administration statements MODIFY-DISTRIBUTION-RULE-ENTRY and REMOVEDISTRIBUTION-RULE-ENTRY allow you to change entries in the distribution rule and
remove them from it, respectively (see page 252 and page 270).
ADD-DISTRIBUTION-RULE-LIST
CATALOG-NAME-1 = *NONE / <filename 1..18 without-cat-id-generation-version>(...)


LINK-NAME = *HOME / <name 1..8>
,DBH-NAME = *BLANK / <alphanum-name 1..1>
.
.
,CATALOG-NAME-200 = *NONE / <filename 1..18 without-cat-id-generation-version>(...)


164
LINK-NAME = *HOME / <name 1..8>
,DBH-NAME = *BLANK / <alphanum-name 1..1>
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
ADD-DISTRIBUTION-RULE-LIST
Operands
CATALOG-NAME-1 =
First database entered in the distribution rule.
CATALOG-NAME-1 = *NONE
This is the default.
No more databases are entered.
CATALOG-NAME-1 =
<filename 1..18 without-cat-id-generation-version>(...)
Logical name of the database to be entered.
The logical database name is the name by which a database is addressed in the application
program.
You also have to specify the logical database name for each base table to be processed by
CALL DML application programs. The logical database name must be unique throughout
the network.
LINK-NAME = *HOME / <name 1..8>
Logical link name that provides the logical link to the associated entry in the ADDNETWORK-LINK-LIST statement (see page 166).
If the database to be entered is assigned to the same configuration to which SESDCN
is to belong, select the default: *HOME. If you do this, the link to a remote DCN is unnecessary, as is a corresponding entry in the ADD-NETWORK-LINK-LIST statement.
DBH-NAME = *BLANK / <alphanum-name 1..1>
Name of the DBH responsible for working with the database.
The default is a blank.
.
.
CATALOG-NAME-n =
n = 2-200
The nth database entered in the distribution rule.
Up to 200 database entries are permitted.
The parameters of this operand are identical to those of the CATALOG-NAME-1 operand
described above.
U22418-J-Z125-6-76
165
ADD-NETWORK-LINK-LIST
Distributed processing with SESAM/SQL-DCN
ADD-NETWORK-LINK-LIST
This statement describes the physical access path for distributed databases.
Function
The SESDCN control statement ADD-NETWORK-LINK-LIST describes the network for the
databases entered in the distribution rule. It assigns the access paths in the network to the
logical link names of the databases.
You use this statement to define the access path for all databases entered in the distribution
rule that are not in the home configuration. You specify the computer on which the relevant
databases are stored, which remote DCN is responsible for forwarding requests in the case
of remote access, and which configuration the remote DCN belongs to.
A corresponding entry in the ADD-NETWORK-LINK-LIST statement is not necessary for
databases in the home configuration.
You can enter the ADD-NETWORK-LINK-LIST statement once or several times (see
page 156). Up to 340 entries are permitted.
ADD-NETWORK-LINK-LIST
LINK-NAME-1 = *NONE / <name 1..8>(...)
<name 1..8>(...)



PROCESSOR-NAME = <name 1..8>
,CONFIGURATION-NAME = *BLANK / <alphanum-name 1..1>
,DCN-NAME = *BLANK / <alphanum-name 1..1>
.
.
, LINK-NAME-200 = *NONE / <name 1..8>(...)
<name 1..8>(...)



166
PROCESSOR-NAME = <name 1..8>
,CONFIGURATION-NAME = *BLANK / <alphanum-name 1..1>
,DCN-NAME = *BLANK / <alphanum-name 1..1>
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
ADD-NETWORK-LINK-LIST
Operands
LINK-NAME-1 =
First entry of the network access path of a database in the distribution rule.
A network access path must be entered for all databases that are not in the home configuration. The home configuration is the configuration in which this SESDCN is started.
The network access path consists of the name of the computer on which the database is
stored and the configuration name and DCN name of the associated remote DCN. The
remote DCN belongs to the same configuration to which the database is assigned. It
forwards remote accesses of the database, i.e. accesses from application programs
belonging to a different configuration: the configuration of the SESDCN to be loaded, for
example.
LINK-NAME-1 = *NONE
This is the default. No other network access path is entered.
LINK-NAME-1 = <name 1..8>(...)
Logical link name that provides the logical link to the associated entry or entries in the ADDDISTRIBUTION-RULE-LIST statement (see page 164).
The logical link name specifies for which database in the distribution rule the network
access path is to be entered. This name provides the link to the associated remote DCN.
PROCESSOR-NAME = <name 1..8>
Symbolic device name of the computer on which the database is stored and on which
the associated remote DCN must be loaded.
CONFIGURATION-NAME = *BLANK / <alphanum-name 1..1>
Configuration name of the configuration to which the remote DCN is assigned.
The default is a blank.
DCN-NAME = *BLANK / <alphanum-name 1..1>
Name of the remote DCN.
The default is a blank.
.
.
LINK-NAME-n =
n = 2-200
The nth entry of the network access path of a database in the distribution rule.
Up to 200 entries are permitted.
The parameters of this operand are identical to those of the LINK-NAME-1 operand
described above.
U22418-J-Z125-6-76
167
Examples of SESDCN parameterization
Distributed processing with SESAM/SQL-DCN
4.5.3 Examples of SESDCN parametrization
This section describes two examples of the parametrization of SESDCN by means of
control statements. In the first, the communication between application programs and DBHs
is to be implemented for local access, whereas in the second, it is to be implemented for
remote access as well. The control statements for parametrizing SESDCN are stored in an
input file that must be assigned before SESDCN is started.
Local access
In distributed processing with SESAM/SQL-DCN, application programs can communicate
with more than one DBH. If the application program and database belong to the same
configuration, we talk about local access (see the “Core Manual”).
The figure on the next page shows a simple example of local access. The two loaded DBHs
on processor P412 with their assigned databases belong to configuration S. To enable
application programs belonging to this configuration to access the databases via these two
DBHs, the SESDCN distribution component with the DCN name R and the configuration
name S is loaded.
Processor P412
AP
AP
Distribution rule
DBCON
DBCON
DBH A
DBH B
SESDCNR
COMPANY
PERSONNEL
Configuration S
Figure 2: Example of a distributed application with local access
168
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
Examples of SESDCN parameterization
The input file for the control statements of the SESDCNR distribution component contains
the following:
//SET-DCN-OPTIONS // DCN-IDENTIFICATION=*PARAMETERS // (CONFIGURATION-NAME=S,DCN-NAME=R)
//ADD-DISTRIBUTION-RULE-LIST // CATALOG-NAME-1=FIRMA(LINK-NAME=*HOME,DBH-NAME=A), // CATALOG-NAME-2=PERSONAL(LINK-NAME=*HOME,DBH-NAME=B)
//END
An ADD-NETWORK-LINK-LIST statement is not necessary, since all the databases
entered in the distribution rule are assigned to the same configuration.
Remote access
In distributed processing, if application programs access databases in other configurations,
we talk about remote access. Remote access can take place on a single computer or
across computer boundaries.
The figure 3 on page 170 shows a simple example of a distributed application with remote
access. An SESDCN and a DBH are loaded in configuration A on processor P614.
Processor P616 contains two configurations (B and C), each with an SESDCN and a DBH.
Application programs are to be able to access all databases in the network.
The names of the configurations are unique throughout the network so that, in the event of
a computer failure, a restart is possible on the other computer at any time (see section
“Restarting an SESDCN session” on page 152).
For the sake of clarity, only the access paths going from configuration A to configurations B
and C are shown in the following figure.
U22418-J-Z125-6-76
169
Examples of SESDCN parameterization
Distributed processing with SESAM/SQL-DCN
Processor P614
AP
DISTRIB. RULE
DBCON
SESDCN A
DBH 3
WH2
WH1
Configuration A
Processor P616
AP
DISTRIB. RULE
DBCON
SESDCN X
DBH 4
CUSTOM.
Configuration B
AP
DISTRIB. RULE
DBCON
SESDCN Y
DBH 5
SALES
Configuration C
Figure 3: Example of a distributed application with remote access
170
U22418-J-Z125-6-76
Distributed processing with SESAM/SQL-DCN
Examples of SESDCN parameterization
The input file for the control statements of the SESDCNA distribution component contains
the following:
//SET-DCN-OPTIONS // DCN-IDENTIFICATION=*PARAMETERS // (CONFIGURATION-NAME=A,DCN-NAME=A)
//ADD-DISTRIBUTION-RULE-LIST // CATALOG-NAME-1=WAREHOUSE1(LINK-NAME=*HOME,DBH-NAME=3), // CATALOG-NAME-2=WAREHOUSE2(LINK-NAME=*HOME,DBH-NAME=3), // CATALOG-NAME-3=CUSTOMERS(LINK-NAME=PARTNER1,DBH-NAME=4), // CATALOG-NAME-4=SALES(LINK-NAME=PARTNER2,DBH-NAME=5)
//ADD-NETWORK-LINK-LIST // LINK-NAME1=PARTNER1(PROCESSOR-NAME=P616, //
CONFIGURATION-NAME=B, //
DCN-NAME=X), // LINK-NAME2=PARTNER2(PROCESSOR-NAME=P616, //
CONFIGURATION-NAME=C, //
DCN-NAME=Y)
//END
The input file for the control statements of the SESDCNX distribution component contains
the following:
//SET-DCN-OPTIONS // DCN-IDENTIFICATION=*PARAMETERS // (CONFIGURATION-NAME=B,DCN-NAME=X)
//ADD-DISTRIBUTION-RULE-LIST // CATALOG-NAME-1=WAREHOUSE1(LINK-NAME=PARTNER2,DBH-NAME=3), // CATALOG-NAME-2=WAREHOUSE2(LINK-NAME=PARTNER2,DBH-NAME=3), // CATALOG-NAME-3=CUSTOMERS(LINK-NAME=*HOME,DBH-NAME=4), // CATALOG-NAME-4=SALES(LINK-NAME=PARTNER1,DBH-NAME=5)
//ADD-NETWORK-LINK-LIST // LINK-NAME1=PARTNER1(PROCESSOR-NAME=P616, //
CONFIGURATION-NAME=C, //
DCN-NAME=Y), // LINK-NAME2=PARTNER2(PROCESSOR-NAME=P614, //
CONFIGURATION-NAME=A, //
DCN-NAME=A)
//END
U22418-J-Z125-6-76
171
Examples of SESDCN parameterization
Distributed processing with SESAM/SQL-DCN
The input file for the control statements of the SESDCNY distribution component contains
the following:
//SET-DCN-OPTIONS // DCN-IDENTIFICATION=*PARAMETERS // (CONFIGURATION-NAME=C,DCN-NAME=Y)
//ADD-DISTRIBUTION-RULE-LIST // CATALOG-NAME-1=WAREHOUSE1(LINK-NAME=PARTNER2,DBH-NAME=3), // CATALOG-NAME-2=WAREHOUSE2(LINK-NAME=PARTNER2,DBH-NAME=3), // CATALOG-NAME-3=CUSTOMERS(LINK-NAME=PARTNER1,DBH-NAME=4), // CATALOG-NAME-4=SALES(LINK-NAME=*HOME,DBH-NAME=5)
//ADD-NETWORK-LINK-LIST // LINK-NAME1=PARTNER1(PROCESSOR-NAME=P616, //
CONFIGURATION-NAME=B, //
DCN-NAME=X), // LINK-NAME2=PARTNER2(PROCESSOR-NAME=P614, //
CONFIGURATION-NAME=A, //
DCN-NAME=A)
//END
172
U22418-J-Z125-6-76
5 DBH and SESDCN administration
This chapter describes both DBH and SESDCN administration. It covers:
●
the administration interfaces
●
the syntax and functions of the administration statements
5.1 Administration interfaces
There are three interfaces for dynamic DBH and SESDCN administration:
●
administration using INFORM-PROGRAM
(also with SEND-MSG, for reasons of compatibility)
●
administration using a CALL DML program
●
administration using the SESADM administration program.
In addition, the SESAM/SQL monitor SESMON provides information on current operation
that is useful for administration. You can use the DBH and SESDCN statistics produced by
SESMON to work out the optimal settings for the DBH options and SESDCN control statements (see chapter “Outputting operational data with SESMON” on page 377).
i
U22418-J-Z125-6-76
The following always applies:
Output sent to SYSOUT and SYSLST is not upwardly compatible.
Output layout may vary depending on the version used.
173
Administration interfaces
Administration
5.1.1 Administration using INFORM-PROGRAM
When you use the BS2000 command INFORM-PROGRAM for administration, messages
are sent to the DBH or SESDCN in the form of administration commands (STXIT routine).
Replies are written to SYSLST and SYSOUT.
The earlier command SEND-MSG can also be used for reasons of compabitility.
There are two ways to enter the administration commands:
–
at the terminal at which the DBH or SESDCN was started in interactive mode
–
at the console of the BS2000 system administrator.
The BS2000 STXIT routine restricts inputs to a length of 60 characters. You therefore have
to abbreviate the keywords of some of the administration commands.
An administration command sent to the SESAM-DBH can be distributed among several
INFORM-PROGRAM commands. To do this, the entry of the INFORM-PROGRAM
command to be continued must end with a comma. The next INFORM-PROGRAM
command will then be interpreted as the continuation of the administration command. The
administration command is only executed once the entire command entered is complete.
This does not apply to SESAM-DCN.
A job sent via the NFORM-PROGRAMG interface is generally only approved once the
SESAM/SQL-DBH system start has been completed (shown by outputting the message
“SES0060 SYSTEM READY”). The same is true for SESAM-DCN (shown by outputting the
message “SEN3020 SESDCN READY”).
The acknowledge is sent by the administration via INFORM-PROGRAM only after the job
has been completely processes, i.e. the behavior is the same as for the administration when
sent via the CALL-DML interface or via SESADM.
If an internal restart is triggered while an administration command is being processed, the
command is aborted. It can happen in this case that the acknowledge is not sent although
the command has already been executed. However, it may be that the command was not
executed.
174
U22418-J-Z125-6-76
Administration
Administration interfaces
Entering commands at the terminal
If the DBH or SESDCN was started in interactive mode from the system administrator's
terminal, you can enter the administration commands from this terminal.
To enter an administration command, proceed as follows:
–
Press the K2 key or EM DUE1 thus interrupting the task of the DBH (independent
DBH or linked-in application) or SESDCN.
–
Issue a INFORM-PROGRAM command to pass the administration command to the
DBH or SESDCN task:
/INFORM-PROGRAM MSG='administration-command'
Any quotes in the text of the administration command must be entered twice.
Because the DBH or SESDCN is interrupted for the command input and cannot continue
working during this time, it is not advisable to enter an administration command at the
terminal.
Entering commands at the console of the BS2000 system administrator
If the DBH or SESDCN was started in batch mode, you must enter the administration
commands at the console of the BS2000 system administrator. You enter the INFORMPROGRAM command as follows:
/INFORM-PROGRAM JOB-ID=*TSN(TSN=tsn),MSG='administration-command'
where:
tsn
is the task sequence number of the task in which the independent DBH,
linked-in application or SESDCN was started.
Any quotes in the text of the administration command must be entered twice.
In addition, a user with the privilege OPERATING or TSOS can also administer DBHs or
SESDCN via /INFORM-PROGRAM where the DBHs or SESDCN are started in the interactive mode from any terminal.
Outputs occurring during administration via INFORM-PROGRAM are made on the same
terminal as the DBH messages according to the option MSG-OUTPUT.
U22418-J-Z125-6-76
175
Administration interfaces
Administration
Several concurrent STXIT routines
One INFORM-PROGRAM command can activate several STXIT routines concurrently. In
the case of the linked-in DBH, for example, STXIT routines of both the DBH and the application program can be started.
When there are several concurrently active STXIT routines, you can direct the INFORMPROGRAM command at a specific component, such as the DBH:
/ INFORM-PROGRAM JOB-ID=*TSN(TSN=tsn) /
,MSG=component,'administration-command'
where:
component
is the component to which the INFORM-PROGRAM command is to be
directed. You can enter any of the following for component:
SES: DBH STXIT
S63: SEDI63 STXIT
DCN: SESDCN STXIT
component is an optional entry for the administration of SES DCN and the independent
DBH, but it is mandatory for the linked-in DBH.
176
U22418-J-Z125-6-76
Administration
Administration interfaces
5.1.2 Administration using a CALL DML program
In a CALL DML program, you can issue administration commands to the DBH or to
SESDCN by means of a CALL DML statement. The following prerequisites must be fulfilled:
–
When the DBH or SESDCN is started, administration via the CALL interface must be
permitted (using the DBH or DCN option ADMINISTRATOR).
–
The ADMINISTRATOR open statement must be issued in the CALL DML program to
initiate the administration of the DBH (see the “CALL DML Applications” manual). Until
the close statement, only administration statements in this program run can be
executed.
Administration via the CALL interface can be carried out from any BS2000 user ID.
The transfer areas of the CALL DML statement for administration contain the following:
statement area:
where the application program enters the statement in the form of
an administration command in ISP format.
acknowledgment area:
where the DBH or SESDCN reports the acknowledgment of the
administration command.
response area:
where the responses to administration calls are output.
The inquiry area is not evaluated by the DBH or SESDCN.
You will find a thorough description of the different transfer areas in the “CALL DML Applications” manual.
U22418-J-Z125-6-76
177
SESADM
Administration
5.1.3 Administration using SESADM
SESADM is an easy-to-use, SDF-based program for administering the independent DBH
and SESDCN. It reads in administration input via SYSDTA. Output is sent to SYSOUT when
run in the interactive mode and to SYSLST when run in the batch mode.
Status messages and error messages are sent to SYSOUT and SYSLST when run in the
interactive mode and to the console and SYSLST when run in the batch mode.
The SESADM administration program builds on the CALL DML interface. It forms a CALL
DML statement from the entries made by the user, and issues it to the connection module
via CALL SESAM. The connection module converts the statements and forwards them to
the DBH or the responsible SESDCN distribution component.
SESADM automatically checks the output of the statements. If a status other than “00” is
returned, SESADM sets task switch 11 and outputs a corresponding message (see also
section “Setting task switches” on page 470). In both interactive and batch mode, SESADM
then continues running and awaits further input.
Access from the World Wide Web
From SESAM/SQL-Server V3.2 onwards you can access the administration program
SESADM, the performance monitor SESMON and the utility monitor SESUTI all from a
unified access on the World Wide Web (WWW or Web for short) with the aid of the software
product WebTransactions (WebTA).
To access the SESAM programs via the Web, you only need a standard browser in addition
to the software product WebTransactions.
Web access is described in the document “WebTA access for SESAM/SQL” shipped
together with SESAM/SQL-Server V3.2. This document is also available from the Fujitsu
Siemens manual server under the software product SESAM/SQL.
178
U22418-J-Z125-6-76
Administration
SESADM
Embedding of SESADM
SESADM
CALL DML
Connection module
SESDCN
SESDCN
DBH
SESDCN
DBH
Communication between the tasks
Computer boundary
Figure 4: The SESADM administration interface
It is not possible to use SESADM to administer the linked-in DBH.
The SESADM program runs in the SESAM/SQL configuration specified in the configuration
file assigned to this program. If SESADM is started without a configuration file, it runs in the
default configuration 'Ë'.
If the configuration in which SESADM is running is a non-distributed configuration
(SESDCN not loaded), only the default DBH of this specific configuration can be administered with this SESADM. This is the DBH whose DBH name and configuration identifier are
specified in the configuration file assigned to the SESADM program; if no configuration file
is assigned, it is the DBH with the NAM identifier 'Ë' and the configuration identifier 'Ë'.
Specification of any other values in the CONFIGURATION-NAME and DBH-NAME parameters in the SESADM control statement START-DBH-ADMINISTRATION, or any attempt to
administer SESDCN will be rejected with error messages.
Please note the following when administering a SESAM/SQL DBH or a SESAM/SQL DCN.
U22418-J-Z125-6-76
179
SESADM
Administration
Administration of a SESAM/SQL DBH
If the DBH to be administered is running in a non-distributed configuration:
–
Start SESADM in the same configuration and assign the DBH to be administered, i.e.
the SESADM program must be assigned a configuration file in which the DBH name
and configuration identifier of the DBH to be administered are specified.
–
If the configuration file is missing or has not been assigned, then you can input
additional identification for the DBH to be administered via the parameters DBH-NAME
and CONFIGURATION-NAME in the SESADM control statement START-DBHADMINISTRATION. Otherwise the DBH is assigned the NAM identifier 'Ë' and the
configuration identifier 'Ë'.
If the DBH to be administered is running in a distributed configuration:
–
As above
or
–
Start SESADM in any distributed configuration (this can be the same as that in which
the DBH is running, or a different one) whose distribution rule contains at least one
database which is assigned to the DBH to be administered; then identify the DBH to be
administered using the DBH-NAME and CONFIGURATION-NAME parameters in the
SESADM control statement START-DBH-ADMINISTRATION.
Administration of a SESAM/SQL DCN
–
180
Start SESADM in any distributed configuration (this can be the same as that in which
SESDCN is running, or a different one) and identify the SESDCN to be administered
using the DCN-NAME and CONFIGURATION-NAME parameters in the SESADM
control statement START-DCN-ADMINISTRATION.
U22418-J-Z125-6-76
Administration
5.1.3.1
SESADM
Starting SESADM
SESADM runs in BS2000 as a separate task. Accordingly, you can start SESADM in interactive or batch mode. You can also call SESADM from the utility monitor (see the “Utility
Monitor” manual).
You can also access the administration program SESADM from the World Wide Web, see
page 178.
Sequence of commands for starting SESADM
[/ASSIGN-SYSDTA TO-FILE=sesadm input file] ——————————————————
[/ADD-FILE-LINK LINK-NAME=SESCONF,FILE-NAME=configuration file] —————
/START-SESAM-ADMINISTRATION ———————————————————————————
5.1.3.2
(1)
(2)
(3)
(1)
Assigns the SESADM input file. You only need to enter this command if you are
entering the SESADM statements from an input file.
(2)
Assigns a configuration file which can contain as a parameter the name of the
configuration under which SESADM is to run, for example. This command is
optional. It is one of the ways to assign the configuration file (see the “Core
Manual”).
(3)
Starts the administration program with the start command
START-SESAM-ADMINISTRATION (see section “Starting SESAM/SQL programs
via start commands” on page 31)
Entering the SESADM statements
The SESADM administration program reads in the administration inputs with the help of
SDF (see the “Introductory Guide to the SDF Dialog Interface”).
SESADM recognizes the following statements:
–
SESADM control statements (see page 190ff)
–
administration statements (see page 210ff).
The syntax of the SESADM control and administration statements complies with SDF
conventions.
U22418-J-Z125-6-76
181
SESADM
Administration
There are different ways of entering SESADM statements, depending on the mode used:
In interactive mode:
–
you can enter them interactively, directly on screen, with SDF support
–
you can enter them in the SESADM start procedure
–
you can enter them in the SESADM input file, which must be assigned before SESADM
is started.
In batch mode:
–
you can enter them in the procedure for starting SESADM
–
you can enter them in the SESADM input file, which must be assigned before SESADM
is started.
Entering SESADM statements interactively
For the interactive entry of SESADM statements directly on screen, SDF offers two modes:
–
expert mode (the default)
–
nonexpert mode.
You can use the SDF statement MODIFY-SDF-OPTIONS whenever you like to set the
mode.
In expert mode, a system prompt (//) appears after SESADM starts. If you enter a question
mark (?) here instead of an SESADM statement, SDF changes to nonexpert mode and
displays the corresponding selection screens. When you enter an SESADM statement,
SDF switches back to expert mode and the system prompt appears again.
In nonexpert mode, SDF displays a selection screen of the permitted statements when
SESADM is started. When you select a statement, SDF supports operand input by means
of appropriate SDF selection screens (see section “SDF selection screens for SESADM
administration” on page 184).
Entering SESADM statements via an input file or procedure
When entering SESADM statements via an input file or in a start procedure, the following
rules apply:
182
–
The first statement must be the SESADM control statement START-DBHADMINISTRATION or START-DCN-ADMINISTRATION. This SESADM control
statement identifies the DBH or SESDCN to be administered. All the administration
statements that come immediately after it relate to the DBH or SESDCN thus identified.
–
The first statement is followed by administration statements to the identified DBH or
SESDCN.
U22418-J-Z125-6-76
Administration
SESADM
–
The administration statements can be followed by another identifying SESADM control
statement, in turn followed by associated administration statements. This step can be
repeated several times.
–
The SESADM control statement END terminates administration with SESADM (see
page 193).
Example
The example below shows an input file for administration with SESADM. The input file
contains both DBH and SESDCN administration statements.
//START-DCN-ADMINISTRATION //
PASSWORD='ADM',DCN-NAME=A,CONFIGURATION-NAME=2,HOST-NAME=P614
//SHOW-USERS
//START-DBH-ADMINISTRATION //
PASSWORD='ADM',DBH-NAME=7
//SHOW-DBH-OPTIONS
//MODIIFY-ADMINISTRATION NEW-PASSWORD='XTI'
//MODIFY-SUBORDER-LIMIT LIMIT=1000
//SHOW-CATALOG-USERS
//ROLLBACK-TRANSACTION USER=*TSN(TSN=3343)
//START-DCN-ADMINISTRATION //
PASSWORD='ADM',DCN-NAME=C
//SHOW-DISTRIBUTION-RULE-ENTRIES
//REMOVE-DISTRIBUTION-RULE-ENTRY CATALOG-NAME=TEST1
//START-DCN-ADMINISTRATION //
PASSWORD='ADM',DCN-NAME=C
//SHOW-DISTRIBUTION-RULE-ENTRIES
//MODIFY-DISTRIBUTION-RULE-ENTRY //
HOST-NAME=P614,NEW-NAME=P616
//ADD-DISTRIBUTION-RULE-ENTRY //
CATALOG-NAME=TEST2,DCN-NAME=C,CONFIGURATION-NAME=X,HOST-NAME=P616
//SHOW-TRANSACTIONS
//ROLLBACK-TRANSACTION USER=*BY-SELECT(HOST-NAME=P614,
//
*TSN=(TSN=2012),CUSTOMER-NAME=TEST) //END
U22418-J-Z125-6-76
183
SESADM
5.1.3.3
Administration
SDF selection screens for SESADM administration
This section describes the selection screens provided by SDF when you enter the SESADM
statements interactively (see page 182). In nonexpert mode, SDF always displays the
selection masks; in expert mode, only if you enter a question mark (?).
SDF provides the following selection screens:
–
START-MENU
–
DBH-MENU
–
DCN-MENU
START-MENU
END
START-DBH-ADMINISTRATION
START-DCN-ADMINISTRATION
DBH-MENU
DCN-MENU
Menu
Statement
Figure 5: SDF selection screens for SESADM administration
184
U22418-J-Z125-6-76
Administration
SESADM
SDF displays the START-MENU selection screen after SESADM is started. In it you select
one of the following three SESADM control statements:
–
START-DBH-ADMINISTRATION (see page 191)
–
START-DCN-ADMINISTRATION (see page 192)
–
END (see page 193).
DBH-MENU is the selection screen for administration statements to the DBH. SDF switches
to DBH-MENU when you select the START-DBH-ADMINISTRATION control statement from
the START-MENU selection screen and enter the associated parameters.
DCN-MENU is the selection screen for administration statements to SESDCN. SDF
switches to DCN-MENU when you select the START-DCN-ADMINISTRATION control
statement from the START-MENU selection screen and enter the associated parameters.
You will find alphabetically arranged descriptions of all the administration statements as of
page 210.
All three menus contain the SDF commands MODIFY-SDF-OPTIONS, REMARK,
RESTORE-SDF-INPUT, SHOW-INPUT-HISTORY, SHOW-SDF-OPTIONS and
WRITE-TEXT. You will find descriptions of the SDF commands in the “Introductory Guide
to the SDF Dialog Interface”.
U22418-J-Z125-6-76
185
SESADM
Administration
START-MENU
PROGRAM : SESADM
-------------------------------------------------------------------------------AVAILABLE STATEMENTS:
13
16
17
18
28
34
38
39
END
EXECUTE-SYSTEM-CMD
HELP-MSG-INFORMATION
HOLD-PROGRAM
MODIFY-SDF-OPTIONS
REMARK
RESET-INPUT-DEFAULTS
RESTORE-SDF-INPUT
(!)
(!)
61
62
64
67
71
72
76
SHOW-INPUT-DEFAULTS
SHOW-INPUT-HISTORY
SHOW-SDF-OPTIONS
SHOW-STMT
START-DBH-ADMINISTRATION
START-DCN-ADMINISTRATION
WRITE-TEXT
-------------------------------------------------------------------------------NEXT =
Number / Next-stmt / *EXIT"K1" / *EXIT-ALL"F1"
LTG
TAST
Screen description
NEXT=
186
Enter here the number of the statement you want to use.
U22418-J-Z125-6-76
Administration
SESADM
DBH-MENU
The DBH-MENU selection screen is divided into three pages. The first page is shown
below. You will find the subsequent pages on the next two pages.
PROGRAM : SESADM
-------------------------------------------------------------------------------AVAILABLE STATEMENTS:
1 ABORT-LOCK-SEQUENCE
17 HELP-MSG-INFORMATION
3 ADD-OLD-TABLE-CATALOG-ENTRY
18 HOLD-PROGRAM
(!)
4 ADD-SQL-DB-CATALOG-ENTRY
19 HOLD-TRANSACTION-ADMISSION
5 ASSIGN-SYSLST
21 MODIFY-ADMINISTRATION
6 BEGIN-LOCK-SEQUENCE
22 MODIFY-CATALOG-ACCESS-RIGHTS
7 CANCEL-STATEMENT
23 MODIFY-CATID-LIST
8 CHANGE-CATLOG
25 MODIFY-REQUEST-CONTROL
9 CHANGE-DALOG
26 MODIFY-RESTART-CONTROL
10 CLOSE-SPACE
27 MODIFY-RETRIEVAL-CONTROL
11 COMMIT-PTC-TRANSACTION
28 MODIFY-SDF-OPTIONS
12 CREATE-DUMP
29 MODIFY-SQL-SORT-LIMIT
13 END
(!)
30 MODIFY-SUBORDER-LIMIT
14 END-FOREIGN-COPY
31 MODIFY-TRANSACTION-SECURITY
15 END-LOCK-SEQUENCE
(!)
32 PREPARE-FOREIGN-COPY
16 EXECUTE-SYSTEM-CMD
33 RELEASE-USER-RESOURCES
-------------------------------------------------------------------------------NEXT = +
Number / + / Next-stmt / *EXIT"K1" / *EXIT-ALL"F1"
LTG
TAST
Screen description
NEXT=
U22418-J-Z125-6-76
Enter here the number of the statement you want to use. There are three
pages of statements. To turn to the next page, enter a plus sign (+).
187
SESADM
Administration
DBH-MENU
The DBH-MENU selection screen is divided into three pages. The second page is shown
below. The first page of the screen is on the previous page.
PROGRAM : SESADM
-------------------------------------------------------------------------------AVAILABLE STATEMENTS:
34 REMARK
51 SET-TUNING-TRACE
36 REMOVE-OLD-TABLE-CATALOG-ENTRY
53 SET-USER-INACTIVE-TIME
37 REMOVE-SQL-DB-CATALOG-ENTRY
55 SHOW-CALL-DML-SUBORDERS
38 RESET-INPUT-DEFAULTS
56 SHOW-CATALOG-USERS
39 RESTORE-SDF-INPUT
57 SHOW-DBH-MEDIA-CATALOG
(!)
40 RESUME-TRANSACTION-ADMISSION (!)
58 SHOW-DBH-OPTIONS
(!)
42 REUSE-OLD-TABLE-CATALOG-ENTRY
60 SHOW-INACTIVE-SQL-USERS
(!)
43 ROLLBACK-PTC-TRANSACTION
61 SHOW-INPUT-DEFAULTS
44 ROLLBACK-TRANSACTION
62 SHOW-INPUT-HISTORY
45 SET-ACCOUNTING-PARAMETER
63 SHOW-OLD-TABLE-CATALOG-ENTRIES
46 SET-DBH-MSG-TRACE
64 SHOW-SDF-OPTIONS
47 SET-DIAGNOSIS-DUMP-PARAMETER
65 SHOW-SPACE-USERS
48 SET-REQUEST-CONTROL
66 SHOW-SQL-DB-CATALOG-ENTRIES
49 SET-SAT-SUPPORT
67 SHOW-STMT
50 SET-SQL-DB-CATALOG-STATUS
68 SHOW-TRANSACTIONS
-------------------------------------------------------------------------------NEXT = +
Number / + / - / Next-stmt / *EXIT"K1" / *EXIT-ALL"F1"
LTG
TAST
Screen description
NEXT=
188
Enter here the number of the statement you want to use. There are three
pages of statements. To turn to the next page, enter a plus sign (+).
U22418-J-Z125-6-76
Administration
SESADM
DBH-MENU
The DBH-MENU selection screen is divided into three pages. The third page is shown
below. You will find the first page on page 187.
PROGRAM : SESADM
-------------------------------------------------------------------------------AVAILABLE STATEMENTS:
39 RESTORE-SDF-INPUT
57 SHOW-DBH-MEDIA-CATALOG
(!)
40 RESUME-TRANSACTION-ADMISSION (!)
58 SHOW-DBH-OPTIONS
(!)
42 REUSE-OLD-TABLE-CATALOG-ENTRY
60 SHOW-INACTIVE-SQL-USERS
(!)
43 ROLLBACK-PTC-TRANSACTION
61 SHOW-INPUT-DEFAULTS
44 ROLLBACK-TRANSACTION
62 SHOW-INPUT-HISTORY
45 SET-ACCOUNTING-PARAMETER
63 SHOW-OLD-TABLE-CATALOG-ENTRIES
46 SET-DBH-MSG-TRACE
64 SHOW-SDF-OPTIONS
47 SET-DIAGNOSIS-DUMP-PARAMETER
65 SHOW-SPACE-USERS
48 SET-REQUEST-CONTROL
66 SHOW-SQL-DB-CATALOG-ENTRIES
49 SET-SAT-SUPPORT
67 SHOW-STMT
50 SET-SQL-DB-CATALOG-STATUS
68 SHOW-TRANSACTIONS
51 SET-TUNING-TRACE
69 SHOW-USER-SPACES
53 SET-USER-INACTIVE-TIME
70 SHOW-USERS
(!)
55 SHOW-CALL-DML-SUBORDERS
74 STOP-DBH
56 SHOW-CATALOG-USERS
76 WRITE-TEXT
-------------------------------------------------------------------------------NEXT =
Number / - / Next-stmt / *EXIT"K1" / *EXIT-ALL"F1"
LTG
TAST
Screen description
NEXT=
U22418-J-Z125-6-76
Enter here the number of the statement you want to use. There are three
pages of statements. To turn back to the previous page, enter a minus
sign (-).
189
SESADM
Administration
DCN-MENU
PROGRAM : SESADM
-------------------------------------------------------------------------------AVAILABLE STATEMENTS:
2 ADD-DISTRIBUTION-RULE-ENTRY
40 RESUME-TRANSACTION-ADMISSION (!)
12 CREATE-DUMP
41 RESUME-USER-ADMISSION
(!)
13 END
(!)
44 ROLLBACK-TRANSACTION
16 EXECUTE-SYSTEM-CMD
52 SET-USER-CALL-TRACE
17 HELP-MSG-INFORMATION
54 SET-USER-MSG-TRACE
18 HOLD-PROGRAM
(!)
59 SHOW-DISTRIBUTION-RULE-ENTRIES(!)
19 HOLD-TRANSACTION-ADMISSION
61 SHOW-INPUT-DEFAULTS
20 HOLD-USER-ADMISSION
(!)
62 SHOW-INPUT-HISTORY
21 MODIFY-ADMINISTRATION
64 SHOW-SDF-OPTIONS
24 MODIFY-DISTRIBUTION-RULE-ENTRY
67 SHOW-STMT
28 MODIFY-SDF-OPTIONS
68 SHOW-TRANSACTIONS
34 REMARK
70 SHOW-USERS
(!)
35 REMOVE-DISTRIBUTION-RULE-ENTRY
75 STOP-DCN
(!)
38 RESET-INPUT-DEFAULTS
76 WRITE-TEXT
39 RESTORE-SDF-INPUT
-------------------------------------------------------------------------------NEXT =
Number / Next-stmt / *EXIT"K1" / *EXIT-ALL"F1"
LTG
TAST
Screen description
NEXT=
5.1.3.4
Enter here the number of the statement you want to use.
SESADM control statements
On the following pages, you will find detailed descriptions of the SESADM control statements:
190
●
START-DBH-ADMINISTRATION
●
START-DCN-ADMINISTRATION
●
END
U22418-J-Z125-6-76
Administration
START-DBH-ADMINISTRATION
START-DBH-ADMINISTRATION
This statement starts DBH administration.
Function
START-DBH-ADMINISTRATION is an SESADM control statement. If you are working in
nonexpert mode, when you issue this statement, the DBH-MENU selection screen appears.
When you enter the START-DBH-ADMINISTRATION statement, you also specify which
DBH you want to administer.
START-DBH-ADMINISTRATION
PASSWORD = <c-string 3..3> / <x-string 5..6>
,DBH-NAME = *STD / <alphanum-name 1..1> / *BLANK
,CONFIGURATION-NAME = *HOME / <alphanum-name 1..1> / *BLANK
,HOST-NAME = *HOME / <name 1..8>
Operands
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password that prevents unauthorized administration of the DBH using SESADM. It is
assigned by means of the DBH option ADMINISTRATOR when the DBH is started.
DBH-NAME = *STD / <alphanum-name 1..1> / *BLANK>
Name by which the DBH to be administered is identified. The default is the DBH name
assigned via the configuration file. In a non-distributed configuration, only the default value
can be specified.
CONFIGURATION-NAME = *HOME / <alphanum-name 1..1> / *BLANK
Configuration name of the DBH to be administered. The default value is the name of the
home configuration in which SESADM is running. In a non-distributed configuration, only
the default value can be specified.
HOST-NAME = *HOME / <name 1..8>
Symbolic device name of the computer on which the DBH is loaded. The default value is
the name of the home system. In a non-distributed configuration, only the default value can
be specified.
U22418-J-Z125-6-76
191
START-DCN-ADMINISTRATION
Administration
START-DCN-ADMINISTRATION
This statement starts SESDCN administration.
Function
START-DCN-ADMINISTRATION is an SESADM control statement. If you are working in
nonexpert mode, when you issue this statement, the DCN-MENU selection screen
appears.
When you enter the START-DCN-ADMINISTRATION statement, you also specify which
SESDCN you want to administer.
START-DCN-ADMINISTRATION
PASSWORD = <c-string 3..3> / <x-string 5..6>
,DCN-NAME = *BLANK / <alphanum-name 1..1>
,CONFIGURATION-NAME = *HOME / <alphanum-name 1..1> / *BLANK
,HOST-NAME = *HOME / <name 1..8>
Operands
PASSWORD = <c-string 3..3> / <x-string 5..6>
Password that prevents unauthorized administration of the DBH using SESADM. It is
assigned by means of the DCN option ADMINISTRATOR when SESDCN is started.
DCN-NAME = *BLANK / <alphanum-name 1..1>
Name by which the SESDCN distribution component to be administered is identified. The
default is a blank.
CONFIGURATION-NAME = *HOME / <alphanum-name 1..1> / *BLANK
Configuration name of the SESDCN distribution component to be administered. The default
is the name of the home configuration in which SESADM is running.
HOST-NAME = *HOME / <name 1..8>
Symbolic device name of the computer on which the SESDCN distribution component is
loaded. The default is the name of the home system from which administration is carried
out.
192
U22418-J-Z125-6-76
Administration
END
END
This statement terminates SESADM.
Function
END is a SESADM control statement. When you issue it, SESADM terminates.
SESADM automatically checks the output of the statements. If a status other than “00” is
returned, SESADM sets task switch 11 and outputs a corresponding message.
END
Operands
This statement has no operands.
U22418-J-Z125-6-76
193
Administration statements and commands
Administration
5.2 Administration statements and commands
Administration statements and commands are available to you for dynamic administration:
–
DBH-specific administration statements and commands allow you to monitor and
influence the DBH session.
–
In distributed processing with SESAM/SQL-DCN, SESDCN-specific administration
statements and commands allow you to administer the SESDCN distribution
component.
Most administration statements and commands take effect immediately they are issued.
With some of them there may be a wait until the required resources are available.
Depending on the interface you use for administration, you issue administration statements
or administration commands.
–
Administration statements are for administration with SESADM. Their syntax complies
with SDF syntax rules (e.g. SHOW-INACTIVE-SQL-USERS), and they can be abbreviated in accordance with SDF conventions.
–
When you carry out administration using INFORM-PROGRAM or a CALL DML
program, you use administration commands, whose syntax is not subject to SDF rules
(e.g. USER,INACT).
Administration statements and administration commands offer the same functionality.
The following sections briefly describe the syntax and functions of the administration statements. You will find a list of administration statements and the equivalent commands as of
page 199.
Peculiarity of the linked-in DBH
You have to use administration commands to administer the linked-in DBH with INFORMPROGRAM or an integrated CALL DML program. It is not possible to use SESADM to
administer the linked-in DBH.
An administration command to the linked-in DBH is not processed until the next statement
is issued in the application program and control is thus passed to the DBH. In contrast,
administration statements and commands to the independent DBH are processed immediately.
194
U22418-J-Z125-6-76
Administration
Administration statements and commands
5.2.1 Summary of the contents of the administration statements
You will find below an overview of all the administration commands, divided up into groups
according to their purpose.
5.2.1.1
DBH administration statements
The DBH administration statements are divided up into three tables as follows:
–
The table 21 describes all administration statements that provide user-specific information.
–
The table 22 contains all administration statements that display or change the DBH
start statements and options issued.
–
The table 23 contains all other statements that can be used to control the DBH session.
Administration statement
Brief description
SHOW-USER-SPACES
Displays the spaces used by the user and thus locked
SHOW-CALL-DML-SUBORDERS Displays the number of active CALL DML requests of selected
users
SHOW-CATALOG-USERS
Displays the number of active users within a TA for selected
databases
SHOW-INACTIVE-SQL-USERS
Displays all inactive SQL users
SHOW-SPACE-USERS
Displays all active users of a selected space within a TA
together with relevant additional information
SHOW-TRANSACTIONS
Displays all open transactions of selected users together with
relevant additional information
SHOW-USERS
Displays all active users together with relevant additional information
Table 21: DBH administration statements for user-specific information
U22418-J-Z125-6-76
195
Administration statements and commands
Administration
Administration statement
Brief description
ADD-OLD-TABLE-CATALOG-ENTRY
Adds an entry to the CALL DML table catalog
ADD-SQL-DB-CATALOG-ENTRY
Adds an entry to the SQL database catalog
MODIFY-ADMINISTRATION
Changes the administration authorization
MODIFY-CATALOG-ACCESS-RIGHTS
Changes the access rights for the specified database
MODIFY-REQUEST-CONTROL
Changes the parameters for priority control
MODIFY-RESTART-CONTROL
Influences the duration of any restart
MODIFY-RETRIEVAL-CONTROL
Changes the criterion for interrupting retrieval statements
MODIFY-SQL-SORT-LIMIT
Changes the limit value for the number of sort records
found in a cursor table
MODIFY-SUBORDER-LIMIT
Changes the limit value for the maximum number of
SQL scans and/or logical files of CALL DML requests
MODIFY-TRANSACTION-SECURITY
Changes the transaction security parameters
REMOVE-OLD-TABLE-CATALOG-ENTRY Removes an entry from the CALL DML table catalog
REMOVE-SQL-DB-CATALOG-ENTRY
Removes an entry from the SQL database catalog
REUSE-OLD-TABLE-CATALOG-ENTRY
Create valid reference to an existing table entry in the
CALL DML table catalog
SET-ACCOUNTING-PARAMETER
Controls logging of request accounting for the RAV
procedure
SET-REQUEST-CONTROL
Turns priority control on and off
SET-USER-INACTIVE-TIME
Sets a time period after which a user's open but
inactive transactions are rolled back
SHOW-DBH-MEDIA-CATALOG
Displays the currently valid DBH option MEDIACATALOG
SHOW-DBH-OPTIONS
Displays the currently valid DBH options except for
MEDIA-CATALOG
SHOW-OLD-TABLE-CATALOG-ENTRIES
Displays the entries in the CALL DML table catalog
SHOW-SQL-DB-CATALOG-ENTRIES
Displays the entries in the SQL database catalog
Table 22: Administration statements that display or change DBH start statements and options
196
U22418-J-Z125-6-76
Administration
Administration statements and commands
Administration statement
Brief description
ABORT-LOCK-SEQUENCE
Terminate lock sequence of another user
ASSIGN-SYSLST
Switches the SYSLST file
BEGIN-LOCK-SEQUENCE
Starts a lock sequence
CANCEL-STATEMENT
Cancels a DML statement
CHANGE-CATLOG
Changes the CAT-LOG file and DA-LOG files
CHANGE-DALOG
Changes the DA-LOG file
CLOSE-SPACE
Close user space physically
COMMIT-PTC-TRANSACTION
Commits a PREPARE-TO-COMMIT transaction
CREATE-DUMP
Creates a main-memory dump
END-FOREIGN-COPY
Cancel “copy pending” state on spaces after foreign copy
END-LOCK-SEQUENCE
Terminate lock sequence
HOLD-TRANSACTION-ADMISSION
Suspends admission of further transactions
MODIFY-CATID-LIST
Updates the CATID list
PREPARE-FOREIGN-COPY
Closes a catalog logically in order to be able to create a
foreign copy
RELEASE-USER-RESOURCES
Releases all a user's resources
RESUME-TRANSACTIONADMISSION
Permits resumption of transaction admission
ROLLBACK-PTC-TRANSACTION
Rolls back a user's PREPARE-TO-COMMIT transaction
ROLLBACK-TRANSACTION
Rolls back a user's transaction
SET-DBH-MSG-TRACE
Controls the logging of DBH messages
SET-DIAGNOSIS-DUMP-PARAMETER Controls the creation of a dump
SET-SAT-SUPPORT
Controls the logging of security relevant events with SAT
SET-SQL-DB-CATALOG-STATUS
Changes the status of a database
SET-TUNING-TRACE
Controls request logging
STOP-DBH
Terminates a DBH session
Table 23: Other DBH administration statements that control database operation
U22418-J-Z125-6-76
197
Administration statements and commands
5.2.1.2
Administration
SESDCN administration statements
The following table provides an overview of all the administration statements that are
available for the administration of SESDCN:
Administration statement
Brief description
ADD-DISTRIBUTION-RULE-ENTRY
Adds a database to the distribution rule
CREATE-DUMP
Creates a main-memory dump
HOLD-TRANSACTION-ADMISSION
Suspends admission of further transactions
HOLD-USER-ADMISSION
Suspends admission of further users
MODIFY ADMINISTRATION
Changes the administration authorization
MODIFY-DISTRIBUTION-RULE-ENTRY
Changes the host name in the distribution rule
REMOVE-DISTRIBUTION-RULEENTRY
Removes a database entry or database entries from the
distribution rule
RESUME-TRANSACTION-ADMISSION
Resumes admission of transactions
RESUME-USER-ADMISSION
Resumes admission of new users
ROLLBACK-TRANSACTION
Rolls back a user's transaction
SET-USER-CALL-TRACE
Controls the logging of the statements of selected users
SET-USER-MSG-TRACE
Controls the logging of SESAM/SQL messages of
selected users
SHOW-DISTRIBUTION-RULE-ENTRIES Displays active databases entered in the distribution rule
SHOW-TRANSACTIONS
Displays all open transactions of selected users with
relevant additional information
SHOW-USERS
Displays all active users with relevant additional information
STOP-DCN
Terminates SESDCN
Table 24: SESDCN administration statements
198
U22418-J-Z125-6-76
Administration
Administration statements and commands
5.2.2 Equivalent administration statements and commands
This section contains two tables listing all the administration statements (for administration
using SESADM) and administration commands (for administration using
INFORM-PROGRAM or a CALL DML program), and indicating which statements and
commands are equivalent.
The table 25 contains the administration statements in alphabetical order. The table 26 has
the administration commands in alphabetical order.
Administration statement in SDF format
Administration command in ISP format
and at the CALL DML interface
ABORT-LOCK-SEQUENCE
LSQ,A[BORT]
ADD-DISTRIBUTION-RULE-ENTRY
UPD 1
ADD-OLD-TABLE-CATALOG-ENTRY
OPT,CDBC-INS
ADD-SQL-DB-CATALOG-ENTRY
OPT,DBC-INS
ASSIGN-SYSLST
SYSLST
BEGIN-LOCK-SEQUENCE
LSQ,B[EGIN]
CANCEL-STATEMENT
CANCEL
CHANGE-CATLOG
CAW
CHANGE-DALOG
DAW
CLOSE-SPACE
CLOSE,S[PACE]
COMMIT-PTC-TRANSACTION
CPTC
CREATE-DUMP
DUMP[,STOP]
END-FOREIGN-COPY
FCOPY,E[ND]
END-LOCK-SEQUENCE
LSQ,E[ND]
HOLD-TRANSACTION-ADMISSION
HOLD-TA (with SESDCN: HOLD,TA)
WAIT,HOLD 2
HOLD-USER-ADMISSION
HOLD,USER
MODIFY-ADMINISTRATION
OPT,ADM
MODIFY-CATALOG-ACCESS-RIGHTS
OPT,ACCESS
MODIFY-CATID-LIST
UPD,C[ID-LIST]
MODIFY-DISTRIBUTION-RULE-ENTRY
UPDPRO
MODIFY-REQUEST-CONTROL
OPT,REQ-CON
MODIFY-RESTART-CONTROL
OPT,RESTART
MODIFY-RETRIEVAL-CONTROL
OPT,RET-CON
MODIFY-SQL-SORTLIMIT
OPT,SORTLIMIT
Table 25: List of equivalent administration statements and commands
U22418-J-Z125-6-76
(part 1 of 3)
199
Administration statements and commands
Administration
Administration statement in SDF format
Administration command in ISP format
and at the CALL DML interface
MODIFY-SUBORDER-LIMIT
OPT,SUBORDERS
MODIFY-TRANSACTION-SECURITY
OPT,TA-SEC
PREPARE-FOREIGN-COPY
FCOPY,P[REPARE]
RELEASE-USER-RESOURCES
FREE
FREE,USER,INACT
REMOVE-DISTRIBUTION-RULE-ENTRY
DEL,DB
DEL,PRO-NAME
REMOVE-OLD-TABLE-CATALOG-ENTRY
OPT,CDBC-DEL
REMOVE-SQL-DB-CATALOG-ENTRY
OPT,DBC-DEL
RESUME-TRANSACTION-ADMISSION
GO-TA (at SESDCN: GO,TA)
RESUME-USER-ADMISSION
GO,USER
REUSE-OLD-TABLE-CATALOG-ENTRY
OPT,CDBC-REUSE
ROLLBACK-PTC-TRANSACTION
RPTC
ROLLBACK-TRANSACTION
RESET
SET-ACCOUNTING-PARAMETER
ACC,TP
SET-DBH-MSG-TRACE
TRACE
SET-DIAGNOSIS-DUMP-PARAMETER
OPT,DIAG,diag-spec
SET-REQUEST-CONTROL
OPT,REQ-CON or [,ON/,OFF]
SET-SAT-SUPPORT
OPT,SAT
SET-SQL-DB-CATALOG-STATUS
OPT,DBC-UPD
SET-TUNING-TRACE
COS
SET-USER-CALL-TRACE
TRACE=PAR,TYPE=CALL...
TRACE={ON|OFF...}
SET-USER-INACTIVE-TIME
OPT,INACT
SET-USER-MSG-TRACE
TRACE=PAR,TYPE=MSG...
TRACE={ON|OFF...}
SHOW-CALL-DML-SUBORDERS
USER
SHOW-CATALOG-USERS
USER,C[ATALOG]
SHOW-DBH-MEDIA-CATALOG
OPT,MEDIA
SHOW-DBH-OPTIONS
OPT
SHOW-DISTRIBUTION-RULE-ENTRIES
USER,CATALOG
SHOW-INACTIVE-SQL-USERS
USER,INACT
SHOW-OLD-TABLE-CATALOG-ENTRIES
OPT,CDBC-INFO
Table 25: List of equivalent administration statements and commands
200
(part 2 of 3)
U22418-J-Z125-6-76
Administration
Administration statements and commands
Administration statement in SDF format
Administration command in ISP format
and at the CALL DML interface
SHOW-SPACE-USERS
USER,SPACE
SHOW-SQL-DB-CATALOG-ENTRIES
OPT,DBC-INFO
SHOW-TRANSACTIONS
USER,TA
SHOW-USERS
USER,PR
SHOW-USER-SPACES
SPACE
STOP-DBH
STOP[,KEEP]
STOP,DELETE
STOP-DCN
STOP
Table 25: List of equivalent administration statements and commands
1
only in ISP format
2
only on the CALL-DML interface
Administration command in ISP format
and at the CALL DML interface
Administration statement
in SDF format
ACC,TP
SET-ACCOUNTING-PARAMETER
CAW
CHANGE-CATLOG
CANCEL
CANCEL-STATEMENT
CLOSE,S[PACE]
CLOSE-SPACE
COS
SET-TUNING-TRACE
CPTC
COMMIT-PTC-TRANSACTION
DAW
CHANGE-DALOG
DEL,DB
DEL,PRO-NAME
REMOVE-DISTRIBUTION-RULE-ENTRY
DUMP[,STOP]
CREATE-DUMP
FCOPY,E[ND]
END-FOREIGN-COPY
FCOPY,P[REPARE]
PREPARE-FOREIGN-COPY
FREE
FREE,USER,INACT
RELEASE-USER-RESOURCES
GO[-TA] (at SESDCN: GO,TA)
RESUME-TRANSACTION-ADMISSION
GO,USER
RESUME-USER-ADMISSION
HOLD-TA (at SESDCN: HOLD,TA)
HOLD-TRANSACTION-ADMISSION
HOLD,USER
HOLD-USER-ADMISSION
Table 26: List of equivalent administration commands and statements
U22418-J-Z125-6-76
(part 3 of 3)
(part 1 of 3)
201
Administration statements and commands
Administration
Administration command in ISP format
and at the CALL DML interface
Administration statement
in SDF format
LSQ,A[BORT]
ABORT-LOCK-SEQUENCE
LSQ,B[EGIN]
BEGIN-LOCK-SEQUENCE
LSQ,E[ND]
END-LOCK-SEQUENCE
OPT
SHOW-DBH-OPTIONS
OPT,ACCESS
MODIFY-CATALOG-ACCESS-RIGHTS
OPT,ADM
MODIFY-ADMINISTRATION
OPT,CDBC-DEL
REMOVE-OLD-TABLE-CATALOG-ENTRY
OPT,CDBC-INFO
SHOW-OLD-TABLE-CATALOG-ENTRIES
OPT,CDBC-INS
ADD-OLD-TABLE-CATALOG-ENTRY
OPT,CDBC-REUSE
REUSE-OLD-TABLE-CATALOG-ENTRY
OPT,DBC-DEL
REMOVE-SQL-DB-CATALOG-ENTRY
OPT,DBC-INFO
SHOW-SQL-DB-CATALOG-ENTRIES
OPT,DBC-INS
ADD-SQL-DB-CATALOG-ENTRY
OPT,DBC-UPD
SET-SQL-DB-CATALOG-STATUS
OPT,DIAG,diag-spec
SET-DIAGNOSIS-DUMP-PARAMETER
OPT,INACT
SET-USER-INACTIVE-TIME
OPT,MEDIA
SHOW-DBH-MEDIA-CATALOG
OPT,REQ-CON
MODIFY-REQUEST-CONTROL
OPT,REQ-CON
SET-REQUEST-CONTROL
OPT,RESTART
MODIFY-RESTART-CONTROL
OPT,RET-CON
MODIFY-RETRIEVAL-CONTROL
OPT,SAT
SET-SAT-SUPPORT
OPT,SORTLIMIT
MODIFY-SQL-SORTLIMIT
OPT,SUBORDERS
MODIFY-SUBORDER-LIMIT
OPT,TA-SEC
MODIFY-TRANSACTION-SECURITY
RESET
ROLLBACK-TRANSACTION
RPTC
ROLLBACK-PTC-TRANSACTION
SPACE
SHOW-USER-SPACES
STOP,DELETE
STOP[,KEEP]
STOP-DBH
STOP
STOP-DCN
SYSLST
ASSIGN-SYSLST
Table 26: List of equivalent administration commands and statements
202
(part 2 of 3)
U22418-J-Z125-6-76
Administration
Administration statements and commands
Administration command in ISP format
and at the CALL DML interface
Administration statement
in SDF format
TRACE=PAR,TYPE=CALL...
TRACE={ON|OFF...}
SET-USER-CALL-TRACE
TRACE=PAR,TYPE=MSG...
TRACE={ON|OFF...}
SET-USER-MSG-TRACE
TRACE={ON|OFF...}
SET-DBH-MSG-TRACE
UPD
1
ADD-DISTRIBUTION-RULE-ENTRY
UPD,C[ID-LIST]
MODIFY-CATID-LIST
UPDPRO
MODIFY-DISTRIBUTION-RULE-ENTRY
USER
SHOW-CALL-DML-SUBORDERS
USER,C[ATALOG]
SHOW-CATALOG-USERS
USER,CATALOG
SHOW-DISTRIBUTION-RULE-ENTRIES
USER,INACT
SHOW-INACTIVE-SQL-USERS
USER,PR
SHOW-USERS
USER,SPACE
SHOW-SPACE-USERS
USER,TA
SHOW-TRANSACTIONS
WAIT,HOLD
2
HOLD-TRANSACTION-ADMISSION
Table 26: List of equivalent administration commands and statements
1
Only in ISP format
2
Only on the CALL DML interface
U22418-J-Z125-6-76
(part 3 of 3)
203
Administration statements and commands
Administration
5.2.3 Descriptions in alphabetical order
This section provides a detailed description of the syntax and functions of the administration
statements and commands.
5.2.3.1
Description format
The descriptions of the administration statements all have the same structure. There is an
entry for each administration statement. The entry's heading is the name of the administration statement.
Each entry consists of several sections.
Sections that are not relevant to a specific statement are not included in its entry. The most
important sections are described overleaf.
Name of the administration statement
Brief description
Scope of validity
This section indicates the program to which the administration statement belongs, i.e.
whether it is:
–
a DBH administration statement (DBH administration)
–
an SESDCN administration statement (SESDCN administration)
–
a DBH and an SESDCN administration statement (DBH and SESDCN administration)
See also
This section contains references to DBH start statements, SESDCN control statements,
DBH or DCN options or administration statements that are relevant to the statement
described because they provide additional information.
204
U22418-J-Z125-6-76
Administration
User identification
Function
This section provides a detailed description of the administration statement.
It is followed by a syntax diagram.
Name of the administration statement
Operands
Operands
This section contains explanations of the various operands. The operands are dealt with in
the order in which they occur in the syntax diagram.
Administration command in ISP format and at the CALL DML interface
This section describes the syntax of the administration command that has the same
function as the administration statement.
The syntax of the administration command is only explained if it is not self-explanatory or if
its function deviates from that of the administration statement.
5.2.3.2
Syntax for the identification of users
In some administration statements and commands you have to select one or more users to
which the statement or command is to apply.
The identification of users is represented in abbreviated form in the syntax diagrams:
–
<user-identification> in the syntax of administration statements
–
user-identification in the syntax of administration commands.
In fact, the identification of users consists of up to four different partial qualifications.
A <user-identification> is partially qualified if not all data was specified for a user specification. A partially qualified <user-identification> can do more than identify a user.
Depending on the administration command, a partially qualified <user-identification> is only
permitted if it identifies exactly one user.
A <user-identification> is fully qualified when the user specifies all the relevant partial qualifications for unique identification.
U22418-J-Z125-6-76
205
User identification
Administration
Syntax of <user-identification> in administration statements
The complete syntax diagram of <user-identification> is as follows:
<user-identification> = *TSN(...) / *BY-SELECT(...)
*TSN(...)

TSN = <alphanum-name 4..4>
*BY-SELECT(...)






HOST-NAME = *NONE / <text 1..8>
,APPLICATION-NAME = *NONE / *TSN(...) / <text 1..8>
*TSN(...)

TSN = <alphanum-name 4..4>
,CUSTOMER-NAME = *NONE / <text 1..8>
,CONVERSATION-ID = *NONE / <x-text 1..8>
Operands
<user-identification> =
Identifies an SQL or CALL DML user or a group of such users.
<user-identification> = *TSN(...)
User's short ID.
The short ID is adequate for users from a timesharing program on the same computer.
TSN = <alphanum-name 4..4>
Task sequence number of the timesharing user's task
<user-identification> = *BY-SELECT(...)
Identifies the user (timesharing user or application user) by means of the user name, which
consists of different partial qualifications.
HOST-NAME = *NONE / <text 1..8>
Symbolic host name.
The default is *NONE (i.e. no entry is made for this operand).
APPLICATION-NAME = *NONE / *TSN(...) / <text 1..8>
Name of the application.
The default is *NONE (i.e. no entry is made for this operand).
APPLICATION-NAME = *TSN(...)
The name of the application corresponds to the TSN of the timesharing user's task.
TSN = <alphanum-name 4..4>
Task sequence number of the timesharing user's task
206
U22418-J-Z125-6-76
Administration
User identification
CUSTOMER-NAME = *NONE / <text 1..8>
Name of the user.
The default is *NONE (i.e. no entry is made for this operand). The name of the user
depends on the operating mode:
– TIAM: program name
– openUTM: KDCSIGN name
– DCAM: any name.
CONVERSATION-ID = *NONE / <x-text 1..8>
UTM conversation number.
You have to enter the conversation number whenever the user is an asynchronous UTM
conversation.
The default is *NONE (i.e. no entry is made for this operand).
U22418-J-Z125-6-76
207
User identification
Administration
Unique user identification
In some user-specific administration statements, it is enough to specify a partially qualified
<user-identification>. Other statements require that the user be identified uniquely. In such
cases, you must specify all the relevant partial qualifications of <user-identification>. These
cases are known as fully qualified.
Which partial qualifications of <user-identification> are relevant depends on the answers to
the following questions:
–
Is the user local or remote?
–
Is the user a timesharing or application user?
The following overview indicates what you have to enter to identify a user uniquely:
User
Entry
Local user in timesharing mode
TSN = <alphanum-name 4..4>
Remote user in timesharing mode
HOST-NAME = <text 1..8>
,APPLICATION-NAME = *TSN(...)
Local user in transaction mode
(non-openUTM)
APPLICATION-NAME = <text 1..8>
,CUSTOMER-NAME = <text 1..8>
Local user in transaction mode
(openUTM)
APPLICATION-NAME = <text 1..8>
,CUSTOMER-NAME = <text 1..8>
[,CONVERSATION-ID = <x-text 1..8>]
Remote user in transaction mode
(non-openUTM)
HOST-NAME = <text 1..8>
,APPLICATION-NAME = <text 1..8>
,CUSTOMER-NAME = <text 1..8>
Remote user in transaction mode
(openUTM)
HOST-NAME = <name 1..8>
,APPLICATION-NAME = <text 1..8>
,CUSTOMER-NAME = <text 1..8>
[,CONVERSATION-ID = <x-text 1..8>]
Table 27: Unique user identification
208
U22418-J-Z125-6-76
Administration
User identification
Syntax of user-identification in administration commands
The syntax of user-identification in the administration commands is as follows:
user-identification ::= {user-spec|tsn-spec}
user-spec ::= USER=[host],[{appl|tsn-spec}],[user][,vg-id]
tsn-spec ::= TSN=tsn
In cases in which unique identification of a user is required, you must specify all the relevant
partial qualifications:
User
Entry
Local user in timesharing mode
TSN=tsn
Remote user in timesharing mode
USER=host,TSN=tsn,
Local user in transaction mode (non-openUTM)
USER=,appl,[user]
Local user in transaction mode (openUTM)
USER=,appl,[user][,vg-id]
Remote user in transaction mode (non-openUTM)
USER=host,appl,[user]
Remote user in transaction mode (openUTM)
USER=host,appl,[user][vg-id]
Table 28: Partial qualifications with unique user identification
U22418-J-Z125-6-76
209
User identification
5.2.3.3
Administration
Identification of system-internal users
The identifications shown in the table below allow requests of system-internal users to be
identified, together with their type. These identifications can be output with the corresponding SHOW functions if there are any internal requests.
Identification
Type of the system-internal user
HOST-NAME = SESAM
,APPLICATION-NAME = SEND
,CUSTOMER-NAME = MESSAGE
System-internal administrator (this is an internal
user who issues administration commands via
INFORM-PROGRAM)
HOST-NAME = SESAM
,APPLICATION-NAME = RESTART
,CUSTOMER-NAME = <integer 1..7>
Internal user who, in the event of a restart, delays
the rollback of transactions until the resumption of
normal operation
HOST-NAME = SYSTEM
,APPLICATION-NAME = SYSTEM
,CUSTOMER-NAME = SYSTEM
All other internal users
Table 29: Unique identification of users
5.2.3.4
Alphabetical reference section
The administration statements are described below in alphabetical order.
The syntax of the equivalent administration command is given after the description of each
administration statement.
i
210
Note when entering administration commands that the operands must not be
separated by blanks.
U22418-J-Z125-6-76
Administration
ABORT-LOCK-SEQUENCE
ABORT-LOCK-SEQUENCE
This statement terminates the lock sequence of another user.
Scope of validity
DBH administration
See also
–
The DBH administration statement BEGIN-LOCK-SEQUENCE on page 224
–
The DBH administration statement END-LOCK-SEQUENCE on page 239
Function
The ABORT-LOCK-SEQUENCE statement terminates a lock sequence that is uniquely
identified by specifying the identification of the user.
All locks requested on databases and spaces during the lock sequence are released when
the lock sequence is terminated.
You cannot specify your own identification or that of the system-internal administrator (see page 210).
i
The system administrator can protect himself or herself against the termination of his or her
lock sequence by changing the password or administration authorization. The administrator
can make these changes by using the DBH option ADMINISTRATOR or the DBH administration statement MODIFY-ADMINISTRATION (see page 82 or page 243).
You must observe the following points when using the ABORT-LOCK-SEQUENCE
statement:
–
The administration statement is rejected if the SESAM DBH was loaded without transaction management.
–
The user addressed by means of the ABORT-LOCK-SEQUENCE administration
statement must be in a lock sequence. You can use the SHOW-USERS statement (see
page 331) to find out whether there is a lock sequence active for a specific user.
–
On input of the next statement, the addressed user receives a message indicating that
the lock sequence has been terminated.
U22418-J-Z125-6-76
211
ABORT-LOCK-SEQUENCE
Administration
ABORT-LOCK-SEQUENCE
USER = <user-identification>
Operands
USER = <user-identification>
Identifies the user whose lock sequence is to be terminated. The identification must be fully
qualified (see the section “Syntax for the identification of users” on page 205).
Administration command in ISP format and at the CALL DML interface
The LSQ,ABORT administration command corresponds to the ABORT-LOCK-SEQUENCE
administration statement here.
LSQ,A[BORT],user-identification
user-identification must be unique. You therefore have to specify all the relevant partial qualifications.
212
U22418-J-Z125-6-76
Administration
ADD-DISTRIBUTION-RULE-ENTRY
ADD-DISTRIBUTION-RULE-ENTRY
This statement adds a database to the distribution rule.
Scope of validity
SESDCN administration
See also
–
The SESDCN control statement ADD-DISTRIBUTION-RULE-LIST on page 164
–
The SESDCN control statement ADD-NETWORK-LINK-LIST on page 166
Function
The ADD-DISTRIBUTION-RULE-ENTRY statement adds a database entry to the distribution rule.
The logical name of the database you want to add to the distribution rule must be unique in
the distributed application and thus throughout the network. If the distribution rule already
contains an entry with the same logical database name, the administration statement is
rejected.
The distribution rule can contain up to 340 databases. If it is full, SESAM/SQL-DCN rejects
the administration statement.
The administration statement is also rejected if a DBH would be assigned to several
SESDCNs as a result of accepting it.
ADD-DISTRIBUTION-RULE-ENTRY
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
,DBH-NAME = *BLANK / <alphanum-name 1..1>
,DCN-NAME = *BLANK / <alphanum-name 1..1>
,CONFIGURATION-NAME = *STD / <alphanum-name 1..1> / *BLANK
,HOST-NAME = *STD / <name 1..8>
U22418-J-Z125-6-76
213
ADD-DISTRIBUTION-RULE-ENTRY
Administration
Operands
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Logical database name of the SESAM/SQL database or CALL DML table to be entered.
The logical database name is the name by which a database or CALL DML table is
addressed in the application program.
The logical database name must be unique throughout the network.
DBH-NAME = *BLANK / <alphanum-name 1..1>
Name of the SESAM/SQL DBH to which the database is assigned
DCN-NAME = *BLANK / <alphanum-name 1..1>
Name of the remote DCN that forwards remote accesses to the database
CONFIGURATION-NAME = *STD / <alphanum-name 1..1> / *BLANK
Name of the configuration to which the remote DCN is assigned.
The default is the name of the configuration in which administration is being carried out, i.e.
the configuration assigned to the SESDCN that is carrying out administration. This is the
configuration specified by the last START-DCN-ADMINISTRATION statement.
HOST-NAME = *STD / <name 1..8>
Symbolic device name of the computer on which the database to be entered resides.
The default is the name of the computer on which the SESDCN carrying out administration
is running. This is the computer specified by the last START-DCN-ADMINISTRATION
statement.
Administration command in ISP format
The UPD administration command corresponds to the ADD-DISTRIBUTION-RULEENTRY administration statement.
[tsn,]UPD,CATALOG=db-name,PRO=processor[,CNF=k][,DCN=x][,DBH=z]
CNF, DCN and DBH can contain blanks as parameter values. You must enter an underscore
(_) as a metacharacter for a blank.
214
U22418-J-Z125-6-76
Administration
ADD-OLD-TABLE-CATALOG-ENTRY
ADD-OLD-TABLE-CATALOG-ENTRY
This statement adds an entry to the CALL DML table catalog.
Scope of validity
DBH administration
See also
–
The DBH start statement ADD-OLD-TABLE-CATALOG-LIST on page 73
–
The DBH start statement ADD-SQL-DATABASE-CATALOG-LIST on page 76
–
The DBH option OLD-TABLE-CATALOG on page 102
Function
The ADD-OLD-TABLE-CATALOG-ENTRY statement adds an entry to the CALL DML table
catalog.
You can only use this administration statement to add a new entry if there is a free entry in
the CALL DML table catalog. If the CALL DML table catalog is full, the administration
statement is rejected and an error message appears.
The logical database to which you want to assign the CALL DML table must be entered in
the SQL database catalog. You can use the SHOW-SQL-DB-CATALOG-ENTRIES administration statement to check this. If the logical database name does not exist, the CALL DML
table you want to enter cannot be accessed. The CALL DML table remains inaccessible
even if you add the logical database name subsequently, using the ADD-SQL-DBCATALOG-ENTRY administration statement or the CREATE-CATALOG statement, for
example.
The CALL DML table name must be unique (even if a replication is involved); in other words,
this name must not already exist in the CALL DML table catalog.
SESAM/SQL does not check whether the CALL DML table you want to enter really does
exist. Neither does it check whether the table is accessible to CALL DML.
If the CALL DML table is not available after the administration statement is accepted, all
subsequent CALL DML Open statements are rejected and the status indicated. If you then
use the SQL statement CREATE TABLE to create the appropriate CALL DML table subsequently, it will only be accessible to CALL DML when you create a valid reference to an
existing entry using the REUSE-OLD-TABLE-CATALOG-ENTRY administration statement.
U22418-J-Z125-6-76
215
ADD-OLD-TABLE-CATALOG-ENTRY
Administration
ADD-OLD-TABLE-CATALOG-ENTRY
CALL-DML-TABLE-NAME = <text 1..17>
,CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
,SCHEMA-NAME = < c-string 1..31 with-lowercase>
,TABLE-NAME = <c-string 1..31 with-lowercase>
Operands
CALL-DML-TABLE-NAME = <text 1..17>
CALL DML table name used in the CALL DML Open statement. You must enter this name
in full (17 characters). It must be unique, even if a replication is involved.
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database to which the CALL DML table is to be assigned. This name
must be entered in the SQL database catalog.
SCHEMA-NAME = < c-string 1..31 with-lowercase>
Name of the schema to which the CALL DML table is to be assigned.
TABLE-NAME = <c-string 1..31 with-lowercase>
Base table name corresponding to CALL-DML-TABLE-NAME.
216
U22418-J-Z125-6-76
Administration
ADD-OLD-TABLE-CATALOG-ENTRY
Administration command in ISP format and at the CALL DML interface
The OPT,CDBC-INS administration command corresponds to the ADD-OLD-TABLECATALOG-ENTRY administration statement.
OPT,CDBC-INS,C[ALL-DML-]T[ABLE]=call-dml-table-name
,C[ATALOG]=catalog-name
,S[CHEMA]=schema-name
,T[ABLE]=table-name
call-dml-table-name, catalog-name, schema-name and table-name must not contain commas,
since commas act as delimiters.
If you conclude the OPT,CDBC-INS administration command with a comma, the DBH
expects more entries for it.
To ensure these are assigned correctly, you must always include the parameter
CALL-DML-TABLE=call-dml-table-name with them!
If you want the DBH to execute the administration command, you must not conclude it with
a comma. If you conclude an administration command with a comma and follow it with
another administration command, the DBH does not execute the first of the two commands
and an error message appears.
U22418-J-Z125-6-76
217
ADD-SQL-DB-CATALOG-ENTRY
Administration
ADD-SQL-DB-CATALOG-ENTRY
This statement adds an entry to the SQL database catalog.
Scope of validity
DBH administration
See also
–
The DBH start statement ADD-SQL-DATABASE-CATALOG-LIST on page 76
–
The DBH option SQL-DATABASE-CATALOG on page 122
Function
The ADD-SQL-DB-CATALOG-ENTRY statement adds an entry to the SQL database
catalog.
You can only use this administration statement to add a new entry if there is a free entry in
the SQL database catalog. If the SQL database catalog is full, the administration statement
is rejected and an error message appears.
The database name you enter in the SQL database catalog must be unique; in other words,
neither the logical nor the physical database name must already be entered in the SQL
database catalog. This also applies to replications.
ADD-SQL-DB-CATALOG-ENTRY
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
,PHYS-CATALOG-NAME = *NONE / <filename 1..18 without-cat-id-user-id-generation-version>
,USER-ID = *DBH-USER-ID / <name 1..8>
,PASSWORD = *NONE / <c-string 1..4> / <x-string 1..8> / <integer -2147483648..2147483647>
,ACCESS = *ALL / *PARAMETERS (...) / *COPY
*PARAMETERS (...)




READ = *YES / *NO
,WRITE = *YES / *NO
,CAT-ADMINISTRATION = *YES / *NO
,REPLICATION = *YES / *NO
,COPY-NUMBER = *NONE / <integer 1..9999>
218
U22418-J-Z125-6-76
Administration
ADD-SQL-DB-CATALOG-ENTRY
Operands
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database to be entered.
The logical database name is the name by which a database is addressed in the application
program.
The logical database name must be unique; in other words, this name must not already be
entered in the SQL database catalog. This also applies to replications.
PHYS-CATALOG-NAME = *NONE /
<filename 1..18 without-cat-id-user-id-generation-version>
Physical name of the database to be entered.
The physical database name must be unique; in other words, this name must not already
be entered in the SQL database catalog. This also applies to replications.
If you select *NONE, the default, for PHYS-CATALOG-NAME, SESAM/SQL forms the
physical database name from the logical database name you assigned by means of
CATALOG-NAME.
USER-ID = *DBH-USER-ID / <name 1..8>
DB user ID of the database.
The default for USER-ID is the DBH user ID.
PASSWORD = *NONE / <c-string 1..4> / <x-string 1..8> /
<integer -2147483648..2147483647>
BS2000 password that protects the files in the database from unauthorized access.
If you select the default (*NONE), the DBH can only access the database when the BS2000
files in the database are not password protected.
ACCESS =
Defines which access functions are permitted with regard to the database.
ACCESS = *ALL
Access to the database is unrestricted. Read and write access are permitted to both user
data and metadata.
ACCESS = *PARAMETERS (...)
Access to the database is restricted.
The parameters are arranged in a hierarchical structure: if CAT-ADMINISTRATION is
permitted, so, implicitly, are WRITE and READ; in the same way, WRITE implicitly permits
READ.
At least one parameter must be specified with YES.
READ = *YES
Permits read access to user data and metadata. The data can be read but not changed.
U22418-J-Z125-6-76
219
ADD-SQL-DB-CATALOG-ENTRY
Administration
READ = *NO
Prevents access to user data and metadata.
The database entered cannot be accessed until the lock is lifted by means of the
MODIFY-CATALOG-ACCESS-RIGHTS administration statement.
It makes no sense to select READ = NO if you use the default (YES) for either
CAT-ADMINISTRATION or WRITE, since CAT-ADMINISTRATION implicitly permits
WRITE, and WRITE implicitly permits READ.
WRITE = *YES
Permits read and write access to user data. Metadata can be read but not changed.
WRITE implicitly permits READ.
WRITE = *NO
Prevents write access to user data and metadata.
It makes no sense to select WRITE = NO if you use the default (YES) for the
CAT-ADMINISTRATION parameter, since CAT-ADMINISTRATION implicitly permits
WRITE.
CAT-ADMINISTRATION = *YES
Permits read and write access to both user data and metadata. CAT-ADMINISTRATION
implicitly permits WRITE and thus also READ.
CAT-ADMINISTRATION = *NO
Prevents changes being made to the metadata in the catalog space of the database. It
therefore prevents the use of the following statements:
– SQL statements for schema definition and management and memory management
– utility statements
REPLICATION = *YES
The database to be entered is a replication. Only read access and the REFRESH
REPLICATION utility statement are permitted for a replication.
REPLICATION = *NO
The database to be entered is not a replication.
ACCESS = *COPY
After entry in the SQL-DB database catalog, only read access is permitted for this database
(as with ACCESS = READ) in addition to the COPY utility statement. The other access
functions are not permitted. As soon as COPY has been successfully executed, the
parameter CAT-ADMINISTRATION=YES is set (i.e. read and write access is permitted for
both user data and metadata).
If you want to enter the duplicate of a database in the SQL database catalog, you should
select ACCESS=COPY. This prevents changes being made to the duplicate of the
database before a SESAM backup copy has been created (see the “Core Manual”).
220
U22418-J-Z125-6-76
Administration
ADD-SQL-DB-CATALOG-ENTRY
COPY-NUMBER = *NONE
The database to be entered is not a SESAM backup copy.
COPY-NUMBER =<integer 1..9999>
The SESAM backup copy of the catalog space with the specified number is added to the
SQL database catalog. If the number of a SESAM backup copy was specified for the COPYNUMBER operand, specification of ACCESS is not permitted. In this case, the access
rights READ=YES, WRITE=NO and CAT-ADMIN=NO are set for ACCESS by default.
Administration command in ISP format and at the CALL DML interface
The OPT,DBC-INS administration command corresponds to the ADD-SQL-DB-CATALOGENTRY administration statement.
OPT,DBC-INS,C[ATALOG]=catalog-name
[,P[HYSICAL-NAME]=physical-name]
[,U[SERID]=userid]
[,P[ASS]W[ORD]=password]
[,A[CCESS]=(access)]
[,COPY-NR=copyno]
access ::= R[EAD],W[RITE],A[DMIN],C[OPY],REPL[ICATION]
catalog-name and physical-name must not contain any commas, since commas act as delimiters.
If access is not specified, the access functions READ, WRITE and ADMIN are permitted. If
access was specified, specification of copyno is not permitted.
copyno contains the four-digit number of the SESAM backup copy of the catalog space. If
copyno was specified:
–
the specified database must be a complete SESAM backup copy of a database, i.e. one
created by means of COPY CATALOG
–
specification of access is not permitted; ACCESS is set to READ by default
READ permits only read access, WRITE implicitly includes READ, and ADMIN implicitly
includes WRITE and thus also READ.
The value REPLICATION means that this database is a replication. With this entry, only a
replication can be accessed. Only read access and the REFRESH REPLICATION utility
statement are permitted for a replication.
U22418-J-Z125-6-76
221
ADD-SQL-DB-CATALOG-ENTRY
Administration
If you conclude the OPT,DBC-INS administration statement with a comma, the DBH
expects more entries for it. To ensure that these are assigned correctly, you must enter the
parameter CATALOG=catalog-name for them.
If you want the DBH to execute the administration command, you must not conclude it with
a comma. If you conclude an administration command with a comma and follow it with
another administration command, the DBH does not execute the first of the two commands,
and an error message appears.
222
U22418-J-Z125-6-76
Administration
ASSIGN-SYSLST
ASSIGN-SYSLST
This statement switches the SYSLST file.
Scope of validity
DBH administration
Function
You can use the ASSIGN-SYSLST statement to switch the SYSLST file of the first DBHTASK. The command only affects the SYSLST file of the first DBH-TASK that is logging the
currently running session in SESAM/SQL V3.0 and higher.
ASSIGN-SYSLST
TO-FILE = <filename 1..54> / *PRIMARY
Operands
TO-FILE =
Assigns the SYSLST file to an output destination.
TO-FILE = <filename 1..54>
Name of the file to which you assign the SYSLST file.
The name must comply with BS2000 conventions.
TO-FILE = *PRIMARY
Resets the SYSLST file to the primary assignment.
Administration command in ISP format and at the CALL DML interface
The SYSLST administration command corresponds to the ASSIGN-SYSLST administration statement.
SYSLST={filename|(PRIMARY)}
Note when entering the administration command that the file name must not be longer than
54 characters.
U22418-J-Z125-6-76
223
BEGIN-LOCK-SEQUENCE
Administration
BEGIN-LOCK-SEQUENCE
This statement starts a lock sequence.
Scope of validity
DBH administration
See also
–
The DBH administration statement END-LOCK-SEQUENCE on page 239
–
The DBH administration statement ABORT-LOCK-SEQUENCE on page 211
Function
The BEGIN-LOCK-SEQUENCE statement puts the administrator in a state in which all
locks subsequently placed on database catalogs and spaces are maintained. This state
continues until the lock sequence is terminated by one of the administration statements
END-LOCK-SEQUENCE or ABORT-LOCK-SEQUENCE.
You must observe the following points:
–
The BEGIN-LOCK-SEQUENCE statement itself does not impose any locks.
–
Only administration statements are permitted in the lock sequence.
–
The ROLLBACK-TRANSACTION administration statement is not permitted in a lock
sequence and leads to an error message. The RELEASE-USER-RESOURCES
statement is ignored in a lock sequence. Another lock sequence can thus only be terminated with ABORT-LOCK-SEQUENCE.
–
The user must not have opened any other lock sequences in the DBH in which the
statement was issued. For administration via the CALL DML interface, this applies to
the DBH at which the command is issued.
–
The administration statement is rejected if the SESAM DBH was loaded without transaction management.
BEGIN-LOCK-SEQUENCE
MODE = *WAIT / *FORCED
224
U22418-J-Z125-6-76
Administration
BEGIN-LOCK-SEQUENCE
Operands
MODE =
Specifies how the locks are applied in a lock sequence if they cannot be implemented
immediately. This is the case when the object to be locked is still locked by another user.
MODE = *WAIT
There is a wait until the user responsible for locking the object unlocks it.
MODE = *FORCED
If possible, the user responsible for locking the object is rolled back. This is not possible if
the transaction to be rolled back is in the PTC status or is running in another lock sequence.
In this case, the current administration statement is rejected with an appropriate message.
Administration command in ISP format and at the CALL DML interface
The LSQ,BEGIN administration command corresponds to the BEGIN-LOCK-SEQUENCE
administration statement here.
LSQ,B[EGIN],mode
mode::= {W[AIT]|
F[ORCED]}
The mode parameter must be specified.
U22418-J-Z125-6-76
225
CANCEL-STATEMENT
Administration
CANCEL-STATEMENT
This statement cancels a DML statement.
Scope of validity
DBH administration
Function
The CANCEL-STATEMENT statement cancels the processing of a statement that manipulates a user's data.
Note the following:
–
The user must be active in the DBH.
–
If a rollback of the transaction has already been registered for the user, the DBH accepts
the administration statement but does not execute it.
–
A CANCEL-STATEMENT statement cannot cancel a previous CANCEL-STATEMENT
statement.
CANCEL-STATEMENT
USER = <user-identification>
Operands
USER = <user-identification>
Identifies the user to which the CANCEL-STATEMENT statement applies. The identification
must be unique. You must therefore specify all the relevant partial qualifications (see section
“Syntax for the identification of users” on page 205).
Administration command in ISP format and at the CALL DML interface
The CANCEL administration command corresponds to the CANCEL-STATEMENT administration statement.
CANCEL,user-identification
226
U22418-J-Z125-6-76
Administration
CHANGE-CATLOG
CHANGE-CATLOG
This statement changes the CAT-LOG file and the DA-LOG files and creates a copy of the
CAT-REC file.
Scope of validity
DBH administration
Function
You can use the CHANGE-CATLOG statement to close the CAT- LOG file and the DA-LOG
files for the specified database or databases and open the next one, and to create a copy
of the CAT-REC file.
The copy of the CAT-REC file is created in the media of the CAT-LOG file. It cannot be
created on tape.
If the database – and hence also the CAT-REC file – is located in a DB user ID, a file is
created with the name catalog-name.CAT-REC.COPY. Where possible this is done on the DB
user ID. You will find further details about database files and job variables on foreign user
IDs in the section of the same name in the “Core Manual”. If the file cannot be created on
the DB user ID it is created on the DBH user ID.
The CHANGE-CATLOG statement is rejected with an error message in the following situations:
–
–
–
–
–
–
–
–
–
–
the specified database does not belong to the configuration
the specified database is being run without LD backup
READ access only is allowed for the specified database
the specified database is in the “copy pending” state
the specified database cannot be locked during processing (due to parallel utility, DDL
or administration statements)
the specified database is a SESAM backup copy or a replication
SELECT = *ALL is specified and one of the databases cannot be locked during
processing (due to parallel utility, DDL or administration statements).
The name of the database where the error occurred is output; the action was executed
for all databases with LD backup that are before this database in the ordered list of DBC
entries (corresponding to the output for SHOW-SQL-DB-CATALOG-ENTRIES)
the specified database is closed or defective
the specified database is used by utility or administration statements in the moment
there is a resource bottleneck.
U22418-J-Z125-6-76
227
CHANGE-CATLOG
Administration
If you do not specify any databases, the CAT-LOG file and the DA-LOG files are switched
in the order given in the database directory and the action is performed for all databases
with an LD backup. For databases for which logging is not activated, the statement is
ignored.
CHANGE-CATLOG
SELECT = *ALL / *LOGICAL(...) / *PHYSICAL(...)
*LOGICAL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*PHYSICAL(...)

PHYS-CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Operands
SELECT =
Specifies the databases for which the CAT-LOG file and DA-LOG files are to be changed.
SELECT = *ALL
The CAT-LOG file and DA-LOG files of all the databases for which logging is activated are
changed.
SELECT = *LOGICAL(...)
Selection of the database(s) whose CAT-LOG and DA-LOG files are to be changed
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database
SELECT = *PHYSICAL(...)
Selection of the database(s) whose CAT-LOG and DA-LOG files are to be changed
PHYS-CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Physical name of the database
228
U22418-J-Z125-6-76
Administration
CHANGE-CATLOG
Administration command at the CALL DML interface
The CAW administration command corresponds to the CHANGE-CATLOG administration
statement. The CAW administration statement can be issued at the CALL DML interface or
through the INFORM-PROGRAM interface.
CAW[,supplement]
supplement ::= {C[ATALOG]=catalog-name|
P[HYSICAL-NAME]=physical-name}
You can specify the logical name of the database in catalog-name using up to 18 characters.
You can specify the physical name of the database in physical-name using up to
18 characters.
U22418-J-Z125-6-76
229
CHANGE-DALOG
Administration
CHANGE-DALOG
This statement changes the DA-LOG files.
Scope of validity
DBH administration
Function
You can use the CHANGE-DALOG statement when logging to close the DA-LOG files for
the specified database or databases and open the next DA-LOG file.
If you specify databases that do not belong to the configuration or for which logging is not
activated, the statement is rejected.
If you do not specify any databases, the DA-LOG files are changed in the order of the
catalog list. If logging is not activated, the statement is ignored.
The CHANGE-DALOG statement is not permitted while a database is being processed by
a utility statement, and it is rejected with an error message.
The CHANGE-DALOG statement is rejected with an error message in the following situations:
–
–
–
–
–
–
–
–
–
–
–
230
the specified database does not belong to the configuration
logging is not turned on for the specified database
the specified database is being run without LD backup
READ access only is allowed for the specified database
the specified database is a SESAM backup copy or a replication
the specified database is closed or defective
if only READ access is allowed for the specified database
the specified database is in the “copy pending” state
the specified database cannot be locked during processing (due to parallel utility, DDL
or administration statements)
if SELECT = *ALL is specified and one of the databases cannot be locked during
processing (due to parallel utility, DDL or administration statements).
The name of the database where the error occurred is announced; the action was
executed for all databases with LD backup that are before this database in the ordered
list of DBC entries (corresponding to the output for SHOW-SQL-DB-CATALOGENTRIES)
if there is a resource bottleneck.
U22418-J-Z125-6-76
Administration
CHANGE-DALOG
CHANGE-DALOG
SELECT = *ALL / *LOGICAL(...) / *PHYSICAL(...)
*LOGICAL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*PHYSICAL(...)

PHYS-CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Operands
SELECT =
Specifies the databases for which the DA-LOG files are to be changed.
SELECT = *ALL
The DA-LOG files for all databases for which logging is activated are changed.
SELECT = *LOGICAL(...)
Selection of the database(s) whose DA-LOG file is to be changed
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database.
SELECT = *PHYSICAL(...)
Selection of the database(s) for the DA-LOG files is to be changed.
PHYS-CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Physical name of the database.
Administration command at the CALL DML interface
The DAW administration command corresponds to the CHANGE-DALOG administration
statement. The DAW administration command cannot be issued at the CALL DML interface
and through the INFORM-PROGRAM interface.
DAW[,supplement]
supplement ::= {C[ATALOG]=catalog-name|
P[HYSICAL-NAME]=physical-name}
You can specify the logical name of the database in catalog-name using up to 18 characters.
You can specify the physical name of the database in physical-name using up to
18 characters.
U22418-J-Z125-6-76
231
CLOSE-SPACE
Administration
CLOSE-SPACE
This statement physically closes the user space.
Scope of validity
DBH administration
See also
–
The DBH administration statement SHOW-SPACE-USERS on page 322
–
The DBH administration statement BEGIN-LOCK-SEQUENCE on page 224
–
The DBH administration statement END-LOCK-SEQUENCE on page 239
Function
The CLOSE-SPACE statement physically closes the specified user space. The prerequisite
for this is that the user space must be free of transactions. This is ensured by the DBH for
the duration of the close operation. You can find out which users are currently using a space
by using the SHOW-SPACE-USERS statement.
In the following situations it is necessary to close a user space physically:
–
when a foreign copy is created using the TimeFinder function (see the “Core Manual”)
–
when private disks are used for spaces and the storage area of the spaces is to be
changed (with the BS2000 command MODIFY-FILE-ATTRIBUTES, see the BS2000
manual “Commands, Volumes 1 - 5”)
i
Note that closing the user spaces does not lock them in the sense that it prevents
further accesses. The space is opened again each time it is accessed. You can
prevent this happening by issuing the CLOSE-SPACE statement in a lock
sequence. Lock sequences are opened with BEGIN-LOCK-SEQUENCE. ENDLOCK-SEQUENCE terminates the sequence and unlocks the space again.
If the space is already closed when the statement is issued, the statement is executed
without a message being issued. Logical files or cursor positions that reference the space
are lost when it is physically closed.
232
U22418-J-Z125-6-76
Administration
CLOSE-SPACE
CLOSE-SPACE
SPACE-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
,CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Operands
SPACE-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Name of the space to be closed. The name of the space is specified without the physical
database name.
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database to which the space to be closed belongs
Administration command in ISP and at the CALL DML interface
The CLOSE,SPACE administration command corresponds to the CLOSE-SPACE administration statement here.
CLOSE,S[PACE]=space-name,C[ATALOG]=catalog-name
U22418-J-Z125-6-76
233
COMMIT-PTC-TRANSACTION
Administration
COMMIT-PTC-TRANSACTION
This statement commits a PTC transaction.
Scope of validity
DBH administration
See also
The ROLLBACK-PTC-TRANSACTION administration statement on page 280
Function
The COMMIT-PTC-TRANSACTION statement commits a user's PTC transactions. A PTC
transaction is a distributed transaction that has the status “prepared to commit” (see the
“Core Manual”).
openUTM-D and SESAM/SQL-DCN permit distributed transactions involving several DBHs.
Distributed or PTC transactions are divided into three phases:
1. the processing of the transaction
2. the prepare-to-commit phase
3. the commitment (completion) of the transaction
In an external restart of the SESAM/SQL DBH, the transaction and restart mechanism of
openUTM-D or SESAM/SQL-DCN controls the final commitment and, if appropriate, rolling
back of PTC transactions.
If a restart through openUTM-D or SESAM/SQL-DCN is not possible because, for example,
the computers involved are no longer accessible, the system administrator can use the
COMMIT-PTC-TRANSACTION administration statement to complete and thus commit a
user's PTC transactions in the node for which he or she is responsible.
This statement only affects PTC transactions. If no PTC transactions are active in the DBH,
the statement is rejected. It is also rejected if the DBH was loaded without transaction
management.
If a user does not have any transaction in the PTC status, then a message is output.
i
234
You should only use the COMMIT-PTC-TRANSACTION administration statement
after careful consideration; it can destroy the cross-node logical consistency of the
transactions involved.
U22418-J-Z125-6-76
Administration
COMMIT-PTC-TRANSACTION
COMMIT-PTC-TRANSACTION
USER = <user-identification>
Operands
USER = <user-identification>
Identifies the user whose PTC transactions are to be completed. The identification must be
unique so you must specify all the relevant partial qualifications (see section “Syntax for the
identification of users” on page 205).
Administration command in ISP format and at the CALL DML interface
The CPTC administration command corresponds to the COMMIT-PTC-TRANSACTION
administration statement.
CPTC,user-identification
U22418-J-Z125-6-76
235
CREATE-DUMP
Administration
CREATE-DUMP
This statement creates a main memory dump and optionally terminates the DBH or
SESDCN session.
Scope of validity
DBH and SESDCN administration
Function
You use the CREATE-DUMP statement to create a main-memory dump.
The DBH or SESDCN session normally continues after this statement is issued. However,
you can cause the session to be terminated once the dump has been created.
CREATE-DUMP
CANCEL-PROGRAM = *NO / *YES
Operands
CANCEL-PROGRAM = *NO
This is the default. The DBH or SESDCN session continues after the dump is created. In
DBH administration, the DBH issues the consistency check SESADXS: XX/05/99 after this
statement is issued.
CANCEL-PROGRAM = *YES
After the dump is created, the DBH or SESDCN session is terminated.
In DBH administration, the DBH issues the consistency check SESADXS: XX/40/99 after
this statement is issued.
If databases are being edited (by means of SQL statements or CALL DML statements)
when the session is terminated, an external restart is necessary. If transaction
management was not set for the session, the databases involved have to be repaired by
means of media recovery (see the “Core Manual”).
Administration command in ISP format and at the CALL DML interface
The DUMP[,STOP] administration command corresponds to the CREATE-DUMP administration statement. The STOP parameter is not permitted for SESDCN. The SESDCN
session therefore cannot be terminated by means of the DUMP administration command.
DUMP[,STOP]
236
U22418-J-Z125-6-76
Administration
END-FOREIGN-COPY
END-FOREIGN-COPY
This statement cancels any “copy pending” state in the spaces after a foreign copy.
Scope of validity
DBH administration
See also
–
The DBH administration statement PREPARE-FOREIGN-COPY on page 265
–
The DBH administration statement BEGIN-LOCK-SEQUENCE on page 224
–
The DBH administration statement END-LOCK-SEQUENCE on page 239
Function
Use the END-FOREIGN-COPY statement to cancel any “copy pending” state which has
been created by placing a utility statement preceding the foreign copy.
!
CAUTION!
If the “copy pending” state is canceled by means of END-FOREIGN-COPY without
a consistent foreign copy having been created, the space can no longer be repaired
correctly by means of RECOVER.
If the statement is issued in a lock sequence, the locks on the database entries and spaces
are not canceled until the lock sequence is terminated. Lock sequences can be opened with
BEGIN-LOCK-SEQUENCE and terminated with END-LOCK-SEQUENCE.
The statement END-FOREIGN-COPY can also be specified without the prior statement
PREPARE-FOREIGN-COPY. If END-FOREIGN-COPY is not preceded by the statement
PREPARE-FOREIGN-COPY, the “copy pending” state will be cancelled from all catalog
spaces.
If a preceding PREPARE-FOREIGN-COPY statement is used in the same administration
session, the statement END-FOREIGN-COPY will only be active in the spaces entered in
the PREPARE-FOREIGN-COPY statement.
If several PREPARE-FOREIGN-COPY statements have been specified, END-FOREIGNCOPY only acts on the last PREPARE-FOREIGN-COPY statement specified.
U22418-J-Z125-6-76
237
END-FOREIGN-COPY
Administration
END-FOREIGN-COPY
SELECT = *LOGICAL(...) / *PHYSICAL(...)
*LOGICAL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*PHYSICAL(...)

PHYS-CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Operands
SELECT =
Specifies whether the entry is identified by means of the logical or physical name.
SELECT = *LOGICAL(...)
Selects the database in whose space the “copy pending” state is to be canceled.
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database
SELECT = *PHYSICAL(...)
Selects the database in whose space the “copy pending” state is to be canceled.
PHYS-CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Physical name of the database
Administration command in ISP format and at the CALL DML interface
The FCOPY,END administration command corresponds to the END-FOREIGN-COPY
administration statement here.
FCOPY,E[ND],supplement
supplement ::= {C[ATALOG]=catalog-name|
P[HYSICAL-NAME]=physical-name}
You specify the logical name of the database in catalog-name using a maximum of
18 characters.
You specify the physical name of the database in physical-name using a maximum of
18 characters.
238
U22418-J-Z125-6-76
Administration
END-LOCK-SEQUENCE
END-LOCK-SEQUENCE
This statement terminates a lock sequence.
Scope of validity
DBH administration
See also
–
The DBH administration statement ABORT-LOCK-SEQUENCE on page 211
–
The DBH administration statement BEGIN-LOCK-SEQUENCE on page 224
Function
The END-LOCK-SEQUENCE statement terminates a lock sequence of the current user.
All of the requested locks on databases and spaces during the lock sequence are canceled
by this statement.
Note the following points:
–
The administration statement is rejected if the SESAM DBH was loaded without transaction management.
–
The user must be in a lock sequence. If this is not the case, the statement is rejected
and an error message is issued to this effect.
END-LOCK-SEQUENCE
Operands
This statement does not have any operands.
Administration command in ISP format and at the CALL DML interface
The LSQ,END administration command corresponds to the END-LOCK-SEQUENCE
administration statement here.
LSQ,E[ND]
U22418-J-Z125-6-76
239
HOLD-TRANSACTION-ADMISSION
Administration
HOLD-TRANSACTION-ADMISSION
This statement suspends admission of any further transactions.
Scope of validity
DBH and SESDCN administration
See also
The RESUME-TRANSACTION-ADMISSION administration statement on page 276
Function
You can use the HOLD-TRANSACTION-ADMISSION administration statement to suspend
processing of transactions and thus prevent new transactions being admitted.
Application programs affected by this suspension of transaction processing learn of it when
a transaction is started: an SQL program by means of the appropriate SQLSTATE, and a
CALL DML program by means of the status 9K.
If requests with open transactions still exist when the administration statement is issued,
SESAM/SQL displays them in tabular form.
In DBH administration, but not SESDCN administration, you can cause transaction
processing to be suspended only once the DBH is transaction free.
This is the case when all transactions have been committed or rolled back. SESAM/SQL
outputs a message indicating this to the administration program, which then continues its
work.
You can permit the resumption of transaction processing by means of the RESUMETRANSACTION-ADMISSION administration statement.
The HOLD-TRANSACTION-ADMISSION administration statement is rejected if the DBH
was loaded without transaction management (see the DBH option TRANSACTIONSECURITY on page 134).
HOLD-TRANSACTION-ADMISSION
WAIT-EVENT = *NONE / *TRANSACTION-FREE-STATE
240
U22418-J-Z125-6-76
Administration
HOLD-TRANSACTION-ADMISSION
Operands
WAIT-EVENT =
Specifies whether or not the transaction-free state must be reached before transaction
processing can be suspended.
WAIT-EVENT = *NONE
This is the default. Transaction processing is suspended regardless of whether the DBH is
transaction free.
WAIT-EVENT = *TRANSACTION-FREE-STATE
Transaction processing is not suspended until the DBH is transaction free.
This operand is only permitted in DBH administration; it is not permitted in SESDCN administration.
Administration command in ISP format and at the CALL DML interface
Two administration commands fulfill the function of the HOLD-TRANSACTIONADMISSION administration statement:
–
HOLD-TA (for DBH administration)
or HOLD,TA (for SESDCN administration)
–
WAIT,HOLD.
The HOLD-TA administration command is permitted for DBH administration and HOLD,TA
for SESDCN administration. HOLD,TA has the same function as the
HOLD-TRANSACTION-ADMISSION administration statement with the operand
WAIT-EVENT = *NONE.
HOLD-TA
HOLD,TA
The WAIT,HOLD administration command is permitted only in DBH administration and can
only be issued via the CALL DML interface. It has the same function as the
HOLD-TRANSACTION-ADMISSION administration statement with the operand
WAIT-EVENT = *TRANSACTION-FREE-STATE.
WAIT,HOLD
U22418-J-Z125-6-76
241
HOLD-USER-ADMISSION
Administration
HOLD-USER-ADMISSION
This statement suspends admission of any further users.
Scope of validity
SESDCN administration
See also
The RESUME-USER-ADMISSION administration statement on page 277
Function
You use the HOLD-USER-ADMISSION statement to suspend the admission of any further
users.
No further users from the administered configuration are admitted, but users active up to
this point can continue their work.
HOLD-USER-ADMISSION
Operands
This statement has no operands.
Administration command in ISP format and at the CALL DML interface
The HOLD,USER administration command corresponds to the HOLD-USER-ADMISSION
administration statement.
HOLD,USER
242
U22418-J-Z125-6-76
Administration
MODIFY-ADMINISTRATION
MODIFY-ADMINISTRATION
This statement changes administration authorization.
Scope of validity
DBH and SESDCN administration
See also
–
The DBH option ADMINISTRATOR on page 82
–
The SESDCN control statement SET-DCN-OPTIONS on page 158
Function
The MODIFY-ADMINISTRATION administration statement allows you to change the administration authorization to suit requirements. Administration authorization is set by means of
the DBH option ADMINISTRATOR or the SESDCN control statement SET-DCN-OPTIONS.
You can change both the password, which prevents unauthorized administration of the DBH
or SESDCN, and the identification (system user identification) of the administrator.
Note that the system user identification entered here is also required for certain utlity statements, e.g. CREATE CATALOG, in authorization checking.
The MODIFY-ADMINISTRATION administration statement is not permitted unless you have
made the appropriate settings for the DBH option ADMINISTRATOR when starting the
SESAM/SQL DBH. In the case of SESDCN, this is done using SET-DCN-OPTIONS.
i
U22418-J-Z125-6-76
You can even use this statement to withdraw your own administration authorization.
243
MODIFY-ADMINISTRATION
Administration
MODIFY-ADMINISTRATION
NEW-PASSWORD = *UNCHANGED /<c-string 3..3> / <x-string 5..6>
,ADMINISTRATOR = *UNCHANGED / *TIME-SHARING-USER(...) / *APPLICATION-USER(...) / *ANY
*TIME-SHARING-USER(...)


HOST-NAME = <name 1..8>
,USER-ID = <name 1..8>
*APPLICATION-USER(...)



HOST-NAME = <text 1..8>
,APPLICATION-NAME = <text 1..8>
,CUSTOMER-NAME = <text 1..8>
Operands
NEW-PASSWORD = *UNCHANGED / <c-string 3..3> / <x-string 5..6>
New password that is to replace the existing one.
The default is *UNCHANGED, which means that the existing password is not changed.
ADMINISTRATOR =
Identifies the user or user group authorized to issue administration statements using the
CALL interface and SESADM.
ADMINISTRATOR = *UNCHANGED
This is the default. The administration authorization remains the same, i.e. as set by means
of the DBH option ADMINISTRATOR.
ADMINISTRATOR = *TIME-SHARING-USER(...)
Changes the administration authorization.
A timesharing user, identified by his or her system user identification, is the administrator.
HOST-NAME = <name 1..8>
Name of the computer from which administration is to be carried out
USER-ID = <name 1..8>
User ID of the administrator
ADMINISTRATOR = *APPLICATION-USER(...)
Changes the administration authorization.
An application user identified by the system user ID is the administrator.
HOST-NAME = <text 1..8>
Name of the host from which administration is to be carried out
244
U22418-J-Z125-6-76
Administration
MODIFY-ADMINISTRATION
APPLICATION-NAME = <text 1..8>
Name of the application from which administration is to be carried out
CUSTOMER-NAME = <text 1..8>
Name of the requesting user.
If the administrator is working under UTM, you must enter the KDCSIGN name here. If
the administrator is working under DCAM, you must enter the name by which the
system administrator is identified at the programming interface.
ADMINISTRATOR = *ANY
Permits all users to issue administration statements using the CALL interface and
SESADM, provided they know the password.
Administration command in ISP format and at the CALL DML interface
The OPT,ADM administration command corresponds to the MODIFY-ADMINISTRATION
administration statement.
OPT,ADM=xxx[,admin-name]
admin-name ::= {T[IME]-S[HARING]-U[SER]=host,userid|
A[PPLICATION]-U[SER]=host,appl,kdcsign|
ANY}
If you want to change an existing password, enter the new password for xxx.
If you want to change only the identification of the administrator, admin-name, enter the
existing password for xxx.
admin-name must be unique, so you must enter all the relevant partial qualifications.
U22418-J-Z125-6-76
245
MODIFY-CATALOG-ACCESS-RIGHTS
Administration
MODIFY-CATALOG-ACCESS-RIGHTS
This statement changes the access rights for a named database.
Scope of validity
DBH administration
See also
The ADD-SQL-DB-CATALOG-ENTRY administration statement on page 218
Function
The MODIFY-CATALOG-ACCESS-RIGHTS administration statement allows you to change
the access rights for a named database.
This may be necessary when the WRITE access function for a database has been set internally to READ as a result of error recovery. If a consistency check has taken place in the
CAT-LOG or DA-LOG file, SESAM/SQL turns off logging for these files in order to obtain
partial availability of the DBH. In error recovery, SEAM/SQL sets the access function for the
affected database to READ. Once the cause of the error has been eliminated, you can use
the MODIFY-CATALOG-ACCESS-RIGHTS statement to permit the WRITE access function
for the affected database again.
A transactionless state is not required for the MODIFY-CATALOG-ACCESS-RIGHTS
statement.
The change of access rights is transaction-synchronized; in other words, the access rights
are changed under the protection of an exclusive transaction lock on the database entry,
and the change is synchronized.
Changes to the access functions do not take effect until a statement is issued again. Statements active in the DBH are not notified of the change.
246
U22418-J-Z125-6-76
Administration
MODIFY-CATALOG-ACCESS-RIGHTS
MODIFY-CATALOG-ACCESS-RIGHTS
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
,ACCESS = *ALL / *PARAMETERS(...)
*PARAMETERS(...)



READ = *YES / *NO
,WRITE = *YES / *NO
,CAT-ADMINISTRATION = *YES / *NO
Operands
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Logical database name of the database for which the access rights are to be modified. The
database name must not refer to the SESAM backup copy or a replication of a database.
ACCESS =
Specifies which access functions are to be permitted or suppressed for the database.
ACCESS = *ALL
Allows unrestricted access to the database. Permits read and write access to user data and
metadata.
ACCESS = *PARAMETERS(...)
Restricts access to the database.
The parameters are arranged in a hierarchical structure. If CAT-ADMINISTRATION is
permitted, so, implicitly, are WRITE and READ. In the same way, WRITE implicitly permits
READ.
At least one parameter must be specified with YES.
READ = *YES
Permits read access to user data and metadata. The data can be queried but not
changed.
READ = *NO
Prevents read access to user data and metadata.
It makes no sense to select READ = NO if you assign the default (YES) to either CATADMINISTRATION or WRITE, since CAT-ADMINISTRATION implicitly permits WRITE
and WRITE implicitly permits READ.
WRITE = *YES
Permits read and write access to user data. Metadata can be read but not changed.
U22418-J-Z125-6-76
247
MODIFY-CATALOG-ACCESS-RIGHTS
Administration
WRITE = *NO
Prevents write access to user data and metadata.
It makes no sense to select WRITE = NO if you assign the default (YES) to
CAT-ADMINISTRATION, since CAT-ADMINISTRATION implicitly permits WRITE.
CAT-ADMINISTRATION = *YES
Permits read and write access to both user data and metadata.
CAT-ADMINISTRATION = *NO
Prevents write access to the metadata in the catalog space of the database. Thus, it
does not permit the use of the following statements:
– SQL statements for schema definition and management and memory management
– utility statements
Administration command in ISP format and at the CALL DML interface
The OPT,ACCESS administration command corresponds to the MODIFY-CATALOGACCESS-RIGHTS administration statement.
OPT,ACCESS=(access),C[ATALOG]=catalog-name
access ::= R[EAD],W[RITE],A[DMIN]
The administration command is not effective unless you explicitly specify at least one
access function for access.
catalog-name must not contain any commas as characters because commas function as
separators, nor must it refer to a SESAM backup copy or a replication of a database.
READ permits only read access, WRITE implicitly permits READ, and ADMIN implicitly
permits WRITE and thus also READ.
A transactionless state is not required for the OPT,ACCESS=(ADMIN) command. The
change of access rights is synchronized instead.
You cannot subsequently modify the ACCESS=COPY access function. When appropriate,
it is changed internally by the COPY utility statement.
248
U22418-J-Z125-6-76
Administration
MODIFY-CATID-LIST
MODIFY-CATID-LIST
This statement updates the CATID list.
Scope of validity
DBH administration
Function
It is possible to specify a CATID list. This list limits the internal search for files to the CATIDs
specified in this list. It can have a positive effect on the performance of the system, since it
is no longer necessary to include all CATIDs in the search. However, performance is, of
course, also dependent on the length of the specified list. When specifying a CATID list,
note that a maximum of 50 CATIDs are evaluated.
The DBH takes the CATID list from a file. You can use the MODIFY-CATID-LIST statement
to cause the DBH to take a new CATID list or to stop evaluating an existing CATID list. The
modification takes effect the next time a file is opened in the DBH.
If the DBH has already been assigned a file with a CATID list in the start procedure by
means of the ADD-FILE-LINK command, this list takes effect at the startup of the DBH.
The CATID of the default PVS must be contained in the CATID list. If this CATID is not in the
list, the DBH adds it to the list. In addition, a warning is issued.
The file that contains the CATID list must be a SAM file and can, for example, be created
with the file editor EDT (see the manual “EDT (BS2000/OSD) Statements”). The defined
record length must be variable. There is a CATID without colons or blanks in each row. The
CATID can be between 1 and 4 characters in length. After the descriptions of the operands
below you will find an example of a CATID list created with EDT.
MODIFY-CATID-LIST
FILE-NAME = *STD / *NONE / <filename 1..54>
U22418-J-Z125-6-76
249
MODIFY-CATID-LIST
Administration
Operands
FILE-NAME =
Name of the file that contains the CATID list
FILE-NAME = *STD
By default, the CATID file assigned to the DBH at startup with the link name SESAMCID is
used.
FILE-NAME = *NONE
No CATID list is transferred. Any existing CATID list in the DBH is deleted. The DBH
searches for all CATIDs. This is what happens in the versions up to and including
version 3.0.
FILE-NAME = <filename 1..54>
Name of the file that contains the new CATID list. If a CATID list is already active, the file
specified here must be in the same PVS as the file of the active list.
The administration statement is rejected if the CATIDs of the currently open database files
are not contained in the new CATID list specified.
Example
CATID list created using the EDT file editor:
2OGB
2OGE
B321
3OAM
3OLR
C245
L324
LO21
2KL3
PL34
PO54
P567
P123
P425
OL43
%
SHO0301 WARNING: END OF FILE REACHED
S*SOF+
LTG
250
1(
1)
TAST
U22418-J-Z125-6-76
Administration
MODIFY-CATID-LIST
Administration command in ISP format and at the CALL DML interface
The UPD,CID-LIST administration command corresponds to the MODIFY-CATID-LIST
administration statement here.
UPD,C[ID-LIST],file
file ::= {NONE|
STD|
FILE=filename}
filename must comply with BS2000 conventions. In SEND-MSG administration you must
adhere to the permissible length for filename (see the section “Administration using
INFORM-PROGRAM” on page 174).
U22418-J-Z125-6-76
251
MODIFY-DISTRIBUTION-RULE-ENTRY
Administration
MODIFY-DISTRIBUTION-RULE-ENTRY
This statement changes the host name in the distribution rule.
Scope of validity
SESDCN administration
Function
You use the MODIFY-DISTRIBUTION-RULE-ENTRY statement to change the host name
in the distribution rule.
This can be necessary, for example, in the following case:
If the SESDCN restart is carried out on a computer other than the cold-start computer, the
master DCN updates the distribution rules for all remote computers that have worked with
it between the cold start and the abortion of the session and are accessible to it at the time
of the restart. If not all these partners are accessible to the master DCN at the time of the
restart, the system administrator must update some distribution rules manually and use the
MODIFY-DISTRIBUTION-RULE-ENTRY statement to replace the host name.
MODIFY-DISTRIBUTION-RULE-ENTRY
HOST-NAME = <name 1..8>
,NEW-NAME = <name 1..8>
,CONFIGURATION-NAME = *ANY / <alphanum-name 1..1> / *BLANK
Operands
HOST-NAME = <name 1..8>
Symbolic device name of the computer replaced by the new computer.
NEW-NAME = <name 1..8>
Symbolic device name of the new computer replacing the previous one.
CONFIGURATION-NAME = *ANY / <alphanum-name 1..1> / *BLANK
Configuration name that defines which distribution-rule entries are affected by the change
of host name.
CONFIGURATION-NAME = *ANY
Changes the host name in all distribution-rule entries that contain the old host name.
252
U22418-J-Z125-6-76
Administration
MODIFY-DISTRIBUTION-RULE-ENTRY
CONFIGURATION-NAME = <alphanum-name 1..1> / *BLANK
Changes the host name only in distribution-rule entries that contain the old host name and
the specified configuration name.
Administration command in ISP format and at the CALL DML interface
The UPDPRO administration command corresponds to the MODIFY-DISTRIBUTIONRULE-ENTRY administration statement.
[tsn,]UPDPRO,PRO-OLD=r-name1,PRO-NEW=r-name2[,CNF=k]
CNF can contain a blank as a parameter value. You must enter an underscore (_) as a
metacharacter for a blank.
U22418-J-Z125-6-76
253
MODIFY-REQUEST-CONTROL
Administration
MODIFY-REQUEST-CONTROL
This statement changes parameters for priority control.
Scope of validity
DBH administration
See also
–
The DBH option REQUEST-CONTROL on page 103
–
The SET-REQUEST-CONTROL administration statement on page 291
Function
The MODIFY-REQUEST-CONTROL administration statement allows you to change as
required the parameters set by means of the DBH option REQUEST-CONTROL for the
priority control of the DBH.
This administration statement is not permitted unless the DBH has been loaded with priority
control.
MODIFY-REQUEST-CONTROL
REQUEST-CONTROL = *STD / *QUEUE-RANGE(...) / *QUEUE-PRIORITY(...)
*QUEUE-RANGE(...)


LOW-LEVEL = 180 / <integer 30..255>
,HIGH-LEVEL = 240 / <integer 30..255>
*QUEUE-PRIORITY(...)



254
QUEUE-1 = 3 / <integer 1..99>
,QUEUE-2 = 2 / <integer 1..99>
,QUEUE-3 = 1 / <integer 1..99>
U22418-J-Z125-6-76
Administration
MODIFY-REQUEST-CONTROL
Operands
REQUEST-CONTROL = *STD
Defaults apply to all priority-control parameters.
REQUEST-CONTROL = *QUEUE-RANGE(...)
Specifies the limit values between the priority classes Queue-1 and Queue-2, and Queue-2
and Queue-3.
LOW-LEVEL = 180 / <integer 30..255>
Specifies the limit value between the first and second priority classes, Queue-1 and
Queue-2. The default for LOW-LEVEL is 180.
This value must be less than the value for HIGH-LEVEL.
HIGH-LEVEL = 240 / <integer 30..255>
Specifies the limit value between the second and third priority classes, Queue-2 and
Queue-3. The default for HIGH-LEVEL is 240.
This value must be greater than the value for LOW-LEVEL.
REQUEST-CONTROL = *QUEUE-PRIORITY(...)
Specifies the weights of the different priority classes.
QUEUE-1 = 3 / <integer 1..99>
Specifies the weight of the first priority class, Queue-1. The default is 3.
QUEUE-2 = 2 / <integer 1..99>
Specifies the weight of the second priority class, Queue-2. The default is 2.
QUEUE-3 = 1 / <integer 1..99>
Specifies the weight of the third priority class, Queue-3. The default is 1.
Administration command in ISP format and at the CALL DML interface
Two OPT,REQ-CON administration commands, each with different operands, fulfill the
function of the MODIFY-REQUEST-CONTROL administration statement.
OPT,REQ-CON,H[IGH-LEVEL]=n[,L[OW-LEVEL]=m]
OPT,REQ-CON,Q[UEUE]-1=x[,Q[UEUE]-2=y][,Q[UEUE]-3=z]
U22418-J-Z125-6-76
255
MODIFY-RESTART-CONTROL
Administration
MODIFY-RESTART-CONTROL
This statement influences the duration of a restart.
Scope of validity
DBH administration
See also
The DBH option RESTART-CONTROL on page 106
Function
The MODIFY-RESTART-CONTROL administration statement allows you to modify the
BUFFER-LIMIT and TALOG-LIMIT parameters specified using the DBH option
RESTART-CONTROL.
You can use these parameters to reduce the duration of any restart by influencing the
writing of afterimages to the database. It is possible to select different values for the buffers
of the system access data and user data. Parameters not specified in the MODIFYRESTART-CONTROL statement remain unchanged.
Low parameter values cause the afterimages to be written to the database frequently. This
reduces the duration of physical repair in the event of a restart. However, if performance
losses are incurred as a result of parameter values being selected that are too low and of
an increased number of physical read and write accesses, you can use MODIFY-RESTARTCONTROL to adjust the parameter values during operation.
MODIFY-RESTART-CONTROL
RESTART-CONTROL = *BUFFER-LIMIT(...) / *TALOG-LIMIT(...)
*BUFFER-LIMIT(...)


SYSTEM-DATA-BUFFER = 50 / <integer 10..90>
,USER-DATA-BUFFER = 50 / <integer 10..90>
*TALOG-LIMIT(...)

256
LIMIT = 128 / <integer 128..524288>
U22418-J-Z125-6-76
Administration
MODIFY-RESTART-CONTROL
Operands
RESTART-CONTROL =
Specifies which value is to be changed.
RESTART-CONTROL = *BUFFER-LIMIT(...)
Controls the physical writing of the afterimages to the database.
SYSTEM-DATA-BUFFER = 50 / <integer 10..90>
Specifies a percentage limit for the writing of afterimages to the database for system
access data.
USER-DATA-BUFFER = 50 / <integer 10..90>
Specifies a percentage limit for the writing of afterimages to the database for user data.
RESTART-CONTROL = *TALOG-LIMIT(...)
Specifies the limit for how much of the TA-LOG file can be occupied by afterimages. As of
this limit, afterimage blocks are written to the database.
LIMIT = 512 / <integer 128..524288>
Specifies the new limit value in units of 4 Kbytes.
Administration command in ISP format and at the CALL DML interface
Three administration commands with the format OPT,RESTART, each with specific
operands, correspond to the MODIFY-RESTART-CONTROL administration statement here.
OPT,RESTART,B[UFFER-LIMIT],U[SER-DATA-BUFFER]=n[,S[YSTEM-DATA-BUFFER]=m]
OPT,RESTART,B[UFFER-LIMIT],S[YSTEM-DATA-BUFFER]=n[,U[SER-DATA-BUFFER]=m]
OPT,RESTART,T[ALOG-LIMIT]=l
Percentage values expressed as integers between 10 and 90 can be specified for n and m.
An integer between 128 and 524288 can be specified for l.
U22418-J-Z125-6-76
257
MODIFY-RETRIEVAL-CONTROL
Administration
MODIFY-RETRIEVAL-CONTROL
This statement changes the limit value for the interruption of retrieval statements.
Scope of validity
DBH administration
See also
The DBH option RETRIEVAL-CONTROL on page 109
Function
The MODIFY-RETRIEVAL-CONTROL administration statement allows you to change the
parameters INDEX-EVALUATION, USER-DATA-ACCESS and ABORT-EXECUTION of the
DBH option RETRIEVAL-CONTROL to suit requirements.
MODIFY-RETRIEVAL-CONTROL
SELECT = *INDEX-EVALUATION(...) / *USER-DATA-ACCESS(...) / *ABORT-EXECUTION(...)
*INDEX-EVALUATION(...)

LIMIT = <integer 16..2147483647>
*USER-DATA-ACCESS(...)

LIMIT = <integer 1..2147483647>
*ABORT-EXECUTION(...)

LIMIT = <integer 1..2147483647>
Operands
SELECT = *INDEX-EVALUATION(...)
Specifies a limit value as of which the processing of retrieval statements is interrupted via
secondary indexes and continued sequentially. The limit value refers to an expected set of
records found, which the DBH calculates for the first subquestion to be processed.
LIMIT = <integer 16..2147483647>
Specifies the new limit value.
258
U22418-J-Z125-6-76
Administration
MODIFY-RETRIEVAL-CONTROL
SELECT = *USER-DATA-ACCESS(...)
Specifies the number of logical USER-DATA inputs/outputs for CALL DML and SQL before
there is an interruption.
LIMIT = <integer 1..2147483647>
Specifies the new limit value.
SELECT = *ABORT-EXECUTION(...)
Specifies the number of failed logical USER-DATA inputs/outputs for CALL-DML and SQL
as of which the search is aborted.
A request related value defined using the pragma LIMIT ABORT_EXECUTION
<integer 1.. 2147483647> cannot be changed with this statement, see the “SQL Reference
Manual Part 1: SQL Statements”, section “Pragmas”.
LIMIT = <integer 1..2147483647>
Specifies the new limit value.
Administration command in ISP format and at the CALL DML interface
The OPT,RET-CON administration command corresponds to the MODIFY-RETRIEVALCONTROL administration statement.
OPT,RET-CON,INDEX-EVAL=n
OPT,RET-CON,USER-DATA-ACC=y
OPT,RET-CON,ABORT=z
A number between 16 and 231-1 can be specified for n.
A number between 1 and 231-1 can be specified for y.
A number between 1 and 231-1 can be specified for z.
U22418-J-Z125-6-76
259
MODIFY-SQL-SORT-LIMIT
Administration
MODIFY-SQL-SORT-LIMIT
This statement changes the maximum number of records in the sorting of a cursor table.
Scope of validity
DBH administration
See also
The DBH option SQL-SUPPORT on page 123
Function
The MODIFY-SQL-SORT-LIMIT administration statement allows you to change the
INTERNAL-SORT-LIMIT parameter of the DBH option SQL-SUPPORT to suit requirements.
This statement is only permitted when the DBH supports the SQL interface.
MODIFY-SQL-SORT-LIMIT
INTERNAL-SORT-LIMIT = <integer 1..2147483647>
Operands
INTERNAL-SORT-LIMIT = <integer 1..2147483647>
Specifies the maximum number of records a cursor table can contain if the records are to
be sorted in accordance with the cursor declaration.
If the number of records found during the sort exceeds this limit value, processing of the
statement is aborted.
Administration command in ISP format and at the CALL DML interface
The OPT,SORTLIMIT administration command corresponds to the MODIFY-SQL-SORTLIMIT administration statement.
OPT,SORTLIMIT=n
260
U22418-J-Z125-6-76
Administration
MODIFY-SUBORDER-LIMIT
MODIFY-SUBORDER-LIMIT
This statement limits the maximum number of concurrent suborders.
Scope of validity
DBH administration
See also
The DBH option SUBORDERS on page 126
Function
The MODIFY-SUBORDER-LIMIT administration statement allows you to change the
MAXIMUM parameter of the DBH option SUBORDERS to suit requirements.
You use this statement to change the maximum permitted number of suborders (SQL scans
or logical files) in the DBH session.
MODIFY-SUBORDER-LIMIT
LIMIT = <integer 6..262143>
Operands
LIMIT = <integer 6..262143>
Specifies the maximum permissible number of concurrent orders.
If you select a value that is less than the sum of all currently existing suborders,
SESAM/SQL specifies an internal value for LIMIT corresponding to the total of all current
suborders of all users.
The number of parallel suborders cannot fall any lower than the number reached during the
currently running DBH session.
Administration command in ISP format and at the CALL DML interface
The OPT,SUBORDERS administration command corresponds to the MODIFYSUBORDER-LIMIT administration statement.
OPT,SUBORDERS=n
U22418-J-Z125-6-76
261
MODIFY-TRANSACTION-SECURITY
Administration
MODIFY-TRANSACTION-SECURITY
This statement changes the transaction management parameters.
Scope of validity
DBH administration
See also
The DBH option TRANSACTION-SECURITY on page 134
Function
The MODIFY-TRANSACTION-SECURITY statement allows you to change the LOCK-TIME
parameter, the INACTIVITY-TIME parameter or the LOCK-ESCALATION parameter of the
DBH option TRANSACTION-SECURITY during operation.
Only the parameter that is specified in the MODIFY-TRANSACTION-SECURITY statement
is changed. All the other values remain unchanged. The values changed for the LOCKESCALATION parameter do not take effect until a transaction accesses a table or index
after the modification. The changes have no effect on transactions that already have access
to a table or index when the option is changed.
The MODIFY-TRANSACTION-SECURITY administration statement is rejected if the DBH
was loaded without transaction management.
MODIFY-TRANSACTION-SECURITY
SELECT = *LOCK-TIME(...) / *INACTIVITY-TIME(...) / *LOCK-ESCALATION(...)
*LOCK-TIME(...)

TIME = 4 / <integer 1..999>
*INACTIVITY-TIME(...)

TIME = 40 / <integer 1..999>
*LOCK-ESCALATION(...)



262
NUMBER-RECORDS = 4000 / <integer 1..2147483647>
,PERCENTAGE-RECORDS = 50 / <integer 0..100>
,NUMBER-INDEX-VALUES = 1000 / <integer 1..2147483647>
U22418-J-Z125-6-76
Administration
MODIFY-TRANSACTION-SECURITY
Operands
SELECT = *LOCK-TIME(...)
Changes the time after which an inactive transaction that is locking other transactions is to
be rolled back.
TIME = 4 / <integer 1..999>
New value in minutes. The value specified for LOCK-TIME must not be greater than the
current value of INACTIVITY-TIME. If it is, the statement is rejected.
SELECT = *INACTIVITY-TIME(...)
Specifies the number of minutes after which an open but inactive transaction is to be rolled
back.
TIME = 40 / <integer 1..999>
New value in minutes. The value specified for INACTIVITY-TIME must not be lower than
the current value of LOCK-TIME. If it is, the statement is rejected.
SELECT = *LOCK-ESCALATION(...)
Changes the limit values as of which locks escalate. Escalation is when SESAM/SQL
attempts to lock the entire index or table.
NUMBER-RECORDS = 4000 / <integer 1..2147483647>
Specifies the number of records in a table that a user can lock. If more records than this
are locked, the whole table is locked.
PERCENTAGE-RECORDS = 50 / <integer 0..100>
Specifies the percentage of all the records in the table that a user can lock. If a greater
percentage is locked, SESAM/SQL attempts to lock the whole table. If 0 is specified as
the percentage, the entire table is locked immediately.
NUMBER-INDEX-VALUES = 1000 / <integer 1..2147483647>
Specifies the number of values that a user can lock in an index. If a larger number than
this are locked, an attempt is made to lock the entire index rather than just individual
values.
Administration command in ISP format and at the CALL DML interface
Five administration commands with the format OPT,TA-SEC, each with specific operands,
correspond to the MODIFY-TRANSACTION-SECURITY administration statement here.
OPT,TA-SEC,L[OCK-TIME]=n
OPT,TA-SEC,I[NACT-TIME]=m
U22418-J-Z125-6-76
263
MODIFY-TRANSACTION-SECURITY
Administration
OPT,TA-SEC,E[SCALATE-LOCK],N[UMBER]-R[ECORDS]=l
{[,P[ERCENTAGE]-R[ECORDS]=k][,N[UMBER]-I[NDEX-VALUES]=j]|
[,N[UMBER]-I[NDEX-VALUES]=j][,P[ERCENTAGE]-R[ECORDS]=k]}
OPT,TA-SEC,E[SCALATE-LOCK],P[ERCENTAGE]-R[ECORDS]=k
{[,N[UMBER]-R[ECORDS]=l][,N[UMBER]-I[NDEX-VALUES]=j]|
[,N[UMBER]-I[NDEX-VALUES]=j][,N[UMBER]-R[ECORDS]=l]}
OPT,TA-SEC,E[SCALATE-LOCK],N[UMBER]-I[NDEX-VALUES]=j
{[,P[ERCENTAGE]-R[ECORDS]=k][,N[UMBER]-R[ECORDS]=l]|
[,N[UMBER]-R[ECORDS]=l][,P[ERCENTAGE]-R[ECORDS]=k]}
A number from 1 to 999 can be specified for n and m.
A number from 1 to 231-1 can be specified for l and j.
A percentage value from 0 to 100 can be specified for k.
264
U22418-J-Z125-6-76
Administration
PREPARE-FOREIGN-COPY
PREPARE-FOREIGN-COPY
This statement closes spaces of a catalog logically in order to prepare for the creation of a
foreign copy.
Scope of validity
DBH administration
See also
–
The DBH administration statement END-FOREIGN-COPY on page 237
–
The DBH administration statement BEGIN-LOCK-SEQUENCE on page 224
–
The DBH administration statement END-LOCK-SEQUENCE on page 239
Function
At the time when a foreign copy is created, the spaces concerned must be properly closed.
You can use the PREPARE-FOREIGN-COPY statement to close the spaces logically. In
logical closure, the update is interrupted on the space by a transaction lock. The contents
of the buffers of the selected database are written to the corresponding files. These files
remain physically open.
As long as the database is not updated, a foreign copy can be created. Updates must be
prevented by organizational means or by issuing the PREPARE-FOREIGN-COPY
statement in a lock sequence, which is better. Read access to the database is also possible
during the lock sequence. Lock sequences are opened with BEGIN-LOCK-SEQUENCE
and terminated with END-LOCK-SEQUENCE.
The logging for a space, a space set or the entire catalog can be turned on with the
statement PREPARE-FOREIGN-COPY. The logging information can be used for repair with
foreign copies generated after the statement PREPARE-FOREIGN-COPY
The statement PREPARE-FOREIGN-COPY can be used independently of the statement
END-FOREIGN-COPY.
If the statement END-FOREIGN-COPY follows in the same administration session, this only
acts on the spaces entered in the preceding statement PREPARE-FOREIGN-COPY.
U22418-J-Z125-6-76
265
PREPARE-FOREIGN-COPY
Administration
If the logging is only to be turned on for a few spaces and other spaces are to be backed up
as a space set, a PREPARE-FOREIGN-COPY statement must first be given for turning on
the logging. This is then followed by another PREPARE-FOREIGN-COPY statement with
all the spaces to be backed up. The final END-FOREIGN-COPY statement then acts on all
the spaces backed up.
PREPARE-FOREIGN-COPY
SELECT = *LOGICAL(...) / *PHYSICAL(...)
*LOGICAL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*PHYSICAL(...)

PHYS-CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
,SPACE-NAMES = *ALL / *CATALOG /
list-poss(200): <filename 1..18 without-cat-id-user-id-generation-version>
,LOGGING = *UNCHANGED / *ON
Operands
SELECT =
Specifies the name by means of which the database is identified.
SELECT = *LOGICAL(...)
Selects the database to be logically closed.
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical database name
SELECT = *PHYSICAL(...)
Selects the database to be logically closed.
PHYS-CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Physical database name
SPACE-NAMES =
Specifies the spaces to be closed.
The backups of the spaces closed with this statement can be entered in a space list in the
utility statement RECOVER (using foreign copy); see the utility statement RECOVER in
“SQL Reference Manual Part 2: Utilities”.
266
U22418-J-Z125-6-76
Administration
PREPARE-FOREIGN-COPY
SPACE-NAMES = *ALL
All user spaces and the catalog space are logically closed.
SPACE-NAMES = *CATALOG
Only the catalog space is logically closed. You can then only generate a consistent foreign
copy of the catalog space.
SPACE-NAMES =
list-poss(200): <filename 1..18 without-cat-id-user-id-generation-version>
The user spaces entered are logically closed. You can then only generate a consistent
foreign copy of these spaces.
LOGGING =
Specifies whether the logging is turned on for the spaces specified in the operand SPACENAMES.
LOGGING = *UNCHANGED
The settings for the logging remain unchanged.
LOGGING = *ON
The logging is turned on for the spaces specified in the operand SPACE-NAMES. Logging
for individual spaces can only be turned on if the catalog is already logging. The backups
on the spaces which are closed with this statement form the basis of the logging.
Administration command in ISP format and at the CALL DML interface
The FCOPY,PREPARE administration command corresponds to the PREPARE-FOREIGNCOPY administration statement here.
FCOPY,P[REPARE],supplement
[,S[PACE]={space-name,...|,C[ATALOG}][,L[OGGING-ON]]
supplement ::= {C[ATALOG]=catalog-name|
P[HYSICAL-NAME]=physical-name}
You specify a space name of the database in catalog-name using a maximum of
18 characters.
You specify the logical name of the database in catalog-name using a maximum of
18 characters.
You specify the physical name of the database in physical-name using a maximum of
18 characters.
U22418-J-Z125-6-76
267
RELEASE-USER-RESOURCES
Administration
RELEASE-USER-RESOURCES
This statement releases all a user's resources.
Scope of validity
DBH administration
Function
The RELEASE-USER-RESOURCES statement releases all a user's resources.
You can use this statement to intervene in the case of the undefined abortion of an application program, for example, by releasing the resources of the associated user and thereby
disconnecting this user.
You can determine all of the users known to the DBH who have no open transactions and
who have not issued any statements for a certain length of time, and then release all the
resources of these users.
In a DBH session with transaction management, the DBH rolls back all a user's currently
active transactions before releasing the user's resources. If the resources of a UTM user
are to be released, the DBH backs up all the information on the rolling back of transactions
that have started in order to ensure a synchronized UTM restart. However, if you enter the
RELEASE-USER-RESOURCES administration statement a second time for the same user,
the backup information too is permanently deleted.
All users are rolled back that have a (partially qualified) user identifier. If a user is currently
inside of a transaction, then this transaction is rolled back if it does not issue any commands
within the time specified in INACTIVE-TIME.
If a utility is currently active for the user, then the call for this user is ignored.
The system administrator cannot release his or her own resources. If SESAM/SQL recognizes the user identification as being that of the system administrator, then the call for this
user is ignored.
RELEASE-USER-RESOURCES
USER = *ALL (...) / <user-identification>
*ALL (...)

268
INACTIVE-TIME = <integer 1 .. 99>
U22418-J-Z125-6-76
Administration
RELEASE-USER-RESOURCES
Operands
USER =
Identifies the user or a group of users when partially qualified whose resources are to be
released.
USER = *ALL (...)
If *ALL is specified, all the resources are released for all of the users known to the DBH who
have no open transactions and who have not issued any statements since the time
specified with INACTIVE-TIME.
INACTIVE-TIME = <integer 1 .. 99>
Time in minutes.
USER = <user-identification>
Identifies one or more users whose resources are to be released. One partial qualification
is enough to cause the resources of all affected users to be released (see the section
“Syntax for the identification of users” on page 205).
Administration command in ISP format and at the CALL DML interface
Here, two administration commands fulfill the function of the RELEASE-USERRESOURCES administration statement, namely the administration commands FREE and
FREE,USER,INACT.
FREE,user-identification
FREE,USER,INACT=n
A 2-digit number between 1 and 99 can be specified for n.
i
Users that have open transactions or active lock sequences are not affected by the
FREE,USER,INACT call.
The call handles CALL DML users as well as SQL users.
user-identification can be specified as a partial qualification (see section “Syntax for
the identification of users” on page 205).
If the call was recognized as having correct syntax, then it is acknowledged as
having been accepted. This means that a negative acknowledge is not sent when
no specific user was referred to or no user was eliminated by a call with the correct
syntax.
U22418-J-Z125-6-76
269
REMOVE-DISTRIBUTION-RULE-ENTRY
Administration
REMOVE-DISTRIBUTION-RULE-ENTRY
This statement removes a database entry from the distribution rule.
Scope of validity
SESDCN administration
Function
You use the REMOVE-DISTRIBUTION-RULE-ENTRY statement to remove either a single
database entry or all database entries of a specific computer from the distribution rule.
Users who are already active when you do this can continue to work with the databases
removed from the distribution rule. New users are rejected.
REMOVE-DISTRIBUTION-RULE-ENTRY
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version> / *PROCESSOR(...)
*PROCESSOR(...)

NAME = <name 1..8>
Operands
CATALOG-NAME =
Specifies which entries are to be removed from the distribution rule.
CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database whose entry is removed from the distribution rule.
CATALOG-NAME = *PROCESSOR(...)
The entries of all databases on the specified computer are removed from the distribution
rule.
NAME = <name 1..8>
Symbolic device name of the computer whose database entries are removed from the
distribution rule.
270
U22418-J-Z125-6-76
Administration
REMOVE-DISTRIBUTION-RULE-ENTRY
Administration command in ISP format and at the CALL DML interface
Two administration commands fulfill the function of the REMOVE-DISTRIBUTION-RULEENTRY administration statement: DEL,CATALOG and DEL,PRO-NAME.
DEL,CATALOG=db-name
DEL,PRO=processor
U22418-J-Z125-6-76
271
REMOVE-OLD-TABLE-CATALOG-ENTRY
Administration
REMOVE-OLD-TABLE-CATALOG-ENTRY
This statement removes an entry from the CALL DML table catalog.
Scope of validity
DBH administration
See also
–
The DBH start statement ADD-OLD-TABLE-CATALOG-LIST on page 73
–
The DBH start statement ADD-SQL-DATABASE-CATALOG-LIST on page 76
–
The DBH option OLD-TABLE-CATALOG on page 102
Function
The REMOVE-OLD-TABLE-CATALOG-ENTRY statement removes an entry from the CALL
DML table catalog.
You can use this administration statement to remove either a single CALL DML table from
the catalog or all entries assigned to a specific database.
A CALL DML table to be removed from the CALL DML table catalog must not be active. If
it is active (i.e. currently being accessed), the DBH rejects the REMOVE-OLD-TABLECATALOG-ENTRY administration statement for this table.
REMOVE-OLD-TABLE-CATALOG-ENTRY
SELECT = *SQL(...) / *CALL-DML(...)
*SQL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*CALL-DML(...)

272
CALL-DML-TABLE-NAME = <text 1..17>
U22418-J-Z125-6-76
Administration
REMOVE-OLD-TABLE-CATALOG-ENTRY
Operands
SELECT =
Specifies which entries are to be removed from the CALL DML table catalog.
SELECT = *SQL(...)
Removes from the CALL DML table catalog all entries in which a specific CATALOG-NAME
is specified.
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical database name as a criterion for removing the associated entries. Only those
CALL DML tables that are not currently active are affected.
SELECT = *CALL-DML(...)
Removes a specific entry from the CALL DML table catalog.
CALL-DML-TABLE-NAME = <text 1..17>
Name of the CALL DML table as a criterion for removing the associated entry. If the
table is active, it is not affected.
Administration command in ISP format and at the CALL DML interface
The OPT,CDBC-DEL administration command corresponds to the REMOVE-OLD-TABLECATALOG-ENTRY administration statement.
OPT,CDBC-DEL,{C[ALL-DML-]T[ABLE]=call-dml-table-name|
C[ATALOG]=catalog-name}
U22418-J-Z125-6-76
273
REMOVE-SQL-DB-CATALOG-ENTRY
Administration
REMOVE-SQL-DB-CATALOG-ENTRY
This statement removes an entry from the SQL database catalog.
Scope of validity
DBH administration
See also
–
The DBH start statement ADD-SQL-DATABASE-CATALOG-LIST on page 76
–
The DBH option SQL-DATABASE-CATALOG on page 122
Function
The REMOVE-SQL-DB-CATALOG-ENTRY statement removes the entry for a database
from the SQL database catalog.
The database must not be active. The REMOVE-SQL-DB-CATALOG-ENTRY administration statement is only executed when the database has a status of FREE, LOCKED,
DEFECT or NOSPACE. The administration statement is only executed if the status of the
database is not ACTIVE.
REMOVE-SQL-DB-CATALOG-ENTRY
SELECT = *LOGICAL(...) / *PHYSICAL(...)
*LOGICAL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*PHYSICAL(...)

274
PHYS-CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
U22418-J-Z125-6-76
Administration
REMOVE-SQL-DB-CATALOG-ENTRY
Operands
SELECT =
Specifies the database name that identifies the entry to be removed.
SELECT = *LOGICAL(...)
Causes the entry with the specified logical database name to be removed.
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database whose entry is to be removed from the SQL database
catalog
SELECT = *PHYSICAL(...)
Causes the entry with the specified physical database name to be removed.
PHYS-CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Physical name of the database whose entry is to be removed from the SQL database
catalog
Administration command in ISP format and at the CALL DML interface
The OPT,DBC-DEL administration command corresponds to the REMOVE-SQL-DBCATALOG-ENTRY administration statement.
OPT,DBC-DEL,supplement
supplement ::= {C[ATALOG]=catalog-name|P[HYSICAL-NAME]=physical-name}
U22418-J-Z125-6-76
275
RESUME-TRANSACTION-ADMISSION
Administration
RESUME-TRANSACTION-ADMISSION
This statement permits resumption of transaction processing.
Scope of validity
DBH and SESDCN administration
See also
The HOLD-TRANSACTION-ADMISSION administration statement on page 240
Function
The RESUME-TRANSACTION-ADMISSION administration statement allows you to permit
the resumption of transaction processing and admit transactions again after transaction
processing has previously been suspended by means of the HOLD-TRANSACTIONADMISSION administration statement.
The DBH does not accept this administration statement unless the HOLD-TRANSACTIONADMISSION statement has been used previously. SESDCN accepts the statement even
without the HOLD-TRANSACTION-ADMISSION statement.
If the SESAM/SQL DBH was loaded without transaction management, this administration
statement is rejected (see the DBH option TRANSACTION-SECURITY on page 134).
RESUME-TRANSACTION-ADMISSION
Operands
This statement has no operands.
Administration command in ISP format and at the CALL DML interface
The GO-TA administration command corresponds to the RESUME-TRANSACTIONADMISSION administration statement in DBH administration, and the GO,TA administration
command corresponds to it in SESDCN administration.
GO[-TA]
GO,TA
276
U22418-J-Z125-6-76
Administration
RESUME-USER-ADMISSION
RESUME-USER-ADMISSION
This statement permits resumption of user admission.
Scope of validity
SESDCN administration
See also
The HOLD-USER-ADMISSION administration statement on page 242
Function
You use the RESUME-USER-ADMISSION statement to permit the resumption of user
admission.
It cancels the effect of the HOLD-USER-ADMISSION statement. Users can again be
admitted during the session.
RESUME-USER-ADMISSION
Operands
This statement has no operands.
Administration command in ISP format and at the CALL DML interface
The GO,USER administration command corresponds to the RESUME-USER-ADMISSION
administration statement.
GO,USER
U22418-J-Z125-6-76
277
REUSE-OLD-TABLE-CATALOG-ENTRY
Administration
REUSE-OLD-TABLE-CATALOG-ENTRY
This statement creates a valid reference to a table entry in the CALL DML database catalog.
Scope of validity
DBH administration
See also
–
The ADD-OLD-TABLE-CATALOG-ENTRY administration statement on page 215
–
The SHOW-OLD-TABLE-CATALOG-ENTRIES administration statement on page 319
Function
With the REUSE-OLD-TABLE-CATALOG-ENTRY statement, an attempt is made to create
a valid reference to a table for an entry in the CALL DML database catalog.
Before this statement is called, the entry addressed must exist in the CALL DML database
catalog with the CALL DML table name; otherwise, the statement will be rejected.
The table type is not checked. The user must ensure that only references to tables of the
type CALL DML only or CALL DML/SQL are made.
If the table does not exist in the database, an assignment is not possible. The entry
continues to have the status “invalid”. If the database is not open at the time of the call, the
entry also continues with the status “invalid”.
If you do not specify any CALL DML table name in the call, the action is performed for all
entries in the CALL DML database catalog which have the status “invalid”. If no entry has
the status “invalid”, the statement is ignored without an error message.
If the call is successful, the entry subsequently takes on the status “valid”. The specified
table can now be accessed with CALL DML.
If the call is not successful, the table is not available and thus has the status “invalid”.
Subsequent CALL DML statements are rejected with a status message.
278
U22418-J-Z125-6-76
Administration
REUSE-OLD-TABLE-CATALOG-ENTRY
If the table is created subsequently with the SQL statement CREATE TABLE, it is initially
not yet available for CALL DML. In this case, you must issue the ADD-OLD-TABLECATALOG-ENTRY or REUSE-OLD-TABLE-CATALOG-ENTRY administration statement
with a corresponding table entry after CREATE TABLE.
REUSE-OLD-TABLE-CATALOG-ENTRY
CALL-DML-TABLE-NAME = *ALL / <text 1..17>
Operands
CALL-DML-TABLE-NAME = *ALL / <text 1..17>
Name of the CALL DML table (maximum 17 positions). If the default value *ALL is specified,
an attempt is made to create a valid reference for all table entries in the CALL DML
database catalog.
Administration command in ISP format and at the CALL DML interface
Here, the REUSE-OLD-TABLE-CATALOG-ENTRY administration statement corresponds
to the administration command OPT,CDBC-REUSE.
OPT,CDBC-REUSE[,C[ALL-DML-]T[ABLE]=call-dml-table-name]
call-dml-table-name must not contain any commas as characters because commas function
as separators.
U22418-J-Z125-6-76
279
ROLLBACK-PTC-TRANSACTION
Administration
ROLLBACK-PTC-TRANSACTION
This statement rolls back a PTC transaction.
Scope of validity
DBH administration
See also
The COMMIT-PTC-TRANSACTION administration statement on page 234
Function
The ROLLBACK-PTC-TRANSACTION statement rolls back a user's PTC transaction. A
PTC transaction is a distributed transaction that has the status “prepared to commit” (see
the “Core Manual”).
The functional description of the COMMIT-PTC-TRANSACTION administration statement
tells you when it may be necessary to manually roll back or commit PTC transactions.
This statement is only relevant to PTC transactions. If there are no active PTC transactions
in the DBH, the statement is rejected. It is also rejected if the DBH was loaded without transaction management.
A message is output when the user does not have any transactions in the PTC status.
i
You should exercise careful consideration before using the ROLLBACK-PTCTRANSACTION administration statement; it can destroy the logical consistency of
the transaction.
ROLLBACK-PTC-TRANSACTION
USER = <user-identification>
280
U22418-J-Z125-6-76
Administration
ROLLBACK-PTC-TRANSACTION
Operands
USER = <user-identification>
Identifies the user whose PTC transaction is to be rolled back. The identification must be
unique so you must specify all the relevant partial qualifications (see section “Syntax for the
identification of users” on page 205).
Administration command in ISP format and at the CALL DML interface
The RPTC administration command corresponds to the ROLLBACK-PTC-TRANSACTION
administration statement.
RPTC,user-identification
U22418-J-Z125-6-76
281
ROLLBACK-TRANSACTION
Administration
ROLLBACK-TRANSACTION
This statement rolls back a user's transaction.
Scope of validity
DBH and SESDCN administration
Function
The ROLLBACK-TRANSACTION statement rolls back the transaction of a specific user.
A user's transaction can only be rolled back if it is open.
Resources requested outside the scope of transaction are not released.
You cannot use this statement to roll back PTC transactions. You require the ROLLBACKPTC-TRANSACTION administration statement to do that.
It is not possible with the ROLLBACK-TRANSACTION statement to roll back transactions
that have the status UTI (see page 327), since these transactions are really only statements. These statements are only displayed with SHOW-TRANSACTIONS because they
can hold locks. To cancel such statements, use CANCEL-STATEMENT (see page 226).
The ROLLBACK-TRANSACTION administration statement is rejected if the DBH was
loaded without transaction management.
The statement is also rejected if the user addressed has opened a lock sequence.
ROLLBACK-TRANSACTION
USER = <user-identification>
282
U22418-J-Z125-6-76
Administration
ROLLBACK-TRANSACTION
Operands
USER = <user-identification>
Identifies the user whose transaction is to be rolled back. The identification must be unique
so you must specify all the relevant partial qualifications (see section “Syntax for the identification of users” on page 205). In SESDCN administration, you must enter names for
APPLICATION-NAME and CUSTOMER-NAME in the *BY-SELECT(...) operand for
<user-identification>. An entry for HOST-NAME is optional. If you select the default
(*NONE) for HOST-NAME, SESAM/SQL uses the name of the computer on which the
SESDCN to be administered is running.
Administration command in ISP format and at the CALL DML interface
The RESET administration command corresponds to the ROLLBACK-TRANSACTION
administration statement.
RESET,user-identification
U22418-J-Z125-6-76
283
SET-ACCOUNTING-PARAMETER
Administration
SET-ACCOUNTING-PARAMETER
This statement controls the logging of request accounting.
Scope of validity
DBH administration
See also
The DBH option ACCOUNTING on page 71
Function
You use the SET-ACCOUNTING-PARAMETER administration statement to control the
logging of request accounting for the BS2000 RAV accounting procedure (see the BS2000
manual “Introductory Guide to the SDF Dialog Interface”).
SET-ACCOUNTING-PARAMETER
ACCOUNTING = *ON(...) / *OFF
*ON(...)

CPU-TIME = *NO / *YES
*OFF
Operands
ACCOUNTING = *ON(...)
Turns on logging of request accounting. If logging is already on, the administration
statement is rejected.
CPU-TIME = *NO / *YES
Turns CPU-time counting on/off.
ACCOUNTING = *OFF
Turns off logging of request accounting.
If logging is already off, the administration statement is rejected.
284
U22418-J-Z125-6-76
Administration
SET-ACCOUNTING-PARAMETER
Administration command in ISP format and at the CALL DML interface
The ACC,TP administration command corresponds to the SET-ACCOUNTINGPARAMETER administration statement.
ACC,TP={ON[,CPU]|OFF}
U22418-J-Z125-6-76
285
SET-DBH-MSG-TRACE
Administration
SET-DBH-MSG-TRACE
This statement controls the logging of DBH messages.
Scope of validity
DBH administration
Function
You use the SET-DBH-MSG-TRACE administration statement for diagnostic purposes. It
controls the logging of messages exchanged between the task of the DBH and the task of
an application program (message trace).
SET-DBH-MSG-TRACE
TRACE = *ON(...) / *OFF(...)
*ON(...)

OUTPUT = SYSLST / list(2): SYSLST / SYSOUT
*OFF(...)

OUTPUT = (SYSLST,SYSOUT) / list(2): SYSLST / SYSOUT
Operands
TRACE = *ON(...) / *OFF(...)
Turns the message trace of the DBH on/off at the start of the next send request.
TRACE = *ON(...)
The message trace is turned on.
OUTPUT =
Specifies the output medium for the message trace of the DBH.
OUTPUT = SYSLST
This is the default. The message trace is logged to SYSLST.
OUTPUT = list (2): SYSLST / SYSOUT
The message trace is logged only to SYSLST, only to SYSOUT, or to SYSLST and
SYSOUT.
286
U22418-J-Z125-6-76
Administration
SET-DBH-MSG-TRACE
TRACE = *OFF(...)
The message trace is turned off.
OUTPUT =
Specifies the output medium for the message trace of the DBH that will be turned off.
OUTPUT = (SYSLST,SYSOUT)
This is the default. The message trace is not logged to SYSLST or SYSOUT.
OUTPUT = list (2): SYSLST / SYSOUT
The message trace is logged only to SYSLST, only to SYSOUT, or to neither of them.
Administration command in ISP format and at the CALL DML interface
The TRACE administration command corresponds to the SET-DBH-MSG-TRACE administration statement.
TRACE={ON|OFF}[,OUTPUT={SYSOUT|SYSLST|(SYSOUT,SYSLST)]}
U22418-J-Z125-6-76
287
SET-DIAGNOSIS-DUMP-PARAMETER
Administration
SET-DIAGNOSIS-DUMP-PARAMETER
This statement controls the creation of a dump.
Scope of validity
DBH administration
Function
You use the SET-DIAGNOSIS-DUMP-PARAMETER administration statement to specify for
which user, and after which DBH replies, a dump file is to be created.
As soon as the execution of a statement has been completed, the DBH returns the result
of processing (see the “Messages” manual). What the DBH returns depends on whether
the statement is an SQL or CALL DML statement:
–
after SQL statements, the DBH returns an SQLSTATE
–
after CALL DML statements, the DBH returns a status.
You can use the SET-DIAGNOSIS-DUMP-PARAMETER administration statement to cause
returned SQLSTATEs or statuses to be checked against an SQLSTATE or status defined in
the administration statement. If the two values are the same, the DBH outputs message
SES6016 and creates a dump file (see also chapter “Error recovery” on page 457ff).
SET-DIAGNOSIS-DUMP-PARAMETER
DUMP = *ON(...) / *OFF(...)
*ON(...)






SELECT = *SQL(...) / *CALL-DML(...)
*SQL(...)

SQLSTATE = <alphanum-name 5..5>
*CALL-DML(...)

STATE = <alphanum-name 2..2>
,USER = *ALL / <user-identification>
*OFF(...)
SELECT = *SQL / *CALL-DML
288
U22418-J-Z125-6-76
Administration
SET-DIAGNOSIS-DUMP-PARAMETER
Operands
DUMP =
Turns checking of the SQLSTATE or CALL DML status on/off.
DUMP = *ON(...)
Turns on the checking of the SQLSTATE or CALL DML status.
SELECT =
Specifies if the check of the SQLSTATE or of the CALL DML status is to be turned on.
SELECT = *SQL(...)
Turns on checking of the SQLSTATE.
SQLSTATE = <alphanum-name 5..5>
Specifies the SQLSTATE upon whose occurrence a user dump file is created.
SELECT = *CALL-DML(...)
Turns on checking of the CALL DML status.
STATE = <alphanum-name 2..2>
Specifies the CALL DML status upon whose occurrence a user dump file is created.
USER =
Specifies for which users or which group of users (for partial qualification) the checking
of SQLSTATE or of the CALL DML status is to be turned on.
USER = *ALL
Turns on checking of the SQLSTATE or CALL DML status for all users.
USER = <user-identification>
Identifies one or more users for whom the checking of the SQLSTATE or of the CALL
DML status is to be turned on. The syntax of the parameter is described in section
“Syntax for the identification of users” on page 205. The identification entered here is
valid until the administration statement is issued again.
DUMP = *OFF(...)
Turns off checking of the SQLSTATE or CALL DML status.
SELECT =
Specifies if the check of the SQLSTATE or of the CALL DML status is to be turned off.
SELECT = *SQL
Turns off checking of the SQLSTATE.
SELECT = *CALL-DML
Turns off checking of the CALL DML status.
U22418-J-Z125-6-76
289
SET-DIAGNOSIS-DUMP-PARAMETER
Administration
Administration command in ISP format and for the CALL DML interface
The SET-DIAGNOSIS-DUMP-PARAMETER administration command corresponds to the
OPT,DIAG administration command.
OPT,DIAG,{diag-spec[,user-identification]|NOSTATUS|NOSQLSTATE}
diag-spec ::= {STATUS=y|SQLSTATE=z}
290
U22418-J-Z125-6-76
Administration
SET-REQUEST-CONTROL
SET-REQUEST-CONTROL
This statement turns priority control on/off.
Scope of validity
DBH administration
See also
–
The DBH option REQUEST-CONTROL on page 103
–
The MODIFY-REQUEST-CONTROL administration statement on page 254
Function
You use the SET-REQUEST-CONTROL administration statement to turn the priority control
of the independent DBH on or off.
This administration statement is only permitted when the DBH was loaded with priority
control.
If you turn priority control on with SET-REQUEST-CONTROL, the values set by means of
the DBH option apply to weights and levels.
SET-REQUEST-CONTROL
REQUEST-CONTROL = *ON / *OFF
Operands
REQUEST-CONTROL = *ON
Turns on the priority control of the independent DBH. If priority control is already on, the
statement is rejected.
REQUEST-CONTROL = *OFF
Turns off the priority control of the independent DBH. If priority control is already on, the
statement is rejected.
U22418-J-Z125-6-76
291
SET-REQUEST-CONTROL
Administration
Administration command in ISP format and at the CALL DML interface
The OPT,REQ-CON administration command with specific operands corresponds to the
SET-REQUEST-CONTROL administration statement.
OPT,REQ-CON[,ON|,OFF]
If you enter the OPT,REQ-CON administration command without operands, priority control
is initialized with the relevant default values for weights and levels.
292
U22418-J-Z125-6-76
Administration
SET-SAT-SUPPORT
SET-SAT-SUPPORT
Controls logging of security relevant events with SAT in the current DBH session
Scope of validity
DBH administration
Function
Use the statement SET-SAT-SUPPORT to turn the logging of security relevant events with
SAT in the current DBH session on and off.
SET-SAT-SUPPORT
SAT = *ON / *OFF
Operands
SAT = *ON / *OFF
Turns the logging of security relevant events on or off. See also “Core Manual”, section
“Logging of security relevant events with SAT”.
Administration command in ISP format and at the CALL DML interface
The OPT,SAT administration command with specific operands corresponds to the SET-SATSUPPORT administration statement.
OPT,SAT=[ON|OFF]
U22418-J-Z125-6-76
293
SET-SQL-DB-CATALOG-STATUS
Administration
SET-SQL-DB-CATALOG-STATUS
This statement changes the status of a database.
Scope of validity
DBH administration
See also
The SHOW-SQL-DB-CATALOG-ENTRIES administration statement on page 324
Function
The SET-SQL-DB-CATALOG-STATUS statement changes the status of a database.
The possible statuses of a database and what they mean are explained in the functional
description of the SHOW-SQL-DB-CATALOG-ENTRIES administration statement.
Depending on the current status of the database, i.e. its status before you issue the SETSQL-DB-CATALOG-STATUS administration statement, the statement has different results.
A distinction can be drawn between the following cases:
●
●
294
When the status of the database is ACTIVE before you issue the administration
statement:
–
If you specify STATUS = ACTIVE in the administration statement, there is no
response. The status of the database remains ACTIVE.
–
If you specify STATUS = FREE in the administration statement, then the call is
synchronized if internal or external transactions involving this database are still
open. After synchronization is completed, the database is physically closed and the
status of the database is set to FREE in the SQL database catalog.
When the status of the database is FREE, LOCKED or DEFECT before you issue the
administration statement:
–
If you specify STATUS = ACTIVE in the administration statement, the database is
physically opened.
–
If you specify STATUS = FREE in the administration statement, nothing happens.
The status of the database remains FREE.
U22418-J-Z125-6-76
Administration
SET-SQL-DB-CATALOG-STATUS
SET-SQL-DB-CATALOG-STATUS
STATUS = *ACTIVE / *FREE
,SELECT = *LOGICAL(...) / *PHYSICAL(...)
*LOGICAL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*PHYSICAL(...)

PHYS-CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Operands
STATUS = *ACTIVE / *FREE
Status to which the database is to be set
SELECT=
Specifies the name by means of which the entry is identified.
SELECT= *LOGICAL(...)
The entry is identified by means of the logical database name.
CATALOG-NAME=
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database whose status is to be changed.
SELECT= *PHYSICAL(...)
The entry is identified by means of the physical database name.
PHYS-CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Physical name of the database whose status is to be changed
Administration command in ISP format and at the CALL DML interface
The OPT,DBC-UPD administration command corresponds to the SET-SQL-DB-CATALOGSTATUS administration statement.
OPT,DBC-UPD,supplement,S[TATUS]=status
status ::= {A[CTIVE] | F[REE]}
supplement ::= {C[ATALOG]=catalog-name|P[HYSICAL-NAME]=physical-name}
U22418-J-Z125-6-76
295
SET-TUNING-TRACE
Administration
SET-TUNING-TRACE
This statement controls request logging.
Scope of validity
DBH administration
Function
You use the SET-TUNING-TRACE statement to control the request logging of the DBH. You
can turn request logging on or off and specify the volume for the request log file (CO-LOG)
to which the DBH writes its data. You can also specify that the CPU time is to be measured.
When request logging is turned on, the DBH opens the CO-LOG file in order to log the data
in it. If you turn request logging off, the CO-LOG file is closed, even when there are requests
still open.
As soon as the CO-LOG file is closed, the SESCOSP utility edits and outputs the data
collected (see chapter “Evaluating request logging with SESCOSP” on page 341).
Each time request logging is turned on, the file count (iiii) in the default filename of the
CO-LOG file (SESAM.CO-LOG.ssss.iiii) is incremented by 0001. The placeholder ssss
stands for the session ID, which corresponds by default to the BS2000 task sequence
number, TSN (see the “Core Manual”).
In contrast to the recording of operational data with the SESMON performance monitor (see
chapter “Outputting operational data with SESMON” on page 377), this type of request
logging uses the resources of the DBH.
The USER-SELECT parameter allows you to restrict request logging to individual users.
This makes it possible to carry out logging for extended periods without subjecting the DBH
to excessive loads. When evaluating data with SESCOSP, note that the users defined in
SESCOSP represent a genuine subset of the users defined in USER-SELECT. In
SESCOSP the users to be evaluated can be further restricted by means of the SELECT
parameter USERS (see page 349).
296
U22418-J-Z125-6-76
Administration
SET-TUNING-TRACE
SET-TUNING-TRACE
TRACE = *ON(...) / *OFF
*ON(...)

















CPU-TIME = *NO / *YES
,PROTOCOL = *STD / *LONG
,USER-SELECT = *ALL / <user-identification>
,SUPPORT = *PUBLIC-DISK(...) / *PRIVATE-DISK(...) / *TAPE(...)
*PUBLIC-DISK(...)



CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = 192 / <integer 1..16777215>
,SECONDARY-ALLOCATION = 24 / <integer 0..32767>
*PRIVATE-DISK(...)





CAT-ID = *STD / <cat-id>
,PRIMARY-ALLOCATION = 192 / <integer 1..16777215>
,SECONDARY-ALLOCATION = 24 / <integer 0..32767>
,DEVICE-TYPE = <structured-name 1..8>
,VOLUME = list(6): <alphanum-name 1..6>
*TAPE(...)


DEVICE-TYPE = <structured-name 1..8>
,VOLUME = list(6): <alphanum-name 1..6>
*OFF
Operands
TRACE = *ON(...)
Turns on request logging.
CPU-TIME = *NO / *YES
Specifies whether or not the CPU time is to be recorded.
The default is NO, the CPU time is not recorded.
PROTOCOL = *STD / *LONG
Specifies the type of logging.
The following applies to the PROTOCOL=*STD:
– language-specific parts of the SQL statement are only logged to a limited degree;
SQL descriptors are not logged.
– specific parts of CALL-DML are only logged to a limited degree (statement, query
area and answer area).
Unlogged parts cannot be evaluated with SESCOSP (see page 341).
U22418-J-Z125-6-76
297
SET-TUNING-TRACE
Administration
The setting PROTOCOL=*LONG enables full logging.
In this case, the protocol generation loads the DBH still further and the CO-LOG file is
made much larger. The setting of the PRIMARY and SECONDARY ALLOCATION must
be adapted to the CO-LOG file where necessary.
USER-SELECT = *ALL / <user-identification>
Restricts the statement to a group of users. This partial qualification can have more than
one match. The syntax of the parameter is described in the section “Syntax for the
identification of users” on page 205. The default is *ALL (no restriction applies).
SUPPORT =
Specifies the volume for the CO LOG file.
SUPPORT = *PUBLIC-DISK(...)
Causes the CO LOG file to be created on a public disk.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the file is to be stored. The default is the DBH
catalog ID.
PRIMARY-ALLOCATION = 192 / <integer 1..16777215>
Number of PAM pages for the initial allocation of memory space. The specified
number of PAM pages is reserved immediately.
SECONDARY-ALLOCATION = 24 / <integer 0..32767>
Number of PAM pages for subsequent extensions to files
SUPPORT = *PRIVATE-DISK(...)
Causes the CO LOG file to be created on a private disk. To do this, you must make an
entry for DEVICE-TYPE.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the file is to be stored
PRIMARY-ALLOCATION = 192 / <integer 1..16777215>
Number of PAM pages for the initial allocation of memory space.
The specified number of PAM pages is reserved immediately.
SECONDARY-ALLOCATION = 24 / <integer 0..32767>
Number of PAM pages for subsequent extensions to files
DEVICE-TYPE = <structured-name 1..8>
BS2000 device type to which the required disks are assigned.
If you make an incorrect entry, the system prompts you in interactive mode to make
the entry again (see the device type table in the BS2000 manual “Commands,
Volumes 1 - 5”).
VOLUME = list(6): <alphanum-name 1..6>
VSNs of the disks on which the file is to be created. Up to six VSNs are permitted.
You can enter each VSN only once.
298
U22418-J-Z125-6-76
Administration
SET-TUNING-TRACE
SUPPORT = *TAPE(...)
Causes the CO LOG file to be created on tape. To do this, you must make an entry for
DEVICE-TYPE.
DEVICE-TYPE = <structured-name 1..8>
BS2000 device type to which the required disks are assigned.
If you make an incorrect entry, the system prompts you in interactive mode to make
the entry again (see the device type table in the BS2000 manual “Commands,
Volumes 1 - 5”).
VOLUME = list(6): <alphanum-name 1..6>
VSNs of the tapes on which the file is to be created. Up to six VSNs are permitted.
You can enter each VSN only once.
TRACE = *OFF
Turns request logging off.
Administration command in ISP format and at the CALL DML interface
The COS administration command corresponds to the SET-TUNING-TRACE administration statement.
COS,TP={ON[,CPU][,L[ONG]][,user-identification][,file-spec] | OFF}
file-spec ::= V[OL]=(vsn)[,D[EV]=device]
[,S[PACE]=(space)][,C[ATID]=cat-id]
The partial qualification for user-identification can have more than one match.
U22418-J-Z125-6-76
299
SET-USER-CALL-TRACE
Administration
SET-USER-CALL-TRACE
This statement controls the logging of statements.
Scope of validity
SESDCN administration
Function
You use the SET-USER-CALL-TRACE administration statement for diagnostic purposes. It
controls the logging of the call trace, i.e. of the CALL DML or SQL statements of one or more
application programs and the associated SESAM/SQL responses (see also section
“Diagnostics traces” on page 477).
You can turn the call trace on or off for all active users, selected users or a single user.
Statements issued in all application programs, such as SESDCN, that belong to the same
configuration and in which the specified user(s) is/are active are logged.
SET-USER-CALL-TRACE
TRACE = *ON(...) / *OFF(...)
*ON(...)

OUTPUT = SYSLST / list(2): SYSLST / SYSOUT
*OFF(...)

OUTPUT = (SYSLST,SYSOUT) / list(2): SYSLST / SYSOUT
,USER = <user-identification> / *ALL
300
U22418-J-Z125-6-76
Administration
SET-USER-CALL-TRACE
Operands
TRACE = *ON(...) / *OFF(...)
Turns the call trace on or off.
TRACE = *ON(...)
Turns the call trace on.
OUTPUT =
Specifies the output medium for the call trace of the application program.
OUTPUT = SYSLST
This is the default. The call trace is logged to SYSLST.
OUTPUT = list (2): SYSLST / SYSOUT
The call trace is logged only to SYSLST, only to SYSOUT or to both SYSLST and
SYSOUT.
TRACE = *OFF(...)
Turns the call trace off.
OUTPUT =
Specifies the output medium for the call trace of the application program to be turned
off.
OUTPUT = (SYSLST,SYSOUT)
This is the default. Logging of the call trace is turned off for SYSLST as well as for
SYSOUT.
OUTPUT = list (2): SYSLST / SYSOUT
Logging of the call trace is turned off for SYSLST, for SYSOUT or for both.
USER = <user-identification>
Identifies exactly one user whose call trace is to be turned on or off. The user must be
identified uniquely (see the section “Syntax for the identification of users” on page 205).
USER = *ALL
Turns the call trace on or off for all active users.
U22418-J-Z125-6-76
301
SET-USER-CALL-TRACE
Administration
Administration command in ISP format and at the CALL DML interface
The TRACE administration command in the following two formats corresponds to the SETUSER-CALL-TRACE administration statement:
Format 1:
The TRACE command sets the parameters that are to apply when logging is subsequently
turned on.
TRACE=PAR,TYPE=CALL[,OUTPUT={SYSOUT|SYSLST|(SYSOUT,SYSLST)}]
Format 2:
The TRACE command turns logging on or off user specifically.
TRACE={ON|OFF}[,USER=[host],[application],[user][,vgid]]
If you do not specify the USER parameter, logging of the call trace is turned on or off for all
users in the configuration.
The same TRACE command can activate the message trace (see page 304) or the call and
message trace if you enter the parameter TYPE=MSG or TYPE=(CALL,MSG) instead of
TYPE=CALL for the TRACE command in format 1.
Logging is always carried out based on the current values of the TYPE and OUTPUT
parameters, i.e. on the values last set by means of the TRACE command in format 1.
If you do not issue a TRACE command in format 1 during the session, the defaults CALL
and SYSLST apply to the TYPE and OUTPUT parameters.
302
U22418-J-Z125-6-76
Administration
SET-USER-INACTIVE-TIME
SET-USER-INACTIVE-TIME
This statement specifies the maximum permissible inactivity time.
Scope of validity
DBH administration
See also
The DBH option SQL-SUPPORT on page 123
Function
The SET-USER-INACTIVE-TIME administration statement allows you to modify as required
the maximum permissible inactivity time set by means of the DBH option SQL-SUPPORT.
The SET-USER-INACTIVE-TIME administration statement is only permitted in an SQL
session. It is also effective when the DBH has been started without inactivity checking.
SET-USER-INACTIVE-TIME
TIME-LIMIT = <integer 1..999> / *NONE
Operands
TIME-LIMIT = <integer 1..999> / *NONE
Specifies the maximum permissible inactivity time in minutes. *NONE turns off inactivity
checking, in which case the permissible inactivity time is unlimited.
Administration command in ISP format and at the CALL DML interface
The OPT,INACT administration command corresponds to the SET-USER-INACTIVE-TIME
administration statement.
OPT,INACT=[n|OFF]
U22418-J-Z125-6-76
303
SET-USER-MSG-TRACE
Administration
SET-USER-MSG-TRACE
This statement controls the logging of SESAM/SQL messages.
Scope of validity
SESDCN administration
Function
You use the SET-USER-MSG-TRACE administration statement for diagnostic purposes. It
controls the logging of SESAM/SQL messages exchanged between the task of an application program and the task of a SESAM/SQL DBH (message trace). In addition to application-program statements and the associated SESAM/SQL replies, the message trace
also receives internal SESAM/SQL administration information (see also section
“Diagnostics traces” on page 477).
You can turn the message trace on or off for all active users or for selected users.
Statements issued in all application programs that belong to the same configuration as
SESDCN and in which the specified user(s) is/are active are logged.
SET-USER-MSG-TRACE
TRACE = *ON(...) / *OFF(...)
*ON(...)

OUTPUT = SYSLST / list(2): SYSLST / SYSOUT
*OFF(...)

OUTPUT = (SYSLST,SYSOUT) / list(2): SYSLST / SYSOUT
,USER = <user-identification> / *ALL
304
U22418-J-Z125-6-76
Administration
SET-USER-MSG-TRACE
Operands
TRACE = *ON(...) / *OFF(...)
Turns the message trace on or off for the medium specified in OUTPUT.
TRACE = *ON(...)
Turns the message trace on.
OUTPUT =
Specifies the output medium for the message trace of the application program.
OUTPUT = SYSLST
This is the default. The message trace is logged to SYSLST.
OUTPUT = list (2): SYSLST / SYSOUT
The message trace is logged only to SYSLST, only to SYSOUT or to both SYSLST and
SYSOUT.
TRACE = *OFF(...)
Turns the message trace off.
OUTPUT =
Specifies the output medium for the message trace of the application program to be
turned off.
OUTPUT = (SYSLST,SYSOUT)
This is the default. Logging of the message trace is turned off for SYSLST as well as for
SYSOUT.
OUTPUT = list (2): SYSLST / SYSOUT
Logging of the message trace is turned off for SYSLST, for SYSOUT or for both.
USER = <user-identification>
Identifies exactly one user whose message trace is to be turned on or off. The user must
be identified uniquely (see the section “Syntax for the identification of users” on page 205).
USER = *ALL
Turns the message trace on or off for all active users.
U22418-J-Z125-6-76
305
SET-USER-MSG-TRACE
Administration
Administration command in ISP format and at the CALL DML interface
The TRACE administration command in the following two formats corresponds to the SETUSER-MSG-TRACE administration statement:
Format 1:
The TRACE command sets the parameters that are to apply when logging is subsequently
turned on.
TRACE=PAR,TYPE=MSG[,OUTPUT={SYSOUT|SYSLST|(SYSOUT,SYSLST)}]
Format 2:
The TRACE command turns logging on or off user specifically.
TRACE={ON|OFF}[,USER=[host],[application],[user][,vgid]]
If you do not specify the USER parameter, logging of the message trace is turned on or off
for all users in the configuration.
The same TRACE command can activate the call trace (see page 300) or the call trace and
message trace if you enter the parameter TYPE=CALL or TYPE=(CALL,MSG) instead of
TYPE=MSG for the TRACE command in format 1.
Logging is always carried out based on the current values of the TYPE and OUTPUT
parameters, i.e. on the values last set by means of the TRACE command in format 1.
If you do not issue a TRACE command in format 1 during the session, the defaults CALL
and SYSLST apply to the TYPE and OUTPUT parameters.
306
U22418-J-Z125-6-76
Administration
SHOW-CALL-DML-SUBORDERS
SHOW-CALL-DML-SUBORDERS
This statement displays the number of active CALL DML requests.
Scope of validity
DBH administration
Function
The SHOW-CALL-DML-SUBORDERS administration statement displays the number of
currently open logical files, i.e. the number of active CALL DML requests when the
statement is issued.
This statement can apply to all users or a selected one.
If no user or CALL DML requests are active, this is indicated to you.
SHOW-CALL-DML-SUBORDERS
USER = *ALL / <user-identification>
Operands
USER =
Identifies the user or users for whom the number of active CALL DML requests is displayed.
USER = *ALL
This is the default. It displays the total number of CALL DML requests.
USER = <user-identification>
Displays information only on the user with the identification specified here. The syntax of
the parameter is described in the section “Syntax for the identification of users” on
page 205.
The following is displayed:
– the user identification
– the user's conversation number (if the user is an asynchronous UTM application)
– the number of active CALL DML requests
i
U22418-J-Z125-6-76
The total sum of working memory occupied is not output any more as of
SESAM/SQL V3.0.
307
SHOW-CALL-DML-SUBORDERS
Administration
Example
Output to the screen after entering the SHOW-CALL-DML-SUBORDERS administration statement:
%SHOW-CALL-DML-SUBORDERS USER=*ALL
% 2003-09-08 13:42:55 SES7292 NUMBER OF LOGICAL FILES IN THE SYSTEM 9
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The USER administration command corresponds to the SHOW-CALL-DML-SUBORDERS
administration statement.
USER[,user-identification]
If you enter the administration command without user-identification, the total number of
active CALL DML requests of all users is displayed.
308
U22418-J-Z125-6-76
Administration
SHOW-CATALOG-USERS
SHOW-CATALOG-USERS
This statement displays the number of active users of selected databases.
Scope of validity
DBH administration
Function
The SHOW-CATALOG-USERS administration statement displays the number of users
accessing selected databases when you issue the statement. This means that only those
users are output that have access to the database within the transaction. CALL DML users
that only have one CALL DML open on a table in the database but do not yet have access
within a transaction are not taken into account.
If no databases are entered in the SQL database catalog, you receive a message to this
effect.
The following is displayed:
–
the logical name(s) of the selected database(s)
–
the status of each database (see the SHOW-SQL-DB-CATALOG-ENTRIES administration statement on page 324)
–
the number of active SQL and CALL DML users.
SHOW-CATALOG-USERS
CATALOG-NAME = *ALL / <filename 1..18 without-cat-id-user-id-generation-version>
Operands
CATALOG-NAME = *ALL /
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the selected database.
The default is *ALL, which means that all databases are selected.
U22418-J-Z125-6-76
309
SHOW-CATALOG-USERS
Administration
Example
Output to the screen after entering the SHOW-CATALOG-USERS administration
statement:
%SHOW-CATALOG-USERS
CATALOG DCCAT
STATE ACTIVE
CATALOG DB6LOKG
STATE ACTIVE
% 2003-09-08 13:44:21 SES7215 END OF OUTPUT
%//
LTG
0 USERS
7 USERS
TAST
Administration command in ISP format and at the CALL DML interface
The USER,CATALOG administration command corresponds to the SHOW-CATALOGUSERS administration statement.
USER,C[ATALOG][=catalog-name]
310
U22418-J-Z125-6-76
Administration
SHOW-DBH-MEDIA-CATALOG
SHOW-DBH-MEDIA-CATALOG
This statement displays the DBH option MEDIA-CATALOG.
Scope of validity
DBH administration
See also
The DBH option MEDIA-CATALOG on page 94
Function
The SHOW-DBH-MEDIA-CATALOG statement displays the currently valid entries of the
DBH option MEDIA-CATALOG.
SHOW-DBH-MEDIA-CATALOG
Operands
This statement has no operands.
U22418-J-Z125-6-76
311
SHOW-DBH-MEDIA-CATALOG
Administration
Example
Output to the screen after entering the SHOW-DBH-MEDIA-CATALOG administration
statement:
%SHOW-DBH-MEDIA-CATALOG
Media catalog output
------------------------------------------------------------------------------TALOG-SUPPORT:
SUPPORT=*PUBLIC-DISK
CAT-ID=*STD
PRIMARY-ALLOCATION=*STD
,SECONDARY-ALLOCATION=*STD
WALOG-SUPPORT:
SUPPORT=*PUBLIC-DISK
CAT-ID=*STD
PRIMARY-ALLOCATION=*STD
,SECONDARY-ALLOCATION=*STD
CURSOR-MEDIA: SUPPORT-1: SUPPORT=*PUBLIC-DISK
CAT-ID=*STD
PRIMARY-ALLOCATION=*STD
,SECONDARY-ALLOCATION=*STD
CURSOR-MEDIA: SUPPORT-2: SUPPORT=*PUBLIC-DISK
CAT-ID=*STD
PRIMARY-ALLOCATION=*STD
,SECONDARY-ALLOCATION=*STD
.
.
CURSOR-MEDIA: SUPPORT-5: SUPPORT=*PUBLIC-DISK
CAT-ID=*STD
PRIMARY-ALLOCATION=*STD
,SECONDARY-ALLOCATION=*STD
% 2003-09-08 13:47:12 SES7215 END OF OUTPUT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The OPT,MEDIA administration command corresponds to the SHOW-DBH-MEDIACATALOG administration statement.
OPT,MEDIA
312
U22418-J-Z125-6-76
Administration
SHOW-DBH-OPTIONS
SHOW-DBH-OPTIONS
This statement displays DBH options.
Scope of validity
DBH administration
Function
The SHOW-DBH-OPTIONS statement displays the currently valid entries of all DBH
options except MEDIA-CATALOG.
You can display entries of the DBH option MEDIA-CATALOG separately by means of the
SHOW-DBH-MEDIA-CATALOG administration statement.
SHOW-DBH-OPTIONS
Operands
This statement has no operands.
U22418-J-Z125-6-76
313
SHOW-DBH-OPTIONS
Administration
Example
Output to the screen after entering the SHOW-DBH-OPTIONS administration
statement:
%SHOW-DBH-OPTIONS
Current SESAM-DBH options output
------------------------------------------------------------------------------ACCOUNTING
*OFF
ADMINISTRATOR
*ANY
COLUMNS
256
CURSOR-BUFFER
BUFFER-SIZE=640
, FRAME-SIZE=4
DBH-IDENTIFICATION
CONFIGURATION-NAME=G, DBH-NAME=6
DBH-TASKS
1
MSG-OUTPUT
MSG
=*SYSOUT, *SYSLST
OPEN-CLOSE-MSG=*SYSOUT, *SYSLST
OLD-TABLE-CATALOG
10
REQUEST-CONTROL
*NONE
.
.
TRANSFER-CONTAINER
INITIAL=224
, MAXIMUM=16000
USERS
40
USER-DATA-BUFFER
1920
, BUFFER-STRATEGY=*LRU
WORK-CONTAINER
INITIAL=224
, MAXIMUM=224
% 2003-09-08 13:48:32 SES7215 END OF OUTPUT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The OPT administration command corresponds to the SHOW-DBH-OPTIONS administration statement.
OPT
314
U22418-J-Z125-6-76
Administration
SHOW-DISTRIBUTION-RULE-ENTRIES
SHOW-DISTRIBUTION-RULE-ENTRIES
This statement displays the active databases in the distribution rule.
Scope of validity
SESDCN administration
Function
The SHOW-DISTRIBUTION-RULE-ENTRIES statement displays all the databases entered
in the distribution rule.
The following appears for each database:
–
the logical database name (CATALOG)
–
the number of users (USER)
–
the host name (PRO-NAME)
–
the DBH name (DBH-NAME)
–
the DCN name (DCN-NAME)
–
the configuration name (CNF-NAME).
SHOW-DISTRIBUTION-RULE-ENTRIES
Operands
This statement has no operands.
U22418-J-Z125-6-76
315
SHOW-DISTRIBUTION-RULE-ENTRIES
Administration
Example
Output to the screen after entering the SHOW-DISTRIBUTION-RULE-ENTRIES
administration statement:
%SHOW-DISTRIBUTION-RULE-ENTRIES
CATALOG
! USER ! PRO-NAME !DBH-NAME!DCN-NAME!CNF-NAME!
!
!
!
!
!
!
-------------------------------------------------------------------------------DB6LOKG
!
7 ! D016ZE09 !
6
!
A
!
G
!
DB7LOKG
!
0 ! D016ZE09 !
7
!
A
!
G
!
DB0LOKG
!
0 ! D016ZE09 !
!
A
!
G
!
DCCAT
!
0 ! D016ZE09 !
7
!
A
!
G
!
DCCAT8
!
0 ! D016ZE09 !
8
!
A
!
G
!
DB6REMG
!
0 ! D016ZE07 !
6
!
A
!
G
!
DB7REMG
!
0 ! D016ZE07 !
7
!
A
!
G
!
DB8REMG
!
0 ! D016ZE07 !
8
!
A
!
G
!
DB6LOKH
!
0 ! D016ZE09 !
6
!
A
!
H
!
DB7LOKH
!
0 ! D016ZE09 !
7
!
A
!
H
!
DB8LOKH
!
0 ! D016ZE09 !
8
!
A
!
H
!
DB6LOKI
!
0 ! D016ZE09 !
6
!
A
!
I
!
DB7LOKI
!
0 ! D016ZE09 !
7
!
A
!
I
!
DB8LOKI
!
0 ! D016ZE09 !
8
!
A
!
I
!
% 2003-09-08 14:09:10 SEN2014 END OF THE 'SESDCN' ADMINISTRATION STATEMENT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The USER,CATALOG administration command corresponds to the SHOWDISTRIBUTION-RULE-ENTRIES administration statement.
USER,CATALOG
316
U22418-J-Z125-6-76
Administration
SHOW-INACTIVE-SQL-USERS
SHOW-INACTIVE-SQL-USERS
This statement displays inactive SQL users.
Scope of validity
DBH administration
Function
The SHOW-INACTIVE-SQL-USERS administration statement displays all currently inactive
SQL users. If there is no user in the system, a message will appear stating this fact.
The following appears:
–
the user identification
–
the user's conversation number if the user is an asynchronous UTM application
–
the inactivity time in seconds (INACT-TIME).
The inactivity time is the time in which an SQL conversation has not opened a transaction.
SHOW-INACTIVE-SQL-USERS
Operands
This statement has no operands.
U22418-J-Z125-6-76
317
SHOW-INACTIVE-SQL-USERS
Administration
Example
Output to the screen after entering the SHOW-INACTIVE-SQL-USERS administration
statement:
%SHOW-INACTIVE-SQL-USERS
USER-ID: D016ZE09TSN=2BBZUTMTOOL
INACT-TIME:
% 2003-09-08 14:20:37 SES7215 END OF OUTPUT
%//
LTG
44 (SEC.)
TAST
Administration command in ISP format and at the CALL DML interface
The USER,INACT administration command corresponds to the SHOW-INACTIVE-SQLUSERS administration statement.
USER,INACT
318
U22418-J-Z125-6-76
Administration
SHOW-OLD-TABLE-CATALOG-ENTRIES
SHOW-OLD-TABLE-CATALOG-ENTRIES
This statement displays entries in the CALL DML table catalog.
Scope of validity
DBH administration
See also
–
The DBH start statement ADD-OLD-TABLE-CATALOG-LIST on page 73
–
The administration statement REUSE-OLD-TABLE-CATALOG-ENTRY on page 278
Function
The SHOW-OLD-TABLE-CATALOG-ENTRIES statement displays the entries in the CALL
DML table catalog. The following appears for each entry:
●
the name of a CALL DML table (call dml table)
●
the logical name of the database to which the CALL DML table is assigned
(catalog name)
●
the name of the schema to which the CALL DML table is assigned ( schema name)
●
the name of the base table to which the CALL DML table is assigned (table name)
●
the status of the entry:
valid:
When analyzing the entry, an assignment to a CALL DML table was detected;
this assignment still exists.
invalid:
When analyzing the entry, either no assignment to an existing table could be
found or this assignment has been lost again. This is the case when:
–
The database has either been closed again in the meantime (by means of
the SET-CATALOG-STATUS administration statement, for example) or
was not open when the entry was analyzed.
–
The table to which the assignment is to be made is not known (or no longer
known) in the database (e.g. because DROP TABLE was issued for the
table, for example).
.
U22418-J-Z125-6-76
319
SHOW-OLD-TABLE-CATALOG-ENTRIES
Administration
SHOW-OLD-TABLE-CATALOG-ENTRIES
SELECT = *ALL / *SQL(...) / *CALL-DML(...)
*SQL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*CALL-DML(...)

CALL-DML-TABLE-NAME = <text 1..17>
Operands
SELECT =
Specifies which entries in the CALL DML table catalog are to be displayed.
SELECT = *ALL
Specifies that all entries in the CALL DML table catalog are to be displayed.
SELECT = *SQL(...)
Specifies that those entries containing a specific CATALOG-NAME are to be displayed.
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical database name that functions as a criterion for displaying the associated entries
SELECT = *CALL-DML(...)
Specifies that only the entry containing the specified CALL-DML-TABLE-NAME is to be
displayed.
CALL-DML-TABLE-NAME = <text 1..17>
Name of the CALL DML table whose entry is displayed
320
U22418-J-Z125-6-76
Administration
SHOW-OLD-TABLE-CATALOG-ENTRIES
Example
Output to the screen after entering the SHOW-OLD-TABLE-CATALOG-ENTRIES
administration statement:
%SHOW-OLD-TABLE-CATALOG-ENTRIES
<call-dml-table> |<catalog-name>
|<schema-name> / <table-name>
|<status>
------------------------------------------------------------------------------DB6LOKG
|DB6LOKG
|SCHEMA112
| valid
|
|TAB112
|
% 2003-09-08 13:53:23 SES7215 END OF OUTPUT %//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The OPT,CDBC-INFO administration command corresponds to the SHOW-OLD-TABLECATALOG-ENTRIES administration statement.
OPT,CDBC-INFO[,supplement]
supplement :: = {C[ATALOG]=catalog-name|
C[ALL-DML-]T[ABLE]=call-dml-table-name}
If you do not specify the supplement parameter, the whole CALL DML table catalog is
displayed.
U22418-J-Z125-6-76
321
SHOW-SPACE-USERS
Administration
SHOW-SPACE-USERS
This statement displays the users currently working in a space.
Scope of validity
DBH administration
Function
The SHOW-SPACE-USERS administration statement displays all users currently working
in the selected space of a specific database. A user works in a space when using tables or
indexes created in this space. In addition, system-generated identifications of the internal
administrator (see page 208) are output if transactions are executed for the internal administrator in the space.
Only those users are output that have access within a transaction to the space. CALL DML
users that only have one CALL DML open on a table of the space but do not have access
within the transaction are not taken into account.
The following information is displayed:
–
the user identification
–
the user's conversation number if the user is an asynchronous UTM application
–
the program runtime in seconds (DURATION-TIME)
–
the access mode (ACCESS) of the space (READ, WRITE or ADMIN)
–
the state of the space (“copy”, “check pending” or “defect”). You will find information on
the different space states in the “Core Manual”.
SHOW-SPACE-USERS
SPACE-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
,CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
322
U22418-J-Z125-6-76
Administration
SHOW-SPACE-USERS
Operands
SPACE-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Name of the space whose users are displayed. The name of the space is the name of the
space file in BS2000.
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the selected database
If the space cannot be identified based on the two names, a message to this effect
is output.
i
Example
Screen output after entry of the administration statement SHOW-SPACE-USERS
SPACE-NAME=TABLESPACE,CATALOG-NAME=ORDERCUST:
SPACE TABLESPACE
-----------------------------------------------------------------------USER-IDENTIFICATION
!DURATION-TIME! ACCESS
-----------------------------------------------------------------------D016ZE07TSN=12LDSESUTI
!
20 ! READ
% 2003-07-05 15:05:51 SES7215 END OF OUTPUT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The USER,SPACE administration command corresponds to the SHOW-SPACE-USERS
administration statement.
USER,SPACE=space-name,C[ATALOG]=catalog-name
U22418-J-Z125-6-76
323
SHOW-SQL-DB-CATALOG-ENTRIES
Administration
SHOW-SQL-DB-CATALOG-ENTRIES
This statement displays entries from the SQL database catalog.
Scope of validity
DBH administration
See also
The DBH start statement ADD-SQL-DATABASE-CATALOG-LIST on page 76
Function
The SHOW-SQL-DB-CATALOG-ENTRIES statement allows you to display entries in the
SQL database catalog. The following appears for each entry:
●
the logical database name
●
the physical database name
●
in addition, the number of the SESAM backup copy of the catalog space, if the database
is a SESAM backup copy of a database
●
the access mode (Class) permitted for this database (READ, WRITE, ADMIN and
REPLICATION)
●
the DB user ID of the database (USERID)
●
the status of the database (Status) with additional information (Info)
The following statuses are possible:
– STATUS = ACTIVE, which means the database is open during the current DBH
session
– STATUS = FREE, which means the database is physically closed and unlocked
– STATUS = LOCKED, which means the database is not available during the current
session because of a lock
You receive additional information with this status as to why the database is not
available. If there is a DMS error, you receive the DMS error key.
If the problem (e.g. DMS error) has been eliminated, you can use the SET-SQL-DBCATALOG-STATUS administration statement to set the status of the database to
ACTIVE.
– Status = RECOVER, i.e. the database is currently in a state of recovery.
The status of the database changes automatically to ACTIVE at the end of the
recovery if the recovery was successful, or it changes to LOCKED if it could not be
completed successfully.
324
U22418-J-Z125-6-76
Administration
SHOW-SQL-DB-CATALOG-ENTRIES
–
Status = REORG, i.e. the database is currently in a state of reorganization.
The status of the database changes automatically to ACTIVE at the end of the
reorganization if the reorganization was successful, or it changes to LOCKED if it
could not be completed successfully.
Status = REFRESH, i.e. the database is currently in a state of refresh.
The status of the database changes automatically to ACTIVE at the end of the
refresh if the refresh was successful, or it changes to LOCKED if it could not be
completed successfully.
–
SHOW-SQL-DB-CATALOG-ENTRIES
SELECT = *ALL / *LOGICAL(...) / *PHYSICAL(...)
*LOGICAL(...)

CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
*PHYSICAL(...)

PHYS-CATALOG-NAME = <filename 1..18 without-cat-id-user-id-generation-version>
Operands
SELECT =
Specifies which entries from the SQL database catalog are to be displayed.
SELECT = *ALL
Specifies that all entries from the SQL database catalog are to be displayed.
SELECT = *LOGICAL(...)
Specifies that those entries containing the specified CATALOG-NAME are to be displayed.
CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Logical name of the database whose entry is displayed. If the database is a SESAM
backup copy, the number of the SESAM backup copy of the catalog space is also output
on the output medium.
SELECT = *PHYSICAL(...)
Specifies that those entries containing the specified PHYS-CATALOG-NAME are to be
displayed.
PHYS-CATALOG-NAME =
<filename 1..18 without-cat-id-user-id-generation-version>
Physical name of the database whose entry is displayed. If the database is a SESAM
backup copy, the number of the SESAM backup copy of the catalog space is also output
on the output medium.
U22418-J-Z125-6-76
325
SHOW-SQL-DB-CATALOG-ENTRIES
Administration
Example
Output to the screen after entering the SHOW-SQL-DB-CATALOG-ENTRIES administration statement:
%SHOW-SQL-DB-CATALOG-ENTRIES
<catalog-name>
| Copy-|Class| UserID
| Status | Info
<physical-name>
| Nr
|
|
|
|
------------------------------------------------------------------------------DCCAT
|
|ADMIN| SQLDB112 | ACTIVE |
DB112.G6
|
|
|
|
|
DB6LOKG
|
|ADMIN| SQLDB112 | ACTIVE |
CATG6
|
|
|
|
|
% 2003-09-08 14:00:48 SES7215 END OF OUTPUT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The OPT,DBC-INFO administration command corresponds to the SHOW-SQL-DBCATALOG-ENTRIES administration statement.
OPT,DBC-INFO[,supplement]
supplement ::= {C[ATALOG]=catalog-name|P[HYSICAL-NAME]=physical-name}
If you do not specify the supplement parameter, the whole SQL database catalog is
displayed.
326
U22418-J-Z125-6-76
Administration
SHOW-TRANSACTIONS
SHOW-TRANSACTIONS
This statement displays open transactions.
Scope of validity
DBH and SESDCN administration
Function
The SHOW-TRANSACTIONS administration statement displays a table of all open transactions. In SESDCN administration, you can use the statement to display the open transactions of selected users.
This statement is rejected if there are currently no open transactions active in the DBH or
known to SESDCN, in which case you receive a message to this effect. The statement is
also rejected if the DBH was loaded without transaction management.
What is displayed in DBH administration differs from what is displayed in SESDCN administration.
In DBH administration, the following information appears for each open transaction:
●
The user identification
If the user is an asynchronous UTM application, the conversation number is also
displayed.
●
The number of executed I/Os (NUMBER OF I/OS)
●
The runtime in seconds since the beginning of the transaction (DURATION TIME)
●
The status of the transaction (STATUS).
The following transaction statuses are possible:
– Ë (the request is being processed in a thread)
– LOCK (the transaction is locked by another transaction)
– FREE (the request is unlocked)
– PTC (the transaction is at the prepare-to-commit stage)
– ADM (the user is the system administrator)
– RESET (the transaction is being rolled back)
– CAN (the SQL data-manipulation statement is canceled).
– UTI (utility statement)
– INTERN (internal system transaction)
●
The request identification of the locking transaction if the status of the transaction is
LOCK (user-identification BY LOCK). If the user is an asynchronous UTM application,
the conversation number is also displayed.
U22418-J-Z125-6-76
327
SHOW-TRANSACTIONS
Administration
●
In addition, the system-generated identifications of the internal administrator (see
page 210) are output if the internal administrator has locked transactions that are to be
output.
●
Utility statements are output here, as well, although they do not represent transactions
that are visible from the outside. The utility statements are displayed nevertheless
because they can hold locks.
In SESDCN administration, the following information is displayed for each open transaction:
●
the user identification
If the user is an asynchronous UTM application, the conversation number is also
displayed.
●
the runtime (in seconds:minutes) since the beginning of the transaction (RUN-TIME).
●
the activity level of the transaction as a measure of the work completed by the transaction (ACTIVITY LEVEL). The activity level is the sum of all physical I/Os that a transaction has initiated. However, a correct value is only obtained when logging of request
accounting is activated for all the DBHs involved by means of the DBH option
ACCOUNTING (see page 71) or the administration statement SET-ACCOUNTINGPARAMETER (see page 284).
●
the name of the computer on which the transaction is or was active (LOCATION). If the
transaction has not yet been active on any computer, “NO” appears here.
●
the state of the transaction (STATE). The following transaction states exist:
– R (READ)
– W (WRITE)
– R/W (READ and WRITE)
– BTA (beginning of the transaction)
– PTC (the transaction is in the state “prepared to commit”)
– LOCK (the transaction is locked by another transaction)
– UNLC (the transaction is not locked).
●
the lock time (in hours:minutes) if the state of the transaction is LOCK (LOCK-TIME).
SHOW-TRANSACTIONS
USER = *ALL / <user-identification>
328
U22418-J-Z125-6-76
Administration
SHOW-TRANSACTIONS
Operands
USER =
Identifies the user or users whose transactions are to be displayed.
USER = *ALL
This is the default. All open transactions are displayed.
In DBH administration, only the default is permitted.
USER = <user-identification>
Only the open transactions of the user with the specified identification are displayed.
The syntax of the parameter is described in the section “Syntax for the identification of
users” on page 205.
This parameter is permitted only in SESDCN administration.
Example 1
Output to the screen after entering the SHOW-TRANSACTIONS administration
statement in DBH administration:
%SHOW-TRANSACTIONS
USER-IDENTIFICATION ! NUMBER ! DURATION! STATUS ! USER-IDENTIFICATION
ACTIVE
! OF I/OS ! TIME
!
! BY LOCK
-----------------------------------------------------------------------D016ZE07TSN=8GPZ
!
0!
0! ADM
!
ADMINIST
!
!
!
!
D016ZE09TSN=2A2V
!
0!
2053!
!
USER0005
!
!
!
!
D016ZE09TSN=2A2V
!
0!
2035!
!
USER0006
!
!
!
!
D016ZE09TSN=2A2V
!
12!
2123!
!
USER0001
!
!
!
!
D016ZE09TSN=2A2V
!
0!
2106!
!
USER0002
!
!
!
!
D016ZE09TSN=2A2V
!
0!
2085!
!
USER0003
!
!
!
!
D016ZE09TSN=2A2V
!
0!
2070!
!
USER0004
!
!
!
!
% 2003-09-08 14:04:19 SES7215 END OF OUTPUT
%//
LTG
U22418-J-Z125-6-76
TAST
329
SHOW-TRANSACTIONS
Administration
Example 2
Output to the screen after entering the SHOW-TRANSACTIONS administration
statement in SESDCN administration:
%SHOW-TRANSACTIONS
USER
! RUN-!ACTIVITY!LOCATION! STATE ! LOCK! TIME! LEVEL !
!
! TIME
-------------------------------------------------------------------------------D016ZE09TSN=2A2VUSER000100000000EXAMPLE ! 0:42!
0 !D016ZE09!BTA UNLC!
D016ZE09TSN=2A2VUSER000200000000EXAMPLE ! 0:41!
0 !D016ZE09!BTA UNLC!
D016ZE09TSN=2A2VUSER000300000000EXAMPLE ! 0:41!
0 !D016ZE09!BTA UNLC!
D016ZE09TSN=2A2VUSER000400000000EXAMPLE ! 0:41!
0 !D016ZE09!BTA UNLC!
D016ZE09TSN=2A2VUSER000500000000EXAMPLE ! 0:40!
0 !D016ZE09!BTA UNLC!
D016ZE09TSN=2A2VUSER000600000000EXAMPLE ! 0:40!
0 !D016ZE09!BTA UNLC!
% 2003-09-08 14:10:14 SEN2014 END OF THE 'SESDCN' ADMINISTRATION STATEMENT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The USER,TA administration command corresponds to the SHOW-TRANSACTIONS
administration statement.
USER,TA
330
U22418-J-Z125-6-76
Administration
SHOW-USERS
SHOW-USERS
This statement displays active users.
Scope of validity
DBH and SESDCN administration
Function
The SHOW-USERS administration statement displays all currently active users. Active
users are those currently working with the DBH or with SESDCN.
If no users are currently active, you receive a message to this effect.
What is displayed in DBH administration is different to what is displayed in SESDCN administration.
In DBH administration, the following information is displayed for each active user:
●
the user's identification
If the user is an asynchronous UTM application, the conversation number is also
displayed. System-generated identifications may also be displayed here, after a restart,
for example (see page 210). If there is a lock sequence active for the system-internal
user, this user is displayed here.
●
the number of password violations, if any
●
the user's activity status
The following activity statuses are possible:
– Ë (the request is being processed in a thread)
– LOCK (the request is locked by another request)
– FREE (the request is unlocked)
– PTC (the transaction is at the prepare-to-commit stage)
– RESET (the user's transaction is being rolled back)
– ADM (the user is the system administrator)
– CAN (the SQL data-manipulation statement is canceled by means of the CANCELSTATEMENT administration statement)
– UTI (utility monitor request).
– INTERN (internal system transaction)
●
the string LOCK-SEQ if the user has opened a lock sequence
●
the number of logical files in CALL DML, if any are used
●
the number of password violations, if any
U22418-J-Z125-6-76
331
SHOW-USERS
Administration
In SESDCN administration, the following information is displayed for each active user:
●
the user's identification
If the user is an asynchronous UTM application, the conversation number is also
displayed.
●
the application's mode.
The following modes are possible:
– UTM (UTM transaction application)
– DCAM (DCAM transaction application)
– TIAM (interactive mode)
– BAT (transaction application in batch mode).
●
the time (in hours:minutes) since the beginning of the conversation (ELAPSTIME)
●
the name of the computer on which the addressed databases are stored (LOCATION)
If no database has yet been addressed, the name of the home system appears here.
●
the name of the database(s) being accessed by the SESDCN user (CATALOG IN USE)
If no database has yet been addressed, “NO” appears here.
SHOW-USERS
Operands
This statement has no operands.
332
U22418-J-Z125-6-76
Administration
SHOW-USERS
Example 1
Output to the screen after entering the SHOW-USERS administration statement in DBH
administration:
%SHOW-USERS
1.: D016ZE07TSN=8GPZADMINIST
NO. OF LOG. FILES IN CALL-DML:
2.: D016ZE09TSN=2A2VUSER0005
NO. OF LOG. FILES IN CALL-DML:
3.: D016ZE09TSN=2A2VUSER0006
NO. OF LOG. FILES IN CALL-DML:
4.: D016ZE09TSN=2A2VUSER0001
NO. OF LOG. FILES IN CALL-DML:
5.: D016ZE09TSN=2A2VUSER0002
NO. OF LOG. FILES IN CALL-DML:
6.: D016ZE09TSN=2A3VADMINIST
NO. OF LOG. FILES IN CALL-DML:
7.: D016ZE09TSN=2A2VUSER0003
NO. OF LOG. FILES IN CALL-DML:
8.: D016ZE09TSN=2A2VUSER0004
NO. OF LOG. FILES IN CALL-DML:
% 2003-09-08 14:05:15 SES7215 END OF OUTPUT
%//
LTG
U22418-J-Z125-6-76
ADM
1
1
1
1
1
ADM
1
1
1
TAST
333
SHOW-USERS
Administration
Example 2
Output to the screen after entering the SHOW-USERS administration statement in
SESDCN administration:
%SHOW-USERS
USER
!MODE!ELAPS!LOCATION!
CATALOG
!
! TIME!
!
IN USE
-------------------------------------------------------------------------------D016ZE09TSN=2A2VUSER000100000000EXAMPLE !DCAM! 0:42!D016ZE09!DB6LOKG
D016ZE09TSN=2A2VUSER000200000000EXAMPLE !DCAM! 0:42!D016ZE09!DB6LOKG
D016ZE09TSN=2A2VUSER000300000000EXAMPLE !DCAM! 0:42!D016ZE09!DB6LOKG
D016ZE09TSN=2A2VUSER000400000000EXAMPLE !DCAM! 0:41!D016ZE09!DB6LOKG
D016ZE09TSN=2A2VUSER000500000000EXAMPLE !DCAM! 0:41!D016ZE09!DB6LOKG
D016ZE09TSN=2A2VUSER000600000000EXAMPLE !DCAM! 0:41!D016ZE09!DB6LOKG
D016ZE09TSN=2A3VADMINIST00000000SQLDB112!TIAM! 0:39!D016ZE09! NO
% 2003-09-08 14:11:07 SEN2014 END OF THE 'SESDCN' ADMINISTRATION STATEMENT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The USER,PR administration command corresponds to the SHOW-USERS administration
statement.
USER,PR
334
U22418-J-Z125-6-76
Administration
SHOW-USER-SPACES
SHOW-USER-SPACES
This statement displays the spaces that are used by the user and are thus locked.
Scope of validity
DBH administration
Function
The SHOW-USER-SPACES statement specifies all the spaces that are used by a specified
user and are thus locked.
For every space identified in this way, the logical database name and the name of the space
are displayed. In addition, it is indicated whether the space is accessed exclusively.
SHOW-USER-SPACES
USER = <user-identification>
Operands
USER = <user-identification>
Identifies the user. The identification must be fully qualified (see the section “Syntax for the
identification of users” on page 205).
U22418-J-Z125-6-76
335
SHOW-USER-SPACES
Administration
Example
Screen output after entry of the SHOW-USER-SPACES administration statement in
DBH administration:
USER:
TSN=12LD
-----------------------------------------------------------------------NR.
! CATALOG-NAME
! SPACE-NAME
! LOCK-MODE
-----------------------------------------------------------------------1 ! ORDERCUST
! CATALOG
!
2 ! ORDERCUST
! TABLESPACE
!
% 2003-07-05 15:09:04 SES7215 END OF OUTPUT
%//
LTG
TAST
Administration command in ISP format and at the CALL DML interface
The SPACE administration command corresponds to the SHOW-USER-SPACES administration statement here.
SPACE,user-identification
336
U22418-J-Z125-6-76
Administration
STOP-DBH
STOP-DBH
This statement terminates the DBH session.
Scope of validity
DBH administration
Function
The STOP-DBH statement terminates the DBH session.
Before the DBH session is terminated, the DBH rolls back all open transactions except PTC
transactions, empties all buffers and closes the databases involved. If there are PTC transactions, utility statements or lock sequences in the system, SESAM/SQL rejects the
statement. A table containing an overview of these PTC transactions or statements is
output. The TA-LOG file remains active.
In the case of an application with SESAM/SQL and openUTM, the STOP-DBH statement
allows you to choose whether the restart information for the UTM warm start is to be backed
up or deleted.
The restart information is backed up by default. This is important when a DBH restart, but
not a UTM warm start, has been carried out after a system failure. Only if the restart information of the DBH (TA-LOG and WA-LOG file) has been backed up is a UTM warm start
possible in the following DBH session.
You can terminate the DBH up to 64 times with restart-information backup without endangering the UTM warm start.
STOP-DBH
UTM-SESSION-INFO = *KEEP / *DELETE
U22418-J-Z125-6-76
337
STOP-DBH
Administration
Operands
UTM-SESSION-INFO =
Specifies whether the restart information for the UTM warm start is to be backed up or
deleted.
UTM-SESSION-INFO = *KEEP
This is the default. The restart information from the TA-LOG and WA-LOG files of the DBH
is backed up in case a UTM warm start becomes necessary.
UTM-SESSION-INFO = *DELETE
The restart information for the UTM warm start is deleted.
Administration command in ISP format and at the CALL DML interface
Two administration commands fulfill the function of the STOP-DBH administration
statement: STOP[,KEEP] and STOP,DELETE.
STOP[,KEEP]
STOP,DELETE
If you enter only STOP, SESAM/SQL uses the STOP,KEEP command internally.
338
U22418-J-Z125-6-76
Administration
STOP-DCN
STOP-DCN
This statement terminates SESDCN.
Scope of validity
SESDCN administration
Function
The STOP-DCN statement terminates the SESDCN without error.
If an SESDCN has been terminated, remote access is then no longer possible to databases
to which it is assigned as the remote DCN in the distribution rule.
The loaded distribution rule is retained, however, until all application programs and DBHs
in the distributed system and all other SESDCNs in this configuration have been terminated.
STOP-DCN
Operands
This statement has no operands.
Administration command in ISP format and at the CALL DML interface
The STOP administration command corresponds to the STOP-DCN administration
statement.
STOP
U22418-J-Z125-6-76
339
Eine Dokuschablone von Frank Flachenecker
by f.f. 1992
6 Evaluating request logging with SESCOSP
SESAM/SQL logs request-specific data. From the user's viewpoint, a SESCOSP request
corresponds to a statement.
The system administrator uses the SET-TUNING-TRACE administration statement or the
COS administration command (see page 296) to turn request logging on and off. The
system administrator controls the logged data amount by means of the operand
PROTOCOL=*STD/*LONG. When request logging is on, the DBH logs data in a request log
file (the CO-LOG file). The request log file contains a large amount of data, which the
SESCOSP utility then evaluates.
The logged data indicates which statements have been executed for which program, and
which spaces, tables and databases have been addressed. The system administrator can
use the logged data to follow what happened during the relevant period and carry out a
precise analysis. In this way, SESCOSP reports can be used as a basis for finding out
performance-critical statements. The “Performance” manual provides assistance in
analyzing performance problems and indicates any measures required to improve
throughput.
The user can set parameters to cause SESCOSP to evaluate only a subset of the data
logged in the request log file. You can limit the evaluation to selected databases, parts of
databases, users, statements and time periods.
SESCOSP reports essentially provide the following information:
–
for each statement: I/Os and time behavior
–
for each statement step: I/Os, time behavior and accesses to resources
–
for each transaction: I/Os and time behavior
–
for each statement group: termination statistics in the form of total and average values.
SESCOSP outputs the data in selectable report formats.
U22418-J-Z125-6-76
341
Calling SESCOSP
SESCOSP
DBH
Logging
Input
parameters
CO-LOG
file
SESCOSP
Selected data
Edited output
Figure 6: Request logging and evaluation with SESCOSP
i
The following always applies:
Output sent to SYSOUT and SYSLST is not upwardly compatible.
Output layout may vary depending on the version used.
6.1 Calling SESCOSP
Command for starting SESCOSP
/START-SESAM-TUNING-TRACE-EVAL
Starts SESCOSP with the start command START-SESAM-TUNING-TRACE-EVAL (see
section “Starting SESAM/SQL programs via start commands” on page 31).
342
U22418-J-Z125-6-76
SESCOSP
Calling SESCOSP
Example
SESCOSP is started by means of the procedure BEISP.START.COSP.
/CALL-PROCEDURE NAME=BEISP.START.COSP,PROCEDURE-PARAMETERS=NO, /
LOGGING=PARAMETERS(COMMANDS=YES,DATA=YES)
The input parameters are read in via an SDF screen. Since only the name of the
CO-LOG file to be evaluated is specified, SESCOSP generates a report with the default
settings.
/BEGIN-PROCEDURE LOGGING=ALL
/ASSIGN-SYSLST TO-FILE=LST.SESDBB.P.SESCOSP.K6
/ASSIGN-SYSDTA TO-FILE=*PRIMARY
/MOD-MSG-ATTRIBUTES TASK-LANGUAGE=D
/MODIFY-SDF-OPTIONS GUIDANCE=MAXIMUM
/START-SESAM-TUNING-TRACE-EVAL
PROGRAMM
: SESCOSP
STATEMENT: CREATE-REPORT
-------------------------------------------------------------------------------INPUT-FILE
= SESAM.CO-LOG.70EX.0002
Filename_1..54_without-generation-version
Input file, Standard: SESAM.CO-LOG.<TSN>.<NR>
OUTPUT
= *SYSLST
*SYSLST or filename_1..54_without-generation-version
Name of the output file
SELECT
= *ALL
*ALL or *PARAMETERS()
Selection criteria for input
REPORT-FORMAT
= *STD
*STD or *PARAMETERS()
Generic term for all selection criteria for the
output
-------------------------------------------------------------------------------NEXT = *CONTINUE
*EXECUTE"F3" / + / Follow-up statement / *CONTINUE / *EXIT"K1" /
*EXIT-ALL"F1" / *TEST"F2"
MESSAGE:
CMD0175 OTHER OPERATIONS DESIRED? PRESS *EXIT KEY
//CREATE-REPORT INPUT-FILE=SESAM.CO-LOG.70EX.0002
/ASSIGN-SYSLST TO-FILE=*PRIMARY
/MODIFY-SDF-OPTIONS GUIDANCE=EXPERT
/END-PROCEDURE
U22418-J-Z125-6-76
343
CREATE-REPORT
SESCOSP
6.2 SESCOSP input parameters
SESCOSP expects input parameters from SYSDTA.
6.2.1 The higher-level parameter CREATE-REPORT
Function
You use CREATE-REPORT to specify which request log file SESCOSP is to evaluate,
where SESCOSP is to write the report to, which data SESCOSP is to evaluate, and how
the SESCOSP statistics should look.
If you enter the name of the request log file (CO-LOG file) to be evaluated in the appropriate
SDF screen and send it off with the default settings, SESCOSP evaluates all the data and
writes I/O statistics for each statement (see page 357) to SYSLST.
All the operands of CREATE-REPORT are described below as individual parameters.
CREATE-REPORT
INPUT-FILE =
,OUTPUT =
,SELECT =
,REPORT-FORMAT =
Operands
INPUT-FILE =
See section “The individual parameter INPUT-FILE” on page 345.
OUTPUT =
See section “The individual parameter OUTPUT” on page 345.
SELECT =
See section “The individual parameter SELECT” on page 346.
REPORT-FORMAT =
See section “The individual parameter REPORT-FORMAT” on page 356.
344
U22418-J-Z125-6-76
SESCOSP
INPUT-FILE/OUTPUT
6.2.2 The individual parameter INPUT-FILE
Function
You use this parameter to specify the file name of the request log file that SESCOSP is to
evaluate.
INPUT-FILE
= <filename 1..54_without_generation_version>
Operands
INPUT-FILE = <filename 1..54_without_generation_version>
Name of the request log file (CO-LOG file) that SESCOSP is to evaluate. If necessary, see
the SET-TUNING-TRACE administration statement on page 296. Request logging must be
turned off for the file to be evaluated.
6.2.3 The individual parameter OUTPUT
Function
You use this parameter to specify whether SESCOSP is to write the edited data to SYSLST
or a file.
OUTPUT
= *SYSLST / <filename 1..54_without_generation_version>
Operands
OUTPUT = *SYSLST
Writes the report to SYSLST.
OUTPUT = <filename 1..54_without_generation_version>
Writes the report to the specified file. SYSLST is assigned to the specified file internally to
ensure that output is always directed to SYSLST. Following program execution, SYSLST is
reset to the primary assignment, even if SYSLST had an assignment beforehand.
U22418-J-Z125-6-76
345
SELECT
SESCOSP
6.2.4 The individual parameter SELECT
Function
You use this parameter to specify which data from the request log file is to be evaluated by
SESCOSP.
The type of evaluation depends not only on the parameters specified for SELECT but also
on whether statements or transactions are evaluated. You specify this by means of the
REPORT-FORMAT parameter PROTOCOL (see page 357). For each SELECT parameter,
the differences in the logging of statements and transactions are described below.
SELECT
= *ALL / *PARAMETERS(...)
*PARAMETERS(...)







CATALOG-NAMES =
,USERS =
,STATEMENTS =
,TIME =
,CPU-TIME =
,ELAPSED-TIME =
,NUMBER-OF-LOGICAL-IO =
Operands
SELECT = *ALL
SESCOSP evaluates all databases, all spaces, all tables and all statements. The report is
not limited to specific users or specific time periods.
SELECT = *PARAMETERS(...)
The options that allow you to limit the data to be collected are described below individually
as SELECT parameters.
346
U22418-J-Z125-6-76
SESCOSP
CATALOG-NAMES
The SELECT parameter CATALOG-NAMES
Function
You use this parameter to specify the databases to be evaluated. For each database, the
report can be limited to individual schemata, tables and spaces.
A statement is logged when the specified database is accessed, or when selected
schemata, tables or spaces are accessed.
A statement may also evaluated when a table is not accessed. An example of this is the end
statement of a transaction.
A transaction is logged when at least one statement of the transaction accesses the
specified database or selected schemata, tables or spaces.
Note that the selection of individual schemata, tables or spaces affects:
–
what is output in the STEP-IO-STATISTICS and STEP-COMPLEXITY lists
–
the statistical resource data in the output lines and the termination statistics, in
particular the selected logged resource consumption and
the checking of the conditions specified for the SELECT parameters CPU-TIME and
NUMBER-OF-LOGICAL-IO.
CATALOG-NAMES
= *ALL / list(10): <filename 1..18 without-all>(...)
<filename 1..18-without-all>(...)




SCHEMA-NAMES = *ALL / list(10): <c-string 1..31>(...)
<c-string 1..31> (...)

TABLE-NAMES = *ALL / list(10): <text 1..31> / <c-string 1..31>
SPACE-NAMES = *ALL / list(10):<filename 1..18 without-all>
Operands
CATALOG-NAMES = *ALL
All databases are to be evaluated. Specifying *ALL does not have the same effect as specifying all databases individually because internal tables are also evaluated.
U22418-J-Z125-6-76
347
CATALOG-NAMES
SESCOSP
CATALOG-NAMES = list(10): <filename 1..18 without-all>(...)
You specify up to ten databases that are to be evaluated. The databases are identified by
their physical database names (see the DBH start statement ADD-SQL-DATABASECATALOG-LIST on page 76).
<filename 1..18-without-all>(...)
SCHEMA-NAMES = *ALL
All this database's schemas are to be evaluated.
SCHEMA-NAMES = list(10): <c-string 1..31> (...)
You specify up to ten of this database's schemas that are to be evaluated.
<c-string 1..31> (...)
TABLE-NAMES = *ALL
All tables of this schema are to be evaluated.
TABLE-NAMES = list(10): <text 1..31> / <c-string 1..31>
You specify up to ten of this schema's tables that are to be evaluated.
SPACE-NAMES = *ALL
All this database's spaces are to be evaluated.
SPACE-NAMES = list(10): <filename 1..18 without-all>
You specify up to ten of this database's spaces that are to be evaluated.
Example
The following input file for SESCOSP creates a report relating only to the data of the
HEI database and the DC_SCHEMA schema.
//
//
//
//
//
//
//
//
//
//
//
//
//
//
//
348
CREATE-REPORT INPUT-FILE
= CO-LOG.BAR, OUTPUT
= *SYSLST, SELECT
= *PARAMETERS ( CATALOG-NAMES
= HEI ( SCHEMA-NAMES
= ´DC_SCHEMA´ ( TABLE-NAMES
= *ALL ), SPACE-NAMES
= *ALL ), USERS
= *ALL, STATEMENTS
= *ALL, TIME
= *ALL, CPU-TIME
= *ALL, ELAPSED-TIME
= *ALL, NUMBER-OF-LOGICAL-IO = *ALL ),REPORT-FORMAT
= *STD
U22418-J-Z125-6-76
SESCOSP
USERS
The SELECT parameter USERS
Function
You use this parameter to specify the timesharing and application users to be evaluated.
Please note that you can restrict logging to individual users by means of the USERSELECT parameter of the SET-TUNING-TRACE administration statement (see
page 296). Only from these users can you make a selection for evaluation in
SESCOSP by means of the USERS parameter.
i
USERS
= *ALL / *BY-SELECT(...)
*BY-SELECT(...)





HOST-NAME = *NONE / <text 1..8>
,APPLICATION-NAME = *NONE / *TSN (TSN=<alphanum-name 4..4>) / <text 1..8>
,CUSTOMER-NAME = *NONE / <text 1..8>
,CONVERSATION-ID = *NONE / <x-string 1..8> / <alphanum-name 1..8>
,TAC = *NONE / <alphanum-name 1..8>
Operands
USERS = *ALL
All timesharing and application users are evaluated.
USERS = *BY-SELECT(...)
Only specific timesharing and application users are evaluated. You must specify a value
other than *NONE for at least one operand.
HOST-NAME =
The data to be evaluated is selected by specifying a host system.
HOST-NAME = *NONE
The data to be evaluated is not limited to that on a specific host system.
HOST-NAME = <text 1..8>
Only the data of the specified host system is evaluated. The host system is identified by
its symbolic host name. In nondistributed processing, HOMEPROC always identifies
the local system.
U22418-J-Z125-6-76
349
USERS
SESCOSP
APPLICATION-NAME =
The data to be evaluated is selected by specifying an application.
APPLICATION-NAME = *NONE
The data to be evaluated is not limited to that of a specific application.
APPLICATION-NAME = *TSN (TSN=<alphanum-name 4..4>)
In TIAM mode you select the application by specifying the task sequence number
(TSN).
APPLICATION-NAME = <text 1..8>
In UTM mode you select the application by specifying the UTM application name, in
DCAM mode by specifying the DCAM application name.
CUSTOMER-NAME =
The data to be evaluated is selected by specifying a user.
CUSTOMER-NAME = *NONE
The data to be evaluated is not limited to that of a specific user.
CUSTOMER-NAME = <text 1..8>
In UTM mode the user is specified by means of the KDCSIGN name, in TIAM and
DCAM modes by means of the program name.
CONVERSATION-ID =
The data to be evaluated is selected by specifying a UTM conversation.
CONVERSATION-ID = *NONE
The data to be evaluated is not limited to that of a specific UTM conversation.
CONVERSATION-ID =<x-string> / <alphanum-name 1..8>
The UTM conversation is identified by the UTM conversation number.
TAC =
The data to be evaluated is selected by means of the UTM transaction code, the DCAM
user name or the BS2000 user ID.
TAC = *NONE
No selection by means of the UTM transaction code, the DCAM user name or the
BS2000 user ID
TAC = <alphanum-name 1..8>
In UTM mode, the transaction code is specified here, in DCAM mode the DCAM user
name, and in TIAM mode the BS2000 user ID.
350
U22418-J-Z125-6-76
SESCOSP
STATEMENTS
The SELECT parameter STATEMENTS
Function
You use this parameter to specify the statements to be evaluated.
If TRANSACTION is selected for the REPORT-FORMAT format, it is not possible to specify
TERMINAL-NUMBER and STATEMENT-NUMBER. If you try to do this, an error message
appears.
STATEMENTS
= *ALL / *PARAMETERS(...)
*PARAMETERS


TERMINAL-NUMBER = <x-string 1..4> / <integer..32767>
,STATEMENT-NUMBER = <x-string 1..4> / <integer..32767>
Operands
STATEMENTS = *ALL
All statements are evaluated.
STATEMENTS = *PARAMETERS(...)
TERMINAL-NUMBER = <x-string 1..4> / <integer..32767>
Only statements entered at the specified terminal are evaluated. You specify the
terminal by means of the SESAM/SQL internal terminal number (ITN). The ITN can be
obtained from SESCOSP reports.
STATEMENT-NUMBER = <x-string 1..4> / <integer..32767>
Only the specified statement is evaluated. You specify the statement by means of the
user-specific sequence number. The user-specific sequence number can be obtained
from SESCOSP reports.
U22418-J-Z125-6-76
351
TIME-PERIOD
SESCOSP
The SELECT parameter TIME-PERIOD
Function
You use this parameter to specify that SESCOSP is to evaluate only statements or transactions logged during a specific time period.
TIME-PERIOD
= *ALL / *INTERVAL(...)
*INTERVAL(...)






FROM = *PARAMETERS(...)


DATE = <date>
,TIME = <time>
,TO = *PARAMETERS(...)


DATE = <date>
,TIME = <time>
Operands
TIME-PERIOD = *ALL
The data to be evaluated is not limited to the statements or transactions of a specific time
period.
TIME-PERIOD = *INTERVAL(...)
Statements or transactions logged in the period from the start time to the end time are
evaluated. The start time must be before or equal to the end time.
A statement is logged when it is processed in full in the specified time period. A transaction
is selected when all the statements of the transaction lie within the limits of the time period.
FROM = *PARAMETERS(...)
DATE = <date>
Date of the start time, to be entered in the format yyyy-mm-dd
TIME = <time>
Start time, to be entered in the format hh:mm:ss
TO = *PARAMETERS(...)
DATE = <date>
Date of the end time, to be entered in the format yyyy-mm-dd
TIME = <time>
End time, to be entered in the format hh:mm:ss
352
U22418-J-Z125-6-76
SESCOSP
CPU-TIME
The SELECT parameter CPU-TIME
Function
You use this parameter to specify that SESCOSP is to evaluate only statements or transactions whose CPU time is within a specific period. You cannot select a CPU time period
unless the CPU time was recorded during logging (see the SET-TUNING-TRACE administration statement on page 296).
The CPU time of a transaction is obtained by adding up all the CPU times of the statements
involved in the transaction.
CPU-TIME
= *ALL / *INTERVAL(...)
*INTERVAL(...)


FROM = <integer 0..2147483647>
,TO = <integer 1..2147483647>
Operands
CPU-TIME = *ALL
The data to be evaluated is not limited to that logged during a specific CPU-time period.
CPU-TIME = *INTERVAL(...)
Statements and transactions are logged whose consumed CPU time lies between the CPU
time start value (FROM) and the CPU time end value (TO). The time specified for FROM
must be before or the same as that specified for TO.
FROM = <integer 0..2147483647>
CPU start time, to be entered in milliseconds or microseconds, depending on the setting
of the TIME-PRECISION parameter.
Default: 0
TO = <integer 1..2147483647>
CPU end time, to be entered in milliseconds or microseconds, depending on the setting
of the TIME-PRECISION parameter.
Default: 2147483647
U22418-J-Z125-6-76
353
ELAPSED-TIME
SESCOSP
The SELECT parameter ELAPSED-TIME
Function
You use this parameter to specify that SESCOSP is to evaluate only statements or transactions whose elapsed time is within a specific time period. Elapsed time is elapsed real time.
When transactions are evaluated, in addition to the elapsed times of the statements in the
DBH, the elapsed times for the user are also taken into consideration.
ELAPSED-TIME
= *ALL /*INTERVAL(...)
*INTERVAL(...)


FROM = <integer 0..2147483647>
,TO = <integer 1..2147483647>
Operands
ELAPSED-TIME = *ALL
The data to be evaluated is not limited by the elapsed time.
ELAPSED-TIME = *INTERVAL(...)
The elapsed time of the statements or transactions to be evaluated is between the times
specified for FROM and TO. The time specified for FROM must be before or the same as
that specified for TO.
FROM = <integer 0..2147483647>
Start time, to be entered in milliseconds or microseconds, depending on the setting of
the TIME-PRECISION parameter.
Default: 0
TO = <integer 1..2147483647>
End time, to be entered in milliseconds or microseconds, depending on the setting of
the TIME-PRECISION parameter.
Default: 2147483647
354
U22418-J-Z125-6-76
SESCOSP
NUMBER-OF-LOGICAL-IO
The SELECT parameter NUMBER-OF-LOGICAL-IO
Function
You use this parameter to specify that SESCOSP is to evaluate only statements whose
number of logical I/Os lies within a specified range.
The number of logical I/Os of a transaction is the sum of all the logical I/Os of the individual
statements involved in the transaction.
NUMBER-OF-LOGICAL-IO
= *ALL /*INTERVAL(...)
*INTERVAL(...)


FROM = <integer 0..2147483647>
,TO = <integer 0..2147483647>
Operands
NUMBER-OF-LOGICAL-IO = *ALL
The evaluation is limited on the basis of the number of logical I/Os.
NUMBER-OF-LOGICAL-IO = *INTERVAL(..)
Only statements or transactions whose number of logical I/Os lie within the specified range
are evaluated.
FROM = <integer 0..2147483647>
Minimum number of logical I/Os
Default: 0
TO = <integer 0..2147483647>
Maximum number of logical I/Os
Default: 2147483647
U22418-J-Z125-6-76
355
REPORT-FORMAT
SESCOSP
6.2.5 The individual parameter REPORT-FORMAT
Function
You use this parameter to specify the form in which the SESCOSP statistics are to appear.
REPORT-FORMAT
REPORT-FORMAT = *STD / *PARAMETERS(...)
*PARAMETERS(...)


PROTOCOL =
,TIME-PRECISION =
Operands
REPORT-FORMAT = *STD
The default settings apply to the type of statistics and the time precision. These defaults are
described below for each REPORT-FORMAT parameter.
REPORT-FORMAT = *PARAMETERS(...)
The options available for formatting the data for output are described individually below.
They are the REPORT-FORMAT parameters.
356
U22418-J-Z125-6-76
SESCOSP
PROTOCOL
The REPORT-FORMAT parameter PROTOCOL
Function
You use this parameter to specify the type of statistics to be output: statement or transaction
statistics. The format of the different reports is described in section “SESCOSP report
output” on page 359.
PROTOCOL
= *STATEMENT(...) / *TRANSACTION
*STATEMENT (...)


INFORMATION = *STRING-FORMAT / *IO-STATISTICS / *STEP-IO-STATISTICS /
*STEP-COMPLEXITY
*TRANSACTION
Operands
PROTOCOL = *STATEMENT(...)
Information is output relating to statements or statement steps.
INFORMATION = *STRING-FORMAT
The statements are output in printable form.
See page 361 for the structure of the report.
INFORMATION = *IO-STATISTICS
A set of I/O statistics is output for each statement.
See page 367 for the structure of the report.
INFORMATION = *STEP-IO-STATISTICS
A set of I/O statistics is output for each statement step.
See page 369 for the structure of the report.
INFORMATION = *STEP-COMPLEXITY
A set of resource statistics (complexity) is output for each statement step.
See page 371 for the structure of the report.
PROTOCOL = *TRANSACTION
A set of statistics is output relating to transactions.
See page 373 for the structure of the report.
U22418-J-Z125-6-76
357
TIME-PRECISION
SESCOSP
Example
The following input file for SESCOSP generates a set of resource statistics for each
statement step.
//
//
//
//
//
//
//
CREATE-REPORT INPUT-FILE
= CO-LOG.BAR, OUTPUT
= *SYSLST, SELECT
= *ALL, REPORT-FORMAT
= *PARAMETERS ( PROTOCOL
= *STATEMENT ( INFORMATION
= *STEP-COMPLEXITY))
The REPORT-FORMAT parameter TIME-PRECISION
Function
You use this parameter to specify whether time is to be specified in milliseconds or microseconds.
TIME-PRECISION
= *STD / *PARAMETERS(...)
*PARAMETERS(...)


CPU-TIME = *MILLI-SECONDS / MICRO-SECONDS
,ELAPSED-TIME = *MILLI-SECONDS / MICRO-SECONDS
Operands
TIME-PRECISION = *STD
The CPU time and elapsed time are output in milliseconds.
TIME-PRECISION = *PARAMETERS(...)
CPU-TIME = *MILLI-SECONDS / MICRO-SECONDS
The CPU time is output in milliseconds or microseconds.
ELAPSED-TIME = *MILLI-SECONDS / MICRO-SECONDS
The elapsed real time is output in milliseconds or microseconds.
358
U22418-J-Z125-6-76
SESCOSP
Report output
6.3 SESCOSP report output
Each report output by SESCOSP has the following basic structure:
1. SESCOSP input parameters
System type
Operating-system version of the DBH user ID
DBH options
2. Variable part of the report in accordance with the REPORT-FORMAT parameter
PROTOCOL
–
output of statements
–
output of input/output statistics per statement
–
output of input/output statistics per statement step
–
output of resource statistics per statement step (complexity)
–
output of transaction statistics.
3. Termination statistics
Time period involved
4. Catalog-space table assignment table
U22418-J-Z125-6-76
359
Report output
SESCOSP
6.3.1 Output of general information and the DBH options
The output of the SESCOSP input parameters, the system type, the operating system version of the DBH user ID and the DBH options is structured in the same way in all reports.
Example
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112
//
CREATE-REPORT INPUT-FILE = SESAM.CO-LOG, OUTPUT = SESAM.COSP.OUT.TA.ALL, SELECT
= *PARAMETERS( CATALOG-NAMES=*ALL ,USERS=*ALL ,STATEMENTS=*ALL ,
TIME-PERIOD=*ALL ,CPU-TIME=*ALL ,ELAPSED-TIME=*ALL ,
NUMBER-OF-LOGICAL-IO=*ALL ), REPORT-FORMAT = *PARAMETERS ( PROTOCOL =
*TRANSACTION, TIME-PRECISION=*PARAMETERS(CPU-TIME=*MICRO-SECONDS ,
ELAPSED-TIME=*MILLI-SECONDS ))
Anlagentyp:
09:58:59
2003-05-23
PAGE
1
7.500- S130-K
BS2000-Version: V140
ACCOUNTING
ADMINISTRATOR
COLUMNS
CURSOR-BUFFER
DBH-IDENTIFICATION
.
.
360
*OFF
*ANY
1024
BUFFER-SIZE=1408 , FRAME-SIZE=4
CONFIGURATION-NAME=Z, DBH-NAME=X
U22418-J-Z125-6-76
SESCOSP
Output of statements
6.3.2 Variable parts of the report
The variable parts of the report are described below in accordance with the REPORTFORMAT parameter PROTOCOL.
i
If an integer value is too large for an output field, the value is output as a floatingpoint number. In this case, a certain amount of precision is lost.
Output of statements
PROTOCOL=*STATEMENT(INFORMATION=*STRING-FORMAT)
SESCOSP provides the following information for each statement.
Heading
Contents
LFD
Internal record number by means of which the lines belonging to different
SESCOSP reports can be assigned
DATE
Date (yyyy-mm-dd) on which the request was accepted
TIME
Time (hh:mm:ss) at which the request was accepted
HOST
In distributed processing, the host name;
in nondistributed processing, this is always HOMEPROC
APPL/TSN
UTM or DCAM application name;
in TIAM mode, the task sequence number TSN = tsn
USER/PRG
KDCSIGN name in UTM mode or DCAM or TIAM program name; where applicable, LOGON name
CONV-ID
Conversation ID
In UTM mode: the UTM conversation number (specified in hexadecimal format)
TAC/U-ID
UTM transaction code or
BS2000 user ID in TIAM mode or
DCAM user name
ITN
SESAM/SQL internal terminal number (specified in hexadecimal format)
ST-ID
Number of the statement. Forms with the ITN the unique identification of a
statement (specified in hexadecimal format).
STM
Short ID of the SQL statement or SQL statement group, or CALL DML operation
code
DCL: DECLARE CURSOR
SEL: SELECT
OPC: OPEN CURSOR
FET: FETCH
STC: STORE CURSOR
RST: RESTORE CURSOR
Table 30: The STRING-FORMAT report
U22418-J-Z125-6-76
(part 1 of 3)
361
Output of statements
SESCOSP
Heading
Contents
STM
CLC: CLOSE CURSOR
SEL: SELECT
INS: INSERT
UPD: UPDATE
DEL: DELETE
CTA: COMMIT TRANSACTION
RTA: ROLLBACK TRANSACTION
PTC: prepare to commit
DDL: DDL statement
UTI: utility statement
PRP: dynamic statement
SQL: other SQL statement
CALL DML operation code
01: administration
1: cursor-file handling
2: open
3: attribute information
4: record output
5: query
6: search
7/6: sequential search call
7/9: sequential update call
8: close
9: update (add, modify, delete)
90B: begin transaction
90R: roll back transaction
90C: end of transaction
90P: prepare to commit
CPU-UNITS
CPU time used by the statement in milliseconds or microseconds
BruttoEI
Elapsed time of the statement in the DBH (without the connection module)
PhysIO
Number of physical read and write accesses
In CALL DML:
Instruction
Statement in printable form
(for CO-LOG files with standard logging max. 500 bytes)
Acknowledgement
Acknowledgment in dump format
Query area
Values in dump format
(for CO-LOG files with standard logging max. 1000 bytes)
Answer area
Values in dump format
(for CO-LOG files with standard logging max. 1000 bytes)
Table 30: The STRING-FORMAT report
362
(part 2 of 3)
U22418-J-Z125-6-76
SESCOSP
Output of statements
Heading
Contents
In SQL:
ICSQL-Params
ICSQL parameters in printable format
(for CO-LOG files with standard logging max. 500 bytes)
SQL-String
SQL string in printable format
(for CO-LOG files with standard logging max. 29696 bytes)
In-Descriptors
Input descriptors in printable format
(only for CO-LOG files with LONG logging).
The information on length, type, column name and value is output for each entry.
Diagnostic
Diagnostic area in printable format
(for CO-LOG files with standard logging max. 500 byte)
Output
Values in printable format
(only for CO-LOG files with LONG logging).
The information on length, type, column name and value is output for each entry.
When the block mode (FETCH) is used, the information for all the records
supplied is output in succession, the values (results) playing an essential role
here.
In the case of multiple fields the coefficient precedes the values.
Table 30: The STRING-FORMAT report
(part 3 of 3)
The extent of logging of CO-LOG files is set in the administration statement SET-TUNINGTRACE by means of the operand PROTOCOL=*STD/*LONG, see page 297.
U22418-J-Z125-6-76
363
Output of statements
SESCOSP
Example 1: (normal case, in-descriptors and output)
1. PREPARE statement with SQL string
SESCOSP/SQL VERS. 3.2A00
TSN:4IYB ID.:SQLDB112 *** STRING-FORMAT ***
10:14:30
2003-05-22 PAGE
1
LFD
DATE
TIME
HOST APPL/TSN USER/PRG CONV-ID TAC/U-ID ITN STID STM CPUUnits BruttoEl PhysIO
***********************************************************************************************************************************
0017 2003-04-03 11:38:50 D016ZE09 TSN=94E7 UDML202 00000000 XDL1LOE 0002 0017 PRP
0
15
0
ICSQL-Params:
ICSQL-Version = X'02', ICSQL-Type = 'PRE', User-Authorization-ID = 'D0USER', Consistency-Level = X'03', TA-A
ccess-Mode = X'02', Current-Catalog-Name = 'STANCAT4', Is-Static-Statement = FALSE, Statement-Class = X'0205
', Statement-ID = 'SQLENTRQ.ST1'
SQL-String:
--%PRAGMA DIALECT FULL --%PRAGMA CATALOG "STANCAT4"--%PRAGMA SCHEMA "SCHEMA_0001"--%PRAGMA MODULE "SQLENT
RQ"--%PRAGMA PREFETCH 20
SELECT T1.COLUMN_0001, T1.COLUMN_0003, T2.COLUMN_0017
FROM TABLE_0001 T1, TABLE_0001 T2 /* self join */ WHERE T1.COLUMN_0001 > ? AND T2.COLUMN_0002 > ? AN
D CAST( SUBSTRING(T1.COLUMN_0011 FROM 1 FOR 3000) AS VARCHAR(3000)) = CAST( SUBSTRING(T2.COLUMN_0011 FROM
1 FOR 3000) AS VARCHAR(3000)) ORDER BY CAST( SUBSTRING(T1.COLUMN_0017 FROM 1 FOR 3000) AS VARCHAR(3000)
) ASC
Diagnostic:
SQL-State = '00000'
Output:
ITEM
1: TYPE = CHAR(50)
NAME = COLUMN_0001
<UNKNOWN>
ITEM
2: TYPE = CHAR(50)
NAME = COLUMN_0003
<UNKNOWN>
ITEM
3: TYPE = VARCHAR(16000)
NAME = COLUMN_0017
<UNKNOWN>
***********************************************************************************************************************************
2. SQL statement OPEN CURSOR
SESCOSP/SQL VERS. 3.2A00
TSN:4IYB ID.:SQLDB112 *** STRING-FORMAT ***
10:14:30
2003-05-22 PAGE
1
LFD
DATE
TIME
HOST APPL/TSN USER/PRG CONV-ID TAC/U-ID ITN STID STM CPUUnits BruttoEl PhysIO
***********************************************************************************************************************************
0018 2003-04-03 11:38:50 D016ZE09 TSN=94E7 UDML202 00000000 XDL1LOE 0002 0018 OPC
0
2537
31
ICSQL-Params:
ICSQL-Version = X'02', ICSQL-Type = 'OPN', User-Authorization-ID = 'D0USER', Consistency-Level = X'03', TA-A
ccess-Mode = X'02', Current-Catalog-Name = 'STANCAT4', Is-Static-Statement = FALSE, Statement-Class = X'010B
', Statement-ID = 'SQLENTRQ.ST1', Cursor-ID = 'SQLENTRQ.CU03', Is-Scroll-Cursor = FALSE
In-Descriptors: ITEM
1: TYPE = CHAR(20)
BBB
ITEM
2: TYPE = DECIMAL(10,2)
+00000001.11
Diagnostic:
SQL-State = '00000'
***********************************************************************************************************************************
3. SQL FETCH statement with result values
SESCOSP/SQL VERS. 3.2A00
TSN:4IYB ID.:SQLDB112 *** STRING-FORMAT ***
10:14:30
2003-05-22 PAGE
1
LFD
DATE
TIME
HOST APPL/TSN USER/PRG CONV-ID TAC/U-ID ITN STID STM CPUUnits BruttoEl PhysIO
***********************************************************************************************************************************
0019 2003-04-03 11:38:53 D016ZE09 TSN=94E7 UDML202 00000000 XDL1LOE 0002 0019 FET
0
3
1
ICSQL-Params:
ICSQL-Version = X'02', ICSQL-Type = 'FCH', User-Authorization-ID = 'D0USER', Consistency-Level = X'03', TA-A
ccess-Mode = X'02', Current-Catalog-Name = 'STANCAT4', Is-Static-Statement = FALSE, Statement-Class = X'010A
', Statement-ID = 'SQLENTRQ.ST1', Cursor-ID = 'SQLENTRQ.CU03', Fetch-Orientation = X'0000000000000000'
Diagnostic:
SQL-State = '00000'
Output:
ITEM
1: TYPE = CHAR(50)
VOLLMF
ITEM
2: TYPE = CHAR(50)
AAAAkfdljhgslkdjfhglkdfhg
ITEM
3: TYPE = VARCHAR(16000)
THIS WILL BE A SEMI-LONG VCHAR
***********************************************************************************************************************************
364
U22418-J-Z125-6-76
SESCOSP
Output of statements
Example 2: BLOCK MODE (Output)
SQL FETCH statement with result values (PREPARE and FETCH as in the normal case)
***********************************************************************************************************************************
0012 2003-04-03 11:38:50 D016ZE09 TSN=94E7 UDML202 00000000 XDL1LOE 0002 0012 FET
0
3
0
ICSQL-Params:
ICSQL-Version = X'02', ICSQL-Type = 'FCH', User-Authorization-ID = 'D0USER', Consistency-Level = X'03', TA-A
ccess-Mode = X'02', Current-Catalog-Name = 'STANCAT4', Is-Static-Statement = FALSE, Statement-Class = X'010A
', Statement-ID = 'SQLENTRQ.ST1', Cursor-ID = 'SQLENTRQ.CU02', Fetch-Orientation = X'0000000000000000'
Diagnostic:
SQL-State = '00000'
Output:
ROW
1, SQL-STATE = 00000 ------------------------------------------------------------------------------ITEM
1: TYPE = CHAR(50)
AAAAkfdljhgslkdjfhglkdfhg
ITEM
2: TYPE = CHAR(50)
AAAAkfdljhgslkdjfhglkdfhg
ITEM
3: TYPE = VARCHAR(16000)
THIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEM
I-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS W
ILL BE A SEMI-LONG VCHARTHIS WILL BE A S
ROW
2, SQL-STATE = 00000 ------------------------------------------------------------------------------ITEM
1: TYPE = CHAR(50)
BBBAkfdljhgslkdjfhglkdfhg
ITEM
2: TYPE = CHAR(50)
AAAAkfdljhgslkdjfhglkdfhg
ITEM
3: TYPE = VARCHAR(16000)
THIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEM
I-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS W
ILL BE A SEMI-LONG VCHARTHIS WILL BE A S
ROW
3, SQL-STATE = 00000 ------------------------------------------------------------------------------ITEM
1: TYPE = CHAR(50)
CCCAkfdljhgslkdjfhglkdfhg
ITEM
2: TYPE = CHAR(50)
AAAAkfdljhgslkdjfhglkdfhg
ITEM
3: TYPE = VARCHAR(16000)
THIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEM
I-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS W
ILL BE A SEMI-LONG VCHARTHIS WILL BE A S
ROW
4, SQL-STATE = 00000 ------------------------------------------------------------------------------ITEM
1: TYPE = CHAR(50)
DDDAkfdljhgslkdjfhglkdfhg
ITEM
2: TYPE = CHAR(50)
AAAAkfdljhgslkdjfhglkdfhg
ITEM
3: TYPE = VARCHAR(16000)
THIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEM
I-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS WILL BE A SEMI-LONG VCHARTHIS W
ILL BE A SEMI-LONG VCHARTHIS WILL BE A S
***********************************************************************************************************************************
U22418-J-Z125-6-76
365
Output of statements
SESCOSP
Example 3: Output of values of multiple fields (Output)
SQL FETCH statement with result values (PREPARE and FETCH as in the normal case)
***********************************************************************************************************************************
0061 2003-04-03 11:38:54 D016ZE09 TSN=94E7 UDML202 00000000 XDL1LOE 0002 0061 FET
0
9
0
ICSQL-Params:
ICSQL-Version = X'02', ICSQL-Type = 'FCH', User-Authorization-ID = 'D0USER', Consistency-Level = X'03', TA-A
ccess-Mode = X'02', Current-Catalog-Name = 'STANCAT4', Is-Static-Statement = FALSE, Statement-Class = X'010A
', Statement-ID = 'SQLENTRQ.ST1', Cursor-ID = 'SQLENTRQ.CU07', Fetch-Orientation = X'0000000000000000'
Diagnostic:
SQL-State = '00000'
Output:
ITEM
1: TYPE = CHAR(256)
1 AAAAAAAAAABBBBBBBBBB1CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
2 AAAAAAAAAABBBBBBBBBB2CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
3 AAAAAAAAAABBBBBBBBBB3CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
4 AAAAAAAAAABBBBBBBBBB4CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
5 AAAAAAAAAABBBBBBBBBB5CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
6 AAAAAAAAAABBBBBBBBBB6CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
7 AAAAAAAAAABBBBBBBBBB7CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
8 AAAAAAAAAABBBBBBBBBB8CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
9 AAAAAAAAAABBBBBBBBBB9CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
10 AAAAAAAAAABBBBBBBBBB0CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
11 AAAAAAAAAABBBBBBBBBB1CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
12 AAAAAAAAAABBBBBBBBBB2CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
197 AAAAAAAAAABBBBBBBBBB7CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
198 AAAAAAAAAABBBBBBBBBB8CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
199 AAAAAAAAAABBBBBBBBBB9CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
200 AAAAAAAAAABBBBBBBBBB0CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
ITEM
2: TYPE = CHAR(256)
1 AAAAAAAAAABBBBBBBBBB1CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
2 AAAAAAAAAABBBBBBBBBB2CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
3 AAAAAAAAAABBBBBBBBBB3CCCCCCCCCDDDDDDDDDDEEEEEEEEEEAAAAAAAAAABBBBBBBBBBCCCCCCCCCCDDDDDDDDDDEEEEEEEEEE
***********************************************************************************************************************************
366
U22418-J-Z125-6-76
SESCOSP
I/O statistics for each statement
Output of I/O statistics for each statement
PROTOCOL=*STATEMENT(INFORMATION=*IO-STATISTICS)
SESCOSP provides the following information for each statement:
Heading
Contents
LFD
See the “The STRING-FORMAT report” on page 361
DATE
TIME
APPL/TSN
TAC/U-ID
ITN
STID
DB#
Internal database number by means of which the database name can be obtained via
the catalog-space table assignment table (see page 376)
(specified in hexadecimal format)
C-ID
In SQL: number of the statement that declared the cursor, if the evaluated statement
refers to a cursor
In CALL DML: logical file identifier
STM
See the “The STRING-FORMAT report” on page 361
CPUUNITS
BruttoEI
NettoEI
Activity time of the statement; i.e. the sum of the active time of the user and the active
time of all subfunctions (=statement steps)
PhDBIO
Number of physical read and write accesses of the database
LgDBIO
Number of logical read and write accesses of the database
PhCuIO
Number of physical read and write accesses of cursor files
LgCuIO
Number of logical read and write accesses of cursor files
Table 31: The IO-STATISTICS report
U22418-J-Z125-6-76
367
I/O statistics for each statement
SESCOSP
Example
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112
10:57:46
2003-05-23 PAGE
//
CREATE-REPORT INPUT-FILE = SESAM.CO-LOG, OUTPUT = SESAM.COSP.OUT.IOSTAT, SELECT
= *ALL, REPORT-FORMAT = *PARAMETERS ( PROTOCOL = *STATEMENT ( INFORMATION =
*IO-STATISTICS ), TIME-PRECISION=*PARAMETERS(CPU-TIME=*MICRO-SECONDS ,
ELAPSED-TIME=*MICRO-SECONDS ))
.
.
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112 *** IO-STATISTICS ***
10:57:46
2003-06-23 PAGE
LFD
DATE
TIME APPL/TSN TAC/U-ID ITN STID DBC# C-ID STM CPUUnits BruttoEl NettoEl PhDBIO LgDBIO PhCuIO LgCuIO
0079 2003-02-06 13:51:10 TSN=1A2Z DBSRE
0004 0283 0000 A2 90C
429
2808
426
0
0
0
0
007B 2003-02-06 13:51:10 TSN=1A24 DBSRE
0011 0C14 0001 A1 6
1874
11899
11899
0
4
0
0
007C 2003-02-06 13:51:10 TSN=1A2Y DBSRE
0001 13A5 0001 A1 6
1700
2581
2581
0
6
0
0
007E 2003-02-06 13:51:10 TSN=1A4G XDL1DBT3 0015 0026 0003 0026 SEL
4616
10771
10771
0
2
0
0
0080 2003-02-06 13:51:10 TSN=1A4M XDL1DBT3 000B 0043 0003 0041 CLC
2802
13086
13086
0
0
0
0
0081 2003-02-06 13:51:10 TSN=1A4P XDL1DBT3 000C 0025 0003 0025 SEL
4191
4531
4531
0
2
0
0
0082 2003-02-06 13:51:10 TSN=1A4H XDL1DBT3 0005 0034 0002 0034 SEL
3454
3662
3662
0
2
0
0
007A 2003-02-06 13:51:10 TSN=1A25 DBSRE
0009 0BFB 0001 A1 90B
2129
85790
12139
0
7
0
0
007F 2003-02-06 13:51:10 TSN=1A22 DBSRE
001C 0851 0001 A1 6
1698
67756
67756
0
5
0
0
0083 2003-02-06 13:51:10 TSN=1A23 DBSRE
0002 0A96 0001 A2 90B
1187
1193
1193
0
4
0
1
0084 2003-02-06 13:51:10 TSN=1A24 DBSRE
0016 0866 0001 A2 90B
2180
11168
11168
0
4
0
1
0085 2003-02-06 13:51:10 TSN=1A22 DBSRE
0017 06D7 0000 A4 90C
355
357
357
0
0
0
0
0086 2003-02-06 13:51:10 TSN=1A23 DBSRE
000D 0CB5 0001 A1 6
1610
1611
1611
0
6
0
0
0087 2003-02-06 13:51:10 TSN=1A25 DBSRE
000E 0884 0001 A2 90B
2100
2188
2188
0
4
0
1
008A 2003-02-06 13:51:10 TSN=1A4G XDL1DBT3 0015 0027 0003 0027 SEL
5105
10402
10402
0
2
0
0
008C 2003-02-06 13:51:10 TSN=1A4M XDL1DBT3 000B 0044 0000
CTA
421
425
425
0
0
0
0
008D 2003-02-06 13:51:10 TSN=1A24 DBSRE
0011 0C15 0001 A1 6
1910
4149
4149
0
7
0
0
0089 2003-02-06 13:51:10 TSN=1A4N XDL1DBT3 001B 002D 0002 002D OPC
10817
63424
31374
1
5
0
6
008E 2003-02-06 13:51:10 TSN=1A25 DBSRE
0009 0BFC 0001 A1 6
1741
7107
7107
0
4
0
0
008B 2003-02-06 13:51:10 TSN=1A4H XDL1DBT3 0005 0035 0001 0035 SEL
5775
42389
25097
0
2
0
0
.
.
368
1
3
U22418-J-Z125-6-76
SESCOSP
I/O statistics for each statement step
Output of I/O statistics for each statement step
PROTOCOL=*STATEMENT(INFORMATION=*STEP-IO-STATISTICS)
SESCOSP provides this information for each statement step (see the SUB subfunction) and
each SQL table.
Heading
Contents
LFD
See “The STRING-FORMAT report” on page 361
ITN
STID
DB#
See “The IO-STATISTICS report” on page 367
S#
Database-internal space number. See the assignment table on page 376
(specified in hexadecimal format)
TB#
Space-internal table number. See the assignment table on page 376
(specified in hexadecimal format)
C-ID
See “The IO-STATISTICS report” on page 367
SUB
Subfunction (statement step)
PRIO: statement start (request acceptance)
OPT: optimizer
INT: interpreter
BTSC: base-table-scan
TTSC: temp-table-scan
UPSC: update-scan
STM
See “The STRING-FORMAT report” on page 361
CPUUNITS
CPU time used for the statement step, in milliseconds or microseconds
BruttoEI
Elapsed time of the statement step in the DBH
NettoEI
Activity time of the statement step
PhACIO
Number of physical read and write accesses of the access data
LgACIO
Number of logical read and write accesses of the access data
PhDAIO
Number of physical read and write accesses of the primary data
LgDAIO
Number of logical read and write accesses of the primary data
PhCuIO
Number of physical read and write accesses of the cursor files
LgCuIO
Number of logical read and write accesses of the cursor files
Table 32: The STEP-IO-STATISTICS report
U22418-J-Z125-6-76
369
I/O statistics for each statement step
SESCOSP
Example
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112
11:01:02
2003-05-23 PAGE
1
//
CREATE-REPORT INPUT-FILE = SESAM.CO-LOG, OUTPUT = SESAM.COSP.OUT.STEPIO, SELECT
= *ALL, REPORT-FORMAT = *PARAMETERS ( PROTOCOL = *STATEMENT ( INFORMATION =
*STEP-IO-STATISTICS ), TIME-PRECISION=*PARAMETERS(CPU-TIME=*MICRO-SECONDS ,
ELAPSED-TIME=*MILLI-SECONDS ))
.
.
SESCOSP/SQL VERS. 3.2A00
LFD ITN STID DBC# S# TB#
0203 0005 0045 0001
0001 02 0002
0205 001B 0047 0001
0001 02 0002
0205 001B 0047 0001
0205 001B 0047 0001
0001 02 0002
0206 0026 00B8 0000
0206 0026 00B8 0000
0207 001A 0014 0000
0170 0020 01AA 0001
0170 0020 01AA 0001
0001 02 0002
0209 000A 0050 0000
0201 0011 0C20 0001
0201 0011 0C20 0001
0001 02 0002
01D0 0024 0001 0001
0001 01 0005
01D0 0024 0001 0001
0000 00 0000
0001 01 0007
0001 01 000B
0001 01 000F
0001 01 0012
01D0 0024 0001 0001
0001 02 0002
020A 001B 0048 0001
020A 001B 0048 0001
020A 001B 0048 0001
0001 02 0002
.
.
370
TSN:9H16 ID.:SQLDB112 *** STEP-IO-STATISTICS ***
C-ID SUB STM CPUUnits BruttoEl NettoEl PhACIO LgACIO PhDAIO
0045 INT SEL
1132
2
2
0
0
0
BTSC
1607
2
2
0
1
0
0047 PRIO OPC
791
10
10
0
0
0
BTSC
1761
3
3
0
0
0
0047 OPT OPC
180
0
0
0
0
0
0047 INT OPC
470
1
1
0
0
0
BTSC
5943
23
23
0
2
0
AA PRIO 90C
352
1
1
0
0
0
AA INT 90C
368
1
1
0
0
0
PRIO CTA
688
100
2
0
0
0
AD PRIO 6
333
2
2
0
0
0
AD INT 6
583
6
6
0
0
0
BTSC
2907
3722
16
0
7
0
PRIO CTA
340
0
0
0
0
0
A1 PRIO 6
257
0
0
0
0
0
A1 INT 6
312
0
0
0
0
0
BTSC
1412
182
166
0
4
0
0001 PRIO SQL
1476
2
2
0
0
0
BTSC
4435
33
33
0
3
0
0001 OPT SQL 118578
939
786
0
0
0
BTSC
547
1
1
0
0
0
BTSC
1629
33
33
0
1
0
BTSC
2284
16
3
0
2
0
BTSC
1420
2
2
0
4
0
BTSC
50593
459
185
0
2
0
0001 INT SQL
1080
1
1
0
0
0
BTSC
1262
10
10
0
1
0
0047 PRIO FET
497
3
3
0
0
0
0047 OPT FET
2305
15
15
0
0
0
0047 INT FET
606
1
1
0
0
0
BTSC
277
0
0
0
0
0
11:01:04
2003-05-23
LgDAIO PhCuIO LgCuIO
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
6
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
1
0
0
1
0
8
1
0
0
12
3
347
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
2
PAGE
25
U22418-J-Z125-6-76
SESCOSP
Resource statistics for each statement step
Output of resource statistics for each statement step (complexity)
PROTOCOL=*STATEMENT(INFORMATION=*STEP-COMPLEXITY)
SESCOSP provides the following information for each statement step (see the SUB
subfunction) and each SQL table.
Heading
Contents
LFD
See “The STRING-FORMAT report” on page 361
ITN
STID
DB#
See “The IO-STATISTICS report” on page 367
S#
See “The STEP-IO-STATISTICS report” on page 369
TB#
C-ID
See “The IO-STATISTICS report” on page 367
SUB
See “The STEP-IO-STATISTICS report” on page 369
STM
See “The STRING-FORMAT report” on page 361
CPUUNITS
See “The STEP-IO-STATISTICS report” on page 369
BruttoEI
NettoEI
#SI
Number of indexes to be evaluated
#Att
Number of columns (attributes) to be projected
#Pra
Number of predicates to be checked
#Dea
Number of deactivations
#Cal
Number of kernel calls
Table 33: The STEP-COMPLEXITY report
U22418-J-Z125-6-76
371
Resource statistics for each statement step
SESCOSP
Example
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112
13:16:00
//
CREATE-REPORT INPUT-FILE = SESAM.CO-LOG, OUTPUT = SESAM.COSP.OUT.STCOMP, SELECT
= *ALL, REPORT-FORMAT = *PARAMETERS ( PROTOCOL = *STATEMENT ( INFORMATION =
*STEP-COMPLEXITY ) )
.
.
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112 *** STEP-COMPLEXITY ***
13:16:04
LFD ITN STID DBC# S# TB# C-ID SUB STM CPUUnits BruttoEl NettoEl #SI #Att #Pra #Dea #Cal
0203 0005 0045 0001
0045 INT SEL
1
2
2
0
0001 02 0002
BTSC
2
2
2
0
28
0
0
3
0205 001B 0047 0001
0047 PRIO OPC
1
10
10
0
0001 02 0002
BTSC
2
3
3
0
30
1
0
1
0205 001B 0047 0001
0047 OPT OPC
0
0
0
0
0205 001B 0047 0001
0047 INT OPC
0
1
1
0
0001 02 0002
BTSC
6
23
23
0
30
1
0
1
0206 0026 00B8 0000
AA PRIO 90C
0
1
1
0
0206 0026 00B8 0000
AA INT 90C
0
1
1
0
0207 001A 0014 0000
PRIO CTA
1
100
2
0
0170 0020 01AA 0001
AD PRIO 6
0
2
2
0
0170 0020 01AA 0001
AD INT 6
1
6
6
0
0001 02 0002
BTSC
3
3722
16
1
2
1
1
1
0209 000A 0050 0000
PRIO CTA
0
0
0
0
0201 0011 0C20 0001
A1 PRIO 6
0
0
0
0
0201 0011 0C20 0001
A1 INT 6
0
0
0
0
0001 02 0002
BTSC
1
182
166
1
2
1
0
1
01D0 0024 0001 0001
0001 PRIO SQL
1
2
2
0
0001 01 0005
BTSC
4
33
33
0
0
0
0
3
01D0 0024 0001 0001
0001 OPT SQL
119
939
786
0
0000 00 0000
BTSC
1
1
1
0
0
0
0
1
0001 01 0007
BTSC
2
33
33
0
8
0
0
3
0001 01 000B
BTSC
2
16
3
0
3
3
0
4
0001 01 000F
BTSC
1
2
2
0
1
6
0
3
0001 01 0012
BTSC
51
459
185
0
11
3
1 170
01D0 0024 0001 0001
0001 INT SQL
1
1
1
0
0001 02 0002
BTSC
1
10
10
0
29
1
0
3
020A 001B 0048 0001
0047 PRIO FET
0
3
3
0
020A 001B 0048 0001
0047 OPT FET
2
15
15
0
020A 001B 0048 0001
0047 INT FET
1
1
1
0
0001 02 0002
BTSC
0
0
0
0
30
1
0
1
020B 001F 0267 0000
A0 PRIO 90C
0
0
0
0
020B 001F 0267 0000
A0 INT 90C
0
0
0
0
020E 0005 0046 0002
0046 PRIO SEL
0
0
0
0
020E 0005 0046 0002
0046 OPT SEL
2
10
10
0
020E 0005 0046 0002
0046 INT SEL
1
1
1
0
0002 02 0002
BTSC
1
2
2
0
28
0
0
3
020C 0015 003C 0003
003C PRIO SEL
1
1
1
0
020C 0015 003C 0003
003C OPT SEL
2
29
16
0
020C 0015 003C 0003
003C INT SEL
1
1
1
0
0003 04 0005
BTSC
1
3
1
0
28
0
0
3
020F 000D 0CC3 0001
A1 PRIO 90B
0
0
0
0
020F 000D 0CC3 0001
A1 INT 90B
0
0
0
0
0001 02 0002
BTSC
1
1
1
1
2
1
0
1
.
.
372
2003-05-23
PAGE
1
2003-05-23
PAGE
25
U22418-J-Z125-6-76
SESCOSP
Transaction statistics
Output of transaction statistics
PROTOCOL=*TRANSACTION
SESCOSP provides the following information for each transaction.
Heading
Contents
LFD
The sequential number of the transaction's last statement is logged
DATE
Start date (yyyy-mm-dd) of the transaction
TIME
Start time (hh:mm:ss) of the transaction
APPL/TSN
See “The STRING-FORMAT report” on page 361
USER/PRG
TAC/U-ID
ITN
STID
The number of the transaction's last statement is logged
CPUUNITS
Sum of the CPU time used by all of the transaction's statements in milliseconds or
microseconds
BruttoEl
Sum of the elapsed times of all of the transaction's statements in the DBH
(without connection module)
TransEl
Total time of the transaction, including communication times and the time taken by the
user to pause for thought
PhACIO
Sum of the physical read and write accesses to the access data of all of the transaction's statements
LgACIO
Sum of the logical read and write accesses to the access data of all of the transaction's statements
PhDAIO
Sum of the physical read and write accesses to the primary data of all of the transaction's statements
LgDAIO
Sum of the logical read and write accesses to the primary data of all of the transaction's statements
PhCuIO
Sum of the physical read and write accesses to the cursor files of all of the transaction's statements
LgCuIO
Sum of the logical read and write accesses to the cursor files of all of the transaction's
statements
Table 34: The TRANSACTION report
U22418-J-Z125-6-76
373
Transaction statistics
SESCOSP
Example
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112
09:58:59
2003-05-23 PAGE
1
//
CREATE-REPORT INPUT-FILE = SESAM.CO-LOG, OUTPUT = SESAM.COSP.OUT.TA.ALL, SELECT
= *PARAMETERS( CATALOG-NAMES=*ALL ,USERS=*ALL ,STATEMENTS=*ALL ,
TIME-PERIOD=*ALL ,CPU-TIME=*ALL ,ELAPSED-TIME=*ALL ,
NUMBER-OF-LOGICAL-IO=*ALL ), REPORT-FORMAT = *PARAMETERS ( PROTOCOL =
*TRANSACTION, TIME-PRECISION=*PARAMETERS(CPU-TIME=*MICRO-SECONDS ,
ELAPSED-TIME=*MILLI-SECONDS ))
.
.
SESCOSP/SQL VERS. 3.2A00
TSN:9H16 ID.:SQLDB112 *** TRANSACTION ***
09:59:00
2003-05-23 PAGE
2
LFD
DATE
TIME APPL/TSN USER/PRG TAC/U-ID ITN STID CPUUnits BruttoEl TransEl PhACIO LgACIO PhDAIO LgDAIO PhCuIO LgCuIO
00C9 2003-02-06 13:51:10 TSN=1A24 USER0001 DBSRE
0011 0C1A
4685
14
336
0
16
0
2
0
0
00CB 2003-02-06 13:51:11 TSN=1A24 USER0002 DBSRE
0016 086B
2006
10
124
0
4
0
0
0
1
00D2 2003-02-06 13:51:09 TSN=1A23 USER0001 DBSRE
000D 0CB6
5642
102
1684
0
14
0
2
0
0
00D6 2003-02-06 13:51:11 TSN=1A25 USER0002 DBSRE
000E 0887
2327
3
43
0
4
0
0
0
1
00D7 2003-02-06 13:51:11 TSN=1A2Z USER0002 DBSRE
0004 0287
2576
25
123
0
4
0
0
0
1
00E0 2003-02-06 13:51:11 TSN=1A2Z USER0018 DBSRE
0012 026D
2621
73
368
0
4
0
0
0
1
00E1 2003-02-06 13:51:11 TSN=1A23 USER0002 DBSRE
0002 0A99
2366
26
197
0
4
0
0
0
1
.
.
374
U22418-J-Z125-6-76
SESCOSP
Termination statistics
6.3.3 Structure of the termination statistics
Heading
Contents
Function
Function for which the values are added up. A function in this case is a CALL DML
operation code or an SQL statement (group). See “The STRING-FORMAT report” on
page 361 (field 10, STM).
# Auftr
Number of requests for this function
in %
Requests as a percentage of the total number of evaluated requests
Phys. I/O
Number of physical disk accesses
Log. I/O
Number of logical read and write accesses
L:P-AC
Number of logical read and write accesses for the physical read and write accesses
of the access data
L:P-DA
Number of logical read and write accesses for the physical read and write accesses
of the primary data
L:P-Cu
Number of logical read and write accesses for the physical read and write accesses
of the temporary data
Ig:Auf
Number of read and write accesses per request
CPUUnits
Total CPU time
Mitl-CPU
Average CPU requirements per request
WaitTime
Average wait time in the DBH of a job (the wait time in the DBH is equal to the
difference between the average net elapsed time and the average CPU time).
Mitl-Ela
Average gross elapsed time
Table 35: Termination statistics
Example
SESCOSP/SQL VERS. 3.2A00
Funktion
OPEN CURSOR
FETCH
STORE CURSOR
CLOSE CURSOR
SELECT
UPDATE
COMMIT WORK
OTHER SQL-STATEMENT
SUCHFRAGE
BEGIN TRANSACTION
COMMIT TRANSACTION
TSN:9H16 ID.:SQLDB112 *** SUMMARY ***
#Auftr in% Phys.I/O Log. I/O L:P-AC L:P-DA L:P-Cu Lg:Auf
40 2
1
293
0
56
0
7
40 2
0
58
0
0
0
1
9 0
0
0
0
0
0
0
31 1
0
0
0
0
0
0
164 10
13
368
202
13
0
2
8 0
4
188
0
12
0
23
169 10
0
0
0
0
0
0
11 0
8
864
0
26
128
78
249 15
0
1375
0
0
0
5
435 27
0
12323
0
0
0
28
435 27
0
0
0
0
0
0
09:59:06
2003-05-23 PAGE
CPUUnits Mitl-CPU WaitTime Mitl-Ela
259599
6489
17
47
138819
3470
10
25
19891
2210
0
10
74353
2398
4
22
890109
5427
52
84
67916
8489
44
124
69899
413
8
11
421031
38275
253
438
465313
1868
93
103
1262338
2901
41
59
226812
521
6
9
1
Time period captured: 2003-02-06 13:50:49 until 2003-02-06 13:51:54
U22418-J-Z125-6-76
375
Catalog-space table assignment table
SESCOSP
6.3.4 Structure of the catalog-space table assignment table
Value
Meaning
DB#
Internal database number
S#
Internal space number
TB#
Internal table number
DB-Name
Logical database name
Space-Name
Space name
CP-#
Copy number of the space
Schema-Name
Schema name
Table-Name
Table name
Table 36: Catalog-space table assignment table
Example
SESCOSP/SQL
DBC# S# TB#
0001 01 0005
0001 01 0007
0001 01 000B
0001 01 000F
0001 01 0012
0001 02 0002
0002 01 0005
0002 01 0007
0002 01 000B
0002 01 000F
0002 01 0012
0002 02 0002
0003 01 0005
0003 01 0007
0003 01 000B
0003 01 000F
0003 01 0012
0003 04 0002
376
VERS. 3.2A00
Catalog-Name
KON1CATALOG
KON1CATALOG
KON1CATALOG
KON1CATALOG
KON1CATALOG
KON1CATALOG
KON3CATALOG
KON3CATALOG
KON3CATALOG
KON3CATALOG
KON3CATALOG
KON3CATALOG
KON4CATALOG
KON4CATALOG
KON4CATALOG
KON4CATALOG
KON4CATALOG
KON4CATALOG
TSN:9H16 ID.:SQLDB112 *** Catalog-Space-Table-Assignment
09:59:06
Space-Name
CP-# Schema-Name
Table-Name
CATALOG
DEFINITION_SCHEMA
SYSTEM_ENTRIES
CATALOG
DEFINITION_SCHEMA
TABLES
CATALOG
DEFINITION_SCHEMA
UNIQUE_CONSTRAINTS
CATALOG
DEFINITION_SCHEMA
PRIVILEGES
CATALOG
DEFINITION_SCHEMA
INDEXES
SPACE0001
KON1GESAMT
KON1SDB0
CATALOG
DEFINITION_SCHEMA
SYSTEM_ENTRIES
CATALOG
DEFINITION_SCHEMA
TABLES
CATALOG
DEFINITION_SCHEMA
UNIQUE_CONSTRAINTS
CATALOG
DEFINITION_SCHEMA
PRIVILEGES
CATALOG
DEFINITION_SCHEMA
INDEXES
SPACE0001
KON3GESAMT
KON3SDB0
CATALOG
DEFINITION_SCHEMA
SYSTEM_ENTRIES
CATALOG
DEFINITION_SCHEMA
TABLES
CATALOG
DEFINITION_SCHEMA
UNIQUE_CONSTRAINTS
CATALOG
DEFINITION_SCHEMA
PRIVILEGES
CATALOG
DEFINITION_SCHEMA
INDEXES
SPACE0003
KON4NETZ
KON4SDB0
2003-05-23
PAGE
1
U22418-J-Z125-6-76
7 Outputting operational data with SESMON
The SESMON performance monitor collects system data on current database operation
and edits it on the basis of various statistical criteria.
The system administrator can see from the data obtained what effect the DBH and DCN
options have on the time behavior of the database system, the extent to which its resources
are utilized, and where bottlenecks could develop. From this, he/she can work out how to
set the database system to meet the requirements of the specific application.
The “Performance” manual provides assistance in analyzing performance problems and
indicates any measures that may have to be taken.
Access from the World Wide Web
From SESAM/SQL-Server V3.2 onwards you can access the administration program
SESADM, the performance monitor SESMON and the utility monitor SESUTI all from a
unified access on the World Wide Web (WWW or Web for short) with the aid of the software
product WebTransactions (WebTA).
To access the SESAM programs via the Web, you only need a standard browser in addition
to the software product WebTransactions.
Web access is described in the document “WebTA access for SESAM/SQL” shipped
together with SESAM/SQL-Server V3.2. This document is also available from the Fujitsu
Siemens manual server under the software product SESAM/SQL.
Output via SNMP to a management platform
From SESAM/SQL-Server V3.2 onwards you can use a SESAM subagent to transfer the
data from the performance monitor SESMON via SNMP to a management platform,
see page 451.
U22418-J-Z125-6-76
377
How SESMON works
SESMON
How SESMON works
The components shown in the figure below store data in the various pools. SESMON reads
data from the pools, edits it, and outputs it to forms, printed lists or files. SESMON
draws a distinction between SESDCN statistical output and DBH statistical output.
After SESMON is started interactively, you are requested to specify in a selection form
which statistical information you require. SESMON then displays the selected forms cyclically: the CONFIGURATION forms first, if requested, and then the selected SESDCN forms,
followed by the selected DBH forms for each DBH.
SESMON runs as a separate task and does not affect runtime behavior.
DBH 1
...
DBH n
DBH pool 1 ... DBH pool n
Service
task 1
Service task
pool 1
...
Service
task n
... Service task
pool n
SESDCN
DCN pool
AP 1- n
DBCON
TIAM
pool
Appl.pool
1-n
SESMON
TCP/IP network
Management
platform
(SNMP)
Figure 7: Collecting and evaluating data with SESMON
After an internal restart of SESAM/SQL-DBH or SESDCN, interval counters are not
supplied for the first output.
i
378
The following always applies:
Output sent to SYSOUT and SYSLST is not upwardly compatible.
Output layout may vary depending on the version used.
U22418-J-Z125-6-76
SESMON
Overview of statistical output
7.1 Overview of the statistical output of SESMON
The different output options are described below:
–
–
–
–
output on screen
output to a file
output to SYSLST
output via SNMP to a management platform
Output on screen
To allow you to select the information you require easily, it is subdivided into a number of
topics and distributed across a number of different forms.
SELECTION
CONFIGURATION
statistics
SESDCN
statistics
PREFETCHBUFFERS
APPLICATIONS
CAPACITY
APPLICATIONS
TRANSACTIONS
OVERVIEW
DBH
statistics
SQL
INFORM.
SERVICE
ORDERS
I/O
OPTIONS
SERVICE
TASKS
SYSTEM
THREADS
SYSTEM
INFORM.
STATEMENTS
TASKS
TRANSACTIONS
Figure 8: SESMON statistics output
U22418-J-Z125-6-76
379
Overview of statistical output
SESMON
The CONFIGURATION form “APPLICATIONS”
The form provides information on transaction applications which do not operate in
distributed mode.
The CONFIGURATION form “PREFETCH-BUFFERS”
The form shows the buffer space made available when requested for block mode
and the percentage of the buffer being used.
The SESDCN form “APPLICATIONS”
This form provides information on transaction applications which operate in
distributed mode.
The SESDCN form “CAPACITY”
This form contains information on message volume, pool assignment and resource
bottlenecks.
The SESDCN form “OVERVIEW”
This form contains general information on SESDCN operation, such as the set DCN
options and values that apply to the whole SESDCN session.
The SESDCN form “TRANSACTIONS”
This form provides information on the state and behavior of transactions.
The DBH form “I/O”
This form contains information on logical and physical read and write accesses.
The DBH form “OPTIONS”
This form displays the current settings of the DBH options.
The DBH form “SERVICE ORDERS”
The form shows the DDL or utility statements currently being processed in the
service tasks as well as the user ID of the user for each request. If there is a
RECOVER or REFRESH service request, its progress is indicated. In addition, the
current logging file and the most recently processed block are output.
The DBH form “SERVICE TASKS”
This form supplies values on the service tasks and the requests to be processed
therein.
The DBH form “SQL INFORMATION”
This form displays information on SQL statements, SQL access plans, plan buffers
and calls of special SQL components.
The DBH form “STATEMENTS”
The form provides an overview of the current statements. It shows both the statements running within transactions as well as those running outside transactions.
380
U22418-J-Z125-6-76
SESMON
Overview of statistical output
The DBH form “SYSTEM INFORMATION”
This form displays the size of the various containers and the percentage of their
capacity that is utilized. It also contains information on the number of cursors and
existing or used logical files and SQL scans. In addition, it shows whether
accounting, SESCOS and priority control are switched on or off.
The DBH form “SYSTEM THREADS”
This form provides information on active system threads. The system threads
shown are write threads that deal with open write requests to spaces.
The DBH form “TASKS”
This form provides extended statistical data for a multitasking system that can be
used to determine the utilization of the individual DBH tasks.
The DBH form “TRANSACTIONS”
This form provides information on the number of transactions in the various transaction states and the number of DML statements.
You will find the exact layout of the forms as of page 391.
Output to SYSLST
The SYSLST forms contain the same information as the screen forms, but in some cases
it is more detailed. In batch mode, forms are output to SYSLST in accordance with the
specifications in the SET-MONITOR-OPTIONS statement. If SESMON is started interactively, only those forms selected from the “SELECTION” form are output to SYSLST (see
page 389).
You will find the exact layout of the output as of page 439.
Output to a file
SESMON outputs all the statistical data to a file so that it can be processed by an evaluation
program.
You will find the exact layout of the output as of page 425.
Output via SNMP to a management platform
SESMON transfers the statistical data via a SESAM subagent and SNMP and to a
management platform, see page 451.
U22418-J-Z125-6-76
381
Running SESMON
SESMON
7.2 Running SESMON
7.2.1 Starting SESMON
Sequence of commands for starting SESMON
[/SET-FILE-LINK LINK-NAME=SEMSTAT,FILE-NAME=file] —————————————————————
/START-SESAM-PERF-MONITOR —————————————————————————————————————————————
(1)
file stands for the name of the file to which SESMON writes the statistical data.
Without this statement, SESMON writes the data to a SAM file called
SESMON.STATISTIK.yyyy-mm-dd by default.
(2)
Starts SESMON with the start command START-SESAM-PERF-MONITOR (see
section “Starting SESAM/SQL programs via start commands” on page 31).
i
7.2.1.1
(1)
(2)
With SESAM/SQL-Server, the concurrent use of multiple correction delivery
statuses is possible. When the performance monitor is started up, the correction
delivery status of the DBH to be monitored is then specified with the VERSION
parameter. If this is not done, the performance monitor may start up with the most
recent correction delivery status while the DBH is still working with an older status.
In this case, you receive a message indicating that the DBH to be monitored does
not exist (see also section “Specifying the correction delivery status with the start
command” on page 36).
Start parameters when running SESMON in interactive mode
The start parameters are entered in the SELECTION form, which SESMON displays after
it is started in interactive mode. To see the layout of the “SELECTION” form, refer to section
“The layout of the SELECTION form” on page 389.
7.2.1.2
Start parameters when running SESMON in batch mode
In batch mode, SESMON expects the start parameters from SYSDTA via the SETMONITOR-OPTIONS statement (see page below), and form output is not possible. The
default value for SYSLST output can also be changed in batch mode.
382
U22418-J-Z125-6-76
SESMON
Running SESMON
Function
The statement contains the start parameters for SESMON in batch mode.
SET-MONITOR-OPTIONS
RUNTIME = *INFINITE / *DBHDCN / <integer 60..99999>
,CONFIGURATION-NAME = *BLANK / <alphanum-name 1..1>
,DBH-NAMES = *NONE / list-poss(10) : *BLANK / <alphanum-name 1..1>
,OUTPUT = *SNMP / list-poss(2) : *FILE(...) / *SYSLST(...)
*FILE(...)

REFRESH-TIME = *NONE / <integer 1..999>
*SYSLST(...)


























U22418-J-Z125-6-76
REFRESH-TIME = *NONE / <integer 1..999>
,SESAM-CONFIGURATION = *NO / *YES(...)
*YES(...)


APPLICATIONS = *NO / *YES
,PREFETCH-BUFFERS = *NO / *YES
,SESDCN = *NO / *YES(...)
*YES(...)






APPLICATIONS = *NO / *YES
,CAPACITY = *NO / *YES
,OVERVIEW = *NO / *YES
,TRANSACTIONS = *NO / *YES(...)
*YES(...)

NUMBER = 200 / <integer 10..999>
,SESAM-DBH = *NO / *YES(...)
*YES(...)











I-O = *NO / *YES
,SERVICE-ORDERS = *NO / *YES
,SERVICE-TASKS = *NO / *YES
,SQL-INFORMATION = *NO / *YES
,STATEMENTS = *NO / *YES
,SYSTEM-INFORMATION = *NO / *YES
,SYSTEM-THREADS = *NO / *YES
,TASKS = *NO / *YES
,TRANSACTIONS = *NO / *YES(...)
*YES(...)

NUMBER = 200 / <integer 10..999>
383
Running SESMON
SESMON
Operands
RUNTIME = *INFINITE / *DBHDCN / <integer 60..99999>
You specify the length of the time period during which SESMON is to collect data.
*INFINITE specifies that SESMON runs until it is terminated by the STOP administration
command (see page 387), the cancellation of the SESMON task or the termination of all
tasks monitored by SESMON.
The termination of all the tasks monitored by SESMON does not cause SESMON to be
terminated when the CONFIGURATION forms have not been selected.
You specify the length of the SESMON runtime in seconds.
RUNTIME = *DBHDCN
SESMON is automatically terminated when all the relevant DBHs and DCNs are terminated.
CONFIGURATION-NAME = *BLANK / <alphanum-name 1..1>
You enter the name of the configuration in which SESMON is to carry out statistical
analyses.
DBH-NAMES = *NONE / list-poss(10) : *BLANK / <alphanum-name 1..1>
You enter the names of the DBHs for which SESMON is to carry out statistical analyses. By
default (*NONE), statistical analyses is not carried out on any DBHs.
Where OUTPUT=*SNMP, SESMON only collects data for the first DBH name.
Where OUTPUT=*SNMP and DBH-NAMES=*NONE, SESMON collects all configuration
data not assigned to a DBH.
OUTPUT = *SNMP / list-poss(2) : *FILE(...) / *SYSLST(...)
You specify where the statistical data is to be output and at what intervals new values are
to be output (the refresh time). This is also the time period during which the values are
collected. In each case, the values apply to the period immediately prior to output whose
length is specified here.
OUTPUT = *SNMP
SESMON transfers the statistical data via a SESAM subagent and SNMP to a management
plattform, see page 451.
OUTPUT = *FILE(...)
The output destination for the statistical data is a file. The name of the file is either specified
by means of the ADD-FILE-LINK command and assigned under the link name SEMSTAT
when SESMON is started, or the default name (SESMON.STATISTIK.yyyy-mm-dd) is used.
REFRESH-TIME = *NONE / <integer 1..999>
Refresh time in seconds; *NONE means that only one analysis is carried out and
SESMON then terminates if it does not have to support any other output destinations.
384
U22418-J-Z125-6-76
SESMON
Running SESMON
OUTPUT = *SYSLST(...)
The output destination for the statistical data is SYSLST.
REFRESH-TIME = *NONE / <integer 1..999>
Refresh time in seconds; *NONE means that only one analysis is carried out and
SESMON then terminates if it does not have to support any other output destinations.
SESAM-CONFIGURATION = *NO / *YES(...)
Selection of the masks that refer to the configuration
*YES(...)
APPLICATIONS = *NO / *YES
You specify whether the “APPLICATIONS” form is to be output for nondistributed
application users.
PREFETCH-BUFFERS = *NO / *YES
You specify whether the “PREFETCH-BUFFERS” form is to be output.
SESDCN = *NO / *YES(...)
Selection of the masks that refer to SESDCN
*YES(...)
APPLICATION = *NO / *YES
You specify whether the “APPLICATIONS” form is to be output for distributed application users.
CAPACITY = *NO / *YES
You specify whether the “CAPACITY” form is to be output.
OVERVIEW = *NO / *YES
You specify whether the “OVERVIEW” form is to be output.
TRANSACTIONS = *NO / *YES(...)
You specify whether the “TRANSACTIONS” form is to be output.
*YES(...)
NUMBER = 200 / <integer 10..999>
You specify the maximum number of transactions output to SYSLST.
U22418-J-Z125-6-76
385
Running SESMON
SESMON
SESAM-DBH = *NO / *YES(...)
Selection of masks that refer to the DBH.
*YES(...)
I-O = *NO / *YES
You specify whether the “I/O” form is to be output.
SERVICE-ORDERS = *NO / *YES
You specify whether the “SERVICE-ORDERS” form is to be output.
SERVICE-TASKS = *NO / *YES
You specify whether the “SERVICE-TASKS” form is to be output.
SQL-INFORMATION = *NO / *YES
You specify whether the “SQL-INFORMATION” form is to be output.
STATEMENTS = *NO / *YES
You specify whether the “STATEMENTS” form is to be output.
SYSTEM-INFORMATION = *NO / *YES
You specify whether the “SYSTEM-INFORMATION” form is to be output.
SYSTEM-THREADS = *NO / *YES
You specify whether the “SYSTEM-THREADS” form is to be output.
TASKS = *NO / *YES
You specify whether the “TASKS” form is to be output.
TRANSACTIONS = *NO / *YES(...)
You specify whether the “TRANSACTIONS” form is to be output.
*YES(...)
NUMBER = 200 / <integer 10..999>
You specify the maximum number of transactions to be output to SYSLST.
386
U22418-J-Z125-6-76
SESMON
Running SESMON
7.2.2 SESMON administration
SESMON is administered by the command INFORM-PROGRAM. For reasons of compatibility the earlier command SEND-MSG can also be used.
Calling the SELECTION form in interactive mode
After interrupting SESMON with the
K2
key, you can enter
/INFORM-PROGRAM MSG='SEL'
in order to call the SELECTION form, modify the values and continue SESMON analysis
with modified parameter values. Alternatively, you can output the SELECTION form by
means of hitting the K1 key.
Terminating SESMON in interactive mode
After interrupting SESMON with the
K2
key, you can terminate SESMON by entering
/INFORM-PROGRAM MSG='STOP'
Alternatively, you can terminate SESMON by hitting the
K3
key.
Terminating SESMON in batch mode
When SESMON is running in batch mode, you terminate it with
/INFORM-PROGRAM (JOB-ID=*TSN(TSN=tsn), MSG='STOP'
from the console of the BS2000 system administrator. You specify the task sequence
number (tsn).
SESMON can be terminated by means of /INFORM-PROGRAM also by a user with the
privilege OPERATING or TSOS.
U22418-J-Z125-6-76
387
Running SESMON
SESMON
7.2.3 Automatic termination of SESMON operation
Interactive mode
When all the tasks SESMON has to monitor are terminated, the SELECTION form is
displayed.
If a CONFIGURATION form (APPLICATIONS or PREFETCH-BUFFERS) was marked, the
SELECTION form does not appear and the CONFIGURATION form(s) continue to be
output to the selected output destination. SESMON is not terminated even if the DBH is
terminated.
Batch mode
In batch mode, SESMON terminates when all the tasks it has to monitor are terminated.
If PREFETCH-BUFFERS information was requested, PREFETCH-BUFFERS continues to
be output to SYSLST after all the tasks are terminated. SESMON is not terminated even if
the DBH is terminated.
Task switches at termination of SESMON
388
Normal termination
task switches 11 and 12 are not set.
Termination with a warning
task switch 11 is set.
Termination with an error
task switch 12 is set.
U22418-J-Z125-6-76
SESMON
SELECTION form
7.3 The layout of the SELECTION form
================================================================================
>>> SELECTION <<<
V03.2A00
Time: 14:11:05
Configuration:
DBHs :
Output Medium
File
:
Screen :
SYSLST :
Output Masks
SESAM-CONFIGURATION
Applications
SESDCN
Applications
Overview
SESAM-DBH
I/O
Service Orders
SQL Information
System Information
System Threads
Refresh-Time:
Refresh-Time:
Refresh-Time:
Seconds
Seconds
Seconds
:
Prefetch-Buffers
:
:
:
Capacity
Transactions
:
:
200
:
:
:
:
:
Options
Service Tasks
Statements
Tasks
Transactions
:
:
:
:
:
200
.....
>>>
INTERRUPT WITH KEY K2
<<<
================================================================================
LTG
TAST
The user can enter selection criteria in the fields shaded gray.
Field descriptions
V
SESMON version
Time
Time at which the form is output
Configuration
Enter the configuration SESMON is to monitor. All letters, all digits and the blank are
permitted for the configuration name.
DBHs user can enter up to ten SESAM/SQL DBHs for which the DBH forms are to be
output. All letters, all digits and the blank are permitted.
U22418-J-Z125-6-76
389
SELECTION form
SESMON
Output Medium
You specify here the destination(s) to which the information is to be output by
entering x or X against each output destination. You also set the refresh time for
each medium selected. This is the period of time in seconds to elapse before the
next output on this medium. It is also the time period during which the values are
collected. In each case, the values apply to a period immediately prior to output
whose length is specified here.
The values 0 to 999 are permitted as refresh times for output.
If you enter 0, the output is executed only once.
In the case of screen output with a refresh time of 0, you can select only one form.
The displayed form remains on screen.
Output Masks
You must enter x or X against each form you require.
With SESDCN and SESAM-DBH, TRANSACTIONS (the number of logged transactions) has a default value of 200. Values from 10 to 999 can be entered.
This selection applies only to output to the screen and to SYSLST. Output to a file
always includes all data.
......
390
Messages are output in these lines.
U22418-J-Z125-6-76
SESMON
CNF form APPLICATIONS
7.4 Layout of the forms
The CONFIGURATION form APPLICATIONS
The form provides information on transaction applications which do not operate in
distributed mode.
================================================================================
>>> APPLICATIONS <<<
V03.2A00
CNF: Z
Time: 16:02:09
Actual Applications:
Application
ANWEND02
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
1
Maximal Applications:
Number of Users
Actual
7
0
0
0
0
0
0
0
0
0
0
0
0
0
64
Number of Tasks
Maximal
Actual
8
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
Version of the DBH.
CNF
Name of the configuration monitored.
Time
Time at which the form was output.
Actual Applications
Number of transaction applications currently active.
Maximal Applications
Maximum possible number of transaction applications.
Application
Name of the transaction application to which the output figures in this line apply
(eight-position). Only the currently active transaction applications are listed.
U22418-J-Z125-6-76
391
CNF form PREFETCH-BUFFERS
SESMON
Number of Users Actual
Current number of users of the specified transaction application. The output is
sorted in descending order according to the number of active users. A maximum of
14 transaction applications are output.
Number of Tasks Maximal/Actual
Maximum or current number of tasks of this transaction application.
The CONFIGURATION form PREFETCH-BUFFERS
This form contains information on the buffer space made available when requested:
================================================================================
>>> PREFETCH-BUFFERS <<<
V03.2A00
CNF: Z
Time: 16:52:20
Appl./
TSN
T
<=1KB
<=2KB
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
H i t r a t e
<=4KB <=8KB <=16KB <=32KB <=64KB
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
>64KB
Perc.
Occ.
Max.
Occ.
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
Version of the DBH
CNF
Name of the configuration monitored
Time
Time at which the form is output
Appl./TSN
Name of the openUTM transaction application (up to 8 characters) or the TSN in the
case of a TIAM application
392
U22418-J-Z125-6-76
SESMON
CNF form PREFETCH-BUFFERS
T (Type)
Type of the application
U: UTM application
T: TIAM application
Hitrate
Percentage of the requested memory space made available. The information is
subdivided on the basis of how much memory space is requested. The entry “--%”
means that no requests have yet been made in this memory class.
Percentage Occupation
Percentage of the buffer occupied
Maximal Occupation
Maximum percentage of the buffer that can be occupied
The entries (of which there can be up to 15) are sorted on the basis of the quality of the
buffer parametrization. Up to 100 entries are output to SYSLST.
The following aspects are included in the quality assessment:
–
Hit rate for memory requests:
Hit rate in percent =
(total memory space received /
total memory space requested) * 100
–
Maximum percentage of the buffer occupied
The quality of the buffer parametrization is calculated by means of the following formula:
Average hit rate when memory space is requested * maximum percentage of the
buffer that can be occupied
The form merely indicates whether the requested memory area is made available. It does
not say anything about the use of the memory area.
U22418-J-Z125-6-76
393
SESDCN form APPLICATIONS
SESMON
The SESDCN form APPLICATIONS
This form provides information on distributed transaction applications.
================================================================================
>>> APPLICATIONS <<<
V03.2A00
CNF: Z
Time: 13:00:02
Actual Applications:
Application
TSN=8GZN
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
_________________________
1
Maximal Applications:
Number of Users
Actual
6
0
0
0
0
0
0
0
0
0
0
0
0
0
64
Number of Tasks
Maximal
Actual
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
SESDCN version
CNF
Name of the configuration monitored
Time
Time at which the form is output
Actual Applications
Number of currently active transaction applications.
Maximal Applications
Maximum possible number of transaction applications.
Application
Name of the transaction application to which the numbers output in this line apply
(eight characters). Only those transaction applications that are currently active are
listed.
394
U22418-J-Z125-6-76
SESMON
SESDCN form CAPACITY
Number of Users Actual
Current number of active users (in the sense of the DCN option USERS) of the
specified transaction application. The output is sorted in descending order based
on the number of current users. A maximum of 14 transaction applications are
output.
Number of Tasks Maximal/Actual
Maximum/current number of tasks belonging to this transaction application
The SESDCN form CAPACITY
This form contains information on message volume, pool utilization and resource bottlenecks.
================================================================================
>>> CAPACITY <<<
V03.2A00
CNF: Z
Time: 13:01:19
Broadcast Messages:
Mail Messages
:
BCAM Mem. Lacks
:
Requests for Locks:
Pool Locks
:
Synchron Accesses :
Asynchron Accesses:
Elapsed Time in
Contingency
Session Interval
0
0
7
0
0
0
385
3
385
3
88
0
0
0
:
SESAM Messages:
Length
<= 2K
Session
115
Interval
0
Used Pool Containers
Free Pool Containers
0.00%
<= 4K
1
0
Maximum
Messages Fragmentation:
0
Time in Pool Lock
:
4578
Users per Application :
6
Tasks per Application :
1
Container per User
:
3
Sub TAs per User
:
0
Users per Catalog
:
0
<= 8K
4
0
<= 16K
0
0
:
:
<= 32K
0
0
Average
0
12
6
1
3
0
0
551
713
<= 64K
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
SESDCN version.
CNF
Name of the configuration monitored.
Time
Time at which the form is output.
U22418-J-Z125-6-76
395
SESDCN form CAPACITY
SESMON
Broadcast Messages
Number of messages sent additionally because of preparation to commit a transaction, the end of a transaction, the end of a UTM conversation or the rolling back
of a transaction (in this SESDCN session and per time period).
Mail Messages
Number of messages that could not be sent until later because processing was
interrupted (in this SESDCN session and per time period).
BCAM Memory Lacks
Number of remote messages that could not be transferred because not enough
memory was available for them (in this SESDCN session and per time period).
Requests for Locks
Number of requested pool locks (in this SESDCN session and per time period).
Pool Locks
Number of granted pool locks (in this SESDCN session and per time period).
Synchron Accesses
Number of synchronous database accesses (in this SESDCN session and per time
period).
Asynchron Accesses
Number of asynchronous accesses at the CALL DML interface by means of CALL
SESPUT and CALL SESGET(W) (in this SESDCN session and per time period).
Message Fragmentation
Number of message fragments into which the DCAM messages sent so far had to
be subdivided (maximum and average over the whole SESDCN session).
Messages have to be divided up if they are longer than the maximum send length
for the addressed computer.
Time in Pool Lock
Number of milliseconds for which a transaction was locked in the case of a pool
access (maximum and average over the whole SESDCN session).
Users per Application
Maximum number of current users of a transaction application and average number
over the whole SESDCN session.
Tasks per Application
Maximum number of current tasks belonging to a transaction application and
average number over the whole SESDCN session.
Container per User
Maximum number of pool containers (pool container: 256-byte unit) used by a user
in this session and average number of pool containers used by a user (snapshot).
396
U22418-J-Z125-6-76
SESMON
SESDCN form CAPACITY
Sub TAs per User
Maximum number of subtransactions per user in this session and average number
of subtransactions per user (snapshot).
Users per Catalog
Maximum current number of users accessing a database and average number over
the session.
Elapsed Time in Contingency
Specifies how much time SESDCN has so far spent on asynchronous activities. The
value is a percentage of total SESDCN runtime.
Used Pool Containers
Number of containers in the SESDCN pool that are currently used.
Free Pool Containers
Number of containers that are still free.
SESAM Messages
Number of SESAM/SQL messages (remote and local) in this SESDCN session and
per time period. The SESAM/SQL messages are divided into six different classes.
The counter of the class to which the message belongs on the basis of its length is
incremented.
U22418-J-Z125-6-76
397
SESDCN form OVERVIEW
SESMON
The SESDCN form OVERVIEW
The form contains general information on SESDCN operation, such as the set DCN options
and values that apply to the whole SESDCN session.
================================================================================
>>> OVERVIEW <<<
V03.2A00
CNF: Z
Time: 13:02:01
Master DCN
:
Configuration : Z
Session Begin : 10:04:38
Number
Number
Number
Number
Number
of
of
of
of
of
SESDCNs
SESAM-DBHs
active Users
active Applications
active PTCs
Number of DML-Statements
Number of Transactions
Number of Remote DML
Users
:
Inactivity-Time :
2003-09-08 Lock-Time
:
:
:
:
:
:
:
:
:
128
12 min.
8 min.
1
1
6
1
0
Session
88
25
9
Interval
0
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
SESDCN version.
CNF
Name of the configuration monitored.
Time
Time at which the form is output.
Master DCN
Name of the master DCN that opened the SESDCN pool.
Configuration
Name of the configuration monitored.
Session Begin
Date and time the SESDCN session opened on the first SESDCN (master DCN)
being started.
Users Value for the USERS parameter of the DCN option SYSTEM-LIMITS of the master
DCN. USERS specifies the maximum number of users.
398
U22418-J-Z125-6-76
SESMON
SESDCN form OVERVIEW
Inactivity-Time
(field name in the case of output to SYSLST: NATL)
Value for the INACTIVITY-TIME parameter of the DCN option SYSTEM-LIMITS of
the master DCN. The inactivity time is a reset criterion for transactions.
Lock-Time
(field name in the case of output to SYSLST: LCTL)
Value for the LOCK-TIME parameter of the DCN option SYSTEM-LIMITS of the
master DCN. This value is a reset criterion for transactions.
Number of SESDCNs
Current number of SESDCNs loaded on the local computer and belonging to the
selected configuration.
Number of SESAM-DBHs
Current number of DBHs belonging to the selected configuration on the local
computer and participating in distributed processing.
Number of active Users
Number of currently active users.
Number of active Applications
Number of currently active transaction applications.
Number of active PTCs
Number of transactions currently in the PTC state.
Number of DML Statements
Specifies how many DML statements (CALL DML and SQL DML) have been
entered in this SESDCN session/time period.
Number of Transactions
Specifies how many transactions have been started in this SESDCN session/time
period.
Number of Remote DML
Specifies the number of accesses of databases in other configurations in this
SESDCN session/time period.
U22418-J-Z125-6-76
399
SESDCN form TRANSACTIONS
SESMON
The SESDCN form TRANSACTIONS
This form provides information on the state and behavior of transactions.
================================================================================
>>> TRANSACTIONS <<<
V03.2A00
CNF: Z
Time: 13:02:48
External Resets
- Administration
- Application
Deadlock Analysis
Deadlocks Found
:
:
:
:
:
Session Interval
0
0
0
0
0
0
0
0
0
0
Internal Resets
- Deadlock
- Inactivity
- Lock
Open TAs
NR
1
2
3
4
5
6
0
0
0
TAC
EXAMPLE
EXAMPLE
EXAMPLE
EXAMPLE
EXAMPLE
EXAMPLE
User-ID
D016ZE07TSN=8GZNUSER0001
D016ZE07TSN=8GZNUSER0002
D016ZE07TSN=8GZNUSER0003
D016ZE07TSN=8GZNUSER0004
D016ZE07TSN=8GZNUSER0005
D016ZE07TSN=8GZNUSER0006
S
A
A
A
A
A
A
:
:
:
:
Session Interval
6
0
0
0
6
0
0
0
:
6
I/O Lo Duration Statements
0
00:17:11
1
0
00:16:52
1
0
00:16:34
1
0
00:16:13
1
0
00:15:47
1
0
00:15:28
1
0
0
0
0
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
SESDCN version
CNF
Name of the configuration monitored
Time
Time at which the form is output
External Resets
Number of transactions rolled back by means of administration commands or statements or a statement in the application program (in this SESDCN session and per
time period)
Administration
Number of transactions rolled back by means of administration commands or statements (in this SESDCN session and per time period)
Application
Number of transactions rolled back by means of a statement in the application
program (in this SESDCN session and per time period)
400
U22418-J-Z125-6-76
SESMON
SESDCN form TRANSACTIONS
Deadlock Analysis
Number of deadlock analyses carried out (in this SESDCN session and per time
period)
Deadlocks Found
Number of deadlock analyses in which deadlocks were detected (in this SESDCN
session and per time period)
Internal Resets
Number of transactions rolled back for internal reasons (in this SESDCN session
and per time period). Internal reasons for this are deadlock or the inactivity time
(“Inactivity”) or lock time (“Lock”) being exceeded.
Deadlock
Number of transactions rolled back because of deadlock (in this SESDCN session
and per time period)
Inactivity (field name in the case of output to SYSLST: NATL)
Number of transactions rolled back because the inactivity time has been exceeded
(in this SESDCN session and per time period). You set the inactivity time by means
of the INACTIVITY-TIME parameter of the DCN option SYSTEM-LIMITS.
Lock (field name in the case of output to SYSLST: LCTL)
Number of transactions rolled back because the lock time has been exceeded (in
this SESDCN session and per time period). You set the lock time by means of the
LOCK-TIME parameter of the DCN option SYSTEM-LIMITS.
Open TAs
Number of currently open transactions
The following information relates to individual transactions. The transactions are sorted in
descending order according to their duration. A maximum of nine transactions are output.
NR
Unique (two-digit) transaction number assigned by SESMON
TAC
UTM transaction code used to call the application program that opened this transaction (eight characters).
In the case of TIAM applications, the user ID of the application program appears
here, in the case of DCAM applications the request name.
User-ID
Identification of the user who opened the transaction (32 characters). It appears in
the following form: HOST-NAME, APPLICATION-NAME, CUSTOMER-NAME,
CONVERSATION-ID (see page 206)
U22418-J-Z125-6-76
401
SESDCN form TRANSACTIONS
SESMON
S (State)
State of the transaction (one character):
A: active
P: Prepare-to-Commit
L: locked
I/O
Weighted sum of the physical inputs and outputs of this transaction. The weighted
sum is obtained by counting write accesses twice and read accesses once.
Lo (Lock)
Number of the transaction locking this transaction (2 digits). If the output transaction
is locked by a transaction that can no longer be displayed on the screen, this is
indicated by two asterisks (**).
Duration
Elapsed time of the transaction in the form hh:mm:ss
Statements
Number of statements of this transaction that have been executed. Only those
statements that have not been processed completely by the SQL runtime system
are counted. In cases where CALL DML statements are chained, each individual
statement is counted.
402
U22418-J-Z125-6-76
SESMON
DBH form I/O
The DBH form I/O
This form contains information on logical and physical read and write accesses.
================================================================================
>>> I/O <<<
V03.2A00
DBH: X
CNF: Z
Time: 16:09:07
Number of
Spaces
6
Log. Read
Log. Write
Phys. Read
Phys. Write
Hitrate
Phys. Read
Phys. Write
4K Blocks /
Written Blocks
Cursor Files
85
LOG Files
1
System Data Buffer
Session Interval
499309
12584
5974
879
9926
104
1616
20
97.72%
99.08%
User Data Buffer
Session Interval
1346214
13738
1708
548
31872
641
414
71
97.60%
95.02%
Cursor Files
Session Interval
271298
5537
15648
398
1332
29
2024
44
98.83%
98.77%
DA-LOG/CAT-LOG
Session Interval
0
0
0
0
TA-LOG
Session Interval
180
12
2068
91
WA-LOG
Session Interval
5
2
21
14
0.00
1.71
1.38
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version
DBH
Name of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form is output
Number of Spaces
Number of catalog and user spaces
Number of Cursor Files
Number of logical cursors output
Number of LOG Files
Current number of DA-LOG and CAT-LOG files.
U22418-J-Z125-6-76
403
DBH form I/O
SESMON
The following outputs apply only to the DBH task, not to the service tasks.
Log. Read
Total number of logical read accesses of the spaces or the cursor files
(for the session and per time period).
Log. Write
Total number of logical write accesses of the spaces or the cursor files
(for the session and per time period).
Phys.Read
Number of physical read accesses of the spaces or the cursor files
(for the session and per time period).
Phys.Write
Number of physical write accesses of the spaces and cursor files
(for the session and per time period).
Hitrate
Number of logical file accesses of the spaces and cursor files as a percentage of
total accesses (for the session and per time period).
Long-running DBH counters (e.g. Log. Read) may overrun and start again from 0.
If SESMON finds this, no further hit rates are issued.
Phys. Read
Number of physical read accesses of the LOG files, i.e. DA-LOG with CAT-LOG,
TA-LOGs and WA-LOG (for the session and per time period).
Phys. Write
Number of physical write accesses of the LOG files, i.e. DA-LOG with CAT-LOG,
TA-LOGs and WA-LOG (for the session and per time period)
4K Blocks / Written Blocks
Specifies the average number of 4K blocks written during a write operation. The
value is determined as of the beginning of the session for the LOG files.
In output to SYSLST you will find additional information in the DBH form “I/O” (see
page 443). The read and write behavior is indicated there for each file.
404
U22418-J-Z125-6-76
SESMON
DBH form OPTIONS
The DBH form OPTIONS
This form displays the currently set DBH options.
The output can extend to three screen pages. The page is changed when the refresh time
specified in the SELECTION form for the output medium has elapsed.
================================================================================
>>> OPTIONS <<<
V03.2A00
DBH: X
CNF: Z
Time: 15:13:14
ACCOUNTING
ADMINISTRATOR
COLUMNS
CURSOR-BUFFER
DBH-IDENTIFICATION
DBH-TASKS
MSG-OUTPUT
OLD-TABLE-CATALOG
REQUEST-CONTROL
RESTART-CONTROL
RETRIEVAL-CONTROL
*OFF
*ANY
256
BUFFER-SIZE=448
, FRAME-SIZE=4
CONFIGURATION-NAME=Z, DBH-NAME=X
1
MSG
=*SYSOUT, *SYSLST
OPEN-CLOSE-MSG=*NONE
5
*NONE
BUFFER-LIMIT:SYSTEM-DATA-BUFFER=50
BUFFER-LIMIT:USER-DATA-BUFFER=50
TALOG-LIMIT=512
LOGICAL-ROLLBACK=*IMMEDIATELY
USER-DATA-ACCESS=1000
, INDEX-EVALUATION=2147483647
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version
DBH
Name of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form was output
U22418-J-Z125-6-76
405
DBH form SERVICE ORDERS
SESMON
The DBH form SERVICE ORDERS
The form shows the DDL or utility statements which are currently being processed in the
service tasks, as well as the identification of the user for each request. If a RECOVER
service order exists, the progress of this order is shown.
================================================================================
>>> SERVICE ORDERS <<<
V03.2A00
DBH: X
CNF: Z
Time: 15:31:36
User-ID
D016ZE09TSN=6AIWDSQL
Order
RECOVER
TSN
6AXN
S
A
Duration
00:01:01
Recover/Refresh Progress:
Log-File
:5OSB:$XDL1DBT4.STANCAT4.0001.D.0009
Block TSN
23 6AXN
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
Version of the DBH
DBH
Name of the DBH to which the data in the form applies.
CNF
Name of the configuration monitored.
Time
Time at which the form was output.
User-ID
Identification of the user (32 positions). Comprises HOST-NAME, APPLICATIONNAME, CUSTOMER-NAME and CONVERSATION-ID (see section “Syntax for the
identification of users” on page 205).
406
U22418-J-Z125-6-76
SESMON
DBH form SERVICE ORDERS
Order Type of request (20 positions)
If sort requests are processed in the service task when processing DML statements, “SORT” is output.
Otherwise the statement that the user issued is shown.
Possible statements here are:
ALTER MEDIA DESCR (for ALTER MEDIA DESCRIPTION)
ALTER SPACE
ALTER STOGROUP
ALTER TABLE
CHECK CONSTRAINTS
CHECK FORMAL
COPY
CREATE CATALOG
CREATE INDEX
CREATE MEDIA DESCR (for CREATE MEDIA DESCRIPTION)
CREATE REPLICATION
CREATE SCHEMA
CREATE SPACE
CREATE STOGROUP
CREATE TABLE
CREATE USER
CREATE SYSTEM USER
CREATE VIEW
DROP INDEX
DROP MEDIA DESCR (for DROP MEDIA DESCRIPTION)
DROP SCHEMA
DROP SPACE
DROP STOGROUP
DROP TABLE
DROP USER
DROP SYSTEM USER
DROP VIEW
EXPORT TABLE
GRANT
IMPORT TABLE
LOAD
MIGRATE
MODIFY
RECOVER
REFRESH
REORG
REORG STATISTICS
REVOKE
UNLOAD
U22418-J-Z125-6-76
407
DBH form SERVICE ORDERS
TSN
SESMON
TSN of the service task currently processing the request. You can use this specification to find the associated entry on the DBH form SERVICE TASKS.
If the request is not yet processed or is already processed, " " appears here.
S
Status of the request (one position)
W (Waiting):
The request is not yet processed by a service task.
A (Active):
The request is currently being processed by a service task.
F (Finished):
The request has been processed by the service task and can
be retrieved from the DBH.
Duration
Specifies the duration thus far of the request with respect to the current status, i.e.
Duration specifies how long a request has already had the status “W”, “A” or “F”.
The requests are sorted in two levels based on:
–
The status of the request in the following order
1. Status “W”
2. Status “A”
3. Status “F”
–
Within a status, the entries are sorted in descending order based on their duration.
A maximum of 10 requests are output to the screen, and a maximum of 100 to SYSLST.
RECOVER PROGRESS
If there is a RECOVER service request, the following items indicate its progress.
Log-File
Name of the log file (54 characters) currently being processed by the service task
that is executing the RECOVER.
Block Number of the block currently being processed in the log file.
TSN
408
Number of the service task executing the RECOVER. By means of this number the
information specified for Log-File and Block is related to the information specified in
the upper part of the form.
U22418-J-Z125-6-76
SESMON
DBH form SERVICE TASKS
The DBH form SERVICE TASKS
This form supplies values relating to the service tasks and the requests to be processed.
================================================================================
>>> SERVICE TASKS <<<
V03.2A00
DBH: X
CNF: Z
Time: 16:17:21
Service Tasks
Orders
TSN
87KG
87K0
87K2
87M4
Maximal
8
Number(Session)
1193
Order
Number of
Orders
1049
134
10
0
0
0
0
0
0
Actual
4
Active
0
Number(IV)
52
Phys. I/O
3147
402
30
0
0
0
0
0
0
Free
4
Not Processed
0
Used CPUTime (msec)
37712
5693
1055
0
0
0
0
0
0
Load
0.00%
Not Fetched
0
Elapsed
Time (msec)
203508
36937
13338
0
0
0
0
0
0
Load
18.53%
15.41%
7.91%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
Size
(Pages)
729
592
568
233
0
0
0
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version
DBH
Name of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form is output
Maximal
Maximum possible number of service tasks set by means of the DBH option
SERVICE-TASKS
Actual Number of started service tasks
Active Number of currently active service tasks
Free
Number of inactive service tasks that are currently free
Load
Active tasks as a percentage of started service tasks
Number (Session)
Number of requests for service tasks in this session
U22418-J-Z125-6-76
409
DBH form SERVICE TASKS
SESMON
Number (IV)
Number of requests for service tasks per time period
Not Processed
Number of requests not yet processed by the service tasks
Not Fetched
Number of requests processed by the service tasks but not yet fetched by the DBH
The following outputs relate to individual service tasks sorted in descending order on the
basis of the amount of CPU time they have used (“Used CPU-Time”). A maximum of nine
service tasks are output.
TSN
TSN of the service task
Order Type of request currently being processed by the service task:
SORT: sort request
REP: recovery request
UTI: utility statement
Number of Orders
Number of requests for service tasks so far processed (ten digits)
Phys. I/O
Number of physical inputs and outputs of the service task (ten digits)
Used CPU-Time (msec)
Total CPU time of the service task in milliseconds (ten digits). If the CPU time
cannot be determined because, for example, the DBH and thus also the service
tasks are running under a different ID than the monitor or the task is not known to
the system any more, then “********” is output.
Elapsed Time (msec)
Total duration of the service task in milliseconds (ten digits)
Load
“Used CPU-Time” as a percentage of “Elapsed Time”
Size (Pages)
Memory space (in pages of 4 Kbytes) used by the service task
410
U22418-J-Z125-6-76
SESMON
DBH form SQL INFORMATION
The DBH form SQL INFORMATION
This form displays information on SQL statements, SQL access plans, plan buffers and
calls of specific SQL components.
================================================================================
>>> SQL INFORMATION <<<
V03.2A00
DBH: X
CNF: Z
Time: 16:19:01
SQL DML
UPDATE
RETRIEVAL
SQL DDL/SSL
SQL UTI
:
:
:
:
:
Session
7021
398
6623
37
0
Interval
149
0
149
3
0
Number of Calls
Kernel Control :
Catalog Manager :
CALL DML Handler:
Session
697539
322524
1
Interval
23231
10478
0
Sort Operations :
Max. SQL Cursors :
Act. SQL Cursors :
1234
50
48
41
Plans
Accesses Core
:
Accesses Core/IV:
Generated
:
Generated/IV
:
Number per
DBH-Option
:
Plan Buffer
Number of Plans :
Size of
Primary Buffer :
Occupation of
Primary Buffer :
Size of
Secondary Buffer:
7039
164
688
20
50
102
868000
868000
35504
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version
DBH
Name of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form is output
SQL DML
Number of SQL DML statements (in this session and per time period)
UPDATE
Number of SQL update statements (in this session and per time period)
RETRIEVAL
Number of SQL retrieval statements (in this session and per time period)
SQL DDL/SSL
Number of SQL DDL and SQL SSL statements (in this session and per time period)
U22418-J-Z125-6-76
411
DBH form SQL INFORMATION
SESMON
SQL UTI
Number of utility statements (in this session and per time period)
Accesses Core
Number of accesses of SQL access plans during the whole session
Accesses Core/IV
Number of accesses of SQL access plans per time period
Generated
Number of SQL access plans generated in this session. SQL access plans are also
regenerated when they have been displaced from the plan buffer.
Generated/IV
Number of SQL access plans generated per time period. SQL access plans are also
regenerated when they have been displaced from the plan buffer.
Number per DBH-Option
Number of SQL access plans set by means of the DBH option SQL-SUPPORT
Kernel Control
Number of kernel-control calls (in this session and per time period)
Catalog Manager
Number of catalog-manager calls (in this session and per time period)
CALL DML Handler
Number of CALL DML handler calls (in this session and per time period)
Sort Operations
Number of SQL sort operations (in this session and per time period)
Max. SQL Cursors
Maximum number of open SQL cursors in the session
Act. SQL Cursors
Number of currently open SQL cursors (snapshot)
Number of Plans
Number of SQL access plans in the plan buffer (snapshot)
Size of Primary Buffer
Size of the primary plan buffer in bytes
Occupation of Primary Buffer
Space in bytes used in the primary plan buffer (snapshot)
Size of Secondary Buffer
Size of the secondary plan buffer in bytes
412
U22418-J-Z125-6-76
SESMON
DBH form STATEMENTS
The DBH form STATEMENTS
The form provides an overview of all active statements. It displays statements both within
transactions and those outside transactions.
================================================================================
>>> STATEMENTS <<<
V03.2A00
DBH: X
CNF: Z
Time: 16:22:21
Statements
Local DML :
Local SQL :
Remote DML:
Remote SQL:
TAC
QM124ELS
QM124ELS
QM124ELS
KSURQTT1
KSUUQCON
KSUUQDEC
KSUUQDEL
Session
0
0
0
0
Interval
0
0
0
0
User-ID
ANLAGE01TSN=87L0KAASTEUG
ANLAGE01TSN=87LXKAASTEUG
ANLAGE01TSN=87LYKAASTEUG
ANLAGE01ANWEND01QTT1IP020000003B
ANLAGE01ANWEND01QCONHP0100000062
ANLAGE01ANWEND01QDECDS010000005D
ANLAGE01ANWEND01QDELHS010000005C
Statement
Number :
Active :
Waiting:
S
L
L
L
L
I/O
3732
3280
11125
141670
14015
12949
20060
Duration
01:02:50
01:02:41
01:02:25
01:01:03
00:58:28
00:53:32
00:50:20
0
0
0
ActivityTime
0.00
0.00
0.00
0.00
0.00
0.00
0.00
T
M
M
M
M
M
M
M
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
Version of the DBH
DBH
Name of the DBH to which the data in the form applies.
CNF
Name of the configuration monitored.
Time
Time at which the form was output.
Local DML
Number of local CALL DML statements (for the session and per time period).
Local SQL
Number of all local SQL statements, including utility statements (for the session and
per time period).
Remote DML
Number of CALL DML statements entered from a different configuration (for the
session and per time period).
U22418-J-Z125-6-76
413
DBH form STATEMENTS
SESMON
Remote SQL
Number of all SQL statements, including utility statements, entered from another
configuration (for the session and per time period).
Number
Current number of statements (actual value).
This value is the sum of the two subsequent fields Active and Waiting.
Active Number of active statements (actual value), i.e. all statements marked “A” in column
S (see below).
Waiting
Number of waiting statements (actual value), i.e. all statements with the status “A”,
“L” and “W” in column S (see below).
Up to nine statements are output, sorted in descending order based on their duration. The
following specifications refer to individual statements.
TAC
UTM transaction code used to call the application program which opened this transaction (eight positions).
With TIAM applications, the user ID of the application program appears here; with
DCAM applications it is the request name.
User-ID
Identification of the user who opened the transaction. It is output in 32 positions in
the following form: HOST-NAME, APPLICATION-NAME, CUSTOMER-NAME,
CONVERSATION-ID (see section “Syntax for the identification of users” on
page 205).
S
I/O
Status of the statements (one position)
A:
The statement is being processed by a thread.
L:
The statement ran into a transaction lock. (The lock relationships of the
transactions can be taken from the DBH form TRANSACTIONS.)
W:
The statement is in the priority queue or is waiting for a service task.
Number of weighted inputs and outputs of this statement (i.e. write accesses are
counted twice, read accesses once).
Duration
Duration of the statement (elapsed time) in the format hh:mm:ss.
Activity-Time
Elapsed activity time of the statement in the DBH in seconds.
414
U22418-J-Z125-6-76
SESMON
DBH form STATEMENTS
T
Application type
M:
DML statement
D:
DDL statement
U:
Utility statement
Ë (space): The statement type is not yet known
U22418-J-Z125-6-76
415
DBH form SYSTEM INFORMATION
SESMON
The DBH form SYSTEM INFORMATION
This form indicates the size of each container and the percentage of its capacity that is
used. It also contains information on the number of cursors and the available and used
logical files and SQL scans.
================================================================================
>>> SYSTEM INFORMATION <<<
V03.2A00
DBH: X
CNF: Z
Time: 16:20:41
Active Suborders
for CALL DML:
for SQL DML :
1
79
Available Suborders
Maximal:
2000
Actual :
150
Parallel Open
Spaces:
Open Cursors:
6
84
Accounting:
OFF
SESCOS:
OFF
Request Control: ON
Actual
Size
200
64
Container
Work
Transfer
Threads
ACTIVE
Ready
Percentage
Occupation
96.00%
28.91%
Free
Waiting
Used Suborders
Maximal:
Actual :
Maximal
Size
1000
128
TA-Lock
97
80
Percentage
Occupation
19,20%
14,46%
Service
Task
I/O
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version
DBH
Name of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form is output
Active Suborders for CALL DML
Number of active suborders for CALL DML (logical files)
Active Suborders for SQL DML
Number of active suborders for SQL (SQL-DML)
Available Suborders Maximal
Maximum value for the number of concurrent suborders (DBH option
SUBORDERS, MAXIMUM parameter)
416
U22418-J-Z125-6-76
SESMON
DBH form SYSTEM INFORMATION
Available Suborders Actual
Initial value for the number of concurrent suborders (DBH option SUBORDERS,
INITIAL parameter)
Used Suborders Maximal
Maximum number of used suborders in the session
Used Suborders Actual
Current number of used suborders. This value is the sum of the values for “Active
Suborders for CALL DML” and “Active Suborders for SQL DML”.
Parallel Open Spaces
Current number of concurrently open spaces
Open Cursors
Current number of open internal cursor files
Accounting
ON/OFF specifies whether Accounting is currently switched on or off.
SESCOS
ON/OFF specifies whether SESCOS is currently switched on or off.
Request Control
ON/OFF specifies whether priority control is currently switched on or off.
Work Container Actual
Actual size of the work container in the DBH session in Kbytes.
Work Container Actual Percentage Occupation
Actual percentage of the work container occupied in relation to the current amount
occupied.
Work Container Maximal
Maximum occupation for work container according to the DBH options.
Work Container Maximal Percentage Occupation
Maximum percentage of the work container occupied in the DBH session in relation
to the maximum value specified in the DBH options.
Transfer Container Actual
Actual size of the transfer container in the DBH session in Kbytes.
Transfer Container Actual Percentage Occupation
Actual percentage of the transfer container occupied in relation to the current
amount occupied.
Transfer Container Maximal
Maximum value for transfer container according to the DBH options.
U22418-J-Z125-6-76
417
DBH form SYSTEM INFORMATION
SESMON
Transfer Container Maximal Percentage Occupation
Maximum percentage of the transfer container occupied in the DBH session in
relation to the maximum value specified in the DBH options.
Threads Active
Number of currently active threads (threads that are in the “running” state). The
number of active threads is smaller than or equal to the number of tasks.
Threads Ready
Current number of ready threads (threads that are in the “ready to run” state).
Threads Free
Number of currently free threads (threads that currently do not have a job).
Threads Waiting
Current number of threads that are not active due to a semaphore, block or termination of a system job.
Threads TA-Lock
Current number of threads that are not active due to a TA lock.
Threads Service Task
Current number of threads that are not active because they are waiting for a service
task.
Threads I/O
Current number of threads that are not active due to I/O.
418
U22418-J-Z125-6-76
SESMON
DBH form TASKS
The DBH form TASKS
This mask provides extended statistical data for a multitasking system that can be used to
determine the utilization of individual DBH tasks.
================================================================================
>>> TASKS <<<
V03.2A00
DBH: X
CNF: Z
Time: 17:21:09
TSN Threads
446K
6
45I6
6
45I7
1
45I8
5
0
0
0
0
0
0
0
0
0
0
0
0
Orders
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Waits
492
118
242
167
0
0
0
0
0
0
0
0
0
0
0
0
I/Os
334
52
194
72
0
0
0
0
0
0
0
0
0
0
0
0
Waits/IO
1.47
2.27
1.25
2.32
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
Used CPUTime (msec)
86696
3081
2005
2061
0
0
0
0
0
0
0
0
0
0
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version.
DBH
Name of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form is output
In the table of individual tasks one line is output per task, resulting in a maximum of 16 lines.
The tasks are always output in the same order, sorted according to the internal task ID,
together with the following values:
TSN
Task TSN
Threads
Number of threads currently assigned to this task.
Orders
Number of orders still in the communication queue for the task.
Waits Number of wait states due to I/O in the interval.
U22418-J-Z125-6-76
419
DBH form TASKS
I/Os
SESMON
Number of I/Os triggered in the interval.
Waits/IO
Ratio of the two previous values.
Number of wait states due to I/O / Number of I/Os triggered.
Used CPU-Time (10 digits)
Total CPU time used by the corresponding task in milliseconds.
If the CPU time cannot be determined because the DBH is running under a different
ID than the monitor or the task is not known to the system, for example, then
“**********” is output.
420
U22418-J-Z125-6-76
SESMON
DBH form SYSTEM THREADS
The DBH form SYSTEM THREADS
The form provides information on the currently active write threads.
================================================================================
>>> SYSTEM THREADS <<<
V03.2A00
DBH: X
CNF: Z
Time: 15:52:13
Write Threads
Number
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Blocks written total
36
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Blocks written IV
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version
DBH
NAM identifier of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form is output
The currently active write threads are displayed in this form. The maximum number of lines
displayed corresponds to the number of write threads specified by means of the DBH option
SYSTEM-THREADS (see page 131).
One line is output in the table for each write thread, up to a maximum of 16 lines. If more
than 15 write threads are created, the values are added together as of the 16th write thread.
Number
Sequence of the write thread
Written Blocks (Session)
Number of blocks written physically to the spaces by this thread in the DBH session
Written Blocks (IV)
Number of blocks written physically to the spaces in the last measurement period
by this thread
U22418-J-Z125-6-76
421
DBH form TRANSACTIONS
SESMON
The DBH form TRANSACTIONS
This form provides information on the number of transactions. The duration, type and
number of I/Os is output for each transaction.
================================================================================
=
>>> TRANSACTIONS <<<
V03.2A00
DBH: X
CNF: Z
Time: 16:22:21
Transactions
Number
:
Retrieval:
Update
:
Reset
:
N
1
2
3
4
5
6
7
TAC
QM124ELS
QM124ELS
QM124ELS
KSURQTT1
KSUUQCON
KSUUQDEC
KSUUQDEL
Session Interval
120
15
97
14
23
1
79
13
User-ID
ANLAGE01TSN=87L0KAASTEUG
ANLAGE01TSN=87LXKAASTEUG
ANLAGE01TSN=87LYKAASTEUG
ANLAGE01ANWEND01QTT1IP020000003B
ANLAGE01ANWEND01QCONHP0100000062
ANLAGE01ANWEND01QDECDS010000005D
ANLAGE01ANWEND01QDELHS010000005C
Session
1.08
185
Group Commit
:
Number of Locks:
Users
Open TAs
S
L
L
L
L
I/O
3732
3280
11125
141670
14015
12949
20060
:
:
Interval
0
0
80
35
L Duration Statements T
01:02:50
13 M
7 01:02:41
9 M
01:02:25
17 M
01:01:03
156 M
1 00:58:28
13 M
1 00:53:32
8 M
* 00:50:20
15 M
>>> INTERRUPT WITH KEY K2 <<<
================================================================================
LTG
TAST
Field descriptions
V
DBH version
DBH
Name of the DBH to which the data in the form relates
CNF
Name of the configuration monitored
Time
Time at which the form is output
Number
Number of completed transactions (for the session and per time period), including
internal transactions
Retrieval
Number of completed retrieval transactions (for the session and per time period),
including internal transactions
Update
Number of completed update transactions (for the session and per time period)
Reset Number of rolled-back transactions (for the session and per time period)
422
U22418-J-Z125-6-76
SESMON
DBH form TRANSACTIONS
Group Commit / Session
Average number of transactions involved in a group commit (for the session).
Group Commit / Interval
Average number of transactions involved in a group commit within the last time
interval.
Number of Locks / Session
Number of transaction locks for the session.
Number of Locks / Interval
Number of transaction locks per time interval.
Users Number of currently active users.
Open TAs
Number of currently open transactions.
The following outputs apply to individual transactions. A maximum of nine transactions are
output. They are sorted in ascending order according to their duration. The maximum
number of transactions to be output to SYSLST is determined by the user
(range of values: 10-999, default value: 200)
N
Unique transaction number assigned by SESMON (one digit)
TAC
UTM transaction code used to call the application program that opened this transaction (eight characters).
In the case of TIAM applications, the user ID of the application program appears
here, in the case of DCAM applications the request name.
User-ID
Identification of the user who opened the transaction (32 characters). It is output in
the following form: HOST-NAME, APPLICATION-NAME, CUSTOMER-NAME,
CONVERSATION-ID (see section “Syntax for the identification of users” on
page 205).
U22418-J-Z125-6-76
423
DBH form TRANSACTIONS
SESMON
S (State)
State of the transaction (one character):
I/O
A:
The transaction is being processed by a thread.
L:
The transaction is locked.
P:
The transaction is in the PTC state.
R:
The transaction has been rolled back.
W:
The transaction has been canceled due to a service task.
F:
The transaction has been unlocked with
INFORM-PROGRAM JOB-ID=*TSN(TSN=tsn),
MSG='component,RELEASE-USER-RESOURCES'
or the corresponding CALL-DML administration statement.
Ë (space):
The state of the transaction does not correspond to any of the above
categories.
Weighted sum of the physical inputs and outputs of this transaction. The weighted
sum is obtained by counting write accesses twice and read accesses once.
L (Lock)
Number of the transaction that locks this transaction (one digit). If the output transaction is locked by a transaction that can no longer be displayed on the screen, this
is indicated by “*” (asterisk).
Duration
Elapsed time of the transaction in the form hh:mm:ss
Statements
Number of statements executed so far in this transaction. Only those statements
received by the DBH for processing are counted. Statements that have already
been processed by the connection module or the SQL runtime system are not
counted. Chained CALL DML statements are counted as one statement.
T (Type)
Transaction type
M: DML transaction
D: DDL transaction
U: internal utility transaction
424
U22418-J-Z125-6-76
SESMON
Layout of output to a file
7.5 Layout of output to a file
The SESMON output file is a SAM file with a block size of 32768 bytes
(BLKSIZE=(STD,16)). The records have a variable format (RECFORM=V).
The file can contain the following record types:
–
–
–
–
–
configuration records (record identifier: “KON”)
option records (record identifier: “OPT”)
CNF records (record identifier: “CNF”)
DCN records (record identifier: “DCN”)
DBH records (record identifier “DBH”).
The SESMON output file has the following structure:
KON record
[OPT records] (as many OPT records as DBHs in the evaluation)
[CNF record]
[DCN record]
[DBH records] (max. 10 records)
[KON
[OPT
[CNF
[DCN
[DBH
record] ——————————————————————————————————————————————————————————
records] —————————————————————————————————————————————————————————
record] ———————————————————————————————————————————————————————————
record] ——————————————————————————————————————————————————————————
records] —————————————————————————————————————————————————————————
(1)
(2)
(3)
(4)
(5)
[KON
[OPT
[CNF
[DCN
[DBH
.
.
record] ——————————————————————————————————————————————————————————
records] —————————————————————————————————————————————————————————
record] ———————————————————————————————————————————————————————————
record] ——————————————————————————————————————————————————————————
records] —————————————————————————————————————————————————————————
(1)
(2)
(3)
(4)
(5)
(1)
The KON record is only output again if the contents of fields in the KON record have
changed.
(2)
Only those OPT records in which the contents of fields have changed are output
again.
(3)
Output after the currently set output time interval has elapsed.
(4)
Output after the currently set output time interval has elapsed.
(5)
Output after the currently set output time interval has elapsed.
U22418-J-Z125-6-76
425
Configuration record
SESMON
7.5.1 Layout of the output records
In the description of the output records below, the “Field contents” column contains a brief
description of each field output either in a form or to SYSLST. This description is largely
identical to the name of the field in the relevant form or in the SYSLST log.
You will find detailed descriptions of the fields output in forms or to SYSLST in section
“Layout of the forms” on page 391 or, in the case of fields that are only output to SYSLST,
in section “Layout of output to SYSLST” on page 439.
All distances refer to the beginning of the record length field. If the records are read in by
means of C (fread), you receive them without the four-byte long record length field. In these
cases, the distances to the beginning of the record are four bytes less than the values
specified here.
Configuration record
Distance Length
Field contents
Header:
0
2
Length
2
2
Empty
4
3
“KON” record ID (printable)
7
1
Filler
8
8
Time in STCK format
16
10
Date (yyyy-mm-dd), local time (printable)
26
8
Timestamp (hh:mm:ss), local time (printable)
34
10
Date (format yyyy-mm-dd), universal time (printable)
44
8
Time stamp (format hh:mm:ss), universal time (printable)
52
12
Filler for extensions
General values not output in a form:
64
4
Valid output time interval
68
8
Hardware type (SINF macro) (printable)
76
12
Operating system name and version (SINF macro) (printable)
88
4
Main memory in bytes (SINF macro)
92
4
Number of CPUs (SINF macro)
96
4
Number of active CPUs (SINF macro)
100
16
Filler for extensions
Table 37: Layout of the configuration record
426
(part 1 of 2)
U22418-J-Z125-6-76
SESMON
Configuration record
Distance Length
Field contents
116
4
HSI type (SINF macro) (printable)
120
8
DCAM processorname (printable)
128
8
DCN version (printable)
136
2
DCN corrections version status (printable)
138
22
Filler for extensions
Values for the SESDCN form OVERVIEW:
160
1
Name of the master DCN (printable)
161
1
Configuration (printable)
162
10
Session Begin date (yyyy.mm.dd), local time (printable)
172
8
Session Begin timestamp (hh:mm:ss), local time (printable)
180
4
Users option
184
4
Inactivity-Time option
188
4
Lock-Time option
Table 37: Layout of the configuration record
U22418-J-Z125-6-76
(part 2 of 2)
427
Option record
SESMON
Option record
Distance Length
Field contents
Header:
0
2
Length of the record
2
2
Empty
4
3
“OPT” record ID (printable)
7
1
NAM ID of the DBH to which the record refers (printable)
8
8
Time in STCK format
16
10
Date (yyyy-mm-dd), local time (printable)
26
8
Timestamp (hh:mm:ss), local time (printable)
34
30
Date (format yyyy-mm-dd), universal time (printable)
44
8
Time stamp (format hh:mm:ss), universal time (printable)
52
12
Filler for extensions
Current values:
64
8
DBH version (printable)
72
2
Corrections version status of the DBH (printable)
74
6
Filler for extensions
80
3555
DBH options (45 lines of 79 characters each) (printable)
Table 38: Layout of the option record
428
U22418-J-Z125-6-76
SESMON
CNF record
CNF record
Distance Length
Field contents or reference to the field in the form
Header:
0
2
Length of the record
2
2
Empty
4
3
“CNF” record ID (printable)
7
1
Filler
8
8
Time in STCK format
16
10
Date (yyyy-mm-dd), local time (printable)
26
8
Time stamp (hh:mm:ss), local time (printable)
34
10
Date (format yyyy-mm-dd), universal time (printable)
44
8
Time stamp (hh:mm:ss), universal time (printable)
52
12
Filler for extensions
Current values:
Values for the CNF form APPLICATIONS:
64
4
Actual Applications
68
4
Maximal Applications
Table 39: Layout of the CNF record
U22418-J-Z125-6-76
429
SESDCN record
SESMON
SESDCN record
Distance Length
Field contents or reference to the field in the form
Header:
0
2
Length of the record
2
2
Empty
4
3
“DCN” record ID (printable)
7
1
Filler
8
8
Time in STCK format
16
10
Date (yyyy-mm-dd), local time (printable)
26
8
Timestamp (hh:mm:ss), local time (printable)
34
10
Date (format yyyy-mm-dd), universal time (printable)
44
8
Time stamp (hh:mm:ss), universal time (printable)
52
12
Filler for extensions
Current values:
Values for the SESDCN form APPLICATIONS:
64
4
Actual Applications
68
4
Maximal Applications
72
8
Filler for extensions
Values for the SESDCN form CAPACITY:
80
4
Messages Fragmentation (Maximum)
84
4
Time in Pool Lock (Maximum)
88
4
Users per Application (Maximum)
92
4
Tasks per Application (Maximum)
96
4
Container per User (Maximum)
100
4
Sub TAs per User (Maximum)
104
4
Users per Catalog (Maximum)
108
4
Messages Fragmentation (Average)
112
4
Time in Pool Lock (Average)
116
4
Users per Application (Average)
120
4
Tasks per Application (Average)
124
4
Container per User (Average)
128
4
Sub TAs per User (Average)
132
4
Users per Catalog (Average)
Table 40: Layout of the SESDCN record
430
(part 1 of 3)
U22418-J-Z125-6-76
SESMON
SESDCN record
Distance Length
Field contents or reference to the field in the form
136
4
Elapsed time in contingency as a percentage of the total elapsed time (float)
140
4
Used Pool Containers
144
4
Free Pool Containers
148
12
Filler for extensions
Values for the SESDCN form OVERVIEW:
160
4
Number of SESDCNs
164
4
Number of SESAM-DBHs
168
4
Number of active Users
172
4
Number of active Applications
176
4
Number of active PTCs
180
28
Filler for extensions
Values for the SESDCN form TRANSACTIONS:
208
4
Open TAs
212
60
Filler for extensions
Cumulative values:
Values for the SESDCN form CAPACITY:
272
4
Broadcast Messages
276
4
Mail Messages
280
4
BCAM Memory Lacks
284
4
Requests for Locks
288
4
Pool Locks
292
4
Synchronous Accesses
296
4
Asynchronous Accesses
300
4
SESAM Messages up to 2 Kbyte
304
4
SESAM Messages up to 4 Kbyte
308
4
SESAM Messages up to 8 Kbyte
312
4
SESAM Messages up to 16 Kbyte
316
4
SESAM Messages up to 32 Kbyte
320
4
SESAM Messages up to 64 Kbyte
324
12
Filler for extensions
Table 40: Layout of the SESDCN record
U22418-J-Z125-6-76
(part 2 of 3)
431
SESDCN record
SESMON
Distance Length
Field contents or reference to the field in the form
Values for the SESDCN form OVERVIEW:
336
4
Number of DML-Statements
340
4
Number of Transactions
344
4
Number of Remote DML
348
20
Filler for extensions
Values for the SESDCN form TRANSACTIONS:
368
4
External Resets
372
4
External Resets per Administration
376
4
External Resets per Application
380
4
Deadlock Analysis
384
4
Deadlocks Found
388
4
Internal Resets
392
4
Internal Resets per Deadlock
396
4
Internal Resets per Inactivity
400
4
Internal Resets per Lock
Table 40: Layout of the SESDCN record
432
(part 3 of 3)
U22418-J-Z125-6-76
SESMON
DBH record
DBH record
Distance Length
Field contents
Header:
0
2
Length of the record
2
2
Empty
4
3
“DBH” record ID (printable)
7
1
NAM ID of the DBH to which the record refers (printable)
8
8
Time in STCK format
16
10
Date (format yyyy-mm-dd), local time (printable)
26
8
Timestamp (hh:mm:ss), local time (printable)
34
10
Date (format yyyy-mm-dd), universal time (printable)
44
8
Time stamp (hh:mm:ss), universal time (printable)
52
12
Filler for extensions
Current values:
Values for the DBH form I/O:
64
4
Number of Spaces
68
4
Number of Cursor Files
72
4
Number of LOG Files
76
8
Filler for extensions
84
4
4Kbyte Blocks / Written Blocks on LOG Files (float)
88
8
Filler for extensions
96
64
Filler for extensions
Values for the DBH form SERVICE TASKS:
160
4
Service Tasks Maximal
164
4
Service Tasks Actual
168
4
Service Tasks Active
172
4
Service Tasks Free
176
4
Service Tasks Load (float)
180
4
Orders Not Processed
184
4
Orders Not Fetched
188
4
Filler for extensions
Table 41: Layout of the DBH record
U22418-J-Z125-6-76
(part 1 of 5)
433
DBH record
SESMON
Distance Length
Field contents
Values for the DBH form SQL INFORMATION:
192
4
Max. SQL Cursors
196
4
Act. SQL Cursors
200
4
Plans: Number per DBH-Option
204
4
Plan Buffer: Number of Plans
208
4
Plan Buffer: Size of Primary Buffer
212
4
Plan Buffer: Occupation of Primary Buffer
216
4
Plan Buffer: Size of Secondary Buffer
220
20
Filler for extensions
Values for the DBH form SYSTEM INFORMATION:
240
4
Active Suborders for CALL DML
244
4
Active Suborders for SQL DML
248
4
Available Suborders Maximal
252
4
Available Suborders Actual
256
4
Used Suborders Maximal
260
4
Used Suborders Actual
264
8
Filler for additions
272
4
Parallel Open Spaces
276
4
Open Cursors
280
4
Work Container Maximum
284
4
Work Container Actual
288
4
Transfer Container Maximum
292
4
Transfer Container Actual
296
4
Threads Active
300
4
Threads Ready
304
4
Threads Free
308
4
Threads Waiting
312
4
Threads TA-Lock
316
4
Threads Service Task
320
4
Threads I/O
324
12
Filler for extensions
Table 41: Layout of the DBH record
434
(part 2 of 5)
U22418-J-Z125-6-76
SESMON
DBH record
Distance Length
Field contents
Values for the DBH form TRANSACTIONS:
336
4
Active users
340
4
Open TAs
344
4
Group Commit (float)
348
4
Group Commit/IV (float)
Values for the DBH form STATEMENTS:
352
4
Statements Number
356
4
Statements Active
360
4
Statements Waiting
364
20
Filler for extensions
Cumulative values:
Values for the DBH form I/O:
384
4
Log. Read on Spaces
388
4
Log. Write on Spaces
392
4
Phys. Read on Spaces
396
4
Phys. Write on Spaces
400
4
Log. Read on Spaces (System Data)
404
4
Log. Write on Spaces (System Data)
408
4
Phys. Read on Spaces (System Data)
412
4
Phys. Write on Spaces (System Data)
416
4
Log. Read on Spaces (User Data)
420
4
Log. Write on Spaces (User Data)
424
4
Phys. Read on Spaces (User Data)
428
4
Phys. Write on Spaces (User Data)
432
4
Log. Read on Cursor Files
436
4
Log. Write on Cursor Files
440
4
Phys. Read on Cursor Files
444
4
Phys. Write on Cursor Files
448
4
Phys. Read on LOG Files
452
4
Phys. Write on LOG Files
456
4
Phys. Read on DA LOG and CAT LOG
460
4
Phys. Write on DA LOG and CAT LOG
Table 41: Layout of the DBH record
U22418-J-Z125-6-76
(part 3 of 5)
435
DBH record
SESMON
Distance Length
Field contents
464
4
Phys. Read on TA LOG
468
4
Phys. Write on TA LOG
472
24
Filler for extensions
Values for the DBH form SERVICE TASKS:
496
4
Number of Orders
500
12
Filler for extensions
Values for the DBH form SQL INFORMATION:
512
4
SQL DML
516
4
UPDATE
520
4
RETRIEVAL
524
4
SQL DDL/SSL
528
4
SQL UTI
532
4
Plans: Accesses Core
536
4
Plans: Generated
540
4
Number of Calls Kernel Control
544
4
Number of Calls Catalog Manager
548
4
Number of Calls CALL DML Handler
552
4
Number of Sort Operations
556
4
Number of Calls Authentication1
560
4
Number of Calls Authorization 1
564
4
Number of Authentication Opt.1
568
4
Number of Authorization Opt.1
572
36
Filler for extensions
Values for the DBH form TRANSACTIONS:
608
4
Number of Transactions
612
4
Number of Retrieval Transactions
616
4
Number of Update Transactions
620
4
Number of Reset Transactions
624
4
Number of Locks
628
12
Filler for extensions
Table 41: Layout of the DBH record
436
(part 4 of 5)
U22418-J-Z125-6-76
SESMON
DBH record
Distance Length
Field contents
Values for the DBH form STATEMENTS:
640
4
Statements Local DML
644
4
Statements Local SQL
648
4
Statements Remote DML
652
4
Statements Remote SQL
656
16
Filler for extensions
Values not output in a form:
672
10
DBH session begin date (format yyyy-mm-dd, local time) 2
682
8
DBH session begin time (format hh:mm:ss, local time) 2
Table 41: Layout of the DBH record
1
Field is only output to SYSLST and to a file
2
Field is only output to a file
U22418-J-Z125-6-76
(part 5 of 5)
437
Layout of output to a file
SESMON
7.5.2 Example of editing the SESMON output file with C
If you want to read the records using C (fread), you receive the records without the four-byte
long record length field. In this case, you have to reduce all distances by four.
.
.
char
buf_in[32768];
/*
/*
/*
/*
/*
/*
/*
/*
/*
Buffer for reading
( 32768 (corresponding to
STD,16) is taken as the
buffer size so that the
buffer size does not have
to be changed if the length
of a record increases )
Number of characters read
File pointer
int
nread;
FILE
*dz;
.
.
/* Open file */
dz = fopen("link=sesmon","rb,type=record");
while ( !feof(dz) && !ferror(dz) )
{
/* Read a record */
nread = fread( (void *)buf_in, 1, sizeof(buf_in), dz);
if ( nread > 0 )
{
/* Edit a record that has been read */
.
.
}
}
if ( ferror(dz) )
{
/* Output error message */
.
.
}
fclose(dz);
.
.
438
*/
*/
*/
*/
*/
*/
*/
*/
*/
U22418-J-Z125-6-76
SESMON
Layout of output to SYSLST
7.6 Layout of output to SYSLST
The contents of most of the fields are explained in the descriptions of the forms (see
page 391). This section describes only those additional items that are output to SYSLST
but not elsewhere.
Page header
SESMON V03.2A00
INTERVAL: 20 SECONDS
DATE: 2003-03-09
TIME: 12:04:59
PAGE: 1
===================================================================================================================================
Hardware and software environment
The information on the hardware and software environment is output only once, at the
beginning.
>>> HARDWARE AND SOFTWARE <<<
Hardware Type: S130-K
BS2000 V14.0
Hostname: D016ZE09
Number of CPUs: 2
Number of active CPUs: 2
SESDCN
Master DCN:
Users:
0
Main Memory: 832.0 MByte
HSI-Type: XS31
Configuration: S
NATL:
LCTL:
0 min
0 min
===================================================================================================================================
U22418-J-Z125-6-76
439
Layout of output to SYSLST
SESMON
DBH options
The currently set options are output.
>>> OPTIONS <<<
1.DBH
SESAM-DBH V03.2A00
ACCOUNTING
ADMINISTRATOR
COLUMNS
CURSOR-BUFFER
DBH-IDENTIFICATION
DBH-TASKS
MSG-OUTPUT
*OFF
*ANY
800
BUFFER-SIZE=1344 , FRAME-SIZE=4
CONFIGURATION-NAME=S, DBH-NAME=0
1
MSG
=*SYSOUT, *SYSLST
OPEN-CLOSE-MSG=*NONE
OLD-TABLE-CATALOG
3
REQUEST-CONTROL
*NONE
RESTART-CONTROL
BUFFER-LIMIT:SYSTEM-DATA-BUFFER=50
BUFFER-LIMIT:USER-DATA-BUFFER=50
TALOG-LIMIT=512
LOGICAL-ROLLBACK=*IMMEDIATELY
RETRIEVAL-CONTROL
USER-DATA-ACCESS=1000
, INDEX-EVALUATION=2147483647
ABORT-EXECUTION=100000
SECURITY
PRIVILEGE-VIOLATIONS=10
SERVICE-TASKS
INITIAL=1 , MAXIMUM=64 , JOBCLASS=*STD
WORK-FILES=*PUBLIC-DISK
CAT-ID=*STD
PRIMARY-ALLOCATION=*STD
, SECONDARY-ALLOCATION=*STD
RECORDS-PER-CYCLE=*STD
SESSION-LOGGING-ID
SESSION-ID=*STD, START-NUMBER=0001
SPACES
100
SQL-DATABASE-CATALOG 10
SQL-SUPPORT
*YES
INACTIVITY-TIME=5 , CURSORS=300
INTERNAL-SORT-LIMIT=100000
PLANS=70
SUBORDERS
INITIAL=50
, MAXIMUM=50
SYSTEM-DATA-BUFFER
4032
SYSTEM-THREADS
WRITE-THREADS=1
THREADS
30
TRANSACTION-SECURITY *YES
LOCK-TIME=4 , INACTIVITY-TIME=40
MAX-ISOLATION-LEVEL=*STD
LOCK-ESCALATION:NUMBER-RECORDS=4000
LOCK-ESCALATION:PERCENTAGE-RECORDS=50
LOCK-ESCALATION:NUMBER-INDEX-VALUES=1000
TRANSFER-CONTAINER
INITIAL=224
, MAXIMUM=16000
USERS
50
USER-DATA-BUFFER
4032
WORK-CONTAINER
INITIAL=224
, MAXIMUM=224
===================================================================================================================================
440
U22418-J-Z125-6-76
SESMON
Layout of output to SYSLST
The CONFIGURATION form APPLICATIONS
>>> APPLICATIONS <<<
Application
Number of Users
Number of Tasks
Actual Applications:
1
Actual
Maximal / Actual
Maximal Applications:
64
ANWEND02
7
8
/
8
===================================================================================================================================
The CONFIGURATION form PREFETCH-BUFFERS
>>> PREFETCH-BUFFERS <<<
Appl./
TSN
TSN=1Z03
________
________
________
________
.
.
.
T
<=1KB
<=2KB
T
_
_
_
_
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
H I T R A T E
<=4KB
<=8KB <=16KB
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
<=32KB
<=64KB
>64KB
Perc.
Occ.
Max.
Occ.
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
--%
6%
0%
0%
0%
0%
60%
0%
0%
0%
0%
--%
--%
--%
--%
--%
===================================================================================================================================
The SESDCN form APPLICATIONS
A maximum of 50 transaction applications are output. The output is sorted in descending
order according to the number of active users (Number of User Actual).
>>> APPLICATIONS <<<
Application
Number of Users
Actual
Number of Tasks
Maximal / Actual
Actual Applications:
Maximal Applications:
1
64
APPLIC01
6
1 /
1
===================================================================================================================================
The SESDCN form CAPACITY
>>> CAPACITY <<<
Session Interval
Broadcast Messages :
0
BCAM Memory Lacks :
0
Mail Messages
:
7
Requests for Locks :
381
Pool Locks
:
381
Synchron Accesses :
88
Asynchron Accesses :
0
U22418-J-Z125-6-76
-
Maximum Average
Message Fragmentation :
0
Time in Pool Lock
:
4578
Users per Application :
6
Tasks per Application :
1
Container per User
:
3
Sub TAs per User
:
1
Users per Catalog
:
1
0
12
6
1
3
0
1
Elapsed Time in
Contingency
:
Used Pool Containers :
Free Pool Containers :
0.00%
554
710
441
Layout of output to SYSLST
SESAM MESSAGES:
Length
<= 2K
Session
115
Interval
-
<= 4K
1
-
SESMON
<= 8K
4
-
<= 16K
0
-
<= 32K
0
-
<= 64K
0
-
===================================================================================================================================
The SESDCN form OVERVIEW
>>> OVERVIEW <<<
Master DCN
:
Configuration : Z
Session Begin : 2003-09-08
10:04:38
Users
: 128
NATL
: 12 min
LCTL
: 8 min
Number of SESDCNs
:
Number of SESAM-DBHs
:
Number of active Users
:
Number of active Applications:
Number of active PTCs
:
1
1
7
1
0
Session Interval
88
25
9
-
Number of DML-Statements:
Number of Transactions :
Number of Remote DML
:
===================================================================================================================================
The SESDCN form TRANSACTIONS
A maximum of 200 transactions are output. They are sorted according to their duration. If a
transaction is locked by a transaction that can no longer be output, this is indicated in the
“Lock” column by two asterisks (**).
>>> TRANSACTIONS <<<
Deadlock Analysis :
Deadlock Found
:
Open Transactions :
Session Interval
0
0
7
External Resets
- Administration
- Application
:
:
:
Session Interval
0
- Internal Resets
0
- - Deadlock
0
- - NATL
- LCTL
:
:
:
:
Session Interval
6
0
6
0
-
TA-NR TAC
User-ID
S
I/O
Lock
Duration
Statements
1 EXAMPLE D016ZE07TSN=8GZNUSER0001
A
0
00:13:50
1
2 EXAMPLE D016ZE07TSN=8GZNUSER0002
A
0
00:13:31
1
3 EXAMPLE D016ZE07TSN=8GZNUSER0003
A
0
00:13:13
1
4 EXAMPLE D016ZE07TSN=8GZNUSER0004
A
0
00:12:52
1
5 EXAMPLE D016ZE07TSN=8GZNUSER0005
A
0
00:12:26
1
6 EXAMPLE D016ZE07TSN=8GZNUSER0006
A
0
00:12:07
1
7 SQLDB112 D016ZE07TSN=8G40SEDI63
A
0
00:03:14
2
===================================================================================================================================
442
U22418-J-Z125-6-76
SESMON
Layout of output to SYSLST
The DBH form I/O
>>> I/O <<<
DBH: X
Number of
Spaces
Cursor Files
2
System Data Buffer
Session Interval
260
39
16
2
82
0
11
0
66.30% 100.00%
Log. Read
Log. Write
Phys. Read
Phys. Write
Hitrate
DA-LOG/CAT-LOG
Session Interval
0
6
Phys. Read
Phys. Write
4K Blocks /
Written Blocks
LOG Files
0
0
1
3
User data Buffer
Session Interval
114
21
4
1
18
0
3
0
82.20% 100.00%
TA-LOG
Session Interval
1
8
1.00
0
1
2.12
Cursor Files
Session Interval
34
15
13
5
5
2
5
2
78.72%
80.00%
WA-LOG
Session Interval
0
0
0
0
0.00
Spaces and Cursors
Data
Name
REQUESTCUST.CATALOG
<CURSOR FILES>
REQUESTCUST.CUST
SYS
USR
SYS
USR
Log. Read
Session Interval
240
35
100
20
34
15
20
4
14
1
Log. Write
Session Interval
9
0
2
0
13
5
7
2
2
1
Phys. Read
Session Interval
74
0
17
0
5
2
8
0
1
0
Phys. Write
Hitrate
Session Interval
7
0 67.47%
2
0 81.37%
5
2 78.72%
4
0 55.56%
1
0 87.50%
LOG Files
File Name
SESAMZX.TA-LOG
$ID1.REQUESTCUST.0003.D.0001
$ID1.REQUESTCUST.0003.C.0001
Phys. Read
Session Interval
1
0
0
0
0
0
Phys. Write
Session Interval
8
1
3
1
3
0
4K Blocks /
Written Blocks
2.12
1.00
1.00
===================================================================================================================================
Field descriptions
Spaces and Cursors
This output contains a maximum of 100 entries. The entries are sorted in
decreasing order according to their number of I/Os.
Name Space name or <CURSOR-FILES>. In the case of space names, a distinction is
drawn between USR and SYS.
U22418-J-Z125-6-76
443
Layout of output to SYSLST
SESMON
Log. Read
Number of logical read accesses of the catalog space and user spaces and of the
cursor files since the database was opened and per time period
Log. Write
Number of logical write accesses of the catalog space and user spaces and of the
cursor files since the database was opened and per time period
Phys. Read
Number of physical read accesses of the catalog space and user spaces and of the
cursor files since the database was opened and per time period
Phys. Write
Number of physical write accesses of the catalog space and user spaces and of the
cursor files since the database was opened and per time period
Hitrate
Logical accesses of the catalog space and user spaces and of the cursor files as a
percentage of the total number of accesses
LOG Files
This output contains a maximum of 100 entries. The entries are sorted in
decreasing order according to their number of I/Os
File Name
File name of the LOG file
Phys. Read
Number of physical read accesses of the specified LOG file (for the session and per
time period)
Phys. Write
Number of physical write accesses of the specified LOG file (for the session and per
time period). The I/Os for RECOVER are not included here.
4K Blocks/Written Blocks
Average number of 4-Kbyte blocks written in the case of a write request
444
U22418-J-Z125-6-76
SESMON
Layout of output to SYSLST
The DBH form SERVICE ORDERS
A maximum of 100 requests are output.
All RECOVER/REFRESH requests from the listed requests then appear once again under
“RECOVER/REFRESH PROGRESS”.
>>> SERVICE ORDERS <<<
User-ID
D016ZE09TSN=6AIWDSQL
DBH: X
Order
RECOVER
TSN S Duration
6AXN A 00:01:01
===================================================================================================================================
RECOVER/REFRESH PROGRESS:
Log-File
:5OSB:$XDL1DBT4.STANCAT4.0001.D.0009
Block
TSN
23 6AXN
===================================================================================================================================
The DBH form SERVICE TASKS
>>> SERVICE TASKS <<<
Service Tasks
Orders
TSN
66WI
Maximal
1
DBH: X
Actual
1
Active
0
Free
1
Number(Session) Number(IV) Not Processed
10
6
0
Order
Number of
Orders
10
Phys. I/O
30
Load
0.00%
Not Fetched
0
Used-CPUElapsed
Time (msec) Time (msec)
141
5736
Load
2.46%
Size
(Pages)
515
Memory
Extension
1
Pages/
Extension
256.00
===================================================================================================================================
Field descriptions
A maximum of 50 service tasks are output. The output is sorted in descending order
according to the amount of CPU time used (Used-CPU-Time).
Memory Extension
Number of dynamic memory extensions in the service task
Pages/Extension
Average number of requested pages per memory extension in the service task
U22418-J-Z125-6-76
445
Layout of output to SYSLST
SESMON
The DBH form SQL INFORMATION
>>> SQL INFORMATION <<<
SQL DML
UPDATE
RETRIEVAL
SQL DDL/SSL
SQL UTI
Number of Calls
Kernel Control
Catalog Manager
CALL DML Handler
Authentication
Authorization
DBH: X
:
:
:
:
:
Session Interval
22
2
1
0
21
2
0
0
0
0
:
:
:
:
:
Session Interval
131
30
70
16
5
0
26
3
9
2
Authentication Opt. :
Authorization Opt. :
24
5
3
1
Plans
Accesses
Accesses/IV
Generated
Generated/IV
Number per
DBH-Option
:
:
:
:
23
3
3
1
:
70
Plan Buffer
Number of Plans :
Size of
Primary Buffer :
Occupation of
Primary Buffer :
Size of
Secondary Buffer:
Sort Operations :
Max. SQL Cursors :
Act. SQL Cursors :
Session Interval
1
0
1
1
Plan Generation
3
1148000
Size brutto
Secondary
Allocation
:
60
:
0
12000
32792
===================================================================================================================================
Field descriptions
Authentication
Number of authentication calls (for the session and per time period). Authentication
calls check whether the user is allowed to work with the specified authorization key.
Authorization
Number of authorization calls for DML (for the session and per time period). Authorization calls check whether the user is allowed to work with the desired database
objects (e.g. a table) in the desired way (e.g. update them).
Authentication Opt.
Number of successful authentication optimizations (for the session and per time
period)
Authorization Opt.
Number of successful authorization optimizations for DML (for the session and per
time period)
446
U22418-J-Z125-6-76
SESMON
Layout of output to SYSLST
The DBH form STATEMENTS
>>> STATEMENTS <<<
Statements
Local DML :
Local SQL :
Remote DML:
Remote SQL:
DBH: X
Session
5
53
0
0
Interval
0
5
0
0
Statements
Number :
Active :
Waiting:
0
0
0
ActivityTAC
User-ID
S
I/O Duration
Time Type
QM124ELS SYSTEM01TSN=87L0KAASTEUG
3732 01:02:50
0.00 M
QM124ELS SYSTEM01TSN=87LXKAASTEUG
L
3280 01:02:41
0.00 M
QM124ELS SYSTEM01TSN=87LYKAASTEUG
11125 01:02:25
0.00 M
KSURQTT1 SYSTEM01ANWEND01QTT1IP020000003B
141670 01:01:03
0.00 M
KSUUQCON SYSTEM01ANWEND01QCONHP0100000062 L
14015 00:58:28
0.00 M
KSUUQDEC SYSTEM01ANWEND01QDECDS010000005D L
12949 00:53:32
0.00 M
KSUUQDEL SYSTEM01ANWEND01QDELHS010000005C L
20060 00:50:20
0.00 M
===================================================================================================================================
The DBH form SYSTEM INFORMATION
>>> SYSTEM INFORMATION <<<
DBH: 0
Active Suborders
for CALL DML:
for SQL DML :
1
21
Available Suborders
Maximal:
50
Actual :
55
Parallel Open
Spaces:
Open Cursors:
5
1
Accounting
: OFF
SESCOS
: OFF
Request Control: OFF
Container
Work
Transfer
Threads
Active
1
Actual
Size
224
224
Ready
1
Free
19
Percentage
Occupation
84.82%
25.00%
Waiting
1
Used Suborders
Maximal:
Actual :
55
22
Maximal Percentage
Size Occupation
224
100.00%
16000
0.40%
TA-Lock
5
Service
Task
0
I/O
3
===================================================================================================================================
U22418-J-Z125-6-76
447
Layout of output to SYSLST
SESMON
The DBH form TASKS
>>> TASKS <<<
DBH: X
Used CPUTSN
Threads
Orders
Waits/IV
IOs/IV
Waits/IO
Time (msec)
8ENU
0
0
4647
===================================================================================================================================
The DBH form SYSTEM THREADS
>>> SYSTEM THREADS <<<
DBH: 0
WRITE THREADS
Number
Blocks Written Total
1
5374
Blocks Written Intervall
8
===================================================================================================================================
The DBH form TRANSACTIONS
>>> TRANSACTIONS <<<
Transactions
Number :
Retrieval:
Update :
Reset
:
Session
9
5
4
2
DBH: X
Interval
1
0
1
0
Users
:
Open TAs
:
Group Commit
:
Group Commit/IV :
Number of Locks :
Number of Locks/IV:
TA-NR TAC
User-ID
S
1 SQLABT98 SYSTEM01ANWEND01QMUJBS010000004C A
I/O
55926
2
0
0.00
0.00
0
0
Lock Duration Statements Type
00:00:04
181 DML
.
.
.
Locked Transactions:
TA-NR Lock-Type Object-Type Space-Name
Table-/
Index-ID
.
.
.
===================================================================================================================
448
U22418-J-Z125-6-76
SESMON
Layout of output to SYSLST
Field descriptions
A maximum of 200 transactions are output. They are sorted according to their duration. If a
transaction is locked by a transaction that can no longer be output, this is indicated in the
“Lock” column by two asterisks (**).
Type
The transaction type:
DML: DML transaction
DDL: DDL transaction
Ë (blank): the transaction type is still undefined
Locked Transactions
Only transactions marked as locked in upper part of the table. More information is
given here on the locked object.
TA-NR
Unique number of the locked transaction assigned by SESMON. This number can
be used to assign the entry to the associated entry under TA-NR in the upper part
of the table.
Lock-Type
The lock type:
– shared lock
– exclusive lock
– preannounced exclusive lock (required).
Object-Type
The object type of the locked object:
– catalog (whole database)
– space
– table
– record
– index
– SI entry (secondary index entry)
– plan (SQL access plan)
– metadata (metadata of a catalog)
Space-Name
Name of the space. It indicates the space in which the locked object is located.
– For the object types “space”, “table”, “record”, “index” and “SI entry” in the form
log.catalogname.spacename.
– For the object types “catalog” and “metadata” in the form log.catalogname.
– For the object type “plan” spaces are placed here.
U22418-J-Z125-6-76
449
Layout of output to SYSLST
SESMON
Table-/Index-ID (five decimal digits)
Internal table number when a table or record is locked, internal index number when
an index or SI entry is locked.
If the locked object is a record, the table in which the record is locked is specified
here. If the locked object is an SI entry, the index containing the locked SI entry is
specified. Blank spaces are placed here for all object types other than table, record,
index and SI entry.
The universal user can create an assignment table that assigns the correct table
name and index name to the corresponding internal table number and internal index
number. There are two ways to do this:
1. by issuing the following SQL statements for each database (see the “SQL
Reference Manual Part 1: SQL Statements”):
SELECT TABLE_SCHEMA, TABLE_NAME, TABLE_ID FROM
SYS_INFO_SCHEMA.SYS_TABLES
SELECT INDEX_SCHEMA, INDEX_NAME, INDEX_ID FROM
SYS_INFO_SCHEMA.SYS_INDEXES
2. by using the utility monitor to call the forms “SYS_INFO_SCHEMA,TABLES”
and “SYS_INFO_SCHEMA,INDEXES” for each database (see the “Utility
Monitor” manual)
450
U22418-J-Z125-6-76
SESMON
Output of statistical data via SNMP
7.7 Output of statistical data via SNMP
There are two subagents for the SNMP management of SESAM/SQL in BS2000/OSD:
●
Subagent for the management of SESAM databases in the software product SSC-BS2.
This supplies information on SESAM databases and SESAM-DBHs. This subagent is
described in detail in the manual “SNMP Management for BS2000/OSD”.
●
from SESAM/SQL-Server V3.2 onwards:
Subagent for outputting data from the performance monitor SESMON.
This subagent is referred to as SESAM-MON-Subagent.
This section provides a short introduction to the structure of an SNMP installation for
BS2000/OSD and then discusses the use of the SESAM-MON-Subagent.
U22418-J-Z125-6-76
451
Output of statistical data via SNMP
SESMON
Structure of an SNMP installation in BS2000/OSD
SNMP stands for Simple Network Management Protocol and was developed as a protocol
for network management services in the TCP/IP internet. SNMP’s range of application has
since been extended to include system management, application management and even
management of middleware products such as databases and transaction monitors.
Similarly to TCP/IP, the name SNMP does not just stand for the protocol but for the entire
management system which is based on SNMP. SNMP employs a client/server architecture,
where the management platform is the client and the management agents are the servers.
Presentation
Management Platform
Management
Application
MIB
Graphics terminal
C
O
M
M
U
N
I
K
A
T
I
O
N
SNMP
TCP/IP
network
MIB: Management Information Base
Management Agents
C
O
M
M
U
N
I
K
A
T
I
O
N
Agent
Application
MIB
Computer with any operating
system: BS2000/OSD, UNIX, PC
Figure 9: Communication between management platform and agents via SNMP
The SNMP manager (Management Application) is the software which generates the
requests to the individual agents and sends them via SNMP to the corresponding
agents.The SNMP manager displays the information received from the agent.
An SNMP agent (Agent Application) is the software which receives, executes and responds
to the requests sent by the SNMP manager. For the SNMP management in BS2000/OSD
there is an SNMP agent available in the software product SBA-BS2 which is structured
according to a master-subagent principle.
The master agent centrally performs basic tasks such as processing of the SNMP protocol,
safety functions, work distribution, etc. Each subagent is only responsible for a specific
subarea of the monitored components. The subagent communicates with the master agent.
The subagents are self-contained and can be started and terminated at any time.
Examples: HSMS subagent, FT subagent, both SESAM/SQL subagents.
In the Management Information Base (MIB), the management-specific objects of the
relevant component are defined and the object attributes are described. The MIB therefore
forms the basis of the communication between the management platform and an agent.
You will find further information in the manual “SNMP Management for BS2000/OSD”.
452
U22418-J-Z125-6-76
SESMON
Output of statistical data via SNMP
Prerequisites for using SESAM-MON-Subagents
The local computer must be embedded in an SNMP environment. This means that the
SNMP agent for BS2000/OSD (i.e. the BS2000 master agent) must be active on the
computer.
Communication between management platform and SESAM-MON-Subagent
The task of the management platform is to request the required data via the BS2000 master
agent (GET-Request) and to present it. The management platform can define refresh times
or request data directly, i.e. refresh the data in the memory pool regardless of the refresh
times (SET-Request, MIB fields sesamCnfRecCacheTime or sesamCnfRecUpdate).
The MIB is shipped as part of SESAM/SQL-Server V3.2 (File “fscSesam.my” in the library
SYSLIB.SESAM-SQL.032.SNMP-SA).
The layout of the MIB is based on the layout of the file output from SESMON
(see page 425). You will find information on the individual fields online at the management
station.
The statistical data generated by the performance monitor SESMON are supplied via the
SESAM-MON-Subagent to the management platform.
U22418-J-Z125-6-76
453
Output of statistical data via SNMP
SESMON
Starting the SESAM-MON-Subagents
The SESAM-MON subagent is a subagent which is started in the POSIX shell or in
BS2000/OSD.
The SESAM-MON subagent logs on with the BS2000 master agent, transfers its MIB to the
BS2000 master agent, sets up resources and waits for requests from the management
platform (via the BS2000 master agent).
1. Starting in BS2000/OSD:
/START-SNMP-SESAM-MON
VERSION=*STD / <product-version>
, MONJV=*NONE / <filename 1 .. 54 without-gen-vers>
, CPU-LIMIT=*STD / <integer 1 .. 32767> / *NO
, JOB-CLASS=*STD / <name 1 .. 8>
, TIMER-INTERVAL = 5 / <integer 1 .. 32767>
2. Starting in the POSIX shell with:
sesam-monagt [-t <int>]
The operand <int> corresponds to the operand TIMER-INTERVAL.
Operands
VERSION=*STD / <product-version>
Defines the version of the agent to be started.
This statement is not currently evaluated.
MONJV=*NONE / <filename 1..54 without-gen-vers>
Name of the job variable which is to monitor the agent.
The default setting is *NONE - no monitoring by a job variable.
CPU-LIMIT=*STD / <integer 1 .. 32767> / *NO
Entry of the maximum CPU runtime in seconds.
If *STD is entered, the generated default value is used.
JOB-CLASS=*STD / <name 1..8>
Job class with which the agent is started.
If *STD is entered, the generated default job class is used.
TIMER-INTERVAL=5 / <integer 1 .. 32767>
Timer interval in which the agent checks whether there are requests from the command
program. The timer interval is set as default to five seconds.
454
U22418-J-Z125-6-76
SESMON
Output of statistical data via SNMP
Starting the performance monitors
You start the SESMON performance monitor or monitors which are to operate together with
the SESAM-MON subagent as a batch job. In this case you indicate the operand
OUTPUT=*SNMP under the statement SET-MONITOR-OPTIONS (see page 384).
A performance monitor sets up resources on starting and waits for requests from the
SESAM-MON subagents.
Performance monitors and SESAM-MON subagents can be started independently.
How SESAM-MON subagents work
For a description of the working principles of the management platform and SNMP agents
work, see the manual “SNMP Management for BS2000/OSD”.
...
(2)
BS2000
Master
Agent
(1)
SESAM-MONSubagent
(SESAM/SQL)
(6)
Performance
Monitors
(SESMON)
(4)
(5)
(3)
TCP/IP network
Management
Platform
(SNMP)
Memory
Pool
Figure 10: How SESAM-MON subagents work
(1)
The SESAM-MON subagent receives via the BS2000 master agent a request to
prepare data from a management platform. The request may relate to all SESAM
applications on a computer.
(2)
The SESAM-MON subagent communicates with one or more SESAM performance
monitors via memory pools.Thus data from all SESAM applications on a computer
can be requested by the management platform. The SESAM-MON subagent uses
the different performance monitors, depending on the configuration and the DBHs.
U22418-J-Z125-6-76
455
Output of statistical data via SNMP
SESMON
To start the retrieval of information from the memory pools, the SESAM-MONsubagent transmits a signal via P1-Eventing to the appropriate performance
monitor.
(3)
The performance monitors write the result data independently into the common
memory pool.
(4)
After the result data have been written, the performance monitors notify the
SESAM-MON subagent via SOLSIG of the event identification. The SESAM-MON
subagent waits from (2) in P1 eventing.
(5)
The SESAM-MON subagent transfers the result data from the common memory
pool to the MIB and on to the management platform.
(6)
Request end for the SESAM-MON subagent.
Termination of the SESAM-MON subagent
The SESAM-MON subagent is terminated (regardless of the environment in which it was
started) in BS2000/OSD with the command STOP-SNMP-SESAM-MON (no operands) or
in the POSIX shell with:
sesam-moncmd T
The SESAM-MON subagent logs off with the BS2000 master agent, releases resources
and is terminated.
Termination of the performance monitors
You terminate the SESMON performance monitor or monitors which operate together with
the SESAM-MON subagent as described on page 388.
A performance monitor is automatically terminated when all the tasks which SESMON is to
monitor are completed.
456
U22418-J-Z125-6-76
8 Error recovery
This chapter is concerned with the recovery of errors. It describes:
●
how SESAM/SQL responds to errors
●
how the system administrator obtains the necessary diagnostics documentation when
required
U22418-J-Z125-6-76
457
Consistency checks
Error recovery
8.1 Consistency checks
The components of the SESAM/SQL DBH carry out consistency checks within their
spheres of responsibility. Inconsistencies that are found are issued to the console or
terminal and SYSLST in the form of consistency checks (central error messages).
Consistency checks are output in the form module-name: nn/gg/uu, where:
module-name
is the name of the module or component that detects the error or event.
nn
is the number of the consistency check.
gg
is the error weight.
uu
is the subnumber.
module-name, nn and gg allow the error to be localized in subsequent diagnostics.
The error weight (gg) indicates what effects the error or event has on the current session
and, in particular, the status of the databases involved. The error weight indicates whether
and, if so, what action should be taken.
Some consistency checks are output after events that are not necessarily the result of
errors and do not require any action to be taken. For example, consistency check
SESADXS XX/05/99 or SESADXS XX/40/99 is always output as a result of the CREATEDUMP administration statement.
Other consistency checks are caused by inconsistencies that the DBH can correct immediately when it is running with transaction management so that no action needs to be taken.
Still other consistency checks are the result of problems whose cause the system administrator can remove with little effort. Consistency checks that occur after a DMS error is
announced are included in this group. You should first check if the cause of the DMS error
found can be corrected.
Many consistency checks, however, are caused by errors and require precise diagnostics
to be carried out with the relevant diagnostics documentation.
If a consistency check occurs several times in a row, then the diagnostics documentation is
only generated the first time. One requirement for the suppression of a second dump is that
the same consistency check occurs two times in a row.
458
U22418-J-Z125-6-76
Error recovery
Consistency checks
The meaning of the error weight depends on which SESAM component announces the
consistency check. This can be determined based on the different message numbers:
Component
Message number
DBH
SES6000
Service task
SED9001
DBCON
SEK0001
SESDCN
SEN0001,
SEN0003
Table 42: Components and the corresponding message numbers
8.1.1 Error weights of consistency checks for message numbers SES6000
and SED9001
05
Dump created
10
Transaction rolled back
11
Transaction rolled back due to DMS error
12
Transaction rolled back with dump of application program
30
Restart due to an inconsistent system
32
Space I/O error
34
Secondary index defective
36
Table defective
37
Space defective
38
Catalog space of the database defective
39
Cat-Rec defective
40
Security error
50
Timeout during the task synchronization
80
System defective
82
System defective with system dump
83
System defective and dump in local task
88
System and current database defective
U22418-J-Z125-6-76
459
Consistency checks
Error recovery
A brief explanation follows of how the DBH responds to the different error weights when the
DBH session is running with transaction management.
For a session in which only CALL DML applications are to run, transaction management
can also be turned off. If this is done, important security functions of the DBH are deactivated, and the DBH cannot respond appropriately to consistency checks with certain error
weights. The user may then have to take more extensive action. This is described
separately under the heading “Response”.
The following table only lists consistency checks that require special action.
Consistency checks that are not listed here are to be handled according to their error
weights.
460
Consistency check
Detecting functional unit
Diagnostic documentation
SEA....: AD/gg/uu
SESADM
SESADM dump and maybe a
DBH trace
SED....: XX/gg/uu
DDL functions and Utility
functions in the DBH
SESAM dump
SYSLST of the service task
SEDFRVM: XX/gg/uu
SEDFSVM: XX/gg/uu
SESFRVM: XX/gg/uu
SESFSVM: XX/gg/uu
Free space administration of
the space or of the
DATABASE KEYS
SESAM dump
Storing of the affected spaces
DA-LOGs since the last data
backup
SEDTA..: XX/gg/uu
DDL transaction management
in the service task
SESAM dump
SYSLST of the service task
DDLTA file
SEFBM5: XX/gg/uu
SESLBV: XX/gg/uu
SESLR: XX/gg/ uu
SESSDH: XX/gg/uu
SESSPM: XX/gg/uu
SESTACT: XX/gg/uu
Transaction management
SESAM dump,
TA-LOG1,
TA-LOG2,
WA-LOG
SEL....: XX/08/uu
SEL....: XX/88/uu
DDL interpreter
SESAM dump
and catalog space
SEM....: XM/gg/uu
SESAM monitor
SESAM monitor dump
SESADXS: XX/05/99
SESADXS: XX/40/99
Administration handler after
administration statement
CREATE-DUMP or
CREATE-DUMP,STOP
SESAM dump
SESAGPM: AA/gg/uu
SESAGPC: AA/gg/uu
Logical data backup
SESAM dump,
DA-LOG,
CAT-LOG
U22418-J-Z125-6-76
Error recovery
Consistency checks
Consistency check
Detecting functional unit
Diagnostic documentation
SESCO..:XX/05/uu
Job logging
Correct DMS error in the COLOG file, restart job logging
SESLOMA: XX/gg/uu
Recovery
SESAM dump,
DA-LOGs,
CAT-LOGs,
CATALOG space,
CAT-REC file
SEU....: XX/08/uu
SEU....: XX/88/uu
Utility interpreter
SESAM dump
and catalog space
SEUTA..: XX/gg/uu
DDL transaction management
DDLTA file
Error weight 05 - Dump created
Meaning
An event has occurred during the run, but processing of a request, the transaction and the
DBH session can be continued. A dump is generated to help you to trace the source of the
error.
Examples of these events are:
– The DBH has received a defective message.
In this case the DBH sends a request to the sender task to write a dump.
– An error has occured when writing to the CO-LO file.
In this case the DBH turns off the file concerned.
The DBH session continues both during and after this error.
Response
In the case of the CO-LOG file, eliminate the cause of the DMS error. In the case of
defective message reception, save the DBH dump and the application program dump and
send this with the error message report to customer support. If the errors occurred after the
execution of EXPORT or IMPORT statements, you should also save the export file as an
additional diagnostic document.
Error weight 10 - Transaction rolled back
Meaning
During processing of a request, an error occurs that does not affect either concurrent
requests or the overall system. After rolling back the current transaction, the DBH continues
the session.
Response
Save the dump and submit the error message to customer support.
U22418-J-Z125-6-76
461
Consistency checks
Error recovery
Error weight 11 - Transaction rolled back due to DMS error
Meaning
A DMS error occurred during the processing of a job that does not affect parallel jobs or the
overall system. After rolling back the current transaction, the DBH continues the session.
Response
Eliminate the DMS error.
Error weight 12 - Transaction rolled back with application program dump
Meaning
An inconsistency between the application program and the DBH has been found that does
not affect parallel jobs or the overall system. After rolling back the current transaction, the
DBH continues the session.
Response
Save the DBH dump and the application program dump and submit with error message to
customer support.
Error weight 30 - Restart due to an inconsistent system
Meaning
An inconsistency has been detected in the system that cannot be associated with a specific
job, but that can be corrected by an internal restart. All user sessions are closed. If the
session is running without transaction management, then the session is terminated.
Response
Save the dump and submit with error message to customer support.
Error weight 32 - Space I/O error
Meaning
After an I/O error in a space the DBH executes an internal restart and rolls back all open
transactions so that the space is in a consistent state again. All user sessions are closed.
The DBH session is continued, the space remains in the session. If the session is running
without transaction management, then the affected space is taken out of operation.
Response
Eliminate the hardware problem and submit the error message to customer support. If the
session was running without transaction management, then also repair the affected space
using Media Recovery.
462
U22418-J-Z125-6-76
Error recovery
Consistency checks
Error weight 34 - Secondary index defective
Meaning
The DBH rolls back all open transactions via an internal restart. The index is marked as
defective. All user sessions are closed. The DBH session is continued without the affected
index.
Response
Rebuild the defective index Index using the RECOVER INDEX utility statement and submit
the error message to customer support.
Error weight 36 - Table defective
Meaning
A table is inconsistent. Other tables and indexes of the space are generally not affected.
The DBH rolls back all open transactions by means of an internal restart. The affected table
is marked as defective. All user sessions are closed, and the DBH session continues. The
table marked as defective can no longer be accessed.
Response
Submit the error message to customer support. If information on the space containing the
defective table is required for diagnosis, make a copy of the catalog space. Then use the
RECOVER utility statement to repair the space containing the defective table to make the
table accessible again.
Error weight 37 - Space defective
Meaning
A space is inconsistent. The DBH rolls back open transactions by means of an internal
restart. The defective space is removed from the DBH session. All user sessions are
closed. The DBH session continues.
Response
Submit the error message to customer support. If information on the defective space is
required for diagnosis, make a backup copy of it. Then use the RECOVER utility statement
to repair the defective space.
U22418-J-Z125-6-76
463
Consistency checks
Error recovery
Error weight 38 - Catalog space of the database defective
Meaning
Inconsistency in a catalog space. The DBH removes the whole database from the session,
rolls back all open transactions by means of an internal restart, closes all user sessions and
then continues the DBH session.
Response
Submit the error message to customer support. If information on the defective catalog
space is required for diagnosis, make a backup copy of the catalog space, then use the
RECOVER CATALOG_SPACE or RECOVER CATALOG ... SCOPE utility statement to
repair it. Using RECOVER CATALOG ... SCOPE PENDING has the advantage that the
defective data and index spaces are repaired in addition to the catalog space.
Error weight 39 - CAT-REC file of the database defective
Meaning
Inconsistency in the CAT-REC file of the affected database. The DBH sets the database to
ACCESS=READ, rolls back all open transactions by means of an internal restart, closes all
user sessions and then continues the DBH session.
Response
Check to see if the CAT-REC file is from a previous version, for example, or if there is a
different handling error. If possible, provide a correct CAT-REC file. If there is no handling
error, then submit the error message to customer support. If the diagnosis requires information on the defective CAT-REC file, make a backup copy of the CAT-REC file and of the
catalog space. If necessary, create a correct CAT-REC file together with customer support.
Error weight 40 - Security error
Meaning
Error in transaction management or error recovery. All files opened by the DBH are closed,
and the DBH is terminated. There is no internal restart.
Response
In a session with transaction management, initiate an external restart and submit the error
message to customer support. In a CALL DML session without transaction management,
use the resources of media recovery to repair CALL DML tables being directly updated at
the time of termination of the session. Submit the error message to customer support.
464
U22418-J-Z125-6-76
Error recovery
Consistency checks
Error weight 80 - System defective
Meaning
As a result of an error in internal system operations or administration tables, it is not
possible for the DBH session to continue in a consistent state. The DBH tries to restore
consistency to the spaces by means of an internal restart and then terminates the session.
Response
Submit a dump with error message to customer support.
Error weight 82 - System defective with system dump
Meaning
As a result of an error in coordination with the operating system, it is not possible for the
DBH session to continue in a consistent state. The DBH creates a system dump if this is
possible under its identifier and then terminates the session.
Response
Submit the dump with error message to customer support.
Error weight 83 - System defective with local dump
Meaning
As a result of an error in internal system operations that affects the data modules local to
the task, it is not possible for the DBH session to continue in a consistent state. The DBH
creates a local task dump and terminates the session.
Response
Submit the error message to customer support.
Error weight 88 - System and current database defective
Meaning
A catalog space inconsistency indicates that there is a serious error in the administration
tables of the DBH. The DBH removes the affected database from the session and then
proceeds as described for error weight 80 (system defective).
Response
Submit the error message to customer support. If information on the defective catalog
space is required for diagnosis, make a copy of the affected space. Then use the
RECOVER utility statement to repair the catalog space.
U22418-J-Z125-6-76
465
Consistency checks
Error recovery
8.1.2 Error weights of consistency checks for message numbers SEN0001,
SEN0003 and SEK0001
83
System defective
71
System bottleneck
72
DBH defective
70
Caller unknown (error in CC handling routine)
05
Invalid error weight (error in CC handling routine)
The following table shows which documents are to be obtained to diagnose a specific
consistency check and which actions may need to be taken..
Consistency check
Meaning
Diagnostic documentation
Action
SEC<***>: nn/72/uu
The communication module
DBCON of the application
program has detected inconsistencies in the interoperation with
the SESAM/SQL-DBH and
initiates a remote dump of the
DBH
Dump of application program
and remote dump of the DBH.
Send both dumps to system
customer support.
SEC<***>: nn/83/uu
SEC<***>: nn/70/uu
SEC<***>: nn/05/uu
System defective due to error in Dump,
the communication system
send dump to system customer
support
SEC<***>: nn/71/uu
Error in BS2000 services,
e.g. no more free main memory;
more precise specification in
message SEN3*** output at
same time
Dump,
if possible, eliminate the BS2000
problem,
otherwise send dump to system
customer support
If this type of consistency check occurs in a DBH or DCN task, a dump is created and the
task is terminated. A consistency check in an application program task also leads to the
creation of a dump. The corresponding application program receives CDML status 89 or
SQLSTATE 40SA8. Every additional job of this application program is also acknowledged
with status 89 or SQLSTATE 40SA8.
After a consistency check has occurred, a correction run is done for the affected common
memory pool. If another consistency check occurs during this run, then the common
memory pool is defective. A SESAM job that requires this common memory pool in order
to execute is rejected with CDML status 9E or SQLSTATE 81SC5.
466
U22418-J-Z125-6-76
Error recovery
Messages
8.2 Messages
In addition to consistency checks, SESAM/SQL offers the following messages when errors
occur:
–
DBH, SESDCN and utility messages output as system messages via BS2000
–
CALL DML status messages
–
SQL status codes (SQLSTATEs and SQLCODEs)
–
precompiler messages.
CALL DML status messages and SQLSTATES are described in the “Messages” manual.
You will find precompiler messages in the “ESQL-COBOL for SESAM/SQL-Server” manual.
8.2.1 Messages in special situations
Status dump
If a dump is requested for a CALL DML or SQL status using the administration statement
SET-DIAGNOSIS-DUMP-PARAMETER
DUMP=*ON(SELECT=*CALL-DML(STATE=<alphanum-name 2..2>)) or
SET-DIAGNOSIS-DUMP-PARAMETER
DUMP=*ON(SELECT=*SQL(SQLSTATE= <alphanum-name 5..5>)),
message SES6016 is output to inform you of the event. The same applies to a request using
the equivalent administration command OPT,DIAG,STATUS=<xx> or
OPT,DIAG,SQLSTATE=<yyyy>. The dump is written as a result.
File bottleneck
If a bottleneck occurs in one of the logging files or a DBH cursor file, a file-specific message
is output before a restart is initiated. The following applies to this situation:
File bottleneck
Message number
Inserts supplied
CAT-REC
SES6017
Catalog name
DALOG/CATLOG
SES6018
Catalog name
TALOG1/2
SES6019
-
WALOG
SES6020
-
Cursor file
SES6021
-
The DBH session is continued after a follow-up transaction restart.
U22418-J-Z125-6-76
467
Messages
Error recovery
Explanations of the file bottleneck handling
CAT-REC bottleneck or inconsistency
Meaning
There is either an inconsistency between the catalog space and the CAT-REC file or a
bottleneck has occurred while writing the CAT-REC file. The exact cause is output first,
followed by message SES6017, which announces the restart. During the restart all open
transactions are rolled back, all request sessions are closed and only the ACCESS =
*PARAMETERS (READ=*YES) access function is permitted for the affected database.
After that the DBH continues with the session.
Response
When there is enough space again or the correct CAT-REC file is available again, write
access to the database can be authorized again using the MODIFY-CATALOG-ACCESSRIGHTS administration statement.
DA-LOG/CAT-LOG bottleneck
Meaning
A bottleneck has occurred while writing the DA-LOG file or CAT-LOG file. An internal restart
is announced with message SES6018. During the restart all open transactions are rolled
back, all job sessions are closed and only the ACCESS = *PARAMETERS (READ=*YES)
access function is permitted for the affected database. After that the DBH continues with
the session.
Response
When there is enough space again, write access to the database can be authorized again
using the MODIFY-CATALOG-ACCESS-RIGHTS administration statement.
TA-LOG bottleneck
Meaning
A bottleneck has occurred while writing to one of the TA-LOG files. An internal restart is
announced with message SES6019. During the restart all open transactions are rolled
back, all job sessions are closed. This lowers the utilization of the TA-LOG files and the DBH
continues with the session.
Response
None
468
U22418-J-Z125-6-76
Error recovery
Messages
WA-LOG bottleneck
Meaning
A bottleneck has occurred while writing to the WA-LOG file. An internal restart is announced
with message SES6020. During the restart all open transactions are rolled back, all job
sessions are closed. This lowers the utilization of the WA-LOG file and the DBH continues
with the session.
Response
None
Cursor file bottleneck
Meaning
A bottleneck has occurred while writing to a CURSOR file. An internal restart is announced
with message SES6021. During the restart all open transactions are rolled back, all job
sessions are closed. This lowers the utilization of the cursor files and the DBH continues
with the session.
Response
None
U22418-J-Z125-6-76
469
Setting task switches
Error recovery
8.3 Setting task switches
Task switches are used in BS2000 to control tasks. 32 task-specific switches, which can be
set to ON or OFF, are available for each task. At the beginning of the task they are reset (to
OFF), but can be changed in the course of the task (SHOW-JOB-SWITCH, see the BS2000
manual “Commands, Volumes 1 - 5”).
SESAM/SQL uses task switches in error recovery.
Switch 11
Switch 12
–
The DBH sets this switch when errors occur that do not cause the DBH
session to abort, e.g. after errors during entry of DBH options or after a
consistency check without session abortion. After the DBH session is
terminated, a message appears, telling you that the DBH has been
terminated with an indication of the reason why.
–
Sets SESADM if a status other than “00” is returned.
–
In the case of errors that cause the DBH session to abort, the DBH sets
this switch and you receive a message to the effect that the DBH has
been terminated with an error.
–
SESADM sets this switch in the case of:
–
formal errors,
when user entries lead to abortion
(e.g. in the event of errors in the configuration file)
–
resource bottlenecks,
when the status 2B, 2I, 2M or 85 occurs
–
SYSTEM errors,
when a consistency check and/or status 89, 9K or 9E occurs.
SESADM sets task switch but not by evaluating the feedback of a
syntactically correct request.
Switch 13
470
The user can set this switch to cause a dump to be created automatically at
the end of the program.
U22418-J-Z125-6-76
Error recovery
End of session after ABEND events
8.4 End of session after ABEND events
The DBH includes STXIT routines for specific error events of the STXIT event class, such
as program errors or ABEND events (ABEND=Abnormal End).
Before an error event takes effect, the DBH executes an appropriate STXIT routine and tries
to terminate the session normally. It then issues the STOP,KEEP admission command (see
page 337f) internally. In the case of program errors, a dump is output first.
When an error event occurs in a session with transaction management, the DBH tries to
terminate in such a way that the consistency of the data is preserved. If the DBH indicates
errors by means of a job variable, an external restart may be necessary.
In a session without transaction management in which only CALL DML applications have
been running, CALL DML being directly updated at the time of termination must be repaired
by means of media recovery (see the “Core Manual”).
Irrespective of the backup function, the DBH sets switch 12 after the DBH session is terminated, and you receive a message.
U22418-J-Z125-6-76
471
Diagnostics documentation
Error recovery
8.5 Diagnostics documentation
The causes of errors are not always immediately evident. To diagnose complex errors, you
need diagnostics documentation that allows you to establish the status of the system and
follow the exact course of the session.
Main-memory dumps and log files are the essential diagnostics documents. In order to
receive the necessary documentation in the event of an error, the following BS2000
commands must be included in the sequence of commands for starting the DBH, SESDCN
or a SESAM/SQL application:
–
/MODIFY-TEST-OPTIONS DUMP=YES
The parameter DUMP=YES in the MODIFY-TEST-OPTIONS command causes each
dump to be output and a message is issued to SYSOUT.
–
/MODIFY-JOB-OPTIONS LOGGING=PARAMETERS(LISTING=YES)
The LOGGING parameter causes the request to be logged to SYSLST.
In special situations SESAM/SQL not only attempts to create a user dump but also attempts
to create a system dump as a troubleshooting aid in cases where interaction with
BS2000/OSD is involved. In order to enable this additional dump, the user ID must be
permitted to set the test privilege READ-PRIVILEGE to a value greater than 3.
If this is not possible, as an alternative, SESAM generates a user dump so that at least this
diagnostic document exists. However, error diagnosis will continue to be difficult if no
system dump is available.
You can use administration statements or commands to request certain diagnostics utilities
(see the overview on page 484). In the following description, administration statements for
administration with SESADM are preferred. However, you can of course use the corresponding administration command in ISP format instead of the administration statement
described. These administration commands are specified at the end of the descriptions of
their equivalent administration statements in the alphabetical reference section of the
manual (see overview on page 199ff).
The SESAM/SQL monitor SESMON and the SESCOSP request-logging facility also
provide information on database operation that can be useful in diagnosing errors (see
chapter “Outputting operational data with SESMON” on page 377 and chapter “Evaluating
request logging with SESCOSP” on page 341).
BS2000 diagnostic utilities, such as AID, are described in the relevant BS2000 manuals.
472
U22418-J-Z125-6-76
Error recovery
Diagnostics documentation
8.5.1 Main-memory dump
One of the most important diagnostics documents is the main-memory dump.
Normally, SESAM/SQL generates a dump automatically, but the system administrator can
also specifically request a dump.
Automatically generated dump
If a consistency check occurs as a result of a particular error situation, the DBH, SESDCN
or the affected DBCON module automatically generates a dump file of the associated task.
If necessary, SESAM/SQL also generates a dump file for service tasks (see section
“Diagnostics documents for service tasks” on page 484).
The name of the dump file contains the following variables:
userid
User ID under which the dump file is stored
jobname
Job name of the DBH, SESDCN or the application program
tsn
Task sequence number of the DBH, SESDCN or the application program
n
Consecutive number identifying the nth dump in the task
Dump file of the DBH or SESDCN task
The dump file can also be created under an alternative identifier if the join entry of the
identifier forces it.
The dump files of the DBH, service or SESDCN tasks have the following name:
$userid.DUMP[.jobname].tsn.n
Dumps of the multitasking DBH
In general the dumps of the multitasking-DBHs are generated in the start task. A dump is
created in the other DBH tasks only in a few exceptional cases (e.g. for error weight “83”).
Dump file of the application program task
The dump file can be created under an alternative ID.
The dump file is created under the start ID of the user task, and the file name is:
$userid.DUMP[.jobname].tsn.i
U22418-J-Z125-6-76
473
Diagnostics documentation
Error recovery
Remote dump
Remote dumps are dumps that occur in a communication partner. They are usually
triggered in conjunction with a separate dump in the other communication partner.
Remote dumps occur in the following cases:
–
One of the consistency checks MM/03/11, MQ/03/22 or MY/03/28 was announced and
a remote dump was created in the application program (DBCON or DCN communication component) due to a consistency check in the SESAM/SQL-DBH.
–
Message SEK9107 was output in the DBH and a remote dump generated due to a
consistency check in an application program (DBCON or DCN communication
component).
The initial dump as well as the remote dump are to be provided for diagnostic purposes.
Conditional dump
You can cause the DBH or the DBCON module of the application program to automatically
generate a dump file (conditional dump) when certain SQL DML or CALL DML messages
occur.
The name of a dump file like this is the same as that of an automatically generated dump
file (see page 473):
$userid.DUMP[.jobname].tsn.n
or
$SYSUSER.DUMP[.jobname].tsn.n.userid.
Causing a conditional dump of the DBH task to be generated
The SET-DIAGNOSIS-DUMP-PARAMETER administration statement allows you to request
the DBH, given certain prerequisites, to generate a conditional dump (see page 288). You
also use this administration statement to specify the message (SQLSTATE or CALL DML
status) upon whose occurrence the DBH is to generate the dump and, if necessary, to name
a specific user to which the dump is to relate.
After the administration statement is issued, the DBH outputs message SES6016 at each
occurrence of the SQLSTATE or CALL DML status and creates a dump file at the first occurrence. A dump file is otherwise only created if another consistency check occurs in the
meantime.
474
U22418-J-Z125-6-76
Error recovery
Diagnostics documentation
Causing a conditional dump of the application-program task to be generated
If the DBCON module of an application program is to generate a conditional dump automatically, in the case of TIAM and DCAM applications, the configuration file of the application
program must contain the following connection-module parameter:
DIAG-DUMP={(SQLSTATE=ccsss)|(STATUS=ssuu)}.
In the case of a UTM application, the connection-module parameter can also be specified
as a start parameter of the UTM application:
.SESAM DIAG-DUMP={(SQLSTATE=ccsss) | (STATUS=ssuu)}
cc
class
sss
subclass of the selected SQLSTATE
ss
main number
uu
subnumber of the undesired status
See also the “Messages” manual.
You can partially qualify SQLSTATE by entering “∗∗∗” as a subclass. You can partially
qualify STATUS by entering “∗∗” as a subnumber.
The DIAG-DUMP parameter is not available with the connection module of an application
program working with the linked-in DBH (DBCONL).
Requested dump of the DBH or SESDCN task
If you need another dump at any time during the DBH or SESDCN session in addition to
the automatically generated or conditional dumps, you can request it by means of the
CREATE-DUMP administration statement (see page 236).
The name of a requested dump file of the DBH or SESDCN task is the same as that of an
automatically generated dump file:
$userid.DUMP[.jobname].tsn.n
After the DBH administration statement CREATE-DUMP CANCEL-PROGRAM=NO is
issued, the DBH outputs the consistency check SESADXS: XX/05/99. After CREATEDUMP CANCEL-PROGRAM=YES is issued, the DBH outputs the consistency check
SESADXS: XX/40/99. The DBH then creates the dump file.
The CREATE-DUMP administration statement directed at SESDCN does not generate a
consistency check.
U22418-J-Z125-6-76
475
Diagnostics documentation
Error recovery
Other dumps
Dumps can also be generated when running SESAM/SQL that are not announced by
messages SEN0001, SEN0003, SEK0001, SED9001 and SES6000.
The dumps may be cause by:
–
Task switch 13
If task switch 13 is set, a dump is automatically generated for most of the programs of
the SESAM/SQL product when the programs terminate.
–
Consistency check of the SQL runtime system
All consistency checks of the SQL runtime system in the application program output the
following message in SQLSTATE 40SC1:
SEW40C1 INTERFACES OR SYSTEM ERROR (MODULE (&00) ((&01)))
and then generate a dump.
Relevant diagnostic documentation: SYSOUT log, dump of the application task.
476
U22418-J-Z125-6-76
Error recovery
Diagnostics documentation
8.5.2 Diagnostics traces
For the purposes of debugging and diagnostics, SESAM/SQL supports the following trace
functions:
–
the call trace
–
the message trace.
The call trace logs SQL DML and CALL DML statements of the application program and the
associated SESAM/SQL responses.
The connection module of the application program and the ESQL runtime system log the
statement immediately after their transfer from the application program and the responses
immediately before their transfer to the application program.
The message trace logs SESAM/SQL messages exchanged between the task of an application program and the task of the SESAM/SQL DBH. In addition to application-program
statements and the associated SESAM/SQL replies, the message trace also receives
internal SESAM/SQL administration information. The application program's connection
module logs the statement message just before it is sent to the DBH and the reply message
shortly after it is received.
The communication component of the DBH logs the messages of all application programs
that communicate with the DBH. It logs the statement message immediately after its receipt
and the reply message immediately before it is sent.
You can activate the trace as required. There are a number of options:
–
TRACE statement as a connection-module parameter or UTM start parameter
–
TRACE statement at the CALL DML program interface
–
DBH administration statement
–
SESDCN administration statement.
The activated traces are logged to SYSOUT and/or SYSLST.
TRACE statement as a connection-module parameter
You can cause the call trace and/or message trace to begin logging as soon as a TIAM,
DCAM or UTM application program starts. To do this, you must enter the following TRACE
statement as a connection-module parameter in the configuration file of the application
program:
U22418-J-Z125-6-76
477
Diagnostics documentation
Error recovery
TRACE,TYPE ={CALL/MSG/({CALL/MSG},...)}
[,OUTPUT={SYSOUT/SYSLST/({SYSOUT/SYSLST},...)}]
Meanings of the parameters:
TYPE
Selects the type of logging.
CALL: activates the call trace.
MSG: activates the message trace.
OUTPUT
Selects an output medium.
SYSOUT: writes the log information to SYSOUT.
SYSLST: writes the log information to SYSLST (default).
In some cases, logging is activated with a delay and the first statements of the program run
are not logged. This happens, for example, when statements lead to errors before the
configuration file can be evaluated, or when SQL statements issued at the beginning of the
program run are processed completely by the ESQL runtime system.
TRACE statement at the CALL DML program interface
In TIAM and DCAM mode, you can enter the trace statement at the CALL DML program
interface to turn call-trace and/or message-trace logging on or off during the session (see
the “CALL DML Applications” manual). In UTM mode, the TRACE statement is not
permitted at the CALL DML program interface.
DBH administration statement
You can use the SET-DBH-MSG-TRACE administration statement (see page 286) to turn
the message trace on or off during the DBH session. This administration statement also
allows you to select an output file for the log information.
SESDCN administration statement
During an SESDCN session you can turn the message trace and call trace on or off for
specific users. Two administration statements are available for this:
–
The SET-USER-MSG-TRACE statement activates the message trace (see page 304).
–
The SET-USER-CALL-TRACE statement activates the call trace (see page 300).
Both these statements also let you select an output file for the log information.
478
U22418-J-Z125-6-76
Error recovery
Diagnostics documentation
8.5.3 Diagnostic information in the DB-DIAGAREA of openUTM
The DB-DIAGAREA is a task-specific trace area into which openUTM cyclically writes trace
records. You can find more details on the DB-DIAGAREA in the openUTM manual
“Messages, Debugging and Diagnostics”.
At each call, SESAM/SQL supplies return information to openUTM which is transferred to a
trace record in the DB-DIAGAREA. This return information is stored as “DB trace information” in bytes 20-51 of the trace record.
Layout of the DB trace information for SQL requests
Byte in the
trace record
DB-DIAGAREA
Byte in the
DB trace
information
Length Meaning
20
0
1
Identifier “S” for SQL request
21
1
2
Representation of the SQL request (coded)
22
3
1
UTM operation code:
– 0x00 = start parameter input
– 0x04 = connection
– 0x08 = disconnection
– 0x0C = asynchronous disconnection
– 0x10 = user call
– 0x14 = finish DB transaction
– 0x18 = cancel transaction
– 0x1C = interrupt transaction
– 0x20 = continue transaction
– 0x24 = status of transaction
– 0x28 = preliminary end of transaction
– 0x2C = end of process
– 0x30 = interrupt process
– 0x34 = continue process
– 0x38 = restart process
Table 43: Layout of the DB trace information for SQL requests
U22418-J-Z125-6-76
(part 1 of 3)
479
Diagnostics documentation
Error recovery
Byte in the
trace record
DB-DIAGAREA
Byte in the
DB trace
information
Length Meaning
24
4
2
Class of SQL state:
– 00 = successful completion
– 01 = warning
– 02 = no data
– 07 = error in dynamic SQL
– 21 = cardinality violation
– 22 = data exception
– 23 = integrity constraint violation
– 24 = invalid cursor state
– 25 = invalid transaction state
– 26 = invalid SQL statement name
– 28 = invalid authorization specification
– 2C = invalid transaction termination
– 33 = invalid SQL descriptor name
– 34 = invalid cursor name
– 3D = invalid catalog name
– 3F = invalid schema name
– 40 = transaction rollback
– 42 = syntax error or access rule violation
– 51 = recovery errors
– 52 = errors concerning HSMS archive
– 55 = errors reported by BS2000
– 56 = BS2000 limits exceeded
– 57 = status information
– 58 = syntax error in input file
– 59 = errors found by check utility
– 81 = error in SQL environment
– 91 = resource limit exceeded
– 95 = invalid foreign transaction state
– SB = CLI specific condition
26
6
1
reserved
27
8
1
type of SESAM connection:
– 0x01 = with distributed processing
– 0x02 = local processing
28
12
4
message number
32
16
4
transactions serial number
36
20
4
pointer to actual UTAB
40
24
3
target as per distribution rule
43
27
1
DBH configuration name
Table 43: Layout of the DB trace information for SQL requests
480
(part 2 of 3)
U22418-J-Z125-6-76
Error recovery
Diagnostics documentation
Byte in the
trace record
DB-DIAGAREA
Byte in the
DB trace
information
Length Meaning
44
28
4
TSN of the DBH
48
32
1
last digit of the serial number in the CO-LOG file
49
33
3
block number in the CO-LOG file
Table 43: Layout of the DB trace information for SQL requests
(part 3 of 3)
Layout of the DB trace information for CALL-DML requests
Byte in the
trace record
DB-DIAGAREA
Byte in the
DB trace
information
20
0
3
begin of CALL DML statement
23
3
1
UTM operation code:
– as in the table on page 479
24
4
2
CALL DML state
26
6
1
status subcode
27
8
1
type of SESAM connection:
– 0x01 = with distributed processing
– 0x02 = local processing
28
12
4
message number
32
16
4
transaction serial number
36
20
4
pointer to actual UTAB
40
24
3
target as per distribution rule
43
27
1
DBH configuration name
44
28
4
TSN of the DBH
48
32
1
last digit of the serial number in the CO-LOG file
49
33
3
block number in the CO-LOG file
Length Meaning
Table 44: Layout ot the DB trace information for CALL-DM requests
U22418-J-Z125-6-76
481
Diagnostics documentation
Error recovery
Layout of the DB trace information for UTM system orders
Byte in the
trace record
DB-DIAGAREA
Byte in the
DB trace
information
Length Meaning
20
0
3
identifier “UTM” for UTM system order
23
3
1
UTM operation code:
– as in the table on page 479
24
4
2
CALL DML state
26
6
1
status subcode
27
8
1
type of SESAM connection:
– 0x01 = with distributed processing
– 0x02 = local processing
28
12
4
message number
32
16
4
transaction serial number
36
20
4
pointer to actual UTAB
40
24
3
target as per distribution rule
43
27
1
DBH configuration name
44
28
4
TSN of the DBH
48
32
1
last digit of the serial number in the CO-LOG file
49
33
3
block number in the CO-LOG file
Table 45: Layout of the DB trace information for UTM system requests
482
U22418-J-Z125-6-76
Error recovery
Diagnostics documentation
8.5.4 DBH-specific log files
CO-LOG files
In addition to the diagnostics traces, SESAM/SQL also provides the CO-LOG file for
collecting information on a DBH session. This log file is DBH-specific (see the “Core
Manual”). The DBH generates them when logging is turned on.
The CO-LOG file is a log file for request logging. You can use the SET-TUNING-TRACE
administration statement to turn request logging on and specify the data volume for the
CO-LOG file (see page 296):
SET-TUNING-TRACE TRACE=*ON(...)
You can use the same statement to terminate request logging to the CO-LOG file:
SET-TUNING-TRACE TRACE=*OFF
TA-LOG files and WA-LOG file
The transaction log files (TA-LOG files) and the restart log file (WA-LOG file) are DBHspecific files created by the DBH at the beginning of the session (see the “Core Manual”).
Consistency checks within the transaction restart require the TA-LOG files and the WA-LOG
file of the relevant session as additional diagnostics documents along with the dump file.
U22418-J-Z125-6-76
483
Diagnostics documentation
Error recovery
8.5.5 Overview of helpful administration statements
The table below lists all administration statements that are helpful for generating
diagnostics documents. The last column in the table refers you to detailed descriptions of
the administration statements and commands in the alphabetical reference section of the
manual.
Administration
statement
(SDF format)
Administration
command
(ISP format)
Administration Brief description
of
See
page
CREATE DUMP
DUMP
DBH and
SESDCN
Generates a dump.
236
SET-DBH-MSG-TRACE
TRACE
DBH
Controls the message 286
trace.
SET-DIAGNOSISDUMP-PARAMETER
OPT,DIAG,diag-spec
DBH
Controls the creation
of a user dump file.
288
SET-TUNING-TRACE
COS
DBH
Controls request
logging.
296
SET-USER-CALL-TRACE TRACE=PAR,
TYPE=CALL...
TRACE={ON|OFF...}
SESDCN
Controls logging of the 300
statements of selected
users.
SET-USER-MSG-TRACE
SESDCN
Controls the message 304
trace of selected
users.
TRACE=PAR,
TYPE=MSG...
TRACE={ON|OFF...}
Table 46: Administration statements for creating diagnostics documents
8.5.6 Diagnostics documents for service tasks
The SESAM/SQL DBH relocates CPU-intensive activities, such as the sorting of intermediate-result sets or some utility functions, as service tasks (see the “Core Manual”).
The DBH start task logs activities that occur in connection with service tasks, such as the
starting and termination of service tasks, to SYSOUT and SYSLST. Service-task-control
calls are logged in the DBH stack.
As for the DBH task, SESAM/SQL creates a dump file for service tasks when necessary
(see page 473).
484
U22418-J-Z125-6-76
Error recovery
Diagnostics documentation
When SQL messages (SQLSTATEs) occur in service tasks, after certain utility statements,
for example, diagnostics information is also stored in the following files:
File name
Meaning
catid.userid.DUMP[.jobname].tsn.i
Dump file of the DBH task
catid.userid.DUMP[.jobname].tsn.i
Dump file of the service task
catid.userid.SESAMkn.SYSLST.
yyyy.mm.ddhh:mm:ss.tsn
SYSLST log file of the DBH task
catid.userid.SESLKkn.SYSOUT.
yyyy.mm.ddhh:mm:ss.tsn
SYSOUT log file of the linked-in DBH task created
during the RECOVER.
archive-filename.SYSLST
ARCHIVE log file: for SQLSTATEs
after a COPY to tape with ARCHIVE or
after a RECOVER from tape with ARCHIVE
hsms_archiv-filename.SYSLST
HSMS log file: for SQLSTATEs
after a COPY to tape with HSMS or
after a RECOVER from tape with HSMS
catid.userid.catalog.space.EXC.C
Error file for the CHECK FORMAL utility statement
(see also page 486)
catid.userid.catalog.space.EXC.L
Error file for the LOAD utility statement
see also page 486)
catid.userid.catalog.space.EXC.U
Error file for the UNLOAD utility statement
(see also page 486)
catid.userid.SESAMkn.SYSLST.SESSTxx.tsn
SYSLST log file of the service task: for SQLSTATEs
after a COPY to tape or a RECOVER from tape
catid.userid.SESAMkn.SYSOUT.SESSTxx.tsn
SYSOUT log file of the service task: for SQLSTATEs
after a COPY to tape or a RECOVER from tape
Table 47: Files with diagnostic information for service tasks
File names
The table 47 contains the default names of all files containing diagnostics information for
service tasks. The file names contain the following components:
jobname
tsn
n
c
n
xx
yyyy.mm.ddhh:mm:ss
U22418-J-Z125-6-76
Job name of the service task
Task sequence number of the service task or DBH task
Consecutive number specifying the nth dump in the task
Configuration name (one byte)
DBH name (one byte)
Version number
Time stamp
485
Diagnostics documentation
Error recovery
8.5.7 EXPLAIN pragma
An SQL access plan is an evaluation rule for an SQL statement (see the “Core Manual”). In
certain cases, in the case of unexpectedly long response times, for example, you may need
to know the SQL access plan. For diagnostic purposes, you can use the EXPLAIN pragma
to generate a readable version of an SQL access plan (see the “SQL Reference Manual
Part 1: SQL Statements”).
8.5.8 Error files for SQL and utility statements
After SQL messages occur (SQLSTATEs), diagnostic information is stored in error files
(exception files) after the following UTILITY statements:
–
ALTER TABLE
The error file is defined in the SQL statement ALTER TABLE via the USING FILE
parameter. Amongst other things, this file contains column values for which conversion
errors resulted in data loss due to a change in data type.
See the “SQL Reference Manual Part 1: SQL Statements”.
–
CHECK-FORMAL {SPACE | TABLE}
The error file is created by SESAM/SQL when required. Amongst other things, it
contains the respective SQLSTATE which is set on detection of the first inconsistency
of the object to be checked. See the “SQL Reference Manual Part 2: Utilities”.
–
LOAD
The error file is defined in the utility statement LOAD via the USING FILE parameter. It
contains information on the erroneous records of the input file used, and indicates the
cause of the error. See the “SQL Reference Manual Part 2: Utilities”.
–
UNLOAD
The is created by SESAM/SQL as required
(see the “SQL Reference Manual Part 2: Utilities”).
The error files are SAM files whose data block length is four PAM pages. You can view the
error files using the BS2000 command SHOW-FILE or load them using the EDT.
If an SQLSTATE occurs after the CHECK FORMAL utility statement (see the
“SQL Reference Manual Part 2: Utilities”), the copy of the checked space can help in the
error analysis in addition to the error file.
486
U22418-J-Z125-6-76
9 Appendix
This chapter explains:
●
how to specify the sort sequence for CALL DML
●
password protection with SEPA
●
DA LOG formatting by SEDI70
●
the layout of the accounting information
●
Layout of the log records for SAT
●
Using FASTPAM for SESAM/SQL
●
Starting SESAM programs with /START-PROGRAM
9.1 Specifying the sort sequence for CALL DML
SESAM/SQL normally sorts intermediate-result sets of retrieval statements on the basis of
the EBCDI code, but you can change this sort sequence.
The DBH module SESFSxx (xx= version number, for SESAM/SQL V2.2 the DBH module is
called SESFS22) contains a table that specifies the sort sequence. The entries in this table
have the format XL2'nnmm', where nn and mm are characters in hexadecimal notation. An
entry in the XL2'nnmm' format specifies that the second character (mm) follows the first
character (nn) in the sort sequence. The table has a total of 255 entries, which specify the
sort sequence for all 256 characters of the EBCDI code.
If you want to specify a sort sequence other than the default, you can change the table
entries in the source file of SESFSxx. In doing this, you must note the following:
●
In the FSORT macro, you can change only entries that adhere to the format XL2'nnmm'.
●
You cannot change the number of entries in the table.
●
Each character must be assigned a unique place in the sort sequence.
U22418-J-Z125-6-76
487
Specifying the sort sequence for CALL DML
Appendix
Example
The character “a” (X'81') is to come after “A”(X'C1') in the sort sequence:
Default table
Changed table
.
.
.
.
XL2'7F80'
XL2'7F80'
XL2'8081'
XL2'8082'
XL2'8182'
XL2'8283'
XL2'8283'
.
.
.
.
XL2'C0C1'
XL2'C0C1'
XL2'C181'
XL2'C1C2'
XL2'81C2'
XL2'C2C3'
XL2'C2C3'
.
.
.
.
After changing the table, you have to compile the SESFSxx module and enter it in the
SESAM/SQL module library. For a retrieval statement issued with sorting, the module
library must contain a single module called SESFSxx at execution time.
i
488
Do not make any other changes to the table. The table is only taken into consideration during the sort if its sort sequence differs from that of the default table. Making
changes that do not affect the sort sequence is therefore a waste of time.
U22418-J-Z125-6-76
Appendix
Password protection with SEPA
9.2 Password protection with SEPA
The SESAM/SQL utility SEPA allows you to use passwords to protect a CALL DML table
against unauthorized access. The password catalog is in the same user space as the CALL
DML table. Access via the SQL interface is subject to SQL access protection.
In a table that is already protected by passwords, you can use SEPA to add, change or
delete passwords.
If the user space is password protected, the password for the file must be made
known to the task by means of the SDF command ADD-PASSWORD before SEPA
is called.
i
You back up the password catalog by backing up the user space. When recovering
the space, you can use the log files created since the last backup to apply the
modifications to the space up to the current status, but not the password catalog.
Changes to the password catalog are not recorded in the log files. It is therefore
advisable to create a SESAM backup copy of the relevant space after each change
to the password catalog.
A CALL DML table defined with SQL or migrated from a V1 database without
password protection can be accessed via the CALL interface by anyone, provided
a SEPA run has not been executed.
A CALL DML table migrated from a protected V1 database is protected by the
migrated password catalog.
9.2.1 The password-protection concept
It is possible to set up password protection for the records and attributes of CALL DML
tables. You can use a password to limit access to:
–
specific records in a table
–
specific attributes
–
a specific access mode.
The password and information on its access authorization are contained in the password
catalog. In the application program, you enter the password in the first three bytes of CALL
DML statements.
U22418-J-Z125-6-76
489
Password protection with SEPA
Appendix
The CALL DML password-protection concept makes it possible to have hierarchically structured password protection.
It makes sense to assign passwords that apply to a related set of activities:
A single password should allow users to carry out all the operations involved in a UTM
conversation or a transaction, for example.
You should also note that to execute JOIN operations, read authorization is required for the
JOIN attributes of the relevant tables. Access is only possible via the passwords of the
tables involved.
Access protection for the records in a table
Each record in a table is identified by a primary-key value.
The access authorization of a password can be assigned for the access modes read,
update and delete.
Each access mode is exclusive, but all possible combinations of the different access modes
are permitted.
The authorization provided by a password can apply to:
–
specific records or groups of records in a table
–
all the records in a table
–
all the records in a table with the exception of specific records or groups of records
If, in the “read/update” or “read and update” access modes, the password is to provide full
access to all the table records to which it applies (i.e. to all the attributes of each record), it
must be assigned global attribute authorization for these access modes. Delete authorization refers only to table records, and applies regardless of any restrictions that have been
imposed on attribute access.
Example
Record access authorization for the read access mode:
The table COMPANY contains the attributes
PERSNO, PNAME, PFNAM, PSTR, PZIP, PCITY, PBTHDAT, PDEPT, PLANG and
PSAL.
The PERSNO attribute has been defined as the primary key.
490
U22418-J-Z125-6-76
Appendix
Password protection with SEPA
The password XX1 has read authorization for the table records with the primary-key
values 013751 and 234781, and global read authorization for all the table's attributes.
PERSNO
PNAME
PFNAM
PSTR
PZIP
PCITY
PBTHDAT
PDEPT
PLANG
PSAL
013751
018392
111111
234781
333333
.
.
.
.
673241
Table 48: Read authorization for the password XX1.
The password XX2 has read authorization for all the table records except those with the
primary-key values 111111 and 333333, and global read authorization for all the table's
attributes.
PERSNO
PNAME
PFNAM
PSTR
PZIP
PCITY
PBTHDAT
PDEPT
PLANG
PSAL
013751
018392
111111
234781
333333
.
.
.
.
673241
Table 49: Read authorization for the password XX2
U22418-J-Z125-6-76
491
Password protection with SEPA
Appendix
Access protection for attributes
The access authorization of a password can be restricted to the access modes read and
update.
There is no hierarchical relationship between these two access modes; in other words,
update authorization does not include read authorization, and vice versa. However, you can
assign a password both types of authorization at the same time.
The authorization provided by a password can apply to:
–
specific attributes or ranges of attributes
–
all the attributes in the table
–
all the attributes in the table with the exception of selected attributes or ranges of
attributes
The primary key has a special role in the assignment of attribute authorization. Since
primary-key values identify table records, the primary key is not subject to access protection
for attributes. To ensure that the attribute authorization of a password also applies to the
primary key in a specific access mode, the password must also be assigned global record
authorization for this access mode.
Examples
The access authorization for attributes in the read access mode:
The password XX3 has read authorization for the attributes PNAME, PFNAM, PZIP and
PCITY and for all the table's records.
PERSNO
PNAME
PFNAM
PSTR
PZIP
PCITY
PBTHDAT
PDEPT
PLANG
PSAL
013751
018392
111111
234781
333333
.
.
.
.
673241
Table 50: Read authorization for the password XX3
492
U22418-J-Z125-6-76
Appendix
Password protection with SEPA
The password XX4 has read authorization for all attributes except PBTHDAT and PSAL,
and global read authorization for all the table's records.
PERSNO
PNAME
PFNAM
PSTR
PZIP
PCITY
PBTHDAT
PDEPT
PLANG
PSAL
013751
018392
111111
234781
333333
.
.
.
.
673241
Table 51: Read authorization for the password XX4
Combined access protection for records and attributes of a table
You can use a single password to assign access authorization for both records and
attributes. You can impose restrictions on record and attribute access that apply to the
individual access modes independently of each other. Note, however, that restrictions on
record and attribute access in the same access mode overlap.
Examples
Combined access protection in the read access mode:
The password XX5 has read authorization for the attributes PNAME, PFNAM, PZIP and
PCITY and for table records with the primary-key values 013751 and 234781.
PERSNO
PNAME
PFNAM
PSTR
PZIP
PCITY
PBTHDAT
PDEPT
PLANG
PSAL
013751
018392
111111
234781
333333
.
.
.
.
673241
Table 52: Read authorization for the password XX5
U22418-J-Z125-6-76
493
Password protection with SEPA
Appendix
The password XX6 has read authorization for all attributes in the table except for
PBTHDAT and PSAL, and for all the records in the table except for the records with the
primary-key values 111111 and 333333.
PERSNO
PNAME
PFNAM
PSTR
PZIP
PCITY
PBTHDAT
PDEPT
PLANG
PSAL
013751
018392
111111
234781
333333
.
.
.
.
673241
Table 53: Read authorization for the password XX6
The password XX7 has read authorization for the attributes PNAME, PFNAM, PZIP and
PCITY and for all the table's records except the one with the primary-key value 111111.
PERSNR
PNAME
PFNAM
PSTR
PZIP
PCITY
PBTHDAT
PDEPT
PLANG
PSAL
013751
018392
111111
234781
333333
.
.
.
.
673241
Table 54: Read authorization for the password XX7
494
U22418-J-Z125-6-76
Appendix
Overview of the SEPA statements
9.2.2 The SEPA statements
Statement
Meaning
1P0ËNAME='schema;table',
1P0 statement:
Controls program run
Format 1
GEN
SPACE='filename',
[,LIST=Y]
UPDATE
or
1P0ËNAME='schema;table',SPACE='filename',
LIST=P
Format 2
1P1 statement:
E
1P1ËGPËpassword[,AR= Y
N
E
[,AU= Y
N
E
][,OU= Y
N
E
][,OR= Y
N
E
][,OD= Y
N
]
Generates password
]
or
Deletes password
1P1ËDPËpassword[Ëpassword]...
or
Changes password
1P1ËCPËpassword-old1,password-new1
[Ëpassword-old2,password-new2]...
san
1P2ËËb
san
[Ëb
san1 san2
]...
san1 san2
1P2 statement:
Access authorization for
attributes
or
san
1P2NË[b]
[Ë
san1 san2
Table 55: Overview
U22418-J-Z125-6-76
san
]...
san1 san2
1P2N statement:
Access authorization for all
attributes except those in the
1P2N statement
(part 1 of 2)
495
Overview of the SEPA statements
Appendix
Statement
Meaning
Ëprimary-key-value
1P3ËËb
[x]
Gprimary-key-group-value
or
Ëprimary-key-value
1P3NË[b]
[x]
Gprimary-key-group-value
1P3N statement:
Access authorization for all
primary-key values except the one
specified or for all primary-key
groups except the one specified
1P4 statement:
Last value in a range
Ëprimary-key-value
1P4ËËË
1P3 statement:
Access authorization for a primarykey value or primary-key group
[x]
Gprimary-key-group-value
password[Ëpassword]...
1P5 statement:
Outputs information on passwords
1P5Ë
*
END
Table 55: Overview
496
END statement:
End of the sequence of statements
(part 2 of 2)
U22418-J-Z125-6-76
Appendix
9.2.2.1
Overview of the SEPA statements
Overview of the possible SEPA statement sequences
1P0 statement
UPDATE
1P0 statement
GEN
1P1ËDP statement
1P1ËGP statement(s),
then 1P2/1P2N, 1P3/
1P3N and 1P4 statements
as appropriate
1P1ËCP statement
END
Figure 11: Possible SEPA statement sequences after the 1P0 statement (format 1)
1P0 statement
LIST=P
1P5Ë* statement
1P5Ëpassword statement(s)
END
Figure 12: Possible SEPA statement sequences after the 1P0 statement (format 2)
U22418-J-Z125-6-76
497
SEPA: 1P0 statement
9.2.2.2
Appendix
Statement descriptions
This section contains detailed descriptions of the statements of the SESAM/SQL utility
SEPA.
1P0 statement (format 1)
The 1P0 statement specifies which functions SEPA is to execute:
GEN
1P0ËNAME='schema;table',SPACE='filename',
[,LIST=Y]
UPDATE
schema
Name of the schema
table
Name of the table
filename
File name of the space in which the table is located: the password catalog
is stored in the same space as the table.
GEN
Generates the password catalog.
UPDATE
Updates the password catalog.
LIST=Y
Lists the generated or updated passwords.
1P0 statement (format 2)
Lists the passwords for which information is to be output (1P5 statement). Only 1P5 statements are permissible after this statement.
1P0ËNAME='schema;table',SPACE='filename',LIST=P
498
schema
Name of the schema
table
Name of the table
filename
File name of the space in which the table is located. The password catalog
is stored in the same space as the table.
LIST=P
Lists the passwords in the 1P5 statements.
U22418-J-Z125-6-76
Appendix
SEPA: 1P1 statement
1P1 statement
The 1P1 statement allows you to generate, delete and rename passwords. Note the
following:
–
The 1P1 entry must begin in column 1.
–
A statement can contain a maximum of 130 characters.
–
Several 1P1ËGP, 1P1ËDP and 1P1ËCP statements can be issued.
–
Legal combinations:
– 1P1ËDP and 1P1ËCP statements
All 1P1ËDP statements must come before the first 1P1ËCP statement.
– 1P1ËDP and 1P1ËGP statements
All 1P1ËDP statements must come before the first 1P1ËGP statement.
–
Illegal combinations:
– 1P1ËCP, 1P1ËDP and 1P1ËGP statements
– 1P1ËCP and 1P1ËGP statements
1P1 statements must be entered in ascending order by password.
Generating a password and assigning global authorization
E
1P1ËGPËpassword[,AR= Y
N
E
],[OR= Y
N
E
],[AU= Y
N
E
],[OU= Y
N
E
],[OD= Y
N
]
password
The password is a three-character combination of letters, digits and special
characters; it can be specified in printable form or hexadecimal notation. For
example, the password AAA in hexadecimal notation is X'C1C1C1'.
When specifying the password in printable form, note the following:
– The password must not contain any NIL characters.
– The first character of the password must not be a blank.
– The password must not begin with the string X'.
When specifying the password in hexadecimal notation, all combinations except
X'000000', X'FFFFFF' and X'404040' are permitted.
In the LIST log, every password is listed in both printable form and hexadecimal
notation.
U22418-J-Z125-6-76
499
SEPA: 1P1 statement
Appendix
The following operands specify the type of access authorization:
AR
Reads attributes in the table records specified by OR.
OR
Reads table records; the attributes read are specified by AR.
AU
Updates attributes in the table records specified by OU.
OU
Updates table records as specified by AU.
OD
Deletes records from a table.
The following operands specify authorization values:
E
Access authorization is assigned by subsequent 1P2 or 1P3 statements for
individual attributes or records of a table.
Y
Access authorization applies to all attributes or records of a table.
N
Access authorization for all attributes and records of a table is withdrawn from the
password for the specified access mode (default).
Default function:
If no authorization value is specified for any access mode, all access authorization is
withdrawn from the password.
Example
The password ABC allows all attributes to be read but only some to be updated:
1P1ËGPËABC,AR=Y,AU=E
Deleting a password
1P1ËDPËpassword[Ëpassword]...
password
Specify the password to be deleted. If you want to delete several passwords, you
must separate them with blanks. You can enter the passwords in printable form or
hexadecimal notation (see the description of the GP operand).
Example
The passwords AXZ and TTP are to be deleted:
1P1ËDPËAXZËTTP
500
U22418-J-Z125-6-76
Appendix
SEPA: 1P1 statement
Changing a password
1P1ËCPËpassword-old1,password-new1[Ëpassword-old2,password-new2]...
You can enter the passwords in printable form or hexadecimal notation (see the description
of 1P1ËGP).
You can use a single 1P1 statement to enter several changes, separated by blanks.
A change cannot be specified separately in two different 1P1 statements.
Example
The password ABB is to be changed to BBB:
1P1ËCPËABB,BBB
U22418-J-Z125-6-76
501
SEPA: 1P2 statement and 1P2N statement
Appendix
1P2 statement and 1P2N statement
You use these statements to assign access authorization for specific attributes.
Since the primary key is not subject to access protection for attributes, the associated
symbolic attribute name AAA cannot be specified in 1P2 or 1P2N statements. In the case
of a compound key, however, it is possible to use 1P2/1P2N statements to assign access
authorization to a password for the individual compound-key attributes (symbolic attribute
names: AAB, AAC, AAD,...).
After a 1P1 statement you can specify either 1P2 statements or 1P2N statements, but not
both.
You can also use a 1P2/1P2N statement to assign authorization for individual attributes that
the table does not yet contain but that are to be added subsequently.
The 1P2 statement allows you to assign access authorization for specific attributes or
ranges of attributes.
san
san
1P2ËËb
[Ëb
san1 san2
]...
san1 san2
This statement assigns access authorization for all attributes in the table except for those
attributes or ranges of attributes whose symbolic attribute names are specified in the
statement.
b
san
1P2NË[b]
Ë
b
san
[Ë
san1 san2
]...
san1 san2
Type of authorization:
1 for read
2 for update
3 for read and update
In the 1P2N statement, you must always specify the type of authorization. If several
1P2N statements are entered for one 1P1 statement, only the first 1P2N statement
can contain the authorization type. It is specified before the first attribute name or
range. This then applies to all subsequent attributes in the 1P2N statement and all
subsequent 1P2N statements that belong to the same 1P1 statement.
502
U22418-J-Z125-6-76
Appendix
SEPA: 1P2 statement and 1P2N statement
san
Symbolic attribute name
san1san2
For san1, specify the name of the first attribute in a range of attributes.
For san2, specify the name of the last attribute in the range.
If you specify several symbolic attribute names, they must be in ascending order.
Ranges of attributes must not overlap.
Example 1
The attribute with the symbolic name ABC can only be read, the range from CCB to
DFG can only be updated, and FGH can be read and updated:
1P2ËË1ABCË2CCBDFGË3FGH
Example 2
All attributes can be read except ABC, CAF, CAK to DKV, MAN, VWX and XX1. Access
authorization for this is specified in two 1P2N statements:
1P2NË1ABCËCAFËCAKDKV
1P2NËMANËVWXËXX1
U22418-J-Z125-6-76
503
SEPA: 1P3 statement and 1P3N statement
Appendix
1P3 statement and 1P3N statement
You use these statements to assign access authorization for individual records or groups of
records in a table.
The records of a table are identified by primary-key values or primary-key-group values.
After a 1P1 statement you can specify either 1P3 statements or 1P3N statements, but not
both. You can also use a 1P3/1P3N statement to assign authorization for the primary-key
values of records the table does not yet contain but that are to be added subsequently.
The 1P3 statement allows you to assign authorization for an individual record or a group of
records in a table.
Ëprimary-key-value
1P3ËËb
[x]
Gprimary-key-group-value
The 1P3N statement assigns the access authorization b for all the records in a table except
for those specified in the statement.
Ëprimary-key-value
1P3NË[b]
[x]
Gprimary-key-group-value
b
Type of authorization:
1 for read
2 for update
3 for read and update
4 for delete
5 for read and delete
6 for update and delete
7 for read, update and delete
The type of authorization must always be specified for the 1P3 statement. If you
specify several 1P3N statements after a 1P1 statement, only the first can contain
the authorization type. This authorization type then applies to all subsequent 1P3N
statements belonging to the same 1P1 statement.
504
U22418-J-Z125-6-76
Appendix
SEPA: 1P3 statement and 1P3N statement
primary-key-value
Specify a primary-key value (up to 64 characters). You can specify it in printable
form or hexadecimal notation. For example, the primary-key value P19350 is
X'D7F1F9F3F5F0' in hexadecimal notation.
If the primary-key value begins with the string X', it must be specified in hexadecimal
notation.
If the primary key is longer than 64 characters, a follow-up statement is required
(see x below). In this case, the primary-key value can only be specified in printable
form.
G
The operand G applies access authorization to a primary-key group.
primary-key-group-value
Specify a primary-key-group value (up to 64 characters). It can be entered in
printable form or hexadecimal notation. If it is longer than 64 characters, a follow-up
statement is required. In this case, it must be specified in printable form.
x
Flag indicating there is a follow-up statement:
You can use a maximum of 64 characters in a single 1P3/1P3N statement for the
primary-key value. If it is longer, you must enter a 65th character (x) and enter the
rest of the primary-key value in one or more follow-up statements.
Structure of a 1P3 follow-up statement, for example:
1P3ËËËËpsw[x]
Each 1P3/1P3N follow-up statement can contain up to 64 characters. If the primarykey value is too long for the follow-up statement, you again enter a 65th character
(x) to indicate that there is a further follow-up statement.
Example
A primary-key value has 200 characters. The character @ is used to indicate
there is a 1P3 follow-up statement:
Statement
1P3ËËbËz...z@
z...z are the first 64 characters of
the primary-key value.
1st follow-up statement 1P3ËËËËz...z@
z...z are the next 64 characters of
the primary-key value.
2nd follow-up statement 1P3ËËËËz...z@
z...z are the next 64 characters of
the primary-key value.
3rd follow-up statement 1P3ËËËËzzzzzzzz zzzzzzzz are the last 8 characters
of the primary-key value.
U22418-J-Z125-6-76
505
SEPA: 1P4 statement
Appendix
1P4 statement
You use this statement to specify the last value in the range of primary keys or primary-key
groups whose first value was specified in a preceding 1P3 statement.
You can specify the primary-key value in printable form or hexadecimal notation (see the
1P3 statement). Ranges of primary keys or primary-key groups in 1P3/1P4 statements
must not overlap.
Ëprimary-key-value
1P4ËËË
[x]
Gprimary-key-group-value
primary-key-value
Last value in the range of primary keys
primary-key-group-value
Last value in the range of primary-key groups
x
Flag indicating there is a follow-up statement (analogous to the 1P3 follow-up
statement)
Example
The primary-key values in the range from ALPHA to BETA can only be read:
1P3ËË1ËALPHA
1P4ËËËËBETA
506
U22418-J-Z125-6-76
Appendix
SEPA: 1P5 statement/END statement
1P5 statement
You use this statement to output information on passwords.
The 1P5 statement is only permissible if you have specified the 1P0 statement in format 2.
password[Ëpassword]...
1P5Ë *
password
You can enter the password in printable form or hexadecimal notation (see the 1P1
statement). Up to 17 passwords can be specified.
*
Outputs information on all passwords.
The following information is listed for each password specified in a 1P5 statement:
–
name (printable and hexadecimal)
–
information on global authorization for primary-key values (primary-key values are listed
in printable form and in hexadecimal notation)
–
information on global authorization for attributes
–
information on any individual restrictions imposed on specific attributes
–
information on any individual restrictions imposed on specific primary-key values.
END statement
You use this statement to terminate the sequence of statements.
END
U22418-J-Z125-6-76
507
SEPA: Example of password generation
Appendix
9.2.3 Example of password generation
All types of access are to be permitted to the CALL TABLE table COMPANY provided the
correct password (ppp) is entered. If the SEPA statements are entered in a separate file,
this file and a start procedure could have the following structure:
Input file
1P0 NAME='COMPANY_SCH;COMPANY',SPACE='CALL_COMPANY.COMPANY',GEN
1P1 GP ppp,AR=Y,OR=Y,AU=Y,OU=Y,OD=Y
END
Start procedure
/BEGIN-PROCEDURE LOGGING=ALL
/OPTION MSG=FHL
/ASSIGN-SYSLST TO-FILE=LST.SEPA
/MOD-MSG-ATTRIBUTES TASK-LANGUAGE=D
/ASSIGN-SYSDTA TO-FILE=input-file
/START-SESAM-CDML-AUTHORIZATION
/SET-JOB-STEP
/ASSIGN-SYSLST TO-FILE=*PRIMARY
/END-PROCEDURE
where:
508
ppp
is the password
input-file
is the name of the input file for the SEPA statements
U22418-J-Z125-6-76
Appendix
SEDI70: Formatting
9.3 DA-LOG formatting by SEDI70
The SEDI70 program formats CAT-LOG and DA-LOG files (logging files for the catalog
space and user spaces) for printing according to the input parameters of the media recovery
files.
The following information is important to interpret the output:
●
The CAT-LOG file contains all changes to the metadata that are applied to the catalog
during a DBH session. These changes are logged as DMLs (INSERT, UPDATE,
DELETE) because the metadata is stored in the catalog as a table.
Changes to the metadata can be made
–
–
by a user (e.g. by CREATE TABLE, ALTER TABLE ...)
by the system (e.g. by entering the DA-LOG files in the
SYS_INFO_SCHEMA.SYS_DA_LOGS or by changing the “time of change” time
stamp in the SYS_INFO_SCHEMA.SYS_SPACES during the first update of a
space within a DBH session).
●
All changes to the user tables that are made during a DBH session to user spaces when
the logical data backup is switched on are logged in the DA-LOG file.
There is a system table in the user space with the table ID 1. It is used to ensure consistency between the catalog space and user space.
●
CAT-LOG and DA-LOG files are divided into “units”. The units contained in a CAT-LOG
or DA-LOG file can be found in the CAT-REC file or in the
SYS_INFO_SCHEMA.SYS_DA_LOGS. New units are created by the following, for
example:
– opening a file (beginning of session, CAT-LOG/DA-LOG switch, COPY CATALOG)
– logical starting points (COPY SPACE)
– selection (LOAD).
●
Changes are logged in the order in which the were made. A change is only written
permanently by a COMMIT WORK. The association between the change and the corresponding COMMIT WORK is done using the 28-byte user ID. If a restart label (unit
record) exists between the change and a follow-up COMMIT WORK, then the change
is rolled back.
U22418-J-Z125-6-76
509
SEDI70: call
Appendix
Changes that have the same user ID and the same statement ID were produced by an
external statement. For example, an update statement with 100 matches produces 100
update records in the log files. If an error occurs in the nth match (e.g. a data error), then
a cancel statement takes effect. This means that all update increments with the same
user ID and the same statement ID are invalid. The transaction boundary is not affected
by this, i.e. it is still open and a COMMIT WORK later on commits all remaining changes
of the user.
●
i
The following always applies:
Output sent to SYSOUT and SYSLST is not upwardly compatible.
Output layout may vary depending on the version used.
9.3.1 SEDI70 call
Start command sequence
/START-SESAM-LOG-FILE-EVAL
Starts the SEDI70 with the start command START-SESAM-LOG-FILE-EVAL (see section
“Starting SESAM/SQL programs via start commands” on page 31).
510
U22418-J-Z125-6-76
Appendix
SEDI70: CREATE-REPORT
9.3.2 SEDI70 input parameters
SEDI70 expects the input parameters from SYSDTA.
The higher-level parameter CREATE-REPORT
Function
You use CREATE-REPORT to specify which file SEDI70 is to evaluate, where SEDI70 is to
write the report to, which data SEDI70 is to evaluate and how the SEDI70 statistics should
look.
If you enter the name of the log file (DA-LOG file) to be evaluated in the appropriate SDF
screen and send it off with the default settings, SEDI70 produces a report on all the data
and outputs it to SYSLST.
The input for SEDI70 is entered in the SDF format in the same manner as the input for
SESAM-DBH options and the SESCOSP control.
All the operands of CREATE-REPORT are described below as individual parameters.
CREATE-REPORT
INPUT-FILE =
,OUTPUT =
,SELECT =
Operands
INPUT-FILE =
See “The individual parameter INPUT-FILE” on page 512
OUTPUT =
See “The individual parameter OUTPUT” on page 514
SELECT =
See “The individual parameter SELECT” on page 515
U22418-J-Z125-6-76
511
SEDI70: CREATE-REPORT
Appendix
The individual parameter INPUT-FILE
Function
You use this parameter to specify the file name of the log file that SEDI70 is to evaluate.
INPUT-FILE
= <filename 1..54_without_generation_version> / *PARAMETERS(...)
*PARAMETERS(...)






USER-IDENTIFICATION = *OWN / <name 1..8>
,CATALOG-NAME = <filename 1..18 without-all>
,COPY-NUMBER = 1 / <integer 1..9999>
,LOG-FILE-TYPE = *DA-LOG / *CAT-LOG
,SUB-NUMBER-FROM = 1 / <integer 1..9999>
,SUB-NUMBER-TO = 9999 / <integer 1..9999>
Operands
INPUT-FILE =
Name of the log file that SEDI70 is to evaluate.
INPUT-FILE = <filename 1..54_without_generation_version>
Explicit specification of the log file.
INPUT-FILE = *PARAMETERS(...)
Specify one or more log files that belong together by entering the database name, backup
copy number, type and a range of file subnumbers.
This will designate the following log files:
[$user-id.]catalog.cccc.x.ffff
...
[$user-id.]catalog.cccc.x.tttt
512
U22418-J-Z125-6-76
Appendix
SEDI70: CREATE-REPORT
The following terms have the following meanings:
user-id:
BS2000 user ID under which the log files are stored (see the operand
USER-IDENTIFICATION)
catalog:
Name of the catalog (see the operand CATALOG-NAME)
cccc:
Backup copy number (see the operand COPY-NUMBER)
x:
Type of job log file (see the operand LOG-FILE-TYPE)
ffff:
“From” file subnumber (see the operand SUB-NUMBER-FROM)
tttt:
“To” file subnumber (see the operand SUB-NUMBER-TO)
USER-IDENTIFICATION = *OWN / <name 1..8>
BS2000 user ID under which the log files are stored.
USER-IDENTIFICATION = *OWN
The log files are stored under the current BS2000 user ID.
USER-IDENTIFICATION = <name 1..8>
The log files are stored under the specified BS2000 user ID.
CATALOG-NAME = <filename 1..18 without-all>
Name of the database.
COPY-NUMBER = 1 / <integer 1..9999>
Number of the backup copy.
LOG-FILE-TYPE = *DA-LOG / *CAT-LOG
Type of log file.
The name component used is D when *DA-LOG is specified and C when *CAT-LOG
C is specified.
SUB-NUMBER-FROM = 1 / <integer 1..9999>
“From” file number.
SUB-NUMBER-TO = 9999 / <integer 1..9999>
“To” file number.
The SUB-NUMBER-FROM must be smaller than or equal to the SUB-NUMBER-TO.
U22418-J-Z125-6-76
513
SEDI70: CREATE-REPORT
Appendix
The individual parameter OUTPUT
Function
You use this parameter to specify whether SEDI70 is to write the formatted data to SYSLST
or a file.
OUTPUT
= *SYSLST / <filename 1..54>
Operands
OUTPUT = *SYSLST
Writes the report to SYSLST.
OUTPUT = <filename 1..54>
Writes the report to the specified file.
i
514
The specified file is always assigned to SYSLST internally. The output is thus
always sent to the SYSLST system file. At the end of the program run SYSLST is
reset to the primary assignment even when it already had an assignment
beforehand.
U22418-J-Z125-6-76
Appendix
SEDI70: CREATE-REPORT
The individual parameter SELECT
Function
You use this parameter to specify which information is to be output by SEDI70.
SELECT
= *ALL / *PARAMETERS(...)
*PARAMETERS(...)


USERS =
,SPACE-ID =
Operands
SELECT = *ALL
All information is output.
SELECT = *PARAMETERS(...)
The options that allow you to limit the data to be collected are described below individually
as SELECT parameters. The information may be limited to one or more timesharing or
application users as well as to one space or table.
U22418-J-Z125-6-76
515
SEDI70: CREATE-REPORT
Appendix
The SELECT parameter USERS
Function
You use this parameter to specify the timesharing and application users to be output.
USERS
= *ALL / *BY-SELECT(...)
*BY-SELECT(...)



HOST-NAME = *NONE / <text 1..8>
,APPLICATION-NAME = *NONE / *TSN (TSN=<alphanum-name 4..4>) / <text 1..8>
,CUSTOMER-NAME = *NONE / <text 1..8>
Operands
USERS = *ALL
All timesharing and application users are evaluated.
USERS = *BY-SELECT(...)
Only specific timesharing and application users are evaluated. You must specify a value
other than *NONE for at least one operand if *BY-SELECT is specified.
HOST-NAME =
The information to be output is selected by specifying a host system.
HOST-NAME = *NONE
The information to be output is not limited to that on a specific host system.
HOST-NAME = <text 1..8>
Only the information from the user of the specified host system is output. The desired
host system is identified by its symbolic host name. In non-distributed processing,
HOMEPROC always identifies the local system.
APPLICATION-NAME =
The information to be output is selected by specifying an application.
APPLICATION-NAME = *NONE
The information to be output is not limited to that of a specific application.
APPLICATION-NAME = *TSN(TSN=<alphanum-name 4..4>)
In TIAM mode you select the application by specifying the task sequence number
(TSN). This means that only the information that comes from the TIAM user with the
specified TSN is output.
516
U22418-J-Z125-6-76
Appendix
SEDI70: CREATE-REPORT
APPLICATION-NAME = <text 1..8>
Only the information that comes from the user of the specified application is output. In
the openUTM mode you select the application by specifying the openUTM application
name and in the DCAM mode by specifying the DCAM application name.
CUSTOMER-NAME =
The information to be output is selected by specifying a user, i.e. by specifying the user
name.
CUSTOMER-NAME = *NONE
The information to be output is not limited to that of a specific user.
CUSTOMER-NAME = <text 1..8>
Only the information from the user of the specified user name is output.
The name of the user is independent of the user's mode: In openUTM mode the user is
specified with the KDCSIGN name, in TIAM mode with the program name and in DCAM
mode with any name.
U22418-J-Z125-6-76
517
SEDI70: CREATE-REPORT
Appendix
The SELECT parameter SPACE-ID
Function
You use this parameter to specify the space to be output.
SPACE-ID
= *ALL / <integer 1..200>(...)
<integer 1..32767>(...)

TABLE-ID = *ALL / <integer..32767>
Operands
SPACE-ID = *ALL
The information to be output is not limited to a certain space.
SPACE-ID = <integer 1..200>(...)
Output is limited to the space with the specified space number.
The association between the space number and the space name can be determined from
the catalog tables SYS_INFO_SCHEMA.SYS_SPACES and
SYS_INFO_SCHEMA.SYS_TABLES from the SPACE_ID and SPACE_NAME fields,
respectively.
Only the information pertaining to the specified space is output.
TABLE-ID =
The information to be output is limited to that of the specified table.
TABLE-ID = *ALL
The information to be output is not limited to that of a table.
TABLE-ID = <integer 1..32767>
The information to be output is limited to that of the table with the specified table
number.
The association between the table number and the table name can be determined from
the catalog table SYS_INFO_SCHEMA.SYS_TABLES from the TABLE_ID and
TABLE_NAME fields.
Only the information pertaining to the specified table is output.
518
U22418-J-Z125-6-76
Appendix
SEDI70: CREATE-REPORT
Example
In the following the SEDI70 is started, where
–
–
–
the corresponding log files to be evaluated,
the output format (SYSLST) and
the information to be output
are specified.
/SET-PROCEDURE-OPTIONS /
LOGGING-ALLOWED = *YES, /
DATA-ESCAPE-CHAR = *STD
/DECLARE-PARAMETER /
NAME = ( SYSLST
( 'LST.SEDI70' ), /
USER-IDENTIFICATION ( '*OWN' ), /
CATALOG-NAME
( *PROMPT ), /
COPY-NUMBER
( '0001' ), /
LOG-FILE-TYPE
( '*DA-LOG' ), /
SUB-NUMBER-FROM
( '0001' ), /
SUB-NUMBER-TO
( '0001' ), /
OUTPUT
( '*SYSLST' ), /
USERS
( '*ALL' ), /
SPACE-ID
( '*ALL' ) )
/
/MODIFY-TERMINAL-OPTIONS /
OVERFLOW-CONTROL = *NO-CONTROL
/
/WRITE-TEXT '*********************************************************'
/WRITE-TEXT 'Start "SEDI70"'
/WRITE-TEXT '********************************************************'
/
/REMARK 'Meaning of the procedure parameters'
/REMARK 'SYSLST: SYSLST assignment for the procedure'
/REMARK '&USER-IDENTIFICATION: User ID under which the log files are
stored'
/REMARK '&CATALOG-NAME: Name of the catalog that the log files belong to'
/REMARK '&COPY-NUMBER: Number of the copy that the log files belong to'
/REMARK '&LOG-FILE-TYPE: Type of log files (*CAT-LOG or *DA-LOG)'
/REMARK '&SUB-NUMBER-FROM: Subnumber of the 1st log file to evaluate'
/REMARK '&SUB-NUMBER-TO: Subnumber of the last log file to evaluate'
/REMARK '&OUTPUT: Name of the file that SEDI70 writes its output'
/REMARK '&USERS: User for which the report is to be created'
/REMARK '&SPACE-ID: Space ID for which the report is to be created '
/
/ASSIGN-SYSDTA TO-FILE = *SYSCMD
/ASSIGN-SYSLST TO-FILE = &SYSLST
U22418-J-Z125-6-76
519
SEDI70: CREATE-REPORT
Appendix
/
/START-SESAM-LOG-FILE-EVAL
//CREATE-REPORT INPUT-FILE = *PARAMETERS ( //
USER-IDENTIFICATION = &USER-IDENTIFICATION, //
CATALOG-NAME = &CATALOG-NAME, //
COPY-NUMBER = &COPY-NUMBER, //
LOG-FILE-TYPE = &LOG-FILE-TYPE, //
SUB-NUMBER-FROM = &SUB-NUMBER-FROM, //
SUB-NUMBER-TO = &SUB-NUMBER-TO ), //
OUTPUT = &OUTPUT, //
SELECT = *PARAMETERS ( //
USERS = &USERS, //
SPACE-ID = &SPACE-ID )
/
/MODIFY-TERMINAL-OPTIONS /
OVERFLOW-CONTROL = *USER-ACKNOWLEDGE
520
U22418-J-Z125-6-76
Appendix
SEDI70: report output
9.3.3 SEDI70 report output
Every list that SEDI70 outputs has the following basic structure:
1. General information
–
Window line
–
Title line
2. File identification records
3. Variable part of the list
9.3.3.1
General information
The output of the SEDI70 input parameters and the SESAM version of the DBH identifier is
structured the same for all reports.
Window line
A window line is output at the beginning of a page of an output file.
Example
SEDI70/SQL
AUSWERTUNG
VERS. 3.2A00
11:58:58
TSN:6JYY ID.:SQLDB111 SEDI70 - LOGGINGDATEI 2003-06-06
PAGE
1
(It appears in a single line without a carriage return.)
U22418-J-Z125-6-76
521
SEDI70: report output
Appendix
Title line
The title line follows the window line.
Example
USER-IDENTIFICATION
STMT
ACTION
SPC
TAB
REC-NO
Explanation
9.3.3.2
Heading
Information specified
USER-IDENTIFICATION
User ID
STMT
Statement identifier
ACTION
Type of change: INSERT/UPDATE/DELETE
SPC
SPACE identifier
TAB
Table identifier
REC-NO
Internally assigned record number
File identification records
A description of the file identification records follows. File identification records appear when
a new log unit has been started
–
–
–
at the beginning of a new DBH session
at the beginning of a new file (previous one was full, RECOVER statement, DAW, etc.)
when a backup copy of a space is made.
Examples
SEDI70/SQL VERS. 3.2A00
TSN:6JYY ID.:SQLDB111 SEDI70 - LOGGINGDATEI - AUSWERTUNG
11:58:58
2003-06-06 PAGE
1
BENUTZER-IDENTIFIKATION
STMT
AKTION SPC TAB
SATZNR
***********************************************************************************************************************************
**********
DATEINAME: STANCAT1.0232.C.0001
BLOCK: 00000001
**********
**********
DBH-SESSION MIT TRANSACTION-SECURITY = *YES
2003-06-05 17:11:01 LOC **********
***********************************************************************************************************************************
The following file identification record appears after a DBH restart when a new file is started:
SEDI70/SQL VERS. 3.2A00
TSN:6JYY ID.:SQLDB111 SEDI70 - LOGGINGDATEI - AUSWERTUNG
11:58:58
2003-06-06 PAGE
5
BENUTZER-IDENTIFIKATION
STMT
AKTION SPC TAB
SATZNR
***********************************************************************************************************************************
**********
DATEINAME: STANCAT1.0232.C.0001
BLOCK: 00000006
**********
**********
<<< D B H - R E S T A R T >>>
2003-06-05 17:11:07 LOC **********
***********************************************************************************************************************************
All transactions that are not terminated by a COMMIT are rolled back.
522
U22418-J-Z125-6-76
Appendix
9.3.3.3
SEDI70: report output
Variable part of the report
Primary data
Using the record specifications already described, the primary data changes made are
output attribute by attribute.
Example
In the following example all common data types are used (the title line was repeated for the
sake of clarity).
USER-IDENTIFICATION
STMT
ACTION SPC TAB
REC-NO
HOMEPROCTSN=492ESESAM-IS 0000000C INSERT
2
18 00000001
BAN: 0001
SAN: AAA POS#:
FCT: N VALUE:H U G O
C8E4C7D640404040404040404040404040404040
0002
AAB
0
9
00000009
0003
AAC
0
9
0009
0004
AAD
1
0
9
9F
0004
AAD
2
0
9
9F
0005
AAE
0
9
F9
0006
AAF
0
9 . 0 0 0 0 0 E+0 0
41900000
0007
AAG
0
9 . 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 E+0 0
4190000000000000
0008
AAH
0
9 . 0 0 0 0 0 E+0 0
41900000
0009
AAJ
0
2003-09-11
07CA000B000C
000A
AAK
0
1 2:3 0:3 0 . 0 0 1
000C001E001E0001
000B
AAL
0
2003-09-11 12:30:30 .001
07CA000B000C000C001E001E0001
9001
0
OTTO
D6E3E3D6
HOMEPROCTSN=492ESESAM-IS 0000000D
BAN: 0001
SAN: AAA POS#:
0004
AAD
000B
AAL
HOMEPROCTSN=492ESESAM-IS 0000000E
BAN: 0001
SAN: AAA POS#:
U22418-J-Z125-6-76
UPDATE
2
18 00000001
FCT: - VALUE:H U G O
C8E4C7D640404040404040404040404040404040
1
0
8
8F
0
2003-09-11 1 2:3 2:1 7 .0 0 1
07CA000B000C000C002000110001
DELETE
2
18 00000001
FCT: - VALUE:H U G O
C8E4C7D640404040404040404040404040404040
523
SEDI70: report output
Appendix
Explanation
Heading
Contents
BAN
Binary attribute name (the association between the binary attribute name and the
column name can be obtained using the catalog table
SYS_INFO_SCHEMA.SYS_COLUMNS via the SESAM_BAN and
COLUMN_NAME fields).
SAN
Symbolic attribute name (except for Character Varying)
POS#
Position number (only contains data when multiple fields used)
FCT
The action carried out with the following attributes (the hexadecimal string is
always interpreted as a character string and is converted):
0: Change to the new attribute value (no information relating to old value)
L: Value was deleted
N (primary key only): New primary key, i.e. a new record
- (primary key only): No change (used to identify the record)
VALUE
New attribute value (printable/hexadecimal representation)
Secondary data
Secondary data changes are not output!
Transaction borders
All changes made to the affected user are committed or rolled back at a transaction border.
Internally the result of the transaction is logged in two steps: If identical transaction IDs
(TA_ID) appear, then the transaction is considered to be committed, but if they do not
appear, the transaction is considered to be rolled back. This information is presented clearly
in the SEDI70 log so that a conclusion can be reached even when files are exchanged
between the two steps.
Example
HOMEPROCTSN=493GSESAM-IS =====> PREPARE TO COMMIT (TA_ID: 00000001)
524
HOMEPROCTSN=493GSESAM-IS =====> COMMIT WORK
(TA_ID: 00000005)
HOMEPROCTSN=493GSESAM-IS =====> ROLLBACK WORK
(TA_ID: 00000008)
U22418-J-Z125-6-76
Appendix
SEDI70: report output
Canceling a statement:
When a statement is canceled, all changes with the corresponding statement identification
are rolled back (due to SQL state, INTR CANCEL).
Examples
Of a cancellation:
HOMEPROCTSN=492GSESAM-IS 0000000E =====> STATEMENT-CANCEL
Of the normal termination of a statement (only for the option NOTAS):
HOMEPROCTSN=493GSESAM-IS 0000010B =====> STATEMENT-END
DDL statements
Logging is performed using an internal representation. The data is attempted to be
formatted similar to SQL statements.
The ALTER SPACE statement always appears when the metadata of a space is changed.
It is used to modify the space timestamp. The space timestamp is used to check the consistency against the metadata in the catalog space.
Examples of DDL statements that affect the user space:
a) CREATE TABLE
D016ZE09TSN=6V1YSESUTI 00000008 ALTER SPACE (SPACE-ID=3,TIMESTAMP=2003-09-11 09:37:33)
D016ZE09TSN=6V1YSESUTI 00000008 CREATE TABLE
USING SPACE SPACE2
(TABLE-ID=2)
(SPACE-ID=3)
D016ZE09TSN=6V1YSESUTI 00000008 ALTER SPACE (SPACE-ID=3,TIMESTAMP=2003-09-11 09:37:33)
D016ZE09TSN=6V1YSESUTI 00000008 ALTER TABLE
(TABLE-ID=2,SPACE-ID=3)
D016ZE09TSN=6V1YSESUTI 00000008 ADD COLUMN PRIMKEY
CHARACTER(10)
(BAN=0001,SAN=AAA)
PRIMARY KEY
D016ZE09TSN=6V1YSESUTI 00000008 ADD COLUMN CHAR1
CHARACTER(10)
(BAN=0002,SAN =AAB)
D016ZE09TSN=6V1YSESUTI 00000008 ADD COLUMN NUM01
NUMERIC(2,1)
(BAN=0003,SAN=AAC)
D016ZE09TSN=6V1YSESUTI 00000008 ADD COLUMN DEC01
DECIMAL(17,16)
(BAN=0004,SAN=AAD)
D016ZE09TSN=6V1YSESUTI 00000008 ADD COLUMN INT01
INTEGER
(BAN=0005,SAN=AAE)
U22418-J-Z125-6-76
525
SEDI70: report output
Appendix
D016ZE09TSN=6V1YSESUTI 00000008 ADD COLUMN SMINT
SMALLINT
(BAN=0006,SAN=AAF)
D016ZE09TSN=6V1YSESUTI 00000008 ADD COLUMN CHAR2(255)
CHARACTER(256)
(BAN=0007,SAN=AAG)
D016ZE09TSN=6V1YSESUTI
========>
COMMIT WORK
(TA-ID: 00000000E)
b) ALTER TABLE ADD COLUMN
D016ZE09TSN=6V1YSESUTI 0000003E ALTER SPACE (SPACE-ID=2,TIMESTAMP=2003-09-11 10:28:06)
D016ZE09TSN=6V1YSESUTI 0000003E ALTER TABLE
(TABLE-ID=2,SPACE-ID=2)
D016ZE09TSN=6V1YSESUTI 0000003E ADD COLUMN CHAR02
(BAN=0008,SAN=AAH)
CHARACTER(10)
D016ZE09TSN=6V1YSESUTI
========>
COMMIT WORK
(TA-ID: 00000000F)
c) ALTER TABLE ALTER COLUMN
D016ZE09TSN=6V1YSESUTI 0000001F ALTER SPACE (SPACE-ID=3,TIMESTAMP=2003-09-11 10:35:18)
D016ZE09TSN=6V1YSESUTI 0000001F ALTER TABLE
(TABLE-ID=3,SPACE-ID=3)
D016ZE09TSN=6V1YSESUTI 0000001F ALTER COLUMN CHAR01 (BAN=0002,SAN=AAB)
NUMERIC(10)
D016ZE09TSN=6V1YSESUTI
========>
COMMIT WORK
(TA-ID: 00000001E)
d) ALTER TABLE DROP COLUMN
D016ZE09TSN=6V1YSESUTI 00000021 ALTER SPACE (SPACE-ID=3,TIMESTAMP=2003-09-11 10:36:25)
D016ZE09TSN=6V1YSESUTI 00000021 ALTER TABLE
(TABLE-ID=3,SPACE-ID=3)
D016ZE09TSN=6V1YSESUTI 00000021 DROP COLUMN
(BAN=0002,SAN=AAB)
D016ZE09TSN=6V1YSESUTI
(TA-ID: 00000001F)
========>
COMMIT WORK
e) DROP TABLE
D016ZE09TSN=6V1YSESUTI 00000023 ALTER SPACE (SPACE-ID=3,TIMESTAMP=2003-09-11 10:37:32)
526
D016ZE09TSN=6V1YSESUTI 00000023 DROP COLUMN
PRIMARY KEY
(BAN=0001,SAN=AAA)
D016ZE09TSN=6V1YSESUTI 00000023 DROP COLUMN
(BAN=0003,SAN=AAC)
U22418-J-Z125-6-76
Appendix
SEDI70: report output
D016ZE09TSN=6V1YSESUTI 00000023 DROP COLUMN
(BAN=9001)
D016ZE09TSN=6V1YSESUTI 00000023 DROP TABLE
(TABLE-ID=3)
USING SPACE SPACE2 (SPACE-ID=3)
D016ZE09TSN=6V1YSESUTI
========>
COMMIT WORK
(TA-ID: 000000021)
f) Possible data types for ADD COLUMN
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_CHA
CHARACTER(20)
(BAN=0001,SAN=AAA)
PRIMARY KEY
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_VAR
CHARACTER VARYING(20)
(BAN=9001)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_INT
INTEGER
(BAN=0002,SAN=AAB)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_SMI
SMALLINT
(BAN=0003,SAN=AAC)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_DEC (3) (BAN=0004,SAN=AAD)
DECIMAL(1)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_NUM
NUMERIC(1)
(BAN=0005,SAN=AAE)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_REA
REAL
(BAN=0006,SAN=AAF)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_DOU
DOUBLE PRECISION
(BAN=0007,SAN=AAG)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_FLO
FLOAT(1)
(BAN=0008,SAN=AAH)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_DAT
DATE
(BAN=0009,SAN=AAJ)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_TIM
TIME
(BAN=000A,SAN=AAK)
HOMEPROCTSN=492ESESAM-IS 00000006 ADD COLUMN C001_TST
TIMESTAMP
(BAN=000B,SAN=AAL)
U22418-J-Z125-6-76
527
SEDI70: report output
Appendix
SSL statements
Logging is done using an internal representation. The data is attempted to be formatted
similar to SQL statements.
Example
a) CREATE SPACE
D016ZE09TSN=6V1YSESUTI 00000002 CREATE SPACE SPACE1
D016ZE09TSN=6V1YSESUTI
========>
COMMIT WORK
(SPACE-ID =2)
(TA-ID: 000000006)
b) DROP SPACE
D016ZE09TSN=6V1YSESUTI 0000000A DROP SPACE SPACE1
D016ZE09TSN=6V1YSESUTI
========>
COMMIT WORK
(SPACE-ID=2)
(TA-ID: 000000008)
c) CREATE INDEX
D016ZE09TSN=6V1YSESUTI 00000019 ALTER SPACE (SPACE-ID=3,TIMESTAMP 2003-09-11 07:27:05)
D016ZE09TSN=6V1YSESUTI 00000019 CREATE INDEX
(INDEX-ID =12)
ON TABLE
(TABLE-ID=3,SPACE-I=2)
USING SPACE SPACE2
(SPACE-ID=3)
D016ZE09TSN=6V1YSESUTI
========>
COMMIT WORK
(TA_ID: 0000000D)
d) DROP INDEX
D016ZE09TSN=6V1YSESUTI 0000006D ALTER SPACE (SPACE-ID=3,TIMESTAMP=2003-09-11 07:29:29)
D016ZE09TSN=6V1YSESUTI 0000006D DROP INDEX
(INDEX-ID=13)
ON TABLE
(TABLE-ID=3,SPACE-ID=2)
USING SPACE SPACE2
(SPACE-ID=3)
D016ZE09TSN=6V1YSESUTI
528
========>
COMMIT WORK
(TA_ID: 0000001E)
U22418-J-Z125-6-76
Appendix
Layout of the accounting information
9.4 Layout of the accounting information
SESAM/SQL creates an accounting record (DBS1 record) for each user session. The
accounting record is made available at the end of the user session in the accounting buffer.
The contents of this buffer are written to the BS2000 accounting file and can be further
processed by the RAV accounting procedure.
DBS1 record
Field
Length
Meaning
1
2
Total record length
2
2
Free
3
4
Record ID: “DBS1”
4
8
Timestamp (STCK format)
5
2
Length of the user information
6
2
Length of the basic information: 80 bytes
7
4
Free
User information
8
8
TIAM: accounting number
9
8
TIAM: BS2000 ID
10
32
Requesting
user:
UTM R/L 1
DCAM R/L
TIAM R 1
TIAM L
1
1
1-8
9-16
17-24
25-32
host
application
user
TAC name
host
application
user
program name
host
TSN=tsn
program name
userid
request name TSN=tsn
program name
userid
UTM
SESAMUq
Basic information
11
8
Source:
q = {R| L} 1
DCAM
SESAMDq
TIAM
SESAMTq
12
4
Number of physical file accesses
13
4
Number of logical file accesses
14
4
Number of DML statements
4
4
Elapsed time in the following format:
– seconds
– nanoseconds
15
Table 56: DBS1 record
U22418-J-Z125-6-76
(part 1 of 2)
529
Layout of the accounting information
Field
Length
Meaning
4
2
2
2
2
2
1
Beginning of user session: local time, printable
– Year
– Month
– Day
– Hour
– Minute
– Second
– Season:
C'W': winter time, C'S': daylight saving time
1
Free
4
2
2
2
2
2
1
End of user session: local time, printable
– Year
– Month
– Day
– Hour
– Minute
– Second
– Season:
C'W': winter time, C'S': daylight saving time
1
Free
16
17
18
19
Appendix
Variable part
20
8
Host ID of the DBH
21
8
User ID of the DBH
22
8
Account # of the DBH
23
1
Configuration identifier
24
1
Name identifier
25
2
Number of variable fields: 1
26
2
Field distance: X'0000'
27
2
Field identification
28
2
Length of the variable field
4
4
CPU time in the following formats:
– seconds
– nanoseconds
29
Table 56: DBS1 record
1
530
(part 2 of 2)
R = remote, L = local
U22418-J-Z125-6-76
Appendix
Layout of the log records for SAT
9.5 Layout of the log records for SAT
From SESAM/SQL-Server V3.2 onwards, SESAM/SQL logs security relevant events with
the help of the component SAT (Security Audit Trail) of the software product SECOS.
An overview of this function is given in the “Core Manual”, in the section “Logging safetyrelevant events with SAT”. For more information about SAT and the SAT evaluation program
SATUT, see the manual “Security Control System”.
For each security relevant event, a log record (SATLOG record) is written in the protected
SATLOG file. The SATLOG file can be analyzed later using the SATUT evaluation routine.
SATLOG records consist of a fixed part which is constantly supplied, and a variable part
which contains information about the security relevant event from SESAM/SQL.
The following fields in the fixed part of every SATLOG record are always assigned values:
user ID and TSN of the DBH task (user-id, tsn)
–
logging time (timestp)
–
abbreviated name of the event (evt) and result of the event (res)
–
chipcard ID (auditid), if a chipcard is used
Field
name
auditid
al/fil
–
exit
Meaning and values of information:
SDF data type or keywords
*
0001
Chipcard ID
type: x-string 2..32
evt
00F3 Abbreviated name of the event
type: c-string 1..3
res
00F5 Result of the event
keywords: F/S for Failure/Success
timestp
00F1 Logging time
format: yyyy-mm-dd/hh:mm:ss
tsn
00F4 TSN of the DBH task
type: c-string 1..4
user-id
00F6 User ID of the DBH task
type: c-string 1..8
Table 57: Field names and values for every SATLOG record
These fields are therefore no longer mentioned in the following SESAM-specific tables.
For the meaning of the column headers see page 534.
U22418-J-Z125-6-76
531
Layout of the log records for SAT
Appendix
9.5.1 SESAM object events
The table in the following shows the auditable events of the SAT object SESAM, the abbreviated names of the events, the subcodes and indication of their audit attributes.
The /MODIFY-SAT-PRESELECTION command enables the security administrator to
modify the audit attributes for most events.
The individual columns have the following meanings:
–
OBJECT Event column
Specification of the object, accompanied by the operations which result in auditable
events.
–
Event name column
Each event has a 3-character event name which may be used as a keyword in the
commands /SHOW-SAT-STATUS and /MODIFY-SAT-PRESELECTION as well as when
analyzing with SATUT (statements //ADD-SELECTION-CONDITIONS and //SELECTRECORDS).
–
Subcode column
Specification of an event. Forms part of the logged information.
–
Audit attribute Chg column
Indication of whether the SAT audit attribute for the event can be changed.
Y (YES): SAT audit attribute can be changed
–
Audit attribute Dft column
Shows the default setting for the SAT audit attribute of the event:
N: SAT audit attribute NONE, i.e. the event is not logged
OBJEKT
Event
Event name
evt
Subcode
for event
sessubc
Audit attribute
Chg
Dft
SESAM
Administer DBH session
SEA
ADM
Y
N
Grant/revoke rights
Add/remove/modify users
SEP
SEP
PRI
USR
Y
Y
N
N
DDL statement
SSL statement
Utility statement
SES
SES
SES
DDL
SSL
UTI
Y
Y
Y
N
N
N
Start SESAM task (DBH or Service-Task)
Stop SESAM task (DBH or Service-Task)
SET
SET
STRT
END
Y
Y
N
N
Stop process
SEU
END
Y
N
Table 58: Object-related events, event names and audit attributes of the SAT object SESAM
532
U22418-J-Z125-6-76
Appendix
Layout of the log records for SAT
9.5.2 Auditable information for every SESAM object event
The table in the following shows a list of the events for the SAT object SESAM, with the
associated information fields and their type of output:
M = Mandatory (is always output)
O = Optional (may be output)
Event of the
object SESAM
evt
appluid
dbhconf
dbhnam
dbname
dbtable
hostnam
schema
sessubc
sestext
stmtctf
stmtcts
utmsct
utmuser
= is not output
applnam
-
SAT information
Administer DBH session
SEA
M
O
M
M
-
-
M
-
M
M
-
-
M
M
Change access rights and
user accesses
DDL, SSL, utility statement
SEP
M
O
M
M
M
-
M
-
M
O
-
-
M
M
SES
M
O
M
M
M
O
M
O
M
O
-
-
M
M
Start or stop SESAM task
(DBH or Service-Task)
Stop process
SET
-
-
M
M
-
-
-
-
M
M
-
-
-
-
SEU
M
O
M
M
-
-
M
-
M
-
M
M
M
M
Table 59: Auditable informationen of the events of the SAT object SESAM
U22418-J-Z125-6-76
533
Layout of the log records for SAT
Appendix
The table below shows the values present in the various fields.
The field names which can also be monitored via the alarm function of SAT or for which a
filter condition can be defined are identified in the second column (al/fil) by means of an
asterisk (*). The asterisk (*) mark means that aside from the existence of the field the
contents of the field can also be checked.
al/fil
The identifier in the third column (exit) can be used to edit the SAT information in the audit
records when using exit routine 110. The identifiers are specified in hexadecimal notation.
exit
applnam
*
0025
Application name 1
type: c-string 1..8
In case of a TIAM program the field contains the string 'TSN=<tsn>' where
<tsn> stands for the tsn of the application program.
With logging of an administration statement via /INFORM-PROGRAM this
field contains the string ' SEND'.
appluid
*
0162
Application user id
type: c-string 1..8
With logging of an administration statement via /INFORM-PROGRAM this
field is not filled.
dbhconf
*
0160
DBH configuration identifier 2
type: c-string 1..1
dbhnam
*
015F DBH name identifier 2
type: c-string 1..1
dbname
*
0165
Database name
type: c-string 1..18
Logical database name to which the statement relates.
dbtable
*
0167
Table name in the catalog
type: c-string 1..31
Table name which is addressed in a statement. This field is only supplied if
the name is known at the time of logging.
hostnam
*
0029
Name of the host of the user program 1
type: c-string 1..8
With logging of an administration statement via /INFORM-PROGRAM this
field contains the string ' SESAM'.
schema
*
0166
Schema name in the catalog
type: c-string 1..31
Schema which is addressed in a statement. This field is only supplied if the
name is known at the time of logging.
Field
name
Meaning and values of information:
SDF data type or keywords
Table 60: Field names and values for the SAT object SESAM
534
(part 1 of 3)
U22418-J-Z125-6-76
Layout of the log records for SAT
al/fil
Appendix
exit
sessubc
*
015E
Subcode for the SESAM events
type: c-string 1..4
The following subcodes can be evaluated, depending on the event
concerned:
Event SET
– STRT: Start of a SESAM task (DBH or service task)
– END: End of a SESAM task (DBH or service task)
Event SEU
– END: End of process
Event SEA
– ADM: Administer DBH session
Event SEP
– USR: Add/remove/modify users
– PRI: Grant/revoke rights
Event SES
– DDL: DDL statement
– SSL: SSL statement
– UTI: Utility statement
sestext
*
0168
Additional information about the SESAM event
type: c-string 1..64
Depending on the event, the following additional information is given, if it
exists, at the time of logging:
– 'DBH-Task' when a DBH task has been started or terminated
– 'Service-Task' when a service task has been started or terminated
– The first 64 characters of an adminisration statement
– Brief statement texts such as 'ALTER_TABLE' or 'COPY_CATALOG' in
the case of DDL, SSL or utility statements. If the statement has altered
the catalog, the statement number, the internal TAID and number and
subnumber of the catalog will also be issued. This information is used
to understand the changes with the catalog.
stmtctf
*
0164
Number of unsuccessful statements in the process
type: integer 0..231-1
A statement is unsuccessful if it is not acknowledged with “successful
completion”, “no data” or “rollback”.
stmtcts
*
0163
Number of successful statements in the process
type: integer 0..231-1
A statement is successful if it is acknowledged with “successful
completion”, “no data” or “rollback”.
utmsct
*
0161
UTM session counter 1
type: x-string 2..16 (ALARM/FILTER: x-string 16..16)
Field
name
Meaning and values of information:
SDF data type or keywords
Table 60: Field names and values for the SAT object SESAM
U22418-J-Z125-6-76
(part 2 of 3)
535
Field
name
utmuser
al/fil
Layout of the log records for SAT
exit
*
0048
Appendix
Meaning and values of information:
SDF data type or keywords
User id in UTM application frame 1
type: c-string 1..8
With logging of an administration statement via /INFORM-PROGRAM this
field contains the string ' MESSAGE'.
Table 60: Field names and values for the SAT object SESAM
536
(part 3 of 3)
1
A specific process can be identified with the hostnam, applnam, utmuser and utmsct fields
2
The SAT log records for all tasks of a database handler can be identified with the dbhnam and dbhconf fields
U22418-J-Z125-6-76
Appendix
Using FASTPAM for SESAM/SQL
9.6 Using FASTPAM for SESAM/SQL
SESAM/SQL uses the FASTPAM access method for all files except for the database files
that are stored on shared or protected private disks (SPD or PPD).
These files are still processed by SESAM/SQL with the UPAM access method because the
type of disk does not allow you to use FASTPAM.
Accessing the disks with FASTPAM yields higher performance than accessing them with
UPAM because FASTPAM prepares certain paths and resident areas are created.
In order to create resident area the BS2000 user ID requires FASTPAM authorization.
Whether or not the BS2000 user ID has the corresponding authorization is determined via
the BS2000 command SHOW-USER-ATTRIBUTES. The DMS-TUNING-RESOURCES
field must be set to the value *EXCLUSIVE.
FASTPAM can be used even though the BS2000 user ID does not have FASTPAM authorization, but in this case the areas are not stored in resident memory. This also applies to
when the BS2000 user ID has FASTPAM authorization, but not all the required areas
(I/O buffer and administration information) can be stored in resident memory because there
is not enough main memory free.
If the attempt to load SESAM/SQL is rejected in spite of there being a sufficiently high value
for RESIDENT PAGES in the BS2000 user ID, the BS2000 system administrator may have
to increase the maximum number of resident main memory pages allowed accordingly
(BS2000 command MODIFY-SYSTEM-BIAS). You can query the maximum value set
(CORE) by using the BS2000 command SHOW-SYSTEM-STATUS with the
INFORMATION=*SYSTEM-PARAMETERS parameter.
You can enter the required number of resident pages in the START command for the DBH
start in the RESIDENT-PAGES parameter, see page 33. You must specify a minimum and
a maximum value.
If you specify a minimum value = 0, SESAM/SQL will start in any case, although performance may suffer. If you specify a minimum value > 0, SESAM/SQL will only start if the
minimum requirement can be satisfied.
The sizes of the values specified for the I/O buffers are particularly relevant to the calculation of the maximum value. The formula for the number of resident pages required is:
Number of resident pages =
Rounded to 4KB units
(Option SYSTEM-DATA-BUFFER
+ Option USER-DATA-BUFFER
+ Option CURSOR-DATA-BUFFER
+ 129 KB * Option SQL-DATABASE-CATALOG
+ 36 Bytes * Option DBH-Task * (Option THREADS + Option WRITE-THREADS + 11)
)
U22418-J-Z125-6-76
537
Using FASTPAM for SESAM/SQL
Appendix
In addition to the size of the resident memory, the number of required FASTPAM parameter
lists (FPAMACC) also represents a limit for FASTPAM. The number of parameter lists
required by SESAM/SQL depends on the DBH options.
FASTPAM permits a maximum of 5000 parameter lists. This drops to 500 parameter lists in
test mode. Test mode is used in the absence of FASTPAM authorization or when there is
insufficient resident memory.
If the limits for the maximum permitted number of parameter lists are exceeded,
SESAM/SQL issues a corresponding message and switches automatically to UPAM.
Additional information on the FASTPAM access method can be found in the “Introductory
Guide to DMS”.
538
U22418-J-Z125-6-76
Appendix
Starting SESAM programs with /START-PROGRAM
9.7 Starting SESAM programs with /START-PROGRAM
All SESAM/SQL programs are started using SESAM start commands for the specific
programs; see page 31. It is assumed that you have installed SESAM/SQL and CRTE
with IMON or that the files required have been set up under their default filenames
(see page 35).
For reasons of compatibility, you can continue to use the command START-PROGRAM to
start the SESAM programs. Additonal information about the program-specific sections for
DBH, SESADM and utility monitor is contained in this section.
You will also find the command sequences mentioned in the start files of the demonstration
database MAN-DB; see the “Core Manual”.
Version coexistence
If SESAM programs are started by means of the /START-PROGRAM command, the most
recently installed correction delivery status is loaded, if you do not specify the VERSION
parameter. If you do specify the parameter, the specified version must match the version of
the start LLM in the SESAM module library.
Starting the DBH
You should also note the following before starting the SESAM/SQL DBH with
/START-PROGRAM:
–
The SESAM/SQL DBH loads modules dynamically. When dynamically loading the first
module, it searches the following module libraries in the order specified:
1. the module library, which is assigned the link name SESAMOML by means of the
/ADD-FILE-LINK command
2. the module library assigned by means of /SET-TASKLIB LIBRARY=modlib.
This module library is ignored if modlib is the TASKLIB library of the default user ID
3. hardware dependent SYSLNK.SESAM-SQL.032 or SPULNK.SESAM-SQL.032
module library of the calling user ID
4. hardware dependent SYSLNK.SESAM-SQL.032 or SPULNK.SESAM-SQL.032
module library of the default user ID (the user ID specified with the parameter
DEFLUID when the BS2000 system is generated)
5. the TASKLIB module library of the default user ID
All subsequent modules are loaded from the same library as the first one. This means
you must make all SESAM/SQL modules available in the same module library.
–
The default name of the SESAM/SQL module library is SYSLNK.SESAM-SQL.032 for
business servers with /390 architecture and SR2000.
U22418-J-Z125-6-76
539
Starting SESAM programs with /START-PROGRAM
Appendix
The default name of the SESAM/SQL module library is SPULNK.SESAM-SQL.032 for
business seervers with SPARC64 architecture.
If you use another name, or if the module library is not under either the calling user ID
or the default user ID, you have to assign the module library with the link name
SESAMOML
(/ADD-FILE-LINK LINK-NAME=SESAMOML, FILE-NAME=sesam-modlib).
–
The hardware dependent CRTE library is required to run the SESAM/SQL DBH. You
must always assign the CRTE library under the link name BLSLIBxx before starting the
DBH, if you have not installed CRTE with IMON. The placeholder xx stands for a twodigit serial number (00 ≤ xx ≤ 99).
Command sequence for starting the DBH (/390 architecture)
/ADD-FILE-LINK LINK-NAME=SESAMOML, FILE-NAME=$TSOS.SYSLNK.SESAM-SQL.032
/ADD-FILE-LINK LINK-NAME=BLSLIB01, FILE-NAME=$TSOS.SYSLNK.CRTE
/START-PROGRAM FROM-FILE=*MODULE / (LIBRARY=$TSOS.SYSLNK.SESAM-SQL.032 / ,ELEM=SESAM / ,PROG-MODE=ANY / ,RUN-MODE=ADVANCED)
Starting SESADM (/390 architecture)
/ADD-FILE-LINK LINK-NAME=SESAMOML, FILE-NAME=$TSOS.SYSLNK.SESAM-SQL.032
/ADD-FILE-LINK LINK-NAME=BLSLIB01, FILE-NAME=$TSOS.SYSLNK.CRTE
/START-PROGRAM FROM-FILE=*MODULE / (LIBRARY=$TSOS.SYSLNK.SESAM-SQL.032 / ,ELEM=SESADM / ,PROG-MODE=ANY / ,RUN-MODE=ADVANCED)
Starting the utility monitor (/390 architecture)
/ADD-FILE-LINK
/ADD-FILE-LINK
/ADD-FILE-LINK
/ADD-FILE-LINK
/ADD-FILE-LINK
/
/START-PROGRAM
/
/
/
/
/
540
LINK-NAME=MAPLIB,FILE-NAME=$TSOS.SYSFHS.SESAM-SQL.032.UTI.D
LINK-NAME=SESAMOML,FILE-NAME=$TSOS.SYSLNK.SESAM-SQL.032
LINK-NAME=BLSLIB01,FILE-NAME=$TSOS.SYSLNK.CRTE
LINK-NAME=SEEHELP,FILE-NAME=$TSOS.SYSMAN.SESAM-SQL.032.UTI.D
LINK-NAME=SESCONF,FILE-NAME=SESCONF.SESUTI.ZX
,ACCESS-METHOD=SAM
FROM-FILE=*MODULE(LIBRARY=$TSOS.SYSLNK.SESAM-SQL.032
,ELEMENT=SESUTI
,PROG-MODE=ANY
,RUN-MODE=ADVANCED(ALTERNATE-LIBRARIES=YES
,UNRESOLVED-EXTRNS=DELAY
,LOAD-INFORMATION=REFERENCES))
U22418-J-Z125-6-76
Related publications
The Fujitsu Siemens Computers GmbH manuals listed below are available from these
sources:
–
On the Internet from our manual server (URL: http://manuals.fujitsu-siemens.com)
–
On the CD-ROM “BS2000/OSD SoftBooks”.
This CD contains practically all the German language manuals and read me files for
the BS2000 system software of the latest BS2000/OSD version.
Printed copies of the manuals can be purchased separately over the Internet from:
http://FSC-manualshop.com.
SESAM/SQL-Server (BS2000/OSD)
SQL Reference Manual Part 1: SQL Statements
User Guide
Target group
The manual is intended for all users who wish to process an SESAM/SQL database by
means of SESAM/SQL statements.
Contents
The manual describes how to embed SQL statements in COBOL, and the SQL language
constructs. The entire set of SQL statements is listed in an alphabetical directory.
SESAM/SQL-Server (BS2000/OSD)
SQL Reference Manual Part 2: Utilities
User Guide
Target group
The manual is intended for all users responsible for SESAM/SQL database administration.
Contents
An alphabetical directory of all utility statements, i.e. statements in SQL syntax implementing the SESAM/SQL utility functions.
U22418-J-Z125-6-76
541
Related publications
SESAM/SQL-Server V3.0A (BS2000/OSD)
CALL DML Applications
User Guide
Target group
SESAM application programmers
Contents
– CALL DML statements for processing SESAM databases using application programs
– Transaction mode with UTM and DCAM
– Utility routines SEDI61 and SEDI63 for data retrieval and direct updating
– Notes on using both CALL DML and SQL modes
SESAM/SQL-Server (BS2000/OSD)
Core Manual
User Guide
Target group
The manual is intended for all users and to anyone seeking information on SESAM/SQL.
Contents
The manual gives an overview of the database system. It describes the basic concepts. It
is the foundation for understanding the other SESAM/SQL manuals.
SESAM/SQL-Server (BS2000/OSD)
Utility Monitor
User Guide
Target group
The manual is intended for SESAM/SQL-Server database and system administrators.
Contents
The manual describes the utility monitor. The utility monitor can be used to administer the
database and the system. One aspect covered is its interactive menu interface.
SESAM/SQL-Server (BS2000/OSD)
Glossary
User Guide
Target group
This manual is addressed to anyone who uses or wishes to find out about SESAM/SQL.
Contents
The manual contains all technical terms relevant for all SESAM/SQL manuals.
542
U22418-J-Z125-6-76
Related publications
SESAM/SQL-Server (BS2000/OSD)
Messages
User Guide
Target group
All users of SESAM/SQL.
Contents
All SESAM/SQL messages, sorted by message number.
SESAM/SQL-Server (BS2000/OSD)
Migrating SESAM Databases and Applications to SESAM/SQL-Server
User Guide
Target group
Users of SESAM/SQL-Server.
Contents
This manual gives an overview of the new concepts and functions. Its primary subject is,
however, the difference between the previous and the new SESAM/SQL version(s). It
contains all the information a user may require to migrate to SESAM/SQL-Server V2.0.
SESAM/SQL-Server (BS2000/OSD)
Performance
User Guide
Target group
Experienced users of SESAM/SQL.
Contents
The manual covers how to recognize bottlenecks in the behavior of SESAM/SQL and how
to remedy this behavior.
WebTA access for SESAM/SQL
(Product document also available from the Fujitsu Siemens manual server).
Target group
The manual is intended for SESAM/SQL system administrators setting up Web access and
for users who want to use Web access.
Contents
The manual describes the requirements, installation and use of the unified Web access to
the administration program SESADM, the performance monitor SESMON and the utility
monitor SESUTI.
U22418-J-Z125-6-76
543
Related publications
ESQL-COBOL (BS2000/OSD)
ESQL-COBOL for SESAM/SQL-Server
User Guide
Target Group
COBOL programmers wishing to work with SESAM/SQL databases using SQL statements.
Contents
The manual describes the structure of an ESQL-COBOL program, how to embed SQL in
COBOL, and how to compile, link and start such a program.
SDF (BS2000/OSD)
Introductory Guide to the SDF Dialog Interface
User Guide
Target group
BS2000/OSD users
Contents
This manual describes the interactive input of commands and statements in SDF format.
A Getting Started chapter with easy-to-understand examples and further comprehensive
examples facilitates use of SDF. SDF syntax files are discussed.
BS2000/OSD-BC
Commands, Volumes 1 - 5
User Guide
Target group
This manual is addressed to nonprivileged users and systems support staff.
Contents
Volumes 1 through 5 contain the BS2000/OSD commands (basic configuration and
selected products) with the functionality for all privileges. The command and operand
functions are described in detail, supported by examples to aid understanding. An introductory overview provides information on all the commands described in Volumes 1
through 5.
The Appendix of Volume 1 includes information on command input, conditional job variable
expressions, system files, job switches, and device and volume types.
The Appendix of Volumes 4 and 5 contains an overview of the output columns of the SHOW
commands of the component NDM. The Appendix of Volume 5 contains additionally an
overview of all START commands.
There is a comprehensive index covering all entries for Volumes 1 through 5.
544
U22418-J-Z125-6-76
Related publications
BS2000/OSD-BC
Commands, Volume 6, Output in S Variables and SDF-P-BASYS
User Guide
Target group
This manual is addressed to programmers and users who write procedures.
Contents
Volume 6 contains tables of all S variables that are supplied with values by the SHOW
commands in conjunction with structured output. Further chapters deal with:
– introduction to working with S variables
– SDF-P-BASYS
SDF-P (BS2000/OSD)
Programming in the Command Language
User Guide
Target group
The manual addresses BS2000/OSD users and systems support.
Contents
SDF-P is a structured procedure language in BS2000. The introduction is followed by a
detailed description of commands, functions and macros.
BS2000/OSD-BC
Introductory Guide to Systems Support
User Guide
Target group
This manual is addressed to BS2000/OSD systems support staff and operators.
Contents
The manual covers the following topics relating to the management and monitoring of the
BS2000/OSD basic configuration: system initialization, parameter service, job and task
control, memory/device/system time/user/file/pubset management, assignment of privileges, accounting and operator functions.
U22418-J-Z125-6-76
545
Related publications
BS2000/OSD-BC
Introductory Guide to DMS
User Guide
Target group
This manual is addressed to nonprivileged users and systems support staff.
Contents
It describes file management and processing in BS2000.
Attention is focused on the following topics:
– volumes and files
– file and catalog management
– file and data protection
– OPEN, CLOSE and EOV processing
– DMS access methods (SAM, ISAM,...)
BS2000/OSD-BC
Executive Macros
User Guide
Target group
The manual addresses all BS2000/OSD assembly language programmers.
Contents
The manual contains a summary of all Executive macros, detailed descriptions of each
macro with notes and examples, including job variable macros, and a comprehensive
general training section.
ARCHIVE (BS2000/OSD)
User Guide
Target group
– BS2000/OSD users
– BS2000/OSD system administrators
– BS2000/OSD operators
Contents
Functions and statements of the program ARCHIVE for logical data saving. ARCHIVE is
used for saving, reconstructing and transferring files and job variables.
546
U22418-J-Z125-6-76
Related publications
HSMS / HSMS-SV (BS2000/OSD)
Hierarchical Storage Management System
Volume 1: Functions, Management and Installation
Volume 2: Statements
User Guides
Target group
– BS2000/OSD users
– BS2000/OSD system administrators
– HSMS administrators
Contents
– Description of the data saving, archival, migration and data transfer functions
– HSMS management, invocation, execution and installation
– HSMS messages
– Description of the HSMS statements in alphabetical order
EDT (BS2000/OSD)
Statements
User Guide
Target group
This manual is intended for established EDT users as well as users not yet familiar with
EDT.
Contents
The manual describes the processing of SAM and ISAM files, elements from program
libraries and POSIX files. It also contains descriptions of the EDT operating modes,
statement codes, procedures and statements.
BS2000/OSD-BC
Subsystem Management (DSSM/SSCM)
User Guide
Target group
This manual addresses systems support staff and software consultants of BS2000/OSD.
Contents
The following are described: BS2000/OSD subsystem concept, dynamic subsystem
management (DSSM), subsystem catalog management (SSCM) and the associated
commands and statements.
U22418-J-Z125-6-76
547
Related publications
JV (BS2000/OSD)
Job Variables
User Guide
Target group
The manual addresses both nonprivileged users and systems support.
Contents
The manual describes management and possible uses of job variables. The command
descriptions are divided according to function areas. The macro calls are described in a
separate chapter.
BS2000/OSD-BC
Security Handbook for the User
Reference Manual
Target group
Timesharing users working with BS2000/OSD-BC V1.0
Contents
– Introduction to the security functions supported by the BS2000/OSD operating system
– Application notes and recommendations on how to protect data and programs against
unauthorized access
BS2000/OSD-BC
Security Handbook for Systems Support
Target group
This manual is intended for systems support staff and for anyone involved in developing and
implementing security strategies for BS2000 installations.
Contents
The manual provides detailed descriptions of measures to be taken to ensure secure DP
operation. These measures are based on the importance of security evaluations and the
guidelines derived therefrom. Attention is focused on the basic configuration BS2000/OSDBC in conjunction with SECOS. The subjects dealt with include:
– the basic functions of a secure system
– installation and generation of a secure BS2000 system
– user, file and volume management
– protection for operating terminals
– diagnostics
548
U22418-J-Z125-6-76
Related publications
SECOS (BS2000/OSD
Security Control System
User Guide
Target group
– BS2000 system administrators
– BS2000 users working with extended access protection for files
Contents
Capabilities and application of the functional units:
– SRPM (System Resources and Privileges Management)
– SRPMSSO (Single Sign On)
– GUARDS (Generally Usable Access Control Administration System)
– GUARDDEF (Default Protection)
– GUARDCOO (Co-owner Protection)
– SAT (Security Audit Trail).
SORT (BS2000/OSD)
SDF Format
User Guide
Target group
– BS2000 users
– Programmers
Contents
This manual describes the principles, functions and statements for sorting and merging
data records (SDF format), calling the subroutine interface and the SORTZM access
method. A chapter with examples instructs newcomers how to use SORT.
SNMP Management V5.0
SNMP Management for BS2000/OSD
User Guide
Target group
The manual addresses network administrators/operators and system administrators who
wish to integrate a BS2000 system in SNMP-based management or operate such a system.
Contents
This manual describes how SBA-BS2, SSC-BS2, SSA-SM2-BS2 and SSA-OUTM-BS2 are
embedded in BS2000/OSD, the installation and configuration procedures required to
enable operation, and actual system operation. The Agents and their MIBs which are
required for monitoring are dealt with in detail. Installation and configuration of the relevant
management applications on the Unicenter TNG, TransView SNMP and HP OpenView
management platforms are also described.
Further central topics of the manual are access to management information via the World
Wide Web, and the Trap Server for Solaris and Reliant UNIX.
U22418-J-Z125-6-76
549
Related publications
openUTM (BS2000/OSD)
Messages, Debugging and Diagnostics
User Guide
Target group
This manual is intended for programmers, generators and administrators of UTM applications in BS2000/OSD.
Contents
The manual describes the debugging of UTM applications, the format of UTM dumps,
behavior in the event of errors, and the openUTM message concept. It also includes all
messages and return codes output by openUTM.
550
U22418-J-Z125-6-76
Index
In the index, bold page numbers refer to the main sources of the index entries, while italicized page numbers refer to examples.
The collation sequence is a follows: symbols come before digits which come before letters. A punctuation mark is treated as a
symbol.
1P0 statement (SEPA) 498
1P1 statement (SEPA) 499
1P2 statement (SEPA) 502
1P2N statement 502
1P3 follow-up statement (SEPA)
1P3 statement (SEPA) 504
1P3N statement (SEPA) 504
1P4 statement (SEPA) 506
1P5 statement (SEPA) 507
505
A
ABORT-EXECUTION 110
aborting processing 110
ABORT-LOCK-SEQUENCE 211, 224
ACC,TP 285
ACCESS 78, 219
see access function
access
read 79, 219, 247
read and write 79, 220, 248
remote 158, 161, 167, 169
spaces 121
unauthorized 111, 489
write 79, 220, 247
access authorization (SEPA) 489, 500
access function 78, 219, 246, 247, 322, 324
access mode (SEPA)
delete 490
read 490, 492
update 490, 492
U22418-J-Z125-6-76
access path, distributed databases 166, 167
access plan, see SQL access plan
access protection (SEPA)
attributes 492, 492
combined: records and attributes 493, 493
records 490, 490
access right, see access function
access rights, changing 196, 246
ACCOUNTING 66, 71, 284
accounting 71, 284
activating 71
DBS1 record 71, 529
information 71, 529
UTMK record 71
accounting buffer 71, 529
acknowledgment area (CALL DML) 177
activating accounting 66, 71
activating transaction management 67, 134
active CALL DML requests, displaying 195, 307
active databases, displaying 198, 315
active users 309, 322, 331
displaying 195, 198, 309, 331
SESMON 392, 395
active users per space, displaying 195, 322
ADD-DISTRIBUTION-RULE-ENTRY 213
ADD-DISTRIBUTION-RULE-LIST 164, 213
ADD-NETWORK-LINK-LIST 166, 213
ADD-OLD-TABLE-CATALOG-ENTRY 215
ADD-OLD-TABLE-CATALOG-LIST 64, 73, 215,
272, 319
551
Index
ADD-PASSWORD 489
address space 39
ADD-SQL-DATABASE-CATALOG-LIST 64, 76,
215, 218, 272, 274
ADD-SQL-DB-CATALOG-ENTRY 218, 246
ADMIN (access function) 221, 248, 322
ADMINISTRATION 66, 81
administration
in the interactive mode 175
administration authorization 66, 82
changing 196, 198, 243
SESDCN 162
administration command 194, 201, 209,
210–339
administration commands and equivalent
statements 201
administration interfaces 173–193
CALL DML program 177
SESADM 178
administration of SESMON 387
administration password 82, 83, 244
administration program 178
administration statement 181, 194, 199, 208,
210–339, 484
overview 195–198
administration statements and equivalent
commands 199
ADMINISTRATOR 66, 158, 162, 243, 244
ADMINISTRATOR (DBH option) 82
administrator authorization SESDCN 158
alarm function 534
alias 15
alias name 15
alphabetical descriptions
of administration statements 204–339
of DBH start parameters 68–143
alphanum-name (data type) 16
application (SESMON) 391, 394
application name 350, 516
application users 206
evaluating requests 349, 516
APPLICATION-NAME 83, 206, 245
(SEDI70 parameter) 516
SESCOSP parameter 350
552
APPLICATIONS form (SESMON) 391, 394, 441
area for retrieval statements 67, 84
assigning CALL DML table to database 73
assignment table 376, 376
ASSIGN-SYSLST 223
asynchronous accesses (SESMON) 396
attribute name, symbolic 503
authentication calls (SESMON) 446
authentication SESMON 446
authorization (SESMON) 446
authorization calls (SESMON) 446
automatic termination of SESMON 388
B
backup computer 153, 161
backup file, SESDLGk 153
base table 73, 74, 319
batch job 147
batch mode 40, 147, 182
SESMON 382, 387, 388
BCAM memory lacks (SESMON) 396
BEGIN-LOCK-SQUENCE 224
BLSLIB 540
broadcast messages (SESMON) 396
BS2000 accounting file 529
prerequisites 71
BS2000 password 78, 219
BS2000 priorities 103
BS2000 user ID 76
buffer for user data 139
BUFFER-LIMIT 107, 257
buffers
cursor buffer 61, 88
displacement mode 67
plan buffer 124
setting size of 67, 125
system-data buffer 61, 128
transfer container 61, 137
user-data buffer 61, 139
work container 141
U22418-J-Z125-6-76
Index
C
CALL DML accesses (SESMON) 396
CALL DML Applications (manual) 5
CALL DML handler (SESMON) 412
CALL DML program 177
CALL DML requests 307
CALL DML statement
administration 177
chained 402, 424
CALL DML table 102, 111, 215, 272, 319
password protection 489
CALL DML table catalog 73, 102, 215, 272, 319
CALL interface 82, 489
call trace 477, 478
CALL-DML-TABLE-NAME 74, 216, 273, 320
CANCEL 226
canceling a DML statement 197, 226
CANCEL-STATEMENT 226
CAPACITY form (SESMON) 395, 441
cat (suffix for data type) 27
CAT-ADMINISTRATION (access function) 79,
220, 248
catalog files (SESMON) 403
catalog manager (SESMON) 412
catalog space 120, 464, 465
catalog, foreign copy 197
CATALOG-NAME 74, 77, 214, 216, 219, 228,
231, 238, 247, 266, 270, 273, 275, 295, 309,
320, 323, 325
CATALOG-NAMES (SESCOSP parameter) 347,
348
catalog-space table assignment table 376, 376
CAT-ID 96, 115, 298
cat-id (data type) 16
CATID list, updating 197
CAT-LOG file, changing 227
CAT-REC file
creating a copy 227
foreign user ID 227
CAW 229
chained CALL DML statements 402, 424
CHANGE-CATLOG 227
CHANGE-DALOG 230
changes (functions) 7
U22418-J-Z125-6-76
changing
access rights 196, 246
administration authorization 196, 198, 243
CAT-LOG file 227
DA-LOG file 227, 230
database status 197, 294
host name in distribution rule 198, 252
limit value for interrupting retrieval
statements 196
maximum number of suborders 196, 261
number of permitted sort records 196, 260
security settings 66
sort sequence 487
check pending (space state) 322
client/server architecture 452
CLOSE message 99
CLOSE,SPACE 233
CLOSE-SPACE 232
closing user space 197, 232
cold start 154, 158, 161
COLD-START 161
COLDSTART 158
CO-LOG file 61, 117, 296, 341, 345, 461, 483
COLUMNS 67, 84
command sequence
for starting SESADM 181
for starting SESCOSP 342
for starting SESDCN 147
for starting SESMON 382
to start SEDI70 510
command, representation of syntax 12
command-rest (data type) 16
COMMIT-PTC-TRANSACTION 234, 234, 280
committing a PTC transaction 197, 234
communication 51
compl (suffix for data type) 22
complexity 357, 371, 372
composed-name (data type) 16
conditional dump
of the application-program task 475
of the DBH task 474
configuration 49, 66, 86, 91, 153
specifying (SESMON) 384, 389
configuration file 48, 181, 475, 477
553
Index
CONFIGURATION form
APPLICATIONS (SESMON) 391
PREFETCH-BUFFERS (SESMON) 392
CONFIGURATION forms (SESMON)
overview 380
configuration name 49, 86, 158, 160, 167, 191,
192
CONFIGURATION-NAME 66, 86, 167, 191, 192,
214, 252
CONFIGURATION-NAME
(SESMON parameter) 384
connection module SESLINK 47
connection-module parameter 475, 477
consistency checks 99, 458, 466, 470, 473, 475
console 99, 174, 175, 387
constructor (string) 25
containers 67, 125
containers (SESMON) 396, 416
contingency (SESMON) 397
control logging with SAT 197
control statements, see SESDCN control statement
controlling
DBH outputs 66, 99, 101
logging of a user dump 197, 288
logging of DBH messages 197
logging of request accounting 196, 284
logging of SESAM messages 198
logging of statements 198, 300
logging of the message trace (DBH) 286
logging of the message trace (SESDCN) 304
request logging 197, 296
conversation 350
conversation number 207, 317, 322
conversation stacking 140
CONVERSATION-ID 207
SESCOSP parameter 350
conversion error 486
co-ownership 57
COPY
access function 220, 248
utility statement 220, 248
copy (space state) 322
copy of CAT-REC file, creating 227
554
copy pending (space status)
after foreign copy 197
COPY-NUMBER 78
Core Manual 5
corr (suffix for data type) 27, 28
correction delivery statuses 36
COS 299, 341
CPTC 235
CPU load 66
CPU time 358
CPU time period 353
CPU utilization 87
CPU-RESOURCES 66, 87
CPU-TIME 284, 297
SESCOSP parameter 353, 358
CREATE CATALOG 77
CREATE SPACE 120
CREATE-DUMP 236, 458, 475
CREATE-REPORT (SEDI70 parameter) 511
CREATE-REPORT (SESCOSP parameter) 344
CREATE-TABLE 215
creating a dump 197, 198, 236
creating a media catalog 66, 94
CRTE library 540
c-string (data type) 16
current database operation, information
(SESMON) 377
cursor (SESMON) 412, 416, 443
cursor buffer 61, 67, 88
cursor buffer frame 89
cursor file 49, 86, 88, 91, 94, 97
SESMON 403
cursor table 124, 260
CURSOR-BUFFER 67, 88
CURSOR-MEDIA 97
CURSORS 124
CUSTOMER-NAME 83, 207, 245
(SEDI70 parameter) 517
SESCOSP parameter 350
U22418-J-Z125-6-76
Index
D
DA-LOG file, changing 227, 230
Data Base Handler, see DBH
data type
SDF 12, 16
SDF, suffixes 13
vsn 20
database
defective 465
entering in the distribution rule 164, 198, 213
evaluating requests 347
internal number 376
database accesses (SESMON) 396
database entry
removing from the distribution rule 198, 270
database file, foreign user ID 227
database name, logical 76, 213, 215, 218
database name, physical 76, 218, 324
database operation 29
Database Operation (manual) 5
database status 294, 324
changing 197, 294
date (data type) 16
DAW 231
DB Trace Information 479
DB user ID 76,78,324
DB/DC system 2
DB-DIAGAREA 479
DBH
administering 66, 81
assigning to a configuration 66, 86
availability at restart 106
controlling outputs of 66, 99, 101
defective 466
functions of 29
identifying 66, 90
LLM name 38
naming 66, 91, 93, 94, 99, 102, 103, 109,
111, 113, 117, 119, 120, 122, 123, 125,
126, 128, 129, 130, 133, 134, 137, 139,
140, 141, 158, 164, 166, 191, 192, 193
parametrizing 119
processing strategy of 109
U22418-J-Z125-6-76
restart 53–56, 337
search strategy 67
share module 51
specify number of tasks 92
starting 38–49
starting several 49
STXIT 176
terminating 52, 197, 337
DBH administration 173–339
DBH catalog ID 96, 115, 298
DBH forms (SESMON) 403–424
I/O 403
OPTIONS 405
overview 380
SERVICE ORDERS 406
SQL INFORMATION 411
STATEMENTS 413
SYSLST 443
SYSTEM INFORMATION 416
SYSTEM THREADS 421
TASKS 419
DBH ID 78, 115
DBH messages 286
DBH name 49, 91, 191
DBH options 63, 66, 70–143
ACCOUNTING 71
displaying 313
higher-level 66
information on (SESMON) 405
lower-level 66
overview 66
reading in 119
USERS 140
DBH start parameters
END statement 40, 73, 76, 119
entering 45
entering for the independent DBH 41
entering for the linked-in DBH 48
maximum values 61
DBH start statement 63, 64, 73, 76, 119
overview 64
DBH statistical analysis (SESMON) 384
DBH statistics (SESMON) 378
DBH-IDENTIFICATION 66, 90
555
Index
DBH-MENU (SESADM) 185, 187, 188, 189
DBH-NAME 66, 91, 165, 191, 214
DBH-NAMES (SESMON parameter) 384
DBHs, selecting (SESMON) 389
DBH-specific file 49, 94
DBH-TASKS 66, 92, 92
DBS1 record 529
accounting 71, 529
DCAM 140, 163, 207
DCAM messages (SESMON) 396
DCN 2
see SESDCN
DCN forms
overview (SESMON) 380
SESMON 394–402
SYSLST (SESMON) 441
DCN LOG 161
DCN name 158, 160, 167, 192
DCN operation information (SESMON) 398
DCN options 158
information on (SESMON) 398
overview of 158
DCN statistics (SESMON) 378
DCN-IDENTIFICATION 158, 159
DCN-MENU (SESADM) 185, 190
DCN-NAME 167, 192, 214
DDL statements (SESMON) 411
deadlock (SESMON) 401
DEFECT (access function) 294
defect (space state) 322
defective 463, 464, 465
DEL,DB 271
DEL,PRO-NAME 271
delete access mode 490
description format
of administration statements 204
of DBH start parameters 68
device (data type) 16
DEVICE-TYPE 97, 298
DIAG-DUMP 475
diagnostic utilities 472
diagnostics documentation 39, 147, 472, 484
diagnostics traces 477–478
displacement mode for buffers 67
556
displaying 315
active CALL DML requests 195, 307
active databases in the distribution rule 198,
315
active users 195, 198, 309, 331
active users per space 195, 322
DBH option MEDIA-CATALOG 196, 311
DBH options 196, 313
entries in the CALL DML table catalog 196,
319
entries in the SQL database catalog 196, 324
inactive SQL users 195, 317
locked spaces 195
open transactions 195, 198, 327
distributed databases 2
distributed processing 145–172
distribution component, see SESDCN
distribution rule 152, 164, 166, 213, 252, 270,
315
updating 153, 161
DML statement, canceling 197, 226
DML statements (SESMON) 399
DSSM 50
DUMP 289
Dump 461
dump 236, 471, 472
conditional 474
creating 197, 198, 236
generate 461
requested 475
dump file 288, 473, 474
DUMP[,STOP] 236
duration (SESMON) 402
E
elapsed real time 354, 358
elapsed time 358
elapsed time in contingency (SESMON) 397
ELAPSED-TIME (SESCOSP param.) 354, 358
END statement 147
DBH start parameters 40, 65, 65, 73, 76, 119
SEPA 507
SESADM 183, 193
SESDCN control statements 150, 157
U22418-J-Z125-6-76
Index
end time 352
END-FOREIGN-COPY 237
END-LOCK-SEQUENCE 224, 239
entering
DBH options 41, 64, 66
DBH start parameters 64
DBH start statements 41, 64
SESADM statements 181
SESDCN control statements 147, 156
entries
in the CALL DML table catalog 73, 102, 196,
215, 272, 319
in the distribution rule 213, 270
in the SQL database catalog 76, 122, 196,
218, 274
in the SQL database directory 76
ENTRY-1 74, 77
ENTRY-2 80
error diagnosis 472
error event 471
error file 486
error messages, see messages
error weights 458, 459–466
overview of 459
escalation 135, 263
ESQL-COBOL (manual) 5
evaluating data (SESMON) 378
evaluation (SESCOSP) 341
event 532
event name 532
example (SEPA) 508
exception file, see error file
exit routine 110 534
expert mode (SDF) 182
EXPLAIN pragma 486
external restart 471
DBH session 53, 56
F
FASTPAM 537
FCOPY,END 238
FCOPY,PREPARE 267
file bottleneck 467, 468
file counter 117
U22418-J-Z125-6-76
filename (data type) 17
FILE-RESOURCES 66, 93
files 461
CO-LOG file 117, 296, 461, 483
configuration file 48, 181, 475, 477
cursor files 49, 88, 94
DBH-specific files 49, 94
dump file 288
SESDLGk backup file 153
session-specific 66, 117
TA-LOG file 49, 53, 94, 483
temporary work files 94
update log files 66
WA-LOG file 49, 53, 94, 483
filter condition 534
fixed (data type) 16
foreign copy
closing catalog 197
copy pending (space status) 197
foreign user ID
CAT-REC file 227
forms (SESMON) 391–424
overview 379
SYSLST 440–448
FREE (database status) 294
FREE administration command 269
FREE,USER,INACT
administration command 269
full qualification, user-identification 205
G
gen (suffix for data type) 27
global index 25
glossary 6
Glossary (manual) 6
GO,TA 276
GO,USER 277
GO-TA 276
group commit SESMON 423
557
Index
H
higher-level DBH option 66
HIGH-LEVEL 105, 255
hit rate (SESMON) 404, 444
HOLD,TA 241
HOLD,USER 242
HOLD-TA 241
HOLD-TRANSACTION-ADMISSION 240, 276
HOLD-USER-ADMISSION 242, 277
home configuration 166, 167
host 83, 163, 191, 192, 214, 244, 349, 516
host name in distribution rule, changing 198, 252
HOST-NAME 83, 163, 191, 192, 206, 214, 244,
252
SESCOSP parameter 349
HOST-NAME (SEDI70 parameter) 516
http
//FSC-manualshop.com 541
//manuals.fujitsu-siemens.com 541
I
I/O form (SESMON) 403, 443
I/O statistics for each statement step 369, 370
identification of the system-internal user 210
identification of users 205–209
identifying
DBH 66, 90, 191
SESDCN 159, 192
IMON 31, 38, 539
inactive SQL users 317
display 195, 317
INACTIVE-TIME 269
inactivity time 123, 196, 303
INACTIVITY-TIME 123, 135, 161, 263
independent DBH
starting 40–46
terminating 52
index 25
INDEX-EVALUATION 110
INFORM-PROGRAM 174, 175, 387
INITIAL 114, 127, 138
input file
DBH start parameters 41, 48
SESADM statements 181, 182, 183
558
SESDCN control statements 147, 149, 169,
171
input/output statistics
for each statement 344, 367, 368
input/outputs, number of 355
INPUT-FILE (SEDI70 parameter) 512
INPUT-FILE (SESCOSP parameter) 345
inquiry and response areas 137
inquiry area (CALL DML) 177
integer (data type) 18
interactive mode 148, 182
intermediate results 88
internal restart, DBH session 53
internal statement format 141
internal terminal number 351
INTERNAL-SORT-LIMIT 124, 260
INTERRUPT-EXECUTION 110
interrupting processing 110, 258
interrupting SESMON 387
interval
CPU time 353
evaluating requests during 352
SESMON 384, 390
IO-STATISTICS
(SESCOSP parameter) 357
SESCOSP report structure 367, 368
isolation level 135
ITN 351
J
job monitoring 60
job variables 57, 60, 471
foreign user ID 57
monitor program 33
request and program control
JOBCLASS 115
JOB-ID (SESMON) 387
JV, job variables (BS2000) 57
K
K2 key 387
kernel control (SESMON)
57
412
U22418-J-Z125-6-76
Index
L
LIMIT 258, 261
limit values, see limiting
limiting
entries in the CALL DML table catalog 67,
102
entries in the SQL database catalog 67, 122
number of accessible spaces 67, 120
number of threads 133
number of users 67, 140
parameters of the DBH session 67, 129
parameters of the SESDCN session 160
service tasks 66, 113
SESDCN session parameters 158
SQL parameters 67, 123
link and load module, see LLM
link name
BLSLIB 540
logical 165, 166, 167
SESAMOML 539
linked-in DBH
administration 194
starting 47
STXIT routine 176
terminating 52
LINK-NAME 165
Linux 1
LLMs
execution phase of SESDCN 146
execution phase of the DBH 38
loading as subsystems 50
local access 168
local user 208, 209
lock
catalog 211, 239
object (SESMON) 449
space 211, 239
time (SESMON) 401
transaction 134
transaction (SESMON) 423, 449
lock sequence 224, 239
starting 197, 224
terminating 197, 211, 239
LOCKED (access function) 294
U22418-J-Z125-6-76
LOCK-ESCALATION 135, 263
LOCK-TIME 135, 161, 263
log file (SESMON) 408
log files 472, 483
LOG-FILES, SESMON 444
LOGGING 267
logging
call trace 300, 478
DBH request logging 296, 483
evaluating 341
job accounting 72
message trace 286, 304, 478
request accounting 284
service task activities 484
logical accesses (SESMON) 403, 444
logical database name 76, 165, 213, 215, 218
logical file 67, 126, 261, 307, 416
logical input/outputs, number of 355
logical link name 165, 166, 167
LOGICAL-ROLLBACK 107
low (suffix for data type) 22
lower-level DBH option 66
LOW-LEVEL 105, 255
LSQ,ABORT 212, 239
LSQ,BEGIN 225
M
mail messages (SESMON) 396
main-memory dump, see dump
man (suffix for data type) 27, 28
Management Information Base 452
management platform 377, 379, 381, 452
mandatory (suffix for data type) 28
master DCN 153, 156, 398
master-subagent principle 452
MAXIMUM 115, 127, 138
maximum values 61, 155
MAX-ISOLATION-LEVEL 135
media catalog 66, 94
MEDIA-CATALOG 66, 94, 311
memory dump, see dump
memory extension (SESMON) 445
memory extensions, service task
(SESMON) 445
559
Index
memory pool 153, 161
memory requirements 126
message file 39
message fragmentation (SESMON) 396
message fragments (SESMON) 396
message trace 286, 304, 477, 478
message volume (SESMON) 395
messages 390, 467
SESMON 397
special situations 467
Messages (manual) 6
metasyntax SDF 12
MIB 452, 453
microseconds (SESCOSP) 358
Migrating ... (manual) 6
milliseconds (SESCOSP) 358
MODE 225
MODIFY ADMINISTRATION 243
MODIFY-CATALOG-ACCESS-RIGHTS 246
MODIFY-CATID-LIST 249
MODIFY-DISTRIBUTION-RULE-ENTRY 153,
252
modifying, see changing
MODIFY-REQUEST-CONTROL 254, 291
MODIFY-RESTART-CONTROL 256
MODIFY-RETRIEVAL-CONTROL 258
MODIFY-SDF-OPTIONS 41, 182
MODIFY-SQL-SORT-LIMIT 260
MODIFY-SUBORDER-LIMIT 261
MODIFY-TEST-OPTIONS 147
MODIFY-TRANSACTION-SECURITY 262
module library 539
module SESFSxx 487
monitor job variable 60
MSG 100
MSG-OUTPUT 66, 99
multi-db processing 1
multitask sorting 113
multitasking mode 49
multithread mode 133
multi-user operation 1
560
N
NAME 270
name (data type) 18
naming the DBH 66, 91, 93, 94, 99, 102, 103,
109, 111, 113, 117, 119, 120, 122, 123, 125,
126, 128, 129, 130, 133, 134, 137, 139, 140,
141, 158, 164, 166, 191, 192, 193
network 2, 166
network access path 167
NEW-NAME 252
NEW-PASSWORD 244
nonexpert mode (SDF) 182
notational conventions 10
NUMBER-INDEX-VALUES 136, 263
NUMBER-OF-LOGICAL-IO (SESCOSP
parameter) 355
NUMBER-RECORDS 136, 263
O
object events 532
object, locked (SESMON) 449
odd (suffix for data type) 27
OLD-TABLE-CATALOG 67, 102, 215, 272
online application 2
OPEN message 99
OPEN-CLOSE-MSG 100
openUTM 83, 163, 208, 209, 234, 479
OPERATING 175, 387
operational data, outputting (SESMON) 377
OPT 314
OPT,ACCESS 248
OPT,ADM 245
OPT,CDBC-DEL 273
OPT,CDBC-INFO 321
OPT,CDBC-INS 217
OPT,CDBC-REUSE 279
OPT,DBC-DEL 275
OPT,DBC-INFO 326
OPT,DBC-INS 221
OPT,DBC-UPD 295
OPT,DIAG 290
OPT,INACT 303
OPT,MEDIA 312
OPT,REQ-CON 255, 292
U22418-J-Z125-6-76
Index
OPT,RESTART 257
OPT,RET-CON 259
OPT,SAT 293
OPT,SORTLIMIT 260
OPT,SUBORDERS 261
OPT,TA-SEC 263
OPTIONS form (SESMON) 405
options, see DBH options 63
options, see DCN options 158
OUTPUT 286, 287, 301, 305
(SEDI70 parameter) 514
SESCOSP parameter 345
SESMON parameter 384
output destination (SESMON) 390
output masks (SESMON) 390
output medium (SESMON) 390
output to file (SESMON) 390, 425
outputs of the DBH 99
overview
DBH options 66
of administration statements (DBH) 195,
196, 197
of administration statements (SESDCN) 198
of DBH administration statements 195–197
of DBH start statements 64
of DCN options 158
of statistical output (SESMON) 379
OVERVIEW form (SESMON) 398, 442
P
pages per memory extension (SESMON) 445
pages/extension (SESMON) 445
parallel processing 1
parametrizing SESDCN 168
parametrizing the DBH 119
partial qualification, user-identification 205, 208,
209
partial-filename (data type) 19
PASSWORD 78, 83, 191, 192, 219
password
administration (DBH) 82, 244
administration (SESDCN) 162
BS2000 78, 219
SESADM 191, 192
U22418-J-Z125-6-76
password (SEPA) 489, 499
assigning global authorization 499, 500
changing 501
deleting 500
generating 499, 500, 508
information 507
password catalog SEPA 489
password protection 158, 162
CALL DML table 489
SEPA 489
V1 database 489
password violation 111
password, administration (DBH) 83
path-compl (suffix for data type) 22
PERCENTAGE-RECORDS 136, 263
performance 341
Performance (manual) 6
performance monitor 37, 377
permitted inactivity time, setting 196, 303
PHYS-CATALOG-NAME 219, 228, 231, 238,
266, 275, 295, 325
physical accesses (SESMON) 403, 444
physical database name 76, 218, 219, 324
PHYSICAL-NAME 78
plan buffer 61, 124
SESMON 411
PLANS 124
pool containers (SESMON) 396
pool locks (SESMON) 396
pool utilization (SESMON) 395
pools (SESMON) 378
posix-filename (data type) 19
posix-pathname (data type) 19
PREFETCH-BUFFERS form (SESMON) 392
prepare to commit 234
SESMON 399
PREPARE-FOREIGN-COPY 265
prerequisites
for administration using a CALL DML
program 177
for restarting the DBH session 54
for restarting the SESDCN session 152
for starting SESDCN 146
for starting the DBH 39
561
Index
PRIMARY-ALLOCATION 96, 116, 298
primary-key range 506
primary-key value 490, 505
primary-key-group value 505
printable form of statements 357
printer output (SESMON) 381, 439
priority classes 103, 105
priority control 196, 254, 291
privilege
OPERATING 175, 387
TSOS 175, 387
PRIVILEGE-VIOLATIONS 112
processing
aborting 110
interrupting 110
processing sequence 103
processing strategy 67, 130
of the DBH 109
processor 167
PROCESSOR-NAME 167
product-version (data type) 20
program, monitor (job variable) 33
PROTOCOL 297
PROTOCOL (SESCOSP parameter) 357
PTC (SESMON) 399
PTC state 161
PTC transaction 234, 280
committing 197, 234
rolling back 197
Q
QUEUE-1 103, 104, 255
QUEUE-2 103, 104, 255
QUEUE-3 103, 104, 255
QUEUE-PRIORITY 104
QUEUE-RANGE 105
quotes (suffix for data type)
28
R
RAV (BS2000) 71, 284, 529
READ (access function) 79, 219, 221, 247, 248,
322
read access 79, 219, 247
read access mode 490, 492
562
read and write access 79, 220, 248
reading in the DBH options 119
README file 6
real time 354, 358
RECORDS-PER-CYCLE 116
RECOVER PROGRESS (SESMON) 408
recovery request (SESMON) 410
reference to table in CALL DML table catalog
creating valid 196
references 3
refresh time (SESMON) 384, 390
REFRESH-TIME (SESMON parameter) 384
RELEASE-USER-RESOURCES 268
releasing resources 197, 268
Reliant UNIX 1
remote access 158, 161, 167, 169
remote computer 153, 158, 161
remote DCN 152, 161, 166
remote DML (SESMON) 399
remote user 208, 209
REMOTE-ACCESS 158, 161
REMOVE-DISTRIBUTION-RULE-ENTRY 270
REMOVE-OLD-TABLE-CATALOG-ENTRY 272
REMOVE-SQL-DB-CATALOG-ENTRY 274
removing
database entry from the distribution rule 198,
270
entry from the CALL DML table catalog 196,
272
entry from the SQL database catalog 196,
274
REPLICATION 79, 220
replication 57
REPORT-FORMAT (SESCOSP parameter) 356
request accounting 71, 284
request log file 117, 296, 341, 345
request logging 296
evaluating 341
request sequence 103
REQUEST-CONTROL 67, 103, 254, 255, 291
requests for locks (SESMON) 396
RESET 283
resource bottlenecks (SESMON) 395
resource statistics 357, 358, 371, 372
U22418-J-Z125-6-76
Index
resource utilization (SESMON) 377
resources 268, 341
releasing 197, 268
response area (CALL DML) 177
restart
computer (SESDCN) 153
configuration 153
controlling duration of 67
DBH 106
DBH session 53
external, see external restart
openUTM 154
SESDCN session 152
start sequence (SESAM/SQL-DCN) 154
synchronization (SESAM/SQL-DCN) 154
restart duration, influencing 196
restart information 56, 337
restart log file, see WA-LOG file
RESTART-CONTROL 67, 106, 256, 257
RESUME-TRANSACTION-ADMISSION 240,
276
RESUME-USER-ADMISSION 242, 277
resuming
transaction admission 197, 198
transaction processing 276
user admission 198, 277
retrieval (SESMON) 422
retrieval statement 84, 88, 258
retrieval transactions (SESMON) 422
RETRIEVAL-CONTROL 67, 109, 258
REUSE-OLD-TABLE-CATALOG-ENTRY 278
rollback criteria 134
ROLLBACK-PTC-TRANSACTION 234, 280
ROLLBACK-TRANSACTION 282
rolled-back transactions (SESMON) 400, 422
rolling back
PTC transaction 197
transaction 197, 198, 282
RPTC 281
RUNTIME (SESMON parameter) 384
runtime behavior 378
runtime SESMON 384
U22418-J-Z125-6-76
S
SAT 293, 531
SAT audit attribute 532
SAT object 532
SATLOG record 531
SAT-SUPPORT 112
SATUT 531, 532
scan, see SQL scan
schema 74, 319
evaluating requests 348
SCHEMA-NAME 74, 216
SCHEMA-NAMES (SESCOSP parameter) 348
screen forms (SESMON), overview 379
SDF dialog interface 39
SDF selection screens (SESADM) 184
DBH-MENU 187, 188, 189
DCN-MENU 190
START-MENU 186
SDF, representation of syntax 12
search
secondary indexes 109
sequential 109
search strategy of the DBH 67
secondary index, searching 109
SECONDARY-ALLOCATION 96, 116, 298
SECOS 531
SECURITY 66, 111
security administrator 532
security error 464
SEDI61L 47
SEDI63 STXIT 176
SEDI63L 47
SEDI70, start 510
SEL (SESMON) 387
SELECT 228, 231, 238, 258, 266, 273, 275, 295,
320, 325
SEDI70 parameter 515
SESCOSP parameter 346
SELECTION form (SESMON) 382, 387, 389
selection screens 184
SEMSTAT, link name (SESMON) 384
SEND-MSG 174, 387
sep (suffix for data type) 27
563
Index
SEPA 489
1P0 statement 498
1P1 statement 499
1P2 statement 502
1P3 statement 504
1P3N statement 504
1P4 statement 506
1P5 statement 507
END statement 507
statements 495, 498
SEPA statement sequences 497
sequence for request processing 103
sequence number, user-specific 351
sequential search 109
server 1
SERVICE ORDERS form (SESMON) 406, 445
service tasks 61, 113, 378, 445, 484
SERVICE TASKS form (SESMON) 409, 445
SERVICE-TASKS 66, 113
SESADM 178–193, 377
SESADM control statements 181, 190
END statement 193
START-DBH-ADMINISTRATION 191
START-DCN-ADMINISTRATION 192
SESADM input file 181, 182
SESADM statements, entering 181, 182, 183
SESADM, starting 181
SESAM (LLM name) 38
SESAM messages 304, 477
SESAM program 31
SESAM start commands 31, 539
SESAM, SAT object 533
SESAM/SQL manuals 5
SESAM/SQL monitor 173
SESAM/SQL utility SEPA 489
SESAM/SQL-DCN 2, 145–172
SESAM/SQL-LINK 47
SESAM/SQL-Server 1
SESAM-DBAccess (JDBC) 2
SESAM-MON-Subagent 451
SESAMOML 539
SESCOSP 296, 341
input parameters 344
starting 342, 343
564
SESDCN
LLM name 146
parametrizing 158
restart 152–154, 252
share module 51
share modules 146
starting 145, 146–151
STXIT 176
terminating 152, 198, 339
SESDCN administration 173–339
SESDCN control statement
ADD-DISTRIBUTION-RULE-LIST 164
ADD-NETWORK-LIST 166
END statement 150, 157
entering 147, 156
notes on entering 150
SET-DCN-OPTIONS 158
SESDCN forms (SESMON) 394–402
APPLICATIONS 394
CAPACITY 395
OVERVIEW 398
overview 380
SYSLST 441
TRANSACTIONS 400
SESDCN name, see DCN name
SESDCN pool (SESMON) 398
SESDCN session, information (SESMON) 398
SESDCN statistics (SESMON) 378
SESDLG-PASSWORD 158
SESFSxx 487
SESLINK 47
SESMON 178, 377, 377
administration 387
automatic termination 388
interrupting 387
output not upward-compatible 378
overview of 379
running 382
runtime 384
start parameters 382
terminating 384, 387
SESMON forms 391–424
overview 379
SYSLST 440–448
U22418-J-Z125-6-76
Index
session identification 117
SESSION-ID 118
SESSION-LOGGING-ID 66, 117
session-specific files 66, 117
SESUTI 178, 377
SET-ACCOUNTING-PARAMETER 284
SET-DBH-MSG-TRACE 286, 478
SET-DBH-OPTIONS 64, 119
SET-DCN-OPTIONS 158, 243
SET-DIAGNOSIS-DUMP-PARAMETER 288,
474
SET-MONITOR-OPTIONS (SESMON) 382, 383
SET-REQUEST-CONTROL 254, 291
SET-SAT-SUPPORT 293
SET-SQL-DB-CATALOG-STATUS 294
SET-TUNING-TRACE 296, 341, 345, 353, 483
SET-USER-CALL-TRACE 300, 478
SET-USER-INACTIVE-TIME 303
SET-USER-MSG-TRACE 304, 478
SEZTXT.ASS 59
share modules 50, 51, 146
SHOW-CALL-DML-SUBORDERS 307
SHOW-CATALOG-USERS 309
SHOW-DBH-MEDIA-CATALOG 311
SHOW-DBH-OPTIONS 313
SHOW-DISTRIBUTION-RULE-ENTRIES 315
SHOW-INACTIVE-SQL-USERS 317
SHOW-OLD-TABLE-CATALOG-ENTRIES 319
SHOW-SPACE-USERS 322
SHOW-SQL-DB-CATALOG-ENTRIES 294, 324
SHOW-TRANSACTIONS 327
SHOW-USERS 331
SHOW-USER-SPACES 335
size, setting
of cursor buffer 67, 88
of system-data buffer 67, 128
of transfer container 67, 137
of user-data buffer 67, 139
of work container 67, 141
SNMP 377, 379, 381, 452
SNMP agent 452
SNMP manager 452
SoftBooks 541
Solaris 1
U22418-J-Z125-6-76
SORT 113
sort operations (SESMON) 412
sort records 196, 260
sort request (SESMON) 410
sort sequence 487
sort subtask 116
sorting 113, 124
SPACE 336
space 67, 120, 120, 322, 323, 486
closing 197, 232
displaying 195
evaluating requests 348
internal number 376
state 322
space (SESMON) 443
space requirement
to store internal statement formats 85
SPACE-NAME 323
SPACE-NAMES 266
SPACE-NAMES (SESCOSP parameter) 348
SPACES 67, 120
special situations, messages 467
specifying the number of tasks, DBH 92
SQL access plan 124, 126, 137, 141, 411, 486
SQL cursors 61
SQL database catalog 76, 122, 218, 274, 324
SQL INFORMATION form (SESMON) 411, 446
SQL interface 67, 123
SQL scan 67, 126, 137, 141, 261, 416
SQL server 1
SQL Statements (manual) 5
SQL statements (SESMON) 411
SQL users 317
SQL-DATABASE-CATALOG 67, 122, 218, 274
SQL-SUPPORT 67, 123, 260, 303
SSL statements (SESMON) 411
start commands 31
start parameters (SESMON) 382
start parameters, see DBH start parameters
start sequence (SESDCN restart) 154
start statements, DBH, see DBH start statements
start time 352
START-DBH-ADMINISTRATION 182, 191
START-DCN-ADMINISTRATION 182, 192
565
Index
starting (SESADM) 181
DBH administration 191
SESDCN administration 192
starting (SESDCN restart) 154
starting lock sequence 197, 224
starting SESDCN
batch mode 147
general prerequisites 146
interactive mode 148, 149
several SESDCNs 151
starting several DBHs 49
starting several SESDCNs 151
starting the DBH
batch mode 40
general prerequisites 39, 539
independent DBH 40
linked-in DBH 47
sample procedure 46
several DBHs 49
START-MENU (SESADM) 185, 186
START-NUMBER 118
START-PROGRAM 31, 539
START-SEPA 32
START-SESAM-ADMINISTRATION 31, 181
START-SESAM-CALL-DML-DIALOGUE 32
START-SESAM-DBH 31, 38
START-SESAM-DCN 31, 146
START-SESAM-LOG-FILE-EVAL 510
START-SESAM-LOG-FILE-EVALUATION 32
START-SESAM-PERF-MONITOR 382
START-SESAM-PERFORMANCE-MONITOR 31
START-SESAM-RETRIEVAL-DIALOGUE 32
START-SESAM-TUNING-TRACE-EVAL 342
START-SESAM-TUNING-TRACEEVALUATION 32
START-SESAM-UTILITY-MONITOR 32
START-SESLK-CDML-DIALOGUE 32
START-SESLK-RETRIEVAL-DIALOGUE 32
START-SESLK-UTILITY-MONITOR 32
START-SNMP-SESAM-MON 454
state
of space 322
of transaction (SESMON) 424
transaction-free 240
566
statement
evaluate 518
evaluating 341, 351, 360, 361
input/output statistics 344
printable form 357
representation of syntax 12
statement area (CALL DML) 177
statement statistics 357
statement steps, evaluating 341, 357
STATEMENT-NUMBER (SESCOSP
parameter) 351
statements (SEPA), overview 495
STATEMENTS (SESCOSP parameter) 351
STATEMENTS form (SESMON) 413, 447
statistical output, overview of (SESMON) 379
statistics 356
SESCOSP 341, 357
SESMON 377
STATUS 295
status
of database 294, 324
of transaction 327
status dump 467
STEP-COMPLEXITY
SESCOSP parameter 357, 358
SESCOSP report structure 371, 372
STEP-IO-STATISTICS
(SESCOSP report structure) 370
SESCOSP parameter 357
SESCOSP report structure 369
STOP 339
SESMON 384
STOP,DELETE 338
STOP,KEEP 471
STOP[,KEEP] 338
STOP-DBH 52, 337
STOP-DCN 152, 339
STOP-SNMP-SESAM-MON 456
storage information 94
STORAGE-SIZE 67, 125
STRING-FORMAT
SESCOSP parameter 357
SESCOSP report structure 360, 361
structured-name (data type) 20
U22418-J-Z125-6-76
Index
STXIT routine 176, 471
sub TAs per user (SESMON) 397
SUBORDERS 67, 126, 261
suborders 61, 126, 196, 261
SESMON 416
subsystems 36, 50
subtransactions (SESMON) 397
suffixes for data types 13, 22
SUPPORT 298
SUPPORT-n 98
suspend
transaction admission 197, 198
user admission 198
suspending
transactions 240
user admission 242
switches, see task switches
switching the SYSLST file 197, 223
symbolic attribute name 503
synchronization 154
synchronous accesses (SESMON) 396
syntax description 12
syntax representation 12
Syntax representation SDF 12
SYSLST 99, 100, 223
SYSLST file, switching 197, 223
SYSLST output (SESMON) 381, 390, 439
SYSOUT 99, 100
system administration 81
system administrator 82, 163
system bottleneck 466
system data, outputting (SESMON) 377
SYSTEM INFORMATION form (SESMON) 416,
447
system limits, see maximum values
SYSTEM STRATEGIES 67
system threads 67, 131
SYSTEM THREADS form (SESMON) 421, 448
system user identification 82, 83
system, defective 465, 466
system-access data 128
system-data buffer 61, 128
SYSTEM-DATA-BUFFER 67, 107, 128, 257
system-internal user 210
U22418-J-Z125-6-76
SYSTEM-LIMITS 67, 129, 158, 160
SYSTEM-STRATEGIES 130
SYSTEM-THREADS 67, 131
T
table
evaluating 348
internal number 376
name 73
table catalog, see CALL DML table catalog 102
TABLE-NAME 74, 216
TABLE-NAMES (SESCOSP parameter) 348
TAC 350
TA-LOG file 49, 53, 94, 96
TALOG-LIMIT 107, 257
TALOG-SUPPORT 96
task category 40
task sequence number (SESMON) 387
task switches 470
SESMON 388
TASKLIB module library 539
tasks
maximal/actual (SESMON) 392, 395
per application (SESMON) 396
transaction application (SESMON) 392, 395
TASKS form (SESMON) 419, 448
temp-file (suffix for data type) 27
temporary work file 94
terminal 351
terminal number 351
TERMINAL-NUMBER, SESCOSP
parameter 351
terminating
DBH 52, 197, 337
lock sequence 197, 239
lock sequence of another user 197
SESADM 193
SESDCN 152, 198, 339
SESDCN in trusted mode 152
SESMON 384, 387, 388
termination statistics
SESCOSP report structure 375
text (data type) 20
THREADS 67, 133
567
Index
threads 61, 133
throughput, improving 341
TIAM 207
time (data type) 20
time behavior 341, 377
time period
CPU time 353
elapsed time 354
evaluating requests during 352
SESMON 384, 390
time specification (SESCOSP) 358
TIME-LIMIT 303
TIME-PERIOD (SESCOSP parameter) 352
TIME-PRECISION (SESCOSP parameter) 353,
354, 358
timesharing mode 140, 160
timesharing user 206
evaluating requests 349, 516
TO-FILE 223
TRACE 286, 287, 296, 297, 301, 302, 305, 306
trace 286, 300, 479
TRACE statement 477
TRANSACTION
SESCOSP parameter 357
SESCOSP report structure 373, 374
transaction 161, 240, 282, 327, 461
(SESMON) 399, 422
evaluating requests 341, 357
locking 134
rolling back 282
SESMON 422
SESMON) 400
state (SESMON) 424
suspending 240
transaction admission
resuming 197, 198
suspending 197, 198
transaction application
(SESMON) 391
SESDCN 160
SESMON 394
transaction code 350
transaction lock (SESMON) 423, 449
transaction lock, database entry 246
568
transaction log file, see TA-LOG file
transaction management 134
transaction management files, see TA-LOG files
transaction mode 140, 160
transaction monitor 2
transaction processing 2, 240, 276
resuming 276
transaction security 136
changing parameters 196
transaction state 327
transaction statistics 357, 373, 374
transaction, rolling back 197, 198
transaction-free state 240
TRANSACTIONS form (SESMON) 400, 422,
442, 448
TRANSACTION-SECURITY 67, 134, 262
transfer container 61
TRANSFER-CONTAINER 67, 137
transparent access 2
TSN 206, 208, 209
tsn (SESMON) 387
TSOS 175, 387
U
unauthorized access 489
under (suffix for data type) 23
unique user identification 208
Universal Transaction Monitor, see UTM
UPD 214
UPD,CID-LIST 251
update access mode 490, 492
update transactions (SESMON) 422
updating CATID list 197
updating distribution rule 153, 161
UPDPRO 253
USER 212, 235, 269, 281, 283, 289, 301, 305,
307, 308, 329, 335
user 83, 517
system-internal 210
user (SESDCN) 163
user (suffix for data type) 28
user admission
resuming 198, 277
suspending 198, 242
U22418-J-Z125-6-76
Index
user identification 205, 208, 209
user name 207
user space 120
closing 197
password-protected 489
physically closing 232
USER,CATALOG 310, 316
USER,INACT 318
USER,PR 334
USER,SPACE 323
USER,TA 330
user-data buffer 61, 139
USER-DATA-ACCESS 110
USER-DATA-BUFFER 67, 107, 139, 257
USER-ID 78, 219, 244
user-identification 206, 208, 209
USERS 67, 140
SEDI70 parameter 516
SESCOSP parameter 349
users 160, 350, 396
active 309, 322, 331
active (SESMON) 392, 395
actual (SESMON) 392, 395
DBH 61, 140, 268, 322
per application (SESMON) 396
per catalog (SESMON) 397
per database (SESMON) 397
SESDCN 160, 242, 277
user-specific sequence number 351
utility
SESCOSP 296
SESMON 377
Utility Monitor (manual) 5
utility statement
COPY 220, 248
SESMON 410, 412
utilization of resources (SESMON) 377
UTM 83, 140, 163, 207, 208, 209, 234, 350, 479,
517
UTM conversation 350
UTM transaction code 350
UTM warm start 337
UTMK record, accounting 71
UTM-SESSION-INFO 338
U22418-J-Z125-6-76
V
V1 database, password protection
vers (suffix for data type) 28
virtual address space 39
VOLUME 97, 116, 298
vsn (data type) 20
489
W
WAIT,HOLD 241
WAIT-EVENT 241
WA-LOG file 49, 53, 86, 94, 97, 483
WALOG-SUPPORT 97
warm start 161
WebTransactions 178, 377
weights 104
wild(n) (suffix for data type) 23
wild-constr (suffix for data type) 25
Windows 1
with (suffix for data type) 22
with-constr (suffix for data type) 25
with-low (suffix for data type) 22
without (suffix for data type) 27
without-cat (suffix for data type) 27
without-corr (suffix for data type) 27
without-gen (suffix for data type) 27
without-man (suffix for data type) 27
without-odd (suffix for data type) 27
without-sep (suffix for data type) 27
without-user (suffix for data type) 28
without-vers (suffix for data type) 28
with-under (suffix for data type) 23
with-wild(n) (suffix for data type) 23
work container 141
(SESMON) 417
WORK-CONTAINER 67, 141
WORK-FILES 115
World Wide Web 178, 377
WRITE (access function) 79, 220, 247, 248, 322
write access 79, 220, 247
write thread 131, 421
maximum value 61
WRITE-THREADS 131
569
Index
X
x-string (data type) 21
x-text (data type) 21
570
U22418-J-Z125-6-76
Contents
1
1.1
1.2
1.3
1.3.1
1.3.2
1.4
1.5
1.6
1.6.1
1.6.2
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Brief product description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Summary of the contents of the manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Summary of the contents of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Guide to the SESAM/SQL manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
README file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Changes in V3.2 made since V3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Non-SDF notational conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SDF syntax representation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.2
2.2.1
2.2.2
2.2.2.1
2.2.2.2
2.2.2.3
2.2.3
2.2.4
2.2.5
2.3
2.3.1
2.3.2
2.4
2.4.1
2.4.2
2.4.3
Working with the SESAM/SQL DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting SESAM/SQL programs via start commands . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the start commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Operands of the start commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tasks of the start commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying the correction delivery status with the start command . . . . . . . . . . . . . . . . .
Starting the SESAM/SQL DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Startup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the independent DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command sequence for starting the independent DBH in batch mode . . . . . . . . . . . . .
Entering the DBH start parameters for the independent DBH . . . . . . . . . . . . . . . . . . . .
Example of a procedure for starting the independent DBH . . . . . . . . . . . . . . . . . . . . . .
Starting the linked-in DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting several SESAM/SQL DBHs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SESAM/SQL share modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminating the SESAM/SQL DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminating the independent DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminating the linked-in DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarting a DBH session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restart requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling the duration of the restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Carrying out an external restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U22418-J-Z125-6-76
29
31
31
33
34
36
38
39
40
40
41
46
47
49
50
52
52
52
53
54
55
56
Contents
2.5
2.5.1
2.5.2
2.6
Job variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Job variables for controlling requests and programs . . . . . . . . . . . . . . . . . . . . . . . . . . .
Monitor job variables for job monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum values for working with the SESAM/SQL DBH . . . . . . . . . . . . . . . . . . . . . . .
57
57
60
61
3
3.1
3.1.1
3.1.2
3.2
3.2.1
3.2.2
DBH start statements and options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Overview and notes on entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
DBH start statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
DBH options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Descriptions in alphabetical order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Description format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Alphabetical reference section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
ACCOUNTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
ADD-OLD-TABLE-CATALOG-LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ADD-SQL-DATABASE-CATALOG-LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
ADMINISTRATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
COLUMNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
CONFIGURATION-NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
CPU-RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
CURSOR-BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
DBH-IDENTIFICATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
DBH-NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
DBH-TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
FILE-RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
MEDIA-CATALOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
MSG-OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
OLD-TABLE-CATALOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
REQUEST-CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
RESTART-CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
RETRIEVAL-CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
SECURITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
SERVICE-TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
SESSION-LOGGING-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
SET-DBH-OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
SPACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
SQL-DATABASE-CATALOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
SQL-SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
STORAGE-SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
SUBORDERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
SYSTEM-DATA-BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
SYSTEM-LIMITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
SYSTEM-STRATEGIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
SYSTEM-THREADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
U22418-J-Z125-6-76
Contents
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.2
4.3
4.3.1
4.3.2
4.3.3
4.4
4.5
4.5.1
4.5.2
4.5.3
5
5.1
5.1.1
5.1.2
5.1.3
5.1.3.1
5.1.3.2
5.1.3.3
5.1.3.4
THREADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRANSACTION-SECURITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TRANSFER-CONTAINER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USER-DATA-BUFFER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WORK-CONTAINER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
133
134
137
139
140
141
Distributed processing with SESAM/SQL-DCN . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting the SESDCN distribution component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Startup requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting SESDCN in batch mode and passing control statements . . . . . . . . . . . . . . .
Starting SESDCN in interactive mode and passing control statements . . . . . . . . . . . .
Passing control statements by means of an input file . . . . . . . . . . . . . . . . . . . . . . . . .
Starting several SESDCNs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminating SESDCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarting an SESDCN session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SESDCN restart requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restarting SESDCN on a backup computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronization of DBH, SESDCN and UTM restarts . . . . . . . . . . . . . . . . . . . . . . . . .
Maximum values for working with SESAM/SQL-DCN . . . . . . . . . . . . . . . . . . . . . . . . .
SESDCN control statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering SESDCN control statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax and functions of the SESDCN control statements . . . . . . . . . . . . . . . . . . . . . .
SET-DCN-OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADD-DISTRIBUTION-RULE-LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADD-NETWORK-LINK-LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Examples of SESDCN parametrization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
145
146
146
147
148
149
151
152
152
152
153
154
155
156
156
158
158
164
166
168
DBH and SESDCN administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration using INFORM-PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration using a CALL DML program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administration using SESADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting SESADM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Entering the SESADM statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SDF selection screens for SESADM administration . . . . . . . . . . . . . . . . . . . . . . . . . .
SESADM control statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
START-DBH-ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
START-DCN-ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
173
173
174
177
178
181
181
184
190
191
192
193
U22418-J-Z125-6-76
Contents
5.2
5.2.1
5.2.1.1
5.2.1.2
5.2.2
5.2.3
5.2.3.1
5.2.3.2
5.2.3.3
5.2.3.4
Administration statements and commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Summary of the contents of the administration statements . . . . . . . . . . . . . . . . . . . . .
DBH administration statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SESDCN administration statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equivalent administration statements and commands . . . . . . . . . . . . . . . . . . . . . . . . .
Descriptions in alphabetical order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syntax for the identification of users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Identification of system-internal users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alphabetical reference section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ABORT-LOCK-SEQUENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADD-DISTRIBUTION-RULE-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADD-OLD-TABLE-CATALOG-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADD-SQL-DB-CATALOG-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASSIGN-SYSLST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BEGIN-LOCK-SEQUENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CANCEL-STATEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHANGE-CATLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CHANGE-DALOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CLOSE-SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
COMMIT-PTC-TRANSACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE-DUMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
END-FOREIGN-COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
END-LOCK-SEQUENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HOLD-TRANSACTION-ADMISSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HOLD-USER-ADMISSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-CATALOG-ACCESS-RIGHTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-CATID-LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-DISTRIBUTION-RULE-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-REQUEST-CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-RESTART-CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-RETRIEVAL-CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-SQL-SORT-LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-SUBORDER-LIMIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MODIFY-TRANSACTION-SECURITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PREPARE-FOREIGN-COPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RELEASE-USER-RESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REMOVE-DISTRIBUTION-RULE-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REMOVE-OLD-TABLE-CATALOG-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REMOVE-SQL-DB-CATALOG-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RESUME-TRANSACTION-ADMISSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RESUME-USER-ADMISSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REUSE-OLD-TABLE-CATALOG-ENTRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
195
195
198
199
204
204
205
210
210
211
213
215
218
223
224
226
227
230
232
234
236
237
239
240
242
243
246
249
252
254
256
258
260
261
262
265
268
270
272
274
276
277
278
U22418-J-Z125-6-76
Contents
6
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
ROLLBACK-PTC-TRANSACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ROLLBACK-TRANSACTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-ACCOUNTING-PARAMETER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-DBH-MSG-TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-DIAGNOSIS-DUMP-PARAMETER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-REQUEST-CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-SAT-SUPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-SQL-DB-CATALOG-STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-TUNING-TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-USER-CALL-TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-USER-INACTIVE-TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET-USER-MSG-TRACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-CALL-DML-SUBORDERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-CATALOG-USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-DBH-MEDIA-CATALOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-DBH-OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-DISTRIBUTION-RULE-ENTRIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-INACTIVE-SQL-USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-OLD-TABLE-CATALOG-ENTRIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-SPACE-USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-SQL-DB-CATALOG-ENTRIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-TRANSACTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW-USER-SPACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOP-DBH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOP-DCN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
280
282
284
286
288
291
293
294
296
300
303
304
307
309
311
313
315
317
319
322
324
327
331
335
337
339
Evaluating request logging with SESCOSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Calling SESCOSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SESCOSP input parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The higher-level parameter CREATE-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The individual parameter INPUT-FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The individual parameter OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The individual parameter SELECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SELECT parameter CATALOG-NAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SELECT parameter USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SELECT parameter STATEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SELECT parameter TIME-PERIOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SELECT parameter CPU-TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SELECT parameter ELAPSED-TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SELECT parameter NUMBER-OF-LOGICAL-IO . . . . . . . . . . . . . . . . . . . . . . . . .
The individual parameter REPORT-FORMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The REPORT-FORMAT parameter PROTOCOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The REPORT-FORMAT parameter TIME-PRECISION . . . . . . . . . . . . . . . . . . . . . . . .
341
342
344
344
345
345
346
347
349
351
352
353
354
355
356
357
358
U22418-J-Z125-6-76
Contents
6.3
6.3.1
6.3.2
6.3.3
6.3.4
SESCOSP report output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output of general information and the DBH options . . . . . . . . . . . . . . . . . . . . . . . . . .
Variable parts of the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the termination statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the catalog-space table assignment table . . . . . . . . . . . . . . . . . . . . . . . .
359
360
361
375
376
7
7.1
7.2
7.2.1
7.2.1.1
7.2.1.2
7.2.2
7.2.3
7.3
7.4
Outputting operational data with SESMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the statistical output of SESMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running SESMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting SESMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start parameters when running SESMON in interactive mode . . . . . . . . . . . . . . . . . .
Start parameters when running SESMON in batch mode . . . . . . . . . . . . . . . . . . . . . .
SESMON administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic termination of SESMON operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The layout of the SELECTION form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layout of the forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The CONFIGURATION form APPLICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The CONFIGURATION form PREFETCH-BUFFERS . . . . . . . . . . . . . . . . . . . . . . . . .
The SESDCN form APPLICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SESDCN form CAPACITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SESDCN form OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SESDCN form TRANSACTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form OPTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form SERVICE ORDERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form SERVICE TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form SQL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form STATEMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form SYSTEM INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form SYSTEM THREADS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The DBH form TRANSACTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layout of output to a file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layout of the output records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Option record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CNF record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SESDCN record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DBH record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of editing the SESMON output file with C . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layout of output to SYSLST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Output of statistical data via SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
377
379
382
382
382
382
387
388
389
391
391
392
394
395
398
400
403
405
406
409
411
413
416
419
421
422
425
426
426
428
429
430
433
438
439
451
7.5
7.5.1
7.5.2
7.6
7.7
U22418-J-Z125-6-76
Contents
8
8.1
8.1.1
8.1.2
8.2
8.2.1
8.3
8.4
8.5
8.5.1
8.5.2
8.5.3
8.5.4
8.5.5
8.5.6
8.5.7
8.5.8
9
9.1
9.2
9.2.1
9.2.2
9.2.2.1
9.2.2.2
9.2.3
9.3
9.3.1
9.3.2
9.3.3
9.3.3.1
9.3.3.2
9.3.3.3
Error recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Consistency checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error weights of consistency checks
for message numbers SES6000 and SED9001 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error weights of consistency checks
for message numbers SEN0001, SEN0003 and SEK0001 . . . . . . . . . . . . . . . . . . . . .
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Messages in special situations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting task switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
End of session after ABEND events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Main-memory dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic information in the DB-DIAGAREA of openUTM . . . . . . . . . . . . . . . . . . . . .
DBH-specific log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of helpful administration statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics documents for service tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXPLAIN pragma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error files for SQL and utility statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
466
467
467
470
471
472
473
477
479
483
484
484
486
486
Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Specifying the sort sequence for CALL DML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Password protection with SEPA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The password-protection concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The SEPA statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview of the possible SEPA statement sequences . . . . . . . . . . . . . . . . . . . . . . . .
Statement descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1P0 statement (format 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1P0 statement (format 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1P1 statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1P2 statement and 1P2N statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1P3 statement and 1P3N statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1P4 statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1P5 statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
END statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Example of password generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DA-LOG formatting by SEDI70 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEDI70 call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEDI70 input parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The higher-level parameter CREATE-REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEDI70 report output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File identification records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Variable part of the report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
487
487
489
489
495
497
498
498
498
499
502
504
506
507
507
508
509
510
511
511
521
521
522
523
U22418-J-Z125-6-76
457
458
459
Contents
9.4
9.5
9.5.1
9.5.2
9.6
9.7
Layout of the accounting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Layout of the log records for SAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SESAM object events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auditable information for every SESAM object event . . . . . . . . . . . . . . . . . . . . . . . . . .
Using FASTPAM for SESAM/SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting SESAM programs with /START-PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . .
529
531
532
533
537
539
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
U22418-J-Z125-6-76
SESAM/SQL-Server V3.2A (BS2000/OSD)
Database Operation
User Guide
Target group
The manual is intended for SESAM/SQL system administrators.
Contents
The manual covers the options available to the system administrator for controlling and
monitoring database operation.
Edition: November 2003
File: ses_dbb.pdf
Copyright © Fujitsu Siemens Computers GmbH, 2003.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
This manual was produced by
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
U22418-J-Z125-6-76
Fujitsu Siemens computers GmbH
User Documentation
81730 Munich
Germany
Comments
Suggestions
Corrections
Fax: (++49) 700 / 372 00000
e-mail: manuals@fujitsu-siemens.com
http://manuals.fujitsu-siemens.com
Submitted by
Comments on SESAM/SQL-Server V3.2A
Datasbase Operation
✁
U22418-J-Z125-6-76
Information on this document
On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions.
This document from the document archive refers to a product version which
was released a considerable time ago or which is no longer marketed.
Please note that all company references and copyrights in this document have
been legally transferred to Fujitsu Technology Solutions.
Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the format …@ts.fujitsu.com.
The Internet pages of Fujitsu Technology Solutions are available at
http://ts.fujitsu.com/...
and the user documentation at http://manuals.ts.fujitsu.com.
Copyright Fujitsu Technology Solutions, 2009
Hinweise zum vorliegenden Dokument
Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von
Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions.
Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine
bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche
Produktversion.
Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden
Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.
Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions
angeboten und haben die Form …@ts.fujitsu.com.
Die Internetseiten von Fujitsu Technology Solutions finden Sie unter
http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die
Benutzerdokumentation.
Copyright Fujitsu Technology Solutions, 2009
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising