Mainframe-Attached Clients:
The following is a list of error number values that cause abends:
Handling an I/O Abend on z/OS
BTEQ converts an abend to user 1000. This is useful to automate processes based on -job step -condition code checking, as shown in the following example:
//YNBTQ JOB 1,'Your Name',CLASS=B,Notify=YN,
// MSGCLASS=A,MSGLEVEL=(1,1)
//BTEQ EXEC PGM=BTQMAIN
.............................................
.............................................
//NOFILE DD DSN=nofile.inthis.location,DISP=SHR
//SYSIN DD DATA,DLM=##
.Logon <TDPID>/<UserName>,<PassWd>;
.............................................
.Import Data File=NOFILE
.............................................
##
//CCTEST IF (ABENDCC=U1000) THEN
//CRDAFL EXEC PGM=CRATDTFL
.............................................
.............................................
//NOABND ELSE
//PROCED EXEC PGM=DOSMTHNG
.............................................
.............................................
// ENDIF
In the example, the program CRATDTFL is executed if running the BTEQ program results in a user abend 1000 due to an I/O error. If the BTEQ program runs successfully, DOSMTHNG is executed.