  TPU section interactions with DSNlink? 
 The Question is:
 
I made the mistake of going on vacation for a week --
when I got back, my private TPU section file was not
available when I sent mail using VMSmail.  Research
revealed that the only change made on our VAX during
the week was the update of DSNlink to V2.2.
 
We have been running V7.1 for several months and this
problem did not come up until a week ago.
 
I invoke VMSmail using MAIL/EDIT=(SEND,REPLY=EXTRACT).
My mail profile has SET MAIL TPU.  I define logical name
TPU$SECTION as CMD:TPUSEC (my private section file).
 
MAIL, MAILSHR and MAILSHRP are not defined as logical
names.  I can send any other logical definitions,
image idents, etc. as needed.
 
I found that using MAIL/OLD/EDIT=(SEND,REPLY=EXTRACT)
invokes my private section file as expected.
 
 
 
 The Answer is:
 
  You will want to contact the customer support center, as resolving this
  may/will require rummaging around on the system to determine what changed.
 
