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

Conference help::decnet-osi_for_vms

Title:DECnet/OSI for OpenVMS
Moderator:TUXEDO::FONSECA
Created:Thu Feb 21 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3990
Total number of notes:19027

3935.0. "X25 filter stays free" by EVTAI1::LEGOUBEY () Thu Apr 17 1997 12:58

    A customer has ugraded two vaxes from 5.6B to 6.3.
    Both vaxes uses OSI CONS.
    One of them has no problem.
    On the other it is impossible to have the status in use on the
    x25 access filter. 
    OSI transport cons filter is OK
    Disable and enable OSI transport doesn't put the filter in use.
    No error message is displayed.
    
    If we try to do and osit$ivpnit with CONS we immedaitly get:
    OSIT$IVP  ..Creating OSI device
    OSIT$IVP  ..Initiating transport connection
    %SYSTEM-F-INSFMEM, insufficient dynamic memory
    %OSIT-F-RRJCON, connect congestion rejection
    
    The memory doesn't seem to be so depleted????
    
    Thanks for any idea.
    
    Francoise
T.RTitleUserPersonal
Name		DateLines
3935.1Is there an ACP Page File Quota problem?BULEAN::TAYLORFri Apr 18 1997 14:5412
    
    Hi Francoise,
    
    This is just a guess, but how is the NET$ACP process 
    Page File Quota?  Since this is a VAX it may have
    the VMS problem that John Weir identified in
    3762.
    
    Cheers,
    
    Pat
3935.2MARVIN::CARLINIFri Apr 18 1997 15:095
    Another guess: is this the "case-sensitivity" problem that existed a
    while back - double check that the cons filter spec and the x25 access
    filter name match EXaCTlY.
    
    Antonio
3935.3Problem solvedEVTAI1::LEGOUBEYMon Apr 21 1997 03:505
    Looking at sys$loadable_images, I saw that PSI$X25_VCM.EXE was missing.
    Putting back this module solved the problem.
    
    
    Francoise
3935.4Glad you found it ...MARVIN::CARLINIMon Apr 21 1997 16:255
    We've had "problems" with that module before now. Check the link
    date/time on it (1-JUL-1996 is probably the latest). I'd be interested 
    in knowing why it vanished.
    
    Antonio
3935.5PSI$X25_VCM identEVTAI1::LEGOUBEYTue Apr 22 1997 03:5715
    Antonio,
    
    
    The customer in .0 is in V6.3 without any eco.
    However, I had reproduced exactly the same behaviour on a M3100/80 in
    my office in V6.3 ECO6.
    The module has the following identification:
    
                    image name: "PSI$X25_VCM"
                    image file identification: "V6.3-ECO04-506"
                    link date/time: 27-JUN-1996 10:58:08.40
                    linker identification: "05-13"
    
    
    Francoise
3935.6MARVIN::CARLINITue Apr 22 1997 08:1714
    1996 is fine as a date - at one stage we regressed to shipping the
    MAY-1994 image, which has some known issues (although I've long since
    forgotten what they are).
    
    If you make PSI$X25_VCM inaccessible somehow (e.g., move it, delete it,
    rename it) then OSI Transport has no chance of talking to PSI (and vice
    versa) so none of that stuff will work.
    
    If you reproduced the customer problem some way other than a deliberate
    mangling of the disk (i.e. you start with a known good version of the
    system and do a correct upgrade but end up with a missing
    PSI$X25_VCM.EXE) then you need to log an IPMT.
    
    Antonio