Conference iosg::all-in-1_v30

    Sunil,
    
    The Distribution List has a STATUS of SENT that's why it's in the
    Shared Area, and even worse it's in the WASTEBASKET folder.
    
    Neither of these is good it should be in a [.DOCn] subdirectory in
    the DISTRIBUTION LISTS folder with a blank STATUS.
    
    I can't even figure out how to get a distribution list into the same
    state but given it somehow got there I'm not too surprised at how the
    mail code is behaving (:==:)
    
    Regards,
    
    Andrew.D.Wicks 

    Hi Andrew,
    
    The reason why it's in the WASTEBASKET is because the customer deleted
    the EM.
    
    The Distribution List are stored in [.MSG] as far as I know.  This
    behavour is so odd I am really stuck for answers.  I will just have to
    keep on working at this problem and post anything else I find here.
    
    Thanks
    
    Sunil

    Hi,
    
    When I did a <debug on, my terminal hung at a certain point in the
    script.  I ran the script interactively <do wpsend without a problem,
    I suspect that the base TXL's are corrupted.
    
    The customer was unable to compile the base tlx's because the
    WPMDMP.SCR was present in twice in oa$do, in the site and base area. 
    This should have been removed as per the pre-installation checks.  The
    customer has said that they did not remove any of the elements, and had
    a number of error message they have thrown away the logfiles :0( a
    typical customer).
    
    What's the best way to tackle this problem ?  I know we will have to
    make sure that we remove the elements as required by the
    pre-installtion check is there an easy way of achiving this under 3.0 ?
    
    Thanks 
    
    Sunil

    
    	<debug on can sometimes "hang" your terminal by sending funny
    	characters to it caused by incorrect decoding of the lines of
    	the TXL not by TXL corruption. Try resetting your terminal
    	when this happens and see if you can continue.
    
    Regards,
    Paul

    Hi Andrew,                                
    
    Sorry it's taken me sometime to get back to you.  The customer had a
    number of error messages reported during the installation and did
    not keep the logfile (hardcopy) because it was not important !
    
    I have narrowed down the possible reason for the problem I asked her to
    do an audit of her system to ensure that the file ownership and
    protections are correct.  They have a number of systems around
    Australia and are in the process of doing this now, the customer has
    told me a number of files are owned by SYSTEM.
    
    In my absences Hong Lee obtained further information that is of
    interest 
    
    Sanity checks on files in OA$DO, OA$SCP and block size
    
    o *.SCP Files in OA$LIB_BRITISH
    
    32 vs 36 (vanilla vs. customer )
    
    o *.SCP Files in OA$LIB_SHARE
    
    693 vs 756      (vanilla vs. customer )
    
    o *.SCP Files in OA$DO_SHARE
    
    322 vs 339      (vanilla vs. customer )
    
    
    o Size of A1TXL: 1132 vs 1377 blocks    (vanilla vs. customer )
    
    o WPSEND.SCP;5         27-NOV-1992 14:17:04.72
      WPSEND.SCP;4         12-MAR-1992 09:54:41.69
    
    but they're not different.
    
    It's an educated guess that ownership and protection problems maybe the
    cause, because everything works fine from the ALL-IN-1 managers account.  
    As mentioned if the user has the following distribution lists @DEC1 and 
    @ABC and the user enters @D gold <L> they get the error message 
    
      %OA-W-RECORD_IO_ERROR, Error occurred while attempting to GET the record
      -RMS-E-RNF, record not found
    
    If the distribution name is entered in full at the TO: and CC: ie @DEC
    everything works fine, this is slightly different from what I said in
    the base note.
    
    Any other suggestion would be helpful otherwise I will keep on plugging
    away and enter the solution here once I have worked it out.  Thanks for
    your help and interest.
    
    Sunil

    Hi All,                         
    
    I have narrowed down the problem a bit more now and I find myself at a
    loss to explain why this is occuring.  As per the previous note I
    stated that this problem does not occurs for the ALL-IN-1 managers
    account only for user both priviledged and unpriviledged.  If I enter 
    @DEC <ret> that's when the problem occurs and not as stated in -.1, sorry 
    about that minor oversight.  The file ownership and protection problems 
    have been solved.
    
    Now the remaining problem, it would appear from the trace that the
    incorrect WPSEND is being executed.  I asked the customer to check the
    OA$DO:WPSEND.SCP it's the correct version and I asked the customer to
    recompile the A1TXL.TXl it made no difference.  To check that the
    correct version is in A1TXL.TXL I did the following
    
    1. <do$txl_directory wpsend,do,a1txl  - the wpsend.scp was present
    2. <do$txl_list wpsend,do,a1txl - compared the actual ie 
       <list oa$do:wpsend.scp and the one in A1TXL.TXL they are exactly the
       same minus the comments.
    
    A logfile contains details of my login session on the customer's
    system.  I would be grateful for your help and advise the file
    specification is RIPPER::USER$TSC:[SETHI]DHHCS_122192.LOG;1 the
    protection is set to W:R.
    
    Thanks for your help in advance,
    
    Sunil

    Hi All and Happy New Year,
    
    I have finally managed to track down the cause of this problem.  The
    customer has a 3rd party package called Queue File it's a bit like
    Xtree.
    
    If the following command was not executed $set command
    <disk>:queue_file prior to the user invoking ALL-IN-1 the Send option
    would not work, if it was all would work as expected.
    
    The customer will liase with the 3rd party and hopefully get to the
    bottom of all of this.  I will keep you posted on the progress
    providing the customer get's back to me.
    
    Well this one had me pulling my hair out, I wonder if Digital will
    cover the cost of a hair transplant.
    
    From a bolding man downunder :-),
    
    Sunil

Hi,

I've got the same problem, with my Norwegian ALL-IN-1 3.0.
If we try /nocustomize it dosn't help, and the problem still
appears from the WP menu(bu no problemo from EM menu) when 
the user <TAB> down to the SUBJECT field.

There's a trace of this appearing in BERGEN::*.trace.

Any hints....

...Arne

    Hi Arne,
    
    Did you see my previous note as I stated I discovered that a $ set
    command was the problem if you did not have it.  A 3rd party software
    package was installed that caused the problem.
    
    I would suggest that you look at the following 
    
    1. OAINI.SCP and OAINI.COM if they are used to see if they have
       something that may cause the problem.
    
    2. Look at LOGIN.COM and SYLOGIN.COM.
    
    3. Are there some accounts that work and others that do not ? If so
       check for differences.
    
    I started to examine everything from the time the users logged in to
    the time they went into WP menu and entered the send command.  It may
    not be a 3rd party package or it maybe, you just have to look, I
    couldn't access your node.
    
    Good luck,
    
    Sunil

    Hi Arne,
    
>But I discovered somthing very interesting, In the EMFWHD (from the WP menu)
>form doing a select on a private (customer do not use system dist.list) 
>dist.list AND a <RET> the error occurs, BUT doing a <TAB> instead the error 
>do not occur and everything is OK.
    
    Same thing happened to me.
    
    I think that you may have misunderstood me regarding OAINI.SCP,
    OAINI.COM, LOGIN.COM and SYLOGIN.COM.  What I found was that the
    customer had a 3rd party package and if they did not have $ set command
    <whatever>, they had they problem.  So puting in exit in the files will
    not help.
    
    Ask the customer if they have a 3rd party package like the one I
    mentioned.  Alot more information is required about the customers
    installation, it could be a logical that's causing a problem.
    
    Sorry that's the best I can offer for the time being.
    
    Sunil