|
View previous topic :: View next topic
|
| Author |
Message |
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
topic spitted in order to not disturb the original thread
ibmmainframes.com/viewtopic.php?t=38053&highlight=
Sorry if I entered in here wrong.
| enrico-sorichetti wrote: |
| having uncataloged dataset on sms controlled volumes |
Can we have uncataloged datasets on SMS controlled volume?
IBM Library says this
| Quote: |
| All system-managed data sets are automatically cataloged, even if you use a disposition of KEEP. |
So, this applies to creation. After that, can we uncatalog a dataset on SMS volume?
Please explain. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
Hi Gnanas!
You did not finish my sentence
| Quote: |
| ... is symptom of bad habits |
errors occurred and nobody cared about them  |
|
| Back to top |
|
|
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
Hi Enrico!
Thanks for kind your reply 
I read your sentence fully.
I conclude that datasets must be cataloged on SMS volume while creating. But, somehow some datasets may be cataloged... this is a bad habit...
I'm not sure how uncataloged dataset on SMS volume would be under control of SMS!!!
Or
uncataloged datsets on SMS volume are like non-SMS datasets??? 
Thanks, again. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
uncataloged dataset on sms managed volumes are ... errors
in ISPF option 3.4 try to uncatalog a sms managed dataset,
and You will see that Your request will be nicely refused |
|
| Back to top |
|
|
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
Yes, Enrico!
I got this error while trying to uncatalog a SMS managed dataset.
| Code: |
| Managed data sets cannot be uncataloged. |
Now My question is how there might be uncataloged datasets on SMS volume? I mean to ask what causes those errors ???
Thank you! |
|
| Back to top |
|
|
rahulbank
New User
Joined: 25 Sep 2008
Posts: 66
Location: Bengaluruuuuuu
|
|
|
|
I have come across datasets such as these and these are when datasets are deleted logically but not scratched or deleted physically from the volume.
FOr e.g. a gdg with no scratch option will not delete it from the volume but make it uncataloged when it egts rolled off.
Sorry from interrupting the chat but could not hold myself back.
Regards,
Storage Guy |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
Sorry, but I have to disagree,
quoting from somewhere on the net
With SMS, it is a requirement that all data sets be cataloged.
When a DGS is created at step start, it is cataloged in
DEFERRED ROLL-IN status. It is not part of the GDG until it
is rolled in as the result of CATLG at step termination. If
it is not to be scratched at when the LIMIT is exceeded, it will
be ROLLED-OUT.
when a generation is ROLLED OFF it disappears from the associations
but not from the catalog |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
Now i'm curious 
If sms requires all datasets be cataloged, how does a dataset become uncataloged and still remain on the system?
Bug in sms? Something with some shared catalog? Some low-level assembler code that makes marks in the vtoc but not the catalog?
Like i said - just curious. . . |
|
| Back to top |
|
|
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
I got this by GOOGLEing thru.
| Quote: |
| Uncataloged datasets on SMS volumes can occur, as a result of system failures, or an authorized program could have bypassed security and uncataloged them, or if you did a physical dump and restore of the volume: DFDSS/SDFSMSdss will restore a VSAM dataset in that case, but cannot catalog it and will give an ADR318I message to indicate that the data set "may" need to be cataloged (physical dumps do not preserve enough information about VSAM datasets to reconstruct the catalog entries). The last reference date should be the uncatalog date, since on an SMS managed volume the catalog should be consulted every time the data set is accessed. |
Please let me know if any point is wrong. |
|
| Back to top |
|
|
Gnanas N
Active Member
Joined: 06 Sep 2007
Posts: 792
Location: Chennai, India
|
|
|
|
Hi Dick,
| Quote: |
| If sms requires all datasets be cataloged, how does a dataset become uncataloged and still remain on the system? |
This might be the reasons...
| Code: |
We could end up with uncatalogued datasets after batch failures. A reasonably commom problem is restore failures on multi-volume datasets which leaves parts of uncatalogued datasets behind.
While we can not uncatalog a SMS dataset manually using normal processes, it is also easily possible to do it with IDCAMS DELETE - NOSCRATCH, which deletes the catalog entry, but leaves the dataset behind on disk.
It should be quite easy to run a monthly report to check the status of all SMS disks and identify all uncatalogued datasets. We can then decide if we want to catalog them up again, or delete them. |
|
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Also, the most obvious reason of all
| Quote: |
If RACF is installed, you must have access authority under RACF to specify NOSCRATCH. With proper authority, DELETE NOSCRATCH is allowed on SMS-managed VSAM and non-VSAM data sets, thus deleting the BCS entry in the catalog without accessing the VVDS or VTOC.
Attention DELETE NOSCRATCH can result in uncataloged SMS-managed data sets. |
|
|
| Back to top |
|
|
rahulbank
New User
Joined: 25 Sep 2008
Posts: 66
Location: Bengaluruuuuuu
|
|
|
|
| I agree with this reason have seen many also pointed the same in the loop. |
|
| Back to top |
|
|
|
|
