05 hold-name pic x(20). 02<br />05 subscript-1 pic s9(4) comp sync. 03<br />04<br />05<br />06<br />07<br />08<br />09<br />10<br />11<br />12<br />13<br />14<br />15<br />Move CURSOR to a line, use ERASE EOF to Delete it -or- PF20 to Insert After it<br />Semicolon (;) is the TAB Character Asterisk (*) in col. 1 = suppress upcase<br />Press PF2 for Instructions Press PF4 for menu of Named Proformas<br />```** <br />Figure 03 -- Customization Algorithm Entry Screen<br />** with Proforma Code Displayed<br />## <br />Enter Your Work Field Definitions<br />| ```<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DO THIS:<br />Overkey the proforma with the code shown on screen sample, press ENTER.<br />&nbsp;&nbsp;&nbsp;<br />```** <br />Your code will be recorded (added) to the Library and displayed back to you. The Function Code (on top line of screen) (cont.)<br />will be changed from ALGADD to ALGSEE. If you made an error you can just move the cursor down to the body of the screen (cont.)<br />and overkey with the correct code and press ENTER.<br />Your code may be entered in lowercase characters, MAGEC will automatically translate all lowercase characters to (cont.)<br />uppercase. You can override the uppercase translation feature by entering an asterisk (*) in column (cont.)<br />1.<br />You may press the HELP key (PF1) for full instructions on how to use the Librarian online functions (<br />ALG...<br />, etc.). If you press PF2 you will be displayed brief instructions on coding for the %VARSTOR insertion point.<br />| ```<br />**&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DO THIS:<br />Now, press PF12 (Shift-F2, on a PC) to return to the TSKLST.<br />&nbsp;&nbsp;&nbsp;<br />```** <br />**<br />**<br />**<br />**<br />**<br />NOTE:<br />**<br />It is not necessary for you to use the Shift key to enter uppercase alphabetic characters on this screen. MAGEC will (cont.)<br />automatically change any lowercase alphabetic characters to uppercase for you. All the Librarian entry and update (cont.)<br />screens automatically translate to uppercase to simplify your work since Cobol, Assembler, and even JCL are all coded (cont.)<br />in uppercase only (Cobol II accepts lowercase coding as equivalent to uppercase coding).<br />If you *do* wish to enter text in lowercase and *not have it converted* to uppercase, you must type an asterisk (*) in column 1 of each line which you do not want converted to uppercase.<br />| ```<br />**<br />ALGADD 600/VARSTOR<br />SEARCH ARG: ..................................................................<br />Password: M A G E C VARSTOR page<br />New Password: CUSTOM ALGORITHM DEFINITION FOR MMP 600<br />add items to VARIABLE STORAGE TAB Option (PF14=ON/OFF): ON<br />....+..;10.;..+;..20....+...30....+...40....+...50....+...60....+...70..<br />05 VACATION-DUE PIC S9(7)V99 COMP-3. 01<br />05 SICK-DUE PIC S9(7)V99 COMP-3. 02<br />05 COMP-DUE PIC S9(7)V99 COMP-3. 03<br />05 TOTAL-DUE PIC S9(7)V99 COMP-3. 04<br />05<br />06<br />07<br />08<br />09<br />10<br />11<br />12<br />13<br />14<br />15<br />Move CURSOR to a line, use ERASE EOF to Delete it -or- PF20 to Insert After it<br />Semicolon (;) is the TAB Character Asterisk (*) in col. 1 = suppress upcase<br />Press PF2 for Instructions Press PF4 for menu of Named Proformas<br />```** <br />Figure 04 -- Your Custom Coding in %VARSTOR<br />## <br />Entering Procedure Division Code<br />The TSKLST (page 1) will appear.<br />| ```<br />**&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DO THIS:<br />Press PF8 to page forward to page 2.<br />&nbsp;&nbsp;&nbsp;<br />```** <br />The screen will look like the one shown here. Notice that the status of the %VARSTOR task now indicates "1 DONE". That means that you have added one "page" (record) of coding for %VARSTOR.<br />Next you must enter the PROCEDURE DIVISION coding to calculate the figures into the four work fields you have defined. For our purposes we will insert that coding into the "Logical Join" routine.<br />The routine named JA100-LOGICAL-JOIN is performed by the MMP after every READ of the Primary Data Class. When you did (cont.)<br />the Automatic Logical Join sequence in the basic development process (see MAGEC "Application Developer" Tutorial) MAGEC (cont.)<br />automatically generated a piece of Customization coding to be inserted into JA100-LOGICAL-JOIN. The name of the (cont.)<br />insertion point is %JOIN.<br />| ```<br />**&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DO THIS:<br />Press PF8 to page forward to page 3.<br />&nbsp;&nbsp;&nbsp;<br />```** <br />| ```<br />**<br />TSKLST 600 PF8 = Next Page -- PF5 = PAGE 1<br />M A G E C TASK LIST FOR MSK600<br />...............T A S K......................... PAGE 2 .....STATUS......<br />IV. CODE CUSTOMIZATION ALGORITHMS (CONTINUED)<br />4. DATA CONSTANTS %LITERAL DEFAULT LOGIC USED<br />5. Special SECTION-NAME for IDMS %SCHEMA DEFAULT LOGIC USED<br />6. DEFINE user work area %USRAREA DEFAULT LOGIC USED<br />7. add items to VARIABLE STORAGE %VARSTOR 1 DONE<br />B. INITIALIZATION<br />1. MAINT. FUNCTION INITIALIZATION %INIT DEFAULT LOGIC USED<br />2. ATTRIBUTE INITIALIZATION %INITATB DEFAULT LOGIC USED<br />3. BROWSE FUNCTION INITIALIZATION %LOCINIT DEFAULT LOGIC USED<br />4. PRE INITIALIZATION ROUTINE %PREINIT DEFAULT LOGIC USED<br />C. SCREEN HANDLING<br />1. INITIALIZE SCREEN (BLANK SCREEN) %BLNKSCR DEFAULT LOGIC USED<br />2. COMPUTATIONS FOR SCREEN DISPLAY %COMP DEFAULT LOGIC USED<br />3. SCREEN FIELD EDIT(S) %EDIT DEFAULT LOGIC USED<br />4. PHASE 2 EDITS %EDIT2 DEFAULT LOGIC USED<br />5. ADDITIONAL DATA TO BROWSE SCREEN %LOCMOV DEFAULT LOGIC USED<br />Position the Cursor on an Item and Press ENTER to Select it, Press PF2 for<br />Item Description -OR- PF1 FOR HELP<br />KEY = MASK NUMBER<br />```** <br />Figure 05 -- Status Showing Customization Done<br />## <br />Select Logical Join Task<br />Notice that the TSKLST shows that there is one "page" of code on file for %JOIN already. That is what the Automatic Logical Join feature generated.<br />| ```<br />**&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DO THIS:<br />Position the cursor down to the %JOIN task, press ENTER.<br />&nbsp;&nbsp;&nbsp;<br />```** <br />You will be transferred to the screen showing the existing code which is on file.<br />| ```<br />**<br />TSKLST 600 PF8 = next page -- PF5 = Page 1<br />M A G E C TASK LIST FOR MSK600<br />...............T A S K......................... PAGE 3 .....STATUS......<br />IV. CODE CUSTOMIZATION ALGORITHMS (CONTINUED)<br />6. ADD'L EDIT ROUTINE MMP MAINT KEY %NORMKEY DEFAULT LOGIC USED<br />D. DATA BASE COMMANDS<br />1. INITIALIZE RECORD FOR ADD %ADDINIT DEFAULT LOGIC USED<br />2. LOGIC TO ADD TO DATABASE %ADDIT DEFAULT LOGIC USED<br />3. LOGIC TO DELETE FROM DATABASE %DELET DEFAULT LOGIC USED<br />4. Logic to JOIN secondary files %JOIN 1 DONE<br />5. LOGIC TO 'SETL' ON DATABASE %LOCKY DEFAULT LOGIC USED<br />6. READ FOR UPDATE ROUTINE (CHANGE) %RDUKY DEFAULT LOGIC USED<br />7. READ FOR DISPLAY ROUTINE %REDKY DEFAULT LOGIC USED<br />8. LOGIC TO READ FIRST RECORD %REDLE DEFAULT LOGIC USED<br />9. LOGIC TO READ-NEXT RECORD %REDNX DEFAULT LOGIC USED<br />10. LOGIC TO DROP EXCLUSIVE CONTROL %RELES DEFAULT LOGIC USED<br />11. LOGIC TO UPDATE THE DATABASE %UPDAT DEFAULT LOGIC USED<br />E. SCREEN NAVIGATION<br />1. MMP EXIT LOGIC %GOBACK DEFAULT USED<br />Position the Cursor on an Item and Press ENTER to Select it, Press PF2 for<br />Item Description -OR- PF1 FOR HELP<br />KEY = MASK NUMBER<br />```** <br />* ** NOTE: The status of the %JOIN customization task shows "1 DONE", meaning that there is one "page" of customization (cont.)<br />coding in the repository for the insertion point, for this application. Since you have not done any customization for (cont.)<br />%JOIN yet, you might wonder how that could be correct. When you did the initial development of MMP600 in the first (cont.)<br />project, you used the Fully-Automated method. MAGEC automatically generated the necessary Cobol coding to read the (cont.)<br />SIF01 data using the Employee number from the Vacation data as a "foreigh key". This generated Cobol code was added to (cont.)<br />the repository as custom code for the %JOIN insertion point so that you could easily access it to make any alterations (cont.)<br />you might desire.<br />Figure 06 -- Task List Screen, page 3<br />## <br />Modifying Customization Code<br />The screen will be displayed to you as shown on the facing page. You are going to insert some additional Cobol coding (cont.)<br />near the top of this routine, after the first line of the coding which is displayed.<br />This means that you will be inserting using the PF20 key. Refer to the MAGEC "Librarian" chapter for full instructions or press PF1 for HELP.<br />| ```<br />&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;DO THIS:<br />Place the cursor on the first line of code, press PF20 (Shift F10 on PC).<br />&nbsp;&nbsp;&nbsp;<br />```** <br />This will "open up" the screen by temporarily "shoving down" all the lines of code below where you placed the cursor to allow you to key new code into the screen.<br />**<br />NOTE:<br />**<br />The "IF (NOT-FOUND)" coding on the first line of the screen tests whether the Primary data (VAC) was successfully read. (cont.)<br />If it was not, then we do not want to try to do computations using fields from it, nor would we want to try to read the (cont.)<br />SIF data.<br />If the VAC record was not found, then this routine will simply bypass its processing and effectively "do nothing". The (cont.)<br />mainline logic of the generated MMP will not attempt to use any of the data from the records because it too tests for (cont.)<br />the NOT-FOUND condition.<br />| ```<br />**<br />ALGNXT 600/JOIN/01-SIF/000<br />SEARCH ARG:............................................................<br />......<br />Password: M A G E C JOIN page<br />CUSTOM ALGORITHM DEFINITION FOR MSK 600 01-SIF (000)<br />Logical Join - secondary files TAB Option (PF14=ON/OFF): ON<br />....+..;10.;..+;..20....+...30....+...40....;+...50....+...60....+...70..<br />IF (NOT-FOUND) GO TO JA900-RETURN. 01<br />MOVE REDKY TO TWA-DB-CMD. 02<br />MOVE 'SIFK1' TO TWA-DB-KEY-NAME. 03<br /><br />next: cstm03.md.txt