On 7/4/2018 12:13 PM, Rob Scott wrote:
For the record, you do not need ISFTABL to be allocated for SDSF to function
and, in fact, I run without ISFTABL on many of the systems that I use.
If ISFTABL is not found, SDSF retrieves and stores system commands in the ISPF
profile dataset and in this mode the user can store up to 50 commands.
ISFTABL is only required if the user wants to store more than 50 commands.
The reason that SDSF does this is that there is an internal limit to the max
size of a ISPF profile member (64K-ish), and SDSF would very quickly exceed
that size if hundreds of z/OS system commands were stored using standard VPUT
processing. For this reason, it was chosen that we would store the system
commands in an ISPF table instead.
From what I can tell, this new feature was documented, but not in the
migration section as maybe it was deemed an enhancement and not a change to
existing behaviour.
Rob Scott
Rocket Software
Rob,
If this was a new feature and not a migration action, then you have to
make it work as before, and not issue the message by default (turn off
the limit option that the message references). The users noticed the
new behavior, since SDSF decided to enable the new limit by default, but
did not follow up with a migration action for the rest of it. Yes, I'm
being anal retentive, but I've taken more than a few support calls for
this one.
Tom
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
