You just showed me my error it HAS to be //SYSTSPRT DD SYSOUT=A and i had //SYSPRINT DD SYSOUT=A
Now
N 4000000 TESTMVS 11322 13:36:53.87 JOB00567 00000090 $HASP373 DB2EXTR START
N 0000000 TESTMVS 11322 13:36:53.88 JOB00567 00000090 IEF403I DB2EXTR - START
N 0020000 TESTMVS 11322 13:36:54.04 JOB00567 00000090 IEC130I SYSTSIN DD STA
M 0000000 TESTMVS 11322 13:36:54.05 JOB00567 00000090 IEF450I DB2EXTR RUNPROG
E 487 00000090 TIME=13.36.54
N 0004000 TESTMVS 11322 13:36:54.06 JOB00567 00000290 -
S ----PAGING COUNTS---
N 0004000 TESTMVS 11322 13:36:54.06 JOB00567 00000290 -JOBNAME STEPNAME PROC
S PAGE SWAP VIO S
N 0004000 TESTMVS 11322 13:36:54.06 JOB00567 00000290 -DB2EXTR RUNP
S 0 0 0
N 0000000 TESTMVS 11322 13:36:54.06 JOB00567 00000090 IEF404I DB2EXTR - ENDED
N 0004000 TESTMVS 11322 13:36:54.06 JOB00567 00000290 -DB2EXTR ENDED. NAME-
S ELAPSED TIME= .00
N 4000000 TESTMVS 11322 13:36:54.06 JOB00567 00000090 $HASP395 DB2EXTR ENDED
Unfortunately that is not the case. SYSTSPRT will be certainly be used, but SYSPRINT will very likely
also be used.
The brilliant, if occasionally slightly irascible
Dr. Sorichetti has made a good catch that I missed. The full IEC130I message will be
IEC130I SYSTSIN DD STATEMENT MISSING
Check your JCL, and make sure that the SYSTSIN DD statement is well-formed.
ETA: And re-reading the first post, I see that the JCL has SYSIN instead of SYSTSIN. Please change that and re-run.
"You have sat too long for any good you have been doing lately ... Depart, I say; and let us have done with you. In the name of God, go!" -- what I say to a junior programmer at least once a day