Call to runube failing

tnelipov

Active Member
If you want the no-nonsense version...

- Use the account that jde services run under (jdeb7333 perhaps) as the user
who issues runube commands. This method works easily.

- If you desire to call runube from a user other than whoever owns the jde
services, results may vary. Is it possible to use runube as a different
user - it certainly should be (I have not done it).

In my mind, this comes down to a cost vs benefit scenario in terms of the
effort and time involved in troubleshooting what most likely is a
permissions issue. What is the business reason to use runube from another
UNIX account and does it justify the time spent?

My two cents...

Tony

========================


The user we are using to log into the environment is not the problem. As I
stated, the call to runube as the jde unix user works, but when I use a
different unix user, it does not work. My concern was that there are unix
permissions/environment variables that are not set correctly, even though
the environments are set up the same. Let me repeat, the JDE USER is not
the problem here, unless there is a link between which UNIX user runs the
job and which JDE USER is specified for the environment login.

OneWorld Xe on SUN Machine running Oracle 8i

------------------------------------------------------------------------------
This e-mail is intended for the use of the addressee(s) only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.

==============================================================================
 
Forget who just mentioned this on the list but why not have the JDE user
issue the command using another One World user. The key here is that UNIX
and One World don't have to be the same. By this I mean I log in to UNIX as
JDEXE (our JDE user that actually starts and stops One World) and I schedule
all our runube jobs in his (JDEXE's) crontab. The users that are used in the
runube commands vary (no MCU security I use SCHED, MCU security I use XXXEOD
where XXX is a branch abbreviation, etc.) I can see where some shops might
want to create UNIX users similar to JDE to allow more people to do things
from the command line but I generally advise against it. There is really no
reason anyone except the CNC/sys admin should have the power of the JDE
user. Remember once you give a user the same permissions as JDE they can
move anywhere JDE can and next thing you know your spec files are missing or
all your jobs in /PrintQueue are gone. Just my 2 cents.

Mark Siebenschuh
Enterprise Software Systems Administrator
Physician Sales and Service
4345 Southpoint Blvd.
Jacksonville, FL 32216
904-332-3092




Mark Siebenschuh
HP9000/Oracle 8.0.5/JDE XE/Lots of Citrix
 
Back
Top