The complete syntax for the SET command is:

T [[DATE=yyyy.ddd][,CLOCK=hh.mm.ss]][RESET]

[,IPS=xx][,OPT=xx][,ICS=xx][,SMF=xx][,DAE=xx]

[,MPF={(xx[,xx]...)|NO}]

[,SLIP=xx][,PFK=xx][,IOS=xx][,EXS=xx][,SMS=xx][,MMS={xx|NO}][,PROG=xx]

[,DIAG=xx][,GRSRNL=(xx[,xx]...)]

[,APPC=(xx[,xx]...,L)][,ASCH=(xx[,xx]...,L)] [,SCH=(xx[,xx]...,L)]

[,CNGRP={(xx,[xx]...)}|NO ][,PROD=(xx[,xx]..)]

[,OMVS=(xx[,yy...,nn])

[,RTLS=(xx[,xx...])

Note: You may specify the operands in any order, and must specify at least one

operand. Do not put a comma before the first operand you specify. If you

specify DATE or RESET in a position other than the first, be sure to precede

it with a comma. If you specify only one parmlib member with APPC=,

ASCH=, SCH=, GRSRNL=, CNGRP=, MPF=, OMVS=, or RTLS=, you do not

need to enter the parentheses.

DATE=yyyy.ddd

The local date, where

v yyyy is the year, in the range 1900-2042, and

v ddd is the day, in the range 001-366.

1. The most distant date in the future you may specify is 2042.260.

2. The year must be within seventy (70) years of the GMT date or the system

ignores the entire SET command.

3. You must specify the year yyyy using four digits.

4. If you specify a new time that implies a change of date, you must explicitly

specify the new local date.

CLOCK=hh.mm.ss

The local time in hours (00-23), minutes (00-59), and seconds (00-59).

Chapter 4. MVS System Commands Reference 4-339

1. The system does not change the date when the new time implies a change

of date; if you want a new date, use the DATE parameter or wait for the

time to pass midnight.

2. If you specify CLOCK for day 2042.260, the last allowable date, the clock

value must not exceed 23.53.47. Later values may cause unpredictable

results.

The time zone constant which is used to calculate the local date and time is

reset to the value that was read in from the CLOCKxx member of the logical

parmlib during system initialization. The local date and time are changed

accordingly. When you specify RESET, omit DATE and CLOCK.

The following parameters determine which members of the logical parmlib the

system is to use. Use them only at the direction of the system programmer. For

more information on members of the logical parmlib, see OS/390 MVS Initialization

and Tuning Guide.

IPS=xx

The two alphanumeric characters indicating the IEAIPSxx member of the logical

parmlib that contains the new parameters SRM is to use.

Note: The SET IPS command is not valid on systems operating in workload

management goal mode. The command is supported on systems

operating in workload management compatibility mode.

OPT=xx

The two alphanumeric characters indicating the IEAOPTxx member of the

logical parmlib that contains the new parameters SRM is to use.

ICS=xx

The two alphanumeric characters indicating the IEAICSxx member of the logical

parmlib that contains the new installation control specifications SRM is to use.

Note: The SET ICS command is not valid on systems operating in workload

management goal mode. The command is supported on systems

operating in workload management compatibility mode.

SMF=xx

The two alphanumeric characters indicating the SMFPRMxx member of the

logical parmlib containing the parameters MVS/ESA is to use when restarting

SMF.

DAE=xx

The two alphanumeric characters indicating the ADYSETxx member of the

logical parmlib that contains the new parameters that dump analysis and

elimination (DAE) program is to use.

Note: The OPT=, ICS=, SMF=, and DAE= parameters affect the jobs in

progress as well as the jobs read and scheduled after the command.

MPF=(xx[,xx]...)

The two alphanumeric characters indicating the MPFLSTxx members of the

logical parmlib that are concatenated to form the MPF table. xx can represent:

v The message(s) being suppressed by MPF

v The action message(s) not being retained by the action message retention

facility

4-340 OS/390 V2R10.0 MVS System Commands

v The installation exit(s) to receive control for selected messages

v The status of the general WTO installation exit IEAVMXIT

v Whether this message is automated by MPF

v The MPFLSTxx member that identifies the message id, color attribute, or

command installation exit definition

v What color, intensity, and highlighting capabilities are in effect

v The status of the command installation exit routines specified in the logical

parmlib member MPFLSTxx

The MPF parameter on the INIT statement in the CONSOLxx member of the

logical parmlib controls which, if any, MPFLSTxx members are active at IPL.

Ends MPF processing (message suppression and presentation). NO is ignored

when specified in combination with a 2-character suffix.

SLIP=xx

The two alphanumeric characters indicating the IEASLPxx member of the

logical parmlib that contains the commands SLIP processing is to use.

PFK=xx

The two alphanumeric characters indicating the PFKTABxx member of the

logical parmlib that contains the PFK tables that are to be available for a

console. The PFK(xx) keyword on the INIT statement in CONSOLxx identifies

the PFKTABxx member that is available at IPL.

Note: The CONTROL command (K N,PFK=nnnnnnnn) must be issued to

invoke the PFKTABxx member specified in the SET command.

SMS=xx

The two alphanumeric characters indicating the IGDSMSxx member of the

logical parmlib that contains the parameters the system is to use when it starts

SMS. Specifying SMS=xx also starts SMS if it was not started at IPL or, restarts

SMS if it has stopped and can’t restart itself. Depending on the setting of the

PROMPT keyword in the IEFSSNxx member of SYS1.PARMLIB, this command

can display the parameters in the IGSMSxx member. (For a comparison of the

SET SMS command with the SETSMS command, see Table 4-30 on page

4-388.)

You can use SET SMS=xx to specify an IGDSMSxx parmlib member containing

PDSESHARING(EXTENDED) to migrate members of a sysplex to PDSE

extended sharing. This SET SMS command must be routed to every system

that was operating with a PDSESHARING(NORMAL) parmlib member. This

SET SMS for EXTENDED establishes that system’s preference, and causes it

to communicate with the other sysplex members that it would like to switch to

EXTENDED sharing. When all members have requested EXTENDED sharing,

the sysplex can migrate to that level of sharing. You may have to issue the SET

SMS=xx a second time to trigger the switch from NORMAL to EXTENDED

sharing. Each of the systems will issue message IGW306I when it migrates to

EXTENDED sharing.

MMS=xx

When the MVS message service (MMS) is not active, SET MMS=xx starts the

message translation service. When MMS is active, SET MMS=xx changes the

MMSLSTxx member. The two alphanumeric characters indicate the MMSLSTxx

member of the logical parmlib the system is to use.

Chapter 4. MVS System Commands Reference 4-341

Ends MMS processing and frees all allocated resources.

GRSRNL=(xx[,xx]...)

The two alphanumeric characters indicating the GRSRNLxx member(s) of the

logical parmlib that contain the specified GRS resource name lists. GRSRNL

allows you to change the current RNLs specified in one or more GRSRNLxx

member of SYS1.PARMLIB. Do not use parentheses when only one parmlib

member is specified.

For more detail on the use of the SET GRSRNL command, see OS/390 MVS

Planning: Global Resource Serialization.

Attention: You cannot specify the GRSRNL= parameter if GRSRNL has

already been set to EXCLUDE in the logical parmlib member

IEASYSxx.

IOS=xx

The two alphanumeric characters indicating the IECIOSxx member of the logical

parmlib that contains the parameters the system is to use to control MIH

processing and I/O timing processing.

The MIH timing intervals or the I/O timing intervals or the MIH timing intervals

and the I/O timing intervals are changed ONLY for devices that have MIH

statements coded in IECIOSxx.

1. IECIOSxx may also contain parameters that control hot I/O processing.

Using SET IOS=xx to change to another member does not affect the hot I/O

parameters; hot I/O processing is unchanged. Hot I/O processing

parameters can only be changed at system initialization time in response to

message IEA101A.

2. During IPL (if the device is defined to be ONLINE), or during the VARY

ONLINE process, some devices may present their own MIH timeout values,

via the primary/secondary MIH timing enhancement contained in the

self-describing data for the device. The primary MIH timeout value is used

for most I/O commands. However, the secondary MIH timeout value may be

used for special operations such as long-busy conditions or long-running I/O

operations. Any time a user specifically sets a device or device class to

have an MIH timeout value that is different from the IBM-supplied default for

the device class, that value will override the device-established primary MIH

time value. This implies that if an MIH time value that is equal to the MIH

default for the device class is explicitly requested, IOS will NOT override the

device-established primary MIH time value. To override the

device-established primary MIH time value, you must explicitly set aside a

time value that is not equal to the MIH default for the device class.

Note that overriding the device-supplied primary MIH timeout value may

adversely affect MIH recovery processing for the device or device class.

Please refer to the specific device’s reference manuals to determine if the

device supports self-describing MIH time values.

EXS=xx

The two alphanumeric characters indicating the EXSPATxx member of the

logical parmlib that contains the excessive spin recovery actions and the

excessive spin loop timeout interval.

4-342 OS/390 V2R10.0 MVS System Commands

APPC=(xx[,xx]...,L)

The two alphanumeric characters indicating the APPCPMxx parmlib member

that contains the desired APPC/MVS address space configuration that is

appended to the existing configuration. The APPCPMxx member can reside in a

logical parmlib or if no logical parmlib is specified, in any parmlib data set

specified on an //IEFPARM DD statement in the master scheduler JCL. The L is

optional and causes the system to display parmlib statements on the operator

console as they are processed.

ASCH=(xx[,xx]...,L)

The two alphanumeric characters indicating the ASCHPMxx parmlib member

that contains the desired APPC/MVS scheduler configuration that is appended

to the existing configuration. The ASCHPMxx member can reside in a logical

parmlib or if no logical parmlib is specified, in any parmlib data set specified on

an //IEFPARM DD statement in the master scheduler JCL. The L is optional and

causes the system to display parmlib statements on the operator console as

they are processed.

SCH=(xx[,xx]...,L)

The two alphanumeric characters indicating the SCHEDxx members of the

logical parmlib that contain the desired program properties table (PPT)

configuration. The L is optional and causes the system to display parmlib

statements on the operator console as they are processed.

The SET SCH command causes the system to replace the current PPT

definitions with the IBM-supplied default PPT definitions and the PPT definitions

from one or more SCHEDxx members that you specify on the command. The

effect of the command is not cumulative. The new PPT definitions take effect

immediately, without requiring a re-IPL of the system.

1. The SET SCH command only affects the PPT configuration statement.

2. If the SET SCH command fails, the current PPT configuration remains

active.

CNGRP=(xx,[xx]...)

The two alphanumeric characters indicating the CNGRPxx member of the

logical parmlib to be activated. This data is broadcast across the sysplex. It

references the logical parmlib only on the system where the command

executes, and activates only the CNGRPxx members found in that logical

parmlib.

The system is to remove all active console group definitions from the sysplex.

PROG=xx

The two alphanumeric characters indicating the PROGxx member of the logical

parmlib containing definitions that:

v Control the format and contents of the list of APF-authorized libraries

v Control the use of exits and exit routines

v Control the LNKLST concatenation by defining and modifying LNKLST sets

v Control the addition of modules to, and removal of modules from, the LPA

after IPL

You can use the SET PROG=xx command to control exits previously defined to

the dynamic exits facility. Dynamic exits services are implemented by:

v The EXIT statement of the PROGxx parmlib member. The EXIT statement of

PROGxx allows an installation to add exit routines to an exit, delete an exit

Chapter 4. MVS System Commands Reference 4-343

routine for an exit, change the state of an exit routine, change the attributes

of an exit, and undefine an implicitly defined exit.

Use the SETDMN command to change existing values of parameters in a single

domain. Issue the SETDMN command only at the direction of the system

programmer. The keywords that are valid for a given execution of the SETDMN

command are determined by:

1. The keywords specified in the current domain description table.

2. The values specified in the current installation performance specification (IPS).

At the system programmer’s direction, using the SETDMN command, you can

change the relative service distribution among domains. The relative service is

specified as a range of service rates for each domain, or as a fixed contention

index (FIXCIDX). Each relative service rate pair can be specified as an average

service per ready address space (ASRV) in the domain or as domain service totals

(DSRV). FIXCIDX is specified as a constant value which determines the relative

importance of the domain, regardless of the amount of service the domain

consumes.

Note: The SETDMN command is not valid on systems operating in workload

management goal mode. The command is supported on systems operating

in workload management compatibility mode.

The syntax of the SETDMN command is:

SD domainnum,{MIN=n1[,MAX=n2][,ASRV=(n0,n9) ] }

{ |,DSRV=(n0,n9) }

{ |,FIXCIDX=nnn }

{ }

{{ASRV=(n0,n9)}[,MIN=n1][,MAX=n2] }

{{DSRV=(n0,n9)} }

{{FIXCIDX=nnn } }

{ }

{MAX=n2[,ASRV=(n0,n9) ][,MIN=n1] }

{ |,DSRV=(n0,n9) }

{ |,FIXCIDX=nnn }

There are no defaults in the SETDMN command.

At least one keyword must be specified.

Duplicate keywords cannot be specified.

Keywords can be specified in any order.

Specifying the ASRV, DSRV, or FIXCIDX keywords overrides any previous value

set for them either in the current IPS or in another SETDMN command.

The value for n2 in the MAX=n2 parameter must be greater than or equal to the

value of n1.

The domain table entry (1-128) to be modified.

4-348 OS/390 V2R10.0 MVS System Commands

MIN=n1

The minimum multiprogramming level (0-999).

MAX=n2

The maximum multiprogramming level (0-999).

ASRV=(n0,n9)

Allows you to specify the average service per ready address space in the

domain. The value range is 0-999999999.

DSRV=(n0,n9)

Allows you to specify the total service rate for each domain. The value range is

0-999999999.

FIXCIDX=nnn

Allows you to specify the fixed contention index value for each domain. The

value range is 0-655.

Note: For more details about using SETDMN command parameters, see OS/390

MVS Initialization and Tuning Guide.

To set the maximum multiprogramming level (MPL) to 2 in domain 5, enter:

SETDMN 5,MAX=2

All other values in domain 5 remain unchanged.

To set the minimum MPL to 3 and the maximum MPL to 4 in domain 6, enter:

SD 6,MIN=3,MAX=4

For domain 2, to set the minimum MPL to 0, the maximum MPL to 255, and the

relative service at (1,5000) to control the average service rate per domain, enter:

SD 2,MIN=0,MAX=255,ASRV=(1,5000)

To set the contention index of domain 4 to a constant value of 300, enter:

SD 4,FIXCIDX=300

Use the TRACE command to:

v Start, stop, or modify system trace

v Start, stop, or modify master trace

v Start, stop, or modify component trace

v Start, stop, or modify transaction trace

v Display the current status of system trace, master trace, component trace, and

transaction trace

During system initialization, or whenever you reactivate system trace after a system

trace failure, the system creates a TRACE address space. That address space

contains the system trace table. When the TRACE address space is created, the

initial status of system trace (address space and explicit tracing functions) is on, the

initial status of the branch tracing function of system trace is off, and the initial

space set aside for system trace entries for each processor is 64K.

You can issue TRACE ST, TRACE MT, TRACE CT, and TRACE TT only from the

master console or another console with master authority. You can issue TRACE

STATUS from any console.

The complete syntax for the TRACE command is:

TRACE [STATUS ]

[ST[,nnnK][,BR={ON|OFF}] ]

[ST[,OFF] ]

[MT[,nnnK|,OFF] ]

[CT{,WTRSTART=membername[,WRAP|NOWRAP] ]} ]

[CT{,WTRSTOP=jobname} ]

[CT{[ ,ON ],COMP=name[,SUB=(sub)][,PARM=mem]} ]

[ |,nnnnK ]

[ |,nnnnM ]

[ |,OFF ]

[TT[{,COLL|C=collection name }] ]

{,CON=connection type }

{,COR=correlation info }

{,LU=logical unit name }

{,LVL=level }

{,NET=netid }

{,PKG=package name }

{,PLAN=|PL=plan name }

{,PRF=perform }

{,PROC|PR=proc name }

{,PRS=process }

{,SUB=subsystem }

{,TC=transaction class }

{,TRAN|T=transaction name}

{,USER|U=userid }

[,WTR=membername|STOP ]

[,LATENT=Y|N ]

[,BUFSIZ=nnnK|nnM} ]

