Roscoe IMP39 IMPORT TERMINATING DUE TO OVERFLOW IN AWS

Products

• Roscoe

Issue/Introduction

Why is the user getting this message? The file they are trying to import is the same size as another one that they can import with no problems.

Environment

Roscoe® Interactive Environment 6.0

Cause

This error message indicates that the file the user is trying to import has more lines than the AWS (Active Work Space) maximum allows. The maximum number of lines that can be imported is a parameter that can be set In Roscoe. However, the largest value for this parameter is 32000. It does not matter how many characters are on the line as long as it is not greater than 255. If the length of the line is greater than 255, you will not get an error, but the line will wrap and each line of the file will use up 2 lines in the AWS, reducing the total line limit to 16000. The line limit does not have anything to do with the amount of DASD space the file occupies.

Resolution

Workaround:

Increase the line limit if possible.  Determine what the line limit is set to by running the AWS rpf (ro.aws) from the Roscoe command line. The limit is displayed in the top right column:

          MAXIMUM NUMBER OF LINES 32000

For more information about setting and increasing the line limit, please see ROSCOE AWS Datasets, How to view the current settings

Examples

• The line limit is 32,000 and the LRECL of the file 92.  You can have 32,000 lines that are 92 characters wide.
• The line limit is 32,000 and the LRECL of the file 255. You can have 32,000 lines that are 255 characters wide.

If you cannot increase the line limit, or you are already at the line limit, the workaround to manage an import of a file with over 32,000 lines would be to use multiple AWS's.

1. Split the file into different AWS's, each not exceeding 32000 lines.
2. After editing is done in each AWS, the contents of each AWS can be exported to the original data set, if it is a sequential data set. The first EXPort without DISP=, any subsequent EXPort with DISP=MOD added after the data set name.
3. In case the original data set is a member of a PO data set, EXPorting must be done to a sequential file first, which then must be copied into the
   original member to replace this.