Re: WHAT was IBM THINKING?!?!?, Re: QSYGETPH API

I did not notice that the length of the passWord is also required now. That 
sucks.  does that mean that all the pgms I wrote for v5r1 and v5r2 that use 
qsygetph wil now fail?


-----Original Message-----
    From: "James H H Lampert"<jamesl@xxxxxxxxxxx>
    Sent: 9/14/05 3:30:28 PM
    To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
    Subject: Re: WHAT was IBM THINKING?!?!?, Re: QSYGETPH API
    
    "Shannon O'Donnell" <sodonnell@xxxxxxxxxxxxxxxxx> wrote:
    > I don't understand your comments. I just now looked in 
    >the info center ar both vr5r3 and v5r2 for qsysgetph and 
    >the parameters are exactly the same.  
    
    Not exactly. Look at the description of the "Password" 
    parameter.
    
    V5R2:
    
    Password
         INPUT; CHAR(*)
    
         The password for the user ID. On security level 10 
    systems, the password is not required.
    
         You can specify the following special values:
    . . .
    
    V5R3:
    
    Password
         INPUT; CHAR(*)
    
         The password for the user ID or a special value.
    
         Password for the user ID
    
             * Length of password and CCSID of password are 
    required
    
         Special value
    
             * Length of password and CCSID of password are 
    not allowed when specifying a special value.
             * A special value must be a 10 character, blank 
    padded value in CCSID 37.
             * Special values allowed are:
    . . .
    
    Moreover, prior to V5R1 (and all of our development is 
    done at V4), the second optional parameter group didn't 
    exist at all.
    -- 
    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.