View previous topic :: View next topic
|
Author |
Message |
prem_ibm
New User
Joined: 15 Sep 2007 Posts: 31 Location: Chennai
|
|
|
|
Hi All,
Hope all of you will be in the best of Health and doing good...same as here...
1)My query is i have created one Data sets and Catlog it...after that i tried to Uncatlog the same data set by Giving DISP=(OLD,UNCATLG,DELETE),Job went fine with MAXCC=00 but still i am able to open that Data set in 3.4 without giving VOL=SER,as per the UNCATLOG difination it should not open Until unless we provide VOL=SER.
2) Even i tried to Uncatlog the data set from 3.2 Option by giving data set name in quotes & Vol serial.....getting Message Error AND When i removed the Vol ser getting Invalid Request...
Please suggest me on this...it seems basic query but i need proper Answer on this.Thanks
Thanks
Prem |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
You are probably not authorised to use DELETE NOSCR, and quite rightly so.
It gets to us storage people when some half brained numpty tries to uncatalog datasets and causes us problems. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
1. Why would you uncatalog a data set? Your site space management group will not look favorably upon this.
2. What did the JES output of the job say happened to the data set?
3. What "Message Error" are you getting when you attempt to uncatalog the data set from ISPF 3.2? |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Most possibly your site is SMS managed and, these days, most of the shops are. With SMS, UNCATLG is ignored for SMS-managed data sets and VSAM datasets, that means- KEEP is implied. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
Uncataloged datasets are not necessarily a bad thing. Sometimes they are necessary. I agree that uncataloged SMS datasets are a pain and should be avoided at all costs but non-SMS uncataloged datasets are a necessity in most larger sites |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
nevilh wrote: |
... but non-SMS uncataloged datasets are a necessity in most larger sites |
I agree but as an application developer I never had a time when I could need such a DSN. And when I needed, well, there was a good long list of question from the Suport-people...
I agree, if there is some "vendor information" which needs to be dispatched to some vendor via a tape-file why would I keep an entry of such a file in my user or system catalog. Well, having said that, the way original question is posed - I don't see the possibility, I just talked about. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Most often having uncataloged dasd datasets is for the system's people - not the application developers or users.
There are sometimes very large files that need to be "flip-flopped". Keeping both on dasd saves the time needed to run copies to get the data back onto dasd.
To the everyday processes, there is just "the dataset". When the "switch" is made, it is a simple uncatalog/re-catalog. |
|
Back to top |
|
|
|