Charles,

As others have already pointed out, these are 36EE libraries. What I wanted
to add is that #LIBRARY itself is pretty empty. The real "meat" is in the
QSSP library (why? Don't know.). Anyway, if you have that library and are
feeling masochistic, look in the QS36PRC source PF to see how the developers
(Dick Mustain comes to mind) wrote system procedures/commands (all
interpretive) for the 34 and 36. Which is how a lot of us learned to write
flexible (but hairy) procedures back then. Reminds me of some DOS and Unix
commands I've seen.

Jerry C. Adams
IBM i Programmer/Analyst
We shall all be judged by history..and I shall write the history. -Winston
Churchill
--
A&K Wholesale
Murfreesboro, TN
615-867-5070

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Thursday, October 06, 2011 1:36 PM
To: Midrange Systems Technical Discussion
Subject: What's the purpose of the #LIBRARY library?

I've got a non-production system with a #LIBRARY library...

And a production system with
#CGULIB
#DFULIB
#DSULIB
#LIBRARY
#SDALIB
#SEULIB

Google has been useless, as the # is ignored...

So what's the story behind #LIBRARY? I'm thinking it's S36 or S38
related...

Thanks!
Charles

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.