OSI/FTAM Configuration and Management Manual

Example FTAM Configuration Command Files
OSI/FTAM Configuration and Management Manual—421944-001
A-11
Command File to Configure Tandem FTAM
Addresses in OSI/AS
To execute this command file, run SCF and enter the following command at the SCF
prompt:
OBEY EXOSIUP
The EXOSIUP file consists of the following:
=============================================================
== File: EXOSIUP
==
== Example SCF command file to configure and start up OSI/AS
== and underlying processes in support of a Tandem FTAM
== installation.
==
== This SCF command file is specific to an X.25 network
== without SNDCF. An X.25 line named $SX250 must already
== exist.
==
== This command file uses the MIB files created by the
== OSI/AS input file DBFUP.
==
== Note 1: For many remote implementations, you must first
== set the OSI parameter for X.25 call user data packets
== by using the following PARAM command from the TACL prompt:
==
== PARAM TSP^PROTO^ID ON
==
== Note 2: For many implementations, you must first
== abort $SX250, delete any subdevices under $SX250, alter
== the X.25 source address to the correct X.25 source
== address for your installation, and then start the line
== again, before running this command file. For details,
== refer to the SCF Reference Manual for X25AM.
==
== Note 3: You may need to change the volume and subvolume of
== the OSI manager MIB to reflect your environment.
==
== To run this command file, you must be a member of
== the Guardian super user group (group ID 255).
==
=============================================================
== Clean up the OSI/AS subsystem first.
== (These commands require that no subdevices exist for
== the named TAPS and TSP processes.
=============================================================
ALLOW 3 ERRORS
STOP PROCESS $OSM1
STOP PROCESS $L51
STOP PROCESS $L41
ALLOW 0 ERRORS
=============================================================
== Create new OSI manager process.
=============================================================
OSIMGR /NAME $OSM1, NOWAIT, PRI 180, SWAP $OSI, CPU 2/1
=============================================================
== Name the MIB and start the OSI manager. NOTE: You may
== need to change the volume and subvolume of the OSI manager
== MIB to reflect your environment.
=============================================================
ALTER SUBSYS $OSM1, MIB $SYSTEM.OSI.ZOSIDB
START PROCESS $OSM1
DELAY 5
=============================================================