One of my favorite campfire routines. She: Pa, ya gotcher foot in the fahr. Pause She: Pa, ya gotcher foot in the fahr. Pause She: (Emphatically) Pa, ya gotcher foot in the fahr! He: Yeah Ma? Which one?
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Tuesday, May 16, 2017 9:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: setrog lnklst question UPDATE JOB(*) is dangerous. And was discussed in the IBM MAIN Archives, a couple of years ago I think. However, we use it with no ill effect. UPDATE Indicates that the system is to update an address space so that a specified job or jobs associated with that space can use the current LNKLST set. If the job is using another LNKLST set when the current LNKLST set is activated, it will continue to use the original LNKLST set until it completes operations. When the job completes and restarts, it then uses the data sets defined in the new currently active LNKLST set. See "Removing or Compressing a Data Set in an Active LNKLST Set" in z/OS MVS Initialization and Tuning Reference for information about LLA management of the LNKLST data set. Be careful when you use UPDATE. Updating an address space while a program in that address space is fetching a module can cause the fetch to fail or to locate an incorrect copy of the module. The system does not attempt to verify the validity of the data for UPDATE. Start of changeJOBNAME | JOB=jobnameEnd of change Specifies the name of the job or jobs to update. You can use wildcard characters (? or *) for jobname. UPDATE updates any job whose name matches the specified criteria. The system compares jobname to the name of any initiated job or jobs that match, or to the name of the address space. Dangle your foot in the fire. If it does not burn you are okay, If it does, take it out Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Gibney, Dave > Sent: Tuesday, May 16, 2017 4:10 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: setrog lnklst question > > And the LNKLST UPDATE JOB(*) is documented as potentially dangerous. > > On the other hand, so far, I haven't have need to modify my linklst > and effect all running address spaces. It's usually limited to a smaller > subset. > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler > > Sent: Tuesday, May 16, 2017 3:25 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: setrog lnklst question > > > > So an EXAMPLE would be > > > > /* */ > > /* Adding a dataset to the LINKLIST when it */ > > /* does not already exist */ > > /* */ > > LNKLST DEFINE NAME(NEWLNKA) COPYFROM(CURRENT) > > LNKLST ADD NAME(NEWLNKA) DSNAME(SYS1.NEWDSN.INLNK.LIST), > > AFTER(SYS1.LOCTION.INLNK.LIST) > > LNKLST DELETE NAME(NEWLNKA) DSNAME(SYS1.DELETE.THIS.LNKLST.DSN) > > LNKLST ACTIVATE NAME(NEWLNKA) > > LNKLST UPDATE JOB(*) > > APF ADD DSNAME(SYS1.NEWDSN.INLNK.LIST) VOLUME(&SYSR3) > > > > > > APF ADD is not needed if the file being added is already APF Authorized. > > DELETE is not needed if you are not removing anything from the Linklst. > > > > > > Lizette > > > > -----Original Message----- > > >From: Lizette Koehler <stars...@mindspring.com> > > >Sent: May 16, 2017 3:19 PM > > >To: IBM-MAIN@LISTSERV.UA.EDU > > >Subject: Re: setrog lnklst question > > > > > >You can create a parmlib member to > > > > > >COPY the current linklst to a new name Activate the new linklist > > >name > > > > > >If you need further assistance let us know. > > > > > >Lizette > > > > > >-----Original Message----- > > >>From: william janulin <0000008d52e04f2e-dmarc- > > requ...@listserv.ua.edu> > > >>Sent: May 16, 2017 1:52 PM > > >>To: IBM-MAIN@LISTSERV.UA.EDU > > >>Subject: setrog lnklst question > > >> > > >>To list; > > >> Is it possible to add a dataset to the active lnklst? I tried a > > >>setprog lnklst > > add command and got a messagethat the lnklst was active. > > >> > > >>Thank you in advance, Bill J. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
