On Thu, 3 Nov 2016 12:48:03 -0500, Paul Gilmartin wrote:
>But my thought processes have been contaminated by the superior (in
>this case) facilities of VMSES/E. VMSES/E has no ACCEPT nore any
>analogue if the DLIB zone. This enables multi-layer VMFREMOV
>(analog of RESTORE). Suppose a function
On Thu, 3 Nov 2016 11:19:56 -0500, Tom Marchant wrote:
>On Wed, 2 Nov 2016 09:54:49 -0600, Paul Gilmartin wrote:
>
>>I wish that LINK LMODS could appear in a SYSMOD
>>rather than only in SMPCNTL.
>
>I don't see why, but ok.
>
Simpler instructions from the supplier to the customer. If LINK LMODS
On Wed, 2 Nov 2016 09:54:49 -0600, Paul Gilmartin wrote:
>I wish that LINK LMODS could appear in a SYSMOD
>rather than only in SMPCNTL.
I don't see why, but ok.
>Even better if a SYSMOD containing
>LINK LMODS could be RESTORed.
What would that mean? If LINK LMODS creates the target load module
LOL.
Kurt,
Many thanks for the most direct and easy solution. The systems are now as
they should have been.
Rob Schramm
On Thu, Nov 3, 2016, 8:27 AM Kurt Quackenbush wrote:
> > Is this really as simple as
> >
> > LINK LMODS(module1)
> > CHECK.
> >
> > And it will just relink the load module
Is this really as simple as
LINK LMODS(module1)
CHECK.
And it will just relink the load module?
Yes, that's the function of the LINK command.
Well, of course you have to remove CHECK for SMP/E to perform the actual
link edit operation. Doh!
Kurt Quackenbush -- IBM, SMP/E Development
---
Or perhaps implement the re-installed Serverpac system to eliminate any
possibility of copy errors.
Prior to Serverpac, we installed maintenance and upgrades in an SMP/E
zone that was very old, and a mistake could be there for years to come.
When Serverpac came out I quietly said to myself, w
On 2016-11-02, at 09:14, Jesse 1 Robinson wrote:
> I didn't see any comments about the effect of the DELETE action. Doesn't this
> mean that something vital is no longer there?
>
A PTF containing a ++DELETE MCS can not be RESTORED. But I think
that what the OP meant is that ACCEPTed PTFs were
..@sce.com
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Rob Schramm
Sent: Wednesday, November 02, 2016 6:42 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Weird problem hoping to be saved by SMP/E
Kurt,
Is this really as
Kurt,
Is this really as simple as
LINK LMODS(module1)
CHECK.
And it will just relink the load module?
Rob Schramm
On Wed, Nov 2, 2016 at 9:24 AM Tom Marchant <
000a2a8c2020-dmarc-requ...@listserv.ua.edu> wrote:
> On Wed, 2 Nov 2016 05:06:44 +, Rob Schramm wrote:
>
> >What if I make a
EXCELLENT! Much easier than my proposal
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Kurt Quackenbush
Sent: Wednesday, November 2, 2016 8:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Weird problem hoping to be saved by SMP
On Wed, 2 Nov 2016 05:06:44 +, Rob Schramm wrote:
>What if I make a fake USERMOD and then RESTORE it off.
I like this idea. A USERMOD to ZAP the affected modules, then RESTORE the
USERMOD. RESTORE processing will get the modules from the Distribution zone. Do
it on a clone of your target zo
I am looking for ideas on how to get back to the correct versions of the
modules.
Check out the SMP/E LINK LMODS command. Assuming you know exactly which
load modules you want to rebuild, just specify them by name on the LINK
LMODS command and SMP/E will figure out where to get all the module
-MAIN@LISTSERV.UA.EDU
Subject: Re: Weird problem hoping to be saved by SMP/E
Date: Wed, 2 Nov 2016 12:33:53 +
HDZ1D10 is the function for df/SMS and related. This will normally be accepted
at the time of installation.
Try this (not syntax checked).
SET BDY(DLIBZONE).
LIST MOD(). (for ea
HDZ1D10 is the function for df/SMS and related. This will normally be accepted
at the time of installation.
Try this (not syntax checked).
SET BDY(DLIBZONE).
LIST MOD(). (for each of the affected modules). Note UMID and RMIDs.
SET BDY(TARGZONE).
LIST MOD(). (for each o
SMP/E to the rescue!
It goes without saying that you should not be doing this on the active
system, and that you should take a backup first, but I'll say it anyway.
Back up target libraries and zone, DLIBs and DLIB zone. (DFSMSdss or
your favorite alternative is the sysprog's best friend.)
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Gibney, Dave
Sent: Wednesday, November 02, 2016 12:26 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Weird problem hoping to be saved by SMP/E
Is the Serverpac still available? Do another install and run it up to
PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Weird problem hoping to be saved by SMP/E
>
> Dear Listers,
>
> I am attempting to recover or get back to the proper version of a couple
> LPALIB modules. In this case some sysprog decided to copy altered versions
> of a couple
What if I make a fake USERMOD and then RESTORE it off.
My understanding is that once a sysmod is ACCEPTed, then I should always be
able to undo any change back to the point of the last ACCEPT.
Thoughts?
Rob Schramm
On Wed, Nov 2, 2016 at 12:48 AM Paul Gilmartin <
000433f07816-dmarc-requ...@
On 2016-11-01 22:08, Rob Schramm wrote:
>
> ... I have not been able to find
> a backup of the modules.
>
Ouch!
> fails because HDZ1D10 was ACCEPTed.
>
I didn't think that was a concern unless you did ACCEPT PURGE.
> A RESTORE fails for
>
> GIM24501E RESTORE PROCESSING FAILED FOR SYSMOD sy
Dear Listers,
I am attempting to recover or get back to the proper version of a couple
LPALIB modules. In this case some sysprog decided to copy altered versions
of a couple of load modules into SYS1.LPALIB. I have not been able to find
a backup of the modules. So, I am left with what is in SMP
20 matches
Mail list logo
