• Aucun résultat trouvé

PROGRAM/SYSTEM INFORMATION RETRIEVAL

Dans le document SPERRY UNIVAC Series 11 00 (Page 169-200)

FILE,*PRINTR FILE,*DISC1,QXYZ

L, U AO,PACKET ER SMUS

4.8. PROGRAM/SYSTEM INFORMATION RETRIEVAL

4.8.1. Retrieving @XQT Control Statement Options (OPT$) Purpose:

Makes available options specified on the @XQT or processor call statement (see 3.4.4).

Format:

ER OPTS Description:

When control is returned, the specified option letters are set in register AO in master bit notation;

that is, letter A sets bit 25; letter B sets bit 24; letter C sets bit 23; ... letter Z sets bit O. Bit 35-26 are always returned as zero.

4.8.2. Program Control Table Retrieval (PCT$) Purpose:

Makes all or specified portions of the information stored in the Program Control Table (PCT) available to the requesting program.

Format:

Two formats are available:

To transfer a maximum of 10008 words starting at word zero of the main block:

L AO,(n,buffer-addr) ER PCT$

~~~~

_________ V_o_l_u_m_e __ 2 __ EX __ E_C ____________________________________

~UP~D_A_TE_L_EV_E_L

____

~P_A_GE

____ ___

To transfer all or part of the PCT starting at any PCT -relative address:

L AO,(O,buffer-addr) L A 1 ,(n,relative-addr) ER PCT$

Parameters:

buffer-addr n

relative--addr

Description:

Address within the program where the PCT is to be transferred.

Number of words to be transferred.

Address relative to the start of the peT main block from which the transfer should occur.

For information concerning the contents and internal format of the peT, refer to the Software Release

DocumE~ntation (SRO). This ER must be used with caution in that Sperry Univac reserves the right to change the content or format of the peT without notice.

An attempt to transfer information outside of the program's peT causes the activity to be placed in error mode with a type 4, error 2 status.

A PCT's size is determined by program requirements with a configurable maximum of 42 main storage blocks (512 words each). The structure and addressing of the peT is illustrated by the following examplHs.

Assume an eight-block PCT:

Reiadd!" 0770000

-block-8

Reladdr 0775000

-block-4 Rei-add!" 0776000 - block-3 Reiadd!' 0777000

-block-2 Rei-add!" 0000000 - main-peT -bllock (1)

Rei-add!' 0000777 - 1 . -_ _ _ _ _ _ _ _ _ _ _ _ - - '

L,U AO,BUFFER

L A 1 ,(02000,0777000) ER peTS

4144.23 UP-NUMBER

SPERRY UNIVAC SERIES 1100 Executive System

Volume 2 EXEC

I

UPDATE LEVEl

This call transfers block-2 and the main-PCT -block, in that order, to the address BUFFER.

L,U AO,BUFFER L A 1,(0500,0100) ER PCT$

I

PAGE 4-36

Transfers 0500 words to BUFFER, starting at relative address 0100 in the main-PCT -block.

L,U AO,BUFFER

L A1,(0100,0777400) ER PCT$

Transfers 0100 words to BUFFER from relative address 0400 through 0477 of PCT -block-2.

4.8.3. Master Configuration Table Retrieval (MCT$) Purpose:

To retrieve information from the Master Configuration Table (MCT) or to read/update the application program area in the MCT. This is a special application ER which is useful only to certain specialized programs. As a result, only those programs which are allowed real-time status are permitted to execute an ER MCT$ which specifies the application area of the MCT. The contents of the MCT are subject to change as new Executive requirements are defined. The current contents and format of the MCT are described in the Software Release Documentation (SRD).

Format:

L,U AO,pktaddr ER MCT$

4.8.3.1. Packet and Call

MCT information may be retrieved or updated by use of ER MCT$. ER MCT$ requires that register AO contain the address of a 3-word packet of the following general format:

00 status unused function

read buffer address code

01 buffer size MCT relative address

name list equipment number of

write buffer address class entries

02

Word 0

status Returned by ER MCT$ (see 4.8.3.4).

function code See 4.8.3.2 and 4.8.3.3.

~~~

________ ._V __ o_lu_m __ e __ 2 __ E_X_E_C __________________ . ______________________

~_up_D_A_TE_L_E_VE_L

____

~_P_AG_E_-

____ __

buffer read address Word 1

buffer size

MeT relative address

Word 2 name list equipment class number of entries write buffer address

4.8.3.2. Read Functions

Address of read buffer. Used only for read functions.

Read or write buffer size in words.

Word address relative to start of MCT. Used only for function code 3.

Number of words per entry for name list entries.

MCT equipment class found in logical name index entry.

Number of entries in input list; functions 5, 7, and 8.

Address of write buffer used for write functions or address of name list.

The following function codes (decimal) are defined for reading MCT information:

~.---.----~--.---.

Code Function

~.---.----4_--.---~

o Read MCT Pointer Table into buffer provided by the caller.

Read MeT Application Area into a buffer provided by the caller.

Read specified number of words beginning at specified MeT relative address into a buffer provided by caller.

NOTE:

This function code reads the MeT excluding the Application Area. If the request includes the Application Area, an error code of 4 is returned.

5 Read the specified number of MCT logical name index entries into a buffer provided by caller.*

6 Read MCT logical name index entries of a given equipment class codE: into a buffer provided by the caller.

7 Read a specified number of MeT List Entries into a buffer provided by caller. See code. 5.

8 Same as code 5 except equipment class code must be given in S2 of word 2 of packet. and name list entry word 0 contains a Transition Unit position word.

1 () Read the MeT System 10 Table into a buffer provided by the caller.

11 Road the MeT Time and Date Area into a buffer provided by the caller.

1 :2 Road the MeT I/O Section into a buffer provided by the caller.

4144.23 UP-NUMBER

Code 13

14

15

16

17

18

SPERRY UNIVAC SERIES 1100 Executive System Volume 2 EXEC

Function

UPDATE LEVEL

Read MCT BCA (Bootstrap Communication Area) into a buffer provided by the caller.

Read the MCT XER History Entry Table into a buffer provided by caller.

4-38 PAGE

Read the MCT Tape Translator Mnemonic/Index Conversion Table into a buffer provided by the caller.

Read the MCT Mass Storage 10 Table Section into a buffer provided by the caller.

Read MCT Console Configuration Section into a buffer provided by the caller.

Read MCT Equipment Mnemonic Table into a buffer provided by the caller.

*

A name list containing the logical names of the desired logical name index entries is provided by the caller. The name list has entries of 2 or more words (as specified in S 1 of packet word 2) with the logical name appearing in word 0 of each entry. In the event an entry's logical name can not be found in MCT, a 1 is returned in S 1 of word 1 of the entry in addition to a status of 32 in the packet status cell.

For EXEC callers only, an extra word is supplied following each logical name index entry in the caller's buffer. In H2 of this word is the address of the logical name index entry relative to the start of the I/O section of the MCT.

For all read functions, the read buffer size must be given in H 1 of word 1 of ER MCT$ 3-word packet.

4.8.3.3. Write Functions

The following functions are defined for writing MCT information. Only EXEC activities may use the functions with exception of writing of Application Area (59).

Code Function

2 Write the contents of a caller buffer into the Application Area of MCT.

40 Write the specified number of LNIEs in caller buffer back to their respective addresses in the MCT.

Each LNIE in caller buffer must be followed by its address relative to the start of the MCT I/O section.

41 Write the specified number of List Entries in caller buffer back to their respective addresses in MCT.

Each List Entry is caller buffer must be followed by its address relative to the start of the MeT I/O section.

50 Write contents from caller provided buffer to MeT System 10 Table.

51 Write contents from caller provided buffer to MeT Time and Date Area.

52 Write contents from caller provided buffer to MeT I/O Section.

53 Write contents from caller provided buffer to MeT Bootstrap Communications area.

54 Write contents from caller provided buffer to MCT XER History Entry Table.

55 Write contents from caller provided buffer to Tape Translator Mnemonic/Index Conversion Table.

~~~ _________ V __ o_l_u_m_e __ 2 __ E_X __ E_C _________________ . ________________________ ~_up_D_A_T.E __ LE_V_EL ____ ~P_A_G_E ___

Code Function

56 Write contents from caller provided buffer to MCT Mass Storage 10 Table.

57 Write contents from caller provided buffer to MCT Console Configuration Section.

58 Write contents from caller provided buffer to MCT Equipment Mnemonic Table.

59 Write contents from caller provided buffer to Audit Trail Table.

60 Write contents from caller provided buffer to MCT Application Area.

For write functions, the write buffer size must be given in H 1 of word 1 of ER MCT$ 3-word packet.

4.8.3.4. Error Codes

Error conditions are reported to ER MCT$ callers in S 1 of Word 0 of the caller provided 3-word packet

Code Function

The caller provided read buffer information failed a storage limits check.

2 Thf3 caller has provided an illegal function code.

3 Th43 caller is attempting to read/write MeT Application Area without being allowed real-time status.

4 The request is partially completed.

NOTE:

This status may be returned for various reasons; for example, the caller provided read buffer is too small to contain requested information.

6 The MeT I/O section relative address provided on write of logical name index entry or list entry does not fall within I/O section of MeT or relative MeT address provided on read with offset (function code 3) does not fall within MeT.

7 The caller provided write buffer information failed a storage limits check.

8 The caller provided function code does not exist.

9 An I/O error was encountered on read/write of MeT information.

NOTE

Further ER MCT$ requests are ignored until a reboot is performed.

32 The provided Name List contains input that cannot be found in the MeT. See function code 5.

4144.23 UP-NUMBER

SPERRY UNIVAC SERIES 1100 Executive System

Volume 2 EXEC UPDATE LEVEL

4.8.4. Bank Descriptor Index Retrieval and Common Bank Reload (BANK$)

4.8.4.1. BDI Retrieval Purpose:

4-40 PAGE

BANK$ is a multipurpose ER designed to allow the user to obtain varying kinds of information pertaining to a specified bank.

Format:

The BANK$ calling sequence is:

L AO,parameter ER BANK$

Description:

The various functions and parameter formats for BANK$ are as follows:

1. parameter= length,address

Retrieves the BOI of the bank containing the program relative address furnished on the call. Also retrieves information concerning write protection, PSH base, 1- or O-bank address, and a nonconfigured common bank indicator. The length parameter, when added to the initial address parameter, defines the highest relative address of the area for which the BOI is to be returned.

If a zero length is specified, a value of one is assumed. The length cannot be longer than 131071. To handle lengths larger than this, several successive checks must be done. A status is returned in AO in the following format:

Bits 0-11 Bits 12-14 Bit 15 Bit 16 Bit 17 Bit 18 Bit 19 Bit 20 Bit 21

The BOI Zero

1 if the bank is dynamic

1 if bank based on Bo of the PSR if EXEC (common) bank

if mapped as aD-bank

if bank is under utility PS R base (1110, 1100/40, 1100/80 only) if bank is write protected

if bank is nonconfigured common bank

If AO = 0, the address range passed was totally or partially outside the user's window.

The algorithm used to determine if the user's address or address range is within limits is quite similar to the hardware check for an in-limits address, the only exception being that the hardware checks one address at a time, while the software checks a series of contiguous addresses. For 1110, 1100/40, 012 of the main PSR is checked to see which PSR is active (012 = 0 = main PSR, 012 = 1 = utility PSR). After determining the active PSR, the following order of checking against the storage limits is made:

a. Starting address against active PSR's I-bank SLR b. Starting address against active PSR's O-bank SLR c. Starting address against inactive PSR's I-bank SLR

~~~

_________ V_o_l_u_m_e __ 2 __ E_X_E_C ____________________________________

~_u_pD_A_TE_L_EV_E_L

____

~~_A_G_E-

____ __

2.

d. Starting address against inactive PSR's D-bank SLR

Since a USE~r may have up to four banks (1110, 1100/40, 1100/80 only) active in the program, th,ere exists the possibility that the relative starting address passed on the ER call may exist in more than one bank. However, the first storage limit that includes the relative starting address is used and if the entire address range specified on the call (assuming length 1- 1) is not within however, the request would have passed, as the access word is contained totally within the utility D-bank.

R:etrieves storage limits, dynamic/static bit, I-bank/D-bank bit, verified-guaranteed-entry bit, write-protect bit, and guard-mode-protect bit for the bank pointed to by the BDI supplied. The BDI may point to either a common bank or a user program bank. On return to the user, AO

4144.23

UP-HUMBER

SPERRY UNIVAC SERIES 1100 Executive System

Volume 2 EXEC I UPDATE lEVEL

I

PAGE 4-42

contains the upper storage limits in the left half and the lower storage limits in the right half, expressed as 18-bit word addresses. A 1 contains the rest of the information, formatted as follows:

where:

R = dynamic W = write protect P = guard mode

V = verified (guaranteed) entry N = nonconfigured bank D = D-bank

The remaining bits of A 1 are set to zero.

4. parameter = 1*/17+2,BDI

Changes a program bank type from dynamic to static. For this request the caller must have the bank based at the time of the request. If the bank is found to be already static, control is returned to the user with no user action taken. The BDI may not point to a common bank.

5. parameter = 1*/17+3,BDI

Changes a program bank type from static to dynamic. For this request, it is not necessary that the caller have the bank based at the time of the request. If the bank is found to be already dynamic, control is returned to the user with no action taken. The BDI may not point to a common bank.

4.8.4.2. Common Bank Reload Purpose:

To reload a common bank from LlB$ or a common bank file.

Format:

L AO,(Reload Type, BDI) ER BANK$

or

L AO,(Reload Type, PKT ADDR) ER BANK$

where:

Reload Type See Table 4-2

BDI Bank Descriptor Index of the bank to be reloaded

~~~~

________ V __ o_lu_m __ e_2 ___ E_X_E_C ____________________________________ -LU_P_D_AT_·E_LE_V_EL ____

~P_AG_E

____ __

PKT ADDR

00

01

02

where:

stall time

bank-name

Description:

Three word packet as follows:

stall time SDI

bank-name

bank-name

Length of time (in minutes) allowed for common bank to become available for reload. If time is exceeded, request is ignored and control returned to user.

Either bank-name (for S option bank) or element name (see 4.11.1.1 on D option common banks).

User's )\0 is returned with 0 if reload was successful. If the stall time was exceeded, AO is returned unchan'ged and control is returned to the user. All other errors causes the user to be placed in error mode (Contingency Type 12, Error Type 10).

The following restrictions apply to usage of the different request types:

1. An immediate request must be issued from the common bank to be reloaded. This restriction does not apply when the bank to be reloaded is a nonconfigured common bank.

2. An activity making an error type request must have the reload bank based.

3. An activity making a stall request must have the bank based or have the common bank file containing the bank assigned with correct keys.

The stall reload request with buffer input (Type = 0400007) allows the user to change the stall time and use a bank name if the reload SDI is not known. A system standard stall time is used if that cell is zero. If the SDI cell in the PKT is nonzero, bank-name is ignored regardless of its value.

4144.23 UP-NUMBER

Reload Type

SPERRY UNIVAC SERIES 1100 Executive System Volume 2 EXEC

Table 4-2. Common Bank Reload Type

Description

I

UPDATE LEVEL

I

PAGE 4-44

0400004 Immediate Reload. Activities having this bank based are not notified that a new copy of the bank has been loaded.

0400005 Error Request. All activities with bank based are put in ERR mode and given a contingency (Type 04) if registered.

0400006 Stall Request With Register Input (First Format). Reload is not started until all tasks currently having access to the common hank terminate.

0400007 Stall Request With Buffer Input (Second Format). This is the only type that may use PKT Address in AO.

4.8.5. Software Instrumentation Package (SIP) Interface (SYSBAL$) Purpose:

To provide the capability to turn SIP on and off from a user program, and to retrieve the SIP data collected while it was on. In general, all of the SIP options available to the console can be performed via the ER SYSBAL$.

Format:

L,U AO,pktaddr ER SYSBAL$

Parameters:

pktaddr Example:

00 status

01

02 return data

03

04

Address of SYSBAL$ ER packet

SYSBAL$ ER Packet

pkt-Iength unused function code

input data

user-buffer-Iength user-buffer-address

time-of-day

~~~~ ____________ V ___ o_lu_m ___ e __ 2 __ E_X_E_C ______________________________________________ ~u_p_D_A_TE_L_E_VE_L ____ ~P_A_G_E ____ ___

Word 0

status The following status returned:

ER SYSBAL$ Status

Value Meaning

00 Function completed normally

01 Console has control of SIP

02 Console took control of SIP

03 SIPlTrace feature not configured

04 SIP active from console or other user, cannot set auto mode

010 Console has control of 10 Trace in manual mode

011 Console has control of 10 Trace and SIP

012 Console has control of 10 Trace and took control of SIP

020 Console took control of 10 Trace in manual mode

021 Console took control of 10 Trace and has control of SIP

022 Console took control of 10 Trace and SIP

030 SIP could not be initialized

031 Data requested not available

032 FLGON/FLGOF is not allowed

040 Failed quota bit test/function not allowed

041 Illegal function code

042 Buffer limits out of range

043 Buffer not large enough

044 SIPlTrace not turned on by this user

045 Bad value in SIP request

NOTE:

Nonzero status should be examined by the user to determine how to continue. Negative status indicates a user error.

4144.23

UP-NUMBER

SPERRY UNIVAC SERIES 1100 Executive System

Volume 2 EXEC

ER SYSBAL$ Function Codes

Code Function

NOTE:

if QUotlJl Level 4 is configured, the functions in each Quota control group can be performed by a particular user only if the proper bit has been set by the Installation Manager in the User's Quota Set Description Words. If Quota Level 4 is not configured, there is no such restriction.

Word 1 input data Word 2 return data

User input for FLGON and FLGOF functions is in the user-buffer. User-buffer-Iength indicates the numbe'r of flags to be changed. Flag mnemonics in Fieldata, left-justified in the user buffer, indicate which flags to change.

Mnemonic ALL MIS 10 MEM CAU RSP

FJ~C

FI\JC EXP COM OTM

Data All data collection

Miscellaneous; runs open, in core, interrupts, ERs I/O activity

Memory utilization, DA activity CAU utilization

DA, Demand Response Facility usage

Function loader activity

"EXPOOL usage

Communications activity Dispatcher quantum

Flags may not be changed during a SIP collection. A status of 032 is returned in the user packet if a flag change is requested while SIP is on.

[Flag values set by a user do not remain in effect after the user turns SIP OFF (or it is turned off from the console). Values in effect before the user FLGOI\J-FLGOF functions are restored when SIP is turned off.

SIP status for function 031 (STATUS) is returned in words 1 and 2 of the user packet.

SIP Status Return

01 collection flags

::-TSIP/trace trace on/oH output time internal unuse

(second granularity)

I

status

02

4144.23

SPERRY UNIVAC SERIES 1100 Executive System Volume 2 EXEC

To retrieve the jump history which is captured by the system upon the occurrence of a hardware fault interrupt. transferred. This area must be a minimum of the length of the number of jumps to be edited. If a length of zero is specified, the minimum length of the area must be four. (A maximum of four jumps may be captured on the 1110, 1100/40 System, and eight on the 1100/80 System.)

~~~~

_________ V_o_lu_m __ e_2 __ E_X_E_C __________________________________

~_U_PD_A_TE_L_EV_E_L

__

~~P_AG_E

____ __

Description:

The EXHcutive mturns the active BDI and program relative address for each jump in H 1 and H2 of each word of the buffer respectively. If the absolute jump address is not within program limits, a

The EXHcutive mturns the active BDI and program relative address for each jump in H 1 and H2 of each word of the buffer respectively. If the absolute jump address is not within program limits, a

Dans le document SPERRY UNIVAC Series 11 00 (Page 169-200)