Please ignore the question.
The call to the profile switch was missing on the production machine.
So dumb!
Thanks
From:   "Don Brown via MIDRANGE-L" <midrange-l@xxxxxxxxxxxxxxxxxx>
To:     midrange-l@xxxxxxxxxxxxxxxxxx
Cc:     "Don Brown" <DBrown@xxxxxxxxxx>
Date:   21/02/2022 04:29 PM
Subject:        Not authorised baffling
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>
Hello,
I have a web service I was testing using IWS on the development box - 
works great.
I created the web service on the production machine.
Web service is running under the same profile QWSERVICE.
The web service retrieves some attributes from user profiles - does not 
really matter for this explanation as the process is the same on both 
machines.
The program called by the web service is owned by QSECOFR but runs under 
profile *USER - this calls a service program that is the same - owned by 
QSECOFR and runs under profile *USER
I have checked the authority on the QSECOFR profile object and is the same 
on both machines.
I have checked the authority on the QWSERVICE profile object and is the 
same on both machines.
I have compared both profiles on the the two machines and they are the 
same.
Both machines are at 7.3 and same ptf level
I don't mind that I am getting the not authorised message on the 
production machine but why am I not getting the same message on the 
development machine ?
What am I not checking / missing ?
Thanks all
Don
--
This email has been scanned for computer viruses. Although MSD has taken 
reasonable precautions to ensure no viruses are present in this email, MSD 
cannot accept responsibility for any loss or damage arising from the use 
of this email or attachments..
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.