Michael:

Create a program (Cobol, or even a script),  using a database containing the
name and password for each program that you want to run.  The program then
decides (given a parameter) what program it needs to run and creates a file
equation with the lockword (file a=myprog.pub.acct/abc). The program then
terminates. The next command in the job would be run *a.  If you need to know
what program is going to run, echo the program name to the stdlist.

In posix, you can create files and filelockwords that have control characters
enbedded in the name/lockword.  You can even create a file with only one space
as a file name or multiple spaces as the file name.

Hopefully, I have given you some food for thought.

Want more info, send me a email.

Olav Kappert
IOMIT International

PS. POSIX can be used in many wonderful ways.
****************

Michael Anderson wrote:

> Hey ya'all,
>
> If ya don't have a fancy job scheduler, like Maestro, or such. What is
> the best way to hide a lockword in a job stream. I'm not talking about
> logon passwords, I use the PASSEXEMPT option of the JOBSECURITY command
> for that. I'm talking about file lockwords.
>
> One approach that I have used in the past is to say:
>
> Setvar keycode chr(%115) + chr(%66) + chr(%60) + chr(%60) + chr(%71) +
> chr(%61) + chr(%67)
>
> Then
>
> RUN MYPROG/keycode.GRP.ACCT
>
> Which seems to be a little more secure then just:
>
> RUN MYPROG/M600917.GRP.ACCT
>
> Any other options?
>
> --
> Michael Anderson
> Spring Independent School District
> 16717 Ella Boulevard
> Houston, Texas 77090-4299
> office: 281.586.1105
> fax: 281.586.1187
> -
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *