~p~atb~~ INSIDE I I " COS-TO-UNICOS MIGRATION PLAN " PLANNING GUIDE " HOW TO PERFORM DUPLICATION CHECKS " STARTING YOUR CODE CONVERSIONS

Transcription

1 1 /,S INSIDE " COS-TO-UNICOS MIGRATION PLAN " PLANNING GUIDE " STARTING YOUR CODE CONVERSIONS " HOW TO PERFORM DUPLICATION CHECKS " TRAINING CLASSES ~p~atb~~ I I SCIENTIFIC COMPUTING DIVISION NATIONAL CENTER FOR ATMOSPHERIC RESEARCH

2 About the Cover In May 1990, SCD will install a CRAY Y-MP8/864 computer at NCAR. This new system will have a different hardware architecture and a different operating system than the existing CRAY X-MP/48 computer. The CRAY Y-MP8/864 computer is identified with a new naming convention: * CRAY is the manufacturer, * Y-MP specifies the hardware architecture, * the 8 before the slash (/) indicates that this architecture accommodates up to eight processors, * the 8 after the slash (/) states the number of processors installed in this particular unit, and * 64 specifies the amount of primary memory (in millions of 64-bit words) installed in this particular unit. SCD Computing News welcomes cover graphic submissions. Please send your graphic, along with a description including SCD facilities or software used, to Christine Guzy, Mesa Lab, or send to guzy@ncar.ucar.edu, or call Christine at (303)

3 I I - I - 2 SCD Director's Column 3 Introducing the COS-to-UNICOS migration plan Migration schedule to help you plan the conversion of your codes from COS to UNICOS 5 Use this planning guide to convert your code Identifying areas in your COS codes that you must change to run them under UNICOS 6 Conversion steps you can perform using COS Operations you can peform under COS to make your code conversions run more smoothly 8 Start your duplication checks now to ensure successful code conversions Procedure for establishing a reference output for all of your COS codes 10 SCD offers training classes to help you prepare for the CRAY Y-MP Training classes help both new UNIX users and experienced UNIX users

4 by Bill Buzbee This special issue of the SCD Computing News is designed to prepare you for migrating from COS to UNICOS. Among the many advantages of UNICOS are the new capabilities for incorporating interactive debugging and interactive graphics into supercomputer models. Further, the coupling of UNIX with emerging standardized network capability such as the X Window System will provide a rich distributed computing environment. Finally, when the next-generation supercomputers become available, they will be running UNIX, and we will be well-prepared to make best use of them. This special issue of the newsletter is brief and very specific; I urge you to read it from cover to cover. The COS-to-UNICOS Migration Team has identified the critical information that most users will need to prepare for UNICOS. The hardware schedule and some software considerations appear in the lead article "Introducing the COS-to- UNICOS migration plan." The second article is a conversion planning guide developed by Sally Haerer and the Migration Team. Complete your conversions while both the COS and UNICOS computers are on site. I strongly urge you to complete your conversions while both the COS and UNICOS computers are on site. Having both machines available simultaneously will greatly facilitate your isolation of any differences in results. account on shavano to convert your codes that run under COS. Effective immediately, code conversion projects will receive priority for CPU time on shavano. User Services will also be using shavano for conversion training classes. These classes will run from late January through mid- February and will resume in June, as soon as the Y-MP becomes available. Class descriptions appear in the last article of this issue. You can make significant progress with your code conversions using only the CRAY X-MP/48 running COS. Details appear in the articles "Start your duplication checks now to ensure successful COS-to-UNICOS conversion" and "Conversion steps you can perform using COS." The changes coming to our supercomputing facility will affect all users, and our schedule is an aggressive one. In addition to the benefits of UNICOS, consider how you can take advantage of the increased power provided by the Y-MP: * the bank of central processors is doubling in size and will run with a 30% faster clock rate, * the 60-gigabyte local disk capacity triples the storage available on the X-MP/48, and * the primary memory is increasing by a factor of eight. If you have questions about converting your codes, please contact an SCD consultant using the information on the back cover of this newsletter. Please note that shavano, the CRAY X-MP/18 computer running UNICOS, will be removed from the computer room on February 28. You still have time to use this system for converting your code; if you are a current COS user, you can open an 1

5 Introducing the COS-to-UNICOS migration plan by Sally Haerer Our acquisition of a CRAY Y-MP8/864 computer will affect every user of the supercomputing facility at NCAR. This presents two important issues: the computing power at NCAR will increase significantly, and UNICOS will replace the COS operating system for supercomputing at NCAR. All users of the CRAY X-MP/48 computer at NCAR should benefit from the increases in performance and power offered by the Y-MP, but they will also have to change their programs to run under UNICOS. Our experience shows that the average COS code takes one to two weeks to convert to UNICOS. This special newsletter issue and other documentation will help you start this conversion. Hardware schedule The new Y-MP runs with a clock period of 6.0 nanoseconds (ns) and will have 8 CPUs and 64 million words (Mwords) of central memory. When it is fully configured, it will have a 256-Mword SSD and 60 billion bytes (GB) of disk storage. In contrast, the CRAY X-MP/48 runs with a clock period of 8.5 ns, has 4 CPUs, 8 Mwords of memory, a 256-Mword SSD, and 20 GB of disk storage. These numbers indicate the performance and power increases users can expect, but all codes running under COS must be converted for use with UNICOS. The following hardware schedule shows the critical dates for your conversion efforts: February 28-shavano, the CRAY X-MP/18 computer running UNICOS, is removed. May 21-the CRAY Y-MP8/864 running UNICOS arrives. It requires approximately 25 days for installation and acceptance testing. June 15-the CRAY Y-MP is available to users; however, it does not yet have all of its disks or the Solid-state Storage Device (SSD) attached. These disks and the SSD will come from the CRAY X-MP/48 running COS, so they will not be available for the Y-MP until the X-MP/48 is removed. August 15-the SSD is removed from the X-MP/48 and sent to Cray Research for rewiring to make it run with the Y-MP. This process is expected to take approximately six weeks. With this removal of the SSD from the X-MP/48, COS users should expect a drop in performance. October 1-the CRAY X-MP/48 running COS is disconnected; this marks the end of computing with COS at NCAR. Also at this time, the SSD should arrive back at NCAR for attachment to the Y-MP, and the disks from the X-MP/48 will be added to the Y-MP. October 7-the Y-MP, with all its disks and its newly re-wired SSD, is available to users in this fully configured state. We encourage users to complete their code conversions between June and August 1990 while both the COS and UNICOS systems are available. Software considerations UNICOS complies with UNIX System V, an interactive operating system with a batch processing facility (NQS-Network Queuing System). It offers more flexibility than COS, and because UNIX has gained widespread acceptance as an operating system available on most computers today, UNICOS will allow SCD to provide a "one-operating-system" environment. More and more users will only have to know one operating system to use a variety of computers-from workstations and front ends to supercomputers. The default Fortran compilers on the Y-MP will be CFT and CFT77; both will be the same versions that are the current default compilers on the X-MP/48. It is important to note that on the Y-MP, CFT is limited to using no more than 16 Mwords of primary memory; CFT77 does not have this limitation. (CFT was limited to using no more than 8 Mwords of primary memory on the X-MP, but this difference between the two compilers is not noticeable on the X-MP/48

6 because its entire central memory is only 8 Mwords.) However, since the Y-MP will have 64 Mwords of memory, this compiler difference may affect your future needs. Multitasking will be available on the Y-MP in the same form as on the X-MP/48. In addition, autotasking will be available with CFT77 on the Y-MP. The GKS NCAR Graphics Package will be supported on the Y-MP, and the pre-gks NCAR Graphics will not. Edition 9.2 of the International Mathematical and Statistical Library (IMSL) will not be moved to the UNICOS computer, users who plan to use the Y-MP will have to update all IMSL calls to the current 10.0 version. Most performance tools and debuggers available on the COS system will be the same or will have equivalents on the UNICOS system. The UNICOS system will offer additional new capabilities such as interactive debugging tools. These features will be covered in other documentation. Documentation SCD's User Services Section has been busy preparing needed documentation to help users make the transition from the COS environment to the new UNICOS environment. Both of the following documents are scheduled for release in late January: * "COS-to-UNICOS Conversion Guide"-designed to help users with the process of converting and moving codes developed on the COS system to the new UNICOS system. * "Elementary UNIX"--a brief UserDoc to explain the fundamentals of UNIX and provide a description of the most important UNIX commands that Y-MP users at NCAR will need to get started computing with UNICOS. Impact of UNICOS UNICOS is a powerful, flexible, modem operating system for supercomputers. Of course, it will require time and effort for current users of the COS-based system to become comfortable with the new system; this would be true for any new operating system. Many COS users have already made the conversion from COS to UNICOS: it is possible to accomplish this task! The "COS-to-UNICOS Conversion Guide" will provide good assistance; it has been written by SCD consultants who have experienced the process. We believe that once you become adjusted to UNICOS, you will be satisfied and pleased with the advantages it offers. Sally Haerer is the Consulting Group Head in the SCD User Services Section. I

7 Use this planning guide to convert your code by Sally Haerer To prepare yourself for the COS-to-UNICOS conversion tasks that await you, you need to identify critical areas in your major codes that are now running under the COS operating system. The Migration Team has compiled the following list of critical factors that affect each conversion. Some answers you will know immediately, and some answers will have to be researched; we believe that the time you spend now will be worth it at conversion time. If it becomes necessary to call the SCD Consulting Office for assistance, it would be most helpful if you would have this planning guide available when you call. To contact an SCD consultant, use the information on the back cover of this newsletter. We recommend that you make a separate copy of this guide for each major code you plan to convert to UNICOS and then fill in the answers to each item for these codes. 1. Name of program or model: 2. I/O-type definition (for example, COS-blocked binary, SSD usage, MSS usage): 3. Does your code use old datasets on the MSS? (particularly COS-blocked, multifile datasets): 4. Does your code use multitasking? What type? (macro or micro): 5. Does your code use the pre-gks version of NCAR Graphics? (How much and how tailored is it?): 6. Have all of your IMSL library calls been upgraded to Version 10.0? 7. Are there any special Cray Assembly Language (CAL) routines used in this code? 9. CPU time required for your entire code to run to completion: 10. CPU time required for verifiable results to be generated: 11. Central memory required: 12. Disk space required: 13. Do you have any special deadlines before the end of 1990 requiring Cray computer results that have not yet been produced? (Publications, meetings, other): As this list indicates, some codes will take significantly longer than others to convert. Clearly, programs that take a lot of CPU time to run will take more time during conversion than programs that don't take a lot of CPU time. Similarly, programs that use large amounts of memory, I/O, and disks will have to wait for all of these resources to be available before each duplication check can run. Consider the amount of time you will need to convert each use of pre-gks NCAR Graphics to the GKS version. Also, consider that you may need to change or reassemble CAL routines written for the X-MP to run on the Y-MP. Finally, plan to change the syntax of Fortran-callable JCL statements to adhere to the UNICOS method of accomplishing operating system commands from within an executing program. This is just a general list of basic factors; there may be more issues relating to your specific codes. We hope this guide helps you begin the conversion task by defining major factors within your codes. Sally Haerer is the Consulting Group Head in the SCD User Services Section. 8. Locate each occurrence of Fortran-callable JCL in your code and identify the function that each call is invoking:

8 Conversion steps you can perform using COS by Tom Parker Before the CRAY Y-MP running UNICOS arrives, you can still perform a variety of tasks on the Cray X-MP/48 running COS that will make your code conversions go more smoothly. Here are four suggestions for steps you can begin taking now. Convert pre-gks NCAR Graphics calls to GKS calls. Since NCAR plans to discontinue support of the pre- GKS version of NCAR Graphics, it has never been made available on UNICOS systems. Thus, you must convert any programs that call pre-gks routines to use the GKS calls. Both pre-gks and GKS are currently available on COS, so you can make this conversion step prior to the installation of the Y-MP. If your code has pre-gks calls, we recommend that you perform this step now because you might have serious difficulties trying to do this after the COS X-MP is removed. To assist you in converting to GKS, we have prepared the UserDoc "Converting Pre-GKS NCAR Graphics to NCAR Graphics, Version 3.00," Draft Version 1.0, January To obtain copies of SCD documents, see "SCD UserDocs, Manuals/Output Mailing" on the back cover of this newsletter. Convert IMSL Edition 9.2 calls to Edition 10.0 calls. If you have been using Edition 9.2 of IMSL, the best strategy is to convert directly to the 10.0 Edition, because IMSL, Inc. no longer supports 9.2. We strongly recommend that you convert to Edition 10.0 while the COS system is still available. This conversion will involve effort because the subroutine names, function names, and calling sequences have changed radically. The best way to change to 10.0 is to use the IMSL Libraries Edition 10.0 Update Guide. To obtain it, contact the Consulting Office using the information on the back cover of this newsletter. This guide explains which 10.0 subroutines or functions replace the 9.2 ones. Then, using the GETDOC utility on the CRAY X-MP/48, you can get documentation explaining details such as argument specification for the new routines. For example, GETDOC, LIB=IMSL, DOC=(ABIBD). obtains the documentation for routine ABIBD, the Edition 10.0 replacement for 9.2's ABIBN. An alternative to this strategy is to use the IMSLCNV library in conjunction with IMSL Edition IMSLCNV is a conversion library that allows 9.2 calls to be used with the 10.0 library. While making it easier for you, the conversion library is known to be less efficient than IMSL 10.0 alone, and there are cases where numerical differences between 9.2 and IMSLCNV are known to occur. Finally, you'll need to know how to load the IMSL 10.0 library on the CRAY X-MP/48: SEGLDR, CMD='LIB=IMSLIB'. -or- LDR, LIB=IMSLIB. If you are using the conversion library, enter: SEGLDR, CMD='LIB=IMSLIB,IMSLCNV'. --or- LDR, LIB=IMSLIB:IMSLCNV. Locate and identify Fortran-callable JCL routines. All Fortran-callable JCL routines need to be modified when your code runs under UNICOS. To prepare for this, check your source codes and note all statements such as CALL ACQUIRE, CALL DISPOSE, and CALL SKIPF. Here is a complete list of Fortrancallable JCL routines: ACCESS ACQUIRE ADJUST ASSIGN COPYD COPYF COPYR COPYSD COPYSF COPYSR COPYU DELETE DISPOSE MODIFY RELEASE SAVE SKIPD SKIPF SKIPR SKIPU

9 Under UNICOS, some of these routines will have a direct counterpart. Others may require more effort to make the conversion. More information on converting these routines will be available in the upcoming "COS-to-UNICOS Conversion Guide," scheduled for release in late January. Although you cannot convert any Fortran-callable JCL routines using COS, this step is still useful because: * it helps you locate your source codes, * it helps you determine which of your codes contain these calls, as well as how many of these calls occur in each code, and * it alerts you to areas that need attention when you make the conversion. Change your Fortran compiler from CFT to CFT77. Although both CFT and CFT77 will be available on UNICOS, we feel that you will benefit from converting from CFT to the CFT77 compiler for the following reasons: * Cray Research is not making further enhancements to CFT (although it is still supported). * On the Y-MP, CFT is limited to using no more than 16 million words (Mwords) of primary memory; CFT77 does not have this limitation. (CFT was limited to using no more than 8 Mwords of primary memory on the X-MP, but this difference between the two compilers is not noticeable on the X-MP/48 because its entire central memory is only 8 Mwords.) However, since the Y-MP will have 64 Mwords of memory, this compiler difference may affect your future needs. * Although compile times with CFT77 are usually longer, the object modules produced are more efficient and run faster. * CFT77 has additional capabilities such as INCLUDE statements, array notation (for example, A=B where both are arrays), "automatic" arrays (to help save storage), tab character recognition, and so forth. * Under UNICOS, CFT77 will also perform automatic multitasking (autotasking). For more information about converting from CFT to CFT77, please see Appendix H of the CFT77 Reference Manual, available from Cray Research by writing: Order Desk Cray Research, Inc Pilot Knob Road Mendota Heights, MN You may also order Cray documentation by calling (612) If you order by telephone, please state that you are affiliated with NCAR and provide a billing and shipping address. The SCD Consulting Office (Mesa Lab Room 17) and SCD User Area (Mesa Lab Room 22A) also have reference copies of this manual available for your use. Tom Parker is a consultant in the SCD User Services Section.

10 Start your duplication checks now to ensure successful COS-to-UNICOS code conversions by Dick Valent All users of the CRAY X-MP/48 computer at NCAR who will use NCAR's supercomputing facility after ' September 1990 are encouraged to prepare each of their codes for a "duplication check." A duplication check is a test for comparable results from two independent performances of the same operation. The duplication check needed for supercomputing at NCAR requires you to run a test case for each of your codes run under COS, then save the appropriate input and output information so you can compare the results with the output produced by the UNICOS system. Since the CRAY X-MP/48 computer will be decommissioned at the end of September, you should start your duplication checks using the COS system as soon as possible. It's important to start this process now, because sufficient computer time may not be available at the last minute. If you wait until after the COS system is gone, you will have nothing to compare with your output from the UNICOS system. To run the COS part of each duplication check, perform the following steps: Step 1 Determine the variables and the amount of output you need to be sure your COS-to-UNICOS comparison is valid. For example, output data from three iterations of a particular model may be enough if the output fields represent sensitive variables in the model. Step 2 Next, decide how you want to save the data for future comparison. If the amount of data you're comparing is modest, you will be comfortable with making hardcopy for later comparison by eye. On the other hand, if the amount of data is huge, you may need to reduce the size. If you can't do this, or if you require machine-checking, then you must save the data files on the Mass Storage System (MSS) or somewhere else. To avoid problems with machine-checking under UNICOS, save each of your output datasets to be compared as single-file datasets, and avoid blankcompression in their creation. (By default, COS inserts special characters to represent strings of blank spaces in character files, and UNICOS does not.) Step 3 If you have been using Edition 9.2 of IMSL, the best strategy is to convert directly to the 10.0 Edition, because IMSL, Inc. no longer supports 9.2. We strongly recommend that you convert to Edition 10.0 while the COS system is still available. This conversion will involve effort because the subroutine names, function names, and calling sequences have changed radically. The best way to change to 10.0 is to use the IMSL Libraries Edition 10.0 Update Guide. To obtain it, contact the Consulting Office using the information on the back cover of this newsletter. This guide explains which 40.0 subroutines or functions replace the 9.2 ones. Then, using the GETDOC utility on the CRAY X-MP/48, you can get documentation explaining details such as argument specification for the new routines. For example, GETDOC, LIB=IMSL, DOC=(ABIBD). obtains the documentation for routine ABIBD, the Edition 10.0 replacement for 9.2's ABIBN. An alternative to this strategy is to use the IMSLCNV library in conjunction with IMSL Edition IMSLCNV is a conversion library that allows 9.2 calls to be used with the 10.0 library. While making it easier for you, the conversion library is known to be less efficient than IMSL 10.0 alone, and there are cases where numerical differences between 9.2 and IMSLCNV are known to occur. Finally, you'll need to know how to load the IMSL 10.0 library on the CRAY X-MP/48: SEGLDR, CMD='LIB=IMSLIB'. --- or- LDR, LIB=IMSLIB.

11 I - I If you are using the conversion library, enter: SEGLDR, CMD='LIB=IMSLIB,IMSLCNV'. -or- LDR, LIB=IMSLIB :IMSLCNV. Step 4 Convert your COS job to use the NCAR Graphics libraries supported on the UNICOS computer. This means using the COS GKS libraries GKSNCAR and GGLNCAR. If your results do not use variables returned from calls to graphics routines, then you may delay the pre-gks-to-gks conversion until later. For graphics conversion instructions, see the UserDoc titled "Converting pre-gks NCAR Graphics to NCAR Graphics, Version 3.00." To obtain copies of SCD documents, see "SCD UserDocs, Manuals/Output Mailing" on the back cover of this newsletter. Step 5 Use the default CFT compiler only if you intend to use CFT under UNICOS. Otherwise, use the default CFT77 compiler under COS if you intend to use that compiler under UNICOS. Your duplication checks must use the default versions of the CFT or CFT77 compilers under COS because none of the older Fortran compilers will be available under UNICOS. If your code uses C or the Cray Assembly Language (CAL), please contact the SCD Consulting Office for information about the proper COS version of the compiler or assembler you will need to use. Steo 7 Save all of the following items for each of your codes so that you can use them when you run the corresponding UNICOS part of your duplication check: * input data, * input source code (Fortran, CAL, etc.), * input job control language (JCL), * butput COS log file, using the MAP=FULL option on the load map, and * output data. Note: All input items (data and source code) must not be changed between the time you run the COS job and when you run the UNICOS job. Also be sure to save a copy of the JCL you used with the COS job so you can review how your code interacted with the data. If you have any questions about using this duplication check process with your codes for the COS-to- UNICOS conversion, please contact an SCD consultant. Dick Valent is the Software Libraries Group Head in the SCD User Services Section. Step 6 Prepare your COS job and run it, using the MAP=FULL option on the loader (SEGLDR or LDR). Save the resulting load map; it will come in handy later if you suspect that library differences are causing numerical differences between the COS and UNICOS results.

12 SCD offers training classes to help you prepare for the CRAY Y-MP by Sally Haerer Two classes will be offered to help prepare you for the replacement of the CRAY X-MP/48 computer running COS with a CRAY Y-MP8/864 computer running UNICOS: * Conversion classes will train you to modify the codes you ran under COS so you can run them on a UNICOS computer. Conversion classes will also include basic information about UNICOS. * UNICOS classes are designed for users who have not run codes under COS. These classes will help users learn and use the various features offered by UNICOS. Each class will be offered at two levels to ensure that the pacing is correct for the students: * For users with no experience using computers that run a UNIX-like operating system, the instructors will provide a brief introduction to UNIX in an extra session. * The more advanced level is for users who have a working knowledge of UNIX. All classes will give the students experience using a Cray computer running UNICOS. Exercises will be realistic, but they will be designed to use only limited amounts of I/O and CPU resources. Each exercise will provide experience with handling one or two vital problems or issues so that you can quickly develop a well-rounded understanding of the conversion process and computing with UNICOS. Class schedules and registration information The first set of conversion classes have been scheduled, and more will be added. For information about additional conversion classes, read the online Daily Bulletin regularly and watch for flyers to learn the exact dates and locations. UNICOS classes are scheduled to start in early June. Conversion Class I is a three-day class for people without UNIX experience. Class times will be 08:30 to 16:00 each day. Day Monday Tuesday Wednesday Monday Tuesday Wednesday Date January 29 January 30 January 31 February February February Mesa Lab location Damon Room Damon Room Damon Room Director's Conf. Room Director's Conf. Room Director's Conf. Room Conversion Class II is a one-and-one-half-day class for people who already have a working knowledge of UNIX. Class times will be 08:30 to 16:00 on the first day and 08:30 to 12:00 on the second day. Day Thursday Friday Thursday Friday Date February 1 February 2 February 15 February 16 Mesa Lab location Damon Room Damon Room Director's Conf. Room Director's Conf. Room Please register in advance by sending to scdinfo@ncar.ucar.edu or by calling the SCD Course Enrollment line, (303) Conversion classes If you are currently running codes under COS, this class will help you convert them. For people with no UNIX experience, the conversion class will run three days to cover both of the following parts and include lab exercises. For people who have a working knowledge of UNIX, the class will take one and one half days for the conversion part plus all lab exercises. Contents of UNIX part * basic UNIX philosophy * hierarchical storage * a dozen important commands (Is, rm, mail, cd, cat, man, and others) * vi editor (basic commands) * main issues in using the Bourne shell and the C shell 10

13 * basic script usage and structures (primarily for the C shell) * TCP/IP access Contents of conversion part * philosophical differences between COS and UNICOS * file protection and the use of the /usr/tmp directory * COS statements and corresponding UNICOS commands * conversion steps * I/O and memory usage considerations * graphics and libraries * Network Queuing System (NQS) and the charging structure under UNICOS * organizational tools such as make and fmgen * performance tools (ftref, prof, loopmark, ja, and others) Documentation The class will be based on the "Elementary UNIX" UserDoc and the "COS-to-UNICOS Conversion Guide" (both scheduled for completion in late January). UNICOS classes If you plan to compute at NCAR in the future, and if you are not currently running codes under COS, this class will help you use UNICOS. For people with no UNIX experience, the class will run three days to cover both of the following parts and include lab exercises. For people who have a working knowledge of UNIX, the class will take one day (consisting of the UNICOS part only), and there will be no lab exercises. I Contents of UNIX part * basic UNIX philosophy * hierarchical storage * a dozen important commands (Is, rm, mail, cd, cat, man, and others) * vi editor (basic commands) * main issues in using the Bourne shell and the C shell * basic script usage and structures (primarily for the C shell) * TCP/IP access * more advanced UNIX facilities (file redirection, pipes, background and foreground processing, and others) * make and other organizational tools Contents of UNICOS part * basic differences between UNIX and UNICOS * compilers and loader information * graphics and libraries * NQS and the charging structure under UNICOS * interactive debugging with cdbx (for optimized and unoptimized code) * performance tools (ftref, prof, loopmark, ja, and others) Documentation The class will be based on the "Elementary UNIX" UserDoc (scheduled for completion in late January) and the UNICOS Primer (scheduled for completion in the summer of 1990). Sally Haerer is the Consulting Group Head in the SCD User Services Section. 11

14

15 CHANGE OF ADDRESS FORM S[]Add to mailing list [ Delete from mailing list E Change existing entry Name: New address: User number Phone number Send to: User Information, Scientific Computing Division, NCAR, P.O. Box 3000, Boulder, CO Trademarks: CRAY, SSD, and UNICOS are registered trademarks, and CFT, CFT77, COS, and CRAY X-MP are trademarks of Cray Research, Inc. DEC and VAX are registered trademarks of Digital Equipment Corp. HYPERchannel is aregistered trademark of Network Systems Corp. IBM is a trademark of International Business Machines Corp. Macintosh is a trademark of Apple Computers, Inc. Microsoft is a registered trademark of Microsoft Corp.; PageMaker is a registered trademark of Aldus Corp.; PostScript is a registered trademark of Adobe Systems, Inc.; and UNIX is a trademark of Bell Laboratories. Reference to a company or product name does not imply approval or recommendation of that company or product to the exclusion of others.

16 SCD SERVICES DIRECTORY PHONE ' CONTACT (303) General Information SCD Consulting Office Consultant on Duty consultl SCD Visitor/User Information scdinfo SCD Course Enrollment scdinfo Graphics Software Purchase Information scdinfo Data Communications/Networking Maria Meehl maria Project & User Number Assignment Rosemary Mitchell rosemary Computing Resource Applications JoAn Knudson knudson SCD Computing News Editor Brian Bevirt brianb NCAR Switchboard Operations Information Computer Operations Bob Niffenegger niff Machine Room Oper. Supervisor opi Graphics Operations Andy Robertson /42 andy Tape Librarian Sue Jensen sue SCD UserDocs, Manuals/Output Mailing Mary Buck maryb SENDING ELECTRONIC MAIL TO NCAR STAFF: Using the address names listed in the column above, please consult the appropriate information given below based on the network you are using: " Internet address: (IP node ) Examples: SCD IBM 4381 (CMS): note consult1 at ncar.ucar.edu UNIX: mail " BITNET users: To send to NCAR staff, use the Internet address given above. Please consult your system administrator for the exact syntax. " SPAN address: (DECNET node 9580 or 9.364) " Tel OMNET address: (for the Internet address) For further information on , please see the UserDoc, "Using the NCAR System." SCD COMPUTING NEWS Scientific Computing Division National Center for Atmospheric Research P. 0. Box 3000, Boulder, CO NonPfitOrgnizion U.S POSTAGE PAID Boulder / Colorado Permit No. 5% Karon Kelly DIR Mesa Lab NCAR MAIL ROOM