CLP v7.3 versus v7.4 -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: CLP v7.3 versus v7.4
From: Kirk Yates <kirk.yates@xxxxxxx>
Date: Tue, 1 Apr 2025 16:02:56 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>
Z-usanet-msgid: XID913dDaVc67632X32

Strange Issue, system running v7r4

Version of program in Production that works was compiled with V7R3M0 compiler.
Statement in CLP in question:
Source code shows:
/*LWW01*/ CALL PGM(BRNCHSEC) PARM('1' 'INVMAS' ' ' ' ' ' ' &OVRFIL)
RTVCLSRC shows:
CALL PGM(BRNCHSEC) PARM('1' 'INVMAS' ' ' ' ' ' ' &OVRFIL)

Recompiled program with V7R4M0 compiler:
Source code shows:
/*LWW01*/ CALL PGM(BRNCHSEC) PARM('1' 'INVMAS' ' ' ' ' ' ' &OVRFIL)
RTVCLSRC shows:
CALL PGM(BRNCHSEC) PARM(('1') ('INVMAS') (' ') (' ') (' ') -
(&OVRFIL))

Program compiled with V7R4M0 compiler does not work. Variable &OVRFIL is returning as blank.

&OVRFILE is defined as DCL VAR(OVRFIL) TYPE(*CHAR) LEN(10)

Any ideas?

Thank you.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: CLP v7.3 versus v7.4 , Jim Franz
Re: CLP v7.3 versus v7.4 , Rob Berendt

This mailing list archive is Copyright 1997-2026 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.