Conference iosg::all-in-1_v30

2864.0. "Auditing an ALL-IN-1 system" by TINNIE::SETHI (Ahhhh (-: an upside down smile from OZ) Tue Jun 15 1993 09:53

    Hi All,
    
    I am wondering if anyone has done an "audit" on an ALL-IN-1 IOS system. 
    Basically the problem we have at a site is that they have had field
    test versions for ALL-IN-1 IOS, DEC MAILworks, CDA, OpenVMS , you name
    it they have had it on their system.  The have never had ALL-IN-1 IOS
    2.4 they installed 3.0 field test and have installed the SSB kit. 
    WordPerfect or is it WordDefective is also installed, it a never
    ALL-IN-1 IOS installation.
    
    Now a number of the standard ALL-IN-1 sub-systems such as TM have
    problems the system is highly customised.  We alo find doing a
    /nocustomise make no difference and some ALL-IN-1 function don't behave
    as they should like "gold l" in some sub-systems.  They have regular
    stack dumps never in the same place and different ALL-IN-1 functions.
    
    In this nightmare environment and that's not an understatement what
    should I audit ?  I have checked the checksum on the files in OA$BUILD
    and found that oa$build:siteoallv.olb had a different checksum.  It
    does not mean much unless I have a means of systematically going
    through ALL-IN-1 IOS files.  What would you advise ?
    
    Thanks in advance for your input,
    
    Sunil 'desperately seeking a helping hand" Sethi :-)
    

    G'day All,
    
    I am no longer desperately seeking help we have managed to track down
    the problem in a set of scripts.
    
    The customer has written an application called quick mail and answer. 
    The application used the MAIL functions to create the messages and it
    was found that one script had stuck dumps occuring on a regular bases.
    The difference between it and the other was the coding of the MAIL
    function.
    
    In one script they did a MAIL CREATE/OPEN and this script didn't have
    the problem and they did a MAIL CLOSE before copying the text file into
    [.MSG].  The script with the problem didn't do a MAIL CREATE/OPEN and
    copied the text file before it was closed.
    
    I am just adding this reply here to make you all aware that in certain
    circumstances you will get stack dumps at times if you do not "/OPEN"
    when creating a message, or do a copy of the TEXT file before doing a
    copy.
    
    Now they have stack dumps happening due to WordPerfect and this will be
    taken up with WPC Phhhh ;-).
    
    Regards,
    
    Sunil