Re: NULL SMS configuration, versus MINIMAL SMS configuration.
Glenn, * I am building a first copy of a stand alone sysres, commonly called a mini z/OS and I would like SMS to come up in a null configuration. * I have found RTFM guidelines for setting up a MINIMAL configuration but no specifications for a NULL configuration. Am I missing something or do I have the nomenclature confused? * How can I define a NULL SMS configuration? Is it actually documented somewhere? ISTR, IBM used to recommend a null configuration which was an empty linear vsam used for the ACDS. The recommendation was later changed to have a minimal configuration. If you have documentation on setting up a minimal configuration, that is what you want to do. Regards, John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NULL SMS configuration, versus MINIMAL SMS configuration.
On Wed, 3 Mar 2010 17:19:27 -0600, Glen Gasior glen.manages@gmail.com wrote: * I am building a first copy of a stand alone sysres, commonly called a mini z/OS and I would like SMS to come up in a null configuration. * I have found RTFM guidelines for setting up a MINIMAL configuration but no specifications for a NULL configuration. Am I missing something or do I have the nomenclature confused? * How can I define a NULL SMS configuration? Is it actually documented somewhere? * btw I am using zFS. * Thanks to all who have provided samples for building a mini z/OS system. * This system will support only batch processing and TSO ISPF, and SDSF. * I added SMS in a null configuration to my TWOPAKZ8 (used for z/OS 1.7 through z/OS 1.10) sample a few years ago (but not to the ONEPAKZ8 sample). The comments in the job explain it: // //* SMS IS ACTIVATED IN A NULL CONFIGURATION TO ALLOW TCP/IP TO //* DYNAMICALLY ALLOCATE Z/OS UNIX FILES. WITHOUT IT SOME TCP/IP //* FUNCTIONS THAT REQUIRE TO READ THEIR CONFIG FILES FROM UNIX //* VIA DYNALLOC WITH PATHNAME WILL FAIL (RC=4, ERRORCODE=04D0) //* (/ETC/SERVICES IS REQUIRED FOR INETD FOR EXAMPLE AND CAN'T //* BE READ). THIS ISN'T REQUIRED FOR A RESCUE SYSTEM, BUT IS //* INCLUDED IN THE CONFIGURATION ANYWAY AND ALLOWS TELNET INTO //* Z/OS UNIX IF DESIRED (AND CONFIGURED). // You can find my rescue system samples on my web site in the JOBs section: http://home.flash.net/~mzelden/mvsutil.html Anyway, a null configuration is one where you allocate an empty ACDS and COMMDS and have an IGDSMSxx member that points to them and start SMS via IEFSSNxx. A minimal configuration is where you define the base configuration via ISMF and also at least one STORCLAS, one storage group (with at least 1 volume), and ACS routines for the storage class and storage group (DATACLAS and MGMTCLAS are not required). If you've been around a while, you may recall that ServerPac used to come with instructions and samples for an SMS minimal configuration around the time of OS/390 because HFS files had to be SMS managed. So many shops that never used SMS were forced to create the minimal configuration in order to bring up OMVS. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NULL SMS configuration, versus MINIMAL SMS configuration.
On Thu, 4 Mar 2010 08:21:03 -0600, Mark Zelden mzel...@flash.net wrote: (with snippage) Anyway, a null configuration is one where you allocate an empty ACDS and COMMDS and have an IGDSMSxx member that points to them and start SMS via IEFSSNxx. I always thought a null configuration was what you got if there was no IGDSMSxx member, that's what I remember from one-pack systems but I cannot test it now. DC -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NULL SMS configuration, versus MINIMAL SMS configuration.
* Thank you that is all that I need and I will also look at the two pack examples while I am working. I will report any interesting results. This will be on a z10 BC, with a DS8100 (2107). I am going to try the null configuration for the first test. * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NULL SMS configuration, versus MINIMAL SMS configuration.
On Thu, 4 Mar 2010 10:23:57 -0600, David Cartwright dcartwri...@ymail.com wrote: On Thu, 4 Mar 2010 08:21:03 -0600, Mark Zelden mzel...@flash.net wrote: (with snippage) Anyway, a null configuration is one where you allocate an empty ACDS and COMMDS and have an IGDSMSxx member that points to them and start SMS via IEFSSNxx. I always thought a null configuration was what you got if there was no IGDSMSxx member, that's what I remember from one-pack systems but I cannot test it now. Maybe it is just terminology that you are using differently or maybe it has changed from what it once was. But I call no IGDSMSxx no SMS configuration, not a NULL configuration.That is how my sample ONEPAK* systems come up and also my TWOPAK* systems prior to z/OS 1.8 when I made the change to a null configuration (for the reason I wrote about in a prior post). Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NULL SMS configuration, versus MINIMAL SMS configuration.
On Thu, 4 Mar 2010 13:04:19 -0600, Mark Zelden mzel...@flash.net wrote: On Thu, 4 Mar 2010 10:23:57 -0600, David Cartwright dcartwri...@ymail.com wrote: On Thu, 4 Mar 2010 08:21:03 -0600, Mark Zelden mzel...@flash.net wrote: (with snippage) Anyway, a null configuration is one where you allocate an empty ACDS and COMMDS and have an IGDSMSxx member that points to them and start SMS via IEFSSNxx. I always thought a null configuration was what you got if there was no IGDSMSxx member, that's what I remember from one-pack systems but I cannot test it now. Maybe it is just terminology that you are using differently or maybe it has changed from what it once was. But I call no IGDSMSxx no SMS configuration, not a NULL configuration.That is how my sample ONEPAK* systems come up and also my TWOPAK* systems prior to z/OS 1.8 when I made the change to a null configuration (for the reason I wrote about in a prior post). After looking at some saved syslogs from my last IPLs of my onepak and twopak systems, I can also add the following... When you come up in an SMS null configuration, you see these messages: *IGD048I NULL CONFIGURATION ACTIVATED IGD020I SMS IS NOW ACTIVE And a D SMS will display this: D SMS IGD002I 11:40:02 DISPLAY SMS NO CONFIGURATION DATA AVAILABLE When you come up with no SMS configuration, you see no messages at all. A D SMS will display this: D SMS IGD012I COMMAND REJECTED SMS IS NOT ACTIVE Regards, Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: NULL SMS configuration, versus MINIMAL SMS configuration.
David, I always thought a null configuration was what you got if there was no IGDSMSxx member, that's what I remember from one-pack systems but I cannot test it now. I think that is just not running/starting SMS. Is this an option anymore? Running SMS with a null configuration is running with an empty linear vsam dataset as your ACDS. Running SMS with a minimum configuration was as Mark described it earlier. IBM initially recommended running with a null configuration if you were not going to use any of the features. That was changed to run with a minimum configuration later. I have a special SMS with minimum configuration used with our emergency two pack system. Regards, John -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
NULL SMS configuration, versus MINIMAL SMS configuration.
* I am building a first copy of a stand alone sysres, commonly called a mini z/OS and I would like SMS to come up in a null configuration. * I have found RTFM guidelines for setting up a MINIMAL configuration but no specifications for a NULL configuration. Am I missing something or do I have the nomenclature confused? * How can I define a NULL SMS configuration? Is it actually documented somewhere? * btw I am using zFS. * Thanks to all who have provided samples for building a mini z/OS system. * This system will support only batch processing and TSO ISPF, and SDSF. * -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
