This trap is sent whenever the state of one of the documents in a job changes. The state of a single document is represented in the xcmDocGenBasicTable column: xcmDocState. The job's xcmJobIdentifierOnSystem and the document's xcmDocSequenceNumber are included in the trap's variable bindings; these can be used to reference the document's xcmDocGenBasicTable entry. NOTE - the addition of an entire row to the document tables corresponds to the acceptance of another document (in a job) by the server. The state of the document changes from unknown to a specific value (usually transfer pending). Therefore, the agent generates a trap when a document (within a job) is accepted (so that the management station can display the newly arrived document in a timely fashion). This notification has the following special semantics: 1 The agent shall append the document's job's xcmJobClientId to the trap object ID, if the document's job's xcmJobClientId field is not empty. NOTE: If the format of the xcmJobClientId is dotted decimal representation, then it will be encoded as a BER binary OID appended to the trap object ID. NOTE: The BER binary OID shall not include the ASN.1/BER tag of 6 indicating an OID and shall not include the ASN.1/BER length field in octets of the OID. 2 The agent shall append the value of the document's xcmDocSequenceNumber field to the trap object ID. These trap OID qualifiers allow job-submission and monitoring applications to specify exactly which alerts they are interested in and to limit the alerts they receive to ones generated by jobs or jobs and documents that they have submitted. NOTE: The sum of the trap var bind values must be less than can fit into a PDU on any transport, roughly 540 octets on some transports. Thus implementers are warned to minimize the length of the xcmJobClientId and xcmJobIdentifierOnSystem objects.