Re: "Reference #"

[rob@xxxxxxxxx]

Speaking of identity columns, or ROWID's, does anyone know the technical 
of how they do this?

Not that I give a rip about supporting obsolete versions of OS/400, but 
how often has it been that I couldn't save a file to a release that SAVOBJ 
currently supports?  Happens all the time with programs, but files?  Don't 
know if this would happen, but I suspect it would, or dang, I'll just test 
it...
create table rob/orders 
(orderno smallint not null 
 generated always as identity
 (start with 500 
  increment by 1 
  cycle), 
 SHIPPED_TO VARCHAR(36) , 
 ORDER_DATE DATE) 

SAVOBJ OBJ(ORDERS) 
       LIB(ROB) 
       DEV(*SAVF) 
       OBJTYPE(*FILE)
       SAVF(ROB/ROB) 
       TGTRLS(*PRV) 
Message ID . . . . . . :   CPI3215       Severity . . . . . . . :   10  
Message type . . . . . :   Information  
Date sent  . . . . . . :   03/27/03      Time sent  . . . . . . : 09:37:44 
 
  
Message . . . . :   File not valid for save.  
Cause . . . . . :   File ORDERS in library ROB could not be saved for the  
 
  specified target release for reason code 4.  The reason codes are:  
    1 - The file has fields in its record format whose attributes are not  
 
  supported on the target release or the file is an SQL view that 
specifies 
  new function that is not supported on the target release.  
    2 - An attribute of the physical file's access path(s) is not 
supported on
  the target release.  
    3 - An attribute of the physical file's data is not supported on the   

  target release.  
    4 - IDENTITY or ROWID columns are not supported on the target releae.  
 

Hmm, if I was real ambitions I might report to IBM the misspelling of the 
word release, (last word above), but not today...


Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin