• Subject: RE: QWVOLAGP API and CWBRXD window
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Tue, 18 Jan 2000 11:48:17 -0700

Richard,

I have always used them together.  You open a list and 
then use the list processing APIs to retrieve your records.  
If you specify a number of records that exceeds the number 
you expect to have returned, you could probably get away 
without using the retrieve list entry API, but that is not 
going to gain you very much.  Once you are done with a list 
you will want to call the close list API to end the server.

The QGY... retrieve list entry API just retrieves elements 
from a list that is being built.  The list is built in a 
separate process.  You use the status codes returned in the 
list header to determine how many list entries are available 
and whether the list is complete (or in error).  Once you are 
done, you close the list.

Like I said, I don't have any code specific to the activation 
group lists, but the general processing should be the same 
for any type of list. I don't have any code here at work that 
uses a list so I can't post that but here are some structures 
that define the common list fields and the close/retrieve 
record API calls.  Take a look at this and let me know if you 
have any more questions.  I will try to remember to forward 
an example of how these are used.

 **********************************
 * Close List of Objects API call *
 **********************************
DAPIQGYCLst       PR                  EXTPGM('QGY/QGYCLST')
D PR_LstHnd                      4A   CONST                                List 
handle.
D PR_APIErr                           LIKE(APIERR) OPTIONS(*VARSIZE)       
Error structure.
 *********************************
 * Open List of Objects API call *
 *********************************
DAPIQGYGtLE       PR                  EXTPGM('QGY/QGYGTLE')                Get 
list entry.
D PR_LstEnt                  32767A   OPTIONS(*VARSIZE)                    List 
entires.
D PR_LstEntSiz                  10I 0 CONST                                
Available size.
D PR_LstHnd                      4A   CONST                                List 
handle.
D PR_LstInf                     80A                                        List 
information.
D PR_RtnEntCnt                  10I 0 CONST                                
Return entry count.
D PR_StrRcd                     10I 0 CONST                                
Starting entry.
D PR_APIErr                           LIKE(APIERR) OPTIONS(*VARSIZE)       
Error structure.

DLstInf           DS
D LICnt                               LIKE(QGYTR)                          
Total Records.
D LIRtnCnt                            LIKE(QGYRRTN)                        
Records Retd.
D LIHnd                               LIKE(QGYRH)                          
Request Handle.
D LIRcdSiz                            LIKE(QGYRL)                          
Record Length.
D LICmp                               LIKE(QGYIC)                          Info 
Complete.
D LIDatTim                            LIKE(QGYDTC)                         Date 
Time.
D LISts                               LIKE(QGYLSI)                         List 
Status.
D Reserved01                          LIKE(QGYRSV1)                        
Reserved 1.
D LISiz                               LIKE(QGYRTNIL)                       Info 
Length.
D LIFstRcd                            LIKE(QGYFBR)                         
First Record.
D Reserved02                          LIKE(QGYRSV2)                        
Reserved 2.
 /COPY QSYSINC/QRPGLESRC,QGYGTLE

David Morris



>>> richard.hartman@brctsg.com 01/18/00 07:21AM >>>
The information that I have, says that the QWVOLAGP API generates a list of
all activation groups and their attributes for a specific job. It says the
APIs that start with QGY just retrieve more records. I am having a hard time
understanding, how they all work together. 
Does the list processing APIs (start with QGY) also return information about
the activation groups for a specific job?

Thanks in advance.
Richard

> -----Original Message-----
> From: David Morris [SMTP:dmorris@plumcreek.com] 
> Sent: Monday, January 17, 2000 6:23 PM
> To:   RPG400-L@midrange.com 
> Subject:      Re: QWVOLAGP API and CWBRXD window
> 
> Richard,
> 
> Are you having problems with the list processing or this 
> specific API?  I have not used this API, but I have used 
> the list processing APIs (the APIs that start with qgy...) 
> enough to help in that area. If this API is like the other 
> list APIs, it will build your list synchronously or 
> asynchronously depending on the number of records that you 
> specify in a separate server job.  
> 
> David Morris
> 
> >>> richard.hartman@brctsg.com 01/17/00 04:48PM >>>
> Hello,
> 
> Does anybody have any examples on using the QWVOLAGP API? I am using the
> information out of the IBM Red Books, but I can not seem to get the
> information from the API that I want. 
> I am trying to receive the activation group that I am currently in. 
> 
> Also, when I start my computer I have a minimized CWBRXD window. I know it
> has something to do with Client Access, and I do believe that it used to
> run
> behind the scenes of my computer.
> Is there anyway to get rid of that window on startup? 
> 
> Thanks in advance.
> Richard
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


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.