Subject: | |
From: | |
Reply To: | |
Date: | Fri, 18 Apr 1997 18:27:10 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
[log in to unmask] wrote:
>
> We have a rather complicated job that aborts with a kind of interesting
> error. The job :runs MPEX and I have tracked the error to the line:
> %comment ITC(Ola)flyttade skrivaren/ ip-adr pe !8 m402cs1 (per0401)
>
> which I intended to be an informational line (in Swedish) to remind me of a
> change I made ;-).
> I duplicated this in a job like this:
> -------------<excerpt>---------------
> !job mpex,streamer.account;outclass=lp,1
> !RUN MPEX.PUB.VESOFT;PARM=1
> %comment !8
> %e
> !eoj
> -------------<end excerpt>------------
> although this job didn't abort I got the following error:
> Attempt to divide by zero in the expression. (CIERR 9720)
>
> (the real job aborted because of an intricate nesting of IF-clauses inside
> WHILEs inside REPEATs)
>
> So it seems MPEX (or MPE ?) somehow wants to interpret the '!8'. I kind of
> thought I could have *any* text as a comment... Is this the way it should
> be? While testing I found that the '!' is interpreted by the CI as reference
> to the REDO-stack, is this the problem? Insights anyone?
>
> This does not duplicate in session.
> /perMPE and MPEX will always evaluate the "!", even if it is in a comment.
In fact if you look at some of Vesoft's own command files you will see
them use a comment followed by the MPE function to actually execute a
command. i.e. %COMMENT ![mpe('purge @')] (The syntax is a guess). I
believe that doing this avoids setting some JCWs or surpresses some
errors. Still don't know why !8 gives you the error it does, though.
|
|
|