RE: Issues after going from TR4 to TR7 -- MIDRANGE-L

This is interesting - at 7.4 the ability to specify data type and size of literals - sounds like that is the "new" CALL. One might say, this should not have been broken on any release, right?

Cheers
Vern

On Mon, 31 Jul, 2023 at 4:13 PM, Dave Begley <Dave.Begley@xxxxxxxxxxxxxxx> wrote:

To: midrange systems technical discussion

Thank you

Dave Begley | IT Manager
HealthSmart | Benefits Management, LLC
Dave.begley@xxxxxxxxxxxxxxx<mailto:Dave.begley@xxxxxxxxxxxxxxx> | http://www.healthsmart.com/

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of Joe Wood
Sent: Monday, July 31, 2023 3:18 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx<mailto: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.

On 12/02/2022, we hit a similar situation on 7.4 - I don't know the TR levels at the time. From our closed case:

From IBM,
CL was compiled on a system with SI80445 The CL program was sent to another partition where we had SI69410 The PTF level does not support the newer CALL cmd

Recommendation is to install SI81413 on BOTH partitions, then compile, then test.

This solved our problem and was shocked that the situation existed, "Program error when passing 2+parms from CL program to RPGLE".

On Mon, Jul 31, 2023 at 6:12 AM Dave Begley <Dave.Begley@xxxxxxxxxxxxxxx<mailto:Dave.Begley@xxxxxxxxxxxxxxx>>
wrote:

This is just a cl program running in a batch process. It calls an RPG
program using 3 parameters. The parameters aren't making it to the
called program.

Apparently there new parameters to the call command which is causing
the problem.

Dave Begley | IT Manager
HealthSmart | Benefits Management, LLC Dave.begley@xxxxxxxxxxxxxxx<mailto:Dave.begley@xxxxxxxxxxxxxxx> |
http://www.h/
ealthsmart.com<http://ealthsmart.com>%2F&data=05%7C01%7Cdave.begley%40healthsmart.com<http://ealthsmart.com>%7C8a6b1
ec4990b4d1008dc08db91fae10a%7C2ce547c5e80a40628a56f25adceefb52%7C0%7C0
%7C638264278941498677%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ
IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=m24PU
MNH0NV7Y6JwnS%2FAHpKBTyTYmVwcgp24QhXfi3s%3D&reserved=0

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of
Mark Waterbury
Sent: Friday, July 28, 2023 5:13 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx<mailto: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.

Dave,

Passing parameters as literal values on a SBMJOB has the same issues
and problems as doing a CALL from a command line... it uses the CL
CALL command ... :-o

Just search the archives for problems with passing parameters and SBMJOB.

The "best simple" solution is to write a "command" definition wrapper
for this call.

Hope that helps,

Mark S. Waterbury

On Friday, July 28, 2023 at 05:03:33 PM EDT, Dave Begley <

dave.begley@xxxxxxxxxxxxxxx<mailto:dave.begley@xxxxxxxxxxxxxxx>> wrote:

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<mailto:Dave.begley@xxxxxxxxxxxxxxx> |
http://www.h/
ealthsmart.com<http://ealthsmart.com>%2F&data=05%7C01%7Cdave.begley%40healthsmart.com<http://ealthsmart.com>%7C8a6b1
ec4990b4d1008dc08db91fae10a%7C2ce547c5e80a40628a56f25adceefb52%7C0%7C0
%7C638264278941498677%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ
IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=m24PU
MNH0NV7Y6JwnS%2FAHpKBTyTYmVwcgp24QhXfi3s%3D&reserved=0

--
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<http://midrange.com>%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C01%7Cdave.b
egley%40healthsmart.com%7C8a6b1ec4990b4d1008dc08db91fae10a%7C2ce547c5e
80a40628a56f25adceefb52%7C0%7C0%7C638264278941498677%7CUnknown%7CTWFpb
GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
%3D%7C3000%7C%7C%7C&sdata=TC7jJ1xlEKbpS0FuuNW4BPtzhU8rqY9L3RRLIGj1li0%
3D&reserved=0 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 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<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To
subscribe, unsubscribe, or change list options,
visit:
https://list/
s.midrange.com<http://midrange.com>%2Fmailman%2Flistinfo%2Fmidrange-l&data=05%7C01%7Cdave.b
egley%40healthsmart.com%7C8a6b1ec4990b4d1008dc08db91fae10a%7C2ce547c5e
80a40628a56f25adceefb52%7C0%7C0%7C638264278941498677%7CUnknown%7CTWFpb
GZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
%3D%7C3000%7C%7C%7C&sdata=TC7jJ1xlEKbpS0FuuNW4BPtzhU8rqY9L3RRLIGj1li0%
3D&reserved=0 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.

--
----------------
Joe Wood
----------------

E: wood3875@xxxxxxxxx<mailto:wood3875@xxxxxxxxx>
M: 801-891-5223
L: http://www.linkedin.com/in/josephgwood
--
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 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.