Separate LUW

Question

Hi,
Can any one tell me weather it is possible to create a separate LUW inside another LUW, wherein if i write commit statement, only the nested LUW should be commited. Please find below explanation of problem:
I have to use a code which updates a 'Z' table inside a user exit. After updation i have to utilise this 'Z' table entries in my code. But if i write commit in the updation code then the whole transaction will be commited, and if i don't write commit, records will not be updated in the table for furthur utilisation. So i thought of writing this updation code in a seperate LUW, where in if i write commit statement only the 'Z' table updation will be commited, rather than the hole transaction. Although i have written to save the updated records in a internal table, and utilise this table for furthur use, but i wan't to know weather it is possible to write a set of code as a seperate LUW inside another LUW.
Thanks in advance.
Zafar Ali
E-mail: [email protected]

Answer 1

Hi zafar,
1. Nested Luw
2. I tried the same thing now, but could not succeed.
3. Whether we use submit, rfc with NONE, or
   anything else,
   it creates another internal session.
  (inside this session, if we use commit,
   it will commit the main session also).
4. I was just wondering why u need to commit
    the nested luw.
5. As u said, this Z table u are updating,
    inside the user exit.
  Main Program-->UserExit--
>backto main program.
6. So, if u update the Z table inside the userexit,
    its records will still be available in the code of main program,  after the user exit is completed, even without commit work.
(bcos the session is same for main program and the user exit)
(even though they may not be physically updated,
  if we seen in another window/session)
regards,
amit m.