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.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
The report is developed in multistep Step1: Detail data is retreived and hold in file temp A with format ALPHA Step2: Subtotals are appended to temp A at various level Step3: Grand total is appended to temp B at higher level
The code was running and generating the data till some time.
Now there is a strange issue. Detail section is not appearing for few levels. When we analysed the hold file data after taking detail data, found that few column values are stored as blank in the hold file. But detail data is printed (TABLE FILE TEST) directly from the required table which is used to hold in TEMP A is showing data for all columns, there are no null values.
We tried changing the fromat ALPHA to BINARY, Report o/p is looking fine. Detail section is appearing for all levels.
Please let us know ALPHA vs BINARY. Why change in format to BINARY is making our code to work?
There is no difference between Alpha and Binary format with regard what is stored the difference is how it is stored.
Changing from Alpha to binary should not affect the output in any way.
Normally binary is the format that should be used for hold files the exceptions to this are when you want the file to be used by a –READ or as input into another process that requires Alpha data.
Typically the effect you are seeing is caused when the multiple holds are not the same which means that the master and data file are invalid.
For example
SET HOLDLIST = PRINTONLY FILEDEF SOURCE DISK SOURCE:FTM (APPEND -RUN TABLE FILE CAR PRINT MODEL/A25 BY COUNTRY WHERE COUNTRY EQ 'ENGLAND' ON TABLE HOLD AS SOURCE END -RUN TABLE FILE CAR PRINT MODEL/A25 BY COUNTRY WHERE COUNTRY EQ 'W GERMANY' ON TABLE HOLD AS SOURCE END -RUN
Will give you a file that works perfectly
However add another step
-RUN TABLE FILE CAR PRINT MODEL BY COUNTRY WHERE COUNTRY EQ 'ITALY' ON TABLE HOLD AS SOURCE END -RUN
Will give you an invalid data file and master because the format of MODEL is A24
I suspect that this is the issue and not the HOLD FORMAT
Data types are not issue in our code as while appending we had taken care of the data type. If data type is an issue, it should fail for all detail data. But it is failing only for few records, not for all.