Date:         Tue, 16 Nov 1999 10:19:54 +0100
Reply-To:     peter.crawford@DB.COM
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Peter Crawford <peter.crawford@DB.COM>
Subject:      MVS Dilemma: Where to keep documentation?
Comments: To: Dan.J.Lewis@kp.org
Content-type: text/plain; charset=us-ascii

Since putting documentation into the pds, is proposed only to keep it close to
the code, extend the principle -- put a lot of links into that pds member. These
links point to the word, excel, powerpoint, visio or whatever documents hold the
real details. Sure, a brief summary in plain text is a reasonable intro, but
plain text makes diagrams very hard or too brief !
Even though those links in an os/390 mvs pds source member are not going to be
active hyperlinks, they can still provide the document location info.
It would be wise to use unc (universal naming convention) or server ip
addresses, to avoid the problem of changing or slipping standards for "common"
drive letter references.

Good luck
Peter Crawford


Datum:         16.11.99 05:50
An:            SAS-L@listserv.uga.edu




Antwort an:    Dan.J.Lewis@kp.org

Betreff:       MVS Dilemma: Where to keep documentation?
Nachrichtentext:



I am completing a system consisting of some 15 SAS programs and about a hundred
data files. Now it's documentation time. I have a dilemma. I'd like to keep the
documentation in the same MVS library (PDS) as the programs. That way it won't
get lost when I go on to ever greater glory, and the next hapless contractor
will surely stumble across it and hopefully find it useful. However, that
solution seems to require that the documentation be strictly text - no Excel
spreadsheet for a file/program crossreference, no MS-Word with nice formatting,
bolding and italics to help guide the eye. Is there a way to store Excel and
MS-Word documents in an MVS PDS in such a way that it is easily retrievable? Or
does anybody out there have any other suggestions as to how I might approach
this?

Thanks! -Dan