Re: .LIS files not being created properly?

[David Reaves <dreaves@SWBELL.NET>]

Scott,

This is probably way-off base, but any chance that the SQR is trying to
create a printer report for a non-supported device on the Unix system?
Have you tried using the command line options to change printer types?
Maybe the server-side SQR is checking something at the server, finding
it either not-installed or not correctly installed... maybe it's a
problem with a character set or an 8-bit control code.

Just guesses, but the best I can make.

dreaves@swbell.net

Seeley Scott wrote:
>
> > Hi all,
> > I have a problem that may be caused by a .LIS file not being created
> > properly.  This SQR report was written to work under PeopleSoft 6.0
> > and it runs FINE when run on the client (a Windows NT ascii file),
> > either through Peoplesoft or via SQR Workbench.  This same SQR was
> > then copied up to Unix (to run on the server), but it blows up there.
> >
> > KA-BOOM!
> >
> > Actually it's not that exciting.  There's no error message even, it
> > just runs to the end but never exits.  Stuck.  The Unix "kill" command
> > finally has to be used to stop the process.
> >
> > Wanna know exactly where the program hangs up?  Ahhh, good question.
> > A SHOW command was put on the line just before END-REPORT.  It shows
> > up in the sqr.log file - so we know the program is getting all the way
> > to END-REPORT but not actually ending.  Weird, huh?  I'm guessing that
> > the report runs, finishes, but when it tries to create the .LIS file
> > file just before exiting, it pukes and locks up for some reason.
> > Guessing.  This would make sense because when there's no print
> > statements (and therefore no .LIS file to create) it runs fine.
> >
> > By commenting out all the print statements on the Unix file,
> > everything runs peachy.  We can see from a tasty SHOW statements in
> > the SQR.LOG file that everything runs through the end.  But add back
> > one SINGLE print statement into the program, which we did - "print
> > 'please run, you miserable expletive' (+1,,)" - and it goes ka-boom
> > again.
> >
> > This SQR is very similar to at least 25 other SQR's running on the
> > same system, written by the same person over the past few months, and
> > using much of the same code.  This is the ONLY one that has problems.
> > And it only happens in Unix.  PeopleSoft and SQR Workbench runs the
> > SQR perfectly.  There are no control characters in it that we can
> > find.  Since the other SQR's run fine so it can't be a configuration
> > issue.
> >
> The only other clue we have:  when the print statements are in, the
> program also belches about halfway through the main select (returns 45
> rows out of the 72 it should have, then locks up).  The main select
> fires a print statement for every row returned.  When the print
> statements are rem'd out, the main select goes through all 72 rows, nice
> and clean.
>
> > Any ideas, anyone?  Our company is offering up a life-sized solid
> > chocolate llama to whoever has seen this before. (hey, it's better
> > than the year's suppy of canned squid I got for working so much
> > overtime last year...)
> :-)
> > Thanks,
> > Scott
> >
> >
> >