No we have JCLPLUS for that. We literally have thousands of permanent datasets with space allocations that look something like SPACE=(TRK,(500,1,50)). A Space release was accidentally run on the storage pool these datasets reside in, and now jobs are abending on space problems. Many of these datasets have been allocated for many years, and never touched. And I never said it was done right, either. We are dealt with what we have, and am just looking for ways to fix the problem safely trying to avoid allocating a .NEW correctly, IEBCOPY, and RENAMES, but that can be written in REXX, and would probably be the safest.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Lizette Koehler Sent: Monday, August 13, 2012 2:17 PM To: [email protected] Subject: Re: modifying secondary space allocation Dave, Is this what you are asking? JCL in libraries need to be reviewed and if the secondary space parm is incorrect (according to your shop's standards) you want a way to make it better? If I am correct, then this sounds like a JCL parser. Is that what you are looking for? Or something to frontend the converter to catch them? In my shop the users code SPACE=(TRK,(1,1)) which really is a pain here. Is that what you are running into? Lizette -----Original Message----- >From: "Jousma, David" <[email protected]> >Sent: Aug 13, 2012 11:06 AM >To: [email protected] >Subject: Re: modifying secondary space allocation > >Thanks Skip. I think you are misunderstanding my request. I don't want to >add space to the dataset, I want to change the secondary space allocation from >nothing(or something small) to something realistic, so that when space is >needed, it gets more than just 1 track(we have many app datasets where >secondary space is set to 1 TRK). John Kalinch hit the nail on the head with >the CBT CDSCB program. > >Unless I am missing something, I don't see that function in PDS. If it does, >please give me a sample command line command that will do it. > >-----Original Message----- >From: IBM Mainframe Discussion List [mailto:[email protected]] >On Behalf Of Skip Robinson >Sent: Monday, August 13, 2012 1:53 PM >To: [email protected] >Subject: Re: modifying secondary space allocation > >The fully supported program product StarTool can modify secondary space of any >PDS, allocated or not. Its ancestor, the PDS Command--available on CBT--has >performed this function for decades. I've never heard of a failure. > >Note that modifying secondary space does not touch the allocation at all, only >the external data set attributes. The next time space is needed, the system >will add a secondary extent as needed. Be careful though: some PDS uses may >not allow expansion. In particular, link list data sets will not see a new >extent automatically. JES2 proclibs may require a close/open sequence--not a >JES2 restart--to pick up an additional extent. > >. >. >JO.Skip Robinson ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
