A word of caution - be sure that any other programs/procedures that use the file that you are about to modify are not dependant on the current order of the file........You may need to create a new logical.
Warmest Regards,
Richard Reeve
________________________________
From: John Candidi <jacandidi@xxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Sunday, June 14, 2009 10:54:26 AM
Subject: RE: Indexing a Physical File
So, I guess the logical needs to be redefined that we have already from the sounds of it
John A. Candidi
American European Insurance Group
AS400 & POINT Application Manager
856-779-2274
jacandidi@xxxxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Friday, June 12, 2009 2:15 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Indexing a Physical File
John Candidi wrote:
How do you add an index to fields in a physical file
which was defined in COBOL without recreating the file?
Presumably "defined in COBOL" means the file declared\referenced
in\by the COBOL; i.e. an externally described PF was created using
SQL or DDS. In that case, then either of ADDPFCST CL command or the
ALTER TABLE ADD CONSTRAINT SQL statement, to add either a PRIMARY
KEY constraint or a UNIQUE constraint would suffice; note: these
require MAXMBRS(1) for the physical, if it was created using CRTPF.
If the desired key can not be unique, then the best option [to
avoid re-creating the PF with the desired key fields] is to create
and then use a keyed LF over the PF; created either by DDS with
CRTLF or SQL CREATE INDEX SQL statement. I prefer to use the LF
approach anyhow, to use only constraints for any keys in a physical.
Regards, Chuck
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
