We are converting from MVS to Unix and will be utilizing a product to transmit files
between the two systems (Xcom). One requirement of Xcom is that a Userid and
Password are required to transmit.
We are running scripts to replace our MVS procs, so I've created one to handle the
transfer. My problem is that we need a way to secure a file that will hold the
Userid and Password. I can remove the read-write access to the file, but need to
leave the execute access for other users to run the script. In doing so, ksh can
expose the variables being set within the script with the "-v" verbose option.
Is there any way to fully protect this file so that even the verbose mode will not
display the contents?