To list;
Thank you to the listers that responded to my question. We got around it by
modifying PARMLIBmember to prevent automatic startup of SMS as we were having
trouble signing on to TSO due to allocation failures.
It was an error in specifying volumes in a storage group which were defined
To list;
I have been attempting to stop SMS (if that is possible) as we are running
into allocation issues when logging on to TSO. I have tried various
combinations of parameters on the VARY SMS command but continue to get SYNTAX
errors. Has anyone had to stop SMS and if so, could you share
Well, the thought of doing so is terrifying to me. But I guess you could:
FORCE SMS,ARM
...
FORCE SMS
I'm just no sure what this will do. IMO, it would be better to create
a new SCDS dataset as a minimal SMS environment (no ACS routines),
and make it the active SCDS with:
SETSMS
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of william janulin
Sent: Wednesday, January 30, 2013 12:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: stopping SMS
To list;
I have been attempting to stop SMS (if that is possible) as we are running
into allocation issues when logging on to TSO. I have
: stopping SMS
Well, the thought of doing so is terrifying to me. But I guess you could:
FORCE SMS,ARM
...
FORCE SMS
I'm just no sure what this will do. IMO, it would be better to create
a new SCDS dataset as a minimal SMS environment (no ACS routines),
and make it the active SCDS with:
SETSMS
And make the change permanent with a SYS*.PARMLIB(VATLST*) change.
On Wed, Jan 30, 2013 at 11:57 AM, O'Brien, David W. (NIH/CIT) [C]
obrie...@mail.nih.gov wrote:
You might want to mount a non-sms volume as 'public' and then try TSO logon
again.
Thank You,
Dave O'Brien
--
Mike A Schwab,
