top - download
⟦61a10c32d⟧ Wang Wps File
Length: 41995 (0xa40b)
Types: Wang Wps File
Notes: CPS/TPR/009
Names: »2202A «
Derivation
└─⟦6d69be3b6⟧ Bits:30006113 8" Wang WCS floppy, CR 0178A
└─ ⟦this⟧ »2202A «
WangText
;…07…:…0b…:…00…:…05…9…0b…0…01…0…06…/…0d…/…01…/…07….…0d….
-…0a…-…0f…-…05…,…0b…,…00…,…07…+…0b…+…0c…+…00…+…01…+ +…07…*…0b…*…0f…*
*…07…)…0a……86…1
…02…
…02…
…02…
…02…CPS/TPR/009
…02…830105
…02……02…#
OPERATIONAL
SOFTWARE
TEST
SPECIFICATION
AND
PROCEDURES
…02…Issue
1…02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ........................................
4
1.1 PURPOSE ......................................
4
1.2 APPLICABLE DOCUMENTS .........................
4
1.3 TERMS AND ABBREVIATIONS ......................
5
2 TEST SPECIFICATION AND EVALUATION ................
5
2.1 TEST SPECIFICATION ...........................
5
2.1.1 Test Purpose .............................
5
2.1.2 Test Object Identification ...............
6
2.1.2.1 Hardware Configuration ...............
6
2.1.2.2 Software Configuration ...............
6
2.1.3 Requirements .............................
6
2.1.4 System Function ..........................
8
2.1.5 Test/Function Relationship ...............
13
2.2 TEST METHODS AND CONSTRAINTS .................
13
2.2.1 System Test Condition ....................
13
2.2.2 Extent of System Test ....................
14
2.2.3 Data Recording ............................
14
2.2.4 System Test Constraints ...................
15
2.3 TEST EVALUATION ...............................
15
2.3.1 Test Criteria Definitions .................
15
2.3.2 Error Definitions .........................
17
2.3.2.1 Category 1 ............................
17
2.3.2.2 Category 2 ............................
19
2.3.2.3 Category 3 ............................
20
3 TEST DESCRIPTION .................................
21
3.1 GENERAL .......................................
21
3.2 TEST CONTROL ..................................
21
Appendix A: Test Log Format .......................
23
Appendix B: User Function Procedures ..............
25
1̲ ̲ ̲G̲E̲N̲E̲R̲A̲L̲
1.1 P̲U̲R̲P̲O̲S̲E̲
The purpose of this document is
a) to identify:
1) the test object
2) the requirements to be verified
3) the system functions to be exercised
b) to define:
1) the test methods and constraints
2) the test evaluation criteria
c) to describe:
1) test control
2) the procedure for test execution
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
a) CAMPS System Requirements Spec.
CPS/210/SYS/0001
b) CAMPS Acceptance Plan
CPS/PLN/012
c) CAMPS Acceptance Test Spec. Overview
CPS/TSS/001
d) User Procedures and Associated Format
CPS/230/ICD/0001
e) Supervisor Commands and Procedures
CPS/230/ICD/0002
f) Operator Commands
CPS/ICD/010
1.3 T̲E̲R̲M̲S̲ ̲A̲N̲D̲ ̲A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
CAMPS C̲omputer A̲ided M̲essage P̲rocessing S̲ystem
CR C̲hristian R̲ovsing A/S
HDB H̲istorical D̲ata B̲ase
H/W H̲ardw̲are
ICD I̲nterface C̲ontrol D̲ocument
MDCO M̲essage D̲istribution and C̲ontrol O̲perator
MSO M̲essage S̲ervice O̲perator
OCR O̲ptical C̲haracter R̲eader
PTP P̲aper T̲ape P̲unch
PTR P̲aper T̲ape R̲eader
ROP R̲eceive O̲nly P̲rinter
S/W S̲oftw̲are
SRS CAMPS S̲ystem R̲equirements S̲pecification
VDU V̲isual D̲isplay U̲nit
2̲ ̲ ̲T̲E̲S̲T̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲E̲V̲A̲L̲U̲A̲T̲I̲O̲N̲
2.1 T̲E̲S̲T̲ ̲S̲P̲E̲C̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
2.1.1 T̲e̲s̲t̲ ̲P̲u̲r̲p̲o̲s̲e̲ ̲
The purpose of this test is to give a final verification
of CAMPS's operational performance and the reliability
of the software system.
2.1.2 T̲e̲s̲t̲ ̲O̲b̲j̲e̲c̲t̲ ̲I̲d̲e̲n̲t̲i̲f̲i̲c̲a̲t̲i̲o̲n̲
2.1.2.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
The test will be conducted on the SHAPE site CAMPS
configuration.
2.1.2.2 S̲o̲f̲t̲w̲a̲r̲e̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲
The complete CAMPS Software System
2.1.3 R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲s̲
With reference to the Acceptance Test Specification
Overview, sect. 3, the following requirements, as stated
in the SRS, are applicable for CAMPS' operation during
test execution:
3.2.1.2 Operational Messages
3.2.1.3 Service Messages
3.2.1.4 Entry of Complete Messages
3.2.1.5 ACP127 Conversion
3.2.1.6 Transmission
3.2.2.1 Message Reception Procedures
3.2.2.2 ACP127 Analysis
3.2.2.3 Message Distribution
3.2.2.4 Procedures Related to Receipt
of Flash Messages
3.2.2.5 Handling of Messages from SCARS/ACCIS
3.2.3.1 Equipment and Functions allocatable to
a Terminal Position
3.2.3.2 Terminal Access Control
3.2.3.3 Functional Capabilities of
Terminal Procedures
3.2.3.4 Precedence and Queueing
3.2.3.5 Terminal Modes
3.2.3.6 Status Information Available
from Terminal Positions
3.2.3.7 Presentation of Information at
Terminal Positions
3.2.4.1 Supervisor Functions
3.2.4.2 Message Service
3.2.4.3 Message Distribution Control
3.2.4.4 Reports
3.2.4.5 Status Information
3.2.4.6 Engineering Functions
3.2.5.1 Categories of Transactions to
be Logged
3.2.5.2 Logging Events
3.2.5.3 Storage of Log Records
3.2.5.4 Print of Log Records
3.2.5.5 Tracing (Computer Analysis)
of Log Information
3.2.5.6 Definition of Specific Log
Records
3.2.6.1 Statistical Data on Messages
3.2.6.2 Storage Occupancy
3.2.6.3 Channel Availability and
Occupancy
3.2.6.4 Message Distribution
3.2.6.5 Use of Message Formats
3.2.7.1 Message Storage and Retrieval
3.2.7.2 Storage and Retrieval of
Non-Message traffic
3.2.8.1 On-line and Off-line CAMPS site
Software Packages
3.2.8.2 Initialization
3.2.8.3 Errorhandling
3.2.8.4 Recovery Situations
3.2.8.5 Degraded Availability Configuration
3.4.1.2 Message Traffic Throughput
3.4.1.6 Timing Requirements
3.4.5.2 Control of Record Output
3.5.11.4 Software Maintenance and
Modification
3.5.11.5 Support Software
2.1.4 S̲y̲s̲t̲e̲m̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲
During this test all specified CAMPS functions will
be available.
Taken from the SRS table of contents the functions
are:
Operational Messages
Message Preparation
New Message Preparation
Preparation of Message Header
Preparation of Message Text
Correction of Header and/or Text
Append/Coordinate/Release/Defer
Message Editing
Append Message
Message Coordination
Comments
New Comment Preparation
Comment Editing
Comment Presentation
Message Release
Local Distribution
Entry of Complete Messages
Entry from OCR
Entry from PTR
ACP127 Conversion
Conversion of Operational Messages with Plain
text
Conversion of Service Messages
Conversion of Complete Messages
Transmission
Channel Selection and Identification
Procedures Related to Premature Termination of
a
Transmission
Procedures Related to the Zen Prosigns
Procedures Related to FLASH Receipt
Handling of CRYPTO SECURITY
Procedures for Sending Automatically Generated
Abbreviated Service Message
Message Reception Procedures
ACP127 Analysis
Format Line Detection
Selection of Parameter
Determination of Message Type
Message Distribution
Automatic Distribution
Handling of Codress/Plaindress Encrypted Messages
Handling of Data Messages
Handling of CLEAR Message
Distribution of Service Messages
Procedures Related to Receipt of FLASH messages
Handling of Messages from SCARS/ACCIS
Messages from SCARS
Messages from ACCIS
Comments/VDU Displays from SCARS/ACCIS
Equipment and Functions allocatable to a Terminal
Position
Terminal Position Equipment
Stand alone Equipment (Terminals)
Terminal Position Function
Terminal Profile
Operator Profile
Device Profile
Terminal Access Control
Physical Access
Logical Access
VDUs
Stand Alone Devices
Functional Capabilities of Terminal Procedures
Precedence and Queuing
Terminal Modes
Status Information Available from Terminal Positions
Presentation of Information at Terminal Positions
Use of Visual Display Units
Requirement to Printed Output
Supervisor Functions
Supervisor Commands
Common Requirements For Commands
Command Processing Control
Message Processing Control
Terminal Position Control
User Control
External Connection Control
OCR, PTR/PTP, and Stand Alone Teleprinter Control
Report Control
Statistic Control
Log Control
Offline Storage Control
Security Warning Control
Supervisor Engineering Commands
Queue Control at Restart
Message Deletion
Service Message Handling
Reception of Service Messages
Preparation of Service Messages
Message Handling
Message Rerun
Retrieval
Redistribution
Readdressal
Statistics Print
Report Print
Log Print
Queue Status Print
Message Service
Incoming Message Assistance
Routing Indicator Assignment
Routing to PTP
Insertion of CLEAR
Message Distribution Control
Distribution
Retrieve for Distribution
Reports
General
Security Reports
Warning Reports
Command Completion Reports
Queue Status Reports
Channel Reports
Deletion Request Report
Status Information
Back-up of System parameter file
Engineering Functions
Engineering Function Implementation
Engineering Functions Detailed Definition
H/W Configuration Status Display
Software Development
Categories of Transactions to be Logged
Logging Events
Storage of Log Records
Print of Log Records
Tracing (Computer Analysis) of Log Information
Definition of Specific Log Records
Log Records Relating to Incoming Messages
Log Records Related to Incoming NICS-TARE/TRC/
Point to Point connection Messages
Valid Messages
Invalid Messages
Automatically Deleted Messages
Log Records Relating to Incoming ACE CCIS Messages
Log Records Relating to Incoming SCARS II Messages
Log Records Relating to Outgoing Messages
NICS-TARE/TRC/Point to Point connection Messages
Log Records Relating to Outgoing ACE CCIS Messages
Log Records Relating to Outgoing SCARS II Messages
Channel Discontinuity
NICS-TARE/TRC/Point to Point connection Channel
Discontinuity
Log Records Relating to ACE CCIS Channels
Discontinuity
Log Records Relating to SCARS II Channel
Discontinuity
Terminal Procedures
Denotation of Log Fields Contents
Log of User Transactions
Log of Security Procedures
Log of Automatically Deleted Comments/Notification
Log of Printer, PTP, and OCR Transactions
Message Distribution Control
Message Service
Supervisory Transactions
Statistical Data on Messages
Incoming Messages
Outgoing Messages
Rejected Messages
Storage Occupancy
Channel Availability and Occupancy
Message Distribution
Use of Message Formats
Formats A, C1, G1, M, O
Formats B, D, F, G2, H, I, N, P1, P2, Q, R
Storage of Messages and Transactions
Types of Messages to be Stored
Types of Transactions to be Stored
Retrieval of Messages and Transactions
Retrieval Keys
Retrieval by User
Retrieval by Supervisor
Retrieval Restrictions
In-line and Off-line CAMPS Software Packages
Initialization
Error Handling
Error Types
Error Detection
On-line Error Detection
Off-line Error Detection
Error Reports
Error Reactions
Audit Reports
Recovery Situations
Recovery/Restart from Total System Error
Recovery after Switch-over
Degraded Availability Configuration
Message Traffic Throughout
Timing Requirement
Control of Record Output
Print-Out
Punched Paper Tape
Removable Storage Media
Software Maintenance and Modification
Support Software
2.1.5 T̲e̲s̲t̲/̲F̲u̲n̲c̲t̲i̲o̲n̲ ̲R̲e̲l̲a̲t̲i̲o̲n̲s̲h̲i̲p̲
The test shall be conducted in a way, which to the
extent possible, resembles operational conditions.
This implies that:
a) Functions related to message traffic processing
will not be exercised beyond the extent determined
by the message traffic throughput and message traffic
characteristics specified in the SRS para 3.4 and
monitored by means of the system's statistics package.
b) Exercise of retrieval functions shall be in accordance
with the SRS para 3.4.1.6.4.
c) System engineering and supervisory functions related
to:
1) functional reconfiguration
2) system table update and control
3) hardware reconfiguration
4) recovery and restart
shall be exercised to the extent required for support
of system operation only.
2.2 T̲E̲S̲T̲ ̲M̲E̲T̲H̲O̲D̲S̲ ̲A̲N̲D̲ ̲C̲O̲N̲S̲T̲R̲A̲I̲N̲T̲S̲
2.2.1 S̲y̲s̲t̲e̲m̲ ̲T̲e̲s̲t̲ ̲C̲o̲n̲d̲i̲t̲i̲o̲n̲
The purpose of this test is to provide a demonstration
of CAMPS operational performance and the reliability
and stability of the software system.
Conductance of this test assumes the availability of
the connecting points for the specified external interfaces
(NICS TARE, ACE CCIS, SCARS II, TRC and Point-to-Point
Connections). However, in the event one or more of
the interfaces are not available, the test shall be
conducted with exclusion of those functions which are
dependant of the missing interfaces.
The scheduled test duration is 1 period of 15 days
and 2 periods of 20 days each assuming that the test
criteria specified in para 2.3.1 is fulfilled.
The initial 5 days of the testperiod will be used for
on the job training of SHAPE's operational staff. Training
instruction will be given by CR's test supervisor.
All CAMPS user functions shall be executed according
to the procedures specified in appendix B.
Execution of CAMPS supervisory- and operator functions
must be according to CPS/ICD/002 and CPS/ICD/010 respectively.
The test evaluation shall be performed by each operational
staff member participating in test execution. Any observed
departure from the specified system functions shall
be reported to the test supervisor, who will decide
which action has to be taken.
2.2.2 E̲x̲t̲e̲n̲t̲ ̲o̲f̲ ̲S̲y̲s̲t̲e̲m̲ ̲T̲e̲s̲t̲
This test will give an extensive verification of CAMPS
operational performance and of the software reliability.
2.2.3 D̲a̲t̲a̲ ̲R̲e̲c̲o̲r̲d̲i̲n̲g̲
Data Recording is provided by the following CAMPS'
functions:
- Message Storage
- Supervisory Reports
- Log
- Statistics
Further, to provide means for a complete test documentation
and evaluation all user performed transactions must
manually be recorded along with test execution.
2.2.4 S̲y̲s̲t̲e̲m̲ ̲T̲e̲s̲t̲ ̲C̲o̲n̲s̲t̲r̲a̲i̲n̲t̲s̲
No welldefined point of reference or means for monitoring
exists for any of CAMPS' external interfaces. Therefore,
the evaluation of CAMPS' functions related to external
interfaces can only be based on the references provided
by CAMPS, i.e. the Historical Database and the Log
File.
2.3 T̲E̲S̲T̲ ̲E̲V̲A̲L̲U̲A̲T̲I̲O̲N̲
Test evaluation is performed by each operational staff
member participating in test execution. The evaluation
shall be based on comparison of the actual system response
to the expected response. Any discovered departure
from the specified system functions must immediately
be reported to the test supervisor, who will determine
if any impact is caused on the continued test execution.
This determination shall be based on the test criteria
definitions given later in this section.
2.3.1 T̲e̲s̲t̲ ̲C̲r̲i̲t̲e̲r̲i̲a̲ ̲D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲s̲
During execution of the Operational SW Test any failure
of CAMPS's specified functional and operational behaviour
will accoridning to its nature be categorized as follows:
a) C̲a̲t̲e̲g̲o̲r̲y̲ ̲1̲
1) Loss of a message or other transaction
2) Corruption of a message or other transaction
3) A message or transaction being missent
4) Misapplication of security rules
5) Failure of accounting procedures
b) C̲a̲t̲e̲g̲o̲r̲y̲ ̲2̲
1) Loss of service to more than 25 per cent of
all channels and user connecting points.
2) Loss of service to more than 50 per cent of
all operating positions or system reporting
facilities.
3) Loss of ability to recover the system
c) C̲a̲t̲e̲g̲o̲r̲y̲ ̲3̲
This category consists of errors not included in
1 and 2 above.
1) Software errors which adversely affect the
accomplishment of the CAMPS functional and
operational behaviour, so as to degrade performance,
but for which there exist reasonable alternative
work-around procedures.
2) Software errors which cause user inconvenience
or annoyance, but do not affect the systems
functional performance.
3) Errors not included in 3.1 and 3.2.
A software failure is defined as an occurrence of any
of the deviations from CAMPS specified functional and
operational performance which are described under category
1, 2, and 3.3.
The acceptance criteria shall be that the CAMPS system
shall be able to execute the basic software functions
according to the approved SRS for three periods of
each 20 calender days in a live operational mode without
any software failures.
Any software failure shall require a complete re-test
of the 20 day period in progress.
Software errors of categroy 3.1 and 3.2 shall not require
a restart of the test. However, the errors shall be
corrected and verified before final acceptance.
Errors, which are caused by a system utilisation not
corresponding to the approved SRS or by a test execution
not following the appropriate procedures as specified
in 2.2, shall not be considered.
Due to the rigorous Acceptance Criteria a detailed
and unambigous definition of each error type and its
documentation is given in the following.
2.3.2 E̲r̲r̲o̲r̲ ̲D̲e̲f̲i̲n̲i̲t̲i̲o̲n̲s̲
In the following is specified the documentation required
to provide evidence for the occurrence of any of the
failures specified in section 2.3.1 a) - c).
2.3.2.1 C̲a̲t̲e̲g̲o̲r̲y̲ ̲1̲
1a) Loss of incoming messages
Loss of an incoming message is documented by the
existance of an incoming message log record and
non- availability of the message from CAMPS HDB.
1b) Loss of outgoing messages or initiated transactions
Loss of an outgoing message or an initiated transaction
is documented by the user's manually recorded test
log (see appendix A), containing the CAMPS generated
transaction Id, and the non existence of the related
transaction completion log record, i.e for outgoing
messages the transmission completion log record.
2a) Corruption of Incoming Messages
Corruption of an incoming message is documented
by inconsistency between received version of the
message and the message distributed to the addressees.
2b) Corruption of outgoing messages or initiated transactions.
Corruptions of an outgoing message is documented
by inconsistency between the transmitted version
of the message and the final version of the prepared
message.
Corruption of a transaction means that the transaction
cannot be completed using the CAMPS user terminal
capabilities.
Corruption of an initiated transaction is documented
by demonstration.
3) A message or transaction being missent
A missent message or transaction is documented
by a print out of the display containing the missent
information.
The printout shall contain the identification of
the receiving terminal, i.e. Transaction Id, as
well as the intended destination identification.
4) Misapplication of security rules
Misapplication of security rules is documented
by either:
a) demonstration, or
b) a printout clearly indicating the security
rule misapplication.
5) Failure of accounting procedures
Accounting procedures comprise log information
related to:
a) external transactions:
1) incoming messages
2) outgoing messages
3) channel discontinuity
b) internal transactions:
1) terminal procedures
2) message distribution control
3) message servicing
4) dedicated supervisory commands
Any failure in generation of log records related to
the under a) and b) listed transactions as specified
in the SRS para. 3.2.5 is a failure of accounting procedures.
Upto 5 log records may be lost in case of switchover,
ref SRS 3.2.5.3.
Failures are documented by:
- demonstration of the transaction without the generation
of the related log record.
- demonstration of printed or recorded evidence of
the executed transaction and the non-existence
of the related log record.
2.3.2.2 C̲a̲t̲e̲g̲o̲r̲y̲ ̲2̲
1) Loss of service to more than 25 percent of all
channels and user connection points.
SHAPE CAMPS-site on which the Operational S/W Test
shall be performed is equipped with:
30 channels and
34 user connecting points
more than 25 percent are thus
8 channels and
9 user connecting points
loss of service is defined as loss of service for
a time period longer than that required for execution
of an automatic switchover which is 2 minutes.
Errors of this category shall thus be documented
by demonstration of loss of service to more than:
8 channels and
9 user connecting points
for a time period exceeding 2 minutes.
Loss of service caused by supervisor- or operator
transaction shall not be considered.
2) Loss of service to more than 50 per cent of all
operating positions or system reporting facilities.
SHAPE CAMPS-site operating positions and reporting
facilities are:
5 operating positions
5 reporting facilities (printers)
Errors of this category shall thus be documented
by demonstration loss of service to at least:
3 of the following VDUs:
SUP, MSO1, MSO2, MDCO, or OPER
or:
3 of the printers related to these positions:
SUP, MS01, MS02, MDCO, or OPER
for a time period exceeding 2 minutes.
Loss of service caused by supervisor- or operator
transactions shall not be considered.
3) Loss of ability to recover the system.
An error of this category is documented by a demonstration
of any non-conpliance of CAMPS's operation in a
recovery situation with the requirements stated
in the SRS para. 3.2.8.4.
2.2.2.3 C̲a̲t̲e̲g̲o̲r̲y̲ ̲3̲
The defintions of errors of this category are given
in para 2 c).
Any error within this category is documented by demonstration.
3̲ ̲ ̲T̲E̲S̲T̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
3.1 G̲E̲N̲E̲R̲A̲L̲
The purpose of this test is to provide a demonstration
of CAMPS operational performance and the stability
and the reliability of the software system.
The test will be conducted on the CAMPS equipment installed
on the SHAPE site. Test execution shall be performed
by SHAPE's operational staff under CR's supervision.
Test documentation is performed by each CAMPS user
filling in a transaction log (see appendix A) with
command- and data entries, system transaction identification,
and step by step evaluation of the observed system
response.
In case of an observed departure from any specified
system function this shall immediately be reported
to the test supervisor.
3.2 T̲E̲S̲T̲ ̲C̲O̲N̲T̲R̲O̲L̲
SHAPE shall provide a test scenario which outlines
the operations to take place during test execution.
The test scenario shall contain outlines of the operations
to be performed from
a) operator position
b) supervisory positions
c) all user positions
further the scenario shall contain an outline of incoming
traffic planned for all external interfaces.
The test scenario shall be submitted for review by
CR not later than 3 months prior to the start of the
test.
Test operation is performed under CR's supervision.
A SHAPE representative shall be appointed as test witness.
Any observed departure from the specified system functions
shall immediately be reported to the test supervisor.
Any reported departure from the specified system functions
shall be logged in the test report and evaluated by
the test supervisor.
For each error reported the test supervisor shall by
means of the defined error categories determine the
consequenses for the continued test execution in accordance
with para 2.3.1.
All error evaluations made by the test supervisor shall
be agreed by SHAPE's appointed test wittness.
Upon completion of each 20 day testperiod this shall
be indicated in the testreport by the signature of
SHAPE's test witness. Any disagreements between the
test supervisor and the test wittness regarding test
execution and test evaluation shall be settled by a
Test Control Board which is composed of an equal representation
from CR and SHAPE.
APPENDIX A
Example of a manually recorded TEST LOG.
T̲E̲S̲T̲ ̲L̲O̲G̲…01……01…U̲s̲e̲r̲ ̲i̲d̲:̲ ̲ ̲U̲R̲H̲ ̲ ̲ ̲ ̲ ̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲i̲d̲:̲ ̲ ̲A̲B̲C̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲D̲A̲T̲E̲:̲ ̲ ̲8̲1̲1̲1̲0̲3̲
COMMAND STEP TRANSACTION DATA ENTRY EXPECTED COMMENT
OR NO. ID REF. OR ITEM RESULT
FUNCTION REF. ID TIME YES NO
STAMP
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
SION 1 None None X
2 None None X
3 None id + Password X
PRNM 1 001 031036 TMSG 0002 X
2 TMSG 0002 X
3 TMSG 0002 X
4 TMSG 0002 X
5 TMSG 0002 X
PRNM 1 002 031041 TMSG 0003 X
2 TMSG 0003 X
3 TMSG 0003 X
4 TMSG 0003 X
5 TMSG 0003 X
RECV,R 1 003 031048 0012 031042 X
DELETE +
PRESENT 004 031051 00015 031045 X
PRINT 005 031053 00019 031046 X
CURRENT
MENU None None X
RECV, P 006 031058 00025 031052 X
PRINT 007 031102 00029 031055
CURRENT
MENU None None X
DIRS 1 008 031105 None X
A̲ ̲P̲ ̲P̲ ̲E̲ ̲N̲ ̲D̲ ̲I̲ ̲X̲ ̲ ̲B
U̲S̲E̲R̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲S̲
This appendix contains a step by step procedures description
of all CAMPS user functions.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲N̲e̲w̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲P̲R̲N̲M̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# PRNM
#RETURN# 1. Display of Fig.
1
format A-1/1.
2. Enter data "PAGE ON# 1. Display of Fig.
2
format A-1/2.
3. Enter data #ENTER# 1. Display of Fig.
3
format A-2.
4. Enter data #ENTER# 1. Display of Fig.
4
format A-3.
5. Select RELEASE #ENTER# 1. Display of Fig.
5
user menu.
2. Msg. is queued
at the release
terminal.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲N̲e̲w̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲(̲P̲R̲N̲C̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# PRNC #RETURN# 1. Display of Fig.
6
format G1-1.
2. Enter data #ENTER# 1. Display of Fig.
7
format G1-2.
3. Enter data #ENTER# 1. Display of Fig.
8
format G1-3.
4. Select SEND #ENTER# 1. Display of Fig.
5
user menu.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲C̲o̲n̲t̲i̲n̲u̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲(̲C̲T̲M̲P̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# CTMP #RETURN# 1. Display of Fig.
9
format C1-1.
2. Enter IDENT* #ENTER# 1. Display of Fig.
1
format A-1/1
3. Enter appropriate data #PAGE ON# 1. Display of Fig.
2
format A-1/2.
4. Enter appropriate data #ENTER# 1. Display of Fig.
3
format A-2.
5. Enter Appropriate data #ENTER# 1. Display of Fig.
4
format A-3.
6. Select appropriate action #ENTER# 1. Display of Fig.
5
user menu.
* IDENT is Item reference
Id for the current
version of the message
on which the continued
preparation shall
be executed.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲C̲o̲n̲t̲i̲n̲u̲e̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲(̲C̲T̲C̲P̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# CTCP #RETURN# 1. Display of Fig.
10
format G3-1.
2. Enter IDENT* #ENTER# 1. Display of Fig.
6
format G1-1.
3. Enter appropriate data #ENTER# 1. Display of Fig.
7
format G1-2.
4. Enter appropriate data #ENTER# 1. Display of Fig.
8
format G1-3.
5. Select SEND #ENTER# 1. Display of Fig.
5
user menu.
* IDENT is Item reference
Id for the current
version of the message
on which the continued
preparation shall
be executed.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲P̲r̲e̲d̲e̲f̲i̲n̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲P̲R̲P̲M̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# PRPM #RETURN# 1. Display of Fig.
11
format M(x) -
1.
2. Enter predefined message no.
#ENTER# 1. Display of format
M(x) - 2, Fig.
12
(A-1/1).
3. Enter appropriate header data
#PAGE ON# 1. Display of Fig.
2
format A-1/2.
4. Enter appropriate header data
#ENTER# 1. Display of Fig.
3
format A-2.
5. Select appropriate parts of
message text #ENTER# 1. Display of Fig.
4
format A-3.
6. Select appropriate action
#ENTER# 1. Display of Fig.
5
user menu.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲R̲e̲t̲r̲i̲e̲v̲e̲ ̲(̲R̲E̲T̲V̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# RETV #RETURN# 1. Display of Fig.
13
format H-menu
2. #COMMAND# RETV, Param.* #RETURN# 1. Display of format
H-**
3. Enter data #ENTER# 1. RETRIEVAL IN PROGRESS
PLEASE WAIT.
2. Display of retrieved
msg. or catalogue.
* Parameter entered
refers to the category
of message to be
retrieved.
** The format displayed
is depending on the
chosen command parameter.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲S̲i̲g̲n̲-̲O̲n̲ ̲(̲S̲I̲O̲N̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. Turn locking key to ON-position 1. Display of Fig.
14
format K1-1.
2. #COMMAND# SION #RETURN# 1. User id and pass
word is prompted
3. Enter User Id and Password
#ENTER# 1. Display of Fig.
5
user menu.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲S̲i̲g̲n̲-̲O̲f̲f̲ ̲(̲S̲I̲O̲F̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# SIOF #RETURN# 1. Display of Fig.
15
format K2
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲D̲e̲l̲e̲t̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲D̲E̲L̲M̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# DELM #RETURN# 1. Display of Fig.
16
format P1.
2. Enter Time Stamp, IDENT*
and SCD #ENTER# 1. DELETION REQUEST
ACCEPTED.
2. Display of Fig.
5
user menu.
* IDENT is Item reference
Id for the message
to be deleted. Only
messages prepared
at the requesting
terminal are accepted
for deletion.
If appropriate security interrogation will take place
prior to command execution.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲o̲f̲ ̲O̲u̲t̲g̲o̲i̲n̲g̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲D̲I̲O̲M̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# DIOM #RETURN# 1. Display of Fig.
17
format N
2. #PAGE ON# 1. Display of Fig.
18
format N-2.
3. #CANCEL# 1. Display of Fig.
5
user menu.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲o̲f̲ ̲D̲e̲l̲i̲v̲e̲r̲y̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲D̲I̲D̲S̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# DIDS #RETURN# 1. Display of Fig.
19
format R.
2. #CANCEL# 1. Display of Fig.
5
user menu.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲R̲e̲c̲e̲i̲v̲e̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲(̲R̲E̲C̲V̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# RECV, param.*
#RETURN# 1. Display of Fig.
20,
#PAGE ON# *** 21, 22 for formats
B, E2 or D.
Display of fig.
23 for format
E1 or fig. 24
for format G2.
2. #PRINT# 1. The displayed
item is printed
on the associated
printer.
2. Display of next
item in the specified
queue.
* Param. specifies the precedence queue from which the
item for display shall be taken.
** The display format
is determined by
the type of item
to be displayed.
*** Page on the number
of times required
for the actual display
format.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲(̲R̲E̲L̲S̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# RELS #RETURN# 1. First msg. in
release queue
is displayed (Fig.
20, 21 and 22
in Outgoing message
format.
2. #PAGE ON# is repeated until the
entire msg. has been displayed.
1. Display of Fig.
25 format D-2.
3. Enter REL, SCD and eventual
comments #ENTER# 1. Next msg. in release
queue is displayed.
2. A release notification
is queued at the
msg. originator's
VDU.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲o̲f̲ ̲R̲e̲l̲e̲a̲s̲e̲ ̲S̲t̲a̲t̲u̲s̲ ̲(̲D̲I̲R̲S̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# DIRS #RETURN# 1. Display of Fig.
26
format Q.
2. #CANCEL# 1. Display of user
menu.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲R̲e̲s̲p̲o̲n̲s̲e̲ ̲(̲R̲E̲S̲P̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# RESP #RETURN# 1. Display of the
first item in
the response queue.
2. #CANCEL# 1. Display of user
menu.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲t̲e̲r̲m̲i̲n̲a̲l̲ ̲t̲o̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲(̲P̲R̲T̲C̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1 #COMMAND# PRTC #RETURN# Display of fig. 27
2 Enter header data #ENTER# Display of fig. 28
3 Enter text #ENTER# Display of fig. 8
4 Select SEND #ENTER# Display of fig. 5
user menu
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲P̲r̲e̲p̲a̲r̲e̲ ̲V̲D̲U̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲(̲P̲R̲V̲D̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1 #COMMAND# PRVD #RETURN# Display of fig. 29
2 Enter display name #ENTER# Display of fig. 30
3 Enter header data #ENTER# Display of fig. 31
4 Select SEND #ENTER# Display of fig. 5
user menu
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲C̲o̲n̲t̲i̲n̲u̲e̲ ̲T̲e̲r̲m̲i̲n̲a̲l̲-̲t̲o̲-̲T̲e̲r̲m̲i̲n̲a̲l̲ ̲C̲o̲m̲m̲e̲n̲t̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲(̲C̲T̲T̲P̲)̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# CTCP #RETURN# 1. Display of Fig.
10
2. Enter IDENT* #ENTER# 1. Display of Fig.
27
3. Enter appropriate data #ENTER# 1. Display of Fig.
28
4. Enter appropriate data #ENTER# 1. Display of Fig.
8
format G1-3.
5. Select SEND #ENTER# 1. Display of Fig.
5
user menu.
* IDENT is Item reference
Id for the current
version of the message
on which the continued
preparation shall
be executed.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲C̲o̲n̲t̲i̲n̲u̲e̲ ̲V̲D̲U̲ ̲D̲i̲s̲p̲l̲a̲y̲ ̲P̲r̲e̲p̲a̲r̲a̲t̲i̲o̲n̲ ̲(̲C̲T̲V̲D̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1. #COMMAND# CTCP #RETURN# 1. Display of Fig.
10
2. Enter IDENT* #ENTER# 1. Display of Fig.
30
3. Enter appropriate data #ENTER# 1. Display of Fig.
31
4. Enter appropriate data #ENTER# 1. Display of Fig.
8
format G1-3.
5. Select SEND #ENTER# 1. Display of Fig.
5
user menu.
* IDENT is Item reference
Id for the current
version of the message
on which the continued
preparation shall
be executed.
F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲P̲R̲O̲C̲E̲D̲U̲R̲E̲
F̲U̲N̲C̲T̲I̲O̲N̲:̲ ̲ ̲R̲e̲t̲r̲i̲e̲v̲a̲l̲ ̲o̲f̲ ̲V̲D̲U̲ ̲D̲i̲s̲p̲l̲a̲y̲s̲ ̲(̲R̲E̲T̲D̲)̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Step Action Expected Result
N̲o̲.̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1 #COMMAND# RETD #RETURN# Display of fig. 32
2 Enter Display Name #ENTER# Display of fig. 33
Fig. 1
Fig. 2
Fig. 2a
Fig. 3
Fig. 4
Fig. 5
Fig. 6
Fig. 7
Fig. 8
Fig. 9
Fig. 10
Fig. 11
Fig. 12
Fig. 13
Fig. 14
Fig. 15
Fig. 16
Fig. 17
Fig. 18
Fig. 19
Fig. 20
Fig. 21
Fig. 22
Fig. 23
Fig. 24
Fig. 25
Fig. 26
Fig. 27
Fig. 28
Fig. 29
Fig. 30
Fig. 31
Fig. 32
Fig. 33
