MANTIS Server Installation, Startup, and Configuration for

Cincom® MANTIS®

MANTIS Server Installation, Startup, and Configuration for z/OS®

P39-5118-10

Version 6.5.01

Cincom® MANTIS® MANTIS Server Installation, Startup, and Configuration for z/OS® Publication Number P39-5118-10 © 1995-1998, 2001, 2004, 2006, 2008, 2010, 2011, 2013, 2015, 2018, 2019 Cincom Systems, Inc. All Rights Reserved This document contains unpublished, confidential, and proprietary information of Cincom. No disclosure or use of any portion of the contents of these materials may be made without the express written consent of Cincom. See https://www.cincom.com/us/company/terms-policies for a list of Cincom trademarks and other trademarks that may appear in Cincom product documentation. All other trademarks are trademarks or registered trademarks of their respective companies. Cincom Systems, Inc. 55 Merchant Street Cincinnati, Ohio 45246-3732 USA PHONE: +1 513 612 2300 FAX: +1 513 612 2000 WORLD WIDE WEB: http://www.cincom.com

Attention: Some Cincom products, programs, or services referred to in this publication may not be available in all countries in which Cincom does business. Additionally, some Cincom products, programs, or services may not be available for all operating systems or all product releases. Contact your Cincom representative to be certain the items are available to you. External Web site disclaimer: Cincom Systems, Inc. does not own, nor does it warrant the accuracy, adequacy or completeness of, the information and materials contained in linked documentation, and expressly disclaims liability for any errors or omissions in the information and materials. No warranty of any kind, implied, express or statutory, including but not limited to the warranties of non-infringement of third party rights, title, merchantability, fitness for a particular purpose and freedom from computer virus, is given in conjunction with the information and materials contained in this linked documentation. Nothing contained herein constitutes nor is intended to constitute an offer, inducement, promise, or contract of any kind. The data, information, and materials contained herein are for informational purposes only and are not represented to be error free. Any links are provided as a courtesy. They are not intended to nor do they constitute an endorsement by Cincom Systems, Inc. of the linked materials.

https://www.cincom.com/us/company/terms-policies

http://www.cincom.com/

Release information for this manual Cincom® MANTIS® MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118-10, is dated June 1, 2019. This document supports release 6.5.01 of MANTIS®.

Cincom Technical Support for MANTIS® To contact support, please visit https://supportWeb.cincom.com.

https://supportweb.cincom.com/

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 4 Contents

Contents

1. Introduction ........................................................................... 7

Terminology used in this manual ........................................................................ 8

2. Compatibility issues .................................................................. 9

Internal architecture of the transfer file has changed since 5.4.01 .............................. 9 Compatibility issue between the 5.4.01 and 5.5.01-or-higher transfer files ............... 9 Applying a fix that prevents MANTIS 5.4.01 from writing to a 5.5.01-or-higher transfer file............................................................................................................ 9

Bound program incompatibilities ....................................................................... 12 Unbinding programs on your MANTIS system before an upgrade ............................. 12 Binding programs on your 6.4.01 MANTIS system after you have upgraded it ............. 12

Compatibility issue between MANTIS 6.0.01-or-higher programs with breakpoints and previous MANTIS ...................................................................................................... 14

Saved breakpoints are not backward compatible .............................................. 14 Avoiding a NUCUVLE error in a pre-6.0.01 MANTIS release ................................... 14 Steps to take when you encounter a NUCUVLE error in a pre-6.0.01 MANTIS release ... 14

PWA larger than 64K incompatible with releases prior to 6.2.01 ................................. 15 Text fields larger than 254 bytes incompatible with releases prior to 6.2.01 .................. 16 New functionality not supported in prior releases of MANTIS ..................................... 17 MANTIS program name displacement in the TWA.................................................... 18

3. MANTIS Installation Wizard (MAIWI) .............................................. 19

JCL jobs generated by MAIWI............................................................................ 20 JCL jobs described in the order they are generated and submitted ........................ 20

MANTIS modules remaining after MANTIS installation is complete ............................... 21 Modules in the DFHRPL library ..................................................................... 21 Module linking ......................................................................................... 21

Starting MAIWI ............................................................................................. 22 What you will need to know before starting MAIWI ............................................ 22 Procedure for starting MAIWI ....................................................................... 22

Using MAIWI................................................................................................. 23 Option numbering in MAIWI ......................................................................... 23 Getting HELP in MAIWI ............................................................................... 23 Suspending the installation process and terminating MAIWI .................................. 23 Navigating MAIWI ..................................................................................... 23 Generating a JCL job ................................................................................ 24 Determining a JCL job’s success or failure ...................................................... 25

Reference information for MAIWI’s menu panels .................................................... 26 Action Selection Menu ............................................................................... 26 “New Install Menu” and the two Upgrade Menus ............................................... 29

4. Running MANTIS ...................................................................... 37

Making MANTIS definitions available to the currently running CICS .............................. 37 Supplied users and passwords ........................................................................... 38

Supplied system administrator user ............................................................... 38


Supplied development user ......................................................................... 38 MANTIS back door sign-on in CICS ...................................................................... 39

Description ............................................................................................ 39 Syntax .................................................................................................. 39 Password-du-jour ..................................................................................... 40 Considerations ........................................................................................ 40 Troubleshooting....................................................................................... 40

5. Batch Dialog Facility (BDF) Install function ..................................... 41

Overview of the Batch Dialog Facility ................................................................. 41 How MAIWI uses the BDF Install function ............................................................. 42

6. Customizing MANTIS after the installation or upgrade ....................... 43

Customizing the startup, menu, and termination programs ....................................... 43 Entities to change in order to customize MANTIS ............................................... 43 Entity copies in an upgrade ......................................................................... 43

Considerations for MASTER:SIGN_ON and MASTER:TERMINATE .................................... 46 Creating program profiles for protected libraries (HPO users only) .............................. 47 Nominating the Shared Pool list (HPO users only) ................................................... 48

Shared Pool Facility and the IADB file ............................................................ 48 Shared Pool and the Statistics Facility ........................................................... 48 Shared Pool and memory location ................................................................. 48

Running the Split SETPRAY Utility (optional) ......................................................... 49 Running the Split SETPRAY Utility (optional) .................................................... 49 Splitting your SETPRAY again after MANTIS reinstallation .................................... 49 Steps for splitting your current SETPRAY cluster ............................................... 49 Elements needed in order to run the Split SETPRAY Utility .................................. 49

7. Installing AD/Advantage ............................................................ 50

Preliminary considerations .............................................................................. 50 AD/Advantage installation procedure ................................................................. 51

8. Verifying MANTIS SQL Support installation ..................................... 55

Verifying that MANTIS SQL Support installation is complete ...................................... 55 Verifying installation completion for DB2 ........................................................ 55 Verifying installation completion for SUPRA Server SQL ...................................... 55

Verifying that MANTIS SQL Support is available for use ............................................ 56 Verifying availability of MANTIS SQL Support if you have DB2 ............................... 56 Verifying availability of MANTIS SQL Support if you have SUPRA Server SQL .............. 56

9. Linking XREF and performing batch maintenance ............................ 57

XREF linkage ................................................................................................ 58 MANTIS 5.5.01 and above XREF Facilities ........................................................ 58 Programs required in order to run the XREF batch jobs ....................................... 58

Sample input statements in your XREF MACLIB ...................................................... 59 Sample input statements............................................................................ 59 XREFJOB information ................................................................................ 59

10. Installing SSF SL2033 .............................................................. 60

Installation procedure .................................................................................... 61


11. Installing zMantisIDE for use with MANTIS Web .............................. 63

12. CICS Web Interface ................................................................ 64

Purpose of the CICS Web Interface ..................................................................... 65 Enabling the CICS Web Interface ....................................................................... 66

Requirements for enabling the CICS Web Interface ............................................ 66 Checking the availability of the CICS Web Interface ................................................ 67

Steps .................................................................................................... 67 Checking communication between the MantisIDE web application and the web-aware MANTIS Server................................................................................................................ 68

A. MANTIS enhancements and changes and new or changed MANTIS messages ............................................................................................. 69

Reference ................................................................................................... 69

B. Renaming a program entity ........................................................ 70

Steps for renaming a program entity .................................................................. 70

C. Renaming a screen entity .......................................................... 71

Steps for renaming a screen entity..................................................................... 71

D. MANTIS Unbind and Bind Utilities ................................................ 72

Introduction: Incompatibility between pre-5.6.01 MANTIS and 6.4.01 .......................... 72 Unbind and Bind Utilities ................................................................................ 73

Procedure for binding and unbinding ............................................................. 73 Prerequisite for using Unbind and Bind Utilities ................................................ 73 Unbind Utility ......................................................................................... 73 SQLBind Utility ........................................................................................ 74 BINDLOG file ........................................................................................... 76

Index ...................................................................................... 81

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 7 Chapter: 1. Introduction Section: Terminology used in this manual

1. Introduction This guide describes how to install and configure MANTIS on z/OS® operating systems.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 8 Chapter: 1. Introduction Section: Terminology used in this manual

Terminology used in this manual Consider the terms and definitions in this chapter when using this manual.

“CICS” and “Transaction Server”

Throughout this manual, the use of “CICS” implies both CICS® and Transaction Server.

“Installation” vs. “upgrade”

Throughout this manual, “installation” generally implies either a new installation or an upgrade of a MANTIS system. When it is necessary to make a distinction, either “new installation” or “upgrade” will be used.

“Update current copy” and “upgrade-in-place”

These terms are used interchangeably throughout this guide.

“Module” and “program”

These terms are synonymous.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 9 Chapter: 2. Compatibility issues Section: Internal architecture of the transfer file has changed since 5.4.01

2. Compatibility issues Internal architecture of the transfer file has changed since 5.4.01

The internal architecture of the transfer file has changed since release 5.4.01. As a result, the Transfer Facility now has a capacity of 5,000 bins and 30,000 files.

The transfer file formats for releases 5.5.01 and higher are all the same. If you are upgrading from MANTIS 5.5.01 or higher, you can skip this section and go on to Bound program incompatibilities.

Compatibility issue between the 5.4.01 and 5.5.01-or-higher transfer files

MANTIS 5.4.01 can read a 5.5.01-or-higher format transfer file. However, having MANTIS 5.4.01 write to a 5.5.01-or-higher transfer file may corrupt the transfer file. Cincom has supplied a fix that prevents MANTIS 5.4.01 from writing to a 5.5.01-or-higher transfer file. For instructions on how to fix this issue, see the next section, Applying a fix that prevents MANTIS 5.4.01 from writing to a 5.5.01-or-higher transfer file.

Converting a 5.4.01 transfer file to the 5.5.01 and above format. The Transfer Conversion Utility Program (TCUP) converts a 5.4.01 format transfer file to the 6.1.01 format. For more information on TCUP, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

Applying a fix that prevents MANTIS 5.4.01 from writing to a 5.5.01-or-higher transfer file

Having MANTIS 5.4.01 write to a 5.5.01-or-higher transfer file can corrupt the transfer file. To avoid this, apply a fix to your MANTIS 5.4. In addition to preventing MANTIS 5.4.01 from writing to a 5.5.01-or-higher transfer file, this fix displays a MANTIS fault message when MANTIS 5.4.01 attempts to do so. To apply this fix, perform the following:

1. Verify that you have a current backup of your MANTIS cluster. 2. REPRO REPLACE the MANTIS.MCPU5401 dataset into your MANTIS 5.4.01 cluster.

MANTIS.MCPU5401 is the file name on the installation tape/cartridge.

During the installation process, the MANTIS Install Wizard creates the CINCOM.MANTIS.MCPU5401 file and then loads it from the tape/cartridge. The file name is the tape/cartridge file name, prefixed with the high-level qualifiers that were specified as part of the installation process.

3. Verify that the target is your MANTIS 5.4.01 cluster, as the patch will not apply to, and is in fact not needed for, a MANTIS 5.5.01-or-higher cluster.

4. Perform one of the following, depending on your installation media: - If you are installing from tape—REPRO REPLACE the CINCOM.MANTIS.MCPU5401

(this is the filename on the installation tape) dataset into your MANTIS 5.4.01 SETPRAY cluster.


You can perform this step before or after the MANTIS installation has completed.

- If you are installing from the FTP site—Do these steps:

Sign on to the FTP site with the username and password provided in the letter entitled Installing MANTIS 6.4.01 and AD/Advantage 6.4.01 for z/OS, M39-1040 (available only in hardcopy form).

With FTP, transfer the following file, in binary format, to TSO, using a temporary file name:

R6401.xxx/FILE/MCPU5401

In the preceding path, the value xxx represents the three-digit maintenance level of the release you are installing; this is documented in Installing MANTIS 6.4.01 and AD/Advantage 6.4.01 for z/OS, M39-1040 (available only in hardcopy form).

i. Perform a TSO RECEIVE to accept the file into a usable sequential format.

Details on performing steps A–C. For details on the syntax needed when you are using FTP to transfer files from the FTP site to the mainframe, refer to Installing MANTIS 6.4.01 and AD/Advantage 6.4.01 for z/OS, M39-1040.

ii. Once the TSO RECEIVE is complete, perform a REPRO REPLACE of the resulting dataset into your MANTIS 5.4.01 SETPRAY cluster.

You can perform step D before or after the MANTIS installation has completed.

- If you are installing from the MANTIS installation CD-ROM—Perform the following: iii. With FTP, transfer the following file, in binary format, to TSO, using a

temporary file name: E:\R6401.MLxxx\FILE\MCPU5401

In the preceding path, the value E represents the letter of your CD-ROM drive; your CD-ROM drive may have a different letter. The value xxx represents the 3-digit maintenance level of the release you are installing.

iv. Perform a TSO RECEIVE to accept the file into a usable sequential format.

Details on performing steps A and B. For details on using FTP to transfer files from the PC with the CD-ROM drive to the mainframe, refer to the letter entitled Installing MANTIS 6.4.01 and AD/Advantage 6.4.01 for z/OS, M39-1040 (available only in hardcopy form).

v. Once the TSO RECEIVE is complete, perform a REPRO REPLACE of the resulting dataset into your MANTIS 5.4.01 SETPRAY cluster.

You can perform step C before or after the installation is completed.

5. Sign on to the MASTER user, select the MANTIS Utilities option, and select the MANTIS Code Patch Utility. Use the MANTIS Code Patch Utility to apply the following fix, which you just copied into your SETPRAY cluster using IDCAMS: - Patch ID: 010413 - Description: Required patch to access a 5.5.01-or-higher format TRANSFER

cluster from 5401 MANTIS


- APMS code: MN5401

For more information on the MANTIS Code Patch Utility, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 12 Chapter: 2. Compatibility issues Section: Bound program incompatibilities

Bound program incompatibilities

Because Cincom has made major architectural changes to MANTIS in order to support a larger program Data Work Area (DWA), the format of programs that were HPO-bound and/or SQL-bound under any MANTIS release prior to 5.6.01 is incompatible with the format of bound programs under MANTIS release 6.4.01. As a result of this incompatibility, under MANTIS 6.4.01, you cannot access programs that were HPO-Bound and/or SQL-Bound under MANTIS prior to 5.6.01. Attempting to do so causes a NUCBOR (Bound in Old Release) error.

The unbinding on your prior MANTIS system is performed automatically. Cincom recommends that, after you perform the upgrade, you have the unbound programs automatically re-bound. To take care of these tasks, Cincom created the following two utilities:

MANTIS Unbind Utility. This utility performs the automatic unbinding prior to MAIWI’s upgrade of the MANTIS cluster. This is done automatically for all releases.

MANTIS Bind Utility. This utility re-binds the unbound programs after MAIWI successfully upgrades the MANTIS cluster.

Unbinding programs on your MANTIS system before an upgrade Before you upgrade to release 6.4.01, MAIWI automatically unbinds all of the HPO-

bound and/or SQL extended dynamic bound programs that are located on your current MANTIS system. MANTIS performs the unbinding automatically, but in order to do so, may have certain requirements:

If you are performing an upgrade-in-place. MAIWI requires update access to your current MANTIS system.

If you are performing a clone-upgrade. MAIWI does not require update access to your current MANTIS system, because MAIWI will perform the unbind on the copy that it creates during the clone-upgrade process.

Logging during unbinding

During the unbind process, MAIWI defines an external KSDS VSAM file that logs the following:

Which programs were unbound What type of unbinding was performed (HPO, SQL, or both) Other information needed to re-bind the programs, once the upgrade to release

6.4.01 has successfully completed

Binding programs on your 6.4.01 MANTIS system after you have upgraded it

After you have successfully upgraded your MANTIS system to release 6.4.01, one of the following must occur:

During the 6.4.01 upgrade process, MAIWI uses the SQLBIND utility to automatically rebind all of the programs on your 6.4.01 MANTIS system that require it. MAIWI asks you to enter Yes or No for this automatic rebind. The SQLBIND utility uses the log created during the unbinding as input.

After the 6.4.01 upgrade process successfully completes, you perform one of the following:

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 13 Chapter: 2. Compatibility issues Section: Bound program incompatibilities

- Run the SQLBIND utility to automatically rebind all of the programs on your 6.4.01 MANTIS system that require it. The SQLBIND utility uses the log created during the unbinding as input.

- Manually HPO BIND and/or SQL BIND all of the programs on your 6.4.01 MANTIS system that require it.

For more information on the unbind/bind process, see D. MANTIS Unbind and Bind Utilities.

Logging during binding

During the BIND process, MAIWI logs each program’s successful HPO and/or SQL binding.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 14 Chapter: 2. Compatibility issues Section: Compatibility issue between MANTIS 6.0.01-or-higher programs with breakpoints and previous MANTIS

Compatibility issue between MANTIS 6.0.01-or-higher programs with breakpoints and previous MANTIS

Saved breakpoints are not backward compatible When Cincom introduced new debugging commands for MANTIS 6.0.01, it enhanced the internal MANTIS code to make it use an improved statement format that can contain saved breakpoints. Because pre-6.0.01 MANTIS releases do not support this improved format, you cannot run MANTIS 6.0.01-or-higher programs containing saved breakpoints in any MANTIS release prior to 6.0.01. Attempting to do so may cause a NUCUVLE error (“This line does not start with a valid statement”) or may have other, unpredictable results.

Avoiding a NUCUVLE error in a pre-6.0.01 MANTIS release To avoid encountering a NUCUVLE error in a pre-6.0.01 MANTIS release, use the FSE command “CLEAR BREAK” to clear all breakpoints from MANTIS 6.0.01-or-higher programs before moving theseprograms into a pre-6.0.01 MANTIS release.

Steps to take when you encounter a NUCUVLE error in a pre-6.0.01 MANTIS release

If you encounter a NUCUVLE error in a pre-6.0.01 MANTIS release, perform the following to check for and remove breakpoints:

1. Log on to a MANTIS 6.0.01-or-higher User. 2. Open the MANTIS 6.0.01-or-higher version of the program in the MANTIS Full Screen

Editor (FSE). 3. Enter the following FSE command to check whether the program contains

breakpoints: SHOW BREAK

4. If you found program breakpoints in step 3 and you wish to save them for use under MANTIS 6.0.01 or higher, SAVE the program under a different name. This newly SAVED, renamed program is now the one loaded in the FSE.

5. If you found program breakpoints in step 3, enter the following FSE command to clear all breakpoints in the program: CLEAR BREAK

6. REPLACE the program. 7. Transfer the program to the pre-6.0.01 release MANTIS system. 8. If you SAVED the program under a different name in step 4, change the program

name back to the desired name.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 15 Chapter: 2. Compatibility issues Section: PWA larger than 64K incompatible with releases prior to 6.2.01

PWA larger than 64K incompatible with releases prior to 6.2.01 In releases prior to 6.2.01, the maximum size of the Program Work Area for a MANTIS program was 64K. In release 6.2.01 and above, the MANTIS administrator can set the PWA larger than 64K in the Customization macro, up to a maximum of 128K. If a Program Work Area does exceed 64K it is stored in a different format than in prior releases of MANTIS. If you move a program greater than 64K to a MANTIS prior to release 6.2.01, you will get a “NUCPTL: Program too large” error attempting to run or edit the program.

If you will be moving programs, edited/created on release 6.2.01 or above, to a release prior to 6.2.01, you should leave the parameter MXPWA=64K at install time. You can increase the size of this parameter once you are no longer running a prior release of MANTIS.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 16 Chapter: 2. Compatibility issues Section: Text fields larger than 254 bytes incompatible with releases prior to 6.2.01

Text fields larger than 254 bytes incompatible with releases prior to 6.2.01

In releases prior to 6.2.01, the maximum size of a text variable was 254 bytes. In release 6.2.01 and above, a program can have a text variable with a size greater than 254 bytes. If you define a text field, in a program, greater than 254 bytes, and you move the program to a release of MANTIS prior to 6.2.01, you will get a “NUCSOR: subscripts out of range” when you run the program, and MANTIS encounters the defining statement for that text variable.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 17 Chapter: 2. Compatibility issues Section: New functionality not supported in prior releases of MANTIS

New functionality not supported in prior releases of MANTIS The SET TRAP statement was introduced in release 6101.010 and is not supported in releases 5601 and below.

The $OPTION and SET $OPTION statements were introduced in release 6101.018 and are not supported in releases 6101.010 and below. Attempting to execute these statements in a prior release will cause a MANTIS fault.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 18 Chapter: 2. Compatibility issues Section: MANTIS program name displacement in the TWA

MANTIS program name displacement in the TWA Several vendors provide CICS monitors that gather statistics. In a MANTIS environment, the customer often wishes to see statistics on a MANTIS program-by-program basis, for billing or other purposes.

In order to collect this information, the monitor needs to get the MANTIS program name. The program name can be found in the task’s TWA. In MANTIS releases 6001 and up, the displacement from the start of the user's TWA for the 32-character program name is the same: x'04CB'.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 19 Chapter: 3. MANTIS Installation Wizard (MAIWI) Section: MANTIS program name displacement in the TWA

3. MANTIS Installation Wizard (MAIWI) The MANTIS Installation Wizard (MAIWI) guides you through each step of the MANTIS installation or upgrade process. MAIWI, a REXX™ EXEC, provides an ISPF-menu-driven dialog to perform the following:

Collect the information that you enter into the ISPF panels. Verify the entered information, where possible. Build and submit the JCL jobs necessary to complete the new installation or the

upgrade of your current MANTIS. Maintain a status of the success or failure of each step in the process.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 20 Chapter: 3. MANTIS Installation Wizard (MAIWI) Section: JCL jobs generated by MAIWI

JCL jobs generated by MAIWI As you run MAIWI, it generates up to seven JCL jobs. As each job is generated, you must inspect it, modify it if necessary, and submit it for execution. MAIWI generates the JCL for each job during a different portion of the information-gathering process. In order for each job to run, the previous job in the sequence must have successfully completed.

JCL jobs described in the order they are generated and submitted The jobs are listed below, each one identified by its installation library member:

MVXEPMRL. Except in new installations, this JCL job extracts the MANTIS release from your current cluster.

MVXEULOD. Transfers the installation files by one of the following methods: - From tape—Using IEBCOPY and IDCAMS. - From the FTP site—Using FTP and performing a TSO RECEIVE on the files. - From a CD-ROM—Performing a TSO RECEIVE on the files that were already

manually transferred from a CD-ROM. MVXECUST. Chooses customization values for MANTIS and then assembles and links

the CSOPCUST module. MVXEML. Links CICS MANTIS with the appropriate modules for your environment. MVXEMLB. Links Batch MANTIS with the appropriate modules for your

environment. MVXEBDFI. Adds RDO definitions to the DFHCSD file. It then runs the MANTIS Batch

Dialog Facility’s Install function, and also uses other utilities, to perform one of the following: - Initialize a new cluster to the new MANTIS release and maintenance level. - Upgrade your existing cluster to the new MANTIS release and maintenance level

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 21 Chapter: 3. MANTIS Installation Wizard (MAIWI) Section: MANTIS modules remaining after MANTIS installation is complete

MANTIS modules remaining after MANTIS installation is complete

Modules in the DFHRPL library

Module list

After MANTIS installation is complete, only the following modules are saved or replaced in your DFHRPL library:

CSOPGLBL. Required in order to run CICS MANTIS. MANTIS. Required. If, during the installation process, you select the option to

install the MANTIS Web component, the “MANTIS” module supports both terminal operation and MANTIS Web operation. Otherwise, the “MANTIS” module supports terminal operation only and is much smaller.

CSOPBDSO. Generated by the installation process. This tool is used to directly sign on to MANTIS, displaying the MASTER facility menu. This tool skips the execution of the MASTER:SIGN_ON program in case the program becomes unusable for some reason and prevents any logon to Mantis.

CSOPWANL. Generated by the installation process only if you select the option to install MANTIS Web. Required in order to use MANTIS Web. This module is a CICS WEB Services (CWS) analyzer program.

CSOPTSQC. Generated by the installation process only if you select the option to install the Temp Storage Cleaner Utility TransID and program.

Temporary Storage Cleaner definition. The Temporary Storage Cleaner deletes temporary storage for MANTIS web tasks that have exceeded a time limit that you, as the MANTIS Administrator, have specified. It consists of both the Temp Storage Cleaner Utility, which is a CICS stand-alone assembler program that cleans idle temp storage queues, and the Temp Storage Cleaner Facility, which is a MANTIS program that you, as the MASTER User, use to configure the Temp Storage Cleaner Utility. For more information on the Temporary Storage Cleaner, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

CSOPCORE. Generated by the installation process. This support tool, which runs only on a 3270 terminal, displays memory content. To run it, perform the following: On the MASTER User, select Run A Program. Enter the following: CONTROL:CORE

Although this module is named CSOPCORE by default, you can specify your own name for it.

Module linking The installation process creates the load modules by linking the needed modules from the installation libraries.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 22 Chapter: 3. MANTIS Installation Wizard (MAIWI) Section: Starting MAIWI

Starting MAIWI

What you will need to know before starting MAIWI Cincom recommends that, before you begin the installation process, you collect the information that MAIWI will require you to enter.

Procedure for starting MAIWI To start MAIWI, perform the following:

1. Transfer/copy the installation library from the media (cartridge, FTP site, or CD-ROM) from which you have chosen to perform the installation.

Step 1 details. For details on how to accomplish step 1, refer to the letter entitled Installing MANTIS 6.4.01 and AD/Advantage 6.4.01 for z/OS, M39-1040 (available only in hardcopy form).

2. Execute MAIWI by entering the following on the ISPF Primary Option menu: TSO EXEC ′your.MANTIS.install.lib(MVXXINST)′

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 23 Chapter: 3. MANTIS Installation Wizard (MAIWI) Section: Using MAIWI

Using MAIWI

Option numbering in MAIWI As you proceed through the installation process using MAIWI, you will notice that some menus have gaps in the numbering of options. This is normal—some menu items may not appear, depending on chosen features and other factors.

Getting HELP in MAIWI During MANTIS installation, you can access HELP by performing either of the following:

To see an overview of a panel’s purpose. Enter HELP on the command line and press the ENTER key.

To see specific information about a field or option. Place the cursor on a field or option and then perform one of the following: - Enter HELP on the command line, place the cursor on a field or option, and

press the ENTER key. - Place the cursor on a field or option and press your HELP key (PF1).

