If you were going to cover all the possible bases, you would need to do the:
1. VOC
2. OPEN 'CTLG' and read that. This covers 'LOCAL' catalogs
3. CREATE a temporary VOC entry where
att1 is 'DIR'
att2 is @UDTHOME/sys/CTLG/(first letter of program name)
OPEN this file and read using program name as the Key
Hoepfully somebody will come up with something simpiliar. But these are the
three places I know of where object code can live.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of David Wolverton
Sent: Thursday, March 15, 2007 9:20 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] [UD] CALL @progname
I am writing some code that will execute a variable passed in "progname"
using CALL @progname.
Question - what is the 'best' way to know that "progname" exists before I
attempt the CALL.
I thought about reading the VOC, but if it's globally cataloged, that won't
work.
I could read the VOC and then the CTLGTB -- but that was two reads just to
'know' the routine wasn't going to blow up. Is there a more efficient or
systemic way to do this?
**Typically** "progname" will reference a real program, so this testing is
'overhead' for 99.9% of the time - but if someone were to pass in a bad
'progname', I want to be more graceful (and secure!) just falling over.
Since some of the calls will come from 'web connected' clients, and some of
the clients may not know for sure that the host cannot handle the request -
if the client has a different function list than the host at that point and
time... I'm just trying to plan for 'worst case'.
How do others handle CALL @
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
