On Wed, Mar 16, 2016 at 10:51 AM, Hansen, Dave L - Eagan, MN < [email protected]> wrote:
> Hi, > > I went to https://listserv.ua.edu/cgi-bin/wa and did a search on > IBM-MAIN and IBM-MAIN-ARCHIVES (1986-2004). I did a search for SYSPROC and > got no match. > > On one system I have ISRDDN showing SYSPROC with my CLIST concatenated. > I can use ALTLIB (or SPROC) to add it in to the other system. But I have > to manually add these and repeat it. > > My logon Procedure is xxxACCNT. I looked in SYS2.LOG and > SYS2.CLIST(SPFALLOC) for my userid to find userid.CLIST but am not finding > it. > > I looked through the userid.lpar.ISPF .PROFILE datasets. ISRPLIST > shows the last 30 referenced data sets. > > Q). How did I get my CLIST Concatenated permanently? I would like to do > it again. > Actually, nobody here can tell you -- exactly. We do the same. In our logon PROCEDURE, we have a //TSOISPF EXEC PGM=IKJEFT01,PARM='LOGON'. In the SYSPROC DD concatenation, we have a member called LOGON which is what that executes. It is a REXX exec. One of the things that it does is re-allocate the SYSPROC DD to include, if it exists, the equivalent of DSN=&SYSUID.TSO.CLIST . Something like that is most likely what is happening at your shop. But you'll need to track down the CLIST/REXX programs invoked by the "xxxACCNT" logon procedure to determine what you need to do. There is not "IBM standard" way to do this. > > > Thank you, Dave > -- A fail-safe circuit will destroy others. -- Klipstein Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
