Listers -
I think this brings up a good issue. It would be NICE if some VENDOR would
create a process that could do this kind of work.
I believe it could be helpful to have a gui/tso front end where I would point
to my ACS source and SCDS/ACDS datasets and RACF/ACF2/TSS database. And it
wou
ssage-
>> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
>> On Behalf Of retired mainframer
>> Sent: Thursday, August 23, 2012 2:13 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: Documenting SMS environment & ACS routines.
>>
>&g
riginal Message-
> :>: From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> :>: Behalf Of McKown, John
> :>: Sent: Friday, August 24, 2012 5:41 AM
> :>: To: IBM-MAIN@LISTSERV.UA.EDU
> :>: Subject: Re: Documenting SMS environment & ACS routine
;: To: IBM-MAIN@LISTSERV.UA.EDU
:>: Subject: Re: Documenting SMS environment & ACS routines.
:>:
:>: 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 gua
2:13 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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.
>
>
;: To: IBM-MAIN@LISTSERV.UA.EDU
:>: 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 v
to:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Darth Keller
> Sent: Thursday, August 23, 2012 11:30 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Documenting SMS environment & ACS routines.
>
> I might sound like a broken record but I'll say it again -
>
> If you do
I might sound like a broken record but I'll say it again -
If you don't already know how to use Naviquest, learn to use it - if
you're going to re-write code, it will be your friend. Unless you have a
test-plex or a 3rd party product, Naviquest will give you a safe way to
test your code chang
AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Documenting SMS environment & ACS routines.
>
>That's a good idea, if/when we try to upgrade how we do things. But my main
>emphasis right now is how to document them. I am not really very good at
>documenting. I could really use
Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of McKown, John
> Sent: Thursday, August 23, 2012 11:04 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Documenting SMS environment & ACS routines.
>
> That's a good ide
012 12:54 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Documenting SMS environment & ACS routines.
>
> Using DFP segments can make the ACS routines very simple. When a file
> is
> defined in Racf, you add the SMS Management Class and the SMS Storage
> Class
> and in the AC
Using DFP segments can make the ACS routines very simple. When a file is
defined in Racf, you add the SMS Management Class and the SMS Storage Class
and in the ACS routine you add code that says, if the DFP Management class
segment is coded, use it. If the DFP Storage class segment is coded, use
it
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.
--
Jo
13 matches
Mail list logo
