MVSFORUMS.com

[callanand]

Hi All,

I have around 100 vsam files. The definition of these vsam files have index parameters as IMBED and REPLICATE from its previous definition. Since these parameters are now no longer supported for Z/OS v1.8 and higher, we need to get rid of these parameters before upgrading our OS. Can you please let me know if Alter command would work in this case or do I need to copy delete and redefine these datasets again.

Thanks

[jsharon1248]

I think you're out of luck. IMBED and REPLICATE change the physical characteristics of the VSAM data and index datasets. The ALTER only allows certain modifications, and IMBED and REPLICATE are not on that list. There might be utilities to assist with this task, and there might be something delivered with the upgrade to v1.8, but you're not going to be able to use ALTER.

[warp5]

Imbed and replicate are not supported, but they are tolerated, from what I know you do NOT HAVE to replace them, even though you should.
Take a look at these links:
http://www-1.ibm.com/support/docview.wss?uid=isg1II13894
http://www-1.ibm.com/support/docview.wss?uid=isg1OA10952
http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.e0zm100/vsamirk.htm

[callanand]

Thanks a lot Warp5. We are actually upgrading our OS to 1.9 and this conversion is mandatory. The export and import works brilliantly. This is because Export and Import besides copying data also takes in account the catalog information. Thanks for this.
But it does not work for empty VSAM files as there is no data to be copied to the temporary PS file. How do we change the IMBED and Replicate parm for empty VSAM files.
Thanks a lot for your help.

[Nic Clouston]

Delete and redefine with updated control cards
_________________
Utility and Program control cards are NOT, repeat NOT, JCL.

[warp5]

I do not know where you got your information, but these are quotes from the teleconference "Plan your migration to z/OS V1.9!"

Functions Planned to be Withdrawn after z/OS R10 and in the future...

Support for VSAM data sets with IMBED and REPLICATE attributes from DFSMS

In a future release of z/OS, when DFSMShsm or DFSMSdss recalls or restores a VSAM data set with either IMBED or REPLICATE attribute or both, the attributes will be removed. No supported release of z/OS allows you to define new VSAM data sets or catalogs with the IMBED or REPLICATE attributes, and using them for existing data sets can waste DASD space and can often degrade performance. IBM recommends that you stop using these attributes.
For information about how to detect IMBED and REPLICATE attributes on existing data sets and catalogs, refer to INFO APAR II13894.

[warp5]

And hier is the statement taken out of the z/OS 1.9 Migration which I am reading right now.

Redefine existing VSAM data sets that contain the IMBED, REPLICATE, and KEYRANGE attributes Description: No supported release of z/OS honors the IMBED, REPLICATE, and KEYRANGE attributes for new VSAM data sets. In fact, using these attributes can waste DASD space and often degrades performance. Servicing these VSAM data sets has become increasingly difficult. In some cases, unplanned outages have occurred. For these reasons, IBM recommends that you stop using IMBED and REPLICATE, and that you minimize or eliminate your use of KEYRANGE. IMBED and REPLICATE were intended as performance improvements and have been obsoleted by newer, cached DASD devices. Striped data sets provide much better performance than KEYRANGE and should be viewed as a candidate for any existing KEYRANGE data sets.
Element or feature:
DFSMSdfp.
When change was introduced:
The recommendation to migrate from IMBED, REPLICATE, and KEYRANGE was originally made in the z/OS V1R6 timeframe.
Applies to migration from:
z/OS V1R8 and z/OS V1R7.
Timing:
Before installing z/OS V1R9.
Is the migration action required?
No, but recommended to avoid degraded performance and wasted DASD space.