Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

Copy a Sysout file to a GDG as last step

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
drowelf
Warnings : 1

New User


Joined: 03 Mar 2006
Posts: 39
Location: Houston, Texas

PostPosted: Fri Mar 03, 2006 8:13 am    Post subject: Copy a Sysout file to a GDG as last step
Reply with quote

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
View user's profile Send private message

Vidusha

New User


Joined: 01 Feb 2006
Posts: 20
Location: Chennai

PostPosted: Fri Mar 03, 2006 3:37 pm    Post subject:
Reply with quote

( *.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
View user's profile Send private message
drowelf
Warnings : 1

New User


Joined: 03 Mar 2006
Posts: 39
Location: Houston, Texas

PostPosted: Sat Mar 04, 2006 5:28 am    Post subject: Re: Copy a Sysout file to a GDG as last step
Reply with quote

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
View user's profile Send private message
mmwife

Super Moderator


Joined: 30 May 2003
Posts: 1592

PostPosted: Sun Mar 05, 2006 7:13 am    Post subject:
Reply with quote

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
View user's profile Send private message
dneufarth

Active User


Joined: 27 Apr 2005
Posts: 241
Location: Cincinnati OH USA

PostPosted: Sun Mar 05, 2006 8:46 pm    Post subject:
Reply with quote

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
View user's profile Send private message
drowelf
Warnings : 1

New User


Joined: 03 Mar 2006
Posts: 39
Location: Houston, Texas

PostPosted: Mon Apr 10, 2006 2:18 am    Post subject: Re: Copy a Sysout file to a GDG as last step
Reply with quote

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
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Converting Variable block file to Fix... bhavana yalavarthi DFSORT/ICETOOL 11 Tue May 16, 2017 2:20 pm
No new posts Validate date and numeric fields and ... Rick Silvers DFSORT/ICETOOL 6 Thu May 11, 2017 6:51 pm
No new posts Getting error while opening a variabl... apandey1 COBOL Programming 5 Fri May 05, 2017 12:22 pm
No new posts Issue with NDM process to transmit ES... chetanambi All Other Mainframe Topics 6 Wed May 03, 2017 10:52 am
No new posts File processing vishwakotin Mainframe Interview Questions 9 Fri Apr 28, 2017 11:38 am


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us