No, my constraints are:

 1. The TSOLIB must be in an environment where it works.

 2. Very little in CLIST.

 3. No AC(1) in assembler code

 4. Live within security rules
    a. No access to SAMPLIB
    b. No use of external code unless blessed by security

 5. Activation of libraries must be retained when starting a new
    ISPF logical screen

 6. If possible allow the user to allocate VB even though the
    ISPF concatenations are VB.

 7. Not licensed for PL/I

If the user drops back to READY and then starts ISPF again, it's up to him to 
invoke the setup script, either as a CMD() on the command or from an ISPF 
panel. TSOLIB is persistent but new logical screens disable ALTLIB and LIBDEF 
from other applications, and I'd like a way to automaticall enable them for the 
predefined ddnames.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר

________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Binyamin Dissen <bdis...@dissensoftware.com>
Sent: Sunday, December 31, 2023 4:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Checking status of multiple datasets in CLIST and REXX

So your constraints are only CLIST and REXX and no compiled programs?

Well, duplicates are allowed in concatenations.

So you might be able to skip the lookup.

There are ways you can remember that you already did this in a session, such
as allocating IDIDIT and doing an EXECIO against it to determine if it is
allocated.

On Sat, 30 Dec 2023 23:35:11 +0000 Seymour J Metz <sme...@gmu.edu> wrote:

:>I want to set up an environment that supports personal tools. I'd like to 
allow the users to create VB libraries, but if there is no way to retain ALTLIB 
and LIBDEF across START (ISPSTRT) then I'll stick to FB and reconcatenate.
:>
:>Performance is not an issue because the code would only run immediately after 
logon.
:>
:>--
:>Shmuel (Seymour J.) Metz
:>http://mason.gmu.edu/~smetz3
:>??? ?????????? ???
:>?????? ??????????? ???? ??????????
:>
:>________________________________________
:>From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Binyamin Dissen <bdis...@dissensoftware.com>
:>Sent: Saturday, December 30, 2023 12:33 PM
:>To: IBM-MAIN@LISTSERV.UA.EDU
:>Subject: Re: Checking status of multiple datasets in CLIST and REXX
:>
:>On Fri, 29 Dec 2023 14:47:29 +0000 Seymour J Metz <sme...@gmu.edu> wrote:
:>
:>:>I need to check whether any of a list of datasets exists and whether any of 
a list of ddnames is allocated. I'd rather not trap and parse the output of 
LISTALC and LISTCAT, and I'd rather not call LISTDSI for each one. Is there a 
simple way to do that in REXX, or would it be better to write a small service 
routine in assembler?
:>
:>:>I don't have a requirement to handle XTIOT.
:>
:>The elephant in the room - why?
:>
:>Perhaps there is a better way to do what you want.
:>
:>As you are worried about performance, it appears to be something that will
:>need to run quite often. How will you use this information?

--
Binyamin Dissen <bdis...@dissensoftware.com>
http://secure-web.cisco.com/1Mi3wk2UURVZKn7ciz5NSyYbyI170lxQoMoUpH4cZ9IMTGA-QbVm6TIQvlo3hgh9N4a4hist1PpENOCoMnRGGWKwmh7Hcik5FJL8x3k--tRMV0iQtmauNZSLYb2RxZ_C3nV9ZFVZhzHliWg7nDwFe7Jku078ANNvRR14-51P0om0RpeKcIWhj9g-_mkL0FCzs7BnXxuBf2u7bg07sWf9iMp7nSaJzp2oaXaSYrELDQjrzmmS79awvPtoi86vcHsGZDJ86uKIPfCjF0o1xGcepi8X3s8UwonKoXlPyS2luYDKpFlnLxCiqiOZC8u3yiSiWVxh_F_T9h8cOMlNYNC4MdEB45X8EGyzfBlcSGptJZ-62XycP3TNcH9zkTNJqSmCupnYS-hcnakUb8xHdZuGj3ylJzRKUQtygiOfdgGJM9OQ/http%3A%2F%2Fwww.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to