RE: Hiding Password Parm on QSYGETPH

["Marvin Radding" <MRadding@xxxxxxxxxxxx>]

That may be true if you don't set that parameter's DSPINPUT to *NO.
Then only it will display as PASSWORD().

Marvin


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan
Sent: Thursday, August 05, 2004 3:17 PM
To: Midrange Systems Technical Discussion
Subject: Re: Hiding Password Parm on QSYGETPH

Also, if there is a CMD parameter with the password involved somewhere 
and you don't set the PARM keyword, and there is command logging, it 
will show up in the log.

`- Alan

> This is a surprise to me. Which release are you using? Which audit
record
>
>are you looking at? The PS, CD, or some other one? Which field of that
>audit record contains the password? Are you calling QSYGETPH from a CL
>program that was created with the LOG parameter set to *YES or *JOB?
>
>Perhaps sharing the source of the program that calls QSYGETPH would be
>helpful. (Without any real hard-coded user IDs or passwords).
>
>Ed Fishel,
>edfishel@xxxxxxxxxx
>  
>

--
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.