Re: CL Compile Question

I had a similar problem when on V7.3 and compiling to V7.1

my problem revolved around command parameter changes that happened during the lifetime of the version. For instance CPYSPLF changed mid-v7.1 to include the copying a spooled file to a PDF.


It was fixed with APAR for 7.3:

SE69002 - OSP-UNPRED TARGET RELEASE OF N-2 DOES NOT CONTAIN CHANGES FOR N-1

Problem Conclusion

Bug found in the CL compiler PREV search logical does not match.
The n-1 library should also be searched when target release is
n-2 library.

As I understood it this bug existed for a long time.

the V7.3 PTF is SI67446 I do not know if one was created for V7.2 although I do not think it should be too hard.



Bryan


Rich Loeber wrote on 10/25/2018 11:29 AM:

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/