**<br />No dynamic storage<br />**<br />DBPK<br />**<br />Prime Key missing<br />**<br />DBTO<br />**<br />Table Load timeout<br />**<br />DBTS<br />**<br />No more table space<br />**<br />DB1S<br />**<br />Invalid command against a sequential file<br />**<br />DBRL<br />**<br />Incorrect record length (LRECL)<br />**<br />MUxx<br />**<br />MAGEC User-requested abend (via ABEND command to MAGEC I/O)<br />**<br />Note<br />**<br />The CICS abend codes are normally constructed using the standard MAGECIO return codes prefixed by "DB".<br />## <br />Error Messages<br />MAGEC or the MAGEC-generated MMP's might occasionally issue an error message that is displayed in either SCOMPL (top (cont.)<br />line of screen) or SERRMSG (bottom lines of screen) because they have detected an error associated with the database or (cont.)<br />files. This section will list the messages possible and suggested corrective actions where (cont.)<br />appropriate.<br />TWA area clobbered by I/O<br />The MMP has probably read (into TWA-DB-DATA) more data than is defined in the copybook(s) or data definition(s). The (cont.)<br />file data has overlayed the VARIABLE-STORAGE area that is below TWA-DB-DATA in the TWA.<br />io ERROR has occurred<br />The MMP has issued an UPDAT, or DELET command for a record which it (is supposed to have) read with intent to update (cont.)<br />and the specified record can not now be found. This might be a coding error in customization logic which destroys the (cont.)<br />TWA-DB-REQ-SAV area in the TWA or it may be a legitimate I/O error or the specified record may have been deleted from (cont.)<br />another region/partition/machine.<br />DUP RECORD Pending Delete<br />The MMP has tried to add a record having a key value that is a duplicate of the key value for a record which has been (cont.)<br />"pseudodeleted" and has not yet been purged from the file. This error should occur only on Data Classes having Audit (cont.)<br />Stamps specified. If it occurs on other Data Classes then it might mean that an actual duplicate record was added by (cont.)<br />another task while the operator was keying onto the screen and therefore this message should be interpreted as meaning (cont.)<br />the same thing as DUPLICATE RECORD ON FILE in that case.<br />Error retrieving MSKnnn -or- MSK652<br />The MMP issued a command to read its Mask initialization record from the MSK file and the command failed. The contents (cont.)<br />of the field TWA-DB-RETURN-CODE will indicate the type of error, see Abend Codes above.<br />MMPnnn illegally entered<br />The MMP was entered either from the MAGEC Control Program or from another MMP via FTHFUNCT command and it detected that (cont.)<br />the Function Code in SFUNCT (top line of screen) is not one of its valid Functions. It may be that the wrong MMP number (cont.)<br />is specified for that Function on the FCD file or that the %FUNCT customization logic is wrong for this (cont.)<br />MMP.<br />MSKnnn Altered - ReCompile MMPnnn<br />The MMP has detected that its Mask has been changed (that MSKCREAT has been run for it) and that the version number on (cont.)<br />the MSK file record for the Mask does not match the version number in the Mask copybook. Recompile (MMPCREAT) the MMP (cont.)<br />and be sure the TP monitor recognizes that there is a NEW COPY of the program then retry. You may check the version (cont.)<br />numbers by using the MSKSEE nnn Function and comparing the number shown against the version number shown in the (cont.)<br />copybook. You may see the copybook using the LBRSEE MSKnnn-C//002 Function.<br />ERR91A-Warning - Bad Data on File<br />The MMP was generated (MMPCREAT) with the VERIFY option and it has detected non-numeric data in numeric fields of the (cont.)<br />file. The bad fields will appear as asterisks (*) on the screen and may be corrected using the MMP's ...CHG Function if (cont.)<br />desired.<br />attempt to FALL THRU program<br />The MMP contains a coding error in the customization logic that is causing it to "fall through" the end of the program. (cont.)<br />Most likely cause is an incorrect PERFORM THRU or GO TO. Check the customization algorithms for such coding (cont.)<br />errors.<br />WARNING - MAL LOG FILE IS FULL<br />The Activity Logging feature is generated in the MAGEC nucleus (TIMACCT = YES in ALAPARMS) and the MAL file has no more (cont.)<br />room to add records. Execute the MALUTIL program to extract the statistics to a backup tape and then either increase (cont.)<br />the file size or "clear" it by deleting all the records from it. This condition will not prevent the online Functions (cont.)<br />from processing but will cause the Activity Log data to be incomplete.<br />WARNING - LOGGING ERRnn - MAL FILE<br />An I/O error (other than File Full) was detected in reading, adding to, or updating on the MAL file. The Error Return (cont.)<br />Code will be in the TWA field and will also be displayed in this message, see Abend Codes above. This condition will (cont.)<br />not prevent online processing but will cause the statistics to be incomplete.<br />DATA UPDATED BY ANOTHER TASK<br />The MMP is attempting to update a record(s) of a Data Class which has Audit Stamp support generated (on the DCL file (cont.)<br />definition). It has detected that the Audit Stamp has been altered between the time the record was read first (and the (cont.)<br />data displayed on the screen) and the time it was read with intent to update. This probably means that an operator at (cont.)<br />another terminal (or a batch program) has updated the record and that the displayed data is possibly obsolete. This MMP (cont.)<br />will not be allowed to update the record without re-initiating the Function in order to re-display the record in its (cont.)<br />current state. The easiest way to reinitiate it is to alter the Function Code from a ...CHG to a ...SEE to re-display (cont.)<br />the data then alter it back to ...CHG.<br />PROG NOT FOUND or DISABLED ===> MMPnnn<br />MAGEC's Control Program (MAGECCP) has tried to allocate an MMP for a Function which was entered and the MMP (name (cont.)<br />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.)<br />too large for available memory. Try loading a "NEW COPY" of the MMP or recompiling it. It is also possible that the (cont.)<br />wrong MMP number is specified on the FCD file definition for that Function Code.<br /># <br />Appendix B -- Glossary of Terms<br />**LOAD<br />A special MAGEC Function Code that commands MAGEC to reload its main-memory "tables" from the Dictionary files in order (cont.)<br />to reflect any changes that might have been made. Used most often by database administrators and security (cont.)<br />officers.<br />-IFEXIST<br />A control command that is used in conjunction with Symbolic Screen Field References to render them "conditional". Often used in Business Rules.<br />-IFUNIQUE<br />A control command that is used in conjunction with -MAGECINC and renders it "conditional".<br />-MAGECINC<br />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.<br />Activity Log<br />A record of online activity by operator, terminal, and function that includes I/O, transaction, and error statistics maintained by MAGEC automatically.<br />Audit Stamp<br />A 36-byte Element used to record update statistics for a record.<br />Business Rule<br />A routine that is triggered (invoked) whenever a program updates or adds data for a specified Element. Primary purpose (cont.)<br />is to control integrity of data, including cross-field and cross-file validations.<br />Authorization Level<br />A one-digit (0 through 9) code designating a level of access authorization in the MAGEC security system. Operators have (cont.)<br />an individual authorization level in each of up to fifty Logical Applications, 0 = lowest (none), 9 = highest (cont.)<br />(deified).<br />CICS<br />A TP monitor that is a product of IBM.<br />Conditional MAGECINC<br />A source inclusion that will be ignored if the same copybook has been included elsewhere in the same program, see MAGECINC and IFUNIQUE.<br />Copybook<br />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.<br />Data Class<br />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.<br />Data Independence<br />A property of application programs that renders them insensitive to changes in the physical structure of their data; (cont.)<br />i.e. record lengths, access methods. This property is imparted upon MAGEC applications via the dictionary-driven I/O (cont.)<br />modules.<br />Data Item<br />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.<br />Datacom DB<br />A database management system that is a product of Applied Data Research.<br />DBA<br />Database administrator. A person who is responsible for managing the database resources for an organization. This (cont.)<br />person is usually a technically oriented individual who deals directly with the actual database control parameters and (cont.)<br />utilities as opposed to the more administrative person called the data administrator.<br />DBMS<br />Database Management System. A software or hardware product that is used to manage file data and simplify accesses.<br />DB/2<br />IBM's relational database that utilizes SQL.<br />DCL<br />Standard MAGEC designation for Data Class. The DCL file.<br />DD Name<br />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.<br />Displacement<br />The starting position (in the record) at which an Element or key begins, relative to 0000.<br />DIT<br />Standard MAGEC designation for Data Items. The DIT file.<br />Domain<br />A global definition that applies to data items in, potentially, many tables (files). A central definition from which individual data items can inherit specifications.<br />ELT<br />Standard MAGEC designation for Element. The ELT file.<br />Foreign Key<br />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.<br />HELP Key<br />A keyboard key, for online applications, that invokes a display of documentation pertinent to what the user is doing. (cont.)<br />MAGEC includes function-level, field-level, and error-level HELP automatically for online (cont.)<br />applications.<br />Host Variables<br />Data definitions that are included into a program for the purpose of reading into or writing from when using an SQL database management system.<br />IFUNIQUE<br />A control statement in MAGEC that is used in conjunction with the -MAGECINC control statement, rendering it "conditional".<br />KSDS<br />Keyed Sequenced Data Set. A type of VSAM file that is logically ordered via use of an index (key).<br />KYF<br />Standard MAGEC designation for key definition. The KYF file.<br />Logical Join<br />A technique for logically associating the records of one file or Data Class to the records of another without using "physical" pointers.<br />MAGECINC<br />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.<br />MAGECIO<br />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.)<br />MMP's and to handle error conditions in a standard manner. It also makes up a part of the MAGEC Security System since (cont.)<br />it accomplishes the Audit Stamping.<br />Master Key<br />The unique key value that identifies a specific record. The key by which MAGEC MMP's access the record for all maintenance Functions.<br />MBP<br />MAGEC Batch Program. A batch program generated by MAGEC from dictionary specifications.<br />MBPCREAT<br />The batch jobstream used to generate MBP's.<br />MMP<br />MAGEC Message Processor. An online program generated by MAGEC from dictionary specifications.<br />MMPCREAT<br />The batch jobstream used to generate MMP's.<br />Primary Key<br />See Master Key.<br />Pseudodelete<br />To simulate the deletion of a record by setting a "delete flag" on and then just updating the record. MAGECIO does this (cont.)<br />for Data Classes that have an Audit Stamp and for which Real Delete is set to N in the DCL file definition. MAGECIO (cont.)<br />also simulates a NOT-FOUND if a pseudodeleted record is read.<br />Referential Integrity<br />The property of a database of ensuring that all subordinate entities (i.e. invoices) have a valid controlling entity (cont.)<br />(i.e. customer) and that those relationships are not violated during ongoing database update, deletion, and addition (cont.)<br />processes.<br />Request Area<br />A fixed format area of memory into which the MMP's can move the commands and other parameters to communicate to MAGECIO (cont.)<br />(or MAGECCP) what operation is requested. TWA-DB-REQUEST, TWA-NONTP-REQUEST, and TWA-TP-REQUEST are examples of request (cont.)<br />areas.<br />SCOMPL<br /><br />next: db11.md.txt