| Asset ID: |
1-72-1371320.1 |
| Update Date: | 2016-02-02 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1371320.1
:
VSM - IBM z/OS 1.12 and 1.13 May Cause FSC3BC8 Warm Boots Under High Workload
| Related Items |
- Sun StorageTek VSM System
- Sun StorageTek Host Software Component (HSC)
|
| Related Categories |
- PLA-Support>Sun Systems>TAPE>Virtual Tape>SN-TP: VSM
|
In this Document
Applies to:
Sun StorageTek VSM System - Version 4 to 5C [Release 4.0 to 5.0]
Sun StorageTek Host Software Component (HSC) for MVS and z/OS - Version 7.1 to 7.1 [Release 7.0]
Information in this document applies to any platform.
Symptoms
The VSM may experience FSC3BC8 warm boots. In certain situations under a heavy load, the potential for data integrity issues could exist.
Changes
Upgraded to IBM z/OS 1.12 or 1.13
Cause
In IBM release z/OS 1.12 the default block size for SAP pack dump tape records was increased to large block sizes (greater than 200K). This block size is more efficient when using physical tape drives but is less efficient when using virtual architectures.
On the StorageTek VSM product when the large block sizes are used in conjunction with very high combined workloads (front-end, back-end, staging and VTV deletes) it can expose a microcode deficiency in the VSM product. This problem is present in all microcode levels available today for the VSM product.
In IBM release z/OS 1.13 there may be some applications which use large block sizes for tape (real and virtual) and that do not allow the user to control or modify the default block size. Please note that as of the writing of this document Oracle has not yet announced official support of this OS.
Solution
Workaround:
The large block size default setting in z/OS 1.12 should be overridden when writing to a VSM product. It is recommended that a block size of 65520 (64K) be used to avoid this problem.
Fix:The fix for this problem is included in D02.14.32.00, H02.14.32.00 and higher levels of code.
Attachments
This solution has no attachment
