Thanks Mike.
The apps I'm working with already have their own APPID, for profiles, etc.
As for PASSLIB, my understanding is that's required for the LIBDEFs to be
effective for the app, if they are issued before the SELECT NEWAPPL.
i.e.
a) in some menu: SELECT (%SETUPXXX)
SETUPXXX:
LIBDEF ...
LIBDEF ...
SELECT PANEL/etc. NEWAPPL(XXX) PASSLIB /* Actual app start */
/* LIBDEF cleanup */
b) in some menu: SELECT (%SETUPYYY) NEWAPPL(YYY)
SETUPYYY:
LIBDEF ...
LIBDEF ...
SELECT PANEL/etc. /* Actual app start */
/* LIBDEF cleanup (maybe automatic?) */
sas
On Fri, Mar 22, 2019 at 4:03 PM Mike Shaw wrote:
> On 3/22/2019 10:14 AM, Steve Smith wrote:
> >
>
> Steve,
>
> Forgot to mention that NEWAPPL is *required* when your application has
> its own application commands defined in an application command table in
> the ISPTLIB concatenation. ISPF can't honor the application commands if
> it can't find the application command table. The first four characters
> of the application command table name must match the value set by
> NEWAPPL().
>
> Mike Shaw
> MVS/QuickRef Support Group
> Chicago-Soft, Ltd.
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
--
sas
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN