[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

1370.0. "TRM error in ALL-IN-1 V2.4" by UTRTSC::SMEETS (It's a long way to the south) Mon Sep 07 1992 12:14

    Hi everybody,
    
    A customer running TRM housekeeping in ALL-IN-1 V2.4 (patch K603) has
    the following problem.
    
    There a three mailareas OA$SHARA, OA$SHARB and OA$SHARE. Housekeeping
    Job PT looks fine. When looking in the TRM's logfile there is an error
    message in phase 3 for mailarea OA$SHARE.
    
    Error message: 
    
    Error correcting DAF Record
    Error of unknown cause, error = ?End of file on device
    
    ANALYZE/RMS of OA$DAT_E.DAT didn't show any error.
    
    Any suggestions ?
    
    Thanks,
    
    Martin Smeets
    Digital Holland
    
    
T.RTitleUserPersonal
Name
DateLines
1370.1More information pleaseIOSG::MAURICECeci n'est pas une noteWed Sep 09 1992 16:1218
    Hi,
    
    Can you let us know what version of TRM is shown in the log file (just
    so we can double check). We're looking to see if this is a known
    problem that's fixed (perhaps in K604).
    
    Can you also let us know if TRM was run with the option to have lost
    messages (messages with a usage count of 0) recovered to an account
    (usually MANAGER). This option may have been switched off by blanking
    the field containing the name of the account to receive recovered
    messages.
    
    From a preliminary investigation it looks as if this error is benign,
    i.e. an information message only.
    
    Cheers
    
    Stuart
1370.2Requested informationUTRTSC::SMEETSIt's a long way to the southThu Sep 10 1992 09:179
    Hi Stuart,
    
    The customer is running TRM V2.4.
    
    I didn't  find a field where you can switch on or off the option to have
    lost mail send to the manager. Doesn't TRM always send these lost
    messags to the mananager's account ?
    
    Martin
1370.3Master file informationIOSG::MAURICECeci n'est pas une noteThu Sep 10 1992 09:3735
>    The customer is running TRM V2.4.
 
    In the FCVR log file in OA$LOG there should be lines like:
    
    Version 2.4-5
    
    
    Beginning Phase 1 at 11:11 PM -- scanning users' personal File Cabinets
    =======================================================================
    
    ... 
    
    It's the Version number there that I want.
    
    
>    I didn't  find a field where you can switch on or off the option to have
>    lost mail send to the manager. Doesn't TRM always send these lost
>    messags to the mananager's account ?
    
    In V2.4 this is in the Master File. To get there you have to type 
    SM MMF SEL and then select 
    
    Master:      SM_UTILITY_MASTER
    Record:      TRM
    
    Then when you type E (edit) you will find the FCVR policies. 
    
    (In V3.0 this has all changed so that they're on the TRM schedule
    form).
    
    Cheers
    
    Stuart
    
    
1370.4More infoUTRTSC::SMEETSMartin Smeets DS SSO Utrecht HollandThu Sep 10 1992 13:3113
    Hi Stuart,
    
    I've looked in the OA$SM_FCVR_MAIL_AREA.LOGxxxxxxxxxxx in OA$LOG and
    the version is, believe it or not, 2.4 without any subversion number !
    
    The creation date of OA$LIB:OA$SM_FCVR.EXE is 30-May-1990.
    
    In record TRM of SM-UTILITY_MASTER the Manager is the account which
    receives the lost messages.
    
    Regards,
    
    Martin
1370.5Looks like an old version is being runIOSG::MAURICECeci n'est pas une noteThu Sep 10 1992 14:2316
    Hi Martin,
    
    K603 didn't come out until 1991 so it does look like the wrong version
    is being run. Do a $dir of OA$LIB:OA$SM_FCVR.EXE and see if there are
    two versions in there.
    
    If your customer had previously had V2.3 and applied patch K536 then
    there was a bug in that it supplied the image into OA$SITE_LIB_LLV
    rather than OA$LIB_SHARE. 
    
    If this is the case then the remedy is to delete the version in
    OA$SITE_LIB_LLV.
    
    Cheers
    
    Stuart
1370.6Only one versionUTRTSC::SMEETSMartin Smeets DS SSO Utrecht (NL)Fri Sep 11 1992 09:4710
    Hi Stuart,
    
    There's only one version of OA$SM_FCVR.EXE on the system !
    
    I also going to believe that the customer has an old version of
    OA$SM_FCVR.EXE. The housekeeping job PT has version number 2.4-K602.
    
    Cheers,
    
    Martin