User Control Service function
This topic describes the planning and implementation considerations for UCS.
Planning and Installation Considerations
UCS is intended to provide controls directly to your users with a minimum of datacenter involvement, therefore implementation considerations are minimal.
Security Requirements
UCS depends on your installation’s security facility (e.g. RACF, ACF, or Top Secret) to determine whether a user can control a specific job. ThruPut Manager simply makes a System Authorization Facility (SAF) call to determine the user’s authority. This call is modeled on and performs identically to the SAF calls made by SDSF. You must define the resources used to make the SAF calls.
Checking for access to the job
The call used to check for access to the job:
CLASS(JESSPOOL)
RESOURCE($$TM.node.owner.jobname.jobid)
node
Is the current node name.
owner
Is the userid of the job’s submitter, unless overridden by the USER keyword from the JOB statement.
jobname
Is the name of the current job.
jobid
Is the JES2 job identifier for the current job.
Checking for HOLD authority
This call is used to check for authority to apply a hold to the job:
CLASS(OPERCMDS)
RESOURCE($$TM.jesx.MODIFYHOLD.BAT)
jesx
Is the name of the JES2 subsystem.
Checking for RELEASE authority
This call is used to check for authority to release the job:
CLASS(OPERCMDS)
RESOURCE($$TM.jesx.MODIFYRELEASE.BAT)
jesx
Is the name of the JES2 subsystem.
JECL for UCS
Requests for UCS services can be initiated through ThruPut Manager JECL statements that are inserted by your users. For a full description and syntax of these statements, refer to the UCS User Guide or JECL Reference Guide.
JECL Statements for UCS | |
|---|---|
JECL Statements | Purpose |
/*DJC ANDIF | Specifies additional conditions that must be satisfied for a RUNIF or FLUSHIF statement. |
/*DJC CONDIFT | Specifies the condition or conditions that must be satisfied be- fore this job is released by DJC. |
/*DJC FLUSHIF | Defines dependencies that the job has on other jobs or events in the DJC Group that will cause the job to be flushed. |
/*DJC GROUP | Associates a job with a DJC Group. |
/*DJC MESSAGE | Allows jobs to describe a system or application message that is to trigger the signal of an event or events. |
/*DJC RUNIF | Defines dependencies that the job has on other jobs or events in the DJC Group that will allow the job to run. |
/*DJC SIGNAL | Signals a DJC event. |
/*JTS HOLD_ UNTIL | Allows job submitters to apply a JTS hold, and describes when the hold is to be removed. |
/*MHS_USER HOLD | Allows a job submitter to request that a ThruPut Manager user hold be applied to the job. |
JAL for UCS
Several JAL Descriptors are provided to support UCS. These are described in the JAL Reference Guide and UCS User Guide.
JAL Descriptors for UCS | ||
Descriptor | Type | Purpose |
$DJC_CLOSE | Logic | Indicates whether the DJC GROUP JECL statement includes the CLOSE keyword. |
$DJC_CLOSE_TIME | Range | Allows you to determine the value specified for the CLOSE_TIME keyword on the DJC GROUP JECL statement. |
$DJC_GROUP | Char | Allows you to determine the DJC Group name specified on the DJC GROUP JECL statement. |
$DJC_HISTORY_COUNT | Range | Allows you to determine the value specified for the HISTORY_COUNT keyword on the DJC GROUP JECL statement. |
$DJC_HISTORY_DAYS | Range | Allows you to determine the value specified for the HISTORY_DAYS keyword on the DJC GROUP JECL statement. |
$DJC_HOLD | Logic | Indicates whether the DJC GROUP JECL state- ment includes the HOLD keyword. |
$JTS_DATE | Range | Allows you to check the “hold until” date speci- fied for the job. |
$JTS_TIME | Range | Allows you to check the “hold until” time speci- fied for the job. |
$MHS_USER_ HOLD# | Range | Allows you to check the number of MHS_USER HOLD JECL statements. |
ThruPut Manager Initialization Statement Changes
UCS uses the parameters DJC, JTS, and UHS in the OPTIONS keyword of the JES2 initialization statement TMPARM.
JES2 Initialization Statement for UCS Refer to Installation-Guide | |
|---|---|
Statement | Purpose |
TMPARM | Keywords added to enable and disable UCS components. |
The initialization statements JTS OPTIONS and DJC SET allow you to set global defaults. Additionally, the UCS SET initialization statement provides some control over the selection order of jobs in the same Service Class. You can promote a job over jobs that have arrived earlier by setting its arrival time; however, jobs with arrival times that are earlier than the newly set arrival time are still selected first.
The syntax of these statements is described in the chapter “TMSS Initialization Statements” in the Base Product: System Programming Guide.
Initialization Statements for UCS | |
|---|---|
Statement | Purpose |
DJC SET | Sets global defaults for DJC. |
JTS OPTIONS | Sets global defaults for JTS. |
UCS SET | Sets UCS handling of arrival time. |
Operator Command Changes
UCS provides operator commands to manage its parameters and availability, and to display and modify certain aspects of jobs under its control. These are described in the Operating Guide.
Operator Commands for UCS | |
|---|---|
Command | Purpose |
DJC ? | HELP | Displays a list of all the commands available with the DJC function. |
DJC CLOSE | Allows an operator or user to close a DJC Group in the same manner that a CLOSE signal from a job would. |
DJC DELETE | Deletes DJC history data for the specified DJC Group. |
DJC DISPLAY | Displays information about the current state of DJC and jobs managed by DJC. |
DJC HOLD | Requests a user hold for a job managed by DJC or for a DJC Group. |
DJC PURGE | Purges a job managed by DJC from DJC management. |
DJC RELEASE | Releases a job or DJC Group that was previously held by a / DJC HOLD command. |
DJC SET | Allows an operator to specify certain default values. |
DJC SIGNAL | Allows an operator/user to signal an event or completion of jobs. |
JTS ? | HELP | Displays a list of all the commands available with the JTS function. |
JTS DISPLAY | Displays jobs that are under the control of JTS or the current JTS options. |
JTS RESET | Allows you to reset any date and time dependency of a job under the control of JTS and is awaiting execution. |
MHS_USER ? |HELP | Displays a list of all the commands available with the MHS_ USER function. |
MHS_USER DISPLAY | Displays jobs that are in the MHS_USER hold category. |
MHS_USER RELEASE | Removes a job from the MHS_USER hold category. |
TM OPTIONS | Changed. Allows you to enable, disable, and display the status of ThruPut Manager components. |
Installation Summary
The steps required to implement UCS are:
- Install the UCS modules as per the instructions contained in the accompanying Installer’s Guide. This component includes several ISPF panels and a TSO command. These elements are placed in the proper libraries during the installation of ThruPut Manager. To activate UCS, you must concatenate the DTMMENU, DTMPENU, and DTMTENU data sets defined during the INSTALL process to your current ISPF environment.
- When UCS is installed according to the Installer’s Guide, the option names DJC, JTS, and UHS are added to the selection of options that can be controlled through the OPTIONS keyword of the TMPARM JES2 initialization statement and the TM OPTIONS operator command. The default for these options is enabled, therefore no special action is required to activate them.
- Review the DJC SET initialization statement to ensure the DJC defaults reflect your installation’s operating environment.
- Review the JTS OPTIONS initialization statement to ensure the JTS defaults reflect your installation’s operating environment.
- Review the UCS SET initialization statement to ensure the UCS defaults reflect your installation’s operating environment.
- Restart ThruPut Manager on all systems.
After these steps have been completed, UCS is installed and ready for use by your users.