HP Deskjet 3000 User manual

HP RPG/XL Utilities
HP 3000 MPE/iX Computer Systems
Edition 1
Manufacturing Part Number: 30318-90006
E1089
U.S.A. October 1989

2
Notice
The information contained in this document is 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 or fitness for a particular purpose. Hewlett-Packard
shall not be liable for errors contained herein or for direct, indirect,
special, incidental or consequential damages in connection with the
furnishing 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 is protected by
copyright. All rights reserved. Reproduction, adaptation, or translation
without prior written permission is prohibited, except as allowed under
the copyright laws.
Restricted Rights Legend
Use, duplication, or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013.
Rights for non-DOD U.S. Government Departments and Agencies are
as set forth in FAR 52.227-19 (c) (1,2).
Acknowledgments
UNIX is a registered trademark of The Open Group.
Hewlett-Packard Company
3000 Hanover Street
Palo Alto, CA 94304 U.S.A.
© Copyright 1989 by Hewlett-Packard Company

5
HP RPG/XL Utilities-Part 1 XSORT
1 PREFACE
EXTRA FUNCTION SORT FOR RPG (XSORT)
This manual is intended for the use of inexperienced as well as seasoned programmers. To answer the
needs of programmers with varied backgrounds, the manual presents information of varying complexity,
especially in explaining the XSORT specifications. Most of this manual will be devoted to the five-part
specifications. The information will be presented under the following headings:
Overview of XSORT Specifications
shows you which columns of the specifications you must consider when you are preparing a sort.
Overviews serve as a quick reminder to those who are familiar with the program
Overview of Column Entries
lists all possible entries for each column in the specifications. These are brief descriptions and
explanations of the entries and their purposes. Column Entries
provide detailed discussions of the meanings of all possible entries, their relationships to other entries
within the specifications type and other entries in other specification types. They are intended for new
users of XSORT.
Using XSORT Commands
gives you the various MPE commands necessary to use XSORT in job stream and interactive session, with
different arrangements of input and output files.
XSORT Applications
demonstrate how specifications are adapted to the requirements of particular jobs.
The more extensive the user's experience, the more readily will XSORT's versatility and efficiency become
apparent. The manual takes into consideration that some users will be employing the program for the first
time. Information and instruction are provided for several levels of experience so that the new user should
be able to put XSORT to work after reading the manual.
In using XSORT, you may have programs and systems that interface with the Keyed Sequential Access
Method (KSAM/3000), the IMAGE Data Base Management System (IMAGE/3000), and the Data Entry
and Forms Management System (V/3000). For information about these systems, please read:
Manual Title
IMAGE/3000 Data Base Management Reference System
KSAM/3000 Reference Manual
VPLUS/3000 Reference Manual

6
Conventions
NOTATION DESCRIPTION
UPPERCASE Within syntax statements, characters in
uppercase must be entered in exactly the
order shown, though you can enter them in
either uppercase or lowercase. For
example:
SHOWJOB
Valid entries: showjob ShowJob
SHOWJOB
Invalid entries: shojwob ShoJob
SHOW_JOB
italics Within syntax statements, a word in
italics represents a formal parameter or
argument that you must replace with an
actual value. In the following example,
you must replace
filename with the
name
of the file you want to release:
RELEASE
filename
punctuation Within syntax statements, punctuation
characters (other than brackets, braces,
vertical parallel lines, and ellipses)
must be entered exactly as shown.
{ } Within syntax statements, braces enclose
required elements. When several elements
within braces are stacked, you must
select one. In the following example,
you must select ON or OFF:
{ON }
SETMSG {OFF}
[ ] Within syntax statements, brackets
enclose optional elements. In the
following example, brackets around ,TEMP
indicate that the parameter and its
delimiter are optional:
PURGE {
filename } [,TEMP]
When several elements with brackets are

