top - download
⟦a02152953⟧ Wang Wps File
Length: 10281 (0x2829)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN75.00«
Derivation
└─⟦0a9635741⟧ Bits:30006044 8" Wang WCS floppy, CR 0070A
└─ ⟦this⟧ »~ORPHAN75.00«
WangText
J…0a…J…0b…J…0e…J I…09…I…00…I…05…H…09…H…0f…H…05…G…09…G…0e…G…01…G…05…F…0a…F…0b…F…0f…F…05…E…09…E…0d…E…01……86…1
…02…
…02…
…02…
…02…CPS/ICD/009
…02…KR/810713…02……02…
CAMPS
SOFTWARE
INTERFACE
CONTROL
DOCUMENT
…02……02…CAMPS
3.6 M̲E̲S̲S̲A̲G̲E̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲
G̲e̲n̲e̲r̲a̲l̲ ̲C̲o̲m̲m̲u̲n̲i̲c̲a̲t̲i̲o̲n̲ ̲P̲r̲o̲t̲o̲c̲o̲l̲
All application process access to MMS must be performed
via Message Monitor within CSF. Each access consists
of a commandsent to one of the Storage and File Management
Process synchronization elements and a reply sent by
MMS to the Message Monitor answer synchronization element
of the application process. The communication flow
is shown in figure 3.6-1.
A command o MMS consists of up to 3 parts, as shown
in figure 3.6-2.
a) C̲o̲m̲m̲a̲n̲d̲ ̲B̲o̲d̲y̲
This is always present. It is sent in the process
communication information element to the SFM synchronization
element. The standard part contains various control
infrmation, which is independent of the command.
The parameter part contains command dependent
information.
b) C̲o̲m̲m̲a̲n̲d̲ ̲P̲a̲r̲a̲m̲e̲t̲e̲r̲ ̲B̲l̲o̲c̲k̲
Is used for some commands where the parameter information
is too voluminous to be held in the process communiction
information element. The parameter block is a
consecutive area in the data space of the sending
application process.
c) A̲p̲p̲l̲i̲c̲a̲t̲i̲o̲n̲ ̲D̲a̲t̲a̲ ̲B̲u̲f̲f̲e̲r̲
Is only present for read/write commands. It is
a consecutive area in the application data spce
of the sending process.
Execution of a command usually results in updating
the Command Parameter Block and Application Data Buffer,
if present.
Having terminated command execution, MMS returns a
reply formatted as command body, where parametr part
now contains return parameters, including a completion
code. The completion code tells whether the command
was executed as requested, or the reason why it was
not.…86…1 …02… …02… …02… …02…
Fig. 3.6-1…01…MMS Process Communication Scheme…86…1 …02… …02… …02… …02…
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
COMMAND BODY COMMAND CODE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
COMMAND BODY
SANDARD PART
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
COMMAND BODY
PARAMETER PART
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
COMMAND
PARAMETER BLOCK COMMAND
DEPENDENT
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
APPLICATION ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DATA BUFFER
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Fig. 3.6-2…01…GENERAL MMS COMMAND STRUCTURE…86…1 …02… …02… …02… …02… …02…
3.6.1 C̲I̲F̲ ̲H̲a̲n̲d̲l̲i̲n̲g̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
3.6.1.1 C̲r̲e̲a̲t̲e̲ ̲C̲I̲F̲
Input:
Command Body: Security Profile
Command Parameter
Block: CIF Attributes, as described below
Output:
Command Bod: Completion Code
View Ref.
Command Parameter
Block: Completed Attributes, as described
below.
The CIF Attributes input parameter is a View Attributes
Parameter record (see section 4.1.5.1.1 of CPS/SDS/003)
with the following fields filld in by calling application:
- Application Control Information
- Recovery Information:
1: Recoverable CIF
0: Non-Recoverable CIF
- Field Information.
Contains a Field Information Element for each field
of the new CIF. If ALLOCATED LENTH is non-zero,
it will be used to allocate initial disk space
for the field. USED LENGTHS is ignored. FIELD
TYPE specifies for each field whether it is permanent
or temporary. CS, AR and R fields are ignored.
A CIF will be created with the spcified attributes.
A view referencing the CIF will be generated too.
It will reference all field groups of the CIF and
have Read and Write access to all fields. The CIF
attributes parameter will be updated to contain the
view attributes for the enerated view.
The CIF ID field is only relevant if at least one of
the fields is permanent. The version indicator is
set to one, and used length of each field is set to
zero.…86…1 …02… …02… …02… …02… …02…
3.6.1.2 C̲r̲e̲a̲t̲e̲ ̲N̲e̲w̲ ̲C̲I̲F̲ ̲V̲e̲r̲s̲i̲o̲n̲
Input:
Command Body: View Ref. Previous Version.
Command Parameter
Block: CIF Attributes, as specified below.
Output:
Command Body: Compltion Code
View Ref., New Version
Command Parameter
Block: View Attributes, new version.
The input view must reference the latest version of
the CIF, and the CIF must be permanent.
A new CIF version will be generated together with a
vie referencing it. The attributes will be copied
from previous version, except for:
a) VERSION INDICATOR is increased by one.
b) ALLOCATED LENGTH of each field is taken from the
input CIF Attributes.
c) USED LENGTH of each field is set to zero
d) The view will reference all fields with read and
write access.
3.6.1.3 C̲r̲e̲a̲t̲e̲ ̲V̲i̲e̲w̲
Input:
Command Body: View Ref. Predecessor View.
Command Parameter
Block: View Attributes
Output:
Command Body: Completion Code
View Ref., ew View
Command Parameter
Block: View Attributes, New View.
For each field group, the corresponding FIELD INFORMATION
ELEMENT in input View Attributes specifies the field
of the new view as follows:
a) The R field specifies if the field roup shall be
referenced by the view. The new view can only
reference a subset of the field groups referenced
by predecessor view.
b) For those field groups which shall be referenced,
the AR field specifies the access right of the
new view. Wrie access can only be obtained if
the predecessor view has write access.
c) The CS field specifies if a field reference shall
already be created for the new view. If specified,
subsequent calls of the Create Fields command can
be avoided. Field reation and inclusion is handled
as specified in CREATE FIELDS below. Upon return
of reply, the Command Parameter Block contains
the attributes of the new view.
3.6.1.4 C̲r̲e̲a̲t̲e̲ ̲F̲i̲e̲l̲d̲s̲
Input:
Command Body: View Ref.
Command Parameter
Block Field Information
Output:
Command Body: Completion Code
Command Parameter
Block: Updated Field Information
The command specifies for a view previously created
by Create View how field references shall be set in
the new view, if not alrady specified in Create View.
The input parameter contains the specifications.
If the R field is set to one in a Field Information
Element, the CS field specifies, whether the field
shall be included from predecessor view or a new field
shall be dded to the field group. In the latter case
ALLOCATED LENGTH may:…86…1 …02… …02… …02… …02… …02…
- specify that space shall be allocated for the field.
Note that creation or inclusion can only take
place for those field groups which were referenced
in the CREATE VIEW command
Upon return of reply, the Updated Field Information
will contain the complete field information for the
view.
The command may be called several times for the same
view, but each field group must only be specified once.
Note that inclusion ofa field from predecessor view
requires that it is still existing.
3.6.1.5 G̲e̲t̲ ̲V̲i̲e̲w̲ ̲A̲t̲t̲r̲i̲b̲u̲t̲e̲s̲
Input:
Command Body: View Ref.
Output:
Command Body: Completion Code
Command Parameter
Block: View Attributes
The View Attributes are dlivered in a View Attributes
Parameter Record.
3.6.1.6 C̲h̲a̲n̲g̲e̲ ̲A̲t̲t̲r̲i̲b̲u̲t̲e̲s̲
Input:
Command Body: View Ref.
Security Profile
Change Mask.
Command Parameter
Block: Application Control Information
Output:
Command Body: Completio Code.
The changeable attributes are Security Profile and
Application Control Information. The Change Mask specifies
the words of Application Control Information which
shall be changed. Only a trusted process is allowed
to decrease the Security Profile.
3.6.1.7 R̲e̲m̲o̲v̲e̲ ̲V̲i̲e̲w̲
Input:
Command Body: View Ref.
Output:
Command Body: Completion Code.
If the view is not subject to storage, it will be deleted.
Those fields whch are only referenced by the deleted
view and which are not subject to storage will be deleted
too.
Note that a view referencing a recoverable CIF should
be removed by means of the SAVE command.
3.6.2 C̲I̲F̲ ̲I̲/̲O̲ ̲C̲o̲m̲m̲a̲n̲d̲s̲
3.6.2.1 R̲e̲a̲d̲ ̲V̲i̲e̲w̲
Iput:
Command Body: View Ref.
Application Data Buffer Size.
Command Parameter
Block: Field List.
Output:
Command Body: Completion Code
Command Parameter
Block: Updated Field List
Application Data
Buffer: Data read from view.
Reads data from one or more fields as specified in
Field List. The data are placed consecutively in Application
Data Buffer.
Each field list element contains two variables contolling
the read operation from the field:
a) F̲i̲e̲l̲d̲ ̲B̲y̲t̲e̲ ̲A̲d̲d̲r̲e̲s̲s̲
A byte offset within the field specifying where
to start the read operation. Must be even valued.
b) R̲e̲c̲o̲r̲d̲ ̲L̲e̲n̲g̲t̲h̲
The maximum number of bytes to be read from the
field. A alue of zero is allowed. The actual
number of bytes read may be smaller than specified,
as read will not continue beyond USED LENGTH of
the field. Must be even valued.
After the read operation each field list element will
be updated as follows:
c) Record Length will contain number of bytes actually
read. It may be zero, if field was empty or if
application data buffer could not hold more data.
d) Field Byte Address will be increased by Record
Length and will thus point to the first bte after
the bytes read. This will particularly facilitate
a sequence of read operations from a field.
Note that the most efficient read operation is obtained,
if read operations are started on sector boundaries
(512 bytes) within fields, and ifcomplete sectors are
read. Moreover, efficiency is likely to be increased,
if the field groups specified in field list are consecutive.
3.6.2.2 W̲r̲i̲t̲e̲ ̲V̲i̲e̲w̲
Input:
Command Body: View Ref.
Application Data Buffer Size
Command Parameter
Block: Field List
Application Data
Buffer: Data to be written
Ou
