× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Pete:

I have an application that uses QSYGETPH in a CLP.  It continues to work 
at V5R3M0, but there are 2 things I have done:

1)      I am using it with *NOPWD as the second parm
2)      I have compiled this program to a prior release, e.g., 
TGTRLS(V5R1M0)

This may provide an interim plan until you get the answer you seek.

Dave

Pete Helgren wrote - - - - -

message: 10
date: Mon, 26 Jul 2004 08:15:48 -0600
from: "Pete Helgren" <pete@xxxxxxxxxx>
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 thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.