M.ER Supplied Variables
External Reference Entries
The following tables list commonly required entries and additional external reference entries. New technologies may require other entries, and these will be documented in the ISPW Interfaces Guide.
Commonly Required Entries
Type Code | Description |
|---|---|
$COMPANY | The company name of the site. This field can be used in any site panels. |
$TECHSP1 | A string used to describe the primary technical support person or action to be taken when there is an ISPW error. This variable is used in ISPW error messages or panels directing users to contact ISPW support staff. |
$TECHSP2 | A string used to describe the secondary technical support person or action to be taken when there is an ISPW error. This variable is used in ISPW error messages or panels directing users to contact ISPWsupport staff. It may be left empty to indicate there is no secondary person or action available. |
$USER1 | A String that represents the label for the User_Var_1 that is stored against the User Data. This label is used on the M.U, U.0, and “Join Users” functions. During the installation process, it is set to “Department”. |
$USER2 | A String that represents the label for the User_Var_2 that is stored against the User Data. This label is used on the M.U, U.0, and “Join Users” functions. During the installation process, it is set to “Function”. |
APIOVRVR |
Apply IWG048A to make this variable available. To enable this functionality after installing the PTF, define a new M.ER variable called APIOVRVR, set its value to Y, then refresh the server. |
APRVCTLO | A variable used to prevent the owner of a component from promoting and approving the Set for all levels or a specific level in ISPW. |
BKUPMODE | Set to A (automatic) to save copies of Prod (Staging) to a Warehouse, which can speed up processing. When a new version is promoted to production, ISPW will perform an “async” backup. The benefits of enabling this feature aren’t realized until at least one new version has been promoted to production. For example, if V1 is in production when BKUPMODE is enabled, when V2 is promoted to production, ISPW will still need to do warehouse backups of V1 as part of the promote. After the promote of V2 is complete, the V2 parts will be backed up by the new async backup process. After that, when subsequent versions are promoted to production, the benefits of turning on this feature will be realized. |
CRLIMIT | This has been added as part of PTF IWG483A. If set, this will limit the amount of data sent back to the user, by limiting the number of rows returned to the user when displaying component references (TSO AX command, TSO Analysis function, Topaz View Impacts display). |
CTUSERID | This has been added as part of PTF IWG327A. If this variable is set to 'Y', then any requests to download files from the mainframe to Topaz will use the CT user ID instead of the requesting user’s ID. This can add a layer of security to enable update access only by those using ISPW. Access by ISPW in Topaz would not be done directly under their user ID. If you set dataset security to disallow direct access by users, it would enforce access only through ISPW in Topaz and not through any other means, such as ISPF or Topaz Host Explorer. All access would be tracked by ISPW for Auditing purposes. |
DPSEQHLD | This has been added as part of PTF IWG498A. If set to Y, new logic to improve the sequencing of deploy packages will be enabled. The default value is N. |
EXRLCRTE | Exit name for the Create Release function. Describes an ISPF invocation, for example: ISPEXEC SELECT CMD(%WZURLCT) |
EXSTLOCK | Exit name for the Set Lock function. Describes an ISPF invocation, for example: ISPEXEC SELECT CMD(%WZULOCKE) |
HCICTENF | This has been added as part of PTF IWG277A. Setting this on can provide for more security by controlling the connection for dataset access. This can be useful for sites that do not want remote sites to connect directly. It will enforce usage of the HCI parm 'CTNAME' in the 'ISPW_ENV' block. If this property is set to Y, then any requests to download files from the mainframe to Topaz or the Topaz CLI will force users to connect in through the HCI CT, which will then connect to the CTLOCAL CT. If it is not set to Y, then users will connect in through only the HCI CT directly to the dataset, or only through the CTLOCAL CT if there is no HCI CT defined. The result is that you can disallow direct LPAR access by users. |
HEAD2 | This 8-character or less value is used in messages and panels to refer to a “work order” or “work request” identifier that may be associated with an assignment. The ISPW standard name is WORKREQ. A site can optionally change the value to something more meaningful for their users. |
LSTLIM1 | If set, will limit the amount of data sent back to the user, in MB. (For example, if set to 500, only 500 MB will be sent at a time; after that the data will be truncated and the search will need to be refined.) If this value is set to 0, there is no limit. |
LSTLIM2 | If set, will limit the amount of data sent back to the user based on number of rows returned. (For example, if set to 1000, only the first 1000 rows will be returned for a List. If a search is done in the repository for all Tasks at PROD level, and there are 50,000 tasks at PROD, a list of only 1000 will be displayed.) If this value is set to 0, there is no limit. |
OVLYSETI | This is used if a customer requires overlay messages displayed on a set (with the + signs next to setid). If the value is YES, when an overlay warning message is issued for a task that is promoted in a Set, a message is added to the Set to notify the approver and/or any interested parties about the overlay condition. |
PARSSAVE | If set to Y, the Parse on Save feature will be enabled. When an ISPW/Eclipse user saves a source file, CM will pass additional information to CT, allowing EF to parse the source. |
PPINCL | This has been added as part of PTF IWG343A. It adds support for -INC and ++INCLUDE statements to the ISPW COBOL parser. They will be handled in the same manner as the standard COPY statement. This parsing is important for Impact Analysis to function properly if you use these statements. Add this M.ER entry and set it to Y to tell the parser to accept these statements. |
PRNTDSN | The ISPF option 3.6 dataset name to be printed. It can be determined by browsing the panel. |
PRNTPGM | The function invoked to start ISPF option 3.6 print processing. It can be determined by browsing the SEL statements in the ISPF option 3 panel. |
RECOVERY | A YES/NO flag used to indicate if standard ISPF edit recovery is used at the site. Note that setting this switch to “YES” will not take effect if it has been disabled at the ISPF level. |
RLSEID | This has been added as part of PTF IWG309A. This property is for Topaz to control what data is to be returned for a release. Valid values:
|
RLSEPFX | This has been added as part of PTF IWG309A. This property is for Topaz to control what prefixes are returned. Valid values:
|
RTRNASGN | A YES/NO flag used to indicate if the Assignment ID(s) for Task(s) in a Set should be returned with the Webhook notification for Completed and Terminated events. Valid values:
|
RXDPLOGA | Defines the amount of space to allocate for the Deploy Log. Used in WZU@ACI#. If not specified, a default of SP(3 30) TRACKS is used. Example Usage: SP(10 2) TRACKS – will allocate a dataset with an initial size of 10 tracks and will add 2 more tracks each time the log fills up. |
RXDPLOGP | Determines the name of the Deploy Log High Level Qualifier. This prefix has been changed as a part of PTF IWG284A, which introduced the ability to Browse the Deploy Log in Topaz. As a part of that change, the number of characters was limited to 12. However, if all other fields are at their maximum in the Default Naming convention, there is only room for 11 characters. The Dataset Name will be of the format: RXDPLOGP.R.<ReqID>.PKG<PKGID>.#<DPENV>.LOG If RXDPLOGP is longer than 12 characters, shorten it and rename the HLQ for your existing Deploy Log Datasets to match the new RXDPLOGP. After updating this variable, restart CM and all CT tasks. |
SMTPHOST | Email Interface System Name. |
SMTPJOB | Email Interface SMTP Job Name. |
SMTPNODE | Email Interface NJE Node. |
SMTPZONE | Email Interface Time Zone. |
SXDEBUG | Specifies the value for the ISPW Debug variable to be used in Set Processing. This is useful for debugging new exits that are executed in the background during Set Processing. See ISPW-Debug-and-Trace-Facilities for further information. |
SXLOGALC | Allocation Parameters for Set Logs. Each time a Set executes a dataset is created where the log information can be written. |
SXLOGPFX | Dataset Prefix for Set Log Datasets. The Dataset Name will be of the format: sxlogpfx.Snnn.#nnnnnnn.LOG where nnnnnnnn is the Set ID. |
SXMAILOK | Enable sites to send E-Mail messages if Sets complete normally. The sample WZUSETX CLIST provided with the base will send E-Mail messages to designated users. If the value is YES, the last update users and the users defined in the M.AD table SXNOTIFY variable will be notified that the set has completed normally. If the value is NO, only the SXNOTIFY users are notified if a Set fails. |
SXPOSTFT | Provided to enable sites to File Tailor batch jobs from the Set Completion User Exit. When a Set has finished processing, the local Set Completion Exit WZUSETX is invoked. The sample WZUSETX CLIST provided with the base will File Tailor skeleton WZUPOSTX if the variable SXPOSTFT has the value YES. |
WIPMSG | Indicates whether the email interface is invoked for component overlay conditions. |
WVOPALL/ | These two variable combined contain the list of operations that are valid from the ISPW Task List. |
WVOPHIST | Task Operations can be included in this entry that require logging to the Task History. ISPW by default logs the major operations (for example, G, P, X, I, FB, and D). If the customer requires further operations to be logged, list them here. The format of the list is a space-delimited list of operations, for example, “D G X”. To obtain the full functionality of the API improvements for Topaz for Total Test Intelligent Test Case Execution (PTF IWG311A), you must add operation G to this list. |
WZZLLIB | The ISPW program load library. Used in File Tailoring. |
Additional External Reference Entries
Type Code | Description |
|---|---|
SECRTCFG | A flag used to indicate if the security validation for the SERVER RTCONFIG SECRULE needs to be performed. Valid values:
|
SXMDTIME | Time in seconds for set to remain in dispatch status. For example, 300. |
SXMETIME | Time in seconds from last exec_pulse. For example, 7200. |
SXMIMSGS | Enables SX informational messages. For example, N. |
SXMINTVL | Number of 30-second intervals before verifying a running set. For example, 10. |
WIPDSQL | If set, enables dynamic SQL queries for Work List and for Health Check WIP processing in Parts Utilities. Enabling dynamic SQL can improve CPU usage when doing Work List searches under some circumstances. We recommend enabling dynamic SQL if a site is experiencing excessive CPU consumption when doing Work List searches.
|
Implementing APRVCTLO
Perform the tasks in this section to implement the variable APRVCTLO. Use of APRVCTLO enables ISPW administrators to prevent the owner of a component from both promoting and approving the Set that contains the component, either for all levels or for a specific level in ISPW. This allows administrators to prevent users from approving their own work.