Hi support,
A client trying to put a file on our system gets the following error. Is there a way to increase the input buffer?
Ý75.578¨ debug3: request 48: open flags 26
Ý75.578¨ open "//D/UTT.C7298.RP240.MNTH" flags WRITE,CREATE,TRUNCATE mode 0666
ZosDatasetÝI¨: Opening dataset D.UTT.DATASETfor write with options: like(D.SYP.FIX1047) new catalog
Ý75.642¨ debug1: request 48: sent handle handle 0
Ý75.698¨ debug1: request 49: write "//D/UTT.DATASET" (handle 0) off 0 len 131072
Ý75.699¨ debug3: request 49: sent status 0
Ý75.699¨ sent status Success
Ý75.730¨ debug1: request 50: write "//D/UTT.DATASET" (handle 0) off 131072 len 131072
ZosDatasetÝE¨: InputBuffer will not hold 131072 bytes of new data
ZosUtilÝE¨: Unexpected exception caught in zos_write
Ý75.730¨ process_write: write failed
Ý75.730¨ debug3: request 50: sent status 0
Ý75.730¨ sent status Success
Ý75.777¨ debug1: request 51: write "//D/UTT.DATASET" (handle 0) off 262144 len 131072
ZosDatasetÝE¨: dataset write error: seek not allowed
Ý75.782¨ debug3: request 52: close handle 0
Ý75.782¨ close "//D/UTT.C7298.RP240.MNTH" bytes read 0 written 131072
ZosDatasetÝI¨: Closing dataset //D.UTT.DATASET before completion - 131072 bytes received, 124 records written
Ý75.898¨ debug3: request 52: sent status 0
Ý75.899¨ sent status Success
Ý75.941¨ debug3: request 53: realpath
Ý75.941¨ realpath "//D"
Ý75.951¨ debug1: request 53: sent names count 1
Ý75.973¨ debug3: request 54: opendir
Thank you,
Tom
Unexpected exception caught in zos_write
Re: Unexpected exception caught in zos_write
Tom,
This error is actually a bug, which was fixed in release 2.0.1.
See: http://dovetail.com/docs/cozinstall/changes.html
But, the cause of this problem was that we were not handling input lines that were > 128K. This is quite odd, and is usually cause by data that doesn't have any line separators at all.
This error is actually a bug, which was fixed in release 2.0.1.
See: http://dovetail.com/docs/cozinstall/changes.html
But, the cause of this problem was that we were not handling input lines that were > 128K. This is quite odd, and is usually cause by data that doesn't have any line separators at all.