home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR24
/
LAD2ST.ZIP
/
LAD2ST11.TXT
< prev
Wrap
Text File
|
1993-04-30
|
11KB
|
259 lines
LAD/2 TO START 1.1 BRIDGE APPLET (LAD2ST11.CMD VERSION 1.1)
-----------------------------------------------------------
INTRODUCTION
------------
The LAD2ST11.CMD applet converts clients defined in a LAD/2
workgroup into IBM LAN NetView Start 1.1 migration files. (A single
client from a workgroup can also be specified.) These files can be
dragged from an OS/2 directory folder and dropped on a Start topology
container to have LAD/2 clients represented in Start. This applet
does not modify any of the LAD/2 data files.
After using LAD/2, you can then use Start to modify your product
parameters; tune your configuration parameters for LAN Server,
Database Manager, and Communications Manager; and generate the
response files, LCU command files, and/or NetView DM/2 change files to
update the products on your workstation.
LAD2ST11 has the following parameters:
Parameters:
/LADPATH=source pathname of the LAD/2 main directory
/CUSTNAME=customer name
/WGNAME=workgroup name
/USERNAME=user name (or client name)
(optional - if not specified, all the users in the
workgroup are migrated)
/OFILE=fully qualified override file name
(optional - if not specified, no node, LAN adapter, or
LAN Server parameters will be overridden)
/MIGPATH=target pathname of an existing directory for the
generated Start migration files
(optional - defaults to the current directory)
The following example generates Start 1.1 migration files for all
the clients in the sales workgroup for the market customer. LAD2ST11
will expect the LAD/2 EXTD.TBL, LAPS.TBL, LS30.TBL, AND RECEIVER.TBL
data files to be stored in the y:\lad2\market\sales\ directory, and it
will expect the LAD/2 WORKGRP.TBL data file to be stored in the
y:\lad2\ladcode\ directory. (LAD/2 always stores the WORKGRP.TBL in
the LADCODE subdirectory.) The generated migration file will be
stored in the current directory, overwriting any old versions of the
files.
lad2st11 /ladpath=y:\lad2\ /customer=market /wgname=sales
The applet migrates many of LAD/2's configuration parameters.
Both DFT and non-DFT sessions are included in the migration file, as
well as information on LAN Server, local node names, LAN adapters,
etc. Information that had to be defaulted, modified, or extrapolated
during the bridging process will be logged.
OVERRIDE FILE
-------------
Users can specify an override file that replaces values in the
generated migration files, whether to override a default value or a
migrated value drawn from the LAD/2 data tables. The override file
applies to all the migration files generated during a single
invocation. You can limit the override file to a single client if you
include the /USERNAME= parameter in your LAD2ST11 invocation. Users
can specify the same or a different override file each time the applet
is run.
The override file allows users to specify the following:
* For Node information *
DBType /* req, svr, local, or stop */
LANType /* req, svr, dom, or stop */
EMType /* dft, lan or dft lan */
DEFLOCALCP /* 1-8 SNA characters */
CPALIAS /* 1-8 SNA characters */
BootDrive /* 1=A, 2=B, 3=C, etc. */
DBInstalled /* 1=A, 2=B, 3=C, etc. */
CMInstalled /* 1=A, 2=B, 3=C, etc. */
LANInstalled /* 1=A, 2=B, 3=C, etc. */
MachineType /* 4 alphanumeric chars */
MachineNum /* 3 alphanumeric chars */
MfgPlant /* 2 alphanumeric chars */
SerialNum /* 7 alphanumeric chars */
WKSTComment /* 1-60 characters */
NodeID /* 5 hex characters */
* For LAN Adapter information *
AdapterType /* token ring i, token ring ii, token ring /a,
token ring 16/4, token ring 16/4 /a, tr-unknown,
bus master token ring, ibm ethernet /a,
3comethermc, ungermann-bass niups2, or
wd ethercard plus /a */
AdapterSpeed /* 4 or 16 (for token ring connections) */
LocalAdminAdd /* 12 hex characters */
EMDestAdd /* 12 hex characters */
EMRUsize /* 4 digit number */
CSMLANID /* 1-8 SNA characters */
EthernetType /* 802.3 or DIX */
* For LAN Server/Requester information *
DomainName /* 1 - 8 characters from the LAN Character Set */
COMPUTERNAME /* 1 - 8 characters from the LAN Character Set */
FileAccessMode /* 1 - 12 (if < 3, random; = 3, mixed; > 3
sequential) */
The override file format is of the form:
keyword1 value1
...
keywordN valueN
There must be at least one white space between the keyword and
value. The keyword is not case sensitive, however, the value is. If
duplicate keywords are specified, the value of the last specified
keyword will be used. The LAD2ST11 applet will not check to see if
the specified values are in the valid range for the parameter or match
the correct format. Start will check the values when the file is
migrated into a topology.
For example, if the following override file was specified with:
WKSTCOMMENT My comment.
EMRUsize 1000
FileAccessMode
The following values would be changed and logged in the generated
migration files:
Overriding WKSTComment old value ' ' with new value 'My Comment.'.
Overriding EMRUsize old value '1920' with new value '1000'.
Overriding FileAccessMode old value '3' with new value ' '.
Since the override values apply to all the generated migration
files produced by an invocation of the applet, double check to insure
that the following keywords should be applied to all the clients in
your workgroup: DEFLOCALCP, CPALIAS, NodeID, LocalAdminAdd,
EMDestAdd, CSMLANID, DomainName, and COMPUTERNAME. Certain values,
such as COMPUTERNAME, should be unique to each workstation.
OCUNODE
-------
An alternate means of generating Start migration files is to run
OCUNODE on each of the client machines on which LAD/2 has installed
products. OCUNODE.EXE is the Start discovery program that derives
information about the workstation and places it into the created
migration file. An advantage of using the OCUNODE program is that it
will retrieve additional information that LAD2ST11 cannot, such as the
machine type and workstation comment, however, with LAD2ST11, you can
create your migration files from a single workstation using the
information stored in the LAD/2 data tables.
LAD/2 -> START MAPPINGS
-----------------------
The following lists the section parameters in the Start migration
file, their defaults, and how they were derived from the LAD/2 tables.
It is not recommended that you directly change the Start 1.1 migration
file. For more information on the migration process, please consult
the IBM LAN NetView Start 1.1 User's Guide. LAPS configuration data,
OS/2 Service Pack, and application information are not migrated to
Start.
*NODE*
<always present in the migration file>
EMAdapterNum (default - 3)
DBType Database Manager functionality (default - stop)
(Note: If requester/server, value is server.)
LANType LAN Server/Requester functionality (default - stop)
(Note: All servers are bridged as entry servers.
Backup domain controllers are bridged as
servers too.)
EMType Communications Manager functionality
(default - stop)
GWType (default - <blank>)
EMDFTSess #dft terminal and printer sessions (default - 0)
EMNDFTSess #non-dft terminal and printer sessions (default - 0)
DEFLOCALCP local node name (default - nodename)
CPALIAS local node alias (default - nodename)
OSversion (default - os/2 2.0)
BootDrive OS/2 install drive (default - 3)
DBInstalled Database Manager install drive (default - 0)
CMInstalled Communications Manager install drive (default - 0)
LANInstalled LAN Server/Requester install drive (default - 0)
MachineType (default - 0000)
MachineNum (default - 000)
MfgPlant (default - 00)
SerialNum (default - 0000000)
StartDFTSess1 dft session 1 name if autostart (default - <blank>)
StartDFTSess2 dft session 2 name if autostart (default - <blank>)
StartDFTSess3 dft session 3 name if autostart (default - <blank>)
StartDFTSess4 dft session 4 name if autostart (default - <blank>)
StartDFTSess5 dft session 5 name if autostart (default - <blank>)
StartNDFTSess1 non-dft session 5 name if autostart (default -
<blank>)
StartNDFTSess2 non-dft session 5 name if autostart (default -
<blank>)
StartNDFTSess3 non-dft session 5 name if autostart (default -
<blank>)
StartNDFTSess4 non-dft session 5 name if autostart (default -
<blank>)
StartNDFTSess5 non-dft session 5 name if autostart (default -
<blank>)
WKSTComment (default - <blank>)
NodeID local node ID (default - <blank>)
*EMDFTPARMS*
<one for each non-DFT session if Communications Manager is installed
and if DFT adapter is type 3>
SessionNum session number
SessionType session type (1 - terminal, 2 - printer)
SessShortID session short ID
PresSpace session presentation space (1 - 5)
PresSpaceRow (default - <blank>)
PresSpaceCol (default - <blank>)
SessionName session name
*EMNONDFTPARMS*
<one for each non-DFT session if Communications Manager is installed>
SessionNum session number
SessionType session type (1 - terminal, 2 - printer)
(default - 1)
SessShortID session short ID
PresSpace session presentation space size (1 - 5)
(default - 2)
PresSpaceRow (default - <blank>)
PresSpaceCol (default - <blank>)
LUName session name
LULocalAdd session NAU
ForAdapter (default - 0)
AdapType (default - LAN)
*ADAPTER*
<included for DFT type 3 adapter>
AdapterNum (default - 3)
AdapterType (default - dft 3270)
*ADAPTER*
<included for LAPS adapter>
AdapterNum (default - 0)
AdapterType adapter type
AdapterSpeed (default - 4)
(Note: Only present for token ring with speeds)
LocalAdminAdd locally administered address
(default and UAA - 000000000000)
(prefixed with an I if an ethernet address or
T if a token ring address)
EMDestAdd adapter destination address
EMRUsize (default - 1920)
CSMLANID network ID (default - CASMID)
EthernetType 802.3 or DIX (default - 802.3)
(Note: Only present if ethernet adapter)
*LANSRPARMS*
<included for LAN Server>
AdapterNum (default - 0)
DomainName domain name
COMPUTERNAME machine name
FileAccessMode (default - 3)