We tried once again to install z/VM 5.2 this last weekend and had to fall back. This time, it was because the PAV SPE, included in the latest RSU, changed the initialization of the SHARK controllers from 3990 to native. Because of this, software that is critical for TPF shops, VPARS and VTAPE from VSSI, could not even start due to command rejects on ccws such as define extent and set sector. Of course, this behavior did not exhibit itself when running 2nd level under z/VM 4.4 due to the fact that the offending code is not included in that CP.
My questions are 1. Was PAV support offered separately prior to being included in the RSU? 2. Was it ever tested in a TPF shop? One using the VSSI products? 3. Is this change documented somewhere? 4. Were the partners creating software for VM informed of the change? Regards, Richard Schuh
