On Tue, Jun 13, 2017 at 12:41 PM, Jesse 1 Robinson <[email protected]>
wrote:
> I don't want to turn this into a debugging session. We plan to open an SR
> with IBM. Just to verify what I've said, here are some lines from the job
> log. The first step is vanilla CA11. That's where the job dies. We
> completely removed the CA11 step; same result. I was just looking for any
> 'me too' responses.
>
> ---- TUESDAY, 13 JUN 2017 ----
> ICH70001I UCC7 LAST ACCESS AT 03:39:19 ON TUESDAY, JUNE 13, 2017
> $HASP375 TEDD071 ESTIMATED LINES EXCEEDED
> $HASP373 TEDD071 STARTED - INIT 17 - CLASS K - SYS D0
> SCEUJI02I JOB TEDD071 STARTED 03.39.19 13 JUN 17
> IEF403I TEDD071 - STARTED - TIME=03.39.19
> IEF450I TEDD071 RMS@30 RMS - ABEND=S722 U0000 REASON=00000000 841
> TIME=03.39.19
>
> .
> .
> J.O.Skip Robinson
>
Well, just to interject a likely stupid idea, can you access the job
output in SDSF? If so, I would put a question mark in front of the job to
display all the sysout entries. Then see which one has all the output lines
in it. Example:
LIH1 JOB DATA SET DISPLAY - JOB MAGI930D (JOB60835) LINE 1-6 (6)
COMMAND INPUT ===> SCROLL ===>
CSR
PREFIX=* DEST=(ALL) OWNER=* SYSNAME=*
NP DDNAME StepName ProcStep DSID Owner C Dest Rec-Cnt
Page-Cnt Byte-Cnt CC
JESMSGLG JES2 2 MDOFLI N 4
1
JESJCL JES2 3 MDOFLI N 60
4,395 1
JESYSMSG JES2 4 MDOFLI N 3
246 1
RMSRPT CA07RMS RMS@2X 101 MDOFLI N 8
1 577 1
SYSPRINT JS010 PS010 103 MDOFLI N 0
1
DSSMSGDD JS010 PS010 105 MDOFLI N 0
1
--
Veni, Vidi, VISA: I came, I saw, I did a little shopping.
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
