Digital PDFs

AA-V810A-TK

May 1983

34 pages

Original

1.1MB

Document:	DIBOL-83 Compatibility Guide
Order Number:	AA-V810A-TK
Revision:	0
Pages:	34
Original Filename:

OCR Text

DISOl-S3
Compatibility Guide
Order No: AA-V810A-TK
May 1983

Supersession/Update Information:

This is a new manual.

Operating System and Version:

CTS-300 VS.O
RSTS/E DIBOL VS.O
VAX/VMS DIBOL V2.0
Professional Tool Kit DIBOL V1.S

First Printing, May 1983

The information in this document is subject to change without notice and
should not be construed as a commitment by Digital Equipment
Corporation. Digital Equipment Corporation assumes no responsibility for
any errors that may appear in this document.

The software described in this document is furnished under a license and
may only be used or copied in accordance with the terms of such license.

No responsibility is assumed for the use or reliability of software on
equipment that is not supplied by DIGITAL or its affiliated companies.

The specifications and drawings, herein, are the property of Digital
Equipment Corporation and shall not be reproduced or copied or used in
whole or in part as the basis for the manufacture or sale of items without
written permission.
Copyright © 1983 by Digital Equipment Corporation. All Rights Reserved

The following are trademarks of Digital Equipment Corporation:

CTIBUS
DEC
DECmate
DECsystem-10
DECSYSTEM-20
DECUS
DECwriter
DIBOL

~D~DDmD

MASSBUS
PDP
P/OS
PRO/BASIC
Professional
PRO/FMS
PRO/RMS
PROSE
Rainbow

RSTS
RSX
Tool Kit
UNIBUS
VAX
VMS
VT
Work Processor

CONTENTS
Page
INTRODUCTION ............................................................... vii
CHAPTER 1

COMPILER DIRECTIVES

.IFDEF-.ENDC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
.IFNDEF-.ENDC .......................................................
.INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
.LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
.NOLIST. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
.PAGE .................. , ................. " . . . . . .. . .. . .. . . . . . .. ... ..
.TITLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
CHAPTER 2

LANGUAGE ELEMENTS

Character Set .........................................................
Statement Line Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Statement Labels ......................................................
Array Subscripting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Literals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Substrings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Decimal Expressions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
CHAPTER 3

2-1
2-1
2-1
2-1
2-1
2-1
2-1

DATA DIVISION STATEMENTS

RECORD ..... " .... .... .. ................. ......... ........... .......
COMMON............................................................
Field Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Array Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
SUBROUTINE. .. . . . . . ... .. . ... . ... . . ... .. . . ... . . .. .. . . . . .. . . . . . . . . . . ..
CHAPTER 4

1-1
1-1
1-1
1-1
1-1
1-1
1-1

3-1
3-1
3-1
3-2
3-2

PROCEDURE DIVISION STATEMENTS

Value Assignment Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
ACCEPT.... ...... . .... .. ............................. ...............
BEGIN-END. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
CALL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
CLEAR...............................................................
CLOSE.......................................... ................ ....
DELETE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
DETACH. .......... .... ...................... .... ................ ....
DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
DO-UNTIL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
FOR.. .... .. ....... ...... ............. ........... ....................
FORMS..............................................................

iii

4-1
4-1
4-1
4-1
4-1
4-1
4-1
4-1
4-2
4-1
4-2
4-2

CONTENTS (Cont.)
Page

GOTO .............................................................
GOTO (Computed) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
IF........................... .. ......................... . ........ ..
IF-THEN-ELSE .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
INCR ........................ .. .......................... ...... .... ..
LOCASE ...........................................................
LPQUE ...................... .................................... ..
OFFERROR ........................................................
ONERROR ....................................................... ..
OPEN....................... .................................... ..
PROC-END . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
READ (Relative file). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
READ (Indexed file). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
READS...................... .................................... ..
RECV ................................................. -......... ..
RETURN.... .. .. .. . . . ....... . .. .... . . . ... . . . . . . . . . . . . .. . . . .. . ... . ..
SEND....................... .................................... ..
SLEEP....................... .................................... ..
STOP........................ .................................... ..
STORE............................................................
UNLOCK...........................................................
UPCASE ..................... .................................... ..
USiNG........................................................... ..
WHILE.............................................................
WRITE (Relative File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
WRITE (Indexed File) ........... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
WRITES...........................................................
XCALL....................... .. ......................... . ........ ..
CHAPTER 5

4-2
4-2
4-2
4-2
4-2
4-2
4-2
4-3
4-3
4-3

4-4
4-4

4-5
4-5
4-5
4-5
4-5
4-5
4-5
4-5
4-6
4-6
4-6
4-6
4-6
4-6

UNIVERSAL EXTERNAL SUBROUTINE LIBRARY

ASCII .............................. ; . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
DATE............................................................ ..
DECML .......................................................... ..
DELET.. . . .. .... . . . . . .... . .. . .. .... ... . .. . . .... . . . . . . . .. . . .. . . ... ..
ERROR..... ................. .. .......................... ........ ..
FATAL....................... ................... .......... ....... ..
FLAGS....................... ................... .......... .........
INSTR .......................................... ..... ..............
JBNO..............................................................
MONEy............................................................
PAK........ ................... ....................................
RENAM ............................................................
RSTAT.............................................................
;v

5-1
5-1
5-1
5-1
5-1
5-1
5-1

5-2
5-2
5-2
5-2
5-2
5-2

CONTENTS (Cant.)

RUNJB ......................................... .. .................
SiZE.................................................... ...... ....
TIME.......................... ........ ......... . .............. ....
TNMBR............................................................
TTSTS............. .. ........................ ..... ....... ..........
UNPAK .... .... . ......... .................... ....... ..... ...... ....
VERSN ............................................................
WAIT.. . . ................................. ........ ....... ...... ....
CHAPTER 6

6.1

FILE MIGRATION BETWEEN DIBOL SYSTEMS
TRANSFERRING FILES WITH DECNET ................................. .

6.2
TRANSFERRING FILES USING a TRANSFER MEDIUM .................... .
6.3
USING a DISKor DISKETTE as a TRANSFER MEDIUM ..................... .
6.3.1
Preparing a Transfer Medium in RT·11 Format. ........................ .
6.3.2
Preparing Files for Transfer ........................................ .
Files not Requiring Preparation for Transfer ......................... .
6.3.2.1
6.3.2.2
Files Requiring Preparation for Transfer ............................ .
Transferring the Files onto the Transfer Medium ....................... .
6.3.3
6.3.4
Transferring the Files onto the Destination System ...................... .
6.3.5

6.3.6
6.4

5-3
5-3
5-3
5-3
5·3
5·3
5·3
5·3

Converting to Proper File Format ................................... .
Transferring Files To and From a Professional System ................... .
FILE TRANSFERS BETWEEN RMS SYSTEMS ........................... .

6·1
6·1

6·3
6·3
6-4
6-4
6-4
6-5
6-6
6-6
6-6
6·7

INTRODUCTION

DIBOL is implemented on the major DIGITAL operating systems. This has brought about some minor
differences in how DIBOL statements function on those systems. To develop transportable DIBOL
applications, you must know what those differences are.

This manual explains how all the DIBOL statements and Universal External Subroutines behave on each
system and how files may be transferred between different systems.

This manual should be used with the DIBOL Language Reference Manual and the appropriate DIBOL
system user's guides for the systems which you are using.

The information in this manual applies to current and subsequent versions of DIBOL-S3 beginning with
the following implementations:
•
•
•
•

CTS-300 VS.O
RSTS/E DIBOL VS.O
VAXNMS DIBOL V2.0
Professional Tool Kit DIBOL V1.S

NOTE

When RSTS/E appears by inself it refers to RSTS/E RMS and RSTS/E OMS.

vii

CHAPTER 1
COMPILER DIRECTIVES

This chapter points out the specific ways in which DIBOL compiler options differ between systems.

DIRECTIVE

OPERATING
SYSTEM

CHARACTERISTICS

.IFDEF-.ENDC

Same as DIBOL Language Reference Manual

.IFNDEF-.ENDF

Same as DIBOL Language Reference Manual

.INCLUDE

CTS-300
RSTS/E
Professional
VMS

Same as DIBOL Language Reference Manual
Source file libraries and the VAX Common Data
Dictionary can be accessed if the program is compiled
using the NOSTANDARD qualifier.

.LlST

Same as DIBOL Language Reference Manual

.NOLIST

Same as DIBOL Language Reference Manual

.PAGE

Same as DIBOL Language Reference Manual

.TITLE

Same as DIBOL Language Reference Manual

1-1

CHAPTER 2

LANGUAGE ELEMENTS
This chapter points out the specific ways in which DIBOL language elements differ between systems. All
elements are included whether or not there are differences on the various systems.

ELEMENT

OPERATING
SYSTEM

Character
Set

CTS-300
RSTS/E
VMS
Professional

Statement Line
Syntax

Statement
Labels

CHARACTERISTICS

Same as DIBOL Language Reference Manual
The Professional uses the DEC Multinational Character
Set.

Same as DIBOL Language Reference Manual

CTS-300
RSTS/E
Professional
VMS

Same as DIBOL Language Reference Manual
Statement labels can be up to 30 characters long. This
extension is available only if the program is compiled
using the NOSTANDARD qualifier.

Array
Subscripting

Same as DIBOL Language Reference Manual

Literals

Same as DIBOL Language Reference Manual

Substrings

Same as DIBOL Language Reference Manual

Decimal
Expressions

Same as DIBOL Language Reference Manual

2-1

CHAPTER 3
OAT A DIVISION STATEMENTS
This chapter points out the specific ways in which DIBOL data division statements differ between
systems. All statements are included whether or not there are differences on the various systems.
STATEMENT

OPERATING
SYSTEM

RECORD

CTS-300
RSTS/E
Professional
VMS

COMMON

CTS-300
RSTS/E
Professional
VMS

Field
Definitions

CTS-300
RSTS/E
Professional
VMS

CHARACTERISTICS

Same as DIBOL Language Reference Manual
The following options are available with programs which
are compiled using the NOSTANDARD qualifier:
•

A named RECORD area can contain up to 65,535
characters.

•

A RECORD name can contain up to 30 characters.

Same as DIBOL Language Reference Manual
The following options are available with programs which
are compiled using the NOSTANDARD qualifier:
•

A named COMMON area can contain up to 65,535
characters.

•

A COMMON area name can contain up to 30
characters.

Same as DIBOL Language Reference Manual
The following options are available with programs which
are compiled using the NOSTANDARD qualifier:
•

Alpha fields can contain up to 65,535 characters.

•

A field name can contain up to 30 characters.

3-1

STATEMENT

OPERATING
SYSTEM

Array
Definitions

CTS-300
RSTS/E
Professional
VMS

SUBROUTINE

CTS-300
RSTS/E
Professional
VMS

3-2 Data Division Statements

CHARACTERISTICS

Same as DIBOL Language Reference Manual
The following options are available with programs which
are compiled using the NOSTANDARD qualifier:
•

Fields in alpha arrays can contain up to 65,535
characters.

•

Array names can contain up to 30 characters.

Same as DIBOL Language Reference Manual
The subroutine name can be up to 30 characters long.
This extension is available only if the program is
compiled using the NOSTANDARD qualifier.

CHAPTER 4
PROCEDURE DIVISION STATEMENTS

This chapter pOints out the specific ways in which DIBOL procedure division statements differ between
systems. All statements are included whether or not there are differences on the various systems.
STATEMENT

OPERATING
SYSTEM

Same as DIBOL Language Reference Manual

Value
Assignment
Statement
ACCEPT

CHARACTERISTICS

VMS
Professional

Same as DIBOL Language Reference Manual

CTS-300
RSTS/E DMS

Characters can be accepted from a file or terminal.

RSTS/E RMS
DMS

ACCEPT cannot be used with terminals opened in
terminal block mode.

BEGIN-END

Same as DIBOL Language Reference Manual

CALL

Same as DIBOL Language Reference Manual

CLEAR

Same as DIBOL Language Reference Manual

DELETE

Same as DIBOL Language Reference Manual

DETACH

CTS-300

Same as DIBOL Language Reference Manual

RSTS/E

Detached programs cannot open a channel to a terminal. A user or program must be privileged to use
DETACH.

VMS
Professional

DETACH is ignored.

4-1

STATEMENT

OPERATING
SYSTEM

DISPLAY

VMS
RSTS/E RMS
Professional
CTS-300
RSTS/E DMS

CHARACTERISTICS

Same as DIBOL Language Reference Manual
Characters may be displayed to a terminal or a file
opened in 0 mode.

DO-UNTIL

Same as DIBOL Language Reference Manual

FOR

Same as DIBOL Language Reference Manual

FORMS

Same as DIBOL Language Reference Manual

GO TO

Same as DIBOL Language Reference Manual

GOTO (computed)

Same as DIBOL Language Reference Manual

IF-THEN-ELSE

Same as DIBOL Language Reference Manual

INCR

Same as DIBOL Language Reference Manual

LOCASE

Same as DIBOL Language Reference Manual

LPQUE

CTS-300

LPNUM specifies the line printer number (1-4). The
default printers are selected when the spooler is started.
FORM displays the message LOAD XXXXXX IN LP at
the terminal prior to printing the file.

4-2 Procedure Division Statements

STATEMENT

OPERATING
SYSTEM

LPQUE (Cont.)

RSTS/E

CHARACTERISTICS

LPNUM line printer number is 0-7. The default is O.
FORM is not available.

VMS

LPNUM specifies the printer queue number if it is
decimal or the printer queue name if it is alpha. The
default is SYS$PRINT.
FORM specifies the number or name of the form which
must be inserted into the printer before the file is
printed. If FORM is not specified, FORM:O is assumed.
ALIGN places the file in the specified queue in a
"HOLD" status so that the operator may take whatever
action is necessary.

Professional

Requests are not queued. LPQUE prints only if the
printer is free; otherwise it generates an error.

OFFERROR

Same as DIBOL Language Reference Manual

ONERROR

Same as DIBOL Language Reference Manual

OPEN

CTS-300
RSTS/E DMS

The R submode and the RECSIZ qualifier are not
required to create relative files. Files created using 0
mode can be used for sequential or relative access. R
and RECSIZ can be used, however, if compatible syntax
between DMS and RMS is desired; they will be ignored
on DMS.
ISAM files on RSTS/E OMS use a minimum of two
channels even though only one is specified with the
OPEN statement; one channel is used for the index file
and one for a volume. Files having more than one
volume, use an additional channel for each volume, i.e.,
a file with two volumes uses three channels.
On RSTS/E if a file is opened in U mode, it cannot be
opened in I mode on another channel or in I mode by
another program.
BKTSIZ is ignored.

RSTS/E RMS
Professional

BKTSIZ range is one through 15 blocks.

Procedure Division Statements 4-3

STATEMENT

OPERATING
SYSTEM

OPEN (Cont.)

RSTS/E

CHARACTERISTICS

A program which uses an overlay structure implicitly
uses one of the 15 available channels for reading in the
overlays so only 14 channels remain available to the
DIBOL programmer.

VMS

BKTSIZ range is one through 32 blocks.
The following options are available if you compile
programs using the NOSTANDARD qualifier:

PROC-END

CTS-300
VMS
Professional

•

The number of channels available can
increased to 255.

•

Append mode (A) can be used to append to an
existing sequential file or to a print file with the P
submode (A:P).

•

Block submode (I:B,O:B,U:B) can be used to
transfer blocks of data between the file and the
program.

Same as DIBOL Language Reference Manual

RSTS/E
The buffer size should be large enough to include an entire record. For example, if a record spans two phYSical
blocks, PROC should be specified with an argument of

2.
READ (Relative file)

Same as DIBOL Language Reference Manual

READ (Indexed file)

Same as DIBOL Language Reference Manual

READS

4-4

RSTS/E RMS
VMS
Professional

Same as DIBOL Language Reference Manual

RSTS/E DMS
CTS-300

READS cannot be used with files opened in U mode.

Procedure Division Statements

STATEMENT

OPERATING
SYSTEM

CHARACTERISTICS

RECV

Same as DIBOL Language Reference Manual

RETURN

Same as DIBOL Language Reference Manual

SEND

RSTS/E
VMS
CTS-300

Same as DIBOL Language Reference Manual
A terminal number of -2 specifies that if the receiving
program is not running it must be started (detached) in
order to receive the message.
A terminal number of -3 specifies that a new copy of the
receiving program is to be started (detached) in order to
receive the message.

Professional

SLEEP

CTS-300
VMS
Professional
RSTS/E

STOP

A terminal number of -2 or -3 specifies that if the
receiving program is not running it must be started
(detached) in order to receive the message. The
receiving program must be referred to by its task name.

Same

DIBOL

Language

Reference

Manual

Entering a CTRLlC causes program execution to
resume unless digit position eight is set with the FLAGS
subroutine.

CTS-300 SUD
RSTS/E
VMS

Same as DIBOL Language Reference Manual

CTS-300 XMTSD
CTS-300 TSD

Programs cannot chain to an indirect command file.

Professional

Programs cannot chain to an indirect command file. To
chain to another program, you must use its task name.

STORE

Same as DIBOL Language Reference Manual

UNLOCK

Same as DIBOL Language Reference Manual

UPCASE

Same as DIBOL Language Reference Manual

Procedure Division Statements

4-5

STATEMENT

OPERATING
SYSTEM

CHARACTERISTICS

USING

Same as DIBOL Language Reference Manual

WHILE

Same as DIBOL Language Reference Manual

WRITE (Relative file)

Same as DIBOL Language Reference Manual

WRITE (Indexed file)

Same as DIBOL Language Reference Manual

WRITES

XCALL

RSTS/E RMS
VMS
Professional

Same as DIBOL Language Reference Manual

CTS-300
RSTS/E DMS

WRITES is not permitted with files opened in U mode.

CTS-300
RSTS/E
Professional

Same as DIBOL Language Reference Manual

VMS

4-6

Procedure Division Statement

The following options are available with programs which
are compiled using the NOSTANDARD qualifier:
•

Decimal expressions can be used as subroutine
arguments.

•

%VAL, %REF, %DESCR, and %XTRNL are provided to facilitate calling non-DIBOL routines.

•

The subroutine name can be up to 30 characters
long.

CHAPTER 5
UNIVERSAL EXTERNAL SUBROUTINE LIBRARY

This chapter pOints out the specific ways in which DIBOL subroutines from the Universal External
Subroutine Library differ between systems. All subroutines are included whether or not there are
differences on the various systems.

SUBROUTINE

OPERATING
SYSTEM

CHARACTERISTICS

ASCII

Same as DIBOL Language Reference Manual

DATE

Same as DIBOL Language Reference Manual

DECML

Same as DIBOL Language Reference Manual

DELET

VMS
Professional
RSTS/E

Same as DIBOL Language Reference Manual

CTS-300

The channel number is required.

ERROR

Same as DIBOL Language Reference Manual

FATAL

Same as DIBOL Language Reference Manual

FLAGS

CTS-300

Same as DIBOL Language Reference Manual

RSTS/E RMS
Professional

When flag 6 is set it disables implicit carriage control.

RSTS/E

FLAGS cannot be used with terminals opened in
terminal block mode.

VMS

Flag 6 is ignored.
Flag 4 can be used to override the NOSCOPE terminal
setting but cannot be used to override the SCOPE
terminal setting.

5-1

SUBROUTINE

OPERATING
SYSTEM

CHARACTERISTIC

INSTR

Same as OIBOL Language Reference Manual

JBNO

Same as OIBOL Language Reference Manual

MONEY

Same as OIBOL Language Reference Manual

PAK

RSTS/E RMS
VMS
Professional
Same as OIBOL Language Reference Manual
CTS-300
RSTS/E OMS

Key fields in ISAM Files should not be packed.
NOTE

CTS-300 and RSTS/E OMS packed
data format differs from that used by
RSTS/E RMS, VMS, and the
Professional.

RENAM

RSTAT

VMS
Professional
RSTS/E

The new file and the old file must be in the same account
and have the same protection code.

CTS-300

The channel number is required.

CTS-300
RSTS/E OMS

RSTS/E

VMS
Professional
RSTS/E RMS

5-2

Same as OIBOL Language Reference Manual

Procedure Division Statements

For indexed files the terminator is the null character. For
all other cases it may be ESC, LF, FF, or VT.
A terminal opened in terminal block mode is a special
case. Check the RSTS/E OIBOL System User's Guide.

For files, the terminator is the null character. For a
terminal, the terminator may be ESC, LF, FF, or VT.

SUBROUTINE

OPERATING
SYSTEM

RUNJB

CTS-300
RSTS/E
VMS
Professional

CHARACTERISTICS

Same as DIBOL Language Reference Manual
A second argument of -2 specifies a back - ground task
provided no other task by the same name is running.
The filespec argument must be a task name.

SIZE

Same as DIBOL Language Reference Manual

TIME

Same as DIBOL Language Reference Manual

TNMBR

Same as DIBOL Language Reference Manual

TTSTS

CTS-300

The channel number is allowed but is ignored.

RSTS/E
Professional

The channel number is required.

RSTS/E

TTSTS cannot be used with terminals opened in
terminal block mode.

VMS

DIBOL generates a Line Feed when a Carriage Return is
entered. TTSTS can detect the Line Feed only if the
channel number is supplied.
TTSTS returns the number of characters pending. If the
field is not large enough to hold the number, the largest
number the field will hold is returned.

UNPAK

Same as DIBOL Language Reference Manual
NOTE

CTS-300 and RSTS/E DMS
packed data format differs from
that used by RSTS/E RMS,
VMS, and the Professional.
VERSN
WAIT

Same as DIBOL Language Reference Manual
VMS

Same as DIBOL Language Reference Manual

CTS-300
RSTS/E

Digit 3 means the same as digit 2.

Professional

Not implemented

Procedure Division Statements

5-3

CHAPTER 6
FILE MIGRATION BETWEEN DIBOL SYSTEMS

This chapter explains the process necessary to move DIBOL source and data files from one system to
another. There are two ways that you can transfer files: using DECnet and using a transfer medium.

6.1

TRANSFERRING FILES WITH DECnet

DECnet is a system network program which allows different DIGITAL computer systems to be joined
together into a network of systems.

One of DECnet's capabilities is file transfer. If the systems between which you want to transfer files are
linked with DECnet, then using DECnet is the recommended way to transfer files because it is a much
simpler process than using media. Consult your system documentation for using DECnet.

If you are transferring DMS indexed files to an RMS system using DECnet, you must do the following:
•

Convert the DMS indexed files to sequential format before transferring them. Consult section
6.3.2 for information.

•

Transfer the files with DEC net.

•

After they are transferred with DECnet you can convert them back to an RMS indexed format if
you wish; consult section 6.3.5 for information.

If you are transferring RMS relative or indexed files to a DMS system you must do the following:

6.2

•

Convert the files to a sequential format. Consult section 6.3.2 for information.

•

Transfer the files with DECnet.

•

Once files are transferred, no further processing is necessary for relative access files. Those
files to be used for indexed access must be converted using the DMS utility, ISMUTL. Consult
either the CTS-300 System User's Guide or the RSTSIE DIBOL System User's Guide for
information on using ISMUTL.

TRANSFERRING FILES USING A TRANSFER MEDIUM

If DECnet is not available on your system, you must use a transfer medium. The term transfer medium is
used in this chapter to refer to removable storage media such as disks, diskettes, or magtape.

6-1

This chapter recommends two methods. The preferred method uses disks or diskettes and is explained
in section 6.3. If, however, you want to transfer files between systems using RMS, and both systems have
a magtape drive, you may want to consider the method suggested in section 6.4.

This chapter is concerned with the transfer process only and refers to sources of specific information on
the different system file transfer utilities or commands where that information is required.

The systems considered in this chapter are:
1.

CTS-300 on the RT-11 operating system

RSTS/E

RSX-11 M and RSX-11 M-PLUS

NOTE

DIBOL is not implemented on these RSX systems,
but they can serve as host systems to a Professional
system which does implement DIBOL. The
information in this manual applies to both RSX
systems; therefore remaining references will be to
RSX in general.
4.

VAXNMS

The Professional 300 Series

This chapter refers to commands and utilities which you will use as tools to transfer files. For information
on those tools see the following documents:

6-2

•

For RT-11 see the RT-11 System User's Guide

•

For RSTS/E see the RSTS/E System User's Guide

•

For RSX see the Utilities Manual

•

For VMS see the VAX-11 Utilities Reference Manual

•

For RMS on RSTS/E or RSX see the RMS User's Guide.

•

For RMS on VMS see the VAX-11 Record Management Services Utilities Reference Manual

•

For CTS-300 see the CTS-300 System User's Guide

•

For DMS DIBOL on RSTS/E see the RSTS/E DIBOL System User's Guide

File Migration Between DIBOL Systems

6.3

USING A DISK or DISKETTE as a TRANSFER MEDIUM

The method explained in this section is recommended, because it works on all systems implementing
DIBOL. There are other methods and media which you can use, but the process is system or media
dependent. After some experience with transferring files, you may find a more convenient way which
works for your system.

The general process is as follows:

6.3.1

•

Prepare a transfer medium in RT-11 format

•

Prepare the files for transfer

•

Transfer the files onto the transfer medium

•

Transfer the files onto the destination system

•

Convert to the proper file format

Preparing a Transfer Medium in RT-11 Format

This method requires a transfer medium in RT-11 format. All DIBOL systems either read RT-11 format
directly or have file transfer utilities which support RT-11 format.

Figure 6-1 illustrates the relationship between the systems:

CTS-300
(RT-11)

~RT.ll FORMATTE~

RSTS/E

MEDIU~

RSX/

/VAXNMS

~ROFESSIONAL./
Figure 6-1

File Migration Between Dibol Systems

6-3

If you use a new transfer medium, it must be initialized and put into RT-11 format. To prepare a transfer
medium in RT-11 format you must use one of the following tools:
•

On RT-11 use the INITIALIZE command

•

On RSTS/E use the FIT utility

•

On RSX use the FLX utility

•

On VMS use the FLX utility

If you already have a transfer medium in RT-11 format, it does not have to be initialized; it can be used as
it is.
6.3.2

Preparing Files for Transfer

RT-11 supports only a sequential file format, so all files which are transferred onto an RT-11 formatted
medium must be in a sequential format.
6.3.2.1 Files Not Requiring Preparation for Transfer - Files in sequential format do not require any
preparation. Each of the following cases are files already in sequential format:
•

On RT-11 and RSTS/E OMS, sequential and relative files (these files have the same structure
but are accessed differently)

•

On RMS systems, sequentially formatted files

•

OIBOL source code files

If your files are already in sequential format, proceed to section 6.3.3.
6.3.2.2 Files Requiring Preparation for Transfer - Files not in sequential format must be converted
to sequential format before being transferred. Each of the following cases are files not in sequential
format which must be converted:
•

OMS ISAM files on CTS-300 and RSTS/E
To convert these files to sequential format, write a OIBOL program which opens a new
sequential file for output, reads records from the ISAM file, and writes them into the new
sequential file.

•

RMS relative and indexed files on RSTS/E or RSX
To convert either of these file types to sequential format use the following procedure:
1. Use the RMS Convert utility (CNV) to write the contents of the non-sequential file into a
new sequential file.
With this utility the file being converted will be the input file and CNV will create a new
sequential file using the name you specify for output and containing the records from the
relative or indexed input file.

6-4

File Migration Between DIBOL Systems

2. The sequential file is ready for transfer.
•

RMS relative and indexed Files on VMS
To convert either of these file types to sequential format use the following procedure:
1. Use the VMS EDIT utility with the IFDL qualifier to create an FDL file to describe the
characteristics of a sequential file that you will create in step 2.
You may need to consult the VAX-11 Record Management Services Utilities Reference
Manual concerning the File Definition Language to see how to define a sequential file.
2. Use the VMS CONVERT utility with the IFDL qualifier to write the contents of the nonsequential file into a new sequential file that you described in the EDIT/FDL session in
step 1.
For example, if you created the file SEQUEN.FDL in step 1 to describe the sequential file
for transfer and you were converting an indexed file named CUSDAT.IDX, your
command to the convert utility might be as follows:
CONVERT/FDLSEQUEN.FDL CUSDAT.IDX CUSDAT.SEQ
This command would create a new sequential file CUSDAT.SEQ according to the
specifications in SEQUEN.FDL and would write the records from CUSDAT.IDX into
CUSDAT.SEQ.
3. The sequential file is ready for transfer.

6.3.3 Transferring the Files onto the Transfer Medium
Once files are in sequential format they can be transferred. You must mount the transfer medium on your
system and transfer the files onto it. Use one of the following procedures:

NOTE

On VMS and RSX-11 M PLUS you must use the
IFOREIGN qualifier when you mount the RT-11
formatted medium.

•

On RT-11, transfer the files onto the transfer medium with the RT-11 COpy command.

•

On RSTS/E, transfer the files onto the transfer medium with the FIT file transfer utility.

•

On RSX and VMS, transfer the files onto the transfer medium with the FLX file transfer utility.

When this procedure is complete you can move the transfer medium to the destination system.

File Migration Between DIBOL Systems

6-5

6.3.4

Transferring the Files onto the Destination System

On the destination system mount the transfer medium and transfer the files onto that system.
•

On RT-11, transfer the files from the transfer medium onto the RT-11 system with the RT-11
COpy command.

•

On RSTS/E, transfer the files from the transfer medium onto the RSTS/E system with the FIT
file transfer utility.

•

On RSX and VMS, transfer the files from the transfer medium onto the RSX or VMS system
with the FLX file transfer utility.

6.3.5 Converting to Proper File Format
If the files are to remain in sequential format, the transfer process is complete. If the files were originally
in relative or indexed format they can be converted back to that format with one of the following
procedures:
•

On CTS-300 and RSTS/E-DMS, files to be accessed relatively don't require further
processing.
On either of these systems, you can convert files that were originally in indexed format back to
indexed format using the utility ISMUTL.

•

On RSTS/E RMS, RSX, or VMS you can convert files back to their original format by using the
RMS, DEF and CNV utilities.
On RSTS/E RMS and RSX, use the RMS Define utility (DEF) to create a file in the format that
you want and then use the RMS Convert Utility (CNV) to write the records from the transferred
file into the new file in the proper format. You may need to use the TR and PD switches with
the DEF utility.
On VMS, use the EDIT/FDL utility to create the file describing the file format that you want and
then use the CONVERT utility to convert the transferred file into the new file in the proper
format.

6.3.6

Transferring Files to and from a Professional System

Because the Professional must be connected to either a VAXNMS or RSX host system, a Professional
system is a special case. DIBOL file transfers to a Professional system must first go to the host system.

For file transfers involving a Professional system use the following procedure:
•

Determine which type of host system is involved.

•

Transfer the files to the host system.

•

When the files are on the host system, transfer them to the Professional itself.

6-6 File Migration Between DIBOL Systems

For example, assume that you want to transfer DIBOL files from a RSTS/E system to a Professional
system linked to a VAX/VMS host. First treat the procedure as a transfer from RSTS/E to VAX/VMS.
When the transfer to VAXIVMS is complete, transfer the files from the VAXIVMS system to the
Professional.

To transfer files from the Professional to another system, reverse the procedure. Transfer the files from
the Professional to the host system and then follow the file transfer procedure for transferring files
between the host system and whatever system is to receive the files.

For information on transferring files between the Professional and its host system, consult your
Professional system documentation.

6.4

FILE TRANSFERS BETWEEN RMS SYSTEMS

If you are transferring between systems which both have RMS and each system has a magtape drive you
can make a direct transfer between those systems without needing to convert RMS relative or indexed
files to sequential format.

You can do this type of transfer with the following procedure:
•

Prepare the magtape to receive the files.

•

Run the RMS Backup utility to transfer the files from the original system onto the tape.

•

Move the magtape to the destination system and transfer the files from the magtape onto the
destination system using the RMS Restore utility.

File Migration Between DIBOL Systems 6-7

DIBOL-83 Compatibility Guide
AA-V810A-TK
May 1983

READER'S COMMENTS
NOTE:

This form is for document comments only. DIGITAL will
use comments submitted on this form at the company's
discretion. Problems with software should be reported
on a Software Performance Report (SPR) form. If you
require a written reply and are eligible to receive
one under SPR service, submit your comments on an SPR
form.

Did you find errors in this manual?

•

c::
I::
I.!!

If so, specify by page.

Did you find this manual understandable, usable, and well-organized?
Please make suggestions for improvement.

1£
I~

1..2
1°

...

IeIii:
10)

I
I
I
I
I
I
I
I
I
I
I
I
I

Is there sufficient documentation on associated system programs
required for use of the software described in this manual? If not,
what material is missing and where should it be placed?

Please indicate the type of user/reader that you most nearly represent.

o Assembly language programmer

o Higher-level language programmer
o Occasional programmer (experienced)
o User with little programming experience

o Student programmer
o Non-programmer interested in computer concepts and capabilities

Name ________________________________________ Date _________________________
Organization ______________________________________________________________
Street __________________________________________________________________
City _________________________ State ____________ Zip Code _____________
or
Country

I
- - - -

-Do Not Tear - Fold Here and Tape -

----1

- - - - -

IIIIII

~amaama

No Postage
Necessary
if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO.33 MAYNARD MASS.
POSTAGE WILL BE PAID BY ADDRESSEE

DIGITAL EQUIPMENT CORPORATION
Applied Commercial Engineering MK1-2/H32
Continental Boulevard
Merrimack N.H. 03054

ATTN: Documentation Supervisor

Do Not Tear - Fold Here and Tape -

-,
I
I