John, I wished I could help out. I have to write manuals for our products, writing isn't one of my finer points. I was thinking about creating a file to feed Visio to do doc work like what your referring to
Scott ford www.identityforge.com On Aug 24, 2012, at 8:41 AM, "McKown, John" <[email protected]> wrote: > Thanks for that LISTPRT pointer. I used it to create data sets with that > data. That will make it easier to include in my documentation. Of course, > doing so will almost guarantee that the documentation will become obsolete. > We're not too good on keeping our documentation up to date. > > -- > John McKown > Systems Engineer IV > IT > > Administrative Services Group > > HealthMarkets(r) > > 9151 Boulevard 26 * N. Richland Hills * TX 76010 > (817) 255-3225 phone * > [email protected] * www.HealthMarkets.com > > Confidentiality Notice: This e-mail message may contain confidential or > proprietary information. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. HealthMarkets(r) is the brand name for products underwritten and > issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake > Life Insurance Company(r), Mid-West National Life Insurance Company of > TennesseeSM and The MEGA Life and Health Insurance Company.SM > > >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] >> On Behalf Of retired mainframer >> Sent: Thursday, August 23, 2012 2:13 PM >> To: [email protected] >> Subject: Re: Documenting SMS environment & ACS routines. >> >> ISMF options 3, 4, 5, and 6 have the LSTPRT command to document the >> properties of every data class, management class, storage class, and >> storage >> group. >> >> Option 7 can identify from where each of the ACS routines was compiled >> so >> you can find the source if it still exists. It can also identify any >> test >> cases your storage admin used when he developed the system. >> >> The D SMS system command can display the status of each storage group >> and >> the volumes in that group. >> >> Unfortunately, none of this will give you the philosophy or rationale >> of why >> things are this way. You will have to infer that based on your >> understanding of your business environment and anything you know about >> the >> admin himself. >> >> :>: -----Original Message----- >> :>: From: IBM Mainframe Discussion List [mailto:IBM- >> [email protected]] On >> :>: Behalf Of McKown, John >> :>: Sent: Thursday, August 23, 2012 10:35 AM >> :>: To: [email protected] >> :>: Subject: Documenting SMS environment & ACS routines. >> :>: >> :>: We have a rather "fragile" SMS environment at present. It has >> basically >> :>: grown "ad hoc" over the course of almost 2 decades. I really need >> to >> :>: document it very well. Once documented, I would like to use that in >> :>: order to reengineer the environment. Any pointers would be greatly >> :>: appreciated. >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
