| Contents: | Main | Chapter | See Also: | Getting Started Manual | Advanced User Manual | |||
The list below describes the component-specific special processing with DIFROM (per Table 123 in the PDF):
Table 123: DIFROM—Special Processing
If an exact match is found for a HELP FRAME entry, only the existing WORD-PROCESSING field TEXT and the Multiple fields RELATED FRAME and INVOKED BY ROUTINE are deleted from the existing entry. Then, the new entry is brought in on top of the old one.
For all entries brought in by the init, the init loops through the RELATED FRAME Multiple and resolves the pointer field RELATED FRAME, which is a pointer back to the HELP FRAME (#9.2) file.
If a matching entry is found, the old entry in the BULLETIN (#3.6) file is deleted. However, entries in the bulletin's MAIL GROUP Multiple (which identify recipients of the bulletin) present on the target system before the install will remain associated with the bulletin after the incoming bulletin is installed.
The init displays each bulletin brought in by the init and reminds the installer to "Remember to add mail groups for new bulletins."
The current date/time is stuffed into the field DATE INSTALLED AT THIS SITE, within the VERSION Multiple for the current version of the package.
The pointer field PRIMARY HELP FRAME is resolved.
POINTER fields DISPLAY GROUP DEFAULT, PROTOCOL TO EXPORT, DEFAULT PROTOCOL, and MENU are resolved. If pointers to the PROTOCOL (#101) file cannot be resolved because the pointed-to protocol cannot be found, the init routines add a new entry to the PROTOCOL (#101) file (with just a .01 field) in order to resolve the pointer. This is done because PROTOCOLS are exported in a special set of routines (called ONIT routines) that are normally executed as a post-init.
If a matching entry is found, the entire old entry is not deleted. Only the DESCRIPTION field (a WORD-PROCESSING field) and the ITEMS Multiple (containing menu items) are deleted from the old entry before the new one is brought in.
For example, if the site has a local lock on an OPTION, and no lock is brought in by the init, the local lock is preserved.
The POINTER fields SERVER BULLETIN, SERVER MAIL GROUP, PACKAGE, HELP FRAME and the .01 field of the ITEMS Multiple (which points back to the Option file) are all resolved.
No special processing, except that if a matching entry is found in the target system, it is merged rather than replaced. Note that pointers in the SUBORDINATE KEY Multiple are not resolved; so, data should not be exported in that multiple.
No special processing is done for the FUNCTION (#.5) file.
The only special processing done for these templates is that after they are all installed, compiled PRINT and INPUT templates are automatically recompiled. The init uses the system's preferred routine size from the MUMPS OPERATING SYSTEM file (#.7) when compiling these templates. It is possible that the recipient of the init could already have routines with the same names that the compiling routine will use. Thus, the developer should warn the installer of the routine names that will be used by incoming compiled templates, especially if the developer is sending templates that are not namespaced.
Any BLOCKS that are pointed-to by FORMS are automatically included in the init routines. The BLOCKS are installed first, with no special processing. Then, the FORMS are installed. Finally, POINTERs to the BLOCK (#.404) file from the FORM (#.403) file are resolved.
Reviewed/Updated: May 2026