|
|
|
|
|
Figure 20 DO USER (Primitive Method)
ON CLASS = T EXTWTR DEST FORM
PRT COPIES LVL USER DEST MAX COPIES
PRINT/CDAM PARMS =
WHEN LINE 00006 - 00006 COL 00016 - 00019 PRINT REF NXT CT AND/OR
STRING = 1000
DO USER = BR10 LVL LINE COL - S T
SYNONYM = CONCAT =
DO
WHEN LINE 00006 - 00006 COL 00016 - 00019 PRINT REF NXT CT AND/OR
STRING = 1001
DO USER = BR11 LVL LINE COL - S T
SYNONYM = CONCAT =
DO
WHEN LINE 00006 - 00006 COL 00016 - 00019 PRINT REF NXT CT AND/OR
STRING = 1002
DO USER = BR12 LVL LINE COL - S T
SYNONYM = CONCAT =
DO
WHEN LINE 00006 - 00006 COL 00016 - 00019 PRINT REF NXT CT AND/OR
STRING = 1003
DO USER = BR99SP LVL LINE COL - S T
SYNONYM = CONCAT =
DO
Using this method, if we have hundreds of codes for hundreds of recipients, our report decollating mission definition will be very long. If we had defined synonyms in the recipient tree, we could pick the recipient identification from the page itself. Although the recipient name does not appear on the page, the recipient's synonym (alias) does.
If at any time a new branch opens, then using this method, all the report decollating mission definitions that handle reports for the new branch would have to be updated with the new branch name, and so on. Also, if a branch closes, the report decollating mission definitions would have to be updated to reflect this. This would generate a lot of work in maintaining the report decollating mission definitions.
The recommended way to handle this situation is detailed in the following example.
Parent Topic |