× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Rich--

Were you using the TGTRLS(V6R1M0) parameter when compiling on the 7.2 box?

And for all of your experts-- does TGTRLS use the commands (and the compiler) in the QSYSV6R1M0 library (or the one appropriate for the TGTRLS) for the compile??

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Alan Shore
Sent: Thursday, October 25, 2018 11:36 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: [EXTERNAL] CL Compile Question

Hi Rich
Was the command on the 6.1 system, changed to add the new parameter?
In other words - that parameter is NOT part of the IBM supplied command in 6.1

I have known some shops make changes directly to the IBM supplied command and these changes are part of some program somewhere
When a new version of the operating system is applied to that system, THAT file is sued to update the latest version of the commands - but obviously not any of the prior versions

If what I have said is true - then the 7.1 version will also NOT contain this parameter


Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Thursday, October 25, 2018 11:29 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: [EXTERNAL] CL Compile Question

I have two systems here, one running 6.1 to support customers who are back
level quite a ways and another running 7.2. I was compiling a CL program
back to 6.1 today and it failed on an invalid parameter on the RUNSQLSTM
command. When I compile it to 7.2, no problem. When I compile it on the
6.1 machine, no problem too. It just doesn't like compiling on the 7.2
system going back to 6.1.

I found the offending *CMD object in the QSYSV6R1M0 library and the
parameter that I'm using is not there on the 7.2 system. So, I copied the
command from QSYS on the 6.1 system over to the QSYSV6R1M0 library on the
7.2 system. After doing this, the compile on 7.2 going back to 6.1 works
fine.

The question is, am I going to get myself into any trouble by doing this?

Rich Loeber - @richloeber
Kisco Information Systems
[1]http://www.kisco.com

--------------------------------------------------------------------------

References

Visible links
1. http://www.kisco.com/
--


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.