HEWLETT PACKARD COMMUNICATOR 3000 Computer Systems Communication Manual

Ur HEWLETT
PACKARD
©
COMMUNICATOR 3000
Version G.22.00 of MPE V/E (Release 22)
000
se.
LS
HP Computer Museum
www.hpmuseum.net
For research and education purposes only.
HP 3000 Computer Systems
Computer
J (EET Bh
COMMUNICATOR 3000
Version G.22.00 of MPE V/E (Release 22)
ED Pacicano
8000 FOOTHILLS BOULEVARD, ROSEVILLE, CA 95678-6502
Part No. 32033-90248 Printed in U.S. A. 10/91
Volume 3, Issue 4 R3140
NOTICE
The information contained in this document 1s subject to change without notice.
HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not
be liable for errors contained herein or for incidental or consequential damages in connection with the
furnishing, performance or use of this material.
Hewlett- Packard assumes no responsibility for the use or reliability of its software on equipment that
is not furnished by Hewlett-Packard.
This document contains proprietary information which 1s protected by copyright. All rights are
reserved. No part of this document may be photocopied, reproduced or translated to another language
without the prior written consent of Hewlett-Packard Company.
Copyright © 1991 by HEWLETT-PACKARD COMPANY
CONVENTIONS USED IN THIS MANUAL
NOTATION
nonitalics
italics
[1
()
DESCRIPTION
Words in syntax statements which are not in italics must be entered exactly as
shown. Punctuation characters other than brackets, braces and ellipses must also be
entered exactly as shown. For example:
EXIT;
Words in syntax statements which are in i1talics denote a parameter which must be
replaced by a user -supplied variable. For example:
CLOSE filename
An element inside brackets in a syntax statement 1s optional. Several elements
stacked inside brackets means the user may select any one or none of these elements.
For example:
e) User may select A or Bor neither.
When several elements are stacked within braces in a syntax statement, the user must
select one of those elements. For example:
A
B User must select A or B or C.
C
A horizontal ellipsis :n a syntax statement indicates that a previous element may be
repeated. For example:
[,itemame]...;
In addition, vertical and horizontal ellipses may be used in examples to indicate that
portions of the example have been omitted.
À shaded deliineter preceding a parameter in a syntax statement indicates that the
delimeter must be supplied whenever (a) that parameter is included or (b) that
parameter 1s omitted and any other parameter which follows is included. For
example:
itema|itemb] | ,¿temc]
means that the following are allowed:
itema
itema,itemb
itema,itemb,itemc
itema,.iteme
111
CONVENTIONS (continued)
underlining
shading
J
CONTROL) Char
ту
When necessary for clarity, the symbol A may be used in a syntax statement to
indicate a required blank or an exact number of blanks. For example:
SET [ (modifier) ] A (variable) ;
When necessary for clarity in an example, user input may be underlined. For
example:
NEW NAME? ALPHA
In addition, brackets, braces or ellipses appearing in syntax or format statements
which must be entered as shown will be underlined. For example:
LET var[[subscript]] = value
Shading represents inverse video on the terminal’s screen. In addition, it is used to
emphasize key portions of an example.
The symbol ( _) may be used to indicate a key on the terminal’s keyboard. For
example, indicates the carriage return key.
Control characters are indicated by followed by the character. For example,
(CONTROL)Y means the user presses the control key and the character Y simultaneously.
CONTENTS
SECTION 1
INTRODUCTION
Release 22 Overview... 1.121220 4 2 4 4 4 4 4 4 4 4 4 4 A 4 A 2 4 4 4 CL 1 1 LL 1-1
SECTION 2
SYSTEM INFORMATION
New Volume Intrinsic - HPVOLINFO.... 112022044044 444 144 Ве, 2-1
New STORE Option ~ PACKED. . . . . 2200000244 4 4 4 4 4 4 4 A 4 4 eee 2-3
Multiple Database Transaction Logging (MDBX). ........... e 22. 2-5
SECTION 3
ADDITIONAL SOFTWARE PRODUCTS
Announcing Information Access A.06 ...... 42044444 44 4 4 4 4 4 1 4 14 44 120 3-1
SECTION 4
TECHNICAL ARTICLES
HPVOLINFO Volume Intrinsic. .. .. 1.144124 1 4444 44 1 4 1 4 A 1 1 1 CL 140 4-1
SECTION 5
PRODUCT RELEASE INFORMATION
MPE V/E Product Releases. ..... 120402204214 21 LL 2 4 1 4 ooo aaa en 5-1
HP PowerPatch MIT Releases... . 1.122411 4 i te ee ee ee ee eee 5-2
Supported Releases ........Q.oroseeo:oerooe nano oa aa ro re ara ree ae 5-3
SECTION 6
CATALOG OF USER DOCUMENTATION ......................... 6-1
INTRODUCTION
Release 22 Overview
by Ross Martin and Bob Stamps
Software Technology Center
This Hewlett-Packard software release is based on the orignal MPE V/E (G. 00. 00) operating system and
is referred to as Release 22 (G. 22.00). This release of the Communicator describes product introductions
and enhancements that have been added to our existing software products. This commercial release
further extends the functionality and performance of MPE V/E-based HP 3000 systems.
SYSTEM INFORMATION
With the creation of the Software Technology Division, HP has committed to continuing to meet customer
needs on MPE V systems. This commitment assures that HP will continue to support MPE V for the long
term.
The MPE V strategy can be summarized as:
e Continuing to provide viable solutions for customers interested in maintaining their MPE V systems
e Providing a suitable migration solution for customers who wish to upgrade to MPE XL or other HP
systems’ solutions
As a part of this commitment to MPE V customer satisfaction, HP 1s increasing its level of investment in
new MPE V enhancements and bug fixes. Prior to the next Platform introduction, there will be one
additional release, known as Release 23, which will reflect new levels of enhancements and fixes which
have been requested by large numbers of customers over the years. Release 23 1s a future MPE V release
positioned to make customers even more satisfied with their systems, and will make 1t clear that HP is still
listening and responding to customer needs.
An MPE V intrinsic called HPVOLINFO has been available since MPE V Release 20 (G.20.00), but
documentation about the intrinsic has not been published until this issue of the Communicator.
HPVOLINFO allows the gathering of volume space information which used to require a manual process to
obtain. HPVOLINFO is supported on both MPE V and MPE XL.
HP has added a new STORE option called PACKED, which improves the performance of a labeled tape
STORE.
HP is also improving and enhancing TurboIMAGE for MPE V. For example, HP TurboIMAGE 1$ now
providing a Multiple Database Transaction Logging (MDBX) capability. The logging and recovery
capability was limited to transactions involving a single database. Now, MDBX solves the problem of
complex applications with units of work that span multiple databases. Although the software was
provided with Release 21, both the software and documentatien are available with the current release.
1-1
Introduction
ADDITIONAL SOFTWARE PRODUCTS O
The A.06 version of Information Access 1s being released with MPE V Release 22 (G.22.00). The
following enhancements have been included:
e New CONVERT function
IMAGE automatic masters as tables
ADMIN quick configuration
2048 character Item Clause
GROUP BY Clause increased
1-2
SYSTEM INFORMATION
New Volume Intrinsic = HPVOLINFO
by Pat Alvarez, Wayne Booth, Mark Dovi and Lalitha Pejavar
Computer Systems Division
Product Name
HPVOLINFO Intrinsic
PRODUCT OVERVIEW
On MPE, there are different methods to find out how much volume space is available or used through
various commands and utilities - FREE, LISTF, REPORT, VINIT, VOLUTIL, etc. Until now, there were
no intrinsics that returned this type of information. Obtaining volume information was a very manual
process through the use of these commands and utilities. The customer had to write privileged mode
programs, which were not supported by HP, in order to retrieve volume information from the system
tables. Asa way to gather volume information more easily, a new volume intrinsic is now provided which
returns information similar to that returned by the volume commands and utilities available today. This
intrinsic 1s supported on both MPE V and MPE XL.
HPVOLINFO
The new volume intrinsic 1s HPVOLINFO. This intrinsic provides a way to retrieve volume information
from both system and nonsystem volumes (on MPE V, nonsystem volumes are equivalent to private
volumes). The volume information that is returned can be used to track volume space usage. More
specifically, the information that is returned describes how the space on volumes is allocated - ie. how
much is used for operating system purposes, how much space 1s free space, how much space is used for
spool files, etc. Also, with this information, volume fragmentation and lost disc space information can be
determined. With this intrinsic, the trend of volume usage can be observed so that future disc needs can
be predicted.
The term "volume" used throughout this document refers to a disc pack that is mounted in a disc drive.
The following information 1s returned from HPVOLINFO:
System Information
e Drive type O
e Capacity of a volume
e Sector size of a drive
e Amount of volume space used by MPE
e Spool file space usage
e Permanent and temporary file space usage
e Volume type
e Volume set name
e Number of volume classes
e List of volume classes
e Ldev that a volume is configured on
e Free space information
e Number of member volumes
e List of member volume names O
e Number of volume sets
e List of volume sets
New STORE Option - PACKED
by Ching-Ching Su
Commercial Systems Division
To improve the performance of a labeled tape STORE, a new labeled STORE tape format 1s now available.
Results of STORE performance testing shows the new labeled tape STORE performance has significantly
improved (e.g., an 86% improvement when storing between 200 and 1000 files) over that of regular
labeled tape and is comparable to that of unlabeled tape. In this article, the new labeled STORE tape will
be referred to as PACKED tape.
USER INTERFACE
Customers can use the new STORE option PACKED to create the PACKED tape. All STORE/RESTORE
functions that apply to regular labeled tape also apply to PACKED tape.
2-2
System Information
Syntax
: STORE filesetlist;#storefile;PACKED
Creation of the PACKED tape is similar to that of regular labeled tape. First, the user must setup a :FILE
equation describing the destination device, the volumeset, etc., prior to issuing a valid STORE command.
Second, the user must state the PACKED option in the STORE command.
For example, when preparing for a backup to the volume VOLOG6, the following file equation wouid be
entered:
FILE T;DEV=TAPE;LABEL=VOLO6
This would be followed by the STORE command:
:STORE filesetlist;*T; PACKED
Restoring files is identical to that of regular labeled tape.
TAPE FORMAT
The PACKED tape format conforms to ANSI labeled tape format. For PACKED tape, STORE places all
of the STORE/RESTORE data into one logical file. Only a user header label generated by
STORE/RESTORE is not within the file data area. The STORE/RESTORE data is laid out the same
order as the regular labeled tape, but disk file images are separated by a simulated tapemark rather than a
set of trailing labels for one file followed by a set of header labels for the successor file. The simulated
tapemark is an eighty byte record that contains the ASCII character string "End of logical file."
Following 1s the format of PACKED tape.
2-3
System Information
Volume 1 of 2
VIH|H|U S S E|E
o|DID |, | [ae - | FLE |5 | FLE |T (0/0 |"]1
L|R|R M [Directory #1 42 |M|V|V|M|M
1 |112 |! M M 1|2
STORE
Note: When the file spans more than
Header Label | |
Volume 2 of 2 one volume, EOV is written
Tape Mark instead of EOF.
Simulated Tape Mark
и р
VIHIHIU TS S | FILE ELE
olDlD T [Remainder т Таре > I T lo TIT
L | RIR M |ot File #2 Di М | Е | Е М
1 2 L M rectory M (complete) 119
Figure 1. Packed Tapes 6
2-4
System Information
Multiple Database Transaction Logging (MDB X)
by Ron Harnar and Mark Boronkay
Data Management Systems Division
TurboIMAGE provides a transaction logging and recovery capability that allows a programmer to group
multiple TurboIMAGE intrinsic calls into logical transactions that are treated as single units of work
during database recovery. In the past, the logging and recovery capability was limited to transactions
involving a single database. This posed problems for complex applications with units of work that span
multiple databases. To address this specialized requirement, TurboIMAGE is providing a
multiple-database transaction (MDBX) capability.
The following changes have been made to TurboIMAGE in order to support MDBX:
e The TurboIMAGE intrinsics DBBEGIN and DBEND are enhanced so that programmers can define
MDBXs involving up to 15 databases.
e À new mode (404) 1s added to DBINFO for obtaining information about MDBXs.
e The DBRECOV utility 1s modified to allow recovery of MDBXs.
e New operational requirements are enforced for applications that use MDBXs.
e The TurboIMAGE log file 1s changed to permit logging of MDBXs.
Two types of MDBXs are available-optimized and non-optimized. A non-optimized MDBX makes use of
DBBEGIN and DBEND records in the user log file. An optimized MDBX generates new logging records
(MDBXBEGIN and MDBXEND) designed to save space in the log file.
NOTE
The use of the new log records generated by an "optimized" MDBX will
prevent Silhouette from processing these entries appropriately. It is
therefore recommended that Silhouette users use "non-optimized"” MDBXs
on log files that are accessed by Silhouette.
The use of MDBX 1s optional. TurboIMAGE applications that are currently using single-database
transactions can continue to do so without any coding or operational changes. The above changes apply
only if the programmer wishes to take advantage of the MDBX enhancen:ent.
These enhancements are also available in the previous MPE/V Release 21 with version C.00.67 of
TurboIMAGE/V.
2-6
ADDITIONAL SOFTWARE PRODUCTS
Announcing Information Access A.06
by Guy Randazzo
Software Technology Division
INTRODUCTION
The A. 06 version of Information Access is being released with MPE V Release 22 (G. 22.00). Besides the
usual defect fixes, it contains a number of very useful enhancements. Each enhancement 1s described in
some detail below. ( The corresponding MPE XL version 1s A. 06.11, which will ship with the MPE XL
3. 0 Retrofit).
NEW CONVERT FUNCTION
A new function has been added to Access Server that can be used in the SQL statement or in ADMIN
view tables. The function, CONVERT, can be used to convert any data type to any other data types.
Some general uses include:
e Convert character strings to any numeric type.
e Convert one numeric type to another, possible to output to a binary file to be read by a special
application.
e Convert a numeric type to a character string (for date conversion, for example)
e To shorten or lengthen a character string.
e Format a numeric as a character string, specifying decimal place.
CONVERT Syntax
The exact syntax of the new function:
NEW ITEM = CONVERT (expression,datatype-len, {decimals{,conv-type}})
expression --> See Appendix C of the Database Administration manual
datatype-len --> I1 | 12 | I3 | I4 | R2 | R4 | L | C len | X len
| P len | Z len | N len
decimals --> constant
conv-type --> C | R (Used if converting to I, P or Z only).
3-1
Additional Software Products
NOTE
Converting numeric types to ’X’ type indicates that the numbers should O
be zero padded on the front. If converting to 'C”, then extra zeros are
stripped from the converted character string. Using the ’X’ type is
convenient when converting dates where you want the zero padding in
front of the day or month. This feature is available on MPE V version
A. 06.02, and MPE XL version A.06.12, and later. It is not available on
MPE XL version A.06.11.
CONVERT Examples
Here are a few examples of 1t’s use:
*
* The first example breaks up a product number into two pieces, its
* type, which is a character string and its sub-type. Just to
* demonstrate the capability of the CONVERT function, the 3 byte ASCII
* numeric string is converted to an integer.
SQL
SELECT
PRODUCT-NBR , TYPE = SUB(PRODUCT-NBR, 1,3) ,
SUB-TYPE = CONVERT (SUB(PRODUCT-NBR,4,3),11) O
FROM
ORDER-DETAIL;
#
* Next, we convert the on hand quantity, which is a packed number,
* to a character string with no decimal places.
#
SQL
SELECT
PRODUCT-NBR, ON-HAND-QTY,
NEW-ON-HAND-QTY = CONVERT (ON-HAND-QTY,C8,0)
FROM
INVENTORY;
*
* Finally, we convert both unit cost and price to a 2 word or 4 byte
* integer because these items are packed decimal and we are using a
PASCAL program to read a binary file and PASCAL does not support
* packed decimal.
+
#
SQL
SELECT
PRODUCT-NBR, UNIT-COST = CONVERT(UNIT-COST,I2),
PRICE = CONVERT(PRICE,I2)
FROM
PRODUCT -MASTER
+
* This last example demonstrates some arbitrary uses.
3-2
Additional Software Products
+
SQL
SELECT
c20-to-p20 = CONVERT(c20,P20,6,R),
c10-to-c20 = CONVERT(c10,C20),
small-mult = CONVERT(item1-i2 * item2-i2, I1),
int-to-c = CONVERT(i2, C6),
r4-to-c30-6= CONVERT(r4, C30, 6),
date = CONVERT (month,X2) + ”-” + CONVERT(day,X2) + "-" +
CONVERT (year,X2)
FROM
generic-table;
IMAGE AUTOMATIC MASTERS AS TABLES
In ADMIN on the Environment Configuration menu, a new function key has been added which says Auto
Masters. The function key will take you to a screen which lets the DBAs indicate whether they want
automatic master datasets to be considered valid for configuration as IMAGE tables. If you choose this
option, then the automatic master datasets will be displayed when adding IMAGE tables.
ADMIN QUICK CONFIGURATION
In ADMIN on the Add Table menu, a function key has been added which says IMAGE Quick Def. This
function key will take you to 2 screens which allow you to configure more than one dataset at a time. On
the first screen, you enter the database information. On the second screen, you will get a list of all the
dataset names in the database. Select which datasets you want to be configured as IMAGE tables. The
default table name is the same as the dataset name, but you can change this. After pressing the ENTER
key, each table will be added with all of the items in the dataset using the default data conversions. The
Change Table screens can then be used to modify the selection of items and their data conversions, if
desired.
2048 CHARACTER ITEM CLAUSE
Starting with Access Server A.06, the 1tem clause length has been increased from 1024 to 2048 bytes.
This will allow users to create view tables that are far more complex and useful. The current 1024 byte
limit is very restrictive when a need for sophisticated view tables arises.
GROUP BY CLAUSE INCREASED
The GROUT BY clause in Access Server has been increased from 160 characters to 320 characters. This
1s because NewWave Access will often fully qualify the item names if duplicate names exists in tables that
are joined, making the 160 character limit too severe.
3-3
3-4
O
TECHNICAL ARTICLES
4
HPVOLINFO Volume Intrinsic
by Pat Alvarez, Wayne Booth, Marck Dovi and Lalitha Pejavar
HPVOLINFO
Computer Systems Division
Returns volume information.
SYNTAX
HPVOLINFO
);
( status,
volspecifiernum, volspecifier [,itemnum, item][...]
Volume information 1$ returned by the HPVOLINFO intrinsic. Up to six items of information can be
retrieved by specifying one or more itemnum/item pairs. The itemnum/item parameters must appear in
pairs. Note, some of the itemnums to HPVOLINFO are MPE V specific while others are MPE XL specific.
PARAMETERS
status
32-bit signed integer (optional)
Returns the status of the HPVOLINFO call. If no errors or warnings are
encountered, status returns 32 bits of zero. If errors or warnings are
encountered, status is interpreted as two 16 bit fields.
Bits (0:16) comprise status.info. A negative value indicates an error
condition, and a positive value indicates a warning condition.
Bits (16:16) comprise status.subsys. The value represented by these bits,
defines the subsystem that set the status information. On MPE XL, the
volume management identification number is 163. On MPE V, this field will
contain a 0.
4-1
Technical Articles
4-2
Since HPVOLINFO can return information on
the success of its execution in the status
parameter, it is good programming practice to
specify this parameter and check its value
after the intrinsic call. If an error condition
is encountered and the caller did not specify
the status parameter, HPVOLINFO causes the
calling process to abort.
The values of status.info that can be returned from a call to HPVOLINFO
are listed below.
Error Number
-150
- 151
-152
- 153
- 154
-155
-156
-157
-158
-159
-160
-161
-162
-163
-164
-165
Meaning
No errors or warnings (Successf ul call).
Invalid itemnum.
Itemnum or item missing (not paired).
Required parameter omitted.
Parameter address out of bounds
Split stack calls not allowed.
Ldev, volume set/class, volume not mounted.
Invalid volume specifier number.
Invalid volume specifier.
Ldev not a disc ldev.
Device class not configured for volumes.
Device class does not map into a volume class.
Free space range sizes not in ascending order.
Invalid number of free space ranges specified.
Volume class cannot be specified with system set.
Error while scanning the directory.
Volume label 1s unreadable.
-166
-167
-168
-169
-170
-171
-172
-173
-174
-175
-176
-177
-178
-179
150
151
Technical Articles
Disc free space map is bad.
Allocation is disabled for disc free space map.
Defective tracks table 1s unreadable.
Disc I/O error.
Virtual memory 1s only valid on system volumes.
Directory size 1s not valid for specified volume.
Spool files are only valid on system volumes.
Item number 1s only valid on MPE XL systems.
Item number 1s only valid on MPE Y systems.
List length specified is invalid.
Item number / volume specifier number
combination 1s illegal.
Item is not yet implemented.
Volume table is in an inconsistent state.
Unrecognized drive type.
Array passed in cannot hold all names - List
truncated.
File label is unreadable.
In addition, the following warnings/errors may be returned by the XL version of HPVOLINFO:
-180
-181
-182
-183
-184
-185
Physical I/O error.
An unexpected error was detected. The error stack
should be checked to determine the exact error.
An error was detected in the label management
subsystem. The error stack should be checked to
deterinine the exact error.
Disc access error. The error stack should be checked
to determine the exact error.
A mirrored volume that was specified 1s disabled.
The volume set specified 1s not a volume set on the
system.
Technical Articles
volspecifiernum
volspecifier
4-4
-186 The volume class specified is not present in the
volume set specified.
-187 The member volume specified 1s not present in the
volume set specified.
152 Parts of the set or class are not mounted. Data was
only gathered on the portion of the set or class that
was mounted so the data may be incomplete.
16-bit signed integer by value (optional)
A 16-bit integer indicating which volume specifier is to be used to obtain
information from HPVOLINFO. The default value for this parameter is O if
it is not included by the caller. This parameter is used in conjunction with
the volspecifier parameter. The following are valid volume specifier
numbers:
0 volume specifier is ignored. Using this specifier number is
equivalent to specifying all the volumes on the system.
] volume specifier 1s the logicai device number of the volume for
which information is to be obtained.
2 volume specifier is a volume set name.
3 volume specifier is a volume set/volume class name pair.
4 volume specifier 1s a volume set/volume name pair.
5 volume specifier 1s a device class name.
type varies (optional)
The volspecifier is optional when the volspecifiernum is O since the
volspecifier 1s ignored. However, for volspecifiernums 1 through 5, the
volspecifier parameter must be specified. On MPE V, volspecifier must be
declared as a byte array. The data type of the volspecifier depends on the
volspecifiernum:
volspecifiernum volspecifier
0 1gnored
1 16-bit signed integer
2,3,4,5 character array
Technical Articles
When a 01s used as the volspecifiernum, the volspecifier is ignored. When a
volspecifiernum of O is used, it refers to all the volumes on the system. This
includes all the system and nonsystem volumes.
When a lis used as the volspecifiernum, the volspecifier must be a ldev
number which corresponds to a configured and mounted volume. An ldev
number can be any number between 1 and 999.
For the character specifiers, the first character determines the delimiter
character for the parameter. The delimiter must be printable, cannot be
alphanumeric, and cannot be one of the special characters "." "", or " "as
explained below. For example, to pass the volume set FOO, the following
array 1$ a valid way to pass FOO using ’% as the delimiter: ZFOO%.
For specifiers 3 and 4, the volume set name and the volume class or volume
name must be separated by a colon. For example, %SET1:CLASSO% or
ZSET?2:VOLUME8% may be used. A colon (:) cannot be used as a delimiter
character.
Since a volume set or class can be fully qualified on MPE Y, periods (.) are
allowed in the name. Because periods (.) and underscores (__ ) are allowed in a
MPE XL name, these characters (period and underscore) cannot be used as
delimiters.
With specifiers 2 and 3 on MPE Y, for private volumes, a volume set/class
name may be partially or fully qualified (e.g. VSETNAME. GROUP, ACCNT
or CLASSNAM.GROUP.ACCNT). Each field of the name must be one to
eight alphanumeric characters (beginning with a letter) for a possible total of
55 characters, e. g.:
ASETxxxxx. GROUPxxx. ACCOUNTx:CLASSxxx. GROUPxxx. ACCOUNTx%
has six e1ght-character fields, four periods, a colon, and two delimiters. When
the volume set or class name 1s not fully qualified, 1t refers to the volume set
or class in the logon group and/or account.
On MPE XL, a valid volume set or class name consists of as many as 32
characters, where the first character is alphabetic, followed by any
combination of alphanumeric characters. The MPE XL name may include
the underscore (_) and the period (.).
On MPE XL, the name of the system volume set 15
"MPEXL_ SYSTEM VOLUME SET". Since the system volume set on MPE
V does not have a predefined name, the name
"MPEXL SYSTEM VOLUME SET" is used to be compatible with MPE
XL. On both MPE V and MPE XI, for items that return volume set names
(1.e. item #3 and item #12), this name is returned when returning the system
volume set name.
Note that when the system volume set name is used on MPE У, 11 cannot be
followed by a class name (see discussion of volume specifier number 5 below).
Also, on MPE V group and account names cannot be used to partially or fully
4-5
Technical Articles
qualify the set or volume name when the system volume set name 1$
specified. O
For specifier 4 on MPE V, a volume name consists of up to 8 alphanumeric
characters, beginning with a letter. For private volumes, names may be
partially or fully qualified (e.g. VNAME.GROUP.ACCNT). Each field of
the name must be one to eight alphanumeric characters (beginning with a
letter) for a possible total of 55 characters, e. g.:
ZSETxxxxX. GROUPxxx. ACCOUNTx:NAME=xxxx. GROUPxxx. ACCOUNTXx%#
has six eight-character fields, four periods, a colon, and two delimiters. When
the volume name 1s not fully qualified, it refers to the volume name in the
logon group and/or account.
On MPE XL for specifier 4, the volume name consists of any string consisting
of 1 to 16 alphanumeric characters, underscores, or periods, where the first
character is alphabetic.
On MPE Y, the concept of a volume class does not exist for the system volume
set, therefore, in order to access a subset of the system volume set, device
classes are used. But, on MPE XL, the concept of volume classes 1s valid for
both system and nonsystem volume sets and therefore, volume classes take the
place of device classes. Specifier §, for Item# 6 and 7 provides compatibility
between MPE V and MPE XL. Specifier 5 passes the device class of a group
of volumes as they apply to the I/O configuration. The maximum number of
characters allowed in the string is 8. On MPE V, when this specifier 1s used,
it must refer to a device class that 1s configured to a group of vclumes.
On MPE XL, when a device class name is specified, a configured and mounted
volume class with the same name must exist in the system volume set. Data
will be returned based on this volume class in the system volume set if it
exists; otherwise an error will result.
1temnum 16-bit signed integer by value (optional)
Cardinal number of the item desired. This specifies which item value is to be
returned. Refer to Item# in Table 2-2.
item type varies (optional)
On MPE Y, item must be declared as a byte array. The actual type of the
item specified by the corresponding item number. Refer to Item in Table
2-2.
SPECIAL CONSIDERATIONS
No special capabilities are required in order to use the HPVOLINFO intrinsic.
Split-stack calls are not permitted.
4-6
Technical Articles
When an error is returned, the values in the item parameters are all undefined. It is not guaranteed that
the data returned in an item 1s meaningful if any status value less than O 1s returned.
On MPE V, real values are accepted from the caller and returned to the caller in 64-bit HP3000 format.
This 1s the default format for MPE V.
On MPE XL, real values are accepted from the caller and returned to the caller in the format that is the
default for the mode of the caller. If the intrinsic 1s called from compatibility mode, then any real values
specified to HPVOLINFO must be in 64-bit HP3000 format and any real values returned by
HPVOLINFO will be in that format. If the intrinsic is called from native mode, then any real values
specified to HPVOLINFO must be in 64-bit IEEE format and any real values returned by HPVOLINFO
will be returned in that format. Since the format used is always the default for the mode of the caller,
this difference will have no impact on porting between MPE V and MPE XL.
If a lot of activity is occurring on the system while this intrinsic 1s called, some of the item values
returned may not reflect the expected result. For example, when HPVOLINFO is called to return the disc
space used by permanent files, a value 1s returned. But, if immediately after the value 1$ returned, a
process on the system purges a file (FCLOSEs a file with disposition 4), the value will not reflect this
difference.
On MPE V, a set or class is considered to be logically mounted if all of its members are logically mounted
(i.e. LMOUNT or MOUNT command was used).
On MPE XL, if the volume specifier 1s a set or class then at least the master volume must be logically
mounted (i.e. volume must be in a master or member state). If the volume specifier 1s a logical device
number or a volume name then both the volume specified and the master volume (of the set enclosing the
volume specified) must be logically mounted.
If the volume specifier 1s a logical device number then it must be a member of a set or class that is
logically mounted. If the volume specifier is a volume set name then the set must be logically mounted.
If the volume specifier 1s a volume class name then the class must be logically mounted. If the volume
specifier is a volume name then that volume must be a member of a set or class that 1s logically mounted.
When the volume specifier is a device class name, all of the logical device numbers in the specified device
class must be members of logically mounted sets/classes. Finally, all the volumes on the system (whether
they are logically mounted or not) may be specified by using volume specifier number 0.
If the volumes for volume specifier numbers 1 through 5 are not logically mounted as specified above
then the HPVOLINFO intrinsic will return a "volume not mounted" error. If the caller chooses to
continue with the same specifier, the LMOUNT (on MPE V) or VSOPEN (on MPE XL) command can be
used with the COMMAND or HPCICOMMAND intrinsic to logically mount the appropriate volume
sets/classes. If a volume is taken offline while the intrinsic is accessing it, the process will hang (because
IOs cannot complete to the disc) until the volume is back online.
On MPE XL, since mirrored discs maintain identical copies of the same information on two discs, the
values that are returned by this intrinsic reflect information from only one of the volumes in a mirrored
disc pair. When retrieving an ldev number (Item# 13) using a volume name that is associated with a
mirrored disc pair, only one of the ldev numbers of the mirrored pair will be returned. Which one of the
two ldev numbers will be returned 1s random and therefore, 1t should be noted that the ldev number
returned in this case may be different across system start ups. Subsequent use of the ldev numbers
returned for mirrored discs are guaranteed to provide accurate information for the mirrored volume set.
On MPE XL, if information 1s requested for the split backup volume set the information returned will be
for the split user volume set.
4-7
Technical Articles
ITEM NUMBER, ITEM
SUMMARY
The itemnums and items are described here. All item parameters are passed by reference.
Item# = 2
Item# = 3
Item# = 4
Item# = 5
4-8
Number of Volume Sets
Returns the number of system and nonsystem volume sets that are configured
on the system. This item may be used in conjunction with Item# 3. This
item returns a 32-bit signed integer containing the number of volume sets.
Note: O is the only valid specifier.
List of Volume Set Names
Returns a list of all the system and nonsystem volume set names mounted on
the system. On MPE V, the volume set name is fully qualified for private
volumes (i.e. "volume-set-name. group.account"), each field consisting of one
to eight alphanumeric characters, for a possible total of 26 characters (a
name, group, and account and two periods). On MPE XL, the volume set
name consists of a string consisting of 1 to 32 alphanumeric characters,
underscores, or periods. The item must be a character array where the list of
set names will be returned. The first 4 bytes of the array are interpreted as a
32-bit integer describing the length of the array. The caller must set this
value to equal the maximum number of names that will fit in the array being
passed. Item# 2 can be used to determine the maximum number of names
that could be returned. Upon return, the value will have been modified to
reflect the actual number of names returned. The remaining bytes will be
mapped to a list of 32-byte names.
Number of Volume Classes
Returns the number of volume classes that a volume or volume set is
associated with. This item may be used in conjunction with Itemé $. A
volume can be associated with more than one volume class, therefore, when a
1 or 4 is used as the specifier, the number returned is the number of volume
classes that the volume is a member of. When a 2 1s used as the specifier, the
number returned 1s the number of volume classes that are a subset of the
volume set. On MPE XL, this number only includes classes whose members
are all logically mounted. This item returns a 32-bit signed integer
containing the number of volume classes.
List of Volume Class Name
Returns a list of volume class names. A volume can be associated with more
than one volume class, therefore, when a | or 4 is used as the specifier, the list
returned is a list of volume classes that the volume is a member of. Whena 2
1s used as the specifier, the list returned 1s a list of volume classes that are a
subset of the volume set. On MPE XL, the list only includes the names of
classes whose members are all logically mounted. On MPE V, the volume
class name 15 fully qualified for private volumes (i.e.
"volume -class-name. group.account”), each field consisting of one to eight
alphanumeric characters, for a possible total of 26 characters (a name, group,
and account and two periods). On MPE XI. the volume class name consists of
Item = 6
Item# = 7
Technical Articles
a string consisting of 1 to 32 alphanumeric characters, underscores, or
periods. The item must be a character array where the list of class names
will be returned. The first 4 bytes of the array are interpreted as a 32-bit
integer describing the length of the array. The caller must set this value to
equal the maximum number of names that will fit in the array being passed.
Item# 4 can be used to determine the maximum number of names that could
be returned. Upon return, the value will have been modified to reflect the
actual number of names returned. The remaining bytes will be mapped to a
list of 32-byte names.
Number of Member Volumes
Returns the number of member volumes in the specified volume set/class or
device class. This item may be used in conjunction with Item# 7. When a 2
or 3 is used as the specifier, the number of member volumes that make up the
volume set or class is returned. When a 5 is passed, the number of member
volumes configured with the passed device class is returned. For specifier 2
or 3, the returned number includes the master volume in the total count. For
example, 1f a volume set consists of a master volume, MASTER and two
member volumes, MEMBER] and MEMBER2, and the specifier used 1s a
volume set name, the number that will be returned for this item is three. On
MPE XL, since you can remove some or all of the volumes in a volume set
(excluding the master volume), this number will depend on the number of
volumes you have mounted at the time the intrinsic call is made. On MPE V,
since the concept of master and member volumes only refer to private
volumes, if the system volume set is specified, the count will consist of the
number of volumes that are designated as system volumes. On MPE XL, since
mirrored discs maintain identical copies of the same information on two discs,
the number returned by this item will reflect only one of the volumes in a
mirrored disc pair. This item returns a 32-bit signed integer containing the
number of member volumes.
List of Member Volume Names
Returns the list of names of the member volumes in the specified volume
set/class or device class. When a 2 or 3 is used as the specifier, the list of
member volumes that make up the set or class 1s returned. When a 5 is
passed, the list of member volumes configured with the passed device class is
returned. On MPE V for specifier 2 or 3, the returned list will include the
master volume. On MPE XL, a volume class need not include the master
volume so that specifier 3 may return a list that does not include the master
volume. On MPE XL, since you can remove some or all of the volumes in a
volume set (excluding the master volume), this list will depend on the number
of volumes you have mounted at the time the intrinsic call 1s made. On MPE
V, since the concept of master and member volumes only refer to private
volumes, 1f the system volume set 1s specified, the list will consist of the list of
volumes that are designated as system volumes. The item must be a character
array where the list of member volumes will be returned. The first 4 bytes
of the array are interpreted as a 32-bit integer describing the length of the
array. The caller must set this value to equal the maximum number of
names that will fit in the array being passed. Item# 6 can be used to
determine the maximum number of names that could be returned. Upon
return, the value will have been modified to reflect the actual number of
names returned. The remaining bytes will be mapped to a list of 32-byte
names.
4-9
Technical Articles
Item# = §
Item# = 9
Item# = 10
Item/# = 11
Item# = 12
Item# = 13
Drive Type
Returns the type of the drive specified. The drive type refers to the name of
the drive, i.e. HP7935 or HP7937. The character array that is used must be
large enough to contain the longest type string, currently 13 characters.
Drive Sector Size
Returns the drive’s logical sector size. Currently this logical size 1s 256 bytes.
In the future, discs may have different physical sector sizes. However, MPE
will map them to system wide logical sector sizes. This item returns a 32-bit
signed integer containing the drive’s logical sector size in bytes.
Volume Type
Returns a 32-bit integer value specifying the volume type. Valid types are:
1 - System Volume
2 - NonSystem Volume
On MPE, there are two types of volume sets - the system volume set and the
nonsystem volume sets. A volume from the system volume set is considered a
system volume, and a volume from the nonsystem set is considered a
nonsystem volume. On MPE V, a nonsystem set is equivalent to a private
volume set.
Volume Name
Returns the volume name of the specified ldev. On MPE V, the volume name
is fully qualified for private volumes (i.e. "volume-name. group.account"),
each field consisting of one to eight alphanumeric characters, for a possible
total of 26 characters (a name, group, and account and two periods). On MPE
XL, the volume name consists of a string consisting of 1 to 16 alphanumeric
characters, underscores, or periods. The character array must be specified
with a length of 32 bytes.
Volume Set Name
Returns the volume set name corresponding to the passed ldev. A ldev can be
associated with only one volume set. On MPE V, the volume set name is fully
qualified for private volumes (i.e. "volume-set-name.group.account"), each
field consisting of one to eight alphanumeric characters, for a possible total of
26 characters (a name, group, and account and two periods). On MPE XL, the
vulume set name consists of a string consisting of 1 to 32 alphanumeric
characters, underscores, or periods. The character array must be specified
with a length of 32 bytes.
Logical Device Number
Returns the logical device number of the specified volume. On MPE XL,
since mirrored discs maintain identical copies of the same information on two
discs, either of the two discs may be returned by this item. This item returns
a 16-bit signed integer containing the logical device number.
Volume Capacity
Item# = 14 & 15
Item# = 16 & 17
Item# = 18 & 19
Item# = 20 & 21
Technical Articles
Returns the volume capacity. When a l or 4 is used as the specifier, the
volume capacity consists of the capacity of the volume whose ldev or volume
name was specified. When a 2 or 3 is passed, the capacity of the volumes
that make up the volume set or class are totaled and this total value is
returned. Item# 14 returns a 64-bit signed integer containing the volume
capacity in sectors and item# 15 returns it as a 64-bit real.
Total MPE Overhead
Returns the total MPE overhead. The total MPE overhead consists of
everything on a volume that is not set aside for file space use. In other
words, the overhead is the volume space that is used for operating system
purposes. Some of the space that is considered MPE overhead includes the
following: on MPE V - volume label, virtual memory, directory, defective
tracks/sector table, initial segments, disc cold load information table, volume
table, free space map and channel programs; on MPE XL - volume label, file
label table, directory, volume set information table, free space map, transient
space, and transaction management overhead. A subset of the MPE overhead
is returned through itemnums 18 & 19 (MPE XL transient space), 20 & 21
(MPE XL configured transient space), 22 & 23 (MPE V virtual memory), 24 &
25 (Directory), 26 & 27 (MPE XL file label tables), and 28 & 29 (MPE XL
transaction management ). When a lor 4 1s used as the specifier, the total
MPE overhead consists of the MPE overhead on the volume whose ldev or
volume name was specified. When a 2 or 3 is passed, the MPE overhead on
the volumes that make up the set or class is returned. Note: the files that
comprise the code for the operating system are not included in this overhead.
Item# 16 returns a 64-bit signed integer containing the total MPE overhead
in sectors and item# 17 returns it as a 64-bit real.
MPE XL Transient Space Overhead
Returns the MPE XL transient space overhead. This item is only valid on
MPE XL. The transient space overhead 1s volume space that is used for
temporary processes such as stacks, heaps, and operating system data
structures. When a 1 or 4 is used as the specifier, the transient space consists
of the transient space on the volume whose ldev or volume name was
specified. When a 2 or 3 is passed, the transient space on the volumes that
make up the set or class 1s returned. The transient space overhead 1s a subset
of the total MPE overhead (Item# 16 & 17). Item# 18 returns a 64-bit
signed integer containing the transient space overhead in sectors and item#
19 returns it as a 64-bit real.
Configured Maxiruum MPE XL Transient Space
Returns the configured maximum MPE XL transient space. This item 1s only
valid on MPE XL. The configured maximum MPE XL transient space
overhead 1s volume space that is configured for transient space use, but is not
necessarily used. See Item# 18 & 19. It is the space that is configured for
stacks, heaps and operating system structures. When a 1 or 4 is used as the
specifier, the configured maximum transient space consists of the configured
transient space on the volume whose ldev or volume name was specified.
When a 2or 31s passed, the configured transient space on the volumes that
make up the volume set or class is returned. Item# 20 returns a 64-bit
signed integer cortaining the configured maximum transient space in sectors
and 1t&m# 21 returns it as a 64-bit real.
MPE V Virtual Memory Overhead
Technical Articles
Item = 22 8 23
Item# = 24 & 25
Item# = 26 & 27
Item# = 28 & 29
Returns the MPE V virtual memory overhead. This is only valid on MPE V.
The MPE V virtual memory overhead is the amount of volume space that is
allocated for saving segments of main memory temporarily. The amount of
configured virtual memory space 1s equivalent to the amount of used virtual
memory space. Virtual memory on MPE V, 1s allocated on system volumes
only. There is no virtual memory on private volumes. When a | or 4 is used
as the specifier, the virtual memory overhead consists of the virtual memory
on the volume whose ldev or volume name was specified. When a 2 1s passed,
the only valid specifier 1$ "MPEXL SYSTEM VOLUME SET" since
virtual memory is allocated only on system volumes. Because virtual memory
1s only valid on the MPE V system volume set and because the concept of
volume classes does not hold for the MPE V system volumes, specifier 3 is not
a valid specifier for this item. The MPE V virtual memory overhead is a
subset of the total MPE overhead (Item# 16 & 17). Item# 22 returns a
64-bit signed integer containing the virtual memory overhead in sectors and
item# 23 returns it as a 64-bit real.
Directory Space Overhead
Returns the Directory space overhead. Directory space is the area on system
and nonsystem volumes reserved for accounting information. More
specifically, the directory space overhead consists of the directory space used
for permanent files. When a lor 4 1s used as the specifier, the directory
space overhead consists of the directory space on the volume whose ldev or
volume name was specified. When a 2 or 31s passed, the directory space
overhead on the volumes that make up the volume set or class is returned.
On MPE V, the system directory is allocated on ldev 1 and for private
volumes the directory 1s allocated on the master volume of the volume set or
class. Therefore, specifying a volume set or class will give you the same
results as specifying the master volume of the set or class. The directory
space overhead 1s a subset of the total MPE overhead (Item# 16 & 17).
Item# 24 returns a 64-bit signed integer containing the directory space
overhead in sectors and item# 25 returns it as a 64-bit real.
MPE XL File Label Overhead
Returns the MPE XL file label overhead. This item 1s only valid on MPE XL.
On MPE XL, each volume has its own Label Table. The Label Table contains
file labels and extent descriptors for files that begin on that volume. When a
1 or 4 1s used as the specifier, the file label overhead consists of the overhead
on the volume whose ldev or volume name was specified. When a 2 or 3 is
passed, the file label overhead on the volumes that make up the set or class 1s
returned. The file label overhead is a subset of the total MPE overhead
(Item# 16 & 17). Item# 26 returns a 64-bit signed integer containing the
file label overhead in sectors and item# 27 returns it as a 64-bit real.
MPE XL Transaction Management Overhead
Returns the MPE XL transaction management overhead. This item is only
valid on MPE XL. The transaction management overhead consists of any
logging information that is maintained in order to provide file consistency
and also file recovery. When a | or 4 1s used as the specifier, the transaction
management overhead consists of any logging information kept on the
volume whose ldev or volume name was specified. When a 2 or 3 is passed,
the transaction management overhead on the volumes that make up the
volume set or class 1s returned. The transaction management overhead 1s a
subset of the total MPE overhead (Item# 16 & 17). Item# 28 returns a
Item# = 30 & 31
Item# = 32 & 33
Item# = 34 & 35
Item# = 36 & 37
Technical Articles
64-bit signed integer containing the transaction management overhead in
sectors and item# 29 returns it as a 64-bit real.
Spool File Disc Space Usage
Returns the MPE spool file disc space usage. Spool file space consists of the
volume space that is used by hidden spool files. Hidden spool files are files
that are not a part of the permanent file space. This space can only be found
on system volumes that are configured with the device class of SPOOL. Spool
file space is not allocated on nonsystem volumes. When a 1 or 4 is used as the
specifier, the spool file space consists of the space that is used on the volume
whose ldev or volume name was specified. When a 2 is used as the specifier,
the volume set name must refer to the system volume set name. Using 3 asa
specifier 1s only valid on MPE XL. Item# 30 returns a 64-bit signed integer
containing the spool file disc space usage in sectors and item# 31 returns it as
a 64-bit real.
Disc Space Used by Permanent Files
Returns the disc space used by permanent files. When a 1 or 4 is used as the
specifier, the disc space used by files consists of the disc space used by
permanent files on the volume whose ldev or volume name was specified.
When a 2 or 3 1s passed, the disc space used by permanent files on the
volumes that make up the volume set or class is returned. Item# 32 returns a
64-bit signed integer containing the disc space used by files in sectors and
item# 33 returns it as a 64-bit real.
Reserved for Disc Space Used by Temporary Files
Free Space Distribution Array
Returns the free space distribution array. The caller passes an array that
specifies a series of ranges. The intrinsic will return the number of free areas
whose size 1s within each of the ranges. The caller must pass an array of
64-bit values. The values may be in integer format (Item# 36) or real format
(Item# 37). On MPE V, the largest value that may be specified in either
format is 2,147,483,646. Real values will be rounded off by the intrinsic.
The first value is the number of ranges (minimum number of ranges is 2 and
the maximum is 16). The remaining values are the lower bounds for the
ranges in ascending order. Upon return, the first element will be the number
of free areas whose size is smaller than the smallest bound specified. Each
remaining element will be the number of free space areas whose size 1s
greater than or equal to the bound and less than the next larger bound. The
following shows an example which returns values in 6 ranges.
Array Values
Index Passed In Free Area Size Ranges
1 6 1 = 9 contiguous sectors
2 10 10 - 99 contiguous sectors
3 100 100 - 999 contiguous sectors
4 1000 1000 - 9999 contiguous sectors
5 10000 10000 - 99999 contiguous sectors
6 100000 100000 - and up contiguous sectors
4-13
Technical Articles
Item# = 38 & 39
Item# = 40 & 41
Item# = 42 & 43
For example, if there are 4 areas of free space that are between the sizes of
100 and 999, the third value of the free space distribution array would
contain a 4 upon return. NOTE: the number of ranges specified in the
example (in the first element of the array) is 6, but only 5 lower bounds are
specified because the smallest lower bound is assumed to be 1. When a 1 or 4
is used as the specifier, the free space distribution array consists of the
contiguous free space areas on the volume whose ldev or volume name was
specified. When a 2 or 3 is passed, the free space distribution array returns
the total values from the volumes that make up the volume set or class. The
item passed must be a variable length array of 64-bit numbers (maximum
array length of 16 elements). Item# 36 returns an array of 64-bit integers
containing the free space distribution and 1tem% 37 returns 1t as an array of
64-bit reals.
Free Space Distribution Sectors Per Range
Returns the free space distribution sectors per range. The caller passes an
array that specifies a series of ranges. The intrinsic will return, for each
range specified in the array, the total free space for free areas found in that
range. See Item# 36 & 37 for the format of the free space distribution array
passed to the intrinsic and for the format of the returned array.
For example, using the input array from the example in Item# 36 & 37, if
there are 4 areas of free space that are between the sizes of 100 and 999, and
the sizes of these areas are 101, 850, 519, and 432 sectors, the third value of
the return array would contain a 1902 (101+850+519+432 = 1902) When a
| or 4 is used as the specifier, the free space distribution sectors per range
consists of the contiguous free space areas on the volume whose ldev or
volume name was specified. When a 2 or 3 1s passed, the free space
distribution sectors per range returns the total values from the volumes that
make up the volume set or class. The item passed must be a variable length
array of 64-bit numbers (maximum array length of 16 elements). Item# 38
returns an array of 64-bit integers containing the free space distribution
sectors per range and item# 39 returns it as an array of 64-bit reals.
Total Free Space
Returns the total free space on a volume or a group of volumes. When a 1 or
4 is used as the specifier, the total free space consists of the total free space on
the volume whose ldev or volume name was specified. When a 2 ог 3 1$
passed, the total free space on the volumes that make up the volume set or
class 1s returned. Item# 40 returns a 64-bit signed integer containing the
total free space in sectors and 1tem# 41 returns it as a 64-bit real.
Largest Contiguous Free Space Area
Returns the largest contiguous free space area on a volume or a group of
volumes. When a 1 ог 4 1$ used as the specifier, the largest contiguous free
space consists of the largest contiguous free space on the volume whose ldev
or volume name was specified. When a 2 or 3 1s passed, the largest
contiguous free space on the volumes that make up the volume set or class 1s
returned. For example, for specifiers 2 or 3, if a volume set is composed of
the Idevs 2, 3 and 4, and the largest contiguous free space on these volumes
Technical Articles
are 37785, 56528, and 56171, respectively, the value that is returned is
56528. Item# 42 returns a 64-bit signed integer containing the largest
contiguous free space area in sectors and item# 43 returns 1t as a 64-bit real.
4-15
Technical Articles
ITEM# ITEM TYPE APPLICABLE
VOLUME
SPECIFIERS
2 Number of volume sets 132 0
3 List of volume set names CA 0
4 Number of volume class names 132 1,2,4
5 List of volume class names CA 1,2,4
6 Number of member volumes 132 2,3,5
7 List of member volume names CA 2,3,5
8 Drive type CA 1,4
9 Sector size (bytes) 132 1,4
10 Volume type 132 1,4
11 Volume name CA 1
12 Volume set name CA 1
13 Logical device number 116 4
14 Volume Capacity (sectors) 164 1,2,3,4
15 Volume Capacity (sectors) R64 1,2,3,4
16 Total MPE overhead (sectors) 164 1,2,3,4
17 Total MPE overhead (sectors) R64 1,2,3,4
18 MPE XL transient space overhead (sectors)
164 1,2,3,4
19 MPE XL transient space overhead (sectors)
R64 1,2,3,4
20 Configured maximum MPE XL transient space (sectors)
164 1,2,3,4
21 Configured maximum MPE XL transient space (sectors)
R64 1,2,3,4
22 MPE V virtual memory overhead (sectors)
164 1,2,4
23 MPE V virtual memory overhead (sectors)
R64 1,2,4
24 Directory space overhead (sectors) 164 1,2,3,4
25 Directory space overhead (sectors) R64 1,2,3,4
4-16
Technical Articles
26 MPE XL file label overhead (sectors)
164 1,2,3,4
27 MPE XL file label overhead (sectors)
R64 1,2,3,4
28 MPE XL transaction management overhead (sectors)
164 1,2,3,4
29 MPE XL transaction management overhead (sectors)
R64 1,2,3,4
30 Spool file disc space usage (sectors)
164 1,2,3,4
31 Spool file disc space usage (sectors)
R64 1,2,3,4
32 Disc space used by perm files (sectors)
164 1,2,3,4
33 Disc space used by perm files (sectors)
R64 1,2,3,4
34 (Reserved for) Disc space used by temp files (sectors)
164 1,2,3,4
35 (Reserved for) Disc space used by temp files (sectors)
R64 1,2,3,4
36 Free space distribution array 164A 1,2,3,4
37 Free space distribution array R64A 1,2,3,4
38 Free space distribution sectors per range
I64A 1,2,3,4
39 Free space distribution sectors per range
RE4A 1,2,3,4
40 Total free space (sectors) 164 1.2,3,4
41 Total free space (sectors) R64 1,2,3,4
42 Largest contiguous free space area (sectors)
164 1,2,3,4
43 Largest contiguous free space area (sectors)
R64 1,2,3,4
nues 116 16-bit signed integer
I32 = 32-bit signed integer
I64 = 64-bit signed integer
R64 = 64-bit real
CA = character array
I64A = 64-bit signed integer array
R64A = 64-bit real array
Table 2-2
4-17
co
—
I
<
PRODUCT RELEASE INFORMATION
MPE V/E PRODUCT RELEASES
The following table is a Historical/Current list of new products introduced for each MPE V/E version
release for the HP 3000 Computer System. It also includes products added after various releases of the
Master Installation Tape (MIT).
MPE V/E Product Releases
Y. UU. FF. Name Release Product(s) Introduced/ Added
G. 03.04 V-DELTA -4: R28C2 Roll-in of V-Delta-3
SUBSYS Legally The Legally Evaluated DOD release
VUF = Evaluated by SUBSYS VUF = G. À 3. 04
G. A 3. 04 Dept. of HPWORD SERVICES (HP27558)
Defense HPEDIT/V (HP30316)
NSPAD (NSPAD)
G. 03.08 V-DELTA-8 R2944 Roll-in of V-Delta-7
HP CDINSTAL (HP32437)
HP-IB CD-ROM (HPC1 707)
HP LaserRelease
MICRO 3000RX
G.A3.09 V-DELTA-9 R3010 Roll-in of V-Delta-8
HP X. 400/3000 Products (HP32056A)
NewWave Office (B1720A)
(Incorporation of General Release Patches)
G. 1P.00 Platform 1P R 3035 Roll-in of V-Delta-9
Series 6400 Model 1300H DDS
G. 20.00 Release 20 R3042 Roll-in of Platform 1P
HP Search/V (HP36381 A)
HP Browse/V (HP36382A)
G.21.00 Release 21 R3114 Roll-in of Release 20
VPLUS/Windows (HP36393A)
HP GlancePlus/V (HP50733A)
HP DeskManagerPLUS (HP36567 A)*
G. 22.00 Release 22 R 3140 Roll-in of Release 21
Various Enhancements/Fixes
No new products
O *Product has been retrofitted on this version.
Product Release Information
HP POWERPATCH MIT RELEASES
Hewlett-Packard now has a new software support service, HP PowerPatch. This service provides you with
the ability to order current general-release FOS and workstation patches specifically designed for your
system.
HP PowerPatch is provided to those of you who have AMS or RCS software support service agreement.
With HP PowerPatch you will receive the most current set of patches available for your system.
If there is an HP PowerPatch tape available for your release, it should be ordered prior to performing the
installation or update. Contact your Response Center. They will inform you if there is a current patch
tape for the installation/update you are planning to perform. If there is an appropriate HP PowerPatch
tape, you can install it at the same time as the installation/update. These patch sets will -be revised
periodically and are cumulative.
5-2
SUPPORTED RELEASES
Product Release Information
The following matrix provides information on the supported versions of MPE V/E. It lists the currently
supported MITs and the SPUs they are supported on. The matrix also provides all known factory support
termination dates.
date.
SUPPORTED MIT MATRIX
A version of MPE V/E will not have factory support after its support termination
Micro3000 & 3000XE,LX GX
Support
Termination
MITs V.UU. FFs Supported Systems Date
V-Delta-4 G. 03.04, G.B3. 04, 37, 39, 4X, §X, 6X, 70, OCT 1, 1990
G.C3.04 Micro3000 & 3000XE,LX GX
V-Delta-5 G.A3.05, G.B3.05 37, 39, 4X, 5X, 6X, 70, SEPT 1, 1991
Micro3000 & 3000XE,LX,GX
V-Delta-8 G.A3.08 37, 39, 4X, SX, 6X, 70, JAN 1, 1992
Micro 3000 & 3000XE,LX,GX
V-Delta-9 G. A3. 09 37, 39, 4X, SX, 6X, 70, MAY 1,1992
Micro3000 & 3000XE,LX,GX
Platform 1P G.1P.00 37, 39, 4X, 5X, 6X, 70, **AUG 1, 1993
Micro3000 & 3000XE LX,GX
Release 20 G. 20.00 37, 39, 4X, 5X, 6X, 70, ***DEC 1, 1992
Micro3000 & 3000XE,LX,GX
Release 21 G.21.00 37, 39, 4X, SX, 6X, 70, ***DEC 1, 1992
Micro3000 & 3000XE,LX GX
Release 22 G.22.00 37, 39, 4X, 5X, 6X, 70, ***DEC |, 1992
* DOD version (G. 03.04) will be supported indefinitely.
** Or twelve months after the actual first customer ship date of next platform, whichever is later.
*** Or three months after the actual first customer ship date of the next platform, whichever is later.
5-3
+
|
wy
CATALOG OF USER DOCUMENTATION
This section contains a list of customer manuals for the HP 3000 Computer System.
If your contract includes Material Based Services for your appropriate operating system and software
services, you will receive both software and manual updates. For additional copies of manual updates,
Manual Update Services (MUS) can be ordered.
As of this release the subscription services column of this catalog has been removed. Contact your SE for
specific information about subscription services.
Manual Title
Customer
Order No.
Latest Current
Edition Update
FOS SYSTEM MANUALS
General Information Manual
Fundamental 3000 Data Communication Handbook
EDIT/3000 Reference Manual
Using the HP 3000: An Introduction to
Interactive Programming
MPE V Segmenter Reference Manual
MPE V Debug/Stack Dump Reference Manual
Compiler Library Reference Manual
QUERY /3000 Reference Manual
KSAM/3000 Reference Manual
MPE V File System Reference Manual
MPE V System Operation an Resource Management
Reference Manual
MPE V Commands Reference Manual
MPE V Intrinsics Reference Manual
MPE V System Utilities Reference Manual
HP 3000 Guide for the New User
HP 3000 Guide for the New System Operator
MPE Quick Reference Guide
MPE V Storing and Restoring Reference Manual
MPE V System Backup and Recovery User's Guide
MPE V Security & Accounting
MPE V General User's Reference Manual
6-2
5953-7583
5957-4634
03000-90012
03000-90121
30000-90011
30000-90012
30000-90028
30000-90042
30000-90079
30000-90236
32033-90005
32033-90006
32033-90007
32033-90008
32033-90009
32033-90021
32033-90023
32033-90133
32033-90134
32033-90136
32033-90158
10/84
6/84
8/88
4/79
11/82
8/86
11/76
5/87
8/86
10/89
10/89
10/89
10/89
10/89
1/86
4/86
10/89
6/87
6/87
10/88
10/88
8/86
10/88
10/88
Manual Title
Customer
Order No.
Latest Current
Edition Update
Data Entry and Forms Management System
V/PLUS/3000
Using VPLUS/V
FCOPY Reference Manual
Native Language Support Reference Manual
SORT-MERGE/3000 Reference Manual
TurboIMAGE Database Management System
Reference Manual
HP Hi-Li Reference Manual
32209-90001
32209-90004
32212-90003
32414-90001
32214-90002
32215-90050
32424-90002
SUBSYSTEM MANUALS
HP GlancePlus/V User's Manual
HP Security Management Guide
APS/3000 Reference Manual
APS/3000 Quick Reference Card
APS/3000 Pocket Guide Insert
Flexible Discopy/3000
OPT/3000 Reference Manual
OPT Pocket Guide
OPT Insert for MPE Pocket Guide
50733-90002
30382-90001
32180-90001
32180-90002
32180-90003
32199-90001
32238-90001
32238-90002
32238-90003
DATA COMMUNICATIONS MANUALS
LAN Cabling and Accessories Installation Manual
LAN Link Troubleshooting Manual
LAN/3000 and OfficeShare LAN/3000 Design Guide
Making the LAN Connection: À Local Area
Network Primer
5955-7680
5955-7681
5955-7689
5957-4624
10/89
8/86
12/90
11/87
9/81
12/85
11/87
2/91
10/88
11/86
11/86
11/86
8/80
11/86
11/86
11/86
1/86
10/86
11/85
9/84
10/88
9/84
6-3
Customer Latest Current
Manual Title Order No. Edition Update
NetIPC3000/V Programmer’s Reference Manual 5958-8581 7/90
NS3000/V Migration Guide 24405-90001 10/90
NS X.25 3000/V Link Guide 24405-90002 7/90
DSN/RJE 2780/3780 Emulator Reference Manual 30000-90047 2/82 7/83
Point-To-Point Workstation I/O Reference Manual 30000-90250 12/84 4/87
ATP for Meridian SL-1 Interface Supplement to 30144-90016 4/86
the ATP Installation Manual
Workstation Configurator Reference Manual 30239-90001 10/89
LANIC Installation and Service Manual 30242-90001 2/85 5/87
(Series 39, 4X, or 6X)
LANIC Installation and Service Manual (Series 37) 30242-80100 5/85
Getting Started With SNA Node Management 30246-90002 10/88
SNA Link Services Reference Manual 30246-90003 10/88
Installing and Troubleshooting SNA IMF Node 30247-90002 1/85
Manager's Guide
MRJE User/Programmer's Reference Manual 30249-90001 4/88
IMF User/Programmer Reference Manual 30250-90001 5/87
LU 6.2 Base Node Manager's Guide 30252-90001 4/88
LU 6.2 API Node Manager's Guide 30253-90002 4/88
APPC Subsystem On MPE V Node Manager's Guide 30253-90004 8/90
Digital Multiplexed Interface (DMI) 30288-90001 6/86
Reference Manual
HP SNA Products: 30291-61005 8/90
(w/binder)
kit contents:
Manager's Guide (8/90)
ACF/NCP & ACF/VTAM Guide (8/90)
Job Entry Subsystems Guide (12/87)
IMS Guide (4/88)
CICS Guide (8/90)
DISOS Guide (8/90)
SNA NRJE Node Manager's Guide (w/binder) 30292-61000 4/90
6-4
Customer Latest Current
Manual Title Order No. Edition Update
O SNA NRJE User Programmer Reference 30292-61001 4/90
Manual (w/binder)
SNA IMF User/Programmer Reference 30293-61004 12/90
Manual (w/binder)
LU 6.2 API Application Programmer”s 30253-90001 11/89
Reference Guide
RJE User/Programmer Reference 30295-61001 8/90
Manual (w/binder)
HP X.400/HPDesk Node Administrator’s Guide 32055-90001 10/89
HP AdvanceNet Using HPDesk Manager 32055-90002 10/89
Connected to X.400
DS/3000 HP 3000 to HP 3000 User/Programmer 32185-90001 12/85 7/87
Reference Manual
DS/3000 HP 3000 to HP 1000 User/Programmer 32185-90005 12/85
Reference Manual
X.25/Link for the HP 3000 Reference Manual 32187-90001 12/85 1/89
O DSN/DS 3000 Reference Manual 32190-90001 9/82
DSN/DS 3000 To 1000 Reference Manual 32190-90005 11/82
DSN/X.25 For the HP 3000 Reference Manual 32191-90001 2/84
DSN/MRJE Multileaving Remote Job Entry 32192-90001 8/84
DSN/MTS Multipoint Terminal Software 32193-30002 8/82 2/84
Reference Manual
NS3000/V User/Programmer Reference Manual 32344-90001 7/90
NS3000/V Network Manager Reference Manual Volume 1 32344-90002 7/90
NS3000/V Error Message and Recovery Manual 32344-90005 7/90
NS3000/V Network Manager Reference Manual Volume II 32344-90012 7/90
NetDelivery Instrinsics Reference Manual 32346-90001 4/89
NetDelivery Error Message Manual 32346-90003 4/89
Getting Started with NetDelivery Intrinsics 32346-90004 4/89
NetDelivery Configuration Planning Guide 32346-90005 114/89
Customer Latest Current
Manual Title Order No. Edition Update
NetDelivery Utility Commands Reference Manual 32346-90006 4/89
NetDelivery/V Self-Paced Customer Training 32346-91001 9/87
Repeater Installation Manual 92223-90002 11/85 12/88
PROGRAMMER PRODUCTIVITY TOOLS MANUALS
TRACE Reference Manual 03000-90015 6/76
HP SRC User's Guide 30234-60002 11/88
(w/binder)
binder contents:
HP SRC User's Guide (11/88)
HP SRC Implementation Guide (11/88)
HP SRC Quick Reference Card (11/88)
Getting Started with HP SRC (11/88)
HP Software Revision Controller/V Product 30234-90006 9/89
Information Update
HP EDIT Binder Kit 30316-90001 12/90
Learning HP EDIT 30316-90002 12/90
HP EDIT Quick Reference Guide 30316-90005 12/90
Virtuoso Code Generator Reference Manual (w/binder) 30422-60001 10/89
Virtuoso COBOL Sample Library Reference 30426-60001 5/88
Manual (w/binder)
Database Utilities Reference Manual 32244-90012 12/85
REPORT/V User's Guide 32245-90001 2/85
INFORM/V User's Guide 32246-90001 3/88
Getting Started with TRANSACT (w/binder) 32247-60002 5/85 9/88
TRANSACT/V Reference Manual 32247-90001 11/87 10/89
HP TOOLSET Reference Manual 32350-90001 1/84
Using Information Access PC B1716-90014 2/90
Information Access PC Connections and Batch Files B1716-90015 2/90
6-6
Manual Title
Customer
Order No.
Latest Current
Edition Update
Learning Information Access PC
Information Access PC Installation Card
Information Access Server: System Management
Information Access Server: Error Messages
Information Access Server: Database Administration
Information Access Server: Master Index
Information Access Server: Learning the
Administrator Utility
Information Access Server: Planning and
Configuring
B1716-90016
B1716-90017
B1716-90018
B1716-90019
B1716-90020
B1716-90022
B1716-90023
B1716-90024
2/90
2/90
2/90
2/90
2/90
2/90
2/90
2/90
INFORMATION MANAGEMENT SERIES MANUALS
Dictionary/3000 Reference Manual (w/binder)
HP System Dictionary/V SDMAIN Reference Manual
HP System Dictionary Intrinsics Reference Manual
HP System Dictionary Utilities Reference Manual
HP System Dictionary General Reference Manual
Volume 1
HP System Dictionary General Reference Manual
Volume 2
HP System Dictionary COBOL Definition Extractor
Reference Manual
VISOR Tutorial Kit
Kit contents:
Introduction to VISOR
Using EZAccess
Using SQLAccess
Reporting with EZReport
Advanced VISOR Functions
VISOR Reference Information
TURBOIMAGE DBchange/V User's Guide
32244-61000
32254-90001
32254-90002
32254-90003
32254-90004
32254-90005
32255-90001
32425-60001
36020-30001
12/87
12/86
12/86
12/86
12/86
12/86
12/86
10/88
(10/88)
(10/88)
(10/88)
(10/88)
(10/88)
(10/88)
1/87
8/87
8/87
11/87
8/87
11/87
11/87
6-7
Manual Title
Customer
Order No.
Latest Current
Edition Update
HPSQL/V SQL Reference Manual
HPSQL/V ISQL Reference Manual
HPSQL/V Database Administration Guide
HPSQL/V COBOL Application Programming Guide
HPSQL/V Message Manual
HPSQL/V Quick Reference Guide
HPSQL/V Pascal Application Programming Guide
TurboIMAGE Profiler User Guide
36215-90001
36215-90002
36215-90003
36215-90004
36215-90005
36215-90006
36215-90007
36914-91001
LANGUAGE MANUALS
BASIC for Beginners
FORTRAN 77 Reference
FORTRAN 77 Programmer’s
FORTRAN 77 Quick Reference Guide
FORTRAN/3000 to HP FORTRAN/77 Conversion Guide
Cooperative Services: Using Basic Serial
Connection Reference Manual
SPL Reference Manual
SPL Language Textbook
BASIC Interpreter Manual
Scientific Library Reference Manual
FORTRAN Programmer's Guide
HP FORTRAN 77/V Reference Manual Supplement
HP FORTRAN 77/V Programmer's Guide Supplement
SPL Pocket Guide
6-8
03000-90025
5957-4685
5957-4686
5957-4687
5957-4690
5957-9336
30000-90024
30000-90025
30000-90026
30000-90027
30000-90040
30000-90294
31501-90005
32100-90001
9/87
9/87
9/87
9/87
9/87
9/87
9/87
12/85
11/72
5/88
3/87
1/88
6/87
1/89
2/84
6/76
6/76
6/76
6/87
5/88
3/87
11/76
11/87
9/87
9/77
11/86
9/77
6/87
Manual Title
Customer
Order No.
Latest Current
Edition Update
FORTRAN Pocket Guide
BASIC Compiler Reference Manual
RPG/V Reference Manual
RPG Listing Analyzer
RPG Utilities Reference Manual
Pascal Reference Manual
Pascal Pocket Guide
HP Business BASIC Reference Manual
HP Business BASIC Quick Reference Guide
HP Business BASIC Programmer's Guide
BASIC/V to HP Business BASIC Conversion Guide
BASIC/260 to HP Business BASIC Conversion Guide
Using COBOL: A Guide for the COBOL Programmer
COBOLII/3000 Reference Manual
COBOL/3000 to COBOLII/3000 Conversion Guide
Cooperative Services: Pascal Reference Manual
Cooperative Services: Developer's Guide
Cooperative Services: “C” Language
Reference Manual
Cooperative Services: COBOL Reference Manual
32102-90002
32103-90001
32104-90001
32104-90003
32104-90006
32106-90001
32106-90002
32115-90001
32115-90002
32115-90003
32115-90004
32115-90005
32213-90003
32223-90001
32233-90005
32570-90032
32570-90033
32570-90034
32570-90035
5/79
11/74
12/88
2/84
12/88
10/83
10/83
8/86
7/85
8/86
8/86
8/86
3/78
5/89
12/79
1/89
1/89
1/89
1/89
9/77
9/89
9/87
8/87
7/87
9/87
7/87
Manual Title
Customer
Order No.
Latest Current
Edition Update
ADDITIONAL SOFTWARE PRODUCTS MANUALS
HPCopycat/3000 Reference Manual
Administrator's Guide to HPConvert/WPS
HPConvert/DCA Document Conversion Guide
Administrator's Guide to HPOffice Connect to
DISOSS
Using HP DeskManager Connect to DISOSS
Using DISOSS Connected to HP DeskManager
Using HP DeskManager Connected to the IBM
Professional Office System
Using the IBM Professional Office System Connected
to HP DeskManager
HP DeskManager: Intrinsics
HPDRAW Reference Manual
HPEASYCHART Reference Manual
HPMenu Reference Manual
HPMenu Administrator’s Manual
HPMenu Quick Reference Guide
HPMap/3000
Mapping Applications Casebook
Programmatic Access to HPWORD Documents
Getting Started With HPWORD
HPWORD Quick Reference Guide
Using HPWORD
HPWORD Administration
19550-90901
27500-90001
27509-90001
27515-90001
27515-90004
27515-90006
27521-90004
27521-90005
27562-90002
32108-90001
32109-90001
32112-90000
32112-90001
32112-90002
32113-90001
32113-90002
32119-90001
32120-90032
32120-90033
32120-90035
32120-90061
10/88
1/85
12/85
10/86
10/86
10/86
1/86
1/86
1/90
12/83
1/84
1/83
6/83
6/83
7/85
7/85
9/86
4/85
4/85
4/85
9/86
8/88
8/88
Latest Current
Edition Update
Customer
Manual Title Order No.
Printing With HPWORD 32120-90065 8/88
HPListKeeper User's Guide/Reference Manual 32132-90020 9/86
VisiCalc Quick Reference Guide 32133-90001 12/84
VisiCalc Reference Manual 32133-90002 3/84
Deluxe VisiCalc Quick Reference Manual 32133-90010 12/84
Deluxe VisiCalc Reference Manual 32133-90011 12/84
DSG/3000 Reference Manual 32250-90001 12/83
DSG/3000 Quick Reference Guide 32250-90002 2/84
Print Spooler Utility 32345-90001 8/86 12/86
HP Tapemaker/V User's Guide 32434-90004 4/88
PRINT CENTRAL: PC User 32593-90002 12/86
Resource Sharing for MPE V 32597-90079 23/91
PC Backup PC User 32597-90080 4/90
PC Backup System Manager 32597-90081 4/90
HPTREND User's Guide 35136-90001 2/87
HP Easytime Reference Manual 35303-90001 2/87
HP Business Report Writer/V Reference 36070-60002 10/87 11/88
Manual (w/binder)
HPSPELL Administration 36561-90002 11/84
HPSPELL Quick Reference Guide 36561-90003 11/84
HP DeskManager Reference Card 36570-90039 11/84
Using HP DeskManager 36570-90050 9/86 8/88
Programmatic Access to HP DeskManager 36570-90053 8/86
HP DeskManager: 1 Administration Tasks Manual 36570-90087 8/88
HP DeskManager: 2 Administration 36570-90088 8/88
Reference Manual
Using HPTELEX II 36572-90012 9/84
11
Manual Title
Customer
Order No.
Latest Current
Edition Update
Administrator's Guide to HPTELEX II
HPTELEX II Reference Card
Using HPSlate
TDP/3000 Quick Reference Guide
Getting Started With TDP/3000
TDP/3000 Reference Manual
IFS/3000 Reference Manual
IDS/FORM Reference Manual
PRINT CENTRAL: System Management
Print Configuration and Attending Guide
HP Graphics Curator
HP Graphics Curator Update
HP LaserRX/MPE User’s Manual: Analysis Software
HP LaserRX/MPE User’s Manual: Collection Software
HP LaserRX/MPE: A Journey of Discovery
TRANSFORM/3000 Reference Manual
TRANSFORM/3000 IBM S/36 OCL Translation
PROCMON/3000 Reference Manual
6-12
36572-90013
36572-90014
36576-90030
36578-90003
365 78-90005
36578-30009
36580-90001
36581-90002
36890-90003
36890-90008
36926-90001
36926-90007
50700-80022
50700-90024
20700-30026
99940-90001
39940-90002
99941-90001
9/84
9/84
11/84
11/80
8/88
8/88
1/84
2/85
12/86
3/87
2/86
11/86
1/91
1/91
1/91
11/86
11/86
11/86
5/86
9/84
READER COMMENT SHEET
HP 3000 Computer Systems
COMMUNICATOR 3000, Version G.22.00 of MPE V/E (Release 22)
Volume 3, Issue 4
32033-90248 OCTOBER 1991
We welcome your evaluation of this manual. Your comments and suggestions help us to improve our
publications. Please explain your answers under Comments, below, and use additional pages if necessary.
Is this manual technically accurate? [ ] Yes [ ] No
Are the concepts and wording easy to understand? [ ] Yes [ ] No
Is the format of this manual convenient in size, arrangement, and readability? [| Yes [| Мо
Comments:
This form requires no postage stamp if mailed in the U.S. For locations outside the U.S., your local HP
representative will ensure that your comments are forwarded.
—l— JU Ge Ms Do Na o A a A Ms E I Them SEEN EE pe ERE lll EEE EE ied FEE SES esl SEE PEN SEE SLE Ewe Ey Sl UE Moi Mo Mi mi Ms Ss Vs Mis Us o VU Mis Us A E AU Se Sree y Ms a Us Ga Ms Ss AU mel EEE Sai SE SE See SE ie
Company
— — E E Нч НИНЫ чи MU da Vs Mo a o A Cs Yl TPE all Sy We o Se ME SER pd UA Dé SL Sem mE Sk SE mal Sem Sl SE SEES Sma eg mm A See TE TE TE A, UE E CE NE Se St SE ar
Address
=— — A A —]—U— ES EE Eel —— PE El Seg EE Gen Ege EE EE SE Sn ER feel EEE SE Sem SE Боны SEE SEEN meh SE al EEE EERE Spy SEE tll SEE mee Eg el — ly re Seg o A i Te VL SEE Se A —— ——l]—U——_[———
— —= ——— el EE TE Ae Tey ENS Se EE EE TE EE wd SS Sl WE SE wens Emm Sep SE SEN Say Sm Seal EEE SEN Eat ES EEE EEN sep EE teh EE mma SS EE ew. —— EE Seg tp Gr се mar len SE wel Setup Suh SS SEE r—
Tape here PLEASE DO NOT STAPLE Tape here
....Fold Bere. ov iti itt i i ie eet eet ttt tee Fold here....
| | || NO POSTAGE |
NECESSARY
IF MAILED
IN THE
UNITED STATES
BUSINESS REPLY MAIL
FIRST CLASS MAIL PERMIT No. 256 ROSEVILLE CA
POSTAGE WILL BE PAID BY ADDRESSEE
Learning Products Manager R5YA
Hewlett-Packard Company
SWT/Software Technology Center
8010 Foothills Blvd.
Roseville, CA 95678
USA
">