I am having two issues using the Parse XML command.
The command is just “PARSE” on the mainframe (4.3), but is “PARSE XML” using Natural Studio (6.3). This causes an issue when attempting to catalog a program that uses the Parse XML command on either the mainframe or in Studio (depending on which syntax the program is using). Is there fix for this issue?
The mainframe version of the Parse XML command is not properly handling output escaping. I tested by creating a PDA and it’s parse and serialize modules - then executed a program that loads data into the PDA, serializes the data to an XML string, resets the PDA, and then parses the XML string to the PDA. I did verify that the serialize is properly writing out the data. Here are results of parsing tests using the mainframe (4.3) and Studio (6.3):
PDA field loaded with: 1234567890
Mainframe after parse: 1234567890
Studio after parse: 1234567890
PDA field loaded with: 1234<56>7890
Mainframe after parse: 7890
Studio after parse: 1234<56>7890
PDA field loaded with: 12345&67890
Mainframe after parse: 67890
Studio after parse: 12345&67890
Any ideas on what the fix for this might be? I was thinking that it could be a code page issue, but it would seem odd that the default code page on the mainframe wouldn’t be able to handle the translation since I’m using IBM037 encoding (EBCDIC) and data that is generated and processed on the mainframe.
Any help or information about these two issues would be greatly appreciated and I thank, in advance, anyone who takes time to respond!
California State Teachers’ Retirement System