The SENSEG statement

The SENSEG statement defines a segment type in the database to which the application program is sensitive.

A separate SENSEG statement must exist for each segment type. The segments can physically exist in one database or be derived from several physical databases. If an application program is sensitive to a segment beneath the root segment, it must also be sensitive to all segments in the path from the root segment to the sensitive segment. For example, in the following figure if D is defined as a sensitive segment for an application program, B and A must also be defined as sensitive segments.

Figure 1. Example of a SENSEG relationship
Hierarchical structure. Root is segment A. Below A are B and E. Below B are C and D. Path to D is A and B. Segment A: SENSEG PROCOPT=K. Segment B: SENSEG PROCOPT=K. Segment D: SENSEG.

An application program must be sensitive to all segments in the path to the segment that you actually want to be sensitive. However, you can make the application program sensitive to only the segment key in these other segments. With this option, the application program does not have any access to the segments other than the keys it needs to get to the sensitive segment. To make an application sensitive to only the segment key of a segment, code PROCOPT=K in the SENSEG statement. The application program will not be able to access any other field in the segment other than the segment key. In the previous example, the application program would be sensitive to the key of segment A and B but not sensitive to A and B's data.

SENSEG statements must immediately follow the PCB statement to which they are related. Up to 30000 SENSEG statements can be defined for each PSB generation.