[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

1113.0. "EM index username not long enough" by KAOFS::D_STREET () Thu Jul 23 1992 23:42

    Hello,
     I have a client who is complaining about the width of a name field in
    EM. They do "EM C ABC<CR>" and the index appears. The problem is that
    the name field is too small for their names. They get the following 18
    charactors, but not enough to identify the desired recipiant.
    
    1 node AT a1 AT name
    
     Where "name" is only 4 chars long, and not long enough to identify the
    person.
    
    	How would one go about getting around this limitation ?
    
    						Derek Street.
T.RTitleUserPersonal
Name		DateLines
1113.1Well i'm confusedAIMTEC::WICKS_ADEC Mail Works for ME sometimesFri Jul 24 1992 00:3122
    Derek,
    
    I'm assuming that either your typing has gone or you've been working 
    too hard because i've never heard of an address that goes backwards
    like your example.
    
    Surely it should be name@A1@node and not node@A1@name!
    
    The form i'm assuming you're talking about is EMSREC which has one
    field called DISPLAY of 79 characters it's built using the /SHOW on
    form EMHEAD which is:
    
    /SHOW='.USER:30 "( " .FULNAM:35 " )"'/USE_FORM=EMSREC 
    
    Is it the 30 character user name the customer wants expanded? Doesn't
    the 35 character FULNAM give them enough information?
    
    I'm confused as to what you're asking for
    
    Regards,
    
    Andrew.D.Wicks
1113.218 chars don't display node nameKAOFS::D_STREETFri Jul 24 1992 22:3723
    Hello,
     OK, the secret is out, I am dyslexic (no kidding, I was tested in
    College after considerable trouble in accounting class). I apologize
    for the error, but when I am under stress, and in a hurry, these things
    happen.
    
     However, the clients problem is still the same. When in the "To:"
    field they enter "GGO" and <CR>. In EMSADD they get:
    
    	1 GGONDOR AT A1 AT O
    INSTEAD OF
        1 GGONDOR AT A1 AT OTTJ
     It would appear that the 35 character FULNAM is not getting the full
    35 chars. Indeed this would be sufficent. I asked them to try it with
    the /NOCUSTOM and they got the same results. This is a V3.0 system,
    and the "problem" has only started since the upgrade. I looked at the
    named data, and it looks to me like it is displaying inly 18 chars.
    
    SELECT FOR OA$MAIL_ADD_ADDR WITH .USER = #EMDADDRESS
     DO SEL_CHOICE  OA$SEL_LINE:2 "  " .USER:18 "  "
     .ORGUNIT1:25 "  ( " .FULNAM:22 " )"
    
    							Derek Street
1113.3I prefer the v2.4 named dataAIMTEC::WICKS_ADEC Mail Works for ME sometimesFri Jul 24 1992 22:5013
    Derek, 
    
    No problem I assumed you were running v2.4. You're right the code was
    changed in v3.0 - i'm sure there was a good reason for the change but
    it escapes me.
    
    I'd customise the v2.4 named data back in personally. bear in mind that
    you'll need to make the change to form EMSADD as well.
    
    Regards,
    
    Andrew.D.wicks
1113.4Rat hole alert!!!HYTIDE::CREAMERFri Jul 24 1992 22:5510
    
    I was going to suggest the same thing but Andrew beat me to it...
    
    At the risk of opening a rat hole, I noticed that on EMSADD,
    I pressed CTRL-N to look at the named data and returned to EMSADD
    only to find that the items in the scrolled region had changed!!
    How odd!!
    
    Jack