Re: How to expand SYS1.LINKLIB?
Or, when you decide to do a cleanup of old stuff, delete a couple of uncataloged HASPCKPTs and then discover that *the* haspckpt was among them. Only then you realize what the ABSTR JCL statement is good for... Or, do a $PQ command in the early 80's, when JES2 still accepted it without parameters. This was the fasted Cold Start I ever saw... Kees. Matthew Stitt [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... You haven't even lived until you forget to update the IPL bootstrap records on the only sysres you've got that is supposed to work. Got the scars to prove it. g On Wed, 15 Nov 2006 10:30:54 -0600, Rick Fochtman [EMAIL PROTECTED] wrote: --snip Can't be much fun being a trainee sysprog any more - wasn't this one of the rites of passage ???. I guess deleting the MCAT (and getting it back before anyone notices) is also passe ... Not to mention ... Whoa, better stop - ain't Friday yet, even here in the Antipodes. -unsnip- My first rite of passage was a complete OS/360 System Generation...without asking for help or a look at the previous 'gen! G -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 ** -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
Or, do a $PQ command in the early 80's, when JES2 still accepted it without parameters. This was the fasted Cold Start I ever saw... March 14th, 1981. Second week on the job. When in doubt. PANIC!! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
In [EMAIL PROTECTED], on 11/15/2006 at 05:35 PM, Matthew Stitt [EMAIL PROTECTED] said: You haven't even lived until you forget to update the IPL bootstrap records on the only sysres you've got that is supposed to work. While the scope is local rather than global, you haven't lived until you realize that you type EXEC CMS ERASE when you meant to type ERASE CMS EXEC Fastest PA1 in the East -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
The easiest method to compress a library ... I hope no one is contemplating compressing a SYS1.LINKLIB that is currently in use on an active system Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
On Wed, 2006-11-15 at 08:28 -0500, Peter Relson wrote: The easiest method to compress a library ... I hope no one is contemplating compressing a SYS1.LINKLIB that is currently in use on an active system Can't be much fun being a trainee sysprog any more - wasn't this one of the rites of passage ???. I guess deleting the MCAT (and getting it back before anyone notices) is also passe ... Not to mention ... Whoa, better stop - ain't Friday yet, even here in the Antipodes. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
--snip Can't be much fun being a trainee sysprog any more - wasn't this one of the rites of passage ???. I guess deleting the MCAT (and getting it back before anyone notices) is also passe ... Not to mention ... Whoa, better stop - ain't Friday yet, even here in the Antipodes. -unsnip- My first rite of passage was a complete OS/360 System Generation...without asking for help or a look at the previous 'gen! G -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
You haven't even lived until you forget to update the IPL bootstrap records on the only sysres you've got that is supposed to work. Got the scars to prove it. g On Wed, 15 Nov 2006 10:30:54 -0600, Rick Fochtman [EMAIL PROTECTED] wrote: --snip Can't be much fun being a trainee sysprog any more - wasn't this one of the rites of passage ???. I guess deleting the MCAT (and getting it back before anyone notices) is also passe ... Not to mention ... Whoa, better stop - ain't Friday yet, even here in the Antipodes. -unsnip- My first rite of passage was a complete OS/360 System Generation...without asking for help or a look at the previous 'gen! G -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
The easiest method to compress a library for maintenance runs is to use the SMP/E option COMPRESS(xx), or COMPRESS(ALL), where xx is the name of the specific library(ies) to compress. SMP/E will delete all the modules which are to be changed, then compress the library, then apply the maintenance. But there is no subsitute to having SMP/E point to copies of the datasets, and not trying your luck with the running stuff. On Sun, 12 Nov 2006 13:56:16 -0500, Shmuel Metz (Seymour J.) [EMAIL PROTECTED] wrote: In [EMAIL PROTECTED], on 11/09/2006 at 10:08 PM, Bob Henry [EMAIL PROTECTED] said: Is there a SAFE way to expand the size of SYS1.LINKLIB? Yes - on a target volume that you're not currently running from. Any maintenance to the system you're running from puts you at risk. I need to apply a PTF to a module in LINKLIB but I'm afraid it will cause it to go into a secondary extent. If you're talking about your live SYS1.LINKLIB then there may be other risks as well. But it's not my dog. Is there an easier (and safe) way to expand SYS1.LINKLIB? Safe? No, but safer. Make a copy with a larger primary. Rename original. Rename copy. IPL. At you leisure, redo your maintenance strategy so that it does not require updating the running system and you;ll save yourself a lot of grief. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
---snip- The easiest method to compress a library for maintenance runs is to use the SMP/E option COMPRESS(xx), or COMPRESS(ALL), where xx is the name of the specific library(ies) to compress. SMP/E will delete all the modules which are to be changed, then compress the library, then apply the maintenance. unsnip But God help you if IEBCOPY happens to be getting an update.! ---snip- But there is no subsitute to having SMP/E point to copies of the datasets, and not trying your luck with the running stuff. -unsnip- AMEN, BROTHER! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
In [EMAIL PROTECTED], on 11/09/2006 at 10:08 PM, Bob Henry [EMAIL PROTECTED] said: Is there a SAFE way to expand the size of SYS1.LINKLIB? Yes - on a target volume that you're not currently running from. Any maintenance to the system you're running from puts you at risk. I need to apply a PTF to a module in LINKLIB but I'm afraid it will cause it to go into a secondary extent. If you're talking about your live SYS1.LINKLIB then there may be other risks as well. But it's not my dog. Is there an easier (and safe) way to expand SYS1.LINKLIB? Safe? No, but safer. Make a copy with a larger primary. Rename original. Rename copy. IPL. At you leisure, redo your maintenance strategy so that it does not require updating the running system and you;ll save yourself a lot of grief. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
Depending on this module, you might be able to temporarily move it to another data set in the LINKLST and use it until you can get the SYS1.LINKLIB fixed. But only if the fix is urgent enough to install. Or look at MLPA as an alternative until you get SYS1.LINKLIB fixed. If it isn't urgent, then the following would need to be done. Are you using SYMDEF which uses indirect catalog for SYSRES Volumes? If yes, then just close the pack, implement the maintenance on the clone, then IPL. If not, then you will need to clone and clip as others have suggested. You also might have other issues in the Linklst, so a review of all datasets might be in order. Just my two cents worth. Lizette -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
No, there is no safe way to expand SYS1.LINKLIB on the running system. If you want an unsafe way, - create a copy of SYS1.LINKLIB such as SYS1.LINKLIB.COPY - create a LNKLST set that specifies NOCHECK and includes SYS1.LINKLIB.COPY in the right place along with specifying SYS1.MIGLIB and SYS1.CSSLIB in the right places (and if you're on z/OS 1.8, SYS1.SIEALNKE and SYS1.SIEAMIGE). - activate that LNKLST set - get all users off of the old LNKLST. This is unpredictably dangerous (ranging from harmless to fatal), such as by SETPROG LNKLST UPDATE JOB(*). Now no in-use LNKLST has SYS1.LINKLIB. - get LLA to stop using SYS1.LINKLIB. A REMOVE statement in CSVLLAxx might do it. Or you might have to purge LLA. - Now there is no one using SYS1.LINKLIB and the system's ENQs on SYS1.LINKLIB will be released. - Now you can do whatever you want with SYS1.LINKLIB. - And then if you're equally adventurous you can repeat this process doing the analogous stuff to get rid of SYS1.LINKLIB.COPY and restore use of SYS1.LINKLIB. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
On Thu, 9 Nov 2006 22:08:57 -0600, Bob Henry [EMAIL PROTECTED] wrote: Is there a SAFE way to expand the size of SYS1.LINKLIB? I have a z/OS 1.6 ADCD system where SYS1.LINKLIB is using all of its primary extent. I need to apply a PTF to a module in LINKLIB but I'm afraid it will cause it to go into a secondary extent. Why it was set up with the exact number of tracks for primary allocation and then given a secondary allocation I'll never know. There is a one pack IPL-able system on the ADCD I could use but it will take quite a bit to set it up. Is there an easier (and safe) way to expand SYS1.LINKLIB? Nothing to it. When you clone your target zone to apply the maintenance, just make SYS1.LINKLIB bigger on the new target volume. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
-Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Relson No, there is no safe way to expand SYS1.LINKLIB on the running system. If you want an unsafe way, - create a copy of SYS1.LINKLIB such as SYS1.LINKLIB.COPY - create a LNKLST set that specifies NOCHECK and includes SYS1.LINKLIB.COPY in the right place along with specifying SYS1.MIGLIB and SYS1.CSSLIB in the right places (and if you're on z/OS 1.8, SYS1.SIEALNKE and SYS1.SIEAMIGE). - activate that LNKLST set - get all users off of the old LNKLST. This is unpredictably dangerous (ranging from harmless to fatal), ... Another way to say that might be, Results may vary between 'ho-hum' and 'reinstall everything' inclusive. -jc- -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
On Fri, 10 Nov 2006 08:21:08 -0600, Chase, John [EMAIL PROTECTED] wrote: -Original Message- From: IBM Mainframe Discussion List On Behalf Of Peter Relson - get all users off of the old LNKLST. This is unpredictably dangerous (ranging from harmless to fatal), ... Another way to say that might be, Results may vary between 'ho-hum' and 'reinstall everything' inclusive. It's not going to cause you to reinstall. IPL, yes. Install, no. -- Tom Marchant -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
On Fri, 10 Nov 2006 08:01:31 -0500, Peter Relson [EMAIL PROTECTED] wrote: No, there is no safe way to expand SYS1.LINKLIB on the running system. If you want an unsafe way, - create a copy of SYS1.LINKLIB such as SYS1.LINKLIB.COPY - create a LNKLST set that specifies NOCHECK and includes SYS1.LINKLIB.COPY in the right place along with specifying SYS1.MIGLIB and SYS1.CSSLIB in the right places (and if you're on z/OS 1.8, SYS1.SIEALNKE and SYS1.SIEAMIGE). - activate that LNKLST set - get all users off of the old LNKLST. This is unpredictably dangerous (ranging from harmless to fatal), such as by SETPROG LNKLST UPDATE JOB(*). Now no in-use LNKLST has SYS1.LINKLIB. - get LLA to stop using SYS1.LINKLIB. A REMOVE statement in CSVLLAxx might do it. Or you might have to purge LLA. - Now there is no one using SYS1.LINKLIB and the system's ENQs on SYS1.LINKLIB will be released. - Now you can do whatever you want with SYS1.LINKLIB. - And then if you're equally adventurous you can repeat this process doing the analogous stuff to get rid of SYS1.LINKLIB.COPY and restore use of SYS1.LINKLIB. Peter Relson z/OS Core Technology Design How heavily used is this ADCD system? While most if not all will tell you not to attempt this on a live system, I have contracted at several very small environments using an ADCD system that didn't have anything set up for cloning new sysres volumes, indirect cataloging etc. and have used the unsafe method outlined above. You are probably in the same boat, so I'm sure you don't want to go through all the trouble of setting up a cloned system for 1 PTF. Perhaps you don't have the expertise even to do that. Another option - which is safe - is to create the copy of SYS1.LINKLIB and specify it in PROGxx as SYSLIB LINKLIB(SYS1.LINKLIB.COPY) and IPL. Then apply your PTF to SYS1.LINKLIB (I don't think your OP said it had to be applied to the running system). Then you can remove the SYSLIB or replace the specification with an empty dummy library and re-ipl with SYS1.LINKLIB. If you decide to leave in SYSLIB LINKLIB(dsn), make sure you specifically add SYS1.LINKLIB to the LNKLST set. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
unless something has changed, you can change a dsn to multiple extents by coding a space parm with secondary extents and outputing to the dsn. if you add secondary extents to a lnklst lib though you better ipl soon(ish) or the ab/s106 daemons will attack. Jack Kelly LA Systems @ US Courts x 202-502-2390 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
In a message dated 11/10/2006 9:03:53 A.M. Central Standard Time, [EMAIL PROTECTED] writes: unless something has changed, you can change a dsn to multiple extents by coding a space parm with secondary extents and outputing to the dsn. if you add secondary extents to a lnklst lib though you better ipl soon(ish) or the ab/s106 daemons will attack. I saw this happen to a fairly seasoned sysprog. Tried to apply maint and LINKLIB went to secondary and IEBCOPY via SMP got a S106 and were left with an unIPLable system. Did have a current backup but the maint was so out of synch had to start over. There's provisions in Software manufacturing to STEPLIB to CPAC.LINKLIB. If you get in too big a hurry steps get missed/skipped -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
On Fri, 10 Nov 2006 10:39:01 EST, Ed Finnell [EMAIL PROTECTED] wrote: unless something has changed, you can change a dsn to multiple extents by coding a space parm with secondary extents and outputing to the dsn. if you add secondary extents to a lnklst lib though you better ipl soon(ish) or the ab/s106 daemons will attack. I saw this happen to a fairly seasoned sysprog. Tried to apply maint and LINKLIB went to secondary and IEBCOPY via SMP got a S106 and were left with an unIPLable system. Did have a current backup but the maint was so out of synch had to start over. There's provisions in Software manufacturing to STEPLIB to CPAC.LINKLIB. If you get in too big a hurry steps get missed/skipped Exactly... if you are going to ever apply to a running system and that maintenance hits a LNKLST library, make sure you at least add a STEPLIB to the affected libraries in your SMP/E JCL. In particular SYS1.LINKLIB, SYS1.MIGLIB, and SYS1.CSSLIB. This won't prevent the S106 issues later but at least you should be okay after an IPL (or dynamic LNKLST update assuming that doesn't abend also). Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - GITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
Peter, While this method should work in better than 90% of the time, I would strongly recommend that you have an updated copy of your resume before you try this! Wayne Driscoll Product Developer JME Software LLC NOTE: All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Peter Relson Sent: Friday, November 10, 2006 7:02 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: How to expand SYS1.LINKLIB? No, there is no safe way to expand SYS1.LINKLIB on the running system. If you want an unsafe way, - create a copy of SYS1.LINKLIB such as SYS1.LINKLIB.COPY - create a LNKLST set that specifies NOCHECK and includes SYS1.LINKLIB.COPY in the right place along with specifying SYS1.MIGLIB and SYS1.CSSLIB in the right places (and if you're on z/OS 1.8, SYS1.SIEALNKE and SYS1.SIEAMIGE). - activate that LNKLST set - get all users off of the old LNKLST. This is unpredictably dangerous (ranging from harmless to fatal), such as by SETPROG LNKLST UPDATE JOB(*). Now no in-use LNKLST has SYS1.LINKLIB. - get LLA to stop using SYS1.LINKLIB. A REMOVE statement in CSVLLAxx might do it. Or you might have to purge LLA. - Now there is no one using SYS1.LINKLIB and the system's ENQs on SYS1.LINKLIB will be released. - Now you can do whatever you want with SYS1.LINKLIB. - And then if you're equally adventurous you can repeat this process doing the analogous stuff to get rid of SYS1.LINKLIB.COPY and restore use of SYS1.LINKLIB. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
How to expand SYS1.LINKLIB?
Is there a SAFE way to expand the size of SYS1.LINKLIB? I have a z/OS 1.6 ADCD system where SYS1.LINKLIB is using all of its primary extent. I need to apply a PTF to a module in LINKLIB but I'm afraid it will cause it to go into a secondary extent. Why it was set up with the exact number of tracks for primary allocation and then given a secondary allocation I'll never know. There is a one pack IPL-able system on the ADCD I could use but it will take quite a bit to set it up. Is there an easier (and safe) way to expand SYS1.LINKLIB? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
Bob, If are asking to do this in a LIVE (running) environment, I would say NO. If you are asking about a copy of the pack then there are at least 2 ways. User FDR to consolidate extents then compress it. The other way is to copy the data set to another pack and delete it and reallocate it. Again this is with a duplicate pack copy. Ed Ed On Nov 9, 2006, at 10:08 PM, Bob Henry wrote: Is there a SAFE way to expand the size of SYS1.LINKLIB? I have a z/ OS 1.6 ADCD system where SYS1.LINKLIB is using all of its primary extent. I need to apply a PTF to a module in LINKLIB but I'm afraid it will cause it to go into a secondary extent. Why it was set up with the exact number of tracks for primary allocation and then given a secondary allocation I'll never know. There is a one pack IPL-able system on the ADCD I could use but it will take quite a bit to set it up. Is there an easier (and safe) way to expand SYS1.LINKLIB? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: How to expand SYS1.LINKLIB?
The safe way is to copy the IPL pack to another volume. Expand SYS1.LINKLIB on that pack, and then IPL from that pack after clipping it to the same volser as you had before. I hope you are not planning on running SMP jobs agains the live IPL pack. That could lead to disaster. If you applied the maintenance to a copy of your IPL pack, and SYS1.LINKLIB went into extents, you could try compressing SYS1.LINKLIB on your alternate IPL pack and seeing if it fits in 1 extent. Eric Bielefeld Sr. z/OS Systems Programmer Milwaukee Wisconsin 414-475-7434 - Original Message - From: Bob Henry [EMAIL PROTECTED] Newsgroups: bit.listserv.ibm-main To: IBM-MAIN@BAMA.UA.EDU Sent: Thursday, November 09, 2006 10:08 PM Subject: How to expand SYS1.LINKLIB? Is there a SAFE way to expand the size of SYS1.LINKLIB? I have a z/OS 1.6 ADCD system where SYS1.LINKLIB is using all of its primary extent. I need to apply a PTF to a module in LINKLIB but I'm afraid it will cause it to go into a secondary extent. Why it was set up with the exact number of tracks for primary allocation and then given a secondary allocation I'll never know. There is a one pack IPL-able system on the ADCD I could use but it will take quite a bit to set it up. Is there an easier (and safe) way to expand SYS1.LINKLIB? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