7
stacked, you can select any one of the
elements or none. In the following
example, you can select
devicename or
deviceclass or neither:
SHOWDEV [
devicename ]
[
deviceclass ]
[...] Within syntax statements, a horizontal
ellipsis enclosed in brackets indicates
that you can repeatedly select elements
that appear within the immediately
preceding pair of brackets or braces. In
the following example, you can select
itemname and its delimiter zero or
more
times. Each instance of
itemname must
be
preceded by a comma:
[
,itemname ][...]
If a punctuation character precedes the
ellipsis, you must use that character as
a delimiter to separate repeated
elements. However, if you select only
one element, the delimiter is not
required. In the following example, the
comma cannot precede the first instance
of
itemname :
[
itemname ][,...]
|...| Within syntax statements, a horizontal
ellipsis enclosed in parallel vertical
lines indicates that you can select more
than one element that appears within the
immediately preceding pair of brackets or
braces. However, each element can be
selected only one time. In the following
example, you must select ,A or ,B or ,A,B
or ,B,A :
{,A}
{,B}|...|
If a punctuation character precedes the
ellipsis, you must use that character as
a delimiter to separate repeated
elements. However, if you select only
one element, the delimiter is not
required. In the following example, you

8
must select A or B or AB or BA. The first
element cannot be preceded by a comma:
{A}
{B}|,...|
... Within examples, horizontal or vertical
ellipses indicate where portions of the
example are omitted.
Å Within syntax statements, the space
symbol Å shows a required blank. In the
following example, you must separate
modifier and variable with a
blank:
SET[(
modifier )]Å( variable );
underlining User input is underlined. For
example:
PROMPT?response
In a syntax statement, brackets, braces
or ellipses are underlined if you must
enter them. For example:
COMMAND
[[
ParameterA ] ] = ParameterB
Conventions (continued)
NOTATION DESCRIPTION
shading Within an example of interactive dialog,
shaded characters indicate user input or
responses to prompts. In the following
example, OMEGA is the user's response to
the NEW NAME prompt:
NEW NAME? OMEGA
The symbol indicates a key on the
terminal's keyboard. For example, CTRL
indicates the Control key.
CTRL
char CTRL char indicates a control
character.
For example, CTRLY means you have to
simultaneously press the Control key and

9
the Y key on the keyboard.
base prefixes The prefixes %,#, and $ specify the
numerical base of the value that follows:
%
num specifies an octal number.
#
num specifies a decimal number.
$
num specifies a hexadecimal
number.
When no base is specified, decimal is
assumed.

10

1- 11
2 Introduction
Hewlett-Packard's Extra Function Sort for RPG/XL, hereaft er referred to as XSORT, enables users to
rearrange data in their files, drop records from their files, and reformat records, as shown in figure 1-1.
XSORT runs on the MPE XL computer system and is primarily used in conjunction with the RPG
programming language. Its origin was the unsupported utility SORT3 which was designed to perform
most of the functions of IBM's System/3 $DSORT and System/34 #GSORT. Similarities and differences are
covered in appendix A.
Figure 1-1. Uses of XSORT

1- 12
Characteristics of XSORT:
In extending and enhancing your sort capabilities, XSORT:
• Uses from one to nine input files.
• Employs multiple logical criteria to select records from MPE (disk and non-disk) and KSAM files, so you
can process a subset of your input records.
• Builds a different sort key for each type of record using input record fields and forced control fields. This
facilitates the input of files with different data structures.
• Reformats each type of record upon output to give you a choice of record layouts.
• Can perform a count-only pass on the input files. This permits you to conduct a preliminary search of
your records or provide statistics on selected subsets of records.
How XSORT Works
XSORT follows a logical sequence in performing a sort. This sequence is described below:
1 XSORT reads a record from the input file.
2 XSORT checks your specifications to make sure the record is one you want to sort. You may not
wish to sort all the records in the file you have specified.
3 XSORT builds a work record containing sort control fields and data fields. It also formats the data
portion according to your specifications. Work record formatting is important because it controls
the format of your output.
4 XSORT submits the work records to the SORT subsystem for sorting.
5 XSORT retrieves records from SORT after sorting is complete.
6 XSORT writes records into the output file, retaining or dropping control fields, according to your
specifications
NOTE Control fields are input fields whose characteristics are used as a basis for the com-
parisons required by the sort. Control fields are discussed in detail in the section on
Field Descriptions. (See chapter 6.)
-------------------------------------------------------
| | | |
| Control field | Data | Control field |
| A | | B |
| | | |
-------------------------------------------------------
1 10 11 29 30 36
Suppose that you wanted to rearrange the input file above because a proposed sort job requires the
following changes:
1 Change the contents of positions 30 through 36 placed in positions 1 through 7 of the work record.
2 Change the contents of positions 1 through 10 of the input file placed in positions 8 through 17 of
the work file.
3 Change the contents of positions 11 through 29 of the input record placed in positions 18 through