Mainframe ABEND

[Costi Zaboura]

DESCRIPTION

HOW TO-Troubleshoot an ABEND in the ATTDAEMON on the Mainframe

An ABEND occurs when running the DAEMON


1- Add the following to GBLParms (HLQ.def, e.g. attunity.def.GBLPARMS):

APT_NO_ACCVIO_TRAP=1

2-
2.1 Allocate the AC4000.DEF.SYSDUMP and AC4000.DEF.CEEDUMP datasets, as follows:
General Data Current Allocation
Volume serial . . . : DEV001 Allocated tracks . : 20
Device type . . . . : 3390 Allocated extents . : 1
Organization . . . : PS
Record format . . . : FBA
Record length . . . : 133
Block size . . . . : 27930 Current Utilization
1st extent tracks . : 20 Used tracks . . . . : 6
Secondary tracks . : 1 Used extents . . . : 1

Creation date . . . : 2003/01/22
Referenced date . . : 2003/04/10
Expiration date . . : ***None***

2.2 Edit the ATTDAEM JCL file, as follows:

//ATTDAEMN JOB MSGLEVEL=(1,1),CLASS=A,
// MSGCLASS=A,REGION=6M,
// USER=GTPADR,PASSWORD=
2 //STEP1 EXEC PGM=IRPCD,
// PARM='-B -L 90.90.90.18:2551 START IRPCDINI'
//* PARM='-B START IRPCDINI'
//* PARM='-L 90.90.90.18 START'
//*OUTO OUTPUT CLASS=0,OUTDISP=(LEAVE,LEAVE)
3 //STEPLIB DD DSN=AC4000.LOADAUT,DISP=SHR
4 // DD DSN=AC4000.LOAD,DISP=SHR
5 // DD DSN=CEE.SCEERUN,DISP=SHR
6 //SYSPRINT DD SYSOUT=A
//SYSDUMP DD DSN=AC4000.DEF.SYSDUMP,DISP=SHR
//CEEDUMP DD DSN=AC4000.DEF.CEEDUMP,DISP=SHR
7 //GBLPARMS DD DSN=AC4000.DEF.GBLPARMS,DISP=SHR
8 // EXEC PGM=IRPCD,COND=((1,EQ,STEP1),(2,EQ,STEP1)),
// PARM='-KRUNIRPCD START'
//*OUTO OUTPUT CLASS=0,OUTDISP=(LEAVE,LEAVE)
9 //STEPLIB DD DSN=AC4000.LOADAUT,DISP=SHR
10 // DD DSN=AC4000.LOAD,DISP=SHR
11 // DD DSN=CEE.SCEERUN,DISP=SHR
12 //SYSPRINT DD SYSOUT=A
13 //GBLPARMS DD DSN=AC4000.DEF.GBLPARMS,DISP=SHR
//*OUTNORM OUTPUT OUTDISP=(HOLD,HOLD),NAME='P390HS'
//*SYSPRINT DD SYSOUT=O,OUTPUT=(*.OUTO)
14 //SYSDUMP DD DUMMY

Required Logs:
The Bottom of the SYS log (tso sdsf log)
from where the ATTDAEMN starts!
The DataSets:
AC4000.DEF.SYSDUMP
AC4000.DEF.CEEDUMP