User Isue Please Help Urgent

Mike

Moderator
we have login script to connected mfg/pro database .But one user is able to generate report but another not. suppose i have two users "iunit" and "jio" . Here "iunit" able to generate report but not another user "jio". Is that unix or mfg/pro permsioon issue? Please help this issue
its very urgent.

Any Qad guy or anyone??????????//
 

Mike

Moderator
This script is to Start Multi-user session of MFG/PRO Production Database

# Setting up Environment Variables
DLC=/appln/pro91d/dlc;export DLC
PATH=$PATH:$DLC;export PATH
PROMSGS=$DLC/promsgs;export PROMSGS
PROTERMCAP=$DLC/protermcap;export PROTERMCAP
PS1='$$ ';export PS1
DB=/data/cd1/db;export DB

stty intr '^c'
# Set terminal type.
TERM=vt100;export TERM

PROPATH=./:/data/cd1/pgm/mfgpro/:/data/cd1/pgm/mfgpro/xrc/:/data/cd1/pgm/m fgpro/doti:/appln/pro91d/dlc/bin:/data/cd1/pgm/mfgpro/xx:/data/cd1/pgm/mfgpr o/doti:/data/cd1/pgm/mfgpro/frt/nb:/data/cd1/pgm/mfgpro/fusion:/data/cd1/p gm/mfgpro/fusion/ex:/data/cd1/pgm/mfgpro/fusion/f1:/data/cd1/pgm/mfgpro/fusi on/c1:/data/cd1/pgm/mfgpro/fusion/g1:/data/cd1/pgm/mfgpro/fusion/h1:/data/p el1/pgm/mfgpro/fusion/p1:/data/cd1/pgm/mfgpro/fusion/r1:/data/cd1/pgm/mfgpro /fusion/yf:/data/cd1/pgm/mfgpro/qad:/data/cd1/pgm/mfgpro/qad/sw:/data/cd1/ pgm/mfgpro/frm:/data/cd1/pgm/mfgpro/frm/zx:/data/cd1/pgm/mfgpro/local:/data /cd1/pgm/mfgpro/local/xx:/data/cd1/pgm/mfgpro/fams:/data/cd1/pgm/mfgpro/fam s/fas3:/data/cd1/pgm/mfgpro/fams/fas3/zf:/data/cd1/pgm/mfgpro/fin:/data/pel 1/pgm/mfgpro/fin/xu:/data/cd1/pgm/mfgpro/fin/xi:/data/cd1/pgm/mfgpro/fin/xf: /data/cd1/pgm/mfgpro/engg:/data/cd1/pgm/mfgpro/engg/ze:/data/cd1/pgm/mfgpr o/vs;export PROPATH

# Start MFG/PRO Application.

exec $DLC/bin/_progres $DB/mfg.db -db $DB/cool_pel.db -ld cool_ul -db $DB/m fghelp -ld qadhelp -e 100 -l 1000 -p mf.p -D 50 -d dmy -yy 1950 -h 8 -cpinternal IBM850

please help meee.
 

Cringer

ProgressTalk.com Moderator
Staff member
Do they get any errors? At what point does the report fail? What have you tried?
 

Mike

Moderator
report failed at last time .when it is getting output. its showing database not connected (1006)
 

TomBascom

Curmudgeon
Look in the DB .lg file to see what errors the user got that prevented them from successfully connecting.
 

Mike

Moderator
no User is successfully login to mfg/pro but when he creating report 32.12.24 option .p will run successfully but output is not coming . showing database not connected
.
 

TomBascom

Curmudgeon
Clearly the .p is NOT running successfully -- you say that it is throwing an error message. That is not success.

"Database not connected" means what it says.

mfg/pro consists of several databases. The number of databases and their names vary by version of mfg/pro and you may, or may not, have "bolt-on" databases. You may need to check more than one log file. Some log file somewhere should show a connection attempt failing that corresponds to the user and database which is not connected.

Either that or the user is attempting to connect to a database that does not exist.

If you have the source to the .p that the menu option runs then it should have in it information about the databases that it needs or which it is attempting to connect to.
 

TheMadDBA

Active Member
QAD loves to connect/disconnect to different databases depending on the user and site.....

Go to 36.6.2 to review the database connections for each user (the one that works and the one that doesn't).

Verify that the users are using the same startup script.

You can look at 36.6.1 to see which databases are supposed to be connected at startup time. Don't change anything here unless you really know what you are doing.
 

dulecki

Member
What version of QAD are you running? In current versions, there is no 32.12.24 option... 32.12 is the Fixed Asset Report. So I'm going to leap to the conclusion that you've got a custom program... you may need to review that to see where it's trying to put things.

If one user can run it and another can't, it's likely to be a security issue somewhere... either in QAD or the OS. Since your script doesn't show the usual

cd # Change to user's home directory

line, it's entirely possible that the second user doesn't have OS permissions to write to the working directory. This would show for any report going to that destination, though... something you should be able to check easily.
 
Top