EDC5093I AN UNSUPPORTED I/O OPERATION HAS BEEN ATTEMPTED

Anita · New User Joined: 28 May 2005 Posts: 3

Hi,

I am facing this issues in production. We are using a mainframe file to extract data from teradata table , update file and again load data from file to table. This job was running successfully till 3 days back , when there was a data issue, the file was manually opened and some data was corrected. After this manual file correction the jobs is failing everyday with a error message

EDC5093I AN UNSUPPORTED I/O OPERATION HAS BEEN ATTEMPTED.
*** Error: Import file could not be re-opened.

we found the explanation for EDC5093I.

EDC5093I
An unsupported I/O operation has been attempted.

Explanation:
An unsupported I/O operation has been attempted by the application program. The unsupported operations resulting in this message are the following:

• An attempt was made to open a large format sequential data set for read with repositioning (seek), while the data set was already opened for write without repositioning (noseek). This action is prevented because the writer can extend the data set beyond the point where the reader is allowed to read (65535 tracks). A possible solution is to open for read without repositioning (noseek).
Programmer response:
Change the application program to avoid using the unsupported I/OE operation.

System action:
The function call fails.

We tried to create a new file with a different name and run the job , the job continues to fail.

Appreciate any help with this issue.

enrico-sorichetti · Posted: Thu Apr 25, 2013 3:46 pm

not much we can do...
You just posted an error message and nothing more
in any case
EDC messages are not COBOL related as per

4.0 Chapter 4. XL C/C++ Run-Time Messages
where the message is described

what is the TRUE environment, and what program are You running ???

the issue does not really belong to COBOL

and probably hand mangling the file probably broke it ...
really little can be don from here,
what has Your support to tell about it

Anita · New User Joined: 28 May 2005 Posts: 3

Enrico,

Sorry about that..

This is a JCL using a mainframe sequential file to extract data from a teradata table, the same file is again used to load the teradata table using a teradata utility.

//*********************************************************************
//* STEP0030: EXPORT FROM EDW_PPT_VIEW.EDWP031_SVCPART_FINANCIALS_VW
//* FOR CURRENT AND/OR PRIOR MONTHS
//*********************************************************************
//STEP0030 EXEC PGM=BTQMAIN,COND=(0,LT)
//*
//SYSOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//*
//INFILE DD DSN=PABS.PROD.IX237.SEQPARM,-->(problem file)
// DISP=SHR
//*
//OUTFILE DD DSN=PABS.PROD.IX237,
// DISP=OLD
//*
//SYSIN DD DSN=PM.CHGMAN.IX237.TER(PLDWBTHB),
// DISP=SHR

The support team is working on this , we are yet to hear from them.

If this file is broke , i tried creating a new file , but the job still fails.

enrico-sorichetti · Posted: Thu Apr 25, 2013 4:07 pm

unfortunately nothing that we can do from here...

contact teradata for support

Anita · New User Joined: 28 May 2005 Posts: 3

Teradata support has confirmed the issue is with the file. Teradata is not able to open the mainframe file.

I was also able to do a QW EDC5093I in mainframe.

Robert Sample · Posted: Thu Apr 25, 2013 4:42 pm

Since this is not a COBOL issue, the topic has been moved. The EDC5093I message comes from the C/C++ run time library messages -- perhaps you should investigate your program calling sequence to see if C or C++ is invoked at some point?

Bill Woodger · Posted: Thu Apr 25, 2013 4:51 pm

I also think the "edit" broke the file.

Do you delete the file ever?

I'd catalogue a new dataset, copy the content of the old file into it. Attempt with the new dataset.

When cataloguing the new dataset, try to model it on a back-up of the file before the edit.

You may have a "short block", "unfilled track" or even managed to get a record with the wrong length, perhaps, but I'd hope the undefined "method of edit" didn't allow that last.

Has the file been "edited" before? If so, what was different? If not, don't do it again, but find a tested-and-reliable method for achieving what you did to attempt to get Production going again.

You did "test" the "edit" method to fix the data?

dick scherrer · Posted: Thu Apr 25, 2013 6:44 pm

Hello and welcome to the forum,

Is there a backup from Before the file was manually modified?

Hopefully, there has been no work done as the file cannot be opened?

Restore to a test dataset, make sure the data is usable, and then restore production.