IBM Mainframe Forum

Dear all senior and master..
Kindly please assist, during my cobol programming, i getting error file status = 30 during write the record..

According with document :
30 is "The I/O statement was unsuccessfully executed as the result of a boundary violation for a sequential file or as the result of an I/O error, such as a data check parity error, or a transmission error." .. what does it mean ?

Appreciate with your help.
Thanks.

An attempt to write outside the defined boundaries of a data set or record (e.g., by changing the record length and trying to rewrite it). Post the code fragment writing the record and we may be able to be more specific.

Akatsukami wrote:An attempt to write outside the defined boundaries of a data set or record (e.g., by changing the record length and trying to rewrite it). Post the code fragment writing the record and we may be able to be more specific.

thanks Akatsukami..
is that possible because file size also ?
fyi : the file have key.. but if i check key is not unique and can duplicate. I will post the code tomorrow, because the code in my office..

xav3rius wrote:is that possible because file size also ?

That is indeed possible; that is why I wish to see the code, to help narrow down the possibilities.

The error message you quoted indicates a sequential file. Your post mentions a key. Sequential files do not have keys. Is the file sequential, relative, PDS, or VSAM (and if VSAM is it ESDS, RRDS, KSDS, or one of the other types)?

Hmmm, I thought a File Status 30 was "No further information'.
For boundary violations on a sequential file WRITE, it could be simply you are Out Of Space. Did you check this?

OTOH an 'out of space' should lead to an Sx37 abend which has not been mentioned (yet?).

NicC wrote:OTOH an 'out of space' should lead to an Sx37 abend which has not been mentioned (yet?).

That's true.

Since "key" was mentioned, my gut feeling is this is a VSAM file and got a boundary violation on the WRITE (status 34 - out of space).

Hard to help people when you cannot get the information (correct information).

c62ap90 wrote:Since "key" was mentioned, my gut feeling is this is a VSAM file and got a boundary violation on the WRITE (status 34 - out of space).

To the left, the TS says

the file have key.. but if i check key is not unique and can duplicate.

suggesting either that heesh is accessing a KSDS through an AIX (although I don't think you can do this for a write) or that heesh is using "key" in the generic sense, as we would discuss "keys" on a data set to be sorted. In any case, the TS hasn't been back since heesh assured us that heesh woiuld post the code realsoonnow, so I daresay that we can write this off.

Akatsukami wrote:

c62ap90 wrote:Since "key" was mentioned, my gut feeling is this is a VSAM file and got a boundary violation on the WRITE (status 34 - out of space).

To the left, the TS says

the file have key.. but if i check key is not unique and can duplicate.

suggesting either that heesh is accessing a KSDS through an AIX (although I don't think you can do this for a write) or that heesh is using "key" in the generic sense, as we would discuss "keys" on a data set to be sorted. In any case, the TS hasn't been back since heesh assured us that heesh woiuld post the code realsoonnow, so I daresay that we can write this off.

Thanks all,
finally solve .. i just refresh the module.. it's work again.
thanks all..