Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ispf "swapbar" cmnd

1,926 views
Skip to first unread message

Bonno, Tuco

unread,
Feb 17, 2011, 12:34:26 PM2/17/11
to
cross posting to both ibm-main and ispf-l listservers.
my environment is z/os 1.11

the z/os 1.11 “Intro and Release Guide” ga22-7502-17, page 86 says that release 1.10 introduced an ispf enhanced screen swapping facility, documented in the z/os isfp user’s guide, volume 1.

the z/os 1.11 “ISPF User’s Guide volume 1” sc34-4822-09, page 101 talks about a command called “SWAPBAR” which is the means by which the enhanced screen swapping facility is implented/accessed, as follows:

“ …… The list of logical sessions can be activated by entering the SWAPBAR or
SWAPBAR ON command on the command line. The list is displayed on the last
line of the physical screen.
The entry for each logical session is the screen name if assigned or, if a screen
name is not available, it is the panel name of the current panel displayed for the
logical session. The entry for the active logical session has an asterisk (*) in the first
character position and, if the name is 8 bytes long, the last character is not
displayed. Also, the alternate logical session has a ″-″ in the first position and the
8th character is not displayed.
The list remains active until you enter the SWAPBAR or SWAPBAR OFF. "

whenever I enter the command “SWAPBAR “ at any ispf screen, to include any edit sessions, I get only “ikj56500i command swapbar not found” in response. my investigation into ikj56500 has lead me to believe that in order to get this command to work, I need to make an entry in the isptcm . has anybody else had to do this? am I on the right track?

thanks in advance

/s/ tuco bonno
graduate, College of Conflict Management;
University of Southeast Asia:
"I partied on the Ho Chi Minh Trail -- tiến lên ! "

xxxxx

Brenton, Ren

unread,
Feb 17, 2011, 12:50:21 PM2/17/11
to
We had the same problem when we first went to 1.10. The deal is (apparently) that there are command tables (or whatever) allocated to ISPTLIB which SWAPBAR does not like. BUT-once you get it set you’re good and can go back to the allocations (from your LOGON PROC, or wherever), and it’ll stick. But to turn it back off you have to go through the rigmarole again.

TRY THIS:

Exit ISPF and get back to the TSO READY prompt and enter:

FREE FI(ISPTLIB) KEEP
ALLOC FI(ISPTLIB) DA('ISP.SISPTENU') SHR

THEN get into ISPF—the primary option screen, and enter “SWAPBAR”. It should then show you the dialog name at the bottom of the screen.

Then logoff and logon again.

You should be good to go.

Ren

thanks in advance

xxxxx


The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

Pedro Vera

unread,
Feb 17, 2011, 12:59:26 PM2/17/11
to
Since you are getting an IKJxxxx message, I suspect you are issuing it as
a TSO command, by typing TSO SWAPBAR in the ISPF command line.

It should work by typing only SWAPBAR, without the TSO.


Pedro Vera
DB2 Admin Tool
http://www-01.ibm.com/software/data/db2imstools/db2tools/db2admin/

Bonno, Tuco

unread,
Feb 17, 2011, 1:22:37 PM2/17/11
to
thanks. w/ your help, I've gotten it to work. but it was a little more complicated. our logon proc-s have clists-rexxes associated with them that do some extensive manipulation of the isptlib ddn --- after I did the free on isptlib, I lost all sorts of *other things* when I got back into ispf w/ only isp.sisptenu allocated.
thanks.
I am going to try to make an entry in the command table at ispf 3.9 , see if that works as well
thanks for your help

Bonno, Tuco

unread,
Feb 17, 2011, 1:23:21 PM2/17/11
to
thanks, but no, I'm not typing "tso swapbar", just 'swapbar'


like this:


ISPF Primary Option Menu Invalid option
Option ===> SWAPBAR

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@LISTSERV.ND.EDU] On Behalf Of Pedro Vera
Sent: Thursday, 17 February, 2011 12:58 PM
To: ISP...@LISTSERV.ND.EDU
Subject: Re: ispf "swapbar" cmnd

Bonno, Tuco

unread,
Feb 17, 2011, 1:37:46 PM2/17/11
to
thank you. what you said is exactly my problem. my logproc ispptlib concatenation contains several pds-s AHEAD of isp.sisptenu, a couple of which contain members called 'ispcmds' .

I now have a pretty good idea of what I need to do to fix the problem.

thanks to all on BOTH listservers who responded.

/s/ tuco bonno;
Graduate, College of Conflict Management;
University of SouthEast Asia;
"I partied on the Ho Chi Minh Trail - tiến lên !! "


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-...@bama.ua.edu] On Behalf Of Dave Salt
Sent: Thursday, 17 February, 2011 01:25 PM
To: IBM-...@bama.ua.edu
Subject: Re: ispf "swapbar" cmnd


Tuco,

The problem is that someone at your site has customized the IBM version of ISPCMDS. ISPCMDS is the command table that contains regular ISPF commands such as SPLIT, SWAP, HELP (etc). Someone has probably added several commands to this table that are used exclusively at your site; e.g. DOIT, MYCMD, FIXTHIS (etc). They've put the customized version ahead of the IBM version, meaning it's allocated to the ISPTLIB ddname ahead of the IBM version. You can prove this by entering the following on any ISPF command line:

DDLIST ONLY ISPTLIB;M ISPCMDS

This command shows you all the table libraries in which the ISPCMDS member is found. If the DDLIST command doesn't work (i.e. for the exact same reason the SWAPBAR command doesn't work), enter this instead:

TSO ISRDDN;ONLY ISPTLIB;M ISPCMDS

Ideally there should only be ONE table library in which the ISPCMDS member is found. I suspect you'll have at least two, with the customized version ahead of the IBM version. So, whenever you get a new release of ISPF the IBM version of ISPCMDS is updated (e.g. with new commands like SWAPBAR), but the customized version (which is higher in the concatenation and therefore picked up first) doesn't get updated.

Rather than having to continually update the customized version by adding new ISPF commands to it, it's better to delete the customized version completely. That way, the vanilla ISPCMDS table is the ONLY version of ISPCMDS that's allocated to ISPTLIB and you'll always get any new commands that IBM introduces.

As for your site specific commands (DOIT, MYCMD, FIXTHIS etc) they should go in a completely separate command table. You can determine the name for the new command table by going into ISPF option 3.9. If (for example) the 'Command Table Search Order' looks like this:

Command table search order
Application table . : ISR
User table 1 . . . . : USR1
User table 2 . . . . :
User table 3 . . . . :
Site table 1 . . . . : SIT1
Site table 2 . . . . :
Site table 3 . . . . :
System table . . . . : ISP

Then the best table to put your site specific commands in would be SIT1CMDS (where SIT1 is the prefix shown next to Site Table 1 and 'CMDS' is the mandatory suffix for command table members). Create the SIT1CMDS member in the same library you delete your customized version of ISPCMDS from, put the site specific commands in it, logoff/logon, and you're set to go.

I hope that helps,

Dave Salt

SimpList(tm) - try it; you'll get it!

http://www.mackinney.com/products/program-development/simplist.html

> Date: Thu, 17 Feb 2011 12:33:41 -0500
> From: tu...@CIO.SC.GOV
> Subject: ispf "swapbar" cmnd
> To: IBM-...@bama.ua.edu

Dave Salt

unread,
Feb 17, 2011, 1:46:06 PM2/17/11
to

Tuco,

I know you have SimpList installed which means it's really easy for you to add commands to a command table. Simply enter TSO SLNESTER on any ISPF command line and the Command Table Update panel is displayed. Enter MODIFY on the command line, tab down to the list of commands and enter the commands you want to add to the table. Then, point the cursor at the table you want to add the commands to and press ENTER.

HTH,

Dave Salt

SimpList(tm) - try it; you'll get it!

http://www.mackinney.com/products/program-development/simplist.html


