SYNC format |
Top Previous Next |
|
With the store and memories of data about the SYNC format a data bank is demanded in the background. In the data bank tables must exist:
Data bank table AMFMTNR
PURPOSE Management In / FM transaction numbers. The table AMFMTNR is project-covering. It must be put on in the ORACLE data bank. With every store of a plan this number is raised by one.
DATA MANAGEMENT Entries occur exclusively through the system.
ACCESS TERMS INSERT, UPDATE and SELECT authorisation for users of the type "USER". For users of the type "PROJECT" only one SELECT authorisation is allowed.
ATTRIBUTES AM_DATENBANK Name nnn of the subdirectory [DBB.nnn] in which the plans (files are stored by the type *.DBB).
AREA RELATION Name of the plan for which the last transaction number was determined. The file name of the *.DBB file is put down without file type name".DBB".
LETZTE_TRANSAKTIONSNUMMER The last transaction number awarded for this area relation.
EXAMPLE
The plan "5686078. DBB", sheet type 185, becomes or ""was worked on by the transaction with the number "9". The plan "3593896. DBB", sheet type 140, becomes or ""was worked on by the transaction with the number "1".
Data bank table GBRLOCK
PURPOSE Management of the locking entries For every 2000/albatross transaction GRADIS an entry is carried out by the system in the table. If the transaction is concluded successfully, the system extinguishes the entry. If the transaction cannot be finished successfully, the entry continues and is used with the following (automatic) Recovery.
DATA MANAGEMENT Entries occur exclusively through the system.
ACCESS TERMS INSERT, UPDATES, DELETE-and SELECT authorisation for users of the type "USER". For users of the type "PROJECT" only one SELECT authorisation is allowed.
ATTRIBUTES AM_DATENBANK Name nnn of the subdirectory [150.nnn] in which the area relations (files are stored by the type *.DBB).
AREA RELATION Name of the area relation for which the locking entry is valid in the GBRLOCK. The file name of the *.DBB file is put down without file type name".DBB".
AMFM_TRANSAKTIONSNUMMER Number of the transaction to which the locking entry refers. This transaction number becomes for every area relation separately hochgezählt (see table AMFMTNR).
FM_BENUTZERNAME Name of the user of the type the "USER" whose 2000/albatross use GRADIS has generated the entry in the GBRLOCK.
AM_WORKFILE_NR The name of the GRADIS-Workfiles (AM-transaction data bank) which is assigned to the work station of the user.
DATE Date of the locking entry.
AMFM_TRANSAKTIONSSTATUS Tip for Recovery functions of the system. It mean: -1: Area relation closed, but not loaded 1: Area relation closed and in AMTADB loaded
Functions: LOA/file open: The function puts down a locking entry (AMFM_TRANSAKTIONSSTATUS =-1); she puts the AMFM_TRANSAKTIONSSTATUS on '1', as soon as the *.DBB file is transferred into the AM-transaction data bank. Extinguishing of the plan from the field of work: Extinguishes the locking entry, as soon as the protection of the AM-transaction data bank is concluded in the *.DBB archive successfully.
LIMIT VALUES The number of the entries in GBRLOCK is not limited.
EXAMPLE
The area relation of the file [150.185] 5686078. DBB should be worked on in the AM-transaction data bank (Workfile) WF1 by the user USER1; it was already closed for other users, but was been transferred not yet into the AM-transaction data bank.
The area relation of the file [150.140] 3593896. DBB is worked on topically in the AM-transaction data bank WF5 by the user USER2; it is closed for other users, is transferred into the AM-transaction data bank and possibly already worked on.
Data bank table PROUSER
PURPOSE Definition of the 2000/albatross users GRADIS of the type "USER" for the realisation of the data protection.
DATA MANAGEMENT Entries occur through the user "ALBATROSS"
ACCESS TERMS The user "ALBATROSS" must have INSERT, UPDATES, DELETE-and SELECT-privileges on PROUSER. For users of the type "PROJECT" only one SELECT authorisation is allowed.
ATTRIBUTES FM_BENUTZERNAME The user name of the user of the type "USER", the 2000/ALBATROSS GRADIS - uses carries out. Max Länge: 30 signs
PROJECT NAME Name of the project which the FM user works on. Worked on a user several projects, is necessary for every project an entry. Max Länge: 30 signs
F_OWNERM User name of the user of the type "PROJECT" which is responsible for the project relations of the project this puts on and transmits access authorisations to the end users. Max Länge: 30 signs
SECTION NAME Name of the thematic area to which the project belongs (e.g., topography, stream, gas, water, district heating, canal, etc.). This attribute is evaluated not by GRADIS 2000 / ALBATROSS, but serves the information of the project person responsible. Max Länge: 15 signs
AM_DATENBANK Name nnn of the subdirectory [150.nnn] in which the area relations (files are put into archives by the type *.DBB). Max Länge: 3 figures
ARCHIV_DEVICE Logical name of the Devices on which the area relations (files are put into archives by the type *.DBB), e.g., AR0. Max Länge: 3 signs
TEMPORAER_DEVICE Logical name of the Devices on which the contents of the AM-transaction data bank are protected before In / FM synchronisation temporarily, e.g., AR1. Max Länge: 3 signs
ISA_TABELLE Name of the substitute value table which steers the ISA generation (see moreover: Substitute value table). The name of the substitute value table is freely eligible for every project and is fixed here. Max Länge: 30 signs
FUNCTIONS IS1: The name of the substitute value table (ISA_Tabelle) is determined.
LIMIT VALUES The number of the entries in PROUSER is not limited.
EXAMPLE
The user "SG711 of" the type "USER" is entitled, by the user "ABT71 of" the type "PROJECT" to the project "CONTINUANCE PLAN" area relations from the archive AR0: [150.140] *.DBB to work on. For the substitute value production the ORACLE relation "ISATAB" is used. The interprotection occurs in the Directory AR1: [150.140].
Data bank table GBRMOD
PURPOSE Protocol table concluded In / FM transactions The table contain the history In / of FM fish oil Actions
DATA MANAGEMENT Entries occur exclusively through the system.
ACCESS TERMS INSERT and SELECT authorisation for users of the type "USER". For users of the type "PROJECT" only one SELECT authorisation is allowed.
ATTRIBUTES AM_DATENBANK Name nnn of the subdirectory [150.nnn] in which the area relations (files are stored by the type *.DBB).
AREA RELATION Name of the area relation (file name of the *.DBB file without file type name".DBB").
AMFM_TRANSAKTIONSNUMMER Number of the transaction.
FM_BENUTZERNAME Name of the user of the type "USER", of that GRADIS 2000/albatross use the transaction has carried out.
AM_WORKFILE_NR The name of the GRADIS-Workfiles (AM Transaktions datenbank) which is assigned to the work station of the user.
DATE Date of the registration.
FUNCTIONS BSN: If the table does not exist, an error message occurs. ETR: The function generates an entry in the GBRMOD, as soon as a transaction was finished successfully.
LIMIT VALUES The number of the entries in GBRMOD is not limited.
EXAMPLE
TIPS: (1) Every now and then should be checked the GBRMOD on not more necessary entries.
Data bank table RELTAB
PURPOSE Mutual allocation of object types GRADIS and ORACLE relations.
DATA MANAGEMENT Entries occur exclusively through the project person responsible.
ACCESS TERMS SELECT authorisation for users of the type "USER".
ATTRIBUTES AM_RELATIONSNAME For every AM or In / FM relation is carried out exactly one entry in RELTAB. In the logical data structure of the project everybody is assigned In / FM relation exactly one AM-ouch and exactly one FM-relation name. Here the AM-relation name is to be put down. Max Länge: 4 figures
AM_RELATIONSGRUPPE Description of the affiliation of the AM relation to a group within a section; serves as a selection help. If it concerns a pure AM relation, ""is to be given to 0". With FM or In / FM relations any affiliation of relations to relation groups can be fixed by the project person responsible. Max Länge: 4 figures
FM_RELATIONSNAME For every FM or In / FM relation is carried out exactly one entry in RELTAB. In the logical data structure of the project everybody is assigned In / FM relation exactly one AM-ouch and exactly one FM-relation name. Here the FM-relation name is to be put down. Max Länge: 30 signs.
ATTRIBUTNAME_ISA A number unequivocal in the whole data bank (substitute value) is assigned with his production to every object one In / FM relation to the identification by a 2000/albatross function GRADIS. The name of this attribute can be fixed for everybody In / FM object type individually. Max Länge: 30 signs.
ATTRIBUTNAME_GBR The name of the area relation (*.DBB file) is stored with everybody In / FM object in the ORACLE relation. The attribute name can be chosen arbitrarily and is to be put down here. N.: It is obvious to fix a uniform attribute name about everybody In / FM relations. Max Länge: 30 signs.
GENERIERUNG_ISA For the generation of the substitute value (ISA value) must be fixed in which kind the value is to be calculated. In the Default settings a running number is generated by high-level count. In this case the entry "DEFLT" is to be carried out. Max Länge: 6 signs.
SPECIFICATION Concept definition for the name of the object type. Max Länge: 45 signs.
FUNCTIONS BSN: If the table does not exist, an error message occurs. ETR: With the synchronisation become the registrations evaluated. UVA: The FM-relation name of an object is determined. LIMIT VALUES: The number of the entries in RELTAB is limited to 600.
EXAMPLE
The object type "Advertising pillars" is an AM-object type and has the AM-relation name "380". The object type "Transformer arrangements 110/20 KV" is one In / FM object type of the group "2000" with the AM-relation name "2005" and the FM-relation name "TRANSFORMER ARRANGEMENTS"; his surrogate has the name "ISA", the attribute for the Bezeichnug of the area relation is called "BLS". The substitute value (ISA value) is determined defaultmäßig.
TIPS (1) The registrations in RELTAB must be acceptable with the relation definitions ORACLE. (2) If the AM-relation names of AM-object types (AM_RELATIONSGRUPPE = "0")<> ""are used with others In / FM object type (AM_RELATIONSGRUPPE <>"0") at the same time as additional selection keys, here these AM-object types may not be put down!
Data bank table GOSTAB
PURPOSE Mutual allocation of object types GRADIS and allowed selection keys. To every object can be assigned except the AM-relation name up to five other AM-selection keys. By the entries in the GOSTAB it is fixed which selection keys are admitted in objects. Exactly one entry is necessary for every admitted selection key in GOSTAB.
DATA MANAGEMENT Entries occur exclusively through the project person responsible.
ACCESS TERMS SELECT authorisation for users of the type "USER".
ATTRIBUTES AM_RELATIONSNAME AM-relation name of the object type for which the selection key is admitted.
AM_SELEKTIONSSCHLUESSEL Admitted selection key.
EXAMPLE
Description: For the relation with the AM-relation name "1830" maximum two selection keys """"are admitted in 2830 and/or "3830". For the relation with the AM-relation name "1840" maximum three selection keys become "in 2840", """"admitted in 3840 and/or "4840".
Data bank table AMFMDD
PURPOSE Central IN / FM - data dictionary
DATA MANAGEMENT Entries occur exclusively through the project person responsible.
ACCESS TERMS INSERT, UPDATES, DELETE-and SELECT-privileges for users of the type "PROJECT". SELECT privilege for users of the type "USER"
ATTRIBUTES FM_RELATIONSNAME The FM-relation name for which the attribute is defined. Max Länge: 30 signs.
FM_ATTRIBUTNAME FM-attribute name for the defined attribute Max Länge: 30 signs.
AM_ATTRIBUTNAME The AM-attribute name belonging to the FM-attribute name for the defined attribute Max Länge: 3 signs.
AM_EINGABE_INTERAKTIV Definition about the admissibility of the attribute value input from the graphic work station. It mean:
J: yes, interactive input permits from the graphic terminal N: no, interactive input from the graphic terminal forbade.
The interactive input is to be prohibited for all attributes whose value is determined by function from a menu, e.g., with
•Production of the value, e.g., by calculation (user function); •Takeover from an authoritative table (e.g., by the 2000/albatross function GRADIS RT1); •Takeover of other objects (e.g., by the 2000/albatross function GRADIS UVA); •Takeover from system variables (e.g., AREA RELATION)
Length: 1 sign
FM_EINGABE_INTERAKTIV Definition about the admissibility of the attribute value input from the alphameric terminal. It mean: J: yes, interactive input permits from the alphameric terminal N: no, interactive input from the alphameric terminal forbade. The interactive input is to be prohibited for all attributes whose value is determined by function from a use, e.g., with
•Production of the value, e.g., by calculation •Takeover from an authoritative table •Takeover of other objects •Takeover from system variables (e.g., AREA RELATION)
Length: 1 sign
ATTRIBUTE CLASS If FM of data serves as a selection help at the announcement of an identified object. It mean:
G: Geographic attribute L: Logical attribute T: Technical attribute Z: Access attribute (shiningly): No allocation
Length: 1 sign
AMFM_STATUS Defines the hybrid status of an attribute. It mean:
A: AM attribute; the attribute has no representation in FM of data bank F: FM attribute; the attribute has no representation in the AM data bank H: IN / FM - (hybrid) attribute; the attribute is represented in the AM data bank as well as in the FM data bank. B: For the attribute ISA and BLS R: FM-leading attribute; the attribute is represented in the AM data bank as well as in the FM data bank, is led by the FM data bank. Changes in these attributes in the AM data bank become überschieben. O: on both sides controlled attribute. The attribute is represented in the AM data bank as well as in the FM data bank. The attributes are balanced with the store of the plan with the FM data bank reading, with the securing of the plan the attributes are written in the FM data bank. Changing programmes on the FM page must use the locking mechanism about the GBRLOCK table. V: Virtual attribute, generates entries in a 2nd data bank table.
Length: 1 sign
ATTRIBUTE TYPE Data type of the attribute. It mean:
I: integers C: CHAR F: Floating point figures
Length: 1 sign.
ATTRIBUTE-LENGTH Max Länge: 4 figures.
PRUEFMODUS Kind with the input of attribute values plausibility check to be carried out. It mean:
0: with Character attributes length check, no other check. 1: Check whether one value different by the blank exists. 2: how check 1, in addition, examination whether the attribute value is between MINWERT and MAXWERT or like the DEFAULTWERT. This check is carried out only for figures. 3: how 2., in addition, ZERO is permitted. 4: Check about authoritative table; the attribute value must be in the authoritative table. Implemented in Moskito any more, is not realised about Datenbankconstraint.
Length: 1 figure.
DEFAULTWERT Default for the attribute value. Max Länge: 20 signs.
MIN_WERT The smallest allowed attribute value (sensibly with numerical attributes with to non-discreet value areas) Max Länge: 20 signs.
MAX_WERT The biggest allowed attribute value (sensibly with numerical attributes with to non-discreet value areas) Max Länge: 20 signs.
FUNCTIONS BSN: If the table does not exist, an error message occurs. ETR: The check whether input is permitted (AM_EINGABE_INTERAKTIV, FM_EINGABE_INTERAKTIV); Inquiry of FM Relations name and FM attribute name; Compatibility and plausibility check; UR1: The check whether input is permitted (AM_EINGABE_INTERAKTIV, FM_EINGABE_INTERAKTIV); URN: The check whether input is permitted (AM_EINGABE_INTERAKTIV, FM_EINGABE_INTERAKTIV); RG1: Inquiry FM_ATTRIBUTNAME on account of the ATTRIBUTE CLASS
TIPS The registrations in the AMFMDD must be acceptable with the relation definitions ORACLE.
Remarks
The SYNC format and his documentation is based on the programme ALBATROSS of the company IFS/FIELD KRE
Example
Table formats
|