OSP - Parameters for z/OS Batch

The parameters for z/OS batch can be specified as subparameters of profile parameter OSP or macro NTOSP.

Possible settings See OSP Parameter Syntax.
Default setting See Keyword Subparameters.
Dynamic specification yes The parameter OSP can only be specified dynamically. In the Natural parameter module, use the macro NTOSP.
Specification within session no  

The following topics are covered:

OSP Parameter Syntax

The OSP parameter is specified as follows:


For information on subparameter names and values, see Keyword Subparameters.

NTOSP Macro Syntax

The NTOSP macro is specified as follows:

         NTOSP ABEXIT=value,                                           *
               DUMPDSN=value,                                          *
               LBPNAME=value,                                          *
               LEHDLR=value,                                           *
               SUBPOOL=value,                                          *
               TIOBSZ=(value1,value2),                                 *

See Keyword Subparameters.

Keyword Subparameters


ABEXIT - Abend Processing

ABEXIT=value specifies the mode of abend processing within Natural.

Value Explanation
ESTAE Natural intercepts all abends and issues the appropriate error messages.

This is the default value.

SPIE Only program checks (S0Cx abends) are intercepted.
OFF Natural does not intercept any abends or program checks at all. This value corresponds to profile parameter DU=FORCE.

The setting ABEXIT=OFF is not recommended because some functions, which require the abend interception, will not work any longer. The usage of profile parameter MT will cause an abend U0322 instead of error NAT0953 when the CPU time limit is reached.

DUMPDSN - Dump Data Set Name Prefix

DUMPDSN=value can be used to define the prefix for a dynamically allocated dump data set. Then each dump will be written by the z/OS service IEATDUMP to a separate data set instead of the standard data set (SYSUDUMP or SYSMDUMP). This can be very helpful in batch server environments when multiple dumps from different Natural sessions must be written.

The complete dump data set name will be as follows:

Value Explanation
1 - 8 characters High level qualifier for the dump data set name.
' ' (blank)

No dumps are written by means of IEATDUMP. Instead, any dumps are written to the standard dump data set (SYSUDUMP or SYSMDUMP) if allocated.

This is the default value.

LBPNAME - Sharing of Local Buffer Pools

LBPNAME=value controls the sharing of the local buffer pools when running multiple Natural sessions within the same region.

Value Explanation
1 - 8 characters Name of shared local buffer pool environment.
' ' (blank) The local buffer pools are not shared.

This is the default value.


  1. LBPNAME defines the name of the shared local buffer pool environment, and is used to locate the shared local buffer pool.
  2. When running multiple Natural sessions in a z/OS batch or TSO region concurrently, each session allocates storage for a separate local buffer pool. Except for the Natural z/OS batch mode server, the local buffer pools are not shared by default, that is, if the different sessions use the same Natural objects, these have to be loaded once for each session separately. If a name is specified, all Natural sessions will share the same local buffer pool.

LEHDLR - Use of an LE Error Handler for Calling LE Subprograms

LEHDLR=value specifies whether Natural uses an LE error handler for the call of LE subprograms.

Value Explanation
ON An LE error handler is set up by Natural during the call of LE subprograms. This means, if an unhandled LE error occurs during the execution of an LE subprogram, Natural will get control and can handle it (by issuing error NAT0954).

This is the default value.

OFF No set-up of an LE error handler is done by Natural during the call of LE subprograms. This means, if an unhandled error occurs during the execution of a LE subprogram, the LE enclave is terminated and so the Natural session is lost.


  1. For information on LE runtime options, see the description of source module NATLEOPT in the Installation for z/OS documentation.
  2. For information on Natural running with the IBM Language Environment, refer to Natural Execution - Miscellaneous Topics, LE Subprograms in the Operations documentation.

SUBPOOL - Storage Subpool for GETMAIN Requests

SUBPOOL=value specifies the storage subpool for GETMAIN requests.

Value Explanation
1 - 127 Subpool number.
0 This is the default value.


  1. The subparameter SUBPOOL is honored only in the Natural parameter module which is linked to the batch driver, but not in an alternative parameter module which is activated using a PARM= specification.
  2. As the subparameter SUBPOOL is evaluated during session initialization only, it cannot be specified as a dynamic subparameter.

TIOBSZ – Size of the Primary I/O Buffer for Batch Processing

TIOBSZ=(value1,value2) specifies the size of the primary I/O buffer for batch and/or server processing.

Value Explanation


Size of the primary I/O buffer in KB.
Batch size: 4 - 32 KB. It is allocated below the 16 MB line.
Server size: 32 - 999999 KB. It is allocated above the 16 MB line.

(8,64) This is the default setting.

Alternative Specifications:

  • TIOBSZ=10 or TIOBSZ=(10) defines only the batch size.

  • TIOBSZ=(,33) defines only the server size. The value which is not specified will remain unchanged.

USERID - Content of System Variable *INIT-USER

USERID=value specifies the content of the system variable *INIT-USER.

Value Explanation
ON The variable is set to either the user ID from the security access control block (ACEE) if a security package (as RACF or ACF2) is involved or the USER parameter from the job card.
OFF The user ID is the job name.

This is the default value.


  1. The content of *INIT-USER can be changed by the user ID exit NATUEX1 during session initialization.
  2. For further information, see Configuring Natural, Natural User Exits, NATUEX1 - User Exit for Authorization Control in the Operations documentation.

Example of OSP Parameter


Example of NTOSP Macro