When you choose option 3b in the Client Database-Request Statement Caching menu to activate database-request statement caching for all future users by user type, the following menu appears:
Enter the type of statement caching to activate or Q to Quit 
(1-Single, 2-Stack):
Enter the number for the statement caching type, or Q to exit:
  • 1-Single — The ABL client reports only the current ABL program and line number, or a single SQL statement.
  • 2-Stack — Report the call stack up to the current ABL program and line number.
  • Q-Quit — Quit this function and return to the Client Database-Request Statement Caching menu.
After selecting the statement caching type, the following menu appears:
Enter the user type for statement caching activation or Q to Quit
(1-ABL Local, 2-ABL Remote, 3-SQL, 4-All Remote 5-All Clients):
  • 1─ABL Local—Specifies all ABL local clients.
  • 2─ABL Remote—Specifies all ABL remote clients.
  • 3─SQL—Specifies all SQL remote clients.
  • 4─ALL Remote—Specifies all remote clients including, both ABL and SQL.
  • 5─All Clients—Specifies all self-service (local) clients and all remote clients.
After you select the user type for database-request statement caching, tracing is activated for clients of the specified type that will connect to the database in future.
Note: Once activated, database-request statement caching remains activated for the specified user type, until deactivated.
Activating database-request statement caching for all future users by the specified user type changes the values of the -clstmtCacheLevel and -clstmtCacheType startup parameters. For more information, see Client Database-Request Statement Caching Level (-clstmtCacheLevel) and Client Database-Request Statement Caching User Type (-clstmtCacheType).