IEC143I S213-04 on TRANSF file in AW1ID001
search cancel

IEC143I S213-04 on TRANSF file in AW1ID001


Article ID: 142920


Updated On:


Datacom DATACOM - AD Datacom/DB


Running CA Common Services/ENF job AW1ID001 to define the CA ENF databases to a CA Datacom/AD MUF, received errors on the IMPORT step:

IEC143I 213-04,IFG0194D,IDC9079F,IMPORT,TRANSF,E421,LGG001,  308
+IDI0002I Module VTPM9803, CSECT VPE9803, offset X'2670': Abend S213-X'4'
 TIME=09.32.56  SEQ=47932  CPU=0000  ASID=020E
 PSW AT TIME OF ERROR  075C1000   80E90568  ILC 2  INTC 0D

And from the fault analyzer:
 A system abend 213 reason code X'4' occurred in module IGC0001I at offset X'15566'.
 The abend occurred after executing machine instruction 0A13 (OPEN) in module VTPM9803 CSECT VPE9803 at offset X'2670'.


Release : 15.0

Component : CA Datacom/AD


The file listing in the z/OS catalog was not valid for the TRANSF allocated file.


Verify the status of the filename as listed in the IEC143I message. In the case presented, the client needed to manually recall the file from archive, and then the jobstep executed normally.

Preparation to rerun the step in the AW1ID001 job was to delete the IXX0700 and ENF0700 database files, and then rerun the job from the beginning.

Additional Information

Information on the message:

   IEC143I 213-rc,mod,jjj,sss, ddname[- #],dev,volser,dsname(member)                                                                 
   Explanation: An error occurred during the processing of an OPEN macro instruction for a data set on a direct access device. This is probably a user error.
   In the message text:                                                                                                              
rc Associates this message with system completion code 213 and with the return code.                                                                                                                             
mod The name of the module in which the error was detected.                                                                       
jjj The job name.                                                                                                                 
sss The step name.                                                                                                                
ddname[-#] The data definition (DD) name, followed by a concatenation number (#) if the DD statement is part of a concatenation and not the first DD statement in the concatenation.
dev The device number.                                                                                                            
volser The volume serial number.                                                                                                  
dsname(member) The data set name. Member name if specified. If the value of dsname in the message is ...PATH=.SPECIFIED..., the problem was with a z/OS UNIX file.                                                    
   Return Code Explanation                                                                                                           
   04 Either an I/O error occurred in reading the format-1 data set control block (DSCB), or the format-1 DSCB for the data set could not be found on the first volume specified by the DD statement (the volume indexed by the volume sequence number) or in the catalog. For the second case, make sure that the DSNAME and VOLUME parameters in the DD statement or in the catalog are correct. You can specify a recovery attempt request in the data control block (DCB) ABEND exit routine. Or the JFCB has been incorrectly modified or the data set name supplied in the JFCB passed to OPEN was not available to the job because it was being used by some other job. Either the data set was being opened for INPUT and some other job had exclusive control of the data set (either referenced the data set in a DD control statement with DISP of OLD or MOD, or issued an OPEN TYPE=J macro instruction with processing option INOUT, OUTIN, OUTPUT, OUTINX, EXTEND, or UPDATE), or the data set was being opened for an option other than INPUT (INOUT, OUTIN, OUTPUT, or UPDATE: requiring exclusive control of the data set) and some other job was using the data set (either referenced the data set in a DD control statement, or issued an OPEN TYPE=J macro instruction).