Hi Thomas,

The way I read your posting is that it doesn't have to work on 5.4 but you
want to be able to create it on 5.4 and then port the objects to 5.3 to run.

Can you create the outfile on your 5.4 system, rename it to something
unique, ALTER TABLE to remove the extra columns, and then reference and use
this new file?

Yours truly,

Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144

On 16 November 2015 at 12:13, Thomas Garvey <tgarvey@xxxxxxxxxx> wrote:


I've got a CL program that creates and uses the outfile from a DSPOBJD
However, the program is created on a v5r4 partition and must run on a v5r3
The outfiles created by the DSPOBJD command are different on these two OS
There are 6 more fields on the v5r4 version than the v5r3.

The problem is that when the program runs on the v5r3 partition it hard
halts with
CPF0859 (File override caused I/O buffer size to be exceeded).
"The compile-time file was overridden with a run-time file
with a maximum record length smaller than the maximum record length of the
compile-time file."

So, my question is, what can I do with this?
Are there different outfile descriptions available on the v5r4 partition I
should use to compile my CL program on the v5r4 partition?

Thanks for suggestions.

Tom Garvey

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].