Re: JCL disp on abend

2019-07-24 Thread Jesse 1 Robinson
-543-6132 Office ⇐=== NEW robin...@sce.com -Original Message- From: IBM Mainframe Discussion List On Behalf Of CM Poncelet Sent: Tuesday, July 23, 2019 2:53 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: JCL disp on abend ... and "//DDIN DD DSN=file1,DISP=(OLD,DELETE

Re: JCL disp on abend

2019-07-23 Thread CM Poncelet
... and "//DDIN DD DSN=file1,DISP=(OLD,DELETE,KEEP)" states that file1 should be deleted regardless on jobstep termination *unless* it abends.   On 23/07/2019 06:24, Dan D wrote: > "IEF142I TYC1DABK EDIOUT2 STEP02 - STEP WAS EXECUTED - COND CODE 0012" > > As you can see from the IEF142I the job

Re: JCL disp on abend

2019-07-23 Thread Steve Smith
It's traditional for utility programs to trap abends and convert to a return code. Whether that's a good idea or not is a classic moot point. And it has been mooted for decades. Generally, you would need to have conditional (likely IEFBR14) steps to control the disposition of datasets. You

Re: JCL disp on abend

2019-07-23 Thread Elaine Beal
Thanks for the help! Elaine -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: JCL disp on abend

2019-07-23 Thread Carmen Vitullo
: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, July 22, 2019 9:12:18 PM Subject: Re: JCL disp on abend '//EDIOUT2 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //DDIN DD DSN=file1,DISP=(OLD,DELETE,KEEP) //DDOUT1 DD DSN=file2, // DISP=(,CATLG),MGMTCLAS=MC60DY, // LIKE=file1 //SYSIN DD DISP=SHR,DSN=PROCLI

Re: JCL disp on abend

2019-07-22 Thread Dan D
"IEF142I TYC1DABK EDIOUT2 STEP02 - STEP WAS EXECUTED - COND CODE 0012" As you can see from the IEF142I the job did NOT abend but rather IDCAMS ended with a return code 12. Dan -- For IBM-MAIN subscribe / signoff / archive

Re: JCL disp on abend

2019-07-22 Thread Elaine Beal
'//EDIOUT2 EXEC PGM=IDCAMS //SYSPRINT DD SYSOUT=* //DDIN DD DSN=file1,DISP=(OLD,DELETE,KEEP) //DDOUT1 DD DSN=file2, // DISP=(,CATLG),MGMTCLAS=MC60DY, // LIKE=file1 //SYSINDD DISP=SHR,DSN=PROCLIB(AIBACKC1) --> sysin is just reporo in to out //* When these abend with a

Re: JCL disp on abend

2019-07-22 Thread Elardus Engelbrecht
Elaine Beal wrote: >We have a job that is coded as follows- >step1 - idcams repro dummy in to file1,disp=(mod,catalg) >step2 repro above (dummied) file1 , disp=(old,delete,keep) to file2 >disp=(,catlg) >when we get a B37 on step2 file2, file1 is deleted even though it has

Re: [External] JCL disp on abend

2019-07-22 Thread Pommier, Rex
@LISTSERV.UA.EDU Subject: [External] JCL disp on abend We have a job that is coded as follows- step1 - idcams repro dummy in to file1,disp=(mod,catalg) step2 repro above (dummied) file1 , disp=(old,delete,keep) to file2 disp=(,catlg) when we get a B37 on step2 file2, file1 is deleted even though it has disp

JCL disp on abend

2019-07-22 Thread Elaine Beal
We have a job that is coded as follows- step1 - idcams repro dummy in to file1,disp=(mod,catalg) step2 repro above (dummied) file1 , disp=(old,delete,keep) to file2 disp=(,catlg) when we get a B37 on step2 file2, file1 is deleted even though it has disp=(old,delete,keep) I've scoured the