|
when you compile to *PRV, it *only* changes the way the program is
compiled, not the file structure it's compiled against. the APIs will
protect you from these types of issues. so you have 3 choices, either
write your own DSPOBJD to the "old" format, recompile/modify the programs
to use the changed format or fix it for good by rewriting to use the APIs.
should you choose option 1 or 2 be forewarned that should the file change
again in future releases you'll have to go through the same headache
again.
Thanks,
Tommy Holden
From:
Jack Kingsley <iseriesflorida@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:
10/08/2009 09:47 AM
Subject:
Re: DSPOJBD (field length changes) V5R3 to V5R4 help needed
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
Outside of converting it to using API's is there an alternative solution,
I
didn't want to have to rewrite it, if not then I will research the api
route.
On Thu, Oct 8, 2009 at 10:17 AM, <rob@xxxxxxxxx> wrote:
Yes, stop using DSPOBJD to an output file. Use apis like
- List Objects
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apis/quslobj.htm
- Open list of objects
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apis/qgyolobj.htm
- Retrieve Object Description
http://publib.boulder.ibm.com/infocenter/iseries/v6r1m0/topic/apis/qusrobjd.htm
V5R4
Multiple version support is one of the first reasons I first started
using api's.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From:
Jack Kingsley <iseriesflorida@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <MIDRANGE-L@xxxxxxxxxxxx>
Date:
10/08/2009 10:07 AM
Subject:
DSPOJBD (field length changes) V5R3 to V5R4 help needed
Sent by:
midrange-l-bounces@xxxxxxxxxxxx
Is there a workaround for a cl program that is creating a file under
(dspobjd to an outfile) where the field lenghts are different. I havelist
compiled a program to run *PRV but when I run the program on the V5R3
machine it bombs. Thanks.
--
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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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 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 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.