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
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
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
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 /
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
--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
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
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
---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
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
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,
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
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
-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
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
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
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
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
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
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
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
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
: 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
23 matches
Mail list logo
