On Wed, 24 May 2006 18:15:18 -0400, Alan Altmark <[EMAIL PROTECTED] > wrote:
>On Wednesday, 05/24/2006 at 01:37 EST, Brian Nielsen ><[EMAIL PROTECTED]> wrote: >> I've run some traces and know why DDR is abending. If you don't want to >> read the technical details below, the question is: Is this an APAR'abl e >> DDR problem or "user error caused by the HALT - don't do that"? > >Please open a PMR, Brian. Because you asked so nicely ["he's such a >*nice* boy"] and you have such helpful problem determination skills, we' re >inclined to treat it initially as a bug. (And I'm not 100% certain, but I >think it helps that the developer is also named Brian.] Okay, will do. (Honestly, though, my personal opinion is that usage note 1 for HALT probably applies: "1. ATTENTION: Use this command only in extreme cases and after careful consideration. Indiscriminate use of thi s command may cause unwanted results.") HALT causing DDR to abend is obviously an unwanted result. :) Maybe I'm getting a free pass because I'm not using it indiscriminatly. >But I ask you, why can't everyone else include a nice detailed analysis of >the problem in *their* problem descriptions? I mean, it's not like in >some alien language like Java or C++! ;-) [OCO modules excluded, of >course] OCO modules never stopped me! Back in 1987 I wrote a disassembler in REX X that processed TEXT decks and MODULES and created assembler source with labels. Later on (1989) I used it to create a ZAP to the COBOL compiler to remove it's requirement for using an auxilary directory. This allowed COBOL to run from a minidisk whose directory had been saved in a DCSS wit h SAVEFD. Brian Nielsen
