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

Conference vaxaxp::vmsnotes

Title:VAX and Alpha VMS
Notice:This is a new VMSnotes, please read note 2.1
Moderator:VAXAXP::BERNARDO
Created:Wed Jan 22 1997
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:703
Total number of notes:3722

524.0. "Using sharable images?" by PTOSS1::HRIADILM () Thu Apr 24 1997 15:51

    Looking for technical info on the limitations of using sharable
    images...
    
    Specifically, is there a limit on the number of sharable images that
    can be used within a single application? What does "vector full on
    message area" link error mean?
    
    						Many thanks...
T.RTitleUserPersonal
Name
DateLines
524.1More Info Needed...XDELTA::HOFFMANSteve, OpenVMS EngineeringThu Apr 24 1997 17:1814
   Can you post the full error message text, the OpenVMS version
   and platform, and the LINKER command and any options file(s).
   Also some idea of how many component shareable, privileged
   shareables (user-written system services), and message files
   are involved here?

   (I've done a search of the linker facility on both OpenVMS VAX
   and OpenVMS Alpha (V7.1), and do not see this error message
   included there.)

   There's a limit of "42" in this area, but without knowing more
   about the error message, it's difficult to say if you've reached
   this limit.
524.2In processing of getting more info...PTOSS1::HRIADILMThu Apr 24 1997 20:024
    Thanks...
    
    I will attempt to get more specific info from the customer as soon as
    possible.
524.3AUSS::GARSONDECcharity Program OfficeSun Apr 27 1997 23:3518
    re .0
    
    There are some practical limits that you can hit when you have a large
    number of shareable images.
    
    One is a vector limit (that could affect message files or user written
    system services I think). I wasn't aware that it is detected at link
    time. One might get "VECFULL, privileged vector limit exceeded" (at run
    time?). This is a hard limit. The only workaround is application
    change.
    
    The other is the process section limit. You might get "PSTFULL, process
    section table is full" at run time in which case the slack way is to 
    increase PROCSECTCNT but you should probably look at the application to
    see whether it is sensibly designed.
    
    P.S. The customer would benefit from 1) identifying the exact error
    message and 2) giving it to $ HELP/MESSAGE before asking Digital.