When trying to copy more than about 20,000 lines of output into an AWS, we receive error message: INT02 AWS INTERNAL ERROR 23 AWS02 AWS LINE LIMIT EXCEEDED
search cancel

When trying to copy more than about 20,000 lines of output into an AWS, we receive error message: INT02 AWS INTERNAL ERROR 23 AWS02 AWS LINE LIMIT EXCEEDED

book

Article ID: 15957

calendar_today

Updated On:

Products

Roscoe

Issue/Introduction



When trying to copy more than about 20,000 lines of output into an AWS, we receive error message:

INT02 AWS INTERNAL ERROR 23

or


AWS02 AWS LINE LIMIT EXCEEDED

Possibly both messages??

How do we resolve this condition?

Environment

Release:
Component: ROSCOE

Resolution

A)

There is a line limit within this section of CA Roscoe. Just in case the 32,000 line limit has not been reached you might follow the following procedure to assist in this situation.

Issue the AWS command.  Check MAX LINE COUNT, if less than 32000, you can do a
AWS Format process and reset max lines to 32000.  If already set at 32000 then you can do nothing more.  

User must access file in chunks.           

B)

However, the INT02 message tells us that there may be a shortage of index blocks in the AWS files. Since this message was issued first, this may be your cause.

There is an architectural limitation to the number of AWS INDEX BLOCKS
that one user can have. When the limit is reached, CA Roscoe will display the ROS118E CODE 23 message in the logs.                         
 
You should reformat the AWS datasets with a larger data block-size, which will allow more data in one block, which will require less INDEX blocks.                           
 
You probably have some JCL already setup to allocate new files and format them properly. Here is a small example:
 
//FAWSDS   EXEC PGM=FAWSDS,                                          
//         PARM='A#=32,DB=2560,D#=2,SZ=32000'                        
//STEPLIB  DD  DSN=ROSCOE.RO60.RO60LIB,DISP=SHR                      
//AWSPRINT DD  SYSOUT=*                                              
//SYSAWSP  DD  DSN=ROSCOE.A19.MINI.AWSP,DISP=(,CATLG,DELETE),        
//             UNIT=3390,VOL=SER=vvvvvv,                                    ---> alter                             
//             SPACE=(2560,322,,CONTIG,ROUND),                       
//             DCB=(DSORG=DA,BLKSIZE=512)                            
//SYSAWS1  DD  DSN=ROSCOE.A19.MINI.AWS1,DISP=(,CATLG,DELETE),        
//             UNIT=3390,VOL=SER=vvvvvv,                                  --->  alter                             
//             SPACE=(2560,1024,,CONTIG,ROUND),                      
//             DCB=(DSORG=DA,BLKSIZE=2560)                           
//SYSAWS2  DD  DSN=ROSCOE.A19.MINI.AWS2,DISP=(,CATLG,DELETE),        
//             UNIT=3390,VOL=SER=vvvvvv,                                  ----> alter                             
//             SPACE=(2560,1024,,CONTIG,ROUND),                      
//             DCB=(DSORG=DA,BLKSIZE=2560)                           
//*                                              
 
Granted you must make required changes but this will provide a guideline.                            

Additional Information

Please note: In both scenarios you will be required to format new AWS files.