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

Conference turris::pli

Title:PL/I Notes
Moderator:PEROIT::LUCIA
Created:Sat Jan 25 1986
Last Modified:Wed May 14 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:707
Total number of notes:2472

705.0. "moving libraries" by MLNCSC::PASSALACQUA () Wed Mar 19 1997 09:14

    Hi all, a customer of mine has some problem with DEC PL/I 4.0
    on OpenVMS AXP 6.2.
    I suggested him to install the latest version (4.1) and so he 
    did, but now he asks me if it is possible to move programs
    written, compiled and linked with 4.1 on other systems without
    PL/I installed (he wants only to copy the runtime libraries).
    He did some test moving new executables on other Alphas with 
    version PL/I 4.0, but has problems with libraries, so he would 
    like to copy the new libraries on these systems. Is it a good
    idea?
    Thanks all in advance.
    Sonia
T.RTitleUserPersonal
Name
DateLines
705.1SPECXN::DERAMODan D'EramoWed Mar 19 1997 12:0854
>    did, but now he asks me if it is possible to move programs
>    written, compiled and linked with 4.1 on other systems without
>    PL/I installed (he wants only to copy the runtime libraries).
        
        If he links an .EXE on system A against shareable images
        S1,S2,S3,... then he can only use his .EXE on system B
        if B's versions of S1,S2,S3,... are compatible with A's.
        Usually this means B is running the same version of OpenVMS
        Alpha as A is, or B is running a newer version of OpenVMS
        Alpha than A is.
        
        The only special problem that PL/I presents is that installing
        the PL/I compiler also often upgrades the PL/I run-time
        library shareable image (DPLI$RTLSHR.EXE).  Thus, his system A
        may have a newer DPLI$RTLSHR.EXE than system B has.  He will
        not be able to use his .EXE on system B until he upgrades the
        PL/I run-time library shareable image DPLI$RTLSHR.EXE on B.
        
        That usually means redistributing DPLI$RTLSHR.EXE.  When is
        that allowed?  See the extract from the PL/I SPD (25.30.23)
        below.  He need not get a PL/I compiler license for system B.
        Instead, when he ships his application's .EXE to system B he
        can include the V4.1 DPLI$RTLSHR.EXE with it.
        
        Dan
        
        
        
Run-Time Library Redistribution

The DEC PL/I kit may include updated Run-Time Library shareable im-
ages. Digital grants the user a nonexclusive royalty-free worldwide
right to reproduce and distribute the executable version of the Run-
Time Library designated as PLIRTL.EXE (VAX) and DPLI$RTLSHR.EXE (Al-
pha)(the "RTL's") provided that the user:

o  distribute the RTLs only in conjunction with and as a part of the
   user's software application product which is designed to operate
   in the OpenVMS environment;

o  does not use the name, logo, or trademarks of Digital or UniPrise
   Systems, Inc. to market the user's software application product;

o  includes UniPrise Systems, Inc.'s copyright notice for DEC PL/I on
   the user's product disk label and/or on the title page of the doc-
   umentation for software application product; and

o  agrees to indemnify, hold harmless, and defend Digital and UniPrise
   Systems Inc. from and against any claims or lawsuits, including at-
   torney's fees, that arise or result from the use or distribution
   of the software application product. Except as expressly provided
   herein, Digital or UniPrise Systems Inc. grants no implied or ex-
   press license under any of its patents, copyrights, trade secrets,
   trademarks, or any license or other proprietary interest and rights.
705.2thanksMLNCSC::PASSALACQUAThu Mar 20 1997 03:442
    Thanks a lot for your help.
    Sonia