On Wed04-Apr-2011 11:03 , fbocch2595@xxxxxxx wrote:
We do daily reporting on QAUDJRN for about 20 entry types, did
anyone have any issues with journal reporting after the upgrade?
  Some clarification might be worthwhile to offer, in the hope that 
someone might recognize having experienced a similar concern; seems a 
bit nebulous without.  Was the reporting via "canned reports" from the 
GO SECTOOLS menu or perhaps something about the DSPAUJRNE, CPYAUDJRNE, 
or DSPJRN QAUDJRN itself that was suspect?  And about whatever the 
utilized interface, was there some missing data or some other incorrect 
output that was a concern; something specific that can be described?  Or 
perhaps everything was verified to be correct for QAUDJRN, but just not 
so [correct] via some another interface, such that some specific 
differences are obvious and capable of being described?
  There is a PTF for instance that references specifically the 
CPYAUDJRNE for IncorrOut [Incorrect Output] which is on the C1102610 
according to the IBM i 6.1 PSP; APAR SE41683:
SI38487  1102  03/02/10 OSP-OTHER-INCORROUT THE CPYAUDJRNE COMMAND 
GENERATES INCORRE
http://www-912.ibm.com/a_dir/as4ptf.NSF/b3cb9d42f672b70f86256739004afa0f/90f4498171f7de66862576db00528056?OpenDocument
  Also FWiW: Consider that DSPAUDJRNE is deprecated per "The Display 
Audit Journal Entries (DSPAUDJRNE) command will have no further 
enhancements. We recommend you that you use a combination of the Copy 
Audit Journal Entries (CPYAUDJRN) <sic?> command followed by the Run 
Query (RUNQRY) command. This combination provides function that is 
similar to DSPAUDJRNE." from:
http://www.redbooks.ibm.com/redbooks/pdfs/sg247680.pdf
Regards, Chuck
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.