User ALTLIB activation?

[Metz, Seymour]

I have a LOGON proc that checks for userid.USER.EXEC and userid.USER.CLIST;
if it finds one, it allocates it to SYSUEXEC or SYSUPROC and issues the
corresponding ALTLIB ACTIVATE USER(...) command. However, the rules for
ALTLIB make it awkward in an ISPF environment. As of OS/390 2.5, is there
any facility to allow me to define a user CLIST or REXX library that will be
used from the READY prompt and also inherited by ISPF? I could put a command
on ISPSTART, but then it would be invoked every time that the user did a
SPLIT. I could free and reallocate the SYSEXEC and SYSPROC concatenations,
but I'd like to avoid the overhead.

I thought of using EXIT1, but the documentation doesn't make it clear
whether an ALTLIB issued there is in the ISPF environment or in the old TSO
environment.

Shmuel (Seymour J.) Metz

[Conlin, Ron]

We use the 'CONCATEM' program from CBT file270.

Regards.

Ronald L. Conlin
        Jackson National Life Insurance Company
        Technology Department  -  Systems Programmer

[Hawley Scott]

I think Ronald has the best solution for you. I've used
CONCAT instead of ALTLIB. Much easier to handle.
From Sam's file 001 (CBT Index)
CONCATEM TSO CMD ALLOCATE OR DEALLOCATE, * FILE 270
//* (CONCAT) CONCATENATE OR DECONCATENATE * FILE
270
//* THE GIVEN DATASET TO THE * FILE
270
//* GIVEN DDNAME. IN THE CASE OF * FILE
270
//* CONCATENATION, PLACE THE * FILE
270
//* GIVEN DATASET "AT THE TOP OF * FILE
270
//* THE STACK" OF ALL DATASETS * FILE
270
//* CONCATENATED TO THAT DDNAME. * FILE
270

>
> From: Conlin, Ron [SMTP:ron.c...@JNLI.COM]
> Sent: Thursday, December 31, 1998 9:18 AM
> To: ISP...@listserv.nd.edu
> Subject: Re: User ALTLIB activation?
> We use the 'CONCATEM' program from CBT file270.
>>

> -----Original Message-----
> From: Metz, Seymour [ <mailto:sm...@NSF.GOV>]
> Sent: Wednesday, December 30, 1998 5:45 PM
> To: ISP...@listserv.nd.edu
> Subject: User ALTLIB activation?
> I have a LOGON proc that checks for userid.USER.EXEC and
> userid.USER.CLIST;
> if it finds one, it allocates it to SYSUEXEC or SYSUPROC and issues the
> corresponding ALTLIB ACTIVATE USER(...) command. However, the rules for
> ALTLIB make it awkward in an ISPF environment.

<snip>

[Metz, Seymour]

That's my fallback if I can't make anything else work, but I'm trying to
minimize the reallocations.

Shmuel (Seymour J.) Metz

> -----Original Message-----
> From: Conlin, Ron [SMTP:ron.c...@JNLI.COM]
> Sent: Thursday, December 31, 1998 9:18 AM
> To: ISP...@listserv.nd.edu
> Subject: Re: User ALTLIB activation?
>
> We use the 'CONCATEM' program from CBT file270.
>

> Regards.
>
> Ronald L. Conlin
> Jackson National Life Insurance Company
> Technology Department - Systems Programmer
>
>
>

> -----Original Message-----
> From: Metz, Seymour [ <mailto:sm...@NSF.GOV>]
> Sent: Wednesday, December 30, 1998 5:45 PM
> To: ISP...@listserv.nd.edu
> Subject: User ALTLIB activation?
>
>
> I have a LOGON proc that checks for userid.USER.EXEC and
> userid.USER.CLIST;
> if it finds one, it allocates it to SYSUEXEC or SYSUPROC and issues the
> corresponding ALTLIB ACTIVATE USER(...) command. However, the rules for

[Metz, Seymour]

I've used it also; in fact, I've modified it (the original wouldn't work
with SWA above the line.) But my boss wants me to speed up logon, so I'm
looking for ways to avoid excessive reallocations.

Shmuel (Seymour J.) Metz

> -----Original Message-----
> From: Hawley Scott [SMTP:Haw...@TCE.COM]
> Sent: Thursday, December 31, 1998 10:02 AM
> To: ISP...@listserv.nd.edu
> Subject: Re: User ALTLIB activation?
>

[Mickey]

FWIW, my solution to the problem. I just require people to adhere to a
naming convention (i.e. userid.LIB.REXX, userid.LIB.PANELS etc. They are
created at the same time the userid is created. Then they are allocated
at the top of appropriate DD. Again, not the most elegant way, but it
sure works well, and requires the least overhead.

mickey