I like that idea. Sometimes the simplest ideas are the hardest for an old dog to recognize.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Tom Marchant Sent: Friday, January 08, 2010 8:25 AM To: [email protected] Subject: Re: LNKLST & APF Help On Thu, 7 Jan 2010 16:05:49 -0500, Don Williams wrote: >I admit it, I'm lazy. I don't like having to track the current LNKLST set >name (we only IPL production 2 to 4 times a year as needed). I would like to >use the same LNKLST set name that is in my PROGxx member that I used during >the IPL. It could work similar to GDGs. I would backup and make my changes >to our PROGxx member (member name never changes, so no update is required to >IEASYSxx), do a T PROG=xx (that checks and implements my changes and I'm >fairly sure that the next IPL will succeed). The new LNKLST set would be >named LNKLST (or whatever name we were using), the previous one would be >renamed to LNKLSTnn, such that LNKLST1 would be oldest, LNKLST2 would be >next oldest, etc. Why do you need to track the current LNKLST set name? You could get the same effect if every time you updated your PROGxx you changed the name of the LNKLST by incrementing the nn or even by including the date of the change as part of the name, e.g. LNKLSTyymmdd. That could simplify your procedure by requiring only one change. -- Tom Marchant ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
