Override ISPF built-in line commands

mkan · New User Joined: 07 Jun 2006 Posts: 5

Hi,

I need to override ISPF built-in line command and invoke my macro. For example when B is typed against a dataset in dataset list panel, I want to invoke my macro instead of built-in browse command. How to do it?

Thanks.

enrico-sorichetti · Posted: Wed Nov 26, 2008 1:47 pm

do not override the ISPF commands,
people are used to them and it would bother everybody to have
in an ISPF provided panel a behavior different from the standard one

if You insist on having commands with the same name as the ISPF ones
write from scratch an application with the commands that best suit you
make clear in the panels that it is not an ISPF standard panel sequence

the need or i would say the whim is useless anyway
what meaning would You give to your B an illogic one I guess,
wandering thru the zillions of softwares based on ISPF You should have noticed
that .... B always stands for Browse of the object being managed

do not break this good habit,
and do not expect from people who do know ISPF any help in doing it
( not from me at least )

expat · Posted: Wed Nov 26, 2008 2:00 pm

Yes, it is possible, but in total agreement with Enrico as tp the reasons you should not.

mkan · New User Joined: 07 Jun 2006 Posts: 5

The intention is not to change the standard functionality, but to introduce some checks before proceeding to standard functionality. For example for E(edit), I want to check if the user is editing any important common files and throw a warning message and proceed to edit screen. In my site many people are unaware of common files and accidently delete/edit them, thinking that it's used only by their application. So, the point is not to change the normal behavior, but to introduce some checks and avoid accidental edits or deletes. And this macro won't be installed at site level or so. I am planning to distribute it as utility, which each user can include in their login script. So, whoever using it, will know that there is override placed. I appreciate any help in this regard.

Thanks.

enrico-sorichetti · Posted: Wed Nov 26, 2008 2:56 pm

the correct way of doing it is to protect the mission critical files with the proper security package

mkan · New User Joined: 07 Jun 2006 Posts: 5

The problem is we have a group which is involved in both development and issues resolution. They need access to these files to resolve issues raised by business. But, while they are involved in development work they shouldn't change some of the files. Though we have given instructions accident do happen. I am just one programmer who uses the system and don't have privilege to set security rights or something like that. Any programmer implementable solutions are welcome.
Thanks.

enrico-sorichetti · Posted: Wed Nov 26, 2008 3:17 pm

any programmer implementation will be wrong from any point of view,
why shouldn' t people pay attention to what they are doing

You need organization, not workarounds

mkan · New User Joined: 07 Jun 2006 Posts: 5

Exactly words I told my Manager... We need people to be organized and responsible. My manager had tried to make it happen for long time and as it didn't work out he is asking me for work around. I understand the commitment you have and appreciate the same. Because, I was pushed for work around, I tried to get some help. If you feel it’s completely wrong to go for work around like this, I respect that view and won’t seek anymore assistance. On other hand if you think as “one off” case we could do that, to save us from lot of trouble then I will be happy to take help. I am fine with whatever choice you make. Thanks for your thoughts.

enrico-sorichetti · Posted: Wed Nov 26, 2008 3:48 pm

I understand Your concerns, but there are too many ways to edit a dataset
under ISPF...
which means too many panels to modify
and too many user profile choices that allow to circumvent the issue

for example if You use the extendend member list You can edit a member
from any member list..
You choose browse, and You can edit

and if the coworkers are careless , no warning panel will prevent them from doing damage

a better approach would be to try to force the no autosave,
it means to make ISPF ask for confirmation before saving

evaluate the possibilty to use a global setting AUTOSAVE PROMPT
or use an initial edit macro to force AUTOSAVE PROMPT for selected datasets

if You can group the datasets in question under a common pattern it would be the best workaround
it is possible to force an initial macro when customizing ISPF

mkan · New User Joined: 07 Jun 2006 Posts: 5

Thanks for the suggestions..
I will try them and see how things work out!

Pedro · Posted: Wed Nov 26, 2008 10:12 pm

I think you need a change management system. And use different datasets for development than for production. When a change is to be promoted to production, there should be a review and approval process.

Yeah, some people will argue that is an unnecessary bureaucracy but it seems like you problems with out it.

MBabu · Posted: Thu Nov 27, 2008 2:16 am

publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ISPZPC40/4.11.16?

If users are using the Edit or View panels (opts 1, 2) you need to add panel exits to those panels

If users are using the ISPF services, your options are very limited (as others have said)