Your screenshot looks different than ours. We are on V12.3.0, and our SQL code goes into a "Process" tab, not a "JCL" tab.
After execution, we get a PLOG report that echos the SQL statements. Do you get this PLOG report?
Either you constructed the wrong type of UC4 object, or I am unfamiliar with your setup.
------------------------------
Pete
------------------------------
Original Message:
Sent: 11-12-2019 08:36 AM
From: Norman Nation
Subject: Oracle SQL jobs no longer prints DBMS_OUTPUT to Job's Report
Hi Pete,
Thanks for your input on this.
I finally been able to try to enable dbms_output right before the procedure. Unfortunately doesn't seem to make a difference (see screenshot).
Original Message:
Sent: 11-07-2019 05:34 PM
From: Pete Wirfs
Subject: Oracle SQL jobs no longer prints DBMS_OUTPUT to Job's Report
As an experiment, try adding this statement right before you execute your procedure, just to make sure dbms_output services are enabled at the time your request starts running;
dbms_output.enable(NULL);
------------------------------
Pete
Original Message:
Sent: 11-07-2019 03:31 PM
From: Norman Nation
Subject: Oracle SQL jobs no longer prints DBMS_OUTPUT to Job's Report
I'm kind of new to the Automic tool.
Over the last couple of months I noticed that Automic by default printed out dbms_output.put_line from my procedures to the report logs. I'm not sure what cause this but dbms_output.put_line doesn't print out anymore.
The only thing I can think of is that we changed the DB connection from the Oracle to the generic JDBC connection type causing us to lose this functionality by defualt.
Can someone confirm this and if so knows a way to push output from Oracle procedures to Automic?