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: t...@cio.sc.gov
> Subject: ispf "swapbar" cmnd
> To: IBM-MAIN@bama.ua.edu
> 
> 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
> 
> 
> 
> 
> 
> 
                                          

Reply via email to