one of our jobs is creating a temporary dataset with the following parameters :
DISP=(NEW,CATLG,DELETE),
UNIT=SYSDA,
SPACE=(TRK,(50,10),RLSE),
DCB=(RECFM=FB,BLKSIZE=0,LRECL=615)
But now it's required to store the dataset permanently.
with minimum changes i have to do this.
Joined: 29 Jun 2006 Posts: 1436 Location: Bangalore,India
Prabhu,
Quote:
one of our jobs is creating a temporary dataset with the following parameters :
DISP=(NEW,CATLG,DELETE),
UNIT=SYSDA,
SPACE=(TRK,(50,10),RLSE),
DCB=(RECFM=FB,BLKSIZE=0,LRECL=615)
Could you post the entire DD statement declaration.
I did not understand the issue ... Howevr, If u want a permanent dataset just give a dsn name ... If the issue is something else plz write in detail ...
Now the dataset is being stored temporarily on DASD, means after few days it is getting deleted automatically. so for the next subsequent job which access this dataset (which will run after some days), this dataset is not available.
But we want to keep the dataset permanantly without getting deleted automatically.
For that can I use the UNIT parameter as UNIT=PERMDA.
Apart from this change , what changes should I do.
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
Hi,
I do not know what is UNIT=PERMDA, can you please tell me for what this parameter is?
I know about one parameter known as Management class, which is responsible for deletion or 'storage' of some DSN.
For an SMS-managed data set (one with a storage class assigned), the system handles the migration and backup of the data set based on the attributes defined in the management class for the data set.
In many cases, the attributes defined in the management class selected by an installation-written automatic class selection (ACS) routine are sufficient for the data sets you create with DD statements. However, you can specify the name of a management class on the MGMTCLAS parameter for a new SMS-managed data set. (Note that an ACS routine can override the management class that you specify.)
The storage administrator at your installation defines the names of management classes and their attributes. To view a list of management class names and their attributes, use the Interactive Storage Management Facility (ISMF).
Joined: 29 Jun 2006 Posts: 1436 Location: Bangalore,India
Prabhu,
Quote:
In many cases, the attributes defined in the management class selected by an installation-written automatic class selection (ACS) routine are sufficient for the data sets you create with DD statements. However, you can specify the name of a management class on the MGMTCLAS parameter for a new SMS-managed data set. (Note that an ACS routine can override the management class that you specify.)
I support Anuj. Before you apply the parameter what Anuj had suggested, speak with your local STORAGE team. There should some reason for assiging the present management class to your dataset.
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
Quote:
However, you can specify the name of a management class on the MGMTCLAS parameter for a new SMS-managed data set. (Note that an ACS routine can override the management class that you specify.)
Too right the ACS routines can override the user specification of MGMTCLAS. Always the case in a shop where I've set up SMS.
Us storage guys ALWAYS know best - That's why we are the storage guys
I would like to mention you all that, Once If you mention DSN as temporary and DISP=(NEW,CATLG,DELETE), The system itself will correct the DISP parameter as PASS and thats the propety of temporary dataset, I mean logical dataset not a physical one. Hence You cannot store it or catlg it any more after job complete. Its a system controlled dataset.
Instead of temporary dataset, make it as physical I mean don't use '&' while Giving DSN. You can catlg or keep or delete it depends on requirement.
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
Hi Hemantha,
I got some queris to ask from your reply,
1.
Quote:
Once If you mention DSN as temporary and DISP=(NEW,CATLG,DELETE), The system itself will correct the DISP parameter as PASS and thats the propety of temporary dataset
Intresting concept, from where did you get this information, please direct me to some link. My question is, how the system distinguish between the DDs to understand that 'which DD' is meant for Temporary DSN & which is not? Please provide me some example for better understanding ?
2.
Quote:
Hence You cannot store it or catlg it any more after job complete
I never tried to 'store' a DSN in CATALoGue, (actually, I know to make an 'entry' of DSN in CATALoGue & can can just direct the system to do so) Please let me know that how do you do that?
3.
Quote:
Instead of temporary dataset, make it as physical I mean don't use '&' while Giving DSN
What's the definition of temporary & physical here ? I'm confused..
Joined: 01 Mar 2006 Posts: 290 Location: Basel, Switzerland
Hi together,
the file is always stored with this DISP...
but instead of giving a full qualified dataset name on the dd-statement,
it gets a system generated dataset name.
therefore give a full qualified dataset name, and
if you do not have any cleanup process for "old" files,
it will keep on disk. otherwise store it on a tape.
Sorry for late reply, I had some work so i couldn'y able reply.
Quote:
Intresting concept, from where did you get this information, please direct me to some link. My question is, how the system distinguish between the DDs to understand that 'which DD' is meant for Temporary DSN & which is not? Please provide me some example for better understanding ?
I am afraid of with your question, Since My mind was asking question to you DON'T YOU KNOW HOW TO CODE TEMPORARY DATASET?
Its Ok, If you code '&&' in DSNAME, then system generates n treat as temporary dataset.
Just try in your system, I mean try with some job like this,
Code:
// DD DSN=&&TEMP,DISP=(NEW,CATLG,DELETE)
Then look in job spool, Paste the message here, Then I will Tell you the link ;-)
Quote:
I never tried to 'store' a DSN in CATALoGue, (actually, I know to make an 'entry' of DSN in CATALoGue & can can just direct the system to do so) Please let me know that how do you do that?
Please look into my statement, I had said that becuase of If you are going to create a dataset means what? As I know, storing it somewhere(?)(I mean store it in tape drive or in disk(DASD)) and then make the entry in catlg for that somewhere(?). So that system will search for it.
If you don't want to make entry in catlg, how you will code in JCL?, I.e. KEEP(as per JCL)(means don't make entry in catlg but store it!!) Since without storing it somewhere how system will look for Dataset, becuase dataset itself a File(?).
Quote:
What's the definition of temporary & physical here ? I'm confused..
I suggest you to read JCL concept on Temporary Dataset......
Joined: 01 Mar 2006 Posts: 290 Location: Basel, Switzerland
Hy Kumar,
each file (i.e. dataset) will be stored on disk (dasd),
no matter if temporary or permanent.
if you choose temporary, then the system generates an ugly
long dataset name by itself.
therefore of this name, you can actually nomore access the file.
temporary datasets are useful if you need the file in that specific
job stream only. you can PASS it with the DISP from one step to
another within your job.
but just think, it might be useful in case of any error, to look
into the file for its contents, therefore give a full qualified dataset
name... :-)
Joined: 01 Mar 2006 Posts: 290 Location: Basel, Switzerland
hy enrico,
there are always to many follow ups...
it is not necessary to know the solution,
it is just necessary to know, which book to
read. autodidactics are not given to everybody... :-)
anyway you will find everything veryx easily in the internet,
you know, i know, just let the forum also know...
.jpg)
.jpg)
