I could use some TSO advice or REXX help; I'm looking to find a TSO/E REXX
function, if one exists, which says "this DD has these DSNs
allocated/concatenated to it" and then a TSO statement which says "Add this
file [my REXX Library] to the concatenation for SYSEXEC [or SYSPROC]."
Is anyone out there doing anything like this? I'm not getting any joy from
the keyword searches I've tried.
--
--Phil Sevetson
IBM Certified Solutions Expert -- DB2 V7.1 Database Administration for
OS/390;
IBM Certified Database Administrator -- DB2 UDB V8.1 for z/OS;
Oracle Certified Associate (OCA), Oracle 9i
----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX
TSO ISRDDN
This will list the datasets allocated to your TSO session by DD Name and
DSN.
This should get you started.
Chuck
Additionally, withing the ISRDDN facility, there is the primary
command CLIST which will generate a file called yourid.ISRDDN.CLIST.
This file is a set of allocate statements which you'll find useful.
Perhaps you already discovered that in the help panels for ISRDDN.
Dave
-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On Behalf
Of Philip Sevetson
Sent: Tuesday, July 03, 2007 1:41 PM
To: TSO-...@VM.MARIST.EDU
Subject: Re: Allocating the REXXLIB to SYSEXEC via REXX
Exactly the kind of thing I was looking for. Thanks.
On 7/3/07, Hardee, Charles H <Charles...@ca.com> wrote:
>
> I would suggest trying the following command:
>
> TSO ISRDDN
>
> This will list the datasets allocated to your TSO session by DD Name
> and DSN.
> This should get you started.
>
> Chuck
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
For adding your own CLIST/EXEC PDS to SYSPROC/SYSEXEC, look up the TSO
ALTLIB command. I use it in my tsouserid.SIGNON exec so I get them as soon
as I'm logged on to TSO.
TSO HELP ALTLIB has a lot of info in a short space.
ISTR there may be a RECONCAT command (a REXX exec IIRC) somewhere on one of
the CBT files, but I think ALTLIB will do the trick for you.
HTH
Peter
This message and any attachments are intended only for the use of the addressee and
may contain information that is privileged and confidential. If the reader of the
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.
if bpxwdyn("alloc fi(tmp) da(uid.my.rexx) shr msg(s99.)")=0 then
call bpxwdyn "concat ddlist(sysexec,tmp) msg(s99.)"
if result /= 0 then
do
say "Error. BPXWDYN failed, RC="result
do i=1 to s99.0
say s99.i
end
end
James Campbell
>
> Date: Tue, 3 Jul 2007 13:12:04 -0400
> From: Philip Sevetson <psev...@GMAIL.COM>
> Subject: Allocating the REXXLIB to SYSEXEC via REXX
>
> I have an extremely simpleminded REXX/TSO proc, from a former employer, that
> allocates my REXX lib to SYSEXEC. It won't work at my current employer
> because (a) we don't have the same datasets as I have hardcoded in the ALLOC
> statement, and (b) I can't figure out how to tell what we _do_ have
> allocated to FI(SYSEXEC). (Lack of TSO knowledge, I blush to admit)
>
> I could use some TSO advice or REXX help; I'm looking to find a TSO/E REXX
> function, if one exists, which says "this DD has these DSNs
> allocated/concatenated to it" and then a TSO statement which says "Add this
> file [my REXX Library] to the concatenation for SYSEXEC [or SYSPROC]."
>
> Is anyone out there doing anything like this? I'm not getting any joy from
> the keyword searches I've tried.
>
> --
> --Phil Sevetson
> IBM Certified Solutions Expert -- DB2 V7.1 Database Administration for
> OS/390;
> IBM Certified Database Administrator -- DB2 UDB V8.1 for z/OS;
> Oracle Certified Associate (OCA), Oracle 9i
>
----------------------------------------------------------------------
> Date: Tue, 3 Jul 2007 16:53:52 -0400
>
> For adding your own CLIST/EXEC PDS to SYSPROC/SYSEXEC, look up the TSO
> ALTLIB command. I use it in my tsouserid.SIGNON exec so I get them as soon
> as I'm logged on to TSO.
>
I had believed that ALTLIB is effective only if issued in the same
ISPF split in which you wish to run your EXEC, and that issuing
it in the SIGNON is like issuing it from the READY prompt, effective
in neither ISPF split. Do I misunderstand? Or are you not concerned
with ISPF, but only with TSO READY commands?
Since the scope of ALTLIB is one ISPF split, I'd expect to be able to
activate different ALTLIBs in the respective ISPF splits. Is this
possible? How can I avoid contention for the SYSUEXEC DDNAME?
-- gil
--
StorageTek
INFORMATION made POWERFUL
EXEC#1 must be named ISRSETUP. It looks like this:
/* REXX Query/Set environment specific profile */
call altlibs
address 'TSO'
'SUBCOM ISPEXEC'
if rc = 0 then
do
queue '%ISPEXEC SELECT PGM(ISRUDA) PARM(ISRWORK) SCRNAME(WORK)'
/* queue '%ISPEXEC SELECT Panel(ISR@PRIM) ' */
exit
end
if arg() then queue arg(1)
else queue 'ISPSTART CMD(%ISRSETUP) NEWAPPL(ISR)'
exit
EXEC#2 is named ALTLIBS. It looks like this:
address 'TSO'
parse source . exec_type .
do_display = exec_type = 'COMMAND'
call outtrap 'M.'
'ALTLIB DISPLAY'
call outtrap 'OFF'
if exec_type = 'FUNCTION' then
do
parse var m.2 '=' dd_names .
do m# = 3 to m.0; parse var m.m# '=' ?; dd_names = dd_names ?; end
return dd_names
end
call dsn4dd 'SYSUEXEC'
if rc > 0 then
do
do i = 2 to m.0 until dd_name = 'SYSUEXEC'
parse var m.i 'DDNAME=' dd_name
end
if dd_name \= 'SYSUEXEC' then
do
do_display = 1
'ALTLIB ACTIVATE USER(EXEC)'
end
end
call dsn4dd 'SYSUPROC'
if rc > 0 then
do
do i = 2 to m.0 until dd_name = 'SYSUPROC'
parse var m.i 'DDNAME=' dd_name
end
if dd_name \= 'SYSUPROC' then
do
do_display = 1
'ALTLIB ACTIVATE USER(CLIST)'
end
end
if do_display then call trap 'ALTLIB DISPLAY'
return 0
EXEC#3 is named ISPEXEC. It simply issues a what ISPEXEC command is
passed to it.
EXEC#4 is named function DSN4DD. I have posted it several times.
Robin Ryerse
-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On Behalf
Of Paul Gilmartin
Sent: July 4, 2007 3:37 PM
To: TSO-...@VM.MARIST.EDU
> Date: Wed, 4 Jul 2007 16:13:00 -0400
>
> It takes a minimum of 4 execs all of which must be within your SYSEXEC
> (or SYSPROC) concatenation. Start your initial ISPF session from TSO
> with the ISRSETUP exec. The beauty is that all subsequent ISPF splits
> will automatically use that startup.
>
I'm baffled (and quite naive about ISPF). How does it work? More
comments in the code would help. And an example. Suppose that in
split 1 I want to use 'USERID.SYSEXEC1' as my SYSEXEC library, and
in split 2, to use 'USERID.SYSEXEC2'. What exactly must I do?
> -----Original Message-----
> Of Paul Gilmartin
> Sent: July 4, 2007 3:37 PM
>
> Since the scope of ALTLIB is one ISPF split, I'd expect to be able to
> activate different ALTLIBs in the respective ISPF splits. Is this
> possible? How can I avoid contention for the SYSUEXEC DDNAME?
Thanks,
The launch of a TSO environment establishes an ALTLIB environment as per
the SYSEXEC and SYSPROC allocations. I have never understood why the
automatic ALTLIB does not exetend to the SYSUEXEC and SYSUPROC
allocations as well. The exec named ALTLIBS which I posted covers that
"deficiency".
Each allocation (including SYSEXEC) for the hosting TSO session is
inherited by each ISPF environment. You can not have independent
SYSEXEC's per ISPF session. You could however suspend usage of SYSEXEC
via:
ALTLIB DEA SYSTEM(EXEC) and/or switch to an alternate SYSUEXEC
allocation via:
ALTLIB ACT USER(EXEC)
This switching tehnique may be the reason why the IBM code does not
automatically use SYSUEXEC and SYSUPROC.
Sorry about the lack of documentation. The execs were written by me for
me and I understand them. I will say however that the DSN4DD references
can be replaced by "LISTDSI ddname FILE" and check "result" instead of
"rc".
To understand what ISRSETUP accomplishes, presume the TSO LOGON
processing has done all the allocations it will require and is at the
Ready prompt. The execution of ISRSETUP will first ensure a "full"
ALTLIB environment is available for the base TSO session. The exec then
starts ISPF and tells ISPF to use ISRSETUP for that launch. As ISPF
launches, it executes ISRSETUP a second time. This second invocation is
required because the secondary environment (i.e. ISPF) does not have the
full ALTLIB settings.
Robin Ryerse
-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On Behalf
Of Paul Gilmartin
Sent: July 4, 2007 7:44 PM
To: TSO-...@VM.MARIST.EDU
Subject: Re: Allocating the REXXLIB to SYSEXEC via REXX
>I have an extremely simpleminded REXX/TSO proc, from a former employer, that
>allocates my REXX lib to SYSEXEC. It won't work at my current employer
>because (a) we don't have the same datasets as I have hardcoded in the ALLOC
>statement, and (b) I can't figure out how to tell what we _do_ have
>allocated to FI(SYSEXEC). (Lack of TSO knowledge, I blush to admit)
>
>I could use some TSO advice or REXX help; I'm looking to find a TSO/E REXX
>function, if one exists, which says "this DD has these DSNs
>allocated/concatenated to it" and then a TSO statement which says "Add this
>file [my REXX Library] to the concatenation for SYSEXEC [or SYSPROC]."
>
>Is anyone out there doing anything like this? I'm not getting any joy from
>the keyword searches I've tried.
http://web.tampabay.rr.com/mvsrexx/REXX/attach.txt
(change Arabic number to Roman numeral to email)
I get told that I'm not authorised to view that page :-(
Hmmm..... Try http://web.tampabay.rr.com/mvsrexx/REXX/ and then select ATTACH
from the body.
Can anyone help me with this..
I need to update a production file using my REXX code.
And the production file requires an EID to be activated for Edit.
Is there any way that I can activate EID using REXX.
Thanks for your help in Advance.
--Binoj--
What is an EID? I've never heard of that. Edit Initial D????
--
John McKown
Senior Systems Programmer
HealthMarkets
Keeping the Promise of Affordable Coverage
Administrative Services Group
Information Technology
The information contained in this e-mail message may be privileged
and/or confidential. It is for intended addressee(s) only. If you are
not the intended recipient, you are hereby notified that any disclosure,
reproduction, distribution or other use of this communication is
strictly prohibited and could, in certain circumstances, be a criminal
offense. If you have received this e-mail in error, please notify the
sender by reply and delete this message without copying or disclosing
it.
Enter your password ===>
EID Prefix to use ===> Enter the EID Prefix to use
UID string ===> EGMVM... UID string to use
Reason for EID usage
===> ___________________________________________________________
I guess this is some mechanism to provide a few more privileges to the
ACF2 rules assigned to userid.
Thanks
--Binoj--
-----Original Message-----
From: TSO REXX Discussion List [mailto:TSO-...@VM.MARIST.EDU] On Behalf
Of McKown, John
Sent: Thursday, October 18, 2007 11:31 PM
To: TSO-...@VM.MARIST.EDU
Ah, thanks. We use RACF and don't have any such thing.
Robin Ryerse
Mainframe Services EDS Canada
Phone:(905)528-2511.3174
SAY 'EID EIMAMP2 required - EID Panel coming up'
ADDRESS ISPEXEC "SELECT CMD(%EID)" /* Turn on EID */