RE: Specifying Unique keys

Thanks to all.

Made the changes suggested and got the results expected.


Roy Luce
Systems Plus - Midwest

Direct: 847-540-9635
800-913-PLUS (7587)
Cell: 847-910-0884
Email: rluce@xxxxxxxxxxxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Alan Shore
Sent: Wednesday, February 25, 2009 1:46 PM
To: RPG programming on the IBM i / System i
Subject: Re: Specifying Unique keys

Hi Roy
What you need to do is insert an A-spec line BEFORE 9.00 with the word
UNIQUE in the Functions (Prompting will help)
Then make USHPNO and UUPGNAME keys to this file (or it can be a logical to
this physical)



Alan Shore
Programmer/Analyst, Distribution
E:AShore@xxxxxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

rpg400-l-bounces@xxxxxxxxxxxx wrote on 02/25/2009 02:19:50 PM:

To the list.



Here's an example of a file DSS created using STRPDM:



0009.00 A R WHE5FR TEXT('UPGRADES')


0011.00 A USHPNO 6 0 TEXT('SHIPMENT')


0012.00 A ULINENUM 4 0 TEXT('SALES ORDER

LINE

NUMBER')

0013.00 A UUPGTYPE 1 TEXT('UPGRADE TYPE+


0014.00 A 1 = BEFORE
PACKING+

0015.00 A 2 = WHILE
PACKING')

0016.00 A UUPGNAME 20 TEXT('UPGRADE NAME')


0017.00 A UUPGSTAT 1 TEXT('UPGRADE STATUS+


0018.00 A A = ACTIVE+


0019.00 A C = COMPLETE')


0020.00 A UUPGDTE 8 0 TEXT

('FOLLOWUP/COMPLETED

DATE')



I want to establish the fields at lines 11 and 16 as unique keys - for

any

recorded inserted in the file these 2 fields must be unique to the file.



Specifically what coding is required to make this happen?





Roy Luce

Systems Plus - Midwest



Direct: 847-540-9635

800-913-PLUS (7587)

Cell: 847-910-0884

Email: rluce@xxxxxxxxxxxxxxxxxxx



--
This is the RPG programming on the IBM i / System i (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.