Which would be of little help to my co-worker at the moment, as we are on V1.12 and thus cannot run COBOL 5.1. When we will be upgrading (and to which version) is not published yet, so I can't tell when we will get there, or where "there" is.
The enhancements you listed (except the last one) are all at the language level. Our issue at the moment is performance, and yes we do have at least one specialty engine on each of our CEC's, but I don't know what the usage level is yet. I'll have to talk to our system capacity and performance team to find that out. The fact that 5.1 will ONLY use the equivalent of XMLPARSE(XMLSS) is something I missed however, so thank you for that nugget. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Greg Shirey Sent: Wednesday, March 19, 2014 9:49 AM To: [email protected] Subject: Re: XMLSS performance vs COBOL 4.1 runtime XML He might also suggest migrating to COBOL 5.1. From the migration guide: The XML function supported by IBM® Enterprise COBOL for z/OS® has been enhanced: •The XML GENERATE statement has been extended with new syntax that gives the programmer more flexibility and control over the form of the XML document that is generated: ◦The NAME phrase has been added to allow user-supplied element and attribute names. ◦The TYPE phrase has been added to give the user control of attribute and element generation. ◦The SUPPRESS phrase has been added to allow suppression of empty attributes and elements. •XML parsing support has been enhanced with a special register, XML-INFORMATION, to easily determine whether the XML content delivered for an XML event is complete or will be continued on the next event. •The compatibility-mode COBOL XML parser from the COBOL library is no longer supported for use by Enterprise COBOL V5 programs. XML PARSE statements in V5 programs always use the XML parser in z/OS XML System Services. Regards, Greg Shirey Ben E. Keith Company -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Frank Swarbrick Sent: Tuesday, March 18, 2014 7:14 PM To: [email protected] Subject: Re: XMLSS performance vs COBOL 4.1 runtime XML I seem to recall Tom Ross saying that XMLSS is, in fact, generally slower than COMPAT. I believe the only advantage to XMLSS is that it can be offloaded to a specialty engine. So it will be slower but cost less (??). Or slower and cost more if you don't have a specialty engine! Crazy, no? I'm sure Tom will correct me if I have misstated! >________________________________ > From: "Farley, Peter x23353" <[email protected]> >To: [email protected] >Sent: Tuesday, March 18, 2014 3:40 PM >Subject: XMLSS performance vs COBOL 4.1 runtime XML > >One of my co-workers is trying to improve the performance of an Enterprise 4.1 >program that decomposes an input XML file into record fields for processing by >later programs. The volume of the XML input has increased quite a bit and the >performance may soon impact SLA's. > >This program is currently compiled with XMLPARSE(COMPAT), so I advised him to >try compiling a test version with XMLPARSE(XMLSS) and run some production data >through both versions a few times to get some average performance numbers. > >The XMLSS version seems to be running about 10% more CPU utilization and >elapsed time than the production version, on average. > >Are there any tweaks or adjustments that can or should be made to the XMLSS >subsystem to improve performance? Our environment is z/OS V1 R12, z196 >hardware. > >Any RTFM would be most appreciated, since I can't make any such changes myself >but have to refer them to my systems programming group for consideration. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