[,OFF={nn|ALL} ]

Chapter 4. MVS System Commands Reference 4-513

|

|

The system is to display the current status of master trace. Status information

includes the current size of the master trace table.

The display tells the operator to use the DISPLAY TRACE command to obtain

status for system and component trace.

The system is to change the on or off status of system trace, the size of the

system trace table, or the on or off status of the branch tracing function of

system trace. Unless you specify ST,OFF, the system assumes you want to

recreate the TRACE address space if it has terminated and turn system trace

on if it is not on already.

nnnK

The amount of preferred, central storage in K bytes set aside for system

trace table entries for each processor. You can specify for nnn any decimal

number from 1 to 999. If you specify a number that is not a multiple of 4,

the system rounds it up to the next multiple of 4. If you omit this parameter,

the system assumes 64K for each processor, or the size established by the

last TRACE command during the IPL that specified a table size.

BR=ON or OFF

The system is to turn on or turn off the branch tracing function of system

trace. The address space and explicit tracing functions remain on as long

as system trace remains on. If you omit this parameter, the system

assumes that the status of branch tracing remains unchanged.

BR=ON is intended for use in system software problem determination and

diagnosis situations only. Branch tracing consists of tracing these four types

of branches:

v Branch and stack (BAKR)

v Branch and link (BALR)

v Branch and save (BASR)

v Branch and save and set mode (BASSM)

By enabling branch tracing you may be impacting system performance.

Note: You can not specify the BR= parameter if you specify ST=OFF.

The system is to stop system trace and free the system trace table. The

system does not terminate the TRACE address space. Therefore, if you

start system trace again while the TRACE address space is still active, the

on or off status of the different system trace functions and the size of the

system trace table return to the values they had the last time system trace

was on.

The system is to change the on or off status of master trace or the size of the

master trace table. Unless you specify MT,OFF, the system assumes you want

to turn turn master trace on if it is not on already.

nnnK

The master trace table size you want the system to use. You can specify for

nnn any decimal number from 16 to 999. If a master trace table already

4-514 OS/390 V2R10.0 MVS System Commands

|

|

|

|

|

|

|

exists, this new table replaces it. If you omit this parameter, the system

assumes a table size of 24K, unless you specified a different table size in a

previous TRACE command or, during system initialization, in a SCHEDxx

member of SYS1.PARMLIB.

The system is to stop master trace.

Specifies the component tracing options for an MVS component or an

application. The system programmer will supply the trace parameters. To

determine if the component to be traced allows the following parameters, see

″component traces″ in OS/390 MVS Diagnosis: Tools and Service Aids.

WTRSTART=membername

