Before you can create the CSD, you must calculate the amount of space you need in your CSD for definition records. Use the following information:
Resource | Definition record size (maximum) |
---|---|
Connection | 192 bytes |
Corbaserver | 1187 bytes |
DB2CONN | 213 bytes |
DB2ENTRY | 136 bytes |
DB2TRAN | 90 bytes |
DJAR | 337 bytes |
Doctemplate | 195 bytes |
Enqmodel | 345 bytes |
File | 322 bytes |
Journalmodel | 115 bytes |
LSR pool | 326 bytes |
Map set | 101 bytes |
Partition set | 101 bytes |
Partner | 294 bytes |
Processtype | 110 bytes |
Profile | 146 bytes |
Program | 432 bytes |
Requestmodel | 1104 bytes |
Session | 184 bytes |
TCPIPSERVICE | 242 bytes |
Terminal | 211 bytes |
Tranclass | 88 bytes |
Transaction | 453 bytes |
Transient data queue | 262 bytes |
Tsmodel | 201 bytes |
Typeterm | 368 bytes |
In your calculation, allow for approximately 1200 CICS-supplied resource definitions of various types, which are loaded into the CSD when you initialize the CSD with the utility program, DFHCSDUP. Finally, add a suitable contingency (approximately 25%), and use your calculated figure when you define the VSAM cluster for the CSD. (See the sample job in Figure 11.)
[[ Contents Previous Page | Next Page Index ]]