On 20-Jun-2016 11:07 -0500, Bradley Stone wrote:
I have one system where the job log randomly spits out this error
about 25 times in a row (all in less than a second):
Data area CGIDEBUG in *LIBL not found.
Additional Message Information
Message ID . . . . : CPF1015 Severity . . . . . : 40
Message type . . . : Escape
Date sent . . . . : 06/20/16 Time sent . . . . : 10:46:55
Message . . : Data area CGIDEBUG in *LIBL not found.
Recovery . . . : Either correct the data area name or change the
library name (DTAARA parameter). Then try the request again.
FWiW responses inline:
As I repeat so often, if wanting worthwhile feedback via a forum
topic about messages in a joblog, do not copy\paste from a joblog that
was presented to the display; collect instead, the _spooled_ joblog so
as to ensure providing some relevant context; context that will not be
included with just the copy\paste of F1=Help details.
I've searched through every program and not found any reference to
any of the CGIDEBUG commands or settings as found here:
[http://www.easy400.net/cgidev2o/exhibiu5.htm]
If there is source and debug-capable programs, then with the spooled
joblog, the specific code and failure should be easily located.
So it must be something internal. But it's not happening all the
time.. it's just random.
The spooled joblog will generally reveal exactly what program and
[module and procedure and statement or] instruction for the condition
being diagnosed. That would reveal also, what program diagnosed the
error, from which can be inferred the failing request; despite the
request [message, for yet additional context] might not be included, per
lack of CL command request logging [because perhaps the request is not
CLP, or the CL program was created with LOG(*NO) and\or the job runs
with LOGCLPGM(*NO)].
I haven't been able to recreate it yet but I am still trying
everything. :)
I don't think it is a big issue as it's just a warning, but it's odd
that it doesn't happen for every CGI program.
FWiW: Being of type "Escape", the logged condition is officially an
"exception"; the expected effect for what might be called a /warning/
generally would be a "Diagnostic" condition. Possibly, the programmer
decided there was too little value in /moving/ the Escape message [for
which a side effect, IIRC, is converting Escape to Diag] or /removing/
the Escape message. Typically, if the messages are considered by the
programmer to be innocuous, then leaving such messages visible as Escape
or unaccompanied by a diagnostic that reveals why the Escape remains
visible, is regarded by many programmers as /poor programming/; esp. if
the context of the logged error msg CPF1015 was the effect of a Check
Object (CHKOBJ) or Retrieve Data Area (RTVDTAARA) for which the program
then decided that an alternate\extended code-path specific to
debugging\logging should not occur.
Any ideas would be great. I don't know if the yahoo group works
anymore for support of CGIDEV2 but I did find the same question
posted a few years back and they were just forwarded to the page I
linked above. Not much help.
[
https://groups.yahoo.com/neo/groups/Easy400Group/conversations/messages/15515]
"ADDLIBLE CGIDEV2"
Presuming the following topic is the /same/ as what was described in the
OP, the following context suggests: the /failing/ request is a RTVDTAARA
at statement 11100 of procedure ISDEBUG of module XXXDEBUG of program
HSSFCGI. My SWAG: the naming ISDEBUG likely implies a query something
like "Is Debug Desired\Active" for which the failure per missing object
likely gives the effective answer\conclusion to the program that "Debug
is not Desired\Active"; that if the above Add Library List request is
effected [possibly instead by Job Description], then the error will no
longer be visible, and /debug/ activity can\will occur within the
XXXDEBUG processing.
[
https://groups.yahoo.com/neo/groups/Easy400Group/conversations/messages/15511]
"...
MSGID TYPE SEV DATE TIME
FROM PGM LIBRARY INST TO PGM LIBRARY INST
CPF1015 Escape 40 27/09/10 15:18:43.127672
QWCSRTVR QSYS 00B6 HSSFCGI HSSFCGI *STMT
To module . . . . . . . . . : XXXDEBUG
To procedure . . . . . . . : ISDEBUG
Statement . . . . . . . . . : 11100
Message . . . . : Data area CGIDEBUG in *LIBL not found.
..."
midrange.com
