Has anyone seen this? When I run a report locally, it displays fine and gives me a normal message like:

0 NUMBER OF RECORDS IN TABLE= 133 LINES= 133
WebFOCUS Version 7.6.2 compiled and linked on Tue Jun 26 21:27:18 EDT 2007 (Gen branch762:130)

But when I run the same report up on the server, I get two blank lines at the top and the message says:

0 NUMBER OF RECORDS IN TABLE= 2 LINES= 2
ALPHANUMERIC RECORD NAMED SAVE
0 FIELDNAME ALIAS FORMAT LENGTH
RSTT_RMNTH_NAME E01 A7 7
RSTT_RMNTH_NAME E01 A7 7
TOTAL 14
0 NUMBER OF RECORDS IN TABLE= 133 LINES= 133
WebFOCUS Version 7.6.2 compiled and linked on Tue Jun 26 21:27:18 EDT 2007 (Gen branch762:130)

It looks like it's running two reports. Here's a simplified .fex I'm using to try to debug this:

ENGINE SQLORA SET DEFAULT_CONNECTION wmwp
SQL SQLORA EX reports.pk_walmart.load_dash_pos_table 'Rimmel';
END
TABLE FILE POS_TABLE
PRINT
WEEK_SALES
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE NOTOTAL
ON TABLE SET STYLE *
UNITS=IN,
SQUEEZE=ON,
ORIENTATION=PORTRAIT,
PAGECOLOR='WHITE',
$
TYPE=REPORT,
GRID=OFF,
FONT='ARIAL',
SIZE=9,
COLOR='BLACK',
BACKCOLOR='NONE',
STYLE=NORMAL,
$
ENDSTYLE
END

Any suggestions would be appreciated.
Thanks,
-Gregg

quote:

ENGINE SQLORA SET DEFAULT_CONNECTION wmwp
SQL SQLORA EX reports.pk_walmart.load_dash_pos_table 'Rimmel';
END

I'm no expert here, but the above code may be generating the message you see. In Report caster you see a lot more information than often displays on-line.

Ohhh, thanks Leah, that had me so excited, it really made sense! But that wasn't it:

Fex with SP call removed:
==============================================
TABLE FILE POS_TABLE
PRINT
WEEK_SALES
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE NOTOTAL
ON TABLE SET STYLE *
UNITS=IN,
SQUEEZE=ON,
ORIENTATION=PORTRAIT,
PAGECOLOR='WHITE',
$
TYPE=REPORT,
GRID=OFF,
FONT='ARIAL',
SIZE=9,
COLOR='BLACK',
BACKCOLOR='NONE',
STYLE=NORMAL,
$
ENDSTYLE
END

Still produces 2 blank rows and same message:
==============================================
0 NUMBER OF RECORDS IN TABLE= 2 LINES= 2
ALPHANUMERIC RECORD NAMED SAVE
0 FIELDNAME ALIAS FORMAT LENGTH
RSTT_RMNTH_NAME E01 A7 7
RSTT_RMNTH_NAME E01 A7 7
TOTAL 14
0 NUMBER OF RECORDS IN TABLE= 197 LINES= 197
WebFOCUS Version 7.6.2 compiled and linked on Tue Jun 26 21:27:18 EDT 2007 (Gen branch762:130)


Anyone have any other ideas I could try?
Thanks,
-Gregg

Have you tried adding -SET &ECHO='ALL'; at the very top of the program?

How do you run the report on the server? Is it in a BI Dashboard, MRE?

Here's what I get with ECHO:

0 NUMBER OF RECORDS IN TABLE= 2 LINES= 2
ALPHANUMERIC RECORD NAMED SAVE
0 FIELDNAME ALIAS FORMAT LENGTH
RSTT_RMNTH_NAME E01 A7 7
RSTT_RMNTH_NAME E01 A7 7
TOTAL 14
TABLE FILE POS_TABLE
PRINT
WEEK_SALES
ON TABLE SET PAGE-NUM NOLEAD
ON TABLE NOTOTAL
ON TABLE SET STYLE *
UNITS=IN,
SQUEEZE=ON,
ORIENTATION=PORTRAIT,
PAGECOLOR='WHITE',
$
TYPE=REPORT,
GRID=OFF,
FONT='ARIAL',
SIZE=9,
COLOR='BLACK',
BACKCOLOR='NONE',
STYLE=NORMAL,
$
ENDSTYLE
END
0 NUMBER OF RECORDS IN TABLE= 22 LINES= 22
WebFOCUS Version 7.6.2 compiled and linked on Tue Jun 26 21:27:18 EDT 2007 (Gen branch762:130)

The final product is a dashboard with four embedded reports, but I get the two lines no matter how I run the procedures. For this debugging I am simply clicking on the fex on the server in Dev Studio and hitting run.

Thanks,
-Gregg

Turn WFServlet and Procedure tracing on in each environment to capture what code is parsed and executed. Do not forget to turn tracing off again once you have finished!

If this is run via report caster (same report up on the server) then do you have a pre-process fex running before hand?

The additional message you are getting is as a result of running some code like this -

TABLE FILE [something]
BY RSTT_RMNTH_NAME
ON TABLE SAVE
END

Do you have code like this anywhere?

BTW, does it really matter that much? Or are you getting different report output as well?

T

It looks like something is being executed from edasprof or even earlier still in the processing logic (by means of wfs script files).
If you run it locally (on your own pc environment against your own private pc server, I assume) this does not happen, but when you run it an the production server then this does happen.
So it has to be something that is executed automatically before your procedure runs.
The fact that the set echo does not take effect until after the mysterious messages, seems to indicate that indeed something is executed first.
Maybe you systems administrator can shine some light on this issue.

I agree with GamP, something is running before your program, so it's most likely an INCLUDE or EXEC in edasprof.prf.

quote:

Originally posted by Tony A:
BTW, does it really matter that much?
T

It matters because the empty rows ruin the layout of the dashboard and look real amateur. I can't put it in production like this.

I'm going to see if I can copy the server's edasprof to my machine and recreate the phantom report locally.

Thanks,
-Gregg

Got it! It was this line in the edasprof:

SET LINES=9999

Commented that out and the two blank rows went away.

Thank you all for your help!
-Gregg

It's always the simple things that bite you.