GDPS problem determination/detection tool

We will be taking a multi-faceted approach on this broad requirement: (1) the GDPS EasyLog tool - is a windows-based tool created to help you to create and easily download the Syslog and Netlog on a z/OS environment; it has two main objectives: (1) quickly downloading Syslog and Netlog from a z/OS environment on your computer and (2) analyzing the Netlog; and is applicable for all the GDPS products: and (2) ongoing GDPS diagnostics strategy - identify an issue with a GDPS token and then you can search for the GDPS token in netlog to get detailed info; this concept has been rolled out in different parts of GDPS (such as copy services support (e.g., GM)); and will continue to be extended to other areas within GDPS.

As other customers said, we would like to see all GDPS-messages associated with a message ID so we are able to find the description belonging to the error. Right now we need experience or luck when guessing what a message is supposed to mean.

A good idea, but a shame that we need it. The Netview log is almost incomprehensible and is full of traps. I'd prefer it if IBM tried to make it a bit more friendly.

LBG would be supportive of this idea. We consider it a high priority and would like it within the next two years.

Yes, a very good idea. One thing though and I think it was mentioned years ago. Could all GDPS messages be given a message ID? That would go some way in assisting, as it's only via experience that one gets to know what a message is saying, if it has no ID.

A silly example off the cuff is (albeit here easily understood) -

GEORPT ****************************************************

GEORPT * Coupling Facility List

GEORPT *---------------------------------------------------

GEORPT * CF1W1 008561.IBM.02.00000003E818

GEORPT * CF2W1 008561.IBM.02.00000005CFB8

GEORPT *---------------------------------------------------

GEORPT * GDPS Managed Coupling Facility list

GEORPT *---------------------------------------------------

GEORPT * CF1W1 008561.IBM.02.00000003E818 SITE1

GEORPT * CF2W1 008561.IBM.02.00000005CFB8 SITE2

GEORPT ****************************************************

None of the messages have a message ID.

It was just an idea.

A good idea and always useful to be able to pinpoint errors quicker.

Would be useful

Nice to have

Always a good addition to have more/faster information for problem determination. Or at least have (error) messages highlighted / marked in the Netlog.

Good idea. It always makes sense to make things easier

FIS/Worldpay agrees this would be helpful.

Could be useful.

This is a great idea!

We would appreciate such a solution. Many GDPS messages tell us to look for more information in the Netview log. And that contains tons of messages from all kind of Netview tasks as well as system messages. It's often hard to find the right information. And if the root cause is on another system it makes things not easier.

So broad to implement at once, but a start can be: add relevant info step by step. when you solve a PMR, and know which messages were the ones that you were looking for, add those. Step-by-step this might get better and better (or SMEs can read the netlog better, I know).

This would be very applicable to our site. We often find it difficult to dig through logs and decipher what the actual issue is.

For sure, interesting as idea, but not very urgent in my opinion.

I can see it would be a useful feature.

While Easylog may provide some details from the collected logs, the big stumbling block here (for us at least) is going to be that it is a Windows solution required on your laptop/PC.

Unfortunatley that is not going to be allowed within Citi, unless it's a fully supported like all other IBM software providing PTF's, SECINT fixes, EOS/EOL, etc etc.

Thanks

John

.Have you looked at the EasyLog tool available on the GDPS FTP site?

Have you looked at the EasyLog tool that is available on the GDPS FTP site?