Robert,
The fact that you're getting a different ISPVCALL dataset name
indicates a
different config module. When you say PREPEND, what do you mean? I'll
again
suggest using TSOLIB for your LOADLIB (instead of whatever else you're
doing to
"PREPEND"), which has always worked for me.
Prepend is concatenate them in front of what's there, append is at the
back. ;)
I seem to have solved the problem by regenerating my private command
tables from scratch, rather than using the 1.10 & 1.6 versions that I
had copied to the ISPF profile dataset from my 1.10 system (and "that"
system).
This part now works. However, ISPVCALL still hangs and gobbles up all
the CPU it can get. (So as a "solution" I won't use it for now)
I do however think that the current set-up, where there are already four
ISPCFIGU load modules present is not ideal, to put it mildly, but maybe
some of you more at home in these matters might have another opinion you
could share.
Robert
Robert,
ISPVCALL should not hang and gobble CPU. Something about ISPF in your
environment is not right. Four ISPCFIGU modules is a really bad idea.
There should only be 1 in LINKLIST, and possibly 2 if you're testing
your own with TSOLIB. That's it.
Regards,
Tom Conley
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