Identifies the name of the member that contains the source JCL that

invokes a component trace external writer. The system also opens the data

sets the writer uses. The member can be a SYS1.PROCLIB cataloged

procedure or a job. Many installations use a cataloged procedure in

SYS1.PROCLIB.

After you enter a TRACE CT,WTRSTART command, you should turn the

trace on and connect the writer with a WTR parameter in the reply for a

TRACE CT command or in a parmlib member, if specified.

WRAP or NOWRAP

If you specify WRAP, when the system reaches the end of the data set

or group of data sets, it writes over the oldest data at the start of the

data set or the start of the first data set. If you specify NOWRAP, the

system stops writing to the data set or sets when the data set or sets

are full.

If the WTRSTART parameter on the CTncccxx parmlib member or

TRACE CT command specifies NOWRAP, the system uses the primary

and secondary extents of the data set or sets. If the WTRSTART

parameter specifies WRAP or omits the parameter, the system uses

only the primary extent or extents.

WTRSTOP=jobname

Identifies the name of the job for a currently running component trace

external writer that the system is to stop. The system also closes the data

sets the writer used.

The jobname is either:

v Member name, if the source JCL is a procedure

v Job name, if provided on a JOB statement within the source JCL

Before you enter a TRACE CT,WTRSTOP command, you must either:

