MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

RE: Retrieving object text of locked data area



fixed

We are on 6.1. This doesn't work for 6.1 (returns null). I've run some
tests on a 7.1 machine and IBM has apparently changed the rules between 6.1
and 7.1 because the API and other stuff all work on 7.1.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Essinger
Sent: Wednesday, July 16, 2014 10:55 AM
To: Midrange Systems Technical Discussion
Subject: Re: Retrieving object text of locked data area

John,

What version of IBM i/OS are you on? Can you try an SQL command?

This should work at v7.1. 1st Parm is library, second is object type.

Select x.*
From table(QSYS2.OBJECT_STATISTICS('QSYS', 'DTAARA')) as x

Jim Essinger
Western Power Sports
Boise ID


On Wed, Jul 16, 2014 at 8:44 AM, John R. Smith, Jr. <smith5646@xxxxxxxxx>
wrote:

We do not have access to the programs doing the lock so changing to
*EXCLRD is not an option.

WRKOBJ displays the text of a *EXCL locked object so how it is
retrieving it?

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Charles Wilt
Sent: Wednesday, July 16, 2014 10:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: Retrieving object text of locked data area

*EXCL is exclusive, no read...

Nothing else can touch it.

Have the locking process changed to use *EXCLRD which is exclusive,
allow read.

http://www-01.ibm.com/support/docview.wss?uid=nas8N1016811

Charles



On Wed, Jul 16, 2014 at 10:04 AM, John R. Smith, Jr.
<smith5646@xxxxxxxxx>
wrote:

I am writing a program to retrieve the object text of a group of
dataareas for display on a screen. I am having an issue where I get
blanks for the text for a dataarea when another job has it locked
*EXCL. I have tried DSPOBJD and RTVOBJD from CL. I have tried the
APIs
QUSLOBJ and QUSROBJ.
Is
there another API that I am missing or some other way of getting
this information. We are currently at V6R1.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please
take a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact