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

IEBEDIT utility in JCL


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

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix

PostPosted: Tue Jul 30, 2013 10:24 pm
Reply with quote

Hello,

Sorry, your JCL appears correct . . .

You will have to get by the error to proceed. Suggest you talk with your system support.

I'd guess your system is showing a wrong length record - even though the record may be correct. It must be 80. There are other reports of this error in the forum. So far i do not see a solution . . .

Keep in mind that IEBEDIT is very old and very pickly and the "pickiness" is not documented as far as i know. There is at least one example in the forum where the poster says his iebedit works. If i have time later, i'll try to find it.

Good luck.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1787
Location: Bloomington, IL

PostPosted: Wed Jul 31, 2013 12:14 am
Reply with quote

Aradhana Rathore. wrote:
See my target is to execute only steps E16005 of job WDAAAAAA and WDBBBBBB resp.
After executing the job that DSN was created, but was empty.Also my target is still not achieved.

As Mr. Scherrer says, Aradhana-chan, a RC=8 is not an abend, so the data set would not have been deleted by MVS dispositive processing. You can, if you wish, add a second step enclosed in an IF construct, thus;

Code:
//IF1      IF   (STEP001.RC NE 0) THEN
//STEP002  EXEC PGM=IEFBR14
//DD1      DD   DSN=PPPRG2.IRAM.JCL.JCL,DISP=(OLD,DELETE)
//ENDIF1   ENDIF


As Mr. Scherrer also says, IEBEDIT is a very old program (almost as old as I). The SYSPRINT data set, in particular, must have a blocksize that is a multiple of 121, or the step will indeed terminate with RC=8. I recommend that you code it as
Code:
//SYSPRINT DD   SYSOUT=A,DCB=BLKSIZE=121


Finally, that SYSPRINT data set will contain diagnostic messages that explain just what went wrong. If you do not understand, post them here in Code tags. Be sure to include the message number, so that they look like

Code:
IEB024I  high WAS HIGHEST SEVERITY CODE
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix

PostPosted: Wed Jul 31, 2013 1:42 am
Reply with quote

Howdy,

Well, i put together a Very Simple job:
Code:
//STEP001  EXEC PGM=IEBEDIT                                   
//SYSPRINT DD  SYSOUT=*,DCB=BLKSIZE=121                       
//SYSUT1   DD  DSN=MY.TEST.JCLLIB.JNK,DISP=SHR, 
//             DCB=LRECL=80,UNIT=SYSALLDA                     
//SYSUT2   DD  SYSOUT=*,DCB=BLKSIZE=121                       
//SYSIN    DD  *                                             
  EDIT START=BCOPY                                           
/*


submitted it and got:
Code:
IEB027I I/O ERROR                        ,MSRDSEDT,STEP001 ,863B,D,SYSUT1  ,GET   ,WRNG.LEN.RECORD,0000001A000000,QSAM
IEB024I  8 WAS HIGHEST SEVERITY CODE


For whatever reason, it is unhappy with SYSUT1 and i don't see why . . . icon_confused.gif
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1787
Location: Bloomington, IL

PostPosted: Wed Jul 31, 2013 1:53 am
Reply with quote

I'm pretty sure that the blocksizes for SYSUT1 and SYSUT2 have to be multiples of 80. You could use 9680 (= 80 * 121) as blocksize for both, or have SYSUT2 point to a data set rather than the spool. Or you could just not bother, of course icon_smile.gif

One thing that hasn't come up in this discussion is the possibility of Aradhana-chan using something other than a crufty old utility inherited from OS/360.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19243
Location: Inside the Matrix

PostPosted: Wed Jul 31, 2013 2:03 am
Reply with quote

How silly of me . . .

When SYSUT2 with no DCB failed, i added the 121 . . . D'oH . . .

Changed it to 80 and got the same thing.

Still have no clue why SYSUT1 is a problem . . .

Not really a bother, just had a minute and was curious icon_cool.gif
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 Goto page Previous  1, 2

 


Similar Topics
Topic Forum Replies
No new posts Use Copy Utility DB2 7
No new posts REASON 00D70014 in load utility DB2 6
No new posts ISRSUPC search utility - using high l... TSO/ISPF 2
No new posts Any JCL or VSAM Utility to get number... JCL & VSAM 1
No new posts DATA SET LIST UTILITY screen TSO/ISPF 6
Search our Forums:

Back to Top