DATA UPDATED BY ANOTHER TASK
The MMP is attempting to update a record(s) of a Data Class which has Audit Stamp support generated (on the DCL file (cont.)
definition). It has detected that the Audit Stamp has been altered between the time the record was read first (and the (cont.)
data displayed on the screen) and the time it was read with intent to update. This probably means that an operator at (cont.)
another terminal (or a batch program) has updated the record and that the displayed data is possibly obsolete. This MMP (cont.)
will not be allowed to update the record without re-initiating the Function in order to re-display the record in its (cont.)
current state. The easiest way to reinitiate it is to alter the Function Code from a ...CHG to a ...SEE to re-display (cont.)
the data then alter it back to ...CHG.
PROG NOT FOUND or DISABLED ===> MMPnnn
MAGEC's Control Program (MAGECCP) has tried to allocate an MMP for a Function which was entered and the MMP (name (cont.)
specified in message) was not found on the Core-Image or Load Library or the MMP is marked as being "Disabled" or it is (cont.)
too large for available memory. Try loading a "NEW COPY" of the MMP or recompiling it. It is also possible that the (cont.)
wrong MMP number is specified on the FCD file definition for that Function Code.
# Appendix B -- Glossary of Terms
**Note:** see also the [Glossary docment](glossary_main.htm) for more terms.
**LOAD
A special MAGEC Function Code that commands MAGEC to reload its main-memory "tables" from the Dictionary files in order (cont.)
to reflect any changes that might have been made. Used most often by database administrators and security (cont.)
officers.
-IFEXIST
A control command that is used in conjunction with Symbolic Screen Field References to render them "conditional". Often used in Business Rules.
-IFUNIQUE
A control command that is used in conjunction with -MAGECINC and renders it "conditional".
-MAGECINC
A control command that may be embedded in source code to cause the MMPCREAT or MBPCREAT process to "include" or "expand" another member at that point in the program.
Activity Log
A record of online activity by operator, terminal, and function that includes I/O, transaction, and error statistics maintained by MAGEC automatically.
Audit Stamp
A 36-byte Element used to record update statistics for a record.
Business Rule
A routine that is triggered (invoked) whenever a program updates or adds data for a specified Element. Primary purpose (cont.)
is to control integrity of data, including cross-field and cross-file validations.
Authorization Level
A one-digit (0 through 9) code designating a level of access authorization in the MAGEC security system. Operators have (cont.)
an individual authorization level in each of up to fifty Logical Applications, 0 = lowest (none), 9 = highest (cont.)
(deified).
CICS
A TP monitor that is a product of IBM.
Conditional MAGECINC
A source inclusion that will be ignored if the same copybook has been included elsewhere in the same program, see MAGECINC and IFUNIQUE.
Copybook
A stored source-code definition of data, either a file Element or a Mask. Stored on the MAGEC library for use in the generated MMP's.
Data Class
A logical view of a file. A collection of data items that are grouped into Elements that are grouped into a record that resides on a file.
Data Independence
A property of application programs that renders them insensitive to changes in the physical structure of their data; (cont.)
e.g. record lengths, access methods. This property is imparted upon MAGEC applications via the dictionary-driven I/O (cont.)
modules.
Data Item
The MAGEC (and Cobol) designation for a "field" of a record (Element). Data Items must be defined as belonging to an Element defined on the ELT file.
Datacom DB
A database management system that is a product of Applied Data Research.
DBA
Database administrator. A person who is responsible for managing the database resources for an organization. This (cont.)
person is usually a technically oriented individual who deals directly with the actual database control parameters and (cont.)
utilities as opposed to the more administrative person called the data administrator.
DBMS
Database Management System. A software or hardware product that is used to manage file data and simplify accesses.
DB/2
IBM's relational database that utilizes SQL.
DCL
Standard MAGEC designation for Data Class. The DCL file.
DD Name
The "data definition" name used to define a file to the operating system in the TP monitor's start-up JCL. The name specified in the OS "DD" statement or in the DOS "DLBL" statement.
Displacement
The starting position (in the record) at which an Element or key begins, relative to 0000.
DIT
Standard MAGEC designation for Data Items. The DIT file.
Domain
A global definition that applies to data items in, potentially, many tables (files). A central definition from which individual data items can inherit specifications.
ELT
Standard MAGEC designation for Element. The ELT file.
Foreign Key
A Data Item within one Data Class that is used as a key to access another, i.e: customer-number in an invoice Element used to access customer file.
HELP Key
A keyboard key, for online applications, that invokes a display of documentation pertinent to what the user is doing. (cont.)
MAGEC includes function-level, field-level, and error-level HELP automatically for online (cont.)
applications.
Host Variables
Data definitions that are included into a program for the purpose of reading into or writing from when using an SQL database management system.
IFUNIQUE
A control statement in MAGEC that is used in conjunction with the -MAGECINC control statement, rendering it "conditional".
KSDS
Keyed Sequenced Data Set. A type of VSAM file that is logically ordered via use of an index (key).
KYF
Standard MAGEC designation for key definition. The KYF file.
Logical Join
A technique for logically associating the records of one file or Data Class to the records of another without using "physical" pointers.
MAGECINC
A control statement in MAGEC that causes a copybook to be included (expanded) at the point in a program where the -MAGECINC statement is encountered.
MAGECIO
A module that is part of the MAGEC nucleus. Its primary function is to handle the file and database I/O requests of the (cont.)
MMP's and to handle error conditions in a standard manner. It also makes up a part of the MAGEC Security System since (cont.)
it accomplishes the Audit Stamping.
Master Key
The unique key value that identifies a specific record. The key by which MAGEC MMP's access the record for all maintenance Functions.
MBP
MAGEC Batch Program. A batch program generated by MAGEC from dictionary specifications.
MBPCREAT
The batch jobstream used to generate MBP's.
MMP
MAGEC Message Processor. An online program generated by MAGEC from dictionary specifications.
MMPCREAT
The batch jobstream used to generate MMP's.
Primary Key
See Master Key.
Pseudodelete
To simulate the deletion of a record by setting a "delete flag" on and then just updating the record. MAGECIO does this (cont.)
for Data Classes that have an Audit Stamp and for which Real Delete is set to N in the DCL file definition. MAGECIO (cont.)
also simulates a NOT-FOUND if a pseudodeleted record is read.
Referential Integrity
The property of a database of ensuring that all subordinate entities (e.g. invoices) have a valid controlling entity (cont.)
(e.g. customer) and that those relationships are not violated during ongoing database update, deletion, and addition (cont.)
processes.
Request Area
A fixed format area of memory into which the MMP's can move the commands and other parameters to communicate to MAGECIO (cont.)
(or MAGECCP) what operation is requested. TWA-DB-REQUEST, TWA-NONTP-REQUEST, and TWA-TP-REQUEST are examples of request (cont.)
areas.
SCOMPL
The portion of any MAGEC screen in which miscellaneous messages may be displayed, it is the rightmost half of the top line.
Secondary Key
A key for a record that is other than the Master (Primary) key and that needs not uniquely identify the record since it is used only in browse Functions in MAGEC MMP's. Alternate Index.
SERRMSG
The last three lines of any MAGEC screen. The area in which Error messages are usually displayed.
SFUNCT
The portion of the top line of any MAGEC screen in which the Function Code is entered/displayed.
SKEY
The portion of the top line of any MAGEC screen in which the key value is entered/displayed for the Function being done.
SQL
Structured Query Language. A database access language for relational databases.
Subordinate Key
See Secondary Key.
Supra
Cincom's relational database system.
TCP/IP
Transmission Control Protocol/Internet Protocol. A protocol used to communicate between networks of computers
TeraData
A database "back end machine" that is a relational SQL database system.
TP monitor
Any of the software products that is designed to support online processing against 3270-type devices and from Cobol (cont.)
applications programs in a multi-tasking environment. CICS, WESTI, or Datacom DC, etc.
TWA
Task Work Area. Main memory used by an MMP as work space and for passing data to other modules and for reading data (cont.)
into and writing from. Also used for saving data from task to task in a "pseudo-conversational" processing mode since (cont.)
it is saved and restored by the MAGEC Control Program as a service to the MMP's.
Undelete
To restore a pseudodeleted record to "undeleted" status by setting the Delete Flag in the Audit Stamp from X'FF' to blank.
Version Validation
The process of researching and comparing version numbers and creation/modification dates for all entities of an (cont.)
application to find possible sources of errors. Done using the VERZUN function of MAGEC.
VSAM
IBM's Virtual Sequential Access Method, including all its variations.
WESTI
A TP monitor that is a product of Westinghouse. No longer supported by MAGEC as of release 3.0
Workstation
A standalone computer, usually a PC, PS/2, or 9370 type machine, that is a functional replica of the main production (cont.)
system and that serves as a testing and development environment for analysts, designers, and programmers. Provides (cont.)
absolute separation of testing and production. MAGEC supports all of the workstation machines listed (cont.)
above.
# Appendix C -- Networks
Distributed Databases
MAGEC allows for installation on a network with the ability to distribute database files across multiple servers, (cont.)
physical disk drives, and logical disk drives. When MAGEC is installed you must determine on which drive the MAGEC (cont.)
reposittory files and executable (.EXE, .DLL, .BAT, .CMD, etc.) modules are to reside. Then, for each of your (cont.)
applications' database files, you must decide where they are to reside. MAGEC provides an easy way for you to specify (cont.)
where each file resides by entering the drive ID on the KYF (Key Format) panel (refer to page 11 in this (cont.)
section).
MAGEC Software suggests the following configuration for LAN installations:
1. all of the MAGEC repository files (.DAT) should be installed on the same drive on the same server.
2. all nodes should refer to that drive using the same symbolic drive letter (e.g. G:).
3. all nodes should include the SET LANDRV=G statement in their AUTOEXEC.BAT files (assuming that G: is the correct drive ID).
4. each developer's node should have a local disk drive (usually C:) that has several megabytes available for work space and has the Cobol compiler installed in the \COBOL (MicroFocus) directory.
5. the SET LCLDRV=C (assuming that C: is the corrcet drive ID) statement should be included in each node's AUTOEXEC.BAT file.
6. as new application database files are added: if they reside on the same drive as is specified in the SET LANDRV= (cont.)
parameter, the KYF definition should leave the Drive ID specification blank. If they reside elsewhere, the Drive ID (cont.)
should be specified on the KYF panel.
7. end users must have authorization via the LAN operating system to access the servers and drives on which their applications' files reside.
8. If accessing via Windows, the SET statements must be done prior to entering Windows in order to apply to sessions within Windows.
9. It is permissable for any user to have multiple MAGEC sessions via Windows concurrently. A unique "terminal ID" is (cont.)
assigned to each session. Clipboard may be used to copy data from one window to another.
Also refer to the Networks section of your *Application User's Guide* for more about networks.
# Appendix D -- Datacom DB
NonStandard Key & Element Names
MAGEC employs a standard for naming Data Classes, Keys, and Elements. Many of the features of MAGEC depend upon that (cont.)
standard. For Datacom DB users who have installed MAGEC at the time that they installed Datacom DB the MAGEC standard (cont.)
is a very useful one to follow when creating definitions into the Datacom dictionary; thus, the name Datacom knows each (cont.)
entity by is the same as the name MAGEC knows it by. This is the ideal configuration; however, for some users it is not (cont.)
possible.
MAGEC users who already had been using Datacom DB for some time prior to installing MAGEC will already have many Data (cont.)
Classes (Tables), Keys, and Elements defined to Datacom. These may not abide by the MAGEC standard. In order to provide (cont.)
compatibiliity for such situations, MAGEC allows you to specify the true Datacom name, if it is different from the (cont.)
MAGEC name, for each Key and Element.
Standard Names
The Data Class is given a 3-character name in MAGEC. Datacom DB requires that you define each table with a 3-character name. These names should be the same in MAGEC and Datacom.
The MAGEC standard requires that the Master key be named xxxK1(where xxx = the Data Class name). Subordinate Keys are (cont.)
named xxxK2, xxxK3, etc. Datacom permits you to give any 5-character name to your keys.
MAGEC requires that your Elements be named xxxnn (where xxx = the Data Class name, nn is any two characters, usually (cont.)
numerics). Further, special meaning is assigned to the Element names xxx00 and xxx99. The xxx00 name indicates a (cont.)
36-byte audit stamp Element. The xxx99 name indicates a 4-byte record descriptor word for variable-length (cont.)
records.

Next: <a href="https://magec.com/DOC/markdown/db13.md.txt">https://magec.com/DOC/markdown/db13.md.txt</a>