![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
TIBCO Mainframe Service Tracker provides facilities and standard MVS methods for configuring and administering the product. The software contains partitioned data set (PDS) members that consist of a default set of parameters, which are normally sufficient to activate the product.Each configuration parameter contains a keyword, which specifies how to implement a particular function and its associated value. Keywords, which are alphanumeric with no spaces or blanks (low values), must start in column 1 of the input record. For PDS member input parameters, you must separate keyword values with an equal sign (=).You must specify keyword values in the valid format. Keywords can be uppercase, lowercase, or mixed case; and are usually in one of the following formats:
• A string or sentence with embedded spaces. Be sure to enclose the entire string or sentence within single quotation marks (for example, ’TIBCO Software Inc.’). This string is truncated if it exceeds the maximum length.
If you do not specify a keyword value, TIBCO Mainframe Service Tracker applies the default value, if any.You can insert comments or comment lines between parameters or after keyword values. A comment follows the first space, as in JCL comments. An entire comment line begins with an asterisk in column 1.Table 11 describes the main parameters in TIBCO Mainframe Service Tracker.
Table 11 Main Parameters The identity of the associated subsystem. The value must be unique for each instance of TIBCO Mainframe Service Tracker on a logical partition (LPAR). You can also specify the value in the parm field of the EXEC statement, preceded with -S, for example, -SSXKS. If you specify the value in both the parm field and control member, the value in the latter takes precedence.Default: SXKS A job name or job-name prefix that specifies the job or jobs to be monitored by the Tracker Server. MONJOB supports up to 50 entries.Table 12 describes the parameters and values that define their characteristics and behavior. Typically, you construct multiple component parameter statements. You can only specify those statements after the COMPONENT control statement.
Table 12 Component Parameters The component within TIBCO Mainframe Service Tracker. Each component represents a single subtask. The value cannot be blank.MAIN – The main taskTASK – The task manager taskCONSOLE – The console handler, which stops and modifies commandsSUBSYSTM – Creation and termination of a subsystem, which monitors job activitiesSUBSMCL – The Smart Client interfaceHAWKCNTL – Hawk control routinesHAWKPRC – Hawk processing routinesJOBTRACK – Information tracking of job and job stepsRVSEND – Parameters for publishing z/OS event messages through RendezvousRVLISTEN – The parameter for listening to RESEND requestsRVDISPCH – The parameter for dispatching events The name of the load module to be attached in support of a component. The value cannot be blank. 0 – Always published regardless of the value.1 – Errors only or exceptions that do not happen in normal processing.2 – Major events, such as startup and shutdown; major connections; and unusual but expected events.3 – More common events.4 – Detailed trace of processing that describes all events as they occur.5 – Hex displays of control blocks and data structures.Default: 2 The name of a component defined as ATTACHTYPE=SHRQ, which functions as a recipient of work messages. The name of a component defined as ATTACHTYPE=SHRQ, which functions as a source of work messages. An identifier with which the console modify commands specify the receiving component. The amount of time (in microseconds) to wait for TIBCO Mainframe Service Tracker to initialize. The maximum value is 2000000000.Default: 10000000 The amount of time (in microseconds) to wait for TIBCO Mainframe Service Tracker to terminate. The maximum value is 2000000000.Default: 2000000 The ATTACHTYPE=NONE setting causes TIBCO Mainframe Service Tracker to bypass the related component. That is, the related component is not attached or processed during this invocation of TIBCO Mainframe Service Tracker.Table 13 describe the parameters of the component RVSEND. You can only specify these statements after the RVSEND COMPONENT control statement.
Table 13 Rendezvous Parameters The daemon used by the RVSEND component to publish z/OS event messages. The syntax is host:port, where:
• host is the URL or IP address of the machine on which the Rendezvous daemon runs.
• port is the TCP port.Default: 7500 The User Datagram Protocol (UDP) service port used by the Tracker Server components for communication.Default: 7555 Default: tibtrk.jobstep The subject name to which the Tracker Server sends the z/OS SYSLOG messages.Default: tibtrk.logmsg The subject name to which the Tracker Server sends the response after receiving a resend request for a specific job or for all jobs.Default: tibtrk.resend.responseIf a reply subject is in the requested message payload, the Tracker Server sends only the response to that reply subject or inbox. The subject name to which the Tracker Server listens for all RESEND requests.Default: tibtrk.resend.requestTable 14 describes the Hawk component parameters. For details on Hawk parameters, see the TIBCO Hawk Installation and Configuration manual.
Table 14 Hawk Parameters
• host is the URL or IP address of the machine on which the Rendezvous daemon runs.
• port is the TCP port.Default: 7474 NETWORK (Optional) Default: 7473 Default: TIBCO-TRACKER Default: TIBCO TRACKER for Bushmen The frequency (in microseconds) in which the Hawk processor checks for an alert. The maximum value is 2000000000.Table 15 describes the SYSLOG parameters.
Table 15 SYSLOG Parameters A SYSLOG message ID or a prefix of the message ID to be tracked and reported by the Tracker Server, for example:LOGMSGID supports up to 50 entries. A word or a portion of the SYSLOG message to be tracked and reported by the Tracker Server, for example:LOGCHAR supports up to 50 entries.Table 16 describes a JOBTRACK parameter.
Table 16 JOBTRACK Parameter The parameter that, if present, causes the Tracker Server to hold job information for 0 to 60 minutes.Default: 30Table 17 describe the z/OS subsystem parameters.
Table 17 z/OS Subsystem Parameters Default: SXKASINI Default: SXKASFUN Table 18 describes the subsystem control parameters, which you enter without an equal sign or a value. They are stand-alone keywords, similar to TRK or CYL in JCL.
Table 18 Subsystem Control Parameters Table 19 describes the log and trace parameters.
The values for the parameters that specify the diagnostic level (such as DBGLVLALL) ranges from 0 through 5, where 0 is none and 5 is verbose unless otherwise specified, as with DBGLVLALL-WTO.
Table 19 Log and Trace Parameters Default: 2 The default diagnostic level for the intertask messages for all components. SRW stands for send-receive-wait. The recommended value is 2.Default: 2 The diagnostic level for write-to-operator (WTO) messages issued by the subsystem functions routines and the SMF exits.1 – Allow error messages2 – Show major events, such as one-time starting messages3 – Show major events, such as one-time starting messages4 – Activity messages for the requested jobs5 – Activity messages for all jobsDefault: 2 LOGDDN (optional) The Data Definition (DDName) of the data set in which the formatted log information is written. DDName must appear in the Tracker Server’s startup procedure.Valid Value: DDNameDefault: TIBLOG LOGFMT (optional) The log format. When log information for the Tracker Server is routed to a print file, this value determines the edit format in which to display the routed information.1 – Short format output2 – Short format with information on the location of the Tracker ServerDefault: 2 LOGROUTE (optional) The location to which the output for log entries is routed. The DDName selected for routing to a print file is specified by the value of the LOGDBUGDD keyword. The DDName selected for routing to a disk file is specified by the value of the LOGDISK1|LOGDISK2|LOGDISK3|LOGDISK4|LOGDISK5 keywords.P(rint) – Formatted print format: a formatted print file, similar to SYSPRINT.D(isk) – Disk file: a VSAM [virtual storage access method] RRDS [Relative Record Data Set] disk file formatted for the Tracker Server.Default: PNote: P is the only valid option in the current release. LOGDBGDDN (optional) The DDName of the data set in which LTA [Logging, Tracing, and Auditing] agents of the Tracker Server internal debugging information is written. The DDName must appear in the Tracker Server’s startup procedure, if required, for the debugging messages to be displayed.Valid Value: DDNameDefault: LOGDEBUG LOGDBGLVL (optional) The trace debug level. The LTA agents of the Tracker Server have their own internal debugging facility. Always leave this value as the default (1) unless TIBCO Support requires the output. The DDName LOGDBGDDN is required in the startup procedure if you specify a nonzero value. The output is directed to SYSOUT.Default: 1Note: A value of greater than 1 produces overhead and many lines of output. TRCDDN (optional) The DDName of a data set in which Tracker Server-formatted trace information is written. This name must appear in the Tracker Server’s startup procedure.Valid Values: DDNameDefault: TIBTRACE TRCFMT (optional) The format for logged trace information. When trace information is routed to a print file, this value determines the format in which to display the routed information.1 – Short format output2 – Short format with Tracker location informationDefault: 2 TRCROUTE (optional) The location to which the output for trace entries is routed. The DDName selected for routing to a print file is specified by the value of the TRCDDNAM keyword. The DDName selected for routing to a disk file is specified by the value of the TRCDISK1|TRCDISK2|TRCDISK3|TRCDISK4|TRCDISK5 keywords.P(rint) – Formatted print format: a formatted print file, similar to SYSPRINT.D(isk) – Disk file: VSAM RRDS disk file formatted for TIBCO Mainframe Service Tracker.Default: PNote: P is the only valid option in Release 1.0.0. TRCDBGDDN (optional) The DDName of a data set into which LTA agents of the Tracker Server’s internal trace information is written. This name must appear in Tracker Server’s startup procedure, if required, for the debug messages to be displayed.Valid Value: DDNameDefault: TRCDEBUG TRCDBGLVL (optional) The trace debug level. The LTA Agents have their own internal debugging facility. Always leave this value as the default (1) unless TIBCO Support requires the output. The DDName LOGDBGDDN is required in the startup procedure if you specify a nonzero value. The output is directed to SYSOUT.Default: 1Note: A value of greater than 1 produces overhead and many lines of output.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |