2011 Apr 06 2:28 AM
Hi,
I am developing a customer statement report and putting the data into application server.
if the data is less - the file is getting created in application server.
if there is huge amount of data - the back job gets cancelled
The error description/dump is as follows :
Runtime Errors DATASET_WRITE_ERROR
Except. CX_SY_FILE_IO
The current program "ZCUST_STMT" had to be terminated because
a capacity limit has been reached.
The dump points in the line at TRANSFER STATEMENT
>>>>> TRANSFER lv_string TO v_file.
Is there any memeory space (Max limit ) specified for application server for a single file ?
How can we solve this issue ?
Thanks
Senthil
Hi,
I am developing a customer statement report and putting the data into application server.
if the data is less - the file is getting created in application server.
if there is huge amount of data - the back job gets cancelled
The error description/dump is as follows :
Runtime Errors DATASET_WRITE_ERROR
Except. CX_SY_FILE_IO
The current program "ZCUST_STMT" had to be terminated because
a capacity limit has been reached.
The dump points in the line at TRANSFER STATEMENT
>>>>> TRANSFER lv_string TO v_file.
Is there any memeory space (Max limit ) specified for application server for a single file ?
How can we solve this issue ?
Thanks
Senthil
2011 Apr 06 3:42 AM
Hi,
it looks like an error on OS level. Are you sure that there is enough space for your new file? What is the limit for file size?
Cheers
2011 Apr 06 4:39 AM
Hi Senthil,
This issue comes usually if the system cannot find the file, if no more space is available to write or create the file, or if the authorization to access the file is missing. If you are accessing the file through a system ID and not the user-ID you might want to check with your administration folks if the user-ID or the system ID has teh necessary authorization.
For any of the reasons mentioned above(cannot find the file, no enough space available for the file or the authorization issue) your administration folks will able able to help you.
Thanks.
2011 Apr 06 4:30 AM
2011 Apr 06 5:33 AM
Hello Senthil,
Is the program terminating in the DEV box or in another subsequent system?
If in DEV, you can try to catch the exception & get the exception text. Something like this:
DATA: lx_file_err TYPE REF TO cx_root, "File Exceptions
lv_msg_txt TYPE string.
TRY.
TRANSFER x_data TO x_filepath.
CATCH cx_sy_file_io INTO lx_file_err.
lv_msg_txt = lx_file_err->get_text( ). "Get the error text
ENDTRY.BR,
Suhas
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |