OnDemand User Group

Support Forums => z/OS Server => Topic started by: htees on June 03, 2020, 01:07:47 PM

Title: Loads Failing through ARSLOADP but manual loads through job submission working
Post by: htees on June 03, 2020, 01:07:47 PM

Hi folks, we are periodically having load failures when an output file contains LARGE  AFP documents(hundreds of pages) and said file is processed automatically through ARSLOADP.

 2020-05-15 00:07:17.914289: ARS1412E The document size of >2285875577< bytes exceeds the maximum size allowed of >2147483647< bytes.
 2020-05-15 00:07:17.914849: ARS1146I Loaded 2561 rows into the database
 2020-05-15 00:07:17.915274: ARS4311E Loading failed
 2020-05-15 00:08:23.509692: ARS4320I Unloading started
 2020-05-15 00:08:25.176608: ARS4321I Unloading of data was successful

I understand that the message states we are exceeding a 'maximum size', but yet we can load the file MANUALLY by creating a batch load through SAR (CA product) and resubmitting the output to the SAME sysout class ARSLOADP is using.

Thoughts on why the Initial load through ARSLOADP fails?  Are there PARMS that need to be looked at?
What are the maximum sizes of a load allowed?

ZOS - 4.26
CMOD  - 10.1.0.5
Large Object support is used

Thanks for any help offered.  HT



 

Title: Re: Loads Failing through ARSLOADP but manual loads through job submission working
Post by: Justin Derrick on June 03, 2020, 01:33:22 PM

A 2.2GB *document* is crazy.    That's over 432,000 letter-sized pages of text.

I see two solutions... 

1)  You'll need to improve the indexing to break this document down into smaller documents.

2)  You'll probably have to send the file in several pieces as well.

As for why it's successful manually...  Are you sure the entire document is getting loaded, and that it's not getting truncated silently? 

The limitation is related to the 32-bit address space - it can only calculate the size/offset of a document up to the 2GB mark.  After that, it overflows and your data gets corrupted.

-JD.

Title: Re: Loads Failing through ARSLOADP but manual loads through job submission working
Post by: Ed_Arnold on June 22, 2020, 02:28:57 PM

Quote

I understand that the message states we are exceeding a 'maximum size', but yet we can load the file MANUALLY by creating a batch load through SAR (CA product) and resubmitting the output to the SAME sysout class ARSLOADP is using.

What does it say the size of that load is?

If less, is something getting truncated?  Blanks perhaps?

Ed