When we got HTT00x abends, the explanation was more generic, something like, "A module which is OCO had a problem. Contact IBM." The same generic explanation was there, verbatim, for every HTTxxx abend. If the source were shipped, there would be no reason for these codes. It doesn't explain the abend. Rather, the existence and explanation of the abend refutes the statement that you ship source, at least for some components.
The very first HTT abend we had was caused by another vendor's software. I am glad to see that the RCFs do some good. Now, there is information that might have led us to them as the source or, perhaps led them to the problem. When it happened, we naturally sent the dump to IBM, as instructed, and waited until your folks said, "It isn't our problem," before the other vendor really got involved. (We sent them the dump right after sending it to IBM, but they did not have any idea where to look based on the abend code or description. They waited for IBM to make the first determination. Then, they had to enlist help from IBM in order to find the problem.) -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark Sent: Thursday, January 04, 2007 2:35 PM To: [email protected] Subject: Re: IBM ServiceLink greenscreen to be discontinued March 31, 2007 On Thursday, 01/04/2007 at 01:37 PST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > Hmmmm. If you ship source, what is the purpose of the HTTxxx series of > abend codes? Ooooh! Pop quiz! >From a read of HTT001-HTT003 the z/VM 5.2 CP Messages & Codes book, they are abends dealing with incorrect linkage between CP modules (programming errors). Yes, OCO modules can issue abends. Sometimes we give details on those abends and sometimes we just say "Call us". (All HTT abend explanations end with "Contact IBM".) But I'm not sure how our shipping source (or not) changes the explanations of abend codes or your use of VPL. Alan Altmark z/VM Development IBM Endicott
