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:
Since forever. What I'm saying is so simple that I must have misspoken. I'm
saying that the earliest messages that appear on the IPL console also appear in
syslog. These messages, issued long before JES starts--including the start of
JES itself--are captured and eventually written to the syslog
Of course Barbara is right. Operlog for the same reIPL I quoted in my previous
post shows the full sequence of shutdown messages pretty much up to the XCF
wait state. So there is a clear advantage to letting operlog run right up to
the edge of the cliff. Do not shut it down.
.
.
.
J.O.Skip
Jake,
Please provide the following information.
1) When you initiate IPCS for this dump it will produce messages that indicate
what level of IPCS, Post these messages completely. All of them
BLS18223I Dump written by product-name sourceis an example of the
message.
2) What is the
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
In
874b151289704e46a874bf2ae6fdd8d1208d2...@kl126r4b.cs.ad.klmcorp.net,
on 02/11/2015
at 01:16 PM, Vernooij, CP (ITOPT1) - KLM kees.verno...@klm.com
said:
This is working for 2 or 3 decades at least since SVS.
MTRACE is not SYSLOG, nor did it exist in SVS. It's a small virtual
storage buffer,
In
cy1pr0101mb0763bf9493941ee86e7639ecce...@cy1pr0101mb0763.prod.exchangelabs.com,
on 02/11/2015
at 04:36 PM, J O Skip Robinson jo.skip.robin...@sce.com said:
Since forever. What I'm saying is so simple that I must have
misspoken. I'm saying that the earliest messages that appear on the
IPL
Lizette:
Don't waste effort in doing this. Docet from RES (www.res-it.com) does this
and more. And, it gives you the ability to go from the source objects (program
source) through to what scheduler nets are using files, jobs, procs, programs,
etc. It is THE most powerful JCL management
On Tue, 10 Feb 2015 10:56:16 +, Kees wrote:
We have a Resource Group in our Sysplex, which covers several LPARs. The group
is defined as Capacity is in Service Units with Sysplex Scope.
Personally I've always preferred a percentage - different machines in the same
plex may well have
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
On Tue, Feb 10, 2015 at 11:58 PM, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
In
bn1pr0101mb07546706ca5f178b84197399ce...@bn1pr0101mb0754.prod.exchangelabs.com
,
on 02/10/2015
at 06:43 PM, J O Skip Robinson jo.skip.robin...@sce.com said:
There is surely no advantage
This is working for 2 or 3 decades at least since SVS.
You could see the block of messages, like IEA101A Specify system parameters,
inserted into Syslog some time after syslog was active. I believe, they have
been reordered to appear now in correct chronological order.
This is the same buffer
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
Lizette Koehler wrote:
I am looking to see if there are any easy ways to do the following
Mitch gave you a solution, but if you don't want a new product or lost ( damn!
;-D ) some useful to purchase it ...
Control card Input that affects the DSNx is okay to list - no need to know
what
We use SYSLOG, not OPERLOG. And I see the NIP messages in it. It appears
that they are buffered and written to SYSLOG once JES2 comes up and SYSLOG
is available. Given our small size, I don't know if this buffer is a wrap
around and so might lose messages if there are a lot of them before
Shmuel Metz (Seymour J.) wrote:
J O Skip Robinson said:
I'm saying that the earliest messages that appear on the IPL console also
appear in syslog.
Yup. If you still miss them, you quickly remember to use 'K S' next time to
stop scrolling. But this is not a big concern for me.
That's quite
We have a VSAM KSDS that was allocated and populated with data prior to
the CA/Reclaim function being available. This evening we had to reorg
the dataset, and the REPRO back used the same physical dataset with the
REPLACE and REUSE options.
Does this enable CA/RECLAIM for the dataset, or do
20 matches
Mail list logo
