Works great. I made a REXX filter out of by taking out the procedure and end and put a 'short' following. Then I simply prefaced the input stream.
Regards, Richard Schuh -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Aria Bamdad Sent: Thursday, June 29, 2006 12:29 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SFS Question? Richard, Some SFS commands are 'atomic requests'. There is more about this in the CMS Application Dev. Guide. Your EXEC (pipes) creates a default work unit that stays active during the execution of the exec. In order to call the SFS commands you have, you must first close that work unit, then call the command. Below is a sample Rexx procedure you can call to close the default work unit. Then issue the command. Hope this helps. Aria. RelWorkUnit: Procedure CSLRC = 0 CSLRESC = 0 WU = 0 CALL CSL 'DMSRETWU CSLRC CSLRESC WU' If (CSLRC ^= 0) | (CSLRESC ^= 0) then do Say 'Error calling DMSRELWU, RC='CSLRC 'ReasonCode='CSLRESC Say 'Error releasing default workunit.' End Return On Thu, 29 Jun 2006 12:25:00 -0700 Schuh, Richard said: >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:=20 > >enroll user JDOE sfsa (blocks 0 = > =20 >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).=20 > >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?=20 > >Regards, >Richard Schuh >
