Skip to form

Are you ready for OpenVMS on x86-64?

Provide us with the VSI$SUPPORT output and fill out this questionnaire; we will get back to you with information on the complexity and cost of a potential migration of your application to VSI OpenVMS x86-64. If you have several applications, please fill the form out only once, listing information for all of your applications.
No fields except for the email are compulsory, but the more information you provide, the better our estimates will be.

1/7. VSI$SUPPORT

VSI$SUPPORT is a script that generates an HTML summary of the OpenVMS system that it runs on. We need this information to ask fewer questions and provide better estimates based on your actual environment.

Instructions:

1. Download VSI$SUPPORT.
2. Copy it to your VMS system and run it using the below command:
$ @VSI$SUPPORT
If you have several different systems, we recommend that you run the script on a production and development system. 
3. Upload the resulting HTML files below.

2/7. Application

Name of the application that you need to migrate to VSI OpenVMS x86-64
Application Status
List the prerequisite products and their versions. This should include both development products (required to build the application) and runtime prerequisites.

3/7. User Requirements

What are the availability requirements for your application? 24/7, 8/5, etc.
What is the scheduled downtime per year?

4/7. Application Architecture

Client/server, interactive/batch-oriented/transaction-oriented/mixed, etc.
If you have a Subsystem, Module call-out, and/or Object-relation diagram of your system, please attach it here.

5/7. Architectural and Design Documentation

Architectural Specification
High Level Design
Functional Specifications
Test Procedures
Do You Have Access to all Application Code?
For each language used in your application, please include the number of source files, approximate number of lines of code, and any comments you may have.
For each database, please provide the database type, size, and number of tables.
If you are using any interfaces other than command line (e.g. DECforms, TDMS, FMS, Curses, XWindows, Motif, etc.), please provide for each one the number of source files, number of lines of code, and number of forms or windows if window-based.
Please provide details of any transaction processing and middleware technologies that are utilised by the application environment. Examples of transaction processing technologies would include ACMS and TUXEDO. Middleware and messaging technologies may include MQSéries, TIBCO,  DEC MessageQ (now Oracle MessageQ), and so on. For each one, provide the product name, version; number of tasks, services, or integrations; average and peak transaction rates; and messages volumes.
Please provide details of any DECnet task-to-task and ftp/sftp interfaces used by the application, including details regarding the numbers of such interfaces, frequency of use, and data volumes transferred.

6/7. Application Systems Environment

List the hardware and software currently required to support the application; describe the general topology of your application.
For each cluster (if any), provide the following information: cluster name, purpose (e.g. test, dev, prod), business function (e.g. shop floor, financial, network), cluster interconnect.
TB/GB/MB
%
For each standalone system or cluster member, provide the system name, purpose, business function, hardware model, cluster name, total memory, and OS version.

7/7. Other Important Data

Among the applications being migrated, are there any interdependencies that might require that applications be migrated together?
List any other important data that you feel was not addressed in the questionnaire.