IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

IEBEDIT Problem


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
pallarie

New User


Joined: 02 Jan 2007
Posts: 4
Location: Chennai

PostPosted: Fri Feb 15, 2008 7:18 pm
Reply with quote

I tried with the following jcl its not working out

Code:
 
//STEP001  EXEC PGM=IEBEDIT
//SYSPRINT DD SYSOUT=*
//SYSUT1   DD DSN=MYDSN.JCL(MEMBER),DISP=SHR
//SYSUT2   DD SYSOUT=*
//SYSIN    DD *
  EDIT TYPE=INCLUDE,STEPNAME=(STEP009,STEP007)
/*
//*


could you please help me out..
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Fri Feb 15, 2008 7:23 pm
Reply with quote

Could you post the output results? Error messages? Anything else that would be useful?
Back to top
View user's profile Send private message
pallarie

New User


Joined: 02 Jan 2007
Posts: 4
Location: Chennai

PostPosted: Sat Feb 16, 2008 2:25 pm
Reply with quote

I did not encounter any error as such. I could see the Job with STEP007 and STEP009 being recognized. But the steps were not executed.

Later i tried with the following JCL. It worked.

//STEP0001 EXEC PGM=IEBEDIT
//SYSUT1 DD DSN=TFSDPROG.OFFSSE.TEST1(SUREN),DISP=SHR
//SYSUT2 DD SYSOUT=(*,INTRDR)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
EDIT TYPE=INCLUDE,STEPNAME=(STEP040,STEP010)
/*

I think SYSOUT=(*,INTRDR) makes the difference.

Could some one explain the fuctionality of INTRDR.

Thanks in advance
Venkat Palla
Back to top
View user's profile Send private message
superk

Global Moderator


Joined: 26 Apr 2004
Posts: 4652
Location: Raleigh, NC, USA

PostPosted: Sat Feb 16, 2008 8:39 pm
Reply with quote

Start here with this previous post.
Back to top
View user's profile Send private message
priya

Moderator


Joined: 24 Jul 2003
Posts: 568
Location: Bangalore

PostPosted: Sat Feb 16, 2008 9:25 pm
Reply with quote

I recommend this post of superk:

superk wrote:
3. In the "old" days, all JCL, as well as most original data, used to be punched onto 80-column cards and fed into the mainframe through a card reader. Today, we create JCL using terminals and stage it in libraries. The JCL "reader" is no longer a physical device - but it is "simulated" - and it is called the "internal" reader. Putting JCL into the "internal" reader is done by coding the output destination for a file to the "internal" reader and writing the desired JCL into it. This is usually done by coding ( for example )

//jobjcl DD SYSOUT=(,INTRDR)

When the dataset is closed and released, the system will "read" and process the contents just as if it were a submitted job.

Here is some more Internal Reader information:

publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/HAS1A431/3.25?DT=20001026113913
Back to top
View user's profile Send private message
pallarie

New User


Joined: 02 Jan 2007
Posts: 4
Location: Chennai

PostPosted: Tue Feb 19, 2008 12:58 pm
Reply with quote

Thanks Priya and Kevin.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts Map Vols and Problem Dataset All Other Mainframe Topics 2
No new posts z/vm installation problem All Other Mainframe Topics 0
No new posts Job scheduling problem. JCL & VSAM 9
No new posts Problem with IFTHEN=(WHEN=GROUP,BEGIN... DFSORT/ICETOOL 5
No new posts Need to add field to copybook, proble... COBOL Programming 14
Search our Forums:

Back to Top