"trace" in sysvr3?

[heiser at tdw201.ed.ray.com]

A few days ago, I posted a question about a problem I'm having getitng my
Epson printer to work on my Esix system.  One person replied today, sending
me a copy of what the /usr/spool/lp directory structure is supposed to look
like.  I'll check that, eventhough I already compared my system to what is
shown in the manual.  

I have traced the problem a little further -- I CAN cat a file to the printer
device (/dev/lp1).  But when I try to spool printouts to it, lpstat tells me
the device is waiting due to a timeout (or some such syntax).

Further digging led me to the file '/usr/spool/lp/logs/lpsched'.  That file
has lots of "exec of child process failed, no such file or directory" messages.
Aha!  But how to figure out what directory/file it wants???  If this were
SunOS, I'd do a "trace /usr/lib/lpsched" (lpsched doesn't exist in SunOS, but
I think you know what I mean).  I'd then be able to see what file is
being opened when that system call is exectued.  How can I do something 
like this in sysv??? 

... maybe it's time for a call to Esix Support -- they should be able
to tell me what generates that message anyway ...  I did do a 'strings' on
lpsched, and found the offending string, but know of no way to find out
where it get's the filename that it stuffs in the %s in the printf.

Thanks for any ideas on this.  'catting' files to the printer isn't the
best way to print files (especially if I need to print from vp/ix) :-)
-- 
Work:    heiser at tdw201.ed.ray.com
	 {decuac,necntc,uunet}!rayssd!tdw201!heiser
Home(1): bill%unixland.uucp at world.std.com -or- uunet!world!unixland!bill
	 Public Access Unix Coming Soon!
Home(2): Bill.Heiser at f240.n322.z1.fidonet.org (BBS: 1-508-655-3848)
Other:	 heiser at world.std.com     (Pub. Access Unix)