Technical article 100177

What is the SCO DCE Development System for SCO OpenServer 5 (MS107)?

OpenServer 5.0.0

Written · Last revised

Problem

What is the SCO DCE Development System for SCO OpenServer 5, Maintenance Supplement 107, and how do I install it?

NOTE:     Due to attached documentation, this article is especially long.
          It may be unsuitable for faxing.

Solution

The attached cover letter describes the SCO DCE Development System for SCO OpenServer 5, Maintenance Supplement MS107, and the installation procedure.

The files the supplement consists of are available at:

ftp://www.sco.com/Supplements/ms107v1
ftp://www.sco.com/Supplements/ms107v2

The associated cover letter is available at:

ftp://www.sco.com/Supplements/ms107.doc.Z
Dear SCO Customer,
Thank you for downloading the SCO DCE Development System for SCO OpenServer
Release 5.  Use of this product requires a previous purchase of the SCO DCE
Developer's Kit Release 1.0.3.  The original packaging of the Developer's Kit
did not include a working DCE Development System for OpenServer 5, hence this
supplement is provided for your use.  If your package of the SCO DCE
Developer's Kit Release 1.0.3 does contain the SCO DCE Development System
for SCO OpenServer Release 5, then the supplement you just downloaded is not
necessary.

Before installing the SCO DCE Development System for SCO OpenServer Release 5, you have two files:

ms107v1
ms107v2

Before making use of these files, you must decode the files with your DCE development System serial number and activation key.

To do so, execute these commands:
# /etc/brand <serno> <actkey> ms107v1
# /etc/brand <serno> <actkey> ms107v2
where <serno> and <actkey> are your serial number and activation key for
the SCO DCE Development System.  If your serial number is "SCO123456"
and your activation key is "abcdefgh", then the commands would be:
# /etc/brand SCO123456 abcdefgh ms107v1
# /etc/brand SCO123456 abcdefgh ms107v2
After executing these commands, you now have two files that are actually
diskette images.  You must transfer these files to two previously
formatted diskettes.  The commands to do so are:
# dd if=ms107v1 of=/dev/install
# dd if=ms107v2 of=/dev/install
After doing this, you have two product diskettes.  To install the
product, follow the intructions in the enclosed documentation.
Sincerely,
SCO Support Services
                      SCO(r) DCE
              Development System
for SCO OpenServer(TM) Release 5
Release and Installation Notes
*************************************************************************
Postscript picture appears here
*************************************************************************
(c) 1983-1995 The Santa Cruz Operation, Inc.  All Rights Reserved.
No part of this publication may be  reproduced,  transmitted,  stored  in  a
retrieval system, nor translated into any human or computer language, in any
form or by any means, electronic, mechanical, magnetic,  optical,  chemical,
manual,  or otherwise, without the prior written permission of the copyright
owner, The Santa Cruz Operation,  Inc.,  400  Encinal  Street,  Santa  Cruz,
California,  95060,  USA.   Copyright infringement is a serious matter under
the United States and foreign Copyright Laws.
Information in this document is subject to change without  notice  and  does
not represent a commitment on the part of The Santa Cruz Operation, Inc.
SCO DCE Development System software is  commercial  computer  software  and,
together  with  any related documentation, is subject to the restrictions on
U.S.  Government use as set forth below.  If this procurement is for  a  DOD
agency, the following DFAR Restricted Rights Legend applies:
RESTRICTED RIGHTS LEGEND:  Use, duplication, or disclosure by the Government
is subject to restrictions as set forth in subparagraph (c)(1)(ii) of Rights
in Technical Data  and  Computer  Software  Clause  at  DFARS  252.227-7013.
Contractor/Manufacturer  is  The  Santa  Cruz  Operation,  Inc., 400 Encinal
Street, Santa Cruz, CA  95060.
If this procurement is for a civilian government agency, this FAR Restricted
Rights Legend applies:
RESTRICTED  RIGHTS  LEGEND:   This  computer  software  is  submitted   with
restricted  rights  under Government Contract No. _________ (and Subcontract
No. ________, if appropriate).  It may not be used, reproduced, or disclosed
by  the  Government  except as provided in paragraph (g)(3)(i) of FAR Clause
52.227-14 alt  III  or  as  otherwise  expressly  stated  in  the  contract.
Contractor/Manufacturer  is  The  Santa  Cruz  Operation,  Inc., 400 Encinal
Street, Santa Cruz, CA 95060.
The copyrighted software that accompanies this manual is licensed to the End
User  only for use in strict accordance with the End User License Agreement,
which should be read carefully before commencing use of the  software.   SCO
DCE Development System software includes software that is protected by these
copyrights:
(c) 1983-1994 The Santa Cruz Operation, Inc.; (c) 1987-1991 Apollo  Computer
Inc.;  (c)  1989  Berkeley  Softworks;  (c)  1990-1991  Bull S.A.; (c) 1986,
1988-1989 Carnegie  Mellon  University;  (c)  1985-1986,  1988-1991  Digital
Equipment  Corporation; (c) 1989 Encore Computer Corporation; (c) 1989-1991,
1993  Hewlett-Packard  Company;  (c)  1989-1992  Hewlett-Packard  Company  &
Digital   Equipment  Corporation;  (c)  1990-1991  Hewlett-Packard  Company,
Digital Equipment Corporation, &  Locus  Computing  Corporation;  (c)  1985,
1987-1992  IBM  Corporation;  (c) 1981-1988 Informix Software Inc.; (c) 1990
Locus Computing Corporation; (c) 1984-1990 Microsoft Corporation;  (c)  1985
MIPS  Computer  Systems  Inc.;  (c)  1985-1991  Massachusetts  Institute  of
Technology;  (c)  1986-1988   MIT  Information  Systems  and   MIT   Student
Information   Processing   Board;  (c)  1986-1988  MIT  Student  Information
Processing Board; (c) 1990-1993 Open Software Foundation Inc.; (c) 1981-1985
Relational  Database Systems Inc.; (c) 1990 RSA Data Security Inc.; (c) 1988
Secureware Inc.; (c) 1987-1991 Siemens AG;  (c)  1991-1992  Siemens  Nixdorf
Information  Systems;  (c) 1990-1992 Siemens Nixdorf Informationssysteme AG;
(c) 1984, 1987 Sun Microsystems Inc.; (c)  1989-1993  Transarc  Corporation;
(c)  1991 Transarc Corporation, Hewlett-Packard Company, & Digital Equipment
Corporation; (c) 1980, 1982-1983, 1985-1991 Regents  of  the  University  of
California;  (c)  1983  Eric P. Allman; (c) 1988-1989 Adam de Boor; (c) 1986
Gary S. Brown; (c) 1986 David Kovar; (c) 1987 Drew  D.  Perkins;  (c)  1986-
1987  Damon  Permezel;  (c)  1985  Avadis  Tevanian, Jr.; (c) 1988 Walter L.
Wimer.  All Rights Reserved.
SCO, the SCO logo, The Santa Cruz Operation,  Multiscreen,  SCO  OpenServer,
Open  Desktop,  ODT,  SCO  Global  Access,  SCO  Open  Server,  SCO MPX, SCO
MultiView, SCO Visual Tcl, and VP/ix are trademarks or registered trademarks
of  The Santa Cruz Operation, Inc. in the USA and other countries. All other
brand and product names are or  may  be  trademarks  of,  and  are  used  to
identify products or services of, their respective owners.
16 June 1995       Document Version: 1.0.3 B
About this book
     How this book is organized ..........................................
     Related documentation ...............................................
     Typographical conventions ...........................................
     How can we improve this book? .......................................

Chapter 1 Installing and removing the SCO DCE Development System Before installing ................................................... Installing the SCO DCE Development System ........................... Removing the SCO DCE Development System .............................

Chapter 2
Using the SCO DCE Development System
     Components of the development system ................................
     Developing world-wide applications ..................................
     Using thread-safe libraries .........................................
        libsocket routines ...............................................
        libc routines ....................................................
        Process-blocking routines ........................................
        Replacement thread-safe routines .................................
     Linking applications ................................................
Appendix A
Reference pages
        Name         .....................................................
        Syntax         ...................................................
        Description         ..............................................
        See also         .................................................
        Standards conformance         ....................................
About this book

This book provides the information you need to install and use the SCO(r) DCE Development System Release 1.0.3 for SCO OpenServer(TM) Release 5. It describes how to install the libraries, header files, and IDL (Interface Definition Language) compiler, as well as how to write multithreaded applications, and how to link your applications.

_________________________________________________________________________
   NOTE  To learn about any limitations on the SCO DCE Development
   System Release 1.0.3 for SCO OpenServer Release 5, or to find
   additional information not contained in the printed documentation,
   read the ASCII file /opt/dcelocal/readme/README.devsys after
   installing the product.
_________________________________________________________________________

You will find the information you need more quickly if you are familiar with:

+  ``How this book is organized''
+  ``Related documentation''
+  ``Typographical conventions''
Although we try to present information in the most useful way, you are
the ultimate judge of how well we succeed.  Please let us know how we can
improve this book.
How this book is organized
This book describes:
+  how to install the SCO DCE Development System.
+  when to use data privacy.
+  how to make thread-safe procedure calls.
+  how to link your applications.
Related documentation
The SCO DCE Development System Release 1.0.3 includes online versions of
all of the OSF DCE manual pages, and all of the additional SCO manual
pages for commands, files, and routines that have been added or modified
by SCO.  Unlike the SCO manual pages, which use alphabetic sections, the
OSF DCE manual pages use numeric manual page sections, supplemented with
an alphabetic three letter suffix, For example, the DCE library routine
rpc_binding_free is referenced as rpc_binding_free(3rpc).
Cross-references to standard UNIX(r) system commands and routines in the
DCE manual pages use numbered sections, rather than the alphabetic
sections used in SCO documentation.  For example, a reference to the
admin command appears as admin(1) rather than admin(CP).
Some of the manual pages include tables that are formatted for screens
that are wider than 80 columns, making them difficult to read.  A
workaround is to display such manual pages in a scoterm(X) window, then
widen the window sufficiently to see the entire width of the table.

To access the manual page for a command that is normally entered as two or more words separated by spaces, replace the spaces with underscores. For example, to display the manual page for the rpccp add mapping command, enter man rpccp_add_mapping.

PTR Prentice-Hall publishes the DCE documentation provided by OSF(TM). (All of the following PTR Prentice-Hall books are included in the SCO DCE Development Kit Release 1.0.3.)

OSF DCE Application Development Guide
     describes how to write DCE applications.  This book should be
     understood before writing DCE applications.

OSF DCE Application Development Reference lists the library routines that DCE applications can call.

Introduction to OSF DCE provides an overview of DCE and a glossary of DCE terminology.

OSF DCE Administration Guide - Core Components describes how to administer a DCE cell.

OSF DCE Administration Guide - Extended Services
     describes how to configure and administer the X.500 Global Directory
     Service (GDS).

OSF DCE Administration Reference lists the DCE administration commands.

Other books about DCE are available.  The following books are published
by O'Reilly and Associates:

Understanding DCE gives an overview of DCE and DCE planning.

Guide to Writing DCE Applications provides an introduction to writing DCE application programs.

The following book is published by McGraw-Hill, Inc.:

OSF DCE: Guide to Developing Distributed Applications describes how to build distributed software using OSF DCE.

Typographical conventions

This publication presents commands, filenames, keystrokes, and other special elements in these typefaces:

Example:     Used for:
lp or lp(C)  commands, device drivers, programs, and utilities (names,
             icons, or windows); the letter in parentheses indicates the
             reference manual section in which the command, driver,
             program, or utility is documented

/new/client.list files, directories, and desktops (names, icons, or windows)

root         system, network, or user names
filename     placeholders  (replace with appropriate name or value)
<Esc>        keyboard keys
Exit program?
             system output  (prompts, messages)
yes or yes   user input
``Description''
             field names or column headings  (on screen or in database)
Cancel       button names
Edit         menu names
Copy         menu items

File != Find != Text sequences of menus and menu items

open or open(S)
             library routines, system calls, kernel functions, C
             keywords;  the letter in parentheses indicates the reference
             manual section in which the file is documented
$HOME        environment or shell variables
SIGHUP       named constants, signals
``adm3a''    data values
How can we improve this book?
What did you find particularly helpful in this book?  Are there mistakes
in this book? Could it be organized more usefully? Did we leave out
information you need or include unnecessary material?  If so, please tell
us.
To help us implement your suggestions, include relevant details, such as
page number, section name, page number, or system component.  We would
appreciate information on how to contact you in case we need additional
explanation.

To contact us, write to us at:

Technical Publications
Attn:  CFT
The Santa Cruz Operation, Inc.
PO Box 1900
Santa Cruz, California  95061-9969
USA
or e-mail us at:
techpubs@sco.com  or   ...  uunet!sco!techpubs
Thank you.

Chapter 1 Installing and removing the SCO DCE Development System

This chapter describes:
+  the steps to take before installing the SCO DCE Development System.
+  the hardware and software needed to install the SCO DCE Development
   System (see ``Before installing'').
+  the procedure for installing the SCO DCE Development System.
+  the procedure for removing the SCO DCE Development System.
Before installing

Before installing the SCO DCE Development System for SCO OpenServer Release 5, check that:

+  the SCO DCE Developer's Kit Release 1.0.2 is not installed on your
   system.  See the SCO DCE Developer's Kit Release and Installation
   Notes for information on how to remove the Kit if it is installed.
+  the SCO DCE Developer's Kit EAP Release 1.0.3 is not installed on your
   system.  If it is installed, remove it using custom(C).
+  the SCO DCE Development System Release 1.0.3 for SCO(r) Open
   Desktop(r) Release 3.0 is not installed on your system.  If it is
   installed, remove it using custom(C).
+  12MB of free disk space is available to install the SCO DCE
   Development System.
+  the SCO OpenServer Development System Release 5 is installed.
Installing the SCO DCE Development System
1.  Log in as root.
2.  Start the Software Manager:
+  From the UNIX prompt, enter custom.
+  Select the Software Manager from the System Administration
   toolshed on the Desktop.
3.  Select Install New from the Software menu.
4.  Select the current host by pressing Continue.
5.  Insert the SCO DCE Development System for SCO OpenServer Release 5
    floppy disk Volume 1.
6.  Choose the correct media device (such as Floppy Disk Drive 0) and
    press Continue.  The system installs the custom data files and
    executes the Product Prep script.
7.  When prompted for your installation preference, press Full for a full
    installation or Partial for a partial installation.
_________________________________________________________________________
     NOTE  Only choose Partial  if you do not want to install the
     development system manual pages. If you choose partial, you are
     presented with a selection list of components to install.
1.  Expand the list by selecting Expand Fully.
2.  Highlight the components you want to install.
     3.  Press Install.
_________________________________________________________________________
8.  When prompted to insert the next volume, insert Volume 2, then press
    Continue.  The system extracts the files from the disk, then executes
    the initialization script.
9.  When prompted, enter your serial number, then your activation key.
    These are printed on the SCO PRODUCT ACTIVATION KEY CARD packaged
    with the product.  When prompted, press <Return>.

10. The system runs the DCE Development System initialization script.

If initialization fails, you see a message describing what to do to work around the problem.

Press <Return> to continue.

11. Select Exit from the Host menu.

12. Remove the disk from the disk drive.

Removing the SCO DCE Development System

Before removing the SCO DCE Development System, ensure that noone is currently using it or bring the system to single-user mode. Any binaries in use during the product removal will not be removed.

1.  Log in as root.
2.  Start the Software Manager:
+  From the UNIX prompt, enter custom.
+  Select the Software Manager from the System Administration
   toolshed on the Desktop.
3.  Highlight the SCO DCE Development System Release 1.0.3.
4.  Select Remove Software from the Software menu.
5.  Choose Remove to confirm the removal.

The system creates a file list and removes the SCO DCE Development System.

6.  Select Exit from the Host menu.
Chapter 2
Using the SCO DCE Development System
The SCO DCE Development System provides the runtime libraries, header
files, and IDL compiler to create threaded, distributed client/server
applications that use secure Remote Procedure Calls (RPC).  For a list of
the components provided, see ``Components of the development system''.
With these libraries, it is possible for clients and servers to make use
of the DCE Cell Directory Services or X.500 Directory Services in such a
way that clients can locate compatible servers by name at runtime.
DCE applications are typically threaded to improve performance.  For
information on thread-safe libraries, see ``Using thread-safe
libraries''.
To learn how to link your applications, see ``Linking applications''.
This chapter supplements the information in the OSF DCE Application
Development Guide and OSF DCE Application Development Reference.  Read
these books to learn how to build DCE applications.  You can also read
the books on DCE application development listed in ``Related
documentation''.
Components of the development system

