> ISPF application environment.

I'm not trying to set up an ISPF application environment.; I'm trying to set up 
a TSO user environment. I want to automatically activate user extensions to the 
standard conventions whenever the user has allocated libraries with appropriate 
names, e.g., userid,USER,EXEC, userid.USER.ISPP.

At other shops I've done it by reallocating the standard concatenations when 
the user libraries existed; I want an alternative to that.

> ISPF works as designed

NOVALUE is a REXX *style* issue  and has nothing to do with ISPF.

> everyone must follow these rules

There is no rule in REXX requiring the use of SIGNAL ON NOVALUE.

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

________________________________________
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Jon 
Perryman <jperr...@pacbell.net>
Sent: Thursday, December 28, 2023 9:55 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: ISPF setup macro

On Thu, 28 Dec 2023 02:01:54 +0000, Seymour J Metz <sme...@gmu.edu> wrote:

>I'm trying to use LIBDEF as an alternative to freeing and reallocating the 
>standard ISPF concatenations.

LIBDEF is commonly used to eliminate the need for reallocating standard ISPF 
DDs. There are situations where ISPxUSR is useful but I suspect most don't use 
it. I'm sure CBTTAPE.ORG has multiple examples of setting up the ISPF 
application environment.

>Yes, typo for ISPxUSR. The allocation is before starting ISPF. The 
>documentation shows
> those ddnames as being picked up automatically only for the DATASET keyword.

If you are developing an application, then I suggest avoiding ISPxUSR unless 
your requirements need it. Using LIBDEF for products means the datasets are 
freed when not in use.

>I'm aware of the contingent that advocates NOVALUE, but I don't agree with 
>that perspective.

ISPF works as designed and everyone must follow these rules or request they be 
changed.

>To clarify, my logon panel calls userid.AD.CLIST, which does allocations, 
>ALTLIB and TSOLIB before calling ISPF.

A requirement for products that I've worked on is that everything is contained 
within the REXX and nothing needs to be modified in TSO other than making the 
REXX available to the users who need it.

> I want to add, e.g., user panels, in a form that will persist across START 
> (ISPSTRT).

Persistence is typically achieved through REXX using the appropriate LIBDEFs. 
You would still need a REXX with permanent DD's because you should have a 
different ISPF ZAPPLID for your application.

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