Hi Start with taking look at XPRINT.REMIT and see what it is doing at that line - at a guess I'd say "Execute ... Capturing ... Returning". Otherwise you could be using an OPENSEQ.
You've either got a permissions problem on the directory (or the files in the directory) used to hold capture files - or you have run out of file handles. The most likely cause is permissions - make sure the directory used to capture temporary files from EXECUTE...CAPTURING...RETURNING is set read/write/execute for the group that represents your UniData (or UniVerse as appropriate) database. It should also have the group sticky bit set (chmod g+s). Look for OLD capture files lying around which have not been swept up by housekeeping and get rid of them (I usually institute a daily cron script to remove any files not in use (fuser -u) and > 48 hours old). Don't leave the UniVerse or UniData TEMP work area at /tmp - it should be in it's own directory structure and preferably on it's own disk/volume. That way you can unconditionally clear it down when you stop (or start - your choice) the database. Otherwise: If you are using O/S file handles you need to police them up and close them when you are done. If the program XPRINT.REMIT is opening O/S file handles (anything except hashed files) you need to make sure EVERY method call which invokes this program - directly or indirectly - leaves any O/S file handles in the state in which they were found (i.e. closed). Do *not* use root user to start and stop RedBack - please...... Note 1 on Solaris: On Solaris, 32-bit applications have a hard limit of 256 file handles - and if you are on Solaris this may be your problem. Make sure NFILES (UniData) or MFILES (UniVerse) is around 240 and you will probably be OK. If you are using lots of O/S file handles (OPENSEQ etc) and not closing files you need to change the application code to close these files when done. Within O/S limits of course you can adjust the maximum number of open files per user / on the system and the number of concurrently used inodes as you wish - it's just Solaris that has the hard limit. Note 2 on Solaris: Solaris 10 (and 9 I think) support kernel virtualisation - it's not just /etc/system any more. I haven't read up on this much, so any group contribution welcomed. Hope this helps Regards JayJay -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of john reid Sent: 31 October 2007 19:32 To: [email protected] Subject: [U2] unable to create capture file Group, I think that I have sent this before, so apologies. We have a number of RedBack processes which seem to be unable to properly do an EXECUTE ' XXX ' CAPTURING OUTCOME The error message is : Wed Oct 31 14:46:53 0 RedBack Program "XPRINT.REMIT":Line 95, Message[010291] which translates to " Unable to create capture file." Anyone know a cause for this? -- john ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
