|
View previous topic :: View next topic
|
| Author |
Message |
Srinivasa Rao
New User
Joined: 21 Jun 2005
Posts: 75
|
|
|
|
Hi,
I am taking dump of few datasets and I am facing this message.
ADR411W (001)-DTDSC(04), DATA SET HSM.OCDS IN CATALOG CATALOG.VSYST01 ON VOLUME SYSN01 WAS NOT SERIALIZED ON REQUEST
I went through the manuals and as far as i understood problem is related to the VTOC of the dataset.
Could anyone please suggest how to resolve this problem. Do I need to uncatalog and then catalog the dataset HSM.OCDS on the new volume? |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
HSM control datasets should not really be touched by external backup / dumps.
They should only be processed by HSM iteslf with the use of HSM's internal CDS backup facility. This is very important as it keeps the HSM log in sync with the CDS backups.
Using external methods to backup these datasets can cause irreprible harm. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
the message is probably the consequence of using the TOLERATE(ENQFAILURE) parameter
anyhow I stand by expat in his recomendations..
unless You are undergoing some kind of dataset redistribution/reallocation
( but in this case HSM should not be up ) |
|
| Back to top |
|
|
Srinivasa Rao
New User
Joined: 21 Jun 2005
Posts: 75
|
|
|
|
Yes I used TOL(ENQF) parameter because of which the datasets were not dumped.
We will plan to bring down HSM to move a head.
Thanks a lot for you inputs. |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Are you trying to MOVE the CDS ?
If so, why is HSM still up.
Stop all HSM backup / migrate / restore / recall functions
Perform the HSM internal CDS backup
Bring HSM down
Move the dataset - I have always used REPRO to newname and then rename
Bring HSM up again |
|
| Back to top |
|
|
Srinivasa Rao
New User
Joined: 21 Jun 2005
Posts: 75
|
|
|
|
Yes we are trying to move CDS too.
HSM cannot be brought down as is used by production continuously.
Is there any way we take dump of HSM files when HSM is up? |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
To move a CDS in use by HSM you must bring down HSM to preserve the integrity of the CDS.
Think about it. You copy the CDS, HSM quite happily performs its functions during this copy using the original CDS, and you then flip the catalog to point to a CDS that does not have the updates recently performed.
If HSM needs to take a hit to perform this task, that is the end of the matter.
| Quote: |
| HSM cannot be brought down as is used by production continuously. |
Then I would seriously take a deep long look at your storage management policies. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| HSM cannot be brought down as is used by production continuously. |
You can plan a maintenance outage (even though undesirable) or you may have to deal with an unplanned crisis - which may cause an even longer downtime and/or loss of data.
Most management really resents crisis. . . . |
|
| Back to top |
|
|
|
|
