Cognos Fatal Error *322*

[Peter Bateman]

Erwin:
I saw this kind of thing a few years back. We had a signalling conflict 
between C-ISAM
and InterBase. But I can't think of how we resolved it.
We might have split our QTP run into two separated process runs.
i.e. Run one access C-ISAM and output to a subfile.
     Run two access subfile and update InterBase.
Good luck.
Peter Bateman

>Hi folks,
>
>   Our environment is Unix with C-ISAM.  We recently moved one nightly job 
>to
>its own queue and have reorganized nightly processes. Approximately once 
>per
>week during the nightly run we get a:
>
>*Fatal Error* *322* Notify Cognos Customer Support [;f[JCommand died on
>'abort' signal
>
>   Any information on this problem or suggestions on how to debug it would 
>be
>greatly appreciated.
>
>Thanks,
>Erwin Kadach
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l@lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to 
>powerh-l-request@lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.

_________________________________________________________________
Powerful Parental Controls Let your child discover the best the Internet has 
to offer. 
http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines 
  Start enjoying all the benefits of MSNŽ Premium right now and get the 
first two months FREE*.