|
We got bit by this change and had to modify our code accordingly. While researching the change I ran into this APAR and if I read it correctly, specified PTF would make the 'old' code work for a period of 180 days, supposedly giving customer time to make the necessary code accommodations. http://www-912.ibm.com/n_dir/nas4apar.nsf/fd9ac656a54b8cf286256e770069b197/7 6140dcbc749ed0686256e9f003c9ad7?OpenDocument&Highlight=2,QSYGETPH Elvis -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren Sent: Monday, July 26, 2004 9:16 AM To: Midrange Mailing List Subject: The QSYGETPH API We upgraded to V5R3M0 over the weekend and are dealing with a little bit of fallout ;-) The memo to users said that the QSYGETPH API had changed, and indeed it did, the most important change was that now "Length of password and CCSID of password are required " where it was only the password before. The current API is documented as": 1 User ID Input Char(10) 2 Password Input Char(*) 3 Profile handle Output Char(12) where before it was: 1 User ID Input Char(10) 2 Password Input Char(10) 3 Profile handle Output Char(12) I don't see however any documentation on what the char(*) looks like. I need to change the CL that accesses this API to reflect the change. Where do I find out more on how to change it? Pete Helgren Value Added Software,Inc. 801.581.1154 x202
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.