KEY FEATURES OF SOURCE CONTROL UTILITIES
|
|
- Virginia Johns
- 8 years ago
- Views:
Transcription
1 Source Code Revision Control Systems and Auto-Documenting Headers for SAS Programs on a UNIX or PC Multiuser Environment Terek Peterson, Alliance Consulting Group, Philadelphia, PA Max Cherny, Alliance Consulting Group, Philadelphia, PA ABSTRACT This paper discusses two free products available on UNIX and PC environments called SCCS (Source Code Control System) and RCS (Revision Control System). When used in a multi-user environment, these systems give programmers a tool to enforce change control, create versions of programs, document changes to programs, create backups during reporting efforts, and automatically update vital information directly within a SAS program. These systems help to create an audit trail for programs as required by the FDA for a drug trial. INTRODUCTION The pharmaceutical industry is one of the most regulated industries in this country. Almost every step of a clinical trial is subject to very strict FDA regulations. SAS programs used to summarize and analyze the results of a clinical trial are no exception. SAS programs are considered by the FDA to be an important element of the reliability and accuracy of the information used to approve and manufacture drugs. These programs must adhere to FDA regulations, which require extensive design and documentation controls. The FDA requires SAS code to be compliant with a System Development Life Cycle (SDLC). This includes, but is not limited to, change control, backup/recovery and installation procedures. Drug companies must be able to provide documentation of their software processes and procedures on demand in order to show their software has been safely created and that any changes can be properly managed. Regardless of doing a clinical trial, adherence to a SDLC is a good systems development practice. Besides helping drug companies to meet the FDA regulations, the proper implementation of a SDLC can reduce development costs and decrease the amount of time it takes to report and analyze a clinical trial. Source code control refers to controlling the process of modifying software by managing changes. It lets developers control who can make changes and when these changes are made. It helps to prevent conflicts that could arise when many people edit the same file. It lets programmers save multiple versions of a file and choose the one they would like to use. It also lets them review the history of changes made to a file. There are many different utilities and applications on the market designed to help developers implement a source code control process. This paper discusses two of them, Revision Control System (RCS) and Source Code Control System (SCCS). These are free utilities which are readily available on most UNIX systems and can be also installed on Windows 9x/NT. These systems have been used for many years and there is a lot of free documentation regarding their usage. RSC VS. SCCS The SCCS system was developed by AT&T in the 1970s as a simple system to control source code development. It includes various features that help support a production development environment RCS, which is a more powerful utility than SCCS, was written in early 1980s by Walter F. Tichy at Purdue University in Indiana. It used many programs developed in the 1970s, learning from mistakes of SCCS and can be seen as a logical improvement of SCCS. Since RCS stores the latest version in full, it is much faster in retrieving the latest version. RCS is also faster than SCCS in retrieving older versions and RCS has an easier interface for first time users. RCS commands are more intuitive than SCCS commands. In addition, there are less commands, the system is more consistent and it has a greater variety of options. Since RCS is a newer, more powerful source code control system, this paper will primarily focus on that system. KEY FEATURES OF SOURCE CONTROL UTILITIES RCS does not store the entire version of each file but only the differences between files. Therefore, all versions of a program are being saved in a space efficient way. This can significantly reduce the amount of space required to keep all source files. Since previous revisions remain easily accessible, all subsequent changes do not overwrite the original. Users are always able to retrieve any given revision using version numbers, symbolic names, dates, authors and states. Users can retreat to an older version if they decide that the current version is incorrect, or if they want to see some text that has since been changed or deleted. The only way to permanently delete or corrupt a program is to modify a file located in the RCS directory. The ability to recreate old versions of a single file or a group of files allows users to use source code control as a simple backup system and to recover and modify earlier releases of a product or document. By keeping all file revisions in a separate location, source code control utilities protect these programs from many cases of accidental file deletion or corruption. If a user checks out a program and then accidentally removes it they can easily restore the original version of a program since a copy is kept in another location. RCS allows users to perform a limited, personalized backup of files. If files are being backed up once a week, programmers can check their daily progress notes into a source code control system and have a safe copy in case any of these files are accidentally damaged or deleted. This should not be viewed as a replacement for doing system backups because users will still be vulnerable to system or disk problems, but it may provide for a better control over recovering from a disaster RCS may be used to formalize the process of installing the final version of a program from a user's environment to a production environment. A programmer may check in a final version of a program from their user area and then send a request to a dedicated person to install that version into a production area. The installation of a program into a production area will be done simply by checking out files from the RCS library. All changes to a file are automatically stored in a log file within the RCS subdirectory. Text of each revision, author identification, date and time of check-in and log message summarizing the change is kept by RCS. This allows someone the ability to review the entire history of a program without having to track down colleagues or look for old notes and comments. In another words, it creates an audit trail. RCS provides a version numbering
2 scheme so users can tell which versions of a file are more recent. By saving the history of revisions to a file, users are able to analyze that history later. This can be invaluable because it gives them the ability to see the logic of each incremental change that led from the original source to the current source. If several people are working with the same version, a source code control system can help them coordinate their work by alerting the programmers, preventing one modification from corrupting the other and keeping track of who did what and when. RCS allows branching of versions. This gives users the capability to perform parallel development of several different variants of the same file. For example, while working on the version 2.0 release users can produce a maintenance update to the 1.0 version by modifying several source files from the 1.0 release. RCS stores files as a series of revisions that evolved from each other, as a tree. Each node in the tree represents a revision of the same file. The first version of a file creates a root. All subsequent revisions form a trunk. A branch occurs when a single revision forms more than two revisions. The latest version of both branches and trunk is called a head. Branches are used to maintain parallel versions of the same file. These versions may be then merged together. RCS can automatically update information, including program name, author name, revision number, creation time and date within a program itself. A programmer does not have to worry about updating comments in a program since RCS does it automatically. This is arguably one of the best features of RCS. Please note that source control systems are good tools for controlling all sorts of files, not just source code. Script, flat ASCII files, logs or output files can be controlled by using RCS as well. THE FLOW OF A PROGRAM USING THE RCS SYSTEM back into the RCS library after all necessary changes are made. Therefore the RCS library functions as an extra protection layer between production and user areas. USING RCS One of the reasons why these utilities are so useful is their simplicity. Most of the work is done through few easy-toremember commands. Please look through the following example to see how to use RCS. First, in order for RCS to work there must exist a RCS directory. It can be created in the same directory with program files or it may be located elsewhere. Make RCS directory : mkdir RCS Create a sample program file called with a header containing some of the keywords: /******************************************* Program: $Source$ Version: $Revision$ Date: $Date$ Programmer: $Author$ DO NOT MODIFY ABOVE THIS LINE Project: Ax14723 First Draft Version 1.2 -In -Out Modify Program RCS Library Back In Put into Production Production Version Read-Only Platform: UNIX Purpose: Print all patients in dataset demog Requirements: N/A Parameters: N/A Macros: N/A Formats: N/A Input: N/A Output: N/A Assumptions: N/A Invocation: N/A DO NOT MODIFY BELOW THIS LINE Modification History: $Log$ Figure 1. The flow of a program using the RCS system A draft program is being developed in a programmer's user or test area. After the program is tested, it is checked into the RCS library. The program header should contain RCS keywords so that it can be updated by RCS. Another user, who has write access into the production area, puts the program into production by checking out the program into a directory where all of production code is stored. If this program requires modification it is checked out for editing. The programmer checks the program *******************************************/ data demog; input pid $ sex $ age height weight; cards; 1001 m f f run;
3 To place into RCS control type: ci RCS/,v <-- enter description, terminated with single '.' or end of file: NOTE: This is NOT the log message! >> Enter a description of this version, for example, type: Created dataset demog To save enter. (period) initial revision: 1.1 done RCS just stated you that was placed under RCS control. Note that the program is no longer located in the directory. However, in the RCS directory there is a file,v. By looking at the contents of this file this will not be the original testing file. Instead, the file will contain special codes that RCS uses to keep track of the file. RCS automatically starts version numbering at 1.1, but there are options of using names instead of versions. That's all, the file is now being managed by RCS. To open as read - only type the following command: co -kv The -kv option allows RCS to update the header without extraneous characters. Open the program and notice that information in the header was automatically updated! To modify the file and create the next version of this program, open the file in edit mode by typing: co -l The -l option locks the file so that only one person can edit it at a time. RCS will display the following message: RCS/,v -->.c revision 1.1 (locked) done Modify the program by adding a simple proc print statement: proc print data=demog; run; the program back into the RCS by repeating the ci command: ci RCS/,v <-- new revision: 1.2; previous revision: 1.1 enter log message, terminated with single '.' or end of file: Notice that the version number was incremented to 1.2. If the program was checked out and then checked back in with changes, RCS will make it version 1.3. See the example below. out again and notice that it's header was updated as follows: /******************************************* Program: C:\SUG/RCS/,v Version: 1.3 Date: 2000/02/22 18:33:51 Programmer: CHERNM DO NOT MODIFY ABOVE THIS LINE Project: Ax14723 Platform: UNIX Purpose: Print all patients in dataset demog Requirements: N/A Parameters: N/A Macros: N/A Formats: N/A Input: N/A Output: N/A Assumptions: N/A Invocation: N/A DO NOT MODIFY BELOW THIS LINE Modification History: Testrcs.sas,v Revision /02/22 18:33:51 CHERNM02 Added title to proc print Revision /02/22 18:33:25 CHERNM01 Added proc print Revision /02/22 18:32:54 CHERNM01 Initial revision *******************************************/ One of the most powerful features is the ability to check out any version of a program. This is done by using the -r option. For example, let's assume there are three versions of and we need to edit the second version. This version is numbered by RCS as version 1.2.
4 Type the following command to check out an earlier version: co -l -r1.2 This will open the second revision of in edit mode. Note that RCS will number the next version of as version instead of 1.4. All subsequent changes to that version will be branched out. Accordingly, a change to version 1.2 will create a version 1.3 (See figure 2). Version 1.3 Head Version 1.2 Branch start Root Figure 2. Tree of revisions OTHER USEFUL COMMANDS Use RCS rlog command to see a document's revision history: rlog It will produce the following output : Version Branch head Version Branch node RCS file: RCS/,v Working file: head: 1.3 branch: locks: strict access list: symbolic names: keyword substitution: kv total revisions: 3; selected revisions: 3 description: Initial version revision 1.3 date: 2000/02/22 16:09:31; author: chernm02; state: Exp; lines: +7-3 Added title to proc print revision 1.2 date: 2000/02/22 16:08:06; author: chernm01; state: Exp; lines: Added proc print revision 1.1 date: 2000/02/22 16:07:14; author: chernm01; state: Exp; Created dataset demog RCS can show all files currently being edited by the users: rlog -L -R RCS/* This will produce a list of files currently being edited: RCS/,v As you can see, RCS is easy to use, but each of its commands have many different options. On UNIX read the man pages for all of the options. AUTO-DOCUMENTING HEADERS No program is complete without proper documentation. Any source program should contain, at a minimum, information about its author, last modification date, program name, and a description of the code and all the changes that have been made to the code. Unfortunately, many programs are not sufficiently documented. Manytimes even if there are comments in a program, these comments may not be up to date. Also, many programmers forget to comment on all changes they make to a program. RCS may help to ensure the proper documentation of source code. It allows users to insert certain keywords into working files. These keywords all have special meaning. Each special keyword is inserted into a comment in the original version of a program. When these keywords are in a file during a check out, a check out command updates the value of each keyword with the information stored in the RCS library. The most useful RCS keywords are: $Source$ $Author$ $Date$ $Revision$ $Log$ The $Log$ keyword corresponds to the comments which are entered during a version check in. These comments will be then automatically inserted into a program. Therefore, a programmer will no longer have to be concerned with updating the main documentation in the program because RCS will do most of the work. It will automatically update any file information as long as the proper RCS keywords are used within a comment. A programmer will never forget to describe changes to a program because RCS forces a programmer to describe changes to programs every time it is checked in. Needless to say, it is still the responsibility of a programmer to properly document a program. IMPLEMENTING A VERSION CONTROL SYSTEM IN YOUR COMPANY It is very easy to start using a version control system in your company. However, consider the following issues before implementing a version control system: Choice of SCCS vs. RCS. RCS seems to be a much better utility than SCCS. Location of the RCS directory. The directory where RCS files are stored must be easily accessible, readable and writeable by all users. Note that the entire path to RCS files must be explicitly specified if the RCS directory is located in any other place but a subdirectory.
5 Choice of keywords in the program headers RCS has various keywords which could be inserted into SAS programs. Not all of them are needed. At least the following keywords should be used: $Source$, $Date$, $Author$ and $Log$. Format of standardized headers Since RCS keywords are going to be a part of a program's header it may be helpful to develop standard headers used by all programmers in the group. It will simplify the development of a consistent source control process. Development of user-friendly menu systems RCS is a very powerful and flexible system. It provides users with many different options which may be difficult to remember. In order to simplify the use of these utilities and minimize a chance of a mistake develop a user-friendly menu system. A menu system may shield users from having to remember various RCS commands. A basic menu system may be easily developed by using UNIX scripts or batch files. There are also exist several commercial GUI versions of RCS. TRADEMARKS SAS is a registered trademarks of SAS Institute Inc. Cary, NC, USA indicates USA registration. CONTACT INFORMATION Terek Peterson, MBA Clinical SAS Programming Consultant Alliance Consulting Group (610) (W) terekp@excite.com Max Cherny Clinical SAS Programming Consultant Alliance Consulting Group (610) (W) chernym@yahoo.com REFERENCES: 1. UNIX man pages 2. Robin Burk, David Horvath, "UNIX Unleashed, Internet Edition", Sams, Publishing Sams, "Unix Unleashed", Sams, 1994
COSC345 2013 Software Engineering. Lecture 7: Version Control
COSC345 2013 Software Engineering Lecture 7: Version Control Some Problems Communications File system problems Version control Basic principles and use Outline When to use version control Examples SCCS
More informationTable of Contents. The RCS MINI HOWTO
Table of Contents The RCS MINI HOWTO...1 Robert Kiesling...1 1. Overview of RCS...1 2. System requirements...1 3. Compiling RCS from Source...1 4. Creating and maintaining archives...1 5. ci(1) and co(1)...1
More informationABSTRACT TECHNICAL DESIGN INTRODUCTION FUNCTIONAL DESIGN
Overview of a Browser-Based Clinical Report Generation Tool Paul Gilbert, DataCeutics, Pottstown PA Greg Weber, DataCeutics Teofil Boata, Purdue Pharma ABSTRACT In an effort to increase reporting quality
More informationHow To Backup A Database In Navision
Making Database Backups in Microsoft Business Solutions Navision MAKING DATABASE BACKUPS IN MICROSOFT BUSINESS SOLUTIONS NAVISION DISCLAIMER This material is for informational purposes only. Microsoft
More informationLocal Version Control (sccs, rcs)
Steven J Zeil February 21, 2013 Contents 1 History 2 2 Exploration 5 3 Collaboration 7 4 Strengths and Weaknesses 8 1 Localized Version Control The earliest version control systems in wide use were sccs
More informationSource Code Management/Version Control
Date: 3 rd March 2005 Source Code Management/Version Control The Problem: In a typical software development environment, many developers will be engaged in work on one code base. If everyone was to be
More informationHow To Use Sas With A Computer System Knowledge Management (Sas)
Paper AD13 Medical Coding System for Clinical Trials 21 CFR Part 11 Compliant SAS/AF Application Annie Guo, ICON Clinical Research, Redwood City, CA ABSTRACT Medical coding in clinical trials is to classify
More informationLibrarian. Integrating Secure Workflow and Revision Control into Your Production Environment WHITE PAPER
Librarian Integrating Secure Workflow and Revision Control into Your Production Environment WHITE PAPER Contents Overview 3 File Storage and Management 4 The Library 4 Folders, Files and File History 4
More informationImplementing an Audit Trail within a Clinical Reporting Tool Paul Gilbert, Troy A. Ruth, Gregory T. Weber DataCeutics, Inc.
Paper AD12 Implementing an Audit Trail within a Clinical Reporting Tool Paul Gilbert, Troy A. Ruth, Gregory T. Weber DataCeutics, Inc., Pottstown, PA ABSTRACT This paper is a follow-up to Overview of a
More informationSUGI 29 Applications Development
Backing up File Systems with Hierarchical Structure Using SAS/CONNECT Fagen Xie, Kaiser Permanent Southern California, California, USA Wansu Chen, Kaiser Permanent Southern California, California, USA
More informationChapter 25 Backup and Restore
System 800xA Training Chapter 25 Backup and Restore TABLE OF CONTENTS Chapter 25 Backup and Restore... 1 25.1 General Information... 2 25.1.1 Objectives... 2 25.1.2 Legend... 2 25.1.3 Reference Documentation...
More informationPART 10 COMPUTER SYSTEMS
PART 10 COMPUTER SYSTEMS 10-1 PART 10 COMPUTER SYSTEMS The following is a general outline of steps to follow when contemplating the purchase of data processing hardware and/or software. The State Board
More informationVersion Control Systems
Version Control Systems ESA 2015/2016 Adam Belloum a.s.z.belloum@uva.nl Material Prepared by Eelco Schatborn Today IntroducGon to Version Control Systems Centralized Version Control Systems RCS CVS SVN
More informationContinuous Integration. CSC 440: Software Engineering Slide #1
Continuous Integration CSC 440: Software Engineering Slide #1 Topics 1. Continuous integration 2. Configuration management 3. Types of version control 1. None 2. Lock-Modify-Unlock 3. Copy-Modify-Merge
More informationHow To Write A Clinical Trial In Sas
PharmaSUG2013 Paper AD11 Let SAS Set Up and Track Your Project Tom Santopoli, Octagon, now part of Accenture Wayne Zhong, Octagon, now part of Accenture ABSTRACT When managing the programming activities
More informationusing version control in system administration
LUKE KANIES using version control in system administration Luke Kanies runs Reductive Labs (http://reductivelabs.com), a startup producing OSS software for centralized, automated server administration.
More information1. Product Information
ORIXCLOUD BACKUP CLIENT USER MANUAL LINUX 1. Product Information Product: Orixcloud Backup Client for Linux Version: 4.1.7 1.1 System Requirements Linux (RedHat, SuSE, Debian and Debian based systems such
More informationOnline Backup Client User Manual Linux
Online Backup Client User Manual Linux 1. Product Information Product: Online Backup Client for Linux Version: 4.1.7 1.1 System Requirements Operating System Linux (RedHat, SuSE, Debian and Debian based
More informationOnline Backup Client User Manual
Online Backup Client User Manual Software version 3.21 For Linux distributions January 2011 Version 2.0 Disclaimer This document is compiled with the greatest possible care. However, errors might have
More informationNovaBACKUP. User Manual. NovaStor / November 2011
NovaBACKUP User Manual NovaStor / November 2011 2011 NovaStor, all rights reserved. All trademarks are the property of their respective owners. Features and specifications are subject to change without
More informationFile Management. Chapter 12
Chapter 12 File Management File is the basic element of most of the applications, since the input to an application, as well as its output, is usually a file. They also typically outlive the execution
More informationPharos Uniprint 8.4. Maintenance Guide. Document Version: UP84-Maintenance-1.0. Distribution Date: July 2013
Pharos Uniprint 8.4 Maintenance Guide Document Version: UP84-Maintenance-1.0 Distribution Date: July 2013 Pharos Systems International Suite 310, 80 Linden Oaks Rochester, New York 14625 Phone: 1-585-939-7000
More informationRecoveryVault Express Client User Manual
For Linux distributions Software version 4.1.7 Version 2.0 Disclaimer This document is compiled with the greatest possible care. However, errors might have been introduced caused by human mistakes or by
More informationinforouter Version 8.0 Administrator s Backup, Restore & Disaster Recovery Guide
inforouter Version 8.0 Administrator s Backup, Restore & Disaster Recovery Guide Active Innovations, Inc. Names of all products herein are used for identification purposes only and are trademarks and/or
More informationHow to Use the IBM Tivoli Storage Manager (TSM)
HPCx Archiving User Guide V 1.2 Elena Breitmoser, Ian Shore April 28, 2004 Abstract The Phase 2 HPCx system will have 100 Tb of storage space, of which around 70 Tb comprises offline tape storage rather
More informationWriting Packages: A New Way to Distribute and Use SAS/IML Programs
Paper SAS4201-2016 Writing Packages: A New Way to Distribute and Use SAS/IML Programs Rick Wicklin, SAS Institute Inc. ABSTRACT SAS/IML 14.1 enables you to author, install, and call packages. A package
More informationABSTRACT INTRODUCTION WINDOWS SERVER VS WINDOWS WORKSTATION. Paper FC02
ABSTRACT Paper FC02 Implementing SAS using Microsoft Windows Server and Remote Desktop Paul Gilbert, DataCeutics, Inc., Pottstown, PA Steve Light, DataCeutics, Inc., Pottstown, PA DataCeutics provides
More informationFile Management. Chapter 12
File Management Chapter 12 File Management File management system is considered part of the operating system Input to applications is by means of a file Output is saved in a file for long-term storage
More informationOnline Backup Linux Client User Manual
Online Backup Linux Client User Manual Software version 4.0.x For Linux distributions August 2011 Version 1.0 Disclaimer This document is compiled with the greatest possible care. However, errors might
More informationMapGuide Open Source Repository Management Back up, restore, and recover your resource repository.
MapGuide Open Source Repository Management Back up, restore, and recover your resource repository. Page 1 of 5 Table of Contents 1. Introduction...3 2. Supporting Utility...3 3. Backup...4 3.1 Offline
More informationOnline Backup Client User Manual
For Linux distributions Software version 4.1.7 Version 2.0 Disclaimer This document is compiled with the greatest possible care. However, errors might have been introduced caused by human mistakes or by
More informationFeatures of AnyShare
of AnyShare of AnyShare CONTENT Brief Introduction of AnyShare... 3 Chapter 1 Centralized Management... 5 1.1 Operation Management... 5 1.2 User Management... 5 1.3 User Authentication... 6 1.4 Roles...
More informationWorking with Versioning. SharePoint Services
in SharePoint Services Table of Contents INTRODUCTION TO VERSIONING... 1 ABOUT ENABLING AND CONFIGURING VERSIONS FOR A LIST OR LIBRARY... 2 ABOUT MANAGING MAJOR AND MINOR VERSIONS... 2 OTHER SETTINGS THAT
More informationPlanning for a Disaster Using Tivoli Storage Manager. Laura G. Buckley Storage Solutions Specialists, Inc.
Planning for a Disaster Using Tivoli Storage Manager Laura G. Buckley Storage Solutions Specialists, Inc. Objective Discuss how DRM assists in the recovery of the ADSM server and clients in a disaster
More informationCHAPTER 11 COMPUTER SYSTEMS INFORMATION TECHNOLOGY SERVICES CONTROLS
11-1 CHAPTER 11 COMPUTER SYSTEMS INFORMATION TECHNOLOGY SERVICES CONTROLS INTRODUCTION The State Board of Accounts, in accordance with State statutes and the Statements on Auditing Standards Numbers 78
More informationConfiguration Management Models in Commercial Environments
Technical Report CMU/SEI-91-TR-7 ESD-9-TR-7 Configuration Management Models in Commercial Environments Peter H. Feiler March 1991 Technical Report CMU/SEI-91-TR-7 ESD-91-TR-7 March 1991 Configuration Management
More informationUser s Manual. Version 4.0. Levit & James, Inc.
User s Manual Version 4.0 April 2008 [This page is intentionally left blank] CrossWords Installation & Operation Guide 3 LEGAL NOTES The information contained in this document represents the current view
More informationEssential Project Management Reports in Clinical Development Nalin Tikoo, BioMarin Pharmaceutical Inc., Novato, CA
Essential Project Management Reports in Clinical Development Nalin Tikoo, BioMarin Pharmaceutical Inc., Novato, CA ABSTRACT Throughout the course of a clinical trial the Statistical Programming group is
More informationFigure 1. Example of an Excellent File Directory Structure for Storing SAS Code Which is Easy to Backup.
Paper RF-05-2014 File Management and Backup Considerations When Using SAS Enterprise Guide (EG) Software Roger Muller, Data To Events, Inc., Carmel, IN ABSTRACT SAS Enterprise Guide provides a state-of-the-art
More informationMATLAB @ Work. MATLAB Source Control Using Git
MATLAB @ Work MATLAB Source Control Using Git Richard Johnson Using source control is a key practice for professional programmers. If you have ever broken a program with a lot of editing changes, you can
More informationREx: An Automated System for Extracting Clinical Trial Data from Oracle to SAS
REx: An Automated System for Extracting Clinical Trial Data from Oracle to SAS Edward McCaney, Centocor Inc., Malvern, PA Gail Stoner, Centocor Inc., Malvern, PA Anthony Malinowski, Centocor Inc., Malvern,
More informationMicrosoft SQL Server Guide. Best Practices and Backup Procedures
Microsoft SQL Server Guide Best Practices and Backup Procedures Constellation HomeBuilder Systems Inc. This document is copyrighted and all rights are reserved. This document may not, in whole or in part,
More informationAccess Control and Audit Trail Software
Varian, Inc. 2700 Mitchell Drive Walnut Creek, CA 94598-1675/USA Access Control and Audit Trail Software Operation Manual Varian, Inc. 2002 03-914941-00:3 Table of Contents Introduction... 1 Access Control
More informationSoftware License Registration Guide
Software License Registration Guide When you have purchased new software Chapter 2 Authenticating a License When you would like to use the software on a different PC Chapter 3 Transferring a License to
More informationUsing Windows Administrative Tools on VNX
EMC VNX Series Release 7.0 Using Windows Administrative Tools on VNX P/N 300-011-833 REV A01 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Copyright 2011 -
More informationWhile You Were Sleeping - Scheduling SAS Jobs to Run Automatically Faron Kincheloe, Baylor University, Waco, TX
CC04 While You Were Sleeping - Scheduling SAS Jobs to Run Automatically Faron Kincheloe, Baylor University, Waco, TX ABSTRACT If you are tired of running the same jobs over and over again, this paper is
More informationManual Password Depot Server 8
Manual Password Depot Server 8 Table of Contents Introduction 4 Installation and running 6 Installation as Windows service or as Windows application... 6 Control Panel... 6 Control Panel 8 Control Panel...
More informationTIBCO Spotfire and S+ Product Family
TIBCO Spotfire and S+ Product Family Compliance with 21 CFR Part 11, GxP and Related Software Validation Issues The Code of Federal Regulations Title 21 Part 11 is a significant regulatory requirement
More informationAttix5 Pro Server Edition
Attix5 Pro Server Edition V7.0.3 User Manual for Linux and Unix operating systems Your guide to protecting data with Attix5 Pro Server Edition. Copyright notice and proprietary information All rights reserved.
More informationAssessment of Vaisala Veriteq vlog Validation System Compliance to 21 CFR Part 11 Requirements
/ WHITE PAPER Assessment of Vaisala Veriteq vlog Validation System Compliance to 21 CFR Part 11 Requirements The 21 CFR Part 11 rule states that the FDA view is that the risks of falsification, misinterpretation,
More informationWHITE PAPER Achieving Continuous Data Protection with a Recycle Bin for File Servers. by Dan Sullivan. Think Faster. Visit us at Condusiv.
WHITE PAPER Achieving Continuous Data Protection with a Recycle Bin for File Servers by Dan Sullivan 01_20131025 Think Faster. Visit us at Condusiv.com WITH A RECYCLE BIN FOR FILE SERVERS 2 Article 1:
More informationImproving Your Relationship with SAS Enterprise Guide
Paper BI06-2013 Improving Your Relationship with SAS Enterprise Guide Jennifer Bjurstrom, SAS Institute Inc. ABSTRACT SAS Enterprise Guide has proven to be a very beneficial tool for both novice and experienced
More informationTiburon Master Support Agreement Exhibit 6 Back Up Schedule & Procedures. General Notes on Backups
General Notes on Backups This document describes the procedures to backup the minimum set of files required to recover application and/or data files in the event of a hardware failure or data loss. These
More informationSPSS: Getting Started. For Windows
For Windows Updated: August 2012 Table of Contents Section 1: Overview... 3 1.1 Introduction to SPSS Tutorials... 3 1.2 Introduction to SPSS... 3 1.3 Overview of SPSS for Windows... 3 Section 2: Entering
More informationDiskPulse DISK CHANGE MONITOR
DiskPulse DISK CHANGE MONITOR User Manual Version 7.9 Oct 2015 www.diskpulse.com info@flexense.com 1 1 DiskPulse Overview...3 2 DiskPulse Product Versions...5 3 Using Desktop Product Version...6 3.1 Product
More informationThe Real Challenges of Configuration Management
The Real Challenges of Configuration Management McCabe & Associates Table of Contents The Real Challenges of CM 3 Introduction 3 Parallel Development 3 Maintaining Multiple Releases 3 Rapid Development
More informationUSING SAS WITH ORACLE PRODUCTS FOR DATABASE MANAGEMENT AND REPORTING
USING SAS WITH ORACLE PRODUCTS FOR DATABASE MANAGEMENT AND REPORTING Henry W. Buffum, R. O. W. ScIences, Inc. Darryl J. Keith, U.S. Environmental Protection Agency Abstract: Data for a large environmental
More informationExchange Brick-level Backup and Restore
WHITEPAPER BackupAssist Version 4 Exchange Mailbox Add-on www.backupassist.com 2 Contents 1. Introduction and Overview... 3 1.1 What does the Exchange Mailbox Add-on do?... 3 1.2 Who needs the Exchange
More informationTELE 301 Lecture 7: Linux/Unix file
Overview Last Lecture Scripting This Lecture Linux/Unix file system Next Lecture System installation Sources Installation and Getting Started Guide Linux System Administrators Guide Chapter 6 in Principles
More informationSecurity Correlation Server Backup and Recovery Guide
orrelog Security Correlation Server Backup and Recovery Guide This guide provides information to assist administrators and operators with backing up the configuration and archive data of the CorreLog server,
More informationSiebel Correspondence, Proposals, and Presentations Guide. Siebel Innovation Pack 2013 Version 8.1/8.2 September 2013
Siebel Correspondence, Proposals, and Presentations Guide Siebel Innovation Pack 2013 Version 8.1/8.2 September 2013 Copyright 2005, 2013 Oracle and/or its affiliates. All rights reserved. This software
More informationOnline Backup Client User Manual
For Mac OS X Software version 4.1.7 Version 2.2 Disclaimer This document is compiled with the greatest possible care. However, errors might have been introduced caused by human mistakes or by other means.
More informationSimaPro 7.3.3 database update instructions from SimaPro7.3.0 or older database versions
SimaPro 7.3.3 database update instructions from SimaPro7.3.0 or older database versions SimaPro 7 Technical Note 13, February 2012 Contents SIMAPRO 7.3.3 DATABASE UPDATE INSTRUCTIONS FROM SIMAPRO7.3.0
More informationUsing Continuous Operations Mode for Proper Backups
Using Continuous Operations Mode for Proper Backups A White Paper From Goldstar Software Inc. For more information, see our web site at Using Continuous Operations Mode for Proper Backups Last Updated:
More informationBacking Up TestTrack Native Project Databases
Backing Up TestTrack Native Project Databases TestTrack projects should be backed up regularly. You can use the TestTrack Native Database Backup Command Line Utility to back up TestTrack 2012 and later
More informationDisaster Recovery Planning for Ingres
WHITEPAPER Disaster Recovery Planning for Ingres Specific Information and Issues to Recovery of an Ingres Installation by Chip Nickolett, Ingres Corporation table of contents: 3 Preface 3 Overview 4 Developing
More informationOrder from Chaos: Using the Power of SAS to Transform Audit Trail Data Yun Mai, Susan Myers, Nanthini Ganapathi, Vorapranee Wickelgren
Paper CC-027 Order from Chaos: Using the Power of SAS to Transform Audit Trail Data Yun Mai, Susan Myers, Nanthini Ganapathi, Vorapranee Wickelgren ABSTRACT As survey science has turned to computer-assisted
More informationSuite. How to Use GrandMaster Suite. Backup and Restore
Suite How to Use GrandMaster Suite Backup and Restore This page intentionally left blank Backup and Restore 3 Table of Contents: HOW TO USE GRANDMASTER SUITE - PAYROLL BACKUP AND RESTORE...4 OVERVIEW...4
More informationSAS 9.4 Intelligence Platform
SAS 9.4 Intelligence Platform Application Server Administration Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2013. SAS 9.4 Intelligence Platform:
More informationAccounts Receivable System Administration Manual
Accounts Receivable System Administration Manual Confidential Information This document contains proprietary and valuable, confidential trade secret information of APPX Software, Inc., Richmond, Virginia
More informationSymantec Backup Exec 11d for Windows Servers New Encryption Capabilities
WHITE PAPER: ENTERPRISE SECURITY Symantec Backup Exec 11d for Windows Servers New Encryption Capabilities White Paper: Enterprise Security Symantec Backup Exec 11d for Windows Servers Contents Executive
More informationFrequently Asked Questions
BACKUPS FAQ Why Backup? Backup Location Net Connections Programs Schedule Procedures Frequently Asked Questions I do a backup once a week and sometimes longer, is this sufficient? In most cases, I would
More informationThis policy is not designed to use systems backup for the following purposes:
Number: AC IT POL 003 Subject: Backup and Restore Policy 1. PURPOSE The backup and restore policy establishes the need and rules for performing periodic system backup to permit timely restoration of Africa
More informationSubversion Integration for Visual Studio
Subversion Integration for Visual Studio VisualSVN Team VisualSVN: Subversion Integration for Visual Studio VisualSVN Team Copyright 2005-2008 VisualSVN Team Windows is a registered trademark of Microsoft
More informationCentralized Disaster Recovery using RDS
Centralized Disaster Recovery using RDS RDS is a cross-platform, scheduled replication application. Using RDS s replication and scheduling capabilities, a Centralized Disaster Recovery model may be used
More informationStart Here. Figure 1: Program-Analyze-Write-Review Process
Supporting the Program-Analyze-Write-Review Process with a Development Environment for Base SAS and the Macro Language Barry R. Cohen, Planning Data Systems, Inc. ABSTRACT Pharmaceutical companies do much
More informationHow to Use SDTM Definition and ADaM Specifications Documents. to Facilitate SAS Programming
How to Use SDTM Definition and ADaM Specifications Documents to Facilitate SAS Programming Yan Liu Sanofi Pasteur ABSTRCT SDTM and ADaM implementation guides set strict requirements for SDTM and ADaM variable
More informationSAP Note 1642148 - FAQ: SAP HANA Database Backup & Recovery
Note Language: English Version: 1 Validity: Valid Since 14.10.2011 Summary Symptom To ensure optimal performance, SAP HANA database holds the bulk of its data in memory. However, it still uses persistent
More informationManaging XML Documents Versions and Upgrades with XSLT
Managing XML Documents Versions and Upgrades with XSLT Vadim Zaliva, lord@crocodile.org 2001 Abstract This paper describes mechanism for versioning and upgrding XML configuration files used in FWBuilder
More informationWorkflow Templates Library
Workflow s Library Table of Contents Intro... 2 Active Directory... 3 Application... 5 Cisco... 7 Database... 8 Excel Automation... 9 Files and Folders... 10 FTP Tasks... 13 Incident Management... 14 Security
More informationSwitching from PC SAS to SAS Enterprise Guide Zhengxin (Cindy) Yang, inventiv Health Clinical, Princeton, NJ
PharmaSUG 2014 PO10 Switching from PC SAS to SAS Enterprise Guide Zhengxin (Cindy) Yang, inventiv Health Clinical, Princeton, NJ ABSTRACT As more and more organizations adapt to the SAS Enterprise Guide,
More informationSecurity Policy System Access Control, Data Protection and Recovery
This document describes the security policy for system access control, data protection and recovery in the for the Controller s Office and Treasury Services at Miami University. The security policy sets
More information5 barriers to database source control and how you can get around them
WHITEPAPER DATABASE CHANGE MANAGEMENT 5 barriers to database source control and how you can get around them 91% of Fortune 100 companies use Red Gate Content Introduction We have backups of our databases,
More informationAttix5 Pro Server Edition
Attix5 Pro Server Edition V7.0.2 User Manual for Mac OS X Your guide to protecting data with Attix5 Pro Server Edition. Copyright notice and proprietary information All rights reserved. Attix5, 2013 Trademarks
More informationWorking with a Version Control System
Working with a Version Control System Summary Tutorial TU0114 (v2.4) March 18, 2008 This tutorial looks at how you can use Altium Designer s built-in version control capabilities to check project files
More informationPharmaSUG 2015 - Paper QT26
PharmaSUG 2015 - Paper QT26 Keyboard Macros - The most magical tool you may have never heard of - You will never program the same again (It's that amazing!) Steven Black, Agility-Clinical Inc., Carlsbad,
More informationBack it up. Get it back. Simple.Secure.Affordable.
Back it up. Get it back. Simple.Secure.Affordable. Based on feedback from the Carbonite community, we re expanding our offerings to support user-requested features such as External Hard Drive Backup, Bare
More informationMOVING THE CLINICAL ANALYTICAL ENVIRONMENT INTO THE CLOUD
MOVING THE CLINICAL ANALYTICAL ENVIRONMENT INTO THE CLOUD STIJN ROGIERS, SENIOR INDUSTRY CONSULTANT, LIFE SCIENCES/HEALTH CARE (EMEA/AP) SANDEEP JUNEJA CONSULTING MANAGER (SSOD) AGENDA Move towards cloud
More informationConnectivity. SWIFTNet Link 7.0. Functional Overview
Connectivity SWIFTNet Link 7.0 Functional Overview December 2010 SWIFTNet Link 7.0 Table of Contents 1 Introduction... 3 2 Enhancements and features... 4 2.1 Message and File Copy... 4 2.2 Message and
More informationwww.cristie.com CBMR for Linux v6.2.2 User Guide
www.cristie.com CBMR for Linux v6.2.2 User Guide Contents CBMR for Linux User Guide - Version: 6.2.2 Section No. Section Title Page 1.0 Using this Guide 3 1.1 Version 3 1.2 Limitations 3 2.0 About CBMR
More informationDatabase Management Tool Software User Guide
Database Management Tool Software User Guide 43-TV-25-29 Issue 5 February 2015 Database Management Tool Software Licence Agreement Refer to the Database Tool installer for the software licence agreement.
More informationADSMConnect Agent for Oracle Backup on Sun Solaris Installation and User's Guide
ADSTAR Distributed Storage Manager ADSMConnect Agent for Oracle Backup on Sun Solaris Installation and User's Guide IBM Version 2 SH26-4063-00 IBM ADSTAR Distributed Storage Manager ADSMConnect Agent
More informationBacking up and restoring HP Systems Insight Manager 6.0 or greater data files in a Windows environment
Technical white paper Backing up and restoring HP Systems Insight Manager 6.0 or greater data files in a Windows environment Table of contents Abstract 2 Introduction 2 Saving and restoring data files
More informationDocAve 4.1 Backup User Guide
September 2007 DocAve 4.1 Backup User Guide Additional user guides available at http://www.avepoint.com/support AvePoint DocAve TM 4.1 Enterprise Backup User Guide 1 Copyright 2001-2007 AvePoint, Inc.
More informationActive Directory backup and restore with Acronis Backup & Recovery 11. Technical white paper. o o. Applies to the following editions: Advanced Server
Active Directory backup and restore with Acronis Backup & Recovery 11 Technical white paper Applies to the following editions: Advanced Server Virtual Edition o o o Advanced Server SBS Edition Advanced
More informationC6 Easy Imaging Total Computer Backup. User Guide
C6 Easy Imaging Total Computer Backup User Guide Clickfree and the Clickfree logo are trademarks or registered trademarks of Storage Appliance Corporation. Other product names used in this guide are recognized
More informationMicrosoft Visual Studio Integration Guide
Microsoft Visual Studio Integration Guide MKS provides a number of integrations for Integrated Development Environments (IDEs). IDE integrations allow you to access MKS Integrity s workflow and configuration
More informationSQL Server Protection
User Guide BackupAssist User Guides explain how to create and modify backup jobs, create backups and perform restores. These steps are explained in more detail in a guide s respective whitepaper. Whitepapers
More informationWHITE PAPER: ENTERPRISE SOLUTIONS. Symantec Backup Exec Continuous Protection Server Continuous Protection for Microsoft SQL Server Databases
WHITE PAPER: ENTERPRISE SOLUTIONS Symantec Backup Exec Continuous Protection Server Continuous Protection for Microsoft SQL Server Databases White Paper: Enterprise Solutions Symantec Backup Exec Continuous
More informationQuality Assurance: Best Practices in Clinical SAS Programming. Parag Shiralkar
Quality Assurance: Best Practices in Clinical SAS Programming Parag Shiralkar eclinical Solutions, a Division of Eliassen Group Abstract SAS programmers working on clinical reporting projects are often
More information