DSECTs

For ease of migration, mapping DSECTs used as templates should not be explicitly duplicated within source code. An example of this technique is the use of JES2 $PDDB macro.
Whenever possible, the use of locally-defined DSECTs, macros, or equated symbols should be avoided. This technique helps to avoid future migration problems.

If you leave a control section (CSECT or RSECT) to define a DSECT, to return to the control section, use the &J2SECTN and &J2SECTT; assembly variables.

&J2SECTN contains the control section name.
&J2SECTT contains the control section type, either CSECT or RSECT.

For example:

MYMOD      $MODULE ENVIRON=USER,.....
⋮
**************************************************
*                                                *
* DEFINE DATA                                    *
*                                                *
**************************************************
MYDATA     DSECT
           DCs
⋮
**************************************************
*                                                *
* RETURN TO CONTROL SECTION                      *
*                                                *
**************************************************
&J2SECTN   &J2SECTT
⋮