The SCO DCE Development System includes the following tools and libraries:

+  the library archives libcma.a (POSIX threads) and libdce.a (DCE
   library routines)
+  libgds.a (a reentrant, thread-safe XDS/XOM library archive)
+  header files (in /usr/include and in /usr/include/dce)
+  the IDL compiler and header files
+  the uuidgen(1rpc) utility
+  the source files for two sample time provider programs,
   dts_ntp_provider and dts_null_provider.  (These programs are described
   in the Prentice-Hall book OSF DCE Administration Guide -- Core
   Components.)
+  the online manual pages
_________________________________________________________________________
   NOTE  The SCO DCE Development Kit Release 1.0.3, of which the SCO
   DCE Development System is a part, contains all the components of
   the SCO Distributed Services, including:  SCO Cell Directory
   Service, SCO Security Services, SCO X.500 Directory Services, the
   SCO DCE Executive, and the SCO Distributed Administration Service.
_________________________________________________________________________
Developing world-wide applications
Applications that must run on hosts both inside and outside North America
must not use the data privacy option for RPC.  Data privacy uses the Data
Encryption Standard (DES) encryption method.  Because DES cannot be
exported outside of North America, only the North American version of the
SCO DCE Executive supports data privacy.  A distributed (client/server)
application that requests or uses data privacy fails with a runtime error
if either the client or the server is not running the North American
version of the SCO DCE Executive.
Using thread-safe libraries
The SCO DCE Development System provides a user-level implementation of a
POSIX-compliant threads package with a library of functions that can be
used to write multithreaded applications.  When writing multithreaded
applications, you must take into account the fact that not all library
routines are reentrant, and therefore not thread-safe.  This is true of
some of the routines in the SCO OpenServer Development System.
Routines that return pointers to static structures are not thread-safe.
Applications that call such routines must use the global semaphore
(mutex).  Use the pthread_lock_global_np(3thr) library routine to lock
the mutex, and pthread_unlock_global_np(3thr) to unlock it (after copying
the static data to local data).  An application that does not call these
routines, even if it executes only a single thread, can run incorrectly.
The following sections list all of the routines in the SCO OpenServer
Development System that are known to be thread-safe, and those that are
not.  If a routine is not listed here as thread-safe, assume that it is
not thread-safe.  Some of the routines listed are thread-safe because
they are reentrant, and some have been made thread-safe by implementing
``jackets'' around them.  (See the OSF DCE Application Development Guide
for a discussion of jackets).
You must write your own jacket around every unjacketed routine you call
that can eventually call a routine that is not thread-safe.  Knowing
whether a jacket is required can be a non-trivial task.  A routine may
not directly call a non-reentrant routine, yet one of those called
routines may, in turn, call a non-reentrant routine.  Some code paths may
result in a call to a non-reentrant routine, while others may not.  If
there is even a single code path, starting from a routine you call
explicitly in your application, that can result in just one call to a
non-reentrant routine anywhere in the calling stack, the routine you call
must be jacketed to guarantee that your application is thread-safe.
_________________________________________________________________________
   NOTE  For better application program performance, whenever possible
   use thread-safe libraries instead of locking routines with jackets.
_________________________________________________________________________
To ensure that your application links with thread-safe routines, list the
libraries in the order described in ``Linking applications'' when
compiling and linking.
_________________________________________________________________________
   WARNING  To avoid abnormal program termination and core dumps in
   multithreaded applications that handle signals, use only POSIX
   signal handling services.
_________________________________________________________________________

For more information on programming multithreaded applications, including the use of POSIX signal handling services, refer to the OSF DCE Application Programming Guide.

libsocket routines
Most libsocket.a routines are thread-safe.  Only those listed here are
not thread-safe:
endhostent                   getnetent                        parsetos
endnetent                    getprotobyname                   rcmd
endprotoent                  getprotobynumber                 rexec
endservent                   getprotoent                      ruserok
endtosent                    getservbyname                    sethostent
ether_aton                   getservbyport                    setnetent
ether_ntoa                   getservent                       setprotoent
gethostbyaddr                gettosbyname                     setservent
gethostbyname                hsterror                         settosent
getnetbyaddr                 inet_ntoa
getnetbyname                 logwtmp
libc routines
Most libc.a routines are thread-safe.  Only those listed here are not
thread-safe:
dial                           fcvt                               getpass
ecvt                           getlogin                           undial

