Resolving AS/400 error messages regarding attempts to use an object without authority

I'm the assistant data center manager at the People's Bank of Sri Lanka. These days, our in-house development team tests SMS banking. The following error messages appear in the job log during that job process in the system. 
Display All Messages
                                                          System:   S65A3E2D
 Job . . :   QZDASOINIT    User . . :   QUSER         Number . . . :   050651

     Job 050651/QUSER/QZDASOINIT started on 02/01/09 at 10:59:38 in subsystem
       QUSRWRK in QSYS. Job entered system on 02/01/09 at 10:59:38.
     User NIMALRJ from client 15.65.0.112 connected to server.
     Attempt to use permanent system object NIMALRJ without authority.
     Attempt to use permanent system object NIMALRJ without authority.
     Scalar operand contains a value that is not valid.
     Scalar operand contains a value that is not valid.
     Scalar operand contains a value that is not valid.
     Scalar operand contains a value that is not valid.

                        Bottom  Press Enter to continue.
 F3=Exit   F5=Refresh   F12=Cancel   F17=Top   F18=Bottom
The following is the journal entry that appears. 

Display Journal Entry

 Object . . . . . . . :                   Library  . . . . . . :
 Member . . . . . . . :
 Incomplete data  . . :   No              Minimized entry data :   *NONE
 Sequence . . . . . . :   139269996
 Code . . . . . . . . :   T  - Audit trail entry
 Type . . . . . . . . :   PS - Process user profile swap

             Entry specific data
 Column      *...+....1....+....2....+....3....+....4....+....5
 00001      'HQUSER                                            '
 00051      '            '
Would you be able to explain what a "profile swap" is? Also, are these job log error messages appearing because of the profile swap?
A profile swap occurs when the process or thread changes the profile under which it's running.

This happens routinely in servers such as the Telnet and database servers. I don't think that the profile swap entries in the audit journal have anything to do with the "attempt to use permanent system object NIMALRJ without authority."

To find the source of that issue, you should be looking for an AF subtype A entry where the object name is NIMALRJ.

This was first published in April 2009

Back to top