|
View previous topic :: View next topic
|
| Author |
Message |
Alan Playford
New User
Joined: 22 Aug 2012
Posts: 48
Location: UK
|
|
|
|
Any ideas how to find where IMBED and REPLICATE are stored in the catalog entry for a VSAM cluster?
We have a need to reproduce such clusters for testing out some platform conversion processes, but you cannot nowadays specify IMBED or REPLICATE (well, you can, but they get ignored! Even on EXPORT/IMPORT or DFDSS DUMP/RESTORE.)
My idea is to identify the bit settings where the catalog thinks these properties exist, and then somehow zap them to foolw the system.
Can this be achieved? |
|
| Back to top |
|
 |
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1335
Location: Bamberg, Germany
|
|
|
|
You can use for ex. IBM's supplied FINDIMBD Tool to identify existing REPLICATE, IMBED, KEYRANGE clusters and Migrate/Recall them. If you make a dump of of Catalog Cells before and after, you may be able to identify the Offsets where the information is stored.
However I do not recommend zapping the Catalog. |
|
| Back to top |
|
|
Alan Playford
New User
Joined: 22 Aug 2012
Posts: 48
Location: UK
|
|
|
|
Joerg,
Many thanks for taking the time but this useful utility only finds existing ones and upgrades them?
Our trouble is that the systems have moved on and we simply don't have any VSAM clusters with those attributes to work on any more?!
The problem comes with recreating such clusters so we can test our migration's recognition of them! :-) |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 734
Location: Denmark
|
|
|
|
| Just zapping those bit, assuming that there are some, would most likely render the cluster unusable. Remember that the physical index structure for IMBED and REPLICATE are totally different from a 'normal' cluster. |
|
| Back to top |
|
|
Alan Playford
New User
Joined: 22 Aug 2012
Posts: 48
Location: UK
|
|
|
|
A fair point, well made, Willy!
I had forgotten that, not having used such clusters for a decade.
Using EXPORT/IMPORT or DFDSS DUMP/RESTORE can remove the attributes but make the cluster unusable anyway, according to the manual?
A colleague reported that they had done this and it was readable, but I doubt that it was actually usable?
Looks like we'll have to do the actual testing on our Customer's site instead, as I can see no way for us to get one of these clusters on our system otherwise? |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 734
Location: Denmark
|
|
|
|
I agree that to will be best to do where you can actually test it. Perhaps offer a slight discount :-)
But if you only want to detect those options, what's wrong with IDCAMS LISTCAT? |
|
| Back to top |
|
|
Joerg.Findeisen
Senior Member
Joined: 15 Aug 2015
Posts: 1335
Location: Bamberg, Germany
|
|
|
|
| Willy Jensen wrote: |
But if you only want to detect those options, what's wrong with IDCAMS LISTCAT? |
It takes additional steps to process the output, while the latest FINDIMBD I know of uses the Catalog Search Interface. |
|
| Back to top |
|
|
|
|
