SMP
Posted: Wed 04 Aug 2010, 09:25Looking through SYSLOG, I see a lot of failed attempts to access SYSFAN.SMPTABL. I'm pretty sure these are attempts to start the SMP dialogs in ISPF.
The administrators have blocked most of us (including me!) from accessing this data set, so most of us cannot use the SMP dialogs.
However, all of us can use batch SMP. This is not all that hard to do.
Looking through the volumes, I can see a few data sets that appear to be SMP CSI data sets, however, I would expect access to them would be blocked, at least for update, too. All of us can allocate CSI data sets within our userids. I think I see a couple of attempts to do this, but whoever did it did it wrong. An SMP CSI data set is a VSAM data set, not a non-VSAM data set. You might be able to copy a valid CSI data set to a private copy and then use UCLIN to update the target and DLIB zones in the private CSI to use your CSI, but you might be better off starting from scratch.
The administrators have blocked most of us (including me!) from accessing this data set, so most of us cannot use the SMP dialogs.
However, all of us can use batch SMP. This is not all that hard to do.
Looking through the volumes, I can see a few data sets that appear to be SMP CSI data sets, however, I would expect access to them would be blocked, at least for update, too. All of us can allocate CSI data sets within our userids. I think I see a couple of attempts to do this, but whoever did it did it wrong. An SMP CSI data set is a VSAM data set, not a non-VSAM data set. You might be able to copy a valid CSI data set to a private copy and then use UCLIN to update the target and DLIB zones in the private CSI to use your CSI, but you might be better off starting from scratch.