Re: members

Hello AL,

I'd just like to add my voice to this.  I also think it is foolish to implement 
DB features only via SQL.  A 
native interface should always be provided.  Doing so may help sites who do not 
wish to embrace SQL to avail 
themselves of newer technology.

Also SQL in V4R3 has an ALIAS keyword allowing you to nominate the specific 
member of a DB file.  No more 
OVRDBF calls in SQL, ODBC, JDBC, etc.  For example: CREATE ALIAS MyLib/MyAlias 
FOR Lib/File (Member)

Another thing, does anyone else hate the direction IBM is taking with Ops 
Navigator?  I don't mind its 
existence but I do dislike being _forced_ to configure an AS/400 from Windows.  
Especially if I have embarked 
on a corporate window-less strategy (there are other choices).  If I choose an 
AS/400 I am forced to obtain, 
install, and maintain at least one windows box just so I can configure DHCP, 
etc.  I don't expect an Ops Nav 
for OS/2 or Mac (although a Java version might be the proper solution) but I do 
expect a 5250 interface to 
configure *all* the AS/400 components.

Regards,
Simon Coulter.

//----------------------------------------------------------
// FlyByNight Software         AS/400 Technical Specialists
// Phone: +61 3 9419 0175      Mobile: +61 0411 091 400
// Fax:   +61 3 9419 0175      E-mail: shc@flybynight.com.au
// 
// Windoze should not be open at Warp speed.
//--- forwarded letter -------------------------------------------------------
> X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
> Date: Sun, 27 Sep 98 16:15:13 -0400
> From: "Al Barsa, Jr." <barsa2@ibm.net>
> To: MIDRANGE-L@midrange.com
> Reply-To: MIDRANGE-L@midrange.com
> Subject: Re: members

> 
> At 12:46 PM 9/27/98 -0400, you wrote:
> >Someone said the other day that members are dead.  IBM has seen that no
> one else is going down the members road, so they are pulling back and
> offering no further support beyond what we see right now.
> >
> >Does this fit with what others have heard?   
> 
> The multi-membered concept was a System/38 invention, and has proven
> awkward to use, easy to mess up in production.  IBM could have just backed
> off of this as being strategic, but there were two problems:
> 
> 1.    SQL (as first developed off of the System/38 - AS/400) did not address
> multi-members as a strategy.
> 2.    System/38 - AS/400 heavily embraced multi-members for source.  
> 
> SQL will likely never embrace multi-members.  IBM is not doing anything in
> the database that not addressed by SQL, and (IMHO very foolishly) starting
> to implement some new features only through SQL!
> 
> I have addressed on many occasions with IBM on the concept of
> re-architecting source files into a different animal, but there are very
> many complications.  Keep in mind that sources files can be updated from
> many other places than SEU/SDA/RLU and TM/38; any HLL program can process
> source files!
> 
> Al
> 
> Al Barsa, Jr. - Account for Midrange-L
> Barsa Consulting, LLC.        
> 400 > 390
> 
> Phone:        914-251-9400
> Fax:  914-251-9406

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---