RE: "Reference #"

Awww.  Not running V5R2 yet?

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




"Chuck Lewis" <clewis@xxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
03/27/2003 03:09 PM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     "'RPG programming on the AS400 / iSeries'" 
<rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        RE: "Reference #"


Thanks everyone !

I took a look at UUID's and searched the archives, etc. and learned a lot
about them, etc. and then it hit me that I was over complicating this.

I ended up taking job #/date/time (via the TIME keyword) and have an 18
position # that should do the trick !

Thanks again everyone,

Chuck


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Thursday, March 27, 2003 9:41 AM
To: RPG programming on the AS400 / iSeries
Subject: Re: "Reference #"

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 
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.