dynamic allocation of rexx/clist lib - bad news and good news

Harrington, Mark

unread,

Jul 30, 2002, 1:02:53 AM7/30/02

to

Thanks Ak ,
I tried that and it didn't seem to work. But you did reminded me of the
command(s) I had done previously.

FREE F(SYSPROC)
ALLOC F(SYSPROC) DSN(CLIST 'XXX.CLIST' XXX.ISR.ISRCLIB' 'XXX.TSOE.CLIST'
'MY.REXX.LIb') shr

now the new sysproc concatenation has my.rexx.lib in it.
remember to include all the needed system libraries or you'll be sunk.

p.s. option 6 is a good place to issue this from as the input field wraps
around to the next line.

-----Original Message-----
From: AK, Kannan (CORP, Consultant) [mailto:Kann...@CORPORATE.GE.COM]
Sent: Friday, July 26, 2002 3:35 PM
To: TSO-...@VM.MARIST.EDU
Subject: Re: dynamic allocation of rexx/clist lib

This will do.
"ALLOC FI(SYSUEXEC) DA('SYSAK.MY.EXEC') SHR"
"ALTLIB ACTIVATE USER(EXEC)"
"ALTLIB DISPLAY"

It brings CLIST/EXEC "onboard" under SYSUEXEC.

-----Original Message-----
From: Harrington, Mark [mailto:MHarr...@MEDNET.UCLA.EDU]
Sent: Friday, July 26, 2002 6:00 PM
To: TSO-...@VM.MARIST.EDU
Subject: dynamic allocation of rexx/clist lib

Hi all,
If I remember correctly I used to be able to allocate a library in a
particular users library list dyanmically in tso so that the user could have
SESSION access to my rexx/clist lib.... but i forgot how.
Am I correct ? If so could you tell me the commands ?

further detail - i want to go to a users terminal while the user is logged
on and add my library to the users lib list (serach chain ?) so the user can
have acces to my rexx lib for the session only.

thanx in advance

p.s. yes I know my pselling is bad. :)

m.h.

"LIFE IS A BATCH AND THEN YOU ABEND"

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

Thomas Conley

unread,

Jul 30, 2002, 4:59:04 PM7/30/02

to

Mark,

Try this from option 6 without all the other garbage:

address tso "ALTLIB ACT APPL(CLIST) DA('my.rexx.lib')

That should work fine.

Regards,
Tom Conley

----- Original Message -----
From: "Harrington, Mark" <MHarr...@MEDNET.UCLA.EDU>
Newsgroups: bit.listserv.tsorexx
Sent: Tuesday, July 30, 2002 1:02 AM
Subject: Re: dynamic allocation of rexx/clist lib - bad news and good news

> Thanks Ak ,
> I tried that and it didn't seem to work. But you did reminded me of the
> command(s) I had done previously.
>
> FREE F(SYSPROC)
> ALLOC F(SYSPROC) DSN(CLIST 'XXX.CLIST' XXX.ISR.ISRCLIB' 'XXX.TSOE.CLIST'
> 'MY.REXX.LIb') shr
>
>
> now the new sysproc concatenation has my.rexx.lib in it.
> remember to include all the needed system libraries or you'll be sunk.
>
> p.s. option 6 is a good place to issue this from as the input field
wraps
> around to the next line.
>
>
>

----------------------------------------------------------------------

Rob Hamilton

unread,

Aug 2, 2002, 5:18:05 PM8/2/02

to

Thomas Conley wrote:

> Mark,
>
> Try this from option 6 without all the other garbage:
>
> address tso "ALTLIB ACT APPL(CLIST) DA('my.rexx.lib')
>
> That should work fine.
>
> Regards,
> Tom Conley

My problem with ALTLIB is that there appear to be several EXECs around
our shop that use it to temporarily adjust the active, um, search path.
In my automatic exec that runs when I logon, I allocate SYSUEXEC and
SYSUPROC (if I remember correctly) with the necessary libraries, and then
I issue ALTLIB ACTIVATE USER(*). Then, after I start ISPF, I have to reissue
ALTLIB if I want to use my EXECs. THEN, if I get into SDSF, if I happen to
want to run an EXEC, I'd have to do it there too. And maybe again after
I get OUT of SDSF. Do I just need to reallocate SYSEXEC in my startup
EXEC if I want my EXECs in the list, because of all the other times people
reissue ALTLIB? Is there an orderly way for me to know when I'll need
ALTLIB before being able to use my EXECs when I've already issued it
once?

Thomas Conley

unread,

Aug 2, 2002, 7:06:25 PM8/2/02

to

----- Original Message -----
From: "Rob Hamilton" <rham...@cas.org>
Newsgroups: bit.listserv.tsorexx
Sent: Friday, August 02, 2002 5:18 PM
Subject: Re: dynamic allocation of rexx/clist lib - bad news and good news

>

> My problem with ALTLIB is that there appear to be several EXECs around
> our shop that use it to temporarily adjust the active, um, search path.
> In my automatic exec that runs when I logon, I allocate SYSUEXEC and
> SYSUPROC (if I remember correctly) with the necessary libraries, and then
> I issue ALTLIB ACTIVATE USER(*). Then, after I start ISPF, I have to
reissue
> ALTLIB if I want to use my EXECs. THEN, if I get into SDSF, if I happen to
> want to run an EXEC, I'd have to do it there too. And maybe again after
> I get OUT of SDSF. Do I just need to reallocate SYSEXEC in my startup
> EXEC if I want my EXECs in the list, because of all the other times people
> reissue ALTLIB? Is there an orderly way for me to know when I'll need
> ALTLIB before being able to use my EXECs when I've already issued it
> once?
>

Rob,

You shouldn't need to do this. Check your EXECUTIL settings to ensure that
SYSEXEC and SYSUEXEC will be used in addition to SYSPROC. Also, here's a
blip from the manual:

Under ISPF, ALTLIB works the same as in line mode TSO/E. However, if you use
ALTLIB under line mode TSO/E and start ISPF, the alternative libraries you
specified under line mode
TSO/E are unavailable until ISPF ends. <=== enhhh, thank you for playing.

When you use ALTLIB under ISPF, you can pass the alternative library
definitions from application to application by using ISPEXEC SELECT with the
PASSLIB operand; for example:

ISPEXEC SELECT NEWAPPL(ABC) PASSLIB

The PASSLIB operand passes the ALTLIB definitions to the invoked
application. When the invoked application completes and the invoking
application regains control, the ALTLIB
definitions that were passed take effect again, regardless of whether the
invoked application changed them. If you omit the PASSLIB operand, ALTLIB
definitions are not passed to the
invoked application.

</manual>

Regards,
Tom Conley