UNIX versions of MAGEC as of release 2.6; it is planned for inclusion into the mainframe versions in a future (cont.)
release.
To define and use a compressed file :
On the DCL definition screen
specify MAGCMPRS access method.
specify fixed-length (F) mode.
In programs
read and write the records as if they were fixed-length.
When loading the file
use MAGINIT to initialize the file before loading records
use either an online program, or a batch program you have written thatcalls the MAGEC I/O module.
The mainframe MAGEC system will accept the MAGCMPRS specification as an access method, but will treat it as equivalent to VSAM--records will be store in their full size, uncompressed.
# 
Appendix A -- Error Codes and Messages
## 
CICS Abend Codes
In testing and using MAGEC applications you might encounter a Transaction Failure with an accompanying Abend Code. If (cont.)
there is an error in the MMP itself or in the MAGEC software then the Abend Code might be one of CICS's standard ones, (cont.)
such as ASRA or AICA. If you have attempted to execute a program that has not yet been installed then you might receive (cont.)
the APCT code. These are standard codes that are documented in IBM manuals.
MAGEC will, in certain situations, deliberately abort the task with a MAGEC-specified Abend Code. In PC MAGEC these (cont.)
codes are displayed on the top line of the screen, much as they are in CICS. Most of the conditions which will cause (cont.)
MAGEC to do this regard database or related problems. The MAGEC Abend Codes which you might encounter (cont.)
are:
**
DBGM
**
A Getmain command has failed (MAGECCP)
**
DBVS
**
A fatal VSAM return code was received (possible incorrect definition to TP monitor)
The following Abend Codes consist of the prefix "DB" plus a two-digit number. These two-digit numbers are consistent with the error return codes placed into the MAGECIO Request area.
**
DB01
**
Invalid I/O request attempted
**
DB02
**
No such file defined
**
DB03
**
No such key name defined (path)
**
DB04
**
Invalid Record ID
**
DB05
**
File is Closed (or Open Failure)
**
DB06
**
File Opened Read-Only, Update attempted
**
DB07
**
File is Full, cannot add records
**
DB08
**
Index is Full
**
DB09
**
Prerequisite for this command not met
**
DB10
**
Attempt to add Duplicate record
**
DB11
**
Attempt to alter Primary Key Value in record
**
DB12
**
Internal record problem
**
DB13
**
Internal record problem
**
DB14
**
No Record Found, or End of List
**
DB16
**
Exclusive Control Interlock -or- Record updated by another task
**
DB17
**
Hardware Failure or File or Index Corrupted
**
DB22
**
Element not defined
**
DB23
**
Security violation
**
DB24
**
Too many exclusive controls
**
DB30
**
Bad Command for file
**
DB35
**
Open/Close failure
**
DB36
**
Database not Open
**
DB81
**
Error retrieving repository definitions for file (PC)
**
DB82
**
Error retrieving repository definitions for file (PC)
**
DB83
**
Error retrieving repository definitions for file (PC)
**
DB8E
**
No Element record found for Data Class
**
DB8F
**
Table overflow - internal KYF/ELT table
**
DB90
**
Unsupported command
**
DB92
**
Commit/Rollback failed
**
DB93
**
Inconsistent Element/Key Name
**
DB94
**
Unknown access method
**
DB95
**
Invalid Element List (not terminated by Spaces)
**
DB96
**
Too many Exclusive Control requests
**
DB97
**
Attempt to Update an Audit-Stamp
**
DB98
**
No Exclusive Control Data (MAGECIO)
**
DB99
**
ELT or KYF definition not found (MAGECIO)
**
DB9G
**
Incorrect Gateway for file (TCP/IP)
**
DB9H
**
MAGEC Host not responding (TCP/IP)
**
DB9I
**
MGCLIENT not installed / inaccessible (TCP/IP)
**
DBCE
**
Critical file Error
**
DBCL
**
Bad concurrent load
**
DBCM
**

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