_ U.S. Environmental Protection Agency .
55 ^^ji£i$&1 § Office of Administration and Resources Management
% «fe^!^^ ^ Office ot Information Resources Management
Washington, D.C. 20460
N FOR MAT! ON
RESOURCES
ANAGEMENT
DIRECTIVES
VOLUME 2:
NCC-IBM User's Guide
NCC-VAX User's Guide
LAN Technical Guidlines
-------
UNITED STATES ENVIRONMENTAL PROTECTION AGENCY
Research Triangle Park. NC 27711
March 1, 1988
OFFICE OF
ADMINISTRATION
AND RESOURCES
MANAGEMENT
Attached is your copy of the newest version of the NCC VAX User's
Guide* Please remember to discard any previous versions you may
have. This manual contains new or updated information on many
topics, including:
* File archiving and recovery
* NCC training courses
* On-line documentation
* TAPESYS
* Usage charges
* VAX/IBM file transfer
This manual is being provided to all authorized VAX Cluster users.
For further information or additional copies, please contact User
Support at (919) 541-7862, FTS 629-7862 or 1-800-334-2405.
-------
United States Office of Administration 201/001E
Environmental Protection and Resources Management
Agency National Data Processing Division
Research Triangle Park. NC 27711
SEPA IMCC-VAX
User's Guide
-------
NCC-VAX USER'S GUIDE
February 17, 1988
Prepared by:
VAX User Support
Contract No. 68-01-7437
U.S. ENVIRONMENTAL PROTECTION AGENCY
NATIONAL DATA PROCESSING DIVISION
P.O. BOX 123U
RESEARCH TRIANGLE PARK, NORTH CAROLINA 277U9
-------
Preface
The NCC-VAX User's Guide provides the user with information
about the National Computer Center (NCC), Its procedures,
available resources, and operations. This information is
current as of the date given on the previous page.
As the NCC-VAX service expands, this guide will be updated
periodically to cover changes and additions.
11
-------
Table of Contents
Preface. . • • • « . . . . . ( • « 11
1.0 INTRODUCTION 1-1
1.1 PURPOSE AND SCOPE ; 1-1
1.2 USING THE GUIDE 1-1
1.2.1 Numbering Systems ........ 1-1
1.2.2 Command Format ......... 1-1
1.2.3 Manual Maintenance ........ 1-2
1.2.4 Manual Distribution ........ 1-2
2.0 GENERAL FACILITIES AND SERVICES 2-1
2.1 ORGANIZATION AND MANAGEMENT 2-1
2.2 VAX STANDARD CONFIGURATION 2-1
2.2.1 Standard VAX Hardware Configuration ..... 2-1
2.2.2 Standard VAX Software Configuration 2-3
2.3 TELECOMMUNICATIONS ACCESS 2-3
2.3.1 Interactive Access ........ 2-3
2.3.2 Dial-Up Procedure ........ 2-3
2.3.3 Ethernet Access ......... 2-4
2.3.4 Setting Terminal Characteristics ..... 2-5
2.3.5 Common Terminal Problems ....... 2-5
2.4 SERVICES TO USERS 2-6
2.4.1 Business Hours ......... 2-6
2.4.2 User Information Services ....... 2-7
2.4.2.1 Availability of Manuals 2-7
2.4.2.2 On-Line Help Function ..... 2-7
2.4.2.3 On-Line Documentation System .... 2-7
2.4.2.4 EPA-NCC User Memos 2-7
2.4.3 Consultation, Assistance, and Training .... 2-8
2.4.3.1 Telecommunications Assistance .... 2-8
2.4.3.2 User Support Services ..... 2-8
2.4.3.3 NCC Centralized Problem Management System . 2-8
2.4.3.4 Classroom Training ...... 2-9
2.4.3.5 On-Line Training 2-12
ill
-------
2.4.4 Data Processing Support Services (DPSS) .... 2-12
2.4.4.1 Tape Library ....... 2-12
2.4.4.2 I/O Control 2-12
2.4.4.3 Printout Distribution ..... 2-12
2.4.4.4 Auxiliary Services ...... 2-13
3.0 MANAGEMENT OF NCC-VAX SYSTEM RESOURCES 3-1
3.1 SITE POLICY AND SYSTEM AVAILABILITY 3-1
3.2 REGISTRATION PROCEDURES 3-1
3.3 RESOURCE MANAGEMENT 3-2
3.3.1 Disk Space Management. ....... 3-2
3.3.1.1 Quotas ........ 3-2
3.3.1.2 File Archiving 3-2
3.3.1.3 Standby Archiving 3-3
3.3.2 Disk Backup and Recovery ....... 3-4
3.3.2.1 Disk Backup Schedule ..... 3-4
3.3.2.2 File Recovery Procedure ..... 3-4
3.3.3 Security .......... 3-6
3.3.3.1 Terminal Access ...... 3-6
3.3.3.2 Computer Room ....... 3-6
3.3.3.3 Physical Security ...... 3-6
3.3.4 Tape Management ......... 3-6
3.3.4.1 Tape Assignment ...... 3-6
3.3.4.2 Tape Management System ..... 3-7
3.3.4.3 Foreign Tapes ....... 3-7
3.3.4.4 Alien Tapes ....... 3-8
3.3.4.5 Tape Maintenance and Disposition . . . 3-8
3.4 ACCOUNTING 3-10
3.4.1 System Usage and Chargeback ...... 3-10
3.4.1.1 CPU Chargeback 3-11
3.4.1.2 Computer-Related Charges ..... 3-11
3.4.1.3 Access Charges 3-11
3.4.1.4 Usage Charges 3-12
3.4.2 Refunds ...»•••••• 3-13
3.5 PRODUCTION CONTROL SERVICES 3-13
iv
-------
4.0 VAX/VMS OVERVIEW 4-1
4.1 SYSTEM ACCESS 4-1
4.1.1 Logging In.......... 4-1
4.1.2 Logging Out ......... 4-1
4.1.3 Interactive CPU Limit 4-2
4.2 DISK STRUCTURE AND FILE SPECIFICATIONS 4-2
4.2.1 Disk Structure and Directories ...... 4-2
4.2.2 Creating Subdirectories ....... 4-3
4.2.3 File Specifications ........ 4-3
4.3 CHANGING DEFAULT DISK OR DIRECTORY 4-4
4.4 CHANGING PASSWORDS 4-4
4.5 PRINTING FILES 4-5
4.5.1 System Printer ......... 4-5
4.5.2 Laser Printers ......... 4-6
4.6 TRUNCATING COMMANDS 4-6
4.7 VOLUME AND FILE SECURITY 4-7
4.7.1 Disk Directory and File Protection ..... 4-8
4.7.2 Tape Protection ......... 4-fa
4.8 MOUNT COMMAND 4-8
4.8.1 Mounting Disks ......... 4-9
4.8.2 Allocating Tape Drives ....... 4-9
4.8.3 Mounting Tapes ......... 4-9
4.9 LOGICAL NAMES 4-10
4.9.1 Logical Name Tables ....... .4-10
4.9.2 Logical Name Displays ...... .4-11
4.9.3 Logical Name Translation ...... .4-11
4.9.4 Concealed Device Names ...... .4-11
4.9.5 Default Logical Names ...... .4-11
5.0 VAX/VMS UTILITIES 5-1
5.1 TEXT EDITORS 5-1
5.1.1 EOT ........... 5-1
5.1.1.1 Calling EDT 5-1
5.1.1.2 EDT Recovery Features ..... 5-1
5.1.1.3 Entering Commands ...... 5-2
-------
5.1.2 EVE «•««««•«««« j—3
5.1.2.1 Accessing EVE 5-3
5.1.2.2 Terminating EVE 5-3
5.1.2.3 Getting Help 5-3
5.1.2.4 EVE Recovery Feature ..... 5-3
5.1.2.5 Entering Commands ...... 5-4
5.1.2.6 Multiple File Editing 5-6
5.1.2.7 Using DCL with EVE 5-6
5.2 MAIL UTILITY 5-7
5.2.1 MAIL Command ......... 5-7
5.2.2 Sending a MAIL Message ....... 5-7
5.2.3 Reading Your MAIL Messages 5-8
5.3 PHONE 5-9
5.3.1 PHONE Command ......... 5-9
5.3.2 Creating a PHONE Conversation ...... 5-9
5.4 TAPESYS TAPE MANACE11ENT SYSTEM 5-10
5.4.1 VAX Tape Label Policy 5-11
5.4.2 Allocating a Tape from Scratch ...... 5-12
5.4.3 Freeing a Tape Back to Scratch ...... 5-12
5.4.4 Inquiring about Tapes ....... 5-12
5.4.5 TAPESYS Automated Backup and Restore Functions . . 5-13
5.4.6 Using Backup and Restore Commands ..... 5-14
5.4.7 Interactive Tape Use ........ 5-14
5.4.8 Summary of TAPESYS Functions ...... 5-16
5.4.9 Help ........... 5-16
5.5 BACKUP UTILITY 5-16
5.5.1 BACKUP Qualifiers 5-17
5.5.2 BACKUP Utility Examples 5-1 b
5.6 LIBRARIAN UTILITY 5-18
5.6.1 Creating and Maintaining Libraries ..... 5-19
5.6.2 LIBRARIAN Routines 5-20
5.7 DIGITAL STANDARD RUNOFF (DSR) 5-20
5.8 DIFFERENCES 5~20
5.8.1 DIFFERENCES Command 5-21
5.8.2 Examples .......... 5-21
vi
-------
5.9 SORT 5-22
6.0
6.1
6.2
6.3
7.0
7.1
7.2
7.3
7.4
8.0
6.1
8.2
8.3
6.4
8.5
9.0
9.1
9.2
5.9.1 SORT Command ........
5.9.2 Examples .........
PROGRAMMING LANGUAGES
VAX-11 FORTRAN ;
VAX-11 MACRO ASSEMBLY LANGUAGE . . . ...
VAX-11 SYMBOLIC DEBUGGER
6.3.1 Calling the Debugger .......
6.3.2 Debugger Commands .......
APPLICATION PACKAGES
STATISTICAL ANALYSIS SYSTEM (SAS)
FOCUS. ...........
TEKTRONIX LIBRARY
INTERNATIONAL MATHEMATICAL AND STATISTICAL LIBRARY (1MSL)
COMMUNICATION PACKAGES
KLRMIT— 32 ...........
CROSSTALK ...........
8.2.1 Crosstalk Command Files ......
8.2.2 Running Crosstalk .......
HASP+ ••••««••»«•
DECNET ...........
8. A.I Displaying the Network ......
6.4.2 Logging on to a Remote Node .....
8.4.3 Using DCL Commands over the Network ....
SNA .•••••«•••••
8.5.1 Logging on to IBM Systems through DECnet/SNA .
8.5.2 Emulating a 3270 Terminal ......
8.5.3 Submitting Batch Jobs to the IBM 390. ...
SUBMITTING BATCH JOBS
BATCH QUEUE POLICY
SUBMIT COMMAND
. 5-23
. 5-23
. 6-1
. 6-1
. 6-1
. 6-1
. 6-2
. 6-3
. 7-1
. 7-1
. 7-2
. 7-2
. 7-3
. 8-1
. 8-1
. 8-2
. 8-2
. 8-3
. b-5
. 8-7
. 8-7
. 8-8
. fc-b
. 8-9
. 8-9
. 8-10
. 8-10
. 9-1
. 9-1
. 9-2
vii
-------
Appendix A: Telephone Numbers ......... A-l
Appendix B: Sample Forms .......... B-l
Appendix C: Digital Control Language (DCL) C-l
Appendix D: Telecommunications: Diagnosing and Reporting Problems . D-l
Appendix E: HELP Files .......... E-l
Appendix F: VAX Supported Software ........ F-l
Appendix G: Registration Procedures ........ G-l
Appendix H: Moving a SAS Data Set from the VAX to the IBM . . . H-l
Appendix I: Procedure for Transferring a File from the VAX Cluster
to the IBM 3090 System 1-1
Appendix J: Procedure for Transferring a File from the IBM 3090 System
to the VAX Cluster ......... J-l
Appendix K: Plotting with the CalComp 1051 Plotter on the
NCC-VAX Cluster K-l
Appendix L: Alphabetic Listing of Common DCL Commands .... L-l
List of Illustrations
Figure Title Page
2-1 NCC-VAX Cluster 2-2
4-1 Disk Structure 4-2
5-1 Keypad Editing Keys 5-2
5-2 Editing Keys on the VT100 and VT220 Terminals 5-5
5-3 PHONE Screen Display 5-10
5-4 TAPESYS V4.2 Backup Screen 5-13
5-5 TAPESYS V4.2 Restore Screen 5-13
8-1 Mapping of VT100 Keypad Application Mode Functions 8-4
8-2 Arrow Keys and Equivalent Crosstalk Keys 8-5
8-3 3270 TE Keyboard Highlighting the 3270 Keys 8-10
Table
2-1 Hours of Operation 2-6
viii
-------
NCC-VAX USER'S GUIDE
1.0 INTRODUCTION
This document provides Introductory as well as technical information for
users of the VAX Cluster at the EPA National Computer Center (NCC). Sections
1.0 through 3.0 contain general information required by all users. Sections
4.0 through 9.0 provide technical Information concerning the available soft-
ware packages for the VAX system. The appendixes contain Information which
changes frequently.
1.1 PURPOSE AND SCOPE
This manual Is a useful source of general Information concerning the NCC, its
procedures, available resources, operations, and supported software. Much of
this information is explained in greater detail in various VAX manuals from
Digital Equipment Corporation (DEC). Extensive references to these manuals
have been included, and the user can obtain copies for referencing (see
Section 2.4.2.1).
Since this manual Is intended primarily for NCC-VAX Cluster users, the NCC
welcomes any suggestions, comments, or contributions from the user community
which would Improve the usefulness of the manual. Appendix B contains a
Readers' Commentary form.
1.2 USING THE GUIDE
1.2.1 Numbering Systems
Pages within the Guide are numbered by section, followed by the page number
within the section (e.g., 3-5). Sections are numbered according to the
decimal system. For example, Section 2.0 is divided into Subsections 2.1,
2.2, etc.; and Section 2.2 Is further divided into Subsections 2.2.1, 2.2.2,
etc. This manual limits the numbering system to four digits (e.g., Section
2.3.2.2).
Table and figure numbers follow the format n-a (e.g., Figure 5-1). The first
number is the section number; the second number Is the number of the figure
or table within that section.
1.2.2 Command Format
VAX commands are printed in uppercase letters. The portion of commands
contributed by users (e.g., filenames) are in lower case. Included is the $
prompt, which is the VAX equivalent to READY.
1-1
-------
1*2.3 Manual Maintenance
Maintenance of this Guide is the responsibility of VAX User Support. All
questions or suggestions regarding the manual should be submitted to the User
Contact Center at the NCC. Appendix A contains appropriate addresses and
telephone numbers.
1.2.4 Manual Distribution
The NCC-VAX User's Guide will be supplied upon request by VAX User Support at
NCC, or one nay be obtained by calling the User Contact Center (see Appendix A
for telephone number). New users are automatically sent a copy when their ID
is established, and all registered users are provided with updated versions
when they become available.
1-2
-------
2.0 GENERAL FACILITIES AND SERVICES
2.1 ORGANIZATION AND MANAGEMENT
The NCC is one of the largest, most modern, high-speed computer centers in
the nation. Its mission is to support the Environmental Protection Agency in
scientific and administrative applications. It serves EPA offices In
Washington, D.C. (Headquarters), regional offices, and laboratories throughout
the U.S. Services are also provided to other government agencies and contractors,
The NCC consists of certain physical facilities, hardware, and software which
constitute the central computer system. A communications network allows
distribution of computer services to remote locations. The NCC also provides
user support services to its users.
The NCC is located within the EPA Environmental Research Center at Research
Triangle Park (RTP), North Carolina. The RTP is situated within the geograph-
ical triangle formed by North Carolina State University, Duke University, and
the University of North Carolina at Chapel Hill. The NCC occupies approxi-
mately 46,000 square feet within the Environmental Research Center.
The NCC operates three principal data processing facilities: an IBM-compat-
ible configuration, a SPERRY-compatible configuration, and a DEC-compatible
configuration. Management of the systems is organizationally structured under
the National Computer Center within the Office of Administration and Resources
Management. The NCC, managed by the National Data Processing Division, is
responsible for managing the computer hardware, software, telecommunications
network, and support services for the three major EPA hardware systems.
2.2 VAX STANDARD CONFIGURATION
The VAX Cluster consists of timesharing VAX machines available to the EPA
scientific user community. See the NCC-VAX Cluster diagram in Figure 2-1.
2.2.1 Standard VAX Hardware Configuration
The standard VAX hardware configuration follows:
o Central Processing Unit (CPU)
o Console
o Unibus Expansion Cabinet
o Disk Drives
o Tape Drives
o Printer
o Terminal
2-1
-------
K)
K>
ETHERNET
TIMESHARE
VAX 6600
(VAXTM1)
NCC-VAX CLUSTER
STAR
COUPLER
MODELING
VAX 11/765
(NCCORD)
SPERRY
1100/80
• LP-26 I
SOFTWARE
VMS
FORTRAN
SAS
SAS6RAPH
OECNET
OECNET/SNA
KERMIT
HASP
FOCUS
1MSL
TAPESVS
Figure 2-1. NCC-VAX Cluster
-------
2.2.2 Standard VAX Software Configuration
The standard VAX software configuration follows:
o VMS o SAS
o FORTRAN o SASGRAPH
o DECnet/SNA Gateway o Selected DECUS Utilities
o HASP o FOCUS •
o KERMIT o IMSL
o TAPESYS
2.3 TELECOMMUNICATIONS ACCESS
2.3.1 Interactive Access
Users can gain access to the NCC-VAX Cluster in one of the following ways:
a. Dialing one of the access telephone numbers listed in Appendix A.
b. Dialing one of their local TYMNET telephone numbers (obtained from
Telecommunications Support—see Appendix A for their telephone number).
The user should then select 'EPA1' as the Site-ID for 1200 baud
or 'EPA2f for 2400 baud.
2.3.2 Dial-Up Procedure
Various types of modems are used to gain access to the VAX system. Refer to
the manual for your particular type of modem for specific Instructions.
General characteristics for access through a modem are as follows:
a. Terminal speed should be set to 300, 1200, or 2400 baud, depending
on modem.
b. Dial the correct phone number by keying in the numbers (modem) or
by using the telephone (acoustic coupler).
c. A high-pitched, steady tone is heard if the connection is successful.
d. Hit . Welcome messages appear with a menu listing systems
available. The ENTER SELECTION: prompt requires that 'VAX1 be typed
in. It may not echo on the screen, depending on the modem used.
Refer to Section 4.1 for information on how to log in after communications have
been established.
2-3
-------
2.3.3 Ethernet Access
Some users access the VAX through the Ethernet network. The following
summarizes the commands you may Issue at the DECserver 200 Terminal Server
LOCAL prompt:
o HELP TUTORIAL - quick guide on using a terminal server.
o SHOW SERVICES - displays all available services on the network.
o SHOW PORT - displays Information about your port setup.
o SHOW SESSIONS - displays all active sessions.
o SHOW USERS - shows all users logged on to your terminal server.
o SET BREAK REMOTE - allows your terminal to send characters to
the remote system.
o SET BREAK LOCAL - causes the character to return you to the
terminal server command prompt.
o SET LOCAL SWITCH [character] - sets a character which, when pressed,
returns you to the terminal server command prompt.
o SET FORWARD SWITCH [character] - sets a character which, when pressed,
connects you to your next seq-i^anlally numbered session.
o Sr,T BACKWARD SWITCH [character] - sets a character which, when pressed,
connects you to the previously numbered session.
o SET SESSION PASSALL - sets terminal server to pass binary data; useful
for file transfer.
o CONNECT VAX - connects you to the VAX 8600 timesharing system.
o CONNECT MODEL - connects you to the VAX 11/785 modeling machine.
o CONNECT PSU - connects you to the port selector
o CONNECT PSUBIN - connects you to the port selector in transparent mode.
o DISCONNECT SESSION n - terminates an active session.
o LOCK - locks your terminal server port with a password that you
supply. This password must be reentered to unlock the port.
o LOGOUT - logs out your terminal off the server and disconnects any
active sessions.
2-4
-------
2.3.4 Setting Terminal Characteristics
Each VAX installation, including the VAX Cluster, establishes default para-
meters for its terminals. The SHOW TERMINAL command displays the parameters
of your terminal. You can change the characteristics of the terminal with
the SET TERMINAL command. For example,
SSET TERMINAL/PAGE-n
specifies the page length (in lines) of the terminal. Values of 0 through 255
can be specified.
SSET TERMINAL/NOBROADCAST
Choose this parameter when you do not want output Interrupted by MAIL or
REPLY messages, or when you are using a terminal as a noninteractive terminal.
$SET TERMINAL/DEVICEJTYPE-terminal type
designates the terminal type. Refer to the VAX/VMS DCL Dictionary for Infor-
mation on the SET TERMINAL command and the terminal parameters.
Refer to Appendix C of this manual for a list of terminal special function
keys and control keys.
2.3.5 Common Terminal Problems
Following is a list of common terminal problems and their solutions. Refer
to Appendix D for a discussion on diagnosing and reporting problems. If a
terminal problem cannot be solved by using these two sources, call the User
Contact Center (see Appendix A for telephone number).
a. POWER LIGHT NOT ON
Terminal or modem not turned on.
Fuse blown in terminal.
Terminal not plugged in.
b. BUSY SIGNAL
All lines on the rotor are busy. Try again later.
c. HIGH-PITCHED TONE BUT TERMINAL DOES NOT RESPOND
Forgot to press CARRIAGE RETURN.
Terminal is in local mode.
Terminal is not connected to modem.
Noise on the telephone line caused a false recognition.
LA36 terminal paper Is jammed or has run out.
2-5
-------
d. TERMINAL PRINTS GARBAGE AFTER CARRIAGE RETURN
RETURN was not pressed.
Speed of terminal or computer set incorrectly.
Call the User Contact Center.
e. TWO OF EACH CHARACTER
Terminal and/or modem is switched to HALF DUPLEX mode.
f. TERMINAL WENT DEAD
Your program is hung in a loop. Try typing CTRL/C twice.
LA36 terminal paper is jammed or has run out. Check paper supply.
Telephone line hung up or system hung. Check carrier light. If
not lit, redlal and attach to your job.
See if terminal works when in local mode.
Check modem and terminal power.
Call User Contact Center.
2.4 SERVICES TO USERS
2.4.1 Business Hours
Table 2-1 presents hours of operation in Eastern Standard Time or Eastern
Daylight Time, depending on the season. Services during nonscheduled hours
will be made available upon prior coordination with User Contact Center.
TABLE 2-1. HOURS OF OPERATION
Facility
*VAX Availability
*0perator Coverage
User Support
Telecom. Support
DPSS Support
Monday-Friday
Continuous
Continuous
0800-1900
0600-2400
0700-2400
Saturday
Continuous
Continuous
None
0800-1600
0700-1630
Sunday
Continuous
0000-080(1
None
None
None
Information concerning unavailability due to system backups can be
obtained by typing the following at the S prompt: OPERATION_SCHEDULE
or by dialing the status recording at (919) 541-2969. Normally the
cluster will be unavailable from 1700 Monday until 0800 Tuesday due to
system backups, maintenance, and testing.
2-6
-------
A detailed operation schedule is made available to the user community before
the start of each week. Users can display this schedule by entering:
$OPERATION SCHEDULE
2.4.2 User Information Services
2.4.2.1 Availability of Manuals
Technical manuals and reference documents required to support the EPA user
community are maintained in the VAX User Support and VAX System Support areas
of the NCC. This documentation, available as reference material only, covers
aspects of the VAX hardware, software, languages, special programs, and other
operating areas of the NCC. Sites which have VAX's installed may also main-
tain documentation sets. Check with the system manager of a particular site.
Information on obtaining software documentation from vendors can be found in
Appendix F.
2.4.2.2 On-Llne Help Function
A group of HELP files has been established to provide descriptions of software
and system functions available with the VAX/VMS operating system. The user
oust type in 'HELP* at the dollar sign prompt to receive a complete list of
on-line help topics. More specific information can be retrieved by typing in
the topic at the 'topic' prompt within the Help facility, or the user may
directly type at the dollar sign 'HELP subtopic*. For example,
5HELP MAIL
will display text on the MAIL utility program and its commands can be used.
See Appendix E for a list of available Help files.
2.4.2.3 On-Line Documentation System
In addition to the on-line Help facility described in Section 2.4.2.2, a
collection of useful documentation is also maintained on-line for user
reference. The system is menu-driven and is accessed by typing the command
ONLINEDOC. It allows the user to display, print, or copy documentation
dealing with various topics of interest.
2.4.2.4 EPA-NCC User Memos
Memos are periodically issued containing Information pertinent to computing
activities at the NCC. These memos are mailed to users who have asked to
receive them. Memos particularly relevant to the VAX system or concerning
the NCC in general can also be accessed on-line. Type the command MEMO to
Invoke a menu-driven facility that will allow you to locate and view the
available memos.
2-7
-------
2.4.3 Consultation and Assistance
The NCC provides extensive consultation resources to assist users who have
problems related to ADP usage. Although many of these resources are spread
througout the NCC organization, the primary focus of these services is the
User Contact Center. The major areas of consulting services and user assis-
tance are discussed Individually in this section, primarily to Inform the
reader of the type and extent of the services available.
2.4.3.1 Telecommunications Assistance
The NCC provides and maintains hardware and software components required to
support the NCC interactive network. Continuous monitoring of the network is
provided, and, when necesssary, software modifications and hardware changes
are made. Where possible, attempts are made to anticipate and prevent commu-
nication problems along the network. Users experiencing communication prob-
lems should contact the User Contact Center for assistance.
2.4.3.2 User Support Services
The NCC has a comprehensive user support service to provide the user with
technical assistance, problem diagnosis and solution, and consultation with
respect to all NCC methods, procedures, and software needed to access and
effectively use the NCC ADP resources. The User Contact Center (UCC) is the
primary point of contact between the user community and the VAX facility.
Personnel requiring assistance or Information can contact the UCC by phone
(see Appendix A for the telephone number). The User Contact Center is staffed
and equipped to handle most problem areas and abnormal situations encountered
by a user. In other cases, it has the means to contact the appropriate
persons and to get answers to unusual user problems.
2.4.3.3 NCC Centralized Problem Management System
All user problems and questions are documented through the NCC Centralized
Problem Management (CPM) system. A Problem Management Record (PMR) is opened
each time a user contacts the NCC, either through User Support or Telecom-
munications. The PMR contains essential Information relating to the call,
including the user's name, User-ID, telephone number, a description of the
problem, and, eventually, complete documentation of its resolution.
This tracking system benefits both users and the NCC. The user is assured
that his problem has been documented when he is given a corresponding PMR
number. Additionally, this number may be referenced when recontacting the
NCC. Through an acceleration mechanism within the system, the problem's
priority is automatically Increased until it is closed. The CPM system also
benefits the NCC by providing a record of all user calls for historical
purposes.
2-8
-------
2.4.3.4 Classroom Training
Through the facilities of the EPA National Computer Center (NCC), the National
Data Processing Division provides ADP training at a reasonable cost to EPA
and to other Federal agencies and state and local governments. These courses
include several VAX-related classes. The classes are scheduled regularly at
the NCC in Research Triangle Park, N.C., and can also be provided at other
locations by special arrangement.
The courses currently offered are:
Title: VAX Course 1
Description:
Target
Audience:
Course
Objective:
Length:
Prerequisites:
Course
Outline:
VAX Course 1 is designed to familiarize the end-user with
the basics for using the VAX/VMS computer. Operating
system commands will be covered, as well as the essentials
of constructing command procedures for repeated usage.
The VAX batch environment, editing, and NCC communication
basics are detailed as part of the overall presentation.
End-users of the VAX/VMS computer who require a basic,
beginning-level explanation of the system.
Participants will gain a working knowledge of the VAX/VMS
computer system and its capabilities.
2 days
None
VAX/VMS Overview
Basic System Commands
VAX Files
DCL Commands, Loglcals, Symbols
Command Procedures
Logln.com - Special Command Procedure
Batch Processing
Editing
VAX Clusters and Networking
2-9
-------
Title:
Description:
Target
Audience:
Course
Objective:
Length:
Prerequisites:
Course
Outline:
VAX Course 2
This course is designed to expand the knowledge of the
VAX/VMS user. Concentration areas Include additional
information on system usage: Advanced Command Procedures,
the VAX Librarian Utility, Task Spawning, the Run Time
Library (RTL), System Services, and the Symbolic Debugger.
The new Extensible VAX Editor (EVE) will be discussed as
a powerful addition to the user's environment. VAX
FORTRAN will be covered as the language of choice for
examples, and there will be separate presentations on
the FORTRAN Compiler and special features of the language.
Users of the VAX/VMS computer system who require a more
In-depth knowledge of system capability. The need for
this level of understanding generally arises in the
program development environment. Any intensive VAX user
could benefit from the course material, even if FORTRAN
is not the local language of choice for development.
Participants will gain a working knowledge of some
VAX/VMS advanced capabilities. They will learn to write
more extensive command procedures, edit files using the
EVE editor, create and maintain VAX Libraries, use the
Symbolic Debugger, call on VMS System Services and RTL
routines, and use certain FORTRAN features for program
development.
2 days
VAX Course 1
EVE - The Extensible VAX Editor
Advanced Command Procedures and Lexlcals
VAX Librarian Utility
DCL Commands for Programming Support
FORTRAN Language Features
FORTRAN Compiler and VMS Linker
VAX Run Time Library and FORTRAN
VAX File Handling and FORTRAN
VAX Symbolic Debugger
VMS System Services
2-10
-------
Title:
Description:
Target
Audience:
Course
Objective:
Length:
Prerequisites:
Course
Outline:
VAX/FOCUS
This course parallels the equivalent course for the IBM
mainframe. The course is designed for the user needing
to produce reports from existing data bases. The nature
of data base construction and maintenance will be covered
in a subsequent course. Topics for this course include
standard reporting, advanced reporting, and s'lort sections
on statistics and data graphing; also included are the
creating of new variables and the use of batch and
command mode for the running of FOCUS reports.
Users of the VAX/VMS system who by nature of their
position need the output of FOCUS data bases to complete
their daily requirements. The development and maintenance
of FOCUS data bases is not covered.
Participants will become familiar with the reporting
capabilities associated with FOCUS data bases.
2 days
VAX Course 1 or equivalent experience
FOCUS Basics
Standard Report Preparation
Report Formatting
Report Procedures
Reports from External Files
FOCUS Statistics
FOCUS Graphics
DEFINE Environment
FOCUS Batch and Command Files
For further information about any training services, contact:
EPA National Computer Center
Training Office, MD-34B
Research Triangle Park, NC 27711
(919) 541-7352; (FTS) 629-7862
2-11
-------
2.4.3.5 ON-LINE TRAINING
There are two courses available for users to learn about the EDT Editor and
the VMS operating system. To access these, type the following:
RUN EDT2CAI (for the editor training session)
RUN VMS2CAI (for the VMS training session)
2.4.4 Data Processing Support Services (DPSS)
2.4.4.1 Tape Library
DPSS is responsible for all computer tapes stored at the NCC. This responsi-
bility includes inventory control, utilization and ownership reporting,
replacement of defective tapes, purchase of new tapes, and Initialization of
volumes at regular intervals.
2.4.4.2 I/O Control
DPSS is responsible for retrieving, separating, and distributing output, and
for the following additional I/O activities:
a. Preparing, logging, and shipping output.
b. Answering computer room telephones.
c. Coordinating routine and special duties performed by the con-
tracted courier service.
d. Receiving foreign tapes, assigning slot numbers, informing users,
and releasing and returning tapes to users.
e. Distributing monthly tape lists to users.
f. Controlling visitor access to the computer room.
2.4.4.3 Printout Distribution
Output distribution bins have been designated for VAX users. DPSS will place
all printed output In the bins, and the user is responsible for picking up
his output or requesting courier or mail service.
DPSS Is responsible for coordinating the courier service in the RTF area. A
commercial vendor has been contracted to perform this service. Twice each
day, at 0700 hours and 1300 hours, DPSS dispatches output via courier to
offices located in the RTP area. Deliveries of input to DPSS from users are
made each weekday at 1100 hours and at 1600 hours.
2-12
-------
2.4.4.4 Auxiliary Services
The NCC installation includes a number of auxiliary services important to
overall operations, but not directly concerned with data processing. Infor-
mation on two of the major ones follows:
a. Tape Degausser; A tape degausser is a device that passes magnetic
tape through a strong magnetic field, thereby erasing any informa-
tion recorded on it. This device ensures an erasure level of not
less than 80 decibels; normal computer tape recording levels are
between 50 and 60 decibels. This erasure level complies with the
requirements of the Privacy Act of 1964 and meets National Security
Agency standards. The degausser will erase a 2400-foot reel of
computer tape in about 15 seconds. This operation removes all
data, Including any labels and header information.
b. Tape Cleaner/Evaluator; The NCC has two cleaner/evaluators for
magnetic tapes. Tapes are cleaned and/or evaluated by request or
as needed, based on an established set of standards.
2-13
-------
3.0 MANAGEMENT OF NCC-VAX SYSTEM RESOURCES
3.1 SITE POLICY AND SYSTEM AVAILABILITY
Policy for providing highly responsive computer services Is a product of the
dictates of EPA Headquarters, vendor recommendations, the local EPA Site
Manager, and the VAX System Manager. Time Is allocated for the following
types of activities:
o Full Service (Includes operator assistance, local operations, and
Remote Job Entry)
o Partial Service (restricted)
o Preventive Maintenance
o Software Maintenance and System Backup Operation
o System Programming
3.2 REGISTRATION PROCEDURES
To obtain accounts on the VAX Cluster, ADP Coordinators must complete Form N258
and return It to the Time Sharing Services Management System (TSSMS) Office.
(A copy of the form is included in Appendix B.) The address is shown on the
lower left-hand corner of the form. Signature of the ADP Coordinator is
required, denoting approval to establish the new account. The correct Finan-
cial Management System (FMS) accounting code must be supplied to establish a
link to the Agency's budgeting structure. The VAX account code (sometimes
referred to as a project code) will be constructed of the first four charac-
ters of the FIMAS code, followed by one character designating the type of
activity (D • Development, T • Testing, C « Conversion, P • Production,
etc.), then three optional characters to tie this account to a user's budget
system. The FIMAS utilization code should be entered in the box labeled
"Purpose...." One can be assigned during the account registration process if
it does not previously exist. There should be at least one account per
system.
An initial password is established with each new user account. When the new
user first logs into the VAX system, the password should be changed immediate-
ly, using the SET command. Refer to Section 4.4 for Instructions on using
the SET PASSWORD command.
3-1
-------
3.3 RESOURCE MANAGEMENT
3.3.1 Disk Space Management
3.3.1.1 Quotas
Currently, the amount of disk space a user nay occupy on a public park is
unrestricted. However, users are expected-to exercise good judgment vd.th
regard to the amount of space they use. Users are encouraged to check peri-
odically for unneeded files that can be deleted and to purge old versions of
files. Large files used only occasionally nay also be moved to magnetic tape
for long-term storage. If a shortage of disk space becomes a problem at some
future time, the VAX Disk Quota utility can be Invoked to limit users to a
specified number of blocks of storage space.
3.3.1.2 File Archiving
To make the most efficient use of disk space on the VAX Cluster, unused files
are archived to tape. A file is determined to be "unused" by the expiration
date associated with it. To see this date, use the following command:
$ DIR/DATE-EXP
Each tins a file is accessed, its expiration date is reset 45 days into the
future. An "access" can be any read or write operation. Data Management
jobs are regularly run to look for files that have reached their expiration
dates, Indicating that they have not been used for at least 45 days. These
files are copied to tape and deleted from the disk. The archive tapes are
kept for a period of 1 year. A second copy of the archive tapes is also made
and stored offsite for use In disaster recovery.
Files may be recovered from the archive tapes without any operator assistance.
It is a two-step procedure: First, you must find out where the file is
(archive tape reel number and saveset name), and then you must issue a request
to restore it back to disk.
To get a listing of archived files, issue the following command:
$ TAPE REPORT/SYSTtM/HISTORY-ARCHIVE filespec
"Filespec" may be a particular file, or it may Include wildcards to reference
multiple files. Specifying "[...]*.*" will produce a listing of all archived
files. The qualifier, /OUTPUT-f lie name, may also be added to s-ind the report
to a file instead of the terminal screen. For exani>le, assume that user XYZ
issues the following command (while his default directory is $2$DUA1:[XYZ]):
$ TAPE REPORT/SYSTEM/HISTORY-ARCHIVE/OUTPUT-REPOKT.DAT MYDATA.DAT
3-2
-------
The following report would be written to [XYZjREPORT.DAT:
IRun date 31-DEC-1987 10:27 Page 1
System Backup Report
Set ARCHIVE — File *::$2$DLA1:lXYZjMYDATA.DAT;*
OVAXTM1::$2 $DUA1:[XYZ JMYDATA.DAT;1
28-JUL-1987 08:13 098469 $2$DUA1.ARC
0 End of report
The listing indicates the date and time the file was archived, the six-digit
reel number of the tape it was copied to, and the name of the saveset that
contains it (diskname.ARC). You will need this information to issue the
request to restore the file, which is done with the following command:
TAPE RESTORE/SELECT«filename reel-number saveset-name output-file
For example, to restore the file listed in the report above, the command
would be:
$ TAPE RESTOREXSELECT-MYDATA.DAT 098469 $2$DUA1.ARC *.*
A batch job will be submitted to perform the restoration, and you will receive
a HAIL message when it is completed. The above procedure can also be carried
out through the TAPESYS menu system (see Section 5.4 for details).
Note; The act of restoring a file from archive does not reset its
expiration date. Once restored, it is Immediately a candidate
for archiving again and will be picked up by the next archive job
run. Therefore, users should access a restored file as soon as
possible after recovery.
3.3.1.3 Standby Archiving
You may also request a file to be Intentionally archived for long-term (2-year)
storage. To initiate the procedure, called Standby Archiving, enter the
following command:
$ TAPE BACKUP/REEL«ARCHIVE/NOTES-2_YEAR/RECORD/LOG filename
a. The REEL- specification must be the word ARCHIVE.
b. The /NOTES- qualifier must be included in all requests, with the
first word being 2_YEAR (in capital letters) to indicate an archive
class to TAPESYS.
3-3
-------
c. The /LOG option will include a log entry in the user's directory.
d. The /RECORD option will Bake an entry in the history file to enable
the user to inquire about the file at a later date.
As an alternative to using the preceding command, you nay make an archive
request through the TAPESYS menu. This can be accessed by typing TMENU for
the TAPESTS main menu, or STORE for accessing the file backup menu directly.
(TAPE BACKUP/SCREEN will also display the file backup menu.) When using the
menu, the /NOTES, /LOG, and /RECORD options are Included by default. The
user only needs to specify ARCHIVE for the reel identification Instead of
FREE TAPE, the menu's default.
It should be noted that archiving is not accomplished immediately upon
executing the preceding commands. The actual archiving of the flle(s) is
done by jobs executed by NCC Data Management personnel several times a week.
This execution may be 1 or 2 days after the archive request was made. The
user will receive a MAIL message when the job runs and the file is archived.
At that time, he may delete it from disk. Users are charged only for Issuing
the command, not for the unload or storage of the file.
3.3.2 Disk Backup and Recovery
3.3.2.1 Disk Backup Schedule
Files on disk volumes are copied to magnetic taf>e by the NCC Operations staff
using the BACKUP utility program. Backups are of two kinds: full, in which
all files on the disk are copied to tape, and Incremental, in which new files
or files that have been modified are copied to tape. Full backups will be
done biweekly on Monday nights during system time. Incremental backups will
be done nightly. The full backup tapes will be retained for 4 weeks; incre-
mental backup tapes for 31 days. During these intervals, files can be re-
stored from tape to disk as needed.
Note: Private user packs are not subject to system backups. It is the
responsibility of the owners of these disk packs to perform backups.
However, the NCC Operations staff will perform such backups by special
arrangement with the owners. Contact DPSS for more Information.
3.3.2.2 File Recovery Procedure
Users may recover their files from the system Incremental backup tapes
without any operator assistance. It is a two-step procedure: First, you
Dust find out where the file is (backup tape reel number and saveset name),
and then you must issue a request to restore it back to disk.
To get a listing of a file's backup copies, issue the following command:
$ TAPE REPORT/SYSTEM/HISTORY-DAILY filespec
-------
"Filespec" may be a particular file, or it nay Include wildcards to reference
multiple files. Specifying "I...]*.*" will produce a listing of all backed-up
files. The qualifier, /OUTPUT-filename, oay also be added to send the report
to a file Instead of the terminal screen. For example, assume that user XYZ
issues the following command (while his default directory is $2$DUA1:[XYZ]):
$ TAPE REPORT/SYSTEM/HISTORY-DAILY/OUTPUT-REPORT.DAT LOGIN.COM
The following report would be written to [XYZjREPORT.DAT:
IRun date 21-DEC-1987 09:45 Page 1
System Backup Report
Set DAILY — File *::$2$DUA1:[XYZjLOGIN.COM;*
OVAXTM1 :
OVAXTM1 :
OVAXTM1 :
:$2$DUA1 : [XYZ]LOGIN.COM;48
13-DEC-1987 12:01 097307
:$2$DUA1 : [XYZ]LOGIN.COM;47
7-DEC-1987 17:38 097861
:$2$DUA1:[XYZ]LOGIN.COM;46
2-DEC-1987 13:48 097740
$2$DUA1.BAK
$2$DUA1.BAK
$2$DUA1.BAK
[USE, XYZ]
[USE, XYZ]
[USE, XYZ]
0 End of report
The listing indicates the date and time the backup was made, the six-digit
reel number of the tape it was put on, and the name of the saveset that
contains it (diskname.BAK). You will need this information to issue the
request to restore the file, which is done with the following command:
TAPE RESTORE/SELECT-filename reel-number saveset-name output-file
For example, to restore the first file listed in the report above, the command
would be:
$ TAPE RESTORE/SELECT-LOGIN.COM;48 097307 $2$DUA1.BAK *.*
A batch Job will be submitted to perform the restoration, and you will receive
a MAIL message when it is completed. The above procedure can also be carried
out through the TAPESYS menu system (see Section 5.4 lor details).
3-5
-------
3.3.3 Security
3.3.3.1 Terminal Access
Access to the VAX via terminals is controlled by the user name and password.
These elements are checked upon entry for validity and accessibility to the
system.
3.3.3.2 Computer Room
The computer room (which contains CPU's, disk and tape drives, line printers,
and more) has limited access. Entrance is allowed only to Operations staff
and authorized personnel.
3.3.3.3 Physical Security
Security of the programs and data is controlled by periodic backup operations
and offsite storage of backup tapes in case of a facility disaster.
3.3.4 Tape Management
3.3.A.I Tape Assignment
The NCC maintains a supply of 9-track 6250 bpi magnetic tapes for general
use. These tapes are considered standard by the NCC. Magnetic tapes may be
acquired for use at the NCC by using the TAPE ALLOCATE command. (See
Section 5.4, TAPESYS Tape Management System.)
A tape number will be assigned to the user from the pool of available tapes.
The tape number will be used in the appropriate MOUNT command in a computer
run that will read and/or write to the tape.
Tapes acquired from external sources (foreign tapes) may require some prepa-
ration before they can be used on the VAX systems. Such tapes fall into two
categories: those written at some other computer installation, and uninitial-
ized tapes which have never been used before. The file names and volume
identifications of tapes created at other installations are unknown to the
VAX system. Therefore, processing of such tapes may require special handling.
VAX User Support should be contacted if assistance is required to process
foreign tapes.
DPSS can perform cleaning and/or degaussing of tapes as requested. However,
this process must be scheduled and will be performed as promptly as possible,
depending on the current workload.
3-6
-------
3.3.4.2 Tape Management System
Tapes on the NCC-VAX Cluster are accessed through and controlled by a Tape
Management System (IMS) called TAPESYS. TAPESYS benefits both users and
system management by providing the following functional advantages:
a. Gives user additional capabilities that are not provided by the
operating system for handling tape data files.
b. Reduces the human intervention required to handle tapes and
operate a computer center.
c. Increases computer system productivity by reducing clerical load
and manual operations required for handling tapes.
d. Provides additional protection against loss or misuse of tape data
files.
e. Provides useful management Information, including daily logs of
tapes approaching expiration.
The TMS software assumes most of the clerical burden associated with tape
handling. Thus, operators are relieved of accounting and tracking chores
related to tape processing, and users are provided with the capability to
treat tape files with much of the ease usually associated with disk files.
(See Section 5.4, TAPESYS Tape Management System.)
3.3.4.3 Foreign Tapes
DPSS defines foreign tapes as those not permanently stored In the NCC tape
library. This category includes any tape submitted from a source for proces-
sing at the NCC and any scratch tape purchased from DPSS and processed as
foreign.
Foreign tapes provided by the user to be processed at the NCC should be
delivered or mailed to Dl'SS at the address given in Appendix A.
Users are required by the NCC to properly Identify their tapes prior to sub-
nlttal. Identification stickers should be applied by the user to the face of
each foreign tape, indicating the following:
o Dser Name
o Account Number
o Telephone Number
o Bin Number or Mailing Address
o Original Reel Identification Number
Nonlabeled tapes must also be uniquely identified for cross-reference during
tape assignment by a job.
3-7
-------
The user is responsible for the cost of shipping tapes to the NCC. He will
be notified of the arrival of tapes by DPSS. Upon notification, the user may
process the tape.
The NCC has established a system that uniquely identifies each foreign tape.
The Tape Librarian assigns a slot number to each, thereby establishing a
unique identifier to aid the operator in finding the tape. The slot numbers
indicate the system on which the foreign tape is to be used Initially.
However, tapes can be used interchangeably (for read-only) from system to
system using the same slot number originally assigned. The slot number is in
the following form:
BXnnnn
I
where X-0, 1, or 2, representing IBM, SPERRY, and VAX, respectively, and
where nnnn represents a number in the range 0001-9999.
No foreign tape will be placed into service until the user has been contacted
and given the slot number.
Within 90 days, foreign tapes may be released by calling DPSS and requesting
the release. These tapes will be shipped upon request at the NCC's expense.
After 90 days, such tapes are automatically released and sent to the person
under whose User-ID or name the tape Is registered. To permanently maintain
data files stored on foreign tapes at the NCC, such data must be copied by
the user to an Internal NCC tape or disk.
3.3.4.A Allen Tapes
Any tape that has been created on an NCC system other than the system which
will read the tape is considered an alien tape.
Users must contact DPSS (see Appendix A for telephone number) to request that
the tape be made available to another system. Verification of ownership of
the tape will be made. Any jobs submitted prior to this procedure will be
canceled with the appropriate message to the user.
The tape will have a file-protect ring to prevent attempts to write on the
tape. The tape will then be moved to the staging area for the system that Is
to read it. At the end of the day, the tape will be returned to its native
system without the write ring. If the tape Is needed before the end of the
day, the user should just submit the Job that calls for the tape.
3.3.4.5 Tape Maintenance and Disposition
TMS-controlled tapes are intended to remain in the NCC Tape Library or in the
computer room. Any tape created with the intention of removing it from the
NCC, either temporarily or permanently, should be processed as a foreign tape,
3-8
-------
whether that tape is provided by the user or purchased from DPSS. TMS tapes
sent offsite oust be purchased ($20 each). The slot will then be filled by
another tape with the same number.
Some exceptions are made for the removal of IMS-controlled tapes from the NCC
to support certain specific purposes, including the following ones:
o Micrographics Processing
o Keypunch Processing
o Archival Storage
When a TMS-controlled tape is removed from or returned to the NCC, as in the
cases above, DPSS will update the TMS to reflect the transaction.
Monthly Foreign Tape Report. A monthly Tape Report is sent to the holder of
every User-ID having foreign tapes registered in the NCC Tape Library. The
report lists all tapes registered to that User-ID. It serves to inform each
user of the tapes currently being stored and the slot number assigned to each
tape.
Monthly TMS Tape Report. This report provides tape volume numbers, creation
dates, expiration dates, dates of last use, and current status. The status
indicates whether the tapes are active, archived, or checked out to the user.
If a tape was checked out of the library, the date of removal is shown.
To correct any entry on the report or to alter the status or expiration date
of any tape, the user should note the change on a copy of the report ana
return it to DPSS. Any urgent corrections to the report, Including the ex-
tension of an expiration date, should be made by telephoning DPSS with the
appropriate information. Users will find that effective verbal communication
regarding items on the tape report will be difficult, if not impossible,
unless the report is in hand during such conversations.
Users may have tapes scratched at any time by submitting a request in writing.
The monthly tape report may be used to note changes to be made by placing an
X to the left of the entry for the tape to be scratched. When requesting
that a tape be scratched, the user should remember that all data files on the
tape will be scratched. If there are data files that must be retained, the
user should not scratch the tape. Ownership will be verified prior to
scratching TMS tapes.
The tape report should be returned to DPSS after all appropriate entries,
Including the user's signature and commercial telephone number, have been
nade. The entries on the report must be clear and precise. Only in cases
where there is some ambiguity will the user be contacted by telephone for
clarification or verification of information on the tape report.
Archiving, Dearchiving. and Releasing from Archive. The NCC archival library
Is available for offsite storage of users' backup tapes and tapes containing
data to be retained indefinitely but with no immediate processing requirement.
There is no charge for storage in the archival library, but a $10 fee is
assessed for each retrieval. A user may have a tape transferred to (archived)
3-9
-------
or returned from (dearchived) the archive library by notifying DPSS (Appendix
A). Advance notice of 24 hours is required for dearchlval. The user will be
notified when the dearchived tape is onslte and available for processing. If
a job is submitted prematurely, it will be terminated.
Archived tapes are considered to be permanently inactive, and references to
such tapes are purged from the Tape Management System. Inactive tapes can be
read upon dearchlval, but writing to an inactive tape Is not allowed. To
ensure that such tapes are not overwritten, they are protected by a file
guard ring that prevents insertion of a write ring, and the tapes are labeled
with a NO RING EVER warning. If the user wants the data on the archived tape
to become active, he should copy the data to an active TMS-controlled library
tape and either return the dearchived tape to the archive library or release
It. Dearchived tapes will be returned to the archive library no later than 5
days from the date of notification to the user of the availability of the
tape onslte. If more time is needed for processing a dearchived tape, the
data should be copied to a TMS-controlled library tape. Verification of
ownership will be made prior to archival, dearchival, or release from archive.
When a tape is archived, its TMS slot and associated external label are
assumed by a new active tape. The archived tape retains its internal label,
but receives a new external label from the archival library. Thus, the TMS-
Imposed compatibility between the Internal and external labels is negated.
Upon dearchival and access of the tape, the user should refer to the tape as
if it were a foreign tape; that Is, he should refer to the archive tape
number, not the original external label.
3.4 ACCOUNTING
3.4.1 System Usage and Chargeback
The VAX has the capability of accumulating usage statistics for chargeback
purposes for each account and user. These statistics can be any number of
variables determined by the system manager. Usually there are three categories:
o Monthly Recurring Charges
o Monthly One-Time Charges
o Processor Charges
Monthly recurring charges consist of tape and/or disk rental, disk utilization,
foreign tape storage, terminal rental, dedicated port, and batch privileges.
Monthly one-time charges include terminal Installation, technical charges,
and graphics plotter charges.
Processor charges are connect time and system utilization measured by the VAX
resources used.
3-10
-------
ADP Coordinators receive monthly billing reports for all registered accounts.
These reports are broken down by the account and utilization categories. For
conversion activities, monthly reports are received but not charged to the
FMS accounting code. Billing rates for FY88 follow. These rates are tentative
and may be adjusted for proper cost recovery.
3.4.1.1 CPU Chargeback
FY88 CPU chargeback rates are:
Processor Chargeback Unit of Measure Rate
VAX 8600 $/CPU hour 150.00
VAX 11/785 $/CPU hour 60.00
3.4.1.2 Computer-Related Charges
FY88 computer-related charges are:
Component Chargeback Unit of Measure Rate
Disk-Storage Charges
Public Disk Storage $/thousand blocks/day 0.075
Private Disk Storage S/pack/month 300.00
Tape Data Storage
Standard Tape Storage $/month 10.00
Foreign Tape Storage, Days 1-5 $/day 2.00
Foreign Tape Storage, after 5 Days $/day 5.00
Archive Tape Storage S/month 5.00
Print Lines S/thousand lines 1.50
3*4.1.3 Access Charges
Access charges are appropriate for certain data telecommunications services
for which there are limited capabilities to monitor and equitably charge for
services on a "usage basis." Access charge rates for data telecommunications
services In FY88 are as follows:
Service Chargeback Unit of Measure Rate
VAX DECnet $/month 500.00
MicroVAX DECnet (Optional) $/month 100.00
3-11
-------
All ORO laboratories with DEC VAX computers will be charged a DECnet access
fee of $500 per month during FY88. This charge is Independent of the actual
usage of DECnet; no DECnet usage charges will be implemented in FY88. All
ORD labs and other EPA program offices with DEC MicroVAX's desiring DECnet
services will be charged a MicroVAX DECnet access fee of $100 per month during
FY88.
3.A. 1.4 Usage Charges
The majority of all data telecommunications costs are recovered via terminal
connect time charges for various classes of service, based on the total time
a user terminal maintains an active link to an Agency mainframe computer.
Due to significantly higher costs associated with the Agency's expanding data
telecommunications capabilities, it is necessary to Increase "usage" chargeback
rates for FY88. The rates are:
Service Chargeback Unit of Measure Rate
Terminal Connect $/hour 9.00
High-speed Terminal Connect $/hour 15.00
The following algorithm is used to calculate the cost of a VAX batch job:
Batch Job Cost - ((CPU * PBF) + $P)
where PbF « Priority Billing Factor, defined as follows:
Batch Queue Requested Priority Billing Factor
Fast 2.0
Normal 1.0
Slow 0.5
$P - (Print Rate * Print Lines (generated by the Job and printed at NCC,
divided by 1000)
The following algorithm Is used to calculate the cost of an interactive VAX
terminal session:
Interactive Job Cost - ($CPU * IBF) - $CT)
where $CPU » (CPU rate * CPU hours (used during terminal session) )
IBF « Interactive Billing Factor (FY88 value • 1.0)
$CT - (Connect Time rate * Hours (accumulated for the terminal
session)
3-12
-------
3.4.2 Refunds
Charges will be refunded if a transaction fails due to console operator error,
system hardware failure, or system software errors. Jobs using more than
2 hours of CPU time must have a user-defined save and restart capability to
be eligible for a refund. The refund will not exceed charges greater than
those Incurred during 2 hours of CPU utilization. To apply for a refund,
please contact User Support at the numbers listed in Appendix A.
3.5 PRODUCTION CONTROL SERVICES
The Operations staff provides services to monitor jobs, distribute output,
and process run requests that are required on a fixed schedule. Tasks that
cannot be scheduled on fixed days or dates are acceptable; however, timeliness
of task execution cannot be guaranteed. Users requiring production control
services should contact the system manager.
3-13
-------
4.0 VAX/VMS OVERVIEW
4.1 SYSTEM ACCESS
If you are using a modem to gain access, refer to Section 2.3 of this guide
for the initial steps in signing on. Once the connection is made with the
VAX system, the procedure is the same for all VAX users.
4.1.1 Logging In
The following steps are used to gain access to the VAX system after communication
has been established through direct line or modem:
a. Hit . Welcome messages appear and a prompt for USERNAME: will
be given by the system. It is a constant, known to anyone, and
typed and printed on the screen.
b. Hit . A prompt for PASSWORD: is set initially by the system
manager but should be changed. It is not known to other users and
is typed but does not appear on the screen.
c. Hit . Enter project identifier (account number of 5-8 characters)
at prompt.
d. Hit . System messages appear such as the welcome statement,
the last login, and text from the system manager.
e. $ (PROMPT). The appearance of this symbol on the screen indicates
that the system has acknowledged the user's presence and has run any
prespecified command files.
NOTE: While engaged in a session on the terminal, usage of resources will be
billed to the PROJECT entered at logon time. This project can be changed
while logged in by using the following command at the prompt:
CP (for Change Project)
It will then prompt for the new project to charge system usage to.
4.1.2 Logging Out
Unless otherwise specified, the command to signoff the VAX system is as
follows:
$LOGOUT
4-1
-------
4.1.3 Interactive CPU Limit
A limit for CPU usage per interactive session of 20 minutes has been estab-
lished. This will restrict large CPU intensive jobs from running inter-
actively and slowing down other users.
4.2 DISK STRUCTURE AND FILE SPECIFICATIONS
4.2.1 Disk Structure and Directories
A directory is a file on a disk volume that holds information about other
files. Access to the other files is through the directory. User directories,
which are functionally the user disk apace, are referenced by the directory
name enclosed in square brackets.
Each disk contains a top level directory indicating user file directories on
the disk. Each user directory locates the files in that directory and
Indicates the next level of subdirectories (see Figure 4-1 below).
Mister
File
Directory
UMr
File
Directory
Utcr
File
Directory
I
1
Uter
File
Directory
Sub-
directory
(1nltwtll
-4—
|D»u
File
Sub-
directory
(1n level)
'
IDete
File
1
Sub-
directory
(2nd tottl)
I
Dm
File
Additional d*u files
and tutadirectorits
Figure 4-1. Disk Structure
4-2
-------
Three formats of directory names (designated by square brackets) are possible:
a. An alphanumeric string from three to nine characters long. For
example, [EPAXAV].
b. A two-part octal number in the format of the User Identification
Code (UIC). For example, (10,5].
c. A sequence of directory names (namel.name2.name3....nameS), where
each name represents a directory level and may have up to 9
alphanumeric characters. For example, [EPAHUB.TESTFILES.DATA].
You may not mix UIC format and alphanumeric format within the same
directory name.
Note that the alphanumeric format can be used to specify direc-
tories whose names are in UIC format. The group and member fields
(see Section 4.2.2) must be zero-filled on the left. For example,
[10,5] would become [010,005].
4.2.2 Creating Subdirectories
The initial directory for each user is established by system management. The
user can create subdirectories under his main, or first level, directory by
use of the CREATE/DIRECTORY command. For example, user [EPAWAR] creates a
second level directory by
$CREATE/DIRECTORY [EPAWAR.TASKS]
Eight directory levels, including the first level, are allowed. The disk
space allocated to the first level or main directory is the physical limit
on the space used by the subdirectories. Subdirectories can be deleted only
after all the files in them have been deleted.
4.2.3 File Specifications
File specifications tell the VAX/VMS operating system where to locate a file.
The maximum length of a file specification is 128 characters. File specifi-
cation formats are as follows:
NODE::DEVICE:[DIk]FILENAME.TYPE;VER
where NODE is the node, or system, name. For example, the VAX Cluster
consists of two nodes, VAXTM1 and NCCORD. A node specifi-
cation is only necessary if the file is located on another
system on the network.
DEVICE is the device (usually a disk) that the file resides on.
It is not needed if referencing a file that is on the
current default device.
4-3
-------
DIR is the name of the directory containing the file. It
must be contained in square brackets ([ j) and must be
used when referencing a file that is not in the current
default directory.
FILENAME Is the name of the file. It may be 1 to 39 characters
long. You may use letters, numbers, and the "_" and "$"
characters in the file name.
TYPE Is an extension to the file name. It may be 0 to 39
characters long, but it is typically 3 and usually serves
to identify the contents of the file (for example, DAT
is a data file, and COM is a command procedure).
VER is the version number of the file, indicating how many
times the file has been altered.
4.3 CHANGING DEFAULT DISK OR DIRECTORY
Each user's default directory is designated in the system's user authorization
file. To change the default, use the SET DEFAULT command—for example,
$SET DEFAULT USER0$DISK:[EPA]
This command changes the default disk device to USER0$DISK and the default
directory name to [EPA].
It" the command had been
$SET DEFAULT USER0SDISK
the default disk, but not the directory, would have been changed.
If the command had been
$SET DEFAULT [EPA]
the default directory, but not the default disk, would have been changed.
4.4 CHANGING PASSWORDS
Passwords should be changed often, and immediately whenever the secrecy of a
password is compromised. Passwords may be from 6 to 31 characters in length.
Valid characters for password use are A-Z, 0-9, $, and (underscore).
The user may change his password by typing the following command:
$ SET PASSWORD
4-4
-------
The user is then prompted for the old password, the new password, and verifi-
cation (a third prompt), for the new password again.
Example:
SET PASSWORD
Old Password: (passwordl)
New Password: (password2)
Verification: (password2)
Note that responses will not echo
back to the terminal.
4.5 PRINTING FILES
4.5.1 System Printer
Files can be printed using the PRINT command with or without associated
qualifiers. A file is placed in a printer or terminal queue by the PRINT
command, a unique job identification number is assigned by the system, and
the job number is displayed when it has been successfully queued. The default
PRINT command can be modified by specifying qualifiers as described below:
$ PRINT/NOTE-B0nn[qualifiers] file-specl/file-qualifiers]
Note; You must use the /NOTE- qualifier to specify your bin number to the
operators. If you do not know your bin number, contact DPSS at the
number listed in Appendix A.
Where qualifiers are as follows:
/AFTER-time
/CHARACTERISTICS-(c[...
/FORMS-type
/JOB__COUNT-n
/NAME-job-name
/NOTE-bbbb
/INOJNOTIFY
/OPERATOR-me s s age
/QUEUE-queue-name
Job will not print until after a specific time.
Specifies one or more installation-defined
characteristics desired for printing.
Specifies the name or number of the form for
the print job.
Requests the job be printed n times.
Defines a name string to identify the job and
is printed on the flag page.
Specifies where to file or mail printed output.
Controls whether a message notifying completion
Is broadcast to anywhere a user is logged on.
Sends a specified message to an operator.
Requests a print job to a specific queue.
4-5
-------
And where file-qualifiers are as follows:
/COPIES-n Specifies the number of copies to print.
/(NO]DELETE Controls whether the files are deleted after
printing.
/[NO]FEED Controls whether the PRINT command automatically
Inserts form feeds.
/INO]HEADER Controls whether a heading line is printed at
the top of each input page.
/PAGES-n Specifies the number of pages to print on a
specific job.
In the following example, 10 copies of MEMO.TXT will be printed after 8:00 p.m.
(2000 hours).
$ PRINT/AFTER-20/COPIES-10 MEMO.TXT
4.5.2 Laser Printers
Some users have access to local LN03 laser printers and thus can specify
special forms types. The command format to submit a file to print on one of
these printers is:
$ PRINT/QUEUE-laser_queue__name/FORM-form_name filename
The defined forms types are:
Form Name Description Comments
LASER 66 x 96 portrait Default
NORMAL 66 x 96 portrait Same as LASER
WIDE 50 x 134 landscape
COMPRESS 92 x 109 portrait
WIDE_COMPRESS 68 x 147 landscape
COMPRESS WIDE 68 x 147 landscape Same as WIDE_COMPRESS
LETTER ~" 57 x 78 portrait
LPT80 66 x 80 portrait
4.6 TRUNCATING COMMANDS
Tou can type DCL commands to the VAX by using either full or abbreviated
Input. All command keywords entered as input can be abbreviated:
.command names
.command keyword parameters
.qualifiers
.qualifier keyword values
4-6
-------
The command interpreter only examines the first four characters of each key-
word entered, and all command name keywords are unique when truncated to
their first four characters. Abbreviation to fewer characters by users is
allowed as long as a unique truncation is chosen. For example, the commands
DEALLOCATE and DEASS1GN have the same first three letters and cannot be
truncated to less than four letters.
Four commands which are exceptions to the unique truncation rule are:
CONTINUE
DEPOSIT
EXAMINE
RUN
They can all be abbreviated to their first character, even though other
commands begin with the same letter. All other command keywords (parameters,
qualifiers, qualifier values) recognized by individual commands are unique
compared to other keywords used by that command and can be truncated to four
or fewer characters.
4.7 VOLUME AND FILE SECURITY
Tape and disk volumes and individual files on disk volumes, Including direc-
tories, are protected by an owner UIC and a protection code. The protection
code indicates who is allowed access for various purposes.
The UIC provides a user with a group number, followed by a member number
within the group. When any user attempts to access a file or volume, his UIC
is compared with the owner UIC of that file or volume. Depending on the two
UIC's, the user requesting access is categorized as follows:
a. System; A user with system privilege (SYSPKV) or a group number
between 1 and 10 octal. Generally refers to system managers,
system programmers, and operators.
b. Owner; Has the same UIC as the file or volume's creator.
c. Group; Has the same group number as the owner of the file.
d. World; All users who are not in the above groups.
Each of these categories can be allowed or denied the following access:
a. Read; Reading, printing, or copying a file or files on a volume.
b. Write; The ability to create or modify a file, or to write files
on a volume.
4-7
-------
c. Execute; The ability to execute files that contain executable
images. Note that read access implies execute access. For a
volume, execute access is equivalent to the ability to create
files.
d. Delete; The ability to delete files on a volume.
4.7.1 Disk Directory and File Protection
The VAX/VMS system provides default protection codes for files you create.
SYSTEM-RWED, OWNER-RWED, GROUP-RE, WORLD-NO ACCESS
If this is not satisfactory, you can define the protection you want with
either the COPY or SET commands. For example,
5COPY filenamel.type filename2.type-
$_/PROTECTION-(SYSTEM:RE,OWNEk:RWED,GROUP:RE,WORLD)
$SET PROTECTION=(SYSTEM:RWE,OWNEk:RWED,GROUP:RL,WORLD)-
$_f ilename.type
You can examine the protection of individual files with the DIRECTORY/-
PROTECTION command.
Directory protection is equally as important as file protection. For example,
use of the RENAME command allows processes that have write access to a direc-
tory to DELETE files from that directory even when the files are protected
against deletion.
SRENAME [HSCjfilenamel.type (XYZ]filename2.type
In this case, the file has been renamed and relocated to (XYZj. The file is
no longer available to the original owner.
4.7.2 Tape Protection
Protection must be explicitly specified when a tape volume is initialized and
will apply to all files on the volume. Execute and delete access have no
meaning with tapes. The owner and system users always have both write and
read access to tapes. Write access to a tape volume Implies read access.
4.8 MOUNT COMMAND
The MOUNT command is used with various qualifiers for both tape and disk
volumes. The format is:
SMOUNT (device-name!;][,...]) [(volume-labelI,...])] Ilogical-name I:]]
4-8
-------
The device name can be either a physical device name or a logical name for
the device on which the volume will be mounted. The volume-label length is
from 0 through 6 characters for tapes, and from 1 through 12 characters for
disks. If you specify more than one volume, separate the labels with commas
or plus signs. Volumes Bust be part of the same volume set and must be
specified in ascending order by relative number. The logical name is a 1
through 63 alphanumeric character string name associated with the device. If
you do not specify a logical name, by default the logical name DISK$volume-
label is assigned to a disk drive, and TAPE$volume-label is assigned to a
tape drive.
When you use the MOUNT command, the system checks that the device is not
allocated to another user, and that the volume is loaded on the device speci-
fied. The label on the volume is compared to the label you have specified.
A.8.1 Mounting Disks
Certain disk volumes on VAX/VMS systems are considered public volumes. These
disks are mounted with the /SYSTEM qualifier during system startup. An
example is the disk volume VAXVMSRL3 which contains components of the VMS
operating system. Users do not need to issue an additional MOUNT command for
public volumes.
Disk volumes that are not considered public must be mounted by users. The
MOUNT command allocates the device to the user. If several users need to
have simultaneous access to a disk volume, it must be mounted with the /SHARE
qualifier.
4.8.2 Allocating Tape Drives
All tape drives are permanently allocated to TAPESYS, the Tape Management
System. No user allocation is required. (See Section 5.4, TAPESYS Tape
Management System.)
4.8.3 Mounting Tapes
The mounting of tape volumes may require the assistance of various qualifiers,
In VAX/VMS systems, the default tape label is based on Level 3 of the ANSI
standard for magnetic tape labels (ANSI X3.27-1978). If you want to mount a
tape that was not created on a VAX/VMS system, use the /FOREIGN qualifier.
The program used to read the tape must be able to process any volume labels
because the VAX/VMS operating system does not provide an ancillary control
process to do this.
If you are mounting an ANSI tape created on a computer other than a VAX, use
the /OVERRIDE-identification option to signify a non-VAX tape. IBM and
Sperry should also use the /NOHDR3 option since they only support through
Level 2 of the ANSI standard.
4-9
-------
If you mount a foreign tape volume, you oust use the /BLOCKSIZE-n qualifier
to designate the block size. The default block size for foreign tapes is 512
bytes; valid values are In the range 18 through 65,534.
The /RECORDSIZE-n qualifier is used with the /FOREIGN and /BLOCKSIZE-n
qualifiers to read or write fixed length records. The record size must be
less than or equal to the block size.
4.9 LOGICAL NAMES
A logical name is a descriptive word for all or part of a file specification,
or for a physical device. Use of logical names allows device and file Inde-
pendence in program design. The DEFINE command establishes the connection
between the logical name and the equivalent file specification or device.
DEFINE logical-name equivalence-name
For example:
DEFINE INFILE NY_METEOR.DAT
DEFINE SYSSDISK DUAO:
DEFINE SYS$TEST DUAO:[SYSO.SYSTEST]
Logical names and their equivalence name strings can each have as many as 255
characters. A logical name can form all or part of a file specification. If
only part of a file specification is a logical name, it must be the leftmost
part of the file specification. One logical name may be assigned to another
logical name up to a limit of ten levels.
4.9.1 Logical Name Tables
Three logical name tables are maintained by the system.
a. The Process logical name table contains logical names that are
local to a particular process.
b. The Group logical name table contains logical name entries
qualified by a group number. To use Group logical names, you
oust have the same group number in your UIC as the process that
assigned the logical names.
c. The System logical name table contains entries accessible by any
process in the system.
The privileges GRPNAM and SYSNAM are necessary to make entries in the Group
and System logical name tables, respectively.
4-10
-------
A.9.2 Logical Name Displays
The SHOW LOGICAL command will display the contents of the Process, Group, and
System logical name tables. You can use this command with a qualifier to
display the entries in a particular table (e.g., SHOW LOGICAL/PROCESS to show
those logical names defined for your process). You can also show individual
logical names. For example,
$SHOW LOGICAL USER0$DISK
"USER0$DISK"--$2$DUA1:" (System)
*.9.3 Logical Name Translation
Translation is the substitution of an equivalence name for a logical name.
When the system reads a device name or a file specification, It examines the
name or specification to see if the leftmost component is a logical name;
that is, the leftmost alphanumeric character string, Including dollar signs
and underscores and ending in a colon or space, is compared against the
Process, Group, and System logical name tables in that order. If an equiva-
lence name is found, it is substituted for the logical name. For example,
$PRINT SYS$SYSDEVICE:Ioperator1TRANSLATE.MAR
In this example, SYSSSYSDEVICE: is checked to see if it is a logical name.
To request that the system not translate a device name in a DCL command as a
logical name, precede the device name with an underscore character.
4.9.4 Concealed Device Names
DEFINE commands for logical names in which the equivalence name is preceded
by two underscore characters cause that logical name to be displayed by the
system rather than the equivalence name. For example,
SDEFINE SYS$SYSDEVICE DBAO:
Although the SHOW LOGICAL command will indicate that SYS$SYSDEVICE is equiva-
lent to _ DBAO:, other commands, such as SHOW DEFAULT, will display SYSSSYS-
DEVICE. ~"
4.9.5 Default Logical Names
VMS functions by default have logical names In the following format:
xxx$name
The three-character prefix Identifies the system component that uses the
logical name. Certain default logical names are created for each process at
login by VMS. These can be listed by the following command:
$SHOW LOGICAL/PROCESS
4-11
-------
5.0 VAX/VMS UTILITIES
5.1 TEXT EDITORS
The VAX/VMS operating system offers several text editors for creating or
changing files. The VAX systems at NCC have two editors—EDT and EVE—
available to users, with EDT being the default.
5.1.1 EDT
EDT is a very versatile editor offered with the VAX/VMS operating system. It
can be used in keypad node with the DEC VT52 and VT100 terminals, line mode
from hardcopy terminals, or nokeypad mode for video terminals with keyboards
more limited than the VT series. EDT makes use of buffers to store text for
later display or utilization, and allows work with several parts of a file at
a time. During editing, the file contents are protected by creation of a
Journal or temporary file which can be used in case of system failure to
recover the file. You can redefine the function of keys, adapting EDT to
your specific needs. On-line HELP texts are available to explain certain EDT
functions. For example,
$HELP EDIT/EOT (Provides general information about the EDT Editor.)
PF2 key (Provides on-line help while you are editing.)
Complete information on the EDT editor is available in the EDT Editor Manual.
5.1.1.1 Calling EDT
The EDT editor is initiated with one of the following commands:
$EDIT/EDT file-spec
or
$EDT file-spec
At this point, the editor is in line editing mode. To change to the more
versatile keypad mode, enter CHANGE. To exit from keypad mode back to line
editing mode, enter CTRL/Z. To exit from EDT and retain your file, type EXIT.
If you don't want to retain the work from the editing session, use the QUIT
command to leave EDT.
5.1.1.2 EDT Recovery Features
Unless requested not to, EDT creates a temporary file (flie-spec.JOU)
during an editing session. This temporary file is deleted at a normal exit
5-1
-------
from EDT. If the system crashes during the editing cession, you can make use
of the temporary file after system restart by reentering EDT with the /RECOVER
qualifier,
$EDIT/EDT/RECOVER file-spec
You can then proceed with your edit.
5.1.1.3
Entering Commands
Two methods of entering commands are available. Line commands are entered at
the * prompt (using CTRL/2) or the "command" prompt (using gold/command on
the keypad). Keypad commands are invoked by pressing the keys on the numeric
keypad. The PF1 key is a "gold" key vhich allows alternate functions on the
keypad to be used, (see Figure 5-1 below).
Keypad Ediiinjt Key* - VTlOO Terminal*
Keypad Editing Key* - VT52 Terminals
ft
UP
k. '»
1
DOWN
ii
—
LIFT
«»
•OLD
T
PAQE
COMMAND
4
ADVANCE
•OTTOM
1
WOND
CMNOCMC
PM
HELP
H
SECT
nu.
•
•ACKUP
TOP
t
101
OCLIOL
t
0
LINE
•MM UN*
a
PFJ
FNDNJCT
PINO
11
t
APPEND
ME PLACE
CUT
PAST!
a
CHAM
•PCCtNS
1
•ELECT
PF4
DEL I
UNDL
n
DEL W
UNOW
it
OELC
UNOC
INTEP.
INTIP.
flu
OOLD
T
PAOE
COMMAND
4
ADVANCE
•OTTOM
*
1
WOND
BMNOCAM
i
HELP
1C
1
PNDNXT
two
I
•ACKUP
TOP
t
101
OILIOL
t
LINE
OPYNUKE
a
DELL
UNO I
11
t
OELW
UNOW
a
OBtC
UNDC
a
CUT
PASTE
*
•ELECT
SXSCT
t UP
••PLACE
it
4 DOWN
MCT
n
WOKT
•Ptcwa
14
LIFT
APPEND
11
INTEft
•NTEP.
•uss
Figure 5-1. Keypad Editing Keys
For more information on how to use the EDT Editor, refer to the EDT Reference
Manual or the Text Processing section in the User's Manual. An on-line course
is also available by typing the following:
$RUN.EDT2CAI
This course covers all features of the EDT Editor in a comprehensive, easy-to-
understand format.
5-2
-------
5.1.2 EVE
EVE (Extensible VAX Editor) is an editing interface to the VAX Text processing
(VAXTPU). Its capabilities and operation are similar to those of keypad-mode
EDT but also include several unique features such as split-screen editing,
insert and overstrike modes, and the ability to execute DCL commands without
leaving the editor.
5.1.2.1 Accessing EVE
EVE is accessed by typing the command "EDIT/TPU" at the DCL prompt. For ease
of access, it is suggested that the following statement be included in the .
LOGIN.COM file:
$EVE:«EDIT/TPU
This will allow you to access the editor by simply typing "EVE".
5.1.2.2 Terminating EVE
To terminate and save your edited text, use one of the following:
Press CTRL/Z
or
Press the DO key (see Figure 5-2) and then enter the command "EXIT".
To terminate without saving, press the DO key and enter the command "QUIT".
5.1.2.3 Getting Help
As with the EDT Editor, help screens may be accessed by pressing the PF2 key.
5.1.2.4 EVE Recovery Feature
Similar to EDT, EVE will create a temporary Journal file (named FILENAM.TJL)
in which all editing commands are recorded. If the EVE session is interrupted,
the file changes can be recovered by using the /RECOVER qualifier as follows:
$EVE/RECOVER filename
Then proceed with the EVE session. (Note: Some of the last few keystrokes
will be missing due to EVE's storage system.)
5-3
-------
5.1.2.5 Entering Commands
EVE commands are entered using the keypad edit keys or using the DO key and
a command.
Keypad Edit Keys. These keys allow you to perform many useful functions
including the following:
a. Move Cursor. The cursor may be moved by character or by line
using the keypad. The NEXT SCREEN and PREV SCREEN keys allow you
to page through a file in either direction.
b. Cut and Paste. Blocks of text may be moved from one location in a
file to another (or even from one file to another). The procedure
le a follows:
Step 1 - Press the SELECT key and move the cursor to highlight the
text to be moved.
Step 2 - Press the REMOVE key to delete the text.
Step 3 - Move the cursor to the desired location and press the INSERT
HERE key to restore the text.
c* Insert and Overstrike. You may toggle between insert and overstrike
mode by pressing the INSERT-OVERSTR key. Note that the status line
at the bottom of the screen displays the current state.
d. Find Text. Pressing the FIND key causes EVE to prompt for the text
string you wish to find. Type in the text and press , and EVE
will position the cursor at the next occurrence of that text. The
direction of search is determined by the FORWARD-REVERSE key; its
current state is displayed on the status line. To search again for
the same text, press the FIND key twice.
e. Get Help. Pressing the HELP key displays a map of the keypad and
allows you to access help about a key function by then pressing that
key.
Figure 5-2 illustrates the keypad functions and their locations on the VT100
and VT220 terminals.
5-4
-------
Editing K«yt_VT100-Sarias Terminals
I I
cmje
CTKJl
crauv
Editing K«yt—VT200-S«ri*s Terminals
•in
rn
CIM to Son 0 i
Figure 5-2. Editing Keys on the VT100 and VT220 Terminals
5-5
-------
DO key and Command. Pressing the DO key causes EVE to prompt for a command.
Some examples of commands that may be entered this way are as follows:
TOP Moves cursor to the top or bottom of the file.
BOTTOM
MARK Marks current cursor location with an invisible label.
GO TO Cursor may be returned to this position using GO TO
command.
SET LEFT MARGIN Resets margins.
SET RIGHT MARGIN
DEFINE KEY Assigns an EVE command to a single key or control key
sequence.
5.1.2.6 Multiple File Editing
EVE allows you to edit two or more files during an edit session. This is
especially useful if you want to copy text from one file to another. The
procedure is as follows:
$EDIT/TPU filel.txt (Edit the first file.)
press the DO key (Get command prompt.)
GET FILE file2.txt (Create new buffer.)
You are now editing file2.txt. To change back to filel.txt, use the following
procedure:
press the DO key (Get command prompt.)
BUFFER filel.txt (Switch to filel.txt buffer.)
To view what buffers have been created, use the SHOW command.
It is also possible to view two files on your screen simultaneously:
$EDIT/TPU filel.txt (Edit the first file.)
press the DO key (Get command prompt.)
TWO WINDOWS (Splits the screen into two sections; each
contains a copy of filel.txt.)
press the DO key (Get command prompt.)
GET FILE file2.txt (Displays file2.txt in the current window.)
You now have both files displayed on your screen. The command OTHER WINDOW
will move you back and forth between them.
5.1.2.7 Using DCL with EVE
You may execute a DCL command without leaving the EVE Editor by pressing the
DO key and entering 'DCL command-name'. EVE will create a buffer and open a
5-6
-------
window on the screen to display the command and its output. You may then
move the cursor to the DCL window and copy text from the command output to
the file you are editing.
For more information on these and other EVE features, consult the Guide to
Text Processing on VAX/VMS.
5.2 MAIL UTILITY
The MAIL utility program allows you to send messages to other system users
and to read, forward, print, and reply to messages that other users send to
you. Messages that you receive are stored in the message file MAIL.MAI; new
messages are appended to the end of the file.
5.2.1 MAIL Command
The MAIL command invokes the MAIL utility, which responds with the MAIL>
prompt. Among the MAIL commands are the following:
DIRECTORY Lists your MAIL.MAI file by message number,
date, author, and subject.
READ [message no.] Displays a particular message when you supply
the message number, or the next message in
the file.
SEND
Sends a message to a user or users
FORWARD Forwards the last read message to a user or
users.
REPLY Sends a reply to author of the last read
message.
PRINT Prints the last read message.
HELP Displays information on using the MAIL utility
and lists all the commands available.
EXIT Exits from the MAIL utility.
5.2.2 Sending a MAIL Message
The format of the SEND command is:
MAIL> SEND[/qualifier][file-spec]
There are two qualifiers: /EDIT and /LAST. You may specify only one. The
/EDIT qualifier specifies that the EDT Editor be called to edit the message
5-7
-------
you are sending. The /LAST qualifier specifies that the last message that
you sent be used as the text for this message.
The file-spec is the name of the file to be sent by MAIL. If you don't
specify a file, you will be prompted to enter the text of your message.
The MAIL utility first prompts for the name of the user(s) to receive the
message:
To:
You can supply the user name(s), a file name of a distribution list file,
listname.DIS, preceded by an at ((?) sign, or the generic name USER SUPPORT,
as follows: ~~
To: [username,...J[(?listname] [USER_SUPPORT]
MAIL then prompts for the subject of the message:
Subj:
The body of the message follows the subject entry. If you specified a file
in the SEND command, the text of that file becomes the message sent to users.
If you did not specify a file, MAIL prompts:
Enter your message below. Press CTRL/Z when complete.
CTRL/C to quit.
Note that if you are sending a multiline message, once you have pressed the
carriage return at the end of a line, there is no way to change that line.
CTRL/C will abort the whole message and return you to the MAIL prompt. If
you need to compose a lengthy MAIL message, you should use the /EDIT qualifier
to Invoke the EOT Editor.
5.2.3 Reading Your MAIL Messages
The READ command will display messages sent to you. The format is:
MAIL> READ [filename][message-number]
The default file is MAIL.MAI, your MAIL message file. If you specify another
message file, a file type of .MAI is assumed. The message number is the
position of a message in the message file. If you do not specify a number,
the first message in the file will be displayed. If you enter a number
greater than the number of messages in your file, the latest message will be
displayed.
5-8
-------
5.3
PHONE
The PHONE utility allows users to simulate a telephone conversation with up
to five other users, answer a call, display file contents while in a conver-
sation, leave a message, put a caller on hold, hangup, or reject a call.
5.3.1
PHONE Command
The PHONE command invokes the PHONE utility. The terminal responds by
splitting the screen and leaving the cursor at the Z prompt. Some of the
cooands within the PHONE utility are as follows:
ANSWER
DIRECTORY
DIAL/PHONE
FACSIMILE
HELP
MAIL
HOLD/UNHOLD
HANGUP
EXIT
CTRL/G
CTRL/L
CTRL/S
CTRL/Q
CTRL/W
CTRL/Z
Answers the phone when you receive a call.
Lists users available on the system.
Calls another user. (May use either command.)
Allows users to include file contents in the
telephone conversation.
Lists information on the PHONE utility.
Mails a short message to another user.
Places all users on hold or releases them.
Disconnects all current links without exiting
the PHONE utility.
Executes HANGUP and exits the PHONE utility.
Rings the bell of all users in conversation.
Clears the viewport.
Freezes the screen.
Unfreezes the screen.
Refreshes the screen
Hangs up.
5.3.2 Creating a PHONE Conversation
After Invoking the PHONE utility, call another user with the following:
$DIAL [user-name]
5-9
-------
Or to receive a call, enter the following:
$ PHONE ANSWER
Messages will appear Indicating that the phone is ringing the particular user
or that no one with that particular user name Is available at that particular
time. When a connection Is established, the caller can type on his (top half)
screen, and the Information will simultaneously be displayed on the answering
user s (lower half) screen. See Figure 5-3 for a Illustration of the screen
display.
To return to the command line, type 'X'. From the command line, a caller can
add users (DIAL), include contents of a file (FACSIMILE), hangup, or exit.
See Section 5.2.1 for a list of commands available.
If a user wishes to be undisturbed, the DCL command $ SET TERM/NOBROADCAST
does not allows the PHONE utility to Interrupt a session.
I VAX/VMS Phone Facility! 11-SEP-1984
% (command input line)
TAURUS::SMITH
GEMINI::PETERS
Figure 5-3. PHONE Screen Display
5.4 TAPESYS TAPE MANAGEMENT SYSTEM
Tape access and use on the NCC-VAX Cluster is accomplished through TAPESYS, a
Tape Management System (TMS). TAPESYS provides users with an efficient means
of performing many common tape activities. Tape activities may be performed
In two ways: using DCL-like commands, or using menus. The menus are provided
to automate the common procedures of backing up and restoring data to and
from tapes. These and other tasks may also be carried out "manually" by
5-10
-------
using individual commands that could be included in command procedure's,
access the menus, use the command
STMENU
which will display the TAPESYS main menu illustrated below:
To
TAPESYS vA.2
'USER'S TAPE ACTIVITY MENU
Backups Reports
1 Request a Backup via CRT
2 Request a Restore via CRT
5 Inquire on a Specific Tape
7 Modify Notes
8 Free a Specific Tape (or Set)
Q Return to Entry Point
Commands
9 Inquire on All Owned Tapes
10 List Tapes by Scratch Date
11 List Files on Owned Tapes
12 List Files on Sysmgr's Tapes
V Display TAPESYS Version
T Standard Tape Command
5.4.1 VAX Tape Label Policy
An important feature of TAPESYS is the increased security it provides tape
users, thereby reducing the risk of accidentally mounting and overwriting
someone else's tape. TAPESYS does this by verifying that the tape number
requested for mounting matches that tape's intern*! label. If they do not
match, the operator will be notified of the discrepancy, an<\ T^PHSYS will
him to either confirm or abort the mount. If the tape involved is an 099xxx
or higher series VAX tape, the mount request will be aborted. VAX tape
policy requires that all such tapes have matching internal and external
labels; users should therefore exercise care when performing tape operations
that could potentially alter the tape's label. Other tapes, such as D-tapes,
are mounted regardless of label status. Users who experience problems mounting
tapes should contact User Support for assistance (see Appendix A for telephone
numbers).
5-11
-------
5.4.2 Allocating a Tape from Scratch
Users may allocate new tapes by typing the command TAPE ALLOCATE at the DCL
"$" prompt. TAPESYS will then prompt for:
- The quantity of tapes desired.
- The tape format. This identifies the format of the data you plan
to put on the tape. Valid formats, are BACKUP, LABELLED, UNLABELLED,
EBCDIC, and ASCII. Tour choice has no physical effect on the tape,
but is recorded in the information TAPESYS keeps about the tape.
- Note; This can be up to 64 characters of Identifying Information
associated with a tape.
The system will assign a tape and display a summary of Information about it.
The tape will be prelnltialized with a density of 6250 and an internal label
Identical to its external label (reel number). The tape's scratch date will
be set to 5 days from the date of allocation.
You may change the format and notes associated with an allocated tape at any
time by using the TAPE MODIFY command, as shown below:
$TAPE MODIFY/FORMAT reel-id format
5TAPE MODIFY/NOTES reel-id notes
5.4.3 Freeing a Tape Back to Scratch
An allocated tape will be returned to scratch automatically when its scratch
date arrives. A user may also free a tape as soon as it Is no longer needed
by using the following command:
STAPE FREE reel-id
where "reel-Id" is the tape's number.
5.4.4 Inquiring about Tapes
Several commands are available to provide information about tapes currently
allocated to you:
To obtain a detailed listing of information about a specific tape:
$TAPE INQUIRE reel-id
To obtain a summary of ALL tapes allocated to you:
STAPE INQUIRE SUMMARY
To obtain a listing of your tapes sorted by scratch data:
$TAPE INQUIRE FORECAST
5-12
-------
5.4.5 TAPESYS Automated Backup and Restore Functions
TAPESYS provides an automated oenu-driven facility for backing up and restoring
files from tape. These are accessed through Options 1 and 2 on the main
TAPESYS menu. The backup and restore request aenus are shown in Figures 5-4
and 5-5, respectively.
6P32'c TAPESYS V4.2 BACKUP SCREZN
4»F2-H*t, TAB forvartf, BACKSPACE backward, RETURN to send, *
Fifes to be included fuse arrevs to scroTt)
Fflestob* excluded (use «rrovs te scroll)
Qu»lif >«r*
0«t» options
Q1 Nont
2 Btfor*
3 Sine*
Vortfy B»ekup
Us* CRC?
Mtiahz* <«p»?
locks
Uc* /LOG
Online Oirtctory
R*»l fit*
Scratch d*t*
Tap* Notts
Figure 5-4. TAPESYS V4.2 Backup Screen
SP/32's TAPESYS V4.2 RESTORE SCREEN
-------
Use the tab and backspace keys to move between fields and supply the requested
Information. The PF2 key will provide help with any item, and the tilde
character (f ) can be used to quit at any prompt. When complete, press
RETURN. Tour request is processed automatically as a batch Job. The operator
will be notified to hang the appropriate tape, the backup or restore operation
will be completed, and the system will respond to you with a VMS MAIL message.
5.A.6 Using Backup and Restore Commands
Backup and restore requests may also be entered in command form Instead of using
the menus. To request a backup in this manner, use the following command:
$TAPE BACKUP/qualifiers files
where "files" is the list of files to be backed up and where "qualifiers"
include the same parameters that may be specified through the menu:
/BAckup /BEfore»time /CRC /Density-density
/CREated SINce=time /Fast /EXClude-files
/EXpired /Initialize /Owner_ulc[-uic]
/Modified /Log /Reel-reed_id
/Record /SAve__set«save__set
/Verify /SCRAtch-time
/INit /SIze-reel_size
To'request a restore, use the following command:
$TAPE RESTORE/qualifiers reel-id saveset output_file
where "reel-id" is the tape number, "saveset" is the backup saveset name,
"output_flie" is the file name to which files will be restored, and
"qualifiers" may Include any of the following:
/New__version /Crc /OWner__uic[-uic]
/OVerlay /Log /Select-files
/REPlace /Verify
5.A.7 Interactive Tape Use
At times, you may wish to have a tape mounted for purposes other than the
automated backup and restore procedures described above. For example, you
might have a FORTRAN program that requires the use of a tape. In this case,
you must interactively request the operator to load the tape.
5-14
-------
First, you must request that a tape drive be allocated to your process. Use
the following command:
$ TAPE SELECT drive reel-id
where "drive" is a name of your choosing which will become a logical
name for the tape drive you are assigned and where "reel-id" is the tape
number of the tape you intend to mount.
Note that TAPESYS will recognize only VAX system tape numbers. If you are
going to use a B-tape or other foreign tape, specify the keyword BTAPE Instead
of the reel-id. Examples are:
$ TAPE SELECT MYDRIVE 099123
$ TAPE SELECT MYDRIVE BTAPE
After entering this command, your terminal session will be suspended until
the operator responds to your request. If all tape drives are in use, requests
are answered in the order they were received, as drives become available.
When a tape drive has been assigned, you can request the operator to load
your tape with the following command:
$ TAPE LOAD drive reel-id
where "drive" is the same drive you specified in the TAPE SELECT command
and where "reel-id" is the tape number (specify a B-tape number here, if
applicable).
If you wish to write-enable the tape, add the qualifier /RING. Following is
an example:
$ TAPE LOAD/RING MYDRIVE 099123
This command will request the operator to mount tape 099123 on the previously
selected tape drive with a write-ring.
When the operator completes your request, you will receive a message inaieating
that the tape is mounted. However, the TAPE LOAD command does not perform a
VMS MOUNT of the tape. You must Issue a MOUNT command separately—for example:
$MOUNT MYDRIVE 099123 SAMPLE
When you are finished using the tape, dismount it with the DISMOUNT command
and deallocate the tape drive with the DEALLOCATE command—for example:
SDISMOUNT MYDRIVE
SDEALLOCATE MYDRIVE
5-15
-------
5.A.8 Summary of TAPESYS Functions
The following table summarizes the TAPESYS functions:
Task Command
Get a new tape. TAPE ALLOCATE
Allocate a tape drive. TAPE SELECT
Deallocate a tape drive. DEALLOCATE drive name
Request a tape be mounted. TAPE LOAD
Mount a tape. MOUNT drive volume logical
Dismount a tape. DISMOUNT drive
Perform a backup. TAPE BACKUP or TMENU (menu driven)
Recover from backup. TAPE RESTORE or TMENU (menu driven)
Initialize a tape. INITIALIZE device label (Tapes are
preinitialized when allocated.)
5.4.9 Help
Further information and help is available on-line. These may be displayed with
the following commands:
$HELP TAPESYS
and
$HELP TAPE
5.5 BACKUP UTILITY
The BACKUP utility is used for making backup copies of files. A backup may
be made to disk, but it is usually made to tape, often for purposes of trans-
porting the files to another system. When backing up to tape, files are
stored in a special format called a "saveset," which can only be read with
the BACKUP utility. The format of the command is:
BACKUP input-specifier/qualifiers output-specifier/qualifiers
The BACKUP utility determines that it is to perform a SAVE, RESTORI, or COPY
operation based on the devices and qualifiers used in the above command.
5-16
-------
Note; Users should realize that the TAPESYS Tape Management System described
in Section 5.4 serves as an easy-to-use Interface to the BACKUP utility
(with regard to tape backups). In most cases, its use is considered
preferable to Issuing BACKUP command6 directly. TAPESYS has a
significant advantage in that it maintains an on-line file directory,
allowing you to display the contents of a tape made with TAPESYS
without having to actually mount the tape.
5.5.1 BACKUP Qualifiers
BACKUP qualifiers can be categorized as command qualifiers or input or output
qualifiers. Three useful command qualifiers are:
/LIST[-filespec] This qualifier lists the names of files con-
tained in a save-set. You can use the /FULL
qualifier with the /LIST qualifier in order to
list information about each file in the form
of the DCL command DIRECTORY/FULL. The default
qualifier for /LIST is /BRIEF, which lists
each file's creation date and size in blocks.
If no file spec is given with /LIST, the
default is SYS50UTPUT.
/LOG This displays at SYS$OUTPUT, the file specifi-
cation of each file processed.
/VERIFY This qualifier for BACKUP performs data verifi-
cation after backing up or restoring by com-
paring Input and output media.
Several useful output qualifiers are:
/BLOCK_SIZE-n This specifies the block size in bytes. The
minimum is 2048 bytes; the maximum is 65,535
bytes. The default block size for tape is
8464 bytes; for disk, 32,528 bytes. On tapes,
BACKUP ignores any block size defined in the
DCL command MOUNT. Note that it is possible
for a tape to run off the end of its reel if
the block size is set to a large value.
/DENSITY-n The density qualifier specifies the recording
density of an output tape. The default density
is the current one on the tape drive addressed.
The density value must be supported by the
hardware.
5-17
-------
/LABEL-(stringI,...]) This specifies the volume label for a save-set
written on tape. The string oust be from one
through six alphanumeric characters. By default,
the label will be derived from the save-set-
naote. Tape volumes are numbered beginning at
01.
5.5.2 BACKUP Utility Examples
To create a backup tape copy of the directory [EPAWORK] and all its sub-
directories on a tape labeled JAN15SAVE.BCK
5BACKUP (EPAWORK...J* TAPE:JAN15SAVE.BCK
All files in [EPAWORK] and in all its subdirectories will be Included. Note
that the tape must have been mounted with MOUNT/FOREIGN.
To create a backup using more than one tape device, you must specify the
save-set-name with the first device only. Separate the other devices with
commas. For example,
$BACKUP [EPAWORK...]* MTAO:JAN15SAVE.BCK,MTA1:
To restore all files in a save-set to a directory (e.g., from the tape volume
JANJ5SAVE.BCK to the directory [EPAWORK] and corresponding subdirectories) use
SBACKUP TAPE:JAN15SAVE.BCK [EPAWORK...]
If you wish to restore a specific file, use the /SELECT qualifier. For
example, to restore the file METHAN.DAT to the subdirectory
[EPAWORK.ORGANIC.ATMOSPH] from the tape JAN15SAVE.BCK, use
5BACKUP MTAO:JAH15SAVE.BCK/SELECT-[EPAWORK.ORGANIC.ATMOSPH]-
METHAN.DAT METHAN.DAT
If you are restoring a few files from a large save-set, it is advisable to
use the /LOG qualifier. BACKUP will continue to process the save-set until
It reaches the end. Once the files you need have been restored, you can
terminate the RESTORE with CTRL/Y.
5.6 LIBRARIAN UTILITY
The LIBRARIAN utility provides the user with easy access to libraries which
are Indexed files containing frequently used code or text modules. There are
five library types and each library is comprehensively indexed regarding its
•odules, their location, and modification history.
5-18
-------
The five kinds of libraries are:
HELP (File Type HLB)
MACRO (File Type MLB)
OBJECT (File Type OLE)
SHAREABLE IMAGE
(File Type OLB)
TEXT (File Type TLB)
Contains nodules that provide Information
about editors, programs, utilities, etc.
Contains macro definitions used as input to
the Assembler whenever the Assembler encounters
a macro not.defined In a source program.
Contains frequently called routines used as
Linker Input. The Linker searches the object
module library if it encounters a reference
that it cannot resolve from the input flle(s).
Contains the symbol tables of shareable
Images used as Linker input.
Can contain any sequential record files that
are retrieved as data for programs.
5.6.1 Creating and Maintaining Libraries
The LIBRARY command maintains libraries. With various command qualifiers, it
can be used to create, delete, or modify libraries, and to Insert, delete,
extract, and list library modules and symbols. The format of the LIBRARY
command is:
$LIBRARY/qualifier(s) library-file-spec linput-file-spec[/-
MODULE-module-name][,...]]
Where:
/quallfier(s)
library-file-spec
input-flie-spec[,...]
/MODULE-module-name
Functions to be performed. More than one,
if compatible, can be designated.
Name of library to be created or maintained.
Name of file containing modules to be inserted
in the specified library.
Name of a text module you want to insert or
replace.
5-19
-------
5.6.2 LIBRARIAN Routines
The LIBRARIAN provides 25 routines that user programs can call to:
. Initialize a library.
. Open a library.
. Locate a key in a library.
. Insert a new key in a library.
. Return the names of the library's keys.
. Delete a library key and associated text.
. Read text records.
. Write text records.
For complete information on LIBRARIAN routines, refer to Sections 10.5.1
through 10.5.25 in the VAX-11 Utilities Reference Manual.
5.7 DIGITAL STANDARD RUNOFF (DSR)
Digital Standard Runoff (DSR or RUNOFF) is a text formatting facility designed
to create a formatted document Including a table of contents and index. The
user accesses a text editor to create or edit a file, invokes RUNOFF to
process the file and format the text, and then prints the file. Commands
specify the format of text (size of pages, right justification, line spacing,
etc.) Flags emphasize text through special characters such as capital letters,
spacing of text, and others. The DCL command RUNOFF processes the file and
controls certain characteristics of the file. The utilities for the table of
contents and index allow a quick method to create both.
The DSR commands always begin with a control flag (.) which must be In column
1 of a line unless it follows another command in the same line. (Multiple
commands on the same line are permitted.) A keyword follows the flag to
specify the function. Arguments can follow certain functions and are separated
by commas or spaces. A terminator (;) ends the command or string of commands.
After using DSR to format a file, use the DCL PRINT command (see Section 4.6)
to output the file.
For more details refer to the VAX Digital Standard Runoff Reference Manual.
5.8 DIFFERENCES
The DIFFERENCES facility compares two disk files on a record to record basis
to find if they are identical and, if not, list how they are different. The
DIFFERENCES session can be tailored to ignore data, control the format of the
output listing, and control the extent of the comparison by using command
qualifiers.
5-20
-------
5.8.1 DIFFERENCES Command
The format of the DIFFERENCES command is as follows:
DIFFERENCESI/qualifiers] naster-file-spec Irevision-file-spec]
If no revision-file-spec (the file that is to be compared to) is specified,
the next lover version of the master-file-spec will be compared.
The most common qualifiers are as follows:
/COMMENT_DELIMITER[-delimiter] Specifies comment delimiters which are to be
ignored (comma, exclamation point, etc.).
/IGNORE-(optlon) Specifies special characters, strings, or
records to be Ignored.
/MATCH-size Specifies the number of records that constitute
a match.
/MAXIMUM_DIFFERENCES-n Terminate DIFFERENCES after a specified number
of unmatched records are found.
/MERGED[=n] Create an output file containing a merged list
of differences with matched records.
/[NOJNUMBER Controls whether line numbers are generated in
the listing.
/OUTPUT!-file-spec] Defines an output file for listing rather than
the SYS$OUTPUT default.
/PARALLELl-n] Creates a parallel list of differences with a
number (n) of matched records.
/SEPARATED!-input-file] Creates sequential lists of unmatched records
from specified input files.
/WINDOW-size Controls the number of records to search before
listing a record as unmatched.
5.8.2 Examples
The following examples are from the DCL Dictionary. For more detailed
Information, refer to the section on DIFFERENCES in the DCL Dictionary.
In the following example, the DIFFERENCES command compares the contents of
the two most recent versions of the file EXAMPLE.TXT in the current default
directory. DIFFERENCES compares every character in every record and displays
the results at the terminal.
5-21
-------
S DIFFERENCES EXAMPLE.TXT
************
File DISK1:[GEORGE.TEXT)EXAMPLE.TXT;2
1 DEMONSTRATION
2 OF V3.0 DIFFERENCES
3 UTILITY
******
File DISK1:IGEORGE.TEXTJEXAMPLE.TXT;!
1 DEMONSTRATION
2 OF VMS DIFFERENCES
3 UTILITY
************
Number of difference sections found: 1
Number of difference records found: 2
DIFFERENCES/MERGED-1-
DISK1:[GEORGE.TEXTJEXAMPLE.TXT;2
DISK1:(GEORGE.TEXTJEXAMPLE.TXT;1
In the next example, the DIFFERENCES command compares the same files as in
above but ignores all comments following the first 'V encountered by
DIFFERENCES. The command also specifies that an 80-column parallel list of
differences be displayed.
$ DIFFERENCES/PARALLEL/WIDTH«80/COMMENT_DELIMITER-"V" EXAMPLE.TXT
File DISKI:(GEORGE.TEXTJEXAMPLE.TXT;2 | File DISK1:[GEORGE.TEXTjEXAMPLE.TXT;!
I j
DEMONSTRATION I DEMONSTRATION
Number of difference sections found: 1
Number of difference records found: 1
DIFFERENCES/IGNORE"(COMMENTS)/COMMENT_DEL1MITER-("V")/WIDTH-80/PAKALLEL-
DISK1:(GEORGE.TEXTJEXAMPLE.TXT;2-
DISK1:[GEORGE.TEXT J EXAMPLE.TXT;1
5.9 SORT
The SORT utility sorts records in Input files based on the fields defined in
the SORT command. It generates a reordered output file specified in the
command. Unless specified otherwise, the entire record will be sorted as a
whole. By using qualifiers, the sort can be tailored to the user's needs.
5-22
-------
5.9.1 SORT Command
The format of the SORT command is as follows:
SORT[/qualifiers] input_file(s) output_file
The most common qualifiers are as follows:
/KEY-(POSITION:n,SlZE:n) Specifies the starting position of the field
the file is to be sorted on and the size of
that field.
/KEY-(....ASCENDING) Will sort in ascending order.
/KEY-(....DESCENDING) Will sort in descending order.
/(NO]DUPLICATES By default SORT will keep records with duplicate
keys.
5.9.2 Examples
This will sort on the first eight characters of the file and output to
DATA2.LIS.
S SORT/KEY-(POSITION:!,SIZE:8) DATA1.LIS DATA2.LIS
The next example will sort in ascending order on the field from position 8 to
position 27.
$ SORT/KEY-(POS:8,SIZ-20,ASCENDING) STAT.LIS STAT2.LIS
The last example will sort on the entire record and not allow duplicates in
the output file.
$ SORT/NODUPLICATES PERSONNEL.DAT PERSONNEL2.DAT
5-23
-------
6.0 PROGRAMMING LANGUAGES
Two programming languages are offered on the NCC VAX systems:
Language File Type
VAX-11 FORTRAN .FOR
VAX-11 MACRO . .MAR
For convenient operation, source programs should have the standard file type
recognized by the appropriate language compiler.
Agency policy stresses the use of high-level languages whenever possible.
6.1 VAX-ll FORTRAN
FORTRAN (FORmula TRANslator) is a high-level programming language used pri-
marily for applications which involve extensive mathematical calculations.
The American National Standards Institute (ANSI) has defined a standard
FORTRAN. The FORTRAN language available on VAX/VMS systems is called VAX-11
FORTRAN and is based on ANSI FORTRAN-77 (ANSI X3.9-1978). Some extensions to
ANSI FORTRAN-77, as well as support for programs written under ANSI X3.9-1966
standards, are included.
VAX-11 FORTRAN is a compatible superset of DEC's PDP-11 FORTRAN-77, so you
can compile existing PDP-11 FORTRAN-77 programs using the VAX-11 FORTRAN
compiler. FORTRAN upgrades usually occur when the VMS operating system is
upgraded.
6.2 VAX-11 MACRO ASSEMBLY LANGUAGE
MACRO is the assembly language for VAX/VMS systems. The Assembler reads a
file of MACRO statements and produces relocatable object code suitable for
linking to other object modules, if necessary, by the VAX-11 LINKER to create
an executable image.
Refer to the VAX-11 MACRO User's Guide and the VAX-11 MACRO Language Reference
Manual for additional Information on the MACRO assembly language.
6.3 VAX-11 SYMBOLIC DEBUGGER
The VAX-11 Symbolic Debugger is an interactive tool that allows programmers
to debug source programs in COBOL, FORTRAN, or MACRO assembly language. It
Is called a symbolic debugger because you can refer by symbols to program
locations. Data can be displayed or entered in several formats. Version 3
of the Debugger is available on the VAX systems at NCC. Users should refer
to the VAX-11 Symbolic Debugger Reference Manual, the VAX-11 COBOL User's
Guide, or the VAX-11 FORTRAN User's Guide for additional information.
6-1
-------
6.3.1 Calling the Debugger
Programs that you intend to debug should be compiled and linked with the
/DEBUG command qualifier:
$FORTRAN/DEBUG file-spec
$LINK/DEBUG file-spec
The COMPILE command controls whether the compiler makes local symbol table
and traceback information available. Using the /DEBUG qualifier in the LINK
command Includes them in the executable image as veil. The RUN command will
call the Debugger and leave you at the Debugger prompt, DBG>:
$RUN file-spec
VAX-11 DEBUG Version 3.0
XDEBUG-I-INITIAL, language is xxx .module set to 'file-spec*
DBG>
Alternately, if your program is running without Debugger control and you want
to call the Debugger, interrupt the running program with CTRL/Y and give the
DEBUG command:
$RUN file-spec
CRTL/Y
$DEBUG
If you interrupt a running program and enter the DEBUG command, you will not
know which instruction was executing. The instruction can be determined by
the SHOW CALLS command:
$DEBUG
VAX-11 DEBUG Version 3.0
ZDEBUG-I-INITIAL,language is xxx .module set to 'file-spec'
DBOSHOW CALLS
At the initiation of a debugging session, the language, xxx, in which the
program (module) being debugged is written will determine certain parameters
for the Debugger. These language-dependent parameters are MODE, OUTPUT,
STEP, and TYPE.
6-2
-------
6.3.2 Debugger Commands
The format for Debugger commands Is:
DBG>command[keyword][operand[.operand]...)
The Debugger commands and their functions are as follows:
CANCEL [keyword] Removes one or more specified items from the
debugging session.
DEFINE Assigns a symbolic reference to a virtual
address.
DEPOSIT Changes the contents of specified addresses.
EVALUATE Calculates the value of a specified expression
or address.
EXAMINE Displays the content of addresses.
EXIT Ends the debugging session.
GO Initiates program execution, or continues to
either the next breakpoint or watchpoint.
HELP Displays information about the Debugger
commands.
SET [keyword] Establishes parameters for the debugging
session.
SHOW [keyword] Displays information on the debugging session.
STEP Initiates program execution and continues for
a specified number of instructions.
The acceptable keywords for the CANCEL, SET, and SHOW commands are:
ALL
BREAK
LANGUAGE
MODULE
SCOPE
STEP
TRACE
WATCH
6-3
-------
7.0 APPLICATION PACKAGES
7.1 STATISTICAL ANALYSIS SYSTEM (SAS)
SAS was originally a statistical package, but has evolved into a more general
data analysis system. SAS reads data from disk or tape and then organizes
the values into a SAS data set which contains both the data and its descrip-
tion. The data set can be combined with other data sets, analyzed statis-
tically, and Incorporated into reports. SAS produces both preformatted
reports and user-formatted reports.
SAS was developed for the IBM 370/30XX/43XX environment in batch and Inter-
active mode and is now being issued in a version capable of running under
the VAX/VMS operating system. The VAX systems operated at NCC offer this
version and SAS/GRAPH. Further Information can be found in:
Document Title Order // Price
SAS User's Guide: Basics, Ver. 5 Edition 5003 $19.95
SAS Introductory Guide, Third Edition 5685 $ 4.95
SAS Companion for the VMS Operating System,
1986 Edition 5701 (call)
Technical Report P-138: Using SAS Ver. 5
under VMS 5970 $ 4.95
SAS/GRAPH User's Guide, Ver. 5 Edition 5616 $28.95
SAS/GRAPH Guide to Hardware Interfaces,
Ver. 5 Edition 5638 $ 9.95
The above information is subject to change; call to verify current prices.
These documents and all other SAS documentation may be ordered from:
SAS Institute, Inc.
Publications Sales Department
Box 8000, SAS Circle
Gary, NC 27511-8000
(919) 467-8000, ext. 7001
7-1
-------
7.2 FOCUS
FOCUS, ^ a fourth-generation language, is a complete "information control
system" with comprehenive features for entering, maintaining, retrieving, and
analyzing data. The nonprocedural FOCUS language was designed to replace
traditional programming languages In most applications programming situations.
The simplicity of the command syntax in the language stems from the fact that
It uses simple English phrases. FOCUS is invoked with the following command:
$ FOCUS
The NCC Training Department offers a course in FOCUS on the VAX (see Section
2.4.3.3). Also, the following comprehensive documentation is available
directly from the vendor:
Document Title Order # Price
FOCUS Users Manual for VAX/VMS DN40228 $40.00
Simultaneous Usage Facility for VAX DN40288 $ 7.50
Subroutine Library Users Manual DN40384 $10.00
Host Language Interface Users Manual DN40285 $ 7.50
This information is subject to change; call to verify current prices. The
docucientation above and all other FOCUS documentation may be ordered from:
Publications Order Department
Information Builders, Inc.
1250 Broadway
New York, NY 10001
(212) 563-9120
7.3 TCKTRONIX LIBRARY
A Tektronix library is available for graphics applications in conjunction
with a graphics (4010 or 4014) terminal. To use this library the program
should be linked with the following file specification which calls the library
routines:
US£R2$D1SK:[UGL]UGT
The link statement has the following format:
LINK program-name,file-spec/LIB
For example,
LINK TEKDEMO,USER2$DISK:(UGLJUGT/LIB
7-2
-------
7.4 INTERNATIONAL MATHEMATICAL AND STATISTICAL LIBRARY (IMSL)
IMSL is a set of mathematical and statistical routines for use in FORTRAN
programs. The IMSL libraries consist of three separate but coordinated
libraries that allow easy user access:
MATH/LIBRARY general applied mathematics
STAT/LIBRARY statistics
SFUN/LIBRARY special functions
The IMSL libraries on the VAX Cluster can be referenced with the logical name
"IMSL" and can be linked as follows:
LINK program_name,IMSL/LIB
Most of the subprograms are available in both single and double precision
versions. The following is a general discussion of IMSL subroutine capabilities
a. Analysis of Experimental Design Data; Contains several of the
subroutines which form the essential parts of application programs.
Performs the basic computations for the analysis of data and several
types of experimental designs.
b. Basic Statistics; Components of application programs.
c. Categorized Data Analysis; Provides for the analysis of categorized
data.
d. Differential Equations, Quadrature Differentiation; Differential
equation solver, quadrature, cubic spline, and bi-cubic spline type
subroutines.
e. Elgenanalysis; Provides for computation of all eigenvalues and
(optionally) all eigenvectors of a Complex, Hermition, Real, or
Symmetric matrix.
f. Generation and Testing of Random Numbers, Goodness of Fit; Aids in
testing pseudo-random deviates for randomness and in producing ran-
dom deviates.
g. Interpolation, Approximation, and Smooth; Provides for cubic spline
interpolation, approximation, and smoothing.
h. Linear Algebraic Equations; Provides for solutions of linear equa-
tions, matrix inversion, decomposition, substitution, Improvement,
and rectangular matrix abilities.
1. Mathematical and Statistical Functions; Allows calculations of
probabilities associated with various distribution functions. Also
provides for computing the inverse of certain probability distribu-
tion functions.
7-3
-------
Non-Parametric Statistics:
talning to population.
Provides statistics on hypotheses per-
k. Observation Structure. Multivarlate Statistics; Allows testing for
Independence of sets of normally distributed variables, finds princi-
pal components of a sample of nultivariate observations, estimates
the mean and variance from a grouped or censored normal sample, and
performs a complete factor analysis.
1* Regression Analysis: Designed to be useful in developing versatile
application programs of three general types - multiple linear regres-
sion analysis, stepvise linear regression analysis, and curvilinear
regression analysis.
m. Sampling; Used in developing application programs in the general
areas of acceptance sampling, preference testing, and survey sampling,
n. Vector-Matrix Arithmetic; Provides for matrix arithmetic as well as
vector sort.
o. Forecasting, Econometrics, Time Series, and Transforms; Eighteen
subroutines perform time series analysis. Among these are efficient
algorithms for generating time series from a given ARIMA stochastic
model and other Box-Jenkins type calculations.
p. Utility Functions
q. Zeros and Extreme, Linear Programming
For detailed Information on the use of IMSL, the following documentation is
available directly from the vendor:
Document
MATH/LIBRARY
User's Manual (3 vols. in 3-ring binders)
User's Manual (1 vol., soft cover)
Quick Reference
SFUN/LIBRARY
User's Manual (1 vol. in 3-ring binder)
User's Manual (1 vol., soft cover)
Quick Reference
STAT/LIBRARY
User's Manual (3 vols. in 3-ring binders)
User's Manual (1 vol., soft cover)
Quick Reference
Product Code Price
MALB-USM-3RING $45.00
MALB-USM-PERFCT $15.00
MALB-QRF $ 1.00
SFLB-USM-3RING $15.00
SFLB-USM-PERFCT $ 7.00
SFLB-QRF $ 1.00
STLB-USM-3RING $45.00
STLB-USM-PERFCT $15.00
STLB-QRF $ 1.00
7-4
-------
The preceding information is subject to change; call to verify current prices.
The vendors*s address is:
IMSL, Inc.
2500 ParkWest Tower One
2500 CltyVest Boulevard
Houston, TX 77041-3020
(713) 782-6060
7-5
-------
8.0 COMMUNICATION PACKAGES
8.1 KERMIT-32
KERMIT-32 is a file transfer protocol designed for the Digital Equipment
Corporation VAX series computers under the VAX/VMS Version 3 or higher opera-
ting systems. It stores data based on standard VAX file specifications unless
otherwise specified. The file specifications, record attributes, and record
type are the major factors affecting the execution of KERMIT.
KERMIT can be run interactively by invoking the program or by a single command
at Level 0 of DCL (if a foreign command is defined such as KERMIT:-$KERMIT).
Command keywords can be abbreviated to the shortest prefix that still makes
them unique.
On-line documentation is available for user retrieval and can be accessed by
reading the following files:
VAXTM1::$2$DUA0:(KERMITjKERMlT.DOC
VAXTM1::$2$DUA0:IKERMIT]VMSV3.DOC
VAXTM1::$2$DUA0:[KERMITjVMSV31AN.DOC
The following is an example of a KERMIT session:
At the Personal Computer (PC) prompt (usually », type:
KERMIT
KERMIT will be invoked. Then type at the KERMIT prompt (also »:
SET BAUD 1200
CONNECT
Enter the access telephone number, for example:
ATDTA642
Note; DO NOT USE THE 'TAKE IBM/SPERRY1 OPTIONS!
Connect messages and then the menu will be displayed. Choose the option for
the VAX machine:
Selection: VAX [may not echo on screen]
Then you can log onto the VAX (see Section 4.1.1 for more information) and
establish the server mode:
$KERMIT
KERMIT-32> SERVER
CTRL/JC
8-1
-------
Server node has now been established and you are now back to the local (PC)
level. Use any commands desired at this point, such as:
>REMOTE DIR (lists files on the remote VAX directory]
>GET filename
When you are finished with the remote directory files, enter the following at
the prompt:
BYE flogs off remote VAX system]
or
FINISH [disconnects server mode]
and
CONNECT [connects back to VAX]
$LO [log off or any other DCL command]
CTRL/JC [returns to PC level]
>EX1T
8.2 CROSSTALK
Crosstalk is a communication package residing on standard EPA personal computers
allowing users to access other systems from a microcomputer through dial-up
lines. Its two major functions are a terminal look-alike program and a file
transfer program. The terminal program emulates the compatible terminal for
the mainframe it is communicating with. The file transfer capability allows
a user to access another system with or without Crosstalk and transfer any
type of file from system to system. Files can be stored on disk or in the
memory of the microcomputer.
Crosstalk is menu-driven and allows several options for the user as well as
the capability of tailoring the menu to a specific application. Commands are
entered at the bottom of the screen to change terminal characteristics, dial
a system, display information, or transfer information.
8.2.1 Crosstalk Command Files
Command files can be created for frequently used sequences of commands. A
list of command can be stored in a file and executed by typing the following:
XTALK file-name
8-2
-------
Listed below are examples of some common commands used:
Command
NAME
NUMBER
SPEED
PARITY
DATA
GO R 30
SLEEP
RQUEST
XMIT
BYE
LOAD
KERMIT
Value
VAX
4642
1200
None
8
MESSAGE.TXT
MORE.TXT
ANOTHER.TXT
Comments
System name
Dial-up number
Modem speed
8 bits, no parity
Dial every 30 seconds
Kill 5 seconds
Get this file
Send this file
Bang up
Go do another file
Goes into KERMIT Mode in
Crosstalk Version 6 (see
Section 8.1)
8.2.2 Running Crosstalk
a. From the standard EPA menu on the PC, choose F4.
b. Establish a connection (using NU 4642).
c. Choose option on the menu for the system to be accessed.
d. Enter "GO" at the prompt.
e. Log into the system (see Section 4.1.1 for more details about login.)
f. Press the escape key to get the Crosstalk command line.
8-3
-------
g. At the Crosstalk command line, you may use the following commands:
SEND From PC to system accessed without Crosstalk.
XM1T From PC to system with Crosstalk.
CAPTURE From system to PC.
QUIT
When using Crosstalk to emulate a VT100, some functions on the numeric keypad
«ay be moved. Other functions are not supported. These are as follows:
132 column mode
Smooth scrolling
Split screen
Double high characters
Double wide characters
The functions keys PF1 through PF4 normally found on the numeric keypad are
assigned to Fl-FA function keys. The COMMA key on the DEC terminal is
substituted with the asterisk (*) key. CTRL/Backspace works as a DELETE (or
RUBOUT) key. See Figure 8-1 below.
VT-100 Numeric Keypad: Typical PC Keypad:
Figure 8-1. Mapping of VT100 Keypad Application Mode Functions
8-4
-------
The DEC arrow keys can be simulated by separate arrow keys provided on the
PC, by arrow keys specified on the numeric keypad when NUMLOCK Is off (if
NUMLOCK is on, either numeric codes or DEC application codes will be produced),
or by using the ALT keys with the specific keys depicted in Figure 8-2.
Up
Down
Left
Right
VT-100 Arrow Keys:
ALT-
J
ALT-
J .
ALT-
»
ALT-
+
Equivalent CROSSTALK key:
Figure 8-2. Arrow Keys and Equivalent Crosstalk Keys
For more information, see the Crosstalk XVI manual.
8.3
HASP+
HASP+ is a communications software package that allows remote workstations
to transmit data to other workstations or a host computer by behaving as a
remote job entry workstation. It can emulate any multileaving remote job
entry workstation and is therefore compatible with the VAX 8600.
HASP-*- can be run Interactively or can be set up to function with very little
operator Intervention. After it is activated, the operator dials the remote
site and then signs on to that system to begin the communications session.
Data transmission in either direction (multileaving) is automatically started.
The disposition of each stream can be controlled by using various options.
For file transfer, the mode used on the VAX Cluster is REMOTE.
A command procedure has been implemented on the VAX 8600 (VAXTM1) to route
jobs from that system to other machines using HASP. It is used as follows:
$ SEND filename boat-machine
Note; Currently, the only host available is the NCC-SPERRY System, which is
designated as "UNI."
An example of a command to submit a job to the SPERRY would be:
$ SEND TEST.DAT UNI
8-5
-------
A DNX record, which is treated as a comment by the host system, can be added
to the beginning of the job file to route the output of that job back to the
VAX. The format of that record is as follows:
§MSG DNX username USER0SDISK:[directory]filename[/PRINT/SW]
If the DNX card is omitted, the job output .will be routed back to the original
system's printer.
By specifying the user name, a HAIL message will be sent to that user when
the output has been received back from the other system. The file name
specifies where the received job will be copied to. Print qualifiers can be
used to queue the file for printing. Any available qualifier for printing
can be used (see Section A.5 on printing files).
Examples of the DNX card are as follows:
a. @MSG DNX SMT USER0SDISK:[SMTjUSER_FILE.DAT
The received file Is copied into USER_FILE.DAT and a MAIL message is
sent to SMT informing him that a job has returned.
b. 0MSG DNX SMT /PRINT/COPIES-5/NAME-USER_JOB/NOTIFY/NOTE-B045
The received file is queued on the system printer with a banner of
USER_JOB, a bin number specified with /NOTE, and 5 copies made. A
MAIL message is sent to SMT when the job Is queued, and the user is
notified when the print job completes if he is still logged on.
c. @MSG DNX SMT USER0$DISK:[SMT]FILE.DAT/PRINT/HOLD/QUEUE-SYS$PLOT
The received file is copied to the user directory as FILE.DAT and
also queued to the system plotter in a hold state waiting for the
user to do a SET ENTRY/RELEASE command prior to printing. A MAIL
message is also sent to SMT notifying that his Job has been routed
and queued.
You can also check the status of a job with the TEL command. The following
command will display jobs waiting for transmission:
TEL .QUE
If a job listed has an asterisk next to the entry number, it is currently
being transmitted. The others are waiting for transmission. To maximize use
of system resources, communication with the SPERRY system is not continuously
active. The VAX connects to the SPERRY at regular intervals, and any jobs
that have been queued are automatically sent at that time.
For more information on HASP+, see the HASP+ VAX/VMS Reference Manual.
8-6
-------
8.4
DECNET
DECnet is the collective name for the hardware and software products that
allow the VAX to function as one of several Interconnected nodes that make up
a network. Through DECnet, a user who is logged on to one of the network's
nodes is able to access any other node on the network. DECnet may be used to
log on to another node or to access files residing on it.
8.4.1 Displaying the Network
To get information about what nodes are available on the network, type the
following:
$SHOW NETWORK
The current status of all network nodes will be displayed, as shown in the
following example:
VAX/VMS Network status for local node 1.12 VAXTM1 on 31-DLC-1987 09:06:19.37
Node
Links Cost Hops
1.12
1.11
1.20
1.21
1.22
1.30
1.31
1.100
1.101
1.102
1.103
1.120
1.140
1.160
1.161
1.163
1.164
1.165
1.167
1.168
1.175
1.200
1.260
1.270
1.300
1.301
1.302
1.320
1.340
VAXTM1
NCCORD
UVAX
NCCOTS
THULE
SNA001
SNA002
ITVAX1
ITRSX1
ITPC1
ITRSX3
MIS VAX
EMSLRT
NTCEN
NTPHY
NTEP
NTEPIO
NTBEH1
NTSTAR
NTSEB1
NTGAG1
ORE ADC
MUTUAL
MADMAMD
VEGAS
DOSE
AIR
DULUTH
ATHENS
2
4
0
0
0
1
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
12
2
12
11
11
2
11
21
21
11
11
^^^^^_
0
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
2
1
2
2
2
1
2
3
3
2
2
(Local)
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
UNA-1
Next Hop to
Node
1.12
1.11
1.20
1.21
1.22
1.30
1.31
1.100
1.101
1.102
1.103
1.120
1.140
1.160
1.161
1.163
1.164
1.165
1.163
1.168
1.163
1.20
1.20
1.270
1.20
1.20
1.20
1.20
1.20
VAXTM1
NCCORD
UVAX
NCCOTS
THULE
SNA001
SNA002
I TV AX 1
ITRSX1
ITPC1
ITRSX3
MISVAX
EMSLRT
NTCEN
NTPHY
NTEP
NTEPIO
NTBEH1
NTEP
NTSEB1
NTEP
UVAX
UVAX
MADHAD
UVAX
UVAX
UVAX
UVAX
UVAX
8-7
-------
Node
1.360
1.380
1.400
1.401
1.410
1.419
1.440
1.480
1.500
1.520
1.521
NARVAX
CINCY
CORVLS
CORGIS
NSIG1S
NEWPRT
GULFBR
LLRS
ADAVAX
EERF
UEERF
Licks Cost
0
0
0
0
0
0
0
0
0
0
0
11
11
11
14
21
20
11
11
11
11
21
ops Next Hop to
2 UNA-1 ->
2 UNA-1 ->
2 ' UNA-1 ->
3 UNA-1 ->
3 UNA-1 ->
3 UNA-1 ->
2 UNA-1 ->
2 UNA-1 ->
2 UNA-1 ->
2 UNA-1 ->
3 UNA-1 ->
Node
1.20
1.20
1.20
1.20
1.20
1.20
1.20
1.20
1.20
1.20
1.20
UVAX
UVAX
UVAX
UVAX
UVAX
UVAX
UVAX
UVAX
UVAX
UVAX
UVAX
Total of 40 nodes.
8.4.2 Logging on to a Remote Node
To establish communications with another node, you must have a valid User-ID
on the remote system. Type the following command:
$SET HOST oodename
Where nodename is one of the available nodes displayed by the SHOW NETWORK
command. The remote system will then prompt for your username and password.
To return control to your local node, type the following:
SLOGOUT
or press CTRL/Y several times in rapid succession.
8.4.3 Using DCL Commands over the Network
Most DCL commands used to perform file operations at a local node can also be
used to perform these operations on remote nodes. You can obtain file
directory listings, manipulate files, and execute command procedures that
reside on other nodes.
The extent to which you can access the remote system will depend on whether
you are an authorized user on it. If you are not, you will only be able to
access directories and files which permit WORLD access. If you are an
authorized user on the remote node, you will have the same access authority
as you have when you are logged on to that node; however, you must include
your username and password In the remote file specification. The format is:
node"username password"::device:(directory]filename
8-8
-------
Examples ;
1 . User ZZZ on node VAXTM1 wants to get a directory listing of the files he
has on node NARVAX, where his username Is also ZZZ and his password Is
"1A2B3C". While logged on to VAXTMl, he enters the following command:
$DIRECTORY NARVAX"ZZZ 1A2B3C": :USER$D1SK:
2. User ZZZ wants to copy his LOGIN. COM file from VAXTMl to NARVAX:
$COPY LOGIN. COM NARVAX"ZZZ 1A2B3C": :USER$DISK: [ZZZ]*.*
8.5 SNA
8.5.1 Logging on to IBM Systems through DECnet/SNA
You may access the NCC-IBM 3090 system, as well as EPA-IBM Logical Mainframe
systems, through the SNA Gateway. (You must be an authorized user on the
remote system.) To access the network menu, type the following command:
$ NET SOL
The following menu will be displayed:
U.S. EPA TELECOMMUNICATIONS NETWORK MENU
10:01 Monday January 11, 1988
NATIONAL COMPUTER CENTER
PFKEY SELECTION SERVICE
PF13 PCICS CICS - PRODUCTION
PFKEY SELECTION
PF15 NY
PF14
PF19
DCICS
TSO
CICS - DEVELOPMENT
TSO - NCC
PF16
PF17
PF20
PF21
PF22
PF23
PF24
PF2
PF3
PFA
PF5
DV
W1C
SE
AT
DA
KC
PH
CI
BN
CH
SF
TERM:T250198
MODEL 2
SERVICE
TSO - NEW YORK LhF
TSO - DENVER NEIC LMF
TSO - WASH INFO CENTER
TSO - SEATTLE LMF
TSO - ATLANTA LMF
TSO - DALLAS LMF
TSO - KANSAS CITY LMF
TSO - PHILADELPHIA LMF
TSO - CINCINNATI LMF
TSO - BOSTON LMF
TSO - CHICAGO LMF
TSO - SAN FRANCISCO LMF
HIT PF KEY OR ENTER SELECTION
Select the system to which you would like to connect. To return to the VAX,
log off the remote system and then press Control-Z.
You may also access TSO on the IBM 3090 system directly by using the following
command:
$ TSO
8-9
-------
8.5.2 Emulating a 3270 Terminal
While logged on to an IBM through DECnet/SNA, VTlOO-type terminals will
emulate an IBM 3270. Figure 8-3 Illustrates the keyboard function conversions
On-line help may be obtained by pressing the keypad's period key and then the
"H" key.
Figure 8-3. 3270 TE Keyboard Highlighting the 3270 Keys
8.5.3 Submitting Batch Jobs to the IBM 3090
You may submit jobs to run on the IBM system through the SNA Gateway. Create
your Job in a file using appropriate JCL commands, and then use one of the
following procedures for submitting it.
a. An automated procedure can be used by typing:
IBMSUBMIT filename
You will be prompted for your VAX password, and your Job will be
submitted using the /NOLOG and /NOTIFY qualifiers.
b. At the DCL prompt, type the following command:
SUBMIT/SNA/NOLOG node'userid password":ifilename
where "node," "userid," and "password" are those belonging to the
signed-on VAX user and where "filename" Is the Job file (use quotation
narks as shown in the command). Following is an example:
SUBMIT/SNA/NOLOG VAXTM1"XY2 RTPNC"::IBMJOB.JCL
8-10
-------
Note; It is Important to use the /NOLOG qualifier to avoid any
possible compromise of your password's secrecy. Without this
qualifier, a log is created that includes your User-ID and password.
OR
c. Allow WORLD read access to the file with the following command:
SET FILE/PROTECTION-W:R filename
Then submit it with the following command:
SUBMIT/SNA filename
Note; If the file resides in a subdirectory, WORLD must have read
or execute access to that directory as well.
After Issuing the SUBMIT command, you will receive a message stating that the
job has been assigned to the SNARJE$R£ADER queue to await transmission to the
IBM. You may check its status by typing the following command:
SHOW QUEUE SNARJESREADER
You may also review the job's log file to be sure that it was properly
submitted. It can be found in:
[uid1f ilename.LOG
where "(uid)" is your top-level file directory and where "filename" is
the name of the file you submitted.
If you wish to check the job's status as it executes on the IBM, you must log
on to that system and use a utility such as QUEUE or SDSF to do so. (See
Section 5.1 of the NCC-IBM User's Guide for assistance.)
When the job is executed on the IBM, a VAX MAIL message will be sent to the
username specified in the DNX card informing you that the job has been
completed and that the output has been routed to the file specified in the
DNX card.
8-11
-------
9.0 SUBMITTING BATCH JOBS
A procedure that Is executed frequently can be submitted as a batch job
rather than being repeatedly executed Interactively. To submit a batch job,
enter the commands normally used to run the job interactively into a file
called a Batch Command Procedure.
Note: The first line in the Batch Conmand Procedure must indicate the user's
Project-ID in a commented form as follows:
$! project-id /-
Submitting this file creates a request for the system to run the job. The
batch system executes the commands stored in the command procedure file.
After executing the last command, the batch system ends the job by logging it
off. The batch system records the job in a log file which is written on a
default disk. When the job completes, the log file is queued to SYS$PRINT
and deleted from disk after it is printed.
Use the SUBMIT command to enter the batch queue (see Section 9.2, following).
9.1 BATCH QUEUE POLICY
The batch queues have been structured into specific queues based on CPU
runtime. This allows flexibility with regard to batch job execution, faster
turnaround time for short jobs, and better interactive response time. Three
queues control batch jobs, based on CPU time used:
Queue Priority CPU Limit
Fast 3 5 minutes
Norm 2 180 minutes
Slow 1 Unlimited
The SHOW QUEUE command will display the current status of entries in the
batch queue. If used in the form
SSHOW QUEUE SYS$BATCH
only information about jobs owned by your process will be displayed. When
used with the /ALL qualifier
SSHOW QUEUE/ALL SYS$BATCH
the names of all current and pending jobs in the queue will be displayed.
9-1
-------
9.2 SUBMIT COMMAND
The SUBMIT command enters one or more command procedures in the batch queue.
You must specify the procedure file name and the file type unless it is the
default, .COM. The NORM queue is the default unless otherwise specified.
$SUBMIT/QUEDE-queue-nane file-namel.type[,file-name2.type,...]
VMS will create a batch process to execute the command procedure(s). The
order of submission to the queue determines the order of execution.
There are a number of qualifiers with the SUBMIT command. The /AFTER-time
qualifier requests that the job be held until after the time indicated.
Absolute time, delta time, or a combination of the two may be specified.
$SUBMIT/QUEUE-queue-name/AFTER-16:00 filename.type
Absolute times have the following format:
[dd-mmm-yyyy[:]][hh:mm:ss]
You can specify either the date or the time, or both. It is possible to
truncate either the date or the time; however, if you are specifying both,
the date must contain at least one hyphen. Note that 0 through 23 are accept-
able values for hours. Expressing a start time of midnight as /AFTER:24:00:00
is invalid.
The delta time format is:
[dddd-][hh:mm:ss]
Refer to the VAX/VMS Command Language User's Guide, Section 5.8, pages 5-14
and following, for additional Information on time expression.
9-2
-------
Appendix A
TELEPHONE NUMBERS
Following are the telephone numbers for the primary NCC-VAX service areas.
For numbers associated with services other -than those listed, call the User
Contact Center at the number given below:
Service Area
VAX Access Number
(For more information on toll free 2400 baud
access, contact Telecommunications.)
User Contact Center
EPA-NCC
MD-34B
Research Triangle Park, NC 27711
TSSMS Office
EPA-NCC
MD-34C
Research Triangle Park, NC 27711
NCC Network Control Facility (Telecommunications)
EPA-NCC
MD-24
Research Triangle Park, NC 27711
Data Processing Support Services
(includes Tape Librarian,
1/0 Control Desk, and
Shift Supervisor)
EPA-NCC
MD-24
Research Triangle Park, NC 27711
Status Phone (VAX Cluster)
Status Phone (OTS VAX)
Telephone Number
(919) 541-4642 (1200 baud)
(FTS) 629-4642 (1200 baud)
(800) 334-1079 (1200 baud)
(919) 541-0700 (2400 baud)
(FTS) 629-0700 (2400 baud)
(919) 541-7862
(FTS) 629-7862
(800) 334-2405
(919) 541-3629
(FTS) 629-3629
(919) 541-4506
(FTS) 629-4506
(800) 334-0741
(919) 541-2385
(FTS) 629-2385
(800) 334-9700
(919) 541-2969
(FTS) 629-2969
(919) 541-2492
(FTS) 629-2492
A-l
-------
Appendix B
SAMPLE FORMS
READER'S COMMENTARY FOR THE NCC-VAX USER'S GUIDE
Please use this form to express your opinions and comments concerning this
publication. We are particularly interested in your views concerning the
completeness, technical accuracy, and organization of the manual.
Please complete the following:
o Commentator's Name:
o Telephone Number:
o Title:
o How often do you use this publication?
Frequently for reference.
For introductory purposes to a subject
Other (please specify).
o Comments (Include page numbers and give examples):
o Do you require a response? Yes No
This form, together with any supporting material, should be forwarded to:
User Contact Center
EPA-NCC
MD-34B
Research Triangle Park, NC 27711
Thank you for your comments.
B-l
-------
USER PROFILE WORKSHEET
Please enter/verify:
NAME:
ADDRESS:
PHONE: ' USER-ID:
Computer System: IBM SPERRY DEC
IBM PC PRIME ^Z^ LEXITRON
NCC Publications: IBM User's Guide
SPERRY Reference Manual
NCC VAX User's Guide
Do you wish to receive ALL user memorandums, regardless of subject area?
Yes NO
If you need only selected information, check the subject areas of your choice:
Data Center Management
General Information
Data Center Policy, Usage
Hardware
Telecommunications System
Technical Advisories
Software (All Software)
System Software
Utilities
Compilers (All Compilers)
FORTRAN
PL/1
COBOL
Application Packages (All Packages)
Database Management Systems
Retrieval/Reporting Systems
MATH/STAT Systems
Project Management Systems
Plotting/Graphics Systems
File Management Systems
RETURN COMPLETED FORM TO: Communications and Training
EPA
MD-34B
Research Triangle Park, NC 27711
Attn: User Profile
B-2
-------
ODP TELECOMMUNICATIONS SERVICE BECUEST
The ODP Telecommunications Service Request (TSR) consists of
six pages containing all anticipated user needs fox ODP
telecommunications sezvice. The TSR addresses
telecommunications support services only, not procurement of
ADP equipment.
Each page of the TSR is accompanied by instructions for completing
the form page. Although the TSR is largely self-explanatory, the
instructions provide additional clarification regarding certain items
The TSR contains the following six pages:
PAGE 1: ODP Telecommunications Service Request
PAGE 2: Full-Screen Application Terminal Equipment
PAGE 3: Graphics and ASCII (TTY) Terminal Equipment
PAGE «»: RJE Registration Form
PAGE 5: Projected Equipment Activity .
PAGE 6: Terminal Activity by Function and Host Systems
PAGE 1 of the TSR oust be included with every request. Otherwise,
only those pages necessary to document the request should be
submitted. Note that page 1 contains a narrative section to allow
users to explain specifically what is needed.
Please fill out the requested information as thoroughly as you
can. Upon receipt of the form by NCC, our telecommunication staff
will work with you to supply any missing information.
Return the ODP Telecommunications Service Request to:
NCC/TELECOM ADMIN GROUP
EPA
HD-21A
RTP, NC 27711
B-3
-------
ADP Coordinator Name
Title
Phone
Signature
Site Location
Building
Address .
City
Room Number
Zip Code
Contact Person
Commercial Phone
FTS Phone
NARRATIVE EXPLANATION ££ REQUESTED ACTION
Requested Completion Date
This change uill be: Permanent
If Temporary, uhat is duration? Months
Temporary
From
To
RETURN TELECOMMUNICATIONS SERVICE REQUEST TO:
NCC/TELECOn ADMIN GROUP
EPA
MD-2<*A
RTF. KC 27711
FOR ODP USE ONLY
TAG RECEIPT:
Date
TSR No.
Title _
B-4
-------
INSTRUCTIONS FOR PAGE J.
PAGE 1 of the TSR oust be submitted with every request. Mote
•specially the following items:
Signature: The signature line aust be signed only by the
ADP Coordinator. The signature represents approval of the
request for service.
Site location: Provide the exact location at which the
service/equipment is to be received. Note that the room number
and the building should be included.
Contact Person: Provide the name and telephone numbers of
the person uho can specify exactly the parameters surrounding
the request.
EPA Ptei'eet Officer •• If the service/equipment requested is
for a contractor site* the name of the EPA Project Officer must
be listed.
Narrative Explanation: Describe your request as fully as
possible. Explain any information that you believe needs
clarification or justification.
Permanent or Temporary Change• If the request is for
temporary service/equipment* specify the length of time for
which the service/equipment will be needed.
B-5
-------
FULL-SCREEK APPLICATION TERMINAL ECUIPMENT PAGE 2
FULL-SCREEN EOUIPMEMT ACTION
Terminals Printers Controllers
Keu
Expand
Hove*
Delete
Existing Full-Screen Equipment:
Terminals Printers Controllers
AILC-U TERMINALS USING PROTOCOL CONVERTER
Ctv/Manufaeturer/Mod
Terminals Protocol Converter Ports
Keu
Expand __
Move* __^__^___
Delete
Existing Full-Screen Equipments Terminals Ports
»HOVE INFORMATION
From: Building Building
Attention . Attention
Telephone Telephone
Address Address _
City City
State Zip State . zip
B-6
-------
INSTRUCTIONS FOR PAGE £
PAGE 2 of the TSR should be submitted as neeessazy to document the
zequest. It must be submitted if the request is for "true" full-
screen equipment or for full-screen-emulation equipment. Full-
screen equipment includes the IBM 3270, the SPERRY Uniscope, and
other terminals. Completed samples of this page are available
from the NCC/TELECOM AOMIN GROUP.
B-7
-------
GRAPHICS AND ASCII (TTY) TERMINAL E2UIPMENT
PAGE 3
GRAPHICS TERMINAL EQUIPMENT
fitv/Mantifaetuggg/Hodel
Terminals Printers
Host Type
Neu
Expand
Move*
Delete
ASCII CTTY) TERMINAL EQUIPMENT
Neu
Expand
«ove«
Delete
gtv/Manufacturer/Model
Terminals Printers Host Type
•MOVE INFORMATION
From: Building
Room
Attention
Telephone
Address
City
State
Building
Room
Zip
Attention
Telephone
Address
City
State Zip
B-8
-------
INSTRUCTIONS FOR PAGE £
PAGE 3 of the TSR should be submitted AS necessary to document the
request. Completed samples are provided upon request by the
KCC/TELECOM ADMIN GROUP. Note that page 3 applies only to graphics
terminals and ASCII TTY's.
B~9
-------
RJE REGISTRATION FORM
PAGE «4
TERMINAL TYPE
Texainal Manufacturer
Terminal Model Number
Line Pzotocol (BSC/SDLC)
line Printer Speed
Existing Line Type
(Lease/Dial)
Host Access
TERMINAL PERIPHERALS
Number of Readers
Number of Printers
Number of Punches
PRINTER SETUP
Print Positions
Lowercase
Separator PAGE
Drain Start
PR1
Protocol Equivalent
2770. 3781
2780
3780
S360/20 Hod H.S
S360/20 Hod 5.6
S360/22. 25, «tc.
1130
System JJ ___
3770 _
3270-Atteched:
3262
3287
NTR
100U
TERMINAL FEATURES
Compress/Expand Feature
Horizontal Format Feature
Additional Buffer Expansions
Multiple Record Features
Transparency
Buffer Expansion
Console Support .
FOR ODP USE ONLY
RMT ID:
IBM
SPERRY
P/W
B-10
-------
INSTRUCTIONS FOR PAGE jl
PAGE «4 of the TSR should be submitted as necessary to document the
request.
Terminal Type
Provide the following information* manufacturer; model number;
communications line protocol to be used; line printer speed;
•xisting line type (either dedicated-circuit communications or
dial-up communications); and the CPU host(s) to be accessed (IBM,
SPERRY, PDP. etc.).
Terminal Peripherals
As applicable, list the number of readers, printers, and punches.
Printer Setup
Enter the special characteristics for each of your printers.
Print Positions: Enter the number of horizontal print positions
for each printer. The default is 132.
lowercase Support: Indicate if the printer supports uppercase
and lowercase printing. The default is uppercase.
Separator PAGE: Indicate if you wish to have the standard JES2
separator page printed with each job printed. The default
is to print separator pages.
Drain/Start: Indicate if you wish to have the drain at RJE
sign-on.
Terminal Features
Hake a checkmark on the blank line beside the desired categories.
Protocol Equivalent
Make a checkmark on the blank line beside the type of RJE station
the site is emulating. Only one box should be checked.
B-ll
-------
PROJECTED ECUIPFIENT ACTIVITY
PAGE 5
FILE TRANSFER (PERSONAL COMPUTER)
1 Receiving I From
Application 1 Device 1 Location
1 1
1 1
1 1
lEMOTE JOB PRINTING (RJE)
1 Average 1
Application 1 Lines/Day 1
1 1
1 1
1 1
1 To 1 File
1 location 1 Size
1 1
1 1
1 1
Peak 1 Hours
lines/Day 1 Per Day
1
1
1
1
1 Freq.
1
1
1
.____ f
1
1 CPU
1
1
1
. _ j
BULK DATA TRANSFER (HOST TO HOST)
Application
1 From
1 Location
1
1
1
1
1
1
1
1
To 1 File 1
Location I Size 1 Fret.
1 1
1 I
1 1
1
1
1
1
1
Time
of Day
B-12
-------
INSTRUCTIONS FOR PftGE £
PAGE 5 of the TSR should be submitted as necessary to document the
xequest. It Bust be completed if new applications or equipment
dictate neu requirements.
file Transfer {Personal Computer)
Since file transfer can affect telecommunications requirements
throughout the network, this section must be completed if the user
anticipates file transfer on a regular basis to support a particular
application.
Application: Specify the applicaton name with uhich the data
is associated.
Receiving Device: Identify the device receiving the file (IBM
PC/XT. IBM 3081, etc.).
From Location: Specify the computer system storing the original
file that will be transferred (IBM PC/XT, IBM 3081, etc.
To location: Specify the computer system that will receive
the transferred file.
File Size: Specify the maximum number of megabytes of
data that will be transferred at one time (one byte
per character).
Frequency: Specify the frequency of the file transfer (daily,
weekly, or monthly) and. if possible, the time of day the
transfer will occur.
Remote Job Printing (RJE)
If the equipment prints in the unattended mode, these print hours
should also be included when specifying the hours per day. Remember
too the importance of distinguishing between CPU's when providing
print information.
JLUlfc Pata Transfer (Host £0. Host)
For guidance in completing this section, see the instructions above
for File Transfer. Specify the time of day the transfer will occur.
(With the installation of IBM USXX's at different sites, software
will be available for automatically transferring files between
processors as part of a standard update cycle. This capability
will also enable users to transfer files to another CPU for further
processing.)
B-13
-------
PAGE 6
TERMINAL ACTIVITY BY FUNCTION AND HOST SYSTEMS
HOST SYSTEMS
IAPPL. FUNCTION
I
I
I DATA ENTRY
I Hours/Day
(No. of Terminals
lAvg. Input
I Char/Trans....
lAvg. Output
I Char/Trans
lAvg. No. of
I Tzans/Houz....
lAvg. No. of
I Trans. Peak
I Houz
(PROGRAM DEV.
(Houzs/Day
(No. of Terminals
(Usage (L. A, H>*
I
(GEN. TIMESHARING
IHours/Day
(No. of Terminals
(Usage (L. A, H)*
I
(GRAPHICS
(Houzs/Day
(No. of Terminals
(Usage (I, A, H)*
I
ICHAR. PNTR OTPUT
(No. Chaz. Pntzs
lAvezage Lines/Hz
lAvg Chaz/Pzt
I Line
TSO
IOC RTP
SPF
LOC RTP
CICS
LOC RTP
SPERRY
DEC
PRME
OTH
•Usage Key:
L (Light Terminal Activity)
A (Avezage Terminal Activity)
H (Heavy Terminal Activity)
• < 1 Houz Fez Day
« > 1 Houz Pez Day
« > 3 Houzs Pez Day
B-U
-------
TMSTEUCTIOMS FOR PAGE £
PAGE 6 of the TSR should be submitted as necessary to document the
request. It must be completed if an additional terminal is added
to the network. The data traffic information it provides uill be
used in determining if the telecommunications equipment must be
upgraded to provide sufficient service. Since follou-up questions
uill normally be required between the telecommunications analyst
and the requestor, the information provided on page 6 is considered
to be simply a starting point for further discussions.
The page is broken doun by function across various systems or system
interfaces.
Host Systems
The system interface columns (TSO, SPF, and CICS) are divided into
local and RTF columns. "Local" refers to the IBM processor located
at your site. "RTF" refers to the IBM processor at Research Triangle
Park.
Application Function
Because "function" affects the service required, categorize the
terminal activity by application function. For the "hours per day"
give the average for the number of terminals specified for that
particular function.
Data Entry Data entry information related to the transaction
size and number of transactions uill be available
from the Kational System Manager and is particularly
relevant for CICS activity. It is not expected that
data entry on the IBM systems uill be made under TSO
or SPF. The only exception uill be the use of TSO uith
the Fourth Generation Information Center software.
Character Printer Output: This section refers to an IBM 3287
or other cluster-attached printer. In the DEC environment,
this unit is normally a terminal-auxiliary printer.
B-15
-------
EPA APR IBM. LMF. SPERRY. & VAX ACCOUNT AND USER REGISTRATION
l_
THIS REQUEST:
ESTABLISHES A KEN ACCOUNT
MOS. tCLETES. OR CHANGES USER(S) ON EHSTIN6 ACCOUNT
TSSMS USC ONLY
DATE RECEIVED:
(gjj: FORM K 251 MUST BE COMPLETED TO MODIFY INFORMATION QTHEP. THAN USER DATA OH AN EXISTING ACCOUNT.)
HARDWARE (CHECK ONLY ONE)
HNJ090 IBM 436) HASH.. K SPERRY
IMF (SPECIFY) ___
HAD »AJt NCC VAX CLUSTER
OTHER (SPECIFY) __
WP lino HARDWARE ONLT: FORM N 2MA
MUST K COMPUTED.
SOURCE OF T1MESHARE FUNDS (CHECK OMIT ONE)
U.S. PA I»TERA6ENCY/imR6CVE»«NTAL A6REEMEKT (1AG)
OT«R (SPECIFY)
TO BE COMPLETED BY EPA 1A6 COORDINATOR
IS ACCOUNT TO BE CHAWED I AC 101 SURCHARGE?
TCS
COORDlNATOK S SIbN»TURl)
WRPOSE OF ACCOUNT OR «I£F KSttlPTION OF ACTIVITY ACCOUNT Mill SUPPORT
EPA OR&AN1ZAT10N CODE (6-D1CIT CODE)
FTC CODE (ID-DIGIT CODE)
ACCOUNT TITLE (LIMIT: 60 CHARACTERS. INCLUDING SPACES)
ACCOUNT RANAKR'S MK (LAST. FIRST. H.I.). WST BE EPA EWLOYEE.
MAIL CODE (OR ROW) OFFICE OR LOCATION
ADDRESS (STREET OR P.O. BOX)
CITY
WOKE
rrs
PHONE (INCLUDE AREA CODE)
STATE
ZIP CODE
REFERENCE
INITIALS
(TSS«-
ASSIGNED)
TO BE A USER ON THIS ACCOUNT. ACCOUNT NANASR MUST BE INCLUDED ON REVERSE SIDE.
CPA ADP COORDINATOR'S NAME (PLEASE PRINT OR TYPE)
EPA ADP COORDINATOR'S SIGNATURE (REQUIRED)
DATE
COOES USED M ASSIGNING USERS ON REVERSE 61DE
VSER INITIALS COPE
(TSSKS-ASSIGNED)
(SUPPLY IF MOWN)
FORM TO:
. ENVIRONMENTAL PROTECTION AGENCY
•ATIONAL DATA PROCESSING DIVISION
TSSMS OFFICE (KD.S4C)
79 ALEXANDER DRIVE. BUILDING 4501
RESEARCH TRIANGLE PARK. NC 27711
(CHECK 0*1 FOR LAU1 U51K LISTED)
(DEFAULT IS IBM SPF)
S - IBM STORET (AASTORET)
R • SPERRY AUTOMATIC RUN CARD
(FORM N 252 MUST BE ATTACHED.)
0 • OTHER (PLEASE SPECIFY.)
USER STATUS CODES
(CHECK 0*1 FOR [*EH USER LISTED)
E - EPA EMPLOYEE
C • CONTRACTOR/COMMERCIAL
F - FEDERAL NON-EPA
S • STATE OR LOCAL GOVERNMENT
U » UNIVERSITY
0 • OTHER
we (PAS n
(SEE REVERSE SIDE FOR ASSIGNING USERS TO ACCOUNT)
B-16
-------
USERS ASSIGNED TO ACCOUNT
(Please Print or Type)
USER NAME (LAST, FIRST. M.I.)
MAIL CODE (OR ROOM) OFFICE AND/OR COMPANY
ADDRESS (STREET OR P. 0. BOX) CITY
PHONE
(FTS)
PHONE (INCLUDE AREA
< ,""2
STATE
2IP CODE
USER INITIALS
TSSMS-ASS1GNED
SPECIAL FUTURES
S
* 0
USER STATUS
E S
c u
F 0
UPDATE ACTION: ADO USER DELETE USER CHANGE USER INFORMATION AS LISTED ABOVE
USER NAME (LAST. FIRST. N.I.)
MAIL CODE (OR ROOM) OFFICE AND/OR COMPANY
ADDRESS (STREET OR P. 0. BOX) CITY
PHONE
(FTS)
PHONE (I
0
( )
STATE
*
RCLUDE AREA
ODE)
ZIP CODE
USER INITIALS
TSSMS-ASSIGNED
SPECIAL FEATURES
S
__R 0
USER STATUS
E S
C U
F 0
UPDATE ACTION: ADD USER DELETE USER CHANGE USER INFORMATION AS LISTED ABOVE
USER| NAME (LAST. FIRST. M.I.)
MAIL CODE (OR ROOM) OFFICE AND/OR COMPANY
DDRESS (STREET OR P. 0. BOX) CITY
PHONE
(FTS)
PHONE (INCLUDE AREA
< ,m£2
STATE
ZIP CODE
USER INITIALS
TSSMS-ASSIGNED
SPECIAL FEATURES
S
R 0
USER STATUS
E S
C U
F 0
UPDATE ACTION: ADD USER DELETE USER CHANGE USER INFORMATION AS LISTED ABOVE
USER NAME (LAST. FIRST. M.I.)
NAIL CODE (OR ROOM) OFFICE AND/OR COMPANY
ADDRESS (STREET OR P. 0. BOX) CITY
PHONE
(FTS)
PHONE (
( )
STATE
INCLUDE AREA
CODE)
ZIP CODE
USER INITIALS
TSSMS-ASSIGNED
SPECIAL FEATURES
S
R 0
USER STATUS
E S
C U
F 0
UPDATE ACTION: ADD USER DELETE USER CHANGE USER INFORMATION AS LISTED ABOVE
USER) NAME (LAST. FIRST. N.I.)
NAIL CODE (OR ROOM) OFFICE AND/OR COMPANY
ADDRESS (STREET OR P. 0. BOX) CITY
PHONE
(FTS)
PHONE (INCLUDE AREA
CODE)
( )
STATE
ZIP CODE
USER INITIALS
TSSMS-ASSIGNED
SPECIAL FEATURES
S
R 0
USER STATUS
t S
C U
F 0
ACTION: ADD USCT DELETE USER CHANGE USER INFORMATION AS LISTED ABOVE
USER(S) UPDATE
SIGNATURE REQUIRED
^CCOIMT niMBFR (PLFASE SPECIFY) tPA ACCOUNT MANAGER
1
| EPA ADP COORDINATOR
VHOHl
N 256 (PAGE 2)
B-17
-------
Appendix C
DIGITAL CONTROL LANGUAGE (DCL)
Terminal Special Function Keys
CARRIAGE RETURN Initiates login procedure. If logged in, this key
transmits the current line to the system.
DELETE Deletes the last character entered and backspaces
over it.
ESCAPE Usually the same as RETURN, but can have special
uses to certain programs.
Control Keys
Control keys are entered by holding down the CTRL key while typing the letter.
All control keys are echoed on the terminal as the up arrow followed by the
letter.
CTRL/C Cancels command or program execution.
CTRL/I Same as TAB key.
CTRL/K Advances to the next vertical tab stop.
CTRL/L Form feed.
CTRL/O Suppresses terminal display of output. Alternately
continues display of output.
CTRL/Q Restarts terminal output after suspension by
CTRL/S.
CTRL/R Retypes the current line.
CTRL/S Suspends terminal output until CTRL/Q is entered.
CTRL/T Displays a single line of statistical information
about the current process.
CTRL/U Discards the current input line.
CTRL/X Discards the current line and deletes data in the
type-ahead buffer.'•
C-1
-------
CTRL/Y same as CTRL/C.
CTRL/Z Signals end-of-file for data entered from the
terminal.
Arrow Keys Recall last 20 lines typed in.
C-2
-------
Appendix D
TELECOMMUNICATIONS: DIAGNOSING AND REPORTING PROBLEMS
1. Check the Terminal
Verify that the terminal's electrical power is turned on. Check that all
terminal cables are attached securely. Check that the terminal is in
communication (on-line) mode, and that parameters such as transmit and
receive speed are correct. Parity checking should be both on and even.
2. Check the Modem and Telephone Line
Verify that the modem is plugged in and turned on. Check that all modem
cable attachments are secure. Verify that the telephone works correctly
and has good tone with no noise or crosstalk.
3. Check the Encryption Box (for use with Confidential Business Information
System)
Verify that the encryption box has electrical power and is turned on.
Check that cables to the encryption box are securely attached. Verify
with your Project Manager or Security Officer that the current primary
key has been loaded.
4. Reporting Problems
If your terminal is malfunctioning, call the manufacturer for repair, if
the modem or telephone line is bad, call the NCC Communications staff for
assistance. Depending on your location, call:
RTF Communications (FTS) 629-4506
D-D. (919) 541-4506
WATS (800) 334-9794
Have the following information when calling to report a problem: tele-
phone number(s) dialed, terminal type, modem type, coupler or data phone
type.
For miscellaneous communications problems, call VAX User Support at
(919) 541-7892 or (FTS) 629-7862.
D-1
-------
Appendix E
HELP PILES
To display the text on a particular topic, type HELP filename.
ALLOCATE DUMP MAIL RTL
ANALYZE EDIT MCR RUN
APPEND EOD MERGE RUNOFF
ASS1GN EOJ MESSAGE SEARCH
ATTACH ERRORS MONITOR SET
BACKUP EXAMINE MOUNT SHOW
CANCEL EXIT ON SORT
CHGPASSWD FDL OPEN SPAWN
CLOSE FORTRAN OPSCH SPECIFY
CONTINUE GOTO PASSWORD START
CONVERT HELP PATCH STOP
COI>Y HELPUSER PHONE SUBMIT
CREATE IF PRINT SYMBOL ASSIGN
DEALLOCATE INITIALIZE PRINTOUTS SYNCHRONIZE
DEASSIGN INQUIRE PROCEDURE SYSTEM
DEBUG JOB PURGE TASSIST
DECK LEXICAL QUEUES TECO
DEFINE LIBRARY READ TYPE
DELETE LINK RENAME UNLOCK
DEPOSIT LOGIN REPLY USER
DIFFERENCES LOGOUT REQUEST WAIT
DIRECTORY MACRO RMS WRITE
DISMOUNT
E-1
-------
Appendix F
VAX SUPPORTED SOF1VARE
Software
Level Vendor/Address
Documentation Reference
VMS
4.6
DEC
P. 0. CS2008
Nashua, NH 03061
Introduction to VAX/VMS
DCL Dictionary
VAX FORTRAN 4.6
DEC (see above)
VAX-11 FORTRAN
Reference Manual
DECNET 4.6
Phase 4
DEC (see above)
Networking
HASP+
5-3
DATANEX
GEJAC, Inc.
P. 0. Box 188
Rlverdale, MD 20737
HASP+ VAX/VMS Reference
Manual
KERM1T
(public domain)
VAXTM1::$2$DUA0:(KERMITjKERMlT.DOC
VAXTM1::$2$DUA0:[KERMITJVMSV3.DOC
VAXTM1::$2$DUA0:[KERMITJVMSV31AN.DOC
SAS
5.16 SAS Institute
Gary, NC 27511
SAS Users Guide
IMSL
10
IMSL, Inc.
2500 ParkWest Tower One
2500 CityVest Blvd.
Houston, TX 77042-3020
IMSL Library
FOCUS
1.3.1 Information Builders, Inc.
1250 Broadway
NY, NY 10001
FOCUS VAX/VMS User's Guide
TAPESYS
4.3 Software Partners/32, Inc.
447 Old Boston Rd.
Topsfield, MA 01983
TAPESYS Users Guide
F-l
-------
Appendix G
REGISTRATION PROCEDURES
If a user wishes to be added to one of the DEC systems, use the following
procedure:
o Obtain a TSSMS user registration fora (see Appendix B for a sample)
and fill out completely.
o Contact the ADP Coordinator for billing account, organization code,
FMS code, approval, and signature.
o If the billing account Is new, a FIMAS code must be assigned, and the
EPA Project Manager must approve the form also.
If the user is being added to the NCC-VAX Cluster, approval will be obtained
by the EPA VAX Cluster Project Manager. When the user is added, an authori-
ration notice and card will be sent to the user, and the ADP Coordinator is
called.
G-l
-------
Appendix H
MOVING A SAS DATA SET FROM THE VAX TO THE IBM
To transfer an existing SAS data eet from the VAX to the IBM, certain steps
oust be taken. Below Is an explanation of each of these steps on each machine
VAX MACHINE
1. Log onto the VAX (see Section 4.1.1).
2. Allocate a tape for use and have the tape loaded on a tape drive.
(See Section 5.4, TAPESYS Tape Management System.)
(Message will be received from operator when completed.)
Then use the following command to mount the tape:
>MOUNT/FOREIGN/NOASSIST tape-drive
(If you are not using the VAX Cluster, type In this command to have SAS
recognize the correct tape drive.)
>ASSIGN tape-drive SASTAPE
Continue with these commands:
>ASSIGN SASTAPE IXTAPE
>SAS
1? LIBNAME MYFILES '[dlr.subdlr]'; (where data sets reside)
2? PROC COPY IN-MYTILES OUT-IXTAPE EXPORT;
3? RUN;
...messages received for files written to tape...
4? END SAS;
>DISMOUNT tape-drive
DEALLOCATE tape-drive
3. Log off the VAX If finished with this session.
IBM MACHINE
1. Call DPSS to have the tape transferred to the IBM (see Appendix A for
telephone number).
2. Log onto the IBM.
H-l
-------
3. Run a TAPESCAN to evaluate the tape. An example of a job follows:
//jobname JOB (acct-fimasid,bin0),name,PRTY-4,TIME"(,3)
//EXEC TAPESCAN,PRINT-'*',VOL-tape*.PARM-(LIST20,HEX),OPTCD-Q
Output from the TAPESCAN should have no 10 errors, number of blocks should
be specified, and output should have header records.
4. Run a SAS program to copy the SAS data set from tape to disk. An example
of this follows:
//jobname JOB (acct-fiaasid,bin0),name,PRTY-4,TIME-(,3),PASSWORD-pswd
/*ROUTE PRINT HOLD
//EXEC SAS.REGION-3000K
//Fl DD UNIT-TAPE,LABEL-(1,NL,EXPDT-98000).DISP-OLD,
// VOL-SER-tape#,DCB-(RECFM-FB,LRECL-80,BLKSIZE«8000)
//F2 DD DSN-SASLIBRARY.NAME,DISP«OLD
//SYSPRINT DD DUMMY
//SYSIN DD *
PROC XCOPY IN-F1 OUT-F2 IMPORT;
RUN;
/*
If a SAS library does not exist, a new data set name must be specified
in the following format:
//F2 DD DSN-SASDATA.NAME,UNIT-DISK,DlSP-(,KEEP)
SAS will assign space and DCB attributes based on the input file.
H-2
-------
Appendix I
PROCEDURE FOR TRANSFERRING A FILE
FROM THE VAX CLUSTER TO THE IBM 3090 SYSTEM
PURPOSE
This document provides users on the NCC-VAX Cluster system with a simple
method of transferring files to the NCC-IBM 3090 system. Although the
procedure is by no means the only method of performing this task, it is an
effective solution. This document may also be accessed through the on-line
documentation system (ONLINEDOC).
The following procedure allows you to transfer a text file from the VAX to
the IBM system by means of an IBM batch job. The entire procedure is carried
out without logging off the VAX. You must have a valid IBM User-ID, however.
To use the procedure, you create a job on the VAX and then submit it to the
IBM through the SNA gateway. The Job utilizes the IBM utility IEBGENER to
copy the file to an IBM data set.
PROCEDURE
1. To begin, you must create an IBM batch job using a VAX editor. The format
of the job is:
//uid JOB (acctfimas,bbbb),VAXTOIBM,PRTY-4,TIME-(,3),
// PASSWORD-password
/*ROUTE PRINT HOLD
//STEP1 EXEC PGM-IEBGENER
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT-A
//SYSUT2 DD DSN=dataset specificatlon,DISP=(disp)
//SYSUT1 DD *
You need to modify this model as follows:
Replace With
uid your IBM User-ID
acctfimas your IBM account & FIMAS-ID
bbbb your bin code
password your IBM password
dataset specification the name of the IBM data set receiving
the file
disp the disposition of the data set receiving
the file
1-1
-------
Notes
- All job statements oust be uppercase, or the job will fall.
- The /*ROUTE PRINT HOLD statement is optional, but it will cause the
JES2 job log to be held for your review in case of problems with the
job.
- The job card parameters used above (PRTY and TIME) are samples. The
Job will run with the given parameters, but you may wish to modify them
and/or add other parameters to suit your particular needs. Also, your
data set specification in line 7 oust include an appropriate DISP
statement to indicate the status of the output data set. If you need
additional information on these parameters, consult Section 4.0 of the
NCC-1BM User's Guide.
2. The next step is to append the file you wish to transfer to the end of
the above code, following the statement //SYSUT1 DD *. (If you are using
the EDT editor, this is most easily done with the INCLUDE command. It
can also be done with the DCL command APPEND.) At the end of your file,
add /* (beginning in column 1) to mark the end of the Job.
Example
The following example shows how your completed job might look:
//ZQX JOB (AORTFAKET.MZQX),SAMPLE,PRTY-4,TIME-(,3),
// PASSWORD-RTPNC
/*ROUTE PRINT HOLD
//STEP1 EXEC PGM-IEBGENER
//SYSIN DD DUMMY
//SYSPRINT DD SYSOUT-A
//SYSUT2 DD DSN-ZQXAORT.VAXFILE.TRANSFER.DISP-(OLD)
//SYSUT1 DD *
************** xhis is test file for transfer to the IBM ***********
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCccccccccccccccccccccccccccccccccccc
0123456789012345678901234567890123456789012345678901234567890
letfSZ &*() -H- ]?><,./:;"'
XXXXXXXX Last Line of sample file XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
/*
Notes
- Your text file may have a record length greater than 80, but if so be
sure to add a /RECORD- qualifier to the SUBMIT command (see step 3 below),
- The occurrence of the characters /* beginning in column 1 anywhere in
your text file will cause the transfer to cease at that point.
1-2
-------
3. The job is now ready to submit to the IBM through the SNA gateway. There
are three methods for doing this:
a. An automated procedure can be used by typing:
IBMSUBMIT filename
You will be prompted for your-VAX password. Your job will be
submitted using the /NOLOG and /NOTIFY qualifiers.
b. At the DCL prompt, type the following command:
SUBMIT/SNA/NOLOG VAXTM1"userid password":filename
where "userid" and "password" are those belonging to the
signed-on VAX user and where "filename" is the job file.
(Use quotation marks as shown in the the command.)
Note; It is important to use the /NOLOG qualifier to avoid any
possible compromise to your password's secrecy. Without
this qualifier, a log is created that includes your
User-ID and password.
OR
c. Allow WORLD read access to the file with the following command:
SET FILE/PROTECTION=W:K filename
Then submit it with the following command:
SUBMIT/SNA filename
Note; If the file resides in a subdirectory, WORLD must have
read or execute access to that directory as well.
With either method, if the file you are submitting contains records greater
than 80 characters in length, you must add the following qualifier:
/RECORD-n
where "n" is the maximum number of characters in a record.
For example, if the file you are transferring has a maximum record length
of 120, you would use the command SUBMIT/SNA/RECORD«=120 filename. The
maximum record size allowed is 250.
1-3
-------
4. After issuing the SUBMIT command, you will receive a message stating that
the job has been assigned to the SNARJE$READER queue to await transmission
to the IBM. You may check its status by typing the following command:
SHOW QUEUE SNARJESREADER
You may also review the job's log file to be sure that it was properly
submitted. It can be found in:
[uidjfilename.LOG
where "[aid]" is your top-level file directory and "filename" is the
name of the file you submitted.
If you wish to check the job's status as It executes on the IBM, you must
log on to that system and use a utility such as QUEUE or SDSF to do so.
(See Section 5.1 of the NCC-IBM User's Guide for assistance.)
1-4
-------
Appendix J
PROCEDURE FOR TRANSFERRING A FILE
FROM THE IBM 3090 SYSTEM TO THE VAX CLUSTER
PURPOSE
This document provides users on the NCC-VAX Cluster system with a simple
method of transferring files from the NCC-IBM 3090 system to the VAX.
Although the procedure is by no means the only method of performing this
task, it is an effective solution. The document may also be accessed through
the on-line documentation system.
OVERVIEW
The following procedure allows you to transfer a text file from the IBM system
to the VAX by means of an IBM batch Job. The entire procedure is carried
out without logging off the VAX. You must a valid IBM User-ID, however. To
use the procedure, you create a job on the VAX and then submit it to the IBM
through the SNA gateway. The job contains a special record called a DNX
card, which serves to route the Job output (that is, the IBM data set you are
retrieving) back to a specified file on the VAX.
Several different Job models are provided to accommodate the various types of
data sets you may wish to transfer to the VAX. Both partitioned and sequential
data sets may be transferred. Data sets with record lengths of no more than
80 work best, because these are transferred in punch format and the output
requires very little "cleanup." Data sets with record lengths greater than
80 are transferred in print format and require some editing to restore to
original form. Data sets with record lengths greater than 133 will be
truncated.
J-l
-------
PROCEDURE
1. Consult the chart below to determine which job to use, based on the record
length and organization of the IBM data set you will be transferring:
Data Set Type
Sequential
Partitioned (transferring
a single member)
Partitioned (transferring
more than 1 but less than
all members)
Partitioned (transferring
all members)
Record Length <-80
Model A
Model B
Model B
Model C
Record Length 81-133
Model D
Model D
* Use Model D and Transfer one member at a time.
2. The job models are presented below. Using the appropriate model as a
guide, create your job with an editor on the VAX. Copy the statements
exactly as shown. You will notice that some statements contain lowercase
items for which you must substitute, such as your User-ID, data set name,
etc. The following key should be used to complete your job:
Replace
uid
acctfimas
bbbb
password
vaxuid
joblogfilespec
datasetname
membername
outputfilespec
With
your IBM User-ID
your IBM account & FIMAS-1D
your bin code
your IBM password
your VAX User-ID
a complete file specification, Including device,
directory, and file name (The contents of the
IBM JES2 Job log will be routed to this file.)
the name of the IBM data set to be transferred
the name of a member of a partitioned data set
a complete file specification, Including device,
directory, and file name (The IBM data set text
will be routed here.)
J-2
-------
Model A
//uid JOB (acctfimas,bbbb),IBMTOVAX,PRTY-4,TIME-(,3),
// PASSWORD-password
//*DNX vaxuid joblogfilespec
//STEP1 EXEC PGM-IEBPTPCH
//SYSUT1 DD DSN»datasetname,DISP-(OLD,KEEP)
//SYSUT2 DD SYSOUT-B
//SYSPRINT DD SYSOUT-A
//SYSIN DD *
PUNCH MAXFLDS-1.TYPORG-PS
TITLE ITEM-CDNX vaxuid outputfilespec',1)
RECORD FIELD-(SO)
/*
Example
//ZQX JOB (AORTFAKET,MZQX),SAMPLE,PRTY-4,TIME-(,3),
// PASSWORD-RTPNC
//*DNX ZOX USERSDISK:IZQXJJOBLOG.DAT
//STEP1 EXEC PGM-IEBPTPCH
//SYSUT1 DD DSN=ZQXAORT.IBM.DATA.DISP»(OLD,KEEP)
//SYSUT2 DD SYSOUT-B
//SYSPRINT DD SYSOUT-A
//SYSIN DD *
PUNCH MAXFLDS-1,TYPORG-PS
TITLE ITEM-CDNX ZQX USER$DISK:IZQX.IBM]IBMDATA.DATI,I>
RECORD FIELD-(80)
/*
In the above example, the sequential data set ZQXAORT.IBM.DATA is
transferred to the VAX and placed in the file IBMDATA.DAT in the
directory (ZQX.IBMj. The JES2 Job log for the Job is routed to
JOBLOG.DAT in the directory (ZQX).
Notes on Model A
- The first DNX card (line 3) nay be omitted if you do not want a copy
of the JES2 log.
- The DNX card you place in single quotes in the TITLE ITEM specification
(in line 10) can be no longer than 40 characters.
- See also "Notes Pertaining to All Jobs" at the end of item 2.
J-3
-------
Model B
//uid JOB (acctfimas,bbbb),IBMTOVAX,PRTY-4,TIMl>(,3),
// PASSWORD-password
//*DNX vaxuid joblogfilespec
//STEP1 EXEC PGM-IEBPTPCH
//SYSUT1 DD DSN-datasetname,DISP-(OLD,KEEP)
//SYSUT2 DD SYSOUT-B
//SYSPRINT DD SYSOUT-A
//SYSIN DD *
PUNCH MAXFLDS-l.TYPORG-PO, MAXNAME-1000
TITLE ITEM-CDNX vaxuid outputfilespec',1)
RECORD FIELD-(SO)
/*
Example
//ZQX JOB (AORTFAKET,MZQX),SA11PLE,PRTY-4,TIME«=(,3),
// PASSWORD-RTPNC
//*DNX ZQX USER$DISK:[ZQXjJOBLOG.DAT
//STEP1 EXEC PGM-IEBPTPCH
//SYSUT1 DD DSN-ZQXAORT.IBM.DATA.DISP-(OLD,KEEP)
//SYSUT2 DD SYSOUT-B
//SYSPRINT DD SYSOUT-A
//SYSIN DD *
PUNCH MAXFLDS-l.TYPORG-PO,MAXNAME-1000
TITLE ITEM=('DNX ZQX USER$DISK:[ZQX.IBMjIBMDATA.DAT',1)
MEMBER NAME-DOCUMENT
RECORD FIELD"(80)
/*
In the above example, member DOCUMENT of the partitioned data set
ZQXAORT.IBM.DATA is transferred to the VAX and placed in the file
IBMDATA.DAT in the directory [ZQX.IBM]. The JES2 job log for the
job is routed to JOBLOG.DAT in the directory IZQX].
Notes on Model B
- The first DNX card (line 3) may be omitted if you do not want a copy
of the JES2 log.
- The DNX card you place in single quotes in the TITLE ITEM specification
(in line 10) can be no longer than 40 characters.
- Additional members may be specified by repeating the MEMBER NAME
statement as necessary. When multiple members are specified, they will
all be placed in the same output file on the VAX and must be manually
separated.
- See also "Notes Pertaining to All Jobs" at the end of item 2.
-------
Model C
//uid JOB (acctfimas,bbbb),IBMTOVAX,PRTY-4,TIME-(,3),
// PASSWORD-password
//*DNX vaxuid joblogfilespec
//STEP1 EXEC PGM-IEBPTPCH
//SYSUT1 DD DSN-datasetname,DISP-(OLD,KEEP)
//SYSUT2 DD SYSOUT-B
//SYSPRINT DD SYSOUT-A
//SYSIN DD *
PUNCH MAXFLDS-1,TYPORG-PO
TITLE ITEM=('DNX vaxuid outputfilespec',1)
RECORD FIELD-(80)
/*
Example
//ZQX JOB (AORTFAKET.MZQX),SAMPLE,PRTY-4,TIME-(,3),
// PASSWORD-RTPNC
//*DNX ZQX USER$DISK:(ZQXJJOBLOG.DAT
//STEP1 EXEC PGM-IEBPTPCH
//SYSUT1 DD DSN-ZQXAORT.IBM.DATA.DISP-(OLD.KEEP)
//SYSUT2 DD SYSOUT-B
//SYSPRINT DD SYSOUT-A
//SYSIN DD *
PUNCH MAXFLDS-1,TYPORG-PO
TITLE ITEM-CDNX ZQX USER$DISK:[ZQX.IBM]IBMDATA.DAT',I)
liEMBER NAME-DOCUMENT
RECORD FIELD-(80)
/*
In the above example, all members of the partitioned data set
ZQXAORT.IBM.DATA are transferred to the VAX and placed in the file
IBMDATA.DAT in the directory [ZQX.IBM]. The JES2 job log for the
job is routed to JOBLOG.DAT in the directory [ZQX].
Notes on Model C
- The first DNX card (line 3) may be omitted if you do not want a copy
of the JES2 log.
- The DNX card you place in single quotes in the TITLE ITtM specification
(in line 10) can be no longer than 40 characters.
- All data set members will be placed in the same output file on the VAX
and must be manually separated.
- See also "Notes Pertaining to All Jobs" at the end of item 2.
J-5
-------
Model D
//uid JOB (acctfimas,bbbb),IBMTOVAX,PRTY-4,TIME-(,3),
// PASSWORD-password
//*DNX vaxuid joblogfilespec
//STEP1 EXEC PGM-IEBGENER
//SYSIN DD DUMMY
//SYSUT1 DD DSN-datasetname,DISP-(OLD,KEEP)
//SYSUT2 DD SYSOUT-A
//SYSPRINT DD SYSOUT-A
/*
Example
//ZQX JOB (AORTFAKET.MZQX),SAMPLE,PRTY-4,TIME-(,3),
// PASSWORD-RTPNC
//*DNX ZQX USER$DISK:IZQX.IBMjTRANSFER.DAT
//STEP1 EXEC PGM-IEBGENER
//SYSIN DD DUMMY
//SYSUT1 DD DSN-ZQXAORT.IBM.DATA.DISP-(OLD,KEEP)
//SYSUT2 DD SYSOUT-A
//SYSPRINT DD SYSOUT-A
/*
In the above example, the sequential data set ZQXAORT.IBM.DATA is
transferred to the VAX and placed in the file TRANSFER.DAT in the
directory [ZQX.IBM].
Notes on Model D
- If the data set being transferred is partitioned, specify one member
name along with the data set name in line 6.
Example; ZQXAORT.IBM.DATA(DOCUMENT)
To transfer multiple members, you must submit multiple Jobs.
- The output received on the VAX will be in "print" form, containing
header pages, the JES2 job log, and the data set text imbedded within
it. You oust edit this file and delete the extraneous text.
- See also "Notes Pertaining to All Jobs" below.
Notes Pertaining to All Jobs
- All Job statements and parameters must be in uppercase, or the Job will fail,
- The Job card parameters used in the models (PRTY and TIME) are samples.
The Jobs will run with the given parameters, but you may wish to modify
them and/or add other parameters to suit your particular needs. If you
need additional information on these parameters, consult Section 4.0 in the
NCC-IBM User's Guide.
J-6
-------
3. After creating your Job, the last step is to submit it to the IBM through
the SNA gateway. There are three methods for doing this:
a. An automated procedure can be used by typing:
IBMSUBMIT filename
You will be prompted for your VAX password. Your job will be
submitted using the /NOLOG and /NOTIFY qualifiers.
b. At the DCL prompt, type the following command:
SUBMIT/SNA/NOLOG VAXTM1"userid password":filename
where "userid" and "password" are those belonging to the
signed-on VAX user and where "filename" is the job file.
(Use quotation marks as shown in the the command.)
Note; It is Important to use the /NOLOG qualifier to avoid any
possible compromise to your password's secrecy. Without
this qualifier, a log is created that includes your
User-ID and password.
OR
c. Allow WORLD read access to the file with the following command:
SET FILE/PROTECTION=W:R filename
Then submit it with the following command:
SUBMIT/SNA filename
Note; If the file resides in a subdirectory, WORLD must have
read or execute access to that directory as well.
With either method, if the file you are submitting contains records greater
than 80 characters in length, you must add the following qualifier:
/RECORD-n
where "n" Is the maximum number of characters in a record.
For example, if the file you are transferring has a maximum record length
of 120, you would use the command SUBMIT/SNA/RECORD-120 filename. The
maximum record size allowed is 250.
J-7
-------
4. After issuing the SUBMIT command, you will receive a message stating that
the job has been assigned to the SNARJE$READER queue to await transmission
to the IBM. You may check its status by typing the following command:
SHOW QUEUE SNARJESREADER
You may also review the job's log file to be sure that it vas properly
submitted. It can be found in:
luid]f ilename.LOG
where "(uld]" Is your top-level file directory and "filename" is the
name of the file you submitted.
If you wish to check the job's status as it executes on the IBM, you must
log on to that system and use a utility such as QUEUE or SDSF to do so.
(See Section 5.1 of the NCC-IBM User's Guide for assistance.)
When the job is executed on the IBM, a VAX MAIL message will be sent to
the username specified in the DNX card, Informing you that the job has
been completed and that the output has been routed to the file specified
in the DNX card.
J-8
-------
Appendix R
PLOTTING WITH THE CALCOMP 1051 PLOTTER
ON THE NCC-VAX CLUSTER
GENERAL
It is possible to create plot files on the VAX cluster that are compatible
with the CalCoop plotter in the NDPO Print Room. For you, the user, the main
interface to the plotter is contained in the VMS PLOT command, which queues a
temporary plot "header" and your plot file to a printer queue called ~CALC$PLOT'
This queue is regularly dumped to a magnetic tape, which is then carried to
the Print Room for plotting. (The program to dump plot files to tape is run
at approximately the same time a similar program is run on the IBM systems -
at 7:00 a.m., 12:00 noon, and 5:00 or 6:00 p.m., depending on the operator
workload.)
A plot file can be created by the utilities within SAS/GRAPH or by a FORTRAN
program that calls the plotting subroutines supplied by CalComp. The SAS/GRAPH
interface is explained further in the following section labeled "SAS/GRAPH"
and in the "SAS/GRAPH User's Guide" produced by SAS Institute, Cary, N.C.
Any FORTRAN interface must be created by you and must be compatible with the
subroutines in the CalComp library. A brief description of each subroutine
is provided in the following section labeled "CALCOMP-SUPPLIED BASIC ROUTINES"
and In the manual entitled "Programming CalComp Electromechanical Plotters,"
Manual 1006G, 1985 version. This manual Day be obtained from CalComp by
ordering part number W0001-050 from the Sales Department at this number:
(BOO)-CALCOMP - which translates to (800) 225-2667
PLOTTER SPECIFICATIONS
The plotter in the NDPD Print Room is a CalComp 1051 plotter with a CalComp
925 controller. It has four pens labeled "1" through "4" in the following
order:
Black (1), Red (2), Blue (3), Green (4)
The 1051 is considered an "offline" plotter. In this case, plot files must be
created on a magnetic tape on a host system in CalComp-compatlble format and
then hand-carried to, and loaded on, the 925 controller unit. Also, the
CalComp-supplled routines for VAX/VMS systems were written with the assumption
that a dedicated tape drive would be continuously online and available to
users. Since this is not the case within our current configuration, NCC-VAX
Cluster users must first create a plot file, then send that file to a "plotter
queue" (in this case, CALC$PLOT), which will be written to tape at reular
intervals*
K-l
-------
Other plotter specifications Include:
o Width (length of Y axis) - 33 inches
o Stepsize • .001 inches
o Plotting speed - 10 inches/sec.
CALCOMP-SUPPLIED BASIC ROUTINES
As noted earlier, CalComp supplies a set of routines with each controller.
There are several groups of routines, although the NCC currently has only the
HCBS (Host Computer Basic Software) set. The routines are written in FORTRAN
and may be accessed by executing a standard CALL command, then linking the
object module from your main routine to the CalComp object module library,
which has a system-wide logical name of CALCOMP.
These routines permit you to move the pen, change colors of the plot (within
the limits of the colors contained on the four pens), and draw annotation,
axes, and numbers. As the name of the set indicates, the routines are truly
basic. There are no routines to plot arcs and circles, although this can be
done through careful coding.
If you want to create an interface of your own FORTRAN program with CalComp
routines, thereby creating your own plot file, you must first compile your
program (e.g., $FOR MYPLOT), then link it to the CALCOMP library using the
/LIB qualifier, with your program acting as the "main" routine (e.g., $LINK
MYPLOT,CALCOMP/LIB). Before running the resultant executable image, assign
the logical nane CP to the filename into which you would like your output
placed (e.g., $ASSIGN/USER MYPLOT.DAT CP). To queue the file to the plotter
queue, use the VMS PLOT command (e.g., $PLOT IfYPLOT). For a full discussion
of this command, see the following section labeled "THE VMS PLOT COMMAND."
The following list provides a brief overview of the CalCotop-supplied plotting
subroutines currently available on the NCC-VAX Cluster. If you plan to use
these routines extensively, you should obtain the CalComp programming reference
manual mentioned earlier.
SYMBOL - produces plot annotation at any angle and in practically any
size.
NUMBER - converts a floating-point number to the appropriate decimal
equivalent.
SCALE - examines the data values in an array and determines a starting
value (minimum or maximum) and a scaling factor (positive or
negative).
AXIS - draws a scaled axis at any angle, divides the line into 1-inch
segments, annotates the divisions with appropriate scale values,
and labels the axis with a centered title.
K-2
-------
LINE - produces a line plot of the pairs of data values in two arrays
(X and Y).
PLOTS - performs initialization of the PLOT subroutine. It opens the
plot output device and, in the NDPD configuration, creates the
first Search record. This is the first call in a plot and
should be called only once per plot.
PLOT - moves the plotter pen in a straight line to a new position,
with the pen either up or down during the movement. The PLOTS
entry oust be called before any other entries are called.
NEWPEN - enables program selection of any of the available pens.
FACTOR - enables enlargement or reduction in size of the entire plot by
changing the ratio of the desired plot size to the normal plot
size.
WHERL - obtains the pen's current location for optimizing pen movement.
Most of these routines have several arguments that must be passed to and from
the calling program. A complete discussion of each of these arguments is
Included in the CalComp programming reference manual mentioned above.
SAS/GRAPH
Because the CalComp 1051 plotter and 923 controller are not supported by
existing SAS/GRAPH device drivers, a separate device driver was created.
This driver is called CALC1051. It is available only to SAS/GRAPH versions
5.16 and up. It may be invoked by issuing a "GOPT10NS UEVICE-CALC1051;"
statement in your SAS/GRAPH plotting routine. This statement, in turn,
Invokes the SAS/GRAPH metagraphics utility, which creates a metafile, and
then a CalComp-compatible output file that can be sent to the CALC5PLOT plotter
queue. A sample SAS command file is listed below:
GOPTIONS COLORS-(BLACK,RED,GREEN,BLUE) DEVICE-CALCIOSI GSFNAME=C?:
PROC GTESTIT;
RUN;
ENDSAS;
The GSFNAME-CP option is used to point to the logical name that will direct
output from the metagraphics utility to the filename of your choice (see the
following discussion of the VMS PLOT command). There are several other ways
of doing this, including using the SAS X command to assign a filename to the
CP logical name, or using the SAS FILENAME command to write the output file,
or using the ASSIGN command in a VMS command file just before invoking SAS.
The following Is an example command file that could be used interactively to
generate plot files:
K-3
-------
$ SET VERIFY
$ SET DEFAULT $YOURS.CALCOMP!
$ ASSIGN PLOTFILES.OUT CP
$ SAS MYSAS.SAS
$ DIR/SIZE PLOTFILES.OUT
$ PLOT PLOTFILES.OUT;*
$ DEASSIGN CP
S SET NOVERIFY
$ EXIT
Keep in mind that the PLOT command, In this case, will generate plots in the
reverse order in which they were created (if this matters).
Since the CalComp 1051 is not supported by SAS and is also offline, some of
the features of the SAS/GRAPH implementation are awkward. The most difficult
of these is the failure of the SAS/GRAPH metagraphics utility to work correctly
under VKS in batch mode. What happens in batch mode is this: After SAS/GRAPH
produces the metafile (called FOR023.;) for each "picture" or plot generated
by the plot routine, it is unable to run the metagraphics utility. SAS,
Inc., calls this an "unfixable" problem and recommends that each user run the
metagraphics utility - in this case, by Issuing a $RUN SAS$SASLIB:CALC1051
command for each "picture" created by SAS/GRAPH.
To add to the difficulty, the metagraphics utility is expecting a file called
FOR023.DAT (not FOR023.;). Therefore, before running SAS an ASSIGN command
must be issued that "points to" the correct filename. Also, since the output
from the metagraphics utility will be directed toward the logical name CP, an
ASSIGN/USER command should be issued before each Invocation of the SRUN
SAS$SASLIB:CALC1051 command, which in turn must be run for each "picture"
file (metagraphics file) that has been created.
The following command file is one way of handling SAS/GRAPH in VMS batch mode:
$ SET VERIFY
$ SET DEFAULT SYOURS.SAS!
$ ASSIGN FOR023.DAT FOR023
$ SAS MODEL.SAS
S DIR/SIZE/DATE FOR023.DAT
$ LOOP:
FILENAME - F$SEARCH("FOR023.DAT;*")
SHO SYM FILENAME
IF FILENAME.EQS."" THEN GOTO DONE
ASSIGN/USER SASGRAPH.OUT CP
RUN SAS$SASLIB:CALC1051
DELETE 'FILENAME'
COCO LOOP
$ DONE:
$ PLOT SASGRAPH.OUT.*
$ DIR/SIZE SASGRAPH.OUT
$ SHOW QUE/ALL CALC5PLOT
$ DEASSIGN FOR023
$ SET NOVERIFY
§ EXIT
K-4
-------
Notice that in the loop there is a VMS DELETE command that deletes the metafile
(FOR023.DAT) as you progress down the filename list. This command enables
you to generate a new, CalComp-compatible file for each metafile produced and
also keeps your directory clean of metafiles, which could cause confusion if
several batch jobs were to run in sequence.
This procedure will result in another reversal of the order of the plots when
sent to the CALCSPLOT file, so they will be plotted in the same order in
which they were created.
Additional information on using SAS/GRAPH on VMS is available through several
SAS publications, including the "SAS/GRAPH User's Guide," "Technical Report
P-128," and "Technical Report P-138."
THE VMS PLOT COMMAND
As has been noted earlier, the CalComp routines originally assumed that a
dedicated tape drive would be continually online to receive plots. Since
this situation does not currently exist for NCC-VAX Cluster users, the CalComp
routines were modified to send output to a file that translates to the logical
name CP. Therefore, before running the executable image of your recently
created plot program (now called (MYPLOT.EXE), you must assign the logical
name CP to the filename of your choice (e.g., $ASS1GN MYPLOT.DAT CP). If you
do not assign the logical name to a filename, a file called CP.DAT will be
created.
Once the plot has been created, issue the VMS PLOT command to queue the file
to the CALC$PLOT queue (e.g., $PLOT MYPLOT.DAT). Two messages will subsequently
be displayed on your terminal. The first message will indicate that a
temporary plot header has been created and queued to CALCSPLOT just prior to
your plot file. This plot header contains your VAX username, the node name
and CPU type of the system on which you created the plot, and the date and
time of plot creation. It will be temporarily stored in your root directory
(SYS$LOGIN directory) with a unique filename constructed from the current
time of day in hours, minutes, and seconds. When the transfer of plot files
to tape has been completed by the operator, your job entries on the CALC5PLOT
queue will be deleted, and your temporary plot header will be deleted from
your SYS$LOGIN directory. Do not move or delete this temporary header. It
is quite small and will take no more than a few blocks of disk space.
Please note that the PLOT command accepts TIP qualifiers and only one parameter.
You may use the "*" wildcard character to plot a complete set of files.
K-5
-------
Appendix L
ALPHABETIC LISTING OF COMMON DCL COMMANDS
ALLOCATE
Function
Reserves a device for exclusive access and optionally associates a logical
nane with it.
Format
ALLOCATE device-name [logical-name]
Command Qualifiers
/[NO]LOG
/[NO]GENERIC
Associated Command
DEALLOCATE device-name
Examples
$ ALLOCATE DBA3:
IDCL-I-ALLOC, _DBA3: allocated
$ DEALLOCATE MUAO:
$ ALLOCATE MU: TAPEJJNIT
ZDCL-I-ALLOC, _MUAO: allocated
$ SHOW LOGICAL TAPEJJNIT
"TAPE UNIT" - " MUAO:" (LNM$PROCESS TABLE)
$ DEALLOCATE TAPEJUNIT:
$ DEASSIGN TAPE UNIT
L-l
-------
APPEND
Function
Adds the contents of a specified flle(s) to the end of a specified file.
Format
APPEND Input-file output-file
Command Qualifiers
/BACKUP
/BEFORE[-time]
/BY_OWNER[-UIC]
/[NO]CONFIRM
/CREATED
/EXCLUDE-[filename]
/EXPIRED
/[NO]LOG
/MODIFIED
/SINCE[-time]
Defaults
/CREATED
/BEFORE-TODAY
/NOCONFIRM
/CREATED
/CREATED
/NOLOG (displays file specifications)
/CREATED
/SINCE-TODAY
File Qualifiers
/[NO]CONTIGUOUS
/[NO]NEW_VERSION
/PROTECTION-[code]
/[NO]READ_CHECK
/[NO]WRITE_CHECK
/NOCONTIGUOUS
/NONEW_VERSION
/[NO]READ_CHECK
/NOWRITE CHECK
Examples
$ APPEND TEST3.DAT TESTA.DAT
$ APPEND/NEW VERSION/LOG *.TXT MEM.SUM
L-2
-------
CONTINUE
Function
Resumes execution of a DCL command, program, or command procedure which has
been Interrupted by CTRL-Y or CTRL-C (no qualifiers).
Example
$ RUN PROCRAMl
CTRL-Y
$ SPAWN SHOW TIME
ZDCL-S-SPAWNED, process USER_1 spawned
ZDCL-S-ATTACHED, terminal now attached to process USER 1
15-DEC-1985 12:04:12 ~~
ZDCL-S-RETURNED, control returned to process USER
$ CONTINUE
Within a command procedure:
§ ON SEVERE ERROR THEN CONTINUE
L-3
-------
COPY
Function
Creates a new file from one or more existing files.
Format
COPY input-file-spec[,...] output-flie-spec
Command Qualifiers*
/BACKUP
/BEFORE!-time]
/BY_OWNER[-UIC]
/[NOJCONFIRM
/CREATED
/EXCLUDE-[filename]
/EXPIRED
/[NOJLOG
/MODIFIED
/SINCE[-time]
Defaults
/CREATED
/BEFORE-TODAY
/NOCONFIRM
/CREATED
/CREATED
/NOLOG (displays file specifications)
/CREATED
/SINCE-TODAY
File Qualifiers
/[NO]CONTIGUOUS
/PROTECTION-[code]
/[NO]READ_CHECK
/[NO]WRITE CHECK
/NOCONTIGUOUS
/[NO]READ_CHECK
/NOWRITE CHECK
Examples
$ COPY/LOG/WRITE_CHECK *.DAT MTAO:
$ COPY [ACCTNG]QUARTERLY.RPT [SUMM]QUARTER1.RPT
-------
CREATE
Function
Creates one or more sequential disk files from records that follow the command
In the Input stream.
Format
CREATE file-spec[,...]
Command Qualifiers Defaults
/[NO]LOG /NOLOG
/PROTECTION-code
Example
$ CREATE A.DAT,B.DAT
Input line one for A.DAT...
Input line two for A.DAT...
CTRL-Z
Input line one for B.DAT.
Input line two for B.DAT.
CTRL-Z
$
L-5
-------
CREATE/DIRECTORY
Function
Defines a new directory or subdirectory for cataloging files. The /DIRECTORY
qualifier Is required.
Format
CREATE/DIRECTORY directory-spec!....]
Command Qualifiers Defaults
/[NO]LOG /NOLOG
/PROTECTION-code
/VERSION_LIMIT-n
Examples
$ CREATE/DIRECTORY [MALCOM.SUB]
$ SET.DEFAULT [MALCOM.SUB]
$ CREATE/DIRECTORY/PROTECTION-(S:RWED,0:RWED,G,W)-
_$ [MALCOM.SUB.HELP]
To Delete a Directory
1. Make sure It contains no files or subdirectories
2. SET PROTECTION-(OWNER:D) directory-name
3. Delete the directory.
L-6
-------
CREATE/FPL
Function
Creates empty RMS data file using previously created File Definition Language
(FDL) description file.
Format
CREATE/FDL-FDL-flie-spec file-spec
Example
$ CREATE/FDL-COMDATA.FDL COMDATA.DAT
L-7
-------
DEFINE/KEY
Function
Associates an equivalent string and a set of attributes with a key on the
terminal keyboard. The /KEY qualifier Is required.
Format
DEFINE/KEY key-name equivalent-string
Command Qualifiers Defaults
/[NO]ECHO /ECHO
/[NO]ERASE /NOERASE
/[NO]LOG /LOG
/[NO]TERMINATE /NOTERMINATE
Associated Commands
$ SET TERMINAL/APPLICATION
(/NONUMERIC)
$ DELETE/KEY key-name
/ALL
/LOG
$ SHOW KEY
Definable Keys
PF1 ... PFA
LEFT
RIGHT
Example
$ DEFINE/KEY PF3 "SHOW TIME"/TERMINATE
Z DCL-I-DEFKEY, DEFAULT key PF3 has been defined
L-8
-------
DELETE
Function
Deletes one or more files from a mass storage disk volume.
Format
DELETE file-spec[,...]
Command Qualifiers Defaults
/BACKUP
/BEFORE[-time]
/BY_OWNER-uic
/[NOJCONFIRM /NOCONFIRM
/CREATED
/[NOJERASE
/EXCLUDE
/EXPIRED
/[NO]LOG /NOLOG
/MODIFIED
/SlNCE[-tlme]
Examples
$ DELETE TEST.*;*,*.OBJ;*/LOG
$ DELETE *.FOR/CONFIRM
$ DELETE *.DAT;*/BEFORE-01-JAN-84/LOG
L-9
-------
DELETE/ENTRY
Function
Deletes one or more Jobs from the Job queue.
Format
DELETE/ENTRY-(entry number,...) queue name:
Examples
$ PRINT TEST1.TXT
Job TEST1 (queue SYS$PRINT, entry 110)
$ DELETE/ENTRY-110 SYS$PRINT
$ SUBMIT/HOLD TEST2
Job TEST2 (queue SYS$BATCH, entry 151) holding
$ DELETE/ENTRY-151 SYS$BATCH
L-10
-------
DIFFERENCES
Function
Compares the contents of two disk files and creates a listing of those records
that do not match.
Format
DIFFERENCES master-file-spec [revision-file-spec]
Command Qualifiers Defaults
/COMMENT_DELIMITER[-(delimlter[,...]]
/IGNORE-(option[,...])
/MATCH-slze /MATCH-3
/MAXIMUM_DIFFERENCES-n
/MERGED[-n] /MERGED-1
/(NO]NUMBER /NUMBER
/OUTPUT[-file-spec]
/PARALLEL[-n]
/SEPARATED[-(input-flie[,...]>]
/WIDTH-n
/WINDOW-size
/IGNORE - (options)
BLANK_LINES
COMMENTS
FORM_FEEDS
TRAILING_SPACES
SPACING
Example
DIFFERENCES CHARTS.FOR CHARTS2.FOR
(shows differences)
Number of different sections found:
Number of different records found:
L-ll
-------
DIRECTORY
Function
Provides a list of files or Information about a file or group of files.
Format
DIRECTORY [flie-spec[,...]]
Command Qualifiers
/BEFORE[-time]
/BRIEF
/COLUMNS-n
/CREATED
/[NOJDATE[-option]
/EXCLUDE-(file-spec[,
/FULL
/[NO]HEADING
/MODIFIED
/OUTPUT[-flle-spec]
/[NO]OWNER
/[NO]PROTECTION
/SINCE[-time]
/[NO]SIZE-ALLOCATED
-ALL
-USED
/TOTAL
/[NO]TRAILING
/VERSIONS-n
1)
Defaults
/BRIEF
/COLUMNS-A
/CREATED
/NODATE
/BRIEF
/HEADING
/CREATED
/NOOWNER
/NOPROTECTION
/NOSIZE
/BRIEF
/TRAILING
Example
$DIR
$DIR *.FOR
$DIR/OUTPUT-MYDIR.LIS *.*
$DIR/SINCE-YESTERDAY
L-12
-------
DUMP
Function
Displays or prints the contents of files or volumes In ASCII, decimal, octal,
or hexadecimal representation.
Format
DUMP file-spec
Command Qualifiers
/BLOCKS[-option] START:n;END:n;COUNT:n
/BYTE
/DECIMAL
/FILE_HEADER
/FORMATTED
/HEADER
/HEXADECIMAL
/LONGWORD
/NUMBER[-n]
/OCTAL
/OUTPUT[-file-spec]
/RECORD[-optIon] START:n;END:n;COUNT:n
/WORD
Examples
$ DUMP TEST.DAT
$ DUMP TEST.DAT/OCTAL/BYTE
L-13
-------
EDIT/FPL
Function
Creates or modifies an FDL RMS file description template.
Format
EDIT/FDL FDL-flle-spec
L-U
-------
INITIALIZE
Function
Formats and writes a label on a mass storage volume.
Format
INITIALIZE device-name volume-label
Command Qualifiers
/[NO]ERASE
/OWNERJJIC-uic
/PROTECTION-code
Qualifiers for Magnetic Tapes
/DENSITY-denslty-value
/OVERRIDE-(optlon,...)
Example
$ ALLOCATE MS: TAPEJJNIT
ZDCL-I-ALLOC, _MSAO: allocated
$ INITIALIZE TAPEJJNIT: PROGS
$ MOUNT TAPEJJNIT: PROGS
ZMOUNT-I-MOUNTED, PROGS mounted on MSAO:
$ DISMOUNT TAPEJJNIT:
$ DEALLOCATE TAPEJJNIT:
$ DEASSIGN TAPE UNIT
L-15
-------
INQUIRE
Function
Requests interactive assignment of a value for a symbol during the execution
of a command procedure*
Format
INQUIRE symbol-name [prompt-text]
Command Qualifiers
/GLOBAL
/LOCAL
/[NO]PUNCTUATION
Example
$ INQUIRE CHECK "Enter Y[ES] to continue'
$ IF .NOT. CHECK THEN EXIT
L-16
-------
LOGOUT
Function
Terminates an Interactive terminal session.
Format
LOGOUT
Command Qualifiers Defaults
/BRIEF /BRIEF
/FULL /BRIEF
/[NOJHANGUP (Requires PHY_IO privilege.)
L-17
-------
MERGE
Function
Invokes the VAX-11 SORT utility to combine two through ten similarly sorted
Input files and create a single output file. Note that Input files to be merged
MUST be In sorted order.
Format
^^^m
MERGE Input-flie-spec!,Input-flle-spec2[,...] output-flie-spec
Command Qualifiers
/CHECKJEQUENCE
/COLLATING SEQUENCE-sequence
/DUPLICATE
/KEY«(fleld[,...J)
/SPECIFICATION-flie-spec
/STABLE
Defaults
/COLLATING SEQUENCE-ASCII
Input File Qualifiers
/FORMAT-(flie-attribute[,...])
Output File Qualifiers
/ALLOCATION-n
/BUCKET_SIZE-n
/CONTIGUOUS
/FORMAT«(record-format[,...])
/1NDEXE D_SEQUENTIAL
/OVERLAY
/RELATIVE
/SEQUENTIAL
/STABLE
Example
$ MERGE/KZY-(POSITION:1,SIZE:80)/CHECK SEQUENCE-
$[BILLING.WORKJCUST01.DAT,- "~
~$[BILLING.WORKJCUST02.DAT,-
_$[BILLING.WORK]CUST03.DAT -
__$ [ BILLING. WORK JBILLS.DAT
L-18
-------
MOUNT
Function
Makes a mass storage volume available for processing and optionally assign a
logical name to it.
Format
MOUNT device-name [volume-label] [logical-name]
Command Qualifiers Defaults
/[NOJASSIST /ASSIST
/COMMENT-"string"
/FOREIGN
/[NOJMESSAGE
/OVERRIDE=(option,...) (IDENTIFICATION, OWNER IDENTIFIER)
/OWNER_UIC-uic ~~
/FROTECTION-code
/[NO]WRITE /WRITE
Qualifiers for Magnetic Tapes Defaults
/BLOCKSIZE-n /BLOCKSIZE«2048
/DENSITY-density-value
/[NOJHDR3 /HDR3
/RECORDSIZE-n
Associated Commands
DISMOUNT device-name [/[NOJUNLOAD]
Example
$ ALLOCATE MTA1:
IDCL-I-ALLOC, _MTA1: allocated
$ MOUNT/OVERRIDE-OWNER MTA1: DECUS
XMOUNT-I-MOUNTED, DECUS mounted on MTA1:
$ DISMOUNT MTA1:
$ DEALLOCATE MTA1:
L-19
-------
PRINT
Function
Queues one or more files for printing, either on a default system printer or on
a specified device.
Format
PRINT file-spec[,...]
Command Qualifiers
/AFTER-tlne
/CHARACTERISTICS-(c
/FORMS-type
/JOB_COUNT-n
/NAME-job-name
/[NOJNOTIFY
/OPERATOR-message
/QUEUE»queue-name
Defaults
/JOB_COUNT=1
/NONOTIFY
File Qualifiers
/COPIES-n
/(NO]DELETE
/[NOJFEED
/[NOJFLAG
/[NO]HEADER
/PAGES-n
/SPACE
Defaults
/COPIES-1
/NODELETE
/FEED
/NOHEADER
L-20
-------
PURGE
Function
Deletes all but the highest-numbered version or versions of a specified file or
files.
Format
PURGE [file-spec!....]]
Command Qualifiers Defaults
/ERASE
/KEEP-n /KEEP-1
/[NO]LOG /NOLOG
Examples
$ PURGE/LOG
$ PURGE *.LIS
$ PURGE BADFILE.TXT/KEEP-5
L-21
-------
RENAME
Function
Changes the directory specification, file name, file type, or file version of
an existing disk file or disk directory.
Format
RENAME Input-file-spec[,...] output-flie-spec
Command Qualifiers Defaults
/[NO]CONFIRM /NOCONFIRM
/[NO]LOG /NOLOG
/[NO]NEW_VERSION /NEWJTERSION
Examples
$ RENAME FINANCE.DAT ACCOUNTING.DAT
$ RENAME REPORT1.LIS [.REPORTS]*.*
$ RENAME [DEPT1JTEST_FILE.DAT;! [DEPT2JPROD_FILE.DAT;!
L-22
-------
REQUEST
Function
Displays a string at the system operator's terminal and optionally requests a
reply.
Format
REQUEST "message-text"
Command Qualifiers
/REPLY
Example
$ REQUEST "Please mount tape number 53 on MFAO:"
L-23
-------
SEARCH
Function
Searches one or nore files for a specified strlng(s) and lists all the lines
containing occurrences of the strlng(s).
Format
SEARCH flie-spec[,...] search-string(,...]
Command Qualifiers Defaults
/[NO]EXACT /NOEXACT
/EXCLUDE-(flie-spec[,...])
/FORMAT-optlon /FORMAT-TEXT
/[NOJHEAD1NG /HEADING
/[NO]LOG /NOLOG
/MATCH-optlon /MATCH-OR
/[NO]NUMBERS /NONUMBERS
/[NO]OUTPUT[-flie-spec] /OUTPUT-SYS$OUTPUT
/[NOJREMAINING /NOREMAINING
/tNO]WINDOW[-(nl,n2)] /NOWINDOW
Examples
$ SEARCH CABLE.MEM,NEWDATE.MEM "MANUAL TITLE"
$ SEARCH/OUTPUT-RESULTS.DAT/WINDOW-9 DISLIST.MEM NAME
L-24
-------
SET BROADCAST
Function
Enables you to selectively screen out various kinds of messages being broadcast
to your terminal.
Format
SET BROADCAST-Cclass-naae,...)
Class Names
ALL
[NOJDCL
[NO]GENERAL
[NO]MAIL
NONE
[NO]OPCOM
[NO]PHONE
[NO]QUEUE
[NO]SHUTDOWN
[NO]URGENT
Associated Command
SHOW BROADCAST
Example
$ SET BROADCAST-(NOMAIL, NOPHONE)
L-25
-------
SET DEFAULT
Function
Changes the default device and/or directory name for the current process.
Format
SET DEFAULT [device:][directory-spec]
Associated Commands
SHOW DEFAULT
Examples
$ SET DEFAULT DBA1:
$ SET DEFAULT [USER1]
$ SET DEFAULT SYS$SYSDEVICE
L-26
-------
SET FILE
Function
Modifies the characteristics of one or more files.
Format
SET FILE file-spec I,..]
Command Qualifiers
/[NO]BACKUP
/BEFORE[-time]
/BY_OWNER[-uic]
/CONFIRM
/CREATED
/END_OF_FILE
/ERASE_ON_DELETE
/EXCLUDEDfile-spec,...)
/[NOJEXPIRATION DATE[-date]
/[NOJLOG
/OWNER_UIC[-uic]
/PROTECTION[-code]
/SINCE[-time]
/TRUNCATE
/UNLOCK
/VERSION LIMIT-n
Example
$ SET FILE/OWNER_UIC-[322,1A5] SPOTLIGHT.LIS
L-27
-------
SET PASSWORD
Function
Allows users to change their own passwords.
Format
SET PASSWORD
Command Qualifier
/GENERATE
Example
$ SET PASSWORD
Old password: (old)
New password: (new)
Verification: (new)
L-28
-------
SET PROMPT
Function
Enables the user to change the DCL prompt screen.
Format
SET PROMPTf-strlng]
Example
$ SET PROMPT-"DCL >"
L-29
-------
SET TERMINAL
Function
Changes the characteristics of a specified terminal.
Format
SET TERMINAL [device-name[:]]
Command Qualifiers
/[NOJADVANCED_VIDEO
/[NO]ANSI_CRT
/APPLICATION_KEYPAD
/[NO]BROADCAST
/[NO]DEC_CRT[-(valuel,value2)J
/DEVICE_TYPE-terminal-type
/[NOJECHO
/[NOJFULLDUP
/[NO]HALFDUP
/[NOJHARDCOPY
/INQUIRE
/INSERT
/LINE_EDITING
/[NO]LOCAL_ECHO
/[NO]LOWERCASE
/NUMERIC_KEYPAD
/OVERSTRIKE
/PAGE[-n]
/PRINTER_PORT
/[NO]REGIS
/[NOJSCOPE
/SPEED-rate
/[NO]TAB
/[NOJTTSYNC
/[NO]TYPE AHEAD
/UNKNOWN "~
/[NO]UPPERCASE
/VT52
/VT100
/WIDTH-n
/[NO]WRAP
Defaults
/NUMERIC KEYPAD
/BROADCAST
/ECHO
/HALFDUP
/HALFDUP
/OVERSTRIKE
/NOLOCAL_ECHO
/NUMERIC_KEYPAD
/OVERSTRIKE
/NOTAB
/TTSYNC
/TYPE AHEAD
/WRAP
Associated Command
$ SHOW TERMINAL
L-30
-------
SHOW
Function
Displays Information about the current status of the process, the system, or
devices In the system.
Format
SHOW option
Options
[DAY]TIME
DEVICES
MAGTAPE
MEMORY
NETWORK
PRINTER
PROCESS
QUEUE I/CHARACTERISTICS]
[/FORM]
I/ALL]
QUOTA
STATUS
SYSTEM
USERS
L-31
-------
SORT
Function
Invokes the VAX Sort Utility (SORT) to reorder the records In a specified file,
Format
SORT Input-file-spec[,...] output-flie-spec
Command Qualifiers Defaults
/COLLATING_SEQUENCE-sequence /COLLATING SEQUENCE-ASCII
/KEY-(field[,...])
/PROCESS-type /PROCESS-RECORD
/SPECIFICATION[-file-spec]
/STABLE
/STATISTICS
/WORK_FILES-n /WORK_FILES-2
Input File Qualifiers
/FORMAT-(flie-attribute[,...])
Output File Qualifiers
/ALLOCATION-n
/BUCKET_SIZE-n
/CONTIGUOUS
/FORMAT-(record-format[,...]>
/1 NDEXED_SEQUENTIAL
/OVERLAY
/RELATIVE
/SEQUENTIAL
Examples
$ SORT/KEY-(POSITION:1,SIZE:80)-
_$INSURANCE.LIS CLAIMS.LIS
$ SORT/KEY-(POSITION:47,SIZE:2)-
$/KEY-(POSITION:51,SIZE:7)-
~$GUEST.LIS MAILING.LIS
L-32
-------
SPAWN
Function
Creates a subprocess or the current process. The context of the subprocess
Is copied from the current process*
Format
SPAWN [command string]
Command Qualifiers Defaults
/INPUT-flie-spec /INPUT-parent terminal
/[NO]LOG /LOG
/OUTPUT-flle-spec /OUTPUT-parent terminal
/PROCESS-Bubprocess name
Example 1
$ RUN LONGREPORT
CTRL-Y
$ SPAWN SHOW SYSTEM
System Prompts
(Performs SHOW SYSTEM command.)
$ CONTINUE
Example 2
$ RUN TEST
CTRL-Y
*INTERRUPT*
$ SPAWN
ZDCL-S-SPAWNED, process USER_1 spawned
ZDCL-S-ATTACHED, terminal now attached to process
$...
$ LOGOUT
Process DSER_1 logged out at 27-FEB-1986 11:10:09.61
ZDCL-S-RETURNED, control returned to process USER
$ CONTINUE
L-33
-------
SPAWN/NOWAIT
Function
Creates a subprocess which does not suspend the parent process during execution.
Format
SPAWN/NOWAIT
Command Qualifiers
/INPUT-file-spec
/INO]LOGICAL NAMES
/OUTPUT-file~spec
/NOTIFY
/PROCESS-subprocess-name
/SYMBOLS
Associated Command
$ ATTACH [process-name] [/IDENTIFICATION-pid]
L-34
-------
STOP
Function
Terminates execution of:
o A command, image, or command procedure that was Interrupted by CTRL-Y.
o A command procedure.
o A sub-process or detached process.
Format
STOP [process-name]
Command Qualifier
/IDENTIFICATION-pld
L-35
-------
SUBMIT
Function
Enters one or more command procedures in the batch Job queue
Format
SUBMIT file-spec[,...]
Command Qualifiers Defaults
/AFTER-time
/CPUTIME-option
/[NO]KEEP
/[NO]LOG_FILE-flie-spec
/NAME-job-name
/[NO]NOTIFY /NONOTIFY
/PARAMETERS-(parameter[,...])
/[NO]PRINTER[-queue-name] /PRINTER-SYS$PRINT
/QUEUE-queue-name /QUEUE-SYS$BATCH
File Qualifiers Defaults
/[NO]DELETE /NODELETE
Examples
$ SUBMIT/NOTIFY STATUS_REPORT
$ SUBMIT BACKUP1/PARAMETERS«(ALL,2,55)/LOG__FILE-BACKUP1.LOG-
S/NOPRINTER/KEEP
L-36
-------
SYNCHRONIZE
Function
Places a process issuing this command In a wait state until the specified Job
completes.
Format
SYNCHRONIZE [job-name]
Command Qualifiers Defaults
/ENTRY-
/QUEUE- /QUEUE-SYS$BATCH
Examples
$ SUBMIT/NAME-GRAPH CHARTS/PARAMETERS-(SORT,PURGE)
$ SUBMIT PLOTS
Contains $ SYNCHRONIZE GRAPH
Will wait for GRAPH to complete before running
$ SUBMIT/NAME-FINANCE ACCTNG.COM (entry 311)
$ SYNCHRONIZE/ENTRY-311
Terminal goes into wait state until FINANCE Job completes.
L-37
-------
TYPE
Function
Displays the contents of a file or group of files.
Format
TYPE file-spec!,...]
Command Qualifier Default
/OUTPUT-flle-spec /OUTPUT-SYS$OUTPUT
/PAGE
L-38
-------
UNLOCK
Function
Makes a previously improperly closed file accessible.
Format
$ UNLOCK file-spec
Command Qualifiers Defaults
/[NO]CONFIRM /NOCONFIRM
/[NO]LOG /NOLOG
Example
$ TY CLASS.DAT
Z TYPE-E-OPEN1N, error opening DISK$USER:[CLASSJCLASS.DAT;1
-as input
-SYSTEM-W-FILELOCKED.file is deaccess locked
$ UNLOCK CLASS.DAT
$ TYPE CLASS.DAT
L-39
-------
Index
- A -
Access to the VAX 2-3
Accounting 3-10
Addresses A-l
Alien tapes 3-b
Application packages 7-1
Archiving tapes 3-9
Assembly language 6-1
Assistance 2-8
Auxiliary services 2-13
- B -
BACKUP utility 5-14, 5-16
Batch Jobs 9-1
Batch queue policy 9-1
Business hours 2-6
- C -
CalComp 1051 Plotter K-l
Centralized Problem Management System ...2-8
Changing default directories 4-4
Changing password 4-4
Chargeback 3-10
Classroom training 2-9
Command format 1-1
Comments and suggestions B-l
Common terminal problems 2-5
Communi cat ion packages • 8-1
Computer room, security 3-6
Concealed device names 4-11
Configuration 2-3
Consultation 2-8
Control keys C-l
Cost of services 3-11, 3-12
Crosstalk 8-2
Index-1
-------
- D -
Data Processing Support Services (DPSS) 2-12
DCL
Commands L-l
with DECnet 8-8
with EVE 5-6
Dearchlvlng tapes 3-9
Debug 6-2
DECnet 8-7
Default logical names 4-11
Dial-up procedure 2-3
DIFFERENCES utility 5-20
Digital Standard Runoff (DSR) 5-19
Directories 4-2
Disk
Backup 3-4
Space management 3-2
Space quotas 3-2
Structure 4-2
- E -
Editors, text 5-1
EDT 5-1
Ethernet 2-4
EVE 5-2
- F -
Facilities 2-1
File
Printing 4-5
Protection 4-7
Protect ring of tape 3-10
Recovery 3-4
Specification 4-3
Transfer 1-1, J-l
Facility Impact Monitoring and Analysis System (FIMAS)...3-1
Financial Management System (FMS) 3-1
FOCUS 7-2
Foreign tapes 3-7
Format of commands • •• • 1-1
Forms 8-1
FORTRAN 6-1
Index-2
-------
- H -
Hardware configuration 2-1
HASP+ 8-5
Help
Facility 2-7
File E-l
On-1 ine 2-7
with EDT 5-1
with EVE 5-3
TAPESYS 5-16
- I -
Interactive access • • •• 2-3
Interactive CPU limit 4-2
International Mathematical & Statistical Library (1MSD..7-3
Introduction 1-1
I/O control 2-7
- K -
KERMIT-32 8-1
Keypad 5-2, 5-4, 6-4
- L -
Languages, programming 6-1, 7-2
Laser printer 4-6
LIBRARIAN utility 5-18
Logging in 4-1
Logging out 4-1
Logical names
Displays 4-11
Tables 4-10
Translation 4-11
Index-3
-------
- M -
MACRO 6-1
MAIL utility 3-2, 5-7
Maintenance of manual 1-2
Manual
Availability 2-7
Distribution 1-2
Maintenance 1-2
MOUNT command 4-8
Mounting
Disks 4-9
Tape s 4-9
- N -
Names, logical 4-1 0
New users • • 3-1
Numbering system • 1-1
- 0 -
On-line
Documentation 2-7
Training 2-12
Organization of NCC 2-1
- P -
Password, changing 3-1, 4-4
PHONE utility 5-9
Phone numbers • • A-l
Physical security 3-6
Printing file 4-5
Printout distribution 2-12
Problems, terminal 2-5
Production Control services.... 3-13
Programming languages 6-1
Protection 4-7
- Q -
Quotas 3~2
Index-4
-------
- R -
Recovery of files 3-4
Registration procedures 3-1, G-l
Reports
Foreign tape 3-9
IMS tape 3-9
Resource management • 3-2
RESTORE command 5-1A
- S -
Sample forms B-l
SAS 7-1
Schedule
Operations 2-6
Disk Backup 3-4
Security 3-6, 4-7
Services 2-1, 2-6
Setting terminal characteristics 2-5
Setting passwords 4-4
Signing on 2-3, 4-1
Site policy 3-1
Slot number of tape 3-8
SNA 8-9
Software
Configuration 2-3
VAX supported F-l
SORT utility 5-22
Special function keys C-l
Subdirectories 4-3
Submitting batch jobs 9-1
Suggestions B-l
Symbolic debugger 6-1
System
Access 4-1
Printer 4-5
Usage 3-12
Index-5
-------
- T -
Tape
Alien 3-8
Allocating drives 4-9
Archiving 3-9
Assignment 3-6
Cleaner/Evaluator % 2-13
Cost 3-11
Dearchlving 3-9
Degausser 2-13, 3-6
Disposition 3-8
File protect ring 3-8
Foreign 3-7
Label policy 5-11
Library 2-12
Maintenance • 3-8
Management 3-6
MOUNT command 4-8
Protection 4-8
Releasing from archive 3-9
Reports 3-9
Tape Management System (TMS) 3-7, 5-10
TAPESYS 5-10
Tektronix library 7-2
Telecommunications
Access 2-3
Assistance 2-8
Problems D-l
Service request B-3
Telephone numbers A-l
Terminal
Access 3-6
Characteristics 2-5
Problems 2-5
Text editors 5-1
3270 terminal emulation 8-10
Training
Classroom 2-9
On-line 2-12
Transferring files 1-1, J-l
Truncating commands 4-6
Index-6
-------
- u -
User nemos B-2
User profile B-2
User Support Services 2-7
Utilities 5-1
- V -
Volume security 4-7
Index-7
------- |