Calculating CSD disk space

Before you can create the CICS® system definition data set (CSD), you must calculate the amount of space you need in your CSD for definition records.

Procedure

  1. In your calculation, allow for approximately 1800 CICS-supplied resource definitions of various types, which are loaded into the CSD when you initialize the CSD with the CSD update batch utility program DFHCSDUP. You need to consider:
    1. Each resource definition (for example each program, transaction and terminal) needs one record.
      The sizes of these definition records are:
      Resource Definition record size (maximum)
      ATOMSERVICE 720 bytes
      BUNDLE 698 bytes
      CONNECTION 260 bytes
      CORBASERVER 1375 bytes
      DB2CONN 308 bytes
      DB2ENTRY 236 bytes
      DB2TRAN 198 bytes
      DJAR 445 bytes
      DOCTEMPLATE 567 bytes
      ENQMODEL 447 bytes
      FILE 369 bytes
      IPCONN 468 bytes
      JOURNALMODEL 222 bytes
      JVMSERVER 208 bytes
      LIBRARY 925 bytes
      LSRPOOL 425 bytes
      MAPSET 190 bytes
      MQCONN 240 bytes
      PARTITIONSET 190 bytes
      PARTNER 408 bytes
      PIPELINE 959 bytes
      PROCESSTYPE 206 bytes
      PROFILE 231 bytes
      PROGRAM 499 bytes
      REQUESTMODEL 1211 bytes
      SESSION 296 bytes
      TCPIPSERVICE 571 bytes
      TDQUEUE 331 bytes
      TERMINAL 327 bytes
      TRANCLASS 192 bytes
      TRANSACTION 545 bytes
      TSMODEL 308 bytes
      TYPETERM 402 bytes
      URIMAP 1443 bytes
      WEBSERVICE 708 bytes
    2. Each group requires two 122-byte records
    3. Each group list requires two 122-byte records
    4. Each group name within a list requires one 68-byte record
  2. Add a suitable contingency (approximately 25%) to the size that you have calculated so far.

What to do next

Use your final figure when you define the VSAM cluster for the CSD. (See the sample job in Initializing the CSD.)