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



Actually, would the definitions also work if you did this, which is both simpler and clearer?

d mstrDS e ds extname(hclmmas)
d savmstr s like(mstrDS)
d newmstr s like(mstrDS)




Booth Martin wrote:
You'll have trouble I believe if you don't have another data structure. (least ways, I always have. :) )

d savmstr e ds extname(hclmmas) prefix(o)
d newmstr e ds extname(hclmmas) prefix(n)
d mstrDS e ds extname(hclmmas)
then I brought in the data:

chain(n) (cmyrin: cmycin) clmmas; // get data for pg
savmstr = mstrDS; .... go to lunch, whatever
.... do stuff to change proposed record values
newmstr = mstrDS / save new values
chain cmyrin: cmycin) clmmas; // get data for pgm
if savmstr <> mstrds // then changed at another workstation
.... tell user changes made, etc.
else
eval mstrDS = newmstrds
update CMYRIN
endif

Gene Burns wrote:
Thanks, Booth!

I setup 2 data structures to start with:

d savmstr e ds extname(hclmmas) prefix(o)

d mstrDS ds likerec(clmmas)

then I brought in the data:

chain (cmyrin: cmycin) clmmas; // get data for pgm
// ekb13 begin block
chain(n) (cmyrin: cmycin) clmmas mstrDS; // load DS
unlock hclmmas; // release lock
savmstr = mstrDS;
// ekb13 end block

So now I have the data saved in a data structure, still have the fields
available (no rewrite), and no lock on the file.

Thanks everyone!


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