|
View previous topic :: View next topic
|
| Author |
Message |
hiravibk
Warnings : 1
Active User
Joined: 14 Dec 2008
Posts: 107
Location: India
|
|
|
|
Hi,
I have a job which executes a DB2 program say PROG1 using IKJEFT01 in STEP1. The SYSOUT is routed to xporter as below:
| Code: |
//SYSOUT DD SYSOUT=(5,PROG1),
// DEST=XP2I,
// HOLD=NO
|
But i want the SYSOUT to be routed to a dataset instead. When i did an override and submit the job, the job would start executing and using the CPU, but it just would be there doing nothing. It was not waiting for a dataset or for the operator to release. It would just be there. But it would run fine if i dont do an SYSOUT override.
The overridden dataset has LRECL of 133. I tried giving RECFM of overridden dataset as FB,FBA,VBA but still had the same issue. I removed the HOLD parameter itself from STEP1 and the DEST parameter too, but still faced the same issue. Any help is very much appreciated. Thank you |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10903
Location: italy
|
|
|
|
what You posted is not enough to provide any help!
and... how was the JOB terminated ?
You should have, at least, posted the JCL used
and the relevant part of the output. |
|
| Back to top |
|
|
hiravibk
Warnings : 1
Active User
Joined: 14 Dec 2008
Posts: 107
Location: India
|
|
|
|
Enrico,
The job would just be there with the below message in SYSTSPRT:
| Code: |
READY
DSN SYSTEM(DB25)
DSN
RUN PROGRAM(AECBVOLX) PLAN(PAEBDEV2)
|
I had to cancel the job after waiting for a long time. Below is the job:
| Code: |
//TAE2XM61 JOB (,0024),'MONTHLY RPT',CLASS=E,MSGCLASS=A,NOTIFY=&SYSUID
//*
/*ROUTE XEQ TESTDB2
//*
//S01 EXEC PGM=IKJEFT01,
// DYNAMNBR=100
//SYSOUT DD SYSOUT=(5,AE2XM61),
// DEST=XP2I,
// HOLD=NO
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=D
//SYNC DD DSN=TAE2.SXMTRN.VOL.EXTR.FILE(+1),
// DISP=(,CATLG,DELETE),
// SPACE=(CYL,(50,10),RLSE),
// UNIT=SYSDA
//SYSTSIN DD *
DSN SYSTEM(DB25)
RUN PROGRAM(AECBVOLX) -
PLAN(PAEBDEV2)
END
/* |
|
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| hiravibk wrote: |
Enrico,
The job would just be there with the below message in SYSTSPRT:
| Code: |
READY
DSN SYSTEM(DB25)
DSN
RUN PROGRAM(AECBVOLX) PLAN(PAEBDEV2)
|
I had to cancel the job after waiting for a long time. Below is the job:
| Code: |
//TAE2XM61 JOB (,0024),'MONTHLY RPT',CLASS=E,MSGCLASS=A,NOTIFY=&SYSUID
//*
/*ROUTE XEQ TESTDB2
//*
//S01 EXEC PGM=IKJEFT01,
// DYNAMNBR=100
//SYSOUT DD SYSOUT=(5,AE2XM61),
// DEST=XP2I,
// HOLD=NO
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=D
//SYNC DD DSN=TAE2.SXMTRN.VOL.EXTR.FILE(+1),
// DISP=(,CATLG,DELETE),
// SPACE=(CYL,(50,10),RLSE),
// UNIT=SYSDA
//SYSTSIN DD *
DSN SYSTEM(DB25)
RUN PROGRAM(AECBVOLX) -
PLAN(PAEBDEV2)
END
/* |
|
I may be missing something but I don't see where you have done anything with sysout!! |
|
| Back to top |
|
|
hiravibk
Warnings : 1
Active User
Joined: 14 Dec 2008
Posts: 107
Location: India
|
|
|
|
Thanks Craq!!
I replaced the SYSOUT statement with the below SYSOUT:
| Code: |
//SYSOUT DD DSN=TAE2.REPORT.AECBVOLX.FILE.DT0405,
// DISP=(,CATLG,DELETE),
// SPACE=(CYL,(50,10),RLSE),
// UNIT=SYSDA,
// RECFM=FB,LRECL=133 |
|
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10903
Location: italy
|
|
|
|
while Your job is running/hanging, from TSO enter
TSO ISRDDN ENQ
and follow the instructions
if You are lucky You might find what <holds> Your JOB
so that You can take the appropriate action |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6248
Location: Mumbai, India
|
|
|
|
At the face value of what you've posted so far, all looks fine. So possibly, you can "compare" the JESMSGLG and/or JESYSMSG of both the Jobs - one which executes and the other which does not.
Second, you can try using DISP=(,CATLG,CATLG), for the 'SYSOUT-file', and try with TIME=2 (some small value after which Job abends with a Time-abend) in Job card. Check what is there in the SYSOUT dataset.
Okay, all this is to get you going - none of them is a solution. |
|
| Back to top |
|
|
hiravibk
Warnings : 1
Active User
Joined: 14 Dec 2008
Posts: 107
Location: India
|
|
|
|
Thank you for your time guys. It is working fine now.
The problem was, i noticed that this step is writing huge data to SYSOUT. And since i was routing SYSOUT to a dataset, the job was writing it to the dataset and there was obviously no messages in the spool indicating that the job was writing the output. But i didnt override, i could see the SYSOUT while the job was running!
I just submitted the job and left it overnight and gave it its time and it was fine. So, actually there was no problem at all! My bad! Thanks again |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6248
Location: Mumbai, India
|
|
|
|
All is well, that ends well!
 . |
|
| Back to top |
|
|
|
|
  |
All times are GMT + 6 Hours |
|
