PowerPoint Presentations are also available on this web site in 2 different formats. They can be:

  Viewed On-Line                              

                  Downloaded for viewing with PowerPoint 2000  

______________________________________________________________________________

TPS/SOURCE 2000^™ is source control and release management software for applications maintained on Stratus Computers. Through a disciplined environment called a library, TPS/SOURCE 2000 automatically manages all phases of software change from development through production. TPS/SOURCE contains all the required functionality of any good source control software: version management and release access control with checking in, checking out, building, compare and merge, and a full audit trail of everything that was done. Yet, TPS/SOURCE also includes an extensive querying capability that provides an exceptionally accurate look at your system. TPS/SOURCE has the functionality to manage a single library or multiple libraries.

Within every library TPS/SOURCE 2000 ensures the integrity of production releases by keeping development separate from production. For development, it uses a single source code repository to support multiple versions of source code and their variants across multiple hardware architectures and operating systems. It also preserves each version so any changes can be backed out easily, or versions can be compared for differences, or versions can be replicated. For production, TPS/SOURCE enforces standards, and it builds, "freezes," and runs production releases. It emphasizes security and accountability too. It tightens security through access levels, and by constructing a comprehensive audit trail, it tracks every change to the software and labels it with the author's name, time stamp, and release tag for reference.

TPS/SOURCE offers unsurpassed flexibility for customizing the source control environment. It can easily address your prevailing requirements as well as your future requirements when your needs change.

Source Code Control-TPS/SOURCE 2000^™

• Creates the environment of one or more libraries. Each library contains a database of relationships, a history log, and two main subdirectories (Sources and Release).
• Stores and manages versions of source code. A version can be changed by checking it out, changing it, then checking it back in. Upon check-in a new version is created and stored. Any version can be backed out.
• Provides advanced variant management within a library.
• Stores and manages one or more cross sections of versions that comprise a release. A release in the production environment is integrated by the development teams, built, "frozen" for testing, and eventually, released for production.
• Enhances VOS security by allowing customized group or individual access to specific libraries or releases within a library.
• Supports a single library for an in-house application or for an isolated system.
• Supports distributed development in multiple libraries that can be linked into an architecture with a global dictionary (for multiple applications that may depend on each other, on some common platform of routines and utilities, or on specialized systems).
• Supports all Stratus hardware architectures.
• Includes the components TPS/Make, TPS/Scan, and optionally, TPS/Distribution.

Automatic Synchronization of Changed Sources-TPS/Make Facility^™

TPS/Make Facility^™, a component of TPS/SOURCE 2000, performs library auditing and synchronization of TPS/SOURCE-controlled libraries utilizing a top/down approach. It is designed to facilitate the automatic building of releases from changed source. It makes sure a release can stand alone without any missing components. When auditing a release library, TPS/Make moves through the directory tree structure figuring out what the correct version of each source file for a given object and program module should be. If necessary, it recompiles all source files that have changed or that meet specified selection criteria. It also automatically rebinds the necessary commands and objects. TPS/Make eliminates the need to maintain "make files" for determining cross dependencies, and ensures the consistency of source module changes, program module builds, and site-specific production standards.

• Automates compiling and binding by comparing path names and dates encoded in each existing object and program module to its actual file and date last modified. When it locates changed source, it recompiles and binds it.
• Provides the ability to include or exclude back releases in a library or in external libraries from being audited.
• Provides the ability to exclude specific source modules from make processing, e.g., system or communications object modules that likely do not have source files.
• Consistently applies compiler and binder options to enforce standards.
• Offers hundreds of configuration options to perform in whatever structure your application needs, e.g., recompile everything, recompile based on a date, or recompile based on a user-created cross-reference file.

Site Software Audits and Cross Referencing - TPS/Scan Facility^™

TPS/Scan Facility^™, a component of TPS/SOURCE 2000, is a configuration auditing facility designed to simplify the management of large disk volumes and large production libraries. It reports on those objects that meet requested criteria such as, date last modified, or date compiled. It can determine exactly what system components were last changed, and by whom. It also can create a cross-reference of relationships that it discovers when scanning a directory tree.

TPS/Scan was created to answer the following real-world questions:

"What has changed in production this week?"

"Why are there multiple versions of this module?"

"Which module is being used in production?"

"How many modules are compiled with compiler options that effect performance?"

"How much disk space do all of the files that are hit at least once a week require?"

"Are you sure that you recompiled and rebound EVERYTHING since making that change?"

"In all the source code of this application, where are all the locations that refer to the error-code, code, or status?"

• Scans large libraries and disk volumes.
• Creates a cross-reference of relationships by decoding object and program modules to discover the source and object file relationships used to create modules. The contents of the cross-reference only contains information from the decoding. TPS/SOURCE uses the cross-reference file to build all dependents of a module.
• Provides an editor to create a user-defined master cross-reference. The master cross-reference supports various precompile relationships as well as other types of files created by translating source files that were either user-defined or not part of the standard set of VOS languages. Relationships in the master cross-reference remain unless changed by a user. The regular cross-reference is recreated often to keep it current. TPS/Scan uses the master cross-reference file as a base whenever it builds a new cross-reference file.
• Locates and lists all files matching a list of starnames contained under a given root directory.
• Locates, lists, chases, and verifies all links that match a list of starnames.
• Locates and lists all directories in a tree structure.
• Audits files and directories by applying filtering options, such as, program modules modified since last week, or sources in production.
• Audits production elements.
• Audits DASD utilization using a wide range of filters to produce meaningful reports such as disk usage by a specific user or files not used in the last 90 days.
• Automatically builds a command macro, e.g., a macro to compile all pl1 modules.
• Collects library statistics, such as, how many object modules and their compiler options.
• Searches source files for a given string.
• Lists the blocks, subroutines, include files, entry points, external variables in an object module, as well as, the object modules in a program module.
• Shows the children of an object module, parents of a subroutine, and a complete summary of an entry point.
• Locates missing sources bound into objects or objects that have been bound into program modules, but they do not reside in the current directory tree.
• Shows object and source orphans.
• Finds all occurrences of a given object, source or program module.
• Determines who creates and binds object modules.
• Determines who defines or calls a given subroutine.
• Determines who defines a block of code.
• Determines who includes a given include file.
• Determines who uses a given external variable.

Site Tracking and Product Distribution - TPS/Distribution Facility^™

TPS/Distribution Facility^™, an optional component to TPS/SOURCE 2000, performs product distribution management. TPS/Distribution is particularly applicable to software providers because it offers site/system software configuration tracking to facilitate delivering the correct software configuration to each site/system.

• Tracks site/system information
• Groups files into product.
• Automatically transfers a release to any media type for transmission over a network.
• Provides for selecting a current release or a prior release of one or more products.
• Maintains a distribution data base that tracks the release sent to a site/system, the date, etc.
• Generates a list of the shipment content and a pick list for documentation.

The SCI Group sells, supports and maintains all the TPS products worldwide.

Data subject to change without notice. TPS, TPS/Source, TPS/Distribution, TPS/Make, TPS/Trace, are trademarked by Developer's Edge, Inc. Stratus, Continuous Processing, and VOS are registered trademarks of Stratus Computer, Inc. Other computer software or service names mentioned in this publication are trademarks, service marks, or registered trademarks of their respective holders.

 *Please contact your SCI Group Professional for additional information.

SCI Group Marketing and Sales:
Sales: (800) 494-9928 E-Mail: scisales@sci-group.com

Technical Support:
Toll Free: (888) 516-5546 E-Mail: scisupport@sci-group.com