Question regarding the "mcxquery" and "dscl -mcxread" commands:

Question

Question regarding the mcxquery and dscl -mcxread commands:
Does anyone know why the mcxquery and the dscl . -mcxread commands don't show any info about MCX managed login items & printers? The System Profiler's "Managed Client" section does. Id like to see info regarding managed printers and managed login items using the mcx tools. I have Mac users running 10.5.2 with both login items and printers that are pushed out to them via MCX. The System Profiler app shows all of their policies, but the dscl . -mcxread and mcxquery tools dont. Why not?
-D
Message was edited by: Daniel Stranathan
null

Answer 1

How do you "call procedures/functions" without sql code? You need at least the call statement like
{call myProc(?,?,?)}that you wrap into a CallableStatement.
Other than that: when you switch off autocommit, you need to call commit/rollback at the end. Usually, if you don't commit/rollback a non-autocommitted connection, the transaction get's committed/rollbacked when you close the connection - that depends on the JDBC driver. But it's never a good idea to ommit the commit/rollback calls on a non-autocommit connection. Usually you enclose your code in a try/catch block like this:
con.setAutocommit(false);
try {
   con.commit();
} catch (Exception e) {
   con.rollback();
} finally {
    con.setAutocommit(true); //or:
    con.close();
}