--- title: "magref_main" original_file: "magref_main" generated: "2026-06-17 14:40:25" --- ** # Attributes ## 3270 Attributes [*](#legal) [](#MAGREF001002) The symbolic names are six characters long, each character position having a unique meaning and set of possible values: | **Character Position** | **Letter Value** | **Meaning of Letter Value** | **Entry Protection** | 1 | P | Protected | S | Skip-Protected | U | UnProtected | **Keyboard Shift** | 2A | Alpha-Numeric | N | Numeric Shift (keyboard) | **Display** | 3D | Displayable | N | Non-Displayable | **Highlighting** | 4R | Regular Intensity | H | High Intensity | **Selector Pen** | 5N | Non Selector Pen Detectable | **Modify Data Tag** | 6M | Modify Data Tag ON | F | Modify Data Tag Off Note1:** Selector Pen option discontinued by IBM and not supported by MAGEC **Note2:** Strategic Priorities: MAGEC-generated MMPs are designed to prioritize 1/ database integrity, 2/ run-time (cont.) efficiency, and 3/ operator efficiency. Thru customization, you can override that strategy virtually without limit. A (cont.) SEE Function normally does NOT set field attributes to 'Protected', so the operator CAN overtype data displayed; but (cont.) MUST overtype the function code to the CHG Function to actually update the database (if all validations pass, of (cont.) course). This eliminates an unnecessary extra transaction to re-display with 'UnProtected' attributes. (cont.) ** If you wished to make it even easier for an operator to transfer from a SEE Function to a CHG Function, you could allow them to use a PF Key instead of overtyping the function code. If you prefer to be even more sure they intended to update the data, you could set the Attribute to 'Protected' on a SEE Function, and to 'UnProtected' on an ADD, CHG, or DUP. Or, if runtime efficiency is your paramount concern, set the Modify Data Tag OFF attribute for data fields on the SEE (cont.) Function, thus reducing TP I/O overhead for inquiry-only applications. We recommend that you give it a good bit of (cont.) consideration before any such modifications. The default strategy has worked well for a long time! ## Table of Attributes [](#MAGREF001000) [](#MAGREF002000) | **Symbolic Name (in MSKDEF)** | **Cobol Name (in MAGEC003) ** | **Actual Code Value** | UANRNF | ATUANRNF | < | UADRNF | ATUADRNF | b (blank) | UADHNF | ATUADHNF | H | UANRNM | ATUANRNM | ( | UADHNF | ATUADHNF | H | UADRNM | ATUADRNM | A | UADHNM | ATUADHNM | I | UNDRNF | ATUNDRNF | & | UNDHNF | ATUNDHNF | Q | UNDRNM | ATUNDRNM | J | UNDHNM | ATUNDHNM | R | PANRNF | ATPANRNF | % | PADRNF | ATPADRNF | - (dash) | PADHNF | ATPADHNF | Y | PANRNM | ATPANRNM | _ (underscore) | PADRNM | ATPADRNM | / | PADHNM | ATPADHNM | Z | SANRNF | ATSANRNF | + | SADRNF | ATSADRNF | 0 (zero) | SADHNF | ATSADHNF | 8 | SANRNM | ATSANRNM | ' (apostrophe) | SADRNM | ATSADRNM | 1 (one) | SADHNM | ATSADHNM | 9 # Automatic Editing ## Table of Edit Types [](#MAGREF001002) [](#MAGREF003000) | ** Alpha-Numeric Edit Types: ** | X | Miscellaneous alpha-numeric. Any characters will be accepted. Example: Company Name, or Comments, etc. | b (blank) | Default. Same as X | A | Alphabetic. Only (A - Z and b [blank]) Example: Person's Name, City Name, etc. | U | Uppercase. Any characters accepted. MAGEC converts any lowercase alpha to uppercase | T | Table Lookup. Same as U plus MAGEC looks up in a Table | W | Where to display Table description used in conjunction with a T. MAGEC moves the description of the found entry in the Table to a W field (if so specified). | ** Numeric Edit Types: ** | N | Numeric, MAGEC will pad leading zeros. | S | Numeric, MAGEC will suppress leading zeros | = | Same as S, plus trailing minus sign | Z | Numeric, leading zeros plus comma insertion | - | Same as Z, plus trailing minus sign | $ | Same as -, plus floating dollar sign | ** Date Edit Types: ** | M | MM/DD/YY (2-digit year) or MM/DD/CCYY (4-digit year) | D | DD/MM/YY (2-digit year) or DD/MM/CCYY (4-digit year) | Y | YY/MM/DD (2-digit year) or CCYY/MM/DD (4-digit year) NOTE:** MAGEC accepts any valid operator entry (depending on field Edit Type) and adjusts it to the "edited" format for the field. For instance: in a type-$ field the operator can enter:** 12345.5 - or 1,234.50 - or $1,234.50 et cetera, all of which are equivalent. # Developer Functions ## Online Developer Functions [](#MAGREF002000) [](#MAGREF004000) **PFnn / **PAnn | Simulate any PF or PA key | ALGLST mmm | List directory of Customization Algorithms for Mask mmm | ALGxxx mmm/pppppppp/etc. | Inquiry and Maintenance for Customization Algorithms | DBDITO | Hex/Character display and update of file data | DBUTIL | Hex/Character display only | DOCxxx topic name | Inquire/maintain documentation | ERRxxx eee | Inquire/maintain error messages | LBRxxx member name/modifier | Inquire/maintain library member | LBRLST 1 | List index of Library members | MMPxxx nnn | Inquire/maintain MMP definition | MSKDEF mmm | Manual screen painting | MSKDEL mmm | Delete all screen fields | MSKDUP mmm | Duplicate screen definition | MSKSEE mmm | Display generated screen | PAINT1 mmm (thru Paint7 mmm) | Automatic screen painting | SCDLST mmm | List Locate-Headings for fields | SCDCHG mmm/row/col | Change Locate-Heading for field | TBLLST ttt | List entries in a Lookup Table | TBLxxx ttt/cccc | Inquire/maintain table entries | TOCxxx ttt | Inquire/maintain Table-of-Contents for Lookup Tables | TSKLST mmm | Developer Menu + Status screen | VERZUN mmm, or nnn | Version verification for MMP, MSK, etc. | **LEGEND:** | mmm | Mask number | xxx | standard nine suffixes (ADD, CHG, etc.) | ttt | Table number | nnn | MMP number | pppppppp | Insertion Point name | nn | PF (01-24) or PA (01-03) key number | cccc | 1- thru 16-character code # PF Keys in Developer Functions ## Developer Functions PF Keys [](#MAGREF003000) [](#MAGREF005000) | ** PF Keys (general) ** | PF15 | exit MAGEC or exit Split-Screen | PF12 | return to TSKLST for this Mask # | PF9 | Swap Windows | PF2 | HELP (field-level) | PF1 | HELP (function-level) Next: https://magec.com/DOC/markdown/magref02.md.txt