|
If you go waaaaaaaaaaaaaaay back to V3R6 there was a change in
putenv()/getenv() support. Up through V3R1 the environment variable
support was part of the CPA toolkit option of OS/400. Back in those days
you used the CRTCPAPGM to create your application and your application was
bound to QP0ZSRV01. In V3R6 the environment variable support was moved
into the base of OS/400 and applications were bound to QP0ZCPA.
There must be something else going on.
Bruce Vining
Simon Coulter
<shc@xxxxxxxxxxxx
om.au> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s+bvining=us.ibm. <midrange-l@xxxxxxxxxxxx>
com@xxxxxxxxxxxx cc
Subject
01/19/2006 07:59 Re: API location on V4Rx?
PM
Please respond to
Midrange Systems
Technical
Discussion
On 20/01/2006, at 12:35 PM, qsrvbas@xxxxxxxxxxxx wrote:
> That is why I asked. I had programming developed on I think V4R4
> (maybe 4.5) and restored the *PGM to a V5R1 system. The restore didn't
> succeed in giving me an executeable *PGM because the APIs (exports)
> couldn't be found in the referenced *SRVPGM. It was necessary to come
> up with a messy workaround.
That doesn't make sense. We use putenv and getenv all though some of
our code and have run the same *PGM objects on 440 to 530 with no
problems.
Restore doesn't check exports. They are only checked during compile and
run. Provide the exact error messages from the job log.
> My memory says it was getenv()/putenv() but I wanted to see if anybody
> could help. If those don't show up as I remember, then I'm going to do
> more digging to see if I can track down exactly what APIs were
> involved. Quite a while ago now, but it happened at the V5R1 upgrade.
I don't recall anything special about putenv/getenv on 510.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software AS/400 Technical Specialists
http://www.flybynight.com.au/
Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\
Fax: +61 3 9419 0175 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
--
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-2025 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.