This ドキュメント describes how to install a Natural Web I/O Interface server (product code NWO) under the runtime environment SMARTS on VM/CMS.
The following topics are covered:
For details, refer to the general section Prerequisites.
The installation tape contains the datasets listed in the table below. The sequence of the datasets and the number of library blocks needed are shown in the Report of Tape Creation that accompanies the installation tape.
Dataset Name | Contents |
---|---|
NWOvrs.EXEC |
Contains the modules needed to execute the Web I/O Interface server installation. |
NWOvrs.TAPE |
Contains the load modules of the Web I/O Interface server. |
APSvrs.TAPE |
Contains all SMARTS objects and modules. |
APSvrs.PLnn
|
Contains all SMARTS objects and modules of the
latest patch level nn .
|
NCFvrs.TAPE |
Contains the load modules of the Natural Com-plete Interface and the installation routine. |
ADA744.LX02 |
Adabas LCO. |
The notation vrs
in the dataset
names and in the program samples represents the version, release and system
maintenance level of the product.
Create the
.NWOvr.NWOvrs
directory and copy the file NWOvrs.EXEC
from the tape into this directory.
If the sequence number of
NWOvrs.EXEC
, as shown by the
Report of Tape Creation, is n,
you must position over 3 n - 2 tape marks (that is,
FSF 1
for the first dataset, FSF 4
for the second,
etc.).
CREATE DIRECTORY .NWOvr.NWOvrs (dirc ACCESS .NWOvr.NWOvrs B TAPE REW TAPE FSF (n) TAPE LOAD * *
In the VM directory entry of the NWO server, include the following directory control statement:
XCONFIG ADDRSPACE MAXNUMBER 16 TOTSIZE 64M SHARE
Define the virtual storage size as 64 MB, either in the
USER
statement or with a STORAGE
statement.
Ensure that the machine runs in XC architecture (CP command:
SET MACHINE XC
).
Access the following shared directories:
ACC .NWOvr.NWOvrs B /* NWO installation modules */ ACC .NATvr N /* Natural runtime directory containing your operative Natural */ ACC .NATvrs O /* Natural install library containing Natural MACLIB and TEXT files. */ ACC .ADAVvrs P /* Adabas TXTLIB */
Copy the file NATPARM ASSEMBLE
from your operative Natural
residing on directory NATvr
into the
NWO installation directory
.NWOvr.NWOvrs
.
COPYFILE NATPARM ASSEMBLE O = = B
Use XEDIT
to set the Natural profile parameter
NUCNAME=NATSRVvr
in the NATPARM
ASSEMBLE
file and replace rv
by
the corresponding version and release number. This nucname
NATSRVvr
is used in several
configuration and start-up parameter files. So it is not recommended to choose
a different nucname.
Use XEDIT
to set the Natural profile parameters
FNAT
, FUSER
,
FSEC
and FDIC
as you will use for
NWO. For further information, see Installing Natural under
VM/CMS in the Natural Installation
documentation.
Use XEDIT to configure your Unicode/Code Page Environment. For further information, see Configuration and Administration of the Unicode/Code Page Environment in the Unicode and Code Page Support documentation.
NATLODSV EXEC B
contains the variable
LOADLIST
and is called by the INSTNWO EXEC
(see
below) to build the Natural server module
NATSTVvr
.
You may wish to use XEDIT
to customize the contents of
variable LOADLIST
, for example, to include your own routines that
you defined as CSTATIC
in NATPARM
Run INSTNWO EXEC B
, which will perform the following
steps:
Creates and accesses shared directories on which the tape files for NWO, APS, and NCF are loaded.
Creates and accesses the shared run time directories for NWO
(NWOvrPRD
) and APS
(APSvrPRD
).
Sets up the shared run time directories for NWO and APS by several copy, merge and binding actions.
Builds the NWO front-end NCFvr
MODULE
.
INSTNWO EXEC
writes a log INSTNWO LOG A
.
Use XEDIT
to adapt the Natural web I/O interface server
NWOvrC RTS A
. At least yo have to adapt
the PORT_NUMBER
for your NWO server.
For information on how to configure the NWO server, refer to the section Configuring the Natural Web I/O Interface Server.
# --------------------------------- # NWO Configuration File # --------------------------------- FRONTEND_NAME = NCFvr PORT_NUMBER = 9999 TRACE_LEVEL = 31 HANDLE_ABEND = NO
This Zap illustrates how to modify VMID
of the ID table
manager in ADALCO
. For Adabas Version 7.4.4, the ADALCO
MODULE
resides on the shared file directory
.NWOvr.ADA74X02
.
For further information, see Adabas Installation for z/VM in
the Adabas Installation documentation.
NAME ADALCO ADALDI VER 0034 C4C2,C9C4,E2C5,D9E5 REP 0034 C4C2,C9C4,E2C5,D9E5
Access the following directories:
ACCESS .NWOvr.NWOvrPRD A ACCESS .NWOvr.APSvrPDR B ACCESS .NWOvr.ADA74X02 C /* ADALCO MODULE if ADAV74 */ ACCESS .ADAvr D /* Your ADABAS directory */
Run APSSTART EXEC
to start SMARTS.
SMARTS automatically launches the NWO server specified in the
STARTUPPGM
parameter of the SMARTS configuration file
SMARTS CONFIG A
.
Enter command DTASKS
to verify if SMARTS is
active. The DTASKS
should respond with a list of tasks running
under SMARTS. For example:
-
To terminate SMARTS and the Natural Web I/O Interface server, use the
command EOJ FORCE
.
APSOPC0030-* SMARTServer termination in progress APSSVR0027-* Server NCFNAT42 terminated APSPSX0031-SysName Waiting for 1 user(s) to terminate APSSVR0027-* Server OPERATOR terminated APSDIS0023-* Waiting for task group SYSTEM to quiesce APSDIS0023-* Waiting for task group DEFAULT to quiesce APSOPC0031-* SMARTServer terminated RASNSEPR - Termination processing RDR FILE 0284 SENT FROM nnnn PRT WAS 0284 RECS 0194 CPY 001 A HOLD NOKEEP
Check the output protocol in your Readerlist.