Re: QSYGETPH change in V5R3M0

[rob@xxxxxxxxx]

The exact reason it is working is because you are using the special value
*NOPWD.  And the documentation says that if you are using a special value
then the length and the CCSID are not required.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


|-----------------------------+-------------------------------------------|
|   Dave Schnee               |                                           |
|   <DSchnee@xxxxxxxxxxxxxxxxx|                                           |
|   om>                       |                                         To|
|   Sent by:                  |                                      midra|
|   midrange-l-bounces@midrang|                                      nge-l|
|   e.com                     |                                      @midr|
|                             |                                      ange.|
|   07/26/2004 09:37 AM       |                                      com  |
|                             |                                         cc|
|         Please respond to   |                                           |
|         Midrange Systems    |                                    Subject|
|       Technical Discussion  |                                      Re:  |
|      <midrange-l@xxxxxxxxxxx|                                      QSYGE|
|                m>           |                                      TPH  |
|                             |                                      chang|
|                             |                                      e in |
|                             |                                      V5R3M|
|                             |                                      0    |
|                             |                                           |
|                             |                                           |
|                             |                                           |
|                             |                                           |
|                             |                                           |
|                             |                                           |
|-----------------------------+-------------------------------------------|






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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.