Re: Ref:changing keys of a physical file

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Santosh

Glad you got it solved. The easiest path here is to modify source, then use 
CHGPF against the physical, naming the source member - the key will get 
changed automatically. You don't need to rename the file, or anything. I 
assume it should not be in use, however.

You're right that, had you compiled over the SQL table, you'd have been 
fine. SQ: tables, after all, are only physical files with one special 
attribute that mostly forces them to being single-member files.

Using one of the tools listed in the link I mentioned earlier makes the job 
easier - physical files are one of the easiest things to reverse-engineer.

Regards
Vern

At 09:36 AM 12/23/2003 +0530, you wrote:
> With due regards to Booth and Steve.
> I will tell you what I did.

-snip-

> 6. There was a unique set of keys on the file with  a set of 4 columns.I
> could use DSPPFD to see the key names. We now wanted to have unique on  a
> set of 5 keys.
> 7. I renamed the old file and kept in the system.
> 8. I created a DB2 SQL table by same name and columns. But the program wont
> run with return code 39 .( the open stat. was unsuccessful because  a
> conflict was detected between a  fixed file attributes and the attributes
> specified for that file in the program ). I think I could have run my
> program if I had compiled the program source once.
> 9. Then I went to infocenter and read material and tried to create a DDS
> file for making PF.
> 10. I compiled the PF file, inserted records in it from old file using SQL.
> i then compiled the program which accessed that file and yes, it now works
> fine.

-snip-

> Regards
> Santosh.