Hi,

My first idea would have been:
1. In batch, is the library list correct, i.e. is your library added to the
library list.
2. Are there several occurances of the file F78P00 in differenct libraries. 
   May be your batch programm is working with the file located in an other
library than yours. 
   And you always check the wrong file, i.e. your file was empty, so it
seems that CLRPFM worked 
   while writing to this file did not work, because the records were written
in an other file.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them?  Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----.
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Tomasz Skor¿a
Gesendet: Thursday, February 22, 2007 23:33
An: midrange-l@xxxxxxxxxxxx
Betreff: Why not update in batch - part four - last


Hi

"Temporary" means NOT in production library (but also NOT in QTEMP). File
F78P00 is located in my library. I checked file by RUNQRY. I tried the same
function/logic in RPG, RPGLE and SQLRPGLE - always work in interact - not
work in batch (where "not work" mean that file F78P00 was clear as first
step, but second step - adding record - not work/occured) I checked library
list - correct. Finally I created query in Query Manager and than CL with
call STRQMQRY - it works both interactively and in batch/in job schedule.
But why? I haven't idea .... Thanks for all answers.

Regards

Tomasz


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.