P~OTENTIA\L VORTICITY

T 40.0 DAYS

INSIDE

" COLOR DICOMEDNOW IN ACTION

" COMMHTEE RE-LEASES ADVICE ONDOCUMENTATION

" MIMPORT/MEXPORTFACILHTY AVAILABLE

" USAN NEIWORKEXPANDS

" TRACKING DOWNRUN-TIME ERRORS

1SCIENTIFIC COMPUTING DIVISIONNATIONAL CENTER FOR ATMOSPHERIC RESEARCHA:ff sr_lwj Lo F -]

About the cover

POTENTIAL VORTICITY

T = 40.0 DAYS

The cover graphic was produced by Murry Salby and PatCallahan of the University of Colorado in collaboration withRolando Garcia of the Atmospheric Chemistry Division. It ispart of a study of the redistribution of trace constituents byplanetary wave motions in the stratosphere.

The graphic illustrates potential vorticity behavior in a high-resolution, equivalent barotropic simulation of stratosphericair motions forced by a 1000-meter deflection of the lowerboundary. The initial state is zonally symmetric, with amidlatitude westerly jet and a critical line at 10 degreesNorth. After 40 days, the stratospheric vortex has beendisplaced off the pole, and there is extensive mixing of air inthe subtropics. The solid line with superimposed dotsrepresents a material locus, originally coincident with thecritical latitude; stippling denotes air initially located equa-torward of the critical latitude. Under the adiabatic, nearlyinviscid conditions of the simulation, potential vorticity is atracer for stratospheric air motions.

This graphic was generated using the DICOMED graphicsrecorder. The hardcopy of the graphic was produced on aQMS PS-800+ laser printer.

3 Documentation Advisory Committee releases reportResults of user survey, recommendations given

5 New policy for using half-inch magnetic tapesMagnetic tapes being phased out

6 Friendly user period opens for color slide outputProducing 35-mm slides in color

7 Correction to "Transferring binary metafiles to VAX/VMSsystems"

Missing parameter in mfc command

8 MIMPORT/MEXPORT facility ready for general useImporting and exporting data between magnetic media and the MSS

2 SC irector's Column

11 Systems NewsDynamic sharing of SSD resources implemented * CFT77 compiler changesscheduled * CMS Release 4 now on IBM 4381

12 MSS NewsOld method of sending MSS purge notices discontinued

12 Networking and Data Communications NewsUSAN expands to eight sites * NSFNET update: Measuring the size of theInternet * Telenet WATS numbers changed * Sending and receiving mail andfiles over the Internet and BITNET from the NCAR IBM 4381 (10) computer* Central post office computer now handling Telemail and Omnet mail

18 Graphics News

Metafile manipulation utilities now support CGM

19 Hints from the SCD ConsultantsTracking down run-time errors

23 DocumentationUpdated documentation available from IBMDocumentation available from SCD: * Acronyms document * Metafile utilitiesdocument * Transferring binary metafiles to VAX/VMS * MEXPORT/MIMPORT* MIGS user's guide * SUDOOS documentation * Cray JCL * Locally developedutilities

24 News from SCDUGComputing at the Research Aviation Facility * Documentation Advisory Com-mittee

27 Acronyms and Terms

28 Computer Resources Allocated

30 Index

DECEMBER 1988

I I - I la ~e Ir I , I - - I I r I

by Bill Buzbee

We are pleased that SCD's new color film outputoption is ready for friendly users (see "Friendlyuser period open for color output"). This systemhas its genesis in a recommendation from theComputer Output Committee about 12 months ago.The system includes a high-resolution color filmrecorder, color film processing equipment, a Sun-4controller, and new software. We are especiallypleased that this system handles Graphical KernelSystem graphics metacode. Initial service will belimited to 35-mm plots and slides, with additionalcapability being added over the next three to fourmonths. Remember that "friendly usage" meansthe system is not yet robust, and testing willcontinue during this initial phase. My personalthanks to all who are helping bring this system tofruition; we look forward to some spectacularoutput!!

The SCD Documentation Advisory Committeeconcluded that, compared with that of othercenters, SCD documentation is about "average"(see "Documentation Advisory Committee releasesreport"). Actually, it was only within the last yearthat our documentation was upgraded to "average,"thanks to a lot of work by our DocumentationGroup. It is paradoxical that computer documenta-tion is so often neglected. User productivity ispaced by the ease with which users can obtainaccurate and up-to-date information. Part of theproblem lies in the difficulty of structuring andmaintaining good documentation, especially forhigh-tech gadgetry such as computers. We muchappreciate the thorough analysis and recommenda-tions provided by this committee. They arealready influencing SCD.

Please note "New policy for using half-inchmagnetic tapes." This policy reflects our need tomaximize efficiency in operations and in space

utilization. Also, note "MIMPORT/MEXPORTfacility ready for general use." Those of you whouse the Cray-1A for staging tapes to the MassStorage System are urged to switch to MIMPORT/MEXPORT. The Cray-1A will probably be de-commissioned in 1989, which could come on shortnotice. Further, we are developing MIMPORT/MEXPORT to accommodate a large range ofmedia.

The installation of the COS 1.16 operating systemis paying handsome dividends. It has high effi-ciency (delivers more cycles per unit time to usercode), it has greatly reduced the number of jobslost across system interrupts, and it offers somenew capability in managing the Cray Solid-stateStorage Device (see "Systems implements dynamicsharing of SSD resources"). Thanks to all whohelped install COS 1.16!

Ct .

's ^. ^ ^L~ ^. ^.^ ^ ^. ^^

DECEMBER 1988

F06

Documentation Advisory Committeereleases report

by Linda Bath and Mary Downton

The Documentation Advisory Committee (DAC) wasformed in February of 1988 to help provide user inputto documentation plans and to aid SCD in respondingto concerns of the SCD Advisory Panel. The SCDAdvisory Panel's concerns centered on the lack of acomprehensive plan for online documentation and thelarge amount of documentation that SCD planned toproduce. We reported on Committee findings at theOctober 24th SCDUG meeting. (Editor's Note: TheCommittee's final report and recommendations havebeen published as NCAR Technical Note NCAR/TN-323+STR (October 1988), 74 pages, available fromLaura Morreale. Her e-mail address islaura2@ncar.ucar.edu on the Internet. Her telephonenumber is (303) 497-1288.)

The DAC consisted of six NCAR staff members, fiveUniversity members and three advisory members fromSCD. It was split into three subcommittees, one tosurvey users concerning their experience with docu-mentation, one to review the current document collec-tion, and one to look into online documentation sys-tems. Committee members worked many hours in re-searching these questions.

Committee members Mary Downton (CGD) andRobin Vaughan (MMM/ATD) designed and distrib-uted a questionnaire on SCD documentation. High-lights of the survey responses appear later in thisarticle.

Local committee members Chris Burghart (ATD) andLinda Bath (CGD), with university members JohnMerrill (University of Rhode Island), Martin Corrigan(Iowa State University), and Kelvin Droegemeier(University of Oklahoma), performed a detailed reviewand evaluation of the existing documents. Responsesfrom the user survey, interviews with other users, andcomments from participants of the August 1988 SiteLiaison Workshop provided input to this evaluation.The subcommittee also studied the use of vendordocuments at NCAR, the current documentation style,online vs. written formats, and document distribution.They presented a priority list for document upgrades,and recommended that SCD continue to provide

overlap with vendor documents and to provide morequick reference guides to various aspects of thecomputing system, including the NCAR Graphicspackage.

Members of the online documentation subcommitteewere Pat Waukau (MMM), Linda Bath (CGD),Ginger Caldwell (SCD), Barb Homer-Miller (SCD),Vic Tisone (HAO), Kevin Ingels (Florida StateUniversity), and David Chapman (Woods HoleOceanographic Institution). This subcommitteeperformed a market survey of existing online docu-mentation systems, details of which are included inthe committee's final report. This software market isjust beginning to explode, with new systems appearing

Documentation Advisory Committee members from NCAR,shown left to right, were Chris Burghart (ATD), Linda Bath(CGD, chairperson), Robin Vaughan (MMM/ATD), PatWaukau (MMM), and Mary Downton (CGD). Not shown isVic Tisone (HAO). Other committee members were DavidChapman (Woods Hole Oceanographic Institution), MartinCorrigan (Iowa State University), Kelvin Droegemeier (Univer-sity of Oklahoma), Kevin Ingels (Florida State University), andJohn Merrill (University of Rhode Island).

continued on next page

DECEMBER 1988 3

continued from previous page

frequently. The subcommittee also explored thecomplex connectivity problems associated with provid-ing this type of system in the NCAR environment, andthe possible configuration options that might supplythe needed functionality. The subcommittee's recom-mendations include a phased implementation, and apriority list for documents to add to an online textbase.A comprehensive online system would be costly, andshould not be attempted at the expense of the writtendocumentation effort, the committee felt.

Users gave high priority toupdating documentation ofthe NCAR Cray computers,the Mass Storage System,and the NCAR Graphicspackage.Documentation Advisory Committee meetings havebeen lively and interesting, and we also learned a lot.We appreciate the opportunity to provide input to thisvery important User Services function.

Users give opinions on documentation

"SCD documentation is about average for computerdocumentation, that is, just awful. In addition, muchof it is out-of-date. The problem with 'documenta-tion' is conceptual - experts use 'documents'; whatusers need are clear, concise 'instructions."'

Users of SCD computers had a chance to give frankopinions such as the one above in a survey of SCDdocumentation needs last July. Mail-in questionnaireswere distributed to a random sample of 190 non-SCDpeople who had used the NCAR Cray computersduring the period from October 1, 1987, to May 31,1988. Questionnaires were returned by 131 people,giving an excellent 69% response rate.

Users gave high priority to updating documentationof the NCAR Cray computers and the Mass StorageSystem and to improving documentation of the NCARGraphics package. Users also asked for comprehen-sive new documents on networking, communications,and electronic mail.

Several common themes emerged in open-endedcomments. Users want lots of examples - "The moreexamples the better." They asked for regular updatingand for indexes in major documents. Many peoplerequested a catalog of SCD publications. (A UserDocumentation Catalog is now available and wasdistributed in the September issue of SCD ComputingNews.)

Many users requested quick reference guides forfrequently used commands. (A reference guide to theCray computers is planned to partially meet that need.)New and occasional users may also find The Primerhelpful as an introductory reference on the mostcommonly used SCD facilities.

Respondents reserved their strongest criticism forvendor documentation, urging SCD to continueproviding documentation that overlaps with thatprovided by Cray and IBM. A typical comment was,"Cray and IBM manuals are always written in 'messyto read' form, but SCD manuals are usually easy tounderstand and more localized to the environment weuse."

Online documentation was considered important by89% of the university users and 73% of the NCARusers. Most people asked for online help files, somespecifically requesting online help for Cray, MassStorage System, and NCAR Graphics commands.They did not ask for a complex online system withsophisticated search capabilities, perhaps because fewhave had the opportunity to try such a system. Theneed for searching mechanisms was expressed indi-rectly by the comment, "The problem with onlinedocumentation is if you don't know what you want,it's tough to find out."

Our thanks to the many computer users who re-sponded to the questionnaire. The SCD Documenta-tion Group now has a wealth of information on whichto base their documentation planning.

Linda Bath, a programmer in the CCM Core Group withinthe Climate and Global Dynamics Division (CGD), chairedthe Documentation Advisory Committee. Mary Downton,who also served on the committee, is an associate scientistin the Environmental and Societal Impacts Group withinCGD.

New policy for using half-inch magnetic tapes

by Bob Niffenegger

NCAR's Scientific Computing Division (SCD) plansto discontinue long-term storage of "round" tapes (1/2-inch magnetic tape on 10-1/2-inch reels). This affectsall user-owned and SCD-owned tapes at NCAR. SCDwill continue to accept data from round tapes, but afterJanuary 1, 1989, you must transfer the data from anyincoming tapes to our Mass Storage System (MSS)within 30 days. Users with tapes currently beingstored by SCD will have until January 1, 1990 totransfer their data to the MSS.

Procedures for users currently storing tapesin SCD

If you currently store data on round tapes that areowned either by you or by SCD, please transfer yourdata to the MSS as soon as possible. After youtransfer all the data from your tapes, contact SueJensen (formerly Sue Long), SCD Tape Librarian, at(303) 497-1245 or send e-mail to sue@ncar.ucar.edu.She will remove your tapes from storage and returnthem to you via the postal service or interoffice mail.We encourage you to pick up your tapes in personwhen possible, from Mesa Lab Room 5. After youtransfer all your data from SCD-owned tapes, notifySue and she will recycle the tapes.

Procedures for users submitting new tapesand cartridges to SCD

We assign a visitor number to each round tape orsquare cartridge that is owned by a user so the datacan be accessed from the computers in SCD. Thefollowing instructions explain the procedures for sub-mitting round tapes or square cartridges to the SCDcomputing center. If the following procedures areimpractical for any reason, please contact Sue to makespecial arrangements.

For users at NCAR

Take your tapes or cartridges to Sue Jensen in MesaLab Room 5; she will assign a visitor number foreach. In the evenings and on weekends, the operatorscan assign and release visitor numbers, but you arerequested to enter and retrieve your tapes and car-tridges during normal working hours when possible.

Please make note of your visitor numbers; if you losea number, call Sue.

For off-site users

Send your tapes or cartridges to:

Sue Jensen, Tape LibrarianNCAR/SCD1850 Table Mesa DriveBoulder, CO 80303-3000

Include a note indicating that you need visitor num-bers, then provide your name, your user number, yourproject number, and either your e-mail address or yourphone number. Sue will contact you with the numbersthat have been assigned.

Exporting data on round tapes

Users may also purchase from SCD or supply theirown round tapes to copy data from the MSS fortransfer to other institutions. These tapes may residein the SCD computer area for up to 30 days. If youhave special requirements, please contact Sue.

Cartridges require less floor space for data storage andimprove turnaround time for data retrieval. Pictured is NancyWaldron, Operations and Maintenance, next to part of SCD'sMass Storage System.

continued on next page

DECEMBEK 1988

continued from previous page

Moving data from tape to the MSS

The present method for moving data from a roundtape to the MSS requires you to run a Cray job inwhich you ACQUIRE the data from the tape to theCRAY-1A computer, then DISPOSE the data to theMSS. SCD has developed a new software facility for

After January 1, 1989, youmust transfer the data fromany incoming tapes to ourMass Storage System (MSS)within 30 days.

reading and writing round tapes and square cartridgesthat does not require you to pass your data through theCRAY-1A computer. This facility is called MIM-PORT/MEXPORT and it has just been released. Allcapabilities that existed as part of the CRAY-1A tapefacility will be preserved or expanded in the MIM-PORT/MEXPORT facility.

The MIMPORT/MEXPORT utilities transfer datadirectly between the physical media and the MSS.

Users issue a single command through either of theCray computers to transfer their data. (See examplesin "MIMPORT/MEXPORT facility ready for generaluse" in this issue.)

Currently, MIMPORT/MEXPORT software is imple-mented only from the Cray Operating System. In thefuture, MIMPORT/MEXPORT will also be imple-mented from the CMS and UNIX operating systemsand will be available through most of the nodes on theMainframe and Server Network (MASnet). MIM-PORT and MEXPORT will also be available throughthe MASnet/Intemet Gateway Server (MIGS). Wedesigned the MIMPORT/ MEXPORT user interfacecommands for ease of use, keeping the commandsyntax as consistent as possible across the implemen-tations on the various computer systems.

SCD designed the MIMPORT/MEXPORT facility tohandle a variety of media as data storage technologiesevolve and user needs change. Currently, MIMPORT/MEXPORT supports round tapes and IBM-format3480 cartridges. We will support the new EXAbytehigh-capacity cartridge system soon.

Bob Niffenegger is the manager of the Computer OperationsSection in SCD.

Friendly user period opens for color slide output

by Nancy Dawson

Have your colleagues recently been dazzling you withcolor slides of their work? Now you, too, can beginproducing 35-mm color film for slides, using the newequipment available in SCD. The "friendly user"period is now in progress.

Color output is produced by SCD via the newlyimplemented Sun/UNIX DICOMED Online OperatingSystem (SUDOOS). Only the 35-mm color film forslides option is available at this time. The capability ofproducing color movies is scheduled to becomeavailable in February or March. (Watch the DailyBulletin and future issues of the SCD Computing Newsfor announcements.)

SUDOOS uses the SCD Fortran Computer GraphicsMetafile (CGM) translator to process metafiles thatwere produced with the Graphical Kernel System(GKS) version of NCAR Graphics. SUDOOS does notaccept pre-CGM NCAR metafiles. (The existingblack-and-white cameras continue to accept pre-CGMmetafiles only; they will not accept NCAR CGMmetafiles.)

What to expect during friendly use

During the friendly user period, there will be timeswhen SUDOOS is taken out of production while newfeatures are tested or bugs are fixed. During suchperiods, queued jobs will be held until SUDOOS

returns to production mode. There may be occasionallost jobs or poor quality output as we continue toimplement SUDOOS, and there may be some changesto the software. Watch the Daily Bulletin for announce-ments of new SUDOOS parameters and new function-alities.

Color film will be processed three times a day onweekdays and mailed to university sites once eachweekday. Black-and-white film production and ship-ping will not be affected by the work on SUDOOS.

SUDOOS documentation

For detailed information on using SUDOOS from theCray computers, order the SCD UserDoc, "User'sGuide to Producing Color Output from the CrayComputers," which is available in draft form. A draftversion of the "Preliminary Sun/UNIX DICOMEDOnline Operating System Reference Manual" is alsoavailable. However, it is hoped that 80% - 90% ofusers will only need the User's Guide.

NCAR metafiles can also be submitted to SUDOOSfrom other systems, although the documentationfor other systems is not yet available. These new

documents will be announced in the Daily Bulletin asthey are written. The SUDOOS Reference Manual alsocontains information on preparing and submitting jobsfrom other systems.

You can order SCD documentation from Mary Buck.Her e-mail addresses are maryb@ncar.ucar.edu on theInternet and MARYB on the IBM 4381 (IO) front-endcomputer, and her telephone number is (303) 497-1232. If you are at the Mesa Lab, you can also obtainSCD documentation from the SCD Consulting Office,Room 17.

What to do if you have problems

If you encounter problems in using SUDOOS that arenot caused by the system being temporarily out ofproduction mode, please contact the SCD consultantsby sending e-mail to consultl@ncar.ucar.edu on theInternet or CONSULT1 on the IBM 4381 (IO) front-end computer. You can also call the consultants at(303) 497-1278 or drop by Room 17 of the Mesa Lab.

Nancy Dawson is a writer/editor in the DocumentationGroup within SCD.

Correction to 'Transferring binary metafiles to VAX/VMSsystems"

In the November 1988 issue of SCD Computing News,the article, "Transferring binary metafiles to VAX/VMS systems," please note the following correction:

The mfc command is missing a parameter. Thecommand should read:

mfc -d -r -f -m -i inlen -o outlen filename.filetype

where -m was left out in the original document. Thedefinition for the -m parameter is:

Create Relative file organization from a Sequentiallyorganized file.

When metafiles are created on a VAX they are alreadyin Relative organization. However, when a metafile istransferred to a VAX it is in Sequential organization.Many VAX translators require Relative organization.

DIECEMBER 1988

SOFTWARE N E WS

MIMPORT/MEXPORT facility ready for general useby Ken Hansen

The MIMPORT/MEXPORT facility that was an-nounced for "friendly user" testing in the Novemberissue has been released for general use on the CRAY-1A (CRAY,C1) and CRAY X-MP/48 (CRAY,CX)computers. It will become the primary method forstaging 9-track, 1/2-inch magnetic tapes to and fromthe Mass Storage System (MSS) when the CRAY,C1is disconnected. We strongly encourage you tobecome familiar with this facility before the CRAY,C1

MIMPORT/MEXPORT willbecome the primary methodfor staging 1/2-inch magnetictape to and from the MSS.

is phased out. The UserDoc "MEXPORT and MIM-PORT: Transferring Data Between the Mass StorageSystem and Tape" is available in draft form. (Order-ing instructions are given at the end of this article.)

These utilities provide a simple user interface toprocesses that execute on the Mass Storage ControlProcessor (MSCP). The import or export of data isinitiated from the Cray Operating System (COS), butthe actual data transfer is controlled by the MSCP andoccurs directly between the physical storage mediaand the MSS - no datasets on the Cray disks areinvolved. Once the transfer is complete, a statuscompletion file is returned to the computer of joborigin and not to the log file of the Cray job thatinitiated the request.

Volume serial numbers and tape lists

All tapes to be read or written must have a volumeserial number. Call the SCD Tape Librarian, SueJensen, at (303) 497-1245 to obtain these assignments.The article "New policy for using half-inch magnetictapes" in this issue of the newsletter contains detailedinstructions for submitting new tapes to SCD.

If you wish to read or write more than one tape in asingle job session or within a 24-hour period, you

must give a tape list to the computer operators onceeach day at least five minutes prior to submitting yourjob. A tape list should include the following informa-tion: your login name used on the computer of joborigin and the volume serial number of each tape thatis to be mounted. This list allows the computeroperators to pull all of the necessary tapes at one time.You may send e-mail to opl@ncar.ucar.edu on theInternet, call (303) 497-1200, or use the TAPELISTexec on the IBM 4381 (IO) front-end computer.(Type HELP TAPELIST for information on this exec.)

Functional differences from the CRAY,C l'stape facility

Although they are accessible from COS throughsimple Job Control Language-level commands (JCL),these utilities were designed to transfer data directlybetween various storage media and the MSS. There-fore, they should not be thought of as functionallyequivalent to the use of the ACQUIRE and DISPOSEcommands with the CRAY,C1's tape facility.

When importing data using the CRAY,C1 's tapefacility, an ACQUIRE is issued from COS to obtaindata from the tape; control is not returned to the useruntil the dataset has been staged to the Cray disks andthe job has been given local access to the dataset. Bycomparison, when the MIMPORT command is issuedfrom COS, the request is passed to the MSCP, controlis immediately returned to the job, and processingcontinues at the next control statement. With MIM-PORT, the dataset is read directly from the specifieddevice (magnetic tape) to the MSS. It is not staged tothe Cray disks. You cannot issue an MIMPORTcommand and expect to use the referenced dataset in thesame job submission, because there is no guaranteethat the import will finish before the ACQUIRE is issued.

The MEXPORT process is also different fromCRAY,CI's tape facility. Using the CRAY,C1'sfacility, the desired file is DISPOSEd from theCRAY,C1 disks to tape. With MEXPORT, the task isissued from either Cray computer, and the data aretransferred to tape directly from the MSS, not from theCray disks. Unlike the import process, you may

DECEMBER 1988

SOFTWARE

transfer data from the Cray disks to the MSS (using aDISPOSE statement) and then to tape (using anMEXPORT statement) in one job submission, provid-ing you use the WAIT parameter on your DISPOSEstatement to the MSS. The WAIT parameter suspendsfurther job processing until the DISPOSE has beencompleted.

