That's grand! Glad you got past any issues and have a new system.. Scott
On Wed, Apr 8, 2009 at 12:17 PM, Martin, Terry R. (LOCKHEED MARTIN Performance Engineering/CTR) (CTR) <terry.mar...@cms.hhs.gov> wrote: > Hi Scott, > > > > I just wanted to let you that I was able to build the new system and IPL > without any issues. I did not get the errors in AUTOLOG2 this time. So I > must have messed up initially. I re-copied all of packs and made sure that > the System Config and the Directory were pointing to the correct packs and > this time I did a FORCE and the spool started fine. > > > > Thanks again for your help along with everyone else! > > > > > > *Thank You,* > > > > *Terry Martin* > > *Lockheed Martin - Information Technology* > > *z/OS & z/VM Systems - Performance and Tuning* > > *Cell - 443 632-4191* > > *Work - 410 786-0386* > > *terry.mar...@cms.hhs.gov* <terry.mar...@cms.hhs.gov> > ------------------------------ > > *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On > Behalf Of *Scott Rohling > *Sent:* Tuesday, April 07, 2009 5:30 PM > > *To:* IBMVM@LISTSERV.UARK.EDU > *Subject:* Re: Format a SPPOL VOLUME on First IPL > > > > Hi Terry -- Everything should work fine using spool from the other system > - and you basically want to avoid having to rebuild your NSS/DCSS's. A > FORCE is normal after coming up from a copy of your spool -- pointers have > usually changed... I've occasionally been able to come up WARM, but it's > rare and all depends on how off the pointers (warm/chkpoint) on your SYSRES > are from the spool packs and how fast things copied. Anyway - FORCE is > fine. > > The only thing you might want to do is to come up without AUTOLOG2 (which > it sounds like you have by accident) and scratch things from spool from the > old system. You should be able to issue some commands to kill most of it > -- like: > > PIPE CP Q RDR ALL | DROP FIRST | SPECS /PURGE/ 1 W1 nw /RDR/ nw W2 nw | CP > | CONS > > Do that 3 times - once for RDR - another for PRT - another for PUN .. > and you should should have cleaned up any old junk from the old system you > don't want. > > For your AUTOLOG2 problem -- you'll have to show us the error.. Try this: > > XAUTOLOG AUTOLOG2 SYNCH #SET SECUSER AUTOLOG2 * > > And see what messages are issued.. or you may get an error from the > autolog and show us that.. > > Scott > > On Tue, Apr 7, 2009 at 3:03 PM, Martin, Terry R. (LOCKHEED MARTIN > Performance Engineering/CTR) (CTR) <terry.mar...@cms.hhs.gov> wrote: > > Hi Scott, > > > > Probably don’t need to. What I am doing is a DFDSS full volume copy of my > test system to a new set of system and user packs. I defined some mdisks on > the running system pointing to the SYSTEM CONFIG and User Directory files on > the NEWRES. I made the changes to the SYSTEM CONFIG and Directory files that > matched the new environment, such as new sysres, page, spool, and work > volumes. > > > > Pointing to the area on the NEWRES pack that contains the User Directory is > done and than defining another mdisk for NEWRES as 0 to END. Once the > changes were made I issued the DIRECTXA USER DIRECT M (FM=’M’ is the FM that > I accessed the mdisk for the Directory area on the NEWRES pack with > > > > Question: > > 1. Is ok to copy the spool from the other system to the new system? Are > the NSS on the spool specific for each system or does it matter if this > information is copied to another system? > 2. When I tried to IPL this new system the first time I issued a WARM > IPL this failed and I was prompted to STOP or FORCE I elected to issue > FORCE. It looked like everything came up but I noticed that xautolog of the > autolog2 had failed. The xautolog of autolog1 which starts RACF and a few > other machines worked fine, but when aoutlog2 was executed it failed. I > wrote down the error message but I left it at work. Is there a way to get > any error text from the execution of the AUTOLOG2 exec like to a RDR so > that > I can see if there any other errors? > > > > I guess that is it for now. Thanks for the help!! > > > > *Thank You,* > > > > *Terry Martin* > > *Lockheed Martin - Information Technology* > > *z/OS & z/VM Systems - Performance and Tuning* > > *Cell - 443 632-4191* > > *Work - 410 786-0386* > > *terry.mar...@cms.hhs.gov* <terry.mar...@cms.hhs.gov> > ------------------------------ > > *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On > Behalf Of *Scott Rohling > *Sent:* Tuesday, April 07, 2009 2:19 PM > > > *To:* IBMVM@LISTSERV.UARK.EDU > *Subject:* Re: Format a SPPOL VOLUME on First IPL > > > > Why are you formatting the spool volume? There's probably a better way to > do what you're trying to accomplish without toasting your NSS files and > rebuilding everything... > > Scott > > On Tue, Apr 7, 2009 at 12:16 PM, Kris Buelens <kris.buel...@gmail.com> > wrote: > > Some extra word of caution: if you'd format the active spool volumes, > you will also loos all VM's saved segments, like CMS, CMSPIPES etc, > all of them will need to be recreated or restored from an SPXTAPE > backup. > > 2009/4/7 Kris Buelens <kris.buel...@gmail.com>: > > > You can format -new- spool space while VM is running. > > Anyhow: if you IPL VM with any startup you can, VM will have > > initialized its spool before you can do something. > > > > But, you should have a look on MAINT CF1, search for ICKSADSF MODULE. > > If you find it, you have the standalone ICKDSF version, that you can > > start instead of VM: > > - IPL with as loadparm SYSG or an address of a 3270 (like an ICC > > console). This will start SAPL in prompt mode. > > - in SAPL press PF9 (Filelist) and select ICKDSF > > - enter the ICKDSF statements to format whatever you want. > > When done, reipl the "normal way" > > > > 2009/4/7 Martin, Terry R. (LOCKHEED MARTIN Performance > > Engineering/CTR) (CTR) <terry.mar...@cms.hhs.gov>: > >> Hi > >> > >> > >> > >> I am building a new test system and I want the first IPL to format the > spool > >> volume. Currently VM is set up to IPL automatically WARM. Where/how do I > >> change it to prompt for a Startup parameter at IPL time so that I can > >> specify the formatting of the spool volume? > >> > >> > >> > >> > >> > >> Thank You, > >> > >> > >> > >> Terry Martin > >> > >> Lockheed Martin - Information Technology > >> > >> z/OS & z/VM Systems - Performance and Tuning > >> > >> Cell - 443 632-4191 > >> > >> Work - 410 786-0386 > >> > >> terry.ma...@cms.hhs.gov > >> > >> > > > > > > > > -- > > Kris Buelens, > > IBM Belgium, VM customer support > > > > > > -- > Kris Buelens, > IBM Belgium, VM customer support > > > > >
