Defining DFHBRNSF
For VSAM files and data tables, you need to use IDCAMS to create file DFHBRNSF.
Figure 1 shows a some sample IDCAMS statements that you can modify to create the DFHBRNSF file. Change the cluster name and volume values to comply with your own standards.
//DEFDS JOB accounting info,name,MSGCLASS=A
//TDINTRA EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
DEFINE CLUSTER(NAME(CICSTS22.CICS.DFHBRNSF)-
INDEXED-
TRK(1 1)-
RECORDSIZE(384 384)-
KEYS(13 20)-
FREESPACE(0 50)-
SHAREOPTIONS(2 3)-
LOG(NONE)-
VOLUME(DISK01)-
CISZ(512)) -
DATA (NAME(CICSTS22.CICS.DFHBRNSF.DATA)-
CISZ(512)) -
INDEX (NAME(CICSTS22.CICS.DFHBRNSF.INDEX)-
CISZ(512))
/*
//
See Coupling facility data tables for guidance on creating coupling facility data tables.
File DFHBRNSF contains two control records plus 1 record for each router region that accesses the file. The maximum number of records that can be written to DFHBRNSF is 731 (this includes the 2 control records).
You need to define file DFHBRNSF to CICS® in the Link3270 router regions. Resource definitions have been provided for all versions of the file. You should include the appropriate group in your startup grouplist, or copy chosen definitions into a group in the grouplist. You will need to edit the definitions to match your IDCAMS statements. Change the DSN field to match the cluster name used with IDCAMS to create the file, unless the CFDT version of the file is to be used. If the CFDT definition is being used, change the CFDTPOOL value to the name of the pool containing the table defined by the file definition. The table shows the groups provided that contain the DFHBRNSF definitions.
| Group | Type |
|---|---|
| DFHBRVR | VSAM RLS |
| DFHBRVSL | Local VSM, non-RLS |
| DFHBRVSR | Remote VSAM, non-RLS |
| DFHBRCF | Coupling facility data table |
| DFHBRUT | User maintained data table |
- If DFHBRNSF becomes unavailable, only Link3270 requests that do not cause an allocation or release of a bridge facility namespace range will still complete successfully.
- If DFHBRNSF file has to be redefined for any reason, all router regions that access the file should be shut down before the file is redefined, and restarted after the file has been redefined.