Hi,

Has anyone ever experienced the above message before? We get it
the first time and everytime we try to print a report which
references an Oracle table. The system appears to hang.

The way round it is to hit ctrl+brk then try it again, and
it works perfectly. Very strange!!!!

ProIV UK tell us that its something to do with the unix (solaris 2.6)LP
command which is setup in $SYSDEF. This appears to be the
case, but we cant think what could be causing it as there is
no change in the command from previous versions on this platform.

Any Ideas?

Thanks in advance
Chris.

What version? 4.0?

This message comes up normally when PRO-IV first attempts to connect to the Oracle DB - this occurs as soon as the first read attempt is made in a session, but (on VMS at least) doesn't happen again. I assume that the Oracle table you're using in this report isn't the only one you use?

What (exactly) is the lp default command set to in $SYSDEF? Is is different to lp -s -d? If you direct the print in $SPOOL to (for example) /dev/null, or a file, or CRT, does it still happen? (None of these use the lp command). As an example, you could work around the problem by printing to /tmp/{@TERM}, and then doing SYSTEM('lp -s -d {print_queue} /tmp/{@TERM} after the function is completed, which then bypasses PRO-IV's use of lp but has the same result (prints to the same printer).

If that gets rid of the problem, then PRO-IV may be right.

If not, then they're wrong and the problem is something else.

Hope this helps, keep us posted!

Cheers

Dan Shannon
GREYCELL SYSTEMS LIMITED

In response to Versions Etc, we use version 4r530 SL on
Sun Solaris.

I have found another caveat which does not support the LP command
theory. We get this message when we run an (U)pdate for the
first time aswell. It gets stranger and stranger.

As ever, CTRL+BRK then re-run immediately works fine.

Any more comments, suggestions most appreciated.

Regards
Chris.

Hi,

You say you use ctrl + break to stop the function. This implies that you are using the GUI Client.
Have you tried to run the report in green screen?

Glen

Hi Glen,

Yes, we do use the GUI and I have tried running the report in
green screen. We get exactly the same result, and also fix it
by hitting CTRL+BRK.
Cheers
Chris.