>Do I need to
>make sure OA43495 (or its 2.1 PTF) is applied on a 2.1 system, and
>only then recopy MIGLIB? Or is there a way I can apply the maintenance
>directly to the 2.1 MIGLIB on the 2.2 system?
Surely the necessary thing is to install the APAR (into the 2.1 miglib)
and then use that
> > We saw this internally recently--
> > I believe this specific 878-10 is due to the installation of a +
> +APAR for OA43495 which I think is for new hardware toleration.
> Either some versions of the ++APAR don't have part IOSVFMTC included
> which has updates to IOS formatters that are called
[Yes, I realize I'm replying to an old posting]
On 11 February 2015 at 09:28, Nick Jones wrote:
> We saw this internally recently--
> I believe this specific 878-10 is due to the installation of a ++APAR for
> OA43495 which I think is for new hardware toleration. Either
This solution is assuming that Jake is on the z13 ESP and has part of OA43495
++APARs or PTFs applied.
If this is not the case then, please open a PMR and we'll investigate the
problem.
Nick Jones
z/OS Service Aids
On Wed, 11 Feb 2015 08:28:23 -0600, Nick Jones nrjo...@us.ibm.com wrote:
to see which one fails.
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Elardus Engelbrecht
Sent: Wednesday, February 11, 2015 7:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IPCS error help
Jake anderson wrote:
I am
Hi All,
By IPCS 2.2, i believe he means option 2.2 from the main panel which points to
IP STATUS.
We saw this internally recently--
I believe this specific 878-10 is due to the installation of a ++APAR for
OA43495 which I think is for new hardware toleration. Either some versions of
the
Jake anderson wrote:
I am using the correct version of IPCS to view the dump.
You still did not answered Peter Relson's question about the version.
Please show the exact BLS18223I (or BLS18224I) message.
Groete / Greetings
Elardus Engelbrecht
Jim Mulder wrote:
System ABEND 878, reason code 0010
GPR 8R 9R 7FFF4000 10R 11R 7F809970
System abend code 878, reason code 0016.
Why two different reason codes (0010 and 0016)?
IPCS's ESTAE apparently chooses to format the reason code (x'10')
as a
Jim Mulder wrote:
IPCS's ESTAE apparently chooses to format the reason code (x'10') as a
decimal number (16). That would not be my choice.
Understood. That is the product developers choices.
I have to admit that I cheated, and found it documented in the comments in
module IGVVSERR
I tried with tso region size 20 but no luck.
What do you mean no luck? It still abended? Then try something bigger
than that. And if your site doesn't allow that, then talk to your site
people.
FWIW, my TSO logon panel shows size 2096128.
This happens specifically for IPCS 2.2
What is
Hi Peter
I tried with the same tso region size you have used.
I am using the correct version of IPCS to view the dump.
On 11 Feb 2015 18:18, Peter Relson rel...@us.ibm.com wrote:
I tried with tso region size 20 but no luck.
What do you mean no luck? It still abended? Then try something
Did you try to log off and log on again with more REGION?
justmainfra...@gmail.com (Jake anderson) wrote:
Hi List,
I was trying to open a dump dataset using IPCS 2.2 but it ended with below
message.
System ABEND 878, reason code 0010
PSW 070C1000 814F7878, module IEANUC01, CSECT IGVVSERR,
Hi John
I tried with tso region size 20 but no luck. This happens specifically
for IPCS 2.2
Jake
On 10 Feb 2015 20:32, John Eells ee...@us.ibm.com wrote:
Did you try to log off and log on again with more REGION?
justmainfra...@gmail.com (Jake anderson) wrote:
Hi List,
I was trying to
Hi List,
I was trying to open a dump dataset using IPCS 2.2 but it ended with below
message.
System ABEND 878, reason code 0010
PSW 070C1000 814F7878, module IEANUC01, CSECT IGVVSERR, offset 0E40
Instruction area 00181610 0A0D18CE 18FB180C
GPR 0R 8400 1R 84878000 2R 7F809C10 3R
Jim Mulder wrote:
System ABEND 878, reason code 0010
GPR 8R 9R 7FFF4000 10R 11R 7F809970
System abend code 878, reason code 0016.
Why two different reason codes (0010 and 0016)?
Register 9 contains the size of the request (x'7FFF4000'), which is too
large
I was trying to open a dump dataset using IPCS 2.2 but it ended with
below
message.
System ABEND 878, reason code 0010
PSW 070C1000 814F7878, module IEANUC01, CSECT IGVVSERR, offset 0E40
Instruction area 00181610 0A0D18CE 18FB180C
GPR 0R 8400 1R 84878000 2R 7F809C10 3R
On Tue, 10 Feb 2015 20:37:17 +0530, Jake anderson wrote:
I tried with tso region size 20 but no luck. This happens specifically
for IPCS 2.2
The only time I've had 878's on a region like that was SADumps. But like Jim, I
tend not to use the 2.x commands.
Big dumps in an interactive TSO
17 matches
Mail list logo