RE: IDDU, S36 & AS/400 SQL & RPG -Reply

John:

I tried to change the MAXMBRS parm after doing a CREATE TABLE and received 
CPD3213:  Maximum-member value not valid for file FILENAME.  Here's the 
2nd-level help text:
Cause . . . . . :   File BGTABLE in library BGUETZKOW is either a Structured  
  Query Language (SQL) table, view or index, or a non-SQL file in SQL data    
  base BGUETZKOW.                                                             
    SQL tables, views, indexes, and non-SQL files that are in an SQL data base
  must have only one member; however, the value that you specified on the     
  maximum number of members (MAXMBRS) parameter is either a number greater    
  than one or *NOMAX.  For more information about SQL tables, views and       
  indexes, see the Programming: Structured Query Language Programmer's Guide, 
  SC41-9609.                                                                  
Recovery  . . . :   Change the value in the MAXMBRS parameter to 1 or *SAME,  
  and try the request again.                                                  

I also ran DSPFD against the table-file created with CREATE TABLE and on the 
first screen I found this info:
Data Base File Attributes                                       
  Externally described file . . . . . . . . . :            Yes  
  SQL file type . . . . . . . . . . . . . . . :            TABLE

So...apparently SQL Tables are physical files with a unique attributes which 
prevents multiple members.

Just thought you'd all find this interesting.  (We rarely use multiple-member 
files, so it has never come up as a problem for us in the past.)

Bruce Guetzkow
Team Coordinator, Applications Development
Highsmith Inc.
W5527 Highway 106 P.O. Box 800
Fort Atkinson, WI  53538-0800
Tel (920) 563-9571  Fax (920) 563-7395
EMAIL bguetzkow@highsmith.com


----------
From:   John Carr[SMTP:74711.77@compuserve.com]
Sent:   Tuesday, December 09, 1997 9:35 PM
To:     Midrange-L
Subject:        Re: IDDU, S36 & AS/400 SQL & RPG -Reply



RE:     Re: IDDU, S36 & AS/400 SQL & RPG -Reply

<< Jhon Carr wrote  >>
>Someone said
>>>To use the files in SQL I believe you have to create an SQL table,
>>> instead of a CRTPF or CRTLF.

>>I said;
>>Uh ... wrong.    Thats the nice thing on the AS/400 a *FILE is a
>> *FILE as opposed to the PC where a file is a .EXE a .XLS a .DOC a
>> .DLL a .ETC and it's up to the application to open it up and say
>> WHAT IS THIS JUNK or whatever runtime message each package
>> gives you(like.. Sorry; this is not a Powerpoint Presentation).
>
>> Anyway,  SQL sees a PF created from the CRTPF command exactly
>> like it see a table created using the CREATE TABLE and vice versa,
>> etc, and so on.
>  
                              --------------------

>While it is generally true that SQL don't know da difference 'tween a
>"CREATE TABLE" objects and a "CRTPF" object, there are some
>differences, at least at the system level.  One is that SQL tables can
>not have more than one member, even though SQL can access
>multiple member "CRTPF" files using OVDBF.  So somewhere down in
>the bowels of the system, there is (are?) a difference(s).
>Scott Cornell
>Mercy Information Systems

I'd be willing to bet that it is not 'down in the bowels of the system'.
I think it may be 'at the top of the system'

By that I mean,  Down in the bowels I think CREATE TABLE equates/runs
the CRTPF CPP.   I think it may be the fact that there is not a 
MBR parameter on the CREATE  TABLE SQL command. 

Try creating a table with SQL and then go ahead an do a CHGPF and 
change it to MAXMBRS(*NOMAX)  and add a couple of members.  I 
bet you can.  I don't know for sure, I haven't got my machine on
at this moment.  

The other major differences is that the CREATE TABLE creates a 
journal receiver automatically and a few other thing I think.


John Carr
EdgeTech


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---