[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index] [Date Index] [Thread Index]
[SQR-USERS Info] [SQRUG Home Page]

[sqr-users] SQR and Appworx



Hi,

   If anyone is using Appworx as a job scheduler for SQR jobs, how did you 
get around this problem:

in the program option script SQR_MC Appworx calls the SQR command line as 
follows

command="sqr $program $login $srv -E$module-j$seq_no.err 
-I/opt/appworx/banner/oplib/sqr/proc_lib/ $sqropt @$par"
$command

By having $login on the command line, the username and password for Appworx 
shows up in the ps listing, allowing everyone on the machine to basically 
see the password for an account that has DBA privs.

generally when I run SQR from a Unix script I can pass in the connect info 
via a here document
like

$command<<__EOF__
$login
__EOF__

This doesn't work with Appworx, because SQR is using a @par file for 
parameters, so it is looking in the par file for the login information 
before checking the here document.

I have thought about changing the Appworx script to put the username and 
password into the par file, but I am not crazy about this idea as Appworx 
leaves the par files in the run directory.

I have also thought about setting up Appworx as an OPS$ account so that it 
could connect without a password and use OS authentication, but I am not 
sure if the Appworx agents are really "logged into" the OS in such a way 
that OS authentication would work.

Has anyone battled with this problem and come up with a good solution?

Thanks
Colin

=======================================
Colin Abbott
Analyst (Finance)
Information Systems Resources
McGill University
E-mail: Colin.Abbott@MCGILL.CA
Fax: 1-514-398-8252
=======================================

_______________________________________________
sqr-users mailing list
sqr-users@sqrug.org
http://www.sqrug.org/mailman/listinfo/sqr-users