KEYPOINT DESCRIPTION FILE

---._---01.3.2 KEYPOINT DESCRIPTION FILE

The keypolnt descriptions are used by the keypoint analyzer utility to direct the reformatting of the keypoint information.

Each area has a keypoint constant deck xxOKEY (where ~x

Is the product idle The keypotnt descriptions are now included In this deck Immediately following the keypoJnt constants (slmiliar to the message templates).

Each description has the fo.lowing format.

Note: each element ( I f given) is positionally dependant.

CLASS of keypoint - required E En tr y

X eX i t

U Unusual

o

Debug

SUB_ID_FIELD - optional - (described later)

KEYPOINT_lABEl - required - This is a string that describes the purpose of the keypoint.

DATA_LABEL - optional - This Is a string of up to 8

characters describing the data portion of the keypoint.

DATA_FIELD_DESCRIPTOR - optiona' - This consists of data format and length.

data_format

H Hex

I Integer (decimal) A A.SCII

Concatenated to this Is the length of the data portion of the keypolnt, In decltral bits.

For example: 120

NOS/VE BACKGROUND DOCUMENTS

10126/82 01.0 KEYPOINTS

01.3.2.1.1 EXAMPLE KEYPOINT OECK

N N N N N N N _ N _ N N N N N N N N N N N N N N N N N N w N N N N N N N N N N N N N N N N N N _ N N N N N N N N N N N N N N N _ _ NNN

01.3.2.1.1 EXAMPLE KeYPOI~T DeCK STOKEY

COMMON { PURPose:

{ Th Is deck contal ns al. of the set manager keypoi nt constants.

CONST

stkScreate_set : stk$base + 1,

{E 'stpScreate_setl 'ring • H}

{X 'stp$create_set ^I 'status t 120 } stkSpurge_set

=

^{stkSbase + 2,}

{E 'stp$purge_set' }

{X 'stp$purge_set' 'status '120}

stkScant_dm_store_set_ord

=

^stkSbase,

{U 'cant dmp$store_8vt_set_ordlnal' 'avtindx ' H20 }

stkSpf_root_size

=

^{stkSbase + 5;}

{O 'pf _root_s ^I ze' 'root s I z • H20 } I? PUSH (LIST :. OFF) 11

{*c a II c osdkeyd 1? POP??

This optional field alleMS ⁸ means of subdividing a single keypoint Into several descriptors. The particular descr Iptor is chosen on the basis of a selectable number of bits of the data field. This field has the followjng format:

SUB_10_LENGTH - This specifies the number of bits (right most) of the data field to use, to determine which

descriptor to choose.

SUB_10_MATCH - This specifies the integer Identifier used to

match the data portion.

Example:

mmk$page_fault : mmkSmcnitof_base + 6, {E 'page fault processor' }

{E 4.1 'Page found in avail queue' 'pfti ^t H16}

{E 4.2 'Page 'ound In avail modi,jed queue' 'pftl ^t H16}

MOS/VE BACKGROUND DOCUMENTS

10/26/82 01.0 KEYPOINTS

01.3.2.1.2 SUB_ID_FIELD NN _ _ _ _ N _ N N _ _ N _ _ _ _ _ _ _ _ _ _ N _ _ _ _ _ N _ _ _ _ N _ _ _ _ _ N _ _ _ _ _ _ _ _ _ _ _ _ _ NN _ _ _ _ NNN _ _ N _ _

If this keypoint was Issued and produced data of 2, the descriptor with the sUb_id_match field of 2 would be used (tpage found in avail modified queue' ).

These keypoints were issued with a sub_id_length

=

4, thus the 4.x. for example:

#INLINE (tkeypoint', oskSentry, oskSm

*

(pfti

*

^{16 {2}

**

sub_ld_length} + 2{sub_id_match}}, mmk$page_fault)j

The keypolnt descriptions are kept on 8 file called KEYOESC on the Integration catalog. This ftle may be produced by:

SES.GENCOMP M=OSMKEYS AS-«NOSVEPl,OSlPI,INTZ») CF=KEYDESC

The user may add keypolnts to her xxOKEY deck locally, and the KEYDESC f'Ie may be produced as above, specifying the additi onal local bases. The KEYOESC ^{f i} I e may then be saved

on her catalog.

If new keypoint decks are added, *catlc 's to these new decks chould be added to the deck OSMKEYS, and the appropriate

base constants added to deck OSOKEYD.

When transmitting changes to keypoint decks, be sure to inform Integration, via the transittal form, to recreate the fi Ie

KEYDESC.

This section wl'l only be useful to those desiring to add additional keypolnt classes, keypolnt class base constants, or new keypoint description decks.

The classes, Identifiers, and descriptions are each buffered

by a comment. for example, to add another keypolnt class:

{$$$ START KEYPOINT CLASSES $SSl CONST

pskSentrya osk$product_set_class + 1; {E PS - entry keypoint}

{$$$ END KEYPOINT CLASSES ^{$$$ }}

note: The E follwoing the "{" wi II be used in the description.

NOS/VE BACKGROUND DOCUMENTS

10126/62 01.0 KEYPOINTS

01.3.2.3 osmkeys format

_ R N N N _ N N N N N _ _ ~NNNNNNN_N_NN_N_NNNNN_N _ _ _ N_NN _ _ N N _ N _ N N _ _ _ _ NNNNN _ _ _ _ NNN

This new section should be appended to the end of the KEYDESC file. Readers desiring mere information should reference the attached BMF, and the attached decks OSMKEYS.

The following represents a sample of how to set up the description module.

Note: Comment put around *c811 for sake of documentation only.

{SIS START KEYPOINT DESCRIPTIONS SSS}

{*callc,amdkey

NOS/VE BACKGROUND DOCUMENTS 01.0 KEYPOINTS

01.3.2.3 osmkeys format

10/26/82

_ N _ _ _ _ NNN _ _ _ _ _ NNNN _ _ NMN _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ N _ _ _ _ _ N _ _ _ N _ _ _ _ _ _ _ NN _ _ _ _ _ _

{*ca.tc,tmdJkey {*eal' c, jsdmkey {*eal' c, JsdJkey

{* c a I • c, av dk ey {*cal' c, sfdkey {*cat Ie, iodkey

{*eall c,rmdkey

{$$$ END KEYPOINT DESCRIPTIONS $S$}

MODEND keypolnt_descrlptl~n_flle;

The output from procedure NVEKEY Is a file called KEYfllE.

This reformatted listing contains two sections. The first

section Is a listing of all the keypoints In the order they were Issued. The second section is a summary of the number of times each keypotnt occured.

Each .Ine In the first section has the following format;

The RT field designates the value of the free running

microsecond clock (time since deadstart) when the keypoint was executed. On the simulater the clock is incremented by 1 for each instruction executed.

The 1SL field designates the time (microseconds) since the last keypolnt instruction was executed.

The DATA field specifies the value of the data portion of the keypoint in the format described in the keypoint description file for this keypoint.

The DATA_LABEL field Is the data 'abel field from the keypoint description file for this keypoint.

This Identifies the data being displayed.

The S field specifies the state of the machine when the keypoint was Issued and is one of the following:

M - Monitor mode

J - Job mode

An

*

preceding the S field Indicates that

trap processing Is active, that is the trap handler has

NOS/VE BACKGROUND DOCUMENTS

10/26/82

01~O KEYPOINTS

Dans le document lists It (Page 100-105)