| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2685.1 | Not sure, it's a new one | CHRLIE::HUSTON | | Mon May 10 1993 13:31 | 17 |
|
It means that either:
1) You have customized a customized language on the system and you
did not customize SYSTEM_FOLDERS.DAT, or..
2) Something is internally corrup.
What will it do? good question. THe code will default to upper casing
by 8 bit ascii rules. If this is not good, then you will get corrupt
strings like folder names, drawer names etc.
Can you run the oafc$sysfold_seed utility and select the option to
list all languages? Put the output in here.
--Bob
|
| 2685.2 | output from OAFC$SYSFOLD_SEED | GIDDAY::LEH | | Tue May 11 1993 08:37 | 82 |
| Bob
Thanks for the info...
There didn't seem an option in OAFC$SYSFOLD_SEED to list all languages;
instead it expected a 4-letter lang code, e.g. ENGB.
I used OPEN to extract all records in their SYSTEM_FOLDERS.DAT, which seemed
to contain identical entries as did on our internal system :
XX = "CHCNHANZI ...������
XX = "CHTWHANYU ...�ǵ�
XX = "DA DANISH ...INDBAKKE
XX = "DEDEGERMAN ...EINGANG
XX = "EL GREEK ...INBOX
XX = "ENGBBRITISH ...INBOX
XX = "ENUSENGLISH ...INBOX
XX = "ESESSPANISH ...NO LEIDOS
XX = "FI FINNISH ...SAAPUNEET
XX = "FRCACANADIAN ...ARRIV�
XX = "FRFRFRENCH ...ARRIV�
XX = "IS ICELANDIC ...ASENT
XX = "ITITITALIAN ...RICEVUTO
XX = "IW HEBREW ...��
XX = "JAJPJAPANESE ...�����
XX = "KOKRHANGUL ...������
XX = "NLNLDUTCH ...ONGELEZEN
XX = "NO NORWEGIAN ...INNKURV
XX = "PTPTPORTUGUESE ...RECEBIDO
XX = "SVSVSWEDISH ...INKORG
Details on ENGB and ENUS were as follows:
...............
Enter the 4 letter country code: engb
FOLDER NAME FOLDER TAG FOLDER ORDER
----------- ---------- ------------
INBOX 1 FIFO
READ 2 LIFO
CREATED 3 LIFO
OUTBOX 4 LIFO
UNREAD 5 FIFO
UNSENT 6 LIFO
SENT 7 LIFO
WASTEBASKET 8 LIFO
DISTRIBUTION LISTS 9 LIFO
PENDING ARCHIVE 10 LIFO
ARCHIVED DOCUMENTS 11 LIFO
DICTIONARIES 12 LIFO
RECOVERED DOCUMENTS 13 LIFO
RECOVERED SHARED DOCUMENTS 14 LIFO
POSTMASTER MAIL NBS FROM MR 15 FIFO
Enter the 4 letter country code: enus
FOLDER NAME FOLDER TAG FOLDER ORDER
----------- ---------- ------------
INBOX 1 FIFO
READ 2 LIFO
CREATED 3 LIFO
OUTBOX 4 LIFO
UNREAD 5 FIFO
UNSENT 6 LIFO
SENT 7 LIFO
WASTEBASKET 8 LIFO
DISTRIBUTION LISTS 9 LIFO
PENDING ARCHIVE 10 LIFO
ARCHIVED DOCUMENTS 11 LIFO
DICTIONARIES 12 LIFO
RECOVERED DOCUMENTS 13 LIFO
RECOVERED SHARED DOCUMENTS 14 LIFO
POSTMASTER MAIL NBS FROM MR 15 FIFO
The system involved started having intermittent problems on un-RESERVE certain
docs in ex-SFCP drawers and unavailable FC server. They'll document in details
those incidents when able to catch them.
Hong
|
| 2685.3 | Still not sure what to say | CHRLIE::HUSTON | | Tue May 11 1993 14:31 | 35 |
|
Everythign from SYSTEM_FOLDERS.DAT looks fine.
I did go back and read the .0 though and noticed something:
>10-MAY-1993 11:15:36.05 Server: VAX8::"73=" Error: %OAFC-E-LANGUAGENS,
>Language not supported Message: UtltoUpper; Unknown country code: ,
>defaulting to 8-bit ^^^^
|
What the heck is that? It should have the language code for the
language that it did not understand. By having it blank I can think of
a couple of potential problems:
1) Partition.dat is corrupt and a drawer (or more than one) has no
language set for it.
2) There is a session_char parameter when connecting to the FCS, one
of the options for this is to tell the FCS that it should ignore
the lnaguage stuff, the client will do all upper casing. I know that
IOS never does it this way so something else may be amiss.
Other than that I am at a loss.
You mentioned something about failed reserve/replace. THere are some
problems about "dangling" reservations (Kevin want to help me out here)
in which a document only gets half reserved or replaced. This may be
a symptom of that, though I have never seen it show itself in this
way before.
More information would be nice.
--Bob
|
| 2685.4 | Check PARTITON and PROFIL language fields... | IOSG::PYE | Graham - ALL-IN-1 Sorcerer's Apprentice | Tue May 11 1993 18:16 | 9 |
| I would suggest a loop through the PARTITION dataset looking for
drawers with blank or invalid language fields might be a good idea. A
recent note here suggested that SFCP migrations could get problems if
the language field wasn't correct. Maybe this is what happens!
It's probably also worth checking the language field in the PROFIL
records too, to ensure they are all BRITISH or whatever.
Graham
|
| 2685.5 | PROFIL language fields already checked | GIDDAY::LEH | | Tue May 11 1993 22:27 | 12 |
| Graham in .4
Will check out language field in PARTITION
During upgrade, 2 SFCP accounts and one ordinary account had blank
language field, which were reported by partition seeding and corrected
promptly. The customer was quite positive about the language field in
all PROFIL records with correct value: BRITISH
Thanks
Hong
|
| 2685.6 | seeming to be stable | GIDDAY::LEH | | Wed May 12 1993 08:54 | 19 |
| Hope latest discoveries were correct..
o One heavily-used ex-SFCP cabinet did have blank language code field,
which would have explained all the "...Unknown country code..." errors.
It was on node VAX8 and since fixed, its server log hasn't shown any of
above errors for the past working day.
Bob in .3
o One node had default CHANNELCNT and its server log reported a number
of problems, incl. those on reservations. Again, haven't seen these
errors again since the upgrade of the above parameter.
I'll post progresses when avail.
Many thanks
Hong
|