|
Even more info... this is weird.
I found the program that lists job log messages that it appears to be
coming from. Ran my program in debug to verify and no errors appeared in
the QGYSERVER job.
I then ended debug, ran it again, errors. Repeated with debug on, no
errors, and turned it off and the errors popped up again.
On Sun, Jan 15, 2023 at 9:04 AM Brad Stone <bvstone@xxxxxxxxx> wrote:
Looks like another APAR out there for this too that was just issued aweek
ago:named
https://www.ibm.com/support/pages/apar/SE78985
Apparently they broke it again or the original fix wasn't right.
On Sun, Jan 15, 2023 at 8:55 AM Brad Stone <bvstone@xxxxxxxxx> wrote:
Display Call Stack
System:
Job: QGYSERVER User: BVSTONE Number: 201055
Thread: 00000018
Type Program Statement Procedure
QGYLSRVR QSYS /0210
I already have PTF SI78892 installed.
It's also throwing out a ton of dumps, job logs, etc... here's a dump:
DUMP TAKEN FOR UNMONITORED ESCAPE MESSAGE
.MESSAGE ID- MCH0601
.MESSAGE FILE- QCPFMSG LIBRARY-
*LIBL
.SEVERITY- 40
.MSGTYPE- 0F
.SENDING-
..PROGRAM- QGYLSRVR
LIBRARY- QSYS
..INSTRUCTION- 00AC
.RECEIVING-
..PROGRAM- QGYLSRVR LIBRARY-
QSYS
..INSTRUCTION- 00AC
.MESSAGE-
Space offset X'00000000' or X'0000000000000000' is outside current
limit for object .
.MESSAGE DATA-
000000 00000000 00000000 C4C248B1 79001900 00000000 00000000
00000000 00000000 * DBç£` *
000020 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 * *
I am 99% sure this is coming from the List Jobs API in my job monitoring
program... maybe I'll dig into that but it's been running fine for
literally 20 years.
On Sun, Jan 15, 2023 at 4:08 AM Marc Rauzier <marc.rauzier@xxxxxxxxx>
wrote:
Le 14/01/2023 à 21:38, Brad Stone a écrit :
Anyone seen this?
Hello
This APAR might apply to your case
https://www.ibm.com/support/pages/apar/SE77077
Subtype
Message ID . . . . . . : MCH3401
Date sent . . . . . . : 01/14/23 Time sent . . . . . . :
14:10:10
Message . . . . : Cannot resolve to object ??????????. Type and
be
X'0401' Authority X'0000'.
Cause . . . . . : Either a system pointer or a data pointer can not
?????????? ,
resolved.
For a system pointer, it can not be resolved to object
type
and subtype X'0401', authorization X'0000', because either the
--objectlocated but
was not in any context referred to or the correct object was
thedescription
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,
-- 0E0A-User index, 0A01-Data queue, 1401-Class of service
-- 1501-Mode description, 0E05-Session description,control
-- 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
block table,special
-- 19D2-System value, 1B01-Process control space,
-- 1E01-Byte stream file, 1E03-Local socket, 1E06-Character
file,object is
-- 1E07-First-in first-out special file
For a data pointer, it can not be resolved because the named
notprocess.
located within any program activation currently known to the
the
Recovery . . . : Either specify the correct object name or specify
Cloud
correct authority for the object.
Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
Provider!--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.