This document contains a brief overview of the Software AG Multiple Architecture Runtime System (SMARTS) and the requirements to run it.
This document covers the following topics:
SMARTS supports multiple platforms and environments on each platform. It implements a standard runtime environment and supports standard C library functions such as standard I/O, sockets, pthreads, and semaphores.
Although primarily a C runtime environment, SMARTS extensions provide access as well to the facilities from other programming languages including Assembler, COBOL, and PL/1.
SMARTS operates in two distinct environments: server and client.
SMARTS supports a high performance environment for running server components on the different supported platforms: OS/390, VSE/ESA, VM/CMS, MSP (FACOM), and BS2000.
The SMARTS server environment provides a multitasking architecture that uses blocks of storage called 'threads' in which SMARTS application programs can run. By ensuring that all application storage is in contiguous blocks of the address space, the server environment is in a position to move dormant applications out of the address space to make room for more active users. If or when such a dormant application becomes active again, it is simply moved back into the address space and dispatched again.
The SMARTS server environment
uses its multitasking structure to make full use of operating system subtasks to drive the system CPUs.
uses contiguous storage threads to give it more control over the applications' storage areas, thus enabling it to handle more applications running in the one address space.
shares the underlying operating system subtasks between users and is thus not subject to restrictions on the number of processes that can be concurrently supported.
uses a state-of-the-art buffer pool management technique that ensures consistent path lengths, no fragmentation of storage areas, and expansion and contraction of the storage areas within the address space.
uses a state-of-the-art resource manager that ensures the shortest path length possible for the serialization of resources. The technique uses only machine instructions unless it is necessary to wait for a resource.
is ready now for 24-by-7 operation as the nucleus does not need to be cycled for any internal reasons and the buffer manager and resource manager can handle higher than expected loads subject to the resources being available in the address space.
On the supported platforms, SMARTS-based applications are supported in a number of so-called client environments: batch, OS/Transaction Server (CICS), Com-plete (version 6.1 or above), and UTM. In all cases, the support enables client applications to use the SMARTS SDK library functions:
| Server Environment | Supported Client Environments |
|---|---|
| OS/390 | Batch, TSO, OS/TS, IMS/DC, IMS/Batch, Com-plete |
| VSE/ESA | Batch, OS/TS, Com-plete |
| MSP (FACOM) | Batch, Com-plete |
| VM/CMS | CMS Command line programs |
| BS2000 | Batch/TIAM, UTM |
In general, the client environments support everything that the server environment supports; however, Software AG recommends that you avoid running heavy duty applications in client environments. For example, a 'pthreaded' application should not be run in an OS/TS environment, even though it is functionally possible.
IBM OpenEdition TCP/IP available in supported OS/390 and z/OS releases.
VSE/ESA version 2.5 or above using the Connectivity Systems TCP/IP 4 VSE Service Pack E.
Note:
This
requires Adabas SVC 7.4.1 . The prerequisites
described in VSE/ESA Prerequisites in the Release Notes of
EntireX for VSE/ESA must be fulfilled. If you are
using Entire Net-Work, version 5.8.1 or above is
required.
VM/ESA using the standard IBM stack available on VM.
