Re: Cannot Resolve to object error

[Dennis <iseries@xxxxxxxxxxxx>]

Does library QSOC exist on the system, and do the users have authority to access it?
++
Dennis
++
 "The major difference between a thing that might go wrong and a thing that cannot possibly go wrong is that when a thing that cannot possibly go wrong goes wrong it usually turns out to be impossible to get at or repair."
     -- Douglas Adams 


 

Sent from my Galaxy tablet phone.  Please excuse my brevity.
For any grammatic/spelling errors, there is no excuse.
++


"John.BresinaJr" <John.BresinaJr@xxxxxxxxxx> wrote:

> We are getting this error when our application users are running a
> stored procedure, does anyone have some suggestions.
>
> MCH3401    Escape                  40   10/21/11  09:59:59.750088  <
> lveContext             0003AC   QXDAEDRS    QSYS        *STMT
>                       From Program  . . . . . . . :   MnResolveContext
>                               To module . . . . . . . . . :   QXDAEDRS
> To procedure  . . . . . . . :  
> QxdaOptiBndSrvPgm__FP19XDAGlobalDataStruct
>                    Statement . . . . . . . . . :   25           *PRCLT
> Message . . . . :   Cannot resolve to object QSOC. Type and Subtype
> X'0401'
>                                       Authority X'0000'.
> Cause . . . . . :   Either a system pointer or a data pointer can not
> be
> resolved. For a system pointer, it can not be resolved to object QSOC,
> type
> and subtype X'0401', authorization X'0000', because either the named
> object
> was not in any context referred to or the correct object was located
> but the
> user profile did not have the required authority. The object types for
> some
> common type or subtype codes follow: -- 0190-Access group,
> 0201-Program,
> 0401-Library, -- 0701-Journal receiver, 0801-User profile,
> 0901-Journal, --
> 0B90-Data space, 0C01-Directory, 0C90-Data space index, -- 0E01-Job
> queue,
> 0E02-Output queue, 0E03-Message file, -- 0E02-User index, 0A01-Data
> queue,
> 1401-Class of service description -- 1501-Mode description,
> 0E05-Session
>     description, -- 1001-Device description, 1101-Line description, --
> 1201-Controller description, 1901-File, 1902-Message queue, -- 1903-Job
> description, 1904-Class, 1905-Command, 1906-Table, -- 1908-Edit
> description,
> 1909-Subsystem description, -- 190A-Data area, 190C-Graphic symbol set,
> 190D-Chart format, -- 1911-Query definition, 1912-Folder, -- 1915-Panel
> group, 1916-Menu group description, -- 1920-Data dictionary,
> 192D-Management
>       collection, 19D0 Work control block table, -- 19D2-System value,
> 1B01-Process control space, -- 1E01-Byte stream file, 1E03-Local
> socket,
> 1E06-Character special file, -- 1E07-First-in first-out special file
> For a
> data pointer, it can not be resolved because the named object is not
> located
> within any program activation currently known to the process. Recovery 
> . .
>    . :   Either specify the correct object name or specify the correct
>                                      authority for the object.
>
> John Bresina Jr | Sr Engineer | TTS Server Tech VOC HQ | *Target |  33
> S 6th St | Minneapolis, Mn 55402 | 612 304 3665 (ph)
>
> -- 
> 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.