As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Moving forward, myibi is our community platform to learn, share, and collaborate. We have the same Focal Point forum categories in myibi, so you can continue to have all new conversations there. If you need access to myibi, contact us at email@example.com and provide your corporate email address, company, and name.
Here is how I'm building my report: TABLE FILE HOLD001 PRINT HOLD001.HOLD001.PERCENTAGE AS '' BY LOWEST HOLD001.HOLD001.EmployeeName AS '' ACROSS LOWEST HOLD001.HOLD001.K_BUSN_WK_END_DT AS '' ON TABLE SET PAGE-NUM NOLEAD ON TABLE NOTOTAL ON TABLE PCHOLD FORMAT HTML ON TABLE SET HTMLCSS ON ON TABLE SET STYLE * INCLUDE = IBFS:/EDA/EDASERVE/_EDAHOME/ETC/endeflt.sty, $ ENDSTYLE END
It's creating a row in the table for every row in the hold file. But I want it to write 1 row per person and put in the percentages with each of the corresponding dates. The amount of dates coming will be variable for every run.This message has been edited. Last edited by: <Emily McAllister>,
The funky results were probably because you used PRINT instead of SUM.
There's a SET command that's used with PRINT and ACROSS called ACROSSPRT:
The ACROSSPRT parameter reduces the number of report lines within each request that uses the PRINT command and an ACROSS phrase.
The PRINT command generates a report that has a single line for each record retrieved from the data source after screening out those that fail IF or WHERE tests. When PRINT is used in conjunction with an ACROSS phrase, many of the generated columns may be empty. Those columns display the missing data symbol.
To avoid printing such a sparse report, you can use the SET ACROSSPRT command to compress the lines in the report. The number of lines is reduced within each sort group by swapping non-missing values from lower lines with missing values from higher lines, and then eliminating any lines whose columns all have missing values.
Because data may be moved to different report lines, row-based calculations, such as ROW-TOTAL and ACROSS-TOTAL in a compressed report are different from those in a non-compressed report. Column calculations are not affected by compressing the report lines.
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server