OK, I've got a component trace of SYSOMVS and formatted via IPCS but
where are the trace entries documented/mapped? I've been looking
through TFM but can't find it.
And you're not goint to. AFAIK, the only place you can find a mapping of the
trace entries for the various ctraces is in the module
SYSOMVS trace entries are not documented. There are thousands of them and
they were created primarily to allow USS service to debug problems.
One tip: if you look for SYSCALL EXIT trace entries, the last 3 words
contain Return value, Errno, ErrnoJr.
By scanning the trace for you can
Cross posted to IBM-MAIN and MVS-OE
I opened an ETR/ASKQ --- here's the reply
Hello Ken,
unfortunately, the only externalized information about ctraces
can be found in the MVS Diagnosis: Tools and Service Aids.
On Wed, 2006-04-26 at 09:49 -0400, Porowski, Ken wrote:
I opened an ETR/ASKQ --- here's the reply
...
The record contents are OCO and I
can't disclose you the meaning of the fields.
What a load of horsesh1t(*) .
If it isn't bad enough that we have to put up with OCO
What a load of horsesh1t(*) .
If it isn't bad enough that we have to put up with OCO code-base,
we now have to put up with OCO diagnostic data
What good is the diagnostic data without the code? So you get a RC of
XYZ from a module you never heard of doing an undisclosed function. What
would
On Wed, 2006-04-26 at 10:17 -0400, Bob Shannon wrote:
What good is the diagnostic data without the code? So you get a RC of
XYZ from a module you never heard of doing an undisclosed function. What
would that tell you?
So, you're advocating IBM should tear up the Diagnostics manuals, and
stop
What good is the diagnostic data without the code? So you get a RC of
XYZ from a module you never heard of doing an undisclosed function.
What would that tell you?
So, you're advocating IBM should tear up the Diagnostics manuals, and
stop shipping IPCS and any other diagnostic aids to
But some of the info could be of value.
In my case I was tracing FILE entries. It would have been nice to know
if the VN_RDWR trace entry was a read or a write and maybe to what file
etc.
I doubt my issue was a 'defect' so why would I open a defect ETR just to
have someone tell me what I was
I doubt my issue was a 'defect' so why would I open a defect ETR just
to have someone tell me what I was doing?
I would think that IBM would like us to debug our own problems (or at
least try) before 'bothering' them with diags.
I agree with you philosophically, but reality is different. I had
I don't feel guilty, we're paying for the support.
I just like to do as much as I can on my own, how else can I be a Guru
when I grow up?
Anyone know if a SHARE requirement for better trace info might get
anywhere? Or maybe enhanced IPCS formatting of the trace entries? It's
probably been
-Original Message-
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of Shane
Sent: Wednesday, April 26, 2006 9:12 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ARGH! SYSOMVS Component Trace - Trace entry mapping
On Wed, 2006-04-26 at 09:49 -0400, Porowski
JES2 exits - which
*required* changing between releases?
Chris Mason
- Original Message -
From: McKown, John [EMAIL PROTECTED]
Newsgroups: bit.listserv.ibm-main
To: IBM-MAIN@BAMA.UA.EDU
Sent: Wednesday, 26 April, 2006 5:11 PM
Subject: Re: ARGH! SYSOMVS Component Trace - Trace entry
Remember what the O in OMVS used to mean?
-jc-
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at
On Wed, 26 Apr 2006 10:56:39 -0400, Porowski, Ken [EMAIL PROTECTED]
wrote:
...
Anyone know if a SHARE requirement for better trace info might get
anywhere? Or maybe enhanced IPCS formatting of the trace entries? It's
probably been tried before.
...
This would have to be done product by
What good is the diagnostic data without the code? So you get a RC of
XYZ from a module you never heard of doing an undisclosed function. What
would that tell you?
From experience (when I had OCO-access while I was IBM) I know that the
return codes are usually described in some non-OCO
Cross posted to IBM-MAIN and MVS-OE
OK, I've got a component trace of SYSOMVS and formatted via IPCS but
where are the trace entries documented/mapped? I've been looking
through TFM but can't find it.
Thanks all
Ken Porowski
AVP Systems Software
CIT Group
E: [EMAIL PROTECTED]
16 matches
Mail list logo
