[Info-vax] CIFS under V8.4-2L1 - VSI CL

[Rod Regier]

On Tuesday, October 6, 2020 at 7:22:15 p.m. UTC-3, Craig A. Berry wrote:

> That could probably be remedied by disassembling the PCSI kit, modifying 
> the dependencies, and reassembling it. Sounds like work to me. Why not 
> just get the OS from VSI? It's the only game in town at this point anyway.

Can an end-user do those PCSI manipulations, or only the kit author?  VSI is the kit author.

My inhouse system running HPE V/A 8.4 also generates application binaries for HPE EDU license installed base HPE V/A sites.  Upgrade to VSI V/A is a no-go unless all of those downstream sites also upgrade.  We're hoping to get them to upgrade to Integrity servers running HPE V/I64 V8.4

In answer to a possible observation about HPE V/I64 life cycle:

My inhouse system running HPE V/I64 8.4 also generates application binaries for HPE EDU license installed base HPE V/I64 8.4 sites.  Upgrade to VSI V/I64 is a no-go unless all of those downstream sites also upgrade.

In answer to a possible observation about  HPE EDU license life cycle, my installed base sites still running those licenses will be encouraged to purchase permanent licenses for their system, which are still being open-ended offered by HPE leasing division.  (Current HPE EDU licenses expire on 01-Jan-2022 with no current prospect of any further offerings).