>Why would you want a CMS tool to access SMAPI when SMAPI is mostly (at >least it seems to be to me) a programmable extension of Dirmaint? Why >not just use Dirmaint, that is what SMAPI does in the end.
If...
...you've ever had to sit there and go fix/document a 4,400 line EXEC2 exec "front-end" to Dirmaint that provides the local "administrators" of a remote hosted system (where you're the bought in VM sysprog) an ability to make changes to userids using cmds like ADD 4M TO DISK
...you've ever had to deal with MVS automation groups who don't understand that Dirmaint operates asynchronously and their company wide single point of user definition system needs to cope with that instead of just editing a few files and they can't do it and you have to do it for them
...you've ever had to rewrite the entire company wide automated user definition system so as to handle the way that Dirmaint did things asynchronously and did stupid things with the messages that it sent back meaning your message capturing server had to jump through hoops to try and keep up (and that's without dealing with OfficeVision registrations and moving users between different VM systems)
...and all the time dealing with what happens if DATAMOVE decides not to...
...then you wouldn't be asking that question.
I requested a scriptable API from Dirmaint dev. (who actually asked me what my problems with Dirmaint were - so it's their own fault) something like 12 years ago. Hmmm...
I had a rant here about how important things never seem to get REXX interfaces at the time of announcement but somehow, if people haven't gotten the message by now, it just doesn't seem to be worth the effort any more...
Rod (TOPS-20 - wonderful OS - years ahead of its time - I still miss it)
