|
View previous topic :: View next topic
|
| Author |
Message |
hossy
New User
Joined: 28 Jul 2018
Posts: 2
Location: Japan
|
|
|
|
| Hi! We co-existing z/OS V2.1(z13) and z/OS V1.10(z196) environment. We would like to use zEDC compression function on z/OS V2.1(z13), and would like to share this disk from z/OS 1.10(z196) using DFSMSDSS logical volume dum. Is this possible? For example, we applying PTF(APAR) DFSMSDSS on z/OS V1.10. How to share the zEDC disk volume between z/OS v2.1 and old z/OS V10? |
|
| Back to top |
|
 |
Nic Clouston
Global Moderator
Joined: 10 May 2007
Posts: 2454
Location: Hampshire, UK
|
|
|
|
| This was an interview question? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8700
Location: Dubuque, Iowa, USA
|
|
|
|
From the Redbook Reduce Storage Occupancy and Increase Operations Efficiency with IBM zEnterprise Data Compression (SG24-8259) :
| Quote: |
1.3.2 Coexistence
For systems that do not support the zEDC Express feature, but have z/OS V2.1, z/OS V1.13, or z/OS V1.12 installed, it is possible to access a zEDC Express compressed-format data set.
In this case, compressed data is read from data sets and decompressed using software algorithms. New data being written is not compressed.
OpenPGP packages can be accessed with any industry-standard tooling.
The following list describes the coexistence requirements:
z/OS V1.12 and z/OS V1.13 PTFs for authorized program analysis report (APAR) OA41156. This PTF is needed for the systems to tolerate the new SMFPRMxx keywords, and to enable the IFASMFDL SOFTINFLATE keyword and software decompression support.
For z/OS V2.1, any IFASMFDL job needs to specify a region size of 4 megabytes (MB) or greater. This is needed because IFASMFDL has been enhanced to use multi-block logstream browsing. |
There is no indication of V1.10 support -- so if you use zEDC, you will NOT be able to access that data from a 1.10 LPAR.
IBM tells you it is not possible. |
|
| Back to top |
|
|
hossy
New User
Joined: 28 Jul 2018
Posts: 2
Location: Japan
|
|
|
|
Thank you for your quick reply.
I also read the redbook and zEDC supported version matrix.
Is this possible the following alternative solution.
On z/OS v2.1, the zEDC enabled part is separated from the zEDC disabled part using SMS storage class.
Is this possible? I think that this is possible from redbook.
If this is possible, both z/OS 2.1 and 1.10 can read the zEDC disabled storage class part with sharing, and almost of disk volume parts on z/OS 2.1 set up zEDC environment without sharing. |
|
| Back to top |
|
|
|
|
