David At 08:43 AM 1/19/98 -0700, you wrote: >Mark, > >When a CLLE program calls an RPG program you can get a machine check >MCH3601 on the end procedure statement. This happens most of the time >when you specify a return variable that is short. The work around is to declare >the variable with a longer length and substring out the first part. It is not very >consistent. Programs may run for months. One day change the program, >without touching the parms, next day it starts getting MCH3601. It happens more >than 50% of the time with 1 byte return variable, say for instance an error flag. DO you have specifics as to how short is considered short? Also, how much longer will fix it? >We were really surprised when the response from support was that it was >no longer a bug. The APAR was closed and they changed the status to a >"restriction with a work around". Apparently not enough people use CLLE >to make it worth while to fix. They gave us no commitment that it will be fixed >in any future release. We are currently on V3R7. This is the type of bug that the code does "not work as advertised." I'm guessing that it will be fixed soon w/o a lot of fanfare (maybe shortly after the next COMMON.) -mark +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.