Thanks Mr. Pence.
Your feedback is appreciated. It gives me clarity where I had some
confusion. I will be able to complete my coding. Thanks again.
Have a good day
Jorge Moreno
From: CRPence <CRPbottle@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 05/03/2013 04:57 PM
Subject: Re: Retrieve Job Record Locks (QDBRJBRL) API with Optional
parameter Group
Sent by: midrange-l-bounces@xxxxxxxxxxxx
On 03 May 2013 13:10, jmoreno@xxxxxxxxxxxxxxxx wrote:
Looking to resolve the Job record locks and at the same time build
the list of jobs holding the different locks against the identified
records from the different database files
At V7R1 the format JIDF0200 in the Optional Parameter Group is
suppose to give me that information but I have not been able to
get it working.
The above comment seems to imply an expectation that the named format
is used for returned information; i.e. per "supposed to give me that
information".? However that parameter is "Input" to the API, used to
ask for the locks held by the specific thread identified using that
format. That optional parameter simply identifies the layout\format of
the input for the required Parm-4, *if* the defaulted choice of the
format name JIDI0100 is assumed due to a lack of Parm-6.
Optional Parameter Group:
6 : Format of job or thread identification information : Input : Char(8)
I saw this posting from the archives.
http://code.midrange.com/f721093a5d.html
but it does not use the Optional parameter Group)
That code would be identical in effect, if it had added\coded a
Parm-6, and passed the value 'JIDI0100' as the Char(8) Input. That is,
Parm-6 simply identifies what Parm-4 should look like, as /input/ to the
API invocation.
If all that is already understood.... then perhaps the intended
question is about how one finds the thread handle that according to the
docs "is returned on several other interfaces"; i.e. what interfaces
return the thread handle? If so, then there is the Retrieve Thread
Attribute (QWTRTVTA) API, for example.
midrange.com
