The ESP started task in our shop was recycled back in Sep'2017 without a JESLOG=(SPIN,'08:00') parameter since then the JESMSGLG and JESYSMSG have started accumulated and we have a total of 4 Million lines combining JESMSGLG & JESYSMSG.
We are kind on concerned that the SP started task might abend someday due to the space issue. Just wanted to know if there is any hard limitation such as the Start task will abend when there is more than 8 Millions of line accumilated.
Anyways we would restart the start task with JESLOG=(SPIN,'08:00') later this month. But as mentioned above want to know the hard limitation and what are the possible issue/consequences if we continue to run with these log untill it abends.
DDNAME StepName ProcStep DsID Owner C Dest Rec-Cnt Page
JESJCLIN 1 CONTROL Z 2
JESMSGLG JES2 2 CONTROL Z 3M
JESJCL JES2 3 CONTROL Z 53
JESYSMSG JES2 4 CONTROL Z 1M
$INTTEXT JES2 5 CONTROL A 14
EVENTLOG JES2 8 CONTROL A 0
CPEENQLG ESP 103 CONTROL M 45,500
SYS52348 ESP 224 CONTROL M 199,169
Thanks in advance.
ESP doesn't code a limit on its outputs. You may check with your ZOS system admin on the JES setting for ESP STC and/or its job class for possible consequence.
I did google and found following information from IBM website:
IBM Knowledge Center
Hope this helps,
Thanks for the details, our system programming notified we have a default value OUTLIM(5000000). We had recycled the ESP started task with JESLOG=(SPIN,'08:00') on 14th Jan 2018. Now the accumulated JESMSGLG & JESYSMSG logs have been cleared off.
I spin my JESLOG with my ESP log twice a day. I find it nice to have both with the same time periods.
JOB SPINLOG.0559 LINK PROCESS /* ESP SPINLOG TO $AVRS RUN DAILY DELAYSUB 05:59 ESPNOMSG OPER SPINLOG VS '$TS(ESP),SPIN' RELEASE SPINLOG.1759 ENDJOB JOB SPINLOG.1759 LINK PROCESS /* ESP SPINLOG TO $AVRS RUN DAILY DELAYSUB 17:59 ESPNOMSG OPER SPINLOG VS '$TS(ESP),SPIN' ENDJOB