Posted: Thu Oct 09, 2014 4:04 pm Post subject: DFSDUMP ADRDSSU backup performance idea
Hi,
We have a jcl which basically do re-org the vsam dataset.
i.e take copy of vsam file into flat file using idcams
delete define the vsam file and copy back the backup to vsam
This process is taking 1234 cpu seconds
I changed this to ADRDSSU dump, it took only 60 cpu seconds to backup but took 306 cpu seconds to copy back again to vsam file.
Question :
1. Whether this ADRDSSU, will actually re-org the file or it will copy back the file again in same format ? in other words, this delete define we do is for re-org the vsam dataset, will adrdssu solve the purpose, i.e will it re-org the vsam file when copied back again ?
2. For taking backup it took 60 cpu second, but for putting back it took 306 cpu seconds. Any way to optimize it ?
Joined: 26 Nov 2002 Posts: 12377 Topics: 75 Location: San Jose
Posted: Thu Oct 09, 2014 8:51 pm Post subject: Re: DFSDUMP ADRDSSU backup performance idea
Magesh_J wrote:
1. Whether this ADRDSSU, will actually re-org the file or it will copy back the file again in same format ? in other words, this delete define we do is for re-org the vsam dataset, will adrdssu solve the purpose, i.e will it re-org the vsam file when copied back again ?
2. For taking backup it took 60 cpu second, but for putting back it took 306 cpu seconds. Any way to optimize it ?
Magesh_J,
1. You don't seem to have ALLDATA and ALLEXCP parms on your Dump dataset.
I suggest you add a step to delete the vsam cluster before you restore. Actually it can be done on the DUMP command itself.
2. VSAM data sets cannot be renamed during a physical data set restore. If a data set is preallocated with the new name, it is not restored. If a data set is not preallocated, it is restored using the old name. This keyword only applies to movable data sets; therefore, unmovable data sets will not be renamed. RENAMEUNCONDITIONAL is not supported for VSAM data sets during a physical data set restore.
3. You might also need to specify SPHERE on your RESTORE too. _________________ Kolusu
www.linkedin.com/in/kolusu
There are number of delete/insert/re-write opertation are being done in those files. Which inturn results in fragmentation of data. To de-fragment it we need re-org.
I will post the LISTALL, May i know, what parmater you are intrested in that.
May times the idea of "reorging" a VSAM KSDS is left over from the time when CI/CA Splits were problematic for performance of the dataset.
If you have a considerable number of deletes, and the space available from that is not going to be used by new inserts, then that is a reason to do it, but just wondering
Joined: 26 Nov 2002 Posts: 12377 Topics: 75 Location: San Jose
Posted: Mon Oct 13, 2014 11:40 am Post subject:
Magesh_J wrote:
Thanks Kolusu,
I am adding the paramater ALLDATA and ALLEXCP, Please advise how to delete those file in the same step.
Also please advise, Whether the restore will do a Re-org or not.
The purpose of this JCL is only for Re-organzing the file.
Thanks
Magesh
DUMP has a parm called DELETE but is NOT valid for VSAM Clusters. So you have delete it using IDCAMS.
Magesh_J wrote:
There are number of delete/insert/re-write opertation are being done in those files. Which inturn results in fragmentation of data. To de-fragment it we need re-org.
z/OS 2.1 has a new feature called CA RECLAIM which will
• Detects Empty CAs
• The empty CAs are removed from the active index structure and moved to free chains
• Uses the empty CAs when needed before using new CAs
• Reduces or eliminates reorgs in support of 24x7 operations
• Applications that use VSAM key-sequenced data sets (KSDS) can benefit from improved performance, minimized space utilization, and improved application availability
• Performance improvements are anticipated for many applications using CICS®, VSAM, VSAM RLS, IMS™ VSAM, and Catalog processing
Thanks for the kind advice,
Right now it is 2 days after Re-org, the number of deletion of records are less, This is a weekly process, I will get this Liscat before weekly job run, we will have exact data.
Looks like it was available from z/OS V1R12.0 itself. You should be able to use it when you get to V1R13. _________________ Kolusu
www.linkedin.com/in/kolusu
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum