Hi All,
i would like to know the Differences between 7.1.3 and 7.1.5.

please let me know if any one have worked on this new version.

thanks,
Kalyan

This message has been edited. Last edited by: kalyanswarna,

We had some issues with 7.1.3 that seem to be resolved in 7.1.5. Mainly with Prompting for variables. We are waiting on one more Fix to address a SAP BW issue...that would not apply to everyone...and will be going to production with 7.1.6.

We had an issue with the 7.1.3 Reporting Server. We pass the MRE ID from the client to the Reporting Server so we can see who is running reports on the Reporting Server Console. We use service accounts to authenticate to data sources and the Reporting Server was passing down the MRE ID all the way down to the data source trying to authenticate with it rather than the service accounts we have built in. This was fixed in 715.

Does anyone know if the 'variable-length' problem has been corrected or addressed in 7.14? This was a topic on an earlier post (What do you think about WebFOCUS 7?), but was wondering if anyone has a fix for this other than recode or knows if it was fixed in 7.14.

Basically, when migrating from 533 to 713, we discovered that many of the DB2 alpha fields were being treated as variable-length, whereas they were NOT in previous versions. So, MFDs were generated with the variable format, SQL passthru collected data with variable format, etc.

Example: Here's a HOLD file from 5.33

NAME E01 A64
NICKNAME E02 A35

...same code, HOLD file from 7.13

NAME E01 A64V
NICKNAME E02 A35V

This caused all kinds of havoc with 'downstream' calculated fields (DEFINEs and COMPUTEs) where the older code did not account for the variable length. For example, the errors encountered were:

- MORE, MATCH and JOIN errors - (FOC957) FORMAT MISMATCH FOR THE FIELD: EXTDESC
- DECODE error - (FOC272) FORMAT ERROR IN DECODE OR FILE ELEMENT: 015

This variable length problem also seemed to have an effect on SAVE files, where fields where held with longer lengths then what they were declared. Here, it 'jumps' from 32 to 38:

Field Alias Format Length
5.33 - UPDATEUSER UPDATEUSER A32 32
7.13 - UPDATEUSER UPDATEUSER A32V 38

This REALLY effected our -READs as we had to accomodate for the extra length.

The DBAs were unaware of anyway to declare the field other than varchar to WF, so we had quite a little bit of a surprise when we tested with 7.13!

Anyway, just wondering if anyone had heard anything, or if WF has a 'setting' to ignore the 'variable' part of a varchar declaration.

ADD
ENGINE DB2 SET VARCHAR OFF to the server profile

Thanks, Prairie. Will pass this along to the WF Administrator and regen the MFDs. Let you know!

Currently only the 7.1.5 Reporting Server is available. When will the 7.1.6 client be available ??

Adolf,

Your best bet for this information would be to contact the local support on 0845 658 8181. I am sure that they will find out for you and let you know!

T

Hi Adolf and all,

Have you got a chance to contact the local support in England as Tony suggested (many thanks to Tony for your kind direction )?

From what I know, WebFOCUS 7.1.5 is server-only with improvements on performance issues in active reports. The most current version of WebFOCUS client componenet is 7.1.4.

The next release of WebFOCUS client, 7.1.6., is estimated to be available in the coming November.

The following docs/manuals on new features may be of interest as well:

Technical Memo 4640: HTML Active Report (AHTML) Enhancements 7.1.5

Technical Memo 4632: Application Server Only Deployments of WebFOCUS 7.1.4 & higher

WebFOCUS / iWay New Features 7.1.3

Hope this helps.

Cheers,

Kerry

1.) What are the differences between 7.1.6 and 7.6?

2.) Kerry - you mentioned November for 7.1.6. Is there anything further on dates?