Hello Jon,
As a customer I currently have 638 ++APARs installed across my product base. We
regularly get test fixes, as in ++APAR, provided by vendors.
I wouldn't really call them RARE.
On Sat, 4 Nov 2023 13:31:17 -0500, Jon Perryman wrote:
>On Sat, 4 Nov 2023 07:19:49 -0500, Bruce Hewson
~10+ years ago I would give you three FEPs for free.
However they went to junk.
AFAIK they were model 170.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 05.11.2023 o 00:22, Ben Huntsman pisze:
Hi guys-
I apologize for the off the wall request. Not sure this is the best place
to start but
IBM used to document how it assigned the prefix in sysmod ids, but its been
decades since I've seen documentation that matched practice. What I've never
seen violated is that the sysmod ids associated with an APAR all have the same
numeric portion.
The simplest situation is when the error only
Like "SPF", what "PTF" stands for depends on the year, but whether problem,
product or program temporary fix, its role remains the same. Both an APAR and
any resolving PTFs may exist for reasons other than defects, e.g.,
documentation, Small Program Enhancement (SPE).
Is there an edition of
I'll try to clarify things. An APAR is a report used for tracking things, most
often reported errors. Associated with the APAR are identifiers with the same
numeric parts, used as sysmod ids in SMP. A common situation is that the error
exists in multiple releases. There used to be a documented
This chain has an interesting range of opinions that I am not going to comment
on specifically, other than to point out that APAR started out being the
acronym for Authorised Problem Analysis Report which would be outcome of a
verified problem, NOT yet a fix.
Likewise PTF stands for Problem
Hi guys-
I apologize for the off the wall request. Not sure this is the best place
to start but it's somewhere.
Does anyone out there have an old 3745 model 130, 150, or 170 that's not in
use that they'd be willing to sell at a reasonable price? I know they're
awfully rare these days.
On Sat, 4 Nov 2023 07:19:49 -0500, Bruce Hewson
wrote:
>HI,
>
>APARs for me are OAx or PHx - these are the entries describing a
>problem, and may be associates as Error Holds to existing PTFs.
>
>Before a PTF is issued, the vendor may issue a ++APAR for you to test. A
>++APAR fix is
In my experience back in the 1980s and 1990s IBM were far more likely to
provide ++APAR type fixes for source-maintained products than for others. So at
the time that mainly applied to JES2, JES3 and IMS I think. However, I have
been the instigator for a few ++APAR fixes which were zaps.
How about browsing the Holddata explanation page at
https://public.dhe.ibm.com/390holddata/390holddata.html
and retrieving the file to view the contents?
On Fri, Nov 3, 2023 at 11:02 PM Tony Harminc wrote:
>
> On Fri, 3 Nov 2023 at 18:03, Jon Perryman wrote:
> [...]
>
> > Anything beginning
On Sat, 4 Nov 2023 07:19:49 -0500, Bruce Hewson
wrote:
>APARs for me are OAx or PHx - these are the entries describing a
>problem, and may be associates as Error Holds to existing PTFs.
The broader point that needs to be addressed is the purpose of an APAR. Since
++APAR are rarely
On 10/23/2023 10:52 PM, John Dravnieks wrote:
And the binder has support to create program objects with two code sections in
different RMODEs - take a look at RMODE(SPLIT) and RMODEX.
If your code sections are RMODE24 and RMODE31, you should also take a look at
the binder HOBSET option -
HI,
APARs for me are OAx or PHx - these are the entries describing a
problem, and may be associates as Error Holds to existing PTFs.
Before a PTF is issued, the vendor may issue a ++APAR for you to test. A ++APAR
fix is not fully tested.
++APAR names aill be AAx, BAx etc for
On Fri, 3 Nov 2023 23:12:08 -0500, Paul Gilmartin wrote:
>"Standard"? Cite. Does IBM state that component codes prefix SYSMOD IDs.
I never said it was an IBM standard. I said standard vendor practice. Maybe
common vendor practice would have been clearer. Vendor PTF's I've seen have 3
On Fri, 3 Nov 2023 22:24:02 -0400, Doug wrote:
> SMPE claims to be the all knowing wizard but won’t do the resolution.
SMP/e is not (nor ever claimed) to be the all knowing wizard. It is a tool used
by IBM and vendors for keeping your z/OS problem free.
It does not resolve problems. It simply
On Fri, 3 Nov 2023 20:51:44 -0400, Phil Smith III wrote:
> I�m interested in how this works.
This must be discussed in the bigger picture of problem management and the
processes involved. Think about problems your child experiences. Your problem
resolution processes for your child will be
16 matches
Mail list logo
