Documentation
"CMS WordPerfect," U01-0617, discusses the features and peculiarities of WordPerfect on CMS and is available through PRTDOC.
"Transferring WordPerfect Files Between Systems," U01-0623, available through PRTDOC, can assist users who use WordPerfect on more than one computer (CMS, VAX/VMS, Macintosh, IBM PC).
WordPerfect Corp.'s manual is available in Remotes 1, 2 and 8 and on reserve at Hodges Library.
Documentation
The following manuals are on reserve in Hodges Library:
SH35-0069,
Document Composition
Facility: SCRIPT/VS Text Programmer's Guide
SH35-0070,
Document
Composition Facility: SCRIPT/VS Language Reference
SCRIPT filename ([options] PROFILE(DSMPROF3)
where the filetype is assumed to be SCRIPT. The PROFILE option specifies that the system file which contains the starter set definition be used in the processing of the specified file.
Documentation
For a description of the starter set and the formatting results that SCRIPT/VS will produce when its tags are used, see the following IBM publications, which are on reserve in Hodges Library:
SH20-9186, Document Composition Facility: Generalized Markup Language: Starter Set User's Guide SH20-9187, Document Composition Facility: Generalized Markup Language: Starter Set Reference
1) Prepare the source file with the XEDIT text editor. The file may have any valid filename, but the filetype should be the name of the programming language in which the program is written.
2) Compile the source program. See the appropriate section on the language of interest for details. The compiler produces two files with the same filename as the source file but with different filetypes. One is an object program with a filetype of TEXT. The other is a listing file, with filetype LISTING, which contains the source program listing along with error messages, if any, and compilation statistics. Development of the source program should continue until recompilation produces no error messages.
3) Issue any FILEDEF commands needed to associate the file identifiers within the program to the physical CMS files. (NOTE: With the exception of the VMSHR1 disk pack, access to MVS disk data sets from CMS is not provided. See section 4.24.3 for information about VMSHR1.) For more help on the FILEDEF command, enter
HELP FILEDEF
4) Access the appropriate subroutine library(ies) by issuing the GETLIBS command with the appropriate options. The libraries of the following products running on CMS can be accessed with the GETLIBS command, in addition to user load libraries and/or text libraries:
For more information about the GETLIBS command, enter the CMS command HELP GETLIBS.C FORTXLAT OSL COBOL (OS/VS COBOL) IMSL NAG COBOL2 (VS COBOL II) INSPECT PASCAL (Pascal 8000) EISPACKD ISPC PASDEBUG EISPACKS LINPACK PLI ESSL MINPACKD VSPASCAL FORTVS2 MINPACKS SSORT (same as SYNCSORT) FORTDBUG SYNCSORT
5) Provided no errors exist, the LOAD and START commands are issued to load the object code into virtual storage and begin execution as follows:
LOAD filename (CLEAR [options]
START
It is recommended that CLEAR be included in the options, as shown in the example above, so that main memory is cleared before the program is loaded. More information on the LOAD and START commands can be obtained by entering the commands:
HELP LOAD and HELP START
As an alternative to the START command, the GENMOD command can be used to create a MODULE file which can subsequently be executed without first issuing the LOAD command. For more help on the GENMOD command, enter
HELP GENMOD
1. Compile your program using the vector option:
FORTVS2 filename (VECTOR
2. Invoke the vector simulator specifying a report:
VSIM CLEAR CLRSTAT STAT
where CLEAR and CLRSTAT clear the registers and reset the statistics, and STAT turns on the collection of vector instruction statistics.
3. Load and execute the compiled FORTRAN vectorized code:
GETLIBS FORTVS2 LOAD filename (CLEAR START
4. To access the vector statistics collected by the simulator, issue the command
VSIM PRTSTAT
which creates a disk file called VECTOR STAT A containing the statistics. Then use the CMS commands XEDIT, TYPE, or PRINT to display the file.
5. To end the Vector Facility Simulator function, issue the command
VSIM DROP An online help file may be viewed by entering HELP VSIM.
GLOBAL MACLIB DMSSP CMSLIB OSMACRO OSMACRO1
The libraries made available by this command contain all public macros in the VM system. To assemble the source program, enter the following command:
HASM filename (options
where, by default, the filetype is assumed to be ASSEMBLE. For a complete list of options, enter
HELP HASM
Documentation
SC26-4036,
Assembler H Version 2 Programming Guide
, located in
Remote 28 (Physics)
GC26-4037,
Assembler H Version 2 Language Reference
, located in Remotes 1, 2, 8, 17 and 28
CC filename
Then, to load and execute the program, enter the following CMS commands:
GETLIBS C LOAD filename (CLEAR STARTType HELP CC for a detailed description of the CC command and compiler options and examples of loading and executing C programs.
Documentation
The following manuals are located at Remotes 1, 2 and 8.
SC09-1264,
IBM C/370 User's Guide
SC09-1308,
Systems Application Architecture: Common Programming
Interface, C Reference Level 2
The following reference manuals are available at Remotes 1 and 8 and in Ayres Room 101.
SC26-4528,
INSPECT for C/370 and PL/I: Using INSPECT Under MVS
SC26-4529,
INSPECT for C/370 and PL/I: Using INSPECT Under CMS
COBOL2 filename (options
The filetype of the source program must be COBOL. For a list of available options and their defaults, enter
HELP COBOL2
All default options are the same as for the MVS version of this compiler. The execution-time subroutines required by the compiled COBOL program are accessed by issuing the GLOBAL command:
GETLIBS COBOL2
Documentation
The following manuals are located in Remote 8 and on reserve in Hodges Library.
SC26-4045, VS COBOL II Application Programming Guide GC26-4047, VS COBOL II Application Programming Language Reference
GLOBAL TXTLIB SORTLIB EASYT90
A file definition statement (FILEDEF) must be issued for the file SYSIN, the input file for the EASYTRIEVE program. SYSIN can be defined either as a disk file or the terminal. Any other input or output files to be used by the program must also be defined, except for the output file SYSPRINT, which defaults to the CMS file FILE SYSPRINT A1. The EASYT90 command is then issued to execute the program. The EASYTRIEVE Interactive Prompting Facility (IPF) is designed to help non-programming personnel generate, debug, and execute an EASYTRIEVE program. IPF can also be used as an educational tool for users learning EASYTRIEVE. The EZTIPF command is used to initiate EASYTRIEVE/IPF. For more information on this command, enter
HELP EZTIPF
Documentation
The following manual is located in Remote 8 and on reserve in Hodges Library.
EASYTRIEVE Reference Manual
Also available is a UTCC videotaped short course, "EASYTRIEVE," available in Audiovisual Services at the Hodges Library during regular library hours. Printed course materials to accompany this video course can be obtained at 200 Stokely Management Center.
FORTVS2 filename (options
If the filetype is not FORTRAN, then the filetype must be entered also. For a complete list of compiler options and other information, type HELP FORTVS2. It should be pointed out that VS FORTRAN Version 2, has the capability of making use of the Vector Facility on the IBM 3090 computer, which at UTCC runs under the MVS/ESA operating system only. On CMS, the execution of VS FORTRAN is limited to scalar mode. However, the compiler on CMS is capable of producing both scalar and vector object code. The Vector Facility Simulator (VSIM) software available on the IBM 3081 can be used under CMS to simulate the IBM 3090 Vector Facility. Thus, for purposes of program development, FORTRAN users can build and debug their source programs on CMS and, if the Vector Facility is needed, submit the program to the MVS/ESA operating system for execution using the RJE command. The VS FORTRAN compiler includes an inter-compilation analyzer (ICA) feature which can detect incompatibilities between the main program and the and functions. The messages identifying the discrepancies are written to the LISTING file. To use the ICA compiler option for a single source code file, enter
FORTVS2 filename (ICA
For multiple source code files, enter
FORTVS2 filename (ICA(UPDATE(anyname) FORTVS2 filename (ICA(USE(anyname)The intercompilation analysis file has the filename specified in the USE or UPDATE suboption "anyname"; the filetype is ICAFILE. For more information about intercompilation analysis, see chapter 14 of VS FORTRAN Version 2 Programming Guide , SC26-4222. VS FORTRAN has two modes of execution on CMS: link mode and load mode. If you want library routines included within your executable module, choose link mode. If you want library routines loaded during execution of the program, choose load mode. Load mode reduces the time required to create an executable module and reduces the auxiliary storage space required. The choice is made when the GETLIBS command is issued to make the appropriate library routines available as follows:
For load mode: GETLIBS FORTVS2For link mode: GETLIBS FORTVS2 (LINK
For more information about the GETLIBS command, enter HELP GETLIBS. Three predefined files are provided and recognized by CMS when referred to in FORTRAN input/output statements with the appropriate unit number. Unit 5 can be used to read data from the terminal, while unit 6 can be used to write data to the terminal. Unit 7 can be used to write data to the user's virtual card punch. These defaults can be changed and other unit numbers defined with the FILEDEF command.
Note : VS FORTRAN programs to be used with the Interactive Debugger must be compiled with the SDUMP compiler option, which is the default on CMS. On MVS, the UTCC cataloged procedure for the VS FORTRAN compiler specifies FORTOPT=NOSDUMP. CMS users who execute OS compiled load modules on VMSHR1 must recompile these programs using FORTOPT=SDUMP. To invoke the debugger: The following UTCC EXEC will allocate required libraries and files for loading and executing a compiled VS FORTRAN program and invoke the VS FORTRAN Interactive Debug.
FORTDBUG filename
where "filename" refers to the file "filename TEXT" produced by the VS FORTRAN compiler. Internally, the FORTDBUG EXEC issues the following commands:
GETLIBS FORTDBUG FILEDEF AFFON DUMMY FILEDEF AFFPRINT DISK filename AFFPRINT A LOAD filename (CLEAR START * DEBUG (options
The debug environment will then prompt you with FORTIAD to which you may issue debug commands. Online help information is provided for all debug commands and functions. By entering HELP to the FORTIAD prompt, you are presented with the first of a set of screens containing HELP information. The help facility that is available within the debug environment may also be consulted at the CMS level by entering the CMS command HELP AFF. Type HELP FORTDBUG for more information on using the FORTDBUG command. For information on VS FORTRAN and its use in the MVS batch environment, see section 13.6.
Documentation
The following manuals are on reserve in Hodges Library, as well as in the manual racks at the remotes listed in parentheses.
GC26-4219,
VS FORTRAN Version 2 General Information
SC26-4221,
VS FORTRAN Version 2 Language and Library Reference
(Remotes 1, 2, 8, 17 and 28)
SC26-4222,
VS FORTRAN Version 2 Programming Guide
(Remotes 1, 2, 8, 17 and 28)
SC26-4223,
VS FORTRAN Version 2 Interactive Debug Guide and Reference
(Remote 1)
Input requirements
Input source to the translator must be error-free in its
native dialect. Debugging statements should be removed
in advance, as they cannot be recognized by the translator
and will become comment statements.
The source code must be fixed format with a record
length of 80 or 132, unblocked, or VAX TAB format and
may be in uppercase and lowercase ASCII or EBCDIC.
The minimum virtual storage area required to execute the
translator program is two megabytes.
See the
IBM FORTRAN Translation Tool
Program Description/Operation Manual
, in the manual racks at
Remotes 1 and 8, for a list of
other translator limitations.
Execution on CMS
The commands to operate the translator on CMS are
contained in the FORTXLAT EXEC. To execute the
translator on any FORTRAN program, enter the
following command (where fn is the filename of the
input FORTRAN source file). The filetype must be
FORTRAN.
FORTXLAT fn
The translated output file will be named "fn NEWFORT". The output file "fn TRANPRNT" contains comments describing modifications to the original source code and messages denoting questionable or untranslatable statements. A sample batch FORTRAN source file (SAMPLES FORTRAN) containing CDC and DEC source statements is available on CMS for testing the translator. To run the sample program, type the following command.
FORTXLAT SAMPLES
Type HELP FORTXLAT for more information on running the FORTRAN Translation Tool EXEC.
Executing translated programs
Translated programs can normally be executed after
compilation and linkage with the VS FORTRAN compiler
and subroutine libraries. If the translated program contains
calls to the translator-supplied execution-time routines,
they must be made available to the translated FORTRAN
program (see page 211 of the manual).
On CMS, these routines are in the FORTXLAT
TXTLIB library and may be made available by entering
the following command before loading and running
the program.
GETLIBS FORTVS2 FORTXLAT
VSPASCAL filename (options
where the filetype is assumed to be PASCAL. Accessing the VS Pascal subroutine library on CMS and running the program are accomplished by issuing the PASCRUN command:
PASCRUN filename options / Type HELP VSPASCAL on CMS for a description of the VSPASCAL compiler command syntax along with definitions of compiler options and examples of executing VS Pascal programs. For information about PASCRUN, type HELP PASCRUN.
Documentation
The following manuals are available at Remotes 1 and 8 and in 101 Ayres Hall.
SC26-4319,
VS Pascal Application Programming Guide
SC26-4320,
VS Pascal Language Reference
GETLIBS PLI To compile the PL/I source program, use the PLIOPT command which has the following syntax:
PLIOPT filename (options
where the filetype is assumed to be PLIOPT. A help file is available by typing
HELP PLIOPT
Documentation
The following manuals are on reserve in Hodges Library.
SC26-4307,
OS PL/I Version 2 Programming Guide
SC26-4308,
OS PL/I Version 2 Programming: Language Reference
The following reference manuals are available at Remotes 1 and 8 and in Ayres Room 101.
SC26-4528,
INSPECT for C/370 and PL/I: Using INSPECT Under MVS
SC26-4529,
INSPECT for C/370 and PL/I: Using INSPECT Under CMS
Documentation
SyncSort CMS Programmer's Guide
, on reserve in Hodges Library
SyncSort Programmer's Guide
, at Remote 8
BMDP filename (PROG BMDPxx options ...
where the routine "BMDPxx" named in the PROG option must be specified using either the full name of the routine (e.g., BMDP1D) or an abbreviated form consisting of the last two or three letters of the name (e.g., P1D or 1D). For additional information on the format of the BMDP command and other options which may be used, enter
HELP BMDP
or see the BMDP Statistical Software Manual , Volumes 1 and 2, available at the UTK Book and Supply Store and in the manual racks at Remotes 8 and 17.
Documentation
An online help file is available on CMS by entering HELP EISPACK.
"EISPACK Description," U01-0413, is available through PRTDOC.
Matrix Eigensystem Routines - EISPACK Guide , by B. T. Smith and others, Springer-Verlag, 175 Fifth Avenue, New York, NY 10010. This guide is located in Remote 2 (108 Estabrook Hall).
EISPACK - A Package for Solving Matrix Eigenvalue Problems , by J. J. Dongarra. This reference describes the use of EISPACK and changes made to the package for the current release, and is available from the UTCC receptionist, 200 SMC.
How to access ESSL subroutines
To access the ESSL subroutines and the appropriate VS FORTRAN libraries, enter one of the following GETLIBS commands.
For load mode execution: GETLIBS FORTVS2 ESSL
For link mode execution: GETLIBS FORTVS2 ESSL (LINK
To use the vector version: GETLIBS FORTVS2 ESSL (VECTOR
Intercompilation Analysis (ICA) file ESSL provides an ICA file to allow compile-time diagnosis of inconsistencies or errors in call statements to ESSL routines. The ESSL ICA file named ESVICA must be part of the ICA option at compilation, as follows:
FORTVS2 filename (ICA(USE(ESVICA)) [other options]
Documentation
SC23-0184,
Engineering and Scientific Subroutine Library Guide and Reference
,
available at Remotes 1, 2, 8 and 28 and on reserve at Hodges Library
SC23-0410,
Engineering and Scientific Subroutine Library Reference Summary
,
a pocket-size manual available from IBM
that is convenient for
looking up the calling arguments of subroutines
How to use IMSL subprograms on CMS The IMSL library is designed and supported exclusively for the FORTRAN 77 compilers, such as the VS FORTRAN compilers on CMS and MVS. The IMSL libraries (IMSLLIB1 and IMSLLIB2), as well as the appropriate VS FORTRAN text libraries, are made available by entering the CMS command GETLIBS, as follows:
For load mode execution: GETLIBS FORTVS2 IMSL
For link mode execution: GETLIBS FORTVS2 IMSL (LINK To use the IMSL subprograms, write a FORTRAN 77 program to call the desired subprogram(s), using the calling sequence(s) given in the library documentation listed below. Compile the program using the VS FORTRAN compiler. Link and load your program with the IMSL library. Execute the program and (if desired) create a permanent executable program. For more information about using VS FORTRAN on CMS, see section 5.2.6; for general information about using programming languages on CMS, see section 5.2. To view the online help file for the IMSL Library, type HELP IMSL.
The IMSL Interactive Documentation Facility (IDF) The IMSL Interactive Documentation Facility is an online help system designed by IMSL to help users identify the routines they need and to assist them in using those routines. It provides access to most of the information in the IMSL user's manuals. The IMSL IDF can help you identify the best routine for your program by providing information via associated keywords, a series of questions about your problem, or the GAMS classification. The following information is available for each routine:
` purpose of the routine ` keywords associated ` calling sequences ` description of arguments ` remarks regarding usage` GAMS classification ` revision date ` location in user's manual ` example program
Both a menu interface and command interface are available. The first screen of the menu contains the following options:
` search for routines ` general information` customize the user interface ` transfer to the command interface
The command interface provides additional capabilities that are not available in the menu interface. From the command interface you can create a history file, review the results of previous searches, and search for routines by keyword. To access the IMSL IDF enter the command:
IMSLIDF
To exit IMSLIDF, enter QUIT. For more information about the IDF choose "General Information" from the first menu or type HELP IMSLIDF.
IMSL Documentation
The following manuals are located at Remotes 1, 2 and 8 and are on reserve in Hodges Library:
MATH/LIBRARY User's Manual the general applied mathematics subprograms STAT/LIBRARY User's Manual Volumes 1-3, documents the statistical subprograms SFUN/LIBRARY User's Manual the special functions
The manuals may be ordered from IMSL, Sales Division, P.O. Box 4605, Texas 77210-4605.
Documentation
U01-0531, "LINPACK," is available through PRTDOC.
The LINPACK User's Guide by J. J. Dongarra and others, is available at Remotes 2 and 8 and on reserve in Hodges Library. This manual may also be ordered from the Society for Industrial and Applied Mathematics (SIAM), 33 South 17th Street, Philadelphia, PA 19103.
Documentation
The following manual is on reserve at Hodges Library:
SPSS LISREL 7 and PRELIS User's Guide and Reference
Documentation
Online help is available by entering the CMS command HELP MINPACK.
"MINPACK," U01-0605, is available through PRTDOC.
The following manuals are available at Remotes 1, 2 and 8 and on reserve in the Hodges Library.
User Guide for MINPACK-1
by Jorge J. Moore and others
Documentation for MINPACK--Single Precision Version
by Burton S. Garbow
and others
Documentation
An online help file may be accessed by entering HELP MPSX.
The following manuals have been placed at the locations listed in parentheses; "Reserve" means on reserve at Hodges Library. Except for Interface to OSL , the manual titles begin with ;.us IBM Mathematical Programming System Extended (MPSX/370)
SH19-6552,
User's Guide
(Remote 8)
SH19-6553,
Program Reference Manual
(Remote 8)
SH19-6554,
Messages and Codes
(Remote 8)
SH19-6555,
Operations Guide
(Remote 8)
SH19-6586,
Getting Started
(Remote 8)
SH19-6723,
Interface to Optimization Subroutine Library: Guide and Reference
(Reserve)
Important note: The IBM implementation of the NAG Library is a double precision version; variables described as real in the NAG Library manuals must be declared as REAL*8.
Using the NAG Library on CMS The NAG Library can be accessed through calls within a VS FORTRAN program. To access the NAG Library, enter the GETLIBS command as follows before linking the VS FORTRAN program:
For load mode: GETLIBS FORTVS2 NAG
For link mode: GETLIBS FORTVS2 NAG (LINK
Documentation An interactive online help program is available on CMS by typing NAGHELP. The most important parts of the specifications of all NAG FORTRAN routines are available in this online help facility. The NAG FORTRAN Introductory Guide , which contains basic information on the NAG routines, is located in Remotes 1, 2 and 8. The complete NAG Library manual set is in the Reserve Section of the Hodges Library and can be checked out for three days by anyone with library privileges. The IBM User's Note contains IBM-specific information and is, therefore, essential reading. The User's Note is available for reference online on CMS by typing HELP NAGSUN for the scalar version or HELP NAGVUN for the vector version. The User's Note can also be found at the beginning of the ;.us NAG FORTRAN Introductory Guide and in Volume 1 of the NAG Library manual set.
How to use OSL subroutines on CMS To access OSL enter the CMS command GETLIBS, specifying the language(s) of your program along with OSL, before linking your program. For example, if your program is written in FORTRAN, enter one of the commands below.
For load mode execution: GETLIBS FORTVS2 OSL For link mode execution: GETLIBS FORTVS2 OSL (LINK
Enter the CMS command HELP GETLIBS for more information on the GETLIBS command.
Documentation
Online help is available by entering the CMS command HELP OSL.
The following manual is on reserve at Hodges Library:
SC23-0519, Optimization Subroutine Library: Guide and Reference
SAS filename
If your data is in a CMS file separate from the program, the following SAS statement is required within the program:
INFILE 'filename filetype A' MISSOVER;
To run in CMS batch mode, use the following command:
VMBATCH SUBMIT () SAS filename
For more information about VMBATCH on CMS, see section 4.22. Several related SAS programs are available in addition to the basic SAS program. A list of those at UTCC is given below.
SAS/AF Provides a full-screen, interactive applications facility for creating a user-friendly front end to business or information-processing applications SAS/ACCESS Provides an interface to the SQL/DS database SAS/ASSIST Provides a menu system that enables the use of SAS without knowing its programming language SAS/CBT Provides computer-based training for SAS SAS/ETS Provides expanded tools for econometrics and time series analysis SAS/FSP Provides interactive, menu-driven facilities for data entry, editing, retrieval of SAS files, mail-merge, and letter writing SAS/GRAPH Provides presentation graphics. More about SAS/GRAPH in section 5.6.2. SAS/IML Provides an interactive matrix language SAS/OR Provides decision support tools for operations research and project management; available on the MVS system
Help There are extensive help files within SAS. Type HELP on the command line within interactive SAS to get into the help environment. Short courses about SAS are offered by UTCC each academic term. See section 1.4.2.3 for information about obtaining the current short course schedule. Several videotapes about SAS are available in the Audiovisual Department of Hodges Library. Printed materials to accompany some of the videotapes are available from the UTCC receptionist at 200 Stokely Management Center (phone 974-6831). A SAS computer-based training program is available on CMS. This online tutorial is aimed at beginners but is also useful for other SAS users who want to brush up on their skills. Each section presents a lesson on some aspect of how to use SAS. "SAS Computer Based Training," U01-0596, available through the PRTDOC facility, contains instructions for getting started.
Documentation
The following manuals have been placed at the locations listed in parentheses; "Reserve" means on reserve at Hodges Library. In addition, the Master Index to SAS System Documentation is located in Remotes 2, 8 and 17, and Vet Med.
SAS/ACCESS Interface to SQL-DS: Usage and Reference
(Remote 8)
SAS/AF Software: Usage and Reference
(Reserve)
SAS Applications Guide
(Reserve)
SAS Companion for the CMS Environment
(Reserve, Remotes 2, 8 and 17, Human Ecology, Vet Med)
SAS Companion for the MVS Environment
(Remotes 2, 8 and 17,
Human Ecology, Vet Med)
SAS Data Library Series: D-101 World Map Data Sets
(Reserve)
SAS Data Library Series: D-102 1970 SMSA Census Tracts
(Reserve)
SAS Data Library Series: D-103 Zip Code/County Conversion Data Set
(Reserve)
SAS Data Library Series: D-104 Map Data Sets, European and Pacific Countries
(Reserve)
SAS/ETS User's Guide
(Econometrics and Time Series) (Reserve, Remote 8)
SAS for Linear Models
(Reserve)
SAS/FSP Software: Usage and Reference
(Reserve)
SAS/GRAPH Software: Introduction
(Reserve)
SAS/GRAPH Software: Reference
, Volumes 1 and 2
(Reserve, Remote 1 Graphics Lab, Remotes 8 and 17)
SAS Guide to Macro Processing
(Reserve)
SAS Guide to Problem Solving and Error Messages
(Reserve)
SAS Guide to the SQL Procedure: Usage and Reference
(Reserve,
Remote 8)
SAS/IML Software: Usage and Reference
(Remote 8)
SAS/IML User's Guide
(Reserve)
SAS Language and Procedures: Usage
(Reserve)
SAS Language: Reference
(Reserve,
Remotes 2, 8 and 17, Human Ecology, Vet Med)
SAS/OR User's Guide
(Reserve, Remote 8)
SAS Procedures Guide
(Reserve, Remotes 2,
8 and 17, Human Ecology, Vet Med)
SAS Screen Control Language: Reference
(Reserve)
SAS SHARE User's Guide
(Reserve)
SAS/STAT User's Guide, Volumes 1 and 2
(Reserve, Remotes 2,
8 and 17, Human Ecology, Vet Med)
SAS System for Forecasting Time Series
(Reserve)
SAS System for Regression
(Reserve)
SPSS filename filetype (options
The default filetype is SPSS. Default options are DISK (to write the display file to disk with a filetype of LISTING) and TERM (to write only error messages, warnings, and notes to the terminal). To see other options, type HELP SPSS.
Documentation
U01-0548, "Introduction to SPSS," is available through PRTDOC.
The following manuals are on reserve in Hodges Library:
SPSS Advanced Statistics User's Guide
SPSS Base System User's Guide
SPSS Reference Guide
(also at Remotes 8 and 17, Human Ecology)
Documentation
The following manuals are on reserve in Hodges Library:
Getting Started with ANSYS ANSYS User's Manual, Volumes I and II ANSYS Stress Analysis Primer ANSYS Thermal Analysis Primer General Index to ANSYS Documentation
DSL/VS highlights
` DSL/VS provides numerous function blocks, procedures, and macros that allow you to represent commonly encountered system elements with single code statements.
` Nine integration methods are provided, including a self-starting fifth-order Runge-Kutta routine used by default and two methods for stiff systems. In addition to the regular (scalar) integrator, DSL/VS provides array (vector) integrators, saturating integrators, and associated transfer functions.
` Since dynamic systems are often modeled and studied in the frequency domain, DSL/VS contains special features that facilitate frequency response analysis.
` Unconstrained optimization may be performed in the DSL/VS environment to help automate the process of finding the best answer to a given problem in the minimum time.
` Graphic output is obtained with a post processor. Video monitors and may be used to produce line and point plots of many types.
Executing DSL/VS
DSL/VS may be executed interactively on CMS or in batch using the VMBATCH system (see section 4.22). Before using DSL/VS, the DSLINIT command must be issued. DSLINIT links and accesses the DSL/VS minidisk, verifies the availability of the VS FORTRAN subset library, and resets the number of "loader tables" required by the graphics post-processor. Four steps are required for complete execution of a DSL/VS program. These steps and functions are shown in order below.
Step Function DSLT file-spec Translation DSLC Compilation DSLG Load and simulation GRAFAEL Graphics post-processing File-spec is the file name, file type, and file mode of the DSL problem file. The file mode defaults to "A" if omitted. These commands may be executed separately, or the DSL command will execute the first three steps in the order listed. The fourth command may be executed as an option to the DSL command with
DSL file-spec (Grafael
Type HELP DSL for an expanded summary of the DSL command. Information for a specific command may be obtained by entering a question mark after the command. Example: DSLT ?
DSL creates a number of files on your minidisk. The command DSLERASE will erase all DSL files except those associated with the graphics post-processor. The command DSLERASE ALL will erase all DSL files except for the original problem input. An alternate, easier method of running DSL is to use the EZDSL command. The format for this command is:
EZDSL fn ft fm ( [graph]
If no filetype and filemode are specified, they will default to DSL and A, respectively. The ("graph" option will execute the graphics post processor, GRAFAEL. No output to the screen except for graphics will be generated. All output will be found in a file named "fn LISTING." If the graph option is not specified, two files, "fn DSLPLOT" and "fn DSLPLTC," will be saved for later use by EZGRAF. Using the graph option may also create a "fn TABLE" file and/or a "fn GRAPH" file. The command
EZGRAF fn ( [erase]
will run the graphics post processor, GRAFAEL using the two files created from EZDSL. Including the erase option will delete the "fn DSLPLOT" and "fn DSLPLTC" files after running GRAFAEL. Enter HELP EZDSL or HELP EZGRAF for further information on these commands.
Documentation
The following manuals are available at Remote 1 and on reserve at Hodges Library.
SH20-6287,
Dynamic Simulation Language/VS Program Description/Operations Manual
SH20-6288,
Dynamic Simulation Language/VS Language Reference Manual
GDDM/Base GDDM-PGF GDDM-GKS
All of these subroutine libraries may be called from the FORTRAN, PL/I, COBOL, and System/370 Assembler languages. GDDM/Base is a library of general-purpose graphics subroutines that can produce graphics on IBM devices. GDDM/Base supports IBM 3x79G terminals, 328x and 38xx printers, and 737x plotters. Note: To produce graphics on these devices, they must have the proper hardware features and microcode. GDDM-PFG (Presentation Graphics Feature) builds upon GDDM/Base and adds a library of higher-level graphics subroutines for producing business-type charts. GDDM-PGF also includes the Interactive Chart Utility (ICU). The ICU lets you create business charts without programming. GDDM-GKS (Graphics Kernel System) also builds upon GDDM/Base and implements the Graphics Kernel System.
DEVICE=VT240 Digital Equipment Corp. VT240 terminal DEVICE=VT340 Digital Equipment Corp. VT340 terminal DEVICE=TEK4010 Tektronix 4010 graphics terminal DEVICE=TEK4014 Tektronix 4014 graphics terminal DEVICE=TEK4105 Tektronix 4105 color graphics terminal DEVICE=TEK4207 Tektronix 4207 color graphics terminal DEVICE=PS300 PostScript for output to Imagen printer
SAS/GRAPH output to the Imagen printer
SAS/GRAPH information and presentation graphics can be sent to the Imagen printer from CMS using a PostScript driver. Although SAS commands are not case sensitive, in the following example capital letters indicate a portion of the command string that must be entered exactly as shown; lower case letters indicate a value to be supplied by the user. Any SAS grahpics procedure can be substituted for PROC GTESTIT. The filename entered at FILENAME and GSFNAME must be the same. Run the following SAS program on CMS to produce SAS/GRAPH output on the Imagen printer.
FILENAME filename 'POSTSCR LISTPS'; GOPTIONS DEV=PS300 NODISPLAY NOPROMPT HANDSHAKE=XONXOFF GSFNAME=filename GSFMODE=REPLACE GSFLEN=80 GPROTOCOL=SASGPASC; PROC GTESTIT; [or any other graphics procedure] X IMPRINT POSTSCR LISTPS;
The filetype of LISTPS tells the Imagen printer that the output file contains PostScript commands. The output file can also be printed on the Imagen printer with the CMS command:
IMPRINT POSTSCR LISTPS
Documentation
For online help, enter HELP UTCC SAS, or within SAS enter HELP.
A large number of map data sets are available for use with PROC GMAP. They are described in "SAS/GRAPH Map Data Sets," U01-0540, available through PRTDOC.
The following manuals have been placed at the locations listed in parentheses; "Reserve" means on reserve at Hodges Library.
SAS/GRAPH Software: Introduction
(Reserve)
SAS/GRAPH Software: Reference
, Volumes 1 and 2
(Reserve, Remote 1 Graphics Lab, Remotes 8 and 17)
Major ESE features
` Incremental compilation of rules, parameters, and control blocks as
they are entered into the knowledge base, reducing the amount of space
required for their storage and improving processing performance
` Extensive certainty-processing capabilities, including facilities for
processing fuzzy logic
` Both forward and backward chaining inferencing methods, with
high-level user control
` Focus Control Blocks (FCBs) that provide a means of dividing complex
problems into small subproblems to make maintenance and control easier
` An external data interface and user-written routines to access
existing databases; these user routines can also execute and transfer
data to other applications in the CMS or TSO environments.
` An explanation facility to inquire into why a certain piece of
information is requested or how a certain parameter has come to have its
current value
` The facility to build customized displays different from the default
display screens provided with the product
` A built-in editor that provides semantic and syntactic checking while
knowledge bases are being interactively constructed
` An extensive set of debugging tools
` Interfaces to external procedures written in the COBOL, PL/I, VS Pascal,
System/370 Assembler, VS FORTRAN, and REXX programming languages
` Functions that can access SQL/DS databases
Accessing ESE
To run IBM ESE, you may require more disk space than you currently have. To invoke the Expert System Development Environment, log on to CMS and enter the commands:
ESE
For help in using the ESE package, contact your UTCC consultant.
Documentation
An online help file may be accessed by entering the CMS command HELP ESE. The manuals listed below are available from IBM. Those marked with an asterisk are on reserve in Hodges Library.
*SC38-7004, ESE Reference Manual
SC38-7005, Expert System Consultation Environment User's Guide
*SC38-7006, Expert System Development Environment User's Guide
SC38-7007, ESE Reference Card
SQL
Online help is available. Enter the CMS command HELP SQL or, after accessing SQL, enter the command HELP CONTENTS.
Documentation
The following documents are available through PRTDOC:
U01-0604, "Structured Query Language"
U01-0608, "SQL Database Services Utility"
U01-0609, "Advanced Techniques in SQL"
The following SQL/DS manuals are available from IBM; those marked with an asterisk can be found in Remote 8.
SH09-8017,
Database Planning and Administration
*SH09-8019,
Application Programming for VM/SP and VM/XA System Product
*SH09-8047,
Interactive SQL User's Guide for VM/SP and VM/XA System Product
SH09-8048,
Terminal User's Reference
SH09-8052,
Messages and Codes
Documentation
The following manuals have been placed at the locations listed in parentheses; "Reserve" means on reserve in Hodges Library.
SAS/AF Software: Usage and Reference
(Reserve)
SAS/FSP Software: Usage and Reference
(Reserve)
SAS/ACCESS Interface to SQL/DS: Usage and Reference
(Remote 8)
