Re: audit report -- RPG400-L

Yes, that's what I'm using.  The Declare Cursor, then Fetch next 10 records
into a MODS.

On further testing, my problem seems to be with the null indicator data
structure.  Apparently, some of those fields in QADBIFLD are not only null
capable, but actually contain nulls.  When I changed the MODS to bring in
all fields (by externally defining it against the QADBIFLD) instead of just
a few fields, I starting getting an error saying it REQUIRED an indicator
data structure for the nulls.

Unfortunately, I haven't yet been able to get the precompiler to accept any
form of indicator data structure I have tried to feed it.  According to the
manual it is supposed to just be a data structure of 4B 0 fields with one
for every field in the target file.  Also, the number of occurrances has to
match the externally defined MODS.  I just love that precompiler.

-----Original Message-----
From: Rob Berendt <rob@dekko.com>
To: RPG400-L@midrange.com <RPG400-L@midrange.com>
Date: Thursday, July 15, 1999 11:10 AM
Subject: Re: audit report


>Believe it or not, I've never worked with MODS.  My SQL example
>was from an interactive session.  May I recommend using a CURSOR
>and a FETCH?
>
>
>
>
>
>ncsmith@gate.net on 07/14/99 10:53:49 PM
>Please respond to RPG400-L@midrange.com@Internet
>To: RPG400-L@midrange.com@Internet
>cc:
>Fax to:
>Subject: Re: audit report
>
>Oops, I must have hit send too soon.  I wanted to ask you about the code
>example you were showing because I'm having trouble with almost the
>identical thing.
>
>I'm using the open cursor, fetch next method to try to bring some of the
>fields in that same QADBIFLD file to a multiple occurrance data structure.
>I'm requesting some number of records at a time, say 10, into a MODS with
>plenty of occurrances to hold that number and everytime the fields in the
>SQLCA say that it is returning only 1 record, but with no errors or
messages
>of any kind (except the normal completion message saying 1 record was
>returned), but when I look in the MODS, it actually loaded and returned 2
>records.
>
>With no error indications at all, I'm kind of at a loss as to why it is not
>returning the 10 records I requested.  I've had no problem at all doing the
>same thing with my own files.  Is there something different I need to take
>into account when using the QADB files?
>
>-----Original Message-----
>From: Rob Berendt <rob@dekko.com>
>To: RPG400-L@midrange.com <RPG400-L@midrange.com>
>Date: Wednesday, July 14, 1999 9:43 AM
>Subject: Re: audit report
>
>
>>I don't see your reply.
>>
>>
>>
>>
>>ncsmith@gate.net on 07/13/99 09:00:41 PM
>>Please respond to RPG400-L@midrange.com@Internet
>>To: RPG400-L@midrange.com@Internet
>>cc:
>>Fax to:
>>Subject: Re: audit report
>>
>>
>>-----Original Message-----
>>From: Rob Berendt <rob@dekko.com>
>>To: RPG400-L@midrange.com <RPG400-L@midrange.com>
>>Date: Tuesday, July 13, 1999 3:41 PM
>>Subject: Re: audit report
>>
>>
>>
>>>QADBIFLD might be the one you want.
>>>
>>>For example:
>>>SELECT DBIFLD, DBIITP, DBITYP, DBITXT FROM qadbifld WHERE
>>>DBILIB='GPIDIVF' and DBIFIL='IIM'
>>>FIELD       INTERNAL  FIELD     FIELD
>>>NAME        TYPE      TYPE      TEXT
>>>IID            A      CHAR      Record ID; IM/IZ
>>>IPROD          A      CHAR      Item Number
>>>IDESC          A      CHAR      Item Description
>>>IADJ           P      DECIMAL   Month to Date Adjustments
>>>IRCT           P      DECIMAL   Month to Date Receipts
>>>IISS           P      DECIMAL   Month to Date Issues
>>>...
>>>
>>>
>>>
>>>Want to change a field?  Try:
>>>select DBILIB, DBIFIL from QADBIFLD where DBIFLD = 'MANAGR'
>>>LIBRARY     FILE
>>>NAME        NAME
>>>ACCTINTRFC  FREF
>>>ACTATJO     FREF
>>>ACTINTF     FREF
>>>ACTINTO     FREF
>>>ACTINT40    ACTINTCDO
>>>ACTINT40    FREF
>>>ACTINT404   FREF
>>>DPDLUCF30   FREF
>>>MGRTEST002  EMPJOB
>>>ELPFILE     FREF
>>>MGRTEST099  EMPFLUFF
>>>...
>>>
>>
>>
>>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

>>* This is the RPG/400 Discussion Mailing List!  To submit a new         *
>>* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
>>* from this list send email to MAJORDOMO@midrange.com and specify       *
>>* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
>>* be directed to the list owner / operator: david@midrange.com          *
>>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>>
>
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>* This is the RPG/400 Discussion Mailing List!  To submit a new         *
>* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
>* from this list send email to MAJORDOMO@midrange.com and specify       *
>* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
>* be directed to the list owner / operator: david@midrange.com          *
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
>
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>* This is the RPG/400 Discussion Mailing List!  To submit a new         *
>* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
>* from this list send email to MAJORDOMO@midrange.com and specify       *
>* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
>* be directed to the list owner / operator: david@midrange.com          *
>* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *