How to add a 2nd SSP machine on a 436 AS/36?
mik...@hotmail.com
a 436? I need to make our Y2K revisions and want to use a 2nd SSP for
testing. Can the library containing the live SSP be copied into a new library
and run under a second M36? (I have enough DASD for this). What i really want
to do is this: 1. Make a 2nd SSP copied from the current system 2. Make
program changes, test in the 2nd SSP 3. Save revised library and file
conversion programs to tape (don't have ILAN running yet) 4. Restore tape to
SSP1 when ready to switchover, convert files
Has anybody done this?
I can follow IBM's instructions to create the 2nd SSP machine, but it's like
loading a new box - Load SSP from the CD, load utilities, RPG, etc, apply
PTF's, etc - this will take several hours. Any suggestions?
Thanks all
Mike
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Peter Langhammer
mik...@hotmail.com schrieb in Nachricht
<7bkevs$vfa$1...@nnrp1.dejanews.com>...
Save the library which contents the S/36 machine object and perform a RSTLIB
with an other target name (RSTLIB).
I did it before and it worked.
Be careful if you want to do device mapping to a communication line on the
AS/400. When both S/36 machines are started, the first machine locks the
line so that the second can´t get it.
In this case it would be better to change the mapping of the S/36 machine.
Peter
RGMustain
If you keep the workstation/printer configuration the same then the new machine
will try to grab all the same devices. If your configuration is in the same
library you use in the SAVLIB then you will have a copy of it as well. Change
it before starting the 2nd SSP. Don't forget to apply it on the first strm36.
How much free space to you have? Will the 2nd SSP fit on the system
concurrently with your production machine? You may want to reduce the DASD size
of the production machine before you do the SAVLIB. Use chgsysvl dasdsize. If
it still doesn't fit you may have to revert to a full installation where you
can set the disk size of the new SSP.
Dick Mustain
mik...@hotmail.com
I do have room for the second SSP. I plan to duplicate the live SSP, then
downsize the 2nd machine & remove all the comm lines & devices (except one or
two) before trying to start the 2nd SSP. What about the console for the
second SSP? Can I use CPYLIB to copy the first SSP library instead of doing a
Save/Restore?
Thanks for the replys!
RGMustain
You will need a console for the second machine. It can be the same as the first
machines console if you use DEV mapping and tfrm36 into one machine or the
other. This may create some confusion so I would recommend a separate console
if you have a workstation session available.
If you start the 2nd machine while the first one is still active it will try to
grab all the same devices (unless you change the m36cfg). The attempts would
fail if you use controller mapping and you would not be able to get into the
second machine. So you are correct in removing the devices. I would suggest
only configuring a single workstation as the console initially, remove all
other devices. You can add others in later if you need them.
Since chgsysvl dasdsize is an SSP command you will need to start the 2nd
machine before you can downsize it.
Dick Mustain
mik...@hotmail.com
My plan was to stop the first SSP and then load the second, start #2, drop the
devices and then downsize. When I start #2, it should come up identical to #1.
The only point I'm still fuzzy about is the console. Doesn't SSP want the
console at 0,0? Is there some way to map it to another port and address? I
really only need 1 or 2 CRT's and a fake printer for the second SSP. Or is the
mapping back to an Os/400 device eg do I map SSP2 W1 back to DSPnn etc?
JHLMSS
are you coming to the common user group conference next week (start march 7) in
san fransico? i am teaching a class on this subject.
http://www.michsoft.com
j...@michsoft.com
Joseph H. Le Blanc, CCP
Peter Langhammer
performing the TFRM36 press F4 and you are able to decide which S/36
workstation you want to be. This way you can manage up to three S/36
machines with only one AS/400 device.
Peter
mik...@hotmail.com
> are you coming to the common user group conference next week (start march 7)
in
> san fransico? i am teaching a class on this subject.
>
-----------== Posted via Deja News, The Discussion Network ==----------
RGMustain
SSPs many times.
Your question about the console... Since the Advanced 36 uses the *m36cfg
object to define the devices the requirement that the console be at address 0,0
no longer exists. The SSP will use the device defined at position 0,0 in
*m36cfg object as the console. If none exists the machine will start up in a
console check state. You can map position 0,0 to any physical device. If you
have used controller mapping of devices then the system automatically puts the
device at address 0,0 on the controller into position 0,0 of the *m36cfg
object. However, I would suggest you change to use device mapping and place
whatever device you want as the console at position 0,0 of the 2nd SSP. Note
that when you use device mapping or controller mapping you have the option of
displaying an SSP sign-on display at the device. If you chose not to display
the sign-on then you must use tfrm36.
One other thing, you do not need to put any devices in the *m36cfg. You can
use tfrm36 to get to the SSP by creating dummy entries in the the SSP
workstation configuration (CNFIGSSP). Use any device type that matches
reasonably well with the devices you will be using. You can then tfrm36
specifying WSID W1 and become the system console from any workstation.
Hopefully, I haven't confused you even more...
Dick Mustain