Ray, What about terminal screen size? Are all users using the same 3270 device or are some reconfiged for a MOD3, MOD4, or MOD5?
One thing I would look at is the terminal size. Then I would look to see if maybe some have an ISPF concatenation process. The use of ISPF TEST might be helpful here. Lizette > >Hi everyone, > > > >First, Im doing fine things have happened, but Im back on my feet and I >found a very nice position with a small ISV. In addition to writing code, >Im also the sysprog/sysadmin for our z9 development system. Its been good >to get back into the sysprog game, and (usually) it doesnt take up much of >my time. > > > >But Ive run into a strange inconsistent ISPF initialization problem. >Sometime in the past couple of months, Ive 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 dont see it, so Im looking for some >pointers as where else to look. > > > >I should first state that this is based on the standard ADCD environment >(although technically its no longer called ADCD in our case. J ) > > > >Heres 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. Ive logged on using the same proc and Im fine. We have >several other users that use ISPFPROC and they dont have any problems at >all, either. Ive 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. > > > >Im 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. > ---------------------------------------------------------------------- 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
