× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. February 2013

Re: Maintaining Service Program signatures

On 2/20/2013 2:07 PM, Henrik Rützou wrote:

To make a simple example, lets say I have som CGI programs that is build
on My Framework V1.6 that run on lowest level Core V4.3 I have an initial
stack

1. My CGI program
2. Framework V1.6 service programs
3. Core V4.3 service programs

You can install any Core V4.3+ without recompilation in that environment,
if you wish to install Framework V1.7 you will at least have to install
Core V4.8
first because Framework V1.7 uses Core V4.8 as lowest level, but you could
also install Core V4.11 and Framework V1.7 - but still without recompiling
the
CGI programs (ad. 1)

This is what those signatures are for! I wonder how many non-vendors
have interlocking service programs like this? I don't, because if my
equivalent of Framework needs a new Core subprocedure, they are always
compiled together :-)
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.