Hello Lizette , I apologize for the confusion . Actually , we support multiple customers and i should have told that first .
The plan of moving product libraries off my sysres is on a completely different environment and the question of missing XCFAS ENQ is for a different client system . Both are totally different environments .Your suggestion of using the IEASYMxx is exactly what we are planning to implement there . At the moment , plan of moving the product datasets off sysres is on HOLD , and i would resume that work again after a couple of weeks . I will post the progress of that work on the other thread . Now coming back to XCFAS ENQ , Here , we are running a parallel sysplex environment with 4 LPARS and all share the same DASD's . Today i accidentally tried to rename a dataset which was in Linklist . Then from ISPF , i found that its held by LLA and i didnt find an XCFAS ENQ there . Then i checked other datasets in the linklist , and it turned out as "No XCFAS ENQ for any of them" I was wondering how that could happen . Being a production LPAR , i don't believe anybody would have tried a SETPROG UNALLOCATE . Could this have something to do with GRS setup ? Once again , I want to thank you for your support and really appreciate the way you help me all the time :) Regards, Baby On Sun, Oct 6, 2013 at 4:58 AM, Lizette Koehler <[email protected]>wrote: > I would like to know more detail on what you are trying to accomplish. > > From previous posts you wanted to move your product libraries off of your > sysres. Is this part of that plan? > > If so, you may be making a very complicated environment. > > So, could you provide some insight to the following > > Will all LPARs be unique? They will not share dasd or datasets? That > includes JES2 spool? Or are you setting up unique LPARs that will will be > in MONOPLEX? Or are you going to do a SYSPLEX? > > I find sometimes it is easier to have a Usercat for my product libraries > that are shared in grouped (Sysplex) environment. > > Could you tell us what your goals are with these questions about APF, > moving > Product libraries off the SYSRES and what your environment is in general? > Sysplex or Monoplex? > > > We will give you lots of answers but they may not apply equally to what you > are trying to accomplish. > > I like using IEASYMxx member that uses different symbolics based on the > IPL/LPAR name. So you can code each LPAR in the IEASYMxx member and put a > different answer to that same symbolic. Maybe something along that line > might be easier? > > I worked in one shop where all of my LPARs were sharing all of the DASD but > they were different sysplex names. So I determined it would be easier to > use SYMBOLICRELATE function and IEASYMxx to have unique dataset names that > resided in a Usercat. Maybe something like that would be easier for your > requirements? > > > Lizette > > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of baby eklavya > Sent: Saturday, October 05, 2013 3:05 PM > To: [email protected] > Subject: Re: No XCFAS ENQ seen on a LNKLST dataset - Confusing ! > > Yes..But this is a pure production system and am sure that no such commands > were issued since the last IPL . > > That's why am confused ! > > > On Sun, Oct 6, 2013 at 3:32 AM, Ed Jaffe <[email protected] > >wrote: > > > On 10/5/2013 2:53 PM, baby eklavya wrote: > > > >> Am curious how that can happen . Is there a way an XCFAS ENQ can be > >> eliminated while having those datasets in the linklist .We are on > >> Z/os > >> 1.11 > >> running 4 lpars sharing the same LNKLST set for all the LPARS . > >> Please share your thoughts on this > >> > > > > SETPROG LNKLST,UNALLOCATE > > SETPROG LNKLST,ALLOCATE > > > > -- > > Edward E Jaffe > > Phoenix Software International, Inc > > 831 Parkview Drive North > > El Segundo, CA 90245 > > http://www.phoenixsoftware.**com/ <http://www.phoenixsoftware.com/> > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