v Turn the trace off, or

v Disconnect the component trace external writer from the trace leaving the

trace on.

To disconnect the external writer while leaving the trace on enter the

TRACE CT,ON command with WTR=DISCONNECT in the reply or in a

CTncccxx parmlib member, if specified.

If the trace is not turned off or disconnected from the writer, message

ITT121I informs the operator of the condition and the writer will not stop.

Chapter 4. MVS System Commands Reference 4-515

If the component trace is currently off, a TRACE CT,ON command turns it

on. If the component trace is currently on and can be changed, a TRACE

CT,ON command changes the trace options. An installation-supplied

application trace can also have head level and sublevel traces, if specified

in the CTRACE DEFINE macro that defined the trace.

Whenever a trace that has sublevel traces is changed, all sublevel traces

currently in the LIKEHEAD state will also be changed. Therefore, a change

may cascade down a number of levels.

A head trace may have been defined so that it is not allowed to be changed

(HEADOPTS=NO on the CTRACE DEFINE macro). If this is the case, the

trace is really just a place holder for options for other traces.

nnnnK

nnnnM

Specifies the size, in kilobytes (K) or megabytes (M), of the trace buffer you

want the system to use. Specifying the buffer size also turns the trace on.

nnnnK is the buffer size in kilobytes, where nnnn is a decimal number from

1 to 9999. nnnnM is the buffer size in megabytes, where nnnn is a decimal

number from 1 to 2047.

When the size is not specified, the system uses the component-defined

default or the size specified in a CTncccxx parmlib member.

The size specified for an installation-supplied application trace must be

within the range specified on the CTRACE DEFINE macro for the trace; see

the programmer for the size value.

The system is to turn off tracing for the component. If the component is

connected to a component trace external writer, the trace will be implicitly

disconnected from the writer.

Some components do not turn tracing completely off. Instead, they reduce

the tracing activity to the minimum required for serviceability data in a

dump. If the CTRACE DEFINE macro that defined the trace specified the

MINOPS parameter, tracing is reduced to a minimum and component trace

writes a message to the operator.

If a component level trace has sublevel traces that are defined with the

LIKEHEAD parameter on the CTRACE DEFINE macro, the sublevel traces

will either be reduced to the minimal tracing or turned off, in the same

manner as their head level component trace.

COMP=name

Identifies the component trace affected by the command. name is the

external name for the component trace; it is provided for an IBM-supplied

component and must be provided by a system programmer for an

installation-supplied application trace. This parameter is required.

SUB=(subname)

Identifies a sublevel trace for a component or application with multiple

traces. Subname is defined by the component or installation-supplied

application.

4-516 OS/390 V2R10.0 MVS System Commands

The SUB parameter is limited to a single subname; multiple subnames are

not supported.

If the sublevel trace name contains any national characters (@ # $ _), you

must enclose the name in quotes. Otherwise, quotes are not required. In all

cases you may specify the alphabetic characters in upper or lower case.

If subname is a head level, all of the head’s sublevel traces that are defined

with a LIKEHEAD=YES parameter inherit the options specified in the reply

to this command. Therefore, the options you specify for a head level can

affect many sublevel traces.

Omitting the SUB parameter for a head level that is defined with

HEADOPTS=YES affects all sublevel traces with the LIKEHEAD attribute.

PARM=mem

Identifies a SYS1.PARMLIB member that contains the options to be used

for tracing. Using a parmlib member allows the operator to initiate the trace,

change it, or stop it without a message prompting for options.

Any option specified on the TRACE command overrides the option specified

in the parmlib member.

TT Specifies the transaction trace options. The system programmer will supply the

trace parameters. To determine which trace parameters to use, see ″Specifying

TRACE TT Options.″ For further information, see ″Transaction Trace″ in OS/390

MVS Diagnosis: Tools and Service Aids.

The information on this site is the combined effort of a lot of people, please credit the authors if you use their information.
Please read the Disclaimer page for the restrictions, copyright, and other uses of the information contained on this site.
For problems or questions regarding this web contact Bob.
Last updated: August 27, 2001.