View previous topic :: View next topic
|
Author |
Message |
liying
New User
Joined: 27 May 2010 Posts: 47 Location: da lian.china
|
|
|
|
Will update the info in PDS member increase the PDS dataset space allocation?
PDS before update:
XXXX.DS.CNTL
NUMBER = 10
PDS after update:
XXXX.DS.CNTL
NUMBER = 20 |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
What happened when you tried ? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
What you posted has no context -- are you giving us data set space allocated, or directory blocks allocated, or data set space used, or some other number? Furthermore, your question is not clear -- when you say "update the info in PDS member" do you mean that you are changing data in the member and hence replacing the member, or do you mean you are merely updating the member information in the directory? If the former, then the answer is that changing a member means you have to replace the member in the PDS, and the allocated (and used) space for the data set can change. If the latter, then most likely the data set space allocated and used would not change. |
|
Back to top |
|
|
liying
New User
Joined: 27 May 2010 Posts: 47 Location: da lian.china
|
|
|
|
Thank you for your answer.I have a dataset, there are fixed number of members in the dataset. But there are some information in the member will also be changed while the job is run.That means the informatio in the member will update, e.g. change a parameter from 10 to 20,the length won't be change, will this kind of no length update of the PDS member content can conduce the whole PDS dataset's space allocation increased?
In my case, there was an PDS dataset. While the job update the member's content without length change of the info, SE37-04(space not enough) have happened. I want to make sure the upper question. |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
What conclusion can you make from the facts.
The PDS dataset is updated, without chnage of length.
The job abends because there is no space left in the PDS dataset
Do you know how a PDS works when a member has been updated.
Have you considered using PDS-E instead |
|
Back to top |
|
|
liying
New User
Joined: 27 May 2010 Posts: 47 Location: da lian.china
|
|
|
|
No,the dataset was in production environment, therefore I can not change it from PDS to PDS-E easily. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
1. You need to learn about what a PDS is and how it is updated. It is clear that you have no clue about them at this point, hence most of the answers we can provide will not help you.
2. Is the PDS compressed regularly? If not, why not? If yes, then why did you sstill get the SE37 abend? And do you know why a PDS being regularly updated needs to be compressed? If not, you need to do some research.
3. I agree with expat -- you would be wise to take the time, no matter how difficult it is, to change the PDS to a PDSE instead. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Is the space monitored by the storage group? Has it been filling up over time?
During a maintenance window or scheduled system re-cycle, making the dataset larger should not be an issue. If you can get the approval to convert it to a pdse, great, but more space might be lelpful.
Hopefully, someone there is aware that a pds can be "full" just because it needs to be compressed.
Hopefully, your system has storage administration who can help. |
|
Back to top |
|
|
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
Changing one byte in a PDS member will cause the records containing the entire original member to be marked as deleted, and will cause the member to be written in its entirety. The "deleted" records will not be recovered for reuse until the PDS is "compressed".
A PDSE is different. "Deleted" space is re-used.
Either a regular compress (after a backup is usually a good point to do it) or make it a PDSE. Both of these suggestions have been made. They may require more work, but you have to do something :-) |
|
Back to top |
|
|
Dale Robertson
New User
Joined: 21 Jun 2013 Posts: 44 Location: U.S.A.
|
|
|
|
liying,
It looks like you might be putting the cart before the horse. That is, you truly need to sit down, take a deep breath and get a hold of the very best programmer you can find and have him teach you everything he knows about BPAM - Basic Partitioned Access Method - pds's, or TSO libraries or partitioned data sets.
It's easy taking only about an hour of your time in order to straighten out the kinks you have. Then a short bit of practical factors including how to free up space either with IEBCOPY or TSO 3.4 Free instruction and then progress to how to deal with space issues you truly seem to have in your system.
Good luck.
r
"Take a deep breath!"
--Arthur C. Clarke |
|
Back to top |
|
|
|