CURRENT AND FUTURE ENHANCEMENTS OF VERSION 6 OF THE SAS® SYSTEM UNDER CMS

HELD BY: KEITH COLLINS/SAS INSTITUTE

AUTHOR: JOHN W. DE BOSKEY/SAS INSITUTE INC., CARY, NC

What To Look For In Version 6 Current and Future

Enhancements of Version 6

of the SAS® System

Under CMS

fJIllnstitute Inc.

Enhancement Areas

• Language

• Sequential

• Performance

• In The Future

fJIllnstitute Inc.

220

• Fresh New Look

• Increased Interactivity

• Pop - Up Windows

• Added Language Syntax

• Increased Procedural Functionality

fJIllnstitute Inc.

Language

• Libname & Filename

• Transparent Access to datasets

• CMS I X Command Resolution

• SORT Procedure Enhancements

• Graphics Window Support

fJl£ Institute Inc.

I I

t. p

~ f: ~ ., • R ~

" ~:

r ~. I:

" " it.' ~j ~' (, j'

, 'j,

~ ~

~ t,

f ~

~ t

~ ii li'

~

~ Ii ~. li ~ "' ~, ;;i'

f i R ~

~ I i '\

t,

\. "

I

Sequential

• Standard Label Tapes

• Multi - Volume Tapes

• Deferred Mounting

• Reference by Dataset Name

Performance

• Full VM/XA Support

• Vector Processor Support

• User Created Formats & Informats

in Catalogs

• XA & non - XA Segments with new easy

• Associated pptions to use support routines

JJIL Institute Inc. JJIL Institute Inc.

In The Future Language Constructs To Enhance I/O & Portability

• Future Compatibility Projects • LlBNAME statement provides access to

• Other Project Ideas

JJIL Institute Inc.

The LIBNAME 'Statement /

• Provides for more portable SAS

applications

• Common Syntax for redirecting

access to specific, SAS libraries

• Common syntax between systems

• Allows for creation/access of

sequential format ,SAS libraries

SAS System libraries

• FILENAME statement provides access

to CMS external files

JJIL Institute Inc.

LIBNAME Syntax

LlBNAME ref <engine> < pname > <opts>

• LlBNAME ref 'x'; create or read

SAS library from specified minidisk

• LlBNAME ref 'ftx'; library is

aliased to use a CMS filetype

other than the default

221

Dllinstitute Inc.

Libname Syntax II

• LlBNAME ref engine 'fn ft fm';

for using engines that access flat

files or other vendor products

• Some other engines include

XPORT, BMDP®, & OSIRIS®

Dllinstitute Inc.

LIBNAME Performance Gains

• Specifying the fm avoids searching

all accessed minidisks

• Specifying an engine name avoids

library format determination

• LlBNAME librefs are searched

• Physical name of TAPn causes the before CMS FILEDEF ddnarnes

SAS System to read/write a

a sequential format library on • In all cases, more information

the specified device means better system performance

Dllinstitute Inc. Dllinstitute Inc.

The FILENAME Statement FILENAME Syntax

• Does for external files what the

LlSNAME statement does for

SAS data libraries

• Redirect input & output of external

files from within the SAS System

Dllinstitute Inc.

FILENAME Devicetype

• Fileref can be associated with

FILENAME ref

< devicetype > < p - name> < opts>

• ref(member) to include a member

from fl eMS IXTLlS, MACLIS

• Or filename(member) to include a

member from filename MACLIS

Dllinstitute Inc.

FILENAME Physicalname

numerous I/O devices via the • Specify filename, filetype, and ~

devicetype parameter filemode of extemalfile

• DISK (default) • Specify TAPn as the physicalname

• TERMINAL to indicate the external file

• PUNCH is on tape

• PRINTER

Dllinstitute Inc. Dlllnstitute Inc.

222

FILENAME Performance

• Specifying the filemode avoids

searching all accessed minidisks

• FILENAME filerefs are searched

before CMS FILEDEF ddnaliles

• The FILENAME statement causes

native CMS disk I/O to be used

rather than as simulation

As Commands in OMS

• Both UBNAME & FILENAME work

as a command

• Cause a pop - up window to

appear with current· definitions

• Non - interactive users can specify

LIST, SHOW, QUERY, or CLEAR

on the statement form to further

manipulate the assignments

IJIL Institute Inc. IJIL Institute Inc.

Transparent Access What Transparent Access Means

• What is Transparent Access? • Access any native SAS data

• Is an ability to recognize a library

particular native library format

• Do not need to know the Release

• Allows access to the data sets of SASthat created the library

; within that library

." • Eases the transition from one ~~"

• Requires !"Io change to access

Version 5 data sets from Version 6

IJIL Institute Inc.

Release of· SAS to the next

JJI£ Institute Inc.

Transparent Access Supports CMS /XCommand Resolution

• eMS SUBCOM Environment

• R/W Version 5 data libraries introduc~d crills Release 4

• R/W Version 5 Sequential • Single interface for CMS

• RIO Version 5 as DASD command resolution

• RIO 82.3 data libraries • Hand cOding of CMS search rules

• RIO 79.6 data libraries is no longer required

• Full CMS' search rules always

in effect

IJIL Institute Inc. JJlf Institute Inc.

223

CMS IX CMS/X Command Abend Handler Command Functionality

• ABEND handler wrapped around

CMS / X command interface

• Allows SAS to recover from errors

in external programs

.DIilnstitute Inc.

Sort Procedure Enhancements

• EQUALS processing

• NODUPKEY procedure option

• TRANTAB = procedure. option

• ABEND handling

• New functionality throughout

• CMS / X Command

• CMS / X Statement

• CMS / X Function

.DIilnstitute Inc.

EQUALS Processing

• Allows equivalent BY variable

observations to have their input

order preserved

• If provided by Sort utilities

• EQUALS/NOEQUALS option is

passed on SORT control card

• Sc;>rt utility must honor the

'EQUALS' parameter

• NOSORTEQOP

.DIilnstitute Inc. .DIilnstitute Inc.

NODUPKEYProcedure Option 1RANTAB Procedure Option

• Causes omission of records with • TRANTAB= <table-name>

duplicate key fields

• Allows user created translate

• SORTSUMF System option must tables to be used by the

be turned on SORT procedure

• Sort utility must honor the • Documented in SAS Technical

'FIELDS = ' parameter on the ReportP-197

'SUM' control card

.DIilnstitute Inc. JJlf Institute Inc .

224

:}

ABEND, Handling

• External SORT interface wrapped

with ABEND handler

• Allows the SAS System to recover

from external sort program errors

JJl£ Institute Inc.

Supported Windows

• Displaying SAS log & listing output

• Displaying graphics

__ Displaying dataset· information

• LlBNAME & FILENAME information

• Information from SAS global statements

such as TITLE & FOOTNOTE

JJl£ Institute Inc.

Additional Windowing Support

\ l.

\. \'

• Can open multiple windows and

display them concurrently

• TILE/UNTILE tiled windows

• CASCADE/UNCASCADE cascaded windows

• RESIZE for default configuration

• ICON to inconiz~ windows (active)

• pull- down menus

JJl£ Institute Inc.

225

Windowing ,Environment

• Version 5 provided a first pass

• Version 6 provides extensive support

JJl£ Institute Inc.

Graphics Window

• OPTIONS GWINDOW; (default)

• Graphics to a graphics window

• Can be moved & resized

• Multiple graph windows with

IBM3179 or compatible terminal

• Specify NOGWINDOW for

Version 5 compa.tibility .'

JJl£ Institute Inc.

Mouse Support With Windows

• IBM 3179 or 3472 terminal

• Attach a mouse for increased

flexibility from DMS

• Pull- down menus

• Requestor windows

• Window management

JJl£ Institute Inc.

Sequential· ,Enhancements

• Standard Label, Multivolume tapes

• Deferred Mounting .

• Full sequential processing support

• Additional new options on

LlBNAME & FILENAME statements

for tape support

/JI£ Institute Inc.

Deferred Mounting

• If supported by external tape

management system

• SAS support is through the

SYSPARMoperand on the

LlBNAME & FILENAME statements

• Reference tapes by OS - style

name instead of volume serial

JJIL Institute Inc.

New Tape Support Options

• LlBNAME options keyword=value

BLKSIZE DENSITY LABEL

TRACK VOLID LEAVE SYSPARM

• FILENAME options keyword = value

BLKSIZE DENSITY LABEL

TRACK VOLID LEAVE SYSPARM

JJIL Institute Inc.

226

Standard Label/Multivolume

• Uses BSAM access method

under CMS

• If external tape management

system uses· DMSTVI interface

then multifile & multivolume

facilities can be used

/A£ Institute Inc.

Full Sequential Support

• Any operation that can be done

with disk files can be done

with tape files

• Full support through new options

.. on LlBNAME & FILENAME

statements

JJIL Institute Inc.

Version 6 XA EXplOitation

• Completely XA compatible

• Capable Of using the greater

address space available. on·

an XA system.

• Loads & runs above the 16M line

JJIL Institute Inc.

, ,.

XA Exploitation Continued·

_ Practical to install larger

portions of heavily used images

into segments

_ Optional use ALL606 LUST

load list control file

! - Version 6 is composed of entirely

;. re -' entrant code

JJ/£ Institute Inc.

IBM Vector Facilty Support

;3'

)-,;. ~. "

- Optional Feature on 3090 series

processors

- Designed for high speed

manipulation of fixed & floating

point numbers···

- Available, by default, at logon

& 'l: _ Query Virtual Vector

JJ/£ Institute Inc.

. .

ProceduresWifhVF Support

_ ACECLUS

_ CANCORR

_ FACTOR

_ GLM

_ IML

_ LOGIST

_ PRINCOMP

_ OPTEX

JJ/£ InstItute Inc.

227

Vector Facility Support

.. CMS Support

_ SAS Support

_ Procedure Support

JJ/£ Institute Inc.

SASVector Facility Support

_ Syntax is VECTOR/NOVECTOR

_ Default is VECTOR

_ Option is valid as part of

the configuration file or

on the SAS command line

JJ/£ Institute Inc.

Version 6 Formats & Jnformats

- FORMAT procedure puts all created

formats & informats ina catalog

- Catalog is determined by the

UBRARY=option of the

FORMAT procedure

JJ/£ Institute Inc.

Format/lnformat Maintenance

• Can manage these catalogs with

normal SAS utilities

• CATALOG procedure

• CATALOG command(window)

Formatjlnformat Compatibility

• TEXT/TXTLiB files still supported

• User is responsible for file

maintenance

• V5TOV6 procedure to convert to

new Version 6 formats/informats

• Increased performance

.fJI£ Institute Inc. .fJI£ Institute Inc.

Version 6 Segment Support Segment Support Changes

• Upwardly compatible with • SASCSEG1 updated and renamed

Version 5 segment support to SASCSEG6

• fn LOADLIST files updated &

• Same funtionality renamed to fn LLiST

• CMSSEGS SAS program replaced

• Series indicator shifted in by CMSSEGS EXEC

segment names insures peaceful • CMSSEGS control file

co - existance of Version 5 & • Automatic generation of DMKSNT

Version 6 segments or EXEC for bimodal systems

.fJI£ Institute Inc. DIllnstitute Inc.

Segment Support Changes Future Compatibility Projects

• Refined support for load/overlay • VIOBUF

levels

SUPERVISOR PROC1 PROC2 • SAS/SHARE Support

• Levels loaded noncontiguousty

• LOADADDR card in CMSSEGS • Access to Version 6

control file SAS OS DASD data libraries

• LOADADDR supervisor proc1 proc2 • Access to Version 5 & Version 6

SAS VSE data libraries

.fJI£ Institute Inc. /Af Institute Inc.

228

., ~

{

~r; ~ l. :~ c

:~ y. .(

," .~~

.. ,

.)~

" ~(

.["

J::

~}~

"t , ~\;'

1~ -1;

~ ~ t:

"1:

:f ; ~ T 1: :J. 1.;. ~l' 'f'

,-" ,,~

~. if;

i -:;: .)

{; l 5.: ."

i ... ~ 1;.. tf

I \~ \ \:

I '.

~

~

Compatibility Projects II

• Dataset. password protection

• VSAM support in external I/O

• Procedures

TAPECOPV

TAPELABEL

TAPECOMP

JJlllnstitute Inc.

Future Project Ideas II

• REXX subcom environment

• CMS XEDIT window interface

• CMS FILELIST window

• RIO message files in segments

• RIO SAS datasets in segments

JJlllnstitute Inc.

ABSTRACT

Version '6 of the SAS System has a fresh, new look. Increased interactivity and a "point-and-click" environment will help novice users as they create their first SAS applications.' Expert programmers can also realize an increase in pr.oductiv.ity due to the addition of pop-up windows,.' added language syntax, and incr;ased procedural functionality. In addition to the features currently included ~nRelease. 6.06 of the SAS System, there are many interesting projects SCheduled for future releases of the SAS System under CMS. This paper discusses some of the current enhancements and future projects scheduled within Version 6 of the SAS system under CMS.

Future Pr9ject Ideas'

• Multiple SAS library concatenation

• Engine to exploit the Release 6

CMS Shared File System

• TCP/Ip, APPC Engines

• Wildcarding to process multiple

external files

• XWINDOWS Support

• Increased host windowing support

229

JJlllnstitute Inc.

Thank You for Attending!

Questions?

/flllnstitute Inc.

INTRODUCTION

This paper discusses the enhancements that have been made to the SAS System in the language,_ sequential, and performance areas. In the language arena, enhancements to the LIBNAME " FILENAME statements, transparent access to different type data seti via data library engines, eMS " X command' resolution, trIe SORT procedure, and graphic' windows are discussed. Sequential enhan :ements include standard label tapes, multi-volume support, and other associated options. With respect to performance, the. SASSystem now has full VM/XA" support, vector processor suppor t, user~createdformats and informats in catalogs, and new, easier to maintain 'IM/XA'"" non-VM/XA '"segment support. A list ,- E future compatibiiity enhancements and project ideas is also provided for reference.

RELEASE 6.06 LANGUAGE ENHANCEMENTS

LIBNAME & FILENAME Statements

Version 6 of the SAS System provides two new language constructs to enhance I/O performance and portability; the LIBNAME and, FILENAME statements. The LIBNAMEstatement is used to access specific SAS libraries. Similarly, the FILENAME statement is used to access specific CMS external files.

The LIBNAME statement enables the user to write more portable S;'::; applications by providing a common syntax for redirecting access to specific SAS libraries. This syntax is basically the same for all hosts running Version 6 of the SAS System. The LIBNAME statement also provides an interface for creating and accessing sequential format SAS libraries. The format of the LIBNAME statement is;

LIBNAME libref <engine> <physical-name> <options>;

You can specify the physical iocation of the library through the physical name ~arameter.

For example, by specifying the filemode letter of an accessed jisk, the user can force the SAS System to create a new SAS library or read an existing SAS file ,hat resides on a specified disk. If the physical name parameter is specified as Eiletvpe filemode the SAS library is aliased to ~se a CMS filetype other than the default. When using engines that access flat files or data files created by other vendor products, the E ilename f i letype filemode ' format of the physical name ~hould be used. XPORT~ BMDpe, and OSI~ISeare examples of such engines. Finally,' specifying a physical name of 'TAP n ' will cause the SAS System to read and write a SAS I ibraryin sequential format on the specified virtual tape device.

The engine parameter of the LIBNAME statement gives the user the. ability to specify the I/O engine that should be associated with a SAS library. Every SAS library must be assoc.iated with an engine that is responsible for reading and writing -the members of the library. If an engine is not specified in the .LIBNAME statement, the SAS System attempts to determine the format of the SAS library. If the llbcary doesn't exist, an appropriate default or SASE;· engine is caosen.

Performance gains can be realized if the LIBNAME statement specifies the location and engine associated wi~h the SAS library. Specifying the filemode of the library allows the sAs System to avoid searching all accessed disks to find a soecific library. Specifying an· engine name avoids the overhead of determining the format of a given SAS. library. Librefs defined by the LIBNAME s;;atement are also found before ddnames defined by the eMS FILEDEF command. In all cases, the more informa t ion provided, the greater the. perf.ormance benef it.

230

The FILENAME statement provides for external files what the LIBNAME statement does for SAS files. The FILENAME statement is used to redirect the in~ut and output of external files from within the SAS System. The format of the FILENAME statement is

FILENAME fileref <devicetype> <physicalname> <options>;

The syntax of tae FILENAME statement is -,Jery similar to that of the CMS FILEDEF command. Aside from the above syntax,. the fileref parameter can alternatively be specified as fileref(member) when referencing the fileref to indicate that the user wants to access a member of a CMS MACLIB, a CMS TXTLIB, or a partitioned data set (PDS) residing on shared OS DASD. A fileref can be associated with numerous I/O devices,' such as DISK, TERMINAL, PUNCH, and PRINTER, through the device-type pa 3.mete!:. 3y specifying the physicalname paramet· r. the user can identify the filename, fiietype, and filemode of an ekternal file. The user can ~lso indicate that the file is on tape by specifying 'TAPn' as the phys icalname paraineter. Opt ions such as BLKSIZE, LRECL, RECFM, and LABEL control the character ist ics of external files created and read by the SAS System. The FILENAME statement also enables the user to reassign a ddname previously assigned with the CMS FILEDEF command (provided that ddname was not specified with the PERM option).

The FILENAME statement offers i?erformance gains when the physical-name parameter specifies the location of the external file. :Ohis specification avoids the overhead of searching for the external file on all accessed disks. As is the case with the LIBNAME statement, filereEs assigned through the FILENAME statement arl found before those created wi th the btS FILEDEF command. Also note that the specification of a FILENAME statement when performing I/O on CMS disk files causes the SAS System to use aative CMS .disk I/O rather than ~he more costly OS simulation I/O.

The addition of the LIBNAME & FILENAME statements within the SAS System provides the user with an interface for writing more portable SAS applications. Programs tiliHutilize these two constructs us~ally.. require only minor modific.3.tions to the physical-name parameter in order to run successfully on other systems running Version 6 of the SAS System.

Finally, both the LIBNAME & FILENAME statements offer pop-up windows wi chin the Vers ion 6 Display Manager Sys'tem that the user can use to inspect all currently existing logical assignments. Noniriteractive users can specify the LIST, SHOW, or QUERY commands in these two statements to report the details of existing logical assignments. In addition to the LIST, SHOW and QUERY commands, the CLEAR command offers a means of deleting a logical assignment when it is no longer needed.

Transparent Access to SAS Libraries

Transparent access is a term that is used to describe the ability of the SAS System to recognize a particular native library forma: a~d to allow the user to access the data sets within the library as if they were in the base library format. From a user's standpoint, no changes must be made in order to access a Version 5 Eormat data set using Version 6 of the SAS System. Converting Version 5 format data sets to Version 6 format can take place at the user's convenience. This eases the transition from one release of the SAS System to the next.

To further eXDlain the concept of transparent access, the f;llowing CMS example is offered. Suppose a user has several Version 5 Eormat libraries on his or her A disk. The user invokes Version 6 of the SAS System and then invokes the DATASETS proceriure on one of the Version 5 format :lbraries. Remember!ng that a library name translates into the Eiletype of the member, the SAS System interrogates all files on the A disk having the given filetype. As soon as the SAS System identifies the format of the native library, the searching is complete. The SAS System loads the Version 5 compatibility engine into memory, and the engine is called upon to process the requests of the DATASETS procedure. In addition to accessing Version 5 data sets on disk, the Version 5 compatibility engine is responsible for accessing libraries crea ted under Vers ion 82.3 and Version 79.5 of the SAS System. The compatibility engine is also used to process Version 5 sequential format data sets and Version 5 data sets located on OS DASD. Access to these libraries is done transparently for the user.

Transparent access ultimately enables users to access an~ native SAS data library without burdening them with the ~ask of identifying the release of the SAS System that created the library.

CMS & X Command Resolution

IBM®, with VM!SP Release 4 CMS, introduced functionality that enabled programs running under CMS .to .use the Eull functionality of the CMS search order. Previously, pro~rams that wanted to use the full CMS search order had to be coded with all the search rules, and rely on "hidden" CMS control blocks. The SUBCOM

function, introduced in CMS Release 4, provides

a single interface for CMS command resolution

under program control. relieving CMS (and SAS developers) of the need for search rules for each CMS program.

programmers reinventing

Version 6 of the SAS System uses this inter~ace. Now, the CMS/X command, CMS!X statement, and the CMS function behave as iE you had typed your CMS command from the eMS ready prompt, with full CMS search rules in effect.

Additionaly, ABEND handling has been wrapped around the CMS!X command interface. This allows the SAS System to recover from errors that occur during CMS!X command processing.

SORT Procedure

The interface to the sort utility under Version 6 of the SillS System has been modified to take advantage of EQUALS processing provided by the various sort utilities instead of the SAS System serializing the records and sorting by this field. The EQUALS option allows equivalant by variable records to remain in their input order or, in other words, their input sequence with respect to eacll other is preserved. For sort utilities that do not sUDport the EQUALS parame ~r, there is a CMS SAS System option, NOSORTLQOP, that inhibits the interface from passing EQUALS to the utility.

There is a new PROC SORT pararr"ter, NODUPKEY, that enables the user to emit duplicate key fields. In order for the sort utility to be invoked with this option, the SORTSUMF option has to be set indicating that the utility allows the "SUM FIELDS=" control card. ABEND handling has been added around the s.ort utility interface to .enable the S!?;S System to recover from problems that might occur wi thin the e~ternal sort program.

There is a new procedure; TRANTAB. in Release 6.06 of the SAS System that creates translate tables that can be used by PROC SORT via the TRANTAB=< table name > procedure opt ion. The TRANTAB procedure is documented in SAS Technical Report P-l97.

Example: Creating a Translate Table

The j"':o110',,1ng example uses PROC TRANTA3 to create .3. translate table Eor convertir~g EBCDIC strings to JPpe:case. The taole that is c~eated will be the current EBCDIC table with the lowercase chara·::.:ters.

characters replaced

231

proc trantab table=ebcdic; list one; replace 'a' 'ABCDEFGHI'; replace 'j' 'JKLMNOPQR'; replace's' 'STUVWXiZ'; save table=upper;

by uppercase

In the previous code segment, the LIST statement displays the translate table in hexadecimal representation. You can display the oucbound portion of the table using ONE, the inbound portion using TWO, or both by specifing BOTH.

Windows Environment

Version 5 of the SAS System made a first pass of providing a wind,)wing system for 3270 devices. Version 6 provides extensive windowing support to enhance the user interface. The following is a short overview of current support and future enhancements.

Windows are available, not only for viewing SAS log and listing output,. but for dis?laying graphics, data set informat ion, informat ion about files defined through the LIBNAME & FILENAME statements, and information provided by SAS global statements, such as TITLE and FOOTNOTE.

By specifying

OPTIONS GWINDOW;

as part of your SAS application, or specifying GWINDOW at start-up time, graphics output can be sent to a special graphics window. This graphics window can then be resized and moved about on the display. GWINDOW is the default setting. For Version 5 compacibility, NOGWINDOW should be specified.

You can open mUltiple 'windows and display them concurrently. Two other command line options to change the window format are TILE and CASCADE which cause SAS to treat windows in a tiled or cascaded format. The UNTILE, UNCASCADE, or RESIZE commands allow the windows to be put back into their original format. Also provided are pull-down menus and the ability to icon-ize windows, which leaves the windows open, but takes up much less space on the display.

If you have an IBM 3179 or 3472 terminal, you are also able to attach a mouse and gain much more flexibility from DMS. You can use the mouse to selecti tems from the pull-down menus and requestor windows.

Currently, as a future enhancement, investigation is underway to ascertain the feasibilicy of using the X Window System®Erom MIT. This will require having IBM's Tr ansmi ss ion Cont rol Protocol/In te rne t Protocol (TCP/IP) for VM. The X Windows System is an application program interface that allows an application access to a bit-mapped displa~ on a workstation or a dedicated X-Windows terminal connected to the CMS system via a Local Area N,=twork.

232

RELEASE 6.06 ENHANCEMENTS - SEQUr.."NTIAL

Tape Usage

Tape support under Release 6.06 of che SAS System is designed to taKe advantage of tape management support available in the BSAM access method under CMS. I f an external tape management system uses the DMSTVI interface, multifile and m'lltivolume facilities can be exploited by your SAS application.

~he FILENAME & LIBNAME statements offer facilities and options that can be employed to replace the CMS FILEDEF command. New opt ions that apply to CMS tape usage are BLKSIZE=, DENSITY=, 50V=, LABEL=, LEAVE=, SYSPARM=, TRACK=, and VOLID=. These opt ions are des igned to work similar to the ones that are offered in the CMS FILEDEF command.

For the most part, any operation that rean be done with disk files is also availaole ~rom

tape. One exception to this rule is chat the LIBNAME statement does not allow the 'lsec to 'Jse .the 'TAPn' form of the [lhys ieal name ',;hen you specify the TRANSPORT engine. However, for Release 6.06 of the SAS System, the werk-around that will allow you to create sequent ial transport format files is as follows:

FILENAME X TAPE 'TAP1' ~ABEL=SL 1; LIBNAME X XPORT;

The TAPECOPY, TAPECOMP, and TAPELABEL procedures are not available at this time and will be implemented in the future.

The VMTAPE®tape managment system, a product of the Systems Center, has facil ties for defer ing tape mounts until the tape file is opened. The SAS System supports this ability through the SY5PA~M operand on the LIBNAME and FILENAME statements. By use of the deferred mount capab:lity, applications can reference tape files with an OS-style dataset name instead of coding volume serial numbers.

Example: Multivolume Tape Data Sets

When an external tape management facility is available, you can issue the following SAS statements to create a data set that can span multiple volumes:

X LABELDEF <ddname> FLO? VOLID ?; LIBNAME <ddname> TAPE 'TAPl' LABEL=SL 1; DATA <ddname.dsname> (FILEDISP=NEW);

data step statements ... RUN;

The tape management system requests a FILEID and then the VOLID.

example FILEID is: example VOLID is: create one)

userid.<ddname> SCRATCH (since we want to

RELEASE 6.06 ENHANCEMENTS - PERFORMANCE

XA Exploitation

Version 6 of the SAS System is completely XA compatible. Version 6 is capable of using the much qreater address space that an XA system supports, and it loads and runs above the 16-Meg line. It is now also practical to install larger portions of heavily used images into segments since a larger linear address space is available. Along these lines, SAS Institute has provided ALL606 LLIST, a segment loadlist control file that loads ALL of SAS into segments above the l6-Meg line. The linear layout of the ALL606 LLIST file ensures that all images can be used f rom segments 5 imul taneously, unl ike the overlay structure that is used when loading segments below the 16-Meg line. ALL606 can also be edited to remove infrequently used images to reduce space. The functionality of the ALL606 LLIST is possible due to the fact that Versicn 6 is composed entirely of re-entrant code.

Vector Facility

IBM's Vector Facility (VF) is an optional feature of all models of 3090 processors. The Vector Facility is an extension of the real processor and is des .gned to provide significantly increased levels of performance for computationally lntensiveappiications. If a real <1F exists, and if the V~l user directory does not explicitly state otherwise, then a virtual VF is automatically defined to the virtual machine at logon time.

233

The option that controls whether or not the SAS System uses an existing \IF is VECTOR/NOVECTOR, with the default being VECTOR. '!'he (NO)VECTOR option is documented in the CMS Companion and is in the Help subsystem as a host option. It can be specified in a configuration file or as a SAS invocation option.

7here are several SAS procedures that use the Vector Facility to varying degrees. Our testing has shown that use of the Vector Facility can decrease excecution times by as much as 60%. The dec~ease in t.ime your appiication will see depends on its complexity. A simple tdsk with little data will receive little benerit, but a more math-intensive task will see greater benefits.

Some background Vector Facility:

information concerning the

scalar A simple data item. It can be a floating-point binary intc:ger, data.

number, a or logical

vector A linearly ordered collection of scalars. Each scalar is an element of the vector. All elements are of the same type.

o

o

o

o

o

o

o

o

There are scalar instructions and there are vector instructions.

The Vector Facility is an optional feature of all models of the 3090 processor.

The Vector Facility is an extension of the real processor and is des igned to prov ide significantly increased levels of performance for a computationally intensive ;;pplication.

The 'lector Facility is a synchronous instruction processing facility -:apable of high-speed manipulation of fixed-point and floating-point data.

The base 'Jirtual CPU of a virtual machine is automatically defined with a Virtual VF at logon unless the user directory indicates otherwise.

VF support is OCO: Modules HCPAFF, HCPHIS, HCPVDV, HCPVFD, and FCPVFF.

VECTOR/NOVECTOR is in the help SUbsystem as a host option.

The host determines if the correct option is in effect and if the Vector Facility is available. The SAS System uses the VF by default if it is available.

0 Dual Path Code is used. If the 'IF is to be used (and the procedure supports it) , assembler sub-routines are called instead of using ~he C generated code (scalar operations).

o 171 vector assembler instructions.

o Query Virtual Vector.

o Display VRO-VR15, VAC, VMR, VSS.

oSee Virtual Machine Operations (SC23-0377) for more information.

Version 6 Format and Informat Catalog Support

In Version 6 of the SAS System, formats and informats created by the FORMAT procedure are stored in SAS catalogs. The catalog name is decided by the user's specification of the LIBRARY= statement in the FORMAT procedure. This ability to collect user-written formats and informats into a single SAS catalog gives the user a simple method of ouilding format and inf:nmat libraries. Likewis·., the user is able cO manage chese catalogs using normal SAS utilities such as the CATALOG procedure or the CATALOG window available in version 6 of the SAS System.

Previous releases of the SAS System under CMS stored formats and informats as loose TEXT files on the user's A disk. The user was responsible for each individual TEXT file or could opt iona11y collect the TEXT files into a CMS TXTLIB file. This process was confusing and cumbersome for many users. Storing user-written formats and informats in SAS catalogs provides an eas? Interface for format and informat management.

For example, suppose catalogs COntaining (JOBl.FORMATS.CATA~OG

the user creates two SAS formats and informats

and JOB2. FORMATS. CATALOG) and places these catalogs on the A minidisk.

PROC FORMAT LIBRARY=JOBl; ... format and informat definitions

PROC FORMAT LIBRARY=JOB2; '" format and informat definitions ...

In order to access the forma ts in JOBl-FORMATS.CATALOG, 'Jse the LIBNAME statement to assign the LIBRARY libref to the JOBl library as follows:

LIBNAME LIBRARY 'JOBl A';

234

At this point, all of the formats and informats contained in JOBl.FORMATS.CATALOG are made known to the SAS System. Since only one library can be assigned to the LIBRARY libref at a time, the user must change the deE ini tion of the LIBNAME statement in order to access the formats and informats contained within the JOB2 library as follows:

LIBNAME LIBRARY 'JOB2A';

For reasons of compatibility, the SAS System will continue to look for formats and informats in loose TEXT and specified eMS TXTLIB files. However, this search begins only after a search for t >" SAS catalog [Jointed to by the LIBRARY libref has been exhausted.

ator ing formats and informats in SAS catalogs has several key advantages. Because the format oE the SAS catalog is known to the SAS System, utilities such as the CATALOG procedure a:-.d the new CATALOG ·..,inctow can be used to manage formats and informats present within the catalog. Users can also gain an increase in efficiency since the search for a user-written Eormat or informat begins with the SAS catalog pointed to by the LIBRARY libref.

Segments

Segment support f)r Version 6 is upwardly compatible with Version 5 of the SAS System, providing at minimum the same functior.ality as before. A shift of the series indicator in segment names assures that Version 5 and Version 6 segments can co-exist peacefully. Other minor changes include

o SASCSEGI module updated and renamed to SASCSEG6.

o

0

o

o

fn LOADLIST files updated & LLIST.

renamed to En

Cl1SSEGS SAS has been replaced by CMSSEGS E:EC, thus the installation nolonger requires the use of SAS before SAS is installed into segments.

The manual prompting of segment information has been replaced by a CNSSEGS control file; however, prompting is still available if a "?" is coded.

The CMSSEGS program automatically generates a DNKSNT file for non-Bimodal systems or an EXEC wi th segment def ini t ions for Bimodal systems.

\

\:

Another area where segment support has been refined is the load/overlay level. for SUPERVISOR,PROCl, and PROC2. These levels can now be loaded noncontiguously by specifying the load address of each level on the LOADADDR card in the CMSSEGS control file. This was previously done wi th diHicult address of

CONCLUSION

boundary cards, mak i ng to directly s~a~ify

each overlay level.

it the

much more startinq

Release 6.06 ·of the SAS System or; eMS presents many new and different capabilities to both the SAS System user and SAS System applic,atior.3 programmer. New levels of portability insure that an application can be migrated from the development platform to the production platform with a minimum of time and effort. Enhanced pe'rformance and greater functionaiity mean greater productivity and better through-put for your application. Version 6 of the SAS System is an exciting new developme:1t system and gives users the functionality they require in today's world.

SAS is a registered trademark of the SAS System.

IBM is a registered trademark and VM/XA is a trademark of IBM Corporation.

BMDP is a' registered trademark StatistitalSoftware, Inc.

OSIRIS is a reg istered trademark of Computing Services:

:< Window System is· a trademark. Massachusetts Institute of Technology.

235

of BMDP

Columbia

of the