|
Unfortunately, the command returns what is defined as the default (usually
QS36F), not what the current files library is.
Jerry C. Adams
IBM i Programmer/Analyst
A die-hard Republican was interviewed on his 96th birthday. "You've seen
many changes," said the reporter. "Yes," replied the old man, "and I was
against every damned one of them."
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, September 13, 2011 2:18 PM
To: Midrange Systems Technical Discussion
Subject: Re: 36EE Files Library Determination
RTVS36A
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Jerry C. Adams" <midrange@xxxxxxxx>
To: "Midrange-L" <midrange-l@xxxxxxxxxxxx>
Date: 09/13/2011 12:44 PM
Subject: 36EE Files Library Determination
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Hate to be old school (trust me!), but is there an API that will return
the
value of the Files Library for the 36EE? In OCL one can use ?FLIB? to
retrieve the default library into which objects will be created or
retrieved. I checked the API list (we are on 5.1), but couldn't find
anything that applied, but lots of APIs that returned the library lists.
I wrote an RPG IV program that reads through the user portion of the
library
list. If I find QS36F (the normal value), I assume that I'm in
production.
Otherwise, I look for TSTQS36F, which is my test environment version and,
if
found, assume I'm in test. If I can't find either (or I find both), I
assume the situation is fubar and abort.
Just would like a more accurate method.
Jerry C. Adams
IBM i Programmer/Analyst
When they write a history of the significant events that have happened, I
hope they spell my name right.
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
--
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.
--
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.