|
View previous topic :: View next topic
|
| Author |
Message |
drowelf
Warnings : 1
New User
Joined: 03 Mar 2006
Posts: 47
Location: Simpsonville, SC
|
|
|
|
I have a job that has several log datasets that are defined as sysout=T where T is defined as the HOLD Q. Now in the next step I want to gener the log out to a GDG for historical purposes. Here is my Gener Step.
| Code: |
//S1PESMLG EXEC PGM=IEBGENER,COND=EVEN
//STEPLIB INCLUDE MEMBER=IPCSSTEP * IPCS STEPLIBS
//SYSUT1 DD DISP=SHR,DSN=*.C4IPCS.IPCS.ESMLOG
//SYSUT2 DD DSN=&PESMLOG(+1),
// DISP=(NEW,CATLG,CATLG),DATACLAS=X37HELP,
// DCB=(&MDLDSCB,RECFM=FBA,LRECL=133,BLKSIZE=13300),
// SPACE=(133,(500,200),RLSE),AVGREC=K
//SYSPRINT DD DUMMY
|
Now when this step executes I get the following JCL Error.
IEF212I CT0DIPCS S1PESMLG C4PLOGS SYSUT1 - DATA SET NOT FOUND
Now the Sysout file does have data in it. This has got me perplexed. Any thoughts or suggestions as to how I can accomplish my goal?
Thanks, |
|
| Back to top |
|
 |
Vidusha
New User
Joined: 01 Feb 2006
Posts: 20
Location: Chennai
|
|
|
|
( *.C4IPCS.IPCS.ESMLOG. - Sorry a naive doubt. why there is a * infront.)
The reason for Job abend is that the input dataset is not available. If you want the log to be stored, you can remove SYSOUT=T and can provide GDG there itself.
Is it solving? |
|
| Back to top |
|
|
drowelf
Warnings : 1
New User
Joined: 03 Mar 2006
Posts: 47
Location: Simpsonville, SC
|
|
|
|
I don't want to do that, as then the output can not be viewed while the job is running. These are online system jobs that run for days at a time. The GDG are created as DISP=NEW (i.e. OLD) and can not be viewed until the job ends. As Sysout=T files we can view that at any time.
The first *. is required because otherwise I get an invalid refer back error. |
|
| Back to top |
|
|
mmwife
Super Moderator
Joined: 30 May 2003
Posts: 1592
|
|
|
|
Hi Eric,
It would be helpful if you showed us the JCL of the step that created the file you're referring to. Also if the step is in a proc give us the name of the proc.
Thanx, Jack. |
|
| Back to top |
|
|
dneufarth
Active User
Joined: 27 Apr 2005
Posts: 420
Location: Inside the SPEW (Southwest Ohio, USA)
|
|
|
|
you're attempting to copy a JES file to a GDG; I don't think that's possible using the approach you have chosen.
most direct the print data to a dataset as mentioned above
perhaps you could modify the program(s) to send the print data to both JES and a dataset? Online presents challenges here.
does the JES data end up in a report/archival system? Can it be directed to one? It may remain available there for archival purposes. |
|
| Back to top |
|
|
drowelf
Warnings : 1
New User
Joined: 03 Mar 2006
Posts: 47
Location: Simpsonville, SC
|
|
|
|
We don't have access to the code to have it write out to both a DS and a GDG.
I'm pretty sure I've done this in the past.
Ok,
The PROC is
| Code: |
//C4IPCS EXEC C4NIPCS
//EXECUTE INCLUDE MEMBER=S0DIPCS
which has the EXEC Statement
//IPCS EXEC PGM=DKNMTASK
.......
//ESMLOG DD SYSOUT=T (T is the Hold Q)
.....
//*---------------------------------------------------------------*
//* Print the ESM Log to a GDG *
//*---------------------------------------------------------------*
//S1PESMLG EXEC PGM=IEBGENER,COND=EVEN
//STEPLIB INCLUDE MEMBER=IPCSSTEP * IPCS STEPLIBS
//SYSUT1 DD DDNAME=*.C4IPCS.IPCS.ESMLOG
//*
//SYSUT2 DD DSN=&PESMLOG(+1),
// DISP=(NEW,CATLG,CATLG),DATACLAS=X37HELP,
// DCB=(&MDLDSCB,RECFM=FBA,LRECL=133,BLKSIZE=13300),
// SPACE=(133,(500,200),RLSE),AVGREC=K
//SYSPRINT DD DUMMY
|
|
|
| Back to top |
|
|
|
|
