Votes - , Average rating:
(
)
)
Manafacture: HP
File size: 186.66 kb
File name:
Language of manual:
The document is loading, please wait
 |
The document is loading, please wait
Other manuals for this model:
Desktops - HP Integrity NonStop H-Series (1.98 mb)
Desktops - HP Integrity NonStop H-Series (16.73 mb)
Desktops - HP Integrity NonStop H-Series (957.56 kb)
Desktops - HP Integrity NonStop H-Series (2.38 mb)
Desktops - HP Integrity NonStop H-Series (881.66 kb)
Desktops - HP Integrity NonStop H-Series (965.62 kb)
Desktops - HP Integrity NonStop H-Series (676.93 kb)
Desktops - HP Integrity NonStop H-Series (393.72 kb)
Desktops - HP Integrity NonStop H-Series (776.57 kb)
manual abstract
Managing Records With ENSCRIBE
4. Generating source code for your programs. In this step, you request the DDL
output generator to retrieve the data descriptions from either your source schema
or dictionary, translate them into appropriate source code, and write the translated
descriptions to an EDIT file. The output generator can produce these descriptions
in a variety of programming languages, including C, COBOL 74, COBOL85,
FORTRAN, Pascal, TACL, and TAL. From the EDIT file, you can add the source
statements to your application program.
A dictionary can be used by one application alone, or can be shared by many
applications. Through DDL, you can maintain your dictionary by adding, changing,
or deleting object definitions. Furthermore, you can generate many valuable reports
based on the dictionary’s contents.
Although commonly used for data in a database, a DDL data dictionary can be used
for other elements too. For example, an application that relies on interprocess
messages can define the messages with DDL and maintain them in a dictionary. You
can translate the messages from the dictionary into the appropriate programming
language.
Note that a DDL dictionary is not actively integrated with the database files or source
code it describes. So, if you change a dictionary, DDL does not automatically change
the associated database or code. Conversely, if you change a database or source code
directly, the corresponding dictionary is not affected.
Loading Data into Files
When you are ready to load data values into your existing ENSCRIBE files, you can
do so through FUP. You specify the set of records to be loaded along with other
necessary information. With key-sequenced files, input records can be loaded in
sorted or unsorted order. You can also specify various parameters to optimize the use
of file space and files to contain alternate key records. Typically, only a few FUP
commands are necessary to handle all of your loading requirements.
Accessing and
To manipulate records in ENSCRIBE files, your program calls file system procedures
Manipulating Files
or sequential I/O (SIO) procedures, available through the GUARDIAN 90 operating
system. These two kinds of procedures are mutually exclusive; with any given file,
you can use either one kind or the other, but not both.
File system procedures are a generalized set of file-handling procedures available
to programs written in any source language supported by Tandem. They allow
you to insert, read, update, and delete records in a file. They also allow you to
control concurrent access by locking and unlocking an entire file, a single record,
or a set of records identified by key.
SIO procedures provide TAL programmers with a standard set of procedures for
requesting I/O operations commonly required in system and utility programs.
Their main objective is to allow these programs to treat different file types in a
consistent and predictable way. They manage data transfers involving standard
IN and OUT files, handle the BREAK function from a terminal, allocate control-
block space, specify file-opening characteristics, set and check file-transfer
characteristics, and perform other similar system functions.
4-8
15873 Tandem Computers Incorporated
...Other models in this manual:
Desktops - HP Integrity NonStop J-Series (186.66 kb)
Desktops - HP NonStop G-Series (186.66 kb)
Desktops - HP NonStop L-Series (186.66 kb)