ISPF START command does not work.

[yarnseeker]

I am not a sysprog either and I had no trouble using ISPCCONF to activate SITECMDS and USERCMDS for my personal use.

and how did you do that?

[don.leahy]

Originally Posted by yarnseeker

and how did you do that?

The ISPCCONF dialog steps you through the process of building an ISPCFIGU load module that contains ISPF settings, including the ones that activate SITECMDS/USERCMDS. (Which is option 5 on the ISPCCONF menu). Then you copy the ISPCFIGU module to a personal load library that is concatenated to ISPLLIB.

I was surprised at how simple it was. It left me wondering why sysprogs get the big bucks.

(Just kidding about that last part. I am well aware that sysprogs do a lot more than tweak ISPF settings.)

[taltyman]

Originally Posted by don.leahy

The ISPCCONF dialog steps you through the process of building an ISPCFIGU load module that contains ISPF settings, including the ones that activate SITECMDS/USERCMDS. (Which is option 5 on the ISPCCONF menu). Then you copy the ISPCFIGU module to a personal load library that is concatenated to ISPLLIB.

I was surprised at how simple it was. It left me wondering why sysprogs get the big bucks.

(Just kidding about that last part. I am well aware that sysprogs do a lot more than tweak ISPF settings.)

Good information Don. As long as you're tweaking there are a whole lot of defaults and settings that you can play with.

Such as setting a program to use when you have a 3.4 list of vsam files so you can edit/browse, etc.
Number of split screens

A lot of these are simply defaults that are initially used when a users profile gets created and can be changed by the user. However if they are set to acceptable values then it makes life easier for new folks.

I wish I still got the "big bucks", well it was okay money anyway. Just remember that when we mess up or have an aw xxxxx moment that it generally gets noticed by the world.

[don.leahy]

Originally Posted by taltyman

I wish I still got the "big bucks", well it was okay money anyway. Just remember that when we mess up or have an aw xxxxx moment that it generally gets noticed by the world.

I hear ya. The worst that I can do is shoot myself in the foot. I can't hurt anyone else.... well, unless I do something really stupid.

[yarnseeker]

Originally Posted by taltyman

Just remember that when we mess up or have an aw xxxxx moment that it generally gets noticed by the world.

Well I think I'll leave this to the sysprogs! they are on it and are going to activate site commands.

You're awe xxxxxx moments can't be as bad as the 1 at the major credit card company I worked for. For some reason the default there is autosave ON and the sysprog went into edit on 1 of the system datasets, pf3'd and voila! next IPL mainframe wouldn't come up. took them hours/days to figure out what changed and how to get it back up. Now that was the mother of all ?-ups!

I asked why the heck they had it setup to use autosave ON and they said it would be too hard or too much impact to change. * no comment *

[taltyman]

I've only managed to bring down production a couple of times. And survived some other close calls.

[Steve Coalbran]

Originally Posted by don.leahy

.... I am not a sysprog either and I had no trouble using ISPCCONF to activate SITECMDS and USERCMDS for my personal use.

Cheers Don.
I will search and find which ISPF manual describes these, then RTFM!
Steve

[taltyman]

Here's one http://publibz.boulder.ibm.com/cgi-b...20070722190241

[nadel]

Ahhh... time for my annual ISPCCONF warning...


Be careful if you make a personal change to ISPPCONF. ISPF service has seen issues where users create their own load module and forget about it.

When that happens, no one can figure out why certain settings work and others don't. In one case, a person shared their load module with another user and it was even harder to figure out why things didn't work for just those two users. It is not something local service personnel are likely to consider (or even know about) and IBM service probably won't think of it either.

For future reference, you can use TSO ISPVCALL STATUS to see where the load module is coming from.