×

Good News Everybody!

The new search engine is LIVE!

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




We're on v7r1, not sure where we are on the RPG compiler PTFs. We have
TR11 installed, and our cume level is at 16320. (Rob, I know, I know.)

I did find this in the archives:
https://archive.midrange.com/rpg400-l/201702/msg00139.html
but there was no followup to whether there was a PMR submitted or a PTF
issued.

The source below will not pass the SQL preprocessor, which issues SQL0312
for SV_OWNID, SV_ORGID, and SV_SUBORG. This source is culled from
2000-line program to where I could determine where the SQL precompiler was
puking. So, yes, the COMPARE and SAVE data structure are required.

BUT NOTE: If I comment out the COMPARE data structure and its 3 subfields,
it will compile with no errors. (The S1_* fields are defined in the
STATMNT100 file.)

If anyone knows that there was a PTF in v7r1 for this bug, please let me
know. Also, how would someone search IBM's website to see if there's a PTF
for this? FWIW, I have an IBM ID, but I don't have an IBM customer number
I can use.

- Dan

FSTATMNT100IF E K DISK

d NegotiatedCount...
d s 9 0

DCOMPARE DS
D S1_CUSID
D S1_CMPID
D S1_DIVISN
DSAVE DS
D SV_CUSID LIKE(S1_CUSID)
D SV_CMPID LIKE(S1_CMPID)
D SV_DIVISN LIKE(S1_DIVISN)

sv_CUSID = 932014;
sv_CMPID = 'GRPL';
sv_DIVISN = 'VOT';

Exec SQL set :NegotiatedCount =
( select count(*) as aCount
from statmnt1, charges
where s1_CUSID = :sv_CUSID
and s1_CMPID = :sv_CMPID
and s1_DIVISN = :sv_DIVISN
and s1_CusID = su_CusID
and s1_CrgID = su_CrgID
and su_ID1 like '%N %');
*inLR = *on;

Begsr *inzsr;
Read STATMNT100 ;
Endsr;

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.