I should have been more clear.  What I'm referring to are substituted
parameters in jobs such as lockwords, remote logon passwords, ftp
passwords, etc., which may be substituted by value as the job is
streamed.  I didn't mean to imply the job card passwords were displayed
(hopefully, no one is still embedding passwords in job cards! :(    ).

Lee


______________________________ Reply Separator _________________________________
Subject: Re: Re[2]: Reading Input Spoolfiles
Author:  Tracy Johnson <[log in to unmask]> at ~INTERNET
Date:    10/8/96 10:19 AM


I just tested reading an #I file using MPEXs PRINTI command.  I did not
find the password displayed.  We do have STREAMX enabled.  There is a
comment area added that says what the stream file name is, who streamed
it, on what LDEV, and a date time stamp, but no passwords.  If there was
a lockword embedded, perhaps it would be displayed.
 ----------
From:  owner-hp3000-l[SMTP:[log in to unmask]]
Sent:  Tuesday, October 08, 1996 9:15 AM
To:  HP3000-L
Subject:  Re[2]: Reading Input Spoolfiles

One caveat, here, is that input spoolfiles might contain passwords or
other data substituted at stream time (STREAMX and JMS/3000 can do
this) which you don't want exposed.  NBSpool and ESPUL (we use both for
various reasons) have the capability of securing input spoolfiles.  I
consider ESPUL more robust in this regard, being able to secure this
for individual users or groups of users, where NBSpool accomplishes
this by setting a password for INPUT mode.

Lee Gunter          [log in to unmask]
HMO Oregon