|
<lmejia@...> writes:
One more thing, before the new cycle I do this: JvR03DtaDte = %TimeStamp; JvR03DtaDte = JvR03DtaDte + %MSECONDS(1);
Thanks for the suggestion but I don't think this is the problem. I have been having another look at the manual and it looks like I have to pass in a starting sequence on the second and any subsequent calls to the API otherwise it just starts at the beginning again which is what is causing my problem. The code I used as a template for this program is getting the sequence number but I am not passing the details for key 2 (starting sequence) to the API. The manual says: "If the receiver variable was not large enough to hold the retrieved journal entries, the API can be called again, specifying the same selection criteria and specifying a starting sequence number one greater than the last sequence number returned." This is all well and good but I can't specify a starting sequence AND the same selection criteria because I get a CPD7061 message telling me that a start time and a starting sequence number cannot both be used. Looks like I will have to code a separate API call for the second and subsequent calls. Martin
Saludos, Leonel Mejía Chinchilla Administrador de Seguridad de Sistemas Gerencia de Tecnología y Operaciones Regionales BAC | Credomatic Network
As an Amazon Associate we earn from qualifying purchases.
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.