The following routines may or may not require semaphores (see the note following for an explanation):

closedir                        getpwuid                         seekdir
defopen                         fgetgrent                        setgrent
defread                         getutent                         setpwent
endgrent                        fgetpwent                        setutent
endpwent                        getutid                          tdelete
endutent                        getutline                        telldir
getgrent                        opendir                          tfind
getgrgid                        putpwent                         tsearch
getgrnam                        pututline                        twalk
getpwent                        readdir                          utmpname
getpwnam                        rewinddir
_________________________________________________________________________
   NOTE  The routines from libc.a in the preceding table must often be
   called in a transaction-oriented manner from a multithreaded
   application.  This means that one thread must call all of the
   routines needed to complete a ``transaction'' before another thread
   calls any of those same routines.  All threads must attempt to
   seize the same semaphore before calling the routines that make up
   the ``transaction''.  A thread that has the semaphore releases it
   only after it has finished calling all of the routines that
   constitute the transaction.
   If the threads in an application call the above routines to access
   the same directory, they must first attempt to seize the same
   semaphore before making the calls to serialize their access to the
   directory.  If each thread is managing a different directory,
   however, the threads can call the routines without using
   semaphores.
_________________________________________________________________________
Process-blocking routines

The routines listed here either will or may block in the kernel. If a routine blocks in the kernel, the entire calling process is blocked, stopping all threads until the process is rescheduled for execution.

The following routines always block in the kernel:

sleep, wait, wait3, waitpid
The following routines can block in the kernel if called in blocking mode
(the IPC_NOWAIT bit in the flags parameter or parameter field is not
set):
semop, msgrcv, msgsnd
Replacement thread-safe routines
The standard C library function strtok(S) uses static storage to keep
track of how much of the input string has been parsed between consecutive
calls, thus making the routine non-reentrant.  A reentrant (thread-safe)
version of this routine, strtok_r(3thr), is available in libc.a in
conformance with POSIX P1003.4a. See the strtok_r manual page in Appendix
A, ``Reference pages''.
Linking applications

When linking DCE applications, specify the libraries in the following order:

1.  user-created libraries
2.  libgds.a (for XDS/XOM applications only)
3.  libdce.a (DCE library routines)
4.  libcma.a (POSIX threads library)
5.  libm.a (mathematics library)
6.  system libraries other than libsocket.a
7.  libsocket.a (socket routines)

Applications linked with libgds.a must also be linked with libcma.a.

The following lists several different types of application programs and the libraries (in order) they must be linked with.

multithreaded only  user libraries, libcma.a, libm.a, system libraries,
                    libsocket.a
X.500 only          user libraries, libgds.a, libcma.a, system libraries,
                    libsocket.a
XDS/CDS             user libraries, libgds.a, libdce.a, libcma.a, system
                    libraries, libsocket.a
DCE RPC             user libraries, libdce.a, libcma.a, system libraries,
                    libsocket.a
Appendix A
Reference pages
strtok_r(3thr)
Name
strtok_r - reentrant version of strtok (S)
Syntax
cc . . . -lcma
char *strtok_r(
        char *s1,
        char *s2,
        char **s3);
Description
strtok_r() returns substrings from s1.  strtok_r() expects the string s1
to consist of a sequence of zero or more text tokens delimited by spans
of one or more characters specified in separator string s2. The first
call (with pointer s1 specified and *s3 a null pointer) returns a pointer
to the first character of the first token in s1, and replaces the first
delimiter in s1 with the null character (to delimit it as a string).  The
function updates *s3 so that it points to the first character following
the returned token.  On subsequent calls to strtok_r(), s1 should be the
null string, and *s3 should be be left unchanged so that searching
continues from the previous position in s1.  When no tokens remain in s1,
strtok_r() returns the null pointer.

The separator string s2 can change from call to call.

See also
strtok(S)
Standards conformance
IEEE POSIX Std 1003.4a
6 June 1995
AJ08706P001

From the Xinuos technical article database, record 100177. Reproduced with permission. The original is at www.sco.com/ta/100177, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.