BUG: (P0) We have not received the final documentation

[greidplatform]

Reviewing the final checklist of items it appears that we have not received the final version of the documentation that will accompany the release.

Specifically we have not seen the following:

1) Regular FLEXnet product documentation covering the vendors use of LM_SA_USE_EXTERNAL_FILTER

2) Regular FLEXnet product documentation covering the end-users use of the EXTERNAL_FILTER and EXTERNAL_FILTER_SERVER parameters.

3) Updated version of the partner documenation describing the connector APIs (Exhibit 1 from the contract has errors we have already highlighted).

Greg

[davidz]

We are not documenting the new options file settings in the FLEX end user documentation. These options file settings are only intended for configuration by partners, like Platform Computing. Therefore, their descriptions have (and will) only appear in the documentation we sent to you (Exhibit 1). Since this is the first time I've heard Platform express a desire for Macrovision to expose these settings to enterprise users in our documentation, can you explain why you would want this?

Today, we will give you an updated version of the Exhibit 1 documentation that will contain the following changes:
- Corrected description of what the publisher must change in lsvendor.c (this same description will also appear in the 10.8.1 release notes, then in the main reference documentation for all releases 11.0 or 10.9, if there is a 10.9 release; that is, we don't supply a revised reference manual for x.y.z releases, only for x.0 and x.y.0 releases, any changes introduced in x.y.z releases are described in the release notes and folded into the appropriate manual in the next higher-level release)
- Adding documentation for flxStatSetAttr()
- Updated example of how to call the filter functions that does not reference internal FLEX socket functions and has better comments
- Adding documentation for accessing the vendor daemon host name attribute

David

[greidplatform]

Release notes are an acceptable piece of the release documentation from our prespective which addresses issue #1 above and #3 should be resolved with the updates to "Exhibit 1".

For #2, the option file parameters are configured by the end-user and not by the partner (Platform). We would therefore expect such parameters to be noted in the "FLEXnet End User Manual:Chapter 5" which discusses all the option file parameters (or in the relevant release notes as per your explanation).

So the question of why to document comes down to a) it's an end user parameter for them to configure and use and b) it provides a level of confidence to the end user that this is a support functionality of FLEXnet (rather than relying on Platform's word on it).

#1 and #3 were obviously our more pressing concerns so #2 maybe not be a showstopper as we certainly expect all earlier adoptors to be working very closely with us.

But we would like to see some agreement on this going forward.

Greg