Adding a CSECT to your map assembly
This example shows you how to add both a CSECT name and AMODE and RMODE statements to your map assembly.
It is possible that you might need to generate your BMS
maps with a CSECT. For example, you might need to specify AMODE and
RMODE options to ensure that your maps reside above 16 MB, or you
might need to use the DFSMS binder IDENTIFY statement for reasons
of change management. In this case, you need not only include the
appropriate CSECT at the front of your BMS macro statements, but
also
add some conditional assembler statements to ensure that the CSECT
statement is not included in the symbolic description map. The
following
example shows how you can add both a CSECT name and AMODE and RMODE
statements:
Figure 1. Adding a CSECT to the map assembly
//PREPARE JOB 'accounting
information',CLASS=A,MSGLEVEL=1
//ASSEM EXEC PROC=DFHMAPS,MAPNAME=mapsetname,RMODE=ANY|24
//SYSUT1 DD *.
AIF ('&SYSPARM' EQ 'DSECT').SKIPSD
AIF ('&SYSPARM' EQ 'ADSECT').SKIPSD
ANYNAME CSECT Binder IDENTIFY requires CSECT name
ANYNAME AMODE 31
ANYNAME RMODE ANY
.SKIPSD ANOP ,
DFH0STM DFHMSD TYPE=DSECT,MODE=INOUT,CTRL=FREEKB,LANG=COBOL, C
TIOAPFX=YES,TERM=3270-2,MAPATTS=(COLOR,HILIGHT), C
DSATTS=(COLOR,HILIGHT)
SPACE
DFH0STM DFHMDI SIZE=(24,80)...
SPACE
DFHMSD TYPE=FINAL
END.
/*
//