Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Dataset catalog problem.

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
Srinivasa Rao

New User


Joined: 21 Jun 2005
Posts: 75

PostPosted: Tue Feb 12, 2008 3:53 pm    Post subject: Dataset catalog problem.
Reply with quote

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
View user's profile Send private message

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Tue Feb 12, 2008 4:56 pm    Post subject:
Reply with quote

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
View user's profile Send private message
enrico-sorichetti

Global Moderator


Joined: 14 Mar 2007
Posts: 10256
Location: italy

PostPosted: Tue Feb 12, 2008 5:04 pm    Post subject: Reply to: Dataset catalog problem.
Reply with quote

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
View user's profile Send private message
Srinivasa Rao

New User


Joined: 21 Jun 2005
Posts: 75

PostPosted: Tue Feb 12, 2008 5:14 pm    Post subject:
Reply with quote

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
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Tue Feb 12, 2008 5:18 pm    Post subject:
Reply with quote

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
View user's profile Send private message
Srinivasa Rao

New User


Joined: 21 Jun 2005
Posts: 75

PostPosted: Tue Feb 12, 2008 5:24 pm    Post subject:
Reply with quote

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
View user's profile Send private message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Tue Feb 12, 2008 5:32 pm    Post subject:
Reply with quote

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
View user's profile Send private message
dick scherrer

Site Director


Joined: 23 Nov 2006
Posts: 19270
Location: Inside the Matrix

PostPosted: Tue Feb 12, 2008 9:55 pm    Post subject:
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Fileaid 2 commands instream work. In ... descann Compuware & Other Tools 2 Tue May 16, 2017 3:31 pm
No new posts To find out size allocated to a seque... ashek15 JCL & VSAM 15 Thu Apr 27, 2017 9:42 am
No new posts LISTCAT on a dataset with symbolic pa... shreya19 JCL & VSAM 5 Fri Apr 07, 2017 5:43 pm
No new posts Strings with double quotes having pro... raja Arumugam All Other Mainframe Topics 11 Thu Mar 30, 2017 10:34 am
No new posts Unable to catalog a gdg dataset resid... Shovan JCL & VSAM 7 Fri Mar 24, 2017 2:24 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us