When running a Vtape IVP (installation verification) job, with Vtape configured to use P2P, the IVP 'reader' job fails to read data which was created and transmitted from the 'local' Vtape system to a 'remote' Vtape system, resulting in an IEC149I 813-04 error. Also, in the 'local' system from which the Vtape volume was created, messages such as the following were seen in the SVTnUT subtask:
SVT8TP654I RC=-2,0,TCP@TAKE,Connection from <Unknown?> Rejected, xx.yy.zzz.nn:vvvvv, SVT8:nnnn
SVT8TR205E RC=-8,104,P2P@SSRV,TAKE,,Cannot resolve RemoteSystem
Also, in the 'remote' Vtape, the following type of message was seen in the main SVTn task:
SVT8V4116E 0937 Unable to mount SCRTCH,2 remotes found but none accepted the connection
Vtape
A virtual IP address is being passed to Vtape when Vtape tries to resolve/obtain a physical IP address of a remote Vtape system (Vtape makes an internal service call to fetch the resolution of an address specified in Vtape parmlib which is specified as a mnemonic - not a 'hard' IP address).
The customer was able to resolve the problem by not having the test system do a lookup of hostnames using a HOST table, but instead use DNS to resolve addresses. In the error setup, Virtual IP addresses were being returned to Vtape, not the target ('NETSTAT') IP addresses.
As a bypass, the Vtape parmlib member which contains the P2P definitions can hard-code the physical IP address instead of using a 'mnemonic' address which require DNS lookup/resolution.