|
James H H Lampert wrote: > What in the <censored> was IBM thinking when they broke the <blasphemy> > <obscenity> <vulgarity> QSYGETPH API in V5R3, such that it now requires > <censored> parameters that didn't even <censored> exist when the API was > first defined? Can you be a bit more specific? We use the QSYSGETPH api all the time on V4R5 through V5R3 without problems. david p.s. and wash your keyboard out with a soap request ... what would your mother say if she saw you swear with not well-formed xml? You should be using '<vulgarity/>'!
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.