Error Message IEC141I 013-34 directing CICS DD file to OPSMVS
search cancel

Error Message IEC141I 013-34 directing CICS DD file to OPSMVS

book

Article ID: 137297

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

In OPSMVS Installing Guide section 'Direct Generic Data Set Output' at the below link :

Define Generic Data Set Interfaces (GDI)

it is explained how it is possible to direct output from data sets such as log files to CA OPS/MVS for processing by the AOF component. To do this, it is used the generic data set interface (GDI). With this interface enabled, CA OPS/MVS sees each record written to the generic data set as a message event, which executes AOF message rules.

 

As an example a CICS // DD log file (like the //SEQTRMO DD ) can be re-directed to OPS/MVS Opslog. 

 

Sometimes it can happen anyway that the following error is got by CICS task :

 

...

DFHMP0101I CXZZ Managed platform domain initialization has ended.

 DFHSI1503I CXZZ Terminal data sets are being opened.

 IEC141I 013-34,IGG0199G,TXTAZZS1,CXZZ,SEQTRMO

 DFHAP0001 CXZZ An abend (code 013/AKEB) has occurred at offset X'FFFF' in module DFHAPDM.

 DFHME0116 CXZZ

 (Module:DFHMEME) CICS symptom string for message DFHAP0001 is

 PIDS/5655Y0400 LVLS/700 MS/DFHAP0001 RIDS/DFHAPDM PTFS/UI39529

 AB/S0013 AB/UAKEB RIDS/DFHAPDM ADRS/0000FFFF

 DFHDU0201 CXZZ ABOUT TO TAKE SDUMP. DUMPCODE: AP0001 , DUMPID: 21/0001

 DFHDU0202 CXZZ SDUMPX COMPLETE. SDUMPX RETURN CODE X'00'

 DFHDM0105 CXZZ Unsuccessful initialization of DFHAP domain. CICS will terminate.

....

 

defining in the CICS task the file as  follows:

 

//SEQTRMO DD SUBSYS=(OPSS,OPSDSN,BLUE,BALALG)

How is it possible to bypass this abend and correctly re-direct the CICS // DD to the OPS/MVS Opslog? 


  

Environment

 

Component : OPS/MVS

Resolution

In OPS/MVS documentation we detail that :


...

To establish a generic data set interface with CA OPS/MVS, specify JCL that identifies CA OPS/MVS as a target for the output. Specify this JCL as follows:

//ddname DD SUBSYS =(ssid,OPSDSN{,color}{,reportid}{,posmgid})

....

Now, from IBM Guide 


IEC141I 013-rc,mod,jjj,sss, ddname[-#] [,dev,volser, dsname(member)]

Explanation

...


34

The system detected one of these conditions:

- The following combination was specified: QSAM, MACRF=GD or PD, and a RECFM value that is not VS, VBS, DS, or DBS.

- An OPEN macro instruction was issued for a data set with BLKSIZE and BUFL equal to 0. The system determined that it had to obtain buffers but was unable to do so. - 

- RECFM was specified with both the A and M attributes.

- The following combination was specified: QSAM, LRECL=0, and a RECFM value that is not V or VB.

- The following combination was specified: RECFM=V or VB and LRECL greater than the quantity BLKSIZE minus 4.

- The following combination was specified: QSAM and BLKSIZE=0. No nonzero BLKSIZE value was available from any source and the system could not determine one. Coding BLKSIZE=0 in the JCL never has an effect except when overriding a cataloged procedure variable.

- The following combination was specified: RECFM not variable or undefined and LRECL greater than BLKSIZE.

- The following combination was specified: BFTEK=A, RECFM=VBS, and LRECL=0.


This can be caused by the fact that the DCB=(...) information are not provided in the // DD definition.


So the error can be solved by adding the operand DCB=(...)  to the definition:


//SEQTRMO DD SUBSYS=(OPSS,OPSDSN,BLUE,BALALG)