Suspending the installation process and terminating MAIWI At any time while you are using MAIWI, you can suspend the installation process and terminate MAIWI by pressing the RETURN key (PF4). Later, you can execute the MAIWI EXEC again and continue with the installation from the point at which you quit.

Navigating MAIWI The following sample steps demonstrate how to navigate MAIWI:

1. Execute MAIWI. For information on how to do this, see Procedure for starting MAIWI. The Welcome panel (MVXPINST) appears, displaying the MANTIS logo and copyright information. See the following screen shot:

2. Press the ENTER key.


The Action Selection Menu panel (MVXPAMS) appears. See the following screen shot:

3. Select an option from the Action Selection Menu panel.

A new panel, appropriate to the selected option, appears. 4. Perform one of the following in an iterative fashion until the installation is

complete: - If you are on an entry panel, you can perform either of the following after

entering data in the necessary fields: - Save the changes to the current panel and proceed to the next panel by

pressing the NEXT key. - Return to the previous panel without saving any changes to the current panel

by pressing the PREV key. - If you are on a menu panel, select an option. The appropriate panel appears. - If you are on a menu panel or an entry panel, you can return to a higher-level

menu panel by pressing the END key. On the higher-level menu panel, select an option. The appropriate panel appears.

Generating a JCL job At various points throughout the installation, you will be prompted to generate a JCL job. To do so, perform the following:

1. Generate the JCL job by performing one of the following: - Press the assigned JCL PF key. - Enter “JCL” in the Command line. - MAIWI displays the generated JCL job in the ISPF editor.

2. Inspect the generated JCL job in the ISPF editor; if necessary, modify the JCL job. 3. Use your own submit command to execute the JCL job. 4. Verify the JES output for a normal completion. 5. If there are any problems with the executed job, perform one or both of the

following, as appropriate: - Modify the JCL again, correcting any errors, and resubmit it.


- Re-enter the information that you supplied to MAIWI and then press the assigned JCL PF key or enter “JCL” to regenerate the job.

6. If necessary, use the RESTART= parameter to restart the JCL job from the failing step within the JCL job.

Determining a JCL job’s success or failure

Return codes for each step within an installation JCL job

Most steps within a JCL job have a return code of zero, but under certain conditions it is normal for some of these steps to have a return code of 4. If the non-zero return code is normal, you can find out what you need to do in response to it by looking at the comment block located at the beginning of the JCL job. If there is no comment block, the return code for each step within the JCL job should be zero, and the non-zero return code is the result of an error.

If necessary, you can use the RESTART= parameter to restart the JCL job from the failing step within the JCL job.

Steps within each installation JCL job indicating job success or failure

Two steps at the end of every installation JCL job inform MAIWI of the job’s success or failure. The names of these steps are the following, and one or the other of these steps will cause FLUSH to display in the JES job log:

JOBOK. Normally, JOBOK shows RC=0 on the JES job log. If JOBOK shows FLUSH on the JES job log, the job has failed and the MAIWI job status indicator will be updated accordingly.

JOBFAIL. Normally, JOBFAIL shows FLUSH on the JES job log.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 26 Chapter: 3. MANTIS Installation Wizard (MAIWI) Section: Reference information for MAIWI’s menu panels

Reference information for MAIWI’s menu panels

Action Selection Menu

HELP reminder. To see an overview of a panel’s purpose, enter HELP on the command line and press the ENTER key. To see specific information about a field or option, either enter HELP on the command line, place the cursor on a field or option, and press the ENTER key, or place the cursor on a field or option and press the HELP (PF1) key.

The options on the Action Selection Menu (MVXPAMS) are the following:

0- Installation wizard behavior options. This option displays the Installation Wizard Options entry panel (MVXPTPO), on which you can perform the following: - Change MAIWI options, including the following:

o Job name defaults o Navigation behavior within MAIWI o Activation of EXITS panel

- Check installation status when exiting MAIWI. - Generate all JCL in upper case. - PRE-installation JCL Generation mode

1- New MANTIS installation. This option assumes that no previously installed MANTIS exists. It guides you through the steps necessary to complete a new MANTIS installation. For details on the menu displayed by this option, see ‘“New Install Menu” and the two Upgrade Menus’ on page 31.

Do NOT select option 1 if you are upgrading! One erroneous method of attempting to upgrade with this option would be selecting this option and then performing an IDCAMS REPRO REPLACE of your current MANTIS VSAM clusters into the new VSAM clusters. If you do this, you will downgrade and corrupt the newly installed VSAM clusters. Instead, if you are upgrading, you must select option 2 or 3.

2- Clone-Upgrade – Copy your MANTIS and upgrade the copy. This option makes a copy of a current set of MANTIS VSAM clusters (SETPRAY, CSOT, EDPR, EEPR, and EHLP) and upgrades them to the new release or service level. The original set of MANTIS VSAM clusters are not modified in any way. For details on the menu displayed by this option, see ‘“New Install Menu” and the two Upgrade Menus’ on page 31.


Use option 2, Clone-Upgrade, to check how your applications run on the new release. Cincom recommends option 2 for current MANTIS customers who wish to compare how their applications run on the new MANTIS release with how their applications ran on the previously installed release. You can run more than one copy of MANTIS in the same CICS region, but you must specify CICS file names (DD names), for all MANTIS files, that differ from those of your already- installed MANTIS release. Also, for the following programs, you must specify program names and transaction identifiers that differ from those used in the already-installed release:

- CSOPWANL

- CSOPBDSO

- CSOPTSQC

- CSOPCORE

- MANTIS or MANTXML—For MANTIS 6.0.01, the program MANTIS supported only terminal operation, while MANTXML supported both terminal and MANTIS Web operation. For MANTIS 6.2.01 and above, there is only the program MANTIS, which can be configured at MANTIS product installation time to either support only terminal operation or to support both terminal and MANTIS Web operation. (MAIWI warns you if the selected DFHRPL library already contains a MANTIS load module with the name you specify here.)

When you’re installing a second MANTIS in the same CICS, you must specify names, for the programs MANTIS and CSOPGLBL, that differ from the ones used in the already-installed release. Finally, DB2 users must specify a plan/package name that differs from the one used by the already-installed release.

3- Upgrade-In-Place - Update your current MANTIS copy. This option, which is also referred to as an “upgrade in place” in this guide, upgrades your current MANTIS cluster to the new release or service level. For details on the menu displayed by this option, see ‘“New Install Menu” and the two Upgrade Menus’ on page 31.

Create backups! Before you select option 3, create backups of all your MANTIS VSAM clusters and your current linked MANTIS and related load modules.

Once you have selected option 3, Upgrade-In-Place, and completed the upgrade, you cannot back off the upgrade. Instead, if you wish to undo the update, you must restore the MANTIS clusters and modules from backups.

4- Maintenance. This option displays the Maintenance Menu (MVXPPMM). After you have completed a MANTIS installation or upgrade, you can use this menu to perform MANTIS maintenance functions. This menu has the following options: - 1- Job Card—This option enables you to modify the job card to meet your

company’s standards. - 2- Authorize a new password—This option enables you to create Authorization

records for any other CPUID, in batch, using the Batch Dialog Facility. - 3- Convert TRANSFER file to MANTIS 5.5 and above format—This option enables

you to convert a pre-5.5.01 transfer cluster to the current 6.4.01 format, so that MANTIS 5.5.01 and above can access it.

- 4- Create a new empty TRANSFER file—This option enables you to define a new transfer file and initialize it by copying the necessary entities from your newly installed or upgraded MANTIS cluster. This file will be in the new format so that MANTIS 5.5.01 and above can access it.


- 7- MANTIS Customization Macro—This option enables you to modify the CSOPCUST module to set different parameters.

- 8- Link CICS MANTIS and Batch MANTIS—This option relinks CICS MANTIS and Batch MANTIS. You would usually select this option after you have performed one of the following: o Applied maintenance to MANTIS modules. o Modified CSOPCUST with different parameters.

- 9- Upgrade a MANTIS in another region—This option upgrades the files of MANTIS in another region to the 6.4.01 level. This option only upgrades the clusters and does not go through the entire installation process. You may wish to use this option when upgrading another MANTIS system—for example, a production system.

- 10- Delete Uploaded files used for LOCAL installation—This option deletes the temporary files that were created by FTP when you successfully uploaded the installation files from a PC CD-ROM before performing a local installation.

- 11- Enable MANTIS Web component—This option adds the web component to your MANTIS module.

- 15- Installation Status Information—This option enables you to check the status of the last installation that you performed with MAIWI.

5- Uninstall MANTIS. This option displays the Uninstall MANTIS Menu (MVXPPPZ). This menu enables you to either completely reverse the MANTIS installation or just delete some of the libraries or entities created during installation. To uninstall MANTIS, select this option and then perform the following: a. Choose the objects that will NOT be deleted by entering NO next to each one. b. Generate the JCL job that will uninstall MANTIS. To do so, perform one of the

following: o Press the assigned JCL PF key. o Enter “JCL” in the Command line. MAIWI displays the generated JCL job in the ISPF editor.

c. Inspect the generated JCL job in the ISPF editor; if necessary, modify the JCL job.

d. Use your own submit command to execute the JCL job. The JCL job uninstalls MANTIS.

If you wish to delete your installation library, enter the following on the ISPF command line:

TSO DELETE ″your.MANTIS.install.lib″

6- Administration. This option displays the Installation Wizard Admin Menu (MVXPPMN). After you have completed a MANTIS installation or upgrade, you can use this menu to perform MANTIS maintenance functions. This menu has the following options: - 1- Reset Installation library to its original state—This option enables you to

reset the installation library to its original state by deleting members created during installation and updating remaining members to their original values. When you select this option, you are prompted to accept the reset action. Perform one of the following: o To proceed with the reset—Enter ACC (for ACCept) and press the Enter key. o To cancel the reset—Enter nothing and press the END key. After the reset is complete, you can perform a new, clone, or upgrade install. You can use this option either before or after an installation is completed.


- 2- Export/Import installation data information—This option allows you to keep multiple MANTIS installation versions. It avoids making you re-enter most of the information that you already supplied during an earlier installation. Export: Save the current installation data information into the dataset you specify on the 'Import/Export Dataset Name' column from the next panel. Import: Copy installation data information from a previous installation library or from data exported using this MAIWI function.

Resetting MANTIS. Once you have accepted option 1, you can no longer uninstall a MANTIS that was previously installed or upgraded with this installation library.

“New Install Menu” and the two Upgrade Menus After you select “Install-New – New MANTIS installation” (option 1), “Clone-Upgrade – Copy your MANTIS and upgrade the copy” (option 2), or “Upgrade-In-Place – Update your current MANTIS copy” (option 3) from the Action Selection Menu (MVXPAMS), one of the following submenus appears:

Install-New Menu (MVXPPMI) Clone-Upgrade Menu (MVXPPMC) Upgrade-In-Place Menu (MVXPPMU)

Once you select an installation or upgrade option, a new menu panel displays the major steps required for the selected option. You can navigate these steps in two ways:

Use the NEXT key after every entry panel without returning to the New Install or Upgrade menu panel.

After you complete each major step, use the END key to return to the New Install or Upgrade menu panel. At the menu panel, select the next major step.

Possible menu panel options on the installation and upgrade menus

Depending upon the option you selected on Action Selection Menu, some or all of the following options will be displayed on the resulting menu panel:

1– Job Card. This option displays an entry panel (MVXPPP1) on which you can enter all of your basic job card information. Before submitting a job as part of the installation or upgrade process, you can change the job name or any other job parameters.

2– Features Used with MANTIS. This option displays a menu panel (MVXPPM2) with the following options: - 1– Secured—This option displays an entry panel (MVXPPPS) on which you can

enter the password information provided to you with your installation package. This information includes your installation’s features, the MANTIS start and expiration dates, and the required password. MAIWI uses the information that you enter here to determine which files and modules are needed for your installation and to generate the CPUID record for your MANTIS.

- 2– Non-Secured—This option displays an entry panel (MVXPPPT) on which you can select database and feature options. MAIWI uses the information that you select here to determine whether certain modules and files are necessary for your MANTIS installation.


- 3– Tools—This option displays an entry panel (MVXPPPR) for MANTIS Back Door Sign On, Temp Storage Queue Cleanup, and Memory Diagnostic Display.

- 4– Environment information—This option displays an entry panel (MVXPPPU) and asks the following: o Whether a MANTIS 5.4 system still exists in your environment o Whether you want sample data to be loaded in the cross-reference file

(XREFIND) 3– Current MANTIS Objects. (For a new install, this option does not appear.) This

option displays an entry panel (MVXPPP3) on which you can enter the dataset names of your current MANTIS files. The file name list is created based upon information that you entered after selecting the Features Used with MANTIS option (option 2) on either the MVXPPPS and MVXPPPT panels (see the description of the previous step on this panel for information about the MVXPPPS and MVXPPT panels). Current MANTIS objects are upgraded differently, depending on whether you: - Clone a new copy and upgrade it—MAIWI copies files and upgrades the copies to

the new release. Your current files are not updated. - Upgrade-in-place the current copy—MAIWI updates datasets directly.

Create backups if you are performing an upgrade-in-place! If you have not already done so, create backups of the following files before proceeding to the next step in your upgrade-in-place:

- Your current MANTIS datasets - Your MANTIS module - Your CSOPGLBL module - Modules CSOPWANL, CSOPBDSO, CSOPTSQC, and CSOPCORE

If you use the MANTIS DB2 interface: DBRM

4– Edit JCL – Extract Release job. (For a new install, this option does not appear.) This option displays an entry panel (MVXPPP4). On this panel, perform the following to generate and execute a JCL job that extracts the current release number from your MANTIS SETPRAY cluster (MAIWI uses the release number during the upgrade’s tailoring step): e. Generate the JCL job by performing one of the following:

