The database PCB statement

The database PCB statement defines the DBD of the database that the application program will access.

Database PCB statements also define types of operations (such as get, insert, and replace) that the application program can perform on segments in the database. The database can be either physical or logical. A separate database PCB statement is required for each database that the application program accesses. In each PSB generation, up to 2500 database PCBs can be defined, minus the number of alternate PCBs defined in the input deck. The other forms of statements that apply to PSBs are SENSEG, SENFLD, PSBGEN, and END.

Attention: If the PROCOPT values allow a BMP application to insert, replace, or delete segments in databases, ensure that the BMP application does not update a combined total of more than 300 databases and HALDB partitions without committing the changes.

All full-function database types, including logically related databases and secondary indexes, that have uncommitted updates count against the limit of 300. When designing HALDB databases, you should use particular caution because the number of partitions in HALDB databases is the most common reason for approaching the 300 database limit for uncommitted updates.