Just to follow up on this thread: > >The response was: > >"The developer has decided not to change the message type for this messag > >e." > > > That's a totally BS answer. Call them back and challenge it. > > There should at least be a justification for why the developer refused to > change it, especially since it can cause data corruption (bad spool > pointers, anyone?), AND IS DOCUMENTED TO POSSIBLY DO SO. > > C'mon, guys, we know you're working on the Next Big Release, but jeez. > Some things you shouldn't minimize on. > > -- db
This is being worked on in the background. It seems the issue is not so black and white and possible solution is not so trivial as it may have seemed. Stay tuned... "Mike MacIsaac" <mike...@us.ibm.com> (845) 433-7061
