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

Conference noted::pwv50ift

Title:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Notice:Kit: Note 4229; Please use NOTED::PWDOSWIN5 for V4.x server
Moderator:CPEEDY::KENNEDY
Created:Fri Dec 18 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4319
Total number of notes:18478

4290.0. "admin/analyze error" by VAXRIO::LORENA () Wed May 14 1997 10:26

    
    Hello all,
    
    My customer has a problem with "admin/analyze" command.
    Your server is :
    VAX 4000-105A / Open VMS 6.2
    PATHWORKS V5.0E Eco01 fr OpenVMS
    
    The error message is:
    
    [SYSMAINT]>admin/analyze    
    %DCL-W-IVQUAL, unrecognized qualifier - check validity, spelling, and
    placement  \ANALYZE\
    
    But the "admin" works fine with the menu and the "admin/pcsa" too:
    
    [SYSMAINT]>admin/pcsa         
    PCSA_MANAGER> show version    
       
    LAD$KERNEL version   : LAD$KERNEL V1.2    
    LADDRIVER version    : LADDRIVER V1.2     
    
    PCSA_MANAGER version : PATHWORKS for OpenVMS V5.0
    
    I tried to execute under admin menu:
    admin / utilities / event logger / view event log / after=12-may-1997
    
    and I received the following error:
    
    %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
    address=00000038, PC
    =00299D6B, PSL=03C00004
    %TRACE-F-TRACEBACK, symbolic stack dump follows
    module name     routine name                     line       rel PC   
    abs PC
    
                                                               00299D6B 
    00299D6B
                                                               0029995A 
    0029995A
    WE              WE_Spawn                         9963      00000036 
    0025129A
    EVTLOG          EVT_ViewEventLog_SCR            20268      000004DA 
    002478F2
    WE              hot_key_action                  11394      000003FF 
    0025387F
    WE              smg_process_key                 13491      000002C5 
    0025719D
    WE              traverse_dialog_box             14375      00000139 
    0025834D
    WE              WE_dialog_box                    8283      00000B99 
    0024EAD5
    EVTLOG          EVT_main_SCR                    19381      00000096 
    00246386
    NAVIGATE        process_bar_menu_utilities      14785      000000BF 
    00249277
    NAVIGATE        ProcessTopMenu                  14945      00000103 
    002495DB
    WE              ProcessMenu                     11898      000004E2 
    00254692
    WE              traverse_dialog_box             14389      00000163 
    00258377
    WE              WE_dialog_box                    8283      00000B99 
    0024EAD5
    NAVIGATE        process_main_menu               14892      00000049 
    002494B1
    LMMENU          fsp1$main                       34036      00000573 
    00223217
                                                               00308085 
    00308085
    MTS$MAIN        main                             2956      0000001B 
    00222C1F
    [SYSMAINT]>
    
    Thanks in advance for your help and attention,
    Lorena/CSC/Rio 
    
T.RTitleUserPersonal
Name
DateLines
4290.1UTRTSC::SWEEPI want a lolly...Wed May 14 1997 11:264
    Check if customer has local definitions for analyze
    or logicals.
    
    Adrie
4290.2We checked...VAXRIO::LORENAThu May 15 1997 08:519
    
    Adrie,
    
    We checked all of the definitions local and global, but we didnt't find
    any problem. This situation is very curious because the commnads:
    "admin/pcsa"and "admin" works fine.
    We are waiting for your suggestions about this problem,
    Best regards,
    Lorena
4290.3WAGVMSNET::P_NUNEZThu May 15 1997 09:555
    
    Perhaps DCLTABLES is bad (though I'm not sure (1) how to check nor (2)
    how to correct it)...
    
    Paul
4290.4How to fix DCLTABLESCPEEDY::VATNEPeter Vatne, Advanced Server for Digital Unix EngineeringThu May 15 1997 13:079
>    Perhaps DCLTABLES is bad (though I'm not sure (1) how to check nor (2)
>    how to correct it)...

I think Paul's deduction is correct (DCLTABLES is bad).  This can happen
if an old version of PATHWORKS (Macintosh) is installed after PATHWORKS
(LAN Manager).  There should still be a release note on this.

The cure is to execute @SYS$UPDATE:PWRK$INSTALL_COMMANDS.  This will
re-install the ADMIN command from SYS$UPDATE:PWRK$COMMANDS.CLD.
4290.5VAXRIO::LORENAFri May 16 1997 10:4222
  
    Peter and Paul,
    
>>I think Paul's deduction is correct (DCLTABLES is bad).  This can happen
>>if an old version of PATHWORKS (Macintosh) is installed after PATHWORKS
>>(LAN Manager).  There should still be a release note on this.

    The Customer had installed old version of PW V4.2 before PW5
    (LANManager).He performed UPGRADE V4->V5.
    He never installed PW (Macintosh).
    
>>The cure is to execute @SYS$UPDATE:PWRK$INSTALL_COMMANDS.  This will
>>re-install the ADMIN command from SYS$UPDATE:PWRK$COMMANDS.CLD.
    
    We executed the command above and the DCLTABLES was updated, but the
    problem continues with "admin/analyze". 
    
    Could you have some tips to check the customer' system ?
    Thanks for your attention and help,
    Regards,
    Lorena/CSC/RIO
    
4290.6Make sure to logoutCPEEDY::VATNEPeter Vatne, Advanced Server for Digital Unix EngineeringFri May 16 1997 16:0023
>    The Customer had installed old version of PW V4.2 before PW5
>    (LANManager).He performed UPGRADE V4->V5.
>    He never installed PW (Macintosh).

Thanks, that eliminates one theory.
    
>    We executed the command above and the DCLTABLES was updated, but the
>    problem continues with "admin/analyze". 
    
Make sure the customer logs out and logs back in to pick up the new
DCLTABLES.  Sorry I forgot to mention that the first time.

>    Could you have some tips to check the customer' system ?
>    Thanks for your attention and help,
>    Regards,
>    Lorena/CSC/RIO
    
The only other thing I can suggest is to make sure they run the IVP
to validate that all the right PATHWORKS images are installed.

If logging out and in again doesn't fix the problem, and the IVP
shows no checksum errors, then I'm out of ideas off the top of my
head.  You'll have to formally escalate the problem in that case.
4290.7UTRTSC::SWEEPI want a lolly...Tue May 20 1997 06:569
    Also make sure that the customer doesn't have the
    DCLtables in sys$specific.
    
    I saw it once that the customer had 2 dcltables,
    1 in sys$common (that one got updated) and 1 in
    sys$specific (which didn't got updated but got
    used).
    
    Adrie