LOGON REXX execs now possible!!!
Peter Vander Woude
If the user has keyed in a command on the TSO signon screen in the "COMMAND" field, is there any way to get the commands "queued" by the signon exec to execute first?
Thansk,
Peter I. Vander Woude
Mainframe Engineer
Harris Teeter, Inc.
>>> pinn...@FRONTIERNET.NET 10/25/2002 1:55:31 PM >>>
This morning I received an Email from Ken Burrow at Computer Sciences
Corporation with a recommendation that would allow a LOGON REXX exec to be
used instead of a LOGON CLIST. Due to the attention processing problems
documented by OY59638, I have always recommended using a LOGON CLIST. That
changes today. By using the 'queue "ISPF NOLOGO"' command instead of
'address tso "ISPF NOLOGO"' to invoke ISPF from the REXX exec, ISPF runs
under native TSO instead of REXX. That fixes the problem in OY59638. So I
would urge you all to convert your LOGON CLISTs to LOGON REXX execs, even if
you're not running Dynamic ISPF. Here is my sample TSOLOGON exec:
/* rexx */
/* trace i */
/*********************************************************************/
/* This exec replaces CLIST TSOLOGON. The "queue" command at the */
/* end of this exec allows ISPF to run natively under TSO instead of */
/* under REXX, which corrects the problem documented in OY59638. */
/* Thanks to Ken Burrow at Computer Sciences Corporation for this */
/* "queue" command method. */
/*********************************************************************/
msgsave = msg()
x = msg('OFF')
address tso "ALLOC FI(ISPPROF) DA('"userid()".ISPF.ISPPROF') OLD"
if rc <> 0 then
do
profdsn = userid().ISPF.ISPPROF
x = msg('ON')
address tso "ALLOC FI(ISPPROF) DA('"profdsn"') NEW CATALOG",
"CYLINDERS SPACE(1 1) DIR(45) DSORG(PO) RECFM(F B)",
"LRECL(80) BLKSIZE(0)"
if rc = 0 then
say "ISPF profile dataset'"profdsn"'created"
else
say "Unable to allocate ISPF profile dataset'"profdsn"'"
end
x = msg(msgsave)
queue "ISPF NOLOGO"
I'm excited to finally dump my last reason for using CLISTs. I'll be
following this up with an update to DISS, but I wanted to get this out ASAP.
Let me know if you have any questions or concerns.
Regards,
Thomas Conley, President
Pinnacle Consulting Group, Inc.
P: (585)720-0012
F: (585)723-3713
http://www.frontiernet.net/~pinnacle
Ryerse, Robin
exec name and provide the name of the exec/clist that will extend the
signon process. Of course the signon exec will have to honour the operand
provided. To make it universal, the tsologon proc would be coded with
PARM='%GETGOING &USERID' wherein GETGOING would do its thing then check for
the existence of the extender and if found stack it for execution.
My experience is that, yes, the user's command will execute if it is found
within the SYSPROC/SYSEXEC hierarchy. But, typically the signon exec is
building/modifying that hierarchy. Be aware that (on my system) the user's
specified command executes ahead of the but as well as the signon exec named
in the tsologon proc.
Peter Vander Woude
I am trying to find out how I can check for the existence of the command from the LOGON screen. And if there is on, how can I get it so that the command queued by the logon exec will execute BEFORE the command entered on the logon screen.
Here, those users that do use the LOGON screen command field mainly have LOGOFF coded in that spot. In our testing, if we queue the command and exit the exec used in the proc, the LOGOFF command gets executed first! We want to reverse that so that the command(s) queued by the exec get executed first and THEN the LOGOFF command gets executed.
Peter I. Vander Woude
Mainframe Engineer
Harris Teeter, Inc.
>>> robin....@EDS.COM 10/28/2002 10:32:16 AM >>>
<snip>
then check for
the existence of the extender and if found stack it for execution.
</snip>
Mark Zelden
<pwo...@HARRISTEETER.COM> wrote:
>Robin,
>
> I am trying to find out how I can check for the existence of the command
from the LOGON screen. And if there is on, how can I get it so that the
command queued by the logon exec will execute BEFORE the command entered on
the logon screen.
>
<snip>
Try this exec. Not sure if I picked it up from this list or another:
/*****************************************************************rexx*/
/* EXEC: LWALGCMD */
/* */
/* PURPOSE: To return the logon command from the TSO Logon Work */
/* Area (IKJEFLWA). This is filled in from the COMMAND==> */
/* prompt on the TSO logon screen. */
/* */
/* CHANGES: Created by R. Lamerand (10/27/92) */
/**********************************************************************/
ASXBPTR = storage(224,4)
ASXB = storage(d2x(c2d(ASXBPTR)+108),4)
LWA = storage(d2x(c2d(ASXB)+20),4)
LWALGCMD = storage(d2x(c2d(LWA)+186),80)
parse source . calltype .
if calltype = 'COMMAND' then
do
if strip(lwalgcmd) = "" then
say "You currently have no logon command."
else
say "Your current logon command is:" lwalgcmd
return
end
else
return lwalgcmd
--
+-------------------------------------------------------------------+
| Mark Zelden - z/OS and OS/390 Systems Engineer |
| mailto: mark....@zurichna.com |
| Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html |
+-------------------------------------------------------------------+
Gardiner, Roy
>
> I am trying to find out how I can check for the existence of the command
> from the LOGON screen. And if there is on, how can I get it so that the
> command queued by the logon exec will execute BEFORE the command entered
> on the logon screen.
>
> LOGOFF coded in that spot. In our testing, if we queue the command and
> exit the exec used in the proc, the LOGOFF command gets executed first!
> We want to reverse that so that the command(s) queued by the exec get
> executed first and THEN the LOGOFF command gets executed.
>
>
have the users enter the signon exec name in the COMMAND field. This means
that many different parameters and options can be provided and varied
without code change to the signon, and *everyone* can use the same signon.
Roy
The Royal Bank of Scotland plc ('the Bank') is regulated by the Financial
Services Authority and is a member of The Royal Bank of Scotland Marketing
Group. The only packaged products (life policies, unit trusts and other
collective investment schemes and stakeholder and other pensions) the Bank
advises on and sells are those of the Marketing Group, whose other members
are Royal Scottish Assurance plc and Royal Bank of Scotland Unit Trust
Management Limited, both regulated by the Financial Services Authority.
The Royal Bank of Scotland plc. Registered in Scotland No 90312. Registered
Office: 36 St Andrew Square, Edinburgh EH2 2YB.
Agency agreements exist between members of The Royal Bank of Scotland Group.
This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message from
your computer. Internet e-mails are not necessarily secure. The Royal Bank
of Scotland plc does not accept responsibility for changes made to this
message after it was sent.
Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the onward
transmission, opening or use of this message and any attachments will not
adversely affect its systems or data. No responsibility is accepted by The
Royal Bank of Scotland plc in this regard and the recipient should carry out
such virus and other checks as it considers appropriate.
Thomas Conley
From: "Peter Vander Woude" <pwo...@HARRISTEETER.COM>
Newsgroups: bit.listserv.ispf-l
Sent: Monday, October 28, 2002 9:18 AM
Subject: Re: LOGON REXX execs now possible!!!
> Tom,
>
> If the user has keyed in a command on the TSO signon screen in the
"COMMAND" field, is there any way to get the commands "queued" by the signon
exec to execute first?
>
Peter,
Not that I'm aware of. The command field on the TSO LOGON panel is always
executed AFTER the LOGON CLIST or exec. A trick I've used is to not issue
the ISPF command in the LOGON CLIST, which allows the command field on the
TSO LOGON panel to take over.
Tom