.PL63
.PN1
L....T..T.........................................R.L................A
.FO2
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA>@@
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[
UNOTE 55                                                  Page # of 1
.HE3
‰    ‰                                                 Ref:  UNOTE 55~
From‰:‰ Customer Services                                   30 Oct 89~
L....T..T.......T.......T.......T.......T.......T.......T.......T....R
Re‰  :‰ Bug in ucalc (issi mode)~
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA>@@
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[

L.......T.......T.......T.......T.......T.......T.......T.......T....R

Symptom~@@
EEEEEEE 

When using ucalc in issi mode, some commands and softkeys fail
inexplicably if either:

H...L...T.......T.......T.......T.......T.......T.......T.......T.R
 i) you increase the number of columns in an English spreadsheet,~
‰   or~
ii) are not careful when translating.
L.......T.......T.......T.......T.......T.......T.......T.......T....R


Reason~@@
EEEEEE 

The reason is due to an internal conflict between words defined in the
#KEYWORDS section of UAP/uc/issidefs and high column addresses.@@
AAAAAAAAA            IIIIIIIIIIIIIII                           

For example, with the standard 6.10 English configuration, the
#KEYWORDS section contains:@@
AAAAAAAAA                  

FRACSPEC=dec@@
QQQQQQQQQQQQ

and, if you re-configure the spreadsheet to have 3000 columns (issi
address DKJ), then because dec could now be a column address (since it@@
        AAA                AAA                                        
is lexically "less than" dkj) you will hit the problem when you try to@@
                         AAA                                          
format using the softkeys.

Similarly, a 1000 column sheet (issi address ALL) hits the problem due@@
                                             AAA                      
to conflict with the KEYWORD all.@@
                             AAA 


Current situation~@@
EEEEEEEEEEEEEEEEE 

In current English language 6.01, 6.10 and 7.00 product, ucalc is
shipped configured for a maximum of 256 columns - an issi address of
iv.@@
AA 

Although there are some #KEYWORDS that are lexically less than this@@
                        AAAAAAAAA                                  
(eg:  DB=db, FORMAT=f, HDR=h), normal use of ucalc does not seem to@@
      AAAAA  AAAAAAAA  AAAAA                                       
suffer.


Recommendations and work-arounds~@@
EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE 

H...L...T.......T.......T.......T.......T.......T.......T.......T....R
1.  Do not increase the column size if you can avoid it!

2.  If you do, and have problems with softkeys/commands, see if any
    terse keywords are in use.  Where they are, and are softkey
    generated, you can reconfigure round the problem.~
‰   For instance on the dec conflict above, the KEYWORD can be@@
                        AAA                                   
    redefined as decimal and the appropriate softkey strings changed@@
                 AAAAAAA                                            
    from 'dec' to 'decimal'.@@
         AAAAA    AAAAAAAAA 

‰   (note that this may change the format of a LIST file, causing
    later compatibility problems!)~

3.  When translating KEYWORDS, avoid trouble by always using acronyms
    that are lexically greater than gjh (issi address for column@@
                                    AAA                         
    5000).