Modifying the APS Configuration File can be a daunting configuration task. When setting overrides are involved, the complexity is further increased. Add to that the fact that APS will use the most restrictive setting applicable, even if it is different from the most specific setting for the user. It can be very difficult to determine the exact setting that APS will use for a particular user.
APS is very consistent in how it handles configuration. It is very predictable. But it is easy for APS to wade through potentially hundreds of settings, determining limits, applicability and restrictiveness based on internal rules. It is not so easy for a human administrator.
APSTestSettings is provided to report the current configuration settings. Without a command line argument, APSTestSettings will report the default settings in effect. Output is grouped functionally. Each setting is flagged as to whether that setting supports overrides.
Command line arguments can be used to specify a particular user, in which case APSTestSettings will show the settings that are currently in effect for that user.
APSTestSettings calls into the APS libraries to obtain the settings. It does not use code separate from APS. Thus, barring output differences, APSTestSettings will always report what APS will actually see for a given user.
-? |
Show Help |
-m[sel] |
Mode selection |
|
s: Settings Mode (default) |
|
e: Evaluator Mode |
|
l: Lexer Mode |
-q |
Quiet (all modes) |
-d |
Show license detail (Settings Mode Only) |
-# |
Show line numbers (Settings Mode Only) |
-r |
Show attribute mappings (Settings Mode Only) |
-c |
Show complexity settings (Settings Mode Only) |
-t |
Show timings (All Modes) |
-S<sections> |
Explicitly control which sections are displayed (Settings Mode Only) |
-u userpath |
User path, such as LDAP://127.0.0.1/uid=erict,o=nds.com (Settings & Eval Modes Only) |
macro=val |
Context macro definitions (Settings & Eval Modes Only) |
Copyright © 2014 CA.
All rights reserved.
|
|