To find an AUTOMATIC variable in the dump, you should find its offset within automatic using the output from the MAP option (and if necessary the AGGREGATE option). If PLIDUMP has been invoked with the B option, the dump output will contain a hex dump of the "Dynamic save area" (or DSA) for each block. This is the automatic storage for that block.
For example, consider the following simple program:
Compiler Source
Line.File
2.0 test: proc options(main);
3.0
4.0 dcl a fixed bin(31);
5.0 dcl b fixed bin(31);
6.0
7.0 on error
8.0 begin;
9.0 call plidump('TFBC');
10.0 end;
11.0
12.0 a = 0;
13.0 b = 29;
14.0 b = 17 / a;
The result of the compiler MAP option for this program looks like this, except that there is actually one more column on the right and the columns are actually spaced much further apart:
* * * * * S T O R A G E O F F S E T L I S T I N G * * * * * IDENTIFIER DEFINITION ATTRIBUTES A 1-0:4 Class = automatic, Location = 160 : 0xA0(r13), B 1-0:5 Class = automatic, Location = 164 : 0xA4(r13),
So, A is located at hex A0 off of register 13 and B is located at hex A4 off of register 13, where register 13 points to the DSA.
Since in this program PLIDUMP is called with the B option, it will include a hexadecimal dump of automatic storage for each block in the current calling chain. This will look like (again with the right columns cutoff):
Dynamic save area (TEST): 0AD963C8
+000000 0AD963C8 10000000 0AD96188 00000000 00000000
+000020 0AD963E8 00000000 00000000 00000000 00000000
+000040 0AD96408 00000000 00000000 00000000 0AD96518
+000060 0AD96428 00000000 00000000 00000000 00000000
+000080 0AD96448 - +00009F 0AD96467 same as above
+0000A0 0AD96468 00000000 0000001D 00100000 00000000
+0000C0 0AD96488 0B300000 0A700930 0AD963C8 00000000
+0000E0 0AD964A8 00000000 00000000 00000000 00000000
+000100 0AD964C8 0AA47810 0A70E6D0 0AD96540 0AD960F0
+000120 0AD964E8 00000001 0A70F4F8 0AD96318 00000000
+000140 0AD96508 00000000 00000000 00000000 00000000
Since A is at hex offset A0 and B is at hex offset A4 in AUTOMATIC, the dump shows that A and B have the (expected) hex values of 00000000 and 0000001D respectively.
Please note that under the compiler options OPT(2) and OPT(3), some variables, particularly FIXED BIN and POINTER scalar variables, may never be allocated storage and thus could not be found in the dump output.