1.<br />Edit and Normalize the key value. If error found issue the INVALID KEY message and exit.<br />2.<br />Read file using Normalized key. If NOT-FOUND, issue NOT FOUND message and Blank screen with Underscores and exit.<br />3.<br />Save the Audit Stamp (if there is one).<br />4.<br />Fill the screen with data from the record.<br />5.<br />Issue PRESS ENTER TO DELETE message.<br />6.<br />Exit.<br />## <br />DEL Function, Continuation<br />1.<br />Edit and Normalize the key value. If error found issue the INVALID KEY message and exit.<br />2.<br />Read the record for update. If NOT-FOUND, issue NOT FOUND message and exit.<br />3.<br />Compare Audit Stamp to Saved Audit Stamp (if this Data Class has an Audit Stamp). If altered, issue UPDATED BY ANOTHER TASK message and exit.<br />4.<br />Edit for circumstances which would preclude deletion. If found, set FATAL-ERR and ERROR NUMBER and exit. This allows (cont.)<br />you to protect the Referential Integrity of your database when "parent" records are to be deleted by ensuring that no (cont.)<br />"children" will be left on file without a parent.<br />5.<br />Delete the file record.<br />6.<br />If delete was successsful, issue DATA DELETED message, otherwise issue the DB ERROR message.<br />7.<br />Exit.<br />## <br />SEE Function, New Transaction<br />1.<br />Edit and Normalize the key value. If error found issue the INVALID KEY message and exit.<br />2.<br />Read file using Normalized key. If NOT-FOUND issue NOT FOUND message and Blank screen with Underscores and exit.<br />3.<br />Save the Audit Stamp (if there is one).<br />4.<br />Fill the screen with data from the record.<br />5.<br />Exit.<br />## <br />SEE Function, Continuation<br />There is no Continuation Mode for a SEE Function; however, since the New Transaction Mode for a SEE Function is (cont.)<br />identical to the New Transaction Mode for CHG and DEL, the SEE Function can serve as the first phase for them. If the (cont.)<br />Operator changes the suffix of the Function Code from SEE to CHG or DEL then the MMP will go into Continuation Mode for (cont.)<br />the Change or Delete. This is true only if the Operator does not alter the Key Value. If the Key value is changed then (cont.)<br />the MMP will go into New Transaction Mode for the Change or Delete Function.<br />The DUP Function has no New Transaction Mode. The SEE Function serves as the New Transaction Mode for the DUP. If the (cont.)<br />Operator alters the Function Code suffix from SEE to DUP and also *does* alter the Key Value then the MMP will go into (cont.)<br />Continuation Mode for the DUP Function.<br />The NXT Function has no New Transaction Mode either. The SEE Function also serves as its New Transaction Mode. If the (cont.)<br />Operator alters the Function Code suffix from SEE to NXT and *does not* change the key value, the MMP will go into the (cont.)<br />Continuation Mode for the NXT Function. If the key value is altered, the PRIOR FUNCTION WAS NOT A SEE message will be (cont.)<br />issued.<br />## <br />NXT Function, New Transaction<br />There is no New Transaction Mode for a NXT Function. The SEE Function serves as its New Transaction Mode. The NXT (cont.)<br />Function must be preceeded by a successful SEE (not NOT-FOUND). The Operator must alter the Function Code suffix from (cont.)<br />SEE to NXT and *not alter* the key value. The MMP will then go into the Continuation Mode for the NXT Function. (cont.)<br />Pressing PF8 (page forward) or PF7 (page backward) automatically changes the Function Code suffix to (cont.)<br />NXT.<br />## <br />NXT Function, Continuation<br />1.<br />Restore the MAGECIO Request Area from the saved area so that it is the same as after the last READ was done.<br />2.<br />Set the MAGECIO command to REDNX (read next) and issue the MAGECIO Request.<br />3.<br />If NOT FOUND (end of data), move END OF DATA message and "Blank" the screen with Underscores and exit.<br />4.<br />Fill in the screen with data from the record.<br />5.<br />Save MAGECIO Request Area.<br />6.<br />Exit.<br />## <br />DUP Function, New Transaction<br />There is no New Transaction Mode for the DUP Function, the SEE Function serves as its New Transaction phase. The (cont.)<br />Operator first must do a SEE Function and must have successfully found an item (not NOT-FOUND). Then the Operator (cont.)<br />changes the Function Code to the DUP Function by altering the last three characters to "DUP" and also alters the key (cont.)<br />value to the desired new key to be added. He/She may also alter any displayed data on the screen at the same time. Then (cont.)<br />He/She presses ENTER, the resulting transaction will be a DUP Function in Continuation mode.<br />## <br />DUP Function, Continuation<br />1.<br />Internally alter the Function Code suffix to ADD.<br />2.<br />Process the transaction as an ADD Function, Continuation Mode.<br />## <br />LOC Function, New Transaction<br />1.<br />Set NUMBER-OF-RECORDS to 16.<br />2.<br />Normalize the entered key value and set the key name in the MAGECIO Request Area.<br />3.<br />Position generically (LOCKY) using the Normalized key value.<br />4.<br />If NOT-FOUND (end of data), move END OF DATA message to SCOMPL and to screen body and exit.<br />5.<br />Read first record (REDLE). If NOT-FOUND, set DB ERROR message and exit, otherwise go to Step 7 below.<br />6.<br />Read next record (REDNX), if NOT-FOUND, move END OF DATA message to SCOMPL and exit.<br />7.<br />Build a display line from record data and move into screen.<br />8.<br />If screen is full (determined by NUMBER-OF-RECORDS), move PF KEY DIRECTIONS message into SCOMPL and exit.<br />9.<br />Go back to Step 6 above.<br />## <br />LOC Function, Continuation<br />1.<br />Set NUMBER-OF-RECORDS to 16.<br />2.<br />Continue processing starting at Step 6 for New Transaction Mode above.<br />## <br />SCN Function, New Transaction<br />1.<br />Set NUMBER-OF-RECORDS to 16.<br />2.<br />If Character Mask is "virgin", issue ENTER SELECTION MASK message and force the next transaction to also be a New Transaction Mode, exit.<br />3.<br />Normalize the entered key value and set the key name in the MAGECIO Request Area.<br />4.<br />Position generically (LOCKY) using the Normalized key value.<br />5.<br />If NOT-FOUND (end of data), move END OF DATA message to SCOMPL and to screen body and exit.<br />6.<br />Read first record (REDLE). If NOT-FOUND, set DB ERROR message and exit, otherwise go to Step 9 below.<br />7.<br />If number of reads has reached the SCAN-LIMIT, simulate that the screen is full and go to Step 11 below.<br />8.<br />Read next record (REDNX), if NOT-FOUND, move END OF DATA message to SCOMPL and exit.<br />9.<br />Build display line from record data and compare to Selection Mask, if not a "hit", go to Step 7 above.<br />10.<br />Move the display line into the screen.<br />11.<br />If screen is full (determined by NUMBER-OF-RECORDS), move PF KEY DIRECTIONS message into SCOMPL and exit.<br />12.<br />Go back to Step 7 above.<br />## <br />SCN Function, Continuation<br />1.<br />Set NUMBER-OF-RECORDS to 16.<br />2.<br />Continue processing at Step 7 above in New Transaction Mode.<br />## <br />FND Function, New Transaction<br />1.<br />Set NUMBER-OF-RECORDS to 16.<br />2.<br />If Search Argument is null, issue ENTER SEARCH ARGUMENT message and force the next transaction to also be a New Transaction Mode, exit.<br />3.<br />Normalize the entered key value and set the key name in the MAGECIO Request Area.<br />4.<br />Position into the file generically (LOCKY) using the Normalized key value.<br />5.<br />If NOT-FOUND (end of data), move END OF DATA message to SCOMPL and to screen body and exit.<br />6.<br />Read first record (REDLE). If NOT-FOUND, set DB ERROR message and exit, otherwise go to Step 9 below.<br />7.<br />If number of reads has reached SCAN-LIMIT, simulate that the screen is full and go to Step 11 below.<br />8.<br />Read next record (REDNX). If NOT-FOUND, move END OF DATA message to SCOMPL and exit.<br />9.<br />Build display line from record data and compare to Search Argument(s), if not a "hit", go to Step 7 above.<br />10.<br />Move the display line into the screen.<br />11.<br />If screen is full (determined by NUMBER-OF-RECORDS), move PF KEY DIRECTIONS into SCOMPL and exit.<br />12.<br />Go back to Step 7 above.<br />## <br />FND Function, Continuation<br />1.<br />Set NUMBER-OF-RECORDS to 16.<br />2.<br />Continue processing at Step 7 above in New Transaction Mode.<br /># <br />Operating Environment<br />## <br />MAGEC Control Program<br />The MMP operates as a subordinate program to the MAGEC Control Program. Whenever an Operator makes an entry and presses (cont.)<br />a transmit key to send the message to the CPU, the message is passed to the MAGEC Control Program (MAGECCP). MAGECCP (cont.)<br />accepts the incoming message and formats it into the TWA-MSK-AREA where the Mask Copybook defines (cont.)<br />it.<br />MAGECCP performs the Automatic Edits and Security Validation and then passes control to the Cobol MMP -- if the (cont.)<br />Operator is properly authorized. The MMP receives the message in the standard MAGEC Masking format and does not concern (cont.)<br />itself with the mechanics of reading and writing to the terminal or handling the variable incoming and outgoing (cont.)<br />formats. The MMP is actually portable, it can be executed in any MAGEC-supported environment. That includes MVS/CICS, (cont.)<br />VSE/CICS, Westi, VM/CMS (with or without VM-CICS), and PC and PS/2 environments using MS-DOS, PC-DOS, or OS/2, and (cont.)<br />LAN's.<br />SInce all interface with the environmnet is handled by the MAGECCP program, the individual MMP's need not be aware of (cont.)<br />the specifics of that environment. This enables the same MMP to operate in any supported enviroment with no program (cont.)<br />changes. On a network the same MMP can be executed in character mode and in GUI (Graphical User Interface) mode (cont.)<br />simultaneously. That is because the screen formatting and decoding is done externally to the MMP (cont.)<br />itself.<br />After receiving the formatted, edited, incoming message, the MMP does its processing. When it is ready to send the message back to the Operator it just exits, returning control back to MAGECCP.<br /><br />next: genmmp03.md.txt