Re: SQL strangeness

John,

A tip - for any connection, you can also see the library list by expanding Objects => Base Pool => Library List, if you have filter pools visible and haven't removed the library list filter from the base pool.  I think the library list filter also shows without pools being visible, but I don't remember anymore, as I've been using filter pools since '07.

Setting the library lists in the connections (I use a mix of job descriptions, initial commands, and library lists set in the connection) and knowing which connection I'm using when I use the RSE tree isn't an issue for me.  I don't use the table view for opening members, so that's not a problem, either. 


My problem is that there are so many members in our production source files (15,555 and growing in our largest QRPGLESRC, for example) that always using filters when I need to browse a production source member (not development) is completely impractical.  If I know the member name, usually because it's in a source I already have open or I know the process flow well enough to remember, I use Ctrl-Shift-A.  If I forget to check the connection, I may get the wrong library list, which could result in the outline not loading, or loading with incorrect information (yeah, we actually have different files with the same name in different libraries - gah!), and of course not compiling (if I need to put a copy in a development library for debugging).  Years of screwing up have made me careful and I don't often do this to myself anymore, and when I do I usually recognize it quickly, but it sure would be nice to be able to easily tell which connection I opened any
particular member with.

If I tried to work with only one connection open at a time, I'd never get anything done, especially with cross-environment programs.  And please, let's not talk about reorganizing source or environments or anything of that nature.  This system has been growing for roughly 20 years, with a staff of never less than 40 developers, a high of over 125 developers, and currently somewhere around 75.  Making system organization changes is hard, and getting agreement to make changes is worse.  I'd rather herd cats.  A LOT of cats.

 
Dave Shaw


________________________________
From: "Voris, John" <john.voris@xxxxxxxxxxxxx>
To: "wdsci-l@xxxxxxxxxxxx" <wdsci-l@xxxxxxxxxxxx>
Sent: Thursday, January 9, 2014 9:15 AM
Subject: [WDSCI-L] SQL strangeness


There has been numerous arguments showing that many of us use various Liblists to compile source with.  And that yes, it can be confusing to know where you are in RSE or Table Views.
So I thought I would summarize how I manage Liblists .aka. Environments .aka. Connections.

#1 I set the Liblist on each Connetion with *JOBD. 
This is the Compiling *JOBD of various Liblists leftover from the SEU days
 
But I have found that getting Connections set up right using *JOBD is a pain, because what I think I did to finally get this to work is have ONLY one connection open when I set the *JOBD settings on the panel Connections > Subsystems > Commands.  After setting it, you have to close the connection,
Then you have to open the next connection to set the next *JOBD.  And so on.


#2 I have a right-click User Action that does a PRTLIBL.
My User Action is a simple command DSPLIBL *PRINT, and back on the green screen side, then WRKSPLF shows me a QPRTLIBL report that shows me the library list of the Liblist in effect.
( Because of how User Actions work, I had to create two User Actions, a PRTLIBL for Members, and a PRTLIBL for Objects. )

When the user action runs, a panel of the connection opens a panel on the Commands Log which show which connection is open.
This "Joblog" of the Command/User Action shows me my User Action and it also shows what connection I am using.  The Connection Name is in the Panel Tab-Name.

If I do my right-click User Action on a source member on a different Connection, then what I see in the "Commands Log", is that a new panel is created and the panel Tab-Name is the current Connection Name. 
So now I know where I am in my stack of projects and connections, and I am ready to compile, or ready to edit and find the copybooks, etc.