This can be fixed by using a command script instead of a cataloged
command.


Tony Furnivall wrote:
>
> At 07:43 AM 8/20/98 -0500, Ian Collins wrote:
> >I wrote a small command which is catalogued for my users, as follows,
>
> ...snip...
>
> >This command (addcat) works fine when run from the comamnd line.
> >However, if I put a number of these calls into a command file, as
> >follows,
>
> >From the MPE COmmand Manual, p.2-534
>
> If SETCATALOG is used in a UDC, all valid commands through and including the
> setcatalog command execute. But execution of the UDC terminates after the
> execution of the setcatalog command. COmmadns that follow do not execute.
>
> My guess is that the first "addcat" command gets executed up to the point
> where it issues a setcatalog, and then stops, thereby terminating the
> command file execution. This is probably because it "loses track" of where
> abouts it is in the UDC as it catalogs the new addition to COMMAND.PUB.SYS
>
> HTH
> TOny

--
Richard Gambrell, Database Administrator and Consultant to Computing
Services
University of Tennessee at Chattanooga
113 Hunter Hall, 615 McCallie Ave. Chattanooga, TN 37403-2598
UTC e-mail: [log in to unmask]   phone: 423-755-4551
Personal e-mail: [log in to unmask]   postal: PO Box 1401, Hixson, TN
37343-1401