RE: SOLUTION to Authority Problem to *LOCALE QSYS/QLGPGCMA

Just to follow up on this,
Having logged the problem with IBM it appears that many file system
operations require *RX authority to the root of the IFS to execute
correctly.
Having changed this all now works correctly again.

You can read a little more on it in the "Tips and Tools for Securing you
iSeries manual"

Neil   

-----Original Message-----
From: Carley, Neil [mailto:neil.carley@xxxxxxxxx]
Sent: 10 July 2003 16:53
To: 'MIDRANGE-L@xxxxxxxxxxxx'
Subject: Authority Problem to *LOCALE QSYS/QLGPGCMA


Hi all,

Having searched the archives etc I can find many references to the
following in various forms but no definitive answer.
After installing Websphere App Server Network Deployment edition and
upgrading MQ from V5R2 to Websphere MQ we are getting the following
error :

Not authorized to object.  Object is /QSYS.LIB/QLGPGCMA.LOCALE

This occurs in a wide variety of jobs, both application jobs and system
jobs.  In some cases, it seems to have no deleterious effect.  In other
cases, it causes the job to terminate abnormally.  For example, it has
not been possible to start TCP HTTP servers or MQSeries.  

The default authority to the locale object is as follows:
                            Display Object Authority

 

 Object . . . . . . . :   QLGPGCMA        Owner  . . . . . . . :   QSYS

   Library  . . . . . :     QSYS          Primary group  . . . :   *NONE

 Object type  . . . . :   *LOCALE         ASP device . . . . . :
*SYSBAS  
 

 Object secured by authorization list  . . . . . . . . . . . . :   *NONE

 

                          Object

 User        Group       Authority

 QSYS                    *ALL

 *PUBLIC                 *USE


We changed the authority to public *all which had no effect 

Setting the user profile parameters to LOCALE(*NONE) and
SETJOBATR(*NONE) has no beneficial effect.   

The 'workaround' is to grant *ALLOBJ authority to certain user and
system profiles.

Has anyone had this and found a resolution that doesn't involve allobj
across multiple profiles.

thanks
Neil 

   
  

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.