In this example, IDENTIFY statements are used to identify the source level of a control section, a PTF application to a control section, and the functions of several control sections.

//LKED       EXEC   PGM=IEWBLINK
//SYSPRINT   DD     SYSOUT=*
//SYSLMOD    DD     DSNAME=PROJECT.LOADLIB,DISP=OLD
//OLDMOD     DD     DSNAME=PROJECT.OLD.LOADLIB,DISP=OLD
//PTFMOD     DD     DSNAME=PROJECT.PTF.OBJECT,DISP=OLD
//SYSLIN     DD     *

(input object deck for a control section named FORT)

  IDENTIFY   FORT('LEVEL 03')
  INCLUDE    PTFMOD(CSECT4)
  IDENTIFY   CSECT4('PTF99999')
  INCLUDE    OLDMOD(PROG1)
  IDENTIFY   CSECT1('I/O ROUTINE'),
             CSECT2('SORT ROUTINE'),
             CSECT3('SCAN ROUTINE')
/*

Execution of this example produces IDR records containing the following identification data:

• The component ID of the binder that produced the program object or load module, the binder version and modification level, and the date of the current binder processing of the module. This information is provided automatically irrespective of whether you specify an IDENTIFY statement.
• User-supplied data describing the functions of several control sections in the module, as indicated on the IDENTIFY statements.
• If the language translator used supports IDR, the identification records produced by the binder also contain the name of the translator that produced the object module, its version and modification level, and the date of compilation.