× 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.



I've forgotten where I originally got this...

DCL VAR(&MSGDTA) TYPE(*CHAR) LEN(512)
DCL VAR(&PGM) TYPE(*CHAR) LEN(10)
DCL VAR(&ORGLIB) TYPE(*CHAR) LEN(10)

DLTF FILE(QTEMP/NOTFOUND)
MONMSG MSGID(CPF2105) EXEC(DO)
RCVMSG MSGTYPE(*EXCP)
ENDDO
OVRDBF FILE(QPPGMDMP) TOFILE(QTEMP/NOTFOUND)
DMPCLPGM
MONMSG MSGID(CPF0570) EXEC(DO)
RCVMSG MSGTYPE(*DIAG)
RCVMSG MSGTYPE(*EXCP) MSGDTA(&MSGDTA)
CHGVAR VAR(&PGM) VALUE(%SST(&MSGDTA 1 10))
CHGVAR VAR(&ORGLIB) VALUE(%SST(&MSGDTA 11 10))
ENDDO
DLTOVR FILE(QPPGMDMP)

...I've used this in so many places I've lost count.

cw


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Monday, November 07, 2011 12:49 PM
To: Midrange Systems Technical Discussion
Subject: Easy way for CL program to know what library it's in?

Is there an easy way for a CL program to know what library it's located in?

It needs to access a similarly named IFS directory, according to the library where it lives.

--
JHHL
--
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.