Shared profile question:
Joe Aulph
With the recent discussion on sharing ISPF Profile data set, I thought I'd
give it a try.
We are at z/OS 1.10 and have the typical (default) ISPCONFG settings for
profile sharing with the necessary PROFILE_SHARING = YES, setting.
Everything seems to work just as it ought to except for one thing. When I
go into shared mode I lose the use of our customized 'SITE' ISPF Commands.
The default ISPF Commands are all available but my customized table, not
there!
Has any one else seen this, is there something I've missed?
Thanks in advance!
Cheers,
Joe Aulph,
Joe_...@nsrc.myflorida.com
Northwood Shared Resource Center
Senior Systems Programmer:
850-487-8945
Pinnacle
From: "Joe Aulph" <joe_...@NSRC.MYFLORIDA.COM>
Newsgroups: bit.listserv.ispf-l
Sent: Monday, November 23, 2009 2:36 PM
Subject: Shared profile question:
> Hello list,
>
> With the recent discussion on sharing ISPF Profile data set, I thought I'd
> give it a try.
> We are at z/OS 1.10 and have the typical (default) ISPCONFG settings for
> profile sharing with the necessary PROFILE_SHARING = YES, setting.
>
> Everything seems to work just as it ought to except for one thing. When I
> go into shared mode I lose the use of our customized 'SITE' ISPF Commands.
> The default ISPF Commands are all available but my customized table, not
> there!
>
> Has any one else seen this, is there something I've missed?
>
Joe,
Make sure you run ISPCCONF and specify SITE for your site commands table.
Grab my "Configuring ISPF for Fun and Profit" session at my web site below.
Regards,
Thomas Conley, President/CEO
Pinnacle Consulting Group, Inc.
59 Applewood Drive
Rochester, NY 14612-3501
P: (585)720-0012
F: (585)723-3713
http://home.roadrunner.com/~pinncons/
Mark Zelden
wrote:
>Hello list,
>
>With the recent discussion on sharing ISPF Profile data set, I thought I'd
>give it a try.
>We are at z/OS 1.10 and have the typical (default) ISPCONFG settings for
>profile sharing with the necessary PROFILE_SHARING = YES, setting.
>
>Everything seems to work just as it ought to except for one thing. When I
>go into shared mode I lose the use of our customized 'SITE' ISPF Commands.
>The default ISPF Commands are all available but my customized table, not
>there!
>
>Has any one else seen this, is there something I've missed?
>
>Thanks in advance!
>
>Cheers,
>
>Joe Aulph,
>
>Joe_...@nsrc.myflorida.com
>Northwood Shared Resource Center
>Senior Systems Programmer:
I'm still running with it (for me only) in my sandbox sysplex. I see the
my SITE commands (called SITECMDS). Do you see it listed in 3.9?
As I indicated before... this seems like it holds the same value as
excluding SPFEDIT for the ISPF profile data set name in GRS/MIM,
only it is more flexible since the ISPF profile name doesn't matter.
I am running with "KEEP" for all the various conflict options.
I haven't noticed any other issues than the ones I discussed previously.
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark....@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
Joe Aulph
Thanks, that looks like it.
I'm evidently not working with an up to date copy of our configuration.
Time to dig and find my current one, ahh.. the pit falls of taking over
support for the retired guy.....
Thanks again,
Joe Aulph,
Joe_...@nsrc.myflorida.com
Northwood Shared Resource Center
Senior Systems Programmer:
Pinnacle
<pinncons@ROCHEST
ER.RR.COM> To
Sent by: ISPF ISP...@LISTSERV.ND.EDU
discussion list cc
<ISPF-L@LISTSERV.
ND.EDU> Subject
Re: Shared profile question:
11/23/2009 02:45
PM
Please respond to
ISPF discussion
list
<ISPF-L@LISTSERV.
ND.EDU>
----- Original Message -----
From: "Joe Aulph" <joe_...@NSRC.MYFLORIDA.COM>
Newsgroups: bit.listserv.ispf-l
Sent: Monday, November 23, 2009 2:36 PM
Subject: Shared profile question:
> Hello list,
>
> With the recent discussion on sharing ISPF Profile data set, I thought
I'd
> give it a try.
> We are at z/OS 1.10 and have the typical (default) ISPCONFG settings for
> profile sharing with the necessary PROFILE_SHARING = YES, setting.
>
> Everything seems to work just as it ought to except for one thing. When I
> go into shared mode I lose the use of our customized 'SITE' ISPF
Commands.
> The default ISPF Commands are all available but my customized table, not
> there!
>
> Has any one else seen this, is there something I've missed?
>
Joe,
Make sure you run ISPCCONF and specify SITE for your site commands table.
Grab my "Configuring ISPF for Fun and Profit" session at my web site below.
Regards,
Thomas Conley, President/CEO
Pinnacle Consulting Group, Inc.
59 Applewood Drive
Rochester, NY 14612-3501
P: (585)720-0012
F: (585)723-3713
http://home.roadrunner.com/~pinncons/
NOTICE: Florida has a broad public records law. Most written
communications to or from state officials are public records that will be
disclosed to the public and the media upon request. E-mail communications
may be subject to public disclosure.
Pedro Vera
into your ISPTLIB concatenation. I do not think it should be affected by
a shared profile.
Pedro Vera
IMS Tools
Rob Zenuk
of Shared Profiles. One of the documented issues was the "problem" with
SDSF defaulting to the USERID as the default EMCS console for ULOG and all
commands. We wanted our implementation to be seamless for all our users.
So, I wrote a little wrapper EXEC for SDSF called SDSFSHR.
The EXEC simply suffixes the USERID with the &SYSCLONE value to create the
EMCS console ID and passes in a SET CONSOLE command as SDSF is invoked.
This works great for USERID's that are 6 characters or less. If your ID's
are 7 characters, then you will need an alternate approach to &SYSCLONE.
You might be able to use the first or last character of &SYSCLONE. However,
for us and our LPAR naming conventions, this would not work.
The idea is to rename the default IBM ISPF command table entry for SDSF to
something else (SDSFIBM) and replace the existing SDSF command table entry
with this REXX EXEC. The new ISPF Command Table entries are:
SDSF 0 SELECT CMD(%SDSFSHR &ZPARM) NOCHECK
SDSFIBM 0 SELECT PGM(ISFISP) NEWAPPL(ISF) NOCHECK PARM(&ZPARM)
SDSF now points to the SDSFSHR EXEC and passes the &ZPARM straight
through. SDSFSHR ends up using the original SDSF command (now called SDSFIBM) to
do what it has always done. This handles things for everyone that uses the
ISPF SDSF command. For folks that use SDSF from a menu option, the &ZSEL
option must now use SDSFSHR. Obviously, SDSFSHR must be in your SYSEXEC
(I'm not a fan of SYSPROC for REXX EXEC's - messes up my comment boxes).
&ZSEL = TRANS ( TRUNC (&ZCMD,'.')
.
.
S,'CMD(%SDSFSHR) NOCHECK'
.
.
*,'?' )
Here is the code (free, use at your own risk, no warranties - but I will
answer questions). Sorry if this lost the indentation during transmission.
If you don't want to re-indent it and want an indented copy sent to you,
please email me off-list. However, if you end up using this and end up in
Phoenix someday, I expect you to drop me a line and buy me a beer... ;-)
/*********************************************************************/
/* REXX */
/*********************************************************************/
/* Purpose: Launch SDSF and set a default LPAR specific CONSOLE ID */
/*-------------------------------------------------------------------*/
/* Syntax: SDSFSHR cmd */
/*-------------------------------------------------------------------*/
/* Parms: CMD - Any SDSF or MVS command (optional) */
/* */
/* Notes: Change variable ISPFSDSF to the ISPF command used for the */
/* original IBM SDSF command in the ISPF Command Table */
/* */
/* If IBM adds more primary commands to SDSF, add them to */
/* the SDSFCMDS variable. Current as of z/OS 1.10. */
/* */
/* Variable DEFAULT contains the default command for all */
/* users, currently this only sets the CONSOLE ID to support */
/* Shared Profiles by suffixing the EMCS Console name with */
/* the SYSCLONE value. */
/* */
/* If a command is not recognized as an SDSF command it is */
/* assumed it is intended for the CONSOLE and will be */
/* appropriately prefixed with '/' and passed to ULOG. */
/* */
/* Supports all techiques to launch SDSF including command */
/* chaining. */
/* */
/*********************************************************************/
/* Change Log */
/* */
/* Author Date Reason */
/* -------- --------- ----------------------------------------- */
/* R. Zenuk Dec 2003 Initial Creation */
/* R. Zenuk 11/02/09 Updated with unique Console for Sharing */
/* R. Zenuk 11/11/09 Modified for general use (ver 1.1.0) */
/* R. Zenuk 11/12/09 Fixed SDSF chaining problem (ver 1.1.1) */
/* */
/*********************************************************************/
/* SDSF command in the ISPF Command Table */
/*********************************************************************/
ispfsdsf = 'SDSFIBM'
/*********************************************************************/
/* Valid SDSF commands (not sent to the ULOG) */
/*********************************************************************/
sdsfcmds = 'DA I O H ST LOG SR MAS JC SE RES ENC PS INIT PR PUN RDR',
'LINE NODE SO SP RM CK U ULOG ACTION APPC DEST FILTER OWNER',
'PRE PREFIX RSYS SELECT SYSID SYSNAME ARR ARRANGE ? SET',
'SORT WHO PRI PRINT COLS RESET INPUT LOGLIM ABEND RETRIEVE',
'QUERY TRACE F FIND FINDLIM LOCATE UP DOWN LEFT RIGHT TOP',
'BOTTOM NEXT PREV HELP TUTOR BOOK COLSHELP REXXHELP'
/*********************************************************************/
/* Build the DEFAULT command string */
/*********************************************************************/
/* Set the CONSOLE ID using SYSCLONE */
/*********************************************************************/
default = 'SET CONSOLE' userid()||mvsvar('SYSCLONE')
/*********************************************************************/
/* DO NOT CHANGE ANYTHING BELOW THIS LINE */
/*********************************************************************/
version = '1.1.1'
/*********************************************************************/
/* Accept an optional command */
/*********************************************************************/
arg cmdline
/*********************************************************************/
/* Get this EXEC's name */
/*********************************************************************/
parse upper source . . execname .
/*********************************************************************/
/* Get the full command line string including delimiters using ISPF */
/* RETRIEVE (pulls from the ISPF Command Stack) */
/*********************************************************************/
retcmd = 'RETRIEVE'
address ISPEXEC "DISPLAY PANEL(ISRTSO) COMMAND(RETCMD)"
/*********************************************************************/
/* If the command is prefixed with EXEC, SDSF or TSO execname then */
/* parse out the command portion of the retrieved command */
/*********************************************************************/
select
when translate(word(zcmd,1)) = 'EXEC' |,
translate(word(zcmd,1)) = 'SDSF' |,
translate(word(zcmd,1)) = 'SDSX' then
parse var zcmd . cmd
when translate(word(zcmd,1)) = 'TSO' &,
translate(word(zcmd,2)) = execname then
parse var zcmd . . cmd
when translate(left(zcmd,5)) = 'SDSF;' then
do
parse var zcmd 'SDSF;' cmdline
cmd = cmdline
end
otherwise nop
end
/*********************************************************************/
/* Get the ISPF Delimeter */
/*********************************************************************/
address ISPEXEC "VGET (ZDEL)"
/*********************************************************************/
/* If no CMD input, pass the DEFAULT command as simulate ENTER */
/*********************************************************************/
if cmdline = '' then
cmd = ispfsdsf||zdel||default||zdel||zdel
else
/*********************************************************************/
/* CMD provided */
/*********************************************************************/
do
/*********************************************************************/
/* Parse the command string if it has ';' in it */
/*********************************************************************/
if pos(';',cmd) <> 0 then
/*********************************************************************/
/* If so, parse out the first word to see if it is an SDSF command */
/*********************************************************************/
parse var cmd firstword ';' the rest
else
parse var cmd firstword
/*********************************************************************/
/* Is it an SDSF command? */
/*********************************************************************/
if wordpos(translate(word(firstword,1)),sdsfcmds) <> 0 then
/*********************************************************************/
/* YES, use the SDSF command string provided */
/*********************************************************************/
cmd = cmd||zdel||zdel
else
/*********************************************************************/
/* NO, assume this is a CONSOLE command and pass it to the SDSF ULOG */
/* command and scroll right 40 to see entire results */
/*********************************************************************/
cmd = 'ULOG'||zdel||'/'cmd||zdel||'RIGHT 40'
/*********************************************************************/
/* Build entire command string */
/*********************************************************************/
cmd = ispfsdsf||zdel||default||zdel||cmd
end
/*********************************************************************/
/* Stuff the command in the COMMAND buffer */
/*********************************************************************/
address ISPEXEC "DISPLAY PANEL(ISPBLANK) COMMAND(CMD)"
if RC <> 0 then
do
zedlmsg = 'Error issuing command:' cmd', RC='RC
address ISPEXEC "SETMSG MSG(ISRZ000)"
end
Hope this helps,
Rob
In a message dated 11/23/2009 1:16:23 P.M. US Mountain Standard Time,
mark....@ZURICHNA.COM writes:
On Mon, 23 Nov 2009 14:36:28 -0500, Joe Aulph
<joe_...@NSRC.MYFLORIDA.COM>
wrote:
>Hello list,
>
>With the recent discussion on sharing ISPF Profile data set, I thought I'd
>give it a try.
>We are at z/OS 1.10 and have the typical (default) ISPCONFG settings for
>profile sharing with the necessary PROFILE_SHARING = YES, setting.
>
>Everything seems to work just as it ought to except for one thing. When I
>go into shared mode I lose the use of our customized 'SITE' ISPF Commands.
>The default ISPF Commands are all available but my customized table, not
>there!
>
>Has any one else seen this, is there something I've missed?
>
>Thanks in advance!
>
>Cheers,
>
>Joe Aulph,
>
>Joe_...@nsrc.myflorida.com
>Northwood Shared Resource Center
>Senior Systems Programmer:
Pinnacle
From: "Rob Zenuk" <Robz...@AOL.COM>
Newsgroups: bit.listserv.ispf-l
Sent: Monday, November 23, 2009 5:06 PM
Subject: Re: Shared profile question:
<snip>
> (I'm not a fan of SYSPROC for REXX EXEC's - messes up my comment boxes).
>
<snip>
Rob,
The only good reason for putting Rexx execs in SYSPROC is so that they can
be cached by VLF, by using the IKJEXEC class in parmlib member COFVLF00.
Using SYSEXEC does not cache the execs in VLF.
Please explain how it messes up your comments. Wait, don't tell me, VB
SYSPROC (yecch!)?
Regards,
Tom Conley
Rob Zenuk
EXEC's and do not see any performance delays...
My comments comment is even more trivial than VB... I like to use a
starting flower box for the word REXX... In SYSPROC I have to remove the first
line of asterisks... I like to line up my Cheerios on my spoon before I
eat them too...
Rob
In a message dated 11/23/2009 9:14:56 P.M. US Mountain Standard Time,
Paul Gilmartin
>
> My comments comment is even more trivial than VB... I like to use a
> starting flower box for the word REXX... In SYSPROC I have to
> remove the first
> line of asterisks... I like to line up my Cheerios on my spoon
> before I
> eat them too...
>
> In a message dated 11/23/2009 9:14:56 P.M. US Mountain Standard Time,
> pinncons writes:
>
> Please explain how it messes up your comments. Wait, don't tell
> me, VB
> SYSPROC (yecch!)?
>
And that would be a problem because ... what?
My SYSEXEC is VB.
-- gil
Joe Aulph
It was my failure to specify my site customized command table, in my ISPF
configuration,that was the problem.
Ultimately not really a profile sharing issue at all.
Once I properly specified my site table the 'problem' went away.
Cheers,
Joe Aulph,
Joe_...@nsrc.myflorida.com
Northwood Shared Resource Center
Senior Systems Programmer:
Pedro Vera
<pe...@US.IBM.COM
> To
Sent by: ISPF ISP...@LISTSERV.ND.EDU
discussion list cc
<ISPF-L@LISTSERV.
ND.EDU> Subject
Re: Shared profile question:
11/23/2009 03:57
PM
Please respond to
ISPF discussion
list
<ISPF-L@LISTSERV.
ND.EDU>