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



Are you saying it automatically reads (IN opcode), applying a lock? That
doesn't sound right.....  D spec and C spec should produce the same results.
Aside from the definition, the use remains the same, via the IN, OUT, and
UNLOCK opcodes.  Perhaps an unlock after your code that reads (and updates)
the dataarea, though if it was working before, it should be working now.
Are you sure something else wasn't lost when you removed the DEFINE
statement?

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Malchow, Grizzly [mailto:GMalchow@xxxxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, April 01, 2003 8:07 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Data area question


Is it better to define a data area with the *DTAARA    DEFINE, or is
better do it in the D specs? Or is it just a matter of preference? I've
noticed that when it is done in the D specs, the program accesses it
with out the IN op code. We're getting errors because a data area is
locked when other programs go to access the data area. 

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.