message subfile
-
- Profound User
- Posts: 24
- Joined: Wed Mar 21, 2012 3:02 pm
- First Name: Mark
- Last Name: Suhr
- Company Name: Wellington Ins Group
- Phone: 817-732-2111
- Address 1: 6801 Calmont Ave
- City: Ft. Worth
- State / Province: Texas
- Zip / Postal Code: 76116
- Country: United States
- Contact:
message subfile
I have created a RDF with a message subfile and am getting a I/O error of MCH3601 when trying to write to the subfile. Attached is the code for the RDF, the rpg program, the cl program that sends the message and the various error. What am I doing wrong.
- Attachments
-
- 951570_000003_QPMHAMI_03232015_000001.PDF
- (51.26 KiB) Downloaded 54 times
-
- 951570_000002_QPMHAMI_03232015_000001.PDF
- (51.57 KiB) Downloaded 53 times
-
- 951570_000001_QPMHAMI_03232015_000001.PDF
- (51.31 KiB) Downloaded 69 times
-
- Experienced User
- Posts: 2711
- Joined: Wed Aug 01, 2012 8:58 am
- First Name: Scott
- Last Name: Klement
- Company Name: Profound Logic
- City: Milwaukee
- State / Province: Wisconsin
Re: message subfile
The most common cause for an MCH3601 is a parameter problem. For example, if you define a parameter, but then call the program/procedure without passing the parameter, you can get an MCH3601.
-
- Profound User
- Posts: 24
- Joined: Wed Mar 21, 2012 3:02 pm
- First Name: Mark
- Last Name: Suhr
- Company Name: Wellington Ins Group
- Phone: 817-732-2111
- Address 1: 6801 Calmont Ave
- City: Ft. Worth
- State / Province: Texas
- Zip / Postal Code: 76116
- Country: United States
- Contact:
Re: message subfile
Scott, not sure if the RDF and RPG source code files posted but will try again. No parms when calling the RPG, the MCH error happens when I try to write to the message subfile.
-
- Experienced User
- Posts: 2711
- Joined: Wed Aug 01, 2012 8:58 am
- First Name: Scott
- Last Name: Klement
- Company Name: Profound Logic
- City: Milwaukee
- State / Province: Wisconsin
Re: message subfile
The problem here was a case-sensitivity issue between your bound fields (pgm_que and msg_key) and the DDS record format (which has the smae fields in uppercase, PGM_QUE and MSG_KEY). You can work around the problem by re-typing these fields in uppercase... just re-open the binding dialog in the visual designer and type the field names in all uppercase, and it should work again.
This is a bug in Profound UI -- I have changed it on my development box so that it is not case-sensitive like this. This update will be included in future versions of Profound UI. If you'd like a patch to fix your version 5.0.8 copy of the OA Handler, please contact support@profoundlogic.com and ask for a patch for issue 1441.
This is a bug in Profound UI -- I have changed it on my development box so that it is not case-sensitive like this. This update will be included in future versions of Profound UI. If you'd like a patch to fix your version 5.0.8 copy of the OA Handler, please contact support@profoundlogic.com and ask for a patch for issue 1441.
Who is online
Users browsing this forum: No registered users and 0 guests