HP 3000 Manuals HP 3000 Manuals
LISTING OF LOADED PROGRAM: THE LMAP
If you want a map of your loaded program, you can request an LMAP with
the LMAP parameter of the :RUN command. To print the LMAP on the line
printer, use a :FILE equation to define the file named LOADLIST as a line
printer device file. (LOADLIST should not be used as the actual file
designator, since it is the formal file designator.) By default, the
listing is sent to $STDLIST.
The LMAP is useful as a debugging aid when you are developing a new
program. It can also help you decide whether your segmentation is
efficient (that is, whether you have achieved good localization), since
it shows how many external references your program file makes, the
logical number of each calling segment, the type of library each call was
resolved from, and the logical segment number of the external procedure.
Note that the load map may not be displayed if you are running the
program simultaneously with another user. In this case, you are sharing
code and other system resources, and the load map is displayed for the
first user to request execution of the program.
Significant entries in the following sample listing are keyed with
numbers and explained following the listing. The information in the
first four columns of the LMAP (Figure G-2) following the external
procedure name refers to the program that called the procedure
(SCR4.MPE.SYS). The information in the last four columns refers to the
called external procedures.
PROGRAM FILE SCR4.MPE.SYS **1**
SEG40 **2** **3** 0
NAME STT CODE ENTRY SEG
LISTRL' **4** 1 0 32
**5** **6** **7**
MAKEROOMINDL 30 10 **8**
FGETINFO 31 ?
FREADADMR" 32 10
NTOA 33 10
BLANKLINE 34 10
TESTBIT 35 10
DNTOA 36 10
.
.
.
OPENRL 27 2523 2523
FOPEN 70 ?
FLOCK 71 ?
FREADMR' 72 10
SEGMENT LENGTH 3130 **9**
SEG30 1
NAME STT CODE ENTRY SEG
LISTSL' 1 0 106
FGETINFO 33 ?
CLEANUPRTBUF 2 545 545
.
.
.
SEGMENT LENGTH 2030
PRIMARY DB 3350 INITIAL STACK 1440 CAPABILITY 101
**10** **14** **17**
SECONDARY DB 1216 INITIAL DL 0 TOTAL CODE 27320
**11** **15** **18**
TOTAL DB 1566 MAXIMUM DATA 40000 TOTAL RECORDS 155
**12** **16** **19**
ELAPSED TIME 00:14:29.887 PROCESSOR TIME 00:24.156
**13** **20**
Figure G-1. The PMAP
ITEM MEANING
NO.
--------------------------------------------------------------------------------------
1 The name of the program file (filename.groupname.accountname).
2 The segment name.
3 The (logical) segment number.
4 The program unit entry point name or external procedure name.
5 The assigned entry number in the Segment Transfer Table (STT).
6 The beginning location of the procedure code in the segment.
7 The location of the entry point in this segment.
8 The (logical) segment number of the segment containing this external
procedure. If this entry is a number, then the procedure is external to the
segment but internal to the program file; if this entry contains a question
mark (?), then the procedure is external to the segment and external to the
program file.
9 The segment length (in words).
10 The primary DB area size
11 The secondary DB area size.
12 The total DB area size.
13 The time elapsed during the preparation process.
14 The initial stack size.
15 The initial DL size.
16 The maximum area available for data (maximum Z-DL size).
17 Capability of program file.
18 Total code in file.
19 Total records in file.
20 Total central processor time used during preparation process.
--------------------------------------------------------------------------------------
Figure G-1. The PMAP (Continued)
PROGRAM FILE SCR4.MPE.SYS **1**
**3** **5** **7** **9**
TERMINATE' **2** PROG 0 50 11 SSL 0 2 37
**4** **6** **8** **10**
SENDMAIL PROG 0 46 11 SSL 0 2 40
DEBUG PROG 0 44 11 PSL 0 1 52
RECEIVEMAIL PROG 0 6 10 GSL 0 5 40
AWAKE PROG 0 5 11 SSL 0 4 45
WHO PROG 0 45 10 GSL 0 3 33
SETSYSDB PROG 0 33 4 SSL 0 1 33
25 2
GETUSERMODE PROG 0 10 11 SSL 0 5 44
35 4
27 2
55 1
.
.
.
301 302 303 304 305 306 307 310 311 312 **11**
Figure G-2. The LMAP
ITEM MEANING
NO.
--------------------------------------------------------------------------------------
1 The name of the program file (filename.groupname.accountname).
2 The name of the external procedure.
3
The type of the segment referencing the external procedure, where:
PROG = program segment.
GSL = group segmented library segment.
PSL = public segmented library segment.
4 External parameter checking level.
5 External segment transfer table number (STT).
6 External (logical) segment number of calling segment.
7 Entry point segment type, where:
GSL = group segmented library segment.
PSL = public segmented library segment.
SSL = system segmented library segment.
8 Entry point parameter checking level.
9 Entry point segment transfer table (STT) number.
10 Entry point (logical) segment number.
11 A list of the code segment table (CST) numbers to which the program file
segments were assigned. The list is ordered by logical segment number.
--------------------------------------------------------------------------------------
Figure G-2. The LMAP (Continued)