RE: program crash

You're right. I don't see any information (as it relates to a file
problem) that is in a dump without the SDS and INFDS that I gain by
adding those structures.

Since it's our standard here to include the SDS and preferably the
INFDS, I'm used to looking for those areas first. 

If nothing else, by jumping directly to the SDS definition in the dump I
can see what file or operation is involved, without having to read
through all the information at the start of the dump if there are lots
of files. But that's little as far as an improvement.

Thanks for the comment

Jim Wiant


Jim Wiant wrote:
> 
> By adding the Program SDS and file INFDS structures to the program,
> you'll have a lot more information available in the dump - especially
> file details from the INFDS including the last operation performed.
> 

I think you'll find most (all?) of that information in the top section
of the formatted dump (before the variables) even if you don't code the
PSDS or INFDS structures in your module.


This message has been sent from Foodstuffs (Auckland) Limited ("Foodstuffs").

The information contained in this message and or attachments 
is intended only for the person or entity to which it is 
addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon, this 
information by persons or entities other than the intended 
recipient is prohibited. If you received this in error, 
please contact the sender and delete the material from any 
system and destroy any copies.

The views and opinions expressed in this message may be those
of the individual and not necessarily those of Foodstuffs, 
and are not given or endorsed by it.

Please note that this communication does not designate an 
information system for the purposes of the Electronic 
Transactions Act 2002.