Re: Program QWTPITPP

[eric.delong@xxxxxxxxxxxxxxxxx]

     Do you use a trigger program?
     
     eric.delong@pmsi-services.com


______________________________ Reply Separator _________________________________
Subject: Program QWTPITPP 
Author:  <MIDRANGE-L@midrange.com > at INET_WACO
Date:    2/16/99 11:55 AM


I have process that needs to generate EDI transactions for all of a
customer's
items that change. Since I do a series of customers, I was leaving LR off in
my RPG/ILE program.

     My CLLE pgm (AG=QILE) reads a file containing all customers to check
          It calls a RPG/ILE pgm (AG=QILE) passing a customer #
               All items for the customer are checked
               Return without LR on

I am using journalling to verify that my program is running properly. I
noticed that
the last 17 transactions written had a program name of QWTPITPP. An output
only file in RPG will default to blocking, so that the actual movement to
disk is
done for every "n" records. I am assuming that these 17 records were still
in the
buffer when the job ends and the AG is destroyed. They would then be forced
to
disk at that time. Assuming that all this is true, why would the program be
QWTPITPP and not the actual RPG that created the records? Anybody have
any insight on this? The journal entry is misleading and hides the real
activity.

Joe Teff

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---



+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---