This chapter contains reference information about SMC commands and control statements.
See Chapter 4, "SMC Utilities" for information about SMC utilities.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
As shown in Figure 2-1, the ALLOCDef
command includes the following parameters:
optionally, lists current default allocation settings.
LIst
is the default when no parameters are specified on the ALLOCDef
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
optionally, resets all default allocation values to original SMC default settings. Specify LIst
with this parameter to list these settings.
optionally, specifies the minimum level of drive exclusion. If a job is not allocatable at the minimum exclusion level, the SMC still excludes drives to the minimum level and allows the job to fail.
minlevel
indicates the minimum allocation exclusion level. Valid values are 0-8. 2 is the default.
Specifying MINLVL=0
indicates that the job will not be failed by the SMC even if the device and specific volume are incompatible. You can use MINLVL=0
to force SMC to allow allocation to succeed when a ”foreign” tape cartridge has the same volume serial number as an existing library or virtual volume.
Increasing minlevel
has no effect unless message SMC0045 or SMC0091 has been issued for a specific job step.
Refer to Oracle's ELS publication Configuring and Managing SMC for more information about SMC exclusion levels.
optionally, specifies the exclusion level at which affinity and GDG chains are separated.
Specify one of the following values:
an exclusion level between the minimum and maximum levels. When sufficient drives exist, SMC attempts to separate chains at this level. This value cannot be less than the minlevel
value.
Separate affinity and GDG chains for conflicting exclusion criteria whenever sufficient drives are available. This is the default.
Do not to separate affinity and GDG chains beyond the minimum level.
If HSC allocation previously specified UNITAFF(NOSEP)
and GDGALL(NOSEP)
, the default SMC exclusion tables can specify SEPLvl=3
in order to preserve existing behavior for scratch affinity chains with different media types.
Refer to Oracle's ELS publication Configuring and Managing SMC for more information about SMC exclusion levels.
optionally, enables or disables the DFSMS interface. When the DFSMS interface is enabled, the SMC invokes the DFSMS ACS routines. The returned constructs are used to influence device allocation of data sets. See ”SMSDef” on page 156 for information about using specific SMS features.
Specify one of the following values:
Disable the DFSMS interface. This is the default.
Enable the DFSMS interface.
optionally, specifies whether the SMC fails a job step during allocation when a communication failure prevents the retrieval of volume information from a TapePlex, or when no TapePlexes are available.
Specify one of the following values:
SMC does not fail the job step. This is the default.
SMC marks all devices ineligible and fails the job step.
If a communication failure occurs during the volume lookup process for a specific volume, or if no TapePlexes are available and the step contains allocations for specific volumes, the SMC marks all devices ineligible and fails the job step.
If the job step contains only scratch allocations, then the job step is allowed to proceed and allocation is based solely on SMC tape policy specifications.
optionally, specifies whether the EDL is updated at SSI24 time for compatibility with Computer Associates Unicenter CA-MIA Tape Sharing for MSP/EX and OS/390 product.
Specify one of the following values:
Do not update the EDL. This is the default.
Update the EDL. Specify this value if you use Unicenter CA-MIA.
optionally, specifies whether the DEFER
processing is performed at SSI24 time for compatibility with Computer Associates Real Time Stacking feature of its CA-1 tape management system.
Specify one of the following values:
Do not update DEFER
status. This is the default.
Update DEFER
status. Specify this value if you use the Real Time Stacking feature of CA-1.
optionally, enables or disables deferred mount processing for library mounts. With deferred mounting enabled, a library resident volume is mounted when the data set is opened. If the data set is not opened, the cartridge is not mounted, freeing the robot to perform other work If the data set is opened, however, the job waits until the cartridge is mounted.
Specify one of the following values:
Disable deferred mount processing and honor user JCL specifications.
Enable deferred mount processing. This parameter overrides the user's JCL and defers all ACS mounts until the data set is opened. This is the default.
optionally, directs the SMC to use a specified esoteric to allocate a specific external volume (that is, a volume that is not in a TapePlex). When this esoteric is used depends upon the setting of the modifier value specified after the esoteric, and whether the specified esoteric is valid (intersects with the original esoteric specification).
Specify one of the following values:
Disable EXTVOLesot
processing. If possible, select Nonlibrary drives when a specific external volume is allocated. This is the default.
Specifies an esoteric to be used to allocate a specific external volume when the ”use specvol” (UX08) or ”use library drives” (UX13) return code is specified. If the specific volume user exit returns the ”use specvol” (UX08) or ”use library drives” (UX13) return code for this DD, then any drives in the specified esoteric that intersect with the original esoteric will be selected for allocation. This is the default if esoteric is specified.
Whenever an external volume is allocated, select drives in the specified esoteric.
optionally, specifies the exclusion action when there are no scratch volumes in any TapePlex (ON
or OFF
), or in one or more ACSs within a TapePlex in a multiple ACS environment (INside
or OUtside
).
Specify one of the following values:
If an SMC POLICY object applies to an allocation event, then user exit 02 and user exit 08 are not called, even if active. The SMC POLICY object supplies all of the SMC tape policy is such instances. This is the default.
INside
specifies that all nonlibrary drives are excluded when there are no scratch volumes in any ACS, and there are library drives eligible for allocation. This is the default.
OUtside
specifies that all library drives are excluded when there are no scratch volumes in any ACS, and there are nonlibrary drives eligible for allocation.
This is the default. ON
indicates one of the following:
If scratch subpools are not being used, and one or more ACSs contain zero scratch volumes, then drives in those ACSs are excluded from the list of eligible devices.
If a scratch subpool is being requested (either though TAPEREQ
or User Exit 02/04), and one or more ACSs contain zero scratch volumes in the requested subpool, then drives in those ACSs are excluded from the list of eligible devices.
INside
specifies that all nonlibrary drives are excluded when there are no scratch volumes in any ACS, and there are library drives eligible for allocation. This is the default.
OUtside
specifies that all library drives are excluded when there are no scratch volumes in any ACS, and there are nonlibrary drives eligible for allocation.
All drives in all ACSs are to remain eligible for selection.
INside
specifies that all nonlibrary drives are excluded when there are no scratch volumes in any ACS, and there are library drives eligible for allocation. This is the default.
OUtside
specifies that all library drives are excluded when there are no scratch volumes in any ACS, and there are nonlibrary drives eligible for allocation.
optionally, specifies whether scratch user exit 02 or specific user exit 08 are called when an SMC POLICY object is found that applies to the allocation event.
Specify one of the following values:
If an SMC POLICY object applies to an allocation event, then user exit 02 and user exit 08 are not called, even if active. The SMC POLICY object supplies all of the SMC tape policy is such instances. This is the default.
If an SMC POLICY object applies to an allocation event, then the scratch user exit 02 or specific user exit 08 are called and any non-conflicting user exit policy is applied to the same allocation event.
Note:
This setting is recommended only for those customers with CA-Vtape installed who are using a default SMC POLICY object but where CA-Vtape supplied user exits are required.
Only non-conflicting policies from the user exit are applied. Thus, if the SMC policy specifies an esoteric, or a TapePlex name, and user exit 02 or user exit 08 also specifies an esoteric or TapePlex name, the SMC policy specifications will apply. Refer to Oracle's ELS publication Configuring and Managing SMC for more information about SMC interaction with CA-Vtape.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC ALLOCJob
command enables you to override SMC default allocation parameters by job name, step name, and PROC step.
Note:
The SMS parameter is no longer supported for this command. If necessary, code your SMS ACS routines to select jobnames.As shown in Figure 2-2, the ALLOCJob
command includes the following parameters:
optionally, lists current default allocation settings and override settings (in the order they are processed) by job name, step name, and PROC
step.
LIst
is the default when no parameters are specified on the ALLOCJob
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
optionally, removes all job name, step name, and PROC
step overrides for allocation.
If no other parameters are specified, allocation overrides are removed for all jobs.
If only JOBname
is specified, allocation overrides are removed for ALL ALLOCJob
entries for that job name.
If JOBname
, STEPname
and PROCstep
are specified, allocation overrides are removed only for the specified entry.
Global allocation settings are not affected by this parameter.
optionally, specifies a job name. This parameter is required unless LIst
or OFF
is specified.
jobname
indicates the job name. The value entered must be one to eight characters in length. An asterisk (*) can be used as a wildcard when included as the last character. ALLOCJob is set for all jobs whose job names match the characters preceding the asterisk.
optionally, specifies a step name. This parameter is only valid when JOBname
is also specified.
stepname
indicates the step name. The value entered must be one to eight characters in length. An asterisk (*) can be used as a wildcard when included as the last character.
optionally, specifies a PROC
step. This parameter is only valid when JOBname
and STEPname
are also specified.
procstep
indicates the PROC
step. The value entered must be one to eight characters in length. An asterisk (*) can be used as a wildcard when included as the last character.
optionally, specifies that SMC allocation influencing is not performed for the indicated job (jobname
, stepname
, or procstep
).
This parameter cannot be specified with the MINLvl
, SEPLvl
, or SMS
parameter. It is only valid when JOBname
is also specified.
Note:
It is recommended that you useMINLV=0
instead of BYPASS
, unless no mounts will be performed (that is, IEFBR14 jobs).optionally, specifies the desired minimum level of drive exclusion. If a job is not allocatable at the minimum exclusion level, the SMC still excludes drives to the minimum level and allows the job to fail.
This parameter cannot be specified with the BYPass
parameter. It is only valid when JOBname
is also specified.
minlevel
indicates the desired minimum allocation exclusion level. Valid values are 0-8. 0 indicates that the SMC will not exclude any drives, even if all drives would be excluded during level 1 exclusion processing. The default is the current value of the ALLOCDEF MINLVL
setting. Refer to Oracle's ELS publication Configuring and Managing SMC for more information about SMC exclusion levels.
MINLVL=0
indicates that the job will not be failed by the SMC even if the device and specific volume are incompatible. MINLVL=0
may be used to force SMC to allow allocation to succeed when a ”foreign” tape cartridge has the same volume serial number as an existing library or virtual volume.
Increasing minlevel
has no effect unless message SMC0045 or SMC0091 has been issued for a specific job step.
optionally, specifies the exclusion level at which affinity and GDG chains are separated. This parameter cannot be specified with the BYPass
parameter. It is only valid when JOBname
is also specified.
Specify one of the following values:
an exclusion level between the minimum and maximum levels. When sufficient drives exist, the SMC attempts to separate chains at this level. Refer to Oracle's ELS publication Configuring and Managing SMC for more information about SMC exclusion levels. The seplevel
value cannot be less than the minlevel
value.
Do not separate Affinity and GDG chains beyond the minimum level.
Separate Affinity and GDG chains for conflicting exclusion criteria whenever sufficient drives are available. This is the default.
Interfaces:
Console, utility, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required
As shown in Figure 2-3, the CMDDef
command includes the following parameters:
optionally, lists the current command prefix.
This is the default if no parameters are specified. It cannot be specified with any other parameter.
optionally, specifies a command prefix for the SMC subsystem. This parameter may only be specified in the SMCPARMS
data set.
command-prefix
indicates the command prefix. The value entered must be one to eight characters in length and meet the following requirements:
Valid characters include A-Z 0-9 @ ¢ $ # , . / ’ ( ) < > * & + - = | ! ; : ” % _ ?
The command prefix cannot include a command string, a command abbreviation, or any string that invokes a command.
The command prefix cannot include a string that is a subset or superset of an existing prefix beginning with the same character.
Note:
The MSP command,DISPLAY OPDATA
, displays all active command prefixes and their corresponding subsystem name.Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC COMMtest
command performs an end-to-end communication test between SMC and defined TapePlexes or VLEs. This command can generate a request for all paths to all TapePlexes, regardless of their status. The COMMtest
command does not update any error statistics or path status, but does display messages indicating the communication result.
Note:
Only HSC TapePlexes or VLEs are eligible for theCOMMtest
command.As shown in Figure 2-4, the COMMtest
command includes the following parameters:
optionally, restricts communication to the specified TapePlex. By default, communication with all defined TapePlexes is attempted.
tapeplex-name
indicates the TapePlex name as defined by the SMC TAPEPlex
command. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit, or hyphen.
TAPEPlex
and STORMNGR
are mutually exclusive.
optionally, restricts communication to the specified VLE. By default, communication with all defined VLEs is attempted.
stormngr-name
indicates a VLE name as defined by the SMC STORMNGR
command.
TAPEPlex
and STORMNGR
are mutually exclusive.
optionally, restricts communication to the specified server path. When specifying this parameter, TAPEPlex
or STORMNGR
must also be specified. By default, communication with all server paths is attempted.
server-name
indicates the server path name as defined by the SMC SERVer
command. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit, or hyphen.
The local server path, if any, is tested. By default, only defined remote server paths are tested.
All server paths, both local and remote, are tested.
Communication is attempted on all communication paths, including paths that were disabled by an operator command or by the SMC. By default, the communications test is performed on any communication path that is active, inactive, or never active. Specification of ANYSTATus
also includes disabled communication paths.
Interfaces:
Console or utility
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
As shown in Figure 2-5, the DISMount
command includes the following parameters:
optionally, the volume to be dismounted. The volume is dismounted only if the volume on the drive matches the specified volser. If volser
is omitted, any volume that is on the drive is dismounted.
The MSP device address for which the volume is to be dismounted. The device must be defined by a TapePlex known to SMC.
This is a required value.
Note:
Ifvolser
is omitted, a comma must precede the device address.optionally, indicates that if a loaded volume is found on the drive, it should be rewound and unloaded before attempting the requested dismount. This parameter is not supported for virtual drives.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC Display DRive
command displays SMC drive attribute and TapePlex ownership information.
Note:
TapePlex drive information can also be obtained by issuing the HSCDisplay DRives
command through the SMC Route
command.As shown in Figure 2-6, the Display DRive
command includes the following parameters:
a device number, range of device numbers, or list of device numbers to be processed. If specified, all device addresses specified are displayed. The devnum
form of the Display DRive
command is the only way that defined devices that are not TapePlex owned, or not defined by an SMC UNITAttr
command, can be displayed.
devnum
, devnum-range
, and devnum-list
are mutually exclusive with all other Display DRive
parameters.
optionally, lists only devices owned by the specified TapePlex.
name
indicates the TapePlex name. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit, or hyphen.
optionally, lists only ”real” (that is, nonvirtual) devices owned by the specified TapePlex.
optionally, lists only virtual devices owned by the specified TapePlex.
optionally, lists all devices owned by the specified TapePlex. This is the default if no parameters are specified.
optionally, lists only ”real” (that is, nonvirtual) devices owned by SMC-defined TapePlexes.
optionally, lists only virtual devices owned by SMC-defined TapePlexes.
optionally, lists only ”real” devices that are not owned by any SMC-defined TapePlex, but have UNITATTR
statements defined.
optionally, lists all devices owned by SMC-defined TapePlexes.
optionally, lists only drives currently mounted or awaiting mounts according to SMC internal data.
Note:
If aDisplay DRive
command is issued without any parameters, by default, the SMC lists all real and virtual devices owned by SMC-defined TapePlexes.optionally, displays informational message SMC0178, identifying the drive serial number.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (supports XML and CSV)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC Display POLicy
command displays information for a named policy. This command provides the same output as the SMC POLicy
command with the LIst
keyword.
As shown in Figure 2-7, the Display POLicy
command includes the following parameters:
optionally, specifies the name of a policy that matches the name specified in a TAPEREQ
or DFSMS ACS routine management class.
name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name
, if specified, must be the first parameter.
This is a required value.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (supports XML and CSV)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC Display RC
command displays information about the meaning of an SMC return or reason code, or an HSC or VTCS UUI reason code.
As shown in Figure 2-8, the Display RC
command includes the following parameters:
optionally, specifies that the reason or return code value or range is specified as a hexadecimal number.
optionally, lists the return codes for which the explanation is to be displayed.
If X
or HEX
is specified, the value may contain hexadecimal characters 0-9 and A-F.
If X
or HEX
is not specified, the value may contain only numeric characters.
A range specified from the console may contain a maximum of 16 values.
optionally, indicates that all defined return or reason codes are to be listed. ALL
is permitted only from a utility. ALL
and H
or HEX
are mutually exclusive.
optionally, indicates that detailed information about the requested codes is to be listed.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (supports XML and CSV)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC Display
SERVer
command displays information for a named server. This command provides the same output as the SMC SERVer
command with the LIst
keyword.
As shown in Figure 2-9, the Display SERVer
command includes the following parameters:
indicates the server name to be defined, modified, or listed. This is a required value.
name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name
, if specified, must be the first parameter.
The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit, or hyphen.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (supports XML and CSV)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (supports XML and CSV)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC Display STORMNGR
command displays information for a named VLE. This command provides the same output as the SMC STORMNGR
command with the LIst
keyword.
As shown in Figure 2-11, the Display STORMNGR
command includes the following parameters:
Specifies the VLE to be defined, modified or listed. This name is also defined to VTCS, and is initially defined by the VLE GUI. If name
is not specified, then all VLEs are listed.
name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name
, if specified, must be the first parameter.
The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit, or hyphen.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (supports XML and CSV)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC Display TAPEPlex
command displays information for a named TapePlex. This command provides the same output as the SMC TAPEPlex
command with the LIst
keyword.
As shown in Figure 2-12, the Display TAPEPlex
command includes the following parameters:
indicates the TapePlex name to be added, modified, or listed. This is a required value.
name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name, if specified, must be the first parameter.
The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit, or hyphen.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC Display Volume
command displays volume attribute and TapePlex ownership information.
Note:
TapePlex volume information is also available by issuing the HSC Display Volume
command through the SMC Route
command.
When the server is ACSLS, this command displays NONE
for MEDIA
and RECTECH
.
As shown in Figure 2-13, the Display Volume
command includes the following parameters:
indicates the volser
, volser range
, or volser list
to be processed. If multiple volumes are specified, only the first 100 are queried. This is a required value.
optionally, specifies that all active TapePlexes are queried for the specified volser
, volser-range
, or volser-list
. If specified, multiple display lines may be listed for the same volser
if it is defined in multiple TapePlexes.
If this parameter is not specified, the Display Volume
command queries TapePlexes in the order they are defined and lists only the first occurrence of the volume.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC DRIVemap
command maps client drive addresses to server drive addresses. This command enables users to specify different MSP device addresses on different hosts for the same TapePlex or virtual drives in client/server mode.
Note:
Refer to Oracle's ELS publication Configuring and Managing SMC for more information about drive mapping and for information about usingDRIVemap
commands and the HSC DRVHOST
parameter when client and server addresses differ.As shown in Figure 2-14, the MNTD
command includes the following parameters:
optionally, lists all current DRIVemap
mappings.
LIst
is the default when no parameters are specified on the DRIVemap
command. In this case, all DRIVemap
entries are listed.
LIst
may be specified with other parameters. In this case, the LIst
is applied after the other parameters are processed.
optionally, removes all current DRIVemap
mappings. When specified with CLient
, this parameter removes DRIVemap
ranges specified in the CLient
parameter.
optionally, specifies the device numbers mapped by the DRIVemap
command.
devnum
, devnum-range
, or devnum-list
indicates the device number, device number range, or device number list.
optionally, specifies the device numbers that are defined on the HSC server.
devnum
, devnum-range
, or devnum-list
indicates the device number, device number range, or device number list.
The ranges and lists must match those in the CLient
parameter. For example:
CL(AA0-AA2) SE(BA0-BA2)
is valid.
CL(AA0-AA2) SE(BA0, BA1, BA2)
is invalid.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
As shown in Figure 2-15, the Help
command includes the following parameters:
Note:
If you enter theHelp
command without any parameters, information is displayed for all available SMC commands.optionally, indicates an SMC command name.
optionally, indicates the four-digit numeric portion of an SMC message identifier. Leading zeros are not required.
optionally, indicates a range of SMC messages specified using the four-digit numeric portion of the message identifier.
optionally, indicates a full SMC message identifier.
optionally, indicates a range of SMC messages specified using full message identifiers.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: All (No XML/CSV output)
Subsystem Requirements:
Active SMC required
The SMC HTTP
command starts an SMC socket listener component that supports a limited subset of HTTP capabilities, and enables the local SMC subsystem to act as an HTTP server for SMC client subsystems on other hosts. Requests that are sent from other SMC client subsystems to this SMC with an active HTTP Server component are processed by the local HSC.
The SMC HTTP
command should only be executed on hosts where an HSC subsystem is executing; otherwise the HTTP
command provides no operational benefit.
SMC subsystems on other hosts that will be clients to this local SMC with active HTTP Server component must use the SMC SERVER
command to define the communications path to this host.
As shown in Figure 2-16, the HTTP
command includes the following parameters:
optionally, displays SMC HTTP server status information and interval statistics.
optionally, lists I/O, error, accept and reject counts, and CGI module use count information in addition to information displayed in the LIst
command.
optionally, starts the SMC HTTP server.
optionally, specifies the port number to be listened to for incoming requests.
nnnn
indicates the TCP/IP port number. It is recommended that you do not specify well know TCP/IP port numbers. If not specified, The default is 8080
.
optionally, stops the SMC HTTP server.
optionally, directs SMC to process the HTTP
STOp
command even if the status of the SMC HTTP server is not active. Use this parameter only if there has been an unrecoverable HTTP service task termination and the normal SMC HTTP STOp
command has been rejected.
optionally, specifies whether the XAPI user password security protocol is globally enforced for requests processed by this HTTP server.
specifies that the XAPI security protocol is enforced for this server. This is the default setting.
specifies that the XAPI security protocol is not enforced for this server.
optionally, directs SMC to process the HTTP STOp
command even if the status of the SMC HTTP server is not active. Use this parameter only if there has been an unrecoverable HTTP service task termination and the normal SMC HTTP STOp
command has been rejected.
The following parameters can be entered with STArt
or after HTTP startup. It is strongly recommended that you do not change the default values for these parameters unless directed by Oracle StorageTek Software Support.
optionally, specifies the maximum number of SMC HTTP socket I/O tasks to start.
n
indicates the number of I/O tasks.
Note:
TheHSIOtasks
parameter cannot be specified after HTTP server startup, it must be specified as part of the HTTP START
command. However the remaining tuning parameters, MAXClients
, SQUELEN
, and WQUELEN
may be changed after SMC HTTP server startup has completed.optionally, specifies the maximum number of connected requests that will be allowed simultaneously.
nnn
indicates the number of requests. This value must be between 1 and 300. The default value is 100.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required. Not allowed as input to the SMCUSIM
utility.
The SMC LIMIT
command enables you to limit resource usage in the SMC subsystem. This command can limit exposure to Sx78 type abends.
By default, the SMC subsystem starts a new SMC work task whenever a new request is received but no free SMC work task is available. This default behavior manifests using the default LIMIT
settings of LIMIT AUTO OFF
and LIMIT MAXTASKS OFF
.
However, depending upon the SMC subsystem work load, the SMC subsystem may attempt to start work tasks beyond the limits of SMC subsystem resource availability. This may cause Sx78 type abends due to virtual memory constraints. Such abends may lead to misdirected allocation, lost mount conditions, or loss of the SMC subsystem altogether.
If you specify LIMIT AUTO ON
or LIMIT MAXTASKS
nnn
to override the default SMC subsystem behavior, then SMC queues requests for new work when the calculated or specified SMC work task limit is reached.
LIMIT AUTO ON
causes SMC to use a calculated work task limit based upon SMC subsystem availability.
LIMIT MAXTASKS
nnn
causes SMC to use the specified work task limit.
The calculated or specified SMC work task limit acts to slow the processing for new requests. For example, if the calculated or specified SMC work task limit is 200, and a new request is received when 200 SMC work tasks are already active, then the new request is queued and waits until either an existing SMC work task completes its processing, or the LIMIT MAXIDLE
nnn
time elapses.
If the LIMIT MAXIDLE
nnn
time elapses and no existing SMC work task completes its processing, then the SMC starts a new work task to process the new request even though the number of work tasks now exceeds the calculated or specified work task limit. Therefore, the calculated or specified work task limit is a "soft" limit.
The default LIMIT MAXIDLE
time is ten seconds. Therefore, the number of additional SMC work tasks above the calculated or specified work task limit is limited to one new work task every ten seconds until existing work tasks complete their processing.
Note:
Oracle recommends that you only use theLIMIT
command to change the default LIMIT
settings if your SMC subsystem experiences Sx78 type abends.As shown in Figure 2-17, the LIMIT
command includes the following parameters:
limits the number of work tasks within the SMC subsystem. Work tasks process operator commands, allocation queries, mount and dismount requests, and TCP/IP connections to remote hosts, and other system processes. Typically these requests are short lived and their resources are reusable.
the maximum number SMC subsystem work tasks, between 16 and 500.
specifies no MAXTasks
limit. The default value is OFf
which implies the maximum MAXTasks
limit of 500 work tasks.
optionally, limits the number of work tasks within the SMC subsystem that can be connected to a remote server at once. These work tasks are a subset of MAXTASKS
.
The LIMIT MAXClients
command is different from the HTTP MAXCLIENTS
command:
The LIMIT MAXClients
limits the number of client connections on the client side of client/server.
The HTTP MAXClients
limits the number of client connections on the server side of client/server.
The number of SMC subsystem socket I/O work tasks between 1 and 500.
specifies no MAXClients
limit. The default value is OFf
which implies the maximum MAXCLIENTS
limit of 500 SMC work tasks.
optionally, limits the amount of time that the SMC subsystem waits before starting a new work task in excess of the calculated or specified work task limit when new requests are received.
The number of seconds between 0 and 2400. The default is 10 seconds.
Restores the default value of 10 seconds.
optionally, specifies whether the SMC subsystem automatically sets a MAXTasks
limit based on the amount of resources available.
specifies that the SMC subsystem will automatically set a MAXTasks
limit if not overridden by the MAXTasks
parameter.
Specifies that the SMC subsystem will not automatically set a MAXTasks
limit.
optionally, resets all LIMIT
settings to their default values.
optionally, lists the current LIMIT
parameter settings. If LIMITS
is entered without any command parameters, a LIst
is performed.
optionally, lists SMC resource usage and calculated maximum number of work subtasks supported.
Note:
When LIMIT AUTO ON
is specified, the SMC calculates the maximum number of SMC work tasks that it can support. This calculation is performed whenever the SMC starts a new work task that results in a new hi-water SMC work task count.
The calculation for maximum number of SMC work tasks is based on storage usage in various subpools. However, the actual maximum number of SMC work tasks than can be supported in practice is based on the types and timing of requests, and general system workload. The calculation only results in a rough estimate which can change as new subtasks are started.
LIMIT MAXTASKS
nnn
overrides the LIMIT AUTO ON
or LIMIT AUTO OFF
setting. Therefore, if both LIMIT MAXTASKS 190
and LIMIT AUTO ON
are specified, SMC limit processing is triggered when the number of SMC work tasks reaches 190, regardless of the SMC subsystem calculation of the maximum number of work tasks.
LIMIT MAXCLIENTS
is different from HTTP MAXCLIENTS
. LIMIT MAXCLIENTS
imposes restrictions on TCP/IP socket connections on the client side of client/server while HTTP MAXCLIENTS
imposes restrictions on TCP/IP socket connections on the server side of client/server.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC LIst
command displays storage accessible from the SMC started task address space.
This command is intended to be used primarily as directed by Oracle StorageTek Software Support. Output is intended for debugging and support purposes.
As shown in Figure 2-18, the LIst
command includes the following parameters:
optionally, specifies the address at which to begin listing SMC memory contents.
address
indicates the address. The value entered must be a valid hexadecimal address.
optionally, specifies the length of SMC memory (bytes) to be listed. Length
is required if Address
is specified.
length
indicates the value entered must be a valid hexadecimal value between 1 and FFFF. Memory is listed beginning at the location specified in the Address parameter. The default value is 100 (decimal 256).
optionally, specifies the internal SMC control block to be listed.
control-block-name
indicates the control block name.
SMC control blocks are listed for diagnostic purposes. Specify control-block-name
only as directed by Oracle StorageTek Software Support.
optionally, lists the tasks in the SMC subsystem address space.
optionally, lists SMC control blocks associated with the specified unit address(es).
uuuu
or uuuu-uuuu
indicates a unit address or range of unit addresses.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required
The SMC LOG
command logs data communications from either or all of the following:
SMC Library Interface Component
SMC Client Configuration Component
SMC HTTP Server Component
SMC Operator Command Component
These communication transactions are logged to the SMC log file.
This command is intended to be used primarily as directed by Oracle StorageTek Software Support.
As shown in Figure 2-19, the LOG
command includes the following parameters:
optionally, displays HTTP Server status information and interval statistics.
LIst
is the default when no parameters are specified on the LOG
command.
LIst
may be specified with other parameters. In this case, the LIst
is applied after the other parameters are processed.
optionally, resets all LOG
settings to original SMC default settings. OFF
closes the LOG, turns off all record TYPE
s, and sets LRECL
to 0. If a subsequent LOG START
command is issued after the OFF
command, no records are logged until specific LOG
TYPE
s are specified.
Optionally, specifies what record types are to be logged.
record-type
indicates one of the following record types:
For local LIBTRANS
XML transactions sent from the SMC Library Interface Component
For local LIBTRANS
XML responses received by the SMC Library Interface Component
For remote LIBTRANS
XML transactions sent from the SMC Client Communication Component
For remote LIBTRANS
XML responses received by the SMC Client Communication Component
For remote UUI transactions sent from the SMC Client Communication Component
For remote UUI responses received by the SMC Client Communication Component
For all errors detected by the SMC Client Communications Component
For all data sent outbound by the SMC HTTP Server Component
For all data received inbound by the SMC HTTP Server Component
For all errors detected by the SMC HTTP Server Component
For all operator commands received by the SMC Operator-Command Component
Sets all types ON
.
Sets all types OFF
.
optionally, specifies the line length written to the LOG
file.
a value from 80 to 32767, used to limit the logical line length.
If the data sent or received exceeds the specified LRECL
, then multiple lines are written. If LRECL
is specified, then the log date and time stamp are written as separate LOG
records. If this value exceeds the DCB LRECL
, then the DCB LRECL
is used.
The DCB LRECL controls the maximum line length. The LOG
record is appended to the log date and time stamp. This is the default.
optionally, specifies the response when the LOG
file reaches End of File (EOF).
Logging stops at EOF.
The LOG file closes and re-opens at EOF, and logging continues.
optionally, starts logging.
optionally, specifies that data is appended to the current LOG
file when logging is started. If not specified, then data is added to the LOG
file from the beginning of the log file, and any data currently in the log file is lost. APPend
can only be specified when STArt
is also specified.
optionally, stops logging. Current LOG
settings are preserved.
Interfaces:
Utility only
UUI Support: Yes
Subsystem Requirements:
Active SMC required
The SMC METAdata
command displays XML tags associated with a function that produces XML output.
Note:
The METAdata command produces no text output. If neither XML nor CSV output is requested, the command will not produce any output.As shown in Figure 2-20, the METAdata
command includes the following parameters:
The command for which metadata is to be produced.
When the command contains "two parts" such as Display Volume
, both portions should be entered. The METAdata
command uses the same abbreviations for the command-name
as the command itself, for example:
METAdata D V
The METAdata
command itself does not support metadata.
The METAdata
command produces the following tags:
The full name of the command.
Required security level if command authorization is in effect. Values are QUERY
, SET
, and ADMIN
.
Header tag for all XML tags.
The following tags are produced for each XML tag in the requested command:
Header tag for each XML tag.
The XML tag name, for example, volser.
Values are header (header XML tag), data (XML data tag, normally associated with a value), and trailer (indicates the position of the trailer tag associated with a header tag).
The maximum number of expected occurrences, for tags that may occur multiple times. This may be either a numeric value or unlimited
.
The following tags are produced only for data-type tags:
Indicates the type of data expected in the tag value. Produced only for data tags. Values include: char
, numeric
, flag
, hex
, date
, time
.
Indicates the maximum output data size.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required
Cannot be input to the SMCUSIM
utility
The SMC MONitor
command defines parameters associated with SMC monitoring.
Note:
SMC cannot detect pending mounts when either of the following conditions are present:ALLOCDEF DEFER(OFF)
has been specified.
The mount was requested before SMC had initialized and the mount request did not request the DEFER
option.
As shown in Figure 2-21, the MONitor
command includes the following parameters:
Optionally, lists the current MONitor
command settings.
Optionally, resets all MONitor
parameters to their default values.
Optionally, specifies the base SMC monitor scan interval in seconds. The default value is 60.
At each monitor interval, SMC performs the following actions:
SMC attempts to find an active communication path for any inactive TapePlex or Storage Manager.
If PREFprimary(ON)
is set, SMC attempts to change the communication path from a non-primary path to the primary server.
SMC checks to ensure that the SMC IEFJFRQ
exit is active, so that SMC is influencing tape allocation.
SMC clears orphaned task tokens.
SMC attempts to redrive pending mounts.
Note:
It is strongly recommended that you do not set theMONitor
INTerval
to 0 or OFF
. With these values set, SMC is not able to re-drive pending mounts, honor the PREFprimary
setting automatically, or verify that the IEFJFRQ
exit is active.Optionally, specifies the interval in seconds after which SMC should verify that communication is still accessible on an active communication path that has had no activity since the prior active check.
nnn
indicates the interval in seconds. The default value is 180, or 3 times the INTerval
value.
If ACTivecheck
is set to 0 or OFF
, SMC does not monitor active communication paths. If the ACTivecheck
interval is not a multiple of the base INTerval
, it is rounded up to a number of seconds that is a multiple of the INTerval
value.
Optionally, specifies the interval in seconds after which SMC should issue a message indicating that an outstanding mount is pending. The message is repeated after each interval if the mount remains unsatisfied.
nnnn
indicates the interval in seconds. The default value is 0, meaning that the message does not appear.
If the MISSedmnt
interval is not a multiple of the base INTerval
, it is rounded up to a number of seconds that is a multiple of the INTerval
value. It is recommended that you set this interval to at least 600 (10 minutes) to allow the SMC mount monitor processing to attempt to redrive missing mounts before producing the periodic missed mount message.
Optionally, specifies the time in seconds (nnnn
) after which SMC will issue the SMC0231 message and attempt to re-drive a mount request for a VTV.
nnnn
indicates the time in seconds. The default value is 300 seconds (5 minutes).
If the VTVtimeout
value is not a multiple of the base INTerval
, it is rounded up a number of seconds that is a multiple of the interval value.
The minimum value of VTVtimeout
is 300 seconds; the maximum is 1800 seconds.
Optionally, specifies the interval in seconds after which SMC should report on server scratch subpools that are below their threshold value.
nnnn
indicates the interval in seconds. The default value is OFF
.
LOWSCRatch
does not report on scratch shortages that are not associated with a subpool name, except for scratch subpool zero.
If LOWSCRatch
is set to 0 or OFF
, SMC does not perform scratch threshold checking.
If the LOWSCRatch
interval value is not a multiple of the base INTerval
, it is rounded up to a number of seconds that is a multiple of the INTerval
value.
Optionally, indicates whether SMC attempts to establish communication on a higher priority server path when communication is currently active on a server that is not the first defined server for a TapePlex. The default value of ON
indicates that at each MONitor INTerval
, SMC attempts to communicate on the first defined server path if that is not the current active path.
If PREFprimary
is set to OFF
, then SMC continues to communicate on an active path even if one defined earlier becomes available.
The PREFprimary
setting also controls the behavior of the RESYNChronize
command. When PREFprimary(ON)
is set, a RESYNChronize
attempts to communicate to the first defined server. When PREFprimary(OFF)
is set, a RESYNChronize
does not change the current active communication path, if one exists.
Interfaces:
Console or utility
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC MOunt
command requests a mount of a specific or scratch volume on a tape device.
As shown in Figure 2-22, the MOunt
command includes the following parameters:
the volume serial number of the volume to be mounted.
indicates a scratch mount.
optionally, when the volume is specified as SCRTCH
(or PRIVAT
), specifies the name of an SMC policy that defines the subpool name and management class name (if applicable) to be applied for the scratch mount.
policy-name
indicates the policy name.
the MSP device address for which the volume is to be mounted. The device must be defined by a TapePlex known to SMC. This is a required value.
optionally, indicates that the volume is to be mounted with write protect enabled.
optionally, indicates that if a loaded volume is found on the drive, it should be rewound and unloaded before attempting the requested mount. FOrce
is not supported for virtual drives.
optionally, indicates that if SMC detects a pending mount for the drive, indicates that the volume specified in the MOunt
command should override the volume indicated in the pending mount.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC MOUNTDef
command enables you to control message processing options (mounts or dismounts) previously controlled by the HSC MNTD
command, HSC input parameters and LIBGEN
options. The MOUNTDef
command also applies to VTVs.
These options control the following:
automation of pending mounts
delete disposition at dismount time
whether mount and dismount messages are issued
when mount messages are rolled off of the console
swap processing behavior
As shown in Figure 2-23, the MOUNTDef
command includes the following parameters:
optionally, lists current SMC MOUNTDef
settings.
LIst
is the default when no parameters are specified on the MOUNTDef
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
optionally, resets all MOUNTDef
settings to original SMC default settings. Specify LIst
with this parameter to list these settings.
optionally, specifies whether the pending mounts are automated for library or virtual drives found when SMC is first initialized and the owning TapePlex is first activated.
Pending mounts are automated. This is the default.
Pending mounts are not automated.
Note:
IfAUTOPendmount
is OFF
, you must issue an HSC MOUNT
command to complete any pending mounts found when a TapePlex is first activated.optionally, specifies how the SMC interprets the delete disposition on a dismount message for real (nonvirtual) volumes.
Note:
TheDISMSCRReal
and DISMSCRVirt
parameters replace the DELDISP=
parameter of the HSC LIBGEN SLILIBRY
macro.The real cartridge is retained as nonscratch when MSP indicates delete disposition in the dismount message. This is the default, and is recommended for CA-1 or CA-TLMS users to leave volumes in a consistent nonscratch status during the CA-1 and CA-TLMS grace period.
The real cartridge is scratched when MSP indicates delete disposition in the dismount message.
optionally, specifies how the SMC interprets the delete disposition on a dismount message for VTVs.
Note:
TheDISMSCRReal
and DISMSCRVirt
parameters replace the DELDISP=
parameter of the HSC LIBGEN SLILIBRY
macro.The VTV is retained as nonscratch when MSP indicates delete disposition in the dismount message. This is the default.
The VTV is scratched when MSP indicates delete disposition in the dismount message.
optionally, specifies whether an SMC message is issued when a library volume is to be mounted on a nonlibrary drive.
No message is issued when a library volume is to be mounted on a nonlibrary drive.
A console message is issued when a library volume is to be mounted on a nonlibrary drive.
optionally, specifies whether mount messages handled by the SMC are allowed to roll off the operator console before mount requests are satisfied.
Mount messages are allowed to roll off the console screen before mounts are satisfied. This is the default.
You can limit the rolling of specific mount messages (for example, TMS007
) by presetting the messages xxxxRCDC
(Request to Change Descriptor Codes) flag word xxxxRBFB1
. The SAMPLIB
includes a sample MPF USEREXIT
to preset the xxxxRCDC
flag.
Mount messages remain on the console screen until mount requests are satisfied.
optionally, specifies whether VTV mount and dismount messages are issued.
VTV mount (SLS5075I
) and VTV dismount (SLS5076I
) messages are not issued on the host where the server is running. This is the default.
The VTV mount (SLS5075I
) and VTV dismount (SLS5076I
) messages are issued on the host where the server is running.
optionally, specifies whether the SMC enhanced swap process automatically responds NO
to the IBM IGF500D - REPLY 'YES' DEVICE OR 'NO'
message when no compatible swap-to device is found.
SMC automatically replies NO
to the IBM IGF500D - REPLY 'YES' DEVICE OR 'NO'
message after the SMC fails to find compatible devices and issues its own SMC0108
No compatible drive found for SWAP processing
message. This is the default.
SMC does not automatically reply to the IBM IGF500D - REPLY 'YES' DEVICE OR 'NO'
message after the SMC fails to find compatible devices.
optionally, specifies the maximum number of system initiated swaps that SMC influences for the same job step and volume serial.
a swap value of 0-99, or OFF
.
If the value specified is 0 or OFF
, then the SMC continues to attempt to influence the swap indefinitely.
If the value is not specified, the default value is 3.
For any SWAPLimit
value other than 0 or OFF
, SMC stops attempting to influence the swap after nn
attempts for the same job step and volume serial.
Note:
Any operator-initiatedSWAP
commands are not applied to the SWAPLimit
value.Substitute one of the following values for bypassReply
:
ON
optionally, indicates that SMC should not reply to the system message IGF509D
if another swap attempt is detected after the SWAPLIMIT
count is exhausted.
OFF
optionally, SMC generates a response of NO
to an IGF509D
message after nn swap attempts. This is the default.
optionally, specifies whether previously used swap-to devices are to be excluded as possible swap-to devices for the current job step and volume serial.
Previously used swap-to devices are excluded as possible swap-to devices for the current job step and volume serial. If no eligible device is found then SMC issues message SMC0108
and if the MOUNTDef
SWAPAutoreply
is set to ON
then the IGF500D
or IGF509D
message is replied to with NO
. This is the default.
Previously used swap-to devices are eligible to be used for the current job step and volume serial.
optionally, specifies the maximum number of attempts to re-drive a mount request that has failed with an IOS003A
message.
perform an unlimited number of attempts to re-drive the mount request for a given drive following an IOS003A
message for a given drive.
the maximum number of attempts to re-drive the mount request. Valid values are 0-99. The default is 2. A value of 0 is equivalent to IOS003Alimit(OFF)
.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC MSGDef
command defines the appearance of SMC system messages, and controls which messages are displayed and suppressed.
As shown in Figure 2-24, the MSGDef
command includes the following parameters:
optionally, lists current default SMC message settings.
LIst
is the default when no parameters are specified on the MSGDef
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
optionally, resets all MSGDef
values to original SMC default settings. Specify LIst
with this parameter to list these settings. MSGDef
cannot be specified with any other parameter.
optionally, specifies the message case. Valid values are UPPER
or MIXED
.
specifies upper case. This is the default.
specifies mixed case.
optionally, specifies the default level used to control which SMC messages are displayed and suppressed.
the default level. Valid values include the following:
0
- Display error messages only.
4
- Display error and warning messages from the SMC subsystem.
8
- Display all SMC subsystem messages and allocation job log warning messages. This is the default if the MSGDef
parameter is not specified.
Note:
Levels higher than 8 are used for diagnostic purposes and should only be specified as directed by Oracle StorageTek Software Support.optionally, specifies whether mount errors generated by the HSC are echoed directly to the console for the SMC client.
Mount errors generated by the HSC are echoed to the console for the SMC client. This parameter is valid for both local and remote servers.
Mount errors generated by the HSC are not to the console for the SMC client. This is the default.
optionally, specifies whether the SMC0137 prefix is displayed for HSC WTOR messages generated by WTORDEST(CLIENT)
on the TAPEPlex
command.
The SMC0137
prefix is displayed. This is the default.
The SMC0137
prefix is not displayed.
optionally, specifies whether SMC0190
and SMC0191
messages are displayed whenever any SMC settings are altered.
SMC0190
and SMC0191
messages are displayed.
SMC0190
and SMC0191
messages are not displayed.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC MSGJob
command enables you to override of the default message level by job name, step name, and PROC
step.
As shown in Figure 2-25, the MDGJob
command includes the following parameters:
optionally, lists current default SMC message settings and job name, step name, and PROC
step exceptions (in the order of evaluation).
LIst
is the default when no parameters are specified on the MSGJob
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
optionally, specifies a job name.
jobname
indicates the job name. The value entered must be one to eight characters in length. An asterisk (*) can be used as a wildcard when included as the last character. In this case, the message level is set for all jobs whose job names match the characters preceding the asterisk.
optionally, specifies a step name. It is only valid when JOBname
is also specified (may be JOB=*
).
stepname indicates the step name. The value entered must be one to eight characters in length. This parameter is only valid if JOBname is also specified.
optionally, specifies a PROC step. It is only valid when JOBname
and STEPname
are also specified.
procstep indicates the PROC step. The value entered must be one to eight characters in length. This parameter is only valid if JOBname
and STEPname
are also specified.
optionally, specifies the default level used to control which SMC messages are displayed. This parameter is required when JOBname
is specified.
level indicates the default level. Valid values include the following:
0
- Display error messages only.
4
- Display error and warning messages from the SMC subsystem.
8
- Display all SMC subsystem messages and allocation job log warning messages. This is the default if the MSGDef
parameter is not specified.
Note:
Levels higher than 8 are used for diagnostic purposes and should only be specified as directed by Oracle StorageTek Software Support.optionally, removes MSGJob
overrides.
If no other parameters are specified, MSGJob
overrides are removed for all jobs.
If only JOBname
is specified, MSGJob
overrides are removed for all MSGJob
entries for that job name.
If JOBname
, STEPname
and PROCstep
are specified, MSGJob
overrides are removed only for the specified entry.
The global MSGJob
is not affected by this parameter.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (supports XML and CSV)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC POLicy
command specifies all tape policy specifications in a single named policy object. It can be used with SMC TAPEREQ
statements or SMC DFSMS
routines to associate a named policy with an allocation or mount event. Additionally, the POLicy VALidate
option can be used to validate policy objects.
Note:
Refer to Oracle's ELS publication Configuring and Managing SMC for more information about the use of SMC policies.Policies defined using the SMC POLicy
command create SMC policy objects that can be referenced by name from either SMC TAPEREQ
control statements using the TAPEREQ POLicy
parameter. A policy name may be associated with two policy objects: a scratch policy with the specified name, and a specific policy with the specified name. Policies referenced from SMC TAPEREQ
control statements must be defined before executing the TREQDEF
command that processes the TAPEREQ
control statements.
By default, and SMC POLICY
command applies ONLY to SCRATCH volumes. If you want to set a policy for specify volumes, you must specify VOLTYPE(SPECIFIC)
. If you want to specify a policy to apply to both SCRATCH and SPECIFIC volumes, you must specify two separate POLICY
commands with the same POLICY name.
When a policy to be added to the SMC contains a policy specification error, for example, specifying a scratch subpool name with VOLTYPE(SPECIFIC)
, the SMC still creates the policy object to find it. When a policy is marked as in error, the policy is empty, indicating that the default tape policy attributes will be applied to an event that specifies this policy name.
To update an SMC policy, enter a new SMC POLicy
command for the given policy NAme
and VOLType
. Be aware that the new POLicy
command replaces the existing scratch or specific policy object. Therefore, when updating a policy, you must enter all values you want to preserve.
For example, if the original scratch policy object is defined as:
POLICY NAME(POL1) VOLTYPE(SCRATCH) MEDIA(VIRTUAL) MGMTCLAS(MGMT1)
and you want to add a subpool to the policy, you must enter:
POLICY NAME(POL1) VOLTYPE(SCRATCH) MEDIA(VIRTUAL) MGMTCLAS(MGMT1) SUBPOOL(SUBP1)
This behavior enables you to modify one or more POLicy
commands in a file and reload all policies using the SMC READ
command. When using the SMC READ
command to reload the SMC POLICY
file, it is recommended that you specify the option REPlacepolicy
to receive notifications about POLICY
commands present in the original definitions but missing in the new definitions.
When an SMC policy object to be updated contains a policy specification error, for example, specifying a scratch subpool name with VOLType(SPecific)
, the SMC will not update any part of the existing policy object. The policy object is not marked in error, and the complete update is discarded.
DEVTPREF
is not supported on this command. However, you can use an esoteric list to specify preferencing for different device types.
As shown in Figure 2-26, the POLicy
command includes the following parameters:
optionally, displays all policy information. Additional parameters allow you to limit which policies are listed, and how much detail is displayed.
If name is also specified, only policies that match the specified name or generic name are listed. If name is not specified, then all policies are listed.
Note:
Matching policies are listed in alphabetic order, regardless of the order in which they were defined to the SMC. When specified with other parameters, theLIst
is performed after the other parameters have been processed.optionally, specifies the name of a policy that matches the name specified in a TAPEREQ
or DFSMS ACS routine management class. If the keyword NAme
is omitted, the policy name is assumed to be the first parameter following the POLicy
command (if that parameter is not a valid keyword).
name
indicates the policy name.
optionally, displays audit detail information about the policy, including last update date, time, and source. DETail
and TERse
are mutually exclusive.
optionally, lists only policy names and whether each policy name applies to scratch, specific, or all allocations. TERse
and DETail
are mutually exclusive.
optionally, displays each policy in error status.
When a policy to be added to the SMC contains a policy specification error, for example, specifying a scratch subpool name with VOLTYPE(SPECIFIC)
, the SMC still creates the policy object. However, the SMC marks the policy object in error, allowing any reference to the named policy object to find it. However, the returned policy will be empty, indicating that the default tape policy attributes will be applied to the event. ERRor
lists only those policies that contain an error.
optionally, specifies whether the list applies to scratch or specific policy types.
List only scratch (nonspecific) policies. This is the default.
List only specific policies.
optionally, validates and lists policy information against the current TapePlex environment. Additional parameters allow you to limit which policies are validated, and whether all results or just warnings and errors are displayed.
optionally, specifies the name of a policy to be validated.
If the last character is an asterisk (*), all policies that begin with the prefix are displayed. For example, POL VAL NA V*
validates all policies that begin with ”V
”. If the NAme
parameter is omitted, a non-keyword parameter following the POLicy
command is interpreted as the NAME
.
name
indicates the policy name.
optionally, specifies whether the list applies to scratch or specific policy types.
List
only scratch (nonspecific) policies. This is the default.
List
only specific policies.
optionally, specifies whether only warnings and errors are listed, or all tested policies are listed. If not specified, then only a single line for each policy that generates a warning or error message is listed.
optionally, specifies the name of a policy. name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name, if specified, must be the first parameter.
The policy name must match the name specified in a TAPEREQ
or DFSMS ACS
routine management class name.
name
indicates the policy name.
When a policy is not being added or updated, the policy name can be a generic name, for example POLICY V*
lists information for all policies that begin with V
.
optionally, specifies whether the policy applies to scratch or specific allocation.
The policy applies only to scratch (nonspecific) allocations. This is the default.
The policy applies only to specific allocations.
See individual parameters for restrictions on the VOLType
that is permitted or not allowed.
Note:
If you want to specify a policy that applies to both scratch and specific volumes, you must use two separatePOLicy
commands with the same POLicy NAME
, one with VOLType(SCratch)
(or not specified) and one with VOLType(SPecific)
.When a new policy is added, the default VOLType
is SCratch
(or Nonspec
). You can add the same policy name for both SCratch
and SPecific
VOLType
s.
The following parameters require a name
or NAme(
name
)
parameter:
optionally, removes all policy parameters associated with the named policy. Specifying NOne
for a policy implies that the default behavior is applied, for example, any media or rectech, subpool 0, and so on.
optionally, specifies the desired media type for a data set being created. You can enter a list of media types, separated by commas. A list specifies a generic pool from which a selection is made. There is no implied priority.
media-type
indicates the media type. See Appendix A, "MEDia, RECtech, and MODel Values" for a list of valid media-type
values.
If this parameter is not specified, a default is chosen based on the value of the RECtech
parameter. See Appendix A, "MEDia, RECtech, and MODel Values" for default values used if the MEDia
parameter is omitted.
MEDia
and VOLType(SPecific)
are mutually exclusive unless the NOTAPEPlex
parameter is specified. If both media type and recording technique are omitted, all available device types are eligible for allocation.
optionally, specifies the method used to record data tracks on the tape surface for the desired data set. You can enter a list of recording techniques, but they must be separated by commas. A list specifies a generic pool from which a selection is made. There is no implied priority.
recording-technique
indicates the recording technique. See Appendix A, "MEDia, RECtech, and MODel Values" for a list of valid recording-technique
values.
optionally, specifies the model number of a transport. You can enter a list of models, separated by commas. A list specifies a generic pool from which a selection is made. There is no implied priority.
MODel
provides the same type of information as RECtech
, but a user may find it more convenient to specify a transport model rather than a recording technique. MODel
and RECtech
are mutually exclusive.
model-type
indicates the model type. See Appendix A, "MEDia, RECtech, and MODel Values" for a list of valid model-type
values.
optionally, specifies the subpool used to satisfy a scratch request. SUBPool
and VOLType(SPecific)
are mutually exclusive.
subpool-name
indicates the subpool name.
optionally, specifies the name of a device esoteric group, or list of device groups defining the list of eligible transports to be used to satisfy a tape request.
esoteric-group-name
or esoteric-list
indicates the esoteric group name. The name specified can consist of one to eight alphanumeric or national (#, @, $) characters. A slash (/) or hyphen (-) is also valid.
If the esoteric list contains devices not currently in the Eligible Device List, SMC allocation cannot add devices to the list, but can exclude devices not in the specified esoteric. During drive exclusion, devices in any of the listed esoterics are included. During drive prioritization, devices are ordered according to their position in the esoteric list.
optionally, specifies the relative value of the esoteric list and additional preferencing information. PREFer
is only valid when a list of esoterics is specified.
Drives are preferred based on LSM location of a specific volume. This is the default for specific volumes. Location is only valid for VOLType (SPecific)
.
Drives are preferred based on the order specified in the esoteric list. This is the default for scratch allocations.
Drives are preferred based on scratch counts in the LSM. Count is mutually exclusive with VOLTYPE(SPecific)
.
optionally, specifies a Management Class defined on the VTCS MGMTclas
control statement. See "MGMTclas Control Statement" for more information.
name
indicates the Management Class name.
optionally, specifies the name of a TapePlex defined to SMC. SMC uses the specified TapePlex name to determine the owner of an allocation request. Only the specified TapePlex name is queried to determine specific volume information or scratch availability.
name
indicates the TapePlex name. This must be a TapePlex name specified on a TAPEPlex
command. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit, or hyphen.
The named TapePlex must be defined using a TAPEPlex
command before the POLicy
command is processed. TAPEPlex
and NOTAPEPlex
are mutually exclusive.
optionally, specifies that SMC will not perform a TapePlex lookup to obtain volume information. NOTAPEPlex
and TAPEPlex
are mutually exclusive.
optionally, specifies the name of a device esoteric group, or list of device groups defining the list of eligible transports to be used to satisfy a tape request when the specific volume is found to be outside of the library. EXTVOLesot
can only be specified if VOLTYPE=SPECIFIC
is also specified.
esoteric-list
indicates the esoteric-list. Each esoteric group name in the list can consist of one to eight alphanumeric or national (#, @, $) characters. A slash (/) or hyphen (-) is also valid.
optionally, specifies whether VOL=REF
chains are to be broken. SPLITvolref
and VOLType(SPecific)
are mutually exclusive.
VOL=REF
chains are not broken. This is the default.
VOL=REF
chains are broken and the LABEL
data set sequence number is set to 1.
optionally, specifies that a job step matching the policy should be failed during SMC allocation. When this parameter is specified, any job step that matches the policy has all its devices marked ineligible by the SMC allocation process, which causes the job to fail. ALLOCFail
is mutually exclusive with all other parameters except for NAme
, LIst
, VALidate
, and VOLType
.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC READ
command enables you to enter a series of commands using an input data set instead of console commands.
As shown in Figure 2-27, the READ
command includes the following parameters:
optionally, re-processes commands contained in the data set specified in the SMCCMDS
DD statement of the SMC START
procedure.
optionally, processes commands contained in the specified data set.
dsn
indicates the data set name.
Note:
If theDSN
parameter specifies a member name, the full data set must be enclosed in single quotes.optionally, specifies the volume serial number of the DASD volume on which the data set resides. Specify this parameter if the data set is not catalogued.
volser
indicates the volume serial number on which the data set resides.
optionally, specifies the unit name of the specified VOLume
for uncataloged data sets. Requires that VOLume
also be specified.
unitname
indicates the unit name. If not specified, then a unit name of SYSALLDA
is the default.
optionally, specifies a host name for which this READ
command is valid. If this parameter is specified, the READ
command is only processed when the specified hostname
matches the MSP host. If this parameter is not specified, the READ
command is processed regardless of the MSP host.
hostname
indicates the host name.
HOST
is not valid when the READ
command is entered from an MSP console.
Specification of the HOST
parameter enables you to share a single SMC parameter file set across multiple MSP hosts as shown in the following example:
your.parmlib(COMMCMDS
)
MSGDEF CASE(MIXED) ...other common SMC parameter settings... READ DSN(’your.parmlib(MSP1CMDS)') HOST(MSP1) READ DSN(’your.parmlib(MSP2CMDS)') HOST(MSP2)
your.parmlib(MSP1CMDS
)
DRIVEMAP CL(AB0-AB7) SE(BB0-BB7)
your.parmlib(MSP2CMDS
)
DRIVEMAP CL(CB0-CB7) SE(BB0-BB7)
The file COMMCMDS
contains SMC parameter settings applicable to all hosts, and the READ
commands with HOST
specifications for your MSP hosts. The file MSP1CMDS
contains SMC specifications applicable only to MSP host MSP1
, while the file MSP2CMDS
contains SMC specifications applicable only to MSP host MSP2
.
optionally, specifies that all SMC POLICY
objects are to be replaced by any POLICY
statements found in the specified data set (or in any data set subsequently read by the specified READ
data set).
If REPlacepolicy
is not specified, individual POLICY
statements within a READ
command update or add only the referenced POLICY
statements and do not affect unreferenced POLICY
statements.
Note:
After the READ
REPlacepolicy
command is executed, any TAPEREQ
POLICY
references are re-validated. If any TAPEREQ POLICY
references are subsequently found to be in error, the invalid TAPEREQ
statements are left active, but reference a "null" POLICY
(that is, the equivalent of specifying POLICY NAME(
name
) NONE
).
It is recommended that any TAPEREQ
statement(s) be reloaded by inclusion of the TREQDEF
command whenever a READ
REPlacepolicy
command is executed, in order to re-validate all SMC tape policies at the same time.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC RESYNChronize
command re-establishes connections to all defined TapePlexes to acquire drive configuration information from all TapePlexes.
This action is automatically performed when the SMC first activates a new path to a TapePlex, when an HSC subsystem (local or remote) reports a configuration change, or when an active local path to a TapePlex is accessed during an MSP allocation or mount event. However, the operator must issue the RESYNChronize
command in the following instances:
When the user wants to automate pending mounts for a newly activated TapePlex, and does not want to wait for an MSP allocation or mount event to trigger the reconnection.
To attempt to redrive outstanding mounts that may have been lost due to hardware or communication errors.
Note:
It is recommended that you include aRESYNChronize
command at the end of your SMCCMDS
file (after all TAPEPlex
and SERVer
commands) to initialize communication with TapePlexes before the first intercepted allocation or mount.Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required
The SMC Route
command routes command transactions from SMC to a defined TapePlex or VLE. Only the following are supported:
VTCS commands
HSC commands with UUI support, except for VOLRPT
.
Note:
The HSC MOUNT
, DISMOUNT
, ENTER
and MOVE
commands can now be issued from SMC through the ROUTE
command.
Currently, the only command that will be accepted and processed by a VLE is the QUERY SERVER
command.
You can also use the Route
command to issue various commands from a VM Client to an ACSLS XAPI server. Refer to Oracle's ELS publication XAPI Client Interface to ACSLS Server Reference for more information.
As shown in Figure 2-29, the Route
command includes the following parameters:
specifies a TapePlex name as defined on an SMC TAPEPlex
command. SMC routes the request to the specified TapePlex using the currently active TapePlex path. Commands may be sent to either a local or remote HSC TapePlex.
specifies a VLE name as defined on an SMC STORMNGR
command. SMC routes the request to the specified VLE using the currently active VLE path. Commands may be sent to either a local or remote HSC TapePlex or VLE.
specifies the command string to be routed to the requested TapePlex.
Do not prefix VTCS commands with VT
; the HSC UUI interface routes VTCS commands to the correct functional processor without the VT
prefix. The command string must be a command supported by the HSC UUI or any VTCS command (except DISPLAY MSG
and DISPLAY CMD
). This is a required value.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC SERVer
command defines a named path to a remote library server; an HSC subsystem executing on another host. The SERVer
command describes the communication path to the HTTP server.
Note:
Before a SERVer
is defined, the TapePlex that it references must be defined using a TAPEPlex
command. The TapePlex name associated with a SERVer
cannot be changed. See "TAPEPlex" for more information.
Similarly, before a SERVer
is defined, the VLE that it references must be defined using a STORMNGR
command. The VLE name associated with a SERVer
cannot be changed. See "STORMNGR" for more information.
As shown in Figure 2-30, the SERVer
command includes the following parameters:
optionally, specifies the server name to be defined, modified, or listed.
name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name, if specified, must be the first parameter.
The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit or hyphen.
Note:
If you are using the SMC HTTP server component, there can be multipleNAME
d server paths for a single TapePlex configuration. Refer to Oracle's ELS publication Configuring and Managing SMC for more information.optionally, displays status information for TapePlex server paths.
If name is also specified, only the named TapePlex server path is listed. If name
is not specified, then all TapePlex server paths are listed.
Note:
LIst
is the default when no parameters are specified on the SERVer
command. In this case, all library server paths are listed.
LIst
may be specified with other parameters. When specified with parameters other than NAme
, the LIst
is generated after the other parameters are processed.
The following parameters require a name or NAme(
name
)
parameter:
optionally, enables the specified server path to be selected for allocation or mount requests.
optionally, disables the specified server path. If this is the only path to the TapePlex, the TapePlex is unavailable for allocation or mount requests.
optionally, specifies the TapePlex name associated with an actual ACS hardware configuration as defined on an SMC TAPEPlex
command. The TAPEPlex
parameter must be specified when a new server is first defined.
name
indicates the TapePlex name. This name is reported in any TapePlex error message. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit or hyphen.
optionally, specifies a VLE name as defined on an SMC STORMNGR
command. The STORMNGR
parameter must be specified when a new server is first defined. TAPEPlex
and STORMNGR
are mutually exclusive.
name
indicates a VLE name as defined on an SMC STORMNGR
command. This name is reported in any VLE error message.
optionally, specifies the name of the HSC subsystem that represents the Tapeplex associated with the server. This parameter is required only when there is more than one HSC subsystem executing on the server host (HSC running in MULT
mode).
ssss
indicates the HSC subsystem name.
optionally, specifies the IP resolver host name on which the remote HSC subsystem resides. HOst
and IPaddress
are mutually exclusive.
hostname
indicates the name of the remote host. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit or hyphen.
optionally, specifies the subsystem IP address for the remote HSC subsystem. IPaddress
and HOst
are mutually exclusive.
address
indicates the IP address. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit or hyphen.
optionally, specifies the server port. nnnn
indicates the server port. The default is 8080.
optionally, specifies the maximum wait time for any single request made over the network before the SMC assumes that a communication or server problem exists.
nnnn
indicates the wait time in seconds. The default is 60.
Note:
The default for a mount or dismount request is 10 minutes (600 seconds) or more if the specified WAIT
time is greater than 600 seconds.
If your HSC CDS backup job runs longer than the specified wait time, set your wait time to match the normal execution time of your CDS backup job.
optionally, specifies the number of retry attempts for any single request before the task is allowed to resume, and a failure recorded.
nnnn
indicates the number of retries. The default is 3.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC SIMulate
command simulates how SMC would process a single DD job step with a given set of jobstep characteristics. The SIMulate
command simulates the allocation influence (SSI24) portion of SMC processing, but not mount processing.
You provide the keyword jobstep parameters to simulate, and the command invokes SMC allocation, policy lookup, and volume lookup. The SIMulate
output displays the simulation results.
While SIMulate
does not simulate certain jobstep characteristics (such as multiple units, affinity separation, or volref attributes), it does provide a powerful tool to test how changes in SMC policies, including TAPEREQ
and POLICY
commands, user exits, and TAPEREQ
and SERVER
changes will affect your production jobs.
You can issue SIMulate
command to an active SMC subsystem or through the SMCUSIM
utility. The SMCUSIM
utility, working with the SIMulate
command, produces XML output that can be manipulated as CSV to produce before and after reports to compare how jobs would be processed. See "SMC UUI Simulation Utility (SMCUSIM)" for more information about the SMCUSIM
utility.
As shown in Figure 2-31, the SIMulate
command includes the following parameters:
optionally, specifies the job name of the simulated job step to test. The format must conform to MSP standards. If not specified, "(any)" is used, which prevents a match to non-generic job names specified in SMS ACS
routines or TAPEREQ
control statements.
jobname
indicates the job name.
optionally, specifies the step name of the simulated job step to test. The format must conform to MSP standards. If not specified, "(any)" is used, which prevents a match to non-generic step names specified in SMS ACS
routines or TAPEREQ
control statements.
stepname
indicates the step name.
optionally, specifies the program name of the simulated job step to test. The format must conform to MSP standards. If not specified, "(any)
" is used, which prevents a match to non-generic program names specified in TAPEREQ
control statements.
pgmname
indicates the program name.
optionally, specifies the DD name of the simulated data set to test. The format must conform to MSP standards. If not specified, "(any)
" is used, which prevents a match to non-generic DD names specified in TAPEREQ
control statements.
ddname
indicates the DD name.
optionally, specifies the data set name of the simulated data set to test. The format must conform to non-PDS member MSP standards. If not specified, "(any)
" is used, which prevents a match to non-generic program names specified in TAPEREQ
control statements.
dsname
indicates the data set name.
optionally, specifies the volume serial number of the simulated data set to test. The format must conform to MSP standards. If not specified, "SCRTCH
" is used, which simulates a scratch mount.
volser
indicates the volume serial number.
optionally, specifies the name of a device esoteric group defining the list of eligible transports used to satisfy the tape request. The specified esoteric must be a defined MSP esoteric. If not specified, the SIMulate
command simulates an original esoteric consisting of all known library, non-library, and virtual devices for all TapePlex(es). If the default esoteric is used, it may not correspond to a defined MSP esoteric.
esoteric-name
indicates the esoteric name.
optionally, specifies the retention period of the simulated data set to test. The format must conform to MSP standards. If not specified, 0 is used.
retention-period
indicates the retention period.
optionally, specifies the expiration date of the simulated data set to test. The format must conform to MSP standards. If not specified, the current date is used.
expiration-period
indicates the expiration date.
optionally, specifies the label type to be used to select the policy.
label-type
indicates the label type. Specify one of the following:
SL
indicates standardlabeled tape. This is the default if the parameter is omitted.
AL
indicates ANSIlabeled tape.
NL
indicates nonlabeled tape.
NSL
indicates nonstandard labeled tape.
SMC SIMulate command output displays the simulated job characteristics and policy sections displaying the SMS, TAPEREQ
and SMC policy applied.
The following example shows the "minimum" output, where no SMC tape policies were applied:
Example 2-1 SIMulate Command Output - No Tape Policies Applied
SMC0222 SIMULATE command results: ---- Jobstep characteristics ---- JOBNAME=(any), STEPNAME=(any), PROGRAM=(any), DDNAME=(any) DSN-SMCINT.BT1.TEST, RETPD=0 VOLSER=SCRTCH, ESOTERIC=(any) ---- Volume lookup results ---- Owning TAPEPLEX=HSCQ MEDIA=STANDARD,ECART,STK2P RECTECH=LONGITUD,STK2P ---- List of eligible drives ---- 0AA0 TAPEPLEX=HSCQ, ACS=00, LSM=00, 18TRACK, pref=1 0AA1 TAPEPLEX=HSCQ, ACS=00, LSM=00, 18TRACK, pref=1 remainder of drives
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC STORMNGR
command defines a VLE to SMC.
Note:
STORMNGR
and SERVer
commands are required to access a VLE. The STORMNGR
command can also list VLEs that the SMC tries to communicate with and report their status.As shown in Figure 2-32, the STORMNGR
command includes the following parameters:
Specifies VLE to be defined, modified or listed. This name is also defined to VTCS, and is initially defined by the VLE GUI. If name
is not specified, then all VLEs are listed.
name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name
, if specified, must be the first parameter.
The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit or hyphen.
enables the specified VLE. This is the default when new VLE is added.
disables the specified VLE.
optionally, lists VLE information.
If name
is also specified, only the named VLE is listed. If name
is not specified, then all VLEs are listed.
optionally, lists defined VLEs, their attributes and associated servers.
If name
is also specified, only the named VLE is listed. If name
is not specified, then all VLEs are listed.
optionally, lists current status of all VLEs or a single named VLE.
If name
is also specified, only the named VLE is listed. If name
is not specified, then all VLEs are listed.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC TAPEPlex
command defines a TapePlex; a specific Oracle StorageTek tape hardware configuration normally represented by a single CDS. The TAPEPlex
command can also list TapePlexes that the SMC tries to communicate with, and report their status.
Note:
TAPEPlex
and SERVer
commands are required to access remote HSC TapePlexes.
At least one TapePlex must be defined to allow SMC to initialize.
As shown in Figure 2-33, the TAPEPlex
command includes the following parameters:
specifies the TapePlex name to be added, modified, or listed.
name
may be specified with or without the keyword NAme
. If the keyword NAme
is not specified, the name, if specified, must be the first parameter.
The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be either an alpha character or digit.
The last character must be either an alpha character or digit.
Any character between the first and last must be either an alpha character, digit or hyphen.
optionally, lists TapePlex information.
If name
is also specified, only the named TapePlex is listed. If name
is not specified, then all TapePlexes are listed.
LIst
is the default when no parameters are specified on the TAPEPlex
command. In this case, all TapePlexes are listed. LIst
may be specified with other parameters. In this case, the named TapePlex is listed after the other parameters are processed.
optionally, lists defined TapePlexes, their attributes and associated servers.
If name
is also specified, then only the named TapePlex servers are listed. If name
is not specified, then all servers are listed.
optionally, lists current status of all TapePlexes, or a single named TapePlex. The TapePlex status indicates whether a TapePlex is active, inactive, or disabled. For an active TapePlex, the status lists the name of the current server or local subsystem.
If name
is also specified, then only the named TapePlex status is listed. If name
is not specified, then the status of all TapePlexes is listed.
The following parameters require a name
or NAme(
name
)
parameter:
optionally, enables the specified TapePlex to be selected for allocation or mount requests.
optionally, disables the specified TapePlex. The TapePlex is not used for any allocation or mount requests.
optionally, specifies a local HSC subsystem.
subsysname
indicates the subsystem name.
optionally, enables the specified HSC subsystem to be used as a local path to the TapePlex.
optionally, disables the specified HSC subsystem. LOCDISable
can be used to force the SMC to ignore the local subsystem and access the TapePlex through a remote server.
optionally, specifies the console to which HSC WTOR messages are directed. Refer to Oracle's ELS publication Configuring and Managing SMC for messages that apply.
The remote HSC returns selected WTORs to the SMC client without issuing the WTOR message. The SMC client then issues the WTOR to the operator of the system that the SMC executes on. The SMC redrives the mount or dismount request to the server supplying the WTOR response.
WTOR messages are issued on the HSC server console. This is the default.
optionally, specifies a host alias to be used in communications with the HSC TapePlex.
a 1-8 character host name.
The native SMF host name is used in communications with the HSC library. This is the default.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC TCPip
command enables you to alter and/or lists current TCPNAME
and ADSNAME
defaults for your TCP/IP communications environment. You can use this command to direct TCP/IP requests to a specific TCP/IP stack on an MSP host.
As shown in Figure 2-34, the TCPip
command includes the following parameters:
optionally, lists current TCPNAME
and ADSNAME
settings.
LIst
is the default when no parameters are specified on the TCPip
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
optionally, specifies that system defaults are used for client TCP/IP communication.
optionally, specifies whether SMC attempts to re-resolve the SERVER HOST
name after a communication failure.
SMC does not attempt to re-resolve the server host name. This is the default.
SMC attempts to re-resolve the server host name.
SMC first attempts a retry as specified by the SERVER RETRY
parameter. If the error indicates that the IP address may be unavailable, and the RERESolve
parameter is ON, SMC then attempts to resolve the HOST
name again, and if a new IP address is generated, retries the transaction.
optionally, specifies the XAPI user name associated with all transactions originating from this client. This user name will only be used when a login challenge is issued by the targeted server.
username
indicates the XAPI user name.
Note:
The sameUSER
must be defined on both the client and server using the XUDB
command. See "XUDB" for more information.These parameters are mutually exclusive with OFF
or RERESolve
.
optionally, specifies the TCPNAME
value for a specific TCP/IP stack on an MSP host. TCPNAME
is the name of the MSP TCP/IP stack. Refer to the Fujitsu publication TCP/IP for MSP Application Programming Interface Reference for more information about TCPNAME
. The default is none
.
name
indicates the TCPNAME
value. The default is none.
If a subsystem name is specified, it must consist of one to four alphanumeric or national (#,@,$) characters, the first character being alphabetic or national.
If an address name is specified, it must consist of one to eight alphanumeric or national characters.
optionally, specifies the ADSNAME
value for a specific TCP/IP stack on an MSP host. ADSNAME
is the jobname of the TCP/IP startup job. Refer to the Fujitsu publication TCP/IP for MSP Application Programming Interface Reference for more information about ADSNAME
.
name
indicates the ADSNAME
value.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC TRace
command enables SMC tracing using the GTF trace facility and optionally provides a snap dump of the address space before and after control block modification.
Note:
SMC TRace
processing may impact system performance. Use only as directed by Oracle StorageTek Software Support.
TRace JOBname(
jobname
)
causes SMC traces to be produced for UUI commands issued by the HSC or VTCS subsystem address space when jobname
matches the HSC subsystem name. UUI tracing is extremely CPU intensive and should only be used as directed by Oracle StorageTek Software Support.
As shown in Figure 2-35, the TRace
command includes the following parameters:
optionally, lists current SMC trace settings for both the SMC subsystems and SMC components by job name, step name, and PROC step.
LIst
is the default when no parameters are specified on the TRace
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
If no JOBname
is specified, all jobs with SMC components being traced are listed.
If JOBname
is specified, only those jobs with SMC components being traced whose job name matches the specified job JOBname
are listed.
optionally, disables SMC tracing.
If no other parameters are specified, tracing is disabled for all jobs.
If only JOBname
is specified, tracing is disabled for all entries for that job name.
If JOBname
, STEPname
and PROCstep
are specified, tracing is disabled only for the specified entry.
Optionally, indicates whether SMC trace output should be produced in "compact" format.
When GTF trace output is produced in this format, you can use the SMC utility program SMCUGTF
to reformat the trace to the original SMC trace format. See "Trace Format Utility (SMCUGTF)".
SMC trace output is produced in a format that conserves GTF data set space. This is the default.
SMC trace output is produced in human readable format.
optionally, enables or disables SMC tracing for one or more SMC subsystem components or subtasks.
optionally, enables tracing for all SMC subsystem components and tasks. This is the default if no parameters are specified.
optionally, enables tracing for all SMC subsystem ASCOMM
Component tasks.
optionally, enables tracing for all SMC subsystem CGI module processing for all connected client requests. To trace CGI module execution for individual client requests, issue a TRace JOBname REMOTE
command on the appropriate SMC client.
optionally, enables tracing for all SMC subsystem Operator Command Component tasks.
Optionally, enables tracing for all SMC subsystem HTTP Server Component tasks.
Optionally, enables tracing for all SMC subsystem Initiation/Termination Component tasks.
optionally, enables or disables SMC tracing for one or more initiator components in initiators that match the specified jobname
, stepname
, and procstep
name specified. If not specified, tracing information for all jobs is displayed.
jobname
is a specific job name. The value entered must be one to eight characters in length. An asterisk (*) can be used as a wildcard when included as the last character. In this case, all jobs whose job names match the characters preceding the asterisk are traced or listed. To trace all jobs, specify TRACE JOB(*)
.
optionally, specifies a step name.
stepname
indicates the step name. The value entered must be one to eight characters in length. This parameter is only valid if JOBname
is also specified.
optionally, specifies a PROC
step.
procstep
indicates the PROC
step. The value entered must be one to eight characters in length. This parameter is only valid if JOBname
and STEPname
are also specified.
optionally, enables tracing for all SMC initiator components executing in initiators that match the specified jobname
, stepname
, and procstep
name specified. This is the default if no parameters are specified.
optionally, enables tracing for all SMC Allocation tasks executing in initiators that match the specified jobname
, stepname
, and procstep
name specified.
optionally, enables tracing for all SMC Message Handler Component tasks executing in initiators that match the specified jobname
, stepname
, and procstep
name specified.
optionally, enables tracing in the remote SMC HTTP Server for requests originating from the jobname
, stepname
, and procstep
name specified.
Remote tracing does not rely on the GTF trace being active on the SMC client, but GTF tracing must be active on the corresponding SMC HTTP Server.
optionally, enables tracing for all SMC Utility Component tasks executing in initiators that match the specified jobname
, stepname
, and procstep
name specified.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC TREQDef
command specifies and loads the definition data set containing your tape request (TAPEREQ
) parameter statements.
Note:
Existing HSCTREQDEF
control statements are not disabled, but are only processed for remote SMC 6.0 client systems.As shown in Figure 2-36, the TREQDef
command includes the following parameters:
lists information about the definition data set containing TAPEREQ
control statements that are currently loaded. Information includes:
Data set name
Member name
Identifying string (if the data set contains an OPTION TITLE
statement)
Date and time parameters were loaded
LIst
is the default when no parameters are specified on the TREQDef
command.
optionally, specifies the name of the data set containing the TAPEREQ
control statements to be processed and, optionally, an OPTION TITLE
control statement.
dsn
indicates the data set name. This data set can be a fixed length 80-byte sequential data set, or a fixed length 80-byte member of a PDS. If the data set name includes a member name, you must enclose the data set name in quotes. For example:
DATASET(’YOUR.PDS.DSN(MEMBER)')
optionally, specifies the volume serial number of the DASD volume on which the data set resides. Specify this parameter if the data set is not catalogued.
volser
indicates the volume serial number.
optionally, specifies the unit name of the specified VOLume
for uncataloged data sets. Requires that VOLume
also be specified.
unitname
indicates the unit name. If not specified, then a unit name of SYSALLDA
is the default.
optionally, specifies the hostid
from which to execute this control statement. This parameter is valid only for use in PARMLIB
, to allow multiple systems to share a parmlib member containing multiple TAPEREQ
control statement members.
hostid
indicates the host name(s) from which to execute this control statement. Multiple host names must be separated by commas.
optionally, reloads the currently loaded TAPEREQ
control statements from the same data set. This parameter can be used after a TREQDEF DSN(
dsn
)
command is issued, and changes may then be made to the contents of that data set.
The SMC TAPEREQ
control statement specifies a named POLicy
to be applied to a particular job name, step name, program name, data set or group of data sets.
TAPEREQ
statements are placed in the definition data set (DDname
) specified by the SMC TREQDEF
command. SMC allocation calls on these TAPEREQ
statements to help ensure that the correct media type is used to satisfy a request, and that the cartridge is mounted on the appropriate device. TAPEREQ
statements must be placed in the definition data set; they cannot be issued as operator commands.
The SMC POLicy
command enables you to specify all tape policy specifications in a single named object. It is used with TAPEREQ
statements or SMS
to associate a named policy with an allocation or mount event.
The TAPEREQ
POLicy
parameter directs the SMC to reference an associated SMC policy defined by an SMC POLicy
command. Refer to Oracle's ELS publication Configuring and Managing SMC for more information.
If any of the following conditions exist, then the MEDia
and RECtech
or MODel
parameters are set to undefined, which matches all requests. Any available device is eligible for allocation.
There is no TAPEREQ
control statement specified in the definition data set to match a request.
There is no matching Policy
command specifying the MEDia
, RECtech
, or MODel
parameters.
There is no definition data loaded.
Note:
In previous software releases, TAPEREQ
parameters were used to define tape attributes. Refer to Oracle's ELS publication ELS Legacy Interfaces Reference for information about these legacy parameters.
See "TREQDef" for information about the TREQDEF
command.
As shown in Figure 2-37, the TAPEREQ
control statement includes the following parameters:
Note:
TheJOBname
, STEPname
, PROGram
, and DATASET
parameter values can include the following wildcard characters:
%
or ?
indicates any single nonblank character.
*
indicates any character string (length zero to 8) not to exceed one qualification level. For example, A.B.*
matches A.B
and A.B.C
, but does not match A.B.C.D
.
**
used only in DATASET
, indicates any number of qualifiers (zero or more). Cannot be used with any other characters within a qualifier. For example, A.B.**
matches A.B
, A.B.C
, A.B.C.D
, A.B.C.D.E
, and so forth.
optionally, identifies the job name. If JOBname
is not specified, the default value is *.
jobname
indicates the name of the job for which the TAPEREQ
control statement is processed.
The TAPEREQ
control statement is used only when the specified jobname
matches the job name in the request.
Note:
If you are coding aTAPEREQ
statement for DFHSM
, you must specify JOBname
as a selection criteria. Using DATASET (DSN)
can cause unpredictable results.optionally, specifies the step name. If the STEPname
parameter is not specified, the default value is *
.
stepname
indicates the name of the step for which the TAPEREQ
control statement is processed. The TAPEREQ
control statement is used only when the specified stepname
matches the step name in the request.
optionally, specifies the program name.
The program name used is the job step program name. The default value is *
.
program-name
indicates the program name for which the TAPEREQ
control statement is processed.
The TAPEREQ
control statement is used only when the specified program-name
matches the program name in the request.
optionally, specifies the data set name. The default value is **
.
dataset-name
indicates the data set name for which the TAPEREQ
control statement is processed.
The TAPEREQ
control statement is used only when the specified dataset.name matches the data set name in the request. Rules for RACF
and SMS
enhanced generic naming apply.
If you are coding a TAPEREQ
statement for DFHSM, you must specify JOBname
as a selection criterion. Using DATASET (DSN)
can cause unpredictable results.
The name you specify on this parameter might be different from the value coded in the DSN
parameter on a DD statement. For example,
DSN=&&ABC
may be coded on a DD statement if a data set is temporary. However, the actual data set name is not &&ABC
. Similarly, if the DSN
parameter refers back to a previous DD statement, the data set name is resolved to the referred-to data set. Thus, the data set name referred to must be coded on the DATASET
parameter in order for the TAPEREQ
control statement to be processed.
optionally, specifies the DD name of the data set.
DD-name
indicates the DD name.
optionally, specifies the retention period and the relationship that must exist. If you do not specify either RETPD
or EXPDT
, the default value is RETPD(GE,0)
(any expiration date will match this criterion).
EQ
- Equal to.
NE
- Not equal to.
GT
- Greater than.
GE
- Greater than or equal to.
LT
- Less than.
LE
- Less than or equal to.
retention-period
indicates the retention period in days for the data set. Specify the number of days as a 1- to 4-digit decimal number.
optionally, specifies the expiration date and the relationship that must exist.
EQ
- Equal to.
NE
- Not equal to.
GT
- Greater than.
GE
- Greater than or equal to.
LT
- Less than.
LE
- Less than or equal to.
expiration-date
indicates the expiration date of the data set in YYDDD
or YYYY/DDD
format.
optionally, identifies a specific volume id or range of volsers. If VOLSer
is omitted, the default value is *
(any volume).
Using a combination of TAPEREQ
statements and POLicy
commands, SMC enables you to specify allocation policy based on specific volume serial numbers. Refer to Oracle's ELS publication Configuring and Managing SMC for more information.
volser
or volser-range
indicates the volume id or a range of volumes.
VOLSer
requires that the POLicy
parameter is also specified.
optionally, specifies the label type to be used to select the policy.
label-type
indicates the label type. Specify one of the following:
SL
indicates standardlabeled tape. This is the default if the parameter is omitted.
AL
indicates ANSIlabeled tape.
NL
indicates nonlabeled tape.
NSL
indicates nonstandard labeled tape.
LABEL
is valid only if POLicy
is also specified.
optionally, specifies the name of a device esoteric group to be matched with the esoteric supplied in the JCL (or through IDAXESOT
).
esoteric-name
indicates the esoteric group name.
This can consist of one to eight alphanumeric or national (#, @, $) characters. A slash (/) or hyphen (-) is also valid.
JCLESOT
is valid only if POLicy
is also specified. JCLESOT
only matches at SSI55 (IDAX) or SSI24 (allocation) time, such that a POLICY
containing SUBPOOL
and MGMTCLAS
will not be selected by this parameter.
The following example illustrates the use of the JCLESOT
and ACTRECT
parameters:
TAPEREQ DSN(V047970.JCLESOT.*) JCLESOT(HVTSS11) POLICY(POL1) TAPEREQ DSN(V047970.JCLESOT.*) ACTRECT(V) POLICY(POL1) TAPEREQ DSN(**) POLICY(POL2) POLICY NAME(POL1) MED(V) REC(V) MGMT(HSCX400) SUBP(SUBP1) POLICY NAME(POL2) MED(ECART)
In this example, jobs that specify UNIT=HVTSS11
(with the matching DSN
) will be assigned a VIRTUAL
media and rectech at SSI55/SSI24 time. All other data sets will be assigned a media of ECART
. At mount message time, if the recording technique of the allocated drive is virtual for the matching DSN
, then the management class and subpool from POL1
are assigned. Otherwise, no subpool or management class is assigned.
optionally, specifies the recording technique to be used to determine the policy at mount time if the drive where the mount is requested conflicts with the previously selected policy, or if there is no previously selected policy.
For example, if the JCL esoteric prevents selection of a policy recording technique or esoteric substitution, the selected policy might have a scratch subpool inconsistent with the drive where the mount is requested.
Also, if criteria that are not available at mount time, such as JCLESOT
, are used for policy selection, SMC mount processing may not have a policy available to assign mount parameters such as SUBPOOL
and MGMTCLAS
. Specifying ACTRECT
allows a default override.
rectech-name
indicates the recording technique name.
ACTRect
is valid only if POLicy
is also specified.
optionally, specifies the name of a policy (defined by an SMC POLicy
command) to be associated with the allocation or mount request.
policy-name
indicates the policy name.
The SMC uses this policy name to determine all policy information associated with an allocation or mount request.
The named policy must be defined using a POLicy
command before the TREQDEF
command is processed.
See "POLicy" for more information about the SMC POLicy
command. Refer to Oracle's ELS publication Configuring and Managing SMC for information about creating new POLicy
definitions based on existing TAPEREQ
statements.
Use the following procedure to disable a TAPEREQ
definition:
Edit the definition data set containing the current TAPEREQ
control statements.
Delete the parameters of the TAPEREQ
control statement you want to disable, or delete the TAPEREQ
control statement.
Issue the TREQDEF
operator command to reload the definition data set.
To disable all TAPEREQ
definitions, load a definition data set that contains only one TAPEREQ
control statement with no parameters.
Note:
If any individualTAPEREQ
control statement is in error, the entire set is discarded.Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC UEXit
command defines the load module invoked for a specific user exit, and specifies whether the user exit is enabled or disabled.
User exits 1, 2, 4, 8, 9, 10, 11, 12, and 13 are invoked and managed by the SMC.
Note:
Use this command to load each user exit you want to use. If a user exit is not loaded, it will not be called.
All user exits are executed on the host where the SMC resides, regardless of where the library server resides.
Only one format of a given user exit can be invoked, regardless of the number of TapePlexes the SMC interacts with. The desired format (HSC) is specified using the FORMat
parameter.
HSC User exit 7 (SLSUX07
) is no longer supported.
These user exits must reside in a library accessible to the subsystem.
User exit information is not honored when an SMC POLicy
applies to an allocation, or a mount.
Refer to Oracle's ELS publication ELS Legacy Interfaces Reference for information about each user exit.
As shown in Figure 2-38, the UEXit
command includes the following parameters:
optionally, displays status information for all user exits.
LIst
is the default when no parameters are specified on the UEXit
command.
LIst
may be specified with other parameters. In this case, the LIst
is generated after the other parameters are processed.
optionally, specifies the user exit number. Valid values are 1, 2, 4, 8, 9, 10, 11, 12, and 13.
optionally, specifies the user exit's load module name.
name
indicates the load module name (for example, SLSUX01
).
optionally, specifies the format of user exit to be enabled or disabled.
the HSC user exit format.
optionally, loads the specified user exit, making it available for use.
If a user exit is not loaded, it will not be called. A subsequent load of a module for the same user exit causes the currently active copy of the load module to be deleted when its use count reaches zero.
optionally, enables a user exit that was previously disabled due to a problem.
optionally, disables a user exit to allow for problem resolution.
Interfaces:
Console or SMCCMDS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC acquires drive type information from both the MSP/EX operating system and the ELS library control systems (TapePlexes). For the ELS library control systems, HSC data returned from configuration queries is used to augment information returned from the operating system for library-controlled devices.
The SMC UNITAttr
command enables you to specify device addresses and attributes to augment operating system information for nonlibrary controlled devices, and effectively ignore configuration information from TapePlexes for specified devices when multiple TapePlexes define the same device address. The SMC UNITAttr
command enables you to do the following:
Set MODEL=IGNORE
for device addresses not available for this host.
Specify model types for nonlibrary devices on this host.
Specify NOTAPEPlex
for a nonlibrary device address or range that is defined to multiple TapePlexes, but for this host the attached devices belong to the specified TapePlex.
Specify TapePlex ownership and model for devices that may be referenced by a mount after the SMC is started but before the TapePlex is initialized.
Refer to Oracle's ELS publication Configuring and Managing SMC for information about configurations that may require or benefit from the use of UNITAttr
commands.
Note:
Existing HSC UNITATTR
control statements are not disabled. However, UNITATTR
statements for nonlibrary and MODEL(IGNORE)
devices are only processed for remote SMC 6.0 client systems. HSC UNITATTR
statements for library and virtual drives are not used in any HSC processing after release 6.0.
SMC does not support a UNITDEF
command. Each UNITATTR
command is parsed and processed independently.
HSC nonlibrary and MODEL=IGNORE
UNITATTR
statements are no longer returned to SMC on a configuration query. Therefore, if you use UNITAttrs to bypass devices for allocation or to define the device type of nonlibrary drives, you must define these UNITATTR
commands to the SMC subsystem.
As shown in Figure 2-39, the UNITAttr
command includes the following parameters:
optionally, specifies device numbers for which UNITAttr
device attributes are assigned.
devnum
, devnum-range
, or devnum-list
indicates the device number, device number range, or device number list.
optionally, specifies an esoteric for which UNITAttr
device attributes are assigned. When device characteristics are modified, all of the devices in the specified esoteric are modified.
esoteric-name
indicates the MSP esoteric name. This name must be defined to MSP, and must contain only tape devices known to SMC.
optionally, specifies that the model type for the device numbers specified by the ADDRess
parameter or ESOTeric
parameter should be determined from the device UCB, or, for a device which was previously set to MODEL=IGNORE
, that the MODEL
information from the library server should be restored.
lists the UNITAttr
model information for the device numbers specified by the ADDRess
or ESOTeric
parameter.
optionally, specifies the model type of the transport to be assigned the device numbers specified by the ADDRess
parameter.
model-type
indicates the model type.
See Appendix A, "MEDia, RECtech, and MODel Values" for a list of valid model-type
values.
optionally, specifies the name of a TapePlex to be associated with the drive before communication is established.
TAPEPlex
is required when MOdel(VIRTUAL)
is specified. MOdel(VIRTUAL)
drives cannot exist as "non-library" devices.
the TapePlex name.
If specified, this name must match a TapePlex name defined in a TAPEPlex
command.
optionally, removes the TapePlex association from the specified device addresses.
optionally, specifies that the specified address or address range are nonlibrary devices, even when configuration queries from ELS library control systems indicate that the device is library controlled. Use this parameter when a local nonlibrary device address overlaps a TapePlex owned device that is not accessible from his host.
Note:
When a MOdel
is specified with TAPEPlex
, the configuration query model information returned from the TapePlex is assumed to be the ”real” or ”correct” model, and it overrides any MOdel
specified in the UNITAttr
command.
If TAPEPlex
is specified for an address, but that address is not returned from the configuration query for that TapePlex, an error message is issued, but the erroneous TapePlex ownership remains with the specified device address. As a result, any mounts destined for the specified device address are not automated and are rejected by the specified TapePlex.
Interfaces:
Console or SMCPARMS
data set
UUI Support: Yes (No XML/CSV output)
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC USERMsg
command enables you to specify additional message identifiers for messages to be intercepted and passed to the library subsystem's user exit 01. You can also use this command to list the message identifiers for messages that have been defined using the USERMsg
command.
As shown in Figure 2-40, the USERMsg
command includes the following parameters:
optionally, lists the message identifiers in the customer-defined message table. This is the default if no parameters are specified.
optionally, specifies a message to be added to the customer-defined message table. This message is passed to user exit 01.
msgid
indicates the message identifier for the message to be added.
Note:
This parameter may only be specified in theSMCPARMS
data set.Interfaces:
Console, utility, SMCCMDS
or SMCPARMS
data set
UUI Support: Yes (no XML/CSV output)
Subsystem Requirements:
Active SMC required
The SMC VMSG
command enables you to start or stop the Virtual Storage Manager console (VSMc) message processor client. The VMSG message processor client enables the local SMC subsystem to receive and reply to messages issued by the remote VSM console server.
As shown in Figure 2-41, the SMC VMSG
command includes the following parameters:
optionally, displays VMSG
task status information.
optionally, lists only the VMSG processor for the named server.
SSSSSSSS
indicates the server name. If specified, then the named server must have been previously defined by an SMC SERVer command.
LIst
is the default when the STArt
, STOp
, or PREfix
keywords are not specified.
optionally, starts a VMSG message processor client.
specifies the server name for the VMSG processor.
SSSSSSSS
indicates the server name. The server name is required and must have been previously defined by an SMC SERVer
command.
optionally, defines a type-list containing one or more type(s) of messages that are received by the VMSG
client.
Specify one or more of the following in the type-list
, using a comma to separate values:
Receive all messages. This is the default. If ALL
is specified, it cannot be specified with any other message types. This is the default.
Receive highlighted WTO messages.
Receive non-highlighted WTO messages.
Receive messages that require a reply.
optionally, specifies the message prefix identifier that will identify messages from this VSM console server in the SMC subsystem log. If not specified, then the specified server
name is used as the message prefix.
PPPPPPPP
is the message prefix identifier. The prefix can be a maximum of 8 characters in length and can contain any combination of the following:
A-Z
0-9
@#$,.()+-=<|!;%>?:
optionally, stops a VMSG message processor client.
specifies the server name for the VMSG
processor.
SSSSSSSS
indicates the server name. The server name is required and must have been previously defined by an SMC SERVer
command.
optionally, specifies the message prefix identifier that will identify messages from this VSM console server in the SMC subsystem log. If not specified, then the specified server name is used as the message prefix.
PPPPPPPP
indicates the message prefix identifier. The prefix can be a maximum of 8 characters in length and can contain any combination of the following:
A-Z
0-9
@#$,.()+-=<|!;%>?:
specifies the server name for the VMSG processor.
SSSSSSSS
indicates the server name. The server name is required and must have been previously defined by an SMC SERVer
command.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes, supports XML and CSV
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC XCLIENT
command enables you to define XAPI clients that use a different protocol version than the default server XAPI security protocol.
Note:
The XCLIENT
command is only necessary to define clients that use the older "unsecure" protocol. If an XAPI request originates from a client that is not defined with a XCLIENT
command, it will be challenged to produce XAPI login credentials.
If you have back-level ELS or non ELS clients communicating with your ELS 7.3 SMC HTTP server, then they must be defined as protocol version 0 clients with the XCLIENT
command.
The entire XCLIENT
command is not echoed in the SMC0000
message.
XCLIENT
(suppressed) is echoed for all XCLIENT
commands.
The entire XCLIENT
command is not logged when the SMC LOG
command is active.
XCLIENT
(suppressed) is logged for all XCLIENT
commands.
XCLIENT
commands must be specified before any HTTP
or SERVer
commands.
As shown in Figure 2-42, the XCLIENT
command includes the following parameters:
optionally, displays all XCLIENT
settings. LIst
is the default when no parameters are specified on the XCLIENT
command.
optionally, specifies the IP resolver host name on which the client resides.
HHHHHHHH
indicates the name of the client. The HOst
name must be a resolvable name in the TCP_IP
name table. The following rules apply:
The value must be between 1 and 8 characters in length.
The first character must be an alpha character or a digit.
The last character must be an alpha character or a digit.
Any character between the first and last must be either an alpha character, digit, hyphen, or dot.
optionally, specifies the IP address for the client.
NN.NN.NN.NN
indicates The TCP/IP address.
Note:
IPaddress
and HOst
are mutually exclusive.optionally, specifies the name of the client. If the client is SMC/MSP, the NAme
specified should be the name returned as client_subsystem_name
. Otherwise, the NAme
specified should be the name returned in the client_name
. If NAme
is specified as "*", then any request from the specified HOst
or IPaddress
will be defined as using the specified protocol version.
CCCC
indicates the name of the client.
optionally, specifies the protocol version. The default is 0.
0
indicates the older "unsecure" protocol version.
1
indicates the XAPI security protocol version.
Interfaces:
Console, utility, SMCCMDS
data set, or SMCPARMS
data set
UUI Support: Yes, supports XML and CSV
Subsystem Requirements:
Active SMC required, or may be input to the SMCUSIM
utility
The SMC XUDB
command enables you to add, update, delete, and list XAPI Security users.
The XAPI security user list is maintained by both the client and server. In cases where the client and server reside on the same host (that is, SMC/MSP), the XUDB
user list is shared.
Note:
The same USER
must be defined on both the client and server.
A USER
is unique by SERVER
. If the same SMC HTTP server is servicing multiple TapePlexes, any defined users will have access to all TapePlexes.
The entire XUDB
command is not echoed in the SMC0000
message.
XUDB
(suppressed) is echoed for all XUDB
commands.
The entire XUDB
command is not logged when the SMC LOG
command is active.
XUDB
(suppressed) is logged for all XUDB
commands.
The XUDB
commands must be specified before any HTTP
, SERVer
or TCPip
commands.
As shown in Figure 2-43, the XUDB
command includes the following parameters:
displays the specified user on the XAPI security list. LIst
is the default when no parameters are specified on the XUDB
command. In this case, all users are listed.
specifies the user name to be listed. UUUUUUUU
indicates the user name.
specifies that the specified user name or password is to be added to the XAPI Security list.
specifies the user name to be added. UUUUUUUU
indicates the user name.
specifies the user password. PPPPPP
indicates the password.
specifies that the specified user name or password is to be updated in the XAPI Security list.
specifies the user name to be added. UUUUUUUU
indicates the user name.
specifies the user password. PPPPPP
indicates the password.
specifies that the specified user/password is to be deleted from the XAPI Security list.
specifies the user name to be added. UUUUUUUU
indicates the user name.
Oracle recommends that you maintain the XAPI Security user list in a sequential data set, to include XUDB ADD
entries for the XAPI Security user list.
In your SMC startup parameters, include an SMC READ
command for your XAPI security data set.
The XUDB ADD/UPDATE/DELETE
command can be used to modify the XAPI Security user list on the operational SMC/MSP. Any changes must also be reflected in the XAPI SECURITY
data set.
The XAPI Security data set will be secured by SAF(RACF)
permissions.