DIFROM

Running an Init on Target System (5 of 16)

Determining Install Status of Security Codes

Next, if the developer sent file security access codes with the file, the init asks if security codes present on the target system should be overwritten. In most cases, file security is built into files by the developer. However, if there are local security codes that need to be preserved, the installer should answer this question NO.

NOTE: Even if the installer says not to bring in security codes, the init will install the following field security:

• If Write Access is set to the "^" (a write protected field) or the "@" (programmer access required) or the field is a MUMPS type field, Write Access security is installed.
  
  
• If Delete Access is set to an "@" (programmer access required) or the field is a MUMPS-type field, Delete Access security is installed.

Reviewed/Updated: March 4, 2007