This is a personal choice, but I code each of my segments as follows:
when
do
set
write
exit
end
The 'write' stmt starts with some msg id that uniquely identifies the exit
point, like 'SCDT0001' and then whatever values I think might be helpful
at that point - DSN, DSNTYPE, Unit, etc. This way I always know where the
assginment fell out in the code. It saves oh so evermuch time.
There are a few times when I want to do a set without an exit because I
want it to fall into the remaining code, but even there I have a write.
And yes it does generate extra output and I did get some resistance when I
moved to this shop & started putting in the statements, but I believe I've
convinced the powers that be how useful these statements are when it comes
to debugging problems just like this one.
ddk
**************************************************************************************
This e-mail message and all attachments transmitted with it may contain legally
privileged and/or confidential information intended solely for the use of the
addressee(s). If the reader of this message is not the intended recipient, you
are hereby notified that any reading, dissemination, distribution, copying,
forwarding or other use of this message or its attachments is strictly
prohibited. If you have received this message in error, please notify the
sender immediately and delete this message and all copies and backups thereof.
Thank you.
**************************************************************************************
----------------------------------------------------------------------
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
