|
I think using SBMJOB the actual command to process is part of the message sent to the command processor. So you see the request message in the JOBLOG. It will be difficult for the one or two commands to change the secret parms into substitution text (the asterixes). I do not think IBM will enhange/upgrade UIM for that, even though it can be called a securty risk. Just my thoughts. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 18-9-2006 at 15:04 Ingvaldson, Scott wrote:
Yes, and I think that it's definitely an issue. We ran into the same
thing inputting passwords for our FTP commands. We used CHGJOB
LOGCLPGM(*NO) to get them out of the joblogs. -----Original Message----- date: Mon, 18 Sep 2006 13:27:53 -0400 from: rob@xxxxxxxxx subject: CMD, DSPINP, SBMJOB Keep in mind that if you prompt a command like CHGUSRPRF and put in a
password, and then hit F9, or look at DSPJOBLOG, you will not see the
password. However if I do SBMJOB CMD(CHGUSRPRF USRPRF(ROB) PASSWORD(spud)) And then hit F9, once again I'll see SBMJOB CMD(CHGUSRPRF USRPRF(ROB)
PASSWORD(spud))
and I'll also see it in DSPJOBLOG. Has it always worked like this? I am on V5R4 and have been for awhile.
Does anyone find an issue with this?
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.