RE: SST In Logical FIle with Select

Yes, that was correct.

Thanks for all who responded!

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Nick_Radich@xxxxxxxxxxxxxx
Sent: Friday, February 24, 2012 9:41 AM
To: RPG programming on the IBM i / System i
Subject: RE: SST In Logical FIle with Select

Hi Shannon,

If you want an AND condition for your Selects, just remove the 'S' from the
CODEV comparison.

If you want an OR condition, keep the S there.



Thanx,

Nick



Nick Radich
Sr. Programmer/Analyst
EPC Molding, Inc.
Direct (320) 679-6683
Toll free (800) 388-2155 ext. 6683
Fax (320) 679-4516
nick_radich@xxxxxxxxxxxxxx



From: "Shannon ODonnell" <sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxx>
To: "'RPG programming on the IBM i / System i'"
<rpg400-l@xxxxxxxxxxxx>
Date: 02/24/2012 07:59 AM
Subject: RE: SST In Logical FIle with Select
Sent by: rpg400-l-bounces@xxxxxxxxxxxx



OK, for all interested parties...I have an answer, of sorts...

Sorry it took so long to check this but it takes freakin' forever to build
that access path each time! I guess I should have used an existing path
just for testing this but oh well...

Anyway...I got this to work by taking the first Select off of the LF:

A CODEV I SST(DOCODE 1 2)
A K RRAKCN
A K RRAKYR
A K RRAKTY
A K RRAKNO
A*** S STATUS COMP(NE 'X')
A S CODEV COMP(EQ 'EV')


I need that first select on there though so I guess I need to figure
out/read the manual would probably work :-) , how to AND those two Selects.

Man, this has been a real challenge for me! I barely write any RPG code any
more and DDS...forget it!

I'd forgotten how much I used to know!




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Luis Rodriguez
Sent: Friday, February 24, 2012 7:28 AM
To: RPG programming on the IBM i / System i
Subject: Re: SST In Logical FIle with Select

Shannon,

Disregard my previous post. Your LF is keyed and a single file (opposed to a
join file). the DYNSLT keyword would not apply in this case (IIRC).

Regards,

Luis Rodriguez
IBM Certified Systems Expert - eServer i5 iSeries