o Press the assigned JCL PF key. o Enter “JCL” in the Command line. o MAIWI displays the generated JCL job in the ISPF editor.

f. Inspect the generated JCL job in the ISPF editor; if necessary, modify the JCL job.

g. Use your own submit command to execute the JCL job. The JCL job extracts the current release number.

5– New MANTIS Environment. This option displays the New MANTIS Environment menu panel (MVXPPM5), from which you can perform the following: - Provide information about CICS and MANTIS environments—To do this, select

options 1 through 42 from this panel. - Provide information about your DBMS environment—To do this, select options 5

through 9 from this panel. Select this menu’s options in their numbered order. These options are the following: - 1– CICS dataset names and CSD information—This option displays the CICS

Environment entry panel (MVXPPPA). On this panel, enter the following:


o Name of the CICS SDFHLOAD dataset for your system o Name of the DFHRPL library into which you would like to place the MANTIS

executable module created by the CICS link job step o Name of the dataset in which your CICS RDO definitions reside (DFHCSD) o Name of the group that contains, or will contain, your MANTIS RDO

definitions o Name of the group list, if you would like the group added to a group list

- 2– MANTIS Transactions IDs—This option displays the MANTIS Transaction Ids entry panel (MVXPPPB). On this panel, enter the following: o Required. Primary transaction ID for MANTIS o Optional. A resume transaction ID to be used in a pseudo-conversational

environment. o Optional. A print task transaction ID. o Optional. A background task transaction ID. o Optional. A Web/MANTIS Studio transaction ID.

You can enter the optional transaction IDs later as part of MANTIS customization.

For more information on initial, resume, and paired transaction IDs, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

- 3– MANTIS DDname—This option displays the MANTIS DDname entry panel (MVXPPPH). On this panel, enter the CICS RDO DDnames for the MANTIS VSAM support files. Which files appear on the screen depend on the features you specified earlier.

For more information on MANTIS VSAM support files, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

- 4– MANTIS Exits—This option displays the MANTIS Exits entry panel (MVXPPPC). On this panel, enter the names of any custom exits that you have used with MANTIS. Consider the following when entering custom exit names: o For a new install—Cincom recommends that you do not use the sample

MANTIS exits for a new install. Instead, modify and link any necessary exits with MANTIS after you have researched them and customized them for your environment.

o For an upgrade—If you used MANTIS exits in a prior release, enter a YES next to the name of each exit that you previously used and specify the name of the linklib in which the exit can be found. If you changed an exit name from the default value, overtype the default name here with the name you used.

To cause the MANTIS Exits panel to display, you must enter Yes next to “Activate MANTIS Exits panel?” on the Installation Wizard Options entry panel (MVXPTPO). To display this panel, select “Installation wizard options” (option 0) from the Action Selection Menu panel (MVXPAMS).

- 41– MANTIS Web Component—This option displays the MANTIS Web Component entry panel (MVXPPPX). On this panel, enter CICS Web Services objects and the Temp Storage Cleaner Utility objects.

- 42 – Sequential files used by MANTIS – This option displays the sequential files used by MANTIS panel (MVXPPPW). On this panel, enter the 4-character TDQUEUE names and DSNAMES of the sequential files used by MANTIS.


Options 5–9 are selectable only if you have specified an expiration date in the Product Authorization panel (MVXPPPS) or entered YES (see panel MVXPPPT) for the feature associated with that option. For options 5 and 6, the associated feature is DB2; for option 7, the feature is SUPRA® Server SQL; for option 8, the feature is SUPRA PDM; and for option 9, the feature is IMS/DB. For more information on these panels, see the second bullet point under Possible menu panel options on the installation and upgrade menus.

- 5– DB2 dataset and DBRM—This option displays the “DB2 Dataset and DBRM” entry panel (MVXPPPD). On this panel, enter the information that enables MANTIS to connect to DB2.

- 6– DB2 Plan/Package and RDO—This option displays the “DB2 Plan Package and RDO” entry panel (MVXPPPJ). On this panel, enter one of the following: o Name of the DB2 plan to be used o Name of the DB2 package to be used

- 7– SUPRA Server SQL—This option displays the SUPRA Server SQL entry panel (MVXPPPE). On this panel, enter the name of the link library in which the ICICSQBL database interface module can be found.

- 8– SUPRA Server Total/PDM and RDM—This option displays the “SUPRA Server Total/PDM and RDM” entry panel (MVXPPPI). On this panel, enter the following: o Name of the link library containing the PDM batch interface o Name of the link library containing the PDM CICS interface module o Name of the link library containing the RDM CICS interface module

- 9– IMS/DB—This option displays the IMS/DB entry panel (MVXPPPG). On this panel, enter the following: o Name of the CICS Link Library where ASMTDLI for the CICS environment

resides o Name of the IMS RESLIB Link Library where ASMTDLI for the batch

environment resides 6– Transfer Remaining Files. This option displays the Transfer Remaining Files

Menu panel (MVXPPM6), displaying the following options that you should select in their numbered order: - 1- Select the media where the files will be transferred from—This option

displays an entry panel (MVXPPP0) on which you should perform the following: i. Enter the input media that you will be using.

Cincom no longer distributes cartridges.

ii. Fill out the appropriate information for your chosen input media. - 2- Define the target files location and high level qualifiers—This option displays

an entry panel (MVXPPP6) on which you should perform the following: iii. Enter the requested information. iv. Generate the JCL job that creates the necessary datasets and transfers the

rest of the installation files over from the input media. To do so, perform one of the following:

o Press the assigned JCL PF key. o Enter “JCL” in the Command line.

MAIWI displays the generated JCL job in the ISPF editor.


v. Inspect the generated JCL job in the ISPF editor; if necessary, modify the JCL job.

vi. Use your own submit command to execute the JCL job. The necessary datasets are created and the rest of the installation files are transferred from the input media. If your list of MANTIS features includes the HPO and/or the DB2 UDB z/OS, then all HPO-bound and/or SQL-bound programs are going to be unbound. A list of unbound programs is kept and used to rebind all programs later in the “Final Upgrade Setting” installation process.

7– MANTIS Customization Macro. This option displays the MANTIS Customization Macro Menu panel (MVXPPM7). On this panel, you can select options that enable you to tailor MANTIS. This menu panel contains the following options: - 1- Options—This option displays the Options entry panel (MVXPPPQ). On this

panel, enter the following: o Dataset and member name specifying the location of a previous CSOPCUST

job that you want to use as a model. This information makes up part of the data that MAIWI uses to create the CSOPCUST customization module for the new release. You will see this information when you select Parameter Setup (option 2) from the MANTIS Customization Macro Menu panel.

o Whether you wish to enable the Include Interfaces and Exclude Interfaces panels to be displayed from the MANTIS Customization Macro Menu panel (MVXPPM7).

For more information on INCLUDE/EXCLUDE interface, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

- 2- Parameter Setup—This option displays the first of the six Customization - Parameter Setup entry panels (MVXPPLW). These entry panels enable you to tailor MANTIS to your installation needs. For each of these panels, enter your information and then press the NEXT key to proceed to the next panel. When you have entered all of your information on the last panel, press the NEXT key to save the changes you have made to all five panels. On these panels, an indicator may display to the left of each listed parameter. These indicators can be any of the following values: o (C)hanged—Indicates that the specified value is changed from the MANTIS

default. This may be because you supplied a CSOPCUST job to use as a model, or you made a change on the current panel.

o (N)ew—Indicates that the specified value is new in this release of MANTIS. o (B)oth—Indicates that the specified value is both new to this release and

has been changed from the default.

To see which options are new or changed in the current release, as well as to find definitions and valid values for every option name under the Parm column, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

If, during the MANTIS installation procedure, in MAIWI, you set the MANTIS Web Support option to YES, and, in CSOPCUST, you set the MXDWA parameter value lower than 256K, MAIWI automatically sets the MXDWA value to 256K. For more information on the MXDWA parameter, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

- 3- Application Paired TransIDS—This option displays entry panel MVXPPK1. On this panel, enter the Start and Resume transaction ID pairs that you will use with MANTIS.


- 4- Include Interfaces—This option is disabled unless, on the Options entry panel (MVXPPPQ), you entered YES in order to enable the INCLUDE/EXCLUDE panels. This option displays menu panel MVXPPMA, which has the following options: o Interface name(s)—This option displays entry panel MVXPPK2. On this

panel, enter the names of the interfaces that you wish to include with MANTIS.

o Linklib where included interface resides—This option displays entry panel MVXPPPL. On this panel, enter the link libraries where the interfaces to be included with MANTIS reside.

- 5- Exclude Interface—This option is disabled unless, on the Options entry panel (MVXPPPQ), you entered YES in order to enable the INCLUDE/EXCLUDE panels. On this panel, enter the names of any interface programs that you wish to prevent a MANTIS program from calling.

- 6- Linking Customization Macro—This option displays the Linking CSOPCUST entry panel (MVXPPPK). On this panel, perform the following: vii. Enter the following: o Location where the assembled and linked customization module should

reside. o If the desired name for the assembled and linked customization module is

different than the default, which is “CSOPCUST”—Specify the module’s name.

viii. Generate the JCL job that will assemble C$COPCUST and link the resulting object module as the CSOPCUST load module. To do so, perform the following:


MAIWI displays the generated JCL job in the ISPF editor. ix. Inspect the generated JCL job in the ISPF editor; if necessary, modify the

JCL job. x. Use your own submit command to execute the JCL job.

The JCL job assembles C$COPCUST and links the resulting object module as the CSOPCUST load module.

8– Link CICS and Batch MANTIS. This option displays menu panel MVXPPM8. From this panel, select options that enable you to specify information necessary to link CICS and batch MANTIS. This menu panel contains the following options: - 1– CICS—This option displays the Linking MANTIS entry panel (MVXPPPM). In this

panel, perform the following: xi. Enter the following: o The library name where the “LE environment” modules reside. o The library name where the TCP/IP modules INET@ADD and INET@NTA

reside. o Name of the link library in which you would like the CICS MANTIS load

module to reside. This link library is usually the library into which you transferred the individual modules from the install media. The modules necessary for the CICS environment are copied from this link library to the DFHRPL library that you specified on the CICS Environment entry panel (MVXPPA).

o If you do not wish the MANTIS load module to be named MANTIS: New load module name.


o Value that determines whether MANTIS runs above the 16 MB line (YES or NO).

Cincom strongly recommends that you make MANTIS run above the 16 MB line by retaining the default value of “YES.” This means that MANTIS will also acquire its necessary storage above 16 MB line.

o Value that determines whether MANTIS is linked re-entrant (YES or NO). xii. Generate the JCL job that will link your CICS MANTIS. To do so, perform

one of the following: o Press the assigned JCL PF key. o Enter “JCL” in the Command line.

MAIWI displays the generated JCL job in the ISPF editor. xiii. Inspect the generated JCL job in the ISPF editor; if necessary, modify the

JCL job. xiv. Use your own submit command to execute the JCL job.

The JCL job links your CICS MANTIS. - 2– BATCH—This option displays the Linking Batch MANTIS entry panel

(MVXPPPN). On this panel, perform the following: xv. Enter the batch MANTIS objects by performing the following:

I. Enter the name of the link library in which you would like the batch MANTIS load modules to reside. II. Enter the program name for the read/write version of batch MANTIS. III. Optional. Enter the program name for the read-only version of batch MANTIS.

xvi. Enter the system library name where the BLDVRP macro resides.

The default link library name, which was created when the installation files were transferred from the install media, is LINKLIBB.

It is possible to have two versions of batch MANTIS:

One that allows both read and write capability to VSAM files

One that allows read-only capability—This version provides read-only access to the MANTIS (SETPRAY) and transfer (CSOT) clusters. It provides both read and write access to all external files. You should normally use this version when you print MANTIS design objects in batch while the MANTIS VSAM support files are open to the CICS region.

Since batch MANTIS uses Local Shared Resource (LSR) pools to provide optimum performance in batch, access to the BLDVRP macro is necessary. Normally, the BLDVRP macro resides in SYS1.MACLIB.

xvii. Generate the JCL job that will link your batch MANTIS module. To do so, perform one of the following:


MAIWI displays the generated JCL job in the ISPF editor. xviii. Inspect the generated JCL job in the ISPF editor; if necessary, modify

the JCL job. xix. Use your own submit command to execute the JCL job.

The JCL job links your batch MANTIS module. 9– Final Upgrade Setting. This option displays the Final Install/Upgrade Setting

entry panel (MVXPPP9), on which you should perform the following:


A. (This option does not appear if you are upgrading from MANTIS 5.5.01 or higher—it is not necessary, because your transfer file should already be in the 5.5.01- and-above format.) Specify whether you would like your current 5.4.01 transfer (CSOT) file to be converted to the new MANTIS 5.5.01-and-above format.

B. Automatic bind process for: HPO. From the list created in the “Download remaining Files” installation process step, MAIWI will HPO bind all previously HPO-bound programs.

C. Automatic bind process for: SQL. From the list created in the “Download remaining Files” installation process step, MAIWI will SQL bind all previously SQL-bound programs. If you want it to, MAIWI will submit jobs to create Package/Plan for each bound program.

D. Generate the JCL job that will perform the final settings by performing one of the following:


MAIWI displays the generated JCL job in the ISPF editor.

E. Inspect the generated JCL job in the ISPF editor; if necessary, modify the JCL job.

F. Use your own submit command to execute the JCL job. At this point, the Batch Dialog Facility sets the features that you have selected using MAIWI. The BDF then prepares the MANTIS primary cluster (SETPRAY) for use. Once this job has successfully completed, the entire installation is complete.

10–14. These options have been left out in order to make room for additional steps in the future.

15– Installation Status Information. This option displays the Installation Status Information panel (MVXUISCD), which has status indicators for each installation process step. The three possible values for each step are the following: - Blank—The step did not run or is not applicable for the selected action type

(new install, upgrade/clone, upgrade/update) or features that you have. - OK—The step was successfully completed. An asterisk (*) next to the status

indicates that a change occurred after the step had completed. - FAIL—The step was not successfully completed.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 37 Chapter: 4. Running MANTIS Section: Making MANTIS definitions available to the currently running CICS

4. Running MANTIS Making MANTIS definitions available to the currently running CICS

Before you can run MANTIS, you must sign on to CICS and then make MANTIS definitions available to the currently running CICS by performing one of the following (the steps differ depending on how you installed MANTIS):

For a new MANTIS system (INSTALL) or an upgrade of a current MANTIS version that was created by cloning the VSAM files and updating the clone (CLONE). Enter the following to make the MANTIS definitions available to the currently running CICS: CEDA INSTALL GROUP(xxxxxxxx)

xxxxxxxx is the RDO group name supplied to MAIWI.

For an upgrade that was created by updating the current VSAM files (UPGRADE). Enter the following to make the MANTIS definitions available to the currently running CICS: CEMT SET FILE(SETPRAY DLBLnames) CLOSE DISABLE

CECI RELEASE PROG(CSOPGLBL)

(Optional) CEDA INSTALL GROUP(xxxxxxxx)

CEMT SET PROG(MANTIS CSOPGLBL) NEW

CEMT SET PROG(CSOPWANL CSOPBDSO CSOPTSQC CSOPCORE) NEW

CEMT SET FILE(MANTIS ddnames) OPEN ENABLE

If you have selected new features as part of the upgrade, also enter the following (where xxxxxxxx is the RDO group name supplied to MAIWI):

CEDA INSTALL GROUP(xxxxxxxx)

MAIWI may have renamed MANTIS and CSOPGLBL modules.

Depending on your z/OS security package, you may need to define authorization for the MANTIS entities.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 38 Chapter: 4. Running MANTIS Section: Supplied users and passwords

Supplied users and passwords

Supplied system administrator user

User name and password

The supplied system administrator information is the following:

User name: MASTER Initial password:

- For a new MANTIS installation—The MASTER password is documented in Installing MANTIS 6.4.01 and AD/Advantage 6.4.01 for z/OS, M39-1040 (available only in hardcopy form).

- For an upgrade of an existing MANTIS system—The MASTER password is the same as it was before the upgrade.

To change the password for MASTER, use the User Profile Design Facility.

Once you change the password for MASTER, keep a record of this password in a secure place.

Further information on the MASTER user

For more information on the MASTER user, refer to the following sources:

For information on how to perform various functions available to the MASTER user: Refer to MANTIS Administration Tutorial for z/OS and z/VSE, P39-5309.

For information on all the features and functions available to the MASTER user: Refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

Several additional manuals, which can be accessed on the documentation CD, provide information relevant to the MANTIS system administrator.

Supplied development user

User name and password

The supplied system development user information is the following:

User name: EXAMPLES Initial password: CASINO

The EXAMPLES user contains some simple programming examples.

Further information on the EXAMPLES user

For information on getting started with MANTIS development, refer to the MANTIS Application Development Tutorial for z/OS and z/VSE, P39-5308.

Several additional manuals, which can be accessed on the documentation CD, provide information relevant to the MANTIS development user.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 39 Chapter: 4. Running MANTIS Section: MANTIS back door sign-on in CICS

MANTIS back door sign-on in CICS You can use the Back Door Sign On program to directly sign on to MANTIS, skipping the MASTER:SIGN_ON program and immediately displaying the MASTER Facility menu. This approach may be useful if the MASTER:SIGN_ON program becomes unusable for some reason, preventing a normal logon to MANTIS.

Description The Back Door Sign On program is a stand-alone program. MAIWI, the MANTIS Installation Wizard, automatically installs the Back Door Sign On program’s CICS transaction (default name: DBSO) and program (name: CSOPBDSO).

The Back Door Sign On program parses its input string and performs the appropriate action. If the syntax is correct, then the program will XCTL to the MANTIS module specified in the input string (default: MANTIS)

Syntax You can use one of two slightly differing syntaxes for executing the Back Door Sign On program. In each one, you must separate each parameter by a single space and enter the syntax from a blank CICS screen.

First syntax

Below is the first syntax for executing the Back Door Sign On program:

BDSO 123456 MANTIS SO

| | | | | | | +--> Auto Signon indicator. Optional. This literal, | | | which must always be ″SO″, tells MANTIS to | | | automatically sign into the MASTER User. The | | | default is a SPACE, which means that the | | | sign_on screen will be presented.

| | +---------> MANTIS load module name. Optional. The default | | is MANTIS.

| +----------------> Password-du-jour. Generated by the Cincom | Support representative. No default; this | password must be supplied.

+---------------------> CICS transaction to start program CSOPBDSO. The default is BDSO.

Second syntax

Below is the second syntax for executing the Back Door Sign On program. It is very similar to the first syntax, except that “SO” immediately trails the password-du-jour:

BDSO 123456SO MANTIS

Version 6501.006F syntax

Starting from version 6501.006F, the Back Door Sign On is also controlled by MANTIS. Even if the CSOPBDSO syntax is still valid, it is suggested to use this new syntax:

MANT 123456 SO

MANT can be any valid transaction that calls the Mantis load module. The SO literal must be uppercase.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 40 Chapter: 4. Running MANTIS Section: MANTIS back door sign-on in CICS

Password-du-jour The password-du-jour is a six-digit number that is valid for one day only, from midnight to midnight. Cincom will provide it to you when you call in a problem to the Cincom Support Center at 800/727-3525.

Considerations If the MANTIS customization options module (CSOPCUST) does not have any paired

transactions, a CICS transaction called MANT must be defined. When MANTIS is XCTL to by the Back Door Sign On program, if no paired transaction IDs exist, then MANTIS returns to the MANT transaction. If a MANT transaction does not exist, the Back Door Sign On program will dynamically define it.

To all customers that installed MANTIS 6101.010. The MANTIS back door sign on program name has changed from CSOXBDSO to CSOPBDSO. You should manually delete from the library program CSOXBDSO and the CICS RDO definition for program CSOXBDSO or any other name you may have used when installing 6101.010.

Troubleshooting If you misspell the MANTIS module name in your first attempt to execute the Back Door Sign On program, and the MANT transaction did not previously exist, then subsequent attempts to execute the program may fail. If this occurs, perform the following:

1. ALTER the MANT transaction using CEDA. 2. Specify the correct MANTIS module name. 3. INSTALL the transaction.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 41 Chapter: 5. Batch Dialog Facility (BDF) Install function Section: Overview of the Batch Dialog Facility

5. Batch Dialog Facility (BDF) Install function Overview of the Batch Dialog Facility

The Batch Dialog Facility (BDF) is a command-driven interface that enables you to perform the following:

Run several of the Program Design Facility (PDF) functions in batch. Upgrade your cluster in a batch environment.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 42 Chapter: 5. Batch Dialog Facility (BDF) Install function Section: How MAIWI uses the BDF Install function

How MAIWI uses the BDF Install function MAIWI automatically runs the BDF Install function to perform the following:

Modify MANTIS support file external names. Modify the default user log option. Modify CEF options. Insert or update MANTIS’s Authorization record for the currently running CPU.

Adding additional CPU-ID Authorization records to your MANTIS cluster. If you would like to add additional CPU-ID Authorization records to your MANTIS cluster, you can use the BDF Install function to perform this task as a separate batch job. If you need to repeat this task for multiple MANTIS clusters, using the BDF Install function will save time, compared to performing online entry. Refer to the section on adding additional Authorization records with the Batch Dialog Facility in MANTIS Administration for z/OS and z/VSE, P39-5305.

Create program information records on the EEPR file.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 43 Chapter: 6. Customizing MANTIS after the installation or upgrade Section: Customizing the startup, menu, and termination programs

6. Customizing MANTIS after the installation or upgrade Customizing the startup, menu, and termination programs

Entities to change in order to customize MANTIS To customize MANTIS for your installation, Cincom recommends that you change the following entities:

Startup program: MASTER:SIGN_ON. Both Program entity and screen entity. Termination program: MASTER:TERMINATE. Program entity. Menu programs:

- MASTER:FACILITY—Program entity and screen entity. - MASTER:START_FACILITY—Program entity and screen entity. - MASTER:UTILITY_SELECTION—Program entity and screen entity.

You can customize these entities now or later.

For information on customizing these entities, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

If you intend to use the MANTIS Web Temp Storage Cleaner Utility, you must upgrade your UTILITY_SELECTION screen and program to the latest version. This upgrade provides you with access to the Temp Storage Cleaner Facility, which you, as the MASTER User, use to configure the Temp Storage Cleaner Utility. For more information on the Temporary Storage Cleaner, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

Entity copies in an upgrade If you are upgrading MANTIS, you may have already modified the entities listed under Entities to change in order to customize MANTIS. An upgrade cluster does not contain replacements for each of these entities; instead, it contains another copy of each entity that has changed. Each of these copies is named as the previously listed copies, but suffixed with _64. For example, there is a MASTER:FACILITY_64 program and screen.

Using the _64 entity versions

You can use the _64 entity versions in one of two ways:

As models on which to base changes to your existing programs and screens. As replacements for your current programs and screens. To replace your current

programs and screens with the _64 versions, perform the following:

For the steps required to rename entities, see the following:

Renaming the _64 program entities as the current program entities. Renaming the _64 screen entities as the current screen entities.


Perform the steps in “Renaming the _64 program entities as the current program entities” before performing the steps in “Renaming the _64 screen entities as the current screen entities.”

Rename each of your existing entities with an _OLD extension.

Rename each of the new entities without its _64 extension.

For release 6101 and above, program MASTER:SIGN_ON_6x has been modified to support mixed case in MANTIS. If you wish to use mixed case, uncomment the statements that perform the DO of the set case low subroutine. See the program for more details.

Renaming the _64 program entities as the current program entities

Avoiding sign-on problems. MASTER:SIGN_ON or MASTER:FACILITY program errors can prevent you from signing on to MANTIS. Avoid this problem by performing the following when you update or rename either of these two programs:

1. Sign on as the MASTER User. 2. Load the program you intend to change into the Full-Screen Editor. 3. Change the loaded program as desired and replace it. 4. On another terminal, try to sign on as the MASTER User or as another user. If you

cannot, use the first terminal to restore the original, functioning version of your program, or to correct and replace the program.

To rename each old program entity with an _OLD extension and rename each new MANTIS program entity without its _64 extension, perform the following:

1. Sign on as the MASTER User. 2. Rename MASTER:SIGN_ON as MASTER:SIGN_ON_OLD.

For detailed instructions on renaming a program entity, see Renaming a program entity.

3. Rename MASTER:TERMINATE as MASTER:TERMINATE_OLD. 4. Rename MASTER:FACILITY as MASTER:FACILITY_OLD. 5. Rename MASTER:START_FACILITY as MASTER:START_FACILITY_OLD. 6. Rename MASTER:UTILITY_SELECTION as MASTER:UTILITY_SELECTION_OLD. 7. Rename MASTER:SIGN_ON as MASTER:SIGN_ON_OLD. 8. Rename MASTER:SIGN_ON_64 as MASTER:SIGN_ON. 9. Rename MASTER:TERMINATE_64 as MASTER:TERMINATE. 10. Rename MASTER:FACILITY_64 as MASTER:FACILITY. 11. Rename MASTER:START:FACILITY_64 as MASTER:START_FACILITY. 12. Rename MASTER:UTILITY_SELECTION_64 as MASTER:UTILITY_SELECTION.


Renaming the _64 screen entities as the current screen entities

Avoiding sign-on problems. MASTER:SIGN_ON or MASTER:FACILITY screen errors can prevent you from signing on to MANTIS. Avoid this problem by performing the following when you update or rename either of these two screen:

1. Sign on as the MASTER User. 2. Load the screen you intend to change into the Screen Design Facility. 3. Change the loaded screen as desired and replace it. 4. On another terminal, try to sign on as the MASTER User or as another user. If you

cannot, use the first terminal to restore the original, functioning version of your screen, or to correct and replace the screen.

To rename each old screen entity with an _OLD extension and rename each new MANTIS screen entity without its _64 extension, perform the following:

1. Sign on as the MASTER User. 2. Rename MASTER:SIGN_ON as MASTER:SIGN_ON_OLD.

For detailed instructions on renaming a screen entity, see C. Renaming a screen entity. Be aware that the procedure for renaming a screen entity is different from the procedure for renaming a program entity.

3. Rename MASTER:FACILITY as MASTER:FACILITY_OLD. 4. Rename MASTER:START_FACILITY as MASTER:START_FACILITY_OLD. 5. Rename MASTER:UTLITY_SELECTION as MASTER:UTILITY_SELECTION_OLD. 6. Rename MASTER:SIGN_ON_64 as MASTER:SIGN_ON. 7. Rename MASTER:FACILITY_64 as MASTER:FACILITY. 8. Rename MASTER:START_FACILITY_64 as MASTER:START_FACILITY. 9. Rename MASTER:UTILITY_SELECTION_64 as MASTER:UTILITY_SELECTION.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 46 Chapter: 6. Customizing MANTIS after the installation or upgrade Section: Considerations for MASTER:SIGN_ON and MASTER:TERMINATE

Considerations for MASTER:SIGN_ON and MASTER:TERMINATE If you are an HPO user, you will be using a MANTIS background task to load the Shared Pool. When using MANTIS background tasks, be aware of the following considerations for MASTER:SIGN_ON and MASTER:TERMINATE:

Starting MASTER:SIGN_ON. MASTER:SIGN_ON is passed arguments that are specified when the background task is started. To accept this data, the first line of the MASTER:SIGN_ON program must be the following: ENTRY SIGN_ON(NAME,CLEARANCE,PARAMETER)

To complete the sign-on for the background task, MASTER:SIGN_ON should then pass this data to the CONTROL:SIGN_ON program.

Testing TERMINAL=“BACK$MAN” or TERMINAL=“XMLnnnnn”. If you are using an alternate sign-on or a customized termination program, you can test to find out either of the following: - If TERMINAL=“BACK$MAN” is true—If this is true, MANTIS is running in the

background. - If TERMINAL=“XMLnnnnn” is true—(Note that “nnnnn” is the initial CICS task

number when a MANTIS Web session starts.) If this is true, MANTIS is communicating with a web browser or a server.

If either one is true, you may wish to bypass any custom code that you have introduced. This is especially important if your background task does not have access authorization to resources used in an alternate sign-on (VSAM files, for example).

Terminating background tasks. Background tasks cannot perform any terminal I/O, and should terminate by CHAINing to MASTER:TERMINATE.

CSOL file logging. The CSOL file logs the start and stop of each background, Web task, or MantisStudio task. This information accumulates until the CSOL file is deleted and redefined. Therefore, you should regularly perform an IDCAMS LISTCAT of the CSOL file to make sure it is not full. The CSOL file is usually defined as REUSE; if it is, you can use the CEMT SET command to set the file to EMPTY. Once you open the file again, all records will be deleted. The background task will fail if the CSOL log file is full.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 47 Chapter: 6. Customizing MANTIS after the installation or upgrade Section: Creating program profiles for protected libraries (HPO users only)

Creating program profiles for protected libraries (HPO users only) If you are using HPO and you wish to add Cincom-protected library programs to the Shared Program Pool, perform the following:

1. Sign on as the MASTER user. 2. On the MASTER Facility menu, select “Design a User Profile” (option 7). 3. Select “Directory of Users” (option 4).

A list of the Cincom-protected users that are currently installed on your system appears.

4. Press the CANCEL key. You return to the User Profile Design Facility menu.

5. Enter the user name for which you wish to generate EEPRs.

For example, enter CONTROL or VPF for step 5.

6. Select Create Extended Program Profiles (option 8). 7. Confirm your request to create extended program profiles.

MANTIS generates EEPRs for the user you specified. The generated EEPRs provide the program list that appears on the Shared Pool Nominate List.

8. From the program list that appears on the Shared Pool Nominate List, nominate the programs that you would like loaded into the Shared Pool.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 48 Chapter: 6. Customizing MANTIS after the installation or upgrade Section: Nominating the Shared Pool list (HPO users only)

Nominating the Shared Pool list (HPO users only)

Shared Pool Facility and the IADB file The IADB file is required for the operation of the Shared Pool Facility and must be defined to CICS. MAIWI created the CSIADB file as part of the installation process.

Shared Pool and the Statistics Facility MANTIS provides a Statistics Facility to assist the MASTER user in deciding which programs should be nominated to the Shared Pool. This facility also verifies that the Shared Pool is working as expected. The Statistics Facility is available from the MASTER user’s MANTIS Utilities menu.

Shared Pool and memory location For XA MANTIS, the Shared Pool resides in XA memory. For non-XA MANTIS, the Shared Pool can reside in either of the following:

GETMAINed non-XA storage Loaded copies of the CSOPSHRP module, below the 16 MB line.

For C$OPCUST customization options, SHRPMOD and SPSIZE operands, and more information on the C$OPSHRP macro, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 49 Chapter: 6. Customizing MANTIS after the installation or upgrade Section: Running the Split SETPRAY Utility (optional)

Running the Split SETPRAY Utility (optional)

Running the Split SETPRAY Utility (optional)

To reduce SETPRAY I/O and access contention, and to ease maintenance when multiple copies of MANTIS are in use, you can split the SETPRAY cluster into multiple physical data sets that will be accessed as one logical SETPRAY cluster.

Splitting your SETPRAY again after MANTIS reinstallation If you recombined your split SETPRAY before upgrading, you can now split your SETPRAY again.

Steps for splitting your current SETPRAY cluster To split your current SETPRAY cluster, perform the following:

For details on performing these steps, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

1. Create a SETPRAY user exit (CSOXSETP).

If you chose to use a DD name other than SETPRAY for the main MANTIS cluster, MAIWI has already included a generated CSOXSETP with that DD name unless you pointed MAIWI to your version of CSOXSETP during installation.

2. Execute the Split SETPRAY Utility (CSOPSPLT).

Elements needed in order to run the Split SETPRAY Utility The members you will need for splitting your SETPRAY cluster are the following:

Linkdeck for the Split SETPRAY Utility: Member MVLSPLIT, found in the installation MACLIB.

JCL to execute the Split SETPRAY Utility: Member MVJSPLIT, found in the installation JCLLIB.

Sample input statements: In member MNISPLIT, found in the installation MACLIB.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 50 Chapter: 7. Installing AD/Advantage Section: Preliminary considerations

7. Installing AD/Advantage Preliminary considerations

Before installing AD/Advantage, consider the following:

Completed MANTIS installation. You must complete the MANTIS installation (from tape/cartridge, FTP site, or CD) before installing AD/Advantage

EXAMPLES user. You must have the EXAMPLES user in order to install AD/Advantage. If you are upgrading MANTIS, confirm that the EXAMPLES user exists. If you need to create the EXAMPLES user, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

Needed skills. In order to complete the installation procedure, you must understand how to do the following: - Run programs—Use “Run a Program by Name” (option 1). For details, refer to

MANTIS Facilities for z/OS and z/VSE, P39-5301. - Save programs—Use the Program Design Facility. For details, refer to MANTIS

Program Design and Editing for z/OS and z/VSE, P39-5307. - Replace programs—Use the Program Design Facility. For details, refer to

MANTIS Program Design and Editing for z/OS and z/VSE, P39-5307.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 51 Chapter: 7. Installing AD/Advantage Section: AD/Advantage installation procedure

AD/Advantage installation procedure To install AD/Advantage, perform the following:

1. Run MANTIS. The sign-on screen displays.

2. Sign on as the MASTER user. The MANTIS Facility Selection Menu displays. Your MANTIS Facility Selection Menu may look similar, but not identical, to the following screen:

3. In the MASTER User Profile, increase your SLICE/SLOT parameters to at least the

values shown below:

To access the MASTER User Profile, perform the following:

On the MANTIS Facility Selection Menu, select “Design a User Profile” (option 7). In the field provided for the user name, enter MASTER. Press PF3 to “Alter an existing profile”.

- STATEMENTS PER SLOT: 3000 - SLOTS BEFORE INTERRUPT: 200

For more information on SLICE/SLOT parameters, refer to MANTIS Administration for z/OS and z/VSE, P39-5305.

4. Press ENTER to save changes to the MASTER User Profile. 5. Press the CANCEL key to terminate the User Profile Design Facility. 6. On the MANTIS Facility Selection Menu, select “Sign On as Another User” (option

13). 7. Sign on as the MASTER user.

Performing steps 6 and 7 causes the changes you made in step 3 to take effect.


8. On the MANTIS Facility Selection Menu, select “Run a Program by Name” (option 1) to run the AD/Advantage installation program: - English users—Run VPF:ADV_INSTALL_ENU. - German users—Run VPF:ADV_INSTALL_DEU. The AD/Advantage Installation screen displays as shown here:

9. In the New Special Character field, enter appropriate information. See the

following definition:

New Special Character

Description Required. Specifies the special character that begins all AD/Advantage system transactions.

Default Hash character (#)

Consideration After installation, you can change the system special character by using the #UPDCHAR transaction.

10. In the Reinstallation-Options field, enter appropriate information. See the following definition:

Reinstallation-Options

Description Optional. Specifies which entities are deleted and replaced when you upgrade AD/Advantage.

Default (blank)

Options (blank) Creates the AD/Advantage dictionary.

Y Deletes and replaces only the AD/Advantage system entities (the ADV subsystem) stored in the AD/Advantage dictionary.

N Deletes the entire AD/Advantage dictionary and replaces it with a new dictionary.

11. Perform one of the following: - Stop the installation by pressing the CANCEL key. - Continue the installation process by pressing ENTER.


Phase 1 of the installation executes, deleting some or all (depending on your selections in step 10) of the files currently stored in the AD/Advantage dictionary. The system prompts you to press ENTER to continue with Phase 2.

12. Press ENTER. Phase 2 of the installation executes.

13. Press ENTER. The MANTIS Facility Selection Menu appears.

14. On the MANTIS Facility Selection Menu, select “Design a User Profile” (option 7). 15. Enter MASTER in the User Name field. 16. Select Create Extended Program Profiles (option 8).

MANTIS creates EEPR records for the MASTER user’s newly loaded programs. 17. Repeat steps 14 through 16, but for the EXAMPLES user rather than the MASTER

user. 18. If you have HPO installed and you wish to nominate any AD/Advantage programs to

the Shared Pool, repeat steps 14 through 16, but for the VPF user rather than the MASTER user.

19. To activate AD/Advantage, perform the following: a. Rename MASTER:SIGN_ON as MASTER:SIGN_ON_OLD.


b. Rename MASTER:ADV_SIGN_ON as MASTER:SIGN_ON. 20. Before signing off this terminal, test your changes by attempting to sign on to

another terminal. If you cannot, use the first terminal to perform one of the following for any program that is causing problems: - Restore the original, functioning version. - Correct and replace the program

21. If you are upgrading MANTIS, your old MASTER:SIGN_ON program might be customized. If so, merge the changes made to your old MASTER:SIGN_ON program with the new MASTER:SIGN_ON.

22. Modify the MASTER:FACILITY and MASTER:START_FACILITY programs (the actions you take now depend on whether you have installed or will install ACCESS and will use the Software Selection Facility): - If you have installed or will install ACCESS and will use the Software Selection

Facility—Perform the following: i. In the MASTER:FACILITY program, replace the CHAIN“CONTROL:SIGN_ON”

statement with a CHAIN“MASTER:ADV_SIGN_ON” statement. ii. In the MASTER:START_FACILITY program, replace the

CHAIN“CONTROL:SIGN_ON” statement with a CHAIN“MASTER:ADV_SIGN_ON” statement.

- If you have not installed and will not install ACCESS, or will not use the Software Selection Facility—Perform the following: i. In the MASTER:FACILITY program, replace the CHAIN“CONTROL:SIGN_ON”

statement with a CHAIN“MASTER:SIGN_ON” statement. ii. In the MASTER:START_FACILITY program, replace the

CHAIN“CONTROL:SIGN_ON” statement with a CHAIN“MASTER:SIGN_ON” statement.

23. If any of the programs that you have modified and replaced, or renamed, are located in the Shared Program Pool, reload them into the Shared Program Pool in order for your changes to take effect.


MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 55 Chapter: 8. Verifying MANTIS SQL Support installation Section: Verifying that MANTIS SQL Support installation is complete

8. Verifying MANTIS SQL Support installation Verifying that MANTIS SQL Support installation is complete

Verifying installation completion for DB2 MANTIS SQL Support installation is complete for DB2 after the following occur:

MAIWI usually performs these steps automatically at installation time.

CSOPSQL2 has been successfully: - Precompiled - Assembled - Link-edited with MANTIS

DB2 Application Plan has been created Execution authority on the package has been granted to all users or PUBLIC that

access DB2.

Verifying installation completion for SUPRA Server SQL MANTIS SQL Support installation is complete for SUPRA Server SQL after MANTIS has

been successfully linked with the SUPRA Server SQL modules.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 56 Chapter: 8. Verifying MANTIS SQL Support installation Section: Verifying that MANTIS SQL Support is available for use

Verifying that MANTIS SQL Support is available for use When the composite link-edit for MANTIS is finished, MANTIS SQL Support should be available for use.

Verifying availability of MANTIS SQL Support if you have DB2 To verify that MANTIS SQL Support is available for your use, if you have DB2, run the MASTER:SQL_INSTALL_CHECK_DB2_VSE program. By listing the DB2 databases that are defined on your system, this program verifies that MANTIS SQL Support can successfully communicate with DB2. To execute this program, perform the following

1. Sign on as MASTER. 2. Make sure that the DB2 connection is active. If it is not, use the DSNC CICS

transaction to connect to DB2.

For more information on the DSNC CICS transaction, refer to the appropriate DB2 manual.

3. Execute the following program: MASTER:SQL_INSTALL_CHECK_DB2

This program lists the DB2 databases that are defined on your system, verifying that MANTIS SQL Support can successfully communicate with DB2.

What to do if you get an AEY9 abend. The DB2 connection must be active before you execute the SQL_INSTALL_CHECK program. If you receive an AEY9 abend when running the SQL_INSTALL_CHECK program under CICS, the DB2 connection may not yet be active. If you receive this abend, use the DSNC STRT CICS command to activate DB2, then rerun MASTER:SQL_INSTALL_CHECK_DB2. For more information on the DSNC STRT command, refer to the appropriate DB2 manual.

Verifying availability of MANTIS SQL Support if you have SUPRA Server SQL

To verify that MANTIS SQL Support is available for use, if you have SUPRA Server SQL, perform the following:

1. Sign on as MASTER. 2. Execute the following program:

MASTER:SQL_INSTALL_CHECK_SUPRA

CICS must be connected to SUPRA Server SQL before you execute MASTER:SQL_INSTALL_CHECK_SUPRA. If they are not connected, you will receive a connection error.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 57 Chapter: 9. Linking XREF and performing batch maintenance Section: Verifying that MANTIS SQL Support is available for use

9. Linking XREF and performing batch maintenance

In order to use the XREF™ Facility, you must create and occasionally maintain the XREF index. For details concerning XREF batch index creation and maintenance, refer to MANTIS XREF Administration for z/OS and z/VSE, P39-5312.

In order to create and/or maintain the XREF index, you must run certain batch programs that are written in COBOL or PL/1. As part of the installation process, these programs can be compiled and linked (required if you are upgrading from MANTIS 5.4.01 and optional if you are upgrading from MANTIS 5.5.01 or above). See XREF linkage.

For your convenience, this section also includes information about sample input statements in your XREF library. See Sample input statements in your XREF MACLIB.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 58 Chapter: 9. Linking XREF and performing batch maintenance Section: XREF linkage

XREF linkage

MANTIS 5.5.01 and above XREF Facilities There is no difference between the XREF Facility supplied with MANTIS 5.5.01 and above and the one supplied with 6.4.01. For this reason, you can either use your 5.5.01 or above programs with the 6.4.01 XREF Facility or compile and link the 6.4.01 source members.

Programs required in order to run the XREF batch jobs

Source programs

The programs required in order to run the XREF batch jobs are delivered in source form and are located on your XREF source library. You must compile and link one of the following sets of source programs:

COBOL PL/1

XREFC1 XREFP1

XREFC2 XREFP2

XREFC3 XREFP3

JCL members that will compile the XREF source programs

You can use the following JCL members from the MANTIS JCLLIB to compile the XREF 6.4.01 source programs:

MVJCOBL. Sample COBOL compile JCL. MVJPL1L. Sample PL/1 compile JCL.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 59 Chapter: 9. Linking XREF and performing batch maintenance Section: Sample input statements in your XREF MACLIB

Sample input statements in your XREF MACLIB

Sample input statements

Sample input statements for systems without DL/I

The following sample input statements are in your XREF MACLIB. They are all input for jobs within XREFJOB, and are for systems without DL/I installed:

XRNONE. Input for the PRINT job. XREFMOD. Input for the XREF job. XREFMODI. Input for the XREF job.

Sample input statements for systems with DL/I

The following sample input statements are located in your XREF MACLIB. They are all input for the XREF job within XREFJOB, and are for systems with DL/I installed:

XRALLDLI XRALLDLM XRSELDLI XRSELDLM

XREFJOB information

Location for XREFJOB sample JCL

Sample JCL to execute XREFJOB is located in your XREF JCLLIB.

Task to perform before running XREFJOB

Perform one of the following tasks before you run XREFJOB:

Make sure that MANTIS is not running in CICS. Close the XREFIND file to CICS.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 60 Chapter: 10. Installing SSF SL2033 Section: Sample input statements in your XREF MACLIB

10. Installing SSF SL2033 SSF SL2033 runs on MANTIS in the SUPRA PDM environment.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 61 Chapter: 10. Installing SSF SL2033 Section: Installation procedure

Installation procedure

If you are upgrading or cloning a current MANTIS installation, and you already have SSF SL2033 installed, you do not need to upgrade it.

To install SSF SL2033, perform the following:

1. Back up your MANTIS cluster. 2. REPRO the SSF cluster, located on the MANTIS installation tape/cartridge, onto

your MANTIS cluster.

For the file number and name of the file on the installation tape/cartridge, refer to Installing MANTIS 6.4.01 and AD/Advantage 6.4.01 for z/OS, M39-1040 (available only in hardcopy form).

3. Sign on to MANTIS as the MASTER user. 4. On the MANTIS Facility Selection Menu, select “Design a User Profile” (option 7). 5. Select Create Extended Program Profiles (option 8).

MANTIS creates EEPR for the MASTER user’s newly loaded programs. 6. If you have installed HPO and you wish to nominate any SSF programs to the Shared

Pool, perform the following: a. Enter CSI-DBA in the User Name field. b. Select Create Extended Program Profiles (option 8). MANTIS creates EEPR records for the CSI-DBA user’s newly loaded programs.

7. Perform one of the following: - If you are installing SSF SL2033 after a new MANTIS installation, and you will

not be using the Software Selection Facility (SSF) menu: Continue using your current MASTER:SIGN_ON program, without changes.

- If you are installing SSF SL2033 after a MANTIS upgrade, and you will not be using the Software Selection Facility (SSF) menu: Continue using your current MASTER:SIGN_ON program, without changes.

- If you will be using the Software Selection Facility (SSF) menu: Perform the following: i. Rename MASTER:SIGN_ON as MASTER:SIGN_ON_OLD2.


ii. Rename MASTER:FACILITY as MASTER:FACILITY_OLD2. iii. Rename MASTER:TERMINATE as MASTER:TERMINATE_OLD2. iv. Rename MASTER:SIGN_ON_ACCESS2033 as MASTER:SIGN_ON. v. Rename MASTER:FACILITY_ACCESS2033 as MASTER:FACILITY. vi. Rename MASTER:TERMINATE_ACCESS2033 as MASTER:TERMINATE.

- If you are installing SSF SL2033 after a MANTIS upgrade, and you customized your original MASTER:SIGN_ON program, merge your changes with the MASTER:SIGN_ON that SSF installed (and that you renamed in step D).

8. If you are installing SSF SL2033 after installing MANTIS with AD/Advantage, perform the following: a. In the MASTER:FACILITY program, change the CHAIN “CONTROL:SIGN_ON”

statement to CHAIN “MASTER:ADV_SIGN_ON”. b. In the MASTER:START_FACILITY program, change the

CHAIN “CONTROL:SIGN_ON” statement to CHAIN “MASTER:ADV_SIGN_ON”.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 62 Chapter: 10. Installing SSF SL2033 Section: Installation procedure

c. Apply the MANTIS code patch that has fix ID 960529.

Applying patch 960529 enables access to AD/Advantage.

9. Before signing off the current terminal, test your changes by attempting to sign on to another terminal. If you cannot, use the terminal to which you are already signed on to perform one of the following for any program that is causing problems: - Restore the original, functioning version. - Correct and replace the program.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 63 Chapter: 11. Installing zMantisIDE for use with MANTIS Web Section: Installation procedure

11. Installing zMantisIDE for use with MANTIS Web

If you intend to use the MANTIS Web component to access the brower-based MANTIS IDE, use MANTIS Studio to install the zMantisIDE web application on your Java application server system. The MANTIS Studio Help’s Preparing the workbench section describes how to do this. To access this Help section, perform the following:

1. From the MANTIS Studio main menu, select Help > Help Contents. The Help window opens.

2. In the left-hand pane, Contents pane, expand the MANTIS Development User Guide/Getting Started with MANTIS Studio/3. Preparing the Workbench node.

3. Follow the instructions in the following Help topics: - Step 1: Enabling MANTIS scripts - Step 2: Verifying essential MANTIS Studio preferences - Step 3: Starting the MANTIS Listener - Step 4: Checking for the MANTIS perspective - Step 5: Importing and running the MANTIS-supplied web application

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 64 Chapter: 12. CICS Web Interface Section: Installation procedure

12. CICS Web Interface On the z/OS platform, the program that fulfills the “MANTIS Listener” role in MANTIS Web is the CICS Web Interface supplied by IBM®. For more information on the MANTIS Listener role in MANTIS Web, refer to MANTIS Web Concepts Guide, P39-5201.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 65 Chapter: 12. CICS Web Interface Section: Purpose of the CICS Web Interface

Purpose of the CICS Web Interface The CICS Web Interface starts a web-aware MANTIS Server and acts as its information conduit. More specifically, it accepts a SOAP request from a MantisWeb web application or from a web service requestor. No matter whether the message was from a new client or part of an ongoing conversation, the CICS Web Interface then starts a new web-aware MANTIS Server, which processes the message and immediately terminates. The CICS Web Interface also receives messages back from the web-aware MANTIS Server that it has started and passes these messages on to a MantisWeb web application or the appropriate web service requestor.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 66 Chapter: 12. CICS Web Interface Section: Enabling the CICS Web Interface

Enabling the CICS Web Interface Use the default CICS Web Interface that is supplied by IBM, as part of CICS.

Requirements for enabling the CICS Web Interface To enable the CICS Web Interface, you must make sure that the following items are properly configured:

DFHRPL or LPA settings. Set the TCP/IP dataset that will be used by the CICS Web Interface by entering both of the following dataset names either into DFHRPL, which is located in the CICS startup JCL, or LPA: - TCPIP.SEZATCP - TCPIP.SEZALOAD

The preceding two dataset names are the default values supplied by IBM. If your naming convention differs, adjust these names as necessary.

TCPIP parameter in SIT. In SIT, set the TCPIP parameter to YES. GRPLIST parameter in SIT. Make sure that the RDO group DFHWEB is included in

one of the lists specified in the CICS startup GRPLIST list. If this group is successfully included, you should see the following message when CICS comes up: DFHWB1008 xxxxxxx CICS Web environment initialization is complete.

In the preceding message, xxxxxxx is the CICS ApplId name.

CEMT items. In CEMT, make sure of the following: - TCPIPSERVICES is open on the port that you selected during MANTIS

installation.

Note the port you have selected. You will need to enter this port number as part of the MantisServerURL parameter’s value in the webapp.properties file contained in each of your web applications. For more information on the webapp.properties file, refer to MANTIS Web Web App Guide, P39-5203.

Port limitations. A port can be open in only one CICS at a time.

Multiple ports for a single CICS. You can define more than one port for a single CICS. This can be useful if you implement multiple web applications.

- The following three programs exist: o DFHWBA o DFHWBADX o DFHWBXN

- Transaction CWXN points to program DFHWBXN.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 67 Chapter: 12. CICS Web Interface Section: Checking the availability of the CICS Web Interface

Checking the availability of the CICS Web Interface You can check the availability of the CICS Web Interface by sending a message to the web-aware MANTIS Server and checking the response.

Steps To check the availability of the CICS Web Interface, enter the following URL into a web browser’s Address field and press ENTER (this URL is not case-sensitive):

http://web-aware MANTIS Server:host-port-number/cics/cwba/dfh$wb1a

In the preceding URL, substitute the IP address or DNS host name of your mainframe for web-aware MANTIS Server, and for host-port-number, substitute the port number that you defined, during the MANTIS installation process, for your web-aware MANTIS Server to use.

If the CICS Web Interface is available, the z/OS web-aware MANTIS Server sends the following response:

DFH$WB1A on system xxxxxxxx successfully invoked through the CICS Web Interface.

In the preceding response, xxxxxxx is the CICS ApplId name.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 68 Chapter: 12. CICS Web Interface Section: Checking communication between the MantisIDE web application and the web-aware MANTIS Server

Checking communication between the MantisIDE web application and the web-aware MANTIS Server

The MantisIDE web application is a specialized version of the MantisWeb web application; MantisIDE has extra files in it that provide the infrastructure necessary to display the MANTIS IDE (Integrated Development Environment). You can verify that MANTIS Web is installed properly by checking the communication between the MantisIDE web application and the web-aware MANTIS Server. To do so, perform the following:

1. Make sure that MantisIDE web application has been deployed on your web/application server.

2. In your MantisIDE web application’s folder structure, update your webapp.properties file (located in the webApplicationName\WEB-INF folder) by setting the MantisServerURL parameter to the following value: MantisServerURL=http://web-aware MANTIS Server:host-port-number/MANTIS/tttt/mmmmmmmm

In the preceding URL, substitute the IP address or DNS host name of your mainframe for web-aware MANTIS Server, and for host-port-number, substitute the TCP/IP Service port number that you defined, during the MANTIS installation process, for your web-aware MANTIS Server to use. For tttt, substitute the MANTIS Web alias transID that you defined, during the MANTIS installation process, for your web-aware MANTIS Server to use. For mmmmmmmm, substitute the MANTIS program name that you defined, during the MANTIS installation process, for your web-aware MANTIS Server to use.

webapp.properties information. For further information on the webapp.properties file, refer to MANTIS Web Web App Guide, P39-5203.

3. Restart the MantisIDE web application so that it accepts the change you made to the MantisServerURL parameter of the webapp.properties file.

4. Enter the following URL into a web browser’s Address field and press ENTER (this URL is case-sensitive): http://Mantis Web Server Machine:web-server-port-number/MantisIDE/Start

In the preceding URL, substitute the name of your web/application server machine for Mantis Web Server Machine, and for web-server-port-number, substitute the port on your web/application server that is open for connections.

If the communication between the MantisIDE web application and the web-aware MANTIS Server is functioning properly, your web browser displays the MANTIS Sign-On page, and you should now be able to log on.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 69 Appendix: A. MANTIS enhancements and changes and new or changed MANTIS messages Section: Reference

A. MANTIS enhancements and changes and new or changed MANTIS messages Reference

For a listing of MANTIS enhancements and changes and a listing of new and changed MANTIS messages, refer to MANTIS Release Notes for z/OS and z/VSE, P39-5315.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 70 Appendix: B. Renaming a program entity Section: Steps for renaming a program entity

B. Renaming a program entity Steps for renaming a program entity

This appendix provides detailed instructions for renaming a program entity. To rename a program entity, perform the following:

1. Sign on as the MASTER User. 2. On the MANTIS Facility Selection Menu, select “Design a Program” (option 3). 3. Select Rename (option 6). 4. In the “From name” field, enter the initial name of the desired program. For

example, enter START_FACILITY. 5. In the “To name” field, enter the new name for the program. For example, enter

START_FACILITY_OLD. 6. Press PF6.

MANTIS renames the entity.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 71 Appendix: C. Renaming a screen entity Section: Steps for renaming a screen entity

C. Renaming a screen entity Steps for renaming a screen entity

This appendix provides detailed instructions on renaming a screen entity. To rename a screen entity, perform the following:

1. Sign on as the MASTER User. 2. On the MANTIS Facility Selection Menu, select “Design a Screen” (option 4). 3. Select Library Functions (option 7). 4. Enter the name of your existing screen. For example, enter START_FACILITY. 5. Press PF3.

MANTIS fetches the screen. 6. Modify the screen name. For example, you might modify START_FACILITY so that it

becomes START_FACILITY_OLD. 7. Press PF1.

MANTIS saves the screen under a new name.

If you would like to change another screen name, return to step 4.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 72 Appendix: D. MANTIS Unbind and Bind Utilities Section: Introduction: Incompatibility between pre-5.6.01 MANTIS and 6.4.01

D. MANTIS Unbind and Bind Utilities Introduction: Incompatibility between pre-5.6.01 MANTIS and 6.4.01

Because Cincom has made major architectural changes to MANTIS in order to support a larger program Data Work Area (DWA), the format of programs that were HPO-bound and/or SQL-bound under MANTIS prior to 5.6.01 is incompatible with MANTIS 6.4.01. As a result, under MANTIS 6.4.01, you cannot access programs that were HPO-Bound and/or SQL-Bound under MANTIS prior to 5.6.01. Attempting to do so causes a NUCBOR (Bound in Old Release) error.

To resolve this problem, before you upgrade to MANTIS 6.4.01, all of the HPO-bound and/or SQL-bound programs that are located on your pre-5.6.01 MANTIS system must be unbound. After you have successfully upgraded the MANTIS system to MANTIS 6.4.01, all programs that were unbound can be bound again.

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 73 Appendix: D. MANTIS Unbind and Bind Utilities Section: Unbind and Bind Utilities

Unbind and Bind Utilities The unbinding of HPO- and SQL-bound programs on your pre-5.6.01 MANTIS system is always performed automatically. Cincom recommends that, after the cluster is upgraded, you have the unbound programs automatically re-bound. To take care of the unbinding and rebinding, Cincom created the following two utilities:

MANTIS Unbind Utility. This utility performs the automatic unbinding prior to MAIWI’s upgrade of the MANTIS cluster.

MANTIS Bind Utility. This utility rebinds the unbound programs after MAIWI has successfully upgraded the MANTIS cluster.

These two utilities are designed to be run in batch. An external file, BINDLOG, logs the automatic unbinding and rebinding performed by these utilities.

Procedure for binding and unbinding When you initiate the procedure for upgrading a pre-5.6.01 MANTIS cluster to 6.4.01, the following occurs:

1. The MANTIS Installation Wizard (MAIWI) downloads the Unbind Utility and supporting entities to the pre-5.6.01 MANTIS cluster.

2. MAIWI executes the Unbind Utility. The Unbind Utility HPO- and SQL-unbinds all user programs that are HPO- and/or SQL-bound.

3. MAIWI upgrades the pre-5.6.01 cluster to 6.4.01. 4. MAIWI prompts you to specify whether it will execute the Bind Utility on the

upgraded MANTIS 6.4.01 cluster. You can specify either of the following: - Run the Bind Utility—If you select this option, the Bind Utility HPO- and SQL-

binds the programs that the Unbind Utility unbound. - Do not run the Bind Utility—If you select this option, you can manually run the

Bind Utility at a later time, after the installation process is complete.

If you specify NO to either option, you can manually run the Bind Utility at a later time, after the installation process is complete.

Prerequisite for using Unbind and Bind Utilities Before you can use the Unbind and Bind Utilities, a printer definition named BSTAT must be defined in the batch job. For an example, see the Unbind/Bind Utility sample JCL, which is called MVJBUP.JCL and is located in the MANTIS install library.

Unbind Utility The Unbind Utility searches all users for, and unbinds, all HPO- and/or SQL-bound programs. It logs every action to the BINDLOG file; after the MANTIS cluster has been successfully upgraded, this file serves as input to the Bind Utility.

This utility must be run by the MASTER user, and it may be run either in batch or online. To run it using “Run a Program by Name”, enter the following:

CONTROL:UTIL_UPGRADE_UNBIND

Unbinding statuses

You receive different status information for HPO-unbound and SQL-unbound programs:


HPO-unbound programs. You receive the following status information for each program that is HPO-unbound:

SQL-unbound programs. You receive the following status information for each

program that is SQL-unbound:

SQLBind Utility The SQLBind Utility reads the BINDLOG file to find out which programs need to be HPO-bound and SQL-bound; this utility then performs each necessary binding, updating the BINDLOG file after each one. This utility must be run by the MASTER user, and it may be run either in batch or online. It can only be run after the MANTIS cluster has been upgraded to MANTIS 6.4.01. To run it using “Run a Program by Name”, enter the following:

CONTROL:UTIL_UPGRADE_BIND


In order to run, this utility requires the OPTIONS= parameter.

OPTIONS= parameter

Description Optional. Determines how the Bind Utility behaves.

Default LIST

Options HPO Causes the Bind Utility to HPO-bind all programs that were HPO-unbound by the Unbind Utility.

SQL Causes the Bind Utility to SQL-Bind all programs that were SQL-unbound by the Unbind Utility.

BOTH Causes the Bind Utility to HPO- and/or SQL-bind all programs that were HPO- and/or SQL-unbound by the Unbind Utility.

LIST Produces a printout of the BINDLOG file. For more information, see BINDLOG List.

Cincom supplies another utility program, UTIL_UPGRADE_BINDLIST, to list the contents of the BINDLOG file.

Binding statuses

You receive different status information for HPO-bound and SQL-bound programs:

HPO-bound programs. You receive the following status information for each program that is HPO-bound:

SQL-bound programs. You receive the following status information for each

program that is SQL-bound:


BINDLOG file The BINDLOG file is an external VSAM file that is located on the CONTROL user. The Unbind and Bind Utilities both use it as a log file, and the Bind Utility also uses it as an input file.

File View Access screen

This file has the following File View Access screen:

File View Layout Definition of BINDLOG

Screen shot of the File View Layout Definition screen. This file has the following File View Layout Definition:


Fields on the File View Layout Definition screen. The screen contains the following fields:

BL_USERNAME

Description Contains the name of the user on which the program resides.

BL_PROGNAME

Description Contains the program’s name.

BL_USERPASS

Description Contains the user’s password

BL_PROGPASS

Description Contains the program’s password

BL_HPOUNBIND

Description Indicates the HPO-unbound status of the program.

Options Y The Unbind Utility successfully HPO-unbound the program.

N The Unbind Utility attempted to HPO-unbind the program, but there was an error.

Blank The Unbind Utility did not attempt to HPO-unbind the program.

Consideration This field is represented by “HU” on the BINDLOG List report.

BL_HPOBIND

Description Indicates the HPO-bound status of the program.

Options Y The Bind Utility successfully HPO-bound this program.

N The Bind Utility attempted to HPO-bind the program, but there was an error.

Blank The Bind Utility did not attempt to HPO-bind the program. Because the program was not originally HPO-bound, there was no need to rebind it.

Consideration This field is represented by “HB” on the BINDLOG List report.

BL_SQLUNBIND

Description Indicates the SQL-unbound status of the program.


Options Y The Unbind Utility successfully SQL-unbound the program.

N The Unbind Utility attempted to SQL-unbind the program, but there was an error.

Blank The Unbind Utility did not attempt to SQL-unbind the program.

Consideration This field is represented by “SU” on the BINDLOG List report.

BL_SQLBIND

Description Indicates the SQL-bound status of the program.

Options Y The Bind Utility successfully SQL-bound this program.

N The Bind Utility attempted to SQL-bind the program, but there was an error.

Blank The Bind Utility did not attempt to SQL-bind the program. Because the program was not originally SQL-bound, there was no need to rebind it.

Consideration This field is represented by “SB” on the BINDLOG List report.

BL_SQLGENER

Description Indicates whether a program’s package was bound using SQLGener. This field is not used.

Consideration This field is represented by “SG” on the BINDLOG List report.

BL_SQL_MODULE

Description Contains the name of the DB2 Support Module that is used for SQL binding.

BL_SQL_USERNAME

Description Contains the SQL user name that is used for DB/2 for z/VSE SQL binding.

BL_SQL_PASSWORD

Description Contains the SQL password that is used for DB/2 for z/VSE SQL binding.

BL_FUTURE_FLAG1

Description Reserved for future use.

BL_FUTURE_FLAG2


BL_FUTURE_FLAG3


BL_FUTURE


BINDLOG List

Introduction. When you run the Bind Utility with the LIST option, it creates a printout of the BINDLOG file. For more information on options, see OPTIONS= parameter.

Sample printout for the BINDLOG List. Consider the following sample printout (if you are viewing a PDF, zoom in to see it more clearly):


Fields on the sample printout for the BINDLOG List. The printout contains the following fields:

HU

Description The code in this field indicates the HPO-unbind status of the program.

Options Y The Unbind Utility successfully HPO-unbound the program.

N The Unbind Utility attempted to HPO-unbind the program, but there was an error.

Blank The Unbind Utility did not attempt to HPO-unbind the program.

Consideration This field is represented by “BL_HPOUNBIND” on the File View Layout Definition screen.

HB

Description The code in this field indicates the HPO-bind status of the program.

Options Y The Bind Utility successfully HPO-bound this program.

N The Bind Utility attempted to HPO-bind the program, but there was an error.

Blank The Bind Utility did not attempt to HPO-bind the program. Because the program was not originally HPO-bound, there was no need to re-bind it.

Consideration This field is represented by “BL_HPOBIND” on the File View Layout Definition screen.

SU

Description The code in this field indicates the SQL-unbind status of the program.

Options Y The Unbind Utility successfully SQL-unbound the program.

N The Unbind Utility attempted to SQL-unbind the program, but there was an error.

Blank The Unbind Utility did not attempt to SQL-unbind the program.

Consideration This field is represented by “BL_SQLUNBIND” on the File View Layout Definition screen.

SB

Description The code in this field indicates the SQL-bind status of the program.

Options Y The Bind Utility successfully SQL-bound this program.

N The Bind Utility attempted to SQL-bind the program, but there was an error.

Blank The Bind Utility did not attempt to SQL-bind the program. Because the program was not originally SQL-bound, there was no need to re-bind it.

Consideration This field is represented by “BL_SQLBIND” on the File View Layout Definition screen.

SG


Description The code in this field indicates whether a program’s package was bound using SQLGener. This field is not used.

Consideration This field is represented by “BL_SQLGENER” on the File View Layout Definition screen.

Sample files for the BINDLOG file

Cincom provides the following sample files:

MNI0BLGD. VSAM file. Sample definition for the HPO/SQL BINDLOG file (MACLIB). MCIRDOB. RDO file. Sample definition for the HPO/SQL BINDLOG file (CICSTBLS). MVJBUP. JCL for the Bind Utility (JCLLIB). MVJBUL. JCL for generating a list report from the BINDLOG file (JCLLIB).

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 81 Index

Index A

Action Selection Menu in MAIWI (MVXPAMS) 26

AD/Advantage installing installation procedure 51 preliminary considerations 50

administration user supplied name and password 38

B

Back Door Sign On program consideration for MANT CICS

transaction 40 description 39 introduction 39 password-du-jour 40 syntax 39 troubleshooting 40

Batch Dialog Facility. t See BDF 41

BDF how MANTIS uses the BDF Install

function 42 overview 41

Bind and Unbind Utilities description 73 incompatibility in bound files 72

bound program incompatibilities between releases prior to 5.6.01 and 6.1.01 12

C

CICS making MANTIS definitions

available to 37 usage of this term implies both

CICS and Transaction Server 8 CICS Web Interface

checking communication between MantisIDE and the web-aware MANTIS Server 68

compatibility issues between MANTIS 6.0.01 and

6.1.01 program name displacement in the TWA and prior releases 18

between MANTIS 6.0.01 or higher program with breakpoints and previous MANTIS release 14

bound program incompatibilities between releases prior to 5.6.01 and 6.1.01 12

internal architecture of the transfer file has changed since 5.4.01 9

customizing MANTIS _61 entity copies in an upgrade

43 considerations for

MASTERSIGN_ON and MASTERTERMINATE 46

entities to change 43

D

DB2 support verifying MANTIS SQL support

availability for 56 development user supplied name

and password 38

E

entities programs renaming 70 screens renaming 71

EXAMPLES the supplied development user 38

H

HPO users creating program profiles for

protected libraries 47 nominating the Shared Pool list

48

I

installing AD/Advantage 50 MANTIS 19 SSF SL2033 61

internal architecture of the transfer file has changed since 5.4.01 9

J

JCL jobs generated by MAIWI 20

M

MAIWI Action Selection Menu

(MVXPAMS) 26 introduction 19 JCL jobs generated by 20 MANTIS modules remaining after

installation is complete 21 reference information 26 using 23

MANTIS Server Installation, Startup, and Configuration for z/OS®, P39-5118 82 Index

MANTIS definitions making available to

currently running CICS 37 Installation Wizard.

t 19 modules remaining after

installation is complete 21 SQL support verifying availability

of 56 MASTER the supplied system

administration user 38 MASTERSIGN_ON skipping with the

Back Door Sign On program 39

N

nominating the Shared Pool list 48

P

password-du-jour for Back Door Sign On program 40

program entity renaming 70 profiles creating for protected

libraries 47 protected libraries creating

program profiles for 47

R

renaming _60 screen entities as the

current screen entities in an upgrade 45

_61 program entities as the current program entities in an upgrade 44

program entity 70 screen entity 71

S

screen entity renaming 71 SETPRAY splitting 49 Shared Pool list nominating 48 Split SETPRAY Utilty running 49 SQL support verifying availability

of 56 SUPRA Server SQL

verifying MANTIS SQL support availability for 56

verifying MANTIS SQL Support installation completion for 55

system administration user supplied name and password 38

T

Transaction Server implied along with CICS by usage of CICS 8

U

Unbind and Bind Utilities description 73 incompatibility in bound files 72

users and passwords supplied development user 38 system administration user 38

X

XREF linkage 58 sample input statements for

systems with DL/I 59 sample input statements for

systems without DL/I 59 XREFJOB 59

Documents

MANTIS Server Installation, Startup, and Configuration for