Easy enough to google for more information but here's the 50,000 foot overview:
The enhanced reporting command produces a report for a selectable 24-hour period. The report is
output in two optional files. The first file is the raw data extracted from the OnDemand System Log
and formatted as XML. The second file is a summary derived from the raw data. The report covers
three sets of operations of the system, logins, loads, and query/retrieves.
// JOB REGION=0M
//STEP1 EXEC PGM=BPXBATCH
//STDPARM DD *
SH /usr/lpp/ars/V9R0M0/bin/arsrpt -h ARCH900
-c "IBM-037" -t 2015-09-17
-u odv733 -p /u/odv733/edstash
-d /tmp
//STEPLIB DD DISP=SHR,DSN=ARS.ARSV900.SARSLOAD
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDOUT DD SYSOUT=* Note: you can't use V9 libraries to access V8.5 logs --- or at least I can't.
This is the error I see in the JESMSGLG in ARSSOCKD for V8.5 when my JCL points to V9.0:
ARS0013E ODV793 DB Error: {DB2 FOR OS/390}{ODBC DRIVER}{DSN11015}
DSNT408I SQLCODE = -206, ERROR: ODDAT_TIME_STAMP IS NOT VALID IN THE
CONTEXT WHERE IT IS USED
DSNT418I SQLSTATE = 42703 SQLSTATE RETURN
CODE DSNT415I SQLERRP = DSNXORSO
SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD
= -100 0 0 -1 0 0 SQL DIAGNOSTIC INFORMATION DSNT416I
SQLERRD = X'FFFFFF9C' X'00000000' X'00000000' X'FFFFFFFF'
X'00000000' X'00000000' SQL DIAGNOSTIC INFORMATION
ERRLOC=5:10:1 -- SQLSTATE=42S22, SQLCODE=-206, File=
arsdoc.c, Line=2529 Ed
