entwined printings

Hello folks, We are experiencing problems with our DG/UX 5.4.2 spooling system. Sometimes jobs get entwined (cross-linked) - a part of a job appears repeatedly amid the other. And the other job became a never-ending long job (which it actually wasn't). _One_ (meaning that there are others) situation under which this happened goes like this: program P prints a report to file F, spools it with "lp -c ... F" (note that -c option), then it is run again, and F is spooled again. The 2 lives of F were printed as if the 2nd life overwrote the 1st life from the start. It doesn't appear that printing system screwed up things! I've a copy of the final life of F (I'm saving it to show around) and it was exactly as what was printed (i.e. the printing system faithfully produced a hardcopy of the thing). Now I am puzzled as to why this would happen! I mean "lp -c" would have saved the 1st life of F in the spooling area right? So whatever I do to the 2nd life of F wouldn't matter would it? Oh, the report was printed by an Informix-4gl app (produced with v4.1 of Informix-4gl, c compiler version). For the case I detailed, it could be a Informix problem, but the START REPORT whatever TO "F" statement was run twice, so the 2nd life of F shouldn't have any leftovers from its 1st life!! I can't image why Informix would do anything extraordinary (and stupid) other than just "write to F with truncation" when the START REPORT statement was executed. In other problem situations (in which the print jobs appeared to be repeating like mad with parts from other print jobs appearing here and there), not all the involved print jobs are produced by the Informix app. 1 was submitted with the command "lp -c whatever" for example. So what gives? More likely a DG/UX problem? Unfortunately, for these "entwined + repeating" type of situations I don't have a copy of the spool files being printed (the users reported it too late to us). Please help!! Lots of paper have been wasted already and we can't really can't ask someone to sit by the printers to see if anything odd gets printed. Besides, some printing are done overnite, unattended. PS: We asked the local DG people and they said "Oh, we've never seen anything like that, sorry!" Now we all know what vendor support is like don't we? ;(