Previous Topic: Product Region JCL Parameters

Next Topic: Product Name Keys

Product Region JCL Parameter Descriptions

The following list provides detailed descriptions of the JCL parameters that the started task member of your product region can specify. The default value is underlined.

A

ARMNAME=name

Specifies the name used to register a region with the Automatic Restart Manager (ARM). If not specified, the default is SVM_acbname where acbname is the ACB name set by the PRI= JCL parameter. Use the XOPT= JCL parameter to set ARM options.

D

DBCS={ NO | YES | IBM | FUJITSU }

Specifies the DBCS option.

DSNQLCL

Specifies the name of the local VSAM data set qualifier. This value is used when allocating data sets.

DSNQLNV

Specifies the name of the local non-VSAM data set qualifier. This value is used when allocating data sets.

DSNQSHR

Specifies the name of the shared VSAM data set qualifier. This value is used when allocating data sets.

DSNQSNV

Specifies the name of the shared non-VSAM data set qualifier. This value is used when allocating data sets.

DYNVVOL=value

Specifies a default volume for dynamically allocating files. If this parameter is not specified, no volume is specified in the dynamic allocations and SMS allocates the files according to its rules.

I

INIFILE=filename

Specifies the INI file to use for customization of parameters.

INIRESET

Specifies that all current parameters are ignored and the defaults used. If an INI file is specified, do not use this parameter.

INIT={ NMINIT | name }

Specifies the name of the NCL procedure in the COMMANDS library that is executed during region initialization before VTAM ACBs are opened.

Limits: name must have one through eight characters.

INIWTO

Specifies that initialization messages are echoed to the system console.

INT={ 00 | nn }

Specifies which internal commands can be used. The parameter value comprises one hexadecimal byte, where each bit indicates acceptance of a particular command, as shown in the following table. The recommended value is INT=E4, that is, all commands shown in the table.

Bit

Command

Function

X'80'

SHOW STOR

Storage display

X'40

##AT, SH ##AT

AT-trap facility

X'20

##DP

Storage alter

X'10

(Reserved)

(Reserved)

X'08

(Reserved)

(Reserved)

X'04

##PMON

Performance monitor

X'02

(Reserved)

(Reserved)

X'01

(Reserved)

(Reserved)

N

NCLFM={ * | a }

(z/VM) Specifies the CMS filemode that applies to loading NCL procedures. This must be a valid CMS filemode.

NMDID=domainid

Defines the domain ID for this system. If the domain ID is not specified, the first characters (up to a maximum of 4) of the system primary ACB name, specified in the PRI parameter (or the default if not specified), are used as the default value.

The domain ID should be unique across all connected systems. If the value is not unique, it can produce naming conflicts, which restrict inter-system functionality, such as ROF sessions from background environments. Do not confuse this parameter with the system ID in the SYSTEMID parameter group.

Limits: One to four characters

NMSUP=userprefix

Specifies the System User Prefix that is used to prefix the user IDs for background system environments. If not specified, the domain ID is used. If the domain ID has not been specified, the first characters (up to a maximum of 4) of the system primary ACB name specified in the PRI parameter are used as the default value.

Limits: One to four characters

NOMODIFY

Specifies that communication between the operating system MODIFY facility and the product, using the system console, is not supported. If this operand is omitted, the use of MODIFY is supported.

NPF={ NO | YES }

Controls the use of NPF. Specify NO to inhibit NPF in the region. This is useful on test regions where security checking is not required but where a production UAMS is used.

NPFFM={ * | a }

(z/VM) Specifies the CMS filemode that applies when loading NPF tables. This must be a valid CMS filemode.

O

OPT={ 00 | nn }

Activates CPU accounting support. The parameter value comprises one hexadecimal byte, where each bit indicates the level of accounting, as shown in the following table, which lists the values of the OPT parameter.

Bit

Accounting

X'02'

CPU accounting for all threads

X'01

CPU accounting for NCL threads only

OSINP={ YES | NO }

Controls access to the OSCNTL data set. Access can be either read-only or update. Specifying YES (the default) indicates that the data set is opened for read only access. Specifying NO indicates that it is opened for update. When NO is specified, and an attempt to open the file for update fails, the region retries the open for read only access.

P

PRI={ NM | acbname }

Specifies the name of the primary VTAM ACB for the region to be used for terminal communication.

Limits: One to eight characters

Note: If this parameter is omitted, the default (NM) is also the default for the NMDID and NMSUP parameters, and the system ID in the SYSTEMID parameter group.

PROD={ product | (product1,product2,...productn) }

Specifies the list of product name key values for the features to include in the region. The PROD list implies that only the specified products are to be included in the region during initialization and that all other products are to be excluded.

Note: The list of included products cannot be modified without a restart of the region. Products not nominated in the PROD list are not resident in the region while it is active.

R

READY={ NMREADY | membername }

Specifies the name of the NCL procedure, in the COMMANDS procedure library, which executes as part of system initialization after VTAM ACBs have been opened successfully.

Limits: One to eight characters

S

SEC={ * | NO | PARTSAF | NMSAF | name }

Specifies whether the region uses a security exit.

If an asterisk (*) is specified, the region uses a security exit if one has been link edited into the NM001 load module. If no security exit has been link edited, then the region uses the NMUEX01 load module if it is in an accessible load library.

If NO is specified, no security exit is used. This specification overrides any link edited exit or the NMUEX01 load module.

If PARTSAF is specified, a vendor-supplied partial security exit that uses SAF is used.

If NMSAF is specified, the vendor-supplied security solution is used.

If name is specified, the named load module is loaded and used as the security exit. If this load module cannot be found, then the region terminates.

Important! If an abend occurs in the exit and the requested function cannot be performed, it is regarded as a security exposure and the region terminates. Message N00303 is sent to the console as a WTO, with RC=8.

Note: For more information about security exits, see the Security Guide.

SSID={ NO | * | name }

Specifies whether to establish a connection to a SOLVE Subsystem Interface (SSI) during initialization.

If NO is specified, then no connection to a SOLVE SSI is attempted. The connection is started (or attempted) only if the SSI parameter group requests a connection.

If an asterisk (*) is specified, then an SSID of the first four characters of your product region job name is used.

If name is specified, then a specific SSID must be entered.

If * or name is specified, then an attempt to connect to the SSI is made immediately. If it fails, it retries every n seconds, depending on the value in the SSI parameter group.

SSM={ NO | YES }

Specifies whether to enable support for CA OPS/MVS System State Manager (SSM).

Default: NO

SSMAPPL=application_name

Specifies the application name registered with CA OPS/MVS for this product or component.

Limits: Eight characters

Important! Each product or component registers a specific application name with CA OPS/MVS. Do not change this name.

The application name registered for CA SOLVE:Operations Automation and CA SOLVE:Operations Automation for CICS is SOLVE.

SSMHBI=heartbeat_interval

For SSM=YES, specifies how often to send heartbeats to CA OPS/MVS SSM. The heartbeat interval is in minutes. A value of zero indicates no heartbeat.

Initial value: 5

Limits: 0 through 60

T

TZ={ shhmmm | GMT }

Sets the internal time zone for your product region to a specific offset or Greenwich Mean Time (GMT). The operating system offset is ignored, and no changes will be detected or processed. Generally, you should not specify this parameter and your region runs on system local time.

The system hardware clock is usually set to GMT. The system local time is set by the operator when the operating system is initialized. The difference between the hardware time and the local time is the time zone offset from GMT.

When the hardware time is not set to GMT, you can use the TZ parameter to set this time. The region uses the system local time as the current time but uses the specified offset when calculating GMT.

s

Is plus (+) or minus (-), depending on whether the site is ahead (+) or behind (-) GMT.

hhmm

Specifies the four-digit hours and minutes value of the time zone offset.

Limits: 15 hours

If GMT is specified, then, assuming that the hardware clock is set to GMT, the internal time is set to GMT, rather than system local time. For example, if the system is four hours ahead of GMT and the local time is 5 pm, GMT time is 1 pm. Your region will use 1 pm as the displayed 'local' time.

U

UDBDEFER

Specifies that all UDB open processing is to be deferred and no attempts to open UDBs are to be made before the UDBCTL command is used.

NCL automatically attempts to open DD names that start with UDB on the assumption that they are utilized as UDBs. If specific processing options are required for UDBs, such as use of LSR pools, use the UDBCTL command to open the UDB with the required options.

Selecting DD names that do not start with UDB bypasses automatic open processing and requires opening by the UDBCTL command. Typically, UDBCTL commands to open UDBs are placed in the NMINIT or NMREADY procedures.

V

VFSENQ={ YES | NO }

Specifies whether the VFS data set is enqueued exclusively on initialization. The default is YES. NO blocks the ENQ and allows immediate restart.

When using the ABENDCMD command to restart a started task, z/OS do not hold the new task until the old one finishes dumping. This can cause errors during startup. For example, NCL dynamic allocation requests might fail if DISP=OLD is specified. Also, VSAM data sets might fail to open if SHROPTIONS 1 or 2 are in effect.

VSAMIO={ M | S | D }

Specifies how VSAM I/O is performed in your product region:

If significant VSAM activity is anticipated, specifying S improves processing overlap on multi-CPU machines.

W

WTO={ YES | NO }

Specifies whether the system console is to be sent monitor class messages if no definition exists for the system console user ID (usually ppppOPER).

X

XM={ TASK | ZIIP | BEST }

Specifies whether to move some processing performed by the main task of the region from the central processor (CP) to a zIIP.

Default: TASK or T

XOPT={ option | (option, option, ...) }

Specifies the following options (for example, for dump processing and ARM registration). This parameter can be specified more than once.

NOSXWEBU

(Default) Specifies that user security exit cannot handle web users.

SXWEBU

Specifies that user security exit has been modified to handle web users.

SDUMP

Specifies that write ABEND dumps to the SYS1.DUMP data set.

NOSDUMP

(Default) Specifies that send ABEND dumps to the normal dump data sets.

DAE

Specifies to provide DAE symptom information when writing an ABEND dump.

NODAE

(Default) Specifies that DAE symptoms information is not provided.

ARM

Specifies that the region tries to register with the Automatic Restart Manager (ARM), using an ARM element name specified through the ARMNAME= JCL parameter. If a registered region fails, the sysplex ARM restarts that region automatically.

NOARM

(Default) Specifies that the region does not register with ARM.

RLSU

Requests VSAM Record Level Sharing (RLS) for the UAMS file.

NORLSU

(Default) Specifies that VSAM RLS is not used for the UAMS file.

PVLOAD

(Default) Loads persistent variables when starting a region.

NOPVLOAD

Prevents the loading of persistent variables when starting a region.

PWMIX

Specifies that mixed case passwords are supported.

If you enable this support, consider the following important points:

  • Do not share a UAMS database with a region that does not support mixed case passwords and is not using a partial security exit.
  • Ensure that all regions in a multisystem environment have this support enabled.