The Event Handler structure must be AUTOMATIC storage and initialized with the call back values or be assigned prior to invoking PLISAXA or PLISAXB. The Event Handler structure must be populated with an appropriate callback for each element of the structure. If the assignment is done manually using assignment statements, then it can be AUTOMATIC or STATIC.
The following are considerations if migrating an existing z/OS based application:
- A call back EVENT must be provided for every member of the Event Handler structure. Change ENTRY LIMITED alias definitions for Event Handler Items to ENTRY to prevent the compiler from generating an E Level diagnostic. Also, remove all references to LINKAGE(OPTLINK) from ENTRY and Procedure declarations.
- The event
unknown_attribute_reference (E20), which is part of the PLISAXA and PLISAXB event structure (but not part of PLISAXC) is generated with the same content as IBM's SAX processor but occurs earlier in the parsing.
- The reference for the event
unknown_content_reference (E21) is expanded to be its actual value.
- The events
start_of_prefix_mapping (E22) and
end_of_prefix_mapping (E23) are currently not supported to maintain compatibility with applications written using IBM's PLISAXA and PLISAXB functionality.
- When using the SAX Parser, the
exception event (E24) is driven only one time indicating an error, as opposed to having the
exception event driven one time per character. See the topic
XML Parsing Exception Event error codes for a list of Micro Focus error codes for the
exception event (E24).
- PLISAXB accepts filenames as the third parameter in the form
file://dd:ddname under batch, where
ddname is the name of the DD statement that specifies the file. The character string specifying the input file should have no leading or trailing blanks. If this is not the format, the parameter value is assumed to be the actual filename. Only files of RECFM=F, FB, FS, FBS and LSEQ are acceptable input.
