gtpm6m11 | Main Supervisor Reference |
TPF dumps system storage under the following conditions:
You can control the contents of your SERRC dumps by selecting which large areas or tables you want in certain dumps. There are 2 steps to this process:
The relationship of the macros and tables described in the following sections is shown in Figure 1.
Figure 1. Components of Dump Content Control
IBM ships a list of predefined keywords for large IBM storage areas in the IDATB macro. These keywords are defined using IDATG macro calls. When IDATB is assembled, these calls generate entries in the selective memory dump table (SMDT). Entries in the SMDT represent data areas that are normally excluded from dumps. All of IBM's predefined areas start with I for example, ICLH represents the CLH block management tables.
The IDATB macro contains a call to copy member UDATB, which contains user IDATG calls, for customer use. You can code your own IDATG calls to associate keywords with regions of storage that you want to include in (or exclude from) dumps using the IDATG calls in IDATB as an example. Include your IDATG calls in UDATB.
The areas defined in the SMDT will not be included in dumps unless a dump override is created for a particular system error requesting that a storage area be included. The IDOTB macro maps specific system error numbers to keywords, creating dump overrides. IBM's dump overrides are coded on IDOTB macros in segment CIDP. When CIDP is assembled, these calls generate entries in IBM's static override bitmap table (SOBT).
You can code your own dump overrides using IDOTB calls in copy member CUDP of user exit CSECT CCUEXT using IBM's IDOTB calls in CIDP as an example. Your IDOTB calls will generate entries in the user SOBT.
Once the system is up and running, you can use the ZIDOT command to associate system error numbers with keywords or to override what's coded on IDOTB calls.