Using PRO-IV v4 on AIX

I have defined a new Cisam file in @F (SPSTR01M) which has a an alternate key called SPSTR01L.

On exiting the @F screen I get the following warning when it creates the Alt File Defs :

Alternate name already being used by another file 'SPSTR01L'.


Now we did have a Cisam file defined called SPSTR01L but I have deleted the file defenition so I can't see where the name clash is that the error implies.

As an additional check I built myself a little util to list all the Alt Keys define in FILEDEF with an MS var type. I did'nt find any other files with Alt keys of the same name.

So if no references to SPSTR01L are left in FILEHDR or FILEDEF where else could @F be finding a name clash ? Does PRO-IV store the Alt Key name in any other bootstraps which need to be purged ?

This is my abbreviated file def :



Change @F
12/02/10 FILE DEFINITION 200/NAU/PTS_28

CO- AUTO EXTERNAL FILE KEY RECORD
DIV SEQUENCED RECORD FORMAT TYPE LENGTH LENGTH
FILE NAME: SPSTR01M Y Cisam 6 174
ALTERNATE: ../altdata/so/spstr01m RECORD CODE: MSG:
DESC: Stock roll details
Change
-------------------------- R E C O R D L A Y O U T -------------------------
DATA MAX FILL SPECIAL ARRY
SEQ TYPE VARIABLE NAME LEN CODE DISPLAY-CODE CHECK SIZE
--- ---- -------------------------------- ---- ---- ------------ -------- ----
001 K SPSTR01L.ROLL.NO 6 LFZ UPPERINP
002 A SPPDT01M.CODE 20 UPPERINP
003 A SPSTR01L.BRANCH 3 UPPERINP
004 N SPSTR01L.ORIG.LENGTH 7 'ZZ9.999'
005 N SPSTR01L.ORIG.WIDTH 7 'ZZZ9.99'
.
.
021 A SPSTR01L.ADD.ON.NARRATIVE 40
022 MS SPSTR01L
023 M SPPDT01M.CODE 1 20
024 M SPSTR01L.BRANCH 1 3
025 M SPSTR01L.ROLL.NO 1 6
026 ME
027 MS SPSTR02L
028 M SPSTR01L.BRANCH 1 3
029 M SPPDT01M.CODE 1 20
030 M SPSTR01L.ROLL.NO 1 6
031 ME
032 MS SPSTR03L
033 M SPSTR01L.DEAD 1 1
034 M SPSTR01L.BRANCH 1 3
035 M SPPDT01M.CODE 1 20
036 M SPSTR01L.ROLL.NO 1 6
037 ME

did you delete the old physical file and index ?

did you delete the old physical file and index ?

Effectivly Yes. The old IDX and DAT files were renamed.

To be honest I don't remember exactly how this works, but it is a little bit of a kludge.
I assume from what you say that you're using native dev.

IIRC, ProIV creates 'pseudo' FILEHDR records for all alternate keys with a hidden 'pointer' back to the 'main' file definition.
It may not be quite 100% about cleaning up those 'pesudo' header records in certain situations.

My first suggestion would be to triple-check and delete any FILEHDR records that have (re)appeared for your alt indexes.

Our esteemed webmaster can probably give you chapter and verse.