I have a service machine that is an administrator for one of our file pools. I
am trying to get it to clean up the file pool when a userid is deleted from the
system. My method is to first, enroll the userid for 0 blocks, then issue a
delete user command. I can log on to this machine and enter the commands from
the CMS command line and everything works as expected. When I try to do it from
the driver EXEC for the machine, I am greeted with:
enroll user JDOE sfsa (blocks 0
DMSJEN1157E Work unit already active when atomic request is issued for work
unit 1
The delete user fails the same way (different message number, same
information).
How can I determine what is causing the work unit to be active when I try this?
Alternatively, how can I insure that no work unit will be active?
Regards,
Richard Schuh
