Re: SQR Error Message 6004

[John Milardovic <milardj@SX.COM>]

I apologize for the last post I pressed the send button instead of the print
button.

Thanks for replying Clark, but I am left more confused then before.  If the
spf file is getting corrupted when forked from the C program why is it not
being corrupted when run from the command line?  Why are the other 18+-
reports working fine (they all share a common library for determining output
file names/format options)?  One of the reports that is getting an error is
99% identical to another report (the differences are the tables being
accessed and minor differences in the heading) the almost identical report
runs fine.

In regards to printing the file prematurely the C process only creates the
output it doesn't place it in the print queue.

Any ideas would be appreciated.

John Milardovic

Oracle 8
SQR 402
AIX - UNIX

> -----Original Message-----
> From: the dragon [SMTP:ceprn@HOTMAIL.COM]
> Sent: Thursday, December 16, 1999 11:53 AM
> To:   SQR-USERS@list.iex.net
> Subject:      Re: SQR Error Message 6004
>
> John,
>
> According the the SQR Language reference manual, P 403, (A manual *anyone*
> working with SQR needs to have, in addition to the User's manual and SQR
> for
> Peoplesoft and other applications), a 6004 error is:
>
> Encountered unknown SPF code (`01) while reading the printer file.
> Possibly the file got corrupted.  Try to recreate the .SPF file.  If the
> error persists contact customer support. `01 = Unknown SPF Code.
>
> Maybe you're trying to print it before it finishes??
>
> clark 'the dragon' willis
>
>
> ----Original Message Follows----
>
> Hello.
>
> Has anyone ever encountered SQR Error 6004?  I am getting this error
> ('Encountered unknown SPF code (0) while reading the printer file') when
> running two of my reports from a C program which forks off SQR reports.
> If
> I run the reports manually from the command line there is no error.
>
> I did a search of the archives and learned that error codes 6000-6002 are
> related to file permissions/file locking - does anyone know what 6004 is
> related to?  My first thought was that it was a locking problem (two
> reports
> both trying to lock the same tmp file - I use a tmp file to flush the SQR
> buffer) but the problem only happens with two specific reports out of 20
> (all of which are using the same tmp file - the tmp file is never actually
> created ie nothing is printed while the tmp file is the active output
> location).  I wrote two test SQR's which opened the same tmp file (using
> new-report)  and I didn't have a problem so that kind of shot down my file
> locking theory.
>
> Any help (or nudge towards the correct resource) would be much
> appreciated.
>
> John Milardovic
>
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com