• Keine Ergebnisse gefunden

* Cray IDS

Im Dokument FALL 1985 (Seite 111-116)

*

Apollo - Aegis

Interactive facilities are under development for the following Stations, with availability scheduled as indicated:

*

IBM Compatible - MVS (lQ86)

*

CDC Cyber - NOS (2Q86)

*

Sun workstations - Unix(l) 4.2BSO (l-2Q86)

*

Other Unix-based products-COS (1) Unix is a trademark of AT & T 5. Applicability

From the author's perspective as an operating systems developer, one of the primary uses of COS interactive is that it provides a common Cray environment. This environment exists on almost all front-end systems, including the fairly Spartan surroundings of the check-out floor in the on solving developmental problems rather than learning yet-another editor or command interface.

The other major use of COS interactive is as a development tool. While some developmental activities - most notably long assemblies and

*

Interactive is often appropriate for simulation and debugging of operating system, library, and

6.1 Station Responsibili ties

The front-end station is responsible for collecting interactive input from the user, buffering it into record (line) segments, and forwarding these segments to SCPo

Commands, typically denoted by a command-character in the first column of the line, are intercepted and

SCP is responsible for interactive buffer management. from the system's interactive buffers.

A similar path operates for interactive output. The

7. Sample Interactive Session

One of the uses of COS interactive is the on-line debugging of operating systems or other programs through simulators or interactive debuggers.

The use of shared time, as opposed to dedicated time, for software development can make developers more productive. It also allows more time for the testing of code, which can result in fewer problems later in the development cycle. The sample session in this section is taken from actual code under development in the Mendota Heights facility.

The code segment we will examine is in EXEC, the workstation, using a developmental version of the Unix Station running under Unix 4.2BSD. The

CRAY X-MP SERIAL-20l/40 09/24/85 1.14BF3 COS 1.14 ASSEMBLY DATE 09/17/85 front-end system, and contain account information and other COS control statements to let the user customize the interactive environment. In this session the ias command invokes the interactive station, and the '_if option speci fies that an initialization file is to be executed. The author's ini tialization file contains two di rec t i v es: an ACCOUNT statement, and an ACCESS statement.

The system responds to the logon request with the system header (CRA Y ••• ), reads and executes the ACCOUNT and ACCESS statements, then issues the standard control-statement prompt character, I!'. The user is now free to issue any COS control statements, or issue Station commands.

! audit,id=btk. complicated parameter files are typically created using either a local Cray editor (TEDn or on the

Finall y, the user accesses the COS binary to be PARAMETER FILE CONTENTS:

*INSTALL

*END

? dis a 20073b m=e DIS A 00020073 P EXEC

OSPAR PARAM

0020073 006165 030663 071106 007000 0020074 146370 020660 004453 125100 0020075 000004 073201 054226 055202

<etc.>

? bre,I,20074b,m=e

?

Discussion

CSIM, the Cray Simulator, is invoked. It responds with version and parameter information, then issues its prompts the user by reading from $IN.

2 0415172462013013430465 COS X.15 3 0300711363106313634065 09/23/85 STARTUP IS PERFORMING AN INSTALL Breakpoint 1 encountered at P=00020074h BA=OOOOOOOO

SO 0000000000000000000000 FPS EEX 51 0000000000000000000000 WS NEX 52 0200000000000000000000 lOR DL

53 0000000000000000000003 EMA ICP 54 0000001040000000001000 SVL 55 0000000000000000000001

Eventually, the breakpoint set earlier is encountered.

The user issues the CSIM Station command 'X' to examine the currently-executing exchange package in the simulated system.

?step

TRACE CPU-O P=0002oo74d F3A=OOOoOoOO 51 4,A5 Result reqister 51 = 0000001040000000001000

?step .

TRACE CPU-O P=0002oo75b BA=oooOoooo 52 SRO Result register 52 = 1000000000040000000000

?step

TRACE CPU- 0 P=00020075c BA=OooOoooO 52 52<26 Result register 52=0001000000000000000000

?step

TRACE CPU- 0 P=00020075d BA=ooOooooO 52 52>76 Result register 52 = 0000000000000000000000

?step

TRACE CPU- 0 P=0002oo76a BA=oooOOOOO SO 5152 Result register SO = 0000001040000000001000

?a

DIS A 00020073 P EXEC

0020073 006165 030663 071106 007000 0020074 146370 020600 004453 125100 0020075 000004 073201 054226 055202

<etc.>

? 20074d=126100,m=e

? a

DIS A 00020073 P EXEC

0020073 006165 030663 071106 007000 0020074 146370 020600 004453 126100 0020075 000004 073201 054226 055202

<etc.>

? p=20074d,m=e

?

Discussion

The user begins stepping through the code, one

By the time the last step is reached, something has Result register 51 - 0000000000000000000000

?step

TRACE CPU-O P=0002007Sb BA=OOOOOOOO 52 SRO Result register 52 = 1000000000040000000000

?step

TRACE CPU-O P=00020075c BA=OOOOOOOO 52 52<26 Result register 52 = 0001000000000000000000

?step

TRACE CPU-O P=0002007Sd BA=OOOOOOOO 52 52>76 Result register 52

=

0000000000000000000000

?step

TRACE CPU-O P=00020076a BA=OOOOOOOO SO 5152 Result register SO = 0000000000000000000000

? step

TRACE CPU-O P=00020076b BA=OOOOOOOO JSN 20111a

? step code segment. Note that after the initialS-register comparison (P=20076a), the correct (or at least

THE $DSC-EXTENSION WAS RECOVERED AND VALIDA TED SUCCESS FULL Y.

CREA TING NEW EDITION OF THE SYSTEM DIRECTORY

Simulation time limit exceeded.

? run,t=40

Having successfully tested the developmental code, the programmer elects to let STARTUP run to completion. The initial time limit of 20 seconds is insufficient, but the programmer allocates more time and the simulation then runs to completion. development process in Cray's Mendota Heights facility. Large assemblies and compilations are performed in the background, while interactive sessions are used in the debugging, testing and vali dation of new operating system, library, and applications-level code.

Interactive sessions have available the same command set used in the batch environment, though some limitations are imposed by the lack of interactive JOB statements in the area of resource utilization.

A common scheduler is used for both batch and interactive sessions. Some tuning is possible through the use of the Job Class Manager. Response time to interactive sessi ons is largely controlled by the amount of free memory, and the size of jobs needing to roll out to free memory for interactive sessions.

Interactive Session Example

20103a 1204 00002022 c 1205 00002026 20104a 1006 00035013

c 051224

PSMIDLE,O IDLE CPUs PSMUSER,O USER CPUs PSMDOWN,O DOWN CPUs

XEND+HIGHCPUN,O Max CPU number S2!S4 IDLE and USER CPUs requirements were concerned. However, in relation to user exits, system tuning and installation areas, Kimball (Boeing), Jim Sherin (Westinghouse), Lothar Wollschlager (KFA), Claus Hilberg (ECMWF), Mostyn Lewis (Chevron), Larry Yaeger (Digital Productions), Charles Slocomb (LANL) and Don Mason (CRn.

The Committee discussed the relation between the SIC and CUG sessions, without reaching any conclusions. It was thought desirable to have some overlap between the areas covered by different SICs.

MICROTASKING PANEL SESSION

Im Dokument FALL 1985 (Seite 111-116)