We are V9.SP5, and here is an example "Agent Log" from one of our executions of the above script. I don't know why it isn't working for you.
2015-10-31 23:41:03 - U2000005 Job 'GLM0110.PK73334.GL.DIS' with RunID '2842401' started.
2015-10-31 23:41:03 - U2012001 Successfully established connection to 'ssssssss:0001/PRODDB' with user 'xxxxxxxx'.
2015-10-31 23:41:03 Oracle
2015-10-31 23:41:03 Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
2015-10-31 23:41:03 With the Partitioning, OLAP, Data Mining and Real Application Testing options
2015-10-31 23:41:03 - U2012014 JDBC Driver version: 11.2.0.1.0
2015-10-31 23:41:03 ALTER SESSION SET NLS_DATE_FORMAT = 'dd-MON-YYYY'
2015-10-31 23:41:03 - U2012003 0 row(s) affected
2015-10-31 23:41:03 begin
2015-10-31 23:41:03 dbms_output.enable(NULL);
2015-10-31 23:41:03 pk73334_General_Ledger.sp73334_GL_DIS_GL110('10/31/2015');
2015-10-31 23:41:03 end;
2015-10-31 23:42:35 - U2004026 Job script ended normally.
Here is what I am getting. Maybe I am going wrong with the arguments as I am not specifying any in my script.
2015-11-30 13:09:58 - U2000005 Job 'ZWD_V2P_PPM_CREATE_PR_FILE' with RunID '12578704' started.
2015-11-30 13:09:58 - U2012001 Successfully established connection to 'a829dae0.am.csplc.org:1525/MITGD' with user 'ppmdev'.
2015-11-30 13:09:58 Oracle
2015-11-30 13:09:58 Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
2015-11-30 13:09:58 With the Partitioning, OLAP, Data Mining and Real Application Testing options
2015-11-30 13:09:58 - U2012014 JDBC Driver version: 11.2.0.1.0
2015-11-30 13:09:58 sql_set_statement_terminator term="@"
2015-11-30 13:09:58 begin
2015-11-30 13:09:58 dbms_output.enable(NULL);
2015-11-30 13:09:58 Dpsg_FrameworkPOSendPRDet_UC4;
2015-11-30 13:09:58 end;
2015-11-30 13:09:58 @
2015-11-30 13:09:58 ORA-00900: invalid SQL statement
2015-11-30 13:09:58 - U2004025 Job-script execution was aborted.
2015-11-30 13:09:58 - U2012006 SQL Rollback executed