× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




If the progam is compiled on the production system, the code works. The
name of the AS/400 is retreived as expected.

The problem only occurs when the souce code is compiled on the
development AS/400 and the program object is moved from the development
AS/400 to the production AS/400. On the production AS/400, the code
executes, but the system name is not retreived.

Ron

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of DeLong, Eric
Sent: Thursday, November 06, 2008 6:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: System Name - SQL current server

I might expect that your production system does not have a *LOCAL entry
in WRKRDBDIRE...

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hudson, Ron
Sent: Thursday, November 06, 2008 2:44 PM
To: Midrange Systems Technical Discussion
Subject: System Name - SQL current server

I couldn't find it in the recent archives (July/Aug), but I remembered
seeing this trick to get the system name.

C/exec sql
C+ values current server
C+ into :SysName
C/end-exec

It works great on the system it is compiled on. But when I move the
program object to production, it quits working.

I've moved the object using the following methods, none work:
1) Implementer (David ??)
2) ASNET (SSA product)
3) Save program to a *SAVF and use SNDNETF.

Sending the source to the production box and compiling is the only way
I've gotten it to work.

Anyone know any tricks to get around this. Compiling on a production
box is not long term solution.

Thanks
Ron

**********************
** LEGAL DISCLAIMER **
**********************

This E-mail message and any attachments may contain legally privileged,
confidential or proprietary information. If you are not the intended
recipient(s), or the employee or agent responsible for delivery of this
message to the intended recipient(s), you are hereby notified that any
dissemination, distribution or copying of this E-mail message is
strictly prohibited. If you have received this message in error, please
immediately notify the sender and delete this E-mail message from your
computer.
--
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 thread ...

Follow-Ups:
Replies:

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

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.