DATAMASTER
User
Manual
Table
of contents
1. Introduction..................................................................................................................................................................................... 4
1.1. Systemflow..................................................................................................................................................................................... 4
1.2. DATAMASTERs selector function........................................................................................................................................... 5
1.3. Principles and structure................................................................................................................................................................ 5
1.3.1. Extension of the definitions........................................................................................................................................................ 6
1.3.2. Redefining files............................................................................................................................................................................. 6
1.3.3. Integration to other systems....................................................................................................................................................... 6
1.4. Calculation of the capacity........................................................................................................................................................... 7
2. Defining a file.................................................................................................................................................................................. 8
2.1. File shortname................................................................................................................................................................................ 8
2.2. Disc number (lu)............................................................................................................................................................................. 8
2.3. File name (description).................................................................................................................................................................. 9
2.4. Number of records in the file........................................................................................................................................................ 9
2.5. Definition of the individual fields................................................................................................................................................ 9
2.5.1. Fieldnumber................................................................................................................................................................................. 10
2.5.2. Fieldname..................................................................................................................................................................................... 10
2.5.3. Fieldformat................................................................................................................................................................................... 11
2.6. Next field....................................................................................................................................................................................... 11
2.7. Selecting a certain field............................................................................................................................................................... 11
2.8. Amending a field definition........................................................................................................................................................ 11
2.9. Listing the fields on the screen................................................................................................................................................. 12
2.10. Deleting and inserting of fields................................................................................................................................................ 12
2.10.1. Deleting fields............................................................................................................................................................................ 12
2.10.2. Inserting fields........................................................................................................................................................................... 12
2.11. Definition of the key‑fields
(index)........................................................................................................................................... 12
2.11.1. Unique and 'duplicate' keys..................................................................................................................................................... 12
2.11.2. Definition of a key‑field............................................................................................................................................................ 13
2.11.3. Amending a key‑field................................................................................................................................................................ 13
2.11.4. Deleting key‑fields..................................................................................................................................................................... 13
2.11.5. Other types of keys................................................................................................................................................................... 13
2.12. Terminating the fielddefinition................................................................................................................................................. 14
2.12.1. Definition of special keys......................................................................................................................................................... 14
2.12.2. Creating the file.......................................................................................................................................................................... 14
2.13. Syntax at the definition of special
keys................................................................................................................................... 15
2.13.1. Fields........................................................................................................................................................................................... 15
2.13.2. Functions.................................................................................................................................................................................... 15
2.13.3. Grouping fields and functions................................................................................................................................................. 15
2.13.4. Examples of key‑constructions................................................................................................................................................ 15
3. Entering data into the file............................................................................................................................................................ 16
3.1. Examples of screen images......................................................................................................................................................... 16
3.2. The basic functions in the file
maintenance‑program............................................................................................................ 17
3.2.1. Special functions in the status‑field........................................................................................................................................ 17
3.2.2. Key 1 (cr‑) Termination of the
program (END)....................................................................................................................... 17
3.2.3. Lamp‑4 (R4) Lock status............................................................................................................................................................ 17
3.3. Function 1 ‑ Creating a new
record........................................................................................................................................... 17
3.3.1. Special functions during dataentering.................................................................................................................................... 18
3.3.2. Key 3 ‑ Backspace after entering
wrong data (...................................................................................................................... 18
3.3.3. Key 2 ‑ Hold field value (@)...................................................................................................................................................... 18
3.3.4. Key 1 (cr‑) Termination of the
dataentering........................................................................................................................... 18
3.3.5. Key 13 ‑ The help‑key................................................................................................................................................................ 19
3.3.6. Lamp‑1 (R1) Permanent help..................................................................................................................................................... 19
3.4. Function 2‑ Inquiry...................................................................................................................................................................... 19
3.4.1. Next record................................................................................................................................................................................... 19
3.4.2. Searching secondaty index‑keys.............................................................................................................................................. 20
3.5. Function 3 ‑ amending a record................................................................................................................................................. 20
3.5.1. Key 4‑8 Increase/decrease the
fieldvalues............................................................................................................................. 20
3.6. Function 4 ‑ Deleting a record................................................................................................................................................... 21
3.7. Function 5 ‑ Defining the
fieldnumber‑sequence................................................................................................................... 21
3.8. Check‑functions........................................................................................................................................................................... 21
3.8.1. Index‑key fields........................................................................................................................................................................... 21
3.8.2. Date‑fields.................................................................................................................................................................................... 22
3.8.3. Check‑code fields....................................................................................................................................................................... 22
3.9. Keyboard layout for the maintenance‑programs.................................................................................................................... 23
4. Searching with Superindex.......................................................................................................................................................... 24
4.1. Searching using Superindex....................................................................................................................................................... 24
4.1.1. Technique when searching....................................................................................................................................................... 24
4.1.2. Searching using several criteria................................................................................................................................................ 24
4.1.3. Interrupting the search.............................................................................................................................................................. 25
4.1.4. Selecting the fields to be shown.............................................................................................................................................. 25
5. Printing the files............................................................................................................................................................................ 26
5.1. Print with automatic screen image............................................................................................................................................. 26
5.1.1. Printer........................................................................................................................................................................................... 26
5.1.1.1. Lines per page............................................................................................................................................................................ 26
5.1.2. Printing type................................................................................................................................................................................ 26
5.1.2.1. 1 record per page....................................................................................................................................................................... 26
5.1.2.2. As many as possible on each page........................................................................................................................................ 26
5.1.2.3. List (1 record per line)............................................................................................................................................................... 27
5.1.3. Fields............................................................................................................................................................................................ 27
5.1.4. Index (printing‑order)................................................................................................................................................................. 27
5.1.5. Start from and Stop at................................................................................................................................................................ 27
5.1.6. Examples of prints....................................................................................................................................................................... 27
5.2. Print with user‑defined screen
image........................................................................................................................................ 28
5.3. Print using the reportgenerator................................................................................................................................................. 28
5.4. Updating files using the
reportgenerator................................................................................................................................. 29
6. Definition of checks on code‑fields........................................................................................................................................... 30
6.1. Principle......................................................................................................................................................................................... 30
6.2. Using function 7 ‑ define check................................................................................................................................................. 30
6.2.1. Choosing file to check............................................................................................................................................................... 31
6.2.2. Selecting field to check.............................................................................................................................................................. 31
6.2.3. Text length................................................................................................................................................................................... 32
6.2.4. Minimum and maximum allowed value.................................................................................................................................... 32
6.2.5. Text............................................................................................................................................................................................... 32
6.3. Inquiry on the check‑codes....................................................................................................................................................... 33
6.4. Amending the check‑codes....................................................................................................................................................... 33
6.5. Deleting check‑codes.................................................................................................................................................................. 33
6.6. Amending the text length........................................................................................................................................................... 33
6.7. Printing the check‑codes............................................................................................................................................................ 33
6.8. Help‑function by file
maintenance............................................................................................................................................ 33
6.9. Amending the file‑definitions.................................................................................................................................................... 34
6.10. Conflicts when creating legal ranges....................................................................................................................................... 34
6.11. Internal storage of the check‑codes........................................................................................................................................ 34
7. Integration to other files.............................................................................................................................................................. 35
7.1. The principle of integration to other
files................................................................................................................................ 35
7.2. Definition of reference to a file.................................................................................................................................................. 35
7.2.1. Minimum/maximum range.......................................................................................................................................................... 35
7.2.2. Structure of the textfield............................................................................................................................................................ 35
7.2.2.1. File‑shortname............................................................................................................................................................................ 35
7.2.2.2. Index‑number.............................................................................................................................................................................. 35
7.2.2.3. Transferring fields..................................................................................................................................................................... 36
7.2.2.4. Key definitions........................................................................................................................................................................... 36
7.2.3. Various values without references in the
file......................................................................................................................... 36
7.2.4. Limitations................................................................................................................................................................................... 36
8. Definition of individual screen
images...................................................................................................................................... 37
8.1. Maintaining the screen images.................................................................................................................................................. 37
8.2. Using functions 12 and 13.......................................................................................................................................................... 38
8.3. Selecting fields and fieldnumber‑sequence............................................................................................................................. 38
8.4. Commands in functions 12 and 13............................................................................................................................................ 39
8.4.1. Lineno........................................................................................................................................................................................... 39
8.4.2. position....................................................................................................................................................................................... 39
8.4.3. CR.................................................................................................................................................................................................. 39
8.4.4. End or CR‑.................................................................................................................................................................................... 39
8.4.5. PRINT‑printout on printer......................................................................................................................................................... 39
8.4.6. F ‑ Top of form............................................................................................................................................................................ 39
8.4.7. ? or the help‑key......................................................................................................................................................................... 39
8.4.8. IL or LI insert one line................................................................................................................................................................ 40
8.4.9. DL or LD delete a line................................................................................................................................................................. 40
8.4.10. MODE show the field formats/numbers or
names................................................................................................................ 40
8.5. Copying a screen‑image............................................................................................................................................................. 41
8.6. Deletion of a screen image......................................................................................................................................................... 41
9. Redefining files............................................................................................................................................................................. 42
9.1. Redefining an empty file............................................................................................................................................................. 42
9.2. Redefining an existing file.......................................................................................................................................................... 42
9.2.1. Expansion/reduction of the fields............................................................................................................................................ 43
9.2.2. Redefining/adding to the index................................................................................................................................................ 43
9.2.3. Expansion/reduction of the number of
records...................................................................................................................... 43
9.2.4. Moving a file to another disk.................................................................................................................................................... 43
9.3. Amending a file without redefining it....................................................................................................................................... 44
9.4. Consequences of the redefinition............................................................................................................................................. 44
9.4.1. Check on code‑fields.................................................................................................................................................................. 44
9.4.2. Reportgenerator‑programs........................................................................................................................................................ 44
10. Printing and deleting the
definitions........................................................................................................................................ 45
10.1. Printing the file‑definitions........................................................................................................................................................ 45
10.1.1. Remarks on the printout........................................................................................................................................................... 45
10.2. Deleting a file and its definition................................................................................................................................................ 46
Figures.......................................................................................................................................................................................................... 47
Keyword index............................................................................................................................................................................................ 48
1.
Introduction.
DMS.DATAMASTER
is a piece of advanced software which allows the user ‑ without any
previous experience in programming ‑ to define files, maintain them and
expand their contents and size.
This of cause is
done with the greatest consideration of the security for the sake of files used
by other applications.
When the user
has defined a file this is automaticly defined in a way that our reportgenerator
may be used for production of prints and requests as well as ‑ and this
is only in datamaster files ‑ for production of printingprograms that at
the same time updates/computes the fields according to the user's definition
(e.g. MONTH‑END PROGRAMS or like).
2.1. Systemflow
The illustration
mentioned below shows how data are being entered into the machine, the handling
and the output:
Figure 1
Systemübersicht.
┌───────────────┐ ┌────────────────────────┐
│Filename and ├──®┐ ┌──®┤ File definitions (DRN) │
│no.of records │ │ │ └────────────────────────┘
└───────────────┘ │ │
│ │
┌───────────────┐ │ ┌───────────┐ │ ┌────────────────────────┐
│Fieldnames │ │ │ New file │ ├──®┤ Screen images │
│Fielddefinition├──®┤ │ │ │ └────────────────────────┘
└───────────────┘ │ └────┬──────┘ │
│ │ ┌────────────────────────┐
┌───────────────┐ │ │ ├──®┤ File maintenance/inq. │
│Index-keys ├──®┤ │ │ └────────────────────────┘
└───────────────┘ │ ¯ │
│ ╔════╧═══════╗ │ ┌────────────────────────┐
┌───────────────┐ ├────®╢ DATAMASTER ╟────®┼──®┤ File documentation │
│Screen images ├──®┤ ╚════╤═══════╝ │ └────────────────────────┘
│ │ │ ¯ │
└───────────────┘ │ ┌────┴──────┐ │
┌───────────────┐ │ │ Old file │ │
│Filename and │ │ └───────────┘ │
│new no.of ├──®┤ │
│records │ │ │
└───────────────┘ │ │
┌───────────────┐ │ │ ┌────────────────────────┐
│New fieldnames/│ │ └──®┤ Output print (report) │
│definitions ├──®┘ └────────────────────────┘
└───────────────┘
2.3. DATAMASTERs selector function.
When the DATAMASTER is activated the
following menu is shown:
Figure 2 DATAMASTERS
selector
D.M.S. *
D A T A M A S T E R * VERSION 01/01‑1987
CODE FUNCTION
1.....DEFINE NEW FILE
2.....REDEFINE EMPTY FILE
3.....REDEFINE FILE
CONTAINING DATA
4.....REDEFINE FILE
WITHOUT CHANGE OF FIELD‑TYPES
5.....PRINT OF FILE
DEFINITIONS
6.....DELETION OF A FILES
DEFINITIONS AND ALL DATA IN THE FILE
7.....DELETION CHECK OF
CODE‑FIELDS
9.....FILE MAINTENANCE
WITH USER‑DEFINED SCREEN LAYOUT
10....FILE MAINTENANCE
WITH AUTOMATIC SCREEN LAYOUT
12....DEFINE NEW SCREEN
LAYOUT
13....AMEND SCREEN
LAYOUT
14....COPY SCREEN
LAYOUT
15....DELETE SCREEN
LAYOUT
17....PRINT OF FILE DATA
USING USER‑DEFINED SCREEN LAYOUT
18....PRINT OF FILE DATA
USING AUTOMATIC SCREEN LAYOUT
19....SUPERINDEX (SEARCH
ALPHANUMERIC IN FILE)
20....reportgenerator
ENTER CODE:
DATAMASTER
can be devided into 4 logic sections:
1.
Definition of files (functions 1‑7)
2.
Maintenance of data in the files (functions 9‑10)
3.
Definition of individual screen images (functions 12‑15)
4.
Printing and searching in files (functions 17‑20)
2.5. Principles and structure.
When you define a file it is done in an extreemly
simple way, as you only have to enter the field name and the number of
characters/digits of each field. One or several fields may also be marked as
keyfields in the file.
DATAMASTER stores this information on the
disk in a so‑called DATA‑DICTIONARY, i.e. an index of the files.
After this the definitions are automaticly computed and a files is build. A
filemaintenanceprogram is formed and the file is installed in the
reportgenerator.
The file is now ready for use and you may
enter data into it, search in all fields marked as keyfields and print data
using all the facilities of the reportgenerator for
selection/sorting/totalisation and grouping. Furthermore you ‑ by the use
of DATAMASTERs own printingfunctions ‑ may print creation checklists and other
lists from the file.
It is not necessary to have the
reportgenerator installed on the system to be able to use DATAMASTER, but the
purpose of building files may eventually mostly be output in the form of
letters or lists, criss‑crossing the system, which is what the
reportgenerator enables the user to do.
By the use of the search functions in
DATAMASTER (named SUPERINDEX) you may also preform "wide" searching
for names in the files, e.g. search for everybody called PETER, and all
occurences of this name ‑ JOHN‑PETER
as well as PETERSON ‑ will be located, no matter how the search‑criterion
is placed in the name‑fields.
2.6.1. Extension of the definitions.
All the above mentioned functions were
obtained by simply entering the fieldnames and the number of characters/digits
in the fields (format).
Based on this information DATAMASTER is able
to create a screen image for entering data in the files, but of cause it is
also possible for you to define your own screens with exactly the fields you
want and in the order you want them.
You may define field‑checks so a
certain field has a set of allowed values, and each value may even be attached
to a explaining text. In this case the text will show on the screen with the
fields.
It is also possible to define that a field
is key to another file and that one or more fields from this file, e.g. names
and adresses, should be transferred to this file and shown on the screen or
copied to certain fields in this file.
2.6.3. Redefining files.
When you perhaps discovers that you have
forgotten one or more fields in the file when you created it, or if the fields
turn out to be too small, or when you want new index‑keys, or when you
want to remove already existing keys, all you have to do is to choose
DATAMASTERs function for redefining files.
In this function you may amend/extend the
file‑definition in any way you please and DATAMASTER will take care of
reconstructing the file as the new file‑layout
is being compared to the existing. DATAMASTER automatic builds a new file and a
special copying/converting‑program for changing the old file.
When this is done you can go on working with
the new file as if nothing had ever happened.
A particularly simple redefintion is an
extension of the number of records in the file or for instance moving the file
to another disk.
2.6.5. Integration to other systems.
DATAMASTER can pick up information from
existing files, e.g. from customer‑files, but these must be defined by
installation of the system in the same way as a file is defined for the
reportgenerator.
In the reportgenerator you may mix the
existing files and DATAMASTER‑files just as you need.
Existing programs may look up information in
DATAMASTER‑files, but normally it takes assistance from a skilled
programmer to make amendments like this. DATAMASTER‑files are completely
normal files build in the same way a programmer usually would build them and
they may be used in other programs straight away.
2.7. Calculation of the capacity.
DATAMASTER at present takes minimum 20KB
partition and 18 datafiles open in SYSMOD, operating system NIROS from 3.3.4 to
7.0.1, screen RAP or DAP.
Generally it is not possible to calculate
the diskspace needed for DATAMASTER, as this depends on the size of the files
the customer wants to define. However, the below mentioned diagram may be used
as a help during the calculation of the capacity; the system may be divided
onto several discs if necessary.
Figure 3 Creation of a
new file.
───┬────────────────────────────────────────────┬─────────┬──────────┬────┐
No.│ │Sectors │
Total sec│
LU │
───┼────────────────────────────────────────────┼─────────┼──────────┼────┤
1 │Datamaster
programs. │ 600 │ 600
│ │
2 │Reportgenerator programs. │ 600 │ │ │
3 │Workfiles for
datamaster and reportgene‑ │ │ │ │
│tor, normal
installation. │ 250 │ 250
│ │
4 │Datamaster file
definitions: │ │ │ │
│10 files │ 150 │ │ │
│20 file │ 300 │ │ │
│30 files │ 450 │ │ │
5 │Datamaster screen
programs: │ │ │ │
│22 programs │ 100 │ │ │
│44 programs │ 200 │ │ │
│66 programs │ 300 │ │ │
│88 programs │ 400 │ │ │
6 │Datamaster field
check‑code validations: │ │ │ │
│100 field check‑code combinations │ 40 │ │ │
│500 field check‑code combinations │ 200 │ │ │
│1000 field check‑code
combinations │ 400 │ │ │
7 │Reportgeneratorprograms: │ │ │ │
│22 reports (saved) │ 600 │ │ │
│44 reports (saved) │ 1200 │
│ │
│66 reports (saved) │ 1800 │ │ │
│88 reports (saved) │ 2400 │ │ │
│(not saved: as point
5). │ │ │ │
8 │Reportgenerator
sortwork: │ │ │ │
│1000 records │ 100 │ │ │
│5000 records │ 500 │ │ │
│10.000 records │ 1000 │ │ │
9 │Datamaster files
according to user │ │ │ │
│definitions: │ ? │ │ │
───┼────────────────────────────────────────────┼─────────┼──────────┼────┤
│total │ │ │ │
───┴────────────────────────────────────────────┴─────────┴──────────┴────┘
───┬────────────────────────────────────────────┬─────────┬──────────┬────┐
A.│ Eg: 10 files, 22
programs, │ │ │ │
│ 22 reports, 100 checks, 100 sortwork: │ 2500+? │ │ │
│ │ │ │ │
B.│ Eg: 20 files, 44
programs, │ │ │ │
│ 44 reports, 500 checks, 5000 sortwork: │ 4000+? │ │ │
│ │ │ │ │
C.│ Eg: 10 files, 22
programs, │ │ │ │
│ 100 checks, no reportgenerator: │ 1200+? │ │ │
│ │ │ │ │
D.│ Eg: as A., report
programs not saved: │ 2000+? │ │ │
───┴────────────────────────────────────────────┴─────────┴──────────┴────┘
3. Defining a file.
When you want to define a new file you
select function 1 and the following screen appears:
Figure 4 Creation of a
new file.
D.M.S. *
D A T A M A S T E R * 1.....DEFINE NEW FILE
GR 9/DA.GRKA# DEM‑ART.GROUP FILE
KU 9/DA.KUKA# DEM‑CURRENCY FILE
LE 9/DA.LEKA# DEM‑SUPPLIER FILE
FILE SHORTNAME ? VA
4.1. File shortname.
Each file is identified by a 2‑letter
shortname and there cannot be 2 files with the same shortname. CAPITAL letters
must be used. [1] When you define a new file an overview of all
the DATAMASTER files that have been defined on the system will appear on the
screen. Other non‑datamaster files (defined by a programmer) may easily
exist but they will not be shown on the screen nor be accessible for the user,
due to security reasons.
Now you enter a new file shortname and it
is checked that this shortname does not
already exist as a DATAMASTER file or a programmer defined file and you will continue with:
Figure 5 Disc number
(lu) and no. of records.
D.M.S. *
D A T A M A S T E R * 1.....DEFINE NEW FILE
FILE SHORTNAME ? VA
DISKNO. (LU) (0/1/2/9) ? 9
TEXT:ARTICLE FILE
NO.OF RECORDS ? 100
4.3. Disc number (lu)
Here you desides which disc the file should
be placed on, you may select the disc that has the largest amount of free
space.
DATAMASTER will always propose a certain
disc chosen by the programmer during
installation and you may just accept by pressing cr if you agree to the
choice.
If the programmer has only activated one
disc at the installation the question
will not be asked. You will only be able to use the discs the programmer has
permitted.[2][3]
4.5. File name (description).
Now you enter a text containing up till 25
characters. This will be the file name. You cannot leave this text blank.
4.7. Number of records in the file.
Hereafter you indicate how many records you
want the file to be created with.
It will only be possible to create the
number of records in the file which you
indicate here. If you try to create more records than this, you will see the
message: "FILE IS FULL".
By the use of function 3 ‑ redefining
an existing file ‑ you are always able to amend (contract/expand) the
number of records and even to move the file to another disk if there is not
enough space on the chosen disk.
At this moment DATAMASTER does not check if
there is actually space for the file, as this is dependent on the number of
fields and the indexes that we have to define now. The checking is not done
until all the information has been entered and saved.
If it turns out that there is not enough
space for the defined file all the procedures with the exception of the
creation of the file itself will be accomplished. In this case you must ‑
by the use of function 2: redefining an empty file ‑ either reduce the
number of records or move the file to another disk.[4]
4.9. Definition of the individual fields.
When you have entered the basic information
of the file, i.e. shortname, disc, name and number of records you continue with
the detail‑specifications of the individual fields in the file.
A file must contain at least 1 field and
maximum 99 fields.
When the fielddefinition is started a
helpscreen is shown that shortly explains the different functions at your
disposal:
Figure 6 First page
with help information.
DATAMASTER VERSION 01/01‑1987 SYSTEM 61,9
DMS.RAPGEN ENGLISH
1
ARTICLE FILE
FIELDS: 1 BYTES: 0
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
The fields can be defined by giving
a name and a field format.
The field format defines if the
field is alphanumeric or numeric
and how many digits/decimals should
be reserved for the field.
Format Definition
32 32 characters alphanumeric field
2, 2 digit code without decimal places
8,2 numeric field with 8 digits and 2 decimal
places (no sign)
‑8,2 as above, but a sign is allowed
(amounts)
,8,2 as above, comma editing at each 3rd digit
(ie.12,345,678.90)
,6, (,8,) data‑field ie: .6. gives
31.03.86 .8. gives 1986.03.31
in addition it is possible to
specify with the field format, that
the field should be a key‑field,
ie. an index should be set up on this field.
The letter K after the field format
defines a key field (eg. 4.K).
K gives a keyfield, D defines a
keyfield which might not be unique.
'L' can be used to list the fields
on the screen from the current field no.
1
NO.NAME FORMAT CHECK
PSEUDO TYPE VARIABEL BYTE REF. W
Your cursor is placed at the bottom of the
screen‑image, in the column fieldnumber, and right above the cursor the
number 1 is written at the beginning of a blank line.
Each field corresponds to one line on this
screen image and is identified by a fieldnumber written at the start of the
line. The fields are described in
ascending order and once you have created a file with data in the field it is no longer possible to change the
number of a field and still preserve these data, as the number at the start of
the line is telling the system where the field is stored etc.
Later on you may create reports, screen
images ect. by referring to this fieldnumber.
Figure 7 Definition of
the fields.
DATAMASTER VERSION 01/01‑1987 SYSTEM 61,9
DMS.RAPGEN ENGLISH
1
ARTICLE FILE
FIELDS: 10 BYTES: 57
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
1 ARTICLE NO. 4 AAAA
2 DESCRIPTION 20 AAAAAAAAAAAAAAAAAAAA
3 SELLING PRICE 6,2 ######.##
4 COST PRICE 6,2 ######.##
5 DATE OF LAST PURCHASE , 6,
##,##,##
6 SUPPLIER NO. 3 AAA
7 ARTICLE GROUP NO. 2,
##
8 STOCK BALANCE ‑ 6,
‑‑‑‑‑‑#
9 ALTERNATIVE SUPPLIER NO. 3,
###
10 FREE ‑ 6,2 ‑‑‑‑‑‑#.##
11
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
Now you enter the individual fields with
the following information:
4.10.1. Fieldnumber.
To define a new field (or amend an existing)
you just press cr at the fieldnumber, at which you jump to the next column, i.e. the fieldname
of the field shown just above.
First time you define a new file and press
cr you accordingly proceed to the blank line of field number 1. You see the
number of the field you are defining right now at the start of the present
line.
The line above will always show the
previous definition of the field, the
current line will show the definition you enter.
4.10.3. Fieldname.
You enter a text of 1 to 24 characters that
concisely describes the field.
As this text later on may be used as
headline of the field in reports, you shouldn't make the name any longer than
absolutely necessary. A headline containing 24 characters for a code of one
digit does take up a lot of space on the paper.
Naturally you may amend this headline when
defining the report, but it is of cause a lot easier if you can use the
fieldname without any further amendments.
4.10.5. Fieldformat.
Here you in a very simple way define the
layout of your field, i.e. the number of characters or digits (decimals) you
want this particular field to contain.
If you for instance enter 20 you will get a
textfield that contains 20 characters.
If you enter a point after the figure you
get a numerical field that may be used for calculations, e.g. 6, defines a
numeric field containing a maximum of 6 digits.
If you want decimals you must indicate this
after the point, e.g. 6,2 gives you 2
decimals after the point and 6 digits in front of the print.
Based on this fieldformat the system will
calculate how much space should be reserved for this field in the file and thus
how the field should be stored in the smallest possible BASIC‑variable.
If the fieldformat is amended later on
DATAMASTER will automatically perform the calculation again for this and any
following fields and thus you don't have to worry about this at all.
The following formats may be used:
1.
xx, indicates a figure
of xx digits without sign
2.
xx,y indicates a figure
with xx digits before the point y decimals, no sign
3. ‑xx like 1, with sign
4. ‑xx,y like 2, with sign
5.
,xx, like 1, with comma‑editing
for each 1000, e.g. 999,999,999
,6,
date‑field with comma‑editing: 99,99,99 and validation
,8,
date‑field with comma‑editing:
YYYY,MM,DD and validation
6.
,xx,y like 2, with comma‑editing
for each 1000, e.g. 999,999,999.99
7.
xx Omission of a point
defines a textfield of xx characters are created (maximum 80 characters)
4.11. Next field.
When you have defined a field the format
will be shown on the outermost right as a number of X's meaning alphanumerical
textfields and a number of 9's meaning numerical digit‑fields.
Hereafter the fieldnumber is added one and
the screen image is moved up one line. Once again you are now placed in the
fieldnumber column and you may define the next field in exactly the same way
you did the first.
4.13. Selecting a certain field.
If you in the fieldnumber column don't press
cr. but instead the number of a certain field this field will be shown on the
line just above.
4.15. Amending a field definition.
When you have selected a field you may press
cr. in the fieldnumber coloumn and get into the line and enter fieldname and ‑format
once again.
If you only press cr in the fieldnumber
column the previous value will be kept, i.e. you will get either the same
fieldname or the same fieldformat.
Single characters of a fieldname may be kept
by the use of the ""‑key. If the cursor for instance is
positioned below:
BALANCE NEXT YEAR you may enter:
THIS and the new name of
the field will be:
BALANCE THIS YEAR
4.17. Listing the fields on the screen.
If you enter "L" in the
fieldnumber column you will see as many fields as possible listed on the
screen, starting with the fieldnumber in which you are positioned at the time
you enter "L".
This means that if you want a list of the
fields starting at the very first you enter "1" and in this way field
number one is shown. Then you enter "L" and the following fields are
shown. If you have defined more than 17 fields you just enter "L"
once again and see a list of the next 17 fields listed on the screen.
4.19. Deleting and inserting of fields.
As long as you are working with an EMPTY
file, i.e. the first time you define a file you may delete and insert fields
totally freely.
When you have entered data into the file you
should avoid using these functions as the data is identified by the field
numbers and thus data will not be moved when you delete/insert fields!!!
4.20.1.
2.10.1. Deleting fields.
By entering "D" in the fieldnumber
column you will be asked how many fields you want to delete, starting from the
current field.
If you enter "47" for field
number, field 47 will appear on the screen. If you then enter "D" and
answer 2 fields, field numbers 47 and 48 will be deleted.
4.20.3.
2.10.2. Inserting fields.
By entering "I" in the field
number column you may insert a number of fields BEFORE the current field.
If you enter "47" for field
number, field 47 will appear on the screen. If you then enter "I" you
will be asked how many fields you want to insert BEFORE field number 47.
Answering 2 fields, field numbers 47 and onward will now be moved 2 numbers
down and field numbers 47 and 48 will be empty.
NB: If the file after the insert exeeds 99
fields the fields in the end will dissapear without any further warning! This
means that you have to make sure not to exceed the limit of 99 fields.
4.21.
page
\* arabic122.11. Definition of the key‑fields
(index).
Any file in DATAMASTER is built as a
'indexed' file, which means that one or more of the fields in the file is used
as access‑key to one particular record, e.g. name, adress or phonenumber.
If you don't indicate otherwise, the first
field in the file will be created as a key‑field which normally will be
suitable, e.g. a customer‑file should always contain the customer‑number
in the first field.
4.22.1. Unique and 'duplicate' keys.
A unique key is a key in which only one
value of the field can appear. A key defined as 'duplicate' allows the
appearance of several fields with the same value.
For instance a customer‑number will
always be unique, as only one customer can have this number. Opposite a key
defined as customer‑name normally will be 'duplicate' as several
customers with the same name may easily appear.
At least one unique key is required in any
file or you will not be able to find a particular record when entering a
key.
4.22.3. Definition of a key‑field.
A field may be defined as a key‑field
by entering a letter at the same time as you indicate the fieldformat, for
instance the letters "K" and "D" indicate two different
kinds of keys, namely:
Figure 8 Key‑definition.
DATAMASTER VERSION 01/01‑1987 SYSTEM 61,9
DMS.RAPGEN ENGLISH
1
ARTICLE FILE
FIELDS: 10 BYTES: 57
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
1 ARTICLE NO. 4 AAAA
2 DESCRIPTION 20 D AAAAAAAAAAAAAAAAAAAA
3 SELLING PRICE 6,2 ######.##
4 COST PRICE 6,2 ######.##
5 DATE OF LAST PURCHASE , 6,
##,##,##
6 SUPPLIER NO. 3 D AAA
7 ARTICLE GROUP NO. 2, D ##
8 STOCK BALANCE. ‑ 6, ‑‑‑‑‑‑#
9 ALTERNATIVE SUPPLIER NO. 3, D ###
10 FREE ‑ 6,2 ‑‑‑‑‑‑#.##
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
K
defines a unique key (e.g. customer‑number)
D
defines a 'duplicate' key (e.g. name)
4.22.5. Amending a key‑field.
You are always able to define a field as a
key‑field at a later point. All you have to do is to enter the requested
letter in the fieldformat.
You have to notice, however, that if you
have already created records in the file, it may be dangerous to define a field
as a 'unique' key, as identical values of this field in the file may appear,
which means that all the records cannot be copied to the new file. Unique keys
should be defined only at the very first definition of the file.
4.22.7. Deleting key‑fields.
Deleting a key‑definition from a field
is done by entering a blank (space) in the fieldformat.
4.22.9. Other types of keys.
Apart from "K" and "D"
you may use the letters "E", "Z", "V",
"I" and "X" in the fieldformat to define keys with the
following functions:
K = Key, unique key.
Several records with
the same value of this field are not permitted.
D = Duplicates allowed.
More than one record
with the same field‑content, e.g. name.
E = Unique key without
zero‑keys.
Like K, but if the
field is zero or blank the key is left out from the index.
Z = Duplicates allowed
without zero‑keys.
Like D, but if the
field is zero or blank the key is left out from the index.
V = Field with turned
date, duplicates allowed.
A date‑field
with the form DDMMYY must be turned before it may be used as a key.
I = Inverted field,
duplicates allowed.
Inverted means that
instead of the index being sorted in ascending order the records will appear
in descending order.
This function can be used only for numeric fields.
X = Inverted field with
turned date, duplicates allowed.
Blank
= Any index‑mark is deleted.
4.23. Terminating the fielddefinition.
When all the fields have been defined you
enter END instead of a fieldnumber and the following screen will appear:
4.24.1.
2.12.1. Definition of special keys.
Figure 9 Definition of
special‑keys.
DATAMASTER VERSION 01/01‑1987 SYSTEM 61,9
DMS.RAPGEN ENGLISH
1
DEM‑ARTICLE FILE
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
INDEXNO. KEY‑DEFINITION NAME
1
1,S ARTICLE NO.
2 2,NP,S NAME
3 6,NP,S SUPPLIER NO.
4 7,NP,S ARTICLE GROUP NO.
5 9,NP,S ALTERNATIVE SUPPLIER
NO.
6
You can normally just press CR.
here.
All the indexes will be defined by
giving K/D etc. in the field formats.
These definitions can be used in
special (advanced) cases, where you need to
combine several fields into one
index key; take single characters from fields.
Very complex keys can therefore be
defined, eg: 1,2(5,12),3P
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
At
this point you may define additional keys, e.g. compounded and/or packed keys.
USUALLY YOU SHOULD JUST PRESS CR. AT THIS
POINT.
and
you will continue with the next screen.
The definition of special keys is only
necessary in few files but in order to enable the advanced user to get the full
benefit of DATAMASTER we have chosen to support this function.
If you want to define only special keys for
a file, all previous defined keys may be cancelled by entering "‑"
(minus) in the text‑field. In this way you must do the index‑definitions
your self.
4.24.3.
2.12.2. Creating the file.
After termination of the definition of the
special keys the following screen appears:
Figure 10 Generation of read/write for the reportgenerator.
D.M.S. *
D A T A M A S T E R * VERSION 01/01‑1987
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
GENERATING READ/WRITE‑STATEMENTS
‑ PLEASE WAIT....
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABEL BYTE REF. W
During this procedure you just have to wait.
DATAMASTER is now automaticly building a file that corresponds the field‑
and index‑definitions you have entered and with the number of records
that were indicated from the start.
Furthermore the reportgenerator will be
installed with access to this file as read‑ (and write‑) statements
for this will be generated.
When DATAMASTER has finished this procedure
it returns to the main menu. Depending on how large file that has been defined
this will take somewhere between a couple of seconds and several hours, the
latter if you for instance are creating a file with 100.000 records.
4.25.
page
\* arabic212.13. Syntax at the definition of special
keys.
Fieldnumbers are indicated without # in
front and the text constant must be entered in quotation marks (").
By the use of the letters you may specify
the special functions such as Packing, Date turnaround and Zero. Parts of
fields may be indicated in the normal way, e.g. 10(5,6) means characters 5 to 6
in field number 10.
A key always contain an even number of
characters, if you have defined 5‑digit customernumber it will always be
stored in the system with 6 characters in the key. This extra character may be
a zero‑character, i.e. a zero or a blank.
With the Space function you may fill out the
key with blanks. In the following the full syntax for this keydefinition will
be described, followed by a few examples.
4.26.1. Fields.
The fields are entered as fieldnumber
without the # at the start:
10 = Fieldnumber 10
10(5,6) = Characters 5‑6
out of fieldnumber 10
R = Recordnumber
(exact)
N = Recordnumber
(relative to the first datarecord)
"XX" = Text‑constant
4.26.3. Functions.
Functions are indicated with a letter right
after the field:
D = Date turnaround
(DDMMYY ==> YYMMDD as FND)
P = Packing
Z = Zero, surpression
of zeros
S = Space, padding
with a sequence of blanks.
4.26.5. Grouping fields and functions.
Various fields may be combined by separating
these with commas. The P‑function may be used at each individual field or
alone without the fieldnumber, in which case the entire key defined up till now
will be packed. The S‑function may only be used at the end and
alone.
4.26.7. Examples of key‑constructions.
1.
1 Field 1
2.
1,2 Field 1 followed by
field 2
3.
1,2,P Like above, but the
entire key packed
4.
1P,2 Field 1 packed
followed by field 2, unpacked.
5.
1(3,4),2 Character 3 to 4 out
of field 1 followed by field 2.
6.
"01",1 The constant 01
followed by field 1
7.
1,S Field followed by
possible blanks
8.
2,NP,S Field 2, relative
record‑number packed, blanks.
The two latter key‑constructions are
usually used by DATAMASTER, the first one when creating the definition of a
unique key, the second one when creating a 'duplicate' key.
5. Entering data into the file.
Entering data into the file may be done by
the use of two different functions:
9
File‑maintenance with user‑defined screen image.
10
File‑maintenance with automaticly defined screen image.
The programs 9 and 10 work alike, but when
using function 10 DATAMASTER will create a screen image based on the fieldnames
given in the filedefinition and place all the fields of the file in succession
on the screen image to make it look as nice as possible.
Function 10 may be used immediately after
having defined a file, whereas function 9 requires definition of a screen image
first by use of function 12; define new screen image.
Choosing function 10 you have to enter a
file‑shortname, choosing function 9 you enter a program‑ or screen
image‑number and from this DATAMASTER will know the file in question.
Defining your own screen image also gives
you the possibility of placing the relevant fields only in the screen image and
by entirely leaving out fields, you may prevent the user from entering data
into these.
Furthermore, when creating your own screen
image you may set up a fixed sequence of entering the fields and also decide in
which fields you are allowed to enter/amend/display data.
Finally function 10 is limited in the sence
that only the first 44 fields of the file can be shown on the screen.
Consequently, having more than 44 fields, you always have to create your own
screen image in order to get access to
all fields.
There is of cause the possibility of
defining several screen images connected to the same file but you will not be
able to use more than one screen image at the time.
6.1. Examples of screen images.
Figure 11 Creation of the file using automatic screen image.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE.
01 ARTICLE NO. 02 DESCRIPTION
03 SELLING PRICE
04 COST
PRICE
05 DATE OF
LAST PURCHASE
06 SUPPLIER
NO.
07 ARTICLE
GROUP NO.
08 STOCK
BALANCE
09 ALTERNATIVE SUPPLIER NO.
10 FREE
FUNCTION:
1=CREATE 2=READ
3=AMEND 4=DELETE 5=SEQUENCE
Figure 12 File maintenance with user defined screen image.
D.M.S. *
D A T A M A S T E R * 9.....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 02 DESCRIPTION: 07 ARTICLE GROUP NO.
PRICES: 03 SELLING: 04 COST:
SUPPLIER NO: 06 NORMAL:
FUNKTION:
1=CREATE 2=READ
3=AMEND 4=DELETE 5=SEQUENCE
6.3. The basic functions in the file
maintenance‑program.
Having selected a file‑maintenance‑program
the screen image is appearing and you are asked to enter:
FUNCTION:
1=CREATE, 2=READ, 3=AMEND, 4=DELETE,
5=SEQUENCE.
This
means that, by the use of this status‑ and function‑code, you are
able to deside the function of the program.
In an user‑defined screen image this
status might be locked, so that you are only able to make requests or
amendments in this program.
6.4.1. Special functions in the status‑field.
The following functions may be used in
STATUS:
6.4.3. Key 1 (cr‑) Termination of the
program (END).
If you press cr‑ you will return to
the menu.
6.4.5. Lamp‑4 (R4) Lock status.
When lamp‑4 (R4) is switched on you
will avoid repeatingly being asked for the status, the previous status will be
used.
6.5. Function 1 ‑ Creating a new
record.
When you select function 1 you will be asked
to enter the main‑keyfield. This will normally be fieldnumber 1.
The system checks that this number does not
already exist in the file. If it doesn't you will on the bottom line see the
number of free records left in the file and you may go on entering the rest of
the fields.
If the number already exists the creation
will be refused and you return to the status‑field.
The sequence in which the data is entered
will normally be ascending according to the fieldnumbers, but may also be in
any sequence decided by you, by the use of function 5; SEQUENCE. Furthermore,
the user‑defined screen images has a possibility of defining a specific
sequence to the screen image.
After having entered the data into the
different fields the cursor will be placed at the bottom of the screen with the
text FIELDNO:
Figure 13 Entering the fields.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 1001
02 DESCRIPTION TRUCK‑WHEEL
03 SELLING
PRICE 1000,00
04 COST PRICE 500,00
05 DATE OF
LAST PURCHASE 31.12.86
06 SUPPLIER
NO. 205
07 ARTICLE
GROUP NO. 0
08 STOCK
BALANCE 100
09
ALTERNATIVE SUPPLIER NO. 102
10 FREE 0,00
FUNCTION:1=CREATE FIELDNO.? 8 DATA:
9 FREE RECORDS.
Now you may enter the number of one of the
fields shown on the screen and the text DATA: appears. Here you may enter the
new of the field in question. After this you return to the fieldnumber and are
ready to amend the next field.
When you finally press cr without entering a
fieldnumber you return to STATUS and are ready to choose a new function.
If you, by the use of FIELDNUMBER,
amendments the mainkey of the file, or if more than one unique key are defined
in this file, it is possible that a message telling you that this record
already exists will appear when you press cr. If this happens you will return
to the FIELDNUMBER.
In this case you have to amend the unique
key(s) or cancel the amendment completely by pressing the key cr.‑ and
answer no when asked if the writing of this record should be performed.
6.6.1. Special functions during dataentering.
It is possible to use a number of keys to
perform special functions during the dataentering, please refer to the keyboard
layout at the end of this chapter.
The keys are called key‑x and the x
refers to this layout as it unfortunately is different texts written on the
keys depending on what kind of screen you have at your availability.
6.6.3. Key 3 ‑ Backspace after entering
wrong data ().;
Key 3 may be used to backspace one
field.
6.6.5. Key 2 ‑ Hold field value (@).
Key 2 may be used to move one field forward
without erasing the contains of this field.
Furthermore the key 2 may be used if you
accidently enter a wrong fieldnumber and are placed in the DATA field at the
bottom. In this case the present value of the field is kept.
6.6.7. Key 1 (cr‑) Termination of the
dataentering.
Key 1 (cr‑) may be used to interrupt
the dataentering in an arbitrary field and this way you go directly to the
FIELDNO. without having to enter any of the other fields.
When using key 1 in FIELDNO. you will be
asked if this record is to be written and if you answer No this creation will
be cancelled.
6.6.9. Key 13 ‑ The help‑key.
If you press key 13 in an arbitrary field
you will, on the bottom line of the screen, be informed which file and which
fieldnumber you are in, just as thus fieldformats will be shown.
Figure 14 Activating the help‑function.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 1001
02 DESCRIPTION TRUCK‑WHEEL
03 SELLING PRICE 1000,00
04 COST
PRICE 500,00
05 DATE OF
LAST PURCHASE 31.12.86
06 SUPPLIER
NO. 205
07 ARTICLE
GROUP NO. 0
08 STOCK
BALANCE 100
09 ALTERNATIVE SUPPLIER NO. 102
10 FREE 0,00
FUNCTION:3=AMEND FIELDNO.?
7 DATA:
7:VA# 7:##: 0=UNSPEC., 1=SPECIAL,
2=CASH , 3=CARS , CR:
If this field in addition has some check‑codes
attached (by the use of DATAMASTER's function 7) these will be shown (as many
as possible on each line) and you may press cr. to get the next line or cr‑
to return to the field.
6.6.11. Lamp‑1 (R1) Permanent help.
If you switch on lamp‑1 (R1) the help‑line
at the bottom will all the time follow the field you are currently
entering.
6.7. Function 2‑ Inquiry.
By the use of this function you may inquire
a record in the file.
When you have selected this function you
will be asked to enter the access key
of the file and the record in question will be shown on the screen.
6.8.1. Next record.
If you just press cr. for a key you will
automatically get the next record in the file.
6.8.3. Searching secondaty index‑keys.
In connnection with the STATUS‑code
you may enter the key number by which you
want to find the record.
Figure 15 Searching using secondaty index.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 02 DESCRIPTION MONEY
03 SELLING PRICE
04 COST
PRICE
05 DATE OF
LAST PURCHASE
06 SUPPLIER NO. 205
07 ARTICLE
GROUP NO.
08 STOCK
BALANCE
09 ALTERNATIVE
SUPPLIER NO.
10 FREE
FUNCTION:2,3
You have to enter the status‑code, as
two digits separated by a comma.
The first digit is the status‑code
itself, in the present example 2 for reading.
The second digit is the INDEX‑number
(not the fieldnumber) that you want to search so if you enter 2,3 the search
will be carried out according to index no. 3 in the current file.
If this index‑key is not unique you
just have to enter a part of the field in question and the next record with the
key larger than or equal to will be found and shown on the screen.
This choise of index will be valid until you
choose a new index for searching, i.e. you just enter 2 for status the next
time you want to search in index no. 3, but if you want to find an article on
the basis of the article‑number you have to enter 2,1 for status.
6.9. Function 3 ‑ amending a record.
Function 3 is actually a combination of
function 2; inquiry and the last part of function 1; creation, where you may
amend the record by the use of the fieldnumbers.
This means that you may use the searching‑possibilities
from function 2 and the function‑keys in FIELDNO. from function 1.
You may amend all the fields, among these
the key‑fields including the main‑key for files (normally field
number 1).
If you amend any unique key it is possible
that a message informing you that this record already exists will appear when
you press cr. in the fieldnumber. After this you return to FIELDNO.
In this case you have to amend the unique
key(s) or cancel the amendment completely by entering cr‑ and answer No
when asked if this record is to be written.
6.10.1. Key 4‑8 Increase/decrease the
fieldvalues.
In numeric fields you may use the keys 4‑8
to increase/decrease the chosen field with the entered value instead of putting
the entered value directly into the chosen field. If necessary, this may be done by percentage.
If the value of a field is for instance
100000,00 and for DATA you enter 15 followed by key 7 the new value will be
85000,00 as key 7 means %‑. It is 15 per cent of the field's original
value will be subtracted from the value.
Please also see the keyboard layout at the
end of this chapter.
6.11. Function 4 ‑ Deleting a record.
By the use of this function you may delete a
record from the file.
First the function works as a inquiry, i.e.
you may search for a record from a chosen index, after this you will be asked
to confirm the deletion with Yes or No.
If you answer Yes the record is deleted, if
you answer No no damage is done.
6.13. Function 5 ‑ Defining the
fieldnumber‑sequence.
By the use of this function you may attach a
temporary creation‑sequence to this screen image. The sequence is only
valid until you leave the program.
With an user‑define screen image you
may define a fixed sequence, see this chapter.
Figure 16 Specification of a fieldnumber sequence.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 02 DESCRIPTION
03 SELLING PRICE
04 COST
PRICE
05 DATE OF
LAST PURCHASE
06 SUPPLIER
NO.
07 ARTICLE
GROUP NO.
08 STOCK
BALANCE
09 ALTERNATIVE SUPPLIER NO.
10 FREE
FUNCTION:5=SEQUENCE
FIELDNO.SEQUENCE ? 2,6‑7,3‑4
If you enter a fieldnumbersequence like
shown above creating a new record in the file by the use of function 1, you
hhave to fill in the fields, first the main‑key (always) and then the
fields 2,6,7,3 and 4 in the mentioned order.
The rest of the fields will be skipped but
you may amend them during creation by the use of FIELDNO‑DATA.
The sequence is only of consequence by the
creation, not by any other functions.
6.15. Check‑functions.
Different forms of checks may be attached to
a field:
6.16.1. Index‑key fields.
During the creation you can see if a field
is part of a key as the field will be marked with a number of æsteriks
(*******).
If the key has been defined as a unique key
it will not be possible to create two records with the same value of the field.
This is being checked by the time you confirm the dataentering by pressing cr.
in the field‑number.
6.16.3. Date‑fields.
If you have defined a field as a date‑field
by giving the format as either ,6, or ,8, it will be checked that this field
contains a correct date or a zero.
If you just enter cr. in such a field the
date will be taken from the system date.
If the field is defined as ,6, it will be
turned as YY,MM,DD or DD,MM,YY depending on how the programmer set this up by
the installation [5]
Is the field defined as ,8, it will always
be turned as YYYY,MM,DD.
NB: No matter how the date‑field is
turned, you may enter YYMMDD, DDMMYY, DDMM or just DD in the field.
DATAMASTER will turn the date correctly when
you have entered it and it is possible just to enter 2 or 4 digits if you want
to amend the date‑field.
6.16.5. Check‑code fields.
If you by the use of function 7 have defined
checks on fields it will only be the value‑domains defined here that may
be entered into the field in question.
DATAMASTER will sign for this value by
showing the text attached to the value to the right of the field, e.g. a name
fetched from another file.
Figure 17 Screen image with field‑checks.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 0102
02 DESCRIPTION TRUCK‑WHEEL
03 SELLING
PRICE 20000,00
04 COST PRICE 10000,00
05 DATE OF
LAST PURCHASE 1.01.85
06 SUPPLIER
NO. 100 SORENCO A/S
07 ARTICLE GROUP NO. 1 DIVERSE
08 STOCK
BALANCE 0
09
ALTERNATIVE SUPPLIER NO. 0
10 FREE 0,00
FUNCTION:3=AMEND FIELDNO.?
If you do not remember the check‑code
values in question for this field you may always use the HELP‑key and get
a list of the values at the bottom of the screen, please see the previous
paragraph.
6.17. Keyboard layout for the maintenance‑programs.
Figure 18 Tastaturbelegung DATAMASTER.
┌─────────┬──────────┬─────────┬──────────┬─────────┬───────────┐
│ │ │ │ │ │ │
│ _ L4 │ _ L3 │ _ L2 │ _ L1 │ _ │ _ │
│ │ │ │ │ │ │
├─────────┼──────────┼─────────┼──────────┼─────────┼───────────┤
│ │ │ │ │ │ │
│ _ R4 │ _ R3 │ _ R2 │ _ R1 │ _ S │
_ ON/OFF │
│HOLD FUNC│ │ │ HELP │ │ │
├───────┬─┴─────┬────┴──┬──────┴┬───────┬─┴─────┬───┴───┬───────┤
│ │ │ │ │ @ │ │ │ │
│ BS │ Y │ N │ ‑
│
HOLD │ %+ xx │ │ │
│ │ │ │ │ 2│ 7│ 12│ 17│
├───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ │ │ │ │ │ │ │ │
│ C │ 7 │ 8 │ 9 │ │ %- xx │ │ │
│ │ │ │ │ │ 6│ 11│ 16│
├───────┼───────┼───────┼───────┤ CR- ├───────┼───────┼───────┤
│ │ │ │ │ │ │ │ │
│ │ 4 │ 5 │ 6 │ END │
- xxx │ │ │
│ │ │ │ │ 1│ 5│ 10│ 15│
├───────┼───────┼───────┼───────┼───────┼───────┼───────┼───────┤
│ │ │ │ │ │ │ │ │
│ │ 1 │ 2 │ 3 │ │ + xxx │ │ │
│ │ │ │ │ │ 4│ 9│ 14│
├───────┴───────┴───────┼───────┤ CR ├───────┼───────┼───────┤
│ │ │ │ │ │ │
│ 0 │ , │ │ BACK │
% xx │ HELP │
│ │ │ │ 3│ 8 │ 13│
└───────────────────────┴───────┴───────┴───────┴───────┴───────┘
0:
CR Ordinary CR.
1: CR‑ Credit‑key
If the key is
activated alone without any further entering: END.
2:
HOLD The value of the
field is kept and you continue with the next field.
3:
BACKSPACE The value of the
field is kept and you continue with the previous field.
4:
+ The entered value is
added to the value of field.
5: ‑ The entered value is
subtracted from the value of the field.
6:
%+ The entered percentage
of the field is added to the field.
7: %‑ The entered
percentage of the field is subtracted from the field.
8:
% The entered
percentage of the field is entered into the field.
13: HELP The fieldnumber, the
format and the legal codes for this field is shown at the bottom line.
If more than one
code has been defined you must press cr. to look through the lines.
The showing is
interrupted if you press any other key.
R1: HELP
If lamp R1 is switched on the help‑function
automatically appears each time you go to a field.
R4: LOCK STATUS
If this lamp is switched on you no
longer have to enter status.
Instead the status
you previous selected will be used.
7. Searching with Superindex.
8.1. Searching using Superindex.
By the use of SUPERINDEX you may search all
text‑fields in any of the DATAMASTER files:
Figure 19 SUPERINDEX search.
D.M.S. *
D A T A M A S T E R * 19....SUPERINDEX (SEARCH ALPHANUMERIC)
ARTICLE NO0102
DESCRIPTION TRUCK‑HOPPER
SELLING PRICE 20000,00
COST PRICE 10000,00
DATE OF LAST PURCHASE 1.01.85
ARTICLE NO0110
DESCRIPTION TRUCK‑WORK
SELLING PRICE 100000,00
COST PRICE 60000,00
DATE OF LAST PURCHASE 15.12.86
ARTICLE NO1001
DESCRIPTION TRUCK‑WHEEL
SELLING PRICE 1000,00
COST PRICE 500,00
DATE OF LAST PURCHASE 31.12.86
ARTICLE NO1005
DESCRIPTION TRUCK‑GEARBOX
SELLING PRICE 2000,00
COST PRICE 1500,00
DATE OF LAST PURCHASE 1.06.86
SEARCHTEXT:TRUCK
The search is not just the usual use of an
index‑key but a 'wide' searching in all the records of the file, a search
for any occurence of the entered text.
It is if you have a customer by the name
JOHN HANSON you just enter the search‑criterion JOHN or HANSON, maybe
even just NSON, and all the records containing the entered data will one by one
appear on the screen.
8.2.1. Technique when searching.
The superindex will search through the
entire file without using the index and therefore it might take some time
before it comes up with the answer if it has to search through a large file.
However this is done using a special
technique where a buffer that contains approximately 20.000 characters (as big
as possible for the given machine). As many records as possible are now read
into the buffer in one go and they are searched through by a single assembler‑call
from basic. This gives you a very fast searching‑possibility.
For smaller files the search‑time will
typically be a couple of seconds. 1.500 records per minute are searched
through.
The search‑time is dependent on the
total number of records in the file (not just the used records) as well as the
length of the records, and the partition‑size of the system, as these
factors determines the utilization of the buffer.
8.2.3. Searching using several criteria.
For search‑criterion you may enter
several different criteria, separated by "&".
If you for instance enter
JOHN&HARALD&PETER all records containing either JOHN or HARALD or PETER
will be found and shown on the screen in the same reading of the file.
This is particularly usefull if you are in
doubt of the spelling of a certain name.
If there are more than one record that
answer the given criterion, these will be shown in random order as you are not
using the index of the file.
8.2.5. Interrupting the search.
The search may always be interrupted by
pressing the ESCape‑key.
When pressing END as search‑key you
return to the DATAMASTER selector.
8.2.7. Selecting the fields to be shown.
Normally the first five fields will be shown
on the screen. As many records as possible will be shown in one screen image.
After this, the user is asked to press cr. to go to the next page.
However, it it not just these fields that
will be searched but the entire record, so the given criterion does not
neccessarily have to be contained in the shown fields.
In the search‑criterion you may
indicate which fields you want to be shown by entering for instance 1‑5,7,10‑20
followed by the cr‑. After this any future search will show these fields.
Figure 20 Selection of fields by search.
ARTICLE NO0102
DESCRIPTION TRUCK‑HOPPER
SELLING PRICE 20000,00
COST PRICE 10000,00
DATE OF LAST PURCHASE 1.01.85
SUPPLIER NO. 100
ARTICLE GROUP NO. 9
STOCK BALANCE 0
ALTERNATIVE SUPPLIER NO 0
FREE 0,00
ARTICLE NO1005
DESCRIPTION TRUCK‑GEARBOX
SELLING PRICE 2000,00
COST PRICE 1500,00
DATE OF LAST PURCHASE 1.06.86
SUPPLIER NO. 205
ARTICLE GROUP NO. 0
STOCK BALANCE 100
ALTERNATIVE SUPPLIER NO 102
FREE 0,00
SEARCHTEXT:HOP&BOX
9. Printing the files.
DATAMASTER contains three different
possibilities of printing:
1. Print using automatic screen
layout.
2. Print using user‑defined
screen image.
3. The reportgenerator.
DATAMASTER's own printfunctions are
relatively simple and mostly intended for documentation of the creation in the
form of lists or prints of the creation‑screen image, e.g. one screen
image on each page to use as checklists. There is no selection, sorting or
calculating available with these prints.
If you want to define more complex prints it
must be done by the use of the reportgenerator DMS.RAPGEN. This is not a part
of the DATAMASTER but must be purchased separatly. The reportgenerator contains
the possibility of defining all types of reports from up to 9 files at the same
time and the DATAMASTER files may be used directly.
10.1. Print with automatic screen image.
When choosing this function the following
screen image appears:
Figure 21 Selecting DATAMASTERs print functions.
D.M.S. *
D A T A M A S T E R * 18....PRINT OF FILE DATA USING AUTOMATIC
PRINTER:$LPT TYPE:1 1 = 1 RECORD / PAGE
LINES ON FORM: 51 2 = MORE RECORDS /
PAGE
3 = LISTE (1 RECORD PR.LINIE)
FIELDS: INDEX:1 1 = ARTICLE NO.
START FROM: 1000
STOP AT:
1005
and
you may enter the following:
10.2.1. Printer.
You can choose on which printer you want the
print made. If you just press cr. the normal printer $LPT will be chosen.
10.2.2.1. Lines per page.
The length of the page is decided here. If
you just press cr. the standardvalue
decided by the programmer will be used.
10.2.3. Printing type.
Here you may choose between three different
types of print:
10.2.4.1. 1 record per page.
One screen image only printed is on each
page, this function is usually used for checklists.
10.2.4.3. As many as possible on each page.
The print looks just like the print from
function 1, but the system does not throw pages for every record.
10.2.4.5. List (1 record per line).
In this function the print is turned around
so that a heading is built on the basis of the field‑names and the
individual records are listed with one line per record.
10.2.5. Fields.
Here you may choose the fields you want
printed.
This is done by entering for instance 1‑7,15,9‑10
and the fields 1 to 7 followed by fields 15, 9 and 10 are printed.
If you just press cr. fields 1‑99,
i.e. all the fields of the file will be printed.
If you have chosen print‑type 3; List,
only as many fields that one line can hold will be printed no matter if you
have indicated more fields than that.
10.2.7. Index (printing‑order).
Now you may choose in which order you want
the list to be printed in.
An outline of the indexes you have defined
in the file will appear and you may enter the number in question.
If you just press cr. index 1 will be chosen
as a standard.
10.2.9. Start from and Stop at.
After this you may enter start/stop values
according to the chosen index. If you have selected a customer‑number
index you must enter from/to customer‑number and if you have chosen a
name index you must enter from/to name.
If you just press cr. in both of the fields
all the records of the file will be
printed in the selected order.
When having entered the start and stop the
chosen records are printed by the printer and after this you may again enter
start/stop. Several different ranges may be printed.
You terminate the program by typing END or
pressing cr.‑ when placed in the fields Start from.
10.2.11. Examples of prints.
Figure 22 One record on each page.
01 ARTICLE NO. 1001
02 DESCRIPTION TRUCK‑WHEEL
03 SELLING
PRICE 1000,00
04 COST
PRICE 500,00
05 DATE OF
LAST PURCHASE 31.12.86
06
SUPPLIERNO.205
07 ARTICLE GROUP NO. 0
08 STOCK
BALANCE 100
09
ALTERNATIVE SUPPLIER NO. 102
10 FREE 0,00
01 ARTICLE NO. 1005
02 DESCRIPTION TRUCK‑GEARBOX
03 SELLING PRICE 2000,00
04 COST
PRICE 1500,00
05 DATE OF
LAST PURCHASE 1.06.86
06 SUPPLIERNR.100
07 ARTICLE
GROUP NO. 1
08 STOCK
BALANCE 10
09 ALTERNATIVE
SUPPLIER NO. 0
10 FREE 0,00
Figure 23 One record on each line (list).
DATE 31.03.79 * DEM‑ARTICLE
FILE VA * PAGE: 1
01
02
03 04 05 06
07 08 09
ARTI DESCRIPTION SELLING P COST PRIC DATE OF SUPP ARTI STOCK B ALTE
0101 BOLT 2,OO 1,50
1.01.87 271 0
100 270
0102 TRUCK‑HOPPER 20000,00 10000,00
1.01.85 100 9
0 0
0110 TRUCK‑WORK 100000,00 60000,00 15.12.86 123
2 1 100
1001 TRUCK‑WHEEL 1000,00 500,00 31.12.86 205
0 100 102
1005 TRUCK‑GEARBOX 2000,00 1500,00
1.06.86 100 1
10 0
2001 BOLT‑SPEC./AL 20,00 10,00
1.01.87 205 9
10 102
2002 BOLT‑SPEC./BR 25,00 10,00 30.07.86 205
9 200 102
10.3. Print with user‑defined screen image.
When you choose this function you must at
first enter which screen image you want to use. In this way DATAMASTER will
also know which file that is to be printed.
The function works in exactly the same way as
printing with automatic screen image except from the point that you cannot
choose the fields to be printed. This has been defined in the screen image
itself.
Likewise print‑type 3 cannot be chosen
as this has no connection to the screen image.
10.5. Print using the reportgenerator.
Choosing function 20 you jump directly to
the reportgenerator DMS:RAPGEN, that is if it has been installed on the system.
By the use of the reportgenerator you may define all kinds of lists and
letters.
Besides, please refer to the
reportgenerator‑manual for further information on the use of the
reportgenerator.
Figure 24 Definition of a new report.
DMS.REPGEN 1
1....DEFINE NEW REPORT
GR.... ARTICLE GROUP FILE
KU.... CURRENCY FILE
LE.... SUPPLIER FILE
VA.... ARTICLE FILE
FILE SHORTNAME ? VA......ARTICLE
FILE
REPORT NAME (FOR SELECTOR) ? PRICELIST
LINES ON FORM (CR=66) ?
66
MAIN HEADING (N=NONE, CR=AS NAME)
? PRICELIST
PRINT ZERO FIELDS (Y/N) ? Y USER NAME ? XXXXXXXXX
Figure 25 Example of printout from the reportgenerator.
DATE:14,01,87 * WEIGHTED STOCK
VALUE * AS OF 14,01,87
PAGE: 1
NO DESCRIPTION COST PRICE BALANCE STOCKVALUE WEIGHTED
0101 BOLT 1.50 100
150.00 0.12
0102 TRUCK‑HOPPER 10000.00 0 0.00 0.00
0110 TRUCK‑WORK 60000.00 1
60000.00 47.15
ARTICLE GROUP 01 60150.00 47.27
1001 TRUCK‑WHEEL 500.00 100
50000.00 39.29
1005 TRUCK‑GEARBOX 1500.00 10
15000.00 11.79
ARTICLE GROUP 10 65000.00 51.08
2001 BOLT‑SPEC./AL 10.00 10
100.00 0.08
2002 BOLT‑SPEC./BR 10.00 200
2000.00 1.57
ARTICLE GROUP 20 2100.00 1.65
GRAND TOTAL
127250.00 100.00
10.7. Updating files using the
reportgenerator.
Normally it is not possible for the user to
write to any files by the use of the reportgenerator as this would be far too
dangerous. The probability of
incedently destroying the installation is far too big.
However, one exception is the files the
user has defined himself in DMS.DATAMASTER. In these files rewriting is
allowed, protected by a password however, based on the philosophy that you know
suffiently about the data you have defined yourself for rewriting to be
securely.
When rewriting the user simply calculates
the fields in the file instead of calculating the free fields, e.g. #7=#7+1
leads to field 7 (for instance a dun‑code) being increased one each time
the report is run. This, is only done for the records that are printed, not for
records which not fulfils the selection criterias.
There is no possibility of amending index‑fields
during this form of rewriting. If you calculate an index‑field the
contents of the key and the data in the record will become inconsistent. After
this DATAMASTER will reject any aim at amending/deleting such a key‑field.
It is however possible to reconstruct the file by choosing the DATAMASTER
function for expansion of a file, and the new keys will be built up on the
basis of the fields in the datarecord.
At present it is not possible to build
other files in the reportgenerator and when running with integration to several
files it is only possible to rewrite the main‑file, i.e. the file the
report has been defined on.
Rewriting in a file built with DATAMASTER
must be activated already when defining the report, when the file‑shortname
is entered. For instance you enter comma W after the shortname, e.g. KU,W. This
way another text‑file for read statements is loaded in the program.
DMREAD.KUW will be activated instead of the usual DMREAD.KU. At the same time
the report will be password‑protected, so that you have to enter this
password when starting up.[6]
11. Definition of checks on code‑fields.
12.1. Principle.
The principle of a check‑definition is
to choose a specific field from the file and attach one or more legal values to
this field, each value defined with an connected text.
When having defined these checks, it is only
possible to enter the defined values in the field in question and the text
attached to the field will be shown at the screen to the right of the field. In
this way the user is able to see the function of the code in clear text.
Figure 26 File maintenance with check‑codes.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 1001
02 DESCRIPTION TRUCK‑WHEEL
03 SELLING
PRICE 1000,00
04 COST PRICE 500,00
05 DATE OF
LAST PURCHASE 31.12.86
06 SUPPLIER
NO. 205 PRIVATBANKEN
07 ARTICLE
GROUP NO. 0 OTHERS
08 STOCK
BALANCE 100
09
ALTERNATIVE SUPPLIER NO. 102
10 FREE 0,00
FUNCTION:3=AMEND FIELDNO.?
The appearance of this text to the right of
the field is of cause dependent on how the file‑screen image in question
is defined. A text too long may overwrite the next field on the screen. For
this reason we have introduced the concept of text length that defines the
number of characters to be shown at this particular point.
The texts may be created longer than this
length in consideration of the help‑function and the documentation, but
if so, abbreviated on the screen image.
12.3. Using function 7 ‑ define check.
When choosing function 7; definition of
check on code‑fields, the following screen image appears:
Figure 27 Definition of check on code‑fields.
SYSTEM:0/EX DMS.RAPGEN ENGLISH FEB 01, 1988 9:42:40
FILE FIELD TEXT LENGTH
STATUS (1=CREATE, 2=READ, 3=AMEND,
4=DELETE, 5=TEXTLENGTH, 6=PRINT) ?
and
by choosing one of the functions 1‑6 you may maintain the definitions
(i.e. create/amend/delete/print).
If
you just press cr. you return to the DATAMASTER main menu.
12.4.1. Choosing file to check.
When you choose function 1; creation, you
get an outline of all the DATAMASTER files you have access to:
Figure 28 Selection of file.
SYSTEM:0/EX DMS.RAPGEN ENGLISH FEB 01, 1988 9:42:40
FILE FIELD TEXT LENGTH
FILES:
GR ART.GROUP FILE
KU CURRENCY FILE
LE SUPPLIER FILE
VA ARTICLE FILE
STATUS (1=CREATE, 2=READ, 3=AMEND,
4=DELETE, 5=TEXTLENGTH, 6=PRINT) ? 1
and
you choose the file you want to work with by entering the file‑shortname.
If you just press cr. the program returns to the point where you choose
functions.
12.4.3. Selecting field to check.
Now a outline showing the fields of the file
appears:
Figure 29 Selection of a field.
SYSTEM:0/EX DMS.RAPGEN ENGLISH FEB 01, 1988 9:42:40
FILE FIELD TEXT LENGTH
VA ARTICLE FILE
FIELDS:
1 ARTICLE NO
2 DESCRIPTION
3 SELLING PRICE
4 COST PRICE
5 DATE OF LAST PURCHASE
6 SUPPLIER NO
7 ARTICLE GROUP NO
8 STOCK BALANCE
9 ALTERNATIVE SUPPLIER
10 FREE
STATUS (1=CREATE, 2=READ, 3=AMEND,
4=DELETE, 5=TEXTLENGTH, 6=PRINT) ? 1
You may define checks for numeric as well as
alphanumeric fields. Here you select
which field you want to define a check for.
12.4.5. Text length.
After this you enter the length of the text
you want shown on the screen to the right of the field when creating/amending
the file. This length is of cause dependent on how you build the screen image
in question and 10‑16 characters will normally be adequate.
Specificly you may enter 0 here and no text
will be shown at all, only the defined validation will be carried out. This way
you have room for more fields on the screen.
12.4.7. Minimum and maximum allowed value.
Now you enters the wanted legal value‑range
(from‑to) for the field.
Figure 30 Entering of the legal ranges.
SYSTEM:0/EX DMS.RAPGEN ENGLISH FEB 01, 1988 9:42:40
FILE FIELD TEXT LENGTH 16
VA ARTICLE FILE 7 ARTICLE GROUP NO
MIN MAX
TEXT
0 0 UNSPEC
1 1 SPECIAL
2 2
CASH
3 3 CARS
4 10 OTHERS
##
STATUS (1=CREATE, 2=READ, 3=AMEND,
4=DELETE, 5=TEXTLENGTH, 6=PRINT) ? 1
It will be the codes in the given ranges
only (both extreems included) that in the future will be allowed for the field.
If you have already created records in the
file in question the system can of cause not garantee that all previously
created codes will be valid. If necessary you will have to use the
reportgenerator to check up on this.
If the previously created records contains
valid values they will in the future be shown with the attached text.
12.4.9. Text.
Here you enter the text you want attached to
the value‑range.
The first x characters of this, as indicated
in the text length, will be shown to the right of the field by the creation of
the file.
If the first character of the text is ; this
indicates reading from another file and the rest of the text will contain a
definition of how this file is to be read and which fields are to be
transferred/shown, more on this later on.
When having entered the text you will be
asked to enter the next minimum/maximum allowed value of the field and this way
you may specify as many legal ranges as necessary.
If you just press cr. for minimum the
creation is terminated and you return to the function‑field.
12.5. Inquiry on the check‑codes.
In this function, like in the creation of
the definitions, you indicate a file and a fieldnumber and the defined checks
will appear.
12.7. Amending the check‑codes.
If you want to amend the text in an already
created range, or even want to amend the range itself, you use function 3.
The amendment is made in the same way as an
creation of a new check‑code, however, the interval you enter must be
created already.
If you want to add new ranges for a
particular field that already has defined checks, this must be done by the use
of function 1; creation.
12.9. Deleting check‑codes.
By the use of function 4 you can delete a
single interval or all validations created for a certain file.
If you only indicate a file‑name and
simply press cr. at the fieldnumber you wil be asked if you want to delete all
checks valid for this file.
12.11. Amending the text length.
Here
you may amend text length appearance that was entered at the first creation of
check‑codes for the field.
The created codes are shown and after this
you may enter a new text length.
12.13. Printing the check‑codes.
Choosing function 6 all defined check‑codes
for all files will be printed.
The print will always be on the standard
printer ($LPT).
12.15. Help‑function by file
maintenance.
The different allowed values for a code and
their meaning may be shown by pressing the HELP‑key when positioned in
the field in question.
Figure 31 The help‑function for check‑code fields.
D.M.S. *
D A T A M A S T E R * 10....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO. 1001
02 DESCRIPTION TRUCK‑WHEEL
03 SELLING
PRICE 1000,00
04 COST
PRICE 500,00
05 DATE OF LAST PURCHASE 31.12.86
06 SUPPLIER
NO. 205 PRIVATBANKEN
07 ARTICLE
GROUP NO. 0 OTHERS
08 STOCK BALANCE 100
09
ALTERNATIVE SUPPLIER NO. 102
10 FREE 0,00
FUNCTION:3=AMEND FIELDNO.?
You may also switch on lamp‑1 (R1) and
as long as it is switched on the help‑texts will appear each time you move
to a new field.
12.17. Amending the file‑definitions.
You must be aware of the fact that if you
amend the length of a field that has check‑validations attached to it,
these validations will not automaticly be amended!
The result will normally be that you are not
allowed to enter any values at all into the field in question, if for instance
the field is created with check on 2 digits and the field is being extended to
for instance 3 digits this means that the validation‑ranges will be
displaced compared to the current field.
Code‑fields like this should always be
made sufficiently long when created. A code created with 3 digits may always be
reduced to 1 digit by creating check‑intervals in the area 0‑9
alone, whereas an expansion from 1 to 3 digits is not possible directly.
When performing an expansion like this you
have to delete all validations for the field in question by the use of function
4 and after this create them again by the use of function 1.
12.19. Conflicts when creating legal ranges.
When creating check‑codes you must be
very careful with the intervals you specify, so that they will not overlap.
If you for instance define the range 10‑20
to be allowed and after this that
code 13‑13 should also be allowed, this check act slightly odd: The codes
10‑12 will not be allowed, code 13 and 14‑20 will work correctly.
This is due to the fact that DATAMASTER is
always searching for the check‑code that has a maximum value higher than
or equal to the entered value and after this checks that the minimum value in
question is correct.
This means that you instead should create
checks for the ranges 10‑12, 13‑13 and 14‑20 after having
deleted the ranges 10‑20.
12.21.
6.11. Internal storage of the check‑codes.
The defined check‑validations are
stored in an seperate file DXVIKAIX with an access‑key consisting of:
xx File shortname
yy blank, free for later expansion
zz Fieldnumber
Maximum n character maximum of the range
Minimum n character minimum of the range
n
being the length of the field.
The record in this file contains the text
length and the text attached to the range.
n mentioned above means the length of the
field, and a check for the file KU, field 7 in the range 5‑47 will (if
the field is 2‑digit) accordingly have the key:
"KU 074705"
The programmer may have created this file
with a free choice of keylength and recordlength (normally respectively 20 and
64) and in this way it is determined how many characters you have available:
The largest field in which you can create
checks has the length:
n = (keylen‑6)/2, e.g. (20‑6)/2
= 7 digits
The length of record ‑4 is the longest
text that may be attached to a code.
13. Integration to other files.
14.1. The principle of integration to other
files.
When defining check on fields (please see
the previous chapter) you may also define check against/transfering fields from
one ore more other files (max. 8 files and only one file for each field).
By specifying a special text starting with
you may create a connection to another file for the field in question. Instead
of just showing the text DATAMASTER will read the given file and tranfer a
number of fields from this file.
You may transfer any number of fields from
another file and this file does not necessarily have to be a DATAMASTER file,
it may also be an existing customer‑file. However, the files must be defined
by the programmer by the installation as when installing the reportgenerator.
This means that files installed in the
reportgenerator may by used right away.
14.3. Definition of reference to a file.
Reference to another file is defined as a
normal input‑validation with a special text where the first character is .
You may define up till 8 different files,
which means that the program gives you the possibility of working with all in
all 9 files at the same time. The files may be DATAMASTER files or other files
installed in the reportgenerator.
Figure 32 Reference to a secondary file.
SYSTEM:0/EX DMS.RAPGEN ENGLISH FEB 01, 1988 9:42:40
FILE FIELD TEXT LENGTH 16
VA ARTICLE FILE 6 SUPPLIER NO.
MIN MAX
TEXT
000 ZZZ
LE01,2;6
STATUS (1=CREATE, 2=READ, 3=AMEND,
4=DELETE, 5=TEXTLENGTH, 6=PRINT) ? 1
14.4.1. Minimum/maximum range.
The range defined for the check‑code
will normally be from 0‑9999... for numeric fields and from 0 to z for
alphanumeric fields which means that all values of the field will execute a
reference to another file.
14.4.3. Structure of the textfield.
The textfield may for instance be defined
as:
KU01,2,3=4,4=5,2=17;7
and this way starts with
and is followed by:
14.4.4.1. File‑shortname.
KU indicates the 2‑letter shortname of
the file to be read.
14.4.4.3. Index‑number.
01 indicates the index‑number in the
file KU. If this is 1 you may omit this and just write KU,2,....
14.4.4.5. Transferring fields.
This is followed by a specification of which
fields you want transferred from the read file, each separated by a comma.
Each specification consists of:
fieldnumber from this file
=
fieldnumber from the read file
and with the shown definition 3=4,4=5,2=17
the KU fields 4,5 and 17 are moved accordingly to
this
files fields 3,4 and 2.
You may transfer as many fields as you like,
limited only by the length of the text‑field.
You may also leave out this part entirely if
you don't want to tranfer any fields, e.g. ,2;7.
The field‑transfer is terminated with
a semicolon and followed by:
14.4.4.7. Key definitions.
7 in the example shown above defines field 7
from this file to be used as a key when reading the referenced file KU.
Normally it will always be the same
fieldnumber that the check‑code is defined on which appears here, as the
field that executes references to the file naturally also will be used as a
key.
The key‑definition follows the normal
syntax for index‑definitions, please see the description of this. This
means that here you may pack fields, insert constants in front of the field
etc., e.g.:
KU01,2,3=4,4=5,2=17;"00",7(3,4),7(1,2),P
14.4.5. Various values without references in the
file.
When you have defined a check‑code for
a field defining another file to be read it will not be possible to enter
values into this field if no corresponding record key exist in the connected
file.
For certain records you might want not to
set a value at the time of creation
but this is not possible as a key must be found in the file referred to.
In such a case you may create a 'various'
record in the file referred to and this
number should then be used by creation.
You may also define a normal check‑code
in the range of 0 to 0 with the text 'various'. Entering of 0 will not execute
any file reading.
A typical example is a customer number 0000
is defined as a 'various' customer, that always may be used even if this if not
present in the customer file.
14.4.7. Limitations.
You may transfer as many fields as you want
from other file, limited only by the text‑length of 80 characters.
You may refer up till 8 other files.
A check may only refer to one file, it is
registration of one field can not read
from serveral files for the same value.
You may create different checks on a field
so that the field, dependent on the value, causes read from different files.
One file can only be referenced once, you
cannot use the same file from several fields in the same program.
15. Definition of individual screen
images.
By this function you may define your own
screen images for the file maintenance
program.
Figure 33 File maintenance with user defined screen.
D.M.S. *
D A T A M A S T E R * 9.....FILE MAINTENANCE WITH AUTOMATIC
SCREENPICTURE
01 ARTICLE NO.0101 02
DESCRIPTION:BOLT 07 ARTICLE
GROUP NO.0 UNSPEC
PRICES: 03 SELLING:
2.00 04 COST: 1.50
SUPPLIER NO: 06 NORMAL: 271 UNICEF
FUNKTION:
1=CREATE 2=READ
3=AMEND 4=DELETE 5=SEQUENCE
16.1. Maintaining the screen images.
When selecting function 12 you enter:
1.
Program‑number (screen image‑number)
2.
Name of program
3.
File‑shortname
Figure 34 Definition of a new screen image.
D.M.S. *
D A T A M A S T E R * 12....DEFINE NEW SCREEN LAYOUT
1 PRODUCT FILE e
3 INVENTORY FILE
4 CAR FILE
5 EMPLOYE FILE
6 CUSTOMER MAILING
7 ARTICLE GROUPS
8 CUSTOMER GROUPS
PROGRAM NO.(CR=NEXT FREE) ? 2 PROGRAM NAME:ARTICLE
CREATION
16.3. Using functions 12 and 13.
After specification of program no., name and
file you will get a screen like:
Figure 35 Building the screen image.
1...;....10...;....20...;....30...;....40...;....50...;....60...;....70...;....8
1
2
01 NO.AAAA 02 NAME:AAAAAAAAAAAAAAAAAAAA 07 GROUP:## 3
4
PRICES: 03 SALE
######.## 04 COST ######.## 5
6
SUPPLIERS: 06 NORMAL:AAA
7
8
9
10
11
12
13
14
15
16
17
18
LINE,POS:
50...;....60...;....70...;....80...;....90...;....100..;....110..;....120..;....
and
the cursor will be placed in the lowerleft corner in the field, LINE,POS.
The fields are shown on the screen with
their formats. A row of x's indicates a textfield, and a row of #'s or ‑'s
indicates a numeric field. You may select a line by entering the number of this
or the linenumber, comma a position on the line.
How this line and the two following lines
will be shown is seen on the bottom lines of the screen, not with fieldformats
but with fieldnumbers.
The line may now be altered and when you
press CR ‑ the line will be placed on the screen and fieldnumbers are
converted to the fieldformats, and the cursor returns to LINE,POS. Only the
number of characters you enter will be changed. If you wish to delete the line,
you must fill the rest of the line with blanks. You may keep the same character
by using the arrow‑up key.
The changes are ended by typing END or just
press CR‑. NB.: A screen‑image must be kept within the screen's 24
lines and 80 characters. If a field for instance exceeds a line, strange scrolling
will occur when using the image.
16.5. Selecting fields and fieldnumber‑sequence.
In connection with the definition of the
screen‑image you have the possibility of indicating:
‑ fields to be entered by the
creation and the order of this entering
‑ fields allowed to be
amended
‑ fields to be displayed on
the screen
Default
1‑99, it is all fields may be entered/corrected/shown in the order they
appear in the file.
The sequence may be indicated in lines 26,
27 and 28. As screen only holds 24 lines, these lines will not appear on the
screen but only serves to control the data‑entering.
The lines are entered as:
1‑99 all fields
1‑5,17,2 field 1 to 5 followed by field 17 and field
2
In
this way all the sequences of the fields can be indicated.
In the file maintenance‑program
itself (function 9) you may also define
an create‑sequence (status 5). This will overwrite the sequences
defined for the screen image but for the current creation only.
The
lines contain:
26 creation‑sequence
27 fields allowed to be amended
28 fields to be displayed
As mentioned all three lines will contain 1‑99
as default. It is possible to blank out lines 26 and 27 so the only information
left is the information of which fields that are to be displayed. In this case
the user of the program is only allowed to make inquieries on the file, he will
not be able to create, amend or delete.
16.7. Commands in functions 12 and 13.
You may at LINE,POS use the following
special commands:
16.8.1. Lineno.
If a linenumber is entered, the line is
shown on the screen. The screen will scroll up/down if the chosen line is not
in the range of the actual linenumber interval shown on the screen.
16.8.3. position.
As above, the line may be corrected from the
entered position.
16.8.5. CR.
The screen will scroll one line up.
16.8.7. End or CR‑.
Function ended.
16.8.9. PRINT‑printout on printer.
The layout of a screen is printed on the
printer.
16.8.11. F ‑ Top of form.
Will perform a paper feed up to next form.
16.8.13. ? or the help‑key.
You can see the fields of this file.
Figure 36 Help‑function by screen image definition.
PROGRAM NO: 2 ARTICLE CREATION
1 ARTICLE NO
2 DESCRIPTION
3 SELLING PRICE
4 COST PRICE
5 DATE OF LAST PURCHASE
6 SUPPLIER NO
7 ARTICLE GROUP NO
8 STOCK BALANCE
9 ALTERNATIVE SUPPLIER
10 FREE
PRESS CR:
16.8.15. IL or LI insert one line.
By the use of one of these commands you may
insert a line before a particular linenumber and the rest of the lines are
moved one line down.
NB.:
You have to pay attention to the fact that lines 26‑28 (containing
the definition of which fields that are to be created/amended/shown on this
screen) are also moved when using this command. Therefore you must always make
sure to bring them back to their places after having inserted a line.
16.8.17. DL or LD delete a line.
By the use of one of these commands you may
delete a particular line and the rest of the lines are moved one line up.
NB.:
You have to pay attention to the fact that lines 26‑28 (containing
the definition of which fields that are to be created/amended/shown on this
screen) are also moved when using this command. Therefore you must always make
sure to bring them back to their places after having deleted a line.
16.8.19. MODE show the field formats/numbers or
names.
By the use of the MODE command you may define
how you want the fields to be shown or printed(by the use of the PRINT
command). You will be asked to enter some of the following numbers:
0 = show fieldnumbers
1 = field is not shown at all
2 = fieldnames are shown (as long
as there is room for them)
3 = fieldformat is shown (normally)
Figure 37 MODE 0 displays the field numbers.
1...;....10...;....20...;....30...;....40...;....50...;....60...;....70...;....8
1
2
01 NO.#1 02 NAME:#2 07 GROUP:#7 3
4
PRICES: 03 SALE #3 04 COST:#4 5
6
SUPPLIERS: 06 NORMAL:#6
7
8
9
10
11
12
13
14
15
16
17
18
LINE,POS:
50...;....60...;....70...;....80...;....90...;....100..;....110..;....120..;....
16.9.
8.5. Copying a screen‑image.
One screen‑image may be copied to
another by the use of function 14, where you enter:
FROM PROGRAM NO.:
TO
PROGRAM NO.:
NEW
PROGRAM NAME.:
and after this the screen‑image is
copied. The copy‑function is especially useful when used for taking a
copy of an existing screen‑image you want to amend, but certainly not
ruin!, and then perform the amendments in the copy, maintaining the original.
Figure 38 Copy screen images.
D.M.S. *
D A T A M A S T E R * 14....COPY SCREEN LAYOUT
1 PRODUCT FILE
3 INVENTORY FILE
4 CAR FILE
5 EMPLOYE FILE
6 CUSTOMER MAILING
7 ARTICLE GROUPS
8 CUSTOMER GROUPS
PROGRAM NO.? 3 TO PROGRAM NO.? 10 NEW NAME: TESTPROGRAM
16.11. Deletion of a screen image.
By use of function 15 you are able to delete
a screen image, you have to confirm the deletion by answering Y at the question
DELETE Y/N.
Figure 39 Deletion of a screen image.
D.M.S. *
D A T A M A S T E R * 15....DELETE SCREEN LAYOUT
1 PRODUCT FILE
3 INVENTORY FILE
4 CAR FILE
5 EMPLOYE FILE
6 CUSTOMER MAILING
7 ARTICLE GROUPS
8 CUSTOMER GROUPS
PROGRAM NO.? 3 INVENTORY FILE DELETE (Y/N) ?
17. Redefining files.
Redefining an exsisting file may be done by
use of 3 different functions.
2
REDEFINE AN EMPTY FILE
3
REDEFINE AN EXISTING FILE
4
AMENDING A FILE WITHOUT REDEFINING IT
Functions
2 and 3 are protected by a password [7],
and you should be careful before selecting as all the data in the file is
relocated together with the file‑definition when using these functions.
You will always get the warning:
BE CAREFUL ‑ DO YOU HAVE A BACKUP ?
when selecting one of these functions. If a
file has been created with 1000 records and something fails you might risk
ending up without a file and without a file‑definition.
Redefining files of this size should
accordingly always be done right after a disk‑copying (end of run).
18.1. Redefining an empty file.
IN THIS FUNCTION ALL THE DATA IN THE
FILE IS DELETED !!
The function is used for redefining a file
concerning the number of records and/or the number of fields or the length of
the fields.
This function should only be used when the
file does not contain any data you want to keep.
This function may be used for deleting the
contains of a file without redefining the file as you just exit by the use of
END without amending the field‑definitions.
You are able to amend all field‑ and
index‑definitions in the file in exactly the same way as described in the
first chapters of this manual; defining a file.
After having terminated with END a new empty
file is built replacing the
existing.
18.3. Redefining an existing file.
This function is used for redefining an
existing file concering the number of records and/or the number of fields or
the length of the fields.
All data in the old file will be kept.
Before you redefines the file DATAMASTER will take care of keeping a copy of
the old definition of this file.
When you have finished the redefinition the
new definition will be compared to the old definition and a special program
that reads the old file and builds up the new file with the new format will be
generated and run.
18.4.1. Expansion/reduction of the fields.
All information concerning the fields may be
amended with this function as described in "defining a file". You may
add to or reduce the number of fields in the file.
Furthermore the length of the fields may be
amended, even if this would mean that the internal type of BASIC‑variable
of the field must be amended to be able to contain a larger value. The copying‑program
takes hands of this.
You may even change a field‑type from
numeric to text or vice versa. If possible the data will be maintained and a
text containing a figure will accordingly be moved correctly to a new numeric‑field.
YOU
SHOULD NOTE:
If you reduce the length of a field there
is a risk that the old value of the field cannot be contained in the new field.
You must especially try to avoid reducing fields with 4 or more digits to
fields with 3 or less digits without being completly sure that the new field
can contain all the data. If it cannot the file cannot be copied at all.[8]
18.4.3. Redefining/adding to the index.
All the information regarding the index may
also be amended in this function as described in "defining a file".
You may add to or reduce the number of fields in the file.
YOU
SHOULD NOTE:
In case you define new unique keys, e.g.
with K attached to a field, it MUST be possible for DATAMASTER to create a
unique key on the basis of the existing data in the file; there cannot be two
records with the same value in the field in question.
If this is the case anyway it will only be
the first of these records that will survive the copying, all others will be
deleted and you will receive a message of error 109.
18.4.5. Expansion/reduction of the number of
records.
The most simple redefinition is to amend the
number of records in the file and after this press END in the first field. In
this way a file can be expanded or reduced.
However, this new file will not be created
if there is space for it on the disk but the old file will be maintained. This
way you don't loose your data if the unfortunate should happen.
Later on you may perform another
redefinition after having provided the necessary amount of space. This may be
done by for instance deleting other files or by the use of CLEANUP on the disk.
NB.: If you try to reduce a file to fewer
records than has already been created in an existing the extra records will be
deleted and you will receive a message of error 113.
18.4.7. Moving a file to another disk.
In connection with the redefining it is also
possible to move the file to another disk. All you have to do is to specify a
new disk‑number by the start of the redefinition.
18.5. Amending a file without redefining it.
In this function an existing file may be
amended in the same way as described for function 3 but ONLY in such a way that
it does not require any creation of a new file and copying data.
It is much faster to use this function, if
possible, instead of function 3, as building a new file or creating/running a
copying‑program from the old file to the new is not necessary.
In return, it is not all types of amendments
that may be made here. Only amending the field‑definitions is allowed;
the file cannot be moved nor expanded and the index‑definitions cannot be
touched.
The field‑names may be amended without
limitations, whereas amending the field‑formats can only be done to a
limited extent as you have to maintain the BASIC variable‑types the file
was built with.
Accordingly the fields may be reduced since
a smaller field can always be contained in a too large fieldtype, all you risk
is waisting a little space at the disk.
Furthermore, numeric fields may be expanded
with the following limitations:
1‑2 digits may be
expanded to 3 digits (without decimals)
4‑5 digits may be
expanded to 6 digits
7‑9 digits may be
expanded to 10 digits
11‑13 digits may be
expanded to 14 digits
and
if the field from the start has been defined with decimals:
1‑5 digits may be
expanded to 6 digits
Furthermore
comma, and if necessary comma‑editing, may be entered quite freely.
18.7. Consequences of the redefinition.
18.8.1. Check on code‑fields.
If you expand code‑fields on which you
have defined checks by the use of function 7 you must remove these checks
before expanding the field. After the expansion you have to re‑create the
checks. If this is not done, the check‑function
will block the field entirely.
18.8.3. Reportgenerator‑programs.
If you just have added some fields you will
be able to run the existing reports without any further action. However,
you must pay attention to the fact that
the 20 free‑fields automatically inserted by the reportgenerator at the
end of the file will have changed fieldnumbers. It is you have to redefine the
calculation‑lines etc. the first time you want to amend a report like
that.
If you have amended the length of the fields
all reports that handles the file in question should be passed through function
4; define calculations. This way the new file‑structure will be
activated.
Furthermore it may be necessary to adjust
the report‑layout itself. This is done by the use of function 7.
19. Printing and deleting the
definitions.
20.1. Printing the file‑definitions.
When you choose function 5 to print the file‑definitions,
you must specify which file you want printed. After this you will get a
complete documentation of the file in question.
Figure 40 Printout of a file definition.
DATAMASTER SYSTEM 11,9 0/EX
DMS.RAPGEN ENGLISH
(0/ENDATAFIL9) FEB 01, 1988
DRN NO. 1 ARTICLE FILE , TOTAL SIZE =
57 BYTES ( 29 WORDS )
NO.OF FIELDS: 10 , 1% 2 , 2% 2 , 3%
3 , 4% 0 , $ 3 , LEN S$= 28
#1,0/EN.VAKA# READ READ: 1‑10
THE FILE IS DEFINED WITH RECORD
LENGTH = 62 BYTES (31 WORDS)
FILE:VA 0/EN.VAKA# ARTICLE FILE INDEX LENGTH:2,12,3,3,3
INDEX:01 ARTICLE NO 1,S
INDEX:02 DESCRIPTION 2,NP,S
INDEX:03 SUPPLIER NO 6,NP,S
INDEX:04 GROUP NO 7,NP,S
INDEX:05 ALTERNATIVE SUP. 9,NP,S
NO.NAME FORMAT CHECK PSEUDO TYPE
VARIABLE BYTE REF. W
1 ARTICLE NO 4 K 3***** 0
S$(1,4) 4 VA#1 W
2 DESCRIPTION 20 D 3***** 0
S$(5,24) 8 VA#2 W
3 SELLING PRICE 6,2 3 S3(1)
28 VA#3 W
4 COST PRICE 6,2 3 S3(2)
34 VA#4 W
5 DATE OF LAST PURCHASE , 6,
4 DATE 2 S2(1)
40 VA#5 W
6 SUPPLIER NO 3 D 3***** 0
S$(25,27) 44 VA#6 W
7 ARTICLE GROUP NO 2, D 3***** 1
S1(1) 48 VA#7 W
8 STOCK BALANCE ‑ 6, 2 S2(2)
50 VA#8 W
9 ALTERNATIVE SUPPLIER NO 3, D 3***** 1
S1(2) 54 VA#9 W
10 FREE ‑ 6,2 3 S3(3)
56 VA#10W
20.2.1. Remarks on the printout.
The first line contains a heading with the
system‑name and an specification of which file the file‑definition
is stored in.
The next line contains the definition number
followed by an name in clear text and the record length.
Finally is a list of all the fields of the
file. The left part (number, name and format) is defined by the user and the
right part is DATAMASTER's own information on the fields.
The column CHECK contains information on the
input‑validation that must be performed for fields:
3 = keyfield, marked with an * by
input.
4 = validation of date
9 = check‑codes defined for
the field
The column PSEUDO is not being used.
The column TYPE indicates the basic variable
type in which the field is stored and the next column, VARIABEL, indicates the
DATAMASTER name of this variable.
The column BYTE contains the physical
bytenumber in the record in which this field is stored. Together with the basic
variable this gives a programmer all information of the file structure,
nessesary to write special programs using this file.
The columns REF and W are always filled out
with the file‑abbreviation, fieldnumber and W that indicates that the
user has access to write in the field in question.
20.3. Deleting a file and its definition.
By the use of function 6 you may entirely
remove from the system a file and all definitions attached to it.
After having entered the file‑shortname
the following screen‑image will appear:
Figure 41 Deletion of a file.
D.M.S. *
D A T A M A S T E R * 6.....DELETION OF A FILE &
DEFINITIONS
FILE SHORTNAME ? VA ARTICLE
FILE
u
DELETE VA 0/EN.VAKA (Y/N) ?
and
you have to confirm the deleting by answering Y or regret by answering N.
If you answer Y the entire definition and
all data in the file and all the space that was occupied by this is now
free.
Figures
Figure
1 Systemübersicht........................................................................................................................................................................... 4
Figure 2 DATAMASTERS selector.......................................................................................................................................................... 5
Figure 3 Creation of a new file................................................................................................................................................................... 7
Figure 4 Creation of a new file................................................................................................................................................................... 8
Figure 5 Disc number (lu) and no. of records.......................................................................................................................................... 8
Figure 6 First page with help information................................................................................................................................................ 9
Figure 7 Definition of the fields............................................................................................................................................................... 10
Figure 8 Key‑definition............................................................................................................................................................................. 13
Figure 9 Definition of special‑keys......................................................................................................................................................... 14
Figure 10 Generation of read/write for
the reportgenerator.................................................................................................................. 14
Figure 11 Creation of the file using
automatic screen image................................................................................................................ 16
Figure 12 File maintenance with user
defined screen image................................................................................................................ 17
Figure 13 Entering the fields..................................................................................................................................................................... 18
Figure 14 Activating the help‑function................................................................................................................................................... 19
Figure 15 Searching using secondaty
index........................................................................................................................................... 20
Figure 16 Specification of a
fieldnumber sequence............................................................................................................................... 21
Figure 17 Screen image with field‑checks............................................................................................................................................... 22
Figure 18 Tastaturbelegung DATAMASTER....................................................................................................................................... 23
Figure 19 SUPERINDEX search................................................................................................................................................................ 24
Figure 20 Selection of fields by
search.................................................................................................................................................... 25
Figure 21 Selecting DATAMASTERs print
functions......................................................................................................................... 26
Figure 22 One record on each page......................................................................................................................................................... 27
Figure 23 One record on each line
(list)................................................................................................................................................... 28
Figure 24 Definition of a new report........................................................................................................................................................ 28
Figure 25 Example of printout from the
reportgenerator....................................................................................................................... 29
Figure 26 File maintenance with check‑codes........................................................................................................................................ 30
Figure 27 Definition of check on code‑fields.......................................................................................................................................... 30
Figure 28 Selection of file.......................................................................................................................................................................... 31
Figure 29 Selection of a field..................................................................................................................................................................... 31
Figure 30 Entering of the legal ranges..................................................................................................................................................... 32
Figure 31 The help‑function for
check‑code fields................................................................................................................................ 33
Figure 32 Reference to a secondary
file.................................................................................................................................................. 35
Figure 33 File maintenance with user
defined screen............................................................................................................................ 37
Figure 34 Definition of a new screen
image............................................................................................................................................ 37
Figure 35 Building the screen image........................................................................................................................................................ 38
Figure 36 Help‑function by screen
image definition............................................................................................................................. 39
Figure 37 MODE 0 displays the field
numbers....................................................................................................................................... 40
Figure 38 Copy screen images.................................................................................................................................................................. 41
Figure 39 Deletion of a screen image....................................................................................................................................................... 41
Figure 40 Printout of a file
definition....................................................................................................................................................... 45
Figure 41 Deletion of a file......................................................................................................................................................................... 46
Keyword index
Checks............................. 6, 7, 17,
21, 22, 30, 31, 33, 34, 36, 44
CLEANUP........................................................................... 9,
43
Cost.......................... 10,
13, 16‑22, 24, 25, 27‑31, 33, 37‑40, 45
DATAMASTER................... 1,
4‑16, 19, 22‑26, 28‑31, 34, 35,
42, 43, 45
DL............................................................................................. 40
DMREAD................................................................................ 29
DRN..................................................................................... 4,
45
ESCape.................................................................................... 25
FND.......................................................................................... 15
Format.......................................... 6,
9‑11, 13, 14, 22, 23, 42, 45
IL.............................................................................................. 40
Interval.............................................................................. 33,
39
Layout............................. 5,
6, 11, 18, 20, 23, 26, 37, 39, 41, 44
LD............................................................................................. 40
LEN.......................................................................................... 45
LI.............................................................................................. 40
LPT..................................................................................... 26,
33
LU........................................................................................... 7,
8
MODE...................................................................................... 40
NIROS........................................................................................ 7
NOT........................ 5,
7‑9, 12, 13, 16, 17, 20‑22, 24‑26, 29, 32,
34‑36, 38, 39, 40‑45
Partition............................................................................... 7,
24
Password........................................................................... 29,
42
POS..................................................................................... 38‑40
Search................................................................ 5,
20, 21, 24, 25
Status............................................. 17,
18, 20, 23, 30‑32, 35, 38
STOP.................................................................................. 26,
27
SYSMOD................................................................................... 7