You can also save a copy as SYSTEM CONFIG-1 on CF1 and enter FT=CONFIG-1 (or something like that) in the SAPL override parameters .
Kris, IBM Belgium, VM customer support > This is also why it is a good idea to move the previous SYSTEM CONFIG > from the CF1 parm disk to CF2 parm disk. > Should VM not come up, reipl with the LOADPARM console-addr to get > the SAPL screen. Specify LOADPARM 2 to get previous > system config. > I learned my lesson and since then I do as DJ has suggested. > duane > > At 02:34 PM 12/21/2005, you wrote: > >The name of the config syntax checker is: CPSYNTAX EXEC and on my 5.1 > >system, it's found on MAINT's 193 mdisk. Using it after every change is > >a very good idea, imho....;-) > > > >DJ > > > >Rich Greenberg wrote: > > > On: Wed, Dec 21, 2005 at 10:42:19AM -0600,Bob Frankovich Wrote: > > > > > > } We use one of the MP3000 Emulator Sessions for the Z/VM 4.4 > > console. This > > > } morning, during a scheduled IPL, the operator entered SHUTDOWN REIPL on > > > } this console. VM shutdown but no other messages appeared on the console > > > } which was my 4 AM wakeup call. After several attempts over the phone, I > > > } came to work where I treid several other things : Closed the sessions & > > > } restarted them; entered a LOADPARM of E20 (the console address); did a > > > } POWER ON RESET; even rebooted OS/2. All to no avail. I then entered a > > > } LOADPARM of 01D (an address I had defined to OS/2 TCP/IP as an non-SNA > > > } device to be used for a console). VM started coming > > up. During the start > > > } up I noticed a message about an invalid comment in the SYSTEM CONFIG at > > > } line xxx. Once VM was up I checked the SYSTEM CONFIG and sure enough, > > > } there was a "/*" on that line without a "*/". I corrected this > > and IPL'ed > > > } again from 01D - no error. I then IPL'ed without any LOADPARM > > and VM came > > > } up on Address E20. Has anyone else had a similar problem or was the > > > } errant "/*" really the problem ? I'm really at a loss to > > explain this so > > > } any help will be appreciated. > > > > > > Thats exactly why the config syntax checker (which I forget the name of > > > at the moment) should be run whenever you change SYSTEM CONFIG. Even > > > for "trivial" changes. > > >
