Taking advantage of the SAS System on OS/390

Transcription

1 Taking advantage of the SAS System on OS/390 Dave Crow

2 Where I m from ---> Final: DUKE 77 UNC 75

3 The SAS System for OS/390! Getting started with Web Access! What s new in V8 and 8.1 of SAS! What s coming: Project Mercury (V9) SAS is a registered trademark or trademark of SAS Institute Inc. in the USA and other countries. indicates USA registration. Other brand and product names are registered trademarks or Trademarks of their respective companies.

4 SAS is READY: 8e

5 OVERVIEW: WEB Access WEB BROWSER TCP IP WEB SERVER Broker Disk files * Directory based App Server * SAS/IntrNet can also do JAVA -- not shown here. TCP/IP * Batch jobs * (SAS/ IntrNet)

6 SAS/IntrNet Performance! WEB Server and APP Server need high performance -- like TSO.! Work must be appropriate for that priority.! For long programs, consider spinning off a Batch job and use E- Mail for notification.

7 HFS Directory based File System! HFS is the UNIX file system for OS/390! HFS is an integral part of OS/390! Its use requires customization, and is not provided at all sites! Is not restricted to UNIX work; can be used by any OS/390 job or task.! Sample path name: /u/sasdec/v8.projects/schedule

8 One Last HFS example // EXEC PGM=IEBGENER //SYSPRINT DD DUMMY //SYSIN DD DUMMY //SYSUT2 DD SYSOUT=A //SYSUT1 DD RECFM=VB,LRECL=250, // BLOCKSIZE=4096, // PATHOPTS=ORDONLY, // FILEDATA=TEXT, // PATH= /u/sasdec/public_html/daily.job/report_index.html

9 Creating HTML! V6 style macros are still there (%out2htm, %ds2htm)! ODS! Use these to write directly to HFS files

10 Alternatives to HFS! Sequential files! PDSE! NOT: PDS! FTP access method to Web Server Host

11 Web Enablement: Getting Started! Start small -- Learn the tricks one at a time.! If HFS is new to you, put it off.! Do static Web publishing to disk files before you try dynamic Web publishing with SAS/IntrNet.

12 Web Enablement: Getting Started! If using TCP/IP is new, test SAS/C run time configuration with simple FTP access method, or job.! Use product, tech support demos.

13 So far we ve talked about:! SAS/IntrNet! ODS! HFS file system! FTP access method! access method! GIF files, RTF, HTML,CSV

14 What else is in V8?! More ways to access the mainframe from other hosts! Enhancements to traditional SAS

15 SPAWNER! The spawner is used by some options of SAS/Connect and SAS/IntrNet! Spawner uses UNIX System Services! Requirements: -OS/390 V2R6 -APF Authorization -Authorization to special UNIX services

16 AppDev Studio! Supports using OS/390 as a server! AppDev Studio is a product separate from SAS, but it does have dependencies on SAS.! For OS/390, recommend at least V8.1

17 Integration Technologies! Provides access to SAS data objects using standard interfaces! Used by Enterprise Guide and Enterprise Reporter! Also allows access from Visual Basic, and other programming languages! Note: Integration technology has its own OBJECT SPAWNER.

18 3270 support (V8 compared to V6).! Much more use of 3270 Graphic capability! V8 SAS/AF BUILD FRAME requires PC or UNIX SAS! Syntax Sensitive Color Editor (8.1)! Specify SAS option: COLORPGM! Issue the command: SYNCOLOR ON from the command line! Use SYNCONFIG to change the colors

19 Multi-volume Support in V8! Solves problems encountered in V6! V6 style still works! Can now extend to new volume dynamically! Don t have to use Guaranteed Space with SMS! Works with HSM migrate/recall

20 IN MEMORY FILES (8.1)! Cache specified file in memory for duration of SAS session.! Useful when a single file is processed many times.! Can significantly reduce CPU, I/O, and Elapsed time.! Takes more memory: Make sure your system will perform well.! Enabled with the SASFILE statement.

21 V6/V8 Co-existence! V8 designed to co-exist with V6! Excellent paper at: 8papers/V6andV8.pdf! Special consideration for use of XMS access method: SAS/SHARE client and server must be at same level of the SAS system.

22 Performance (V6 to V8): CPU! Typically, V8 is slower than V6.! Most work is slightly slower.! Some work is faster, particularly the STAT procs.! 10-15% slowdown for a given job is not unusual.! If a particular job s performance in V8 is a problem, report it to tech support.

23 Performance (V6 to V8): Memory! V8 uses significantly more memory than does V6.! Small jobs typically double in size.! For large jobs (above 30Meg), the increase is usually a much smaller percentage.! Storage utilization below the 16meg line is about the same, or slightly reduced.! Use of OS/390 LPA very important.

24 Performance (V6 to V8): I/O! V8 I/O is usually about the same as V6.! Any significant increase that causes problems should be reported to tech support.

25 Performance:What does it mean?! These are observations specific to OS/390. SAS on other hosts will show very different comparisons.! V6 runs V6 work a little faster.! V8 has many functions that V6 does not have. New features can often be used to do same thing easier, better, faster.! V8 is designed for co-existence with V6 to allow a gradual transition to V8.

26 Documentation! SAS is moving toward online documentation. Where possible, V8 publications will be delivered on CD.! Hardcopy can be ordered.! A CD with pdf files is also available to allow you to print your own hardcopy as needed.! Give us your feedback: what works, what doesn t?

27 Where are we now: 8.0, 8.1! 8.0 is a high quality system. A lot of customers are installing and using it.! 8.1 is in the box. An NLS version is underway.! What to install? We re going to put out function incrementally. Don t wait: When a release has function you need, put it up.

28 What s next: 8.2! 8.2 is only 6 months away.! 8.2 will have the beginnings of a SESSION ENCODING concept. We want to make European and Asian encodings work as naturally as US EBCDIC does in the U.S.! But 8.2 won t have everything, and it will be easier to get to 8.2 from V8 than from V6, so don t wait till it s all finished.

29 What s next? V9:Project Mercury! Demand for CPU is growing faster than increases in uniprocessor speeds! S/390 systems often 10-way processors! Similar requirements for I/O work: Volume of data is increasing faster than the I/O data rate! Project Mercury is aimed at enabling SAS to exploit both Parallel I/O and Parallel processing! Look for demo in a year.

30 What s next: Project Mercury! As part of this, on OS/390 we are looking at supporting:! OS/390 Striped data sets for SAS data libraries! Unbound libraries in the Native OS/390 file system (presently unbound libaries are only available in the HFS system)! Batch Pipes! And: V9 won t have it all. There s more to come.

31 Acknowledgements! Bryan Wolfe! John Hamlet! OS/390 Host Staff

32 About the Speaker Speaker Company Telephone Fax Dave Crow OS/390 Host Development SAS Institute Inc. SAS Campus Drive Cary, N.C phone: (919) fax: (919)

33 Additional information Our NEW Web site: Co-existence between V6 and V8: v8papers/v6andv8.pdf Details of what s new in V8: periodicals/mvsdirect/current/index.html Documentation of access method: technote/ts605/html me at: dave.crow@sas.com

34 Other SEUGI sessions Today: Tech theater 2: 14:00 (and after) Thursday: * IBM booth for Q/A: 12:20-14:00 * Tech theater 2: 15:45 Friday: Tech Competency Center for Q/A: 10:30-11:45

35 Speaker BIO (Dave Crow) Dave is the manager of the MVS host development group. This group of ten people develops and maintains the code that interfaces the SAS portable code to the OS/390 operating system. Currently, this is approximately 400,000 lines. Dave's own coding responsibility is for the machine code generator used by the data step and other PROCs as a "Just In Time" compiler. Dave graduated with a BSEE from Duke University in 1970, and came to SAS in 1996 after 26 years as a customer systems programmer.