top - download
⟦6d2cd9d64⟧ Wang Wps File
Length: 37131 (0x910b)
Types: Wang Wps File
Notes: STP DESIGN SPECIFICATION
Names: »1003A «
Derivation
└─⟦b282628ca⟧ Bits:30006035 8" Wang WCS floppy, CR 0059A
└─ ⟦this⟧ »1003A «
WangText
…07……00……00…?…0a…?…0b……00……00…?…0c…?…0f…?
? ?…05……1c……0a……1c……0c……1c……0d……1c……02……1c… …1c……05……1c……06……1b……09……1b……0a……1b……0f……1b……00……1b……05……1a……09……1a……0a……1a……0e……1a……0f……1a……00……1a……01……1a……02……1a…
…1a……07……19……0b……19……0f……19… …18……08……18……09……86…1 …02… …02… …02… …02…
…02…CPS/SDS/008
…02…RIM/810801…02…
STP DESIGN SPECIFICATION
…02……02…CAMPS
4̲ ̲ ̲P̲A̲C̲K̲A̲G̲E̲ ̲D̲E̲S̲I̲G̲N̲
This chapter includes the description of the package
design. Chapter 2, Summary of Requirements and 3, Interfaces,
serve as baselines for chapter 4 Package Design.
4.1 P̲A̲C̲K̲A̲G̲E̲ ̲O̲V̲E̲R̲V̲I̲E̲W̲
Processing procedures and related data areas constituted
by STP are shown overleaf. Applications are packages
such as THP, MDP etc. which contribute with information
for the production at hourly, daily and weekly printout
of statistics. CSF statistics generator acts as an
overall tool for accumulation of input information.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Applications Delivering data records to
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ statistics collector by
applications at time of occurence
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Statistics
Collector
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ Transfer of data records to shared
data area by statistics collector
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Shared data
area
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Dump Transfer of 6 minutes data
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ intervals to statistics dump
area
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
STP
dump
a̲r̲e̲a̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
STP Generation of hourly statistics,
dayly statistics and weekly
Generators statistics
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲
STP
f̲i̲l̲e̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Statistics Delivery of generated statistics
delivery information to statistics printer
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Temporary
I̲t̲e̲m̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
…01…Data transfer and related programs
Figure 4.1-1
4.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
4.1.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲B̲r̲e̲a̲k̲ ̲d̲o̲w̲n̲
STP main functions are divided into 4 lower level functions
as depicted below.
STP FUNCTIONAL BREAKDOWN…01…FIGURE 4.1.1.1-1…86…1 …02… …02… …02… …02…
The four functions perform the following:
- Statistics collection
Statistical information collection by CSF into
the shared data area
- Statistics dump
Dump of shared data area every 6 minutes to the
statistics dump area.
- Statistics generation
Generation of hourly statistics information from
statistics dump area. Generation of daily and weekly
statistics information.
- Statistics delivery
Return of statistics information hourly, daily
or weekly upon time-out from CAMPS System Function
timer-monitor.
4.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The software structure of STP consists of a monitor
procedure, a main program and three procedures. Main
program takes care of activating the procedures. Main
program and procedures are contained in one process.
Figure 4.1.2-1 shows the STP software structure. The
lower level description is separated according to high
level software structure, i.e. following sub-packages
exist:
- collection sub-package
- main program sub-package
- dump sub-package
- generation sub-package
- delivery sub-package.
4.1.2.1 M̲o̲n̲i̲t̲o̲r̲ ̲P̲r̲o̲c̲e̲d̲u̲r̲e̲
This statistics collector takes care of updating the
statistics area used for collection. This software
component performs the function statistics collection
as described in paragraph 4.1.1.1.
4.1.2.2 M̲a̲i̲n̲ ̲P̲r̲o̲g̲r̲a̲m̲
The main program takes care of activating the following
activities according to the receiving time-out QEL
or storage occcupancy request QEL.
STP Overview Software Structure…01…Figure 4.1.2-1…86…1 …02… …02… …02… …02…
4.1.2.2.1 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲D̲u̲m̲p̲
The dump statistics software is activated periodically
in order to transfer data from SDA, data section, to
STP file interval section. Software performs the functions
outlined in 4.1.1.1.
4.1.2.2.2 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲
Statistics generation software consists of a procedure
generating the hourly, daily, and weekly statistics.
4.1.2.2.3 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲
Handles the activity of delivering the statistics to
TEP when the procedure is activated by the main program.
TEPs request for storage occupancy is also handled
by this procedure.
4.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
Data flow and control for STP is sequential and therefore
presented in HIPO diagrams.
Overleaf is shown the package overview HIPO diagram
containing the 5 sub package functions:
- statistics collection
- main program
- statistics dump
- statistics generation
- statistics delivery
Explanation to subtext.
Diagram ID
- Diagram identification identifies the number of
the diagram and explain the diagram page out of
the total number corresponding to the diagram number.
Name.
- STP: statistics package
- SP: subpackage
- PD: preliminary design
Description.
- Description of the contents of the diagram.
Contents of HIPOs.
Process step description.
FIGURE…01…(Input - Process - Output)
FIGURE…01…(Input - Process - Output)
4.1.4 P̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
Common data shared between subpackages are:
- shared data area
- statistics file area
4.1.4.1 S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲A̲r̲e̲a̲ ̲(̲S̲D̲A̲)̲
This area is shared between the statistics collection
function and statistics dump function.
The structure of SDA is shown overleaf in figure 4.1.4.1-1.
Table area contains information about the group data
elements in the data area. Contents of table area is
permanent, except when actual CAMPS configuration is
changed. SDA is a main memory resident area addressed
via operands in instructions.
FIGURE 4.1.4.1-1…01…Shared Data Area Layout
4.1.4.1.1 T̲a̲b̲l̲e̲ ̲A̲r̲e̲a̲
The collection of statistics information is table conducted,
i.e. when application request storage of statistics
STP collection consults the table area for determination
of location in data area where data shall be stored.
Included is the procedure identification used in updating
the addressed subfield.
Below is listed the parameters contained in this area
a), their corresponding syntax b) and possible description
c).
a) A̲d̲d̲r̲e̲s̲s̲i̲n̲g̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
- No of groups: indicates number of statistics
groups.
- Group N address: indicates the starting address
of group description in table area.
- Data start addr: indicates the starting address
of the below data area.
- Data area size: indicates the size of the below
data area.
- No of subgroups within the group, e.g. number
of formats per terminal.
- No of fields: indicates number of fields within
a record.
- Record length: indicates the record length
of each record in data area.
FIGURE 4.1.4.1.1.1-1…01…Shared Data Area (SDA)
- No of records: indicate the number of records
in the group, i.e. number of terminals or channels
etc.
- Group start addr.: indicate the starting address
of the data area of the corresponding group
- Field N descriptor: indicate the format and
processing procedure on the subfields. Each
field descriptor is of fixed length.
b) S̲y̲n̲t̲a̲x̲ ̲o̲f̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
- No of groups: integer
- Group N address: integer
- No of subgroups: integer. If no subgroups are
present this parameter shall be 1.
- No of fields: integer
- Record length: integer
- No of records: integer
- Field N descriptor: 3 integers.
First integer indicates the number of bytes in
the subfield.
Second integer indicates the number of subfields
within the field. If no subfields, value is 1.
Third integer indicates the procedure to be used
on the subfields. Procedure identification identifies
collection procedure.
c) D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲o̲f̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
No. of groups: a group is related to the type of
statistics, i.e. incoming messages per channel,
outgoing messages per channel, message distribution
per terminal, etc.
No. of sub-groups: a sub-group is related to the
statistics generated for use at a terminal format,
e.g. format A, B, G2 etc.
Here, group is the sub-groups i.e., formats, related
to the terminal.
Record: entry in a sub-group area containing statistics
about a channel or terminal.
Field: each record consists of a number of fields.
A field contains statistics parameter information
such as accumulated number of messages received,
summarized message length etc.
Sub-field: a field may possibly be partitioned
into sub-fields which, for example, can be of different
precedence levels or classification categories.
Field N description: refer to figure 4.1.4.1.1.1-2
which describes the format of the record and accumulating
procedure to be used on the sub-field.
FIGURE 4.1.4.1.1.1-2…01…Record Layout, example
4.1.4.2 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲F̲i̲l̲e̲ ̲A̲r̲e̲a̲
As shown on figure 4.1.4.2-1-4, the statistics file
area consists of a contiguous file, created prior to
STP initialization. The major sections which are contained
in the file are:
- STP file information area
- Statistics dump area
- Statistics data area
4.1.4.2.1 S̲T̲P̲ ̲F̲i̲l̲e̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲ ̲A̲r̲e̲a̲
This area is placed in the beginning of the file from
byte address no. O. Area contains looping and processing
information used during generation of hourly, daily,
and weekly statistics. Further local recovery information
is contained.
4.1.4.2.2 S̲T̲P̲ ̲D̲u̲m̲p̲
As shown on figure 4.1.4.2.2-1 this area consists of
10 areas each containing statistics for a time interval
of 6 minutes. Each time interval area is an exact copy
of the data area in SDA previously described in paragraph
4.1.4.1.
FIGURE
FIGURE
FIGURE
FIGURE 4.1.4.2-1…01…Statistics File Area Layout
FIGURE 4.1.4.2.2-1
This area is on-line disk resident and is accessed
via the file system. Instructions used on the contiguous
file are such as:
Append bytes, read bytes, and modify bytes.
4.1.4.3 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲D̲a̲t̲a̲ ̲A̲r̲e̲a̲
The contents of this area are three smajor sections,
hourly, daily and weekly section. These sections are
contained in the same contiguous file as the above
mentioned dump area.
4.1.4.3.1 H̲o̲u̲r̲ ̲S̲e̲c̲t̲i̲o̲n̲
Consists of 24 equal hour intervals containing the
accumulated hourly information.
4.1.4.3.2 D̲a̲y̲ ̲S̲e̲c̲t̲i̲o̲n̲
This area consists of 7 equal day sections, each produced
based on the 24 hour sections. Layout of this section
is identical to the hourly section.
4.1.4.3.3 W̲e̲e̲k̲ ̲S̲e̲c̲t̲i̲o̲n̲
Contains statistics information for the last week.
The section consists of 1 area identical to 1 area
of the above mentioned hour or day areas.
4.1.5 E̲x̲t̲e̲r̲n̲a̲l̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
The external data elements shared with other packages
are:
- data records delivered by applications containing
the statistics information to be accumulated.
- statistics information produced by STP upon delivery
to every 24-hour at midnight.
4.1.5.1 A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲s̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
Each data record delivered by applications upon request
of statistics collection has the following parameters:
- statistics group number
- statistics subgroup number
- statistics record number and
- a number of parameters
The use of these parameters are described in subpackage
1 Statistics Collection.
Statistics Data Record Delivered by Application
Statistics Stat. Stat. Statistics
Group Sub- Record Parameters
number number number
A B C
4.1.5.2 S̲T̲P̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲ ̲D̲a̲t̲a̲ ̲E̲l̲e̲m̲e̲n̲t̲s̲
Items are the result of a periodic statistics delivery
to TEP. The item is sent via queue element to statistics
print queue. Request of storage occupancy results in
a send reply function call, i.e. a queue element is
sent to requestor.Layout of each item (is described
in 4.3.2). Format of one hour statistics is identical
to day and week statistics.
4.1.6 I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
This subsection contains the description of STP interfaces
such as:
- external interfaces
- package interfaces
- subpackage interfaces
4.1.6.1 E̲x̲t̲e̲r̲n̲a̲l̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Not applicable
4.1.6.2 P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
STP interfaces to other packages are divided into 2
categories.
- Packages interfacing during collection of statistics
information
- Packages interfacing during delivery of statistics
information
4.1.6.2.1 C̲o̲l̲l̲e̲c̲t̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Category one interface is shown on figure 4.1.6.2-1.
Application calling the collect monitor procedure includes
a pointer referencing the parameters to be used during
collect. Specific input parameters delivered by the
application packages are described in detail in appendix
A.
Input parameters upon a statistics collection are as
follows:
- statistics group number
- statistics subgroup number
- statistics record number
- statistics parameters
4.1.6.2.1.1 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲S̲u̲b̲-̲G̲r̲o̲u̲p̲ ̲N̲u̲m̲b̲e̲r̲
Indicates which of the groups in the data area to be
updated.
4.1.6.2.1.2 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲G̲r̲o̲u̲p̲ ̲N̲u̲m̲b̲e̲r̲
This number is different from 1 if subgroup determination
is necessary during the shared data area update. Examples
of using this mechanism are when TEP request generation
of statistics concerning use of formats.
4.1.6.2.1.3 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲R̲e̲c̲o̲r̲d̲ ̲N̲u̲m̲b̲e̲r̲
Number indicates the involved device. Devices in question
are channels, terminals etc.
4.1.6.2.1.4 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲s̲
Parameters used for the actual calculation and accumulation
of the statistics information in the shared data area.
4.1.6.2.2 D̲e̲l̲i̲v̲e̲r̲y̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Second category includes TEP, CSF and MMS. TEP requests
storage occupancy using the function request call mechanism.
STP returns answers by calling send reply function
call. STP uses the function request method in obtaining
the storage occupancy from MMS.
Delivering statistics to TEP is achieved by sending
a QEL to the statistics printer queue. QEL references
the CIF containing the statistics information. Category
one interface is shown on figure 4.1.6.2-1. Category
two interface is shown on figure 4.1.6.2-2.
FIGURE 4.1.6.2-1…01…Package Interface, collecting statistics
FIGURE 4.1.6.2-2…01…Package Interface, delivering statistics
4.1.6.3 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲
Statistics collection sub-package interfaces to statistics
dump sub-package. Interface active upon transferring
information from shared data area to statistics dump
area as shown on figure 4.1.6.3-1.
Statistics dump sub-package interfaces to statistics
generation sub-package. Active once per hour when hourly
statistics is generated based on the information contained
in the statistics dump area. Figure 4.1.6.3-2 describes
this action.
Statistics delivery sub-package interfaces to statistics
request sub-package. Connection is via the generated
hourly, daily, and weekly statistics elements which
are fetched by subpackage 4 and handed to TEP. Refer
figure 4.1.6.3-3.
Statistics main program sub-package interfaces to the
dump, generation and delivery sub-packages. Interface
is active when main program has received a time-out
or request QEL and the corresponding action shall be
initiated. The actions are then performed by each of
the above mentioned sub-packages. Refer figure 4.1.6.3-4.
FIGURE 4.1.6.3-3…01…Sub-package 1.3 to 1.4 interface
4.2 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲s̲
The subpackages 1.1 to 1.5 are each described during
the subsections 4.2.x, 1 x 5 following next.
4.2.1 C̲o̲l̲l̲e̲c̲t̲i̲o̲n̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
The collection subpackage performs the collection of
the statistics information into the shared data area
(SDA).
4.2.1.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
As shown overleaf the subpackage function consists
of 5 actions:
- request statistics collection
- reserve shared data area
- update shared data area
- release shared data area
- update completion code to application
4.2.1.1.1 R̲e̲c̲e̲i̲v̲e̲ ̲C̲o̲l̲l̲e̲c̲t̲ ̲S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲
Completion of a number of events causes the involved
application to request statistics generation. This
is achieved by issuing a monitor function call which
carries out the 4 later actions listed in section 4.2.1.1.
During receive collect of statistics, input parameters
are validated. These are checked for minimum and maximum
boundaries and format types.
FIGURE 4.2.1.1-1…01…Statistics collection subpackage function 1…01…specification
4.2.1.1.2 R̲e̲s̲e̲r̲v̲e̲ ̲S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲A̲r̲e̲a̲
During update of SDA it is reserved by the collection
subpackage. A CSF reserves variable function call,
where shared data area is input parameter, ensures
that application is the only accessor during update.
4.2.1.1.3 U̲p̲d̲a̲t̲e̲ ̲S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲A̲r̲e̲a̲
The update subfield actions consist of the following
actions:
- initial load of data address pointer
- initial load of procedure address pointer
- loop mechanism containing
a) modify addressed subfield
b) update addressing pointers
4.2.1.1.3.1 D̲a̲t̲a̲ ̲A̲d̲d̲r̲e̲s̲s̲ ̲P̲o̲i̲n̲t̲e̲r̲
Next is referred to figure 4.2.1.1.3.1-1. According
to the group number (A), a part of the statistics data
record delivered by requestor, the group N address
is determined. Each entry in level 1, refer figure
4.1.1.4.1.1-1, is 1 word long. The entry of this location
contains the starting address of level 2 information
for the involved group. Next step in determination
of record address is to combine contents of delivered
statistics data record and contents of level 2 information.
Figure 4.2.1.1.3.1-1 is used to illustrate the calculation
procedure. Determination of start address of data area
is done by reading contents of "group start addr" in
level 2 (H).
Relative record address within the group or subgroup
is then:
(B-1) x F x G + C x F
Refer figure 4.2.1.1.2.1-1.
Initial data record address is then calculated to be:
H + (B-1) x F x G + C x F
If no subgroups are present, statistics subgroup number
(B) in data record shall be equal to 1.
Statistics Data Record Delivered by Application
Statistics Statistics Statistics Statistics
group subgroup record parameters
number number number
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
A B C
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
Table area in SDA
No of subgroups................................. D
No of fields.................................... E
Record length................................... F
No of records................................... G level
2
Group start addr................................ H
Field 1 descriptor..............................
Field N descriptor..............................
SDA Addressing Mechanism…01…Figure 4.2.1.1.3.1-1
4.2.1.1.3.2 P̲r̲o̲c̲e̲d̲u̲r̲e̲ ̲A̲d̲d̲r̲e̲s̲s̲ ̲P̲o̲i̲n̲t̲e̲r̲
To load the procedure address pointer the same procedure
through level 1, as for data address pointer, is performed.
The pointer will then be loaded to point out the 6
entries in level 2. Each entry is 3 integers wide.
Third integer in this entry indicates the processing
procedure to be used on the addressed data entry.
4.2.1.1.3.3 L̲o̲o̲p̲ ̲M̲e̲c̲h̲a̲n̲i̲s̲m̲
The loop mechanism takes care that all subfields related
to the function call are being modified. The entry
in level 2, refer figure 4.1.4.1.1.1-1, no. of fields,
indicates the number of times to initiate the loop.
During each run through of the loop, subfield is modified
and address and procedure pointer updated.
4.2.1.1.3.3.a M̲o̲d̲i̲f̲y̲ ̲A̲d̲d̲r̲e̲s̲s̲e̲d̲ ̲D̲a̲t̲a̲ ̲F̲i̲e̲l̲d̲
The processing of the addressed data field is selected
through the procedure identification in the field descriptor.
The third integer indicates which of the following
procedures is to be used on the field. The following
field procedures exist and additional types may be
implemented on request.
1) Increment one subfield
Add one to the subfield addressed by address pointer,
possibly modified, as specified by input parameter.
2) Add to field.
Summation of input parameter to contents of the
addressed data field.
3) Boundary setting, max.
Compare input parameter with field contents. Exchange
parameters if input parameter is greater than field
contents.
4) Subtract from field
Subtraction of input parameter from the contents
of the specified field.
5) Change field sign.
A O in the field is changed to a 1 and visa versa.
6) Increment two subfields.
The input parameter M specifies two subfields to
be incremented. First subfield is determined from
the algorithm: remainder of M/20, second subfield
is determined from the algorithm: quotient of M
modulo 20.
4.2.1.1.3.3.b U̲p̲d̲a̲t̲e̲ ̲A̲d̲d̲r̲e̲s̲s̲i̲n̲g̲ ̲P̲o̲i̲n̲t̲e̲r̲s̲
Data addressing pointer.
The general contents of the data addressing pointer
is byte address pointing out the first byte of the
field to be updated. If field contains subfields, indicated
by field descriptor integers, data pointer is modified
according to these integers pointing out the subfield
to be updated. Update of basic unmodified data address
pointer after each loop run through is to add total
field length, i.e. (I) x (J) see figure 4.2.1.1.3-1
for the contents of address pointer.
Figure 4.2.1.1.3.3-2 depicts the addressing pointer
update mechanism.
Procedure addressing pointer.
Each field descriptor is of fixed size, which is added
to the procedure addressing pointer to point out next
procedure. This is done after each run through of the
field loop. Procedure is the one indicated by the third
integer as seen in figure 4.2.1.1.3.3-1.
Figure 4.2.1.1.3.3-3 depicts the processing procedure
update mechanism.
Figure 4.2.1.1.3.3-1
4.2.1.1.4 R̲e̲l̲e̲a̲s̲e̲ ̲S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲A̲r̲e̲a̲
Completion SDA update of a complete record by application
results in release of the area for new updates or for
emptying this. A RELEASE VARIABLE function call to
CSF with input parameter SDA handles this operation.
4.2.1.1.5 U̲p̲d̲a̲t̲e̲ ̲C̲o̲m̲p̲l̲e̲t̲i̲o̲n̲ ̲C̲o̲d̲e̲
Completion of a statistics collection function call
is acknowledged to requestor. Contents of return code
tell whether the update was successfully ended or was
cancelled due to parameter errors.
4.2.1.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
Shown overleaf is the main software structure of subpackage
1. The box containing address and process fields to
be updated is further structured in the following diagrams.
Each diagram contains enough information to explain
the hierarchical break down structure.
FIGURE 4.2.1.2-1…01…Collection subpackage…01…main software structure
Figure 4.2.1.2-2…01…Address records and…01…call procedures
FIGURE 4.2.1.2-3…01…Procedure calls
FIGURE 4.2.1.2-4…01…Procedure 1 - 3
FIGURE 4.2.1.2-5…01…Procedure 4 - 6
4.2.1.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
Data flow and control during collection of statistics
information is sequential and presented in HIPO diagram
2. Four main functions occur where function 22 is further
described through four diagrams. This is again broken
down in a hierarchical way indicated by the numbers
in the lower right hand side of the process box.
DIAGRAM ID: 2…01…STP COLLECT SUBROUTINE
DIAGRAM ID 22…01…Update record fields
DIAGRAM ID:…01…Update record fields
DIAGRAM ID: 22…01…Update record fields
DIAGRAM ID: 22 4/4…01…Update record fields
DIAGRAM ID:2281 l/2…01…Procedure 2,…01…Increment one Subfield
DIAGRAM 2/2…01…Procedure 1,…01…Increment one subfield
DIAGRAM 2282…01…Procedure 2, Add input parameter to field
DIAGRAM 2283,…01…Procedure 3…01…max boundary setting
DIAGRAM 2284…01…Procedure 4,…01…subtract input parameter from field
DIAGRAM 2285…01…procedure 5…01…change field sign
DIAGRAM 2286 l/2…01…Procedure 6,…01…increment two subfields
DIAGRAM 2286…01…Procedure 6,…01…increment two subfields
DIAGRAM 24 l/l…01…COMPLETION CODE TO APPLICATION
4.2.1.4 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
Data related to subpackage 1 are the main memory resident
SDA table. This consists of two parts namely:
- table area and
- data area
Paragraph 4.1.4.1 contains a detailed description as
the area is shared with subpackage 2.
4.2.1.5 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Collection subpackage interfaces to the dump subpackage
in two indirect ways. Collected statistics information
is stored in the shared data area (SDA) by collection.
SDA is emptied by dump subpackage, so SDA acts as an
indirect interface.
Access to SDA is requested via CSF by a reserve SDA
function call. Both above mentioned subpackages use
this call during collection and dump respectively.
4.2.2 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲M̲a̲i̲n̲ ̲P̲r̲o̲g̲r̲a̲m̲ ̲S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲
This sub-package handles the main activities, i.e.
dump, generation and delivery of statistics information.
4.2.2.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲s̲
The functions performed are shown in figure 4.2.2.1-1
and are as follows:
- receive next QEL from STP time-out and request
queue
- detect type of QEL
- activation of sub-packages.
4.2.2.1.1 R̲e̲c̲e̲i̲v̲e̲ ̲N̲e̲x̲t̲ ̲Q̲E̲L̲
Main control QELs are sent to the STP time-out and
request queue. QELs are received from this queue by
use of CSF QMON functions.
4.2.2.1.2 D̲e̲t̲e̲c̲t̲ ̲T̲y̲p̲e̲ ̲o̲f̲ ̲Q̲E̲L̲
QELs received in STP time-out request queue are checked
for type of QEL. Following types will be recognized:
- 6 minutes interval time-out from SCF
- storage occupancy request from TEP.
FIGURE 4.2.2.1-1
Functional Specifications
4.2.2.1.3 A̲c̲t̲i̲v̲a̲t̲i̲o̲n̲ ̲o̲f̲ ̲S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲s̲
If the QEL received is of type 6 minutes interval time-out,
a dump of SDA to corresponding interval area in STP
file is incarnated. The HSG is invoked afterwards if
current time is equal to a full hour. If current time
is 2400 hours, DSG is initiated and if it shows the
end of a 7 day period, WSG too. Finally, the delivery
sub-package is invoked if the time is 2400 hours for
delivery of print-out to TEP. The second kind of QEL
detected is of the kind: storage occupancy request.
If this is detected, the delivery sub-package, i.e.
its storage occupancy module, is started.
4.2.2.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The software structure consists of one module performing
the functions listed in 4.2.2.1.
4.2.2.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
Control of this sub-package is achieved by the QELs
arriving in STPs time-out request queue and by return
code from the calling procedures. An overview diagram,
refer figure 2.3.1.6-1, shows this control.
HIPO diagram 4.2.2.3-1 depicts both the data flow and
the control logic for this main control sub-package.
HIPO Diagrams
(2 pages)
4.2.2.4 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
Data pertinent to this sub-package are information
contained in QELs in STP time-out request queue and
information communicated during procedure calls.
The information field in the time-out QEL contains
an event description saying that the QEL refers to
a 6 minutes interval time-out.
Procedure calls data communicated are as follows:
- For dump, interval to be used is interchanged.
- For HSG, hour to be used is interchanged.
4.2.2.5 S̲u̲b̲-̲P̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Interfaces to other sub-packages are as follows:
- Dump sub-package interface is active when main
program sub-package activates the dump procedure.
- Generation sub-package interface is used when the
hourly, daily and weekly statistics are generated.
- Delivery sub-package is used when either storage
occupancy is requested or delivery of statistics
information to the statistics printer is to take
place.
4.2.3 S̲t̲a̲t̲i̲s̲t̲i̲c̲s̲ ̲D̲u̲m̲p̲ ̲S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲
Subpackage 1.2 statistics dump handles the transfer
of accumulated data from shared data area to statistics
dump area. The shared data area lay-out has previously
been outlined in paragraph 4.1.4.1.
4.2.3.1 F̲u̲n̲c̲t̲i̲o̲n̲a̲l̲ ̲S̲p̲e̲c̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
The overview diagram on figure 4.2.3.1-1 depicts the
5 functions carried out under a statistics dump process.
They are:
- activate dump
- request data area access
- transfer data to dump area
- initiate SDA
- release SDA
4.2.3.1.1 A̲c̲t̲i̲v̲a̲t̲e̲ ̲D̲u̲m̲p̲
This is done by CSF timer monitor by placing a queue
element QEL in STP request queue. The main program
activate the dump procedure, when the main program
has detected the dump QEL in the STP request queue.
Fig. 4.2.3.1-1 Statistics Dump Functions Specifications
4.2.3.1.2 R̲e̲q̲u̲e̲s̲t̲ ̲A̲c̲c̲e̲s̲s̲ ̲t̲o̲ ̲S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲A̲r̲e̲a̲
After reception of time-out, access to the shared data
area must be granted by CSF. A RESERVE VARIABLE function
call with input parameter, shared data area, is sent
to CSF. STP can now access the shared data area, knowing
that no update will take place until the area is released
again.
4.2.3.1.3 T̲r̲a̲n̲s̲f̲e̲r̲ ̲o̲f̲ ̲S̲D̲A̲ ̲D̲a̲t̲a̲
Two steps are carried out. Determination of SDA start
address and data area size. Second transfer of the
addressed data area.
4.2.3.1.3.1 G̲e̲t̲ ̲T̲r̲a̲n̲s̲f̲e̲r̲ ̲I̲n̲f̲o̲r̲m̲a̲t̲i̲o̲n̲
Consulting SDA, refer figure 4.1.4.1.1.1-1, from where
the SDA start data address can be found. The amount
of bytes to be transferred during dump is contained
in data area size location.
4.2.3.1.3.2 T̲r̲a̲n̲s̲f̲e̲r̲ ̲D̲a̲t̲a̲
The I/O instruction modify bytes do the transfer of
SDA to an interval section in the STP file. Interval
in question is derived from STP file information area
byte address A which contains status of current interval
area, refer figure 4.1.4.2-1.
4.2.3.1.4 I̲n̲i̲t̲i̲a̲t̲e̲ ̲S̲D̲A̲
After transfer of SDA to STP file, SDA is initiated.
An initial version of SDA is loaded from disk into
main-memory. This version is ready for being updated
during the next 6 minutes interval.
FIGURE 4.2.3.1.3-1…01…Transfer data from shared data area…01…to statistic dump
area.
4.2.3.1.5 R̲e̲l̲e̲a̲s̲e̲ ̲o̲f̲ ̲S̲h̲a̲r̲e̲d̲ ̲D̲a̲t̲a̲ ̲A̲r̲e̲a̲
After completion of data transfer from shared data
area it shall be released. A RELEASE VARIABLE function
call to CSF with input parameter, SDA, acknowledges
CSF statistic collector that collection statistic record
can be continued.
4.2.3.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲
The dump subpackage software structure consists of
a number of modules taking care of the previously mentioned
functions. Refer to figure 4.2.3.2-1.
FIGURE 4.2.3.2-1…01…Statistics dump Software structure
4.2.3.3 D̲a̲t̲a̲ ̲F̲l̲o̲w̲ ̲a̲n̲d̲ ̲C̲o̲n̲t̲r̲o̲l̲ ̲L̲o̲g̲i̲c̲
Overleaf is shown the data flow and control logic for
the dump subpackage, described through HIPO diagrams.
Diagrams contain enough information for understanding
the flow, so no further explanation will follow the
diagrams.
DIAGRAM ID:3 l/1…01…STP Dump
4.2.3.4 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲D̲a̲t̲a̲
The data used by dump subpackage are contained in 2
areas. During a dump data are transferred from the
shared data area (SDA) to one of 10 interval areas.
Interval areas are placed in the statistics file described
in detail in paragraph 4.1.4.2, while SDA description
is found in 4.1.4.1.
4.2.3.5 S̲u̲b̲p̲a̲c̲k̲a̲g̲e̲ ̲I̲n̲t̲e̲r̲f̲a̲c̲e̲s̲
Interface to subpackage collect is described in paragraph
4.2.1.5.
Further an indirect interface to subpackage generate
exists. Subpackage dump stores data in the 10 intervals
in the statistics file. Subpackage generate accumulates
the 10 intervals to form an hourly statistics.
Inteface to main program sub-package is described in
paragraph 4.2.2.5.
