I am not sure what your intent will be. I have added empty datasets in the LINKLST just after the SYS1.LINKLIB entry. That way I can add fixes for products that are below that entry that I can zerodir (empty the dataset) should I need to reverse the change.
However, if you are installing a fix, then IPL for SYS1.LINKLIB is usually safer. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Mark Jacobs > Sent: Thursday, September 11, 2014 7:30 AM > To: [email protected] > Subject: Re: CSV513I Issued for SYSLIB LINKLIB(xxxx) dataset > > AFAIK, this is the first time I've tried it. We're at zOS 1.13. > > I was just hoping that there was an option available on the command that would > allow a wise, or bold, systems programmer to override this restriction. > > Mark Jacobs > > On 09/11/14 10:19, Lizette Koehler wrote: > > Mark, > > Not all datasets can be deleted from a Linklst. This message > > indicated your dataset are in that category > > > > CANNOT DELETE SYSTEM DATA SET > > You cannot delete system data sets SYS1.LINKLIB, SYS1.MIGLIB, > > SYS1.CSSLIB SYS1.SIEALNKE, and SYS1.SIEAMIGE from a LNKLST set. > > > > > > Were you able to do this in the past? > > Is this the first time you are doing this dataset? > > What version of z/OS? > > > > > > Lizette > > > > > >> -----Original Message----- > >> From: IBM Mainframe Discussion List [mailto:[email protected]] > >> On Behalf Of Mark Jacobs > >> Sent: Thursday, September 11, 2014 5:40 AM > >> To: [email protected] > >> Subject: Re: CSV513I Issued for SYSLIB LINKLIB(xxxx) dataset > >> > >> Here's our SYSLIB statements; > >> > >> SYSLIB LINKLIB(SYS1.&SYSNAME..LINKLIB) SYSLIB > >> LPALIB(SYS1.&SYSNAME..LPALIB) > >> > >> My commands were; > >> > >> SETPROG LNKLST,DEFINE,NAME=TEMP,COPYFROM=TCS2 > >> CSV500I LNKLST SET TEMP HAS BEEN DEFINED > >> > >> SETPROG > >> LNKLST,ADD,NAME=TEMP,DSN=SYS1.TCS2.LINKLIB.TEMP,ATTOP > >> CSV501I DATA SET SYS1.TCS2.LINKLIB.TEMP HAS BEEN ADDED TO > LNKLST SET > >> TEMP > >> > >> SETPROG LNKLST,DELETE,NAME=TEMP,DSN=SYS1.TCS2.LINKLIB > >> CSV513I DATA SET SYS1.TCS2.LINKLIB 136 WAS NOT DELETED FROM > LNKLST > >> SET TEMP. > >> CANNOT DELETE SYSTEM DATA SET > >> > >> Mark Jacobs > >> > >> On 09/11/14 08:29, Elardus Engelbrecht wrote: > >>> Mark Jacobs wrote: > >>> > >>>> I tried to replace the SYSLIB LINKLIB dataset in the linklist, but > > SETPROG > >> wouldn't let me delete the in use one from the newly defined linklist set. > >>> Please show us your command attempt(s) and/or PROGxx member and the > >> resulting message(s). > >>>> IMHO, it either should be allowed for any of the SYSLIB datasets in > > PROGxx, or > >> at the least have an option on the SETPROG command that tells it that > >> you understand the risks, but full speed ahead. > >>> There is such command, but just tell us what did you do? > >>> > >>>> UNIX was not designed to stop its users from doing stupid things, > >>>> as > > that would > >> also stop them from doing clever things. > >>> A fool is better than foolproof software... <grin> > >>> > >>> Groete / Greetings > >>> Elardus Engelbrecht > >>> > >> > >> -- > -- > Mark Jacobs > Time Customer Service > Tampa, FL > ---- > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
