This diagram illustrates the logical flow of the MAGEC RAD SEE function, which is a display-only maintenance function used to look up and display an existing record on the screen. An important note before we begin: the SEE function has NO CONTINUATION-MODE. That means every transaction processed by this function is treated as a brand-new request. However, the SEE function can serve as the NEW-TRANSACTION-MODE entry point for other functions, such as NXT, DUP, CHG, or DEL. Processing begins at the top of the diagram with the COBOL paragraph AA100-CHECK-FUNCTION, where the very first insertion point, percent-PREINIT, is encountered. This is the earliest point at which a developer can intercept execution. It runs for every transaction and every function. Next, control passes to paragraph BA100-INIT-STORAGE, which contains the percent-INIT insertion point. Here, the program initializes its working storage areas. This runs for all maintenance functions. From there, the program enters paragraph AAM200-MAINTENANCE-MAINLINE, where the percent-PFKEYM insertion point is processed. This is the top of the maintenance mainline logic and handles PF key detection, such as PF7, PF8, PF1, PF2, PF11, PF16, and PF17. The program then moves to paragraph BA210-MAINT-SCREEN, which houses the percent-INITATB insertion point. Here, screen attributes are initialized and can be overridden by the developer. Next is paragraph BA400-NORMALIZE-MAINT-KEY, containing the percent-NORMKEY insertion point. The key value entered by the operator in the SKEY field is normalized — that is, reformatted and validated — at this step. If the key is INVALID, processing branches to the right side of the diagram. Control goes to paragraph BB100-BLANK-SCREEN, which contains the percent-BLNKSCR insertion point. The screen is blanked, then percent-SNDSCRN in paragraph AA800-SEND-SCREEN is executed to send the screen back to the operator, followed by percent-GOBACK in paragraph AA900-GOBACK to end the task. If the key is valid, processing continues downward to paragraph AAM410-READ-BY-KEY, which contains the percent-REDKY insertion point. This is where the primary data class record is read from the file using the normalized key value. If the record is NOT FOUND, the flow again branches right to the percent-BLNKSCR, percent-SNDSCRN, and percent-GOBACK sequence described above. If the record IS FOUND — the REC-FOUND path — processing continues downward to paragraph JA100-LOGICAL-JOIN, containing the percent-JOIN insertion point. This is where secondary files or derived fields are logically joined to the primary record, building the complete logical record for display. From percent-JOIN, the program flows to paragraph BB200-FILL-SCREEN, which contains the percent-COMP insertion point. Here, all database fields are moved to the screen fields for display. The developer can use percent-COMP to make last-minute adjustments to what the operator sees. After percent-COMP, both the REC-FOUND path and the NOT-FOUND or INVALID-KEY paths converge at paragraph AA800-SEND-SCREEN, percent-SNDSCRN, and finally AA900-GOBACK, percent-GOBACK. To summarize the two main paths through the SEE function: Path one: valid key, record found — PREINIT, INIT, PFKEYM, INITATB, NORMKEY, REDKY, JOIN, COMP, SNDSCRN, GOBACK. Path two: invalid key or record not found — PREINIT, INIT, PFKEYM, INITATB, NORMKEY, BLNKSCR, SNDSCRN, GOBACK. The SEE function is a display-only (inquiry) function. It has NO CONTINUATION-MODE — every invocation is a NEW-TRANSACTION. It may serve as the NEW-TRANSACTION-MODE entry point for functions such as NXT, DUP, CHG, and DEL, which are the natural follow-on actions from viewing a record with SEE. The nine standard MAGEC function codes are: xxxADD, xxxCHG, xxxDEL, xxxSEE, xxxNXT, xxxDUP, xxxSCN, xxxFND, xxxLOC. This diagram covers: xxxSEE. Earliest intercept point for all functions and all modes. Executed before initialization of VARIABLE-STORAGE and before TEST-KEY and TEST-FUNCT are set. Useful for DL/1 PCB scheduling, SQL CONNECT, or altering the key delimiter character. Cannot reference 88-level function-code conditions (ADD-FUNCTION, BROWS-FUNCTION, etc.) without first moving SFUNCT to TEST-FUNCT. The Mask may not yet be initialized; check TWA-MSK-ID before referencing screen fields. Executed early in initialization for all MAINT-FUNCTIONs. VARIABLE-STORAGE is set to LOW-VALUES just before this code runs. Use to initialize custom work fields, especially COMP-3 numerics that must be zeroed to avoid Data Exception errors. Avoid referencing screen fields other than SFUNCT, SKEY, SCOMPL, and SERRMSG. The proper Mask may not yet be formatted. Top of the maintenance mainline. Default code handles PF7/PF8 (browse navigation), PF4 (transfer to LOC), PF1/PF2 (help), PF11 (help index), PF16/PF17 (copy/paste), and cursor-movement detection for CHG intent. PA1, PA2, CLEAR, PF15, and PF13 have predefined MAGEC meanings. SKEY is already moved to TEST-KEY; changes must be made to both. Screen may not yet be formatted with THIS-PGMS-MSK. Inserted at the very end of the Attribute Initialization routine, before BA299-EXIT. Allows developer to override default 3270 attribute values based on Function Code, Operator ID, or any other criteria. Can also alter screen field contents for variable headings. Do not reference file Data Items — I/O has not yet occurred. Exit with GO TO BA299-EXIT or fall through. Do not reference Browse screen (MSK652) fields here. Executed after the standard key editing and reformatting. The fully formatted key value is in FILE-KEY, ready to be moved to NORMALIZED-KEY. Developer can add custom key edits or massage the key value (e.g., add a prefix based on Terminal ID or Operator ID). To signal an error, GO TO BA480-BAD-KEY. Either GO TO BA480-BAD-KEY or fall through; do not GO TO BA499-EXIT without NORMALIZED-KEY being properly set. If doing I/O here, save TWA-DB-REQUEST in TWA-DB-REQ-SAV. MAINT-only — do not confuse with %NKLOC (for Browse functions). Reads the primary Data Class record using NORMALIZED-KEY via the MAGEC I/O module (FSTAT, then REDKY command). After a successful read, PERFORMS JA100-LOGICAL-JOIN. Also saves the Audit-Stamp for later comparison in %RDUKY. Exit via GO TO AAM440-TEST-RETURN-CODE or fall through. If doing non-MAGEC I/O, set TWA-DB-RETURN-CODE appropriately so the REC-FOUND / NOT-FOUND conditions work correctly. Inserted at the end of the blank-screen routine, after all screen variables are set to underscores. Executed on INVALID-KEY FORMAT and on NOT-FOUND. Developer can initialize selected screen fields to values other than underscores, or move values based on the key entry (e.g., reading a related file for context data). Only executed in NEW-TRANSACTION phase (and on INVALID KEY). Cannot reference Browse Mask (MSK652) fields. For logic needed in multiple contexts, place it in %SUBRTNM and PERFORM from %BLNKSCR and other insertion points. > Executed after each standard READ of the primary Data Class. Reads secondary files or computes derived fields to build the full Logical Record. Automatic Logical Join generates code here automatically. TWA-DB-REQUEST is saved/restored by the MMP before PERFORM-ing this routine. Executed for both MAINT and BROWSE functions; test IF (MAINT-FUNCTION) or IF (BROWS-FUNCTION) before referencing screen fields. Exit via GO TO JA900-RETURN (not JA999-EXIT). Inserted at the end of BB200-FILL-SCREEN, after all generated MOVEs from database fields to screen fields, just before BB299-EXIT. Executed in NEW-TRANSACTION-MODE of Maint functions to move data to the screen. Developer can translate codes to readable descriptions, set 3270 color/highlight attributes, or move additional data to SERRMSG. Only executed for MAINT functions; cannot reference MSK652 fields. Data in SERRMSG is display-only and will be overlaid if MAGEC needs to place error messages there. For numeric screen fields, MOVE to both the -N (numeric) and -ED (edit pattern) sub-fields to stay consistent with MAGEC conventions. Executed just before the MMP returns to MAGECCP, which will send the screen and terminate the task (or fetch another function). Last opportunity to put finishing touches on the screen before the operator sees it. Runs for both MAINT and BROWSE functions. Exit via GO TO AA900-GOBACK or fall through. Test TWA-MSK-ID before referencing non-standard screen fields; this point is reached for both Maint and Browse functions. If SKEY is altered, also update TWA-LAST-KEY. Absolutely the last point in the logical flow for all functions, both MAINT and BROWSE. Last opportunity to insert logic before the program issues its GOBACK. Can be used to TERMINATE a PCB (e.g., for IMS). This is the logical end of processing. If referencing screen data, first interrogate which Mask is initialized.