ATYLOGR - doesn't specify how many deleted when DELETE REQUESTED - should provide statistics when job completed
I ran the ATYLOGR with the following: // 'DELETE TO 2023-06-23,18:24:45.016108')
Why doesn't the report report on how many records were deleted? Logstream name=TSI.QLIK.G2W2DATA Maxlen=1024 To-date-time =2023-06-23,18:24:45.016108 DELETE RANGE function has been specified ATYLOGR is ending successfully
Not providing us a count is of little value. This now forces your customers to print the records - delete records - and then reprint to determine how many were deleted?
the ATYLOGR PRINT function with from/to range does not limit to the range selected.
As a customer we should not have to PRINT records - DELETE records - PRINT records to confirm how many were deleted. This is unacceptable from a customer perspective.
From a CUSTOMER perspective we'd like to see:
Logstream name=TSI.QLIK.G2W2DATA Maxlen=1024 To-date-time =2023-06-23,18:24:45.016108 DELETE RANGE function has been specified
NUMBER OF RECORDS DELETED == xxxxx ATYLOGR is ending successfully
You are right, the behavior can be reproduced in our labs. We also noticed the support ticket (00096393). Before we get a fix, maybe change the function code from MAXLEN 1024 to MAXLEN 1 in PRINT JCL could mitigate the JES SPOOL full up.
I modified to MAX-LEN=1 but still had to cancel the job for JES SYSPRINT LOGR 102 TDLM A LOCAL 106M 09.30.13 JOB43234 $HASP375 TDLMLGW3 ESTIMATE EXCEEDED BY 104,500,000 LINES 2 % SPOOL 09.30.15 JOB43234 IEF450I TDLMLGW3 LOGR - ABEND=S222 U0000 REASON=00000000 188 188 TIME=09.30.15
