Shimon,
VMSES/E is a great tool, but the clarity is not quite the best at some
times> It seems that error message from building segments is a particular
weak point to me, too.
One command that has helped me understand VMSES/E a lot better (until I
forget again!) is one I use after any VMSES/E command failure, and when
trying to better understand what files it has just changed:
LISTFILE * * * (TODAY
If you are (perhaps rightly) concerned about changed files on disk that
are no longer accessed, but still LINKed, then the FILEFILE EXEC which
I've posted here before can perform the same quick search function on even
those disks not currently accessed via:
FINDFILE * * * (TODAY ISO
All the changed files (on accessed disks) will show right up, making the
detective work somewhat less tedious.
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily
represent the opinions or policies of Hewitt Associates.
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal policies
and to protect our business. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have accepted these risks if you communicate
with us by e-mail.
