A CL program submits DGL150R. So it is a batch CL program that is calling an RPG program.
Dave Begley | IT Manager
HealthSmart | Benefits Management, LLC
Dave.begley@xxxxxxxxxxxxxxx |
http://www.healthsmart.com/
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Therrien, Paul via MIDRANGE-L
Sent: Friday, July 28, 2023 4:19 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: Therrien, Paul <ptherrien@xxxxxxxxxxx>
Subject: RE: Issues after going from TR4 to TR7
NOTICE: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Re sending under correct subject line....
Are you calling the rpg from a command line?
Assuming you are then the call from a command line should look like this:
CALL PGM(DGL150R) PARM(X'000010000000000F' X'000000000000000F' X'002023072800000F')
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Dave Begley
Sent: Friday, July 28, 2023 4:04 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Issues after going from TR4 to TR7
Sorry about replying to the wrong message. I've been following the discussion in that thread and messed up.
The call is pretty simple. And if the program is recompiled with target release as *PRV, the error does not occur.
Calling program:
DCL VAR(&CPY) TYPE(*DEC) LEN(15 5)
DCL VAR(&PLAN) TYPE(*DEC) LEN(15 5)
DCL VAR(&BEGDT) TYPE(*DEC) LEN(15 5)
CALL PGM(DGR150E) PARM(&CPY &PLAN &BEGDT)
The program being called:
Dcl-pr DGR150E ExtPgm;
i_Cpy Packed(15:5);
i_Plan Packed(15:5);
i_Start Packed(15:5);
End-pr;
Dcl-pi DGR150E;
i_Cpy Packed(15:5);
i_Plan Packed(15:5);
i_Start Packed(15:5);
End-pi;
Job log:
Message . . . . : -CALL PGM(DGL150R) PARM(10000.00000 0.00000 20230728.00000
40 07/28/23 13:52:32.539712 DGR150E CLAIMDG *STMT DGR150E CLAIMDG
From module . . . . . . . . : DGR150E
From procedure . . . . . . : DGR150E
Statement . . . . . . . . . : 6000
To module . . . . . . . . . : DGR150E
To procedure . . . . . . . : DGR150E
Statement . . . . . . . . . : 6000
Message . . . . : Space offset X'00000000' or X'0000000000000000' is outside
current limit for object QCAWAREA.
Cause . . . . . : A program tried to set a space pointer, tried to use
storage outside a space, or tried to use an unallocated page in teraspace.
The space class is X'00'. The space class designates the type of space:
00-primary associated space (includes space objects). 01-secondary
associated space 0. 02-implicit process space for automatic storage.
03-implicit process space for static storage in activation group mark
X'0000000000000000'. 04-implicit process space for heap identifier
X'00000000' in activation group mark X'0000000000000000'. 05-constant space.
06-space for handle-based heap identifier X'00000000'. 07-teraspace offset
X'0000000000000000'. 08-teraspace for System i5 PASE memory address
X'0000000000000000'. Offset X'00000000' only applies to storage outside
teraspace. X'00000000000000000000000000000000' is a pointer to the teraspace
page or the start of the implicit process space for the allocation.
99 07/28/23 13:52:32.540687 QRNXIE QSYS *STMT QRNXIE QSYS
From module . . . . . . . . : QRNXMSG
From procedure . . . . . . : InqMsg
Statement . . . . . . . . . : 8
To module . . . . . . . . . : QRNXMSG
To procedure . . . . . . . : InqMsg
Statement . . . . . . . . . : 8
Message . . . . : Pointer or parameter error (C G D F).
Cause . . . . . : RPG procedure DGR150E in program CLAIMDG/DGR150E at
statement 006000 had an error due to a pointer not being correctly set. The
cause of the error is most likely one of the following: -- A basing pointer
was not set. -- A procedure pointer was not set. -- The pointer was set, but
the object it referenced has been destroyed. -- A parameter was not passed
to the program containing the procedure. -- A parameter was not passed to
the procedure by its caller within the program. -- A pointer offset was
greater than the size of the space the pointer was pointing to. Recovery .
. . : Check the job log for more information on the cause of the error and
contact the person responsible for program maintenance. Possible choices for
Dave Begley | IT Manager
HealthSmart | Benefits Management, LLC
Dave.begley@xxxxxxxxxxxxxxx |
http://www.healthsmart.com/
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Charles Wilt
Sent: Friday, July 28, 2023 3:45 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Issues after going from TR4 to TR7
NOTICE: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
There should be no issues...and we do it all the time.
Show us the parameters. What does screwed up mean? How are you calling it? From the command line or from another program? Show us the call.
The only time in 20+ years I've seen an issue is when the parameters were defined improperly between caller and callee.
It just happened to work on the older version, but broke on the new after re-compile.
In other words, you've very likely got something wrong somewhere...you've just been getting lucky.
Charles
On Fri, Jul 28, 2023 at 12:57 PM Dave Begley <Dave.Begley@xxxxxxxxxxxxxxx>
wrote:
We upgrade our test system (V7R4) from TR4 to TR7 last weekend. (It
was supposed to go to TR8 but they made a mistake.) When we compile a
CL program on the test system and run it on the production system, the
parameters are not getting correctly passed from program to program
and the program bombs.
I can compile the CL program with TGTRLS(*PRV) and the problem goes away.
Does anyone know if what I am doing is ok? Are there other issues
with having the test and production systems on different release levels?
Production will be updated in a couple weeks.
Dave Begley | IT Manager
HealthSmart | Benefits Management, LLC Dave.begley@xxxxxxxxxxxxxxx |
http://www.h/
%2F&data=05%7C01%7Cdave.begley%40healthsmart.com%7C39a57f4c01e54206cf6
708db8fa7f10c%7C2ce547c5e80a40628a56f25adceefb52%7C0%7C0%7C63826172369
5319652%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLC
JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BYLhc5k1eI1tPJ5WN54
jFcsJQVmH3o4S68Ed7MjWw%2F4%3D&reserved=0
ealthsmart.com%2F&data=05%7C01%7Cdave.begley%40healthsmart.com%7C17760
855a44b41667c8c08db8fa32b19%7C2ce547c5e80a40628a56f25adceefb52%7C0%7C0
%7C638261703199110966%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ
IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GUame
Pal0nf91oUAtXX4Nd7KMOE%2Bdi80WIS3qw03Qek%3D&reserved=0
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or intended recipient’s authorized agent, the
reader is hereby notified that any dissemination, distribution or
copying of this e-mail is prohibited. If you have received this e-mail
in error, please notify the sender by replying to this message and delete this e-mail immediately.
--
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://list/
s.midrange.com%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C01%7Cdave.b
egley%40healthsmart.com%7C17760855a44b41667c8c08db8fa32b19%7C2ce547c5e
80a40628a56f25adceefb52%7C0%7C0%7C638261703199110966%7CUnknown%7CTWFpb
GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
%3D%7C3000%7C%7C%7C&sdata=R4OVTetsZsXJ3gXV2GqOwwZRRgyIfK3lQezhWeEjrZQ%
3D&reserved=0 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.
This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or intended recipient’s authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
--
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.
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or intended recipient’s authorized agent, the reader is hereby
notified that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
midrange.com
