× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Rick,

I like your system.  I'm interested to know - do you have any specific 
problems with it?  You said you had been doing it all wrong, but I would 
say that there isn't really a right or wrong way to do it, just whatever 
works anyone's particular case.  That said, I'll explain how I use filter 
pools.  It sounds to me like you have a different development process than 
we do here, so this may not help you specifically, but with luck it will 
give you some ideas that you can apply to your situation.

I generally only use one connection, as I mostly do development in one 
development library, and don't have need for different library lists very 
often.  However, this tended to make each filter rather cluttered.  The 
solution I came up with was to create one filter pool for each application 
group that I work on regularly.  Our naming convention includes a 
two-letter code for application type.  DS for dispatch, FL for fuel and 
mileage tracking, VM for vehicle maintenance, etc.  Then, within each 
filter pool, I have a filter for each source type (RPG, Display, PF and 
LF, etc.).  Let me know if you want more detail than that.

When I click right +  new on iseries objects, under filter
pool is "filter pool reference". If I choose this, the menu
proposes a list of profiles. What exactly is this filter pool
reference?

From what I understand, each filter pool is an object independent of the 
connection, so you can choose which filter pools appear on a 
per-connection basis.  I think the default is for each filter pool to 
appear in all new connections.  Does that help at all?

HTH,
Adam

P.S. - Sorry for replying to Rick's message (wrong threading), but our 
mail server seems to block the first message in a thread periodically. 
Grrr.

Attention:

The information contained in this message and or attachments is 
intended only for the person or entity to which it is addressed and may contain 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance upon, this 
information by persons or entities other than the intended recipient is 
prohibited. If you received this message in error, please contact the sender 
and 
delete the material from any system and destroy any copies. Thank you for your 
time and consideration.

Attention: 

Le contenu de ce message et(ou) les fichiers ci-joints s?adressent 
exclusivement à la personne ou -entité à laquelle ils sont destinés. Ils 
peuvent 
contenir de l?information confidentielle, protégée et(ou) classifiée. Il est 
strictement interdit à toute personne ou entité autre que le(la) destinataire 
prévu(e) de ce message d?examiner, de réviser, de retransmettre ou de diffuser 
cette information, de prendre une quelconque action en fonction ou sur la base 
de celle-ci, ou d?en faire tout autre usage. Si vous avez reçu ce message par 
erreur, veuillez communiquer avec l?expéditeur(trice), supprimer ce message et 
les fichiers ci-inclus de tout système, et en détruire toutes copies, qu?elles 
soient électroniques ou imprimées. Nous vous remercions de votre entière 
collaboration. 

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.