×

Good News Everybody!

The new search engine is LIVE!

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




Entries (and the corresponding parameter on the prototype) should be defined as "10i 0".


Buddy McClean wrote:
Running the program below - I get CPF1666 Number of Entries not in Valid Range (Field name 'ENTRIES')

Am I defining the parameters correctly for QWTSETPX to read them?

I don't think the external program is getting the value.

As a side (or maybe not) - how does QWTSETPX know which error DS I am expecting back ERRC0100 or ERRC0200

H DftActGrp(*no) BNDDIR('DFTBNDDIR') 10/30/08
200 H Debug Optimize(*none) 10/28/08
300 H*Debug(*No) Optimize(*Basic) 10/28/08
400 H InDent('>') Text(*SrcMbrTxt) 10/27/08
500 10/27/08
600 D Entries S 4B 0 Inz(1) 10/30/08
700 D Flag S 1 0 Inz(1) 10/30/08
800 D Format S 8 Inz('SREQ0100') 10/30/08
900 D User S 10 Inz('MBNETUSER') 10/30/08
1000 D Error S Like(QUSEC) 10/30/08
1100 10/27/08
1200 D SetUser PR ExtPgm('QWTSETPX') 10/30/08
1300 D 4B 0 10/30/08
1400 D 1 0 10/30/08
1500 D 8 10/30/08
1600 D 10 10/30/08
1700 D 16 10/30/08
1800 10/30/08
1900 DQUSEC DS 10/28/08
2000 D* Qus EC 10/28/08
2100 D QUSBPRV 1 4B 0 10/28/08
2200 D* Bytes Provided 10/28/08
2300 D QUSBAVL 5 8B 0 10/28/08
2400 D* Bytes Available 10/28/08
2500 D QUSEI 9 15 10/28/08
2600 D* Exception Id 10/28/08
2700 D QUSERVED 16 16 10/28/08
2800 D* Reserved 10/28/08
2900 D*QUSED01 17 116 10/30/08
3000 10/27/08
3100 C Clear QUSec 10/30/08
3200 C Eval QUSBPRV = 16 10/30/08
3300 C CallP SetUser (Entries: 10/30/08
3400 C Flag: 10/30/08
3500 C Format: 10/30/08
3600 C User: 10/30/08
3700 C QUSEC) 10/30/08
3800 10/30/08
3900 C Eval *INLR = *On 10/27/08
* * * * E N D O F S O U R C E * * * *



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.