You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've ran into some hot water with a recent breaking change on Hercules, around the 4.6 mark; this change has seemingly broken PVM. I have tested the following configurations of PVM and found that SOME work:
PVM 2.1 (1993):
VM/SP 5
VM/SP 6
VM/HPO 4.2
VM/HPO 5
VM/ESA 1.1.1 (370)
VM/ESA 1.2.2
VM/ESA 2.1.0
PVM 2.1 (1998):
VM/ESA 2.4.0
z/VM 4.2
z/VM 4.4
z/VM 5.3
z/VM 6.2
z/VM 6.3
z/VM 6.4
z/VM 7.1
Specifically, VM/ESA 2.4 (my hub node) can talk to any not-XA+ VM (so, any 370-type VM). This behavior seems to be correct -- I can have any non-XA version of VM talking to any other non-XA version of VM or an XA version of VM, but, two XA versions of VM cannot talk to each other. There are no protocol differences between the different versions of PVM I used -- I only used different versions to try to gain more "period-accurateness" since I am somewhat lacking in different versions of PVM (I only have 5 versions, 2 of which cannot talk to the other 3). I think this may be related to this issue here: #640 I recall being able to revive the links in the past by recreating the devices, but, it was not a permanent fix.
Version info:
HHC01413I Hercules version 4.7.0.11119-SDL-gf7d2360a
HHC01414I (C) Copyright 1999-2024 by Roger Bowler, Jan Jaeger, and others
HHC01417I ** The SDL 4.x Hyperion version of Hercules **
HHC01415I Build date: Jul 2 2024 at 15:01:43
HHC01417I Built with: GCC 13.2.1 20230801
HHC01417I Build type: GNU/Linux x86_64 host architecture build
HHC01417I Running on: server1 (Linux-6.6.8 x86_64) MP=32
HHC01417I Built with crypto external package version 1.0.0.52-ga5096e5
HHC01417I Built with decNumber external package version 3.68.0.102-g3aa2f45
HHC01417I Built with SoftFloat external package version 3.5.0.105-g4b0c326
HHC01417I Built with telnet external package version 1.0.0.63-g729f0b6
The link devices are defined as such, for example:
Hi folks,
I've ran into some hot water with a recent breaking change on Hercules, around the 4.6 mark; this change has seemingly broken PVM. I have tested the following configurations of PVM and found that SOME work:
PVM 2.1 (1993):
PVM 2.1 (1998):
Specifically, VM/ESA 2.4 (my hub node) can talk to any not-XA+ VM (so, any 370-type VM). This behavior seems to be correct -- I can have any non-XA version of VM talking to any other non-XA version of VM or an XA version of VM, but, two XA versions of VM cannot talk to each other. There are no protocol differences between the different versions of PVM I used -- I only used different versions to try to gain more "period-accurateness" since I am somewhat lacking in different versions of PVM (I only have 5 versions, 2 of which cannot talk to the other 3). I think this may be related to this issue here: #640 I recall being able to revive the links in the past by recreating the devices, but, it was not a permanent fix.
Version info:
The link devices are defined as such, for example:
The device was initialized with
CP SET RDEVICE 441 TYPE CTCA
beforehand, though the autosense detects the correct device type.The text was updated successfully, but these errors were encountered: