This document describes the functionality of the Natural TSO Interface (product code NTI) and the operation and individual components of Natural under TSO in the operating system z/OS.
The following topics are covered:
Installing the Natural TSO Interface on z/OS in the Natural Installation for z/OS documentation.
The Natural TSO interface (
NATTSO) consists of a number of
service routines interfacing with the z/OS operating system.
NATTSO is supplied as a source module and can be customized
to meet your requirements; see also
Natural TSO Interface on z/OS in the Natural
Installation for z/OS documentation. You can either
assemble and link
NATTSO to the Natural nucleus or you can run it
separately by connecting it with a shared nucleus.
NATTSO is fully reentrant and can run above the 16 MB line.
Multiple Natural sessions can be started in parallel within one TSO region, and
you can toggle between the sessions by means of a
(see the corresponding subparameter of profile parameter
TSOP in the
Parameter Reference documentation).
For information on the driver parameters that are available for the
Natural TSO Interface, refer to the description of profile parameter
in the Parameter Reference documentation.
The following data sets are required if certain functions are used during a Natural TSO session:
||Software AG Editor Work File|
||Hardcopy Print Output|
||Dynamic Profile Parameter Report Output|
||Dynamic Profile Parameter Input|
||Additional Reports 01-31|
||External Trace Output|
||Job Submit Output|
||Load Library for External Modules|
||Work Files 01-32|
These data sets are described below.
Unless otherwise stated below, the default DCB
LRECL information is as follows:
LRECL=80 for sequential input
LRECL=133 for sequential output
The Software AG editor work file VSAM data set is required if a local
or global Software AG editor buffer pool is to be used. If not defined in the
JCL or by TSO command
ALLOC, the name of the Editor
work file specified by subparameter
EDBP or parameter
is used by Natural to do the dynamic allocation for the Editor work file.
Alternatively, profile parameter
EDPSIZE can be
used to run with an auxiliary editor buffer pool, which does not require an
editor work file. For more information about the installation of the Software
AG editor, refer to Installing the Software AG Editor
on z/OS in the Natural Installation for
The default name of the hardcopy print output data set is
CMHCOPY. It can be changed by one of the following:
DEST subparameter of profile parameter
the profile parameter
HCDEST, which is an
the setting of the system variable
during the session,
the terminal command
%H during the
The subparameters of the
CLOSE=FIN for the hardcopy print data set, that is, after the data
set is opened for output, any subsequent change of the hardcopy print output
data set name is not honored. If a different name is defined at open time, the
hardcopy data set will be closed upon the next terminal I/O.
During the session, the hardcopy data set can be released and
reallocated (before open or after close) by the by dynamic allocation (see
Natural Application Programming Interface
If the profile parameter
PLOG is set to
ON and data set
CMPLOG is available, the evaluated
dynamic profile parameters are written to this data set during session
initialization. If data set
CMPLOG is not available, the evaluated
dynamic profile parameters are written to the TSO terminal in line mode.
If available, this data set is read during session initialization to get dynamic profile parameters. Only the first 72 positions of each record are used to build a dynamic profile parameter string.
Any other profile parameters which are passed directly for the start of
the Natural nucleus, for example, by the TSO
command, are concatenated at the end of the parameter string which is build
from the input of
CMPRMIN; that is, these can be used to overwrite
the parameters from
These data sets can be used by Natural print file statements like
(nn). If no DCB information (for
available, the defaults are defined by the profile parameter
in the Natural parameter module. The print file data set names can be
overwritten by subparameter
If the profile parameter
ETRACE is set to
ON, or if the equivalent terminal command
was issued, any Natural trace output during the session is written to the
CMTRACE data set. To define the Natural components that shall be
traced, the profile parameter
If data set
CMTRACE is not available, it will be allocated
//CMTRACE DD SYSOUT=*
when the first trace record is to be written.
This data set is used for the Natural job submitting utility. If it is not defined, it will be allocated dynamically as
//NATRJE DD SYSOUT=(A,INTRDR)
when the first job is submitted.
STEPLIB is the default load library name for loading
external modules, for example, the shared nucleus (profile parameter
separate Adabas link routine module (profile parameter
session back-end program (profile parameter
and any external subprograms not linked to the Natural parameter module.
The load library name can be overwritten by profile parameter
The specified load library name must be defined in the TSO job control or by an
ALLOC statement, for example, in the CLIST which starts the
These data sets can be used by Natural work file statements like
READ WORK FILE
nn. If no DCB information
BLKSIZE, etc.) is
available in the JCL or in the VTOC entry for the data set, the defaults are
defined by the WORK profile
parameter or by the
macro in the Natural parameter module. The work file data set names can be
overwritten by subparameter
You can use the Natural example program TSO in library
SYSEXTP to issue TSO commands; for example:
TSO LISTALC STATUS
If you enter TSO without parameters, a menu prompts you for a TSO command. To exit from the menu, enter a period (.) in the first position, or press PF3.