Full considerations
If a note cannot be created because the note pad is full, consider deleting one or more notes from the note pad to free up some note space and reissue the request. You might also consider reissuing the request, perhaps after a short delay, if you believe the dynamics of your note pad are such that notes are likely to be deleted through normal activity.
Alternatively, you might try to increase the capacity of your note pad by issuing IXCNOTE REQUEST=NOTEPAD REQTYPE=MODIFY to increase the number of notes that the note pad is allowed to hold (See Modify note pad). If dynamically increasing the note pad capacity is unsuccessful due to note pad host structure constraints (e.g., the MODIFY request fails with a reason code ixcnoteRsnNo#NotesStrResources), manual intervention might be required to resolve the constraint condition. For example, the installation might need to update the CFRM policy to change the size of the host note pad structure or use the IXLALTER service to expand the size of the structure. Although disruptive, you might choose to delete the note pad and create the note pad again with a higher note limit in order to increase the capacity of an existing note pad. XCF will attempt to locate the newly created note pad in a host structure with sufficient space to satisfy the higher note limit. Deleting the note pad could be disruptive to your application. Adding another note pad likely increases the complexity of your program. Note that there is no guarantee that a new note pad can be created successfully.