Once the command intrinsic executes I will check for the existence of the CM
KSAM file. If it exists, then I know the intrinsic did work successfully. If
the file isn't there then I know it failed.

That will solve the problem. Not the optimum solution but a solution.


Thank you to all who responded,

Brian.



On Mon, 25 Jan 2010 08:29:01 -0700, Keven Miller
<[log in to unmask]> wrote:

>As Roy suggested, try RUN NONEXIST.
>
>My take on it is its working correctly.
>The COMMAND intrinsic had no trouble running KSAMUTIL.
>
>Now if KSAMUTIL QUIT or ABORTED with the internal error,
>then I would expect COMMAND to return the some error that
>the program didn't exit properly.
>
>The KSAMUTIL error was handled by the program,
>it then accepted the "EXIT" command, and terminated properly.
>
>So if you want any error from KSAMUTIL, you WILL need to
>process XEQERR.
>
>Or possibly check JCW incase KSAMUTIL sets that when it
>has an error.
>
>Fox 12 ksamutil
>HP32208A.07.04 MON, JAN 25, 2010, 8:27 AM KSAMUTIL VERSION:A.07.00
>>BUILD KSAMCMF1/OLDKSAM1.PUB;REC=+8192,,F,BINARY;&
>>TEMP;DISC=000050001;CODE=+8133;LABELS=206;FIRSTREC=1;&
>>KEY=B,003,001,,RDUP;KEY=B,004,001,,DUP;KEY=B,005,002,,RDUP;&
>>KEY=B,007,001,,DUP;KEYFILE=KSAMCMK1
>INVALID RESULTANT BLOCK SIZE (FSERR 11)
>>e
>Fox 12:showjcw
>CIERROR = 0
>JCW = 0
>RCRTMODEL = 7009
>RPCVERSION = 1
>RCRTWIDTH = 80
>Fox 12:showvar @err@
>CIERROR = 0
>HPCIERR = -8116
>HPCIERRCOL = 9
>HPCIERRMSG =
>HPERRDUMP = 0
>HPERRSTOLIST = TRUE
>HPFSERR = 0
>Fox 12:
>
>It doesn't.
>
>Keven Miller
>
>* To join/leave the list, search archives, change list settings, *
>* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *