APAR status
Closed as fixed if next.
Error description
When cloning a guest from a guest/prototype, if the source guest has a large minidisk - a mod54 for example that is defined to use most or all of that volume by defining as x-END, it may fail in the middle of the copy and therefore cause the clone to fail: API call returned RC: 8 ... Copy failed with RC: 8 ... BTS Workunit: Clone z/VM Guest xxxxx, Request: Clone MDISK from xxxxx (WN2V) xxxx to xxxxx (WN2V) xxxxSize: xxxxx Cyls ended ... The logs from this timeframe will contain: ... 11/11/2015 11:38:27 com.CSL.WAVE.BTS.Services.BTSMasterService$2 11/11/2015 11:38:27 Service Machine : Send command SM_DDR_COPY parms xxxxxxxxx 11/11/2015 11:38:27 com.CSL.WAVE.BTS.Services.BTSMasterService$2 11/11/2015 11:38:27 Service Machine : Read answer for SM_DDR_COPY ... 11/11/2015 12:08:27 com.CSL.WAVE.BTS.Services.BTSMasterService$2 Communication error caused by: java.net.SocketTimeoutException: Read timed out .... Impact: Fails to clone the source guest to a new guest.
Local fix
If the minidisk definition is changed from x-END to x-(actual ending address), the SMAPI interface gets used instead of the internal processing to handle 'END' - and the copy will succeed without timeout. So for a mod54 - x-END should change to x-65520.
Problem summary
When cloning a guest from a guest/prototype, if the source guest has a large minidisk that is defined to use most or all of the volume by specifying x-END, it may fail in the middle of the copy and cause the clone to fail. This is due to a hardcoded timeout value that is too low to accomodate the copy. This defect is resolved in a future release of the product.
Problem conclusion
Temporary fix
See the Local Fix.
Comments
APAR Information
APAR number
LI78901
Reported component name
WAVE FOR Z/VM
Reported component ID
5648AE101
Reported release
120
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-01-13
Closed date
2016-01-13
Last modified date
2016-01-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R120 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"120","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
13 January 2016