Why rollback is not working....

Question

it's 10g
as far as I know, dbms_scheduler.create_job is not a DDL. So why this is saving insert ...
SQL*Plus: Release 10.2.0.3.0 - Production on Sat May 10 20:58:31 2008
Copyright (c) 1982, 2006, Oracle.  All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
SQL> @y
SQL> drop table junk_34;
Table dropped.
SQL> create table junk_34(f varchar2(10));
Table created.
SQL> set serveroutput on
SQL> declare
  2   command varchar2(20000) ;
  3    job_name varchar2(200) := 'TEST';
  4   temp_name varchar2(200) := DBMS_SCHEDULER.GENERATE_JOB_NAME ;
  5  begin
  6   command := 'BEGIN null; END;';
  7   insert into junk_34 values('a_value');
  8  dbms_scheduler.create_job(
  9    job_name => temp_name,
10    job_type => 'PLSQL_BLOCK',
11   job_action => command,
12    start_date => systimestamp,
13    enabled => true);
14  dbms_output.put_line(command);
15  rollback;
16  end;
17  /
BEGIN null; END;
PL/SQL procedure successfully completed.
SQL> set line 2000
SQL> select * from junk_34;
F
a_value
SQL>
SQL>

Answer 1

it wont even compile with autonomous_transaction
Read my comments carefully. I said you should create "your own wrapper package for the dbms_scheduler that simply surrounds each call to dbms_scheduler with an autonomous transaction". I did not say "stick your code inside an anonymous pl/sql block with an autonomous transaction pragma".
Stripped to the bare minimum, this looks about right - but since I've only spent a few minutes writing it, I'm not going to guarantee that it's doing anything other than giving you the general idea:
create or replace package my_scheduler
as
     procedure create_job(
          i_job_name     in     varchar2,
          i_job_type     in     varchar2,
          i_job_action     in     varchar2,
          i_start_date     in     timestamp with time zone,
          i_enabled     in     boolean
end;
create or replace package body my_scheduler as
procedure create_job (
     i_job_name     in     varchar2,
     i_job_type     in     varchar2,
     i_job_action     in     varchar2,
     i_start_date     in     timestamp with time zone,
     i_enabled     in     boolean
is
     pragma autonomous_transaction;
begin
     dbms_scheduler.create_job(
          i_job_name,
          i_job_type,
          i_job_action,
          i_start_date,
          i_enabled
end;
end;
/If you've got your privileges sorted out correctly, you should be able to create this package, then make a call to my_scheduler.create_job rather than dbms_scheduler.create_job.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk