×
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.
Dave,
What's going on in that msgfd subroutine? You haven't listed the code for that routine. Is it mucking with the subfile record lock required for the update?
Paul Morgan
Principal Programmer Analyst
IS Supply Chain/Replenishment
508-253-3934
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Dave Petrosky
Sent: Friday, July 09, 2010 12:41 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: RE: RPG400-L Digest, Vol 9, Issue 514
Rob and Alan,
The code dies on the first interation of the loop. I have run it through
debug a number of times, dumped the program to check the variables and
indicators, and I am at a major loss. I have used this template for many
subfiles and I don't have this problem with any of them. I compared code
and can't find any differences. The only variable is that we are on a
new machine since the last subfile I created and maybe there is some
setting that is *off, but that seems to be just looking for a reason
where none exists. All other subfiles run fine.
Dave
// Place the error message into the message subfile.
// If needed.
msgfd(w@msid : w@msgf : w@msda : w@mstp :
iStack: ErrorDs);
//
// Update the record in the subfile.
update MCSTS1; <------------Blows up here
midrange.com
