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 VERNON HAMBERG Owner via MIDRANGE-L
Sent: Friday, July 28, 2023 3:20 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: VERNON HAMBERG Owner <vhamberg@xxxxxxxxxxxxxxx>; midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: Visibility to program compilation options
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.
Hi Jon
I just looked at BOUND_MODULE_INFO - 7.5 version has nothing about FIX*. I also looked at CRTRPGMOD - no parameter related to this. I also found that the only command I see with FIXDECDTA is CRTS36RPG - the docs say that FIX_DECIMAL_DATA is OPM only, as well
I haven't seen any view that reports on FIXNBR. Time for a good "idea"?
Cheers
Vern
On Fri, 28 Jul, 2023 at 2:03 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
To: midrange systems technical discussion
You need to look at the module data Bill - if it is anywhere it will be there. Since an ILE program can be built from many modules - each of which could have different settings - it makes no sense for it to be at the PGM level as it was with OPM.
Jon P
On Jul 28, 2023, at 9:35 AM, Howie, Bill <BHowie@xxxxxxxxxxxxxxxx<mailto:BHowie@xxxxxxxxxxxxxxxx>> wrote:
Rob,
I was able to look at the PROGRAM_INFO view for a specific object that I had just compiled using CRTBNDRPG with FIXNBR(*ZONED), and the FIX_DECIMAL_DATA value in the PROGRAM_INFO table was null. So I'm guessing that table won't help.
Bill Howie[Related image]<https://www.hc-companies.com/><https://www.hc-companies.com/>>
Senior ERP Programmer/Analyst
Office: 330.486.5818 | Cell: 330.486.5818 | Toll Free: 800.225.7712
2450 Edison Blvd., Suite 3, Twinsburg, OH 44087
hc-companies.com<http://hc-companies.com/><https://www.hc-companies.com/><https://www.hc-companies.com/>>
Leader in Horticultural Containers
[cid:5db495c3-9876-4661-9f92-33117f8acf3b] <https://www.linkedin.com/company/the-hc-companies><https://www.linkedin.com/company/the-hc-companies>> [cid:adce2550-b2c4-4113-852d-7bf412e71943] <https://www.facebook.com/HCCompanies/><https://www.facebook.com/HCCompanies/>> [cid:fb7b2da3-70d5-4994-b66f-8c911b075fe0] <https://www.instagram.com/hccompanies/><https://www.instagram.com/hccompanies/>> [cid:53882c7f-acbc-46a4-b5c2-d64942d315fe] <https://twitter.com/hc_companies><https://twitter.com/hc_companies>>
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email:
MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto: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%7C3985d46590064668800c08db8f9fb3e7%7C2ce547c5e
80a40628a56f25adceefb52%7C0%7C0%7C638261688311880540%7CUnknown%7CTWFpb
GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
%3D%7C3000%7C%7C%7C&sdata=Jyn1AHlO8q2lhZPDfMrX62jq%2BZGcYz9ZtgS%2BZk9p
V38%3D&reserved=0 or email:
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@lists.
midrange.com> Before posting, please take a moment to review the
archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto: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<mailto: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<mailto: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<mailto: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
