It should-a-been written on an HP3000 in the first place, but what-ever!

The unix application is a in-house written (MF-Cobol) Labor Data
Collection system. The application administrator has the ability to stop
and start terminal server processes from a single menu system (ksh
script). The processes are then adopted by a system process ( maybe
PID#1)  and continue to live long after the ksh script menu is dead an
gone.  These processes are running with a stdin & stdout directed to a
tty device on the terminal server. The terminal device (ADDS 4000) is
unable to receive a "Login:" prompt and they depend on the sys/app
administrator to start the processes, nice security feature.

I can emulate this functionality on MPE by using DTC to take the place
of a terminal server, and a batchjob to take the place of PID#1, and
then ( using MPE/POSIX ) modify the ksh script to echo a start command
into a message file instead of forking a process. Then the batchjob will
read the message an start the appropriate process on the specific
"NAILED!" ldev on a DTC.

I have tested this theory and it works, except for one minor detail;

Every time the batchjob starts a process up with a STDIN & STDLIST
redirected to a specific LDEV a REPLY is generated on the system
console. I had this problem once before, but I can't remember how I got
around it, that was on a classic 3k anyway.

It occurred to me to create a custom profile that would somehow disable
or bypass the reply option for these specific ldev's. However I remember
an old HP application called MM/3000 that did exactly what I'm trying to
do. I'm thinking that it's something simple that I'm just overlooking,
something like a file equation or some createprocess switch somewhere,
do I really need to reconfigure these ports?

All comments will be humbly accepted.

Regards,
Michael Anderson
Houston, Texas