Re: A Strange Problem with compiling an SQLRPGLE -- RPG400-L

Marvin,
Try the compile specifying the TOSRCFILE keyword with a different source
file. This will create the expanded source in that file/member. Then try
to compile the expanded source and see if you are having the same issue.
This will allow you to determine if there is a problem in the CRTRPGSQLI
command processing or in the compiler.

Jeff Young
Sr. Programmer Analyst

On Thu, Aug 31, 2017 at 10:02 AM, Marvin Radding <
marvin.radding@xxxxxxxxxxxxxxxxxxxxx> wrote:

No RDi. This is actually during the transfer from the Pre-Compiler to the
RPG/LE Compiler. I get a full listing from the Pre-Compiler with no errors
as the first diagnostic message states.

Thanks,

Marvin
No trees were killed in the sending of this message, but a large number of
electrons were terribly inconvenienced, traumatized, triggered, and crying
for their safe spaces.

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Justin
Taylor
Sent: Thursday, August 31, 2017 6:44 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <
rpg400-l@xxxxxxxxxxxx>
Subject: RE: A Strange Problem with compiling an SQLRPGLE

Have a verify with RDi? I find that to be helpful sometimes when I get
unusual errors from the pre-compiler.

-----Original Message-----
From: Marvin Radding [mailto:marvin.radding@xxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, August 31, 2017 8:38 AM
To: 'RPG programming on the IBM i (AS/400 and iSeries)' <
rpg400-l@xxxxxxxxxxxx>
Subject: A Strange Problem with compiling an SQLRPGLE

I am having a very strange problem trying to compile an SQLRPGLE. The
following is the job log. I have trimmed it down to the errors that I think
are relevant to the problem. Has anyone had a problem like this and what
did you do to correct it?

Message . . . . : Diagnostic check
of source is complete. Highest severity
is 00.
Cause . . . . . : The diagnostic
check of the specified source member is
------------ 34 data records excluded ------------------------------
-----------------------------------------------------
MCH1210 Escape 40 08/31/17 06:24:38.870799
QSQRCHK QSYS *STMT QSQRCHK QSYS
From module . . . . . . . . :
QSQRCHK
From procedure . . . . . . :
EXPRTYPE
Statement . . . . . . . . . : 46287
To module . . . . . . . . . :
QSQRCHK
To procedure . . . . . . . :
EXPRTYPE
Statement . . . . . . . . . : 46287
Message . . . . : Receiver value
too small to hold result.
CPF9549 Escape 40 08/31/17 06:24:38.891595
QTEUTILS QSYS *STMT QSQPMAIN QSYS
From module . . . . . . . . :
TEEXCH
From procedure . . . . . . :
_Exception_Handler_Exit_Environment
Statement . . . . . . . . . : 4
To module . . . . . . . . . :
QSQPMAIN
To procedure . . . . . . . :
BLD_VIEW_COMMON
Statement . . . . . . . . . : 8700
Message . . . . : Error addressing
API Parameter.
Cause . . . . . : An error
occurred addressing parameter 2 of the
QteAddViewText API. The reason
code was 2. The following are the reasons
why this message is issued. 1 -- A
pointer was used that is not available
------------ 13 data records excluded ------------------------------
---------------------------------------------------
CPF9999 Escape 40 08/31/17 06:24:38.891667
QMHUNMSG *N QSQPMAIN QSYS
To module . . . . . . . . . :
QSQPMAIN
To procedure . . . . . . . :
QSQPMAIN
Statement . . . . . . . . . : 8733
Message . . . . : Function check.
CPF9549 unmonitored by QSQPMAIN at
statement 0000008700, instruction
X'0000'.
Cause . . . . . : An escape
exception message was sent to a program which
did not monitor for that message.
The full name of the program to which the
------------- 8 data records excluded ------------------------------
-----------------------------------------------------
CPF2410 Escape 40 08/31/17 06:24:38.891699
QMHRCVPM QSYS 15E9 QSQPMAIN QSYS
To module . . . . . . . . . :
QSQPMAIN
To procedure . . . . . . . :
QSQPMAIN
Statement . . . . . . . . . : 15203
Message . . . . : Message key not
found in message queue QJOBMSGQ.
Cause . . . . . : Message key
X'40404040' may have been deleted from message
queue QJOBMSGQ, or message key
X'40404040' may not be valid. Recovery . . .
: Verify the correct message key
(MSGKEY) parameter is used or omit the
request. The message key is valid
only if obtained in one of the following
ways: -- Returned in the message
reference key (KEYVAR) parameter on the
Receive Message (RCVMSG) command
or Send Program Message (SNDPGMMSG)
------------- 7 data records excluded ------------------------------
-----------------------------------------------------
CEE9901 Escape 30 08/31/17 06:24:38.994940
QLEAWI QSYS *STMT QSQPRUN QSQL
From module . . . . . . . . :
QLEDEH
From procedure . . . . . . : Q LE
leDefaultEh2
Statement . . . . . . . . . : 175
Message . . . . : Application
error. CPF2410 unmonitored by QSQPMAIN at
statement 0000015203, instruction
X'0000'.
Cause . . . . . : The application
ended abnormally because an exception
occurred and was not handled. The
name of the program to which the
unhandled exception is sent is
QSQPMAIN QSQPMAIN QSQPMAIN. The program was
stopped at the high-level language
statement number(s) 0000015203 at the
time the message was sent. If more
than one statement number is shown, the
----------- 336 data records excluded ------------------------------
-----------------------------------------------------

Thanks,

Marvin
No trees were killed in the sending of this message, but a large number of
electrons were terribly inconvenienced, traumatized, triggered, and crying
for their safe spaces.

Notice: This e-mail transmission may contain information that is
proprietary, privileged and/or confidential and is intended exclusively for
the person(s) to whom it is addressed. This message may also contain
Protected Health Information (PHI) and must be treated confidentially and
handled in accordance with HIPAA and other federal and state privacy laws.
Any use, copying, retention or disclosure by any person other than the
intended recipient or the intended recipient's designees is strictly
prohibited. If you are not the intended recipient or their designee, please
notify the sender immediately and delete this e-mail (and any accompanying
attachments).

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD