Restriction: This topic applies to Windows environments only.
The following describes how to set up your environment to validate tables during the compile process:
- With Security Off, the user ID will be the same authorization ID defined as the primary ID unless you define a secondary ID.
- With Security On, the user ID will be the same ID that you enter in the logon screen and optionally the secondary ID if defined (not applicable to SQL Option Link).
To access tables with the same user ID and authorization ID, use the VALIDATE preprocessor directive. To access tables with different user ID and authorization ID, do one of the following:
- Use VALIDATE and AUTHID preprocessor directives.
- Define group IDs or issue a GRANT to the user ID to have access to the authorization ID defined in the AUTHID preprocessor directive.
- Define secondary IDs.
