home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR24
/
LAD2ST.ZIP
/
LAD2ST11.SCN
< prev
next >
Wrap
Text File
|
1993-04-30
|
9KB
|
224 lines
LAD2ST11 SCENARIO
-----------------
The following scenario illustrates a transfer of user data from
LAD/2 data files to IBM LAN NetView Start 1.1 (Start) migration files.
It involves customer LANNET, workgroup GUI, and five clients: PHIL,
TED, JOHN, DIANE, and MIKE.
As defined in LAD/2, the GUI workgroup under the LANNET customer
has the following common product characteristics:
* OS/2 installed on C: with the default configuration.
* Extended Services Communications Manager installed on D: with a
destination address of 4000000000999, 5 non-DFT sessions, and 5 DFT
sessions (autostartable).
* Extended Services Database Manager installed on E:.
* LAN Server 3.0 installed on F: with a domain name of LADDOM.
* LAPS using a Local Administered Address and an IBM Token-Ring
Network Adapter.
Each of the five users (clients) in the GUI workgroup have
the following individual characteristics:
Username: PHIL
Machine ID: PHILID
LAN functionality: Domain Controller
Local Administered Address: 400000000001
Local Node ID: 00001
Local Nodename: CP000001
Database functionality: Client/Server
Username: TED
Machine ID: TEDID
LAN functionality: Server
Local Administered Address: 400000000002
Local Node ID: 00002
Local Nodename: CP000002
Database functionality: Server
Username: JOHN
Machine ID: JOHNID
LAN functionality: Server
Local Administered Address: 400000000003
Local Node ID: 00003
Local Nodename: CP000003
Database functionality: Client
Username: DIANE
Machine ID: DIANEID
LAN functionality: Requester
Local Administered Address: 400000000004
Local Node ID: 00004
Local Nodename: CP000004
Database functionality: Standalone
Username: MIKE
Machine ID: MIKEID
LAN functionality: Requester
Local Administered Address: 400000000005
Local Node ID: 00005
Local Nodename: CP000005
Database functionality: Client
Note that username is equivalent to client name, and machine ID
is equvalent to computer name in LAD/2 and Start terms.
The directory structure to the LAD/2 data files is as follows:
Y:\LAD2\LADCODE\WKGROUP.TBL
|--->\LANNET\GUI\EXTD.TBL
|------------------->LS30.TBL
|------------------->LAPS.TBL
\------------------->RECEIVER.TBL
This scenario also uses an override file to change values in all
the generated migration files. This override file sets the machine
type of all the migrated nodes to 8570 and assigns them a workstation
comment of "LAD/2 migration: customer LANNET, wkgroup GUI." The
file GUI.OVR is as follows:
MachineType 8570
WKSTComment LAD/2 migration: customer LANNET, wkgroup GUI.
Now, the LAD2ST11 applet can be invoked with the following
parameters:
lad2st11 /ladpath=y:\lad2\ /customer=LANNET /wgname=GUI
/ofile=gui.ovr
with the following result:
***** Start of LAD2ST11.CMD stdout *****
Customer path is Y:\LAD2\LANNET\.
Workgroup path is Y:\LAD2\LANNET\GUI\.
/MIGPATH parameter not specified.
The target directory for generated Start migration files will default to the current directory.
Target migration path D:\REXX\.
Reading in override file FILENAME.
On Migration File: D:\REXX\PHIL.IMP
When migrating the node, Start will set the LAPS drive to C.
In LAD/2, the LAPS drive was set to drive D.
Changed database requester/server functionality to server.
IBM Token Ring adapter specified.
Assuming it is type Token Ring 16/4 /a with a set speed of 4.
Overriding MachineType old value '0000' with new value '8570'.
Overriding WKSTComment old value ' ' with new value 'LAD/2 migration: customer LANNET, wkgroup GUI.'.
On Migration File: D:\REXX\TED.IMP
When migrating the node, Start will set the LAPS drive to C.
In LAD/2, the LAPS drive was set to drive D.
IBM Token Ring adapter specified.
Assuming it is type Token Ring 16/4 /a with a set speed of 4.
Overriding MachineType old value '0000' with new value '8570'.
Overriding WKSTComment old value ' ' with new value 'LAD/2 migration: customer LANNET, wkgroup GUI.'.
On Migration File: D:\REXX\JOHN.IMP
When migrating the node, Start will set the LAPS drive to C.
In LAD/2, the LAPS drive was set to drive D.
IBM Token Ring adapter specified.
Assuming it is type Token Ring 16/4 /a with a set speed of 4.
Overriding MachineType old value '0000' with new value '8570'.
Overriding WKSTComment old value ' ' with new value 'LAD/2 migration: customer LANNET, wkgroup GUI.'.
On Migration File: D:\REXX\DIANE.IMP
When migrating the node, Start will set the LAPS drive to C.
In LAD/2, the LAPS drive was set to drive D.
IBM Token Ring adapter specified.
Assuming it is type Token Ring 16/4 /a with a set speed of 4.
Overriding MachineType old value '0000' with new value '8570'.
Overriding WKSTComment old value ' ' with new value 'LAD/2 migration: customer LANNET, wkgroup GUI.'.
On Migration File: D:\REXX\MIKE.IMP
When migrating the node, Start will set the LAPS drive to C.
In LAD/2, the LAPS drive was set to drive D.
IBM Token Ring adapter specified.
Assuming it is type Token Ring 16/4 /a with a set speed of 4.
Overriding MachineType old value '0000' with new value '8570'.
Overriding WKSTComment old value ' ' with new value 'LAD/2 migration: customer LANNET, wkgroup GUI.'.
***** End of LAD2ST11.CMD stdout *****
LAD2ST11 cannot determine the IBM Token Ring type from the LAPS
specification, so it defaults it to tr-unknown in the generated
migration files. Start 1.1 will set the adapter to type Token Ring
16/4 /a when the migration of the files occur. User PHIL also has a
database functionality of client/server, which LAD2ST11 changes to
Server. Among other customization actions, to change either the
adapter type or database functionality, the user can open up the
notebook for each node and change their attributes.
With the *.imp files generated, the user can drag and drop these
files onto a Start topology container. Start 1.1 will process the
migration import files with the following log entries:
***** Start of OCUMERGE.LOG *****
03-31-93 03:10:07 PM
Migrating file D:\REXX\JOHN.IMP into topology Topology.
Adapter type is unknown. It was set to Token Ring 16/4 /a.
However the node may contain a different adapter.
If so, the adapter type will need to be set in the node notebook
for this workstation.
JOHN Node migrated.
Created a DFT Connection from JOHN to HOST1.
Created a LAN Non-DFT Connection from JOHN to HOST2.
03-31-93 03:10:11 PM
Migrating file D:\REXX\TED.IMP into topology Topology.
Adapter type is unknown. It was set to Token Ring 16/4 /a.
However the node may contain a different adapter.
If so, the adapter type will need to be set in the node notebook
for this workstation.
TED Node migrated.
Created a DFT Connection from TED to HOST1.
Created a LAN Non-DFT Connection from TED to HOST2.
03-31-93 03:10:13 PM
Migrating file D:\REXX\MIKE.IMP into topology Topology.
Adapter type is unknown. It was set to Token Ring 16/4 /a.
However the node may contain a different adapter.
If so, the adapter type will need to be set in the node notebook
for this workstation.
MIKE Node migrated.
Created a DFT Connection from MIKE to HOST1.
Created a LAN Non-DFT Connection from MIKE to HOST2.
03-31-93 03:10:15 PM
Migrating file D:\REXX\DIANE.IMP into topology Topology.
Adapter type is unknown. It was set to Token Ring 16/4 /a.
However the node may contain a different adapter.
If so, the adapter type will need to be set in the node notebook
for this workstation.
DIANE Node migrated.
Created a DFT Connection from DIANE to HOST1.
Created a LAN Non-DFT Connection from DIANE to HOST2.
03-31-93 03:10:17 PM
Migrating file D:\REXX\PHIL.IMP into topology Topology.
Adapter type is unknown. It was set to Token Ring 16/4 /a.
However the node may contain a different adapter.
If so, the adapter type will need to be set in the node notebook
for this workstation.
PHIL Node migrated.
Created a LAN Domain Connection from MIKE to PHIL.
Created a LAN Domain Connection from TED to PHIL.
Created a LAN Domain Connection from DIANE to PHIL.
Created a LAN Domain Connection from JOHN to PHIL.
Created a DFT Connection from PHIL to HOST1.
Created a LAN Non-DFT Connection from PHIL to HOST2.
***** End of OCUMERGE.LOG *****
The five nodes will appear in the topology container with the
above mentioned connections and two generated host nodes. Host node
HOST1 was used to represent DFT connections, and host node HOST2 was
used to represent the non-DFT connections.
The user may now add or change values to the imported nodes and
even generate response files, LCU command files, or NetView DM/2
change files.