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. The ctrace entries are cut by service modules and are meant to a debugging aid to IBM. The record contents are OCO and I can't disclose you the meaning of the fields. I am sorry about this . . If you believe that you are running into a problem and need assistance, I would suggest you to open a defect record to get help. Other than that, I can't assist you. So I guess I'm out of luck. Ken Porowski AVP Systems Software CIT Group E: [EMAIL PROTECTED] -----Original Message----- Don Ault 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 FFFFFFFF you can spot the syscalls that returned -1 (FFFFFFFF). Then pick up the ErrnoJr and run it through BPXMTEXT: TSO BPXMTEXT errnojr If there is something specific you are looking for, I suggest posting it to the MVS-OE forum and see what you get. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