> Date: Thu, 17 Feb 2011 13:36:53 -0500
> From: tu...@CIO.SC.GOV
> Subject: Re: ispf "swapbar" cmnd -- solved
> To: ISP...@LISTSERV.ND.EDU

Bonno, Tuco

unread,
Feb 17, 2011, 2:20:23 PM2/17/11
to
yeah, I thought of that *after* I got your response on the listserver, saw who it was from and said, "Hey, that's the same person as the SimpList guy ..... "

right now these days I'm responding to problems (the SWAPBAR thing is only one of them) which have been fed to me as a result of our migration to 1.11 and in anticipation of the upcoming (i.e., this weekend) migration OFF the z9-s and onto the z10-s .

I promise I haven't forgotten the SimpList, but, as we used to say in viet-nam, "shoot the nearest nva first" .... (actually, we used another word than 'nva' but this is a high-class listserver community so I'm going to try to show some class myself and play nicely ..... )

Ted MacNEIL

unread,
Feb 17, 2011, 4:19:19 PM2/17/11
to
>actually, we used another word than 'nva'

Being a Canadian, and never serving in the military, I have NO idea what an 'nva' is.
-
Ted MacNEIL
eama...@yahoo.ca

Bonno, Tuco

unread,
Feb 18, 2011, 6:35:42 AM2/18/11
to
north vietnamese army; "an nva" was what we called north vietnamese army soldier

-----Original Message-----
From: ISPF discussion list [mailto:ISP...@LISTSERV.ND.EDU] On Behalf Of Ted MacNEIL
Sent: Thursday, 17 February, 2011 04:18 PM
To: ISP...@LISTSERV.ND.EDU
Subject: Re: ispf "swapbar" cmnd -- solved

Mark Zelden

unread,
Feb 19, 2011, 10:12:26 PM2/19/11
to
On Thu, 17 Feb 2011 13:17:01 -0500, Bonno, Tuco <tu...@CIO.SC.GOV> wrote:

>thanks. w/ your help, I've gotten it to work. but it was a little more
complicated. our logon proc-s have clists-rexxes associated with them that
do some extensive manipulation of the isptlib ddn --- after I did the free
on isptlib, I lost all sorts of *other things* when I got back into ispf w/
only isp.sisptenu allocated.
>thanks.
>I am going to try to make an entry in the command table at ispf 3.9 , see
if that works as well
>thanks for your help
>
>

You should be using SITECMDS for any local customization / additions and
you would never run into this sort of problem when IBM changes or adds
things to the supplied ISPCMDS. It's been around since MVS/ESA 4.3 or
maybe 4.2.

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
mailto:mze...@flash.net
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
Systems Programming expert at http://expertanswercenter.techtarget.com/

Mickey

unread,
Feb 21, 2011, 3:36:04 PM2/21/11
to
It was used to denote someone from the North Vietnamese Army. They were
better trained and better equipped than the Viet Cong

--------------------------------------------------
From: "Ted MacNEIL" <eama...@YAHOO.CA>
Sent: Thursday, February 17, 2011 4:17 PM


To: <ISP...@LISTSERV.ND.EDU>
Subject: Re: ispf "swapbar" cmnd -- solved

>>actually, we used another word than 'nva'

Bonno, Tuco

unread,
Feb 22, 2011, 6:15:42 AM2/22/11
to
>>You should be using SITECMDS for any local customization / additions and
>>you would never run into this sort of problem when IBM changes or adds
>>hings to the supplied ISPCMDS. It's been around since MVS/ESA 4.3 or
>>maybe 4.2.

thanks. yes, this was brought to my attention in an off-site post. I try to keep up with all this type of stuff, but sometimes things just never even get WITHIN the event horizon, much stay there long enough to get poppped off the data stack (sorry to mix metaphors/images there .... ) .... but then, these list-server communities help w/ the damage control ....

wjensen_1

unread,
Mar 26, 2011, 1:24:01 PM3/26/11
to
You could also use ispf opt 7.1 (dialog test) and run pgm ISPTL.

Cheers
Willy

0 new messages