As mentioned in the November SCD Computing News,all capabilities of the CRAY,C1 tape facility will bepreserved or expanded in the new MIMPORT/MEX-PORT facility. New blocking options have also beenadded, making it easier to port tapes between othersystems. MIMPORT/ MEXPORT does not restrict thelogical record length to a multiple of eight bytes.Note: Not all options for importing and exportingCray transparent datasets are operational. If youneed to import or export Cray transparent datasets,contact the Consulting Office for the current status ofthese options.

Command format

The user interface commands were designed for easyuse and to closely resemble the format used by theCOS versions of MSINFO, MSCHANG, and othercommands. (For more information on the syntax rulesof MSS utilities, see the UserDoc "Mass Storage FileMaintenance from the Cray Computers." Ordering

All capabilities of theCRAY,C1 tape facility havebeen preserved or expandedunder MIMPORT/MEXPORT.

information is given at the end of this article.) Youspecify the verb, follow it with an open parenthesisand any required and optional parameters, and termi-nate it with a close parenthesis. Blanks delimit thekeywords. The MSS file reference name (NAME) andthe volume serial number (VSN) of the device mediaare required parameters. File positioning and mediacharacteristics such as blocking, density, and formatare specified in an easy, keyword form.

NEWS

Examples

This section illustrates the use of the MIMPORT/MEXPORT facility. Examples are provided for (1)importing an unblocked ASCII file, (2) importing ablocked EBCDIC character file, (3) exporting ablocked EBCDIC character file, (4) importing a binaryfile with undefined record lengths, and (5) exporting abinary file with variable record lengths. The first twoexamples provide functionally equivalent statementsfor the CRAY,C1 tape facility for comparison withMIMPORT/MEXPORT. Please note that the follow-ing JCL is syntactically correct, but it is shown withmore continuations than would normally be needed.

Importing an unblocked ASCII file

The following is a simple example of the MIMPORTcommand. It reads two files from 1/2-inch tape, withvolume number "V09899," in ASCII character format(default), at 1600 bits per inch (bpi), into the MSS filenamed "/JONES3/Models/G CM."

MIMPORT(NAME=/JONES3/Models/GCM A

DEVICE=MT VSN=V09899 DEN=1600 FILES=2)

Note: The caret ( A) is the Cray continuation charac-ter. The command could be typed on a single line.The blank preceding the caret is a parameter delimiter.

The COS statements needed to accomplish the equiva-lent function via the CRAY,C1 tape facility would bean ACQUIRE and DISPOSE as follows:

ACQUIRE,DN=LOCAL,MF=MT,DF=CB,^PDN=V09899,ID=SCOTT,TEXT='DEN= 1600'.DISPOSE,DN=LOCAL,MF=MS,^TEXT='FLNM="/JONES3/Models/GCM"'".

Importing a blocked EBCDIC character file

The next example uses MIMPORT to read a blockeddataset, deblock it, convert it to ASCII, and write it tothe MSS. The dataset in this example contains logicalrecords of 20 bytes, physical records (blocks) of 8000bytes, and data written in the EBCDIC character set.

continued on next oape

DECEMBER 1988

I r, I I I I ' I I I '

I I - I I - '

SOFTWARE NEWScontinued from previous page

cotinedfrom previous page

MIMPORT(NAME=/JONES 3/DATA/^ASIA/V08989 VSN=V08989 DEVICE=MT A

FORMAT=CH,EBCDIC DEN=6250 ^

RECFM=FB BLKSIZE=8000 LRECL=20)

By contrast, the old tape software on CRAY,C1 wouldrequire a two-step process because of the restrictionthat logical record lengths must be a multiple of eightbytes. The first step is to ACQUIRE the dataset fromthe tape and stage it to the CRAY,C1 disks. Duringthis step it is converted from EBCDIC to ASCII. Todeblock it, each blocked record must be read with auser-supplied program, reformatted into the correctlength (20 bytes), and rewritten. Finally, the usermust DISPOSE the deblocked dataset to the MSS.

ACQUIRE,DN=LOCIN,MF=MT,DF=CB,^PDN=V08989,ID=WDB,TEXT='DEN=6250, '̂

'BLKSIZE=8000,TRANS=EBCDIC'.CFT. compile the user program to read the* blocked file from LOCIN and write* the deblocked file to LOCOUTSEGLDR.$ABD.DISPOSE,DN=LOCOUT,MF=MS,TEXT= ^

'FLNM="/JONES3/DATA/AS IA/V08989'".

Exporting a blocked EBCDIC character file

The reverse of the previous example would be to readthe MSS file named '/JONES3/DATA/ASIA/V08989',and write it in 8000-byte blocks in the EBCDICcharacter set.

MEXPORT(NAME=/JONES 3/DATA/A S IA^

/V08989 VSN=V08989 DEVICE=MT ^

FORMAT=CH,EBCDIC DEN=6250 ^

RECFM=FB BLKSIZE=8000 LRECL=20)

Importing a binary file with undefined record lengths

The next example demonstrates how to read a binarytape of undefined record lengths (RECFM=U). Eachphysical record (block) on the tape will read as asingle logical record. The length of each record mayvary from record to record. The record formatRECFM=U is the one you would probably select forreading a tape with unknown factors of format, record

length, or blocking. It is also useful for reading tapesthat were generated on another type of computer in abinary format that may have variable record sizes.The length of the tape block (BLKSIZE) does notneed to be specified if the largest block is less than orequal to 32,760 bytes. If the length of any blockexceeds 32,760 bytes, you must specify the block size,or the MIMPORT facility will truncate the remainderof the block.

MIMPORT(NAME=/JONES3/DATA/^BINARY/V08987 VSN=V08987 A

DEVICE=MT FORMAT=BI ^DEN=6250 RECFM=U)

Exporting a binary file with variable record lengths

To export a binary file with differing record lengths,you follow the next example. If any of the records inthis file are less than 18 bytes, the export process willterminate and send an error message to the statuscompletion file. The exporting of binary recordslarger than 32,760 bytes is not currently implementedbut will be in the near future. Please watch the DailyBulletin for the implementation announcement.

MEXPORT(NAME=/JONES 3/DATAA/BINARY/V08987 VSN=V08987 ^

DEVICE=MT FORMAT=BI ^DEN=6250 RECFM=U)

Obtaining help and documentation

If you have questions or problems using MIMPORT/MEXPORT, contact the SCD Consulting Office atconsultl@ncar.ucar.edu on the Internet (IP address128.117.64.4) or CONSULT1 on the IBM 4381 (IO)front-end computer. You can order SCD documenta-tion from Mary Buck. Her e-mail address ismaryb@ncar.ucar.edu on the Internet or MARYB onthe IBM 4381 (IO) computer. Her telephone numberis (303) 497-1232.

Ken Hansen is a consultant in the User Services Sectionwithin SCD.

DECEMBER 1988

I I I r I I I I I

10

Dynamic sharing of SSDresources implemented

by Susan Smith

The Solid-state Storage Device (SSD) at NCARprovides 268 million words (256 megawords) ofstorage that are attached by two, ultra-high-speedchannels to the 8-megaword central memory of theCRAY X-MP/48 (CRAY,CX). With the advent ofthe Cray Operating System (COS) Version 1.16,SCD's Cray Systems Group was able to implementa new interaction capability between theCRAY,CX and the SSD called the Fast SecondaryStorage (FSS) Preemption. This feature has athreefold advantage:

1. It allows for the SSD to be divided intomultiple partitions. Since COS 1.16 wasimplemented, the SSD has been divided intotwo partitions, one partition (68 million words)servicing the memory swapping (job imageroll) that used to occur between the centralmemory and the DD-49 disk drives, and theother partition (200 million words) servicinguser requests as usual. Functioning as a high-speed storage device to the CRAY,CX centralmemory, the SSD transfers information at arate of 1250 megabytes per second over eachof two channels. This speed represents asignificant increase over the job image roll-over rate of 10 megabytes per second betweenthe CRAY,CX central memory and the con-troller for the DD-49 disk drives.

2. It allows the operating system to oversubscribethe SSD even if there is not enough of theSSD available to meet the requirements of allof the jobs currently in execution. GeneSchumacher, head of the Cray Systems Group,explains, "Jobs can share access to the SSD ina round-robin, priority-driven fashion, muchthe same as central memory is shared amongall active jobs, but over a much longer roll

cycle. This dynamic sharing will more fairlydistribute the SSD resource."

3. It provides a method for the Operations staff tosweep (free up) a specified area of the SSD byswapping jobs that are occupying that area tothe DD-49 drives, thereby freeing enoughroom for incoming MP2 (mono program) jobs.Operators can later reactivate jobs that weresuspended when they were swept from theSSD. Prior to the FSS Preemption feature, ifthere was not enough SSD space for incomingMP2 jobs, those jobs were required to waituntil lower priority jobs completed their use ofthe SSD resources; oftentimes, MP2 jobexecutions were delayed an hour or more.

Gene, in collaboration with the other members ofhis group, Barb Bateman and Sandra Walker,implemented the job image roll capability in earlyAugust. They then implemented the dynamicsharing and sweeping capabilities on October 24,after deeming COS 1.16 to be stable in all otherareas. "We had a few rough spots," Gene said,"but they were largely a matter of learning how touse the FSS feature effectively, and the problemswere quickly worked out. It has been runningsmoothly ever since then."

Susan Smith is a writer/editor in the DocumentationGroup within SCD.

CFT77 compiler changesscheduled

On December 14, 1988, the default Cray Fortrancompilers CFT and CFT77 on the CRAYX-MP/48 are scheduled to change. CFT willchange to a different bug-fix level that appears tofix many of the problems encountered in thecurrent default. CFT77 will change from Release2 (Bug Fix 2) to Release 3 (Bug Fix 3). The newcompilers are currently available by inserting theappropriate ACCESS statement into your JobControl Language (JCL) prior to the Fortran com-pilation, for example:

ACCESS, DN=CFT,ID=V 115BF3.CFT.

continued on next page

DECEMBER 1988 11

continued from previous pageor

ACCESS, DN=CFT77, ID=C7730.CFT77.

If you encounter problems with these compilerversions, please contact the SCD Consulting Officeby sending e-mail to consultl@ncar.ucar.edu onthe Intemet or CONSULT1 on the IBM 4381 (IO)front-end computer. You can also call the consult-ants at (303) 497-1278 or drop by their office,Room 17 of the Mesa Lab.

CMS Release 4 now on IBM4381

Release 4 of the CMS operating system hasbecome the default on the IBM 4381 (IO) front-end computer. A few of the new features of therelease include faster file searching; faster AC-CESS, FILEDEF, RELEASE, SET, and TAPEcommands; and new options for existing com-mands. The XEDIT editor now features an SI(structured indent) command to make it easier toadd indented text.

For a summary of the new features, you can typeHELP CMSREL4. An extensive list of changes inRelease 4 is given in the Release 4 Guide and theCMS manuals for Release 4. See the Documenta-tion department of this newsletter for informationon ordering IBM manuals. If you have anyquestions about Release 4 of CMS, please callPhylecia Brandley at (303) 497-1271.

Old method of sending MSSpurge notices discontinued

by Susan Smith

The following is an excerpt from the Mass StorageSystem (MSS) test purge notice that was sent tousers on November 1, 1988:

This is a test letter being sent to ALL users ofNCAR's Computing Facilities. This letter isbeing sent to a person named "last, first." Weshow you as having an SCD-assigned loginname of userid, with an electronic mailingaddress of "user@host.domain."

The last, first names, userids, and e-mail ad-dresses (user@host.domain) were personalized foreach user.

The old method of sending purge notices wasdiscontinued on November 14. The NCAR centralpost office computer is now using the informationcontained in its user alias database to route allMSS purge notices. If you did not receive a testmessage by November 7, or if you received it on acomputer other than the desired one, you need touse the alias database query/change software -now - to ensure that you receive future MSSpurge notices at your desired e-mail address.

The October issue of SCD Computing News andthe first class mailing contain instructions for usingthe query/change software. Contact ConsultingOffice personnel at (303) 497-1278 if you did notreceive your test message, if you do not receive aconfirmation message (via e-mail) one to two daysafter making a change to your entry in the query/change software, or if you have questions regard-ing the query/change software, purge notices, or e-mail in general.

Susan Smith is a writer/editor in the DocumentationGroup within SCD.

Note: We apologize to those of you who huntedthrough the November issue for the "Noticeprocedure for MSS purges will change November14" article - it was inadvertently omitted.

USAN expands to eight sites

by Joe Choy

The University Satellite Network (USAN) firstbecame operational in February 1986 and has nowexpanded to eight remote stations with NCAR asthe hub station of a star configuration.

The Naval Research Laboratory in Washington,D.C., and the Institute for Naval Oceanography inBay St. Louis, Mississippi, became operational inthe past year. The participating institutions infiscal year 1988 (FY88; through September 30,1988) were:

DECEMBER 1988

I '"

12

Institute for Naval OceanographyUniversity of MarylandUniversity of MiamiUniversity of MichiganNational Center for Atmospheric ResearchNaval Research LaboratoryOregon State UniversityUniversity of WisconsinWoods Hole Oceanographic Institution

The radio for the satellite station located at theNCAR hub was upgraded from a 2-watt to a4-watt model, as was called for in the originaldesign for the network. The immediate improve-ment was a 4-decibel gain in the signal-to-noisemargin. This has increased the quality of datareceived from weak sites in the footprint of theSBS-4 satellite used by USAN. New modulatorsand demodulators were installed at all sites, nowpermitting the power level adjustments to be elec-tronically controlled instead of manually adjusted.

Other developments from the USAN Project overthe past year include improved stability of the

TCP/IP KNET software from the Spartacus com-munications package for the IBM 4381 (IO) front-end computer, development of the Internet RemoteJob Entry (IRJE) facility, and introduction ofdynamic network routing for USAN. The accom-panying diagram shows wide area network connec-tions at NCAR, including USAN sites.

The member institutions of USAN are now a stepaway from being operationally self-supportive forthe hardware and software maintenance of USAN,as well as for the satellite transponder segments.The University of Miami, NCAR, Oregon StateUniversity, and the University of Wisconsin willfund 50% of their operational costs, while theNational Science Foundation (NSF) will fund theother 50% in FY89. The other USAN memberinstitutions contribute 100% of their operationalcosts. In FY90, all member institutions willsupport the full operational cost for their site.

On the international networking scene, the USANProject was requested by NASA and NSF toestablish a network link to Mexico. USAN thus

continued on next page

Wide Area Network Connections at NCAR

0 Regional Network

4 Regional Network plus Supercomputing Center

A Supercomputing Center

* USAN Node only

DECEMBER 1988

---

13

continued from previous page

plans to establish a satellite network link to theUniversidad Nacional Autonoma de Mexico andthe Instituto Technologico y de Estudios Superi-ores Monterrey in early 1989, using the sameUSAN technology.

If you are interested in becoming a part of USAN,please contact Joseph Choy. The e-mail address ischoy@ncar.ucar.edu on the Internet. You canphone (303) 497-1222.

Joe Choy manages the Distributed Computing Sectionwithin SCD.

NSFNET update: Measuring thesize of the Internet

Editor's Note: We thank the NSF Network ServiceCenter for permission to reprint the followingarticle from the October issue of NSF NetworkNews.

The Internet is the collection of interconnected IPnetworks of which NSFNET is a major part.People are often curious about how big the In-ternet actually is. In this article we look at some

of the various metrics people have used to measureIP networks and discuss what they tell us aboutthe size of the Internet.

To measure the size of a network, different peopleuse different measurements according to theirneeds. Network managers typically want to knowthe number of hosts and constituent networkswithin the larger Intemet. Accountants oftenwould like to know how much data is beingexchanged (a number, incidentally, which is notcollected for the Intemet as a whole, althoughmany constituent networks keep such statistics).As a measurement of the size of the Internetworkcommunity, users sometimes want to know howmany other users or other organizations are con-nected.

The measurement that has been tracked the longestfor the Internet is a count of the number of activeIP networks that are connected to it- in otherwords, how many IP networks there are in theInternet. We emphasize the notion of an "IPnetwork." Multiple contiguous physical networkscan be combined into one logical IP network usinga procedure called subnetting, so a count of thenumber of IP networks does not equal the number

NSFNET TrafficOld Backbone (Aug. 87-Jun.88)

- 1987-1988New Backbone (Aug.-Sept. 88

300,000,000

250,000,000

200,000,000

150,000,000

100,000,000

50,000,000

Note: Statistics taken from N/A Nethernet interfaces on old back-bone, from LANO interface fornew backbone. I 198 7 II 1988

New NSFNET backbone: The cutover to the new NSFNET backbone successfully occurred at the end of July.Statistics indicate that the packet traffic passed across the new backbone in September was approximatelydouble what it was on the old backbone in June. As of the end of August, 241 campus nets were in theNSFNET routing tables and 247 ARPANET networks were also reachable through the backbone. Over onehalf of the networks in the Internet are now directly reachable via the NSFNET backbone.

DECEMBEK 1988

Number of Packets

Packets in

I Packets out

Merit/NSFNET Information Services 1988

14

of physical networks. But the number of active IPnetworks is a rough indicator of how fast theInternet is growing. Networks are typically addedwhen new organizations join the network, or whenan already-attached organization outgrows itsexisting subnet and needs to add another one.

Growth of the network

Starting from just over 50 networks in late 1983,the network reached nearly 450 active networks bymid-1988. (As of August 1988, the count hadreached 470.) A startling discovery is that, whileInternet growth was roughly linear between 1983and early 1987, it now appears to be exponential.The Intemet, quite simply, is booming.

This explosive growth rate can be confirmed bycounting the number of hosts attached to theInternet. In the old days, one counted the numberof hosts on the Intemet by counting the number oflines in the HOSTS.TXT text data base maintainedby the NIC. Now, to get an accurate count, onemust consult the domain name system, the distrib-uted naming data base which most systems nowuse for host lookups. Dumping the entire distrib-uted data base is an expensive process, and is onlydone occasionally, so we cannot track the Internetgrowth as finely as we can by counting the num-ber of networks. Still, the host counts are interest-ing. In early 1987, the domain name systemcontained entries for 20,000 Intemet hosts. Byspring 1988, the number of entries had grown to40,000. The current estimate of the number ofhosts is well in excess of 50,000 (although thisestimate has not been checked).

Estimating the number of users on NSFNET is amatter of guesswork. We know that there are atleast 65,000 users because the nameserver at theNIC contains that many entries. But, in practice,the NIC data base lists only a small fraction of thenumber of users. One could generate a morerealistic estimate by multiplying the number oforganizations on the Intemet by the number ofusers at each organization. Using the number ofnetworks as a rough count of organizations, wehave 450 organizations. Estimating the averagenumber of users is harder, but the average count isprobably greater than 1,000 (some of the universi-ties on the network claim user populations inexcess of 10,000, as do a few corporations).Accordingly, our guess is that the number ofInternet users is probably over half a millionpeople.

Telenet WATS numbers changed

Telenet is in the process of changing the In-WATSservices telephone numbers used to access theTelenet Public Data Network. The new In-WATSnumbers are based on a fiber-optic system that willprovide clearer connections and improved trans-mission quality for Telenet In-WATS users. Thischange will provide you with a superior level ofservice, and enable Telenet to provide enhancedfeatures on its In-WATS services in the future.

All Telenet In-WATS Services will have newtelephone numbers effective November 1, 1988:

300 - 1200 bps new number = 1-800-546-1000(old number = 1-800-424-9494)

2400 bps new number = 1-800-546-1000(old number = 1-800-238-0631)

If you encounter any problems or have questions,please call the Telenet Customer Service at 1-800-336-0437, or contact Marla Meehl. Her electronicmail address is marla@ncar.ucar.edu on theInternet. You may also telephone her at (303)497-1301.

Sending and receiving mail andfiles over the Internet andBITNET from the NCARIBM 4381 (IO) computer

by Bill Ragin

The capability now exists on the NCAR IBM 4381(IO) front-end computer to send and receive mailmessages and files over BITNET and the Internet.Mail messages may be sent with the enhancedNOTE command. Files may be sent using theenhanced SENDFILE command. SENDFILE, ingeneral, uses the Mail facility to transfer files.The NOTE and SENDFILE commands represent anew, unified mail system for the IBM 4381. Theenhanced versions of the NOTE and SENDFILEcommands will replace the existing versions ofthese commands on December 12, 1988. TheNOTE and SENDFILE commands can be used tosend mail and files locally, over the Internet, andon BITNET.

continued on next page

DECEMBER 1988

I

15

continued from previous page

Specifying host destinations

The general formats of the NOTE and SENDFILEcommands are:

NOTE addressandSENDFILE fn ftfm TO address

where address has the format:

userid [AT hostname]... [CC: userid [AT host-name]]...

Note: Brackets [ ] indicate optional items, andellipses (...) indicate that items may be repeated.

The hostname will determine whether the mailmessage or file is for a local, Internet, or BITNETuser. A BITNET hostname may optionally havethe .BITNET name appended to it. The Internethostname may be either the full name, for example,windom.ucar.edu, or its IP address enclosed inbrackets, for example, [128.117.64.2]. If thehostname is omitted, then the recipient is assumedto be a local IO user.

Note: None of the node names that were usedwith the EMAIL command will work as hostnameswhen used with the NOTE or SENDFILE com-mand. To translate between the EMAIL nodenames and the Internet hostnames,use the QNODEcommand. You can type HELP QNODE to obtaininstructions.

You may specify the userid and hostname whenusing the NOTE or SENDFILE command, or youmay use a nickname or a name that represents alist of names that are entries in your electronicaddress book. The electronic address book is afile called "userid NAMES A" that you create andmaintain with the NAMES command. You can

type HELP NAMES for a detailed description ofthe NAMES command.

Sending mail messages

The NOTE command will place you in a versionof the XEDIT editor. When you are finishedentering your message, press the PF5 function key(or use the send command) to send it. A singlecopy of the mail message is sent to the recipient, acopy is automatically saved in your ALL NOTE-BOOK A file, and your NETLOG file is updated.When a mail message cannot be delivered, a non-delivery message is returned to your reader ex-plaining the reason. You can type HELP NOTE toget a detailed description of the NOTE command.

Sending files

The SENDFILE command permits you to send atext (not binary) file to recipients locally, or torecipients on the Internet or BITNET. The addressconventions are the same as with the NOTEcommand. If the file cannot be sent, a nondeliverymessage is returned to your reader. Files sent to aBITNET hostname are subject to a limit of300,000 characters, and files sent to an Internethostname are subject to a limit of 50,000 charac-ters. There is no limit if the recipient is a local IOuser. SENDFILE will add a mail header to thefile, unless the recipient is a local IO user or is ata BITNET hostname running the VM/SP operatingsystem. You can type HELP SENDFILE for adetailed description of the SENDFILE command.

Receiving mail and files

All mail and files arriving from senders locally,over BITNET, or over the Internet are delivereddirectly to your virtual reader. These files may beexamined from within your reader with the

DECEMBER 1988

Examples of address

Address Description

tom Local IO user named tom.bill parker cc: don Local users bill and parker, with a copy to don.hans AT dhvrrzno BITNET user hans at BITNET node dhvrrzno.morris AT umdc.umd.edu Internet user morris at umdc.umd.edu.phylecia AT [128.117.64.2] Internet user phylecia at host IP number 128.117.64.2.hack%uwaterloo AT relay.cs.net User hack on CSNET accessed computer uwaterloo.bill jones AT sri-nic.arpa lv3 AT Local user bill jones at sri-nic, and lv3 at windom.

windom.ucar.edu

16

RDRLIST or PEEK commands. The files may bemoved from your reader to one of your minidiskswith the RDRLIST or RECEIVE commands. Filesthat are sent to you over BITNET or the Internetare in the NETDATA format and can only bemoved or examined with these commands. If thefile type of the file in your reader is note (preparedby the NOTE command), the RECEIVE functionof RDRLIST and the RECEIVE command willappend the file to your ALL NOTEBOOK A file.There are help facilities for the RDRLIST, RE-CEIVE, and PEEK commands.

If you have any questions about sending mail ortext files on the IBM 4381, send e-mail or call theSCD Consulting Office. Their e-mail address isconsultl@ncar.ucar.edu on the Internet. BITNETmail may be sent to CONSULT1 AT NCARIO.Phone: (303) 497-1278.

Bill Ragin is a programmer in the Networking and DataCommunications Group of the Distributed ComputingSection within SCD.

Central post office computer nowhandling Telemail and Omnetmail

by Greg Woods

It is now possible to send mail to and receive mailfrom Telemail and Omnet (a subset of Telemail)users via the NCAR central post office computer.The general syntax for a Telemail address is

[user/org]net/country@ telem ail

where user is the user's name on the Telemailnetwork, org and net are the organization andnetwork names that are specific to Telemail, andcountry is generally "usa," for the United States.Omnet user names are usually of the form I.LAST,where "I" is the first initial for the user's formalname (meaning that someone named "Bill" is"W", not "B") and LAST is the user's last name.The brackets are required.

For example, an Omnet address is of the form

[userlomnet]mail/usa@telemail

where mail is the iame of a computer in theTelemail system.

In general it is necessary to know the user'sTelemail address ahead of time; we do not yethave access to an online directory such as thedirectory of e-mail addresses that we provide forNCAR users. It is also essential that there be nospaces in the address, even if Telemail users writetheir address with spaces.

Please note that the [ ] characters will cause theUNIX shell to complain; therefore, UNIX usersshould enclose the whole address in double quotes.For example, on UNIX you might include theaddress above in the following mail command:

mail "[J. DOE/omnet]m ail/us a@telem ail"

Because many NCAR users have accounts onOmnet, which is a subset of the Telemail network,we provide a simpler address syntax to use ingetting there. Omnet users can be reached bysimply mailing to "user@omnet". Thus, theaddress in the example above can just be rewrittenas "J.DOE@ omnet."

VMS users must use additional syntax (such as,for example, adding NCAR% to the beginning ofthe address). Note that the Telemail gateway forusers of the Research Data Support System(RDSS) is unchanged. (For instructions particularto RDSS, you can obtain "A Brief Guide to Elec-tronic Mail on the RDSS VAX" from JonathanCorbet. His e-mail address iscorbet@rdss.ucar.edu. You can phone him at(303) 497-8793.)

For Telemail users to send back to us, they send amessage to

[postman/nasa]nasamail/usa

Then, after getting the Text: prompt from Tele-mail, they type the following (including To:), asthe first line of the message,

To: user@host.ucar.edu

where user and host are specific to the user theyare trying to send to. Note that the To: line mustbe followed by a blank line, then the text of themessage.

In particular, they can use

To: firstlast@ncar.ucar. edu

continued on next page

DECEMBER 1988 17

Scontinued from previous pagewhere first and last are the names listed for theuser they are trying to reach in NCAR's central e-mail database. Instructions for accessing thatdatabase are given in the October issue of SCDComputing News on page 9. Questions should bedirected to the Consulting Office. Their e-mailaddress is consultl@ncar.ucar.edu on the Internetor CONSULT1 on the IBM 4381 (IO) front-endcomputer. Telephone: (303) 497-1278.

Greg Woods is the e-mail specialist in the Networkingand Data Communications Group of the DistributedComputing Section within SCD.

The SCD UserDoc "NCAR Metafile Utilities:MFEDIT, MFMERGE, MFSPLIT, andPLTCONV" details the usage of these facilitiesand provides comprehensive examples.(PLTCONV, also a metafile utility, is only con-cerned with the metafile's structure and not withwhat is in the metafile, and thus it did not requireupgrading.) SCD documentation is available fromMary Buck. Her e-mail address ismaryb@ncar.ucar.edu on the Internet or MARYBon the IBM 4381 (IO) computer. Her telephonenumber is (303) 497-1232. If you are at the MesaLab, you can also obtain SCD documentation fromthe SCD Consulting Office, Room 17.

Fred Clare is a programmer in the Graphics Group ofthe Distributed Computing Section within SCD.

Metafile manipulation utilitiesnow support CGM

by Fred Clare

The metafile manipulation utilities MFEDIT,MFMERGE, and MFSPLIT have been upgradedon the NCAR Cray computers (CRAY,C1 andCRAY,CX). They now accept NCAR CGM inaddition to the previously accepted NCAR pre-CGM metafiles. (CGM stands for ComputerGraphics Metafile and is a national standard formetafile encoding.) CGM files are produced bythe NCAR GKS (Graphical Kernel System)Graphics package. Pre-CGM files are produced bythe NCAR pre-GKS Graphics package (NCARSystem Plot Package-based graphics).

These locally developed Cray utilities provide youwith some important capabilities. MFEDIT allowsyou to edit a metafile on a frame-by-frame basisand save the selected frames into a new metafile.MFMERGE merges named metafiles into a singlemetafile. MFSPLIT, the opposite of MFMERGE,splits a metafile into a specified number of smallermetafiles.

DECEMBER 1988

l

18

Tracking down run-time errors

by Lynne Andrade

* mismatched parameters in subroutine calls

Two approaches to solving operand range errorsare to (1) use the bounds checking option on thecompiler, using ON=O (for example CFT,ON=O)or (2) use the P-address technique.

P-address technique

Run-time errors can be very frustrating and time-consuming to solve. Although there is no one wayto go about finding these errors, this article willlook at two of the most commonly occurring run-time errors - floating-point error and operandrange error - their causes, and ways that you cango about solving them.

One of the reasons that run-time errors are difficultto solve is that it may be difficult to pinpointexactly where an error is occurring in the program.This is because frequently the code does not abortwhen the error is made, but causes an abort muchlater in execution. Once the place in which theerror occurs has been isolated, correction is oftenquite simple.

Floating-point error

A floating-point error can have several causes. Itcould be the result of:

* out-of-bounds references in a Fortran program* nonstandard code in a Fortran program* mismatched parameters in subroutine calls* numerical algorithm deterioration* corrupted input files* use of uninitialized data

Two approaches to solving a floating-point errorare to (1) turn on the bounds checking option onthe compiler, using ON=O (for example,CFT,ON=O) or (2) use the P-address technique.The P-address technique is discussed below.

Operand range error

Causes of the operand range error can be

* out of bounds references in a Fortran program

The P-address technique uses absolute (P) andrelative addresses to calculate the approximate linein the code where the error is occurring. Thismethod requires the following steps:

1. Compile the code, using ON=B to list thebeginning sequence number of each codegeneration block (for example, CFT,ON=B).

2. Obtain a loader map by using MAP=FULL inthe LDR or SEGLDR statement (for example,SEGLDR,CMD='MAP=FULL'.). This mapwill provide load addresses of various entriesin your program.

3. Find the absolute address at which the erroroccurs from the traceback, and note the routinename if possible. From the load map, find theabsolute address of the named subroutine.These addresses are given in octal.

4. Do an octal subtraction of the absolute addressof the subroutine from the absolute addresswhere the error occurred. The result is theoctal relative address where the error occurred.

5. Refer to the compilation listing of the subrou-tine to find the line of code closest to therelative address that was computed in Step 4,based on the information from ON=B.

Error solution examples

Example of using bounds checking

This example illustrates the use of the boundschecking function. Following is the compilerlisting and output for a program compiled usingON=O. Notice that during execution, an error

continued on next page

DECEMBER 1988 19

continued from previous page

message is generated when the upper bound of thearray is exceeded. The error message is not acompiler message; it is a run-time error message.

1 1.

23 2.4 3.56 4.7 5.89 6.10 7.

The error message of interest has been boxed foremphasis - the box is not a product of the normallisting.

PROGRAM TSTBNDS

PARAMETER (N=10)REAL ARR (N)

C

C

C

PRINT *, "EXECUTION OF PROGRAM TSTBNDS BEGINNING."

ARR(N+1) = 2.0

STOPEND

B SAVE: 4T SAVE: 0CONSTANTS: 12

VARIABLES: 14

TEMPORARIES: 34

CODE: 34

TOTAL: 122

EXECUTION OF PROGRAM TSTBNDS BEGINNING.

PROGRAM - TSTBNDS AT LINE 5 SUBSCRIPT VALUE > UPPER BOUND FOR DIMENSION 1

OF ARRAY - ARR

Example of address calculation

This example walks you through the steps previ-ously outlined for using the P-address technique.First, the job is run with the necessary CFT andSEGLDR options. MAXBLOCK=l was used inthe CFT statement for this example. In general, ablock number marks the beginning of each block.The use of this option essentially causes each linein the program to be the beginning of a block. (Italso turns off all optimization and vectorization.)

If you do not use MAXBLOCK=1 each block willcontain more lines of code.

Next, the log file is checked, and, in the traceback,you can see the absolute address of the routine inwhich the job aborted ("P=00000234b" in the firstbox; this can be read as address 234). Also, theroutine in which the job aborted can be noted to bePROC1 (see example on next page).

DECEMBER 198820

CFT, ON=B, MAXBLOCK=1.USER CFOOO - CFT VERSION - 07/16/88 1.15BF2

USERCFTRV - CFT 1.16 Bugfix 2 - 66 Jun. 1988USER CFTRV - Includes mod(s) : Q1704 8A, Q1774 7AUSERCFTRV - Q18534A,Q17310A,T19394A

USER CF O1 - COMPILE TIME = 0.0139 SECONDS

USER CF002 - 27 LINES, 17 STATEMENTS

USER CF003 - 67530 WORDS, 10444 I/O BUFFERS USED

CSP SEGLDR,CMD='MAP=FULL'.

USERSG000 - SEGLDR VERSION 3.1 - 07/16/88 (CHG-11

CSP $ABD.

ABORT AB053 - FLOATING POINT ERROR

ABORT AB000 - JOB STEP ABORTED. P = 00000234bABORT AB000 - BASE 31525000 LIMIT

ABORT TB001 - BEGINNING OF TRACEBACK

ABORT - PROCi WAS CALLED BY

ABORT (WCB) - FLTST AT

ABORT TB002 - E

EXP EXIT.CSP END OF JOB

2/31/86)

31603000 CPU NUMBER

207a (LINE

03

4)AND OF TRACEBACK

In the load map, the load address for PROC1 isfound to be 222 (octal). (See the next boxed line.)Address 234, from the traceback, is between 222

and 251, 251 being the load address shown on thenext line. Therefore, the program is aborting inroutine PROCi, which begins at address 222.

SORTED BY ASCENDING BLOCK ORIGIN ADDRESS

MODULE

BLOCK

FLTST

#TB

#CL

ADDRESS LENGTH SOURCE DATE

200

212

216

12

4

4

$BLD

$BLD

$BLD

11/02/88

11/02/88

11/02/88

OS REV

14:24

14:24

14:24

COSX1614

CosX1614

COSX1614

CFT 1.

CFT 1.

CFT 1.PROCi 222 27 $BLD 11/02/88 14:24 COSX1614 CFT 1.

251300

440

6

102

76

$BLD

$UTLIB

$UTLIB

11/02/88

07/16/88

07/16/88

14:24

08:44

08:44

COSX1614

CO5X1608

COSX1608

CFT

CALCAL

1.

1.

1.

continued on next page

DECEMBER 1988

#TB$BTD

$BTO

21

continued from previous page

Doing an octal subtraction of the load addressfrom the address where the error occurred resultsin an address of 12 in octal: 234, - 222, = 12,8Then, checking the compiler listings, you can see

13 1.

14 C15 2.

16 3.17 4.

18

19 5.20 6.21

22 7.23 8.24 9.25

26 10.

27 11.

C

C

that address 12d is sequence number 7 (line 22).You can ignore the trailing letter ("d" in thisexample) after the octal address.

SUBROUTINE PROC1i(INT)

REAL ARR (10)REAL VAR, NUVARINTEGER I

DEN = INT

NUVAR = VAR/DEN

DO 10, I=1, 10ARR(I) = NUVAR + I

10 CONTINUEC

RETURN

ENDPROC1 BLOCK BEGINS AT SEQ. NO.PROC1 BLOCK BEGINS AT SEO. NO.

5, P= 5b6, P= 7d

IPROC1 BLOCK BEGINS AT SEQ. NO. 7, P= 12dPROC1

PROC1PROC1

PROC1

BLOCK

BLOCK

BLOCK

BLOCK

BEGINS

BEGINS

BEGINSBEGINS

AT

AT

AT

AT

SEQ.

SEQ.

SEQ.

SEQ.

NO.

NO.

NO.

NO.

7,

8,

9,

10,

P= 15a

P= 15a

P= 20cP= 23d

Since the error is flagged after it actually occurs,this address is an approximation. Sequencenumber 7 is the DO loop, so the code previous tothis loop is suspected. Dividing by zero is acommon cause of floating-point errors, so thevalue of DEN should be checked. In this case, itturns out that INT was set to zero in the main

19 5. DEN = INT

120 6. NUVAR = VAR/DEN21 C

22 7. DO 10, I=1, 10

program (not shown) and then passed to PROC1(sequence number 1) with that value. Thus, thefloating-point error occurred in sequence number6, as shown at left.

With the use of these methods, solving run-timeerrors can become more straightforward. If youhave questions regarding these techniques, pleasecontact the Consulting Office atconsultl@ncar.ucar.edu on the Internet or CON-SULT1 on the IBM 4381 (IO) front-end computer.You may also call the consultants at (303) 497-1278 or drop by the Consulting Office, Room 17of the Mesa Lab.

Lynne Andrade is a consultant in the User Servicessection within SCD.

DECEMBER 198822

Metafile manipulation utilities

Updated documentation availablefrom IBM

Manuals for CMS and CP that correspond toRelease 4, the version that became the defaultoperating system on the IBM 4381 (IO) front-endcomputer in November, are available from IBM.

The "IBM VM/SP: System Product Editor User'sGuide," Release 4, SC24-5220-2 ($8.80) is de-signed to give you a working knowledge ofXEDIT, the System Product editor. It discussesboth full-screen and line-mode editing and uses"before and after" examples to illustrate the text.

The "IBM VM/SP: CMS User's Guide," Release4, SC19-6210-3 ($29.25) is intended for thegeneral CMS user. It describes the interactivefacilities of CMS and provides many examples.The topics include using the CMS file system,using the help facility, reading tapes, and writingEXECs.

To order IBM documentation, call 1-800-426-2468and ask for the Education and Software Depart-ment.

New documentation availablefrom SCD

Frequently used acronyms and terms inSCD

"Acronyms and Terms Frequently Used in theSCD Computing Environment," Version 1.0,November 1988 (12 pages), is now available. Itcontains the most frequently used acronyms andterms in use in the SCD computing environment.Entries are listed alphabetically. An appendix thatdiscusses abbreviations for commonly used com-puting units is included.

"NCAR Metafile Utilities: MFEDIT, MFMERGE,MFSPLIT, and PLTCONV," Version 1.0, Novem-ber 1988, details the usage of these manipulationutilities for metafiles produced by both the NCARGKS (Graphical Kernel System) and the NCARpre-GKS Graphics packages.

Transferring binary metafiles to VAX/VMSsystems

"Transferring Binary Metafiles to VAX/VMSSystems, " Version 1.0, November 1988 (5 pages),has been released. This document discusses howto transfer binary metafiles to VAX/VMS systemsfor users of both pre-Computer Graphics Metafile(CGM) NCAR metafiles and NCAR CGMmetafiles. Because of operating system differ-ences, metafiles may have to be reformatted afterthey reach the VAX/VMS system. This documentcontains instructions on how to obtain executablecode through an "anonymous FTP (File TransferProtocol)" to perform these and other file transfor-mations.

MSS tape facility: MEXPORT/MIMPORT

"MEXPORT and MIMPORT: Transferring DataBetween the Mass Storage System and Tape,"Draft Version 1.0, November 1988, documents theuse of the Mass Storage System's tape facility forboth 9-track, 1/2-inch magnetic tape and IBM3480 tape cartridges. Accessible from eitherNCAR Cray computer, this facility will becomethe primary method for staging tapes to and fromthe Mass Storage System when the CRAY-1A isphased out.

MIGS user's guide

The "MIGS: MASnet/Internet Gateway ServerUser's Guide," Draft Version 1.2, November 1988,describes how to use MIGS from both your localsystem and from MASnet systems. MIGS is acombination of hardware and software that allowsaccess to the NCAR Mainframe and ServerNetwork (MASnet) by computers attached to the

continued on next page

DECEMBER 1988 23

continued from previous page

Internet. MIGS provides an easy way to accessthe Cray computers, the DICOMED, and the MassStorage System, as well as other components ofthe NCAR computing environment. MIGS canalso be customized at each local site. The docu-mentation details use of all parameters and pro-vides usage examples.

SUDOOS documentation

Two new documents detail SCD's new colorDICOMED facility. Most users of the Craycomputers will find the information contained inthe User's Guide sufficient for producing coloroutput from the color DICOMEDs.

The "User's Guide to Producing Color Outputfrom the Cray Computers," Draft Version 1.0,November 1988, is now available. This newdocument describes how to produce 35-mm filmfor color via the Sun/UNIX DICOMED OnlineOperating System (SUDOOS). The document pro-vides examples and explains the most commonlyused parameters.

The "Preliminary Sun/UNIX DICOMED OnlineOperating System (SUDOOS) Reference Manual,"Draft Version 3.1, November 1988, is now avail-able. It contains detailed information on preparingjobs for SUDOOS and for submitting those jobsfrom Cray, VM/CMS, UNIX, and VAX/VMSoperating systems. It also provides information onsubmitting jobs to SUDOOS from the MASnet/Internet Gateway Server (MIGS). SUDOOSfeatures that have not yet been implemented areclearly marked in this draft version.

Updated documentation availablefrom SCD

New version of Cray JCL

"Cray Job Control Language with NCAR Site-specific Parameters," Version 2.0, October 1988(37 pages), has been released. Users who obtainedthe draft version (Version 1.0) of this documentare encouraged to order this revision because ofthe substantial amount of new information that itcontains. As before, the document provides a list

of Cray Job Control Language (JCL) with site-specific parameters, gives the possible values ofthose parameters, details site-specific TEXTparameters, and lists Cray- and NCAR-supportedJCL commands. A new section discusses Fortran-callable JCL - Fortran routines whose functionsare the same as in Cray JCL. All 20 Fortran-callable routines are documented with usageinstructions and examples.

New version of locally developed utilities

"Locally Developed Cray Utilities," Version 1.1,November 1988 (20 pages), contains updatedinformation for the eight utilities it documents:AQPLMS, AUDPRJ, DROPJQ, GETDOC,GETSRC, LOCATE, MAQR, and REMOVE.Additionally, UserDoc references for all of thelocally developed utilities and a listing of thevarious ways to access the job queue status displayare new.

Ordering instructions for SCDdocumentation

To order SCD documentation, send e-mail tomaryb@ncar.ucar.edu on the Internet and MARYBon the IBM 4381 (IO) computer, or call MaryBuck at (303) 497-1232. If you are at the MesaLab, you can obtain SCD documentation from theSCD Consulting Office, Room 17.

October 24, 1988

by Juli Rew

Report from the SCD Director - Bill Buzbee

Bill reported that SCD did not expect to obtain aCRAY X-MP/28 in the next year. He said thatalthough such a computer would probably beavailable for lease, funding would only be sufficientfor a limited time, and so it would not be worth theeffort to integrate it into the NCAR system.

DECEMBER 1988

l '

24

He also reported on the status of the CRAY-1A,which is expected to be phased out in the nearfuture. Buzbee and Acting NCAR Director BobMacQueen will form a committee to investigateoptions. At present, the CRAY-1A is expected tobe available at NCAR through the rest of 1988.

Bill reported on several other operational items:

* The new color DICOMED graphic recorder isnow available for "friendly usage."

* Also available for friendly usage is the newMIMPORT/MEXPORT facility for importingand exporting data to and from the NCAR MassStorage System. Bill encouraged users to "helpus shake it down." (See "MIMPORT/MEX-PORT facility ready for general use" in thisissue.)

* The new T1 (1.54 megabits/second) communica-tions link among NCAR's Boulder sites is nowoperating well.

* The COS 1.16 operating system brought up onthe NCAR Cray computers this summer hasdramatically reduced the number of lost jobs.The installation required a lot of work and wentremarkably well. (Another advantage to usersunder COS 1.16 has been improved managementof the Solid-state Storage Device duringmonoprogramming class jobs. See SystemsNews.)

* The method for sending notices of purges on theMSS has changed, and Bill encouraged users tobe sure they are getting their purge messagesproperly via the NCAR central e-mail post officecomputer (see the announcement in MSS News).

* SCD welcomes feedback on the new chargingstructure that was implemented in October.

Computing at the Research AviationFacility

Richard Friesen (ATD/RAF) reported on comput-ing at NCAR's aircraft facility. NCAR's threeaircraft are used to collect data on cloud physics,air chemistry, air motion, and radiation, and RAFassists in the data processing, analysis, archiving,and use of these data in atmospheric models. Thedemand for real-time data acquisition and displayaboard the research aircraft has burgeoned re-cently. Other challenges unique to RAF includethe need for computers that are both small enoughto fit on aircraft and robust enough to be able towithstand buffeting during research flights.

RAF recently obtained a MASSCOMP 6700computer system. It is a multiprocessor UNIXsystem with 16 megabytes of main memory.Friesen said the computer's "specialty" is supportof real-time computing (it is a popular computer atNASA), and it represents a fivefold computingpower increase for the facility. RAF has alsoacquired a Sun-3 portable field workstation toreplace its HP 1000 computer, and is currentlydeveloping an onboard display system based on asmall Eurocard version of the Sun-3. The conver-sion to UNIX operating systems has gonesmoothly. Other computing tasks at RAF includethe use of Computer Aided Design/ComputerAided Engineering for aeronautical and electronicdesign of aircraft and instrument components, andthe use of airflow models to determine the charac-teristics of airflow streamlines around the aircraft.

Dick mentioned that RAF had long faced problemswith being 14 miles away from the Mesa Lab, atJefferson County Airport near Broomfield. Thenew T1 communication link is expected to im-prove communications greatly.

An upcoming major joint project of the RAF andField Observing Facility is the Electra DopplerRadar (ELDORA), which will be an airborne dual-Doppler radar. Data recording and processingneeds are expected to grow with ELDORA.

continued on next page

DECEMBER 1988 25

continued from previous page

Documentation Advisory Committee

Linda Bath (CGD), who chaired the Documenta-tion Advisory Committee, reported on the commit-tee's work and its recommendations to SCD forimproving documentation for users. An article onthe committee's report (the report will be releasedas an NCAR Technical Note) is included in thisissue of SCD Computing News.

The committee recommended, among other things,that SCD augment its online documentation.Buzbee asked about the cost of an online docu-mentation system. Bath replied that availablesystems are costly; it runs about $7500 per year tolease the system used by the NCAR Library for itsonline catalog. Carol Fey (DIR) said a majorconcern is connectivity. With NCAR's multipleoperating systems, front ends, and hardware, it isdifficult to know where to place online documenta-tion to make it accessible by all the users.

Carl Mohr asked who handles the documentationfor the SCD Data Support Section (DSS), whicharchives meteorological data. While the DSS hasin the past distributed its own documentation, its

documentation is now listed in the User Documen-tation Catalog (the catalog, released in September,is available from Mary Buck at the address listedon the back cover of this newsletter).

User questions

SCDUG chairman Carl Mohr (ATD) asked aboutdocumentation for the color DICOMED. GingerCaldwell (SCD) noted that alpha testing was inprogress on UNIX systems and that the SCDConsultants were beginning to test its use via theCray computers. If you have questions about thestatus of SUDOOS, you may contact DennisColarelli. His e-mail address is djc@ncar.ucar.eduon the Internet. Frieda Garcia (SCD, ext. 1254)can provide users with information on MIMPORT/MEXPORT also.

Future agenda

A request was made that SCD present a talk onusing the new color DICOMED.

Juli Rew is acting head of the Documentation Groupwithin SCD.

reetns

DECEMBER 198826

The following list includes acronyms and terms used in this issue and in the NCAR computing environment.

ASCII American Standard Code for Information InterchangeCCM Community Climate ModelCFT77 Cray FORTRAN 77 compilerCGM Computer Graphics MetafileCMS Conversational Monitor System, component of IBM VM operating systemCOS Cray Operating SystemCRAY, C1 CRAY-1A computer at NCARCRAY, CX CRAY X-MP/48 computer at NCARDICOMED Online graphic recorder used at NCAR for producing microfilm and microfiche outputEBCDIC Extended Binary-coded Decimal Interchange CodeELDORA Electra Doppler RadarFSS Fast Secondary StorageFTP File Transfer ProtocolGAU NCAR's General Accounting Unit; used in chargingGKS Graphical Kernel SystemIP Internet ProtocolIRJE Internet Remote Job EntryJCL Job Control LanguageKNET/Spartacus Hardware/software configuration that enables the IBM 4381 (IO) front-end computer to

use the TCP/IP protocol suiteMSCP Mass Storage Control ProcessorMSS Mass Storage System at NCAROmnet A subset of TelemailRDSS Research Data Support SystemSSD Solid-state Storage DeviceSUDOOS Sun/UNIX DICOMED Online Operating SystemTCP/IP Transmission Control Protocol/Internet ProtocolTelemail A commercial service providing electronic mail for subscribersVM/CMS Virtual Machine/Conversational Monitor SystemVM/SP Virtual Machine/System ProductVMS Virtual Memory System; a Digital Equipment Corporation operating system

Organizations

ATD NCAR Atmospheric Technology DivisionCGD NCAR Climate and Global Dynamics DivisionDIR NCAR Director's OfficeDSS NCAR SCD Data Support SectionHAO NCAR High Altitude ObservatoryMMM NCAR Mesoscale and Microscale Meteorology DivisionNASA National Aeronautics and Space AdministrationRAF NCAR Research Aviation FacilitySCDUG Scientific Computing Division Users Group

Networks

BITNET Because It's Time Network; an international Wide Area Network primarily for IBMcomputers at educational and research institutions

Internet A collection of interconnected regional and wide area networks that use the IP protocolMASnet NCAR's Mainframe and Server Network (formerly the NCAR Local Network)MIGS MASnet/Internet Gateway Server at NCARNIC Network Information CenterUSAN University Satellite Network

DECEMBER 1988 27

October 1988

Scientist

Mankin MakUniversity of Illinois

Dennis J. MusilSouth Dakota School of Minesand Technology

Richard L. WalterscheidThe Aerospace Corporation

Melinda S. PengNaval Postgraduate School

Clifford F. MassUniversity of Washington

Delores J. KnippUniversity of Californiaat Los Angeles

Steven A. RutledgeColorado State University

Mitsuhiro KawaseUniversity of Washington

* Douglas B. BoudraEdmo J. D. CamposUniversity of Miami

Michael AlexanderUniversity of Wisconsin

* Roger A. PielkeDouglas A. WesleyColorado State University

* John E. KutzbachPamela NaberUniversity of Wisconsin

* Douglas B. BoudraUniversity of Miami

Walter Francis MillerColorado State University

* Harold D. OrvilleWei YanSouth Dakota School of Minesand TechnologyColorado State University

Project Title

Research in nonlinear large-scaleatmospheric dynamics

Hail reflectivity project

Gravity wave saturation in themiddle atmosphere

Effects of three-dimensionaltopography on fronts

A numerical study of occludedfront development

Mapping the electrodynamic featuresof the high-latitude ionosphere

Modeling the electrical structure inmesoscale convective systems

(OCE) Baroclinic flows in the deepequatorial ocean

(OCE) Stationary Rossby waves onWestern Boundary Currentextensions

(OCE) Midlatitude atmosphere and oceananomalies during El Nifio

Mesoscale upslope snowfallstudies in complex terrain

Atlantic Ocean paleocirculationexperiments

(OCE) A wind- and thermohaline-drivenisopycnic coordinate circulation modelof the North and equatorial Atlantic Ocean

The effect of deforestation onequatorial sea breezes

Influence of boundary-layerstability on deep convection

GAU

Request Allocation

10.0 10.0

5.0 5.0

5.0 5.0

45.0 45.0

36.0 36.0

20.0 10.0

41.0 41.0

40.0 40.0

60.0 60.0

50.0 50.0

31.3 31.3

216.0 216.0

100.0 100.0

40.0 40.0

165.0 165.0

DECEMBEK 1988

f -- -%I

A

28

* Barry SaltzmanRobert J. OglesbyYale University

* Timothy J. DunkertonNorthwest Research Associates

* Wei-Chyung WangAtmospheric & EnvironmentalResearch, Inc.

* Kelvin K. DroegemeierUniversity of Oklahoma

* Shenn-Yu ChaoUniversity of Maryland

* Albert J. Semtner, Jr.Naval Postgraduate School

* Tamas I. GombosiUniversity of Michigan

* J. Michael FritschPennsylvania State University

* Eric J. BarronLee R. KumpPennsylvania State University

* Nelson L. SeamanPennsylvania State University

* Douglas K. LillyVince WongUniversity of Oklahoma

Paleoclimatic sensitivitystudies II

Nonlinear instabilities of rotating,stratified shear flow

Atmospheric trace gases andglobal climate

Simulation of mesoscale andconvective-scale dynamics

(OCE) Tidal modulation of estuarineplumes

(OCE) Development of a global eddy-resolving thermodynamic oceanmodel for the 1990s

Time-dependent modeling ofmultidimensional transonic flowsin cometary atmospheres

Structure, dynamics, and numericalprediction of mesoscale convectivesystems

Coupled models of geochemicalcycles and climate

Numerical investigation ofexplosive marine cyclogenesis

Numerical simulations ofstorm ensemble

* These requests were reviewed by the Scientific Computing Division Advisory Panel on October 6-7, 1988.

OCE: These allocations were made from the 10% of SCD's computing resources earmarked for University Ocean-ography.

Note: The NCAR review procedures may result in a request being supported at a lower level than requested.

JoAn Knudson (SCD) compiles the allocation information.

DECEMBER 1988

395.0

80.0

180.0

222.0

80.0

925.0

75.0

75.0

66.0

103.0

225.0

245.0

80.0

120.0

222.0

80.0

925.0

75.0

75.0

66.0

103.0

125.0

29

An index of articles from the past 12 months appears in each issue.

CatalogUser Documentation Catalog (Sept. 1988)

Charging - GAUsCharges for SCD computing resources (May 1988,

Doc.)Charging started for hardcopy graphic images (Jan.

1988, Systems)MP1 and MP2 job classes (Feb. 1988, SCDUG)Mono-processing 1 (MP1) job class added (Jan. 1988,

Systems)Revised version of charges document (Aug. 1988,

Doc.)SCD reduces GAU charges for CRAY-1A computer

(June 1988, Systems)Slight charge increase for DICOMED film processing

(Feb. 1988, Systems)Trailer sheet with GAU charges added to graphics

output (May 1988)Use new form to correct charging problems (July

1988, MSS)

Cray ComputersAccessing memory on the CRAY X-MP (May 1988)Applications libraries compiled on CFT77 Release 2.0

(July 1988)Bit manipulation with GBYTES and SBYTES (Nov.

1988, Doc.)CFT77 compiler Release 3.0 becomes default October

21 (Oct. 1988)Chervin receives parallel computing award (May

1988)Colorado Science Fair winner uses CRAY-1A

computer at NCAR (June 1988)Cray job class changes (Oct. 1988, Systems)CRAY X-MP Job Queue Manager changes (July

1988, Systems)CRAY X-MP moving to COS 1.16 (May 1988)EDITOR (Aug. 1988, Doc.)Eight new documents available (Oct. 1988, Doc.)Highlights of CFT77 Release 2.0 (July 1988)How to access the FISHPAK software library (Mar.

1988)How to use DN, PDN, and FLNM correctly (Mar.

1988, Hints)Importing data to the MSS from optical disks (Mar.

1988)MSS ONLINE and OFFLINE parameters imple-

mented (Feb. 1988)Mono-processing class now available on CRAY-1A

computer (July 1988, Systems)Mono-processing 1 (MP1) job class added (Jan. 1988,

Systems)

New DISPOSE procedure with MASnet change (Oct.1988)

No tape access on CRAY,CX (Apr. 1988, Systems)One-hour limit on Cray Background 1 jobs removed

(July 1988, Systems)PERFMON: The CRAY Performance Monitor Utility

(Feb. 1988, Doc.)Remote Job Entry over the Internet now available

(Mar. 1988)Revised version of charges document (Oct. 1988,

Doc.)Revised version of documentation on CRAY-1A

direct tape connection (July 1988, Doc.)SCD conducts performance and benchmarking tests

(Apr. 1988)Site Liaison Workshop held for users (Oct. 1988)Time changed for Large Model class jobs (Aug. 1988,

Systems)Two methods for debugging large programs (Oct.

1988, Hints)UNICOS at Los Alamos (Apr. 1988, SCDUG)

GraphicsChange in NCAR Graphics distribution policy (May

1988)Computer Output Committee releases recommenda-

tions (Feb. 1988)The four versions of NCAR Graphics (Mar. 1988)Graphics output on the Xerox 4050 laser printers (Jan.

1988, Hints)Graphics plans for SCD (June 1988, SCDUG)NCAR Graphics - The two-year plan (Jan. 1988)NCAR Graphics Version 2.00 now available for

UNIX (Aug. 1988, Graphics)New GRAPHCAP added (Aug. 1988, Graphics)New release of NCAR Graphics for VAX/ VMS

systems (Jan. 1988)Options to process CGM through the DICOMED

(Feb. 1988, SCDUG)Target date for color output is Thanksgiving (Nov.

1988, Graphics)Transferring binary metafiles to VAX/VMS systems

(Nov. 1988)Xerox 4050 metafile translator has changed (Nov.

1988, Systems)

IBM 4381 (IO) Front-end ComputerAdditional security measures to be implemented on

the IBM 4381 (Apr. 1988)Change on RDR spool files on the IBM 4381 (Feb.

1988, Systems)Change your IBM 4381 front-end password (Oct.

1988, Systems)

DECEMBER 1988

j

30

Changing multiple MSS Files from the IBM 4381(IO) computer (Dec. 1987)

Having problems using FTP to connect to the IBM?(May 1988, Networking)

New version of SAS available (Mar. 1988)Sending and receiving mail and files on the IBM 4381

(Nov. 1988, Networking)VMSECURE command imposes new security (Feb.

1988)

Input/OutputGraphics output on the Xerox 4050 laser printers (Jan.

1988, Hints)Hints from the SCD Consultants (Nov. 1988, IBM)No tape access on CRAY,CX (Apr. 1988, Systems)Tape services provided by SCD (Dec. 1987)What are MASnet, UCARnet, LDN, and TGS? (Jan.

1988, Acronyms)

Macintosh ComputersSaving and printing screen dumps on the Mac (May

1988, Hints)

Mass Storage SystemBITNET at NCAR (Oct. 1988)Change in MSS retention periods (Feb. 1988, MSS)Changing your mass storage passwords (June 1988,

MSS)Duplicate MSS purge notices sent (Oct. 1988, MSS)IEEE Symposium on Mass Storage Systems planned

(Oct. 1988)Importing data to the MSS from optical disks (Mar.

1988)MAQR speeds multiple ACQUIREs (Apr. 1988,

Hints)MASnet/Internet Gateway Server now available (Oct.

1988)Mass Storage System (MSS) (Aug. 1988, SCDUG)MIMPORT/MEXPORT facility ready for friendly

users (Nov. 1988, MSS)The MSS Advisory Committee: Issues and recommen-

dations (Dec. 1987)MSS ONLINE and OFFLINE parameters imple-

mented (Feb. 1988)NCAR has new weather data accessing system (Mar.

1988)New operating system installed (Oct. 1988, MSS)Ninth IEEE Symposium on Mass Storage Systems

(June 1988)Preparing tapes for reading at NCAR (Aug. 1988,

Hints)Problem with purge notices corrected (Mar. 1988)SCD Internet/SPAN gateway operational (Oct. 1988)Should you store duplicate files? (Mar. 1988, MSS)Status report on MSS Advisory Committee (Feb.

1988, SCDUG)

Tape capability via Export/Import on the MSS forUNIX systems (Apr. 1988, SCDUG)

Use new form to correct charging problems (July1988, MSS)

NCAR NewsAccessing the NCAR Library catalog on-line (Dec.

1987)Administrative Computing Services (Nov. 1988,

SCDUG)CAPP receives 8K Connection Machine (Oct. 1988)Computational support in the Atmospheric Chemistry

Division (Apr. 1988, SCDUG)Computer and Communications Committee report

(Aug. 1988, SCDUG)NCAR has new weather data accessing system (Mar.

1988)Office support and the company store (Mar. 1988,

SCDUG)Rick Anthes appointed UCAR president (Nov. 1988)Software engineering application at NCAR (Nov.

1988, SCDUG)Status of Fortran 8x proposal (Jan. 1988, SCDUG)Supercomputing '88 Conference set for November

(Oct. 1988)

Networking and Data Communications1-800 service for Microcom 9600 BPS modem users

(Dec. 1987)An introduction to networking at NCAR (Aug. 1988)BITNET at NCAR (Oct. 1988)BITNET now available (Aug. 1988, Networking)Changes at NSFNET and ARPANET cause slow-

downs (July 1988)Changes to Telenet (Feb. 1988)CMS Kermit updated (Oct. 1988, Networking)Congestion on the NSFNET (Mar. 1988)The Connection Machine (July 1988, SCDUG)Contact your local representatives with Internet

problems (Apr. 1988)Cursor control when using TELNET with KNET/

SPARTACUS (Aug. 1988, Networking)Data communications package update (Dec. 1987)Distributed computing - What does it mean? (May

1988)EM4010 upgrade procedure (Apr. 1988)E-mail routing at NCAR (Nov. 1988)Greg Woods: SCD's electronic mail specialist (June

1988)Having problems using FTP to connect to the IBM?

(May 1988)High-speed WATS access to NCAR now available

(Mar. 1988)How to access the SCD Daily Bulletin on different

computers (Apr. 1988)

continued on next page

DECEMBER 1988

J

31

continued from previous page

How to use "anonymous FTP accounts" (Mar. 1988)Local T1 data and communications network to be

installed (Oct. 1988, Networking)Marla Meehl: Strengthening SCD's data communica-

tions (Oct. 1988)MASnet/Internet Gateway Server now available (Oct.

1988)Movie guide (Aug. 1988, Doc.)NASA Science Network (Jan. 1988, SCDUG)NCAR connection to SPAN (May 1988)New DISPOSE procedure with MASnet change (Oct.

1988)NSFNET backbone to expand and jump to T1 speeds

(June 1988)NSFNET management awarded to MERIT, Inc. (Jan.

1988)New CMS Kermit version installed (July 1988,

Networking)New NSFNET backbone now in service (Aug. 1988,

Networking)New Telenet line-mode/Simware logon procedure

(Mar. 1988)Please stand by: NSFNET experiences network

difficulties (June 1988, Networking)Recent developments in NCAR e-mail (Oct. 1988)Remote Job Entry over the Internet now available

(Mar. 1988)Revised version of RSCS documentation (July 1988,

Doc.)SCD Internet/SPAN gateway operational (Oct. 1988)Sending and receiving mail and files on the IBM 4381

(Nov. 1988, Networking)SPAN (Apr. 1988, SCDUG)Telenet, TELNET, and FTP (May 1988, Acronyms)Telenet WATS numbers changing (July 1988,

Networking)Telenet WATS numbers remain unchanged (Aug.

1988, Networking)UNIX mail: Aliasing names and lists (June 1988,

Hints)UNIX mail hints (June 1988, Doc.)Version 2.6 of SPARTACUS/KNET installed (May

1988)Workshop reviews progress toward next-generation

networks (July 1988)What are MASnet, UCARnet, LDN, and TGS? (Jan.

1988, Acronyms)

SCD NewsBillions and billions of bits (Aug. 1988, Acronyms)Call for Poster Presentations, Supercomputing '88

(July 1988)CAPP receives 8K Connection Machine (Oct. 1988)Computational Space Committee (July 1988, SCDUG)Consulting staff adds new member (Jan. 1988)Eight new documents available (Oct. 1988, Doc.)

Election of new chairperson (July 1988, SCDUG)Graphics plans for SCD (June 1988, SCDUG)IEEE Computer Society contributes to Global Change

Program (July 1988)IEEE Symposium on Mass Storage Systems planned

(Oct. 1988)Joseph receives NCAR Technical Support Award

(Feb. 1988)Keep in touch for better service from the Consulting

Office (Feb. 1988, Hints)New tools monitor SCD computing operations (June

1988)Printing keywords to change (Oct. 1988, Systems)The path to UNIX (Jan. 1988, Director's Col.)Recommended UNIX books (July 1988, Hints)Revised version of charges document (Oct. 1988,

Doc.)SCD appoints Consulting Group Head (Mar. 1988)SCD celebrates first anniversary of Director Bill

Buzbee (June 1988)SCD extends Consulting Office hours (July 1988)SCD offers course for new users (Aug. 1988)SCD visitors' area upgraded (Nov. 1988)Supercomputing '88 Conference notes (July 1988)Supercomputing '88 Conference set for November

(Oct. 1988)Use your password to help maintain computer security

(Aug. 1988)Users Conference examines future supercomputing

use and technology (Feb. 1988)

Software LibrariesAutomated scripts (May 1988, SCDUG)FISHPAK revised (June 1988, Doc.)How to access the FISHPAK software library (Mar.

1988)IMSL Edition 10.0 now available (June 1988)MUDPAK (Aug. 1988, Doc.)MUDPAK: New multigrid software for linear elliptic

partial differential equations available (Aug. 1988)NAG chapter documentation files available (May

1988)NAG Fortran Library is updated (Feb. 1988)NCAR introduces ODEPACK (Nov. 1988)New CMS command available (Aug. 1988)New version of SAS available (Mar. 1988)Proposed software services in distributed computing

(May 1988, SCDUG)SSDLIN revised (June 1988, Doc.)STARPAC 2 now available (Jan. 1988)

DECEMBER 198832

CHANGE OF ADDRESS FORMO Add to mailing list E Delete from mailing list O Change existing entry

Name:

New address:

User number Phone number

Send to: Frieda Garcia, Scientific Computing Division, NCAR, P.O. Box 3000, Boulder,CO 80307-3000.

Trademarks: CRAY, CRAY-1, SSD, and UNICOS are registered trademarks, and CFT, CFT77, COS, and CRAY X-MP are trademarks of CrayResearch, Inc. DEC and VAX are registered trademarks of Digital Equipment Corp. HYPERchannel is a registered trademark of Network SystemsCorp. IBM is a trademark of International Business Machines Corp. Macintosh is a trademark of Apple Computers, Inc. Microsoft is a registeredtrademark of Microsoft Corp.; PageMaker is a registered trademark of Aldus Corp.; PostScript is a registered trademark of Adobe Systems, Inc.; andUNIX is a trademark of Bell Laboratories. Reference to a company or product name does not imply approval or recommendation of that companyor product to the exclusion of others.

~111111111111~~ -

SERVICES DIRECTORY

CONTACT PHONE EMI(303) ______

General InformationSCD Consulting Office Consultant on Duty 497-1278 CONSULT1Visitor/User Information Frieda Garcia 497-1254 FRIEDAGraphics Software Distribution General Information 497-1201Project & User Number Assignment Rosemary Mitchell 497-1235 ROSEMARYComputing Resource Applications John Adams 497-1213 JOHNADNCAR Switchboard 497-1000

Remote Access InformationUS Telecom (T'elenet) Maria Meehl 497-1301 MARLAInternet Access (TCP/IP) Don Morris 497-1282 MORRIS

Operational InformationComputer Operations Bob Nifenegger 497-1240Machine Room Oper. Supervisor 497-1200Graphics Operations Andy Robertson 497-1241/42Tape Librarian - 1/2" and MSS Sue Jensen 497-1245 SUEDocumentation Orders/Output Mailing Mary Buck 497-1232 MARYB

SENDING ELECTRONIC MAIL: The electronic mail (e-mail) addresses above are for the IBM 4381 (10)front-end computer. The following examples show the addresses for sending e-mail to the SCD consultants.

From the IBM 4381 (10) computer, enter: TO CONSULTIOR

From a host computer connected to the Internet, use a local mailing program with the Internet address:consutl@ncar.ucar.edu

If the Internet address does not work, note that the explicit Internet address is 128.117.64.4 and consult your localsystem administrator.

SCD COMPUTING NEWSScientific Computing DivisionNational Center for Atmospheric ResearchP. O. Box 3000, Boulder, CO 80307-3000

Non-Profit OrganizationU.S. POSTAGE PAIDBoulder / colorado

Permit No. 558

NCAR libraryDIRMesa LabNCARMAIL ROOM