I would recommend deleting (or renaming) and re-creating the ISPPROF dataset of 
one of the users concerned.  


Rob Scott
Rocket Software, Inc
275 Grove Street
Newton, MA 02466
617-614-2305
[EMAIL PROTECTED]


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Ray 
Mullins
Sent: 10 November 2008 20:21
To: [email protected]
Subject: Strange ISPF initialization problem

Hi everyone,

 

First, I'm doing fine.things have happened, but I'm back on my feet and I found 
a very nice position with a small ISV.  In addition to writing code, I'm also 
the sysprog/sysadmin for our z9 development system.  It's been good to get back 
into the sysprog game, and (usually) it doesn't take up much of my time.  

 

But I've run into a strange inconsistent ISPF initialization problem.
Sometime in the past couple of months, I've set up a couple of users who, for 
some strange reason, cannot get into ISPF.  They are using the same TSO logon 
proc as others, and those others can access ISPF without any problem.
I must be missing something, but I don't see it, so I'm looking for some 
pointers as where else to look.

 

I should first state that this is based on the standard ADCD environment 
(although technically it's no longer called ADCD in our case.  J )

 

Here's what happens

 

User logs on, gets READY, types in ISPF.  Then they get

 

 ISPP302  Panel 'ISPTERM' error - Invalid attribute keyword or value is   

 specified for attribute override.                                         

 ***                                                                      

 

Then they get the ISPTERM2 panel:

 

                              Unrecoverable Error                        

                                                                         

                                                                         

        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

        * *                                                           * *

        * *  An error occurred within the error routine.              * *

        * *  No recovery is possible.                                 * *

        * *                                                           * *

        * *                                                           * *

        * *                                                           * *

        * *                                                           * *

        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

        * *                                                           * *

        * *  Press ENTER key.                                         * *

        * *                                                           * *

        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

        * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

 

Then finally

 

ISPS014 - ** Logical screen request failed - abend 0003E7 **      

 ISPS015 - ** Contact your system programmer or dialog developer.**

 *** ISPF Main task abend ***                                      

 IKJ56641I ISPF     ENDED DUE TO ERROR+                            

 READY                                                             

 

U0999 is the ISPF "prevent an ABEND loop" abend.

 

This is one of those times that I can say nothing has changed as far as the 
proc and system data sets go.  The user is using the ISPFPROC that comes with 
the ADCD.  I've logged on using the same proc and I'm fine.  We have several 
other users that use ISPFPROC and they don't have any problems at all, either.  
I've also tried DBSPROC (the DB2ish proc from the ADCD) and ISPFLITE (ADCD 
bare-bones ISPF proc); no difference.

 

ISPTERM is sitting in ISP.SISPPENU and it looks just fine.  

 

The only thing I can point to is that some users that were created sometime 
after a general date (this summer) have the problem.  Yet others who were 
defined after this time do not have the problem; they can use ISPF just fine.  

 

I'm at a bit of a loss as to where to go next.  Any/all pointers suggested.

 

Oh, the one catch.this particular environment is 1.7, which, as soon as I can 
accumulate enough round tuits, will be upgraded.  But this is one of those 
"gotta make it work now because of deadlines" situations.

 

Thanks in advance,

Ray

 

-- 

M. Ray Mullins

Roseville, CA, USA

 <http://www.catherdersoftware.com/> http://www.catherdersoftware.com/

 <http://www.mrmullins.big-bear-city.ca.us/>
http://www.mrmullins.big-bear-city.ca.us/

 <http://www.the-bus-stops-here.org/> http://www.the-bus-stops-here.org/

 

German is essentially a form of assembly language consisting entirely of far 
calls heavily accented with throaty guttural sounds. ---ilvi

French is essentially German with messed-up pronunciation and spelling. --- 
Robert B Wilson

English is essentially French converted to 7-bit ASCII. ---Christophe Pierret 
[for Alain LaBonté]

 


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
[EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at 
http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to