|
View previous topic :: View next topic
|
| Author |
Message |
padma_prakasam
New User
Joined: 06 Oct 2005
Posts: 31
|
|
|
|
Hi,
In one my jobs i have created a GDG version with space CYL(150,5). I'm using the same version in another job with DISP=OLD. The DD statement is coded like this,
//FILEIN DD DSN=gdg.name,SPACE = (TRKS,(15,5)),DISP=OLD
This is being used as output file in that step. What for we give SPACE parameter when DISP=OLD coded? Does it override space?
Thanks,
Padma |
|
| Back to top |
|
 |
muthuvel
Active User
Joined: 29 Nov 2005
Posts: 217
Location: Canada
|
|
|
|
Padma,
This is what the manual says,
| Quote: |
| When you specify DISP=OLD for a PDS or a PDSE, and you also specify a member name in the DSNAME parameter, the data set must already exist. If the member name already exists and the data set is opened for output,the system replaces the existing member with the new member. If the member name does not already exist and the data set is opened for output, the system adds the member to the data set. |
I think the above quote's will make you to understand.To be more clear,If the version of the GDG is not there it will create a new version with the given SPACE parameters when coded with DISP=OLD. |
|
| Back to top |
|
|
raak
Active User
Joined: 23 May 2006
Posts: 166
Location: chennai
|
|
|
|
Hi Muthuvel,
When u code DISP=OLD and the version of GDG is not present, u should get a JCL error....
and the quotes that u gave is referring a PDS and It's member. not a PS..
And Padma,
The Space parameter coded for the same generation doesn't make any sense for me. I don't think the space parameter can be overridden for an existing dataset even if u use DISP=OLD.
Corrections are welcomeee  |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
| Quote: |
| //FILEIN DD DSN=gdg.name,SPACE = (TRKS,(15,5)),DISP=OLD |
Nice standards you have - an output file allocated to FILEIN DD
I think that you can actually change the space allocation parameters when writing to a pre existing file, but it will only work for secondary allocations.
OK, why have you created the GDG in a different job when you are going to write to it in another job, what is the point of that. You are using up at least 150 cylinders of DASD resource until the job that writes to the GDG is processed.
Why not create the GDG version when it is written to, and then you can use the RLSE parameter to make sure that you do not hold and waste any unused DASD resource.
And if your storage group have got things set up correctly your GDG will have immediate free space release via DFSMSsms, and if it is empty will be just ONE cylinder in size. |
|
| Back to top |
|
|
padma_prakasam
New User
Joined: 06 Oct 2005
Posts: 31
|
|
|
|
| Thanks for your information. And the DD name actually coded was different. My intention was to clarify wiht the SPACE parameter. Just for an example i gave the name FILEIN. |
|
| Back to top |
|
|
muthuvel
Active User
Joined: 29 Nov 2005
Posts: 217
Location: Canada
|
|
|
|
Raak,
Raak wrote:
| Quote: |
Hi Muthuvel,
When u code DISP=OLD and the version of GDG is not present, u should get a JCL error....
and the quotes that u gave is referring a PDS and It's member. not a PS..
Corrections are welcomeee |
Yes ,you are right if i am mentioning the version not present or new version(+1) I should get a JCL error.
But Padma wrote
| Quote: |
| I'm using the same version in another job with DISP=OLD. |
So In this case it will not cause a problem
Please try out.I tried it and found working  |
|
| Back to top |
|
|
|
|
