HP 3000 Manuals HP 3000 Manuals
Enhancement to SEGMENTER
by Craig Hada--Commerical Systems Division
SEGMENTER, version A.03.X4, on MPE XL has been enhanced to create program
and segmented library (SL) files which are compatible with those created
on MPE V/E based systems. This enhancement will allow MPE V/E compatible
source files to be compiled on MPE XL based systems. SEGMENTER can then
use the USL files produced by the compilers to create program files using
the :PREP command or to add/delete segments to an SL using the
ADDSL/PURGESL commands. These files can be transported to MPE V/E based
systems where the program files and library routines within the SL can be
executed.
IDENTIFYING TRANSPORTABLE PROGRAM FILES
The :LISTF command can be used to identify programs that can be
transported to MPE V/E based systems and executed. The following example
illustrates how compatibility mode program files, that are transportable
to MPE V/E based systems, can be identified.
:LISTF @prog,2
ACCOUNT= MPEV GROUP= HADA
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
NEWPROG PROG 128W FB 206 206 1 208 1 1
OLDPROG PROG 128W FB 206 206 1 208 1 *
This example uses the :LISTF,2 command to identify all file names in the
currently logged group and account that end in "PROG" . The two files
names that were qualified by the :LISTF command are both compatibility
mode programs, which are distinguished by the file code of PROG. File
codes are displayed below the heading of CODE for the :LISTF,2 command.
Program files which have been created by SEGMENTER, version A.03.X4, can
be identified by looking under the MX heading (maximum number of extents)
of the :LISTF,2 display. MPE V/E compatible program files will have a
numeric value in the MX column, while those created with SEGMENTER,
version A.03.X3 or earlier, will show an asterisk in this column.
Those program files which are displayed with an asterisk in the MX column
must be recompiled and :PREPed with version A.03.X4 of SEGMENTER before
they can be transported to an MPE V/E based system.
IDENTIFYING TRANSPORTABLE SL FILES
The :LISTF command can be used to identify SLs that can be transported to
MPE V/E based systems and executed. The following examples illustrate
how SL files, that are transportable to MPE V/E based systems, can be
identified.
:LISTF sl,2
ACCOUNT= MPEV GROUP= HADA
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
SL SL 128W FB 25495 25497 1 25498 1 *
:LISTF sl,2
ACCOUNT= MPEV GROUP= HADA
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
SL SL 128W FB 25495 25497 1 25498 10 10
The first example shows an SL that was created with SEGMENTER, version
A.03.X3 or earlier. The second SL was created with version A.03.X4 of
SEGMENTER. SL files which have been created by SEGMENTER, version
A.03.X4, can be identified by looking under the MX heading of the
:LISTF,2 display. MPE V/E compatible SL files will have a numeric value
in the MX column, while those created with SEGMENTER, version A.03.X3 or
earlier, will show an asterisk in this column.
Those SL files which have been transported from an MPE V/E system to an
MPE XL system and modified will show a numeric value for the maximum
number of extents. These SLs can not be transported back to an MPE V/E
system due to extent misalignment. These SLs along with those showing an
asterisk for the maximum number of extents should be rebuilt from
existing USL (user subprogram library) files.
NOTE Purge all SL files to make sure that none of them have been
transported from an MPE V/E system and modified with version
A.03.X3 or earlier of SEGMENTER.
ENHANCED BUILDSL COMMAND
The BUILDSL command of SEGMENTER has been enhanced to create MPE V/E
compatible SL files. The syntax and parameters for this command are as
follows:
Syntax
-BUILDSL filereference,records,extents
Parameters
filereference Any file whose local name is SL. You can create an SL
file with a local name other than SL, but such a file
cannot be searched by the MPE :RUN command or the CREATE
or LOADPROC intrinsics unless it is renamed SL.
records The total maximum file capacity, specified in terms of
128-word binary logical records.
extents The total number of disc extents that can be dynamically
allocated to the file as logical records are written to
it. The size of each extent is determined by the
records parameter value divided by the extents parameter
value. The extents value must be an integer from 1 to
32.