× 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.




Running out of ideas here.

Under V3R1, an RPGLE program is getting an MCH3601 error at statement 41
of procedure _QRNX_DB_READ of QRNXDBIO.

The program reads transaction FILEA and determines if FILEB needs to be
updated.  
        If FILEB is not updated, the next READ to FILEA has no problem.
        If FILEB is updated, the next READ to FILEA has the run-time
error above followed by a CPI93CA.

The program is created from a single module with the default activation
group (also tried it with ACTGRP(*NEW).
FILEA and FILEB are single member physical files with no overrides.
The READ statement had both EOF and ERR indicators (removed the ERR
indicator, same error)
When coded in RPG/400 there are no errors.
I checked the technical database and APAR SA71024 is the closest match I
found, but there are no overlays in the code.

Has anyone else ever seen this? 
Have any ideas on what might be a cause?

John Compton <john.compton@heiligmeyers.com>
IBM Certified Specialist - RPG
The opinions expressed by me are not necessarily those of my employer.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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-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.