I stand by my statement that the command was not being executed. The users in the list who were already enrolled, were not deleted and the service machine executing the commands is an administrator of the filepool. When deleting an enrolled user from the particular filepool, it takes 1.5-3 minutes per user. The commands were a combination of ENROLL USER for zero blocks followed by DELETE USER. The reason for the ENROLL is because DELETE USER only deletes permissions granted to enrolled users, it does not do anything if the user is not enrolled.
The machine was logging off less than a second after it issued the commands - something that is impossible if it is doing as directed. I inserted console stages at strategic points and confirmed that the commands were being sent down the pipeline. I also confirmed, by cut-and-paste from the file to the command line, that the commands were correct. With 80+ users in the file, at say an average 2.25 minutes per DELETE USER command, it should have taken 3 hours for the EXEC to run, not < 1 sec. I, too, am running vanilla Pipelines. There is neither a nucleus extension nor a EXECLOADed EXEC named DELETE. I know that Pipelines is fast, but it cannot run host commands faster than they run from the command line in their native environment. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Thursday, December 14, 2006 3:44 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: COMMAND vs. CMS On Thursday, 12/14/2006 at 02:49 PST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > Irrelevant in this case. Translation is a by-product, not the main > thrust, of the command environment. In any event, the commands entered > were all upper case. The problem is that either CMS does not recognize > SFS administrative commands (and who knows what others) when entered > from the Pipelines COMMAND filter, or Pipelines is screwed up. There > is no separate command environment for these commands, so they must be > CMS commands, and should be so treated, by both Pipelines and CMS. > > Try the experiment of executing the DELETE USER command from within > the "address command" environment. It will work. nucxmap delete DMSNXM941I Nucleus extension DELETE is not loaded Ready; execmap delete DMSEXM416W There are no DELETE * EXECs storage resident Ready(00028); listfile delete * * DMSLST002E File not found Ready(00028); type temp file DELETE USER ABC (TYPE NOCONFIRM Ready; pipe < temp file a | CMS | cons DMSJDE1139E You are not authorized to issue this command Ready(00076); pipe < temp file a | command | cons Ready(00076); The command is executing in either case (fails, of course, but it executes). Naturally my version of Pipes is vanilla-flavored. :-) Alan Altmark z/VM Development IBM Endicott
