| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1106.1 | ANALYZE/RMS/FDL | caotv2.ca.oracle.com::BZINN | [email protected] | Tue Nov 26 1996 07:48 | 15 |
| Well, since the last message is RMS...
RMS-F-CHG, invalid key change in $UPDATE (CHG not set)
Explanation: A VMS RMS $UPDATE operation specified a record that
contained one or more changed key values for keys that do
not have the 'keys may change' attribute set in the XAB
key option flag,
User Action: Either reorganize the file and specify the 'keys may
change' attribute to be set in teh XAB key option flag, if
necessary, or modify the source program to detect and
respond to the condition.
So, I'd start with an ANALYZE or the file to get the FDL and check the
settings.
Brenda
|
| 1106.2 | how to change the settings? | svrav1.au.oracle.com::MCHAN | | Mon Dec 02 1996 17:22 | 116 |
| Hi,
Attached the FDL file generated by $ana/rms/fdl, as requested.
I suppose the key 0 needs to set to CHANGES YES. Appreciated
anyone tell me how to change the settings.
KEY 0
CHANGES no
Apparently customer called Digital CSC about RMS-F-CHG
error and was told its DBI problem.
Thanks,
Michael.
-----------------------------------------------------------------------------
IDENT "27-NOV-1996 18:05:46 OpenVMS ANALYZE/RMS_FILE Utility"
SYSTEM
SOURCE OpenVMS
FILE
ALLOCATION 14247
BEST_TRY_CONTIGUOUS no
BUCKET_SIZE 1
CLUSTER_SIZE 3
CONTIGUOUS no
EXTENSION 0
FILE_MONITORING no
GLOBAL_BUFFER_COUNT 0
NAME "$1$DIA3:[USER.EHMO]SSRF_020.DAT;1"
ORGANIZATION indexed
OWNER [ISD,TOMMY]
PROTECTION (system:RWED, owner:RWED, group:RWE, world:RWE)
RECORD
BLOCK_SPAN yes
CARRIAGE_CONTROL carriage_return
FORMAT fixed
SIZE 400
AREA 0
ALLOCATION 14247
BUCKET_SIZE 1
EXTENSION 0
KEY 0
CHANGES no
DATA_KEY_COMPRESSION yes
DATA_RECORD_COMPRESSION yes
DATA_AREA 0
DATA_FILL 100
DUPLICATES no
INDEX_AREA 0
INDEX_COMPRESSION yes
INDEX_FILL 100
LEVEL1_INDEX_AREA 0
NAME ""
NULL_KEY no
PROLOG 3
SEG0_LENGTH 32
SEG0_POSITION 0
TYPE string
KEY 1
CHANGES yes
DATA_KEY_COMPRESSION yes
DATA_AREA 0
DATA_FILL 100
DUPLICATES yes
INDEX_AREA 0
INDEX_COMPRESSION yes
INDEX_FILL 100
LEVEL1_INDEX_AREA 0
NAME ""
NULL_KEY no
SEG0_LENGTH 13
SEG0_POSITION 32
TYPE string
ANALYSIS_OF_AREA 0
RECLAIMED_SPACE 0
ANALYSIS_OF_KEY 0
DATA_FILL 60
DATA_KEY_COMPRESSION 74
DATA_RECORD_COMPRESSION 84
DATA_RECORD_COUNT 47124
DATA_SPACE_OCCUPIED 12969
DEPTH 3
INDEX_COMPRESSION 72
INDEX_FILL 56
INDEX_SPACE_OCCUPIED 454
LEVEL1_RECORD_COUNT 12969
MEAN_DATA_LENGTH 400
MEAN_INDEX_LENGTH 34
ANALYSIS_OF_KEY 1
DATA_FILL 75
DATA_KEY_COMPRESSION 63
DATA_RECORD_COUNT 8862
DATA_SPACE_OCCUPIED 804
DEPTH 2
DUPLICATES_PER_SIDR 5
INDEX_COMPRESSION 42
INDEX_FILL 57
INDEX_SPACE_OCCUPIED 15
LEVEL1_RECORD_COUNT 471
MEAN_DATA_LENGTH 34
MEAN_INDEX_LENGTH 15
------------------------------------------------------------------------------
|
| 1106.3 | | svrav1.au.oracle.com::MBRADLEY | I was dropped on my head as a baby. What's your excuse? | Tue Dec 03 1996 03:18 | 7 |
| Michael,
How about editing the FDL and then do CONVERT/FDL.
G'day,
Mark.
|
| 1106.4 | Also EDIT/FDL, but... | BROKE::WRIGHT | NYO&W-Trains Spoken Here-SUSIEQ | Tue Dec 03 1996 10:48 | 15 |
| Michael,
You should also be able to use:
$ EDIT/FDL <filename>.fdl
However, where the key he seems to be interested in changing is key 0 (the
primary key) you may not be able to make the key modifiable. I believe that by
definition (in RMS) the primary key is not modifiable. Which begs the question
of, "If this file is from a legacy system why does he want to change the value
of the primary key?" The system was probably not designed to do that and the
proper procedure is probably to delete the record and reenter the data using the
new key.
Tom
|