A map is a dummy section (or DSECT) that can be used with the MAP command to format an area of virtual storage within a dump. CA SymDump System provides built‑in maps for many of the OS and CICS control blocks. After loading any dump, use the LISTMAPS command to display the names of the loaded maps. Use the LOADMAPS command to load maps from a member in a map library. Use the MAP command to format the contents of virtual storage using one of the loaded maps.
The ability to map control blocks without specifying a MAP name on the command is called Auto-Mapping and is available for all of the known OS and CICS control blocks listed in the dump tree.
Use Auto-Mapping to map any storage location to the appropriate OS or CICS control block automatically. You do not need to know in advance the name of the mapping DSECT or even the type of control block being mapped. For all known control blocks in the dump, this is handled automatically for you.
You can use Auto-Mapping from any display that supports the MAP command. Here are some typical uses:
To reformat the current storage location using the appropriate control block map, type MAP * on the command line.
To map storage at an address in the current display, first type MAP on the command line, place your cursor over the desired address in the display, and press ENTER.
If you have a PF key set for MAP, place the cursor over the address and press the PF key instead.
To map any storage location automatically, type MAP address on the command line and press ENTER.
If a control block is listed in the dump tree, place an F in the Cmd column next to that control block and press ENTER.
Note: If the storage address does not correspond to a known OS or CICS control block, it cannot be mapped automatically. Only those control blocks listed in the dump tree are known. However, you can always use the MAP command to map any storage location using a specified map name.
For more information about the commands related to mapping storage, see the appendix Dump Viewer Commands.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |