The only solution I found for catching these errors was to have a program
that scanned the $STDLIST for errors after the fact.  Of course by then the
horse is out of the barn but maybe you can catch it before it gets too far
away!

Carl McNamee
Billing Concepts

-----Original Message-----
From: Pickering, John (NORBORD) [mailto:[log in to unmask]]
Sent: Wednesday, July 14, 1999 9:12 AM
To: [log in to unmask]
Subject: Re: Help with Quiz...


Hans-Ole Kaae writes ...
>
>I don't know about this OLKIDXREF784-JCW, but the Warning-issue has been
>discussed before - either here or on the PowerHouse-listserver.
>
>As far as I remember, no real solution came up then - but this is an
>important issue. Only a warning is generated - and overlooking this
>warning in an $STDLIST is quite easy but could be quite fatal, since
>the batch jobs proceeds happily.
>
>There is the CJCW ... this JCW (or any other JCW will suffice) should
>follow MPE-standards and be set to a negative value, corresponding
>to the actual warning - IMHO.
>
>But maybe a good solution has come up in the meantime?

PowerHouse components do a poor job of setting JCW's. I have found no
reliable method for detecting errors or warnings using any of CJCW, JCW,
QUIZ or others. So I've tended to ignore the JCW's and employ some sort of
$stdlist processing to look for errors. Roll your own or get something like
JobRescue (or whatever it's now called) from NSD (or whatever they're now
called).

And I think asking Cognos for an enhancement would be rather pointless. They
seem to file such requests in the circular file :-( And this request would
meet with even less enthusiasm since this would be a platform specific
enhancement and they have moved ever closer to a single source version
across all supported platforms.

John Pickering
Toronto