Preventing Unsecured Starts After Upgrades

If the security provider is set to OPSYS in the configuration file and, additionally, the explicit environment variable EDAEXTSEC is set to OPSYS (or ON), and the server cannot impersonate users because it lacks platform-specific authorization steps, the server start aborts and error messages are written to the edaprint log.

This feature prevents an unsecured server start after a software upgrade if any of the required post-upgrade reauthorization steps are missed on a UNIX, IBM i, or z/OS USS deployment. This is not applicable to other platforms. The setting may be placed in any normal server start-up shell or profile that a site is using or in the server edaenv.cfg configuration file. The messages vary slightly by platform.

The edaprint messages are:

I Configured primary security is 'OPSYS' as set in configuration file

E Server security explicitly set to OPSYS, but lacks authority!   

Workspace initialization aborted.

(EDA13171) UNABLE TO START SERVER