Fwd: Two things - *JOB scope and Parm passing after ILE conversion

--- the forwarded message follows ---

---

• Subject: Two things - *JOB scope and Parm passing after ILE conversion
• From: Patrick W Conner <PWConner@xxxxxxxxxxx>
• Date: Thu, 03 May 2001 07:04:15 -0400
• Organization: ConnecTown

A fellow programmer came to me with the following situation:

An OPM CLP with OVRDBF/OPNQRYF calls an ILE RPG. The results prove the
OPNQRYF
statement is being ignored. I see the CLP is in DAG and the RPG is in
*NEW
(substitute your own AG no.). I tell him to change his OVRDBF scope to
*JOB. He does
and gets the same results. Not understanding but still looking for a
solution we run
into situation no. 2.

First, remove all changes made in the above scenario. Now, we convert
OPM CLP to ILE.
The new module is changed from a CALL to a CALLPRC. The CRTPGM binds the
new CLLE
module with the RPGLE module used in the previously called program.
However, before I
can reach the CALLPRC statement in the CL I run into another CALL to a
program named
DATEFUNC. It turns out my CL has the first parm to DATEFUNC defined as
CHAR 6 where
DATEFUNC defines its first parm as CHAR 8. My CL passes '041101' where
DATEFUNC
receives '041101TE'. The 'TE' causes DATEFUNC to not realize the value
as a date and
passes back an error like it should. My question is, "Why was this
working before the
conversion?"
FYI - the new CLLE/RPGLE program uses *NEW AG where DATEFUNC is in QILE
(I don't know
if this matters.)

Patrick Conner
www.ConnecTown.com
(828) 244-0822

---