Magic Software
AppBuilder
Version 3.4
Planning and Installing AppBuilder for the
Mainframe
Corporate Headquarters:
Magic Software Enterprises
5 Haplada Street,
Or Yehuda 60218, Israel
Tel: +972 3 5389213
Fax: +972 3 5389333
E-mail: AppBuilderSupport@MagicSoftware.com
Support Site: http://support.appbuilder.com
© 1992-2019 AppBuilder Solutions
All rights reserved.
Printed in the United States of America.
AppBuilder is a trademark of AppBuilder
Solutions.
All other product and company names mentioned
herein are for identification purposes only and are
the property of, and may be trademarks of, their
respective owners.
Portions of this product may be covered by U.S.
Patent Numbers 5,295,222 and 5,495,610 and
various other non-U.S. patents.
The software supplied with this document is the
property of AppBuilder Solutions and is furnished
under a license agreement. Neither the software
nor this document may be copied or transferred
by any means, electronic or mechanical, except
as provided in the licensing agreement.
AppBuilder Solutions has made every effort to
ensure that the information contained in this
document is accurate; however, there are no
representations or warranties regarding this
information, including warranties of
merchantability or fitness for a particular purpose.
AppBuilder Solutions assumes no responsibility
for errors or omissions that may occur in this
document. The information in this document is
subject to change without prior notice and does
not represent a commitment by AppBuilder
Solutions or its representatives.
Table of Contents
1 Planning and Installing AppBuilder for the Mainframe
2 Planning
2.1
Installation Overview
2.2
Finding the Latest Information
3 Preinstallation requirements and application maintenance
3.1
Understanding the Installed Environment
3.2
Performance Tuning. Suggestions for tuning AppBuilder
3.3
Execution Environment
4 Installation Requirements
4.1
Hardware and DASD Requirements
4.2
Supported Third-party Products
5 Host Installation Workbench
5.1
Using the Host Installation Workbench
5.2
Installation Job Processing
5.3
Backing Out a Release
5.4
Installation Notes
5.5
Installing the Host Installation Workbench
6 Installing Enterprise Repository
6.1
Prerequisites
6.2
Installation Notes for the Enterprise Repository
6.3
Installing the AppBuilder Enterprise Repository
6.4
Option 2 - Repository Functions
6.5
Postinstallation Notes
6.6
Installing MVS Migration Server and Enterprise Preparation Server
6.7
Installation Verification Using TIP
6.8
Invoking an Exit
7 Installing Batch Preparation Workbench
7.1
Prerequisites Installing Batch Preparation Workbench
7.2
Installation Notes Installing Batch Preparation Workbench
7.3
Installing the Batch Preparation Workbench Software
7.4
Option 1 - System Functions Installing Batch Preparation Workbench
7.5
Option 2 - Repository Functions Installing Batch Preparation Workbench
7.6
Postinstallation Notes Installing Batch Preparation Workbench
8 Installng Report Writer Preparation
8.1
Installation Notes of Installng Report Writer Preparation
8.2
Installing Report Writer Preparation
8.3
Postinstallation Notes of Installng Report Writer Preparation
Planning and Installing AppBuilder for the Mainframe
4
5
6
14
18
19
26
31
35
36
38
39
40
44
45
46
48
49
50
51
52
73
94
97
102
104
106
107
108
109
110
114
119
121
122
123
135
page 2 of 284
9 Installing CICS Online Prepration Workbench and Enterprise Server
9.1
Installation Notes of Installing CICS Online Prepration Workbench and Enterprise Server
9.2
Post-installation Notes: Installing CICS Online Prepration Workbench & Enterprise Server
9.3
Installing TCP IP Listener for IBM CICS
9.3.1
Meeting Software Requirements
9.3.2
Performing Post-Installation Steps
9.3.3
Usage Notes
9.3.4
DNAINI Settings
9.4
Configuring AppBuilder for a Multi-CICS Region Environment
9.4.1
AppBuilder Repository CICS Load Libraries
9.4.2
AppBuilder CICS VSAM Files
9.4.3
AppBuilder/CICS Transient Data Queues
9.4.4
AppBuilder/CICS Transactions
9.4.5
AppBuilder/CICS Programs
9.4.6
AppBuilder/CICS Terminals
Introduction to CICS EXCI Resource Definition
9.5
9.5.1
CICS EXCI Resource Definition
10 Installing IMS Online Preparation Workbench and Enterprise Server
10.1 Prerequisites of Installing IMS Online Preparation Workbench and Enterprise Server
10.2 Installation Notes of Installing IMS Online Preparation Workbench and Enterprise Server
10.3 Post-installation Notes: Installing IMS Online Preparation Workbench & Enterprise Server
11 Appendix A. AppBuilder variables
12 Appendix B. CICS table definitions
13 Appendix C. VTAM definitions
14 Appendix D. HPSCGAP, HPICGAP, HPEUCGP, and sample batch JCL
15 Appendix E. Hardware and software checklists
16 Appendix F. Host installation workbench customization worksheets
17 Appendix G. Enterprise repository customization worksheets
18 Appendix H. Batch preparation workbench customization worksheets
19 Appendix I. CICS online preparation workbench and enterprise server customization worksheets
20 Appendix J. IMS online preparation workbench and enterprise server customization worksheets
Planning and Installing AppBuilder for the Mainframe
page 3 of 284
136
137
158
159
160
161
165
166
174
175
176
177
178
179
180
181
182
185
186
187
207
215
216
237
240
256
259
261
276
277
282
Planning and Installing AppBuilder for the Mainframe
This guide provides details on Planning and Installing AppBuilder for the Mainframe.
Planning and Installing AppBuilder for the Mainframe
page 4 of 284
Planning
The first step in planning a transition to the AppBuilder environment is to develop an AppBuilder implementation plan.
AppBuilder Solutions can work with you to help develop your implementation plan.
Planning and Installing AppBuilder for the Mainframe
page 5 of 284
Installation Overview
A standard or “base” AppBuilder installation consists of a single host repository with one or two versions, a limited
number of development work-stations (two or three) and initial verification of the environment using the Test
Installation Process (TIP) application. For all installations a minimum notice period of two weeks should be allowed
in order to complete pre-install activities.
Prior to beginning the installation, a planning process is necessary to ensure that your environment is prepared to
receive the AppBuilder software. This activity is based upon information provided in this manual and may include a
one-day planning meeting at your site — although the entire process can be completed via phone and/or email.
Installation of optional products naturally increases the installation period. For example, an optional product, such as
Report Writer, typically requires an additional half-day to a day to install and verify.
The success of an installation is dictated largely by the quality of preparation; certainly the time scales indicated
below assume a “clean” and “ready” environment at your site. Failure to perform comprehensive installation planning
results in significant delays and costs both to AppBuilder and you.
AppBuilder mainframe products can be installed by customers, and experienced customers often perform their own
installations, with remote support. However, AppBuilder does provide installation services for newly purchased host
products and most organizations utilize an AppBuilder installer. In essence the installation should be deemed to
have started once the planning begins and AppBuilder installers begin discussions with the account team. If
environmental issues are found then these should be resolved prior to the AppBuilder installer traveling to the client
location.
It should also be noted that the installation planning phase provides an opportunity for client systems personnel to
become familiar with the AppBuilder installation process and requirements and thus avoid any unwelcome “first day
shocks.”
As previously indicated, initial installation verification is carried out by the AppBuilder installer using the TIP test
application. This application ensures that each of the elements constituting the “base” AppBuilder products are
correctly installed and integrated and that primary development and execution functions are operable.
In addition, it is recommended that further comprehensive verification be conducted to ensure that all lower level
functions required for subsequent training and development activities are operable. This can be achieved using
scripts prepared by AppBuilder Consulting, which thoroughly exercise the tools by simulating development activities.
Additional verification work is often undertaken during the final days of the installation, while the AppBuilder installer
remains on site to address any problems encountered. AppBuilder Consulting resources have historically engaged in
this activity as, on occasion, have client personnel.
Installation Components
The AppBuilder installation can be broken down into a number of logical parts as follows (durations are estimates
based on experience and assume complete preparation).
Table 1-1 Estimated duration of installation
Base Installation
Systems Software
Enterprise Repository
Optional Products
1 Day
1 to 2 Days
CICS
Planning and Installing AppBuilder for the Mainframe
1/2 Day
page 6 of 284
Mainframe Batch Preparation
1/2 Day
Batch Report Writer
1/2 Day
IMS
1/2 Day
Installation Verification
3 to 5 Days
Architecture Evaluation
AppBuilder allows you to produce and maintain generated applications that can be deployed across a variety of
operating systems, transaction processors and application servers depending on business and technical
requirements. Careful planning, training, and AppBuilder support can combine to help your development organization
fully utilize AppBuilder’s features.
The first requirement is to ensure that your strategic information needs are congruent with your hardware and
systems software architecture. To meet this requirement you must consider:
Your organization’s needs
The hardware and system software combination required to satisfy them
The current architecture and how best to make the transition (if one is required)
Develop a plan for your systems
Determine the technical scope of the new architecture, including hardware and software platforms,
flexibility, and so forth
Develop a hardware configuration and an environment for each platform
Determine the software environment and development languages for each platform
Decide on a database management system (DBMS)
Determine the data communications strategy
Determine the development hardware and software environment
Determine the production hardware and software environment
Establish performance goals
Define security requirements
Analyze your systems: reuse, buy, or build?
Determine which portions of your existing hardware and information systems can be reused and which need to be
replaced.
Described in Chapter 4, “Installation Requirements” are tables of hardware and software requirements. Checklists to
assist your inventory of host hardware and software can be found in Appendix C, “AppBuilder Host Development
Workbench hardware and software checklists.” We recommend that you complete these checklists as part of your
planning document. You should perform similar inventories of systems, if any, and of workstation hardware and
software. Your AppBuilder account executive will gladly assist you in completing these checklists.
Objective: Inventory of hardware and software.
Manage the transition to your AppBuilder-built systems
To implement the solutions to your organization’s strategic information requirements, you need to plan for
constructing, managing, and maintaining your systems.
Objective: Develop a plan to construct, manage, and maintain your systems.
Project Infrastructure
Planning and Installing AppBuilder for the Mainframe
page 7 of 284
Based on your implementation priorities and conversion/bridgeback requirements, develop an overall implementation
plan. This plan should include:
Phased implementation schedule and objectives
Staffing requirements
Hardware, software, and communications requirements for development and execution
workstations
External and internal support requirements
Objective: Phased implementation plan that outlines schedules, objectives, staffing, and resource requirements.
Organization, staffing, and training
Develop an organizational structure to execute your plan. Based on the staffing plan, determine the overall staffing
needs. Assess the need for permanent hires and consultants. Determine training requirements. Address office space
requirements if appropriate.
Objective: Organizational structure, staffing, hiring, training, and office space plans.
End-user participation and training
Based on the phased implementation schedule, determine the extent of end-user participation at each stage.
Estimate the end-user involvement in testing and the amount of training your users will need.
Objective: A document that describes end-user participation needs by level, function, and time period. It also
describes training requirements and a training time frame.
Budgets, tracking, and control
Develop cost estimates and budgets based on:
Resource requirements
Hiring, staffing, and training plans
Consultant expenses and off-the-shelf software requirements
Establish a project planning and control system, including a tracking mechanism.
Objective: A budget by category and by month, and a project planning and control system with a tracking
mechanism.
Organization and Training
When you implement the AppBuilder environment, you may need to restructure your IS department and retrain your
staff.
One language
One major benefit of AppBuilder software is its ability to consolidate many different IS groups into one team.
Although applications might run on two or more different platforms, AppBuilder software developers need to know
only one programming language.
Even though they need not be proficient in third-generation languages, AppBuilder software developers should be
familiar with the concepts of business-to-code paradigm, structured programming, object-oriented design,
and information engineering.
Phased introduction to AppBuilder software
Planning and Installing AppBuilder for the Mainframe
page 8 of 284
If you plan a gradual introduction of the AppBuilder environment, we suggest that soon after installation you schedule
high-level overviews for staff who won’t have access to AppBuilder software. When more detailed training becomes
necessary for these people, they will already have an understanding of the basics. This approach also allows
everyone to participate in the transition to the new environment.
Pilot Project
A simple and effective way to introduce AppBuilder software is through a pilot project. A pilot project is typically a
small-scale effort, staffed by motivated people whose objective is to showcase the technology that will gradually
spread throughout the organization. Thus it is important to select a highly competent team.
Project team composition
Each project needs a sponsor---a senior executive with authority and ultimate responsibility. Each team needs a
project manager and individual contributors with appropriate business skills. To ensure a cross section of skills and
ultimate success, teams should have two to three persons with experience in the traditional development cycle and
senior technical or business personnel.
End users and business experts must be part of the team, because they contribute as much to the analysis and
design of an application as system developers or business analysts. Incorporating users into the development
process accomplishes two objectives: first, it enables you to incorporate good suggestions when it is cost-effective
to do so, and second, it enables the end-users to develop a sense of proprietorship in “their” system. Their positive
attitudes help assure success, and their contributions
make the application perform according to their needs.
The team should have five or six developers and business representatives. Because concepts are new, each
member must have an interest in learning new approaches and technology. Members should be innovative,
entrepreneurial, and able to assist others in applying new technologies.
Project duration
From inception to completion, each project or phase should take up to four months (or 100 person-weeks with six
members per team). The initial projects should contain no more than 50 windows or reports with an average of eight
rules per window or report.
Additionally, the scope of the projects should include topics such as mainframe batch reporting, Dynamic Data
Exchange (DDE) with third-party software, component definition and usage, and local data retrieval by means of a
database manager. For each of these areas, specific standards, conventions, and guidelines must be developed and
published for the benefit of future development teams.
Commitment
Management and users must be committed and involved in order to achieve success in an enterprise-wide project.
Adequate resources, planning, and personnel are critical factors in ensuring that the organization’s goals and needs
are met.
Management
For an enterprise-wide project to succeed, commitment and sponsorship from management is critical. Management
must have long-term vision to see the needs and a short-term orientation to see that the project stays on track.
Management must allocate the necessary resources (physical, financial, and personnel) and resolve problems
beyond the jurisdiction of individual project managers.
You must obtain top management recognition and support for:
Planning and Installing AppBuilder for the Mainframe
page 9 of 284
The need to create an enterprise-wide model
Treating the enterprise-wide model as a major asset
The need to develop standards and conventions to promote consistency and reusability
Ample training for developers and end users
The project development methodology
End-Users
To achieve success, user commitment and involvement must be constant from start to finish of a project.
Throughout the project, user groups must provide sufficient resources and access to personnel with appropriate
business knowledge.
Allocation of resources
A primary building block in the using AppBuilder is the data model. A fully attributed data model should be completed
and approved by the user representative before actual development begins.
IBM’s Financial Services Industry (FSI) data model simplifies this effort, but management must still allocate
resources from both the MIS and business units so the model can be tailored to the company’s needs.
To prove that the model is sufficient, further resources must be committed to build a functional prototype.
Constructing a prototype also provides experience for constructing the real system in a subsequent step.
Development Team
Members of the development team should be motivated and interested in new technology. They should have an
understanding of the AppBuilder environment tools, development methodology, and standards. The development
group members must have experience or ability in the areas listed below.
Project managers
The project manager is responsible for the day-to-day direction of the development team, including:
Resource scheduling
Direction
Problem solving
Candidates must understand enterprise process and data modeling, object-oriented programming, system design,
graphical interface design, and project management.
Managers must have practical experience in leading a development team from analysis through system
implementation. These individuals must have the ability to motivate and train their team members and provide
direction by establishing a detailed project plan with defined deliverables, achievable milestones, and sufficient
checkpoints to ensure project success. Experience in the following areas is desirable:
Project planning in a business-to-code paradigm environment
Estimating for AppBuilder environment resources, time frames, and deliverables
Project life cycle leadership in a business-to-code paradigm
Project standards and procedures
Functional or technical design issues and considerations, concepts, and conventions; for example, Common
User Access (CUA) user interface and cooperative processing implications and usage
Joint Application Design (JAD) facilitation and usage
Estimating function points
System architect
Planning and Installing AppBuilder for the Mainframe
page 10 of 284
The system architect designs information systems and offers strategic technical direction to the project.The system
architect must have extensive development experience with a variety of software and hardware platforms.
The system architect understands the concepts and problems of specifying, designing, and building complex
systems. He or she knows how to measure and control the design of the system, estimate the required resources,
and ensure quality. The architect works with the business analyst to design applications that will satisfy the user’s
expectations.
System analysts and programmers
Programmer/analysts should have system analysis and design capabilities and a thorough understanding of
hardware and software to translate end-user requirements into viable applications.
Programmer
Programmers should have experience in developing medium-to-large applications. At a minimum, they should have a
background in business-to-code paradigm and an understanding of object-based design. Experience in the following
areas is desirable:
Applying logical data modeling and Business Object Analysis (BOA) techniques to application design
Working knowledge and practical expertise with functional and technical design concepts (such as protocycling, coupling and cohesion, cooperative processing application design, and CUA)
Project standards and procedures• Relational database principles and SQL coding
Interviewing and communication skills and techniques
Business analyst
The business analyst is a link between users and developers. He or she analyzes the enterprise and translate
requirements into solutions. These solutions often involve the design and implementation of computer systems.
The business analyst must understand data and process modeling in the financial services industry. The ideal
candidate has five or more years experience in FSI. The business analyst must be able to lead a group to
consensus on technical topics. Strong host and workstation computer skills are a major asset.
Specifically, the business analyst models the business, partitions it into cohesive objects, and designs the
preliminary user interfaces and window navigation of a new application.
Experience in the following areas is desirable:
JAD facilitation and use
Applying logical data modeling and Business Object Analysis techniques to application design
CUA application design and prototyping
Project standards and procedures
Interviewing and communication skills and techniques
Production and support personnel
Quality Assurance (QA) procedures for migrating applications into a production environment
QA procedures for monitoring CUA standards and conventions for naming and using objects
Implementation procedures
Recovery and back out support
Application security that includes user-terminal and application functionality•
Software migration and distribution
Workstation/LAN, communications, and support for mainframe DB2 and CICS
End-user services
Planning and Installing AppBuilder for the Mainframe
page 11 of 284
Development of standards and training materials
Communication and publishing techniques
Graphic design/layout
Training and presentation
Quality Assurance Team
Quality assurance team members should be self-motivated to ensure that the application performs acceptably and
meets user requirements. QA team members should also have a good understanding of the enterprise’s graphical
user interface standards and the AppBuilder tool set used to develop applications.
QA manager
The QA manager directs the QA team. The manager should have knowledge of unit and system testing, interface
design, and validating the business models against the application design.
QA analyst
QA analysts must be meticulous and thorough in testing all facets of an application interface according to a rigorous
test plan. They ensure that the application meets requirements and conforms to design standards.
Data Management Team
Members of the data management team should be motivated to develop, maintain, and provide a stable database on
which future applications will be built.
Data modeler
Data modelers develop relational data models to support the business. They work with business analysts,system
architects, and designers to identify and analyze the business data, model it, and turn the resulting models into
usable logical and physical designs. Modelers should have formal training in relational data modeling and Business
Object Analysis concepts, plus a thorough understanding of the enterprise’s naming and modeling standards.
Database administrator
A database administrator implements a physical data model or schema to validate creating the physical data model
through DB2 table generation and tunes the performance of the resulting database. The database administrator
should have heavy experience in relational database concepts, SQL performance,and tuning.
Application Development Operations Team
Members of the operations team work with QA to maintain the business models and provide business or system
expertise as required. In addition, each member should possess a good understanding of the development
methodology, standards, and the AppBuilder environment tool set.
Repository manager
The repository manager maintains and controls the development of objects in the AppBuilder repository. The
repository manager validates newly developed business models and checks their conformance to standards before
incorporating them into the enterprise-wide model. The repository manager also determines if the functionality of an
existing object can be used or modified to suit the new need. If an existing object is modified, the repository
manager must determine the impact of the change on existing systems.
Planning and Installing AppBuilder for the Mainframe
page 12 of 284
Repository model manager
The repository model manager is the “keeper” of the logical business models. This person works with the
development team to transfer business expertise (as defined in these models) and collect feedback(corrections,
enhancements, or additions) for incorporation.
Repository administrator
The repository administrator performs daily maintenance of the AppBuilder repository and AppBuilder host
environment tool sets. This person must understand repository concepts and relational databases. A background in
business-to-code paradigm and in-depth understanding of the AppBuilder environment is helpful. Strong host skills
are essential and knowledge of intelligent workstations is helpful.
Development support technician
Development support technicians should have experience in developing medium-to-large applications and knowledge
of workstation, CICS, and TSO facilities. Technicians should be interested in working with new technologies.
Experience in DB2 is essential. This person must be trained in AppBuilder software, be able to answer technical
questions on design and implementation, and be able to solve problems.
Production Team
Members of the production support team supply technical expertise to the project teams and assist them in moving
the application to the production environment.
Production support manager
The production support manager needs an understanding of the AppBuilder environment and the production support
role in the development life cycle---especially in the proto-cycling and technical construction phases. The production
support leader should have experience with automated system and security maintenance tools and an understanding
of current and future production environments.
Production support technician
Production support technicians need extensive knowledge of the host environment, and should be familiar with JCL,
TSO, DB2, CICS, Windows, the AppBuilder security model, and RACF or ACF2.
Planning and Installing AppBuilder for the Mainframe
page 13 of 284
Finding the Latest Information
For the latest information on documentation, product updates, support and training, contact AppBuilder Solutions
using the information in this section.
AppBuilder Support
AppBuilder Support
AppBuilder Support
AppBuilder Support
Website: http://support.appbuilder.com
E-mail: AppBuilderSupport@MagicSoftware.com
FTP site: ftp://ftp.appbuilder.com
WebFirst: https://web.appbuilder.com/wfs
AppBuilder Support
AppBuilder Support provides an efficient, centralized point of contact for all service-related communications between
AppBuilder and its clients. You would contact Support to:
Ask technical questions about AppBuilder’s products and services
Report problems with AppBuilder’s products
Check the status of a problem
Provide information software releases, modifications, and/or program fixes (RFXs and/or EFXs) currently
available
Pursue emergency fixes for problems
Suggest enhancements
Order products or services (for example, documentation and training)
Generally, clients find it best to designate one contact person at each location (typically the AppBuilder or
development administrator) for communication with Support. This allows your organization to effectively apply local
expertise in the AppBuilder products you use, and thus provides the quickest possible answers to basic questions.
Designating one contact person also allows the ability to monitor problems and escalate them efficiently as
required. Support is responsible for ensuring a high level of client satisfaction with AppBuilder products and services.
AppBuilder Support also offers an online method for our customers to log, view and maintain their incidents.
WebFirst allows each customer to log new incidents and review and update existing incidents. Please refer to the
AppBuilder Support email and website (noted above) for further information and to obtain a userid and password.
AppBuilder Consulting
AppBuilder Consulting can assist you in addressing any need that might arise, including those related to DB2, CICS,
communications hardware, methodology, process and data modeling, and project planning,as well as issues specific
to AppBuilder installation.
AppBuilder Consulting also offers the services of highly skilled application specialists who are experienced IT
professionals with comprehensive knowledge of the AppBuilder environment and many other hardware and software
systems.
Before Installing AppBuilder Software
You must complete the following steps before installing AppBuilder software:
Complete the non-disclosure agreement
Review installation requirements and obtain pre-installation checklists from AppBuilder Support
Complete pre-installation checklists and email them to AppBuilder Support
Schedule an installation date through your AppBuilder Solutions contact
Identify all AppBuilder support staff
Planning and Installing AppBuilder for the Mainframe
page 14 of 284
Acquire necessary prerequisites
Install and test necessary prerequisites
Define DASD space, installation and training user IDs, and data set naming conventions
Support responsibilities
On receiving a request for installation the Support Manager will work with the client and AppBuilder Sales/Consulting
to prepare for installation. Whenever possible traveling to the client location to perform/support the installation is
optionally available upon request .
Week one
Initial TSR/Consultant contact
Complete and review Installation Customization Worksheets and checklist
Contact client Technical Representative and review any “red flag” install issues
Create action plan to resolve “red flag” issues prior to beginning install
Week two
Contact client to review any “red flag” issues and plan for resolution
Ensure software and documentation have been received by client
Based on planning results and action plan to resolve “red flag” issues confirm installation start date
TSR/consultant responsibilities
Ensure Client Technical Representative completes and returns Installation Customization Worksheets and
checklist to Support staff
Ensure action plan to resolve any “red flag” is implemented
Ensure host sessions available on workstations to be used during installation
Ensure client receives and reviews Planning and Installation, and Install manuals
Client responsibilities
Assign technical contact responsible for working with AppBuilder throughout installation period
Complete Installation Customization Worksheets and checklists
Review checklists and worksheets with Support Analyst
Install and configure third-party software
Ensure appropriate technical resources and personnel are available prior to Support Analyst traveling to client
site
AppBuilder Software Overview
The AppBuilder environment features an enterprise repository that works in conjunction with the developer’s personal
repository or Workgroup repository. The ability to access and share design and development objects enables a high
degree of object reuse. Developers can query the enterprise repository for reusable objects, easily download them to
their personal repository, and work with multiple versions of AppBuilder-built applications. Newly-defined designs,
models, and application specifications can also be uploaded to the host-resident enterprise repository, a DB2-based
facility. Intelligent check-in/check-out controls ensure data integrity and security.
AppBuilder Enterprise Repository (EREP-TSO)
Planning and Installing AppBuilder for the Mainframe
page 15 of 284
AppBuilder Enterprise Repository software provides developers with an interface to the enterprise repository and is
used to perform three important tasks:
Accessing the Enterprise Repository
Generating host-only and host-server application code
Testing host-only and host-server application code
The Enterprise Repository is used to store data, process objects, and executables. It provides a single centralized
storage facility for all AppBuilder-built applications. You can perform global queries, such as extended where-used
reports and keyword searches, against any of these stored objects.
The Enterprise Repository also provides various administration tools. Refer to Enterprise Administration Guide,
Enterprise Application Guide, Enterprise Migration Guide, and Enterprise Rebuild Guide for more detailed information.
For applications that execute on the host in part or entirely, you need to use the Enterprise Repository to complete
the construction and testing phase of application development.
For construction, the Enterprise Repository is used to prepare all host rules, components, windows, and
reports. This creates host-executable modules. This Enterprise Repository is also used to generate the datadefinition language (DDL) for DB2 tables.
For testing, the workbench Batch RuleView facility is invoked through the repository interface to unit test host
batch rules and components. For CICS, the testing facility is invoked via an AppBuilder CICS transaction.
Online Preparation Workbench (ONLP-CICS, ONLP-IMS)
The AppBuilder Online Preparation Workbench generates Enterprise COBOL code from AppBuilder rules in the
Enterprise Repository and compiles it to run on the host. It includes host online RuleView debugging tool and
supports CICS and IMS run-time environments.
Batch Preparation Workbench (BATP-Mainframe)
AppBuilder Batch Preparation Workbench software generates Enterprise COBOL code from AppBuilder rules in the
enterprise repository and compiles it to run on the host. It supports the mainframe Batch run-time environment. It
includes host batch RuleView debugging tool.
Report Writer (RPTP-Mainframe)
The Report Writer supports creation of paper-based reports by batch applications.
3270 Converse Preparation (327 P-CICS, 327 P-IMS)
AppBuilder 3270 Converse Preparation and 3270 Converse Client software allows developers to create WYSIWYG
windows for 3270 terminal-based applications. The 3270 Window Painter supports only those objects that can be
represented in a character-based display, and enforces restrictions on color identical to those imposed by the 3270
terminal. It is no longer necessary for a window to be initially designed on the workstation Window Painter and
converted to the 3270 Window Painter. However, the 3270 Window Painter does provides the option to convert
workstation windows to adhere to 3270 implementations.
Two approaches can be used for adapting workstation and host interfaces to the same application. In the first, a
single end-user interface can be designed to execute on both the workstation and the host, with comparable displays
on each platform, and with minor functional differences in behavior. This approach is convenient, but limits the
workstation “notifies” to the technological limitations of a 3270 terminal. In the second approach, distinct workstation
and host end-user interfaces can be designed for a single window entity---a single application. This approach allows
each interface to take advantage of diverse display capabilities, but requires more effort.
Planning and Installing AppBuilder for the Mainframe
page 16 of 284
Staff responsibilities
Developers can provide users with a consistent look and feel across applications on the host (using NPTs) and on
the workstation.
Product summary
AppBuilder 3270 Converse Preparation generates AppBuilder windows that run on a 3270 NPT in online applications.
You can design, construct, prototype, and debug these windows on the Workstation Development Workbench, and
then use this product to generate host-based run-time versions. It supports CICS and IMS.
Host Middleware (MWSE-CICS, MWSE-IMS, MWCL-327C,
MWCL327I)
There are two host middleware servers and two host middleware clients---one server and one client each for CICS
and IMS. The server products allow server rules to run in CICS or IMS. The client products allow 3270 Converse
applications to run so that end users can use 3270 terminals.
Note
The Host Middleware Enterprise server is packaged with the Online Preparation Workbench. The
Host Middleware client is packaged with 3270 Converse Preparation Workbench.
Planning and Installing AppBuilder for the Mainframe
page 17 of 284
Preinstallation requirements and application maintenance
Maintaining AppBuilder applications requires planning and monitoring of the mainframe platform by the system
administrator. This section provides an overview of the installed system and details about design, tuning, and
execution in the AppBuilder environment.
Planning and Installing AppBuilder for the Mainframe
page 18 of 284
Understanding the Installed Environment
The AppBuilder environment features an enterprise repository that works with a developer’s personal repository or
workgroup repository. The capability to access and share design and development objects enables a high degree of
object reuse. Developers can query the enterprise repository for reusable objects and easily download them to their
personal repository, and work with multiple versions of AppBuilder built applications. Newly-defined designs, models,
and application specifications can also be uploaded to the host-resident enterprise repository, a DB2-based facility.
Intelligent check-in/check-out controls ensure data integrity and security. Topics include:
#Installing Components
#Performance Tuning
Installing Components
The AppBuilder environment has been designed to allow you to customize the installation of AppBuilder software to
ensure conformance to your system standards. The following section identifies all customizable items that must be
determined prior to the start of the installation.
#Data Set Naming Standards
Short-term Data Sets
Security
DB2
CICS
VTAM
IMS
Data Set Naming Standards
AppBuilder system software uses various types of data sets to store product software and user data generated
during the development process. Data sets follow specific naming conventions that are custom-configured at your
site. A description of the data set qualifiers used in AppBuilder follows:
#GLOBQUAL
#INSTQUAL
#BASEQUAL
MODQUAL
REPQUAL
USRVQUAL
VSUVQUAL
VSMQUAL
MIG_FILE_ID
GLOBQUAL
Defined during the initial load of HIW (Host Installation Workbench), this resides in the REXX member INSTART in
&GLOBQUAL..CLIST and names the libraries that comprise HIW.
INSTQUAL
This resides in the INI member @INSTENV and defines that data sets that hold the system and repository
installation software.
BASEQUAL
Planning and Installing AppBuilder for the Mainframe
page 19 of 284
This is initially defined during the AppBuilder System Software Installation and names the libraries that hold the
AppBuilder software. The value is stored in the data set &GLOBQUAL..USER.CLIST in the member for each system
(for example, if you have a system named NEWSYS, there will be a PDS member named NEWSYS also).
MODQUAL
Analogous to BASEQUAL, this qualifier names system libraries which are created empty and can be used to hold
client modifications.
Note The qualifiers BASEQUAL and MODQUAL are also stored in the INI member @HPSENV. Their presence there
defines the system that is associated with a given repository.
REPQUAL
Defined in @HPSENV, this qualifier defines data sets which hold information specific to a given repository.
REPQUAL libraries can also be used to hold software modifications which are to affect only one repository.
USRVQUA
Defined in the INI member @USRENV for each repository version, this qualifier names the data sets which hold
USER application information.
VSUVQUAL
Defined in the INI member @USRENV for each repository version, this qualifier names the VSAM data sets which
hold USER application runtime information. This qualifier names the FCT entries which are required with the CICS
runtime software.
VSMQUAL
This qualifier defines VSAM data sets which are part of the system software and not specific to a repository. This
qualifier is defined in &GLOBQUAL..USER.CLIST (sysid) and in the INI member @HPSENV.
MIG_FILE_ID
Defined in the INI member @MIGENV for each repository version, this qualifier defines the default data set name for
migration data sets.
Short-term Data Sets
Short-term data sets are created during the development stage. They are required only for a short period (typically
two to three days) after which they may be deleted.
A standard naming convention is followed to ease DASD cleanup of temporary data sets. Three qualifiers are used
to name short-term data sets. All variables support more than one node and are listed in Table 2-1. The three
variables are defined in the INI member @HPSENV.
Table 2-1
Short-term data set qualifiers
TEMPQUAL
GRPQUAL
PERMQUAL
Maximum
value
10 characters
18 characters
10
characters
Value contents
Final node must be seven
characters or less
Must contain the
value of SYSUID
Example
TEMP.NN.*
PAY.USERID.*
Planning and Installing AppBuilder for the Mainframe
AB.PERM.*
page 20 of 284
Security
This section provides details pertaining to AppBuilder user ID and security requirements. All AppBuilder user IDs
must have the following logon attributes:
At least six megabytes of main storage must be allocated at logon time.
The AppBuilder IDs require access to the AppBuilder CICS region.
If your CICS region is secured, you must set up the appropriate accesses for the necessary transactions. To
use the LU2 program interface, you must allow the three CICS TCT (see “CICS” on page 2-6) definitions and
corresponding VTAM APPLIDs (see “VTAM” on page 2-7) to execute these CICS transactions:
CEMT
CEDA
HS06
UTBL
Data set access requirements vary based on individual user function.
Table 2-2 summarizes system data set read/execute access needed by AppBuilder installer.
Table 2-2 AppBuilder installer data set access requirements
Data set (for installers)
Read
Write
Allocate
ABOUT..*
3
3
3
&BASEQUAL..*
3
3
3
&GLOBQUAL..*
3
3
3
&GRPQUAL..*
3
3
3
&INSTQUAL..*
3
3
3
&MIG_FILE_ID..*
3
3
3
&MODQUAL..*
3
3
3
&PERMQUAL..*
3
3
3
&REPQUAL..*
3
3
3
&TEMPQUAL..*
3
3
3
&USRVQUAL..*
3
3
3
&VSMQUAL..*
3
3
3
&VSUVQUAL..*
3
3
3
Table 2-3 summarizes system data set read/execute access needed by AppBuilder end users.
Table 2-3
AppBuilder end-user data set access requirements
Data set (for users)
Read
Write
Allocate
Planning and Installing AppBuilder for the Mainframe
page 21 of 284
&GRPQUAL..*
3
3
3
&PERMQUAL..*
3
3
3
&MIG_FILE_ID..*
3
3
3
&MODQUAL..*
3
&BASEQUAL..*
3
&REPQUAL..*
3
&USRVQUAL..*
3
3
3
&TEMPQUAL..*
3
3
3
&VSMQUAL..*
3
&VSUVQUAL..*
3
3
Table 2-4 summarizes system data set read/execute access needed by AppBuilder administrators.
Table 2-4 AppBuilder administrator data set access requirements
Data set (for administrators)
Read
Write
Allocate
&GRPQUAL..*
3
3
3
&PERMQUAL..*
3
3
3
&MIG_FILE_ID..*
3
3
3
&GLOBQUAL..*
3
3
3
&MODQUAL..*
3
&REPQUAL..*
3
3
3
&USRVQUAL..*
3
3
3
&BASEQUAL..*
3
&INSTQUAL..*
3
&TEMPQUAL..*
3
3
3
&VSMQUAL..*
3
&VSUVQUAL..*
3
3
3
Table 2-5 summarizes system data set access for AppBuilder installers and developers.
Table 2-5 System data set access for AppBuilder software installers and developers
Planning and Installing AppBuilder for the Mainframe
page 22 of 284
System data set
Installer access
Developer access
Read
Execute
Read
Execute
C compiler library
3
3
CICS LE link library
3
3
3
3
CICS macro library
3
3
3
3
COBOL II compiler library
3
3
3
3
LE link library
3
3
3
3
DB2 link and load libraries
3
3
3
3
DB2 preprocessor
3
3
3
3
DB2 utility library
3
3
H assembler
3
3
3
3
IDCAMS or equivalent utility
3
3
3
3
IEBGENER and IEBCOPY utilities
3
3
3
3
ISPF libraries
3
3
3
3
PL/I transient libraries
3
3
3
3
DB2
This section provides details pertaining to the DB2 requirements of the AppBuilder software. Your system must be
installed with the following requirements installed.
The use of DB2 packages, as well as plans, must be supported.
SPUFI or an equivalent DB2 query/update facility must be available and accessible from ISPF.
Select access on the DB2 system catalog table SYSIBM.SYSTABLES is required during the installation.
The allocation of DB2 objects must support the use of VSAM definitions if VCATs are used instead of
STOGROUPs.
Recommended initial size on DB2 Buffer pools is 4K.
AppBuilder recommends that the installer’s ID have SYSADM authority. If SYSADM authority cannot be
granted, specific DB2 authorities needed by the installer’s ID in lieu of SYSADM are as follows:
System Privileges:
BINDADD
CREATEDBA
Collection and Package Privileges:
PACKADM on collection ID.
Note
If secondary authorization IDs are used to bind AppBuilder software plans or to
create AppBuilder software DB2 objects, the secondary IDs must also have the
appropriate authorities.
The installer’s IDs, administrator’s IDs, and all AppBuilder software developer IDs must have BINDADD
authority.
Planning and Installing AppBuilder for the Mainframe
page 23 of 284
CICS
The installation process will generate a complete CICS CSD file and provide uncustomized JCL to migrate
AppBuilder definitions into the target region.
Configure the target AppBuilder region(s) to support PL/I, COBOL II, and C programs.
Create the following CICS groups which must be included in the CICS start-up grouplist:
AB34, used for AppBuilder object definitions
HPESDUG, used for utility definitions
HPESDUK, used for utility definitions
HPSTIP, used for associating all definitions required for installation verification
Additional groups are defined to support the CICS Online Server if it has been installed.
Complete the required VTAM system changes.
Define three new APPLIDs.
Define one new LOGMODE entry.
Review USSTAB entry for CICS.
Review USSTAB entry for TSO.
Define 3270 sessions as DFT with four sessions. Four sessions enable the execution of multiple
AppBuilder applications.
The following details list the CICS requirements of the AppBuilder software that must be on an installed system.
Preload the CICS Sign-on Table (SNT).
Configure and activate the CICS DB2 attach facility. Refer to your CICS documentation for further details on
this setup.
Configure CICS for LE support
Configure the CICS Destination Control Table (DCT) to include the DCT definition (see Appendix B, “CICS
Table Definitions”).
Configure the CICS Terminal Control Table (TCT) to include the TCT definitions (see Appendix B, “CICS Table
Definitions”). The first TCT definition in the DFHTCT table is a sample of a AppBuilder terminal. The three
TCT definitions following the sample TCT definition are used for the AppBuilder LU2 program interface. The
NETNAMES contained in the TCT correspond to the three APPLIDs defined to VTAM that are used only for
reference and may be changed in accordance to your network standards. (These values must be the same in
both CICS and VTAM.) The netnames A06HPS1, A06HPS2, and A06HPS3 are the default VTAM application
IDs that appear on the installation panel containing the AppBuilder CICS environment.
CICS processing program table (PPT) and CICS program control table (PCT) will be supplied in CSD file
format (see Appendix B, “CICS Table Definitions”).
Define the transaction security level as public execute for all AppBuilder transactions.
Set resource-level checking to No for all AppBuilder items.
Set up your security system to allow execution of the CEDA and CEMT transactions. These commands will
be executed through a batch job using one of the three VTAM APPLIDs as the entry point to CICS. Therefore,
these three IDs must have execution access to the two commands. The AppBuilder developer’s user ID does
not require the ability to execute CEDA or CEMT commands. The AppBuilder transactions HS06 and UTBL
and their associated programs, HPSNEWC and HPSUTBL, must also be executed by these three APPLIDs.
Configure CICS terminals if LU6.2 protocol will be used.
VTAM
AppBuilder software requires the definition of three VTAM APPLIDs and one VTAM LOGMODE entry. The actual
names of these definitions are configured and defined before installation.
The installation process completes the following required VTAM system changes:
TSO IDs must be defined to allow access to both CICS or IMS and TSO.
AppBuilder software supports the use of session managers. However, the AppBuilder upload/ download
process requires exclusive use of the session manager for the duration of the upload or download.
Planning and Installing AppBuilder for the Mainframe
page 24 of 284
AppBuilder software requires one VTAM LOGMODE must be added to your network configuration. The
LOGMODE name HPSLU2 is used only as a reference and can be changed according to your network
standards. Any changes to the name must also be reflected in the APPLID definitions described previously.
IMS
The following details list the IMS requirements of the AppBuilder software that must be on an installed system.
Configure IMS to support DB2.
Configure IMS to support APPC if LU6.2 protocol will be used during runtime.
Note
If you want to use APPC communications in IMS, Mainframe/APPC communications should be
installed on your system. This feature is a required prerequisite of the IMS Online Preparation
Workbench. Refer to IBM’s IMS Systems Definition Reference manual for instructions to connect
IMS to Mainframe/APPC. Refer to IBM’s IMS DC Admin Guide for instructions about connecting TP
names to specific transactions and IMS MPR classes.
Planning and Installing AppBuilder for the Mainframe
page 25 of 284
Performance Tuning. Suggestions for tuning AppBuilder
Tuning applications to improve performance is a critical issue in any organization. This article describes suggestions
for tuning AppBuilder on the host, in both the development and execution environments. However, keep in mind that
not all of the tuning recommendations may be appropriate for your site--- use caution and common sense when
applying them.
Development Environment
You can improve performance in the development environment by making changes outside and inside AppBuilder.
Recommendations in both areas are listed below.
Make sure you appreciate the differences between traditional development and development using AppBuilder
software. The AppBuilder developer's profile is quite different.
The usage profile also differs at various stages of a project's lifecycle. During analysis, DB2 usage is heavier as
there is more emphasis on the use of the analysis tools, and more text and keywords are uploaded. At later stages,
there is a heavier reliance on batch prepares, and uploads are likely to be smaller and more specific. During testing,
there is more use made of Customer Information Control System (CICS) or Information Management System (IMS)
execution.
Keep the number of TSO users to a minimum. TSO jobs tend to have a higher priority than batch jobs--- so the more
users you have, the slower the system runs.
Increase the number of DB2 threads available for each mainframe transaction--- this is especially useful for volume
tests. However, a practical limit exists, which you should discuss with your database administrator (DBA).
Tune the AppBuilder sign-on, as this process is very resource-intensive. By tuning the sign-on, you reduce the
amount of time that it takes to “get into” AppBuilder each time a developer enters the host workbench, starts an
upload, or runs a batch TSO job.
Consider running AppBuilder in its own logical partition (LPAR) to make management and tuning of the system
easier.
Using the MVS Migration Server
The migration automation uses TCP/IP communications. The migration files are automatically uploaded and the
Analyze and Import are executed. Results of the import are then automatically transferred down to the workstation
for review.
For download, you can query target MRE repositories and select the objects and the scopes to be downloaded. Once
satisfied with your choices, the download process is initiated. The host repository exports the data and makes the
files available for the client to download. The client then downloads the migration files, executes an import and
displays the results to the user.
This feature benefits standard migrations and unit of work migrations equally. This option coexists with standard
migration processing. With this feature, the upload migration steps are simplified to three steps:
1. Specify user connectivity information (userID, password, target repository)
2. Initiate upload process
3. Upon notification of completion of host upload, review the report
The download migration steps are simplified to five steps:
1. Specify user connectivity information
Planning and Installing AppBuilder for the Mainframe
page 26 of 284
2.
3.
4.
5.
Query the objects on a given MRE repository
Select objects to be downloaded and the scope of the download
Initiate the download process
Upon completion, review the report
Migrating Objects
Keep migrations as small as possible. Ask yourself--- is it necessary to export an entire hierarchy, or will a partial
hierarchy be adequate? Also, use the Automate Migration (MIGRATE) action when possible to speed up the
process.
If you are working under time constraints, do not include text or keywords in the migration. You can migrate those
parts later. Migrate message sets on their own, because message sets require relationship text to be migrated.
Use DB2 utilities to reorganize the large migration tables more often than other tables. Reorganize tablespaces after
all big migrations. Change all tablespaces from simple to segmented. However, note that this change is likely to take
some time.
Tables which may need to receive special consideration include:
INMIG
ENT_LOGKEY
RBD_ACTION
RBD_CONFIG_LOGKEY
RBD_ENTITY_LOGKEY
RBD_PHASE
REL_LOGKEY
The following tables should be monitored regularly:
CRC_ENTITY
CRC_RELATION
ENT_SIG_CHANGE
Delete extraneous data using the Clean Up (CLEANUP) action as much as possible without damaging the process--for example, do not clean up analyze and rebuild information that is still part of a delivery cycle. Migration tables
continually fill up and require more maintenance than other repository tables. Consider using a separate High Level
Qualifier (HLQ) for the migration tables to make managing them much easier.
Note
Do not run DB2 RUNSTATS on large tables when they are empty.
If, after your migration, you are going to perform a rebuild, make sure that all objects being migrated prepare in the
source environment. If your objects do not prepare in the source environment, they will not prepare during the rebuild
process.
An additional action that may improve the performance of migrations is to separate the physical location of the
INMIG indices from the physical location of the table.
Tuning the AppBuilder Mainframe Environment
The following tuning methods result from an AppBuilder performance survey in which the objective was to minimize
the elapsed and CPU times for migration processing.
The following suggestions depend on DB2 being tuned as well.
Planning and Installing AppBuilder for the Mainframe
page 27 of 284
Run REORGs, RUNSTATS, and rebinds after all large migrations. If the repository or the migration does not include
particular object types, do not reorganize those tables. Some AppBuilder users clean up the following tables after
each migration:
Table 2-6
Recommended tables to be cleaned after each migration
CRC_ENTITY
CRC_RELATION
E_RULE
E_WINDOW
E_VIEW
E_PANEL
E_FLD
E_WINCON
E_MIGRTN
E_SRCTXT
E_SRCBIN
ENT_SIG_CHANGE
R_RULRUL
R_VUOWNS
R_WNCPNL
R_WNDWNC
R_USESVW
R_WNCHLP
Do not run REORGS or RUNSTATS on empty tables, or while a migration is in progress. A migration is in progress
not only when a particular job is running, but also if the process has not finished all the steps it will take in that
repository, including all the rebuild steps. For instance, even if a migration has finished the analyze step, do not
reorganize if you plan to import the package later.
Tune the SEGSIZE, PCTFREE, FREEPAGE, and SUBPAGE parameters depending on the type of access to which
that physical repository is most commonly subjected. Some repositories (such as quality assurance) have a large
number of updates and inserts due to migrations. Other repositories (such as development) have many more selects
than updates and inserts.
Set CLOSE to NO for all tables. Set the LOCKSIZE to TABLESPACE on the INMIG table in order to minimize the
IRLM overhead.
Because of the sort order used in parts of AMI and the download process, the following index prevents an indexspace scan and sort:
Create unique index OWNERID.XRVUOWNS3 on OWNERID.R_VUOWNS
X_ENTITY_TYPE ASC,
X_INSTANCE_ID ASC,
Y_ENTITY_TYPE ASC,
Y_INSTANCE_ID ASC,
SEP_ID ASC,
VERSION ASC)
Using STOGROUP STOGRPA
PRIQTY... SECQTY...PCTFREE...
SUBPAGES... CLOSE YES;
Tuning the Enterprise Repository
Planning and Installing AppBuilder for the Mainframe
page 28 of 284
The following recommendations enhance the performance of the enterprise repository and uploading and
downloading. These suggestions are based on the analysis of performance monitors and client feedback. They are
not intended to replace the procedures detailed in IBM systems manuals.
CRUD INI Variables
During execution, the enterprise loads certain create, read, update, and delete modules (CRUDs) into memory to
satisfy a given request. For example, when you perform a List Relation (LR) action on a rule entity, the enterprise
brings a number of CRUDs into memory to determine in which relations the rule participates. The enterprise also
loads CRUDs to extract relation instances during uploads and downloads.
The number of modules in memory at any given time is governed by a Least Recently used (LRU) facility. Once the
maximum number of CRUDs are loaded, the next fetch releases the maximum number minus the minimum number
of CRUDs.
Three sets of INI file control variables control the minimum and maximum numbers of the three different types of
DB2 CRUDs. These variables exist in the @HPSENV.INI file, and are prefixed by MN or MX. The MN variable
controls the minimum number of CRUDs kept in memory. The MX variable controls the maximum number of CRUDs
kept in memory. The MNECRUD and MXECRUD variables control the entity CRUDs, the MNRCRUD and MXRCRUD
control the relation CRUDs, and the MNBCRUD and MXBCRUD control the explode CRUDs. The online repository
interface uses the entity and relation CRUDs and, as a result, does not benefit from tuning the explode CRUDs.
Upload and download performance can be improved by tuning the entity and relation CRUDs, but gains the most
from tuning the explode CRUDs.
If you have enough storage, you can increase the MX and MN variables to improve performance. Increasing these
variables reduces SVC008 load calls, which in turn reduces CPU usage and improves response time. Conversely,
you can lower storage requirements by decreasing the MX and MN variables.
Library Lookaside Facility
The Library Lookaside facility (LLA) is a mainframe system facility that lets mainframe use memory instead of disk
reads to eliminate I/O on load libraries. By placing the AppBuilder load module directory into the LLA, you eliminate
physical I/O when fetching CRUD modules. This eliminates EXCPs, and improves response time.
Specify the AppBuilder load library FREEZE parameter. The FREEZE parameter tells the LLA facility that no
updates will occur to the directory, which allows LLA to place the entire directory into storage. The NOFREEZE
parameter is of little benefit to the LLA since the LLA always goes to DASD to read the directory. When using the
FREEZE parameter, updates to the load libraries must be managed manually, otherwise those updates will not be
picked up properly.
Exits used by the LLA can also directly affect performance. LLA uses two logging exits: CSVLLIX1 and CSVLLIX2.
CSVLLIX1 adversely affects the performance of the LLA. CSVLLIX2 incurs less overhead and performs better. You
can attain the best performance without any exit.
Program Management Optimizer (PMO) by Legent is a competitor product and provides similar performance
increases. The main benefit of PMO is that it automatically identifies updates to libraries across systems. For more
information about PMO, call Legent in the United States at 800 676 5468. (Please note that this information is for
your reference only. AppBuilder has not tested PMO, and therefore cannot endorse the product.)
Virtual Lookaside Facility
The Virtual Lookaside facility (VLF) is a general-purpose data space manager that starts at initial program load (IPL)
time, and is non-swappable. This facility can bring CLISTs into memory, which minimizes DASD hits and improves
response time.
During execution, uploads and downloads execute the HPSEFIT and HPSCFIT CLISTs for each upload/ download
request file. Put the &PREFIXP.&LEVELP.CLIST libraries into a VLF data space to maximize performance. This
eliminates EXCPs and improves elapsed time.
Planning and Installing AppBuilder for the Mainframe
page 29 of 284
Quick-Fetch by Legent provides similar functionality to VLF. It places highly-used modules into storage to reduce I/O
during loads. Quick-Fetch identifies when updates occur so it uses the most current version. For more information
about Quick-Fetch, call Legent in the United States at 800 676 5468. (Please note that this information is for your
reference only. AppBuilder has not tested Quick-Fetch, and therefore cannot endorse the product.)
Planning and Installing AppBuilder for the Mainframe
page 30 of 284
Execution Environment
The AppBuilder mainframe application execution (AE) environment supports different national requirements for date,
time, and currency formats.
Data Source
Since the requirement for National Language Support (NLS) formats on the host was driven by similar support on the
PC workstation, we looked to the PC environment for the source of the basic data.
On the PC, two C header files define the supported countries or national language types (for example, while most
countries have a single defined format Canada has Canadian_French and Canadian_English formats), and the data
formats for each of those countries. The information defining these formats includes date and time format (month,
day, year; day, month, year; etc.), the separators used between the parts of date and time, the currency symbol, the
separators used to indicate thousands and decimal positions, and the number of decimal places to be used.
Host Format
On the host, we decided to put this information in a table held in main storage rather than as definitions compiled into
each program that might need them. By storing the information this way, the data:
Is held in only one place
Can be changed without recompiling any executable programs (with the inherent possibility of missing one or
more programs that need to be recompiled)
Can be modified easily during testing or in the field
This last feature allows, for instance, you to create a program to dynamically modify the data based on user input.
Conversion
The PC C header defining the data formats for each country is uploaded to the host where a REXX program
processes it. This program parses the data and creates an output file, which is an Assembler language source
macro. This macro is included into the assembler source defining the table, is loaded into storage, and when
compiled generates the national language data table*. This data table is link edited into the AppBuilder Global
Parameters Program HPEGAPA (for the PCV environment) or HPSCGAP (for the CNV3 environment). Since this
NLS table contains data for all supported countries, an AppBuilder country number functions as an index to the data.
In actuality, the data is held as three interconnected tables---one containing character string data, one containing
punctuation characters and a third containing edit rules and pointers to the other two tables. The reasons for having
three tables are to compress string data and to avoid storing duplicate data, while still permitting flexibility for future
expansion.
Country Code and Code Page
Confusion occurs on occasion about the AppBuilder country code and the code page. The country code is a simple
index into a data table that matches the PC C header file, which defines the supported countries. It is a number
sequentially assigned to the list of supported countries: Albania is 1 and Yugoslavia is 35.
The code page, on the other hand, is an IBM-assigned number that designates the character set used in each
country. This is more relevant on a workstation than the host because most (though not all) hosts use the same
code page, but a workstation can be set up to use many code pages and can switch between them.
The code page defines which character is produced on a display or printer for a given byte value (0 to 255). Many of
these are invariant across code pages, but some produce different results---for example, the value for the dollar sign
in the US appears as the monetary pound sign in the UK.
Planning and Installing AppBuilder for the Mainframe
page 31 of 284
Country Codes for Fields, Panels, and Systems
When a window is painted using the AppBuilder Window Painter and a field that can have national language variants
is placed on the panel, you can choose in which country format to display the field. The choices are: any specific
country, the panel default, or the system default. You choose the panel default the same way. Thus, for a system
running in Switzerland, it is possible to define a panel default of German with fields displaying in French, Italian, and
the default formats.
AppBuilder stores the chosen country code as part of the field and panel definition. If the field country code is zero,
it defaults to the panel, and similarly panel to system. If a specific format is chosen for a field instead of a
predefined country format then this specific format is saved along with the other field attributes and used at runtime.
The system country code is stored in the AppBuilder Global Area Program HPEGAPA. This country code is initially
set to 34 for the United States and so you must change it to the appropriate code when you install AppBuilder.
We provide a small global area customization program called HPEUCGP, in which you can change the country code
to simplify the task of customization. This program is then assembled and linked into the HPEGAPA load module.
Supported Countries
In the current implementation of the host NLS, AppBuilder supports thirty-five countries. These are shown below with
the data for each.
The columns headed P, T, D, N, and DP indicate the default formatting and punctuation for the country, and are
described in Table 2-7.
Table 2-7
Countries supported by NLS
Country name
No.
Date format and
separator
Time format and
separator
Currency
P
T
D
N
DP
ALBANIA
1
%Y/%0m/%d
%t:%0m:%0s
Lek
0
.
,
1
2
ARGENTINA
2
%d/%m/%0y
%0t.%0m.%0s
A
0
.
,
1
2
AUSTRIA
3
%Y-%0m-%0d
%0t:%0m:%0s,%0f
S
2
.
,
1
2
BELGIUM
4
%d/%m/%0y
%0t:%0m:%0s,%0f
BF
3
.
,
5
2
BRAZIL
5
%0d/%0m/%0y
%0t:%0m:%0s
$
1
.
,
1
2
CANADA_FRENCH
6
%0y-%0m-%0d
%0t:%0m:%0s
$
0
,
.
1
2
CANADA_ENGLISH
7
%0d/%0m/%0y
%0t:%0m:%0s.%0f
$
0
,
.
1
2
CHINA
8
%Y.%0m.%0d
%0t:%0m:%0s
¥
0
,
.
1
2
CZECHOSLOVAKIA
9
%Y-%0m-%0d
%0t:%0m:%0s
Kcs
2
.
,
1
2
DENMARK
10
%0d-%0m-%0y
%0t.%0m.%0s,%0f
kr
2
.
,
2
2
FINLAND
11
%0d.%0m.%Y
%0t.%0m.%0s,%0f
Mk
3
,
3
2
FRANCE
12
%0d.%0m.%Y
%0t:%0m:%0s,%0f
F
3
,
5
2
GERMANY
13
%0d.%0m.%Y
%0t:%0m:%0s
DM
0
.
,
1
2
GREECE
14
%0d/%0m/%0y
%0t:%0m:%0s.%0f
Drs
0
.
,
1
2
Planning and Installing AppBuilder for the Mainframe
page 32 of 284
HUNGARY
15
%Y-%0m-%0d
%0t:%0m:%0s
FT
0
,
1
2
ICELAND
16
%Y-%0m-%0d
%0t:%0m:%0s
kr
3
.
,
5
2
ITALY
17
%0d/%0m/%0y
%0t.%0m.%0s,%0f
L
2
.
,
1
0
JAPAN
18
%Y-%0m-%0d
%0t:%0m:%0s
¥
0
,
.
1
0
NETHERLANDS
19
%0d-%0m-%0y
%0t:%0m:%0s
F
2
.
,
2
2
NEW_ZEALAND
20
%0d/%0m/%0y
%0t:%0m:%0s
$
0
,
.
1
2
NORWAY
21
%0d.%0m.%0y
%0t:%0m:%0s,%0f
kr
0
.
,
3
2
POLAND
22
%Y-%0m-%0d
%0t:%0m:%0s
Zl
0
.
,
1
2
PORTUGAL
23
%0d-%0m-%Y
%0t:%0m:%0s
Esc.
3
.
,
1
2
ROMANIA
24
%Y-%0m-%0d
%0t:%0m:%0s
Lei
2
.
,
1
2
SOUTH_AFRICA
25
%Y-%0m-%0d
%0hh%0m:%0s.%0f
R
0
,
0
2
SOUTH_KOREA
26
%Y.%0m.%0d
%0t:%0m:%0s
W
0
,
.
1
2
SPAIN
27
%0d/%0m/%0y
%0t:%0m:%0s
Pts
2
.
,
1
0
SWEDEN
28
%Y-%0m-%0d
kl %0t.%0m.%0s
Kr
3
.
,
5
2
SWITZERLAND
29
%0d.%0m.%0y
%0t,%0m,%0s
Fr.
0
‘
.
1
2
TAIWAN
30
%0y/%0m/%0d
%0t:%0m:%0s.%0f
$
0
,
.
1
2
THAILAND
31
%0d/%0m/%0y
%0t:%0m:%0s
B
0
,
.
2
2
TURKEY
32
%0d/%0m/%0y
%0t:%0m:%0s
TL
0
.
,
1
0
UNITED_KINGDOM
33
%0d/%0m/%0y
%0t:%0m:%0s
£
0
,
.
1
2
UNITED_STATES
34
%0m/%0d/%0y
%0h:%0m:%0s%x
$
0
,
.
1
2
YUGOSLAVIA
35
%Y-%0m-%0d
%0t:%0m:%0s
Din
2
.
,
1
2
P represents the currency symbol position. The possible values are as follows:
0=prefix
1=prefix with a space
2=suffix
3=suffix with a space
T represents the thousands separator.
D represents the decimal indicator.
N represents the negative number format The possible values are as follows (1 represents the number and $
represents the currency symbol):
• 0=($1)
• 1=-$1
• 2=$-1
Planning and Installing AppBuilder for the Mainframe
page 33 of 284
• 3=$1​
• 4=(1$)
• 5=-1$
• 6=1-$
• 7=1$​
DP represents the default number of decimal places displayed.
Monitoring Data Set Space Allocations
Several data sets need to be monitored for adequate space allocation, particularly during periods of heavy
application development. An example is when developers are re-preparing all rules for an application just before
migrating an application from the development region to the testing region.
While the space allocation for all data sets should be watched, those approaching capacity should be noted and
acted on. Keep an eye on all AppBuilder user data sets and panel and view files. The following list contains
AppBuilder data sets that may exceed 90% and should be monitored:
&USRVQUAL..LOADBT (Batch)
&USRVQUAL..NCALBT (Batch)
&USRVQUAL..LOADCI (CICS)
&USRVQUAL..NCALCI (CICS)
&USRVQUAL..LOADIM (IMS)
&USRVQUAL..NCALIM (IMS)
We recommend the repository administrator or AppBuilder tool/environment support analyst develop and run a batch
job periodically (perhaps weekly, depending on the volume of activity at your site) to check for at least these three
things:
1. Which AppBuilder data sets (PDS) are over 90% full? Also, which are with directory blocks that are more than
90% used?
2. Which AppBuilder files (VSAM) have over 75 extents?
3. What AppBuilder VSAM volume is over 90% full?
Observe the data sets approaching their capacities. When you have answers to the three questions above, take
appropriate action to relieve space problems.
Question 1: several actions are available---compress the PDS, add directory blocks, and/or add tracks.
Question 2: work with systems programmers to expand the VSAM data sets. The expansion requires their
deallocation from CICS (unless the VSAM is batch) and about 30 minutes downtime. Because of the
downtime, first notify the application developers. Also, ensure that no CASIM migrations are running during
the expansion activity.
Question 3: the REORG jobs that run nightly at most sites may reallocate the space. If not, coordinate this
work with your onsite DASD group.
It is also important to ‘clean up’ the repository by deleting orphaned objects. Orphan objects are candidates for
deletion from the repository because they are obsolete and take up valuable space. Some users run orphan reports
to identify the objects unrelated to other objects. A program of periodic clean up reduces data set space allocation
problems.
Planning and Installing AppBuilder for the Mainframe
page 34 of 284
Installation Requirements
This section summarizes the hardware and software prerequisites and corequisites for the AppBuilder Host
Development Workbench. See the checklists in Appendix E, “Hardware and Software Checklists” to verify that your
system is ready to install AppBuilder.
Planning and Installing AppBuilder for the Mainframe
page 35 of 284
Hardware and DASD Requirements
Table 3-1 Shows the hardware requirements for the AppBuilder Host Development Workbench.
Table 3-1
Hardware requirements
Mainframe Model
IBM z Systems
Communications
TCP/IP protocol
Media
Optical Drive (for DVD) or FTP download
Table 3-2 Shows the DASD cylinder allocations for the base AppBuilder Host Development Workbench and its
optional products. The DASD cylinder allocations are based on a DASD class of 3390.
Note
Approximate DASD allocations for AppBuilder are derived from AppBuilder's QA testing, and limited
to specified parameters. Customers should consider their own experience, normal system usage, and
growth when determining their overall DASD requirements.
Table 3-2
DASD cylinder allocations
AppBuilder Host Development Workbench
AppBuilder Enterprise Repository (Base)
This is the DASD requirement to install and use base AppBuilder Host
Development Workbench (Enterprise Repository, Host Installation
Workbench, and one repository version) for approximately 6 months.
3000 cylinders (total), comprised
of: 1700 cylinders for base
software and one repository
version
1050 cylinders for DB2 data sets
250 cylinders for temporary work
data sets
DASD cylinder allocation for each additional repository version
660 cylinders per version
(includes repository software and
data for each version)
Optional products
CICS Online Preparation Workbench and Enterprise Server
70 cylinders for data sets 250
cylinders for backups
15 cylinders per repository version
CICS 3270 Converse Preparation Workbench
5 cylinders for data sets 250
cylinders for backups
Mainframe Batch Preparation Workbench
60 cylinders for data sets 250
cylinders for backups
15 cylinders per repository version
Mainframe Report Writer Preparation
5 cylinders for data sets 250
cylinders for backups
Planning and Installing AppBuilder for the Mainframe
page 36 of 284
IMS Online Preparation Workbench and Enterprise Server
70 cylinders for data sets 250
cylinders for backups
15 cylinders per repository version
IMS 3270 Converse Preparation Workbench
5 cylinders for data sets 250
cylinders for backups
Planning and Installing AppBuilder for the Mainframe
page 37 of 284
Supported Third-party Products
For the latest information, contact AppBuilder Support (appbuildersupport@magicsoftware.com) or visit the
AppBuilder Support website (support.appbuilder.com). On the website refer to the Documemtation section and Third
Party Support Matrix.
Planning and Installing AppBuilder for the Mainframe
page 38 of 284
Host Installation Workbench
This section describes how to use the AppBuilder 3.4 Host Installation Workbench.
Planning and Installing AppBuilder for the Mainframe
page 39 of 284
Using the Host Installation Workbench
All host installation is done through the Host Installation Workbench (HIW), an ISPF dialog that provides installation
and maintenance functions for AppBuilder systems and repositories. Once HIW is installed on a mainframe machine
it can be used to manage an unlimited number of systems and repositories resident on the same machine. In this
sense, HIW is considered global.
Another feature is the decoupling of the repository and system. The system contains the AppBuilder software in mod
level and base level libraries and the INI members @MVSENV and @SEERENV. The repository includes the DB2
database, user data sets (VSAM and non-VSAM) and repository data sets including the INI members @HPSENV,
@INSTENV, @HPSSTAT, @USRENVn, @RBDENVn and @MIGENVn. One system can support many
repositories, allowing the addition of repositories as growth demands it without the re-installation of system software.
Topics include:
Maintenance History Log File
INI Files
Repository - System Association
Enable and Disable Functions
Displaying Information about Systems and Repositories
Installation Data Sets
Installation Notes
Installation Procedure
Packing List
You should have received the following software package either as a DVD or a download from the AppBuilder
Support FTP site. If you did not receive all the pieces listed below, please contact AppBuilder Support.
AppBuilder V3.4 that contains the following:
The installation, system and repository software in 10 sub-directories (Bootstrp, CG, DF, HD, HI, IV, RW, SB,
TP, & SV or SX)
Two FTP scripts (abftpboot and abftppc)
Readme PDF document (with release notes)
Maintenance History Log File
The primary control mechanism for the workbench is the Maintenance History Log file (MHLOG) which exists at the
global (HIW) level. It is a sequential file containing records which detail the application of AppBuilder releases at the
system, repository and version level. The file is updated via two HIW programs - ILOG001 and ILOG002 - and should
not be updated manually. The integrity of the file is crucial to smooth operation of the workbench, therefore the file
should be backed up. The following table details the record layout of MHLOG. Please note that all fields are
character.
Table 4-1
Maintenance History Log file record layout
Col 001 to 001:
Record Type (1 system, 2 repository, 3 version)
Col 002 to 009:
System ID
Col 010 to 017:
Repository ID
Col 018 to 019:
Version ID
Planning and Installing AppBuilder for the Mainframe
page 40 of 284
Col 020 to 027:
Release ID
Col 028 to 033:
Product ID
Col 034 to 034:
Version Optional Indicator
Col 035 to 035:
Roll-up Indicator
Col 036 to 036:
Disregard Indicator
Col 037 to 044:
“Cloned From” System ID
Col 045 to 052:
“Associated From” System ID
Col 053 to 069:
Timestamp for start of an action (clone etc.)
Col 070 to 086:
Timestamp for completion of software applied.
Col 087 to 103:
Timestamp for completion of clone system
Col 104 to 120:
Timestamp for completion of backout
The MHLOG file is initially delivered with a DUMMY record as the first record so that the file will never be empty.
This record should be left in place.
Table 4-2
MHLOG field descriptions
Field
Description
Record
type
A 1 in this column indicates a system record - that is, a record of an action performed on a
system. A 2 in this column indicates a repository record and a 3 indicates a version record. A
record is kept for each software release that is applied to a system, repository and version.
System ID
The system name. Each system must be identified by a unique name of up to 8 characters. The
system name must be a valid PDS member name.
Repository
ID
The repository name. Each repository must be identified by a unique name of up to 8 characters.
The repository name must be a valid PDS member name. A repository name cannot be the
same as a system name.
Version ID
The version number.
Release ID
This is the short release name i.e. AB34 or SVB34 which identifies each release of AppBuilder
software.
Product ID
This identifies the product line to which a release belongs.
Version
Optional
Indicator
This flag designates releases that may be optionally applied to a version. It is for AppBuilder use
only.
Rollup
Indicator
If a release includes other releases in it this column will be set to “Y”.
Disregard
Indicator
This column may be used to indicate a release which affects system software only.
Planning and Installing AppBuilder for the Mainframe
page 41 of 284
Clonedfrom
SystemID
This column is not currently used.
Associatedfrom
SystemID
If a repository is moved from one system to another, the source SYSID will be here. This allows
tracking of the repository history.
Timestamp
The four timestamp fields are populated when the indicated actions are performed. If the backout
timestamp is populated, the record will be displayed as “DELETED” when the software history is
viewed.
Another HIW file that is populated during installation is &GLOBQUAL..USER.CLIST (See GLOBQUAL in Chapter 2
for an explanation of the qualifier &GLOBQUAL under Installing Components). The PDS contains one member for
each system and repository. The member has the same name as the entity it describes. The members hold minimal
information needed to describe the entity to HIW. Note that since the system and repository members are in the
same PDS, all systems and repositories must have unique names.
INI Files
The AppBuilder V3.4 correlation of the environmental CLIST is the INI file. Control variables are not accessed via
the ISPF variable pools but are read directly into the active program space from PDS members called INI files. The
INI PDS exists at the &BASEQUAL, &MODQUAL and &REPQUAL levels. The INI members which contain systemwide parameters are @MVSENV and @SEERENV. Variables which pertain to (and should vary between)
repositories are held in @HPSENV and @INSTENV. Variables which pertain to a specific version are held in
@USRENV, @MIGENV, and @RBDENV. The concatenation of the three PDS levels allows flexibility in altering
variables: If a system variable such as the Enterprise PL/I compiler name is to be changed and checked out against
a single repository, the member @MVSENV should be copied up to the @REPQUAL level where the variable
change will affect only the repository described by &REPQUAL..* A change at the &BASEQUAL or &MODQUAL will
affect all repositories associated with the system described by &BASEQUAL..* and &MODQUAL..*.
Repository - System Association
Each repository is associated with a system when it is created. That means that the repository “runs off of” the copy
of AppBuilder software in a given system. The association is accomplished by the setting of the variables
&BASEQUAL and &MODQUAL in @HPSENV. These variables act as pointers to the related system libraries. The
association based on these variables is also expressed in the repository allocation clist HPSALLOC, the skeleton
TSODD and the panel ISR@PRIM. HIW includes a facility for selecting a different system to be associated with a
repository. This action is called Associate Repository and is available on the Repository Workbench menu.
The Associate Repository action could be performed in the following scenario:
Repository R1 is associated with system S1 which is at the AB32 level. System S2 is created using AB32 and then
upgraded with the optional release of AB34. Repository R1 can be associated with System S2 and then upgraded
to AB34, preserving the applications in the repository. This would be an alternative approach to creating new
repository R2 associated with system S2 and then migrating applications from R1 to R2.
Association is only allowed between a repository and a system that is at the same or higher level of software as the
repository. If any product or release has been applied to a repository, the repository cannot be associated with a
system which does not have that product or release. If a repository is associated with a system which has products
or releases applied to it that are not applied to the repository, the repository will be disabled pending upgrade to the
software level of the target system.
Planning and Installing AppBuilder for the Mainframe
page 42 of 284
Enable and Disable Functions
HIW provides the means to enable and disable a repository or version. This function can be used to prevent access
to a resource while it is being maintained. The Enable/Disable Repository action is selected from the Repository
Workbench menu; the Enable/Disable Version action is accessed from the Maintain Version menu. The repository
variable Enable is kept in the INI member @HPSSTAT; the version variable is kept in the @USRENVn INI member.
The repository variable has precedence; an enabled version cannot be accessed within a disabled repository.
Displaying Information about Systems and Repositories
HIW provides two ways to display information about systems and repositories. The Display Software History function
is available from both the System Workbench and Repository Workbench menus. This function reads information
from the MHLOG file pertaining to the specified system or repository and formats it for display. Information about
each release applied is presented in chronological order indicating whether the release was backed out. The List
Systems and Repositories function, also available from either workbench, provides an overview of all systems and
repositories and their associations. The repository status column indicates whether the repository is enabled or
disabled. Repositories which are not currently associated with any system are indicated with a status of “ORPHAN”.
A status of “UNKNOWN” indicates a possible problem with the MHLOG which could be due to an aborted release or
processing failure and should be resolved.
Planning and Installing AppBuilder for the Mainframe
page 43 of 284
Installation Job Processing
HIW employs ISPF tables to control processing of installation jobs. After the release software is unloaded using the
System Workbench, a job table is created which displays the jobs needed to install the release. Some of the jobs
may be optional such as the tape backup job. Others are required. HIW enforces the order in which the jobs are run
by checking the Status column in the job table. A job cannot be run until its prerequisite job has completed
successfully. To ensure smooth job processing it is essential to submit the jobs from the job table panel rather than
from a TSO edit session. Jobs that must be altered should be edited and saved, then submitted from the job panel.
When a job has completed successfully, the Status column will be updated to reflect this. Repository processing is
similar and involves two tables. The first table presented is the installation table and includes all releases which are
needed to bring the repository in line with the system software. These must be selected in order. Within each release
there will be a table of jobs needed to complete that release. Processing of this table is identical to the system
function.
Installation Data Sets
Several data sets are created during installation to hold generated jobs and file tailored items which are copied to
production via batch jobs---for example, INI files. These data sets follow the naming conventions described here:
System jobs and members are written to data sets beginning with &INSTQUAL..&RELNUM where &RELNUM is the
release name such as AB34, SVB34 etc. and &INSTQUAL has the value entered for the system. Generated jobs are
written to &INSTQUAL..&RELNUM..CNTL. Generated members, such as edit macro drivers, are written to
&INSTQUAL..&RELNUM..ICLIST.
Since many repositories can be created from one system, the repository installation jobs are kept in separate data
sets for each repository. These data sets are &INSTQUAL..&REPOSID..&RELNUM..CNTL for optional releases, and
&INSTQUAL..&REPOSID..CNTL for the base release (AB34). File tailored output is written to one of two data sets
depending on the required DCB. Examples follow for a repository called NEWRISE where &INSTQUAL is
“SS0221.INSTALL”:
Table 4-3
Sample Repository Data Sets
SS0221.INSTALL.NEWRISE.CNTL
SS0221.INSTALL.NEWRISE.SVC34.CNTL
SS0221.SVC34.INSTALL.NEWRISE.ICLIST
SS0221.INSTALL.NEWRISE.ISPFREP
holds repository creation jobs for base release
holds file tailored output with FB DCB
holds repository jobs for release
holds file tailored output with DCB same as
client’s CLIST data set (VB if required)
Note
Note Data sets ending in IREP4TB*, IREP400A, ISYS150M and ISYS4TB* hold the job tables.
Planning and Installing AppBuilder for the Mainframe
page 44 of 284
Backing Out a Release
Backing Out a Release
Each PTF includes a job to back out the release by restoring backed up data sets (note that this only works if the
optional backup job is run) and completing the deletion timestamp in the MHLOG record. Backout accomplishes
reversion to the state prior to installation except with respect to the MHLOG file which is updated rather than
reverted. With respect to an initial installation of a release such as AppBuilder 3.4 Host Development Workbench
which creates new AppBuilder data sets, there is no backed-up software to restore. Therefore, to back out an initial
AppBuilder installation the user should delete all data sets beginning with &INSTQUAL, &BASEQUAL, &MODQUAL,
&REPQUAL, &USRQUAL, &VSMQUAL and &VSUVQUAL. In addition, the MHLOG records for the deleted system
or repository should be removed from the log file to allow the system or repository to be re-added in the future. Also,
the entry in &GLOBQUAL..USER.CLIST should be deleted for completeness.
Prerequisites
Refer to Appendix E, "Hardware and Software Checklists" and Appendix F, "Host Installation Workbench
Customization Worksheets" in this document to prepare for this installation.
Planning and Installing AppBuilder for the Mainframe
page 45 of 284
Installation Notes
The installation procedure described in this document is as follows:
1. Install AppBuilder Host Installation Workbench software.
2. Install AppBuilder Enterprise Repository software, as described in "Installing Enterprise Repository" .
a. Install the system portion of AppBuilder Enterprise Repository software.
Create System
First you must perform Option 1, Create System.
b. Install the repository portion of AppBuilder Enterprise Repository software.
Create Repository
The AppBuilder Host Installation Workbench (HIW) software is used to install all subsequent AppBuilder software on
an IBM mainframe. After HIW software is installed, it also provides functions for reviewing and maintaining your
AppBuilder software. For information on HIW post-installation options, see the AppBuilder Enterprise Administration
Reference Guide .
Using the AppBuilder Host Installation Workbench, you can stop an installation after the successful completion of
any function, then return to the next function later. You can also install the system portions of multiple AppBuilder
products before continuing with the repository functions. Figure 4-1 shows the order in which AppBuilder software is
installed. To use the chart, locate the software you wish to install. Read from left to right to see which AppBuilder
software must be installed prior to the software you want to install.
Note
The AppBuilder Host Installation Workbench and the AppBuilder Enterprise Repository must be
installed before any other AppBuilder mainframe-based software is installed.
Figure 4-1 Software installation order
The outline below shows all AppBuilder Host Installation Workbench function options you will use to install
AppBuilder Enterprise Repository software. Option steps must be completed successfully in order. Use the check
boxes provided here to keep track of your completed installation steps.
Planning and Installing AppBuilder for the Mainframe
page 46 of 284
Table 4-4 Host Installation Workbench function options
Option 1—System functions
Create system software
Unload installation data sets
Perform installation
Capture system variables
Unload AppBuilder software
Create system installation jobs
Submit system installation jobs
Option 2—Repository functions
Create repository
Create installation table
Process installation table
Capture repository values
Create repository installation jobs
Submit repository installation jobs
Activate repository
Planning and Installing AppBuilder for the Mainframe
page 47 of 284
Installing the Host Installation Workbench
Before you can install Host Installation Workbench software, content must be transferred to the mainframe via FTP.
The basic steps in this process are:
1) Create a PDS dataset on the mainframe (RECFM=FB, LRECL=80) and transfer the contents of the BOOTSTRP
folder via FTP to this PDS on the mainframe. A sample FTP batch file is provided called ABFTPBOOT.TXT. Edit
and run it using the following command: ftp -s:abftpboot.txt
2) After you upload the BOOTSTRP folder to the PDS, edit and submit job ABXMTALC to allocate all the XMIT
datasets that you will need for the next step.
3) Edit and run ABFTPC.TXT to FTP all the XMIT files to the mainframe. Use the following command: ftp s:abftpc.txt
4) In the PDS created in step 1 above, edit member INSBOOT according to the instructions at the top of the
member: change the string DIALOG.DSNAME in line 14 to the name of the data set created in step 1. Do not make
any other edits.
5) Execute the member INSBOOT from the ISPF environment using the TSO EXEC command. For example, TSO
EXEC hqual.DIALOG(INSBOOT). The Bootstrap Information panel will be displayed for you to enter the workbench
installation information. After entering the information, you will see a job stream displayed for edit in the UNLOAD
member. Edit the job card information in the job stream and submit the job.
6) After the UNLOAD job completes successfully the following datasets will be created and received:
&globqual..CLIST
&globqual..CNTL
&globqual..LNKT
&globqual..LOADLIB
&globqual..MHLOG
&globqual..MSGS
&globqual..OBJ
&globqual..PANELS
&globqual..ROLLUPS
&globqual..SKELS
&globqual..TABLES
&globqual..USER.CLIST
7) The installation of the AppBuilder Host Installation Workbench is now complete. You can then use the Installation
Workbench to install all other AppBuilder software.
8) To start the installation of the AppBuilder Enterprise Repository execute the INSTART member in the same
DIALOG dataset. You must execute this in the ISPF environment. For example, type from the COMMAND prompt in
ISPF: EX ‘AB.INS34.DIALOG(INSTART)’
Planning and Installing AppBuilder for the Mainframe
page 48 of 284
Installing Enterprise Repository
The information in this section describes the detailed requirements and procedures for installing an AppBuilder
Enterprise Repository.
Planning and Installing AppBuilder for the Mainframe
page 49 of 284
Prerequisites
Refer to Appendix E, "Hardware and Software Checklists" and Appendix G, "Enterprise Repository Customization
Worksheets" to prepare for this installation.
Packing List
You should have received the following software. If you did not receive all the pieces listed below, please contact
AppBuilder Distribution.
AppBuilder REL 3.4
Readme document entitled: Readme.pdf
Planning and Installing AppBuilder for the Mainframe
page 50 of 284
Installation Notes for the Enterprise Repository
The installation procedure is as follows:
1. Install AppBuilder Host Installation Workbench software. (See "The Host Installation Workbench" for
installation instructions.)
2. Install AppBuilder Enterprise Repository software.
1. Install the system portion of AppBuilder Enterprise Repository software. First you must perform Option
1, Create System.
2. Install the repository portion of AppBuilder Enterprise Repository software.
Note
Only function options which will be used to install AppBuilder Enterprise Repository are described.
Using the AppBuilder Host Installation Workbench, you can stop an installation after the successful completion of
any function, then return to the next function later. You can also install the system portions of multiple AppBuilder
products before continuing with the repository functions. Figure 5-1 shows the order in which AppBuilder software is
installed. To use the chart, locate the software you wish to install. Read from left to right to see what AppBuilder
software must be installed prior to the software you want to install.
Note
The AppBuilder Host Installation Workbench and the AppBuilder Enterprise Repository must be
installed before any other mainframe-based software is installed.
Figure 5-1
AppBuilder Installation Order
Planning and Installing AppBuilder for the Mainframe
page 51 of 284
Installing the AppBuilder Enterprise Repository
To begin installing the Enterprise Repository, you must first start up the Host Installation Workbench.
Starting the Host Installation Workbench
1. To start the Host Installation Workbench, execute the REXX member INSTART located in the DIALOG data
set. You must execute INSTART in the ISPF environment. For example, type from the COMMAND prompt in
ISPF:
EX 'AB.INS34.DIALOG(INSTART)'
2. After the INSTART REXX executes, it displays the main panel for AppBuilder Host Installation Workbench--Workbench Functions, shown in Figure 5-2.
Note
For this installation, the installer’s TSO session must have a minimum memory allocation of 6
MB.
3. There are two major steps to installing AppBuilder software: Option 1 - System Functions and Option 2 Repository Functions. Installing system functions is described next, and installing repository functions is
described in Option 2 - Repository Functions.
Figure 5-2 Workbench Functions
Option 1 - System Functions
The system function portion of an AppBuilder software installation occurs first. This portion of the installation allows
you to customize AppBuilder software to access your mainframe environment.
1. Enter 1 on the option line, as shown in Figure 5-3. The Create System Software option creates a new full
installation of AppBuilder base system software. This option is only used for AppBuilder Enterprise Repository
software.
200.1 Enter the System ID of the new system [Default: None]
Planning and Installing AppBuilder for the Mainframe
page 52 of 284
Specify up to eight (8) alphanumeric characters per system name for your AppBuilder base system
software. This name will be used to associate your AppBuilder base system software to one or more
AppBuilder repositories. It must be a valid PDS member name which does not exist in the PDS
&globqual..USER.CLIST. Refer to "The Host Installation Workbench" section "Repository - System
Association” for more information.
2. Press Enter. If you entered an existing System ID, a panel appears informing you that the ID already exists.
You can then either specify that you want to enter another ID, or continue using the existing ID.
Figure 5-3 System Functions
Option 1 - Create System Software
Figure 5-4 shows the Create System Software panel. It allows you to create a new installation of AppBuilder base
system software. In its first option, Option 1 - Unload Installation Datasets, you enter data needed to create the
unload JCL. In the second option, Perform Installation, you enter data needed to install and customize the software
for your site.
Figure 5-4 Create System Software
Option 1 - Unload Installation Datasets
1. Select option 1 Unload Installation Datasets in the panel in Figure 5-4 and press Enter.
2. Figure 5-5 is displayed. Enter the requested information and press Enter to continue. After entering the data
set information, if a duplicate data set name qualifier is detected, a panel is displayed alerting you to this
situation. You must either select (N) and enter another qualifier or (Y) to allow the duplicate data sets to be
deleted and recreated.
3. A panel is displayed to edit the Job Control card information. Edit if necessary and press Enter to continue.
4. The unload job is brought up in an edit session. Review and edit, if necessary. Submit the JCL by typing SUB
at the command prompt. Verify the job completed successfully. This job creates the following data sets:
Planning and Installing AppBuilder for the Mainframe
page 53 of 284
&instqual..AB34.CNTL
&instqual..AB34.ICLIST
&instqual..AB34.IPANELS
&instqual..AB34.ISKELS
where &_instqual_ is the value entered for the prompt in step 200.2 below.
5. After the job completes successfully, select option 2 Perform Installation in Figure 5-4 and press Enter.
See Perform Installation for more information.
Figure 5-5 Unload Installation Data Sets
6. Enter the following information:
200.2
Enter Installation Dataset Qualifier [Default: AB1.INSTALL]
Enter the name of the installation data set qualifier. This must be a different qualifier than that entered for
100.1. This qualifier defines data sets that hold the AppBuilder system and repository installation software.
Enter a maximum of 17 characters.
200.3
Enter System Dataset Qualifier [Default: AB1.BASE]
Enter the name of the system data set qualifier. This qualifier defines data sets which hold the AppBuilder
system software. Enter a maximum of 17 characters.
200.4
Enter Maintenance Dataset Qualifier [Default: AB1.MOD]
Enter the name of the maintenance data set qualifier. This qualifier defines data sets which are created empty
and can be used to hold client modifications or product fixes received from AppBuilder. Enter a maximum of 17
characters.
200.5
Enter System VSAM data set qualifier [Default: AB1.BASE]
Enter the name of the system VSAM data set qualifier. This qualifier defines VSAM data sets which are part of
the AppBuilder system software and not specific to a repository. Enter a maximum of 17 characters.
200.6
Enter language for Messages & Panels [Default:ENU]
Planning and Installing AppBuilder for the Mainframe
page 54 of 284
Enter the language code for the messages and panels. Enter ENU (English) or JPN for double byte characters
(Japanese).
200.7
Enter the AppBuilder Release Name [Default: None]
You must enter AB34. This code indicates which AppBuilder product you are installing.
200.8 200.9 200.10
200.11
No Action
Enter the DASD Unit for AppBuilder Datasets [Default: SYSDA]
Enter the DASD unit for AppBuilder data sets.
200.12
Enter the DASD Volume for AppBuilder Datasets (Optional) [Default: None]
Enter the DASD volume for AppBuilder data sets, if applicable.
200.13
Enter the following for VSAM data sets if they apply:
Enter either a volume or management class.
200.13a
Volume [Default: SYSDA]
Enter the volume for VSAM data sets, if applicable.
200.13b
Management class [Default: None]
Enter the management class for VSAM data sets, if applicable.
200.14
Create FB or VB Clists for SYSPROC DD? (F/V) [Default: F]
Specify if the SYSPROC DD concatenation uses F (fixed block) or V (variable block) CLISTS.
200.15
If VB, specify LRECL and BLKSIZE:
If V (variable block CLISTs) entered in step 200.14, enter the required LRECL and BLKSIZE.
200.15a
LRECL [Default: None]
Enter the record length if variable blocked CLISTs are used in step 200.14 (LRECL).
200.15b
BLKSIZE [Default: None]
Enter the block size if variable blocked CLISTS are used in step 200.14 (BLKSIZE).
Perform in sequence the following four options in Figure 5-6.
Perform Installation
Figure 5-6
Perform Installation Menu Options
Planning and Installing AppBuilder for the Mainframe
page 55 of 284
Option 1 - Capture System Variables
1. Select option 1, “Capture System Variables” to display a series of mainframe environment panels. Panel
explanations begin with step 200.16 and end with step 200.72.
2. In each panel, customize the variables for your environment as needed. Press Enter.
Figure 5-7
Capture System Variables — MVS Environment, panel 1 of 9
200.16
LE Link Library [Default: CEE.SCEELKED]
Enter the name of the LE Link Library.
200.17
LE Runtime Library [Default: CEE.SCEERUN]
Enter the name of the LE Runtime Library.
200.18
PL/I Call Library [Default: CEE.SIBMCALL]
Enter the name of the PL/I Call Library.
200.19
PL/I Math Library [Default: blank]
Enter the name of the PL/I Math Library. If you do not use a PL/I Math Library, leave it blank.
200.20
COBOL II Compiler Library [Default: IGY.SIGYCOMP]
Enter the name of the COBOL II Compiler Library.
200.21
Include STEPLIB in the Cobol Compile step (Y/N)? [Default: Y]
Do you want to include STEPLIB in the COBOL Compile step of rule preparation?
200.22
COBOL II Compiler Name [Default: IGYCRCTL]
Planning and Installing AppBuilder for the Mainframe
page 56 of 284
Enter the name of the COBOL II Compiler.
Required Parameters
[Default: 'TRUNC(BIN)',LIB,'FLAG(W)']
You cannot change the required parameters.
Optional Parameters
[Default: LIST]
You can modify the optional parameters to conform to your site specifications. The parameters that appear are
needed for compiles within the product. The required and optional parameters are associated with CPARM1 and
CPARM2 in the @MVSENV ini member and CPARM1 will be concatenated with CPARM2.
For Double Byte sites, the DBCS parameter should be added to the Optional parameter list.
200.23
H Assembler Name [Default: ASMA90]
Enter the Assembler H program name.
Required Parameters
[Default: NODECK,OBJECT]
You cannot change the required parameters.
Optional Parameters
[Default: LIST]
You can modify the optional parameters to conform to your site specifications. The parameters that appear are
needed for compiles within the product. The required and optional parameters are associated with APARM1 and
APARM2 in the @MVSENV ini member and APARM1 will be concatenated with APARM2.
For Double Byte sites, the DBCS parameter should be added to the Optional parameter list.
3. Enter all information in the required data fields, then press Enter
Figure 5-8 Capture System Variables — MVS Environment, panel 2 of 9
Planning and Installing AppBuilder for the Mainframe
page 57 of 284
200.24
Mainframe Macro Libraries [Default: SYS1.MACLIB]
Enter the mainframe Macro library names.
200.25
Mainframe Distribution MGEN Library [Default: SYS1.AMODGEN ]
Enter the name of the mainframe Distribution MGEN library.
200.26
Mainframe Target MGEN Library (Optional) [Default: SYS1.MODGEN ]
Enter the name of the mainframe Target MGEN library if the IBM default name is not used.
200.27
Is the PL/I Compiler Installed? [Default: N]
Specify if the PL/I compiler is installed. If not installed, the following PL/I items are optional. Enter Y or N.
200.28
PL/I Compiler Library [Default: IBMZ.SIBMZCMP]
Enter the name of the PL/I Compiler Library.
200.29
200.30
Include STEPLIB in the PL/I Compile step? (Y/N ) [Default: Y]
PL/I Compiler Name [ Default: IBMZPLI]
Enter the PL/I Compiler name. Define the required and optional parameters needed by the PL/I Compiler.
Required Parameters
[Default: INC,OP,AG,NEST,STMT,GRAPHIC,'OPTIMIZE(TIME)']
You cannot change the required parameters.
Optional Parameters
[Default: 'A(F)','X(F)',MAP,OF,STG]
200.31 200.32 No Action
Planning and Installing AppBuilder for the Mainframe
page 58 of 284
You can modify the optional parameters if necessary. Optional parameters are concatenated with required
parameters.
4. Enter all information in the required data fields, then press Enter to advance to the next panel in the mainframe
environment (see Figure 5-9).
Figure 5-9 Capture System Variables — MVS Environment, panel 3 of 9
200.33
C Compiler Library [Default: CBC.SCCNCMP]
Enter the name of the library that contains the C Pre-link module EDCPRLK.
For Version 3.4, this will be in the compiler library.
200.34
C Messages [Default: CEE.SCEEMSGP(EDCPMSGE)]
Enter the library containing the C/370 compiler messages.
200.35
Enter the following if you will be creating C components.
Steps 200.33 thru 200.35c are optional. They are only required if C components will be written.
200.35a
200.35b
Include STEPLIB in the C compile step? (Y/N) - [Default: Y]
C Compiler Name [Default: CCNDRVR]
Enter the name of the C compiler.
200.35c
C Headers [Default: CEE.SCEEH.H]
Enter the library containing the C header files.
200.36
TCPIP SEZATCP Library [Default: TCPIP.SEZATCP]
200.37
TCPIP SEZACM TX Library [Default: TCPIP.SEZACMTX]
5. Enter all information in the required data fields, then press Enter.
Figure 5-10
Capture System Variables — MVS Environment, panel 4 of 9
Planning and Installing AppBuilder for the Mainframe
page 59 of 284
200.38
Sort Program [Default: SORT]
Enter the sort program name.
200.39
Access Method Program [Default: IDCAMS]
Enter name if not IDCAMS.
200.40
Access Method Library (optional) [Default: None]
Enter library only if access method is not IDCAMS.
200.41
PDS Utility Program [Default: IEBCOPY]
Enter the name of the PDS copy utility program if not IEBCOPY.
200.42
PDS Utility Library (optional) [Default: None]
Enter the library name only if PDS copy utility program is not IEBCOPY.
Note
If this value is blank, you must manually edit the @MVSENV INI file and set the IEBLIB variable to
‘N/A’.
200.43
Reason Code from LISTDSI if Dataset is Not Found [Default: 5]
If a third party package translates return codes from TSO LISTDSI, specify the TSO LISTDSI equivalent. [5] is
returned by TSO LISTDSI. Used to designate the reason code from LISTDSI for data sets that are not found.
200.44
Is Dataset Archival Software such as HSM Used? (Y/N ) [Default: Y]
Specify if data set archival software is used on this system.
200.44a
Name of Program to Delete Archived Data Set [Default: HDELETE]
If “Y” entered for step 200.45, (data set archival software used) enter the name of the program used to delete
archived data sets.
200.44b
Delete Program Parameter String [Default: PURGE WAIT]
Planning and Installing AppBuilder for the Mainframe
page 60 of 284
If “Y” entered for step 200.45, (data set archival software used) enter the delete program parameter string.
200.44c
Reason Code Issued if Data Set is Migrated [Default: 9]
If “Y” entered for step 200.45, (data set archival software used) enter the return code issued if the data set is
migrated.
200.45a
Use a separate step for DB2 preprocessor? (Y/N ) [Default: N]
Specify if a separate DB2 preprocessor step is to be used.
200.45b
Use a separate step for CICS translator? (Y/N ) [Default: N]
Specify if a separate CICS translator step is to be used.
6. Enter all information in the required data fields, then press Enter to advance to the next panel in the mainframe
environment.
Figure 5-11
200.46
Capture System Variables — MVS Environment, panel 5 of 9
Linkage Editor AMODE [Default: 31]
Enter the addressing mode of AppBuilder generated modules.
200.47
Linkage Editor RMODE [Default: ANY]
Enter the residency mode of AppBuilder generated modules.
The following table lists valid and invalid combinations of AMODE and RMODE.
Table 5-1
Valid and Invalid Combinations of AMODE and RMODE
RMODE
AMODE
24
ANY
24
valid
invalid
31
valid
valid
Planning and Installing AppBuilder for the Mainframe
page 61 of 284
ANY
200.48
valid
invalid
Link Pack Area Library [Default: SYS1.LPALIB]
Enter the library name of the link pack area if not SYS1.LPALIB.
200.49
DB2 Load Library [Default: DSNA11.SDSNLOAD]
Enter the name of the DB2 load library that has the DSN command processor.
200.50
DB2 Link Library [Default: DSNA11.SDSNLINK]
Enter the name of the DB2 link library that will be used to link DB2 programs.
200.50a
DB2 Exit Library [Default: DSNA11.SDSNEXIT]
Enter the name of the DB2 exit library.
200.51
DB2 Preprocessor Name [Default: DSNHPC]
Enter the DB2 preprocessor program name.
200.52
Include STEPLIB in the DB2 Preprocessor step? (Y/N) [Default: Y]
200.53
DB2 Utility Proc Name [Default: DSNUPROC]
Enter the DB2 utility procedure name.
200.54
DB2 Utility Load Library [Default: DSNA11.SDSNLOAD]
Enter the DB2 load library that contains the load module DSNUPROC or its equivalent at your site.
200.55
ISPF Link Library [Default: ISP.ISPLOAD]
The name of the ISPF link library used to link AppBuilder ISPF modules.
Note
ISPF library names should not be left blank.
200.56
ISPF Profile Library [Default: None]
The name of the common ISPF table library that contains member ISPPROF.
200.57
Specify Mainframe Codepage [Default: 037]
The codepage is a number assigned by IBM to designate the character set in each country. It defines which
character will be produced on a display or printer for a given byte value (0 to 255). Many of these are unvarying
across codepages, but some produce different results--- for example, the value that produces a dollar sign in the US
shows as a monetary pound sign in the UK. Specify the host codepage for your national language.
200.58
Specify PC Codepage -[Default: 437]
Enter the PC codepage used on the development workstation. 437 is default codepage for US or UK English: 850 is
the MLS codepage (US and UK English, French, Spanish, Italian, German, Danish, etc.). The [NLS] Codepage_OS2
value can be found on the development workstation in \HPS\HPS.INI.
200.59
Specify AIX Codepage [Default: 2]
Enter the AIX codepage used on the development workstation: IS08859-1.
200.60
PC Equivalent of ‘AT’ Character [Default: @]
Planning and Installing AppBuilder for the Mainframe
page 62 of 284
If the codepage you have selected does not support the “@” character, enter the character that maps to the
equivalent host value (for example, the character EBCDIC hex 7C is mapped to on the host).
200.61
Default Language for Repository Objects (Abbreviation) [Default: ENU]
Enter the default language abbreviation for the repository objects. For example, ENU means US English.
The following table lists valid codepage and default language combinations between mainframe, PC and AIX,
referenced by items 200.54, 200.55, 200.56, and 200.58.
Table 5-2
Valid Codepage and Default Languages
Mainframe
PC
Default language abbreviation
037
437, 850, 860, 863
FRC, NLD, ENU, PTF, PTB, ENA
273
437, 850
DEU
280
437, 850
ITA
284
437, 850
ESP
297
437, 850
FRA
500
437, 850
FRS, DES, FRB, NLB
838
437, 874
THA
277
865, 850
DAN, NON, NOR
278
437, 850
FIN, SVE
285
437, 850
ENG
930
942
JPN
933
949
KOR
939
942
JPN
Note
The host install supports the DBCS codepages IBM930 (Japanese), IBM939 (Japanese) and IBM933
(Korean). If the IBM930 codepage is used, lower case SBCS characters cannot be used in any of the
text and keywords. Text encompasses rule source, windows, sets and help files. If the IBM939
codepage is
used, half-width Katakana characters are not supported in text, keywords, and all object names.
The following table provides the definitions of default language abbreviations used in the proceeding table.
Table 5-3
Definition of Default Language Abbreviations
Default Language Abbreviation
Language
DAN
Danish
DEU
German
Planning and Installing AppBuilder for the Mainframe
page 63 of 284
DES
Swiss German
ENA
Australian English
ENG
UK English
ENU
US English
ESP
Spanish
FIN
Finnish
FRA
French
FRB
Belgian French
FRC
French Canadian
FRS
Swiss French
ITA
Italian
JPN
Japanese
KOR
Korean
NLB
Belgian Dutch
NLD
Dutch
NON
Nynorsk Norwegian
NOR
Bokmal Norwegian
PTB
Brazilian Portuguese
PTG
Portuguese
SVE
Swedish
THA
Thai
7. Enter all information in the required data fields, then press Enter.
Figure 5-12
Capture System Variables — MVS Environment, panel 6 of 9
Planning and Installing AppBuilder for the Mainframe
page 64 of 284
200.62
Default Retrieval Format for DB2 DATE Values [Default: ISO ]
Specify the retrieval format of DB2 DATE values. Valid values are:
EUR--- IBM European Standard
ISO---International Standards Organization
JIS---Japanese Industrial Standard
USA---IBM USA Standard
LOCAL---Site defined
200.63
If a LOCAL Date Format is used, enter it Here [Default: None]
Specify the DB2 date format if LOCAL specified in the previous step. This value must match the DATE format
defined when DB2 was installed at your site. Example: % Y-% 0m-% 0d--- year-month-day.
200.64
Default Retrieval Format for DB2 TIME Values [Default: ISO ]
Specify the retrieval format of DB2 TIME values. Valid values are:
EUR--- IBM European Standard
ISO---International Standards Organization
JIS---Japanese Industrial Standard
USA---IBM USA Standard
LOCAL---Site defined
200.65
If a LOCAL Time Format is used, Enter it Here [Default: None]
Specify the DB2 date format if LOCAL specified in the previous step. This value must match the TIME format
defined when DB2 was installed at your site. Example: % 0t.% 0m.% 0s---hour.minute.second.
200.66
Maximum Nested IF statements in HPS Rules [Default: 40]
Specify the maximum level allowed for nesting IF statements consecutively. When rules code exceeds this limit,
severe error #87959 will occur.
200.67
Retention Period for Tape Datasets in Days [Default: None]
Specify the number of days tape data sets will be kept. Input is required in this field.
8. Enter all information in the required data fields, then press Enter.
Figure 5-13
Capture System Variables — MVS Environment, panel 7 of 9
Planning and Installing AppBuilder for the Mainframe
page 65 of 284
These screens request names for CLIST and ISPF libraries, used when running TSO in background mode
(IKJEFT01). Enter the name of at least one library for each of the following.
Note
If more than five libraries are required for each concatenation, you must manually edit the TSODD
skeleton found in &REPQUAL..FTSKEL.
200.68
SYSPROC [Default: None]
Enter the CLIST libraries (SYSPROC) for background TSO jobs.
200.69
ISPPLIB [Default: None]
Enter the ISPF PANEL libraries (ISPPLIB) for background TSO jobs.
9. Enter all information in the required data fields, then press Enter.
Figure 5-14
Capture System Variables — MVS Environment, panel 8 of 9
Planning and Installing AppBuilder for the Mainframe
page 66 of 284
Enter the names of at least one library for each of the following. These libraries will be included in AppBuilder batch
jobs and must include the ISPF libraries.
200.70
ISPMLIB [Default: None]
Enter the ISPF MESSAGE libraries used for background TSO jobs.
200.71
ISPSLIB [Default: None]
Enter the ISPF SKELETON libraries used for background TSO jobs. Continue to the next panel.
10. Enter the names of at least one library for each of the following. These libraries will be included in AppBuilder
batch jobs and must include the ISPF libraries.
Figure 5-15
200.72
Capture System Variables — MVS Environment, panel 9 of 9
ISPTLIB [Default: None]
Enter the ISPF TABLE libraries used for background TSO jobs.
200.73
The ISPLLIB entries are optional. Omit if not used at your site. [Default: None]
Enter the optional ISPL libraries used for background TSO jobs.
1. After entering the appropriate libraries, press Enter to return to the Create System Software panel in Figure 516. With successful completion, the message “VARIABLES CREATED” appears in the top right corner of this
panel.
Figure 5-16 Create System Software Menu
Planning and Installing AppBuilder for the Mainframe
page 67 of 284
Option 2 - Unload AppBuilder Software
1. From the Create System Software panel, select option 2 Unload AppBuilder Software.
Note
After entering the data set information, if a duplicate data set name qualifier is detected, a panel is
displayed alerting you to this situation. Select (N) to enter another qualifier or (Y) to allow the
duplicate data sets to be deleted and recreated.
Figure 5-17
Unload System Software
2. A panel displays Job Control Card information. Edit if necessary and press Enter.
Planning and Installing AppBuilder for the Mainframe
page 68 of 284
3. The unload job is brought up in an edit session. Review and edit if necessary. Submit JCL by typing SUB at
the COMMAND prompt. Verify that jobsteps have completed with a return code of "0". Some steps use the
IEBCOPY utility and will have a return code of "4" because there is a missing member. You should check for
missing members because these members are used later in the product. If you cannot find the member, take note of
it and report it to the AppBuilder Solutions Service Line. Then continue with job by verifying that all members are
copied and all steps have completed. This job creates the data sets in Table 5-4 through Table 5-7.
&BASEQUAL is the value you entered in prompt 200.3.
&MODQUAL is the value you entered in prompt 200.4.
&VSMQUAL is the value you entered in prompt 200.5.
&INSTID is the installer’s TSO userid. This is the data set qualifier used for the Migration data sets as shown
in Table 5-6 and Table 5-7.
Table 5-4
Base Libraries
&BASEQUAL..CGCGINC
&BASEQUAL..CGTABLE
&BASEQUAL..CHDR
&BASEQUAL..CLIST
&BASEQUAL..COPYASM
&BASEQUAL..COPYC
&BASEQUAL..COPYCOB
&BASEQUAL..COPYPL1
&BASEQUAL..CSOURCE
&BASEQUAL..DBRMLIB
&BASEQUAL..DDL
&BASEQUAL..DDLVSAM
&BASEQUAL..ERESFILE.LOADRECS
&BASEQUAL..EHPSFILE.LOADRECS
&BASEQUAL..FTSKELS
&BASEQUAL..ERRMSG
&BASEQUAL..INIDFTIN
&BASEQUAL..INI
&BASEQUAL..LKBS00
&BASEQUAL..LANGCFG
&BASEQUAL..LOADLIB
&BASEQUAL..LKBSEC
&BASEQUAL..MESSAGIN
&BASEQUAL..MSGS
&BASEQUAL..OBJ
&BASEQUAL.OLDOC
&BASEQUAL.OLINST
&BASEQUAL.OLMSGS
&BASEQUAL..PANELS
&BASEQUAL..PCKGBASE
&BASEQUAL..PCKGRANT
&BASEQUAL..PLANBASE
&BASEQUAL..PLKOBJ
&BASEQUAL..PRELINK
&BASEQUAL..PRTLOG
&BASEQUAL..RMIJCL
&BASEQUAL.SAMPLE
&BASEQUAL.SAMP255
&BASEQUAL.SAMP80
&BASEQUAL..SKELS
&BASEQUAL..TABLES
&VSMQUAL..INIDFT
&VSMQUAL..MESSAGES
Planning and Installing AppBuilder for the Mainframe
page 69 of 284
Table 5-5
Maintenance Libraries
&MODQUAL.CGTABLE
&MODQUAL..CLIST
&MODQUAL..DBRMLIB
&MODQUAL..FTSKELS
&MODQUAL..INI
&MODQUAL..LOADLIB
&MODQUAL..MSGS
&MODQUAL..OBJ
&MODQUAL...PANELS
&MODQUAL..PLKOBJ
&MODQUAL..SKELS
Table 5-6
Default Repository
&INSTID..DF.MIG.ELOGKEY
&INSTID..DF.MIG.EMIG
&INSTID..DF.MIG.ENTITY
&INSTID..DF.MIG.INMIG
&INSTID..DF.MIG.KEYWORD
&INSTID..DF.MIG.MIGCNTL
&INSTID..DF.MIG.MIGXX
&INSTID..DF.MIG.RELATE
&INSTID..DF.MIG.RLOGKEY
&INSTID..DF.MIG.SOURCE
&INSTID..DF.MIG.SRCBDAT
&INSTID..DF.MIG.SRCBHDR
&INSTID..DF.MIG.TEXT
Table 5-7
Test Installation Process ( TIP ) Application
&INSTID..TP.MIG.ELOGKEY
&INSTID..TP.MIG.EMIG
&INSTID..TP.MIG.ENTITY
&INSTID..TP.MIG.INMIG
&INSTID..TP.MIG.KEYWORD
&INSTID..TP.MIG.MIGCNTL
&INSTID..TP.MIG.MIGXX
&INSTID..TP.MIG.RELATE
&INSTID..TP.MIG.RLOGKEY
&INSTID..TP.MIG.SOURCE
&INSTID..TP.MIG.SRCBDAT
&INSTID..TP.MIG.SRCBHDR
&INSTID..TP.MIG.TEXT
Option 3 - Create System Installation Jobs
1. The Create System Software panel (Figure 5-16) opens. Select option 3 Create System Installation Jobs.
2. The panel in Figure 5-18 is optional. If it does not appear, proceed to step 3. If the panel does appear, it
indicates this system was started but not completed.
Figure 5-18
Create System Installation Jobs
Planning and Installing AppBuilder for the Mainframe
page 70 of 284
This panel indicates the jobs to install this system have already been generated but not completed. In this panel,
you can choose to:
• Type N and press Enter to complete the system generation in progress. In this case, you proceed to the next step
in the process, "Option 4-Submit System Installation Jobs."
• Type Y and press Enter to abandon the installation in progress and begin again. In this case, you continue with
this process and perform step 3.
3. A panel displays Job Control Card information. Edit if necessary, and press Enter.
4. When the system installation jobs are created, a message appears in the top right corner of the panel in
Figure 5-19. You will see either “JOBS CREATED” for a successful creation or an error message
for unsuccessful creation.
Option 4 - Submit System Installation Jobs
1. From the Create System Software panel, select option 4 Submit System Installation Jobs.
2. A panel displays Job Control Card information. Edit if necessary and press Enter.
3. The panel in Figure 5-19 appears. This panel lists the installation jobs that are ready to be submitted. Submit
each job in order from the top down. Enter SUB to submit a job for processing. Confirm that each job posts a
“COMPLETED” status before progressing. Enter V or VIEW to display a job.
Figure 5-19
Submit Installatin Jobs
Planning and Installing AppBuilder for the Mainframe
page 71 of 284
4. When all jobs have completed successfully, you have completed the System Functions installation. Press F3
repeatedly to return to the starting panel. You return through the hierarchy of installation windows to the Create
System Software panel.
5. Having successfully completed the System Functions settings, you should continue the installation of the
software by completing the Option 2 - Repository Functions installation.
Planning and Installing AppBuilder for the Mainframe
page 72 of 284
Option 2 - Repository Functions
This option installs the repository portion of the Enterprise Repository. You must complete option 1 System
Functions as shown in Figure 5-2
Figure 5-20 Repository Functions Main Menu
Option 1 - Create Repository
1. Select option 1 Create Repository and press Enter.
200.74
Enter the repository ID (name) of the new repository.
Specify up to eight (8) alphanumeric characters per repository name for your AppBuilder repository software. This
name will be associated with your AppBuilder base system software which was created during the System Functions
installation. (Refer to "The Host Installation Workbench" for more information.)
In the example used in this document, “repname” is used as a sample repository name and “sysname” is used as a
sample system name. Panels displayed on your system will display the repository name you have entered.
200.75
Enter the System ID which will be associated with the new repository [Default: None]
Warning
The Repository ID name cannot be the same as the System ID.
2. Enter X or press End to exit the panel.
3. If a duplicate repository name is detected, the following panel will appear:
Figure 5-21
Create Repository Panel
Planning and Installing AppBuilder for the Mainframe
page 73 of 284
4. Press Enter to continue with the installation. The newly-created member in this installation will overwrite
the existing one.
5. Press End to enter another repository ID. You will return to the panel shown in Figure 5-20.
Create Installation Table
There are three steps you must follow in the Create Repository process.
1.
Associate the repository with a system ID, as Figure 5-22 shows.
Figure 5-22
Associating a System ID and the new repository
Figure 5-23
Create Installation Table Options.
Planning and Installing AppBuilder for the Mainframe
page 74 of 284
This panel shows a completion message in the top right corner. Select option 2 to start processing the installation
table.
Process Installation Table
Process all releases in order. If you installed the system portion of more than one release, those items will appear in
the list. Otherwise, only AB34, shown in Figure 5-24, will appear. Make your selection by typing S or SEL in the
Action column next to the desired release.
Figure 5-24
Selecting the Installation Table
Capture Repository Variables
This section allows you to customize variables pertaining to database, job,migration, and user environments at your
site. Complete all three steps in order.
1.
Choose option 1 to start processing repository variables.
Figure 5-25
Selecting the Capture Repository Variables
Planning and Installing AppBuilder for the Mainframe
page 75 of 284
The panel in Figure 5-25 is optional. If it does not appear, proceed to "Capture DB2 Information". If the panel
appears, it means this installation was started but not completed.
Figure 5-26 Create Repository Installation Jobs
This panel indicates the jobs to install this repository have already been generated but not completed.
This panel lets you choose:
• Type N and press Enter to complete the repository installation in progress. In this case, you proceed to the next
step in the process, “Submit Repository Installation Jobs”.
• Type Y and press Enter to abandon the installation in progress and begin again. In this case, you continue with this
process and perform “Capture DB2 Information”.
Capture DB2 Information
Planning and Installing AppBuilder for the Mainframe
page 76 of 284
After selecting, Option 1---Capture Repository Variables, the panel shown in Figure 5-27 will appear. A total of five
panels will appear, each allowing you to customize repository variables. Use this panel to capture information about
your DB2 environment.
Figure 5-27 Capture Repository Variables---DB2 environment, panel 1 of 5
Enter the required information appropriate to this installation. Specify all data about your DB2 installation and press
Enter.
200.76
DB2 Subsystem ID [Default: DSN ]
Enter the subsystem ID where AppBuilder DB2 objects will reside.
200.77
DB2 Object Creator ID [Default: <Installer’s ID>]
Enter the creator or owner ID for all AppBuilder system tables. This ID can either be the installer’s ID or a secondary
auth ID.
200.78
DB2 Plan Owner ID [Default: Installer’s ID]
Enter the DB2 Plan Owner ID. This ID can either be the installer’s ID or a secondary auth ID for the installers’ ID. For
an upgrade, this must be a different ID than INST1ADM.
200.79
AB Database Name [Default: AB34]
Enter the name of the database in which AppBuilder system DB2 objects are to reside.
200.80
DB2 VCAT or Storage Group [Default: None]
Specify whether VCATs or storage groups are used. Enter V for VCAT or S for storage groups. V - you create VSAM
manually, S creates objects in an existing storage groups and VSAM is automatically created.
200.81
DB2 Storage Group Name [Default: None]
If you chose “S” (storage group) in step 200.80, enter the storage group name of an existing storage group you want
to use.
200.82
DB2 VCAT Name [Default: None
Planning and Installing AppBuilder for the Mainframe
page 77 of 284
If you chose “V” (VCAT) in step 200.80, enter the VCAT name.
200.83
Volume ID for DB2 Tablespaces [Default: None]
If you chose VCAT in step 200.80, enter the DASD device where AppBuilder DB2 tablespaces are to be stored. The
same volume name can be used for DB2 tablespaces and indexspaces.
200.84
Volume ID for DB2 Indexspaces [Default: None]
If you chose VCAT in step 200.80, enter the DASD device where HPS’ DB2 indexspaces are to be stored. The same
volume name can be used for DB2 tablespaces and indexspaces.
200.85
DB2 Plan name and Collection ID for repository software [Default: None]
Enter the DB2 Plan name (also known as the Collection ID) for the repository software. There is a maximum limit of
8 characters.
200.86
Owner of Application DB2 Tables [Default: &SYSUID]
Enter the owner ID of the AppBuilder application tables.
200.87
Repository ID [Default: None]
Enter the unique two-character alphabetical suffix used in AppBuilder short name object generation.
200.88
Number of Versions [Default: 1]
Enter the number of versions or partitions within the repository. You may define a minimum of 1 and a maximum of
10 versions per enterprise repository. Additional versions can be installed. Individual versions require additional
allocations of DASD as non-DB2 data sets must be allocated for each version.
Capture Data Set Information
Panels 2 and 3 deal with the data set specifications. Panel 2 is shown in Figure 5-28.
Figure 5-28
Capture Repository Variables---Data sets, panel 2 of 5
Planning and Installing AppBuilder for the Mainframe
page 78 of 284
Enter the required information appropriate to this installation. Specify the information about your data sets and press
Enter . The next panel, Figure 5-29, completes the data set specifications.
200.89
Specify the prefix for each of these non-versioned data sets:
Enter a prefix for each of the following. The prefix entered will be used in the data set name at your site. All variables
support more than one node.
200.89a
Repository Modification [Default: AB1.REP]
Enter the repository modification data set prefix. This qualifier defines data sets which hold information specific
to a given repository. You can also use these data sets to hold software modifica​t ions which are to affect only
one repository. Enter a maximum of 18 characters.
200.89b
User Datasets [Default: AB1.USER]
Enter the user data set prefix. This qualifier defines data sets which hold user application information for
specific repository versions. Enter a maximum of 17 characters.
200.89c
VSAM User [Default: AB1.USER]
Enter the VSAM data set prefix. This qualifier defines VSAM data sets which hold user application runtime
information for CICS, IMS, and Batch. Enter a maximum of 17 characters.
200.89d
Temporary Output [Default: TEMP.NN ]
Enter the temporary output data set prefix. This qualifier defines data sets that will be generated by the user
while working in the AppBuilder Enterprise Repository. May be a maximum of 10 characters, with the final node
being seven (7) characters or less since it is specific to a repository version. The repository version number is
concatenated to the final node.
Note
The &SYSUID variable is not allowed to be used as part of the prefix.
200.89e
User-ID (Short-term) [Default: &SYSUID]
Enter the prefix for output user ID data sets which are short-term, to a maximum of 18 characters. This qualifier
defines data sets that will be generated by the user while working in the AppBuilder Enterprise Repository. This
value must contain the &SYSUID variable since it is specific to each user. For example, you can specify
HPS.&SYSUID.
200.89f
User-ID (Permanent) [Default: AB1OUT]
Enter the prefix for user output data sets that are permanent or long-term. This qualifier defines data sets that
will be generated by the user while working in the AppBuilder Enterprise Repository. May be a maximum of 10
characters.
Note
The &SYSUID variable is not allowed to be used as part of the prefix.
200.90
Should VIEW Copybooks Include Alignment Bytes? (Y/N ) [Default: N]
Specify if VIEW copybooks should include alignment bytes.
Figure 5-29
Capture Repository Variables---Data sets, panel 3 of 5
Planning and Installing AppBuilder for the Mainframe
page 79 of 284
Enter the required information appropriate to this installation. Specify the units and volume IDs for the permanent,
temporary, and VIO data sets. Press Enter.
200.91
Permanent data sets
Enter the following information for permanent data sets.
200.91a
Unit [Default: SYSDA]
Enter the name of the direct access storage device that will store AppBuilder permanent data sets.
200.91b
Volume ID Required? [Default: N]
If pool DASD is used (that is, JCL parameter VOL=SER is not used), then enter N and leave Permanent
Volume ID blank. Otherwise, enter Y and a volume ID.
200.91c
Volume ID [Default: None]
Enter the Volume ID.
200.92
Temporary data sets
Enter the following information for temporary data sets.
200.92a
Unit [Default: SYSDA]
Enter the name of the direct access storage device that will store AppBuilder temporary data sets.
200.92b
Volume ID Required? [Default: N]
If pool DASD is used (JCL parameter VOL=SER not used), enter N and leave Temporary Volume ID blank. If
DASD must be specified, enter Y and a volume ID.
200.92c
Volume ID [Default: None]
Enter the Volume ID.
200.93
VIO data sets
Enter the following information for VIO data sets.
200.93a
Unit [Default: SYSDA]
Planning and Installing AppBuilder for the Mainframe
page 80 of 284
Enter the name of the direct access storage device that will store AppBuilder VIO data sets.
200.93b
Volume ID Required? [Default: N]
If pool DASD is used (that is, JCL parameter VOL=SER is not used), then enter N and leave VIO Volume ID
blank. If DASD must be specified, then enter Y and a Volume ID.
200.93c
Volume ID [Default: None]
Enter the Volume ID.
Capture Job Parameters
Enter the JOB Parameters information appropriate to this installation. Then press Enter in the following panel shown
in Figure 5-30.
Figure 5-30
200.94
Capture Repository Variables---JOB Parameters, panel 4 of 5
Job Class (CLASS) [Default: 1]
Enter the JCL Job Class used for user-submitted jobs through the repository interface.
200.95
Message Class (MSGCLASS) [Default: A]
Enter the JCL Message Class used for user-submitted jobs through the repository interface.
200.96
Time Parameter (TIME) [Default: None]
Enter the JCL time parameter if required for the job card.
200.97
Priority (PRTY) [Default: 12]
Enter the JCL priority parameter if required for the job card.
200.98
Region size (REGION ) [Default: 4M ]
Enter the JCL region size parameter if more than 4M is required.
200.99
Default Jobname Suffix Character [Default: M ]
Planning and Installing AppBuilder for the Mainframe
page 81 of 284
Enter a default JCL suffix character.
200.100
Default Job Description [Default: JOB]
Enter a default job description for AppBuilder jobs.
200.101
Overnight Job Class [Default: 1]
Enter the job class used to defer jobs for overnight execution.
200.102
SYSOUT Class for Batch Jobs [Default: *]
Enter SYSOUT class for batch job processing and batch reports.
200.103
Internal Reader Name [Default: INTRDR]
Enter the name of the internal reader if different from the default name.
200.104
Internal Reader Output Class [Default: 1]
Enter the output class for the internal reader.
200.105
Default Printer [Default: None]
Enter default printer ID to be used for printing reports.
200.106
Use Customized Job Card Skeleton [Default: N]
Specify Y or N to use a customized job skeleton.
200.107
Batch JOB Submission Option [Default: Y]
Specify Y to submit jobs automatically or N to save jobs in a data set. The JCL will be saved in data set
&USRVQUAL..JCL. To override this, specify the fully qualified data set name in the INI variable called
JCLDSN in &REPQUAL..INI(@HPSENV). Y or N for an external scheduling interface.
200.108
Is there an External Scheduling Interface? [Default: N ]
Enter the default value only. Enter the required information appropriate to this installation and press Enter.
Capture Batch File Allocations
The last panel, page five of five, specifies batch file allocations, as shown in Figure 5-31.
Figure 5-31
Capture Repository Variables---Batch File Allocations, panel 5 of 5
Planning and Installing AppBuilder for the Mainframe
page 82 of 284
Specify the batch file allocations by entering Y or N to include or exclude the specified parameters. Press Enter.
200.109
Include the STEPLIB DD in batch jobs?
Specify Y or N if the STEPLIB DD should be included in batch jobs.
200.110
Include the STEPLIB DD in non-DB2 steps?
Specify Y or N if the STEPLIB DD should be included in non-DB2 steps.
200.111
Include each of the following in STEPLIB:
Specify with Y or N whether to include each of the following in STEPLIB. TSODD is a batch job skeleton.
200.111a
DB2 Load Libraries [Default: Y]
Specify if the DB2 load libraries should be in the STEPLIB of TSODD.
200.111b
MODQUAL Load Library [Default: Y]
Specify if the AppBuilder modification load libraries should be in the STEPLIB of TSODD.
Capture Migration Information
The next three panels allow you to customize your migration environment. Figure 5-32 defines the general
environment.
Figure 5-32
200.112
Capture Repository Variables---Migration Environment, panel 1 of 3
Specify the CICS or IMS Transaction ID Option:
Specify the following option, as appropriate. The following are valid values: S-Use Source ID, T-Use Target ID, BBlank.
200.112a
CICS [Default: T]
Specify the CICS transaction ID option.
Planning and Installing AppBuilder for the Mainframe
page 83 of 284
200.112b
IMS [Default: T]
Specify the IMS transaction ID option.
200.113
Default Migration Dataset High Level Qualifier [Default: HPSOUT]
Enter the default migration data set high level qualifier. May be a maximum of 8 characters.
200.114
Analyze Collisions During Import? (Y/N ) [Default: Y]
Specify if collisions are analyzed during import.
200.115
Analyze Collisions on SYSTEMID or LONGNAME?(S/L) [Default: L]
Specify if collisions are analyzed on SYSTEMID or LONGNAME.
200.116
Process User Exits During Migration? (Y/N) [Default: N ]
Specify if user exits are processed during migration.
200.116a
If ‘Y’ Enter Name of Optional Exit Rexx Exec [Default: None]
If ‘Y’ is selected, enter the name of the exit REXX.
200.116b
Will COPYAPP function be used? (Y/N) [Default: N ]
Specify if the Copyapp function will be used.
Figure 5-33 defines default options and user modification capabilities; they require Y or N to specify whether the user
can modify the migration options, as shown in Figure 5-33.
Figure 5-33
200.117
migration:
Capture Repository Variables---Migration Environment, panel 2 of 3
For each of the following enter Y to include the item in a migration or N to exclude it from
Enter Y or N for the following
200.117a
Default Option for ‘Create’ Entities (Y/N) [Default: Y]
Specify Y or N to allow default option for ‘Create’ entities.
Planning and Installing AppBuilder for the Mainframe
page 84 of 284
200.117b
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the ‘Create’ entities option. ‘
200.117c
Default Option for ‘Update’ Entities (Y/N ) [Default: Y]
Specify Y or N to allow default option for ‘Update’ entities.
200.117d
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the ‘Update’ entities option.
200.117e
Default O ption for ‘Delete’ Entities (Y/N) [Default: Y]
Specify Y or N to allow default option for ‘Delete’ entities.
200.117f
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the ‘Delete’ entities option.
200.117g
Default Option for Source (Y/N ) [Default: Y]
Specify Y or N to allow default option for Source.
200.117h
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the Source option.
200.117i
Default Option for Keywords (Y/N) [Default: Y]
Specify Y or N to allow default option for Keywords.
200.117j
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the Keywords option.
200.117k
Default Option for Text (Y/N ) [Default: Y]
Specify Y or N to allow default option for Text.
200.117l
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the Text option.
Enter the required information appropriate to this installation. Press Enter.
The last page defines whether the user can modify the import step, rebuild analyzer, rebuild prepare, and rebuild
install, as shown in Figure 5-34.
Figure 5-34
Capture Repository Variables---Migration Environment, panel 3 of 3
Planning and Installing AppBuilder for the Mainframe
page 85 of 284
200.118
Enter Y to include the following steps in MIGRATE method processing or N to exclude them:
Enter Y or N for the following.
200.118a
Include IMPORT Step? (Y/N ) [Default: N]
Specify Y or N to include the IMPORT step.
200.118b
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the include IMPORT step option.
200.118c
Include REBUILD Analyzer? (Y/N ) [Default: N]
Specify Y or N to include the REBUILD Analyzer.
200.118d
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the include REBUILD Analyzer option.
200.118e
Include REBUILD Prepare? (Y/N) [Default: Y]
Specify Y or N to include the REBUILD Prepare.
200.118f
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the include REBUILD Prepare option.
200.118g
Include REBUILD Install? (Y/N) [Default: Y]
Specify Y or N to include the REBUILD Install.
200.118h
Can the User Modify this Option? (Y/N ) [Default: N]
Specify Y or N whether the user can modify the include REBUILD Install option.
200.118i
Include REBUILD Export? (Y/N) [Default: N ]
Specify Y or N to include the REBUILD Export.
200.118j
Can the User Modify this Option? (Y/N ) [Default: N]
Planning and Installing AppBuilder for the Mainframe
page 86 of 284
Specify Y or N whether the user can modify the include REBUILD Export option.
Enter the required information appropriate to this installation. Press Enter .
Capture Server Information
The next panel allows you to customize your migration and preparation server environments. Figure 5-34a defines
the general environment.
Figure 5-34a
Capture Repository Variables---Server environment, panel 1 of 1
Capture User Information
The last two panels define your user environment. (Two panels appears for each version you are asked to create.)
Figure 5-35 shows the application DB2 environment, configuration units, and begins the list of user libraries for
component preparations.
Figure 5-35
Capture Repository Variables---User Environment, panel 1 of 2
Planning and Installing AppBuilder for the Mainframe
page 87 of 284
200.119
Application DB2 environment
200.119a
Support DB2 Packages? (V/N /P) [Default: N ]
Specify V or P to support DB2 packages. N indicates that packages are not supported. V indicates DB2
packages will be supported for all the projects within a repository version. P indicates DB2 packages will
be supported per project within a repository version. Please refer to the Enterprise Administration Guide
for more information on DB2 package support.
200.119b
If V or P, specify Collection ID [Default: None]
If using packages, specify the default Collection ID for this repository version.
200.119c
If V or P, specify Owner ID [Default: None]
If using packages, specify the default Owner ID for this repository version.
200.119d
If V or P, specify Qualifier ID [Default: None]
If using packages, specify the default Qualifier ID for this repository version.
200.119e
If V or P, specify Plan Name [Default: None]
If using packages, specify the default Plan Name for this repository version.
200.119f
If V or P, specify E if a Package List is Required or W if the Wildcard (*) is Supported
(E/W ) [Default: W]
If you use Packages, specify E to require an explicit package list or specify W to support the asterisk (*)
for wildcards for this repository version.
200.119g
Perform GRANT as part of Prepare Method? (Y/N ) [Default: Y]
Specify Y or N to perform GRANT as a part of the Prepare method.
200.119h
Use Partitions for Preparation? (Y/N ) [Default: N]
Specify Y or N to use configuration units for preparation.
Figure 5-36 completes the list of user libraries for component preparations.
Figure 5-36
Capture Repository Variables---User Environment, panel 2 of 2
Planning and Installing AppBuilder for the Mainframe
page 88 of 284
Optional User Libraries for Component Prepares
200.120
Optional User Libraries for Component Prepares
Enter the following library names.
200.120a
NCAL Batch Library [Default: None]
Define the NCAL batch library.
200.120b
NCAL CICS Library [Default: None]
Define the NCAL CICS library.
200.120c
NCAL IMS Library [Default: None]
Define the NCAL IMS library.
200.120d
Other NCAL Library [Default: None]
Define the other NCAL batch library.
200.120e
Batch Load Library [Default: None]
Define the batch load library.
200.120f
CICS Load Library [Default: None]
Define the CICS load library.
200.120g
IMS Load Library [Default: None]
Define the IMS load library.
200.120h
Other Load Library [Default: None]
Define the other load library.
Planning and Installing AppBuilder for the Mainframe
page 89 of 284
200.120i
ASM Copylib [Default: None]
Define the ASM copylib.
200.120j
COBOL Copylib [Default: None]
Define the COBOL copylib.
200.120k
C Copylib [Default: None]
Define the C language copylib.
200.120l
PL/I Copylib [Default: None]
Define the PL/I copylib.
200.120m ASM DCLGEN [Default: None]
Define the ASM DCLGEN.
200.120n
COBOL DCLGEN [Default: None]
Define the COBOL DCLGEN.
200.120o
CDCLGEN [Default: None]
Define the C Language DCLGEN
200.120p
PL/I DCLGEN [Default: None]
Define the PL/I DCLGEN.
The two panels defining the user environment complete the series of ten panels that capture repository variables. At
the end of series Figure 5-37 appears. Press Enter to continue the installation.
Figure 5-37
Variables Captured
Create Repository Installation Jobs
Planning and Installing AppBuilder for the Mainframe
page 90 of 284
Continuing the installation, you return to the panel in Figure 5-23 to create installation jobs. Initiate this action by
selecting option 2 in the panel. A “JOBS CREATED” message should appear in the top right corner when the action
has completed.
If the installation software detects existing DB2 data sets, the panel in Figure 5-38 appears.
Figure 5-38
Drop Database
Submit Repository Installation Jobs
Continuing the installation, you return to the panel in Figure 5-16 to submit installation jobs. Initiate this action by
selecting option 4. Figure 5-39 appears.
Figure 5-39
Submit Installation Jobs
From this panel, you can either view or submit the jobs. Type V or VIEW to examine the results of the job creation
for correctness. When ready, type SUB to submit it for processing. To modify a job, split the screen and edit. After
saving the member, return to the “Submit Installation Jobs” panel to submit the job.
The Status column will display either one of two messages for submitted jobs--- ‘SUBMITTED’ (in process) or
‘COMPLETED’. Submit all jobs in order.
Note
Ensure that each job completes before submitting the next one.
The jobs and their purposes are:
Planning and Installing AppBuilder for the Mainframe
page 91 of 284
REPJOB--- handle all the non-DB2 work, such as allocating repository data sets. This job creates the
following data sets:
In Table 5-8 &REPQUAL is the value defined in Figure 5-26 for the prefix of the Repository Modification data sets.
Table 5-8
Repository modification libraries
&REPQUAL..CGTABLE
&REPQUAL..CLIST
&REPQUAL..DBRMLIB
&REPQUAL..FTSKELS
&REPQUAL..INI
&REPQUAL..LOADLIB
&REPQUAL..MSGS
&REPQUAL..OBJ
&REPQUAL..PANELS
&REPQUAL..SKELS
In Table 5-9 there can be more than one set of user libraries if the Number of Versions was set to more than one.
Refer to Figure 5-19 and the panel entry for Number of Versions. &USRVQUAL is the qualifier used for AppBuilder
user level data sets that are versioned. The value for &USRVQUAL is contained in &REPQUAL..INI(@USRENVn),
where n is the version number of the repository.
Table 5-9
User libraries
&USRVQUAL..APPLDBRM
&USRVQUAL..CGTABLE
&USRVQUAL..COPYASM
&USRVQUAL..COPYC
&USRVQUAL..COPYCOB
&USRVQUAL..COPYPL1
&USRVQUAL..DCLGNC
&USRVQUAL..DCLGNCOB
&USRVQUAL..DCLGNPL1
&USRVQUAL..JCL
&USRVQUAL..LOADBS
&USRVQUAL..NCALBS
&USRVQUAL..SETC
&USRVQUAL..SETCOB
&USRVQUAL..SETERR
&USRVQUAL..SETPL1
&USRVQUAL..SETREF
&USRVQUAL..VIEWASM
&USRVQUAL..VIEWASMA
&USRVQUAL..VIEWC
&USRVQUAL..VIEWCA
&USRVQUAL..VIEWCOB
&USRVQUAL..VIEWCOBA
&USRVQUAL..VIEWPL1
&USRVQUAL..VIEWPL1A
DB2 OBJ---create the DB2 objects. This job creates the following data set: &USRVQUAL.TRAN.
DB2 BIND---bind the DB2 plans
When you finish submitting all jobs and the status of each is “COMPLETED”, press F3 until the panel in
Figure 5-33 reappears.
Activate Repository
Planning and Installing AppBuilder for the Mainframe
page 92 of 284
Figure 5-40 shows the screen appearing next. Choose option 3 to activate the new repository.
Figure 5-40
Create Repository choices appearing after creating an installation table
Wait for the activation of the repository to complete. A confirmation message in the top right corner notifies you
when it is complete.
Planning and Installing AppBuilder for the Mainframe
page 93 of 284
Postinstallation Notes
Perform the following steps to complete and verify the successful installation of the AppBuilder Enterprise
Repository.
1. Edit your ISPF Primary Option Menu panel to allow access to the Enterprise Repository. Replace
&REPQUAL, &MODQUAL, &BASEQUAL, and &VSMQUAL with the qualifiers shown in Figure 5​-5 and
Figure 5-28. Replace &OCLASS with the output class to be used for SYSOUT data sets to be allocated during
a TSO session. For an example of where to edit these items, see segments of a sample ISR@PRIM in Figure
5-41a and Figure 5-41b.
Figure 5-41a Main ISPF/PDF Options Panel - Sample ISR@PRIM
Planning and Installing AppBuilder for the Mainframe
page 94 of 284
A,'CMD(%HMFISPF &REPQUAL &MODQUAL &BASEQUAL +
&VSMQUAL &ZPLACE N &OCLASS) NEWAPPL(HRIS) NOCHECK'
Note
If the &ZPLACE variable is used, make sure it is initialized with a valid value.
2. Copy the repository CLIST from &REPQUAL..CLIST to a data set included in the SYSPROC concatenation of
AppBuilder users’ TSO sessions.
3. Edit the member HPSALLOC in &REPQUAL..CLIST to remove unwanted data sets or add more data sets to
the ISPF library concatenations. These concatenations are in effect for AppBuilder TSO sessions for all users
and should not contain any data sets that are exclusively for the AppBuilder installer’s TSO session. It also
contains the ISPF command to display an ISPF main panel. If this is not used at your location, edit
HPSALLOC with the appropriate command.
Note
Refer to the @HPSENV INI file in the INI Settings Reference Guide for the values of these
two variables.
4. At the TSO Ready prompt, enter the name of the repository CLIST to set up your TSO session to use
AppBuilder and to allow you to invoke AppBuilder software from a primary ISPF panel (ISR@PRIM).
5. Make sure to set your PF (function) keys to 24 before invoking AppBuilder. After you invoke the AppBuilder
option from the primary ISPF panel, select option 1 to invoke the AppBuilder Enterprise Repository from the
AppBuilder Main Option panel.
Note
You need to repeat steps 6 through 13 for each version of the repository.
6. A window will appear with a list of projects and corresponding versions that your ID can access. The
installer’s ID will have access to the AppBuilder and ADM projects. Select the ADM project for version A.
7. Next to the Users entity, type LE (List Entities) to list the users in the repository. At this point only the
installer’s ID is listed. Type ME (Maintain Entity) next to the installer’s ID to update the job accounting
information for your site. After entering required information, press F3 to save and return. Be certain to update
the installer’s ID for each of the versions listed.
8. Next to the Groups entity, type ADDE (Add Entity) to add the TIP (Test Installation Process) group to the
repository. After entering required information, press F3 to save and return.
9. Next to the Projects entity, type ADDE to add TIP project to the repository. Select the "AB Model" for the
type field. After entering the required information, press F3 to save and return.
10. Next to the Groups entity, type LE to list groups. Next to the TIP group, type ADDR to add the installer’s ID to
the TIP group. The Relation type will be option 5 “Has-As-A-Member User” and press Enter. Set “User
Authority Level” to 1 for Project Leader. After entering required information, press F3 to save and return.
11. Next to the Groups entity, type LE to list groups. Next to the TIP group type ADDR (Add Relationship) to add
the TIP project to the TIP group. The Relation type will be option 4 “Has Project” and press Enter. Set Method
Name and Scope to *, and set Scope Mode to 1 for include. After entering required information, press F3 to
save and return.
Planning and Installing AppBuilder for the Mainframe
page 95 of 284
12. Migrate TIP:
a. Within the Enterprise Repository, type PROJECTS at the command line, and select TIP
for version 1.
b. Next to the Migration entity, type ADDE to create a migration entity for TIP (TIP is the
application that verifies installations). For the migration data set prefix, enter
&INSTID..TP, where &INSTID is the installer’s User ID. After entering required information,
press F3 to save and return.
c. Next to the Migration entity type LE to list the migration entities. Next to the TIP entity,
type ANALYZE. When the ANALYZE finishes successfully, type IMPORT next to the TIP
entity. Type RES next to the TIP entity to look at the ANALYZE and IMPORT messages and
counts.
13. Migrate Default Repository:
a. Within the Enterprise Repository, type PROJECTS at the command line and select AB
for version 1.
b. Next to the Migration entity, type ADDE to create a migration entity for Default
Repository. For the migration data set prefix, enter &INSTID.DF, where &INSTID is the
installer’s TSO User ID. After entering required information, press *F3 to save and return.
c. Next to the Migration entity, type LE to list the migration entities. Next to the Default
Repository entity, type ANALYZE. When the ANALYZE finishes successfully, type IMPORT
next to the Default Repository entity. Type RES next to the Default Repository entity to look
at the ANALYZE and IMPORT messages and counts.
Planning and Installing AppBuilder for the Mainframe
page 96 of 284
Installing MVS Migration Server and Enterprise Preparation
Server
One of the features of AppBuilder is the ability to prepare entities on the mainframe while keeping the entities on the
workstation platform. You can create AppBuilder applications with a workgroup repository and from the Construction
Workbench you can generate the necessary information, transfer this data to the mainframe and initiate a job to
perform the preparation. This is remote preparation to the mainframe and is made possible by the Enterprise
Preparation Server. This does NOT provide the ability to initiate a prepare on the mainframe using data stored in an
enterprise repository.
Another feature of Appbuilder is the ability to migrate applications between the LRE and the MRE. This process is
done by using the MVS Migration Server.
Installation of the Servers to a mainframe includes these procedures:
Updating Server Repository @SERVER INI
Creating the Servers
Adding an Additional Repository to the Server
Starting and Stopping the Servers
Throughout these procedures, these terms are used:
server repository – the repository where the server parameters reside
additional repository – an additional repository that can be prepared against by the server
Follow the procedures outlined in the steps that follow to install the migration server and enterprise preparation
server.
Updating the Server Repository @SERVER INI
Edit the @SERVER ini file (found in the BASEQUAL level) with the following instructions found below. There will be
variable values that will not be answered because they are for future use. In this case, the variable is noted below
but the comment will state: "Do not change".
(SKELETON)
DSNAME=
Enter the name of the data set that will contain the TCP/IP JCL. A recommended name would be
MODQUAL.TCPIP.JCL but it is not required.
(FTPLOCATION)
ADDRESS=
Enter the IP address that your site uses for FTP.
(MIGRATION)
MIG_LONGNAME=
Enter the longname for the TCPIP import method. This will be the qualifer that will be used to create a migration
entity during the import to the Host. For example, TCP_DFT_MIG can be the value and then when the import begins,
a migration entity will be created like TCP_DFT_MIG_nnnnnn, where nnnnn = an assigned number by the system.
(TCPIP)
Planning and Installing AppBuilder for the Mainframe
page 97 of 284
PREPPORT=
Enter the TCP/IP port number that will be used for the Enterprise preparation server to the Host.
PORT=
Enter the TCP/IP port number that will be used for the upload and download process to the Host.
CODEPAGE=
Enter the Mainframe code page for your site. This value would be the same value found in the @MVSENV ini file for
the variable MFCODEPG in the NLS section.
(SRVDB2) QUALIFIER=
Enter the DB2 qualifier for your DB2 tables. This value would be the same value found in the @HPSENV ini file for
the variable INST1ADM in the DB2 section.
DATABASE=
Enter the name of the DB2 database that the Host repository uses. This value would be the same value found in the
@INSTENV ini file for the variable DATABASE in the DB2 section.
DB2MEDIA=
Enter "S" if your site uses DB2 storage groups or "V" if your site uses DB2 volume catalogs. This value would be
the same value found in the @INSTENV ini file for the variable DB2MEDIA in the DB2 section.
DB2VCAT=
Enter the DB2 Volume catalog name if you have entered "V" for the DB2MEDIA variable. This value would be the
same value found in the @INSTENV ini file for the variable DB2VCAT in the DB2 section.
DDLSIZE=
Do not change.
DB2STOG=
Enter the DB2 storage group if you have entered "S" for the DB2MEDIA variable. This value would be the same
value found in the @INSTENV ini file for the variable DB2STOG in the DB2 section.
(TRACE) LOGLEVEL=0
Enter logging level of the server, where 0= no logging, and 1 to 9 is logging on, with 9 the lowest level and 1 the
highest level.
USEPASS=N
Enter Y = use password, N = do not use password for migration jobs.
(FILES) DIRBLK = 10
Enter the number of directory blocks for allocated Remote Prep PDS.
REC290BK = 31320
Enter the standard BLKSIZE for all LRECL=290 data sets.
(Place your Repository Name here)
Place the name of the Repository that operations will be accessing between the parentheses. This value would be
the same value found in the @HPSENV ini file for the variable REPNAME in the REPOSITORY section.
Planning and Installing AppBuilder for the Mainframe
page 98 of 284
BASEQUAL=
Enter the BASE qualifier of the Repository.
MODQUAL=
Enter the MOD qualifier of the Repository.
REPQUAL=
Enter the REP qualifier of the Repository.
Creating the Servers
Access the AppBuilder repository only after completion of Updating the Server Repository @SERVER INI. Go to the
ADM project of any version (except version “A”) to find a selection of Management Services.
Enter the command CRSRVJCL on the line next to Management Services. After entering the CRSRVJCL command,
a panel will appear entitled "Method Handler-Create JCL panel", shown in Figure 5-42.
Figure 5-42
Method Handler Panel
This EXEC creates the library defined by the @SERVER INI variable SKELETON.DSNAME. This library contains
the following members and their functions:
SERVER (if selected)-- JCL to start the MVS Migration Server
JOBHEAD - JOBCARD information used by the Method Handler
REPNAME – the member name equals the value of the REPNAME variable in the @SERVER INI. This is the
Method Handler and contains JCL to run the IMPORT Migration method.
RPSERV (if selected) – JCL to start the Enterprise Preparation Server.
SDSERV – JCL to shut down the MVS Migration Server or Enterprise Preparation Server cleanly.
CRVIEWS (if selected) – JCL to create Views for the repository that is being migrated to.
For entries for the panel, follow the instructions below:
1. On the line entitled Server ini dataset name......, enter the INI data set name that contains the @SERVER
member that you performed an edit on in Step 1, for example, AB.BASE.INI. If you do not enter a valid name,
the screen will not continue with the process.
2. For the section entitled Select Server Options:
If you will be using the MVS Migration Server, enter any character for the line entitled "Create Migration
Server JCL"
If you will be using the Enterprise Preparation Server, enter any character for the line entitled "Create
RemPrep Server JCL"
Do not select the line entitled "Create Views for Migration Server" because it is used by an additional repository. For
further explanation, see the section entitled Adding an Additional Repository to the Server.
Planning and Installing AppBuilder for the Mainframe
page 99 of 284
Special Notes for MVS Migration Server
The automated migration system runs outside of AppBuilder. In order to turn trace ON, go to the TRACE section and
set LOGLEVEL = 1 to 9 (where 1 produces the most logging and 9 the least); to turn trace OFF set LOGLEVEL= 0.
The member SERVER exists within the SKELETON.DSNAME data set. Within that member, the JCL allocates a
user data set in the ISPTLIB DD name concatenation. This user data set name will start with the INSTALLID and
should be the first data set in the concatenation. If you do not prefer to use this name, you can change it to any
ISPF table data set that has write access by the user community. The data set must exist or the server will fail.
The DOWNLOAD and UPLOAD methods that exist on the migration object are not to be used outside of the MVS
Migration Server. (These are internal methods and will not be supported in future releases.)
When either server is cancelled in SDSF, the TCPIP socket associated with the server may hang for several
minutes before releasing. This restricts the startup of the server until the socket frees. The following TCPIP error
message will appear:
EZY4098E Address already in use (EADDRINUSE)
To avoid this problem, use the SDSERV member in the TCPIP.JCL data set to stop the servers. Refer to the
description of the SDSERV before executing.
Adding an Additional Repository to the Server
This section is optional and can be performed if you have another repository that will be accessed by the Enterprise
Preparation Server. If this situation does not exist, then omit this section and continue on with the installation.
STEP 1 : Add the new repository to the @SERVER
Make a new section in the server repository @SERVER INI with the same name as the repository name
REPOSITORY.REPNAME in the @HPSENV INI from the additional repository. In that new section, copy the
BASEQUAL, MODQUAL, and REPQUAL values from the QUALIFIERS section of the @HPSENV INI from the
additional repository.
STEP 2 : Execute CRSRVJCL to create Method Handler JCL
After completion of Step 1, go to the ADM project of any version (except version A) in the additional repository and
enter the command CRSRVJCL next to the Management Services option. On the next screen enter the name of the
data set which contains the @SERVER ini member of the server repository. Do not select any of the other
commands unless the following is true: The MVS migration server will be used AND the repository is running under a
different plan. In this case, you will want to create Views if they are not already created. To create these views place
any character on the line entitled "Create Views ". The CRSRVJCL command creates the member with the name
equal to the additional repository name. The member is placed in the JCL library with the name equal to
SKELETON.DSNAME from the @SERVER ini that was specified.
Starting and Stopping the Servers
Open the skeleton data set name SKELETON.DSNAME and select the following:
Planning and Installing AppBuilder for the Mainframe
page 100 of 284
RPSERV - Submit this job to start the Enterprise Preparation Server. The server should be running on the
specified port. Before starting this job, perform the following edits: Remove the following line from the
ISPTLIB library concatenation:
DD DSN=&USERID.USER.TABLES,DISP=SHR
(where &USERID was the user that executed the CRSVRJCL command). Remove the NOTIFY parm
from the JOB card and replace it with the USER parm. The USER parm will have a value of a userid that has
write access to the user community data sets.
SERVER - Submit this job to start the MVS Migration Server. The server should be running on the specified
port. Before starting this job, perform the following edits: Remove the following line from the ISPTLIB library
concatenation:
DD DSN=&USERID.USER.TABLES,DISP=SHR
(where &USERID was the user that executed the CRSVRJCL command). Remove the NOTIFY parm from the
JOB card and replace it with the USER parm. The USER parm will have a value of a userid that has write
access to the user community data sets.
SDSERV - Submit this job to stop either Server. In the JCL the port number and Server type (e.g. MG or RP)
must be specified before submitting the job. As shown in the following example:
//SHUTDOWN EXEC PGM=HMCSDSRV,
//
PARM='nnnn pppp tt',REGION=512K
In the above example:
nnnn = the Host IP address (any valid address )
pppp = TCP\IP Server port number
tt
= Server type (MG - Migration Server, RP-Enterprise Preparation Server)
Planning and Installing AppBuilder for the Mainframe
page 101 of 284
Installation Verification Using TIP
1. Use the MVS Migration Server to download the TIP application to a Personal Repository on the workstation
and logoff the Mainframe before starting the Download process.
a. Login to the Personal Repository using Freeway Explorer.
b. Select Tools>Download from the menu.
c. You will be prompted for your user ID and password. This is your user ID and
password for the HOST, which may differ from the one on your PC.
d. From the download window, use the Query menu to query the TIP_FUNCTION from
the host.
e. Once queried, you can select objects in the query window and click the Load button
to put them into the download window.
f. Now that you have all the objects you want to download in the download window press
the Download button to begin.
From here, the LRE will make the request to the Host Migration Server to export and download the objects to
the LRE.
2. Prepare the TIP application:
a. Open the AppBuilder Construction Workbench in order to query objects for
preparation.
b. Select Tools >Workbench Options to open the Workbench Options dialog. On the
Preparation tab, be sure that Include Mainframe Rules is checked.
c. Right click in the Hierarchy window and from the pop-up menu select Preparation
Query or select Build > Preparation Query.
d. Select Rule as the object type and then select the Query push button. A list of rules
in the repository appears.
e. Select any rule from the Object instance list box and click Prepare. The results
display in the Prep Status window.
f. Select Build > Preparation Query again with Function as the object type and select
Query. Select the object TIP_FUNCTION to Super Prepare.
g. Make sure the following objects prepared successfully by viewing their completion
status in the Prep Status output window:
TIP_PC_RULE
TIP_PC_WINDOW
TIP_PC_C_COMP
TIP_DRIVER_RULE
TIP_DRIVER_WINDOW
TIP_FUNCTION
Note
You will observe several objects in addition to those listed above, but ignore them because they
are mainframe objects.
Planning and Installing AppBuilder for the Mainframe
page 102 of 284
3. Execute the TIP application:
a. Invoke AppBuilder Execution Workbench on the workstation.
b. A menu is displayed with the TIP Function pulldown. Select the TIP Function
pulldown menu and select TIP Cooperative Process. A window with push buttons is
displayed. Click only on the PC NESTED and C COMP push buttons to verify. Use the
mainframe push buttons to verify mainframe/CICS execution when the AppBuilder CICS
Online product has been installed on the host.
4. Verification of AppBuilder Enterprise Repository installation is now complete.
Planning and Installing AppBuilder for the Mainframe
page 103 of 284
Invoking an Exit
Based on DNAINI values, the listener will now invoke the user authentication exit. This is the same exit that is called
by PCIO. This is instead of performing the EXEC CICS VERIFY and would allow invalid requests to be trapped at a
much earlier stage. If the authentication exits indicates an error, the listener will generate a log message with the
error code 301. This message will include the user ID and the peer ID. A Peer-ID, currently only supported for TCP
and contains the peer's IP address and socket, is now passed to the Authentication and Authorization exits. This
was added to the end of the structure and thus is downward compatible.
Note
The initial structure (srv_ChkUserArgs_t / srv_ChkServArgs_t) passed to the authentication /
authorization exits contains a pointer to the srv_ChkUserStruct / srv_ChkServStruct structures that
contain the the peer ID field. These structures are defined in DNA.H.
DNAINI Setting:
MVS_LISTENER LISTENER_SECURITY = { NO | YES | PART | EXIT | EXITONLY }
Specifying either EXIT or EXITONLY will cause the user's authentication exit to be called. When EXITONLY is
specified, the user ID will *NOT* be used in the subsequent EXEC CICS START command.
Note
Security Cookie not available. The listener cannot pass security-tickets (security cookie)
contents. Existing exits that require this information would not be able to utilize this feature.
Double invocation of the authentication exit. The authentication exit may be called twice: once
from the listener (DNALSTNR) and once from the rule transaction (HPSDNA00). There is no
indication provided to differentiate between the two. In an MRO environment the listener in the
TOR could be configured separately than HPSDNAOO in the AOR - provided they do not
share the DNAINI file. Alternatively you may use different user-exits, one linked with the
listener (DNALSTNR) and one with HPSDNA00. Wherever required, the "dummy" exit need
only return a successful return code (SRV_CHKUSER_SUCCESS). Based on the user's
environment, it may be possible to determine the scenario based on the CICS program name
and/or transaction ID. To obtain this, the user-exit can issue an EXEC CICS ASSIGN
PROGRAM() and/or examine the EIBTRNID field in the EIB.
How to configure the authentication and authorization user exits.
DNA_EXITS SRV_AUTHENT_EXIT = STATIC_LINK
DNA_EXITS SRV_AUTHOR_EXIT = STATIC_LINK
The user exit code must have entry points with the following names:
SrvAuthentLibMain - Entry point for AUTHENTICATION exit. SrvAuthorLibMain - Entry point
for AUTHORIZATION exit.
When pre-linking DNALSTNR and/or HPSDNA00 you must either specifically include the (AUTHENTX) object and
remove DNACEXIT -OR- name the user's object DNACEXIT and ensure it appears first in the OBJECT DD card
concatenation.
For more information on user exits please see the Configuring Communications Guide, Chapter 6 Extending
Communications.
Planning and Installing AppBuilder for the Mainframe
page 104 of 284
Planning and Installing AppBuilder for the Mainframe
page 105 of 284
Installing Batch Preparation Workbench
The information in this section describes the detailed requirements and procedures for installing a Batch Preparation
Workbench.
Planning and Installing AppBuilder for the Mainframe
page 106 of 284
Prerequisites Installing Batch Preparation Workbench
The following AppBuilder software is required prior to the installation of this software.
• AppBuilder REL 3.4 Host Installation Workbench
• AppBuilder REL 3.4 Enterprise Repository
• Refer to Appendix E,“Hardware and Software Checklists” and Appendix H, “Batch Preparation Workbench
Customization Worksheets” to prepare for this installation.
Packing List
You should have received the following software. If you did not receive all the pieces listed below, please contact
AppBuilder Distribution.
• AppBuilder REL 3.4
.
Planning and Installing AppBuilder for the Mainframe
page 107 of 284
Installation Notes Installing Batch Preparation Workbench
The following list shows the options and panels you will use when installing this software.
Option 1 - System Functions
Apply System Upgrade
Update System Software
Option 1 Unload Installation Data Sets
Option 2 Continue
Create System Upgrade Jobs
Regenerate/Edit/Submit Installation Jobs
SYSJOB2 - Set Tape Backup Parameters
SYSJOB5 - Confirm Update Job Submission
Option 2 - Repository Functions
Apply Repository Upgrade
Option 1 Create Installation Table
Upgrade Repository
Option 2 Process Installation Table
Selecting an Installation Table to Process
Create Repository Upgrade Job
Batch environment Variables
Regenerate/Edit/Submit Installation Jobs
Option 3 Activate Repository
Planning and Installing AppBuilder for the Mainframe
page 108 of 284
Installing the Batch Preparation Workbench Software
The Host Installation Workbench Functions panel (Figure 6-1) is the starting point for installing the system and
repository portions of AppBuilder software. You must complete the system functions before continuing with the
repository functions.
1. System Functions--- see Option 1 - System Functions
2. Repository Functions---see Option 2 - Repository Functions.
Figure 6-1
Workbench Functions
Planning and Installing AppBuilder for the Mainframe
page 109 of 284
Option 1 - System Functions Installing Batch Preparation
Workbench
1. After you enter 1 in the option line of the Workbench Functions panel shown in Figure 6-1, the System
Functions panel in Figure 6-2 appears.
2. Enter 2 Apply System Upgrade on the option line to begin the system installation portion of this software.
3. Enter the ID of the system where the software will be installed. Examples are shown in this document as
“SID1”.
4. Press Enter to advance to the selected panel, or enter X or press END to exit the panel.
5. If you press Enter, the Apply System Upgrade panel in Figure 6-3 appears.
Figure 6-2
Host Installation Workbench System Functions
Apply System Upgrade
1. Enter specific information about the software you are installing. This information is used to unload the
installation data sets required for the system installation.
2. In option 1, Receive installation data sets, enter the data needed to create the receive JCL.
3. In option 2, Continue, activate the actual unloading of the data to your system.
Figure 6-3
Workbench Update System Software
4. Enter the following items on the Update Software panel (Figure 6-3)
Release: Enter SVB34, which is the installation code for this software.
Planning and Installing AppBuilder for the Mainframe
page 110 of 284
5. Enter 1, Receive installation data sets, in the option line. This option puts you in edit mode for the receive job.
Review the JCL and submit it. Press F3, and check the output of execution. Confirm the output contains the
following data sets:
&instqual..SVB34.CNTL
&instqual..SVB34.ICLIST
&instqual..SVB34.IPANELS
&instqual..SVB34.ISKELS
where &instqual is the installation data set qualifier for your site. This value was entered in step 200.1 during
your AppBuilder REL 3.4 Enterprise Repository installation.
6. Enter 2, Continue, in the option line after confirming the above data sets were created correctly. This option
allows you to continue the system software installation. Press Enter to continue to the next panel.
7. If this is the first time the system portion of this software has been installed, the Regenerate/Edit/ Submit
Installation Jobs panel in Figure 6-4 appears. Otherwise, a panel appears notifying you the installation tables
to update this system have already been generated. You can either enter N to continue with the current
installation or Y to recreate the table and begin the installation again. This action resets the status of the jobs
but does not regenerate them. The status is reported in the Status column in the Regenerate/Edit/Submit
Installation Jobs panel.
Note
When a job has completed successfully, press the Enter key twice to refresh the status from
SUBMITTED to COMPLETED.
8. The panel shown in Figure 6-4 controls the unloading of data sets. Jobs must be submitted in order (beginning
with SYSJOB1). Each job should complete successfully before submitting the next. SYSJOB1, SYSJOB4,
and SYSJOB5 must be performed---all other jobs are optional.
Note
Backups are not required; however, they are recommended.
Valid actions are regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the software. You
can monitor each jobs progress in the Status column. The status of a job may be [blank] — no activity is
occurring, SUBMITTED — a job is in progress, or COMPLETED — a job is completed.
If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status
column. Press Enter to clear this message and continue
Figure 6-4
Update System Software - Regenerate/Edit/Submit
SYSJOB1---Unload the rest of the tape
Planning and Installing AppBuilder for the Mainframe
page 111 of 284
Proceed with the unload process. You can view, regenerate, or submit the job for execution. The fol​ lowing
data sets are created by SYSJOB1:
Table 6-1
Data sets created by SYSJOB1
&BASEQUAL.SVB34.LKBTEC
&BASEQUAL.SVB34.LKBTEN
&BASEQUAL.SVB34.LKBTNC
&BASEQUAL.SVB34.LKBTUC
&BASEQUAL.SVB34.LOADBT
&BASEQUAL.SVB34.OBJ
&BASEQUAL.SVB34.PLKOBJ
&BASEQUAL.SVB34.SAMPLE
&BASEQUAL.SVB34.PRELINK
SYSJOB2---Backup data sets to tape
When you regenerate or submit SYSJOB2, the “Set Tape Backup Parameters” panel appears. Specify the
tape unit type (such as CART), the volume serial number of your tape (if desired), and the num​ ber of days
that you want the taped data to be retained. Enter the required tape backup information, and press Enter
to activate these parameters. The backup process executes, and you return to the
Regenerate/Edit/Submit Installation Jobs panel.
SYSJOB3---Backup data sets to DASD This job to sends your backup to DASD.
SYSJOB4---Link load modules
When the data sets are unloaded successfully, perform the link of the load modules.
SYSJOB5---Copy to system data sets
When the load modules are linked successfully, copy the modules to the system data sets. If you have
not performed a backup, the “Update System Software--Confirm Update Job Submission” panel alerts you.
If a backup is not made, you will not be able to backout this software. A backup option will not be
available later in this installation-any subsequent backup would have to be done manually.
After SYSJOB5 completes, the following new data sets are created or updated.
Table 6-2
System data set libraries:
System Data Set Libraries from SYSJOB5
&BASEQUAL..LKBTEC
&BASEQUAL.SVB34.PLKOBJ
&BASEQUAL..LKBTEN
&BASEQUAL.SVB34.PRELINK
&BASEQUAL..LKBTUC
&BASEQUAL..OBJ
&BASEQUAL..LOADBT
&BASEQUAL..SAMPLE
&BASEQUAL is the system data set qualifier for AppBuilder data sets.
Maintenance libraries
Table 6-3 Maintenance libraries from SYSJOB5
&MODQUAL..LOADBT
Note
&MODQUAL is the maintenance data set qualifier for AppBuilder data sets.
SYSJOB6--- Restore data sets from tape
Planning and Installing AppBuilder for the Mainframe
page 112 of 284
The restore data sets process can be used to recover (or restore) system software data sets from the tape
or DASD backups made in SYSJOB2 or SYSJOB3 in the event that the outcome of the system software
upgrade is unsatisfactory. Of course, the restore process can be used only if SYSJOB2 or SYSJOB3 was
run. To restore data sets from a tape backup, select SYSJOB6. To restore data sets from DASD backups
select SYSJOB7. The restore process does not affect any repository data sets. If the repository
installation was also completed, any updated repository information must be manually restored and any
DB2 plans rebound using the restored software level.
We recommend that you use the View or REGEN action on SYSJOB6 or SYSJOB7 at this time in order to
create the job for later use, if necessary.
Before submitting the job, edit the tape number of the backup volume used in SYSJOB2 into the job as
directed by the job stream comments.
SYSJOB7---Restore data sets from DASD See the comment above for SYSJOB6.
9. When this panel completes successfully, you have completed the System Functions installation.
Return to the starting panel (Figure 6-1) by typing X and pressing Enter. You can also press F3 repeatedly
to return through the hierarchy of installation windows to Figure 6-1.
10. Having successfully completed step 1---System Functions, you can either:
a. Continue the installation of this software by completing the "Option 2 - Repository Functions"
installation section.
or
b. Install the system portion of other AppBuilder software. Refer to the installation instructions of specific
software for more information.
You can then complete "Option 2 - Repository Functions" for each piece of software.
Note
If you choose procedure (a), ensure all software is installed in the proper order.
Planning and Installing AppBuilder for the Mainframe
page 113 of 284
Option 2 - Repository Functions Installing Batch Preparation
Workbench
1. After entering 2 in the option line of the panel shown in Figure 6-1, the panel in Figure 6-5 will appear. Before
beginning this portion of the installation, all system functions described in "Apply System Upgrade" must have
been successfully completed.
Note
To prevent user access to the repository during the repository upgrade, use option 2,
“Enable/Disable Repository” to disable the repository before beginning the repository upgrade.
2. Enter 4 Apply Repository Upgrade on the option line of this panel (Figure 6-5) to begin the repository
installation portion of this software.
3. Enter the ID of the repository to be updated. Examples are shown in this document as “repname.”
4. Press Enter to advance to the panel selected. To exit the panel, enter X or press END.
5. The panel in Figure 6-6 appears. This begins the installation of the repository functions.
Figure 6-5
Repository Functions
Apply Repository Upgrade
Figure 6-6 shows the menu items you use to begin the installation of the repository software. From this panel you
identify the repository you want to update, choose the options to create and process its installation table, and finally
activate the repository. Perform the following options in order, as described below:
Create Installation Table
Process Installation Table
Activate
Figure 6-6
Apply Upgrade to Repository menu
Planning and Installing AppBuilder for the Mainframe
page 114 of 284
Option 1 - Create installation table
6. Enter 1 Create Installation Table on the option line of this panel (Figure 6-6) and the name of the repository
to be updated and press Enter.
7. If this is the first time this repository has been updated, no subsequent panels will appear when you enter this
option. Option 1 has completed when the “TABLE CREATED” message appears in the top-right corner of the panel.
See Figure 6-7. Otherwise, a panel will appear notifying you the jobs to update this repository have already been
generated. This panel allows you to continue an in-progress installation, or abandon the installation. You can either
enter N to continue with current the installation or Y to recreate the table and begin the installation again.
Note
If you have stopped the installation and are simply resuming the installation, select N. If you have
altered the input data sets or have made other changes, enter Y to abandon this installation and start
over.
Figure 6-7
Create installation table completion notification
Option 2 - Process Installation Table
8. Enter 2 Process Installation Table on the option line of this panel (Figure 6-6),and press Enter. The panel
(Figure 6-8) will appear. This panel contains a table of releases ready to process. You will see an entry for this
software, SVB34, and any other AppBuilder 3.4 software for which the system installation has been completed. If
there is more than release, select each one individually and check that it completes successfully before selecting
the next release. You can monitor each release’s progress in the Status column. The status of a release may be
[blank] — no activity is occurring, SUBMITTED — a release is in progress, or COMPLETED — a release is
completed.
Planning and Installing AppBuilder for the Mainframe
page 115 of 284
9. When you have executed all entries in the release table successfully, press F3.
Figure 6-8
Process Installation Table
10. If this is the first time this repository has been updated, the panel in Figure 6-9 will appear. Otherwise, a panel
will appear notifying you that the jobs to update this repository have already been generated. You can continue an inprogress installation or abandon the installation by entering N to continue with current the installation or Y to recreate
the table and begin the installation again.
11. The variables entered in Figure 6-9 are used to create two jobs that update the repository, REPJOB1 and
REPJOB2.
Figure 6-9
Batch environment Variables
12. Review the following and change if needed:
300.1
Plan name prefix or suffix - [Default: B]
You can form DB2 plan names by using the generated bitmap as the plan name prefix or suffix. Enter B as the prefix
or P to use the bitmap as the suffix.
300.2
Use AppBuilder Project name in Batch plan name? (Y/N) - [Default: N ]
Enter Y or N to specify if you want to use the AppBuilder project name in the Batch plan name.
300.3
If not, enter the string to use here: - [Default: PLNB]
If you specified N above, enter the string you want to use for the Batch plan name.
300.4
Use the repository version number in plan name (Y/N) - [Default: N]
Enter Y or N to specify if you want to use the repository version number in the Batch plan name.
Planning and Installing AppBuilder for the Mainframe
page 116 of 284
13. When you press Enter to accept this panel, a job card is displayed. Job card information is incorporated
from the install into the REPJOB1 and REPJOB2 jobs. Review job card information, alter if needed, and press Enter
to proceed.
14. After accepting the jobs, the panel in Figure 5-19 will appear. Submit the jobs listed in order from the top
down (REPJOB1 then REPJOB2). You can view, submit, or regenerate a job from the Action column. Monitor its
progress in the Status column.
Valid actions are regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the software. You can
monitor each jobs progress in the Status column. The status of a job may be [blank] — no activity is occurring,
SUBMITTED — a job is in progress, or COMPLETED — a job is completed.
If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status column.
Press Enter to clear this message and continue.
Figure 6-10
Regenerate/Edit/Submit Installation Jobs
REPJOB1 — Performs non-DB2 processing. After the job completes, the following new data sets are created.
(You may have more than one set of the following data sets if more than one version was specified during the
Enterprise Repository installation).
Note
&REPQUAL is the data set qualifier for AppBuilder repository level data sets.
Table 6-4
Repository Modification Libraries
&REPQUAL..LOADBT
Note
&USRVQUAL is the data set qualifier for AppBuilder user data sets.
Table 6-5
User Libraries
&USRVQUAL..LOADBT
&USRVQUAL..NCALBT
Note
&VSUVQUAL is the VSAM user qualifier for AppBuilder VSAM data sets.
Table 6-6
User VSAM data sets
Planning and Installing AppBuilder for the Mainframe
page 117 of 284
&VSUVQUAL..BATCH.RLRELATN
&VSUVQUAL.BATCH.RULESRC
&VSUVQUAL..BATCH.VIEWDEF
Refer to Chapter 6, "Installing the Enterprise Repository" in this document for additional information about the
AppBuilder data sets.
REPJOB2 — Performs DB2 processing.
Option 3 - Activate Repository
15. Enter 3 Activate Repository on the option line of this panel (Figure 6-6) and press Enter. This will enable the
repository with the new software. A message will appear in the top right corner, notifying you that the process has
completed. At this point, the installation is complete.
16. After exiting out of the AppBuilder Host Installation Workbench, complete the "Post-installation Notes" steps
before executing the software.
Figure 6-11
Activate repository completion notification
Planning and Installing AppBuilder for the Mainframe
page 118 of 284
Postinstallation Notes Installing Batch Preparation Workbench
Perform the following steps to complete and verify the successful installation of the AppBuilder Batch Preparation
Workbench.
1. Default Repository and Test Installation Process (TIP) application should already be migrated into the
Enterprise Repository. If not, refer to the post installation instructions in Chapter 6, “Installing the Enterprise
Repository” for the migration procedure.
2. Super Prepare TIP batch process:
1. Within the Enterprise Repository, make sure you are in the TIP Project.
2. Next to the Rebuild Package entity, type ADDE (Add Entity) to add a Rebuild Package for TIP. Name
the package whatever you like. Press F3 to save and return.
3. Next to Rebuild Package entity, type LE to list the Rebuild Package entities. Next to the Rebuild
Package you just created, type ADDR (Add Relationship) to add the tip batch process to the Rebuild
Package for TIP. Select option 5 “Has-Root
Process” in popup window and press Enter. Enter
TIP_BATCH_PROCESS as the “Has-Root Process” name. Press F3 to save and end.
4. Next to the Rebuild Package for TIP, type SUPERPR. A message states the job was submitted and
also displays the job number. Several jobs will be submitted at various times.
5. After the last job finishes, check the results be typing LISTRBD next to the Rebuild Package for TIP.
Information will be displayed stating whether SUPERPR was successful or not. Press F3 to save and
return.
3. Verify the country code and currency symbol in the program HPSCGAP included
in&BASEQUAL..SVB34.SAMPLE, and change these appropriately. These values are identified by the labels
HGACSTOK, HGACTRYD and HGACTRYC. Assemble the program, saving the object module into the
relevant object library. Then rerun the COPY1, COPY2, and COPY3 steps in the DSALLOC member found in
the &INSTQUAL.AB34.CNTL data set. This will place the correct version of the translate objects in the
&BASEQUAL.OBJ data set. Then link the member HPSCGAP into your AppBuilder Batch load library using
the link function accessed from the Host Installation Workbench System Functions menu. See Appendix D,
“HPSCGAP, HPICGAP, HPEUCGP, and Sample Batch JCL” for more information about HPSCGAP.
Installation Verification Using TIP
1. Verify the TIP batch process has been prepared successfully.
2. Within the Enterprise Repository, verify you are in the TIP project. If not, enter PROJECTS at the command
line. Select TIP for version 1. Complete steps 2 through 4 for each version of the repository.
3. Type LE next to the Rules entity to list the rules.
4. Allocate the TIPOUT data set to avoid receiving abends by using the following TSO commands:
TSO ALLOC FI(TIPOUT)DA(*)
5. Test the following batch rules by typing TE next to each. Select break points if you wish, and press F16 or
SHIFT+F4 to continue. A message will be displayed for each rule stating whether it is successful or not.
• TIP_BATCH_ASM_RULE
• TIP_BATCH_ASMDB2_RULE
• TIP_BATCH_COB_RULE
• TIP_BATCH_COBDB2_RULE
• TIP_BATCH_PLI_RULE *
• TIP_BATCH_PLIDB2_RULE *
Note
Planning and Installing AppBuilder for the Mainframe
page 119 of 284
Items marked with an asterisk
are optional,only for testing PL/I components. Do not execute
these two rules if PL/I components are not used.
Planning and Installing AppBuilder for the Mainframe
page 120 of 284
Installng Report Writer Preparation
The information in this section describes the detailed requirements and procedures for installing Report Writer
Preparation.
Prerequisites
The following software is required prior to the installation of this software:
• AppBuilder REL 3.4 Host Installation Workbench
• AppBuilder REL 3.4 Enterprise Repository
• AppBuilder REL 3.4 Batch Preparation
Note
Customization worksheets are not required for this product.
Packing List
You should have received the following software. If you did not receive all the pieces listed below, please contact
AppBuilder Distribution.
• AppBuilder REL 3.4
Planning and Installing AppBuilder for the Mainframe
page 121 of 284
Installation Notes of Installng Report Writer Preparation
You should have received the following software. If you did not receive all the pieces listed below, please contact
AppBuilder Distribution.
• AppBuilder REL 3.4
Installation Notes
The following list shows the options and panels you will use when installing this software.
Option 1 - System Functions
Apply System Upgrade
Update System Software
Option 1 Unload Installation Data Sets
Option 2 Continue
Create System Upgrade Jobs
Regenerate/Edit/Submit Installation Jobs
SYSJOB2, Set Tape Backup Parameters
Option 2 - Repository Functions
Apply Repository Upgrade
Apply Upgrade to Repository
Option 1 Create Installation Table
Upgrade Repository
Option 2, Process Installation Table
Selecting an Installation Table to Process
Create Repository Upgrade Job
Regenerate/Edit/Submit Installation Jobs
Option 3, Activate Repository
Planning and Installing AppBuilder for the Mainframe
page 122 of 284
Installing Report Writer Preparation
There are two parts to installing the Report Writer Preparation product option: "Option 1--System Functions" and
"Option 2--Repository Functions". Use the panel in Figure 7-1 to navigate to both parts through the Host Installation
Workbench--- Workbench Functions.
Figure 7-1
Host Installation Workbench Functions panel
The Workbench Functions panel is the starting point for installing system functions and repository functions. You
must first apply the system functions and then the repository functions:
• Option 1, System Functions--- see "Option 1--System Functions".
• Option 2, Repository Functions---see "Option 2--Repository Functions". You must complete Option 1 before
installing Option 2.
Option 1 - System Functions
System functions are those installation processes you start when you choose Option 1, System Functions in Figure
7-1. This option lets you apply the system upgrade for Report Writer Preparation.
Apply System Upgrade
When you install the Report Writer Preparation product system functions, first select System Functions using Option
1 in Figure 7-1. See the System Functions panel in Figure 7-2.
Figure 7-2
Apply System Upgrade panel to install product options
Planning and Installing AppBuilder for the Mainframe
page 123 of 284
Use this panel to perform option 2 Apply System Upgrade.
Select option 2 on the panel.
1. Enter the ID of the system to be upgraded, shown here as “SID2”.
2. Press ENTER to advance to the next panel.
3. Enter X or press END to exit the panel.
The next panel you see appears in Figure 7-3, and it begins the installation of the system functions.
Update system software
Figure 7-3 begins the installation of the system software, starting with unloading the data sets.
Figure 7-3
Update System Software panel to unload installation Data sets
This option unloads the installation data sets required for the system installation. In option 1 Receive installation
data sets, you enter the data needed to create the unload JCL. In option 2 Continue, you activate the actual
unloading of the data to your system. First, we define what you do in this panel.
Enter the Release Details
• Release: - [DEFAULT: RPW34] Enter RPW34, which is the release number for this system upgrade.
Option 1 - Unload installation data sets
Planning and Installing AppBuilder for the Mainframe
page 124 of 284
Selecting option 1 puts you in edit mode for the unload job. Review the JCL and submit it. Press F3, and check the
output of execution. Confirm it contains these three data sets with installation software:
• &instqual..&RPW34.CNTL
• &instqual..&RPW34.ICLIST
• &instqual..&RPW34.IPANELS
• &instqual..&RPW34.ISKELS
where &instqual is the installation data set qualifier. Refer to "Installing the Enterprise Repository" in this document
for additional information about the AppBuilder data sets.
Option 2 - Continue
Select option 2 in Figure 7-3 to continue the system software installation. Press Enter.
Create System Upgrade Jobs
Figure 7-5 appears the first time you perform this installation. The panel in Figure 7-4 is optional; the first time you
apply a system upgrade, it does not appear. But it does in subsequent passes. Its text says that the installation
tables are already generated; consequently, do not generate them again unless you want to begin the installation
again.
Figure 7-4
Create system upgrade jobs panel, to regenerate the installation table
Under normal circumstances, select N (No) and proceed. But if you want to begin the installation again with the first
job, select Y (Yes). This action resets the status of the jobs but does not regenerate them. The status is reported in
the panel in Figure 7-6.
Depending on your response, regeneration either occurs or does not. Regenerating the table clears the status of any
jobs that are ‘SUBMITTED’ or ‘COMPLETED’. On successful completion of either choice, you are ready to update
the system software. This figure appears only if have already applied a system upgrade if this system.
Confirm Update Job Submission
The next panel, confirming the update of your job submission, is in Figure 7-5.
Planning and Installing AppBuilder for the Mainframe
page 125 of 284
Figure 7-5
Confirm Update Job Submission panel
This panel notifies you that no backup has been made. It is recommended that you back up your installation.
Under normal circumstances, select Y (Yes) and proceed. But if you have a strong reason for not backing up the
installation,press N (No). You will not be able backup this PTF later.
After this selection, the Regenerate/Edit/Submit panel appears.
Regenerate/edit /submit Installation Jobs
This panel provides the controls to regenerate, view, and submit installation jobs. Figure 7-6 shows the panel that
controls the actual unloading, backing up, copying, linking, and restoring of installation data sets.
Figure 7-6
Regenerate/View/Submit Installation Jobs panel
This screen controls unloading of data sets. Perform the appropriate steps top down. You can unload the tape, back
up to tape or DASD, link the load modules, and copy the results to system data sets; or restore the data sets if
dissatisfied with the results. Monitor its progress in the Status column and in additional panels that alert you of
specific situations.
The Actions you can make are to regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the
software. You can monitor each jobs progress in the Status column. The status of a job may be [blank] — no
activity is occurring, SUBMITTED — a job is in progress, or COMPLETED — a job is completed.
If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status column.
Press Enter to clear this message and continue.
You must perform jobs 1, 4, and 5; the rest are optional. The following describes the system jobs:
Planning and Installing AppBuilder for the Mainframe
page 126 of 284
• SYSJOB1---Unload the rest of the tape
Proceed with the unload process. You can view, regenerate, or submit the job for execution. The following data
sets are unloaded from the tape by SYSJOB1:
Table 7-1
Data sets
&BASEQUAL..RPW34.LKBS00
&BASEQUAL..RPW34.MVSCODE
&BASEQUAL..RPW34.PRELINK
&BASEQUAL..RPW34.PSFDCL
&BASEQUAL..RPW34.RWPRTLOG
&BASEQUAL..RPW34.OBJ
&BASEQUAL..RPW34.RWERRMSG
&BASEQUAL..RPW34.LOADLIB
&BASEQUAL..RPW34.PLKOBJ
&BASEQUAL..RPW34.PSFCODE
&BASEQUAL..RPW34.RWMSG
&BASEQUAL..RPW34.MVSDCL
&BASEQUAL..RPW34.RWLNCFG
&BASEQUAL..RPW34.STDCODE
&BASEQUAL..RPW34.STDDCL
• SYSJOB2---Backup data sets to tape
When you regenerate or submit SYSJOB2, you see another panel that sets tape backup parameters, as shown
in Figure 7-3.
• SYSJOB3---Backup data sets to DASD
Use this job to direct your backup to DASD.
• SYSJOB4---Link load modules
When the data sets are unloaded successfully, perform the link of the load modules. Before that can be
completed, you must define additional information in another panel, shown in Figure 7-8.
• SYSJOB5---Copy to system data sets
When the load modules are linked successfully, copy the modules to the system data sets. If you have not
performed a backup, the panel in Figure 7-4 alerts you. The following data sets are updated or created by
SYSJOB5:
Table 7-2
SYSJOB5 Data Sets
&BASEQUAL..LKBS00
&BASEQUAL..MVSCODE
&BASEQUAL..OBJ
&BASEQUAL..PSFDCL
&BASEQUAL..RWLNCFG
&BASEQUAL..RWPRTLOG
&BASEQUAL..MVSDCL
&BASEQUAL..PSFCODE
&BASEQUAL..RWERRMSG
&BASEQUAL..RWMSG
&BASEQUAL..STDCODE
&BASEQUAL..STDDCL
• SYSJOB6---Restore data sets from tape
Planning and Installing AppBuilder for the Mainframe
page 127 of 284
The restore data sets process can be used to recover (or restore) system software data sets from the tape or
DASD backups made in SYSJOB2 or SYSJOB3 in the event that the outcome of the system software upgrade
is unsatisfactory. Of course, the restore process can be used only if SYSJOB2 or SYSJOB3 was run. To
restore data sets from a tape backup, select SYSJOB6. To restore data sets from DASD backups select
SYSJOB7.The restore process does not affect any repository data sets. If the repository installation was also
completed, any updated repository information must be manually restored and any DB2 plans rebound using the
restored software level.
AppBuilder Solutions recommends that you use the View or REGEN action on SYSJOB6 or SYSJOB7 at this
time in order to create the job for later use, if necessary.
Note
Before submitting this job, edit the tape number of the backup volume used in SYSJOB2 into the job
as directed by the job stream comments.
• SYSJOB7---Restore data sets from DASD See the comment above for SYSJOB6.
• Status---[blank]
The following lists indicators displayed in the Status column. Observe the status of the Actions you initiate.
• [blank] — No activity is occurring.
• SUBMITTED — A job is in progress.
• COMPLETED — A job is completed.
When this panel completes successfully, you have completed the System Functions installation. Return to the
starting panel by typing X and pressing Enter or by pressing F3 repeatedly. You return through the hierarchy of
installation windows to the Workbench Functions panel in Figure 7-1.
Note
When a job has completed successfully, press the Enter key twice to refresh the status from
SUBMITTED to COMPLETED.
Having successfully completed option 1 System functions, you can either:
a. Continue the installation of this software by completing the "Option 2-- Repository Functions"
installation
or
b. Install the system portion of other AppBuilder software. Refer to installation instructions of specific software for
more information--- for example, "Installing the Enterprise Repository". You would then complete the "Option 2-Repository Functions" for each piece of software.
Note
If you choose procedure a, ensure all software is installed in the proper order.
Planning and Installing AppBuilder for the Mainframe
page 128 of 284
SYSJOB2 - Set Tape Back up Parameters
When you start a backup of data sets to tape, see a panel that identifies the taping parameters as shown in Figure 77.
Figure 7-7
1.
2.
3.
4.
Set Tape Backup Parameters panel
Enter the UNIT for the tape being used for the backup.
Enter the volume serial number of the tape being used for the backup.
Enter the number of days that you want the taped data to be retained.
Specify the required tape backup information, and press ENTER to activate these parameters. The backup
process executes, and you return to the panel in Figure 7-6.
Option 2 - Repository Functions
Repository functions are those installation processes you start when you choose Option 2, Repository Functions in
Figure 7-1. This option lets you apply the repository upgrade for Report Writer Preparation. You must complete the
Option 1, System Functions before proceeding with Option 2, Repository Functions.
info
To prevent user access to the repository during the repository upgrade,use option 2, “Enable/Disable
Repository” to disable the repository before beginning the repository upgrade.
Apply Repository Upgrade
Option 2, Repository Functions, allows you to start installing repository functions, as shown in Figure 7​-8.
Figure 7-8
Apply repository upgrade panel to install product options
Planning and Installing AppBuilder for the Mainframe
page 129 of 284
Use the panel above to perform option 4, Apply Repository Upgrades. The valid actions for this panel are:
1. Select option 4 on the panel.
2. Enter the ID of the repository to be updated.
3. Press ENTER to advance to the panel selected.
4. Enter X or press END to exit the panel.
The next panel you see appears in Figure 7-9, and it starts the installation of the repository functions.
Apply Upgrade to Repository
This panel begins the installation of the repository software, starting with creating installation tables, as shown in
Figure 7-9.
Figure 7-9
Apply Upgrade to Repository panel
This panel starts upgrading the repository portion of the Report Writer Preparation product option. But, you cannot
start this portion until you have completed the system functions described in "Update system software".
From this panel identify the repository you want to create; choose the options to create and process its installation
table, and finally activate the resultant repository. Perform the following options in order, as described below:
• Create Installation Table
• Process Installation Table
• Activate
Option 1, Create Installation Table
Initiate the panel in Figure 7-9 with option 1. Begin by naming the repository to upgrade and selecting option 1
Create Installation Table. (You will return to this panel to perform Option 2 and 3 later.)
If this is the first time upgrading this repository, you know that option 1 is done when the “TABLE CREATED”
message appears in the top-right corner of Figure 7-9. In this case, perform Option 2 and proceed to the panel in
Figure 7-11.
After the initial upgrade of the repository using Option 1, you see the panel on Figure 7-10. After you make your
selection, you return to this panel for action. Assuming you are continuing with the upgrade at hand, proceed to the
panel in Figure 7-11 to perform Option 2.
Planning and Installing AppBuilder for the Mainframe
page 130 of 284
Additional information about Options 2 and 3 appears in sequence later.
Upgrade Repository
Figure 7-11 will appear the first time you perform this installation. The panel appearing next in Figure 7-10 is optional;
the first time you apply a system upgrade, it does not appear. It does appear in subsequent passes. Its text says
that the installation tables are already generated; consequently, do not generate them again unless you have
introduced some change requiring another generation pass.
Figure 7-10
Upgrade Repository panel
This panel allows you to restart the installation if special circumstances demand it.
Under normal circumstances, select N (No) and proceed. But if you have altered the input data sets or introduced
other changes, press Y (Yes) to abandon this upgrade and start again.
This optional panel allows you to decide if the upgrade you are starting is the correct one. Depending on your
response, this repository upgrade can be continued or terminated so another can be started from the beginning:
• If you want to continue the upgrade currently in progress, enter N.
• If you want to stop this upgrade, not allowing it to continue, so you can initiate another modified upgrade,
enter Y.
On successful completion of either choice, you move to the next panel in Figure 7-11.
Option 2 - Process Installation Table
You return to the Apply Upgrade to Repository panel (Figure 7-11), and enter Option 2, Process Installation Table.
Figure 7-11
Apply Upgrade to Repository
Planning and Installing AppBuilder for the Mainframe
page 131 of 284
Select Option 2 for the same repository, and press Enter. Figure 7-12 appears.
Selecting an Installation Table to Process
Figure 7-12 shows the next panel from which you start processing the installation table.
Figure 7-12
Process Installation Table panel
This panel contains a table of releases that you are to process. Select each in top-down order, and assure each
executes completely. The following lists indicators displayed in the Status column. Observe the status of the
Actions you initiate.
• [blank] — No activity is occurring.
• SELECTED — A job is in progress.
• COMPLETED — A job is completed.
When you have executed all entries in the release table successfully, press F3. See the next panel.
Create Repository Upgrade Jobs
Figure 7-14 will appear the first time you perform this installation. The panel appearing next in Figure 7-13 is optional;
the first time you apply a repository upgrade, it does not appear. But it does in subsequent passes. Its text says that
the installation job table is already generated; consequently, do not generate it again unless you want to restart the
installation from the beginning. The next panel is optional,appearing only if you are executing this process more than
once. This panel in Figure 7-13 enables you to recreate the job table and restart the release selected in Figure 7-12.
Figure 7-13
Create Repository Upgrade Jobs panel
The jobs to upgrade this repository have already been generated.To complete the installation using the existing jobs,
enter N below. To recreate the table and begin the installation again,enter Y below. Note that you may encounter
difficulty in attempting to rerun jobs which have already been completed.
Do you want to regenerate the installation table? (Y/N)==>
Planning and Installing AppBuilder for the Mainframe
page 132 of 284
This panel appears when jobs to generate the repository have been created previously. You can accept them as they
are (specify N for No) or recreate the table and restart the installation (specify Y for Yes). Select N or Y, and press
Enter. Figure 7-14 establishes batch variables.
Regenerate/edit /submit Installation Jobs
Figure 7-14 defines the repository jobs that install updates to your repository.
Figure 7-14
Regenerate/Edit/Submit Installation Jobs panel
Execute the jobs in order from the top down. You can view, submit, or regenerate a job from the Action column.
Monitor its progress in the Status column and in additional panels that alert you of specific situations.
This panel is a major control panel for the repository functions update. Its choices are:
• Regenerate (REGEN)
• Vew (V or VIEW)
• Submit (SUB) jobs to update the software
You monitor each jobs progress in the Status column. If you enter an invalid command in the action column, the
message INVALID ACTION appears in the Status column. Press Enter to clear this message and continue.
The following list describes the repository job:
• REPJOB1 — NON-DB2 PROCESSING
The following lists indicators displayed in the Status column. Observe the status of the Actions you initiate.
• [blank] — No activity is occurring.
• SUBMITTED — An action is in process.
• COMPLETED — An action is completed.
When you have completed this job successfully, press the Enter key twice to refresh the status panel and
F3 to exit this panel. You return to the Apply Upgrade to Repository panel, shown in Figure 7-15.
Option 3, Activate Repository
After completing the previous panel, you have applied all the repository updates for RPW34. The last action in this
series activates the repository, as Figure 7-15 shows.
Figure 7-15
Apply Upgrade to Repository
Planning and Installing AppBuilder for the Mainframe
page 133 of 284
Figure 7-15 appears for you to select Option 3, Activate Repository. This option concludes the installation of the
Report Writer Preparation upgrade to your repository.
Planning and Installing AppBuilder for the Mainframe
page 134 of 284
Postinstallation Notes of Installng Report Writer Preparation
Installation Verification Using TIP
Perform the following steps to verify the installation:
Verify the TIP batch process has been prepared successfully. If not, refer to “Post installation Notes” for the Batch
Preparation installation.
1. Within the Enterprise Repository, verify that you are in the TIP project. If not enter PROJECTS at the
command line. Select TIP for version 1. Complete the remaining steps for each version of the repository.
2. Type LE next to the pubs entity to list the rules.
3. Make the following allocations to your session at the command line:
• TSO ALLOC F(HTPRPT) DA(*)
• TSO ALLOC F(SYSOUT) DA(*) [Note: This may already be allocated.]
4. Test the following TIP batch report rule by typing TE next to TIP_REPORT_RULE. Select break points if you
wish, and press F16 or SHIFT+F4 to continue. The TIP report will be displayed on your screen.
5. Test the report method by typing REP next to any rule listed. A panel will be displayed requesting more
information about the report. Enter the following:
Table 7-3 TIP Verification
Object Parts to Process:
Use defaults
Report Output Options:
Select 1 for softcopy
Printer Destination:
Leave blank
Defer Report for Overnight Execution:
Use default
Report Selection Options:
Select 2 for Object Hierarchy
A batch job will be submitted. After the job finishes, view the report by typing RES next to the rule that the report
was run against. Select the “AppBuilder Reporting Facility” results file to display the report.
Planning and Installing AppBuilder for the Mainframe
page 135 of 284
Installing CICS Online Prepration Workbench and Enterprise
Server
The information in this section describes the detailed requirements and procedures for installing a CICS Online
Prepration Workbench and enterprise server.
Prerequisites
The following AppBuilder software is required prior to the installation of this software.
• AppBuilder REL 3.4 Host Installation Workbench
• AppBuilder REL 3.4 Enterprise Repository
Note
Complete the checklists and worksheets provided in Appendix E, “Hardware and Software
Checklists” and Appendix I, “CICS Online Preparation Workbench and Enterprise Server
Customization Worksheets” in this document before proceeding with this installation.
Packing List
You should have received the following software. If you did not receive all the pieces listed below, please contact
AppBuilder Distribution.
• AppBuilder REL 3.4
Planning and Installing AppBuilder for the Mainframe
page 136 of 284
Installation Notes of Installing CICS Online Prepration
Workbench and Enterprise Server
This section contains the following hierarchy of panels for installing the AppBuilder CICS
Online Preparation Workbench and Enterprise Server software.
Option 1 - System Functions
Apply System Upgrade
Update System Software
Option 1 Unload Installation Data Sets
Option 2 Continue
Create System Upgrade Jobs
Confirm Update Job Submission
Regenerate/Edit/Submit Installation Jobs
SYSJOB2 - Set Tape Backup Parameters
SYSJOB5 - Confirm Update Job Submission
Option 2 --- Repository Functions
Apply Repository Upgrade
Apply Upgrade to Repository
Option 1 Create Installation Table
Upgrade Repository
Option 2 Process Installation Table
Selecting an Installation Table to Process
Create Repository Upgrade Job
Batch environment Variables
Regenerate/Edit/Submit Installation Jobs
Option 3 Activate Repository
Installing CICS Online Preparation Workbench and Enterprise
Server Software
There are two parts to installing AppBuilder REL 3.4 CICS Online Preparation Workbench and CICS Enterprise
Server software: “Option1-System Functions” and “Option 2-Repository Functions”.
Use the panel in Figure 8-1 to navigate to both parts through the AppBuilder REL 3.4 Host Installation Workbench--Workbench Functions (Figure 8-1).
Figure 8-1
Host Installation Workbench Functions
Planning and Installing AppBuilder for the Mainframe
page 137 of 284
The Workbench Functions panel is the starting point for installing system functions and repository functions. You
must first apply the system functions and then the repository functions:
• “Option 1-System Functions”
• “Option 2-Repository Functions”
Complete option 1 before installing option 2.
Option 1 - System Functions
System functions are those installation processes you start when you choose Option 1, System Functions in Figure
8-1. This option lets you apply the system upgrade for AppBuilder REL 3.4 CICS Online Preparation Workbench and
CICS Enterprise Server software.
Apply System Upgrade
When you install the AppBuilder REL 3.4 CICS Online Preparation Workbench and CICS Enterprise Server software
system functions, select System Functions using option 1 in Figure 8-1. The System Functions panel opens (Figure
8-2).
Figure 8-2
Apply System Upgrade panel to install product options
Use this panel to perform option 2 Apply System Upgrade.
1. Select option 2 on the panel.
2. Enter the ID of the system to be upgraded, shown here as “SID1”.
3. Press ENTER to advance to the panel selected.
4. Enter X or press END to exit the panel.
Figure 8-3 appears, and it begins the installation of the system functions.
Planning and Installing AppBuilder for the Mainframe
page 138 of 284
Update System Software
This panel begins the installation of the system software, starting with unloading the data sets, as shown in Figure 83.
Figure 8-3
Update System Software
This option unloads the installation data sets required for the system installation. In option 1 Receive installation
data sets, you will enter the data needed to create the receive JCL.
In option 2 Continue, you activate the actual unloading of the data to your system. First, however, you must enter
the following information.
• Release: Enter SVC34, the installation code for this software.
Option 1 - Unload Installation Data Sets
Selecting option 1 displays job card information. Review the data and submit it. Check the output of execution and
confirm it contains the following data sets:
• &instqual..&SVC34.CNTL
• &instqual..&SVC34.ICLIST
• &instqual..&SVC34.IPANELS
• &instquaL..&SVC34.ISKELS
where &instqual is the installation data set qualifier. Refer to “Installing the Enterprise Repository” in this document
for additional information about the AppBuilder data sets.
Option 2 - Continue
Selecting option 2 in Figure 8-3 allows you to continue the system software installation. Press Enter to continue to
Figure 8-4.
Create System Upgrade Jobs
Figure 8-5 appears the first time you perform this installation. The panel shown here in Figure 8-4 is optional; the first
time you apply a system upgrade, it does not appear. But it does in subsequent passes. Its indicates that the
installation tables are already generated; consequently, do not generate them again unless you have introduced
some change requiring another generation pass
Planning and Installing AppBuilder for the Mainframe
page 139 of 284
Figure 8-4
Create System Upgrade Jobs panel, to regenerate the installation table
Under normal circumstances, select N (No) and proceed. If you want to begin the installation again with the first job,
select Y (Yes). This action resets the status of the jobs but does not regenerate them. The status is reported in the
panel in Figure 8-1.
Depending on your response, regeneration either occurs or does not. Regenerating the table clears the status of any
jobs that are ‘SUBMITTED’ or ‘COMPLETED’. On successful completion of either choice, you are ready to update
the system software. Figure 8-4 appears only if you have already applied a system upgrade to this system.
Confirm Update Job Submission
Figure 8-5 appears, confirming the update of your job submission.
Figure 8-5
Confirm Update Job Submission panel
This panel notifies you that no backup has been made. It is recommended that you back up your installation.
Under normal circumstances, select N (No) and proceed with the backup job. But you choose to not back up the
installation by pressing Y (Yes).
Note
You will not be able back out this software later.
After this selection, the Regenerate/Edit/Submit panel (Figure 8-6) appears.
Regenerate/edit /submit Installation Jobs
Planning and Installing AppBuilder for the Mainframe
page 140 of 284
This panel provides the controls to regenerate, view, and submit installation jobs. Figure 8-6 shows the panel that
controls the actual unloading, backing up, copying, linking, and restoring of installation data set.
Figure 8-6
Regenerate/View/Submit Installation Jobs
This screen controls unloading of data sets. Perform the appropriate steps top down. You can unload the tape,
backup to tape or DASD, link the load modules, and copy the results to system data sets; or restore the data sets if
you are not satisfied with the results. Monitor its progress in the Status column and in additional panels that alert you
of specific situations.
The actions you can take are to regenerate (REGEN), view (V or VIEW), or submit (SUB) jobs to update the
software. You can monitor each jobs progress in the Status column. The status of a job may be [blank] — no
activity is occurring, SUBMITTED — a job is in progress, or COMPLETED — a job is completed.
If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status column.
Press Enter to clear this message and continue.
You must perform jobs 1, 4, and 5; the rest are optional. The following describes the system jobs:
• SYSJOB1---Unload the rest of the tape
Proceed with the unload process; you can view, regenerate, or submit the job for execution. The fol​ lowing data
sets are unloaded by SYSJOB1:
Table 8-1
Data sets created by SYSJOB1
&BASEQUAL.SVC34.HPSDNAER
&BASEQUAL.SVC34.OBJ
&BASEQUAL.SVC34.HPSDNAIN
&BASEQUAL.SVC34.PLKOBJ
&BASEQUAL.SVC34.HPSDNART
&BASEQUAL.SVC34.PRELINK
&BASEQUAL.SVC34.LKCIEC
&BASEQUAL.SVC34.SAMPLE
&BASEQUAL.SVC34.LKCIEN
&BASEQUAL.SVC34.SAMP255
&BASEQUAL.SVC34.LKCIUC
&BASEQUAL.SVC34.SAMP80
&BASEQUAL.SVC34.LOADCI
&BASEQUAL.SVC34.VIDTEXT
• SYSJOB2---Backup data sets to tape
When you regenerate or submit SYSJOB1, you see another panel that sets tape backup parameters, as shown
in Figure 8-2.
• SYSJOB3---Backup data sets to DASD
Use this job to direct your backup to DASD.
Planning and Installing AppBuilder for the Mainframe
page 141 of 284
• SYSJOB4---Link load modules
When the data sets are unloaded successfully, perform the link of the load modules. Before that can be
completed, you must define additional information in another panel, shown in Figure 8-3.
When creating the link edit job, a panel is displayed requesting the CICS LINK and RUNTIME libraries. If you
press END to terminate instead of continuing, the JCL for SYSJOB4 is still created with the values present on
the panel at that time. To rectify this error, it is necessary to type REGEN against JOB.
Note
If your site does not use MQ Series and you answered “N” to MQ Series question on the Panel
entitled “Capture Systems Variables - MVS Environment page 2 of 9” in the Enterprise Repository
chapter, then the module HPSDNA00 will not link. Make the following changes:
Change the HPSDNA00 prelink located in &BASEQUAL.SVC34.PRELINK by adding the
following line: INCLUDE OBJECT(DNAMQEMP)
Change the HPSDNA00 link located in &BASEQUAL.SVC34.LKCIUC by removing the
following line: INCLUDE SYSLIB(CSQCSTUB)
Then make a copy of the SYSJOB4 job located in &INSTQUAL.SVC34.CNTL and remove all steps
except the PRELINK and LKCIUC steps. Then remove all prelinks and links except for HPSDNA00.
In the LKCIUC step, remove the following line for HPSDNA00:
INCLUDE SYSLIB(CSQCSTUB)
Then run that copy of SYSJOB4 that contains a PRELINK and LKCIUC steps for HPSDNA00 only.
• SYSJOB5---Copy to system data sets
When the load modules are linked successfully, copy the modules to the system data sets. After this job
completes the following data sets are created or updated:
• System libraries:
Table 8-2
System libraries created or updated by SYSJOB5
&BASEQUAL..COPYC
&BASEQUAL..LKCIEN
&BASEQUAL..LOADCI
&BASEQUAL..PLKOBJ
&BASEQUAL..LKCIEC
&BASEQUAL..LKCIUC
&BASEQUAL..OBJ
&BASEQUAL..PRELINK
Note
&BASEQUAL is the System Data Set Qualifier for AppBuilder data sets.
• System VSAM libraries:
Table 8-3
VSAM libraries createdor updated by SYSJOB5
&VSMQUAL..HPSDNAER.CAT
Note
&VSMQUAL is the System VSAM Data Set Qualifier for AppBuilder data sets.
Planning and Installing AppBuilder for the Mainframe
page 142 of 284
• Maintenance libraries:
Table 8-4
Maintenance libraries createdor updated by SYSJOB5
&MODQUAL..LOADCI
Note
&MODQUAL is the Maintenance Data Set Qualifier for AppBuilder data sets.
• SYSJOB6---Restore data sets from tape
The restore data sets process can be used to recover (or restore) system software data sets from the tape or
DASD backups made in SYSJOB2 or SYSJOB3 in the event that the outcome of the system software upgrade
is unsatisfactory. Of course, the restore process can be used only if SYSJOB2 or SYSJOB3 was run. To
restore data sets from a tape backup, select SYSJOB6. To restore data sets from DASD backups select
SYSJOB7.The restore process does not affect any repository data sets. If the repository installation was also
completed, any updated repository information must be manually restored and any DB2 plans rebound using the
restored software level.
We recommend that you use the View or REGEN action on SYSJOB6 or SYSJOB7 at this time in order to
create the job for later use if necessary.
Note
Before submitting this job, edit the tape number of the backup volume used in SYSJOB2 into the job
as directed by the job stream comments.
• SYSJOB7---Restore data sets from DASD See the comment above for SYSJOB6.
• Status---[blank]
Observe the status of the Actions you initiate. The following lists indicators that are displayed in the Status
column:
•
[blank] — No activity is occurring.
•
SUBMITTED — An action is in process.
•
COMPLETED — An action is completed.
When all jobs have completed successfully, you have completed the System Functions installation. Return to the
starting panel by typing X and pressing ENTER, or press F3 repeatedly. You return through the hierarchy of
installation windows to the Workbench Functions panel in Figure 8-7.
Note
When a job has completed successfully, press the Enter key twice to refresh the status from
SUBMITTED to COMPLETED.
Having successfully completed 1---System Functions, you can:
a. Continue the installation of this software by completing the “Option 2-Repository Functions”
installation
Planning and Installing AppBuilder for the Mainframe
page 143 of 284
or
b. Install the system portion of other AppBuilder software. Refer to the installation instructions of specific software
for more information.You can then complete the “Option 2-Repository Functions” for each piece of software.
Note
If you choose procedure (b), ensure all software is installed in the proper order.
SYSJOB2 - Set Tape Backup Parameters
When you start a backup of data sets to tape, you will see a panel that identifies the tape parameters,as shown in
Figure 8-7.
Figure 8-7
1.
2.
3.
4.
Set Tape Backup Parameters
Enter the UNIT for the tape being used for the backup.
Enter the volume serial number of the tape being used for the backup.
Enter the number of days that you want the taped data to be retained.
Specify the required tape backup information, and press ENTER to activate these parameters. The backup
process executes, and you return to the panel in Figure 8-1.
SYSJOB4 - Capture System Variables
To perform the load link modules step (Action: SYSJOB4) in Figure 8-1, the process needs certain information you
provide in the panel shown in Figure 8-3.
Figure 8-8
Capture System Variables
Planning and Installing AppBuilder for the Mainframe
page 144 of 284
The choices in this panel are:
400.1
CICS Runtime Library -[Default: CICSTS51.CICS.SDFHLOAD]
Enter the name of the CICS runtime library used to link AppBuilder modules.
400.1a
CICS EXCI Runtime Library -[Default: CICSTS51.CICS.SDFHEXCI]
Enter the name of the CICS EXCI runtime library.
400.1b
TCPIP Reentrant C Socket library -[Default: TCPIP.SEZARNT1]
Enter the name of the TCPIP reentrant C socket library.
When you have specified the variables, press ENTER.You return to the panel in Figure 8-1.
Option 2 - Repository Functions
Repository functions are those installation processes you start when you choose option 2, Repository Functions.
This option lets you apply the repository upgrade for AppBuilder REL 3.4 CICS Online Preparation Workbench and
CICS Enterprise Server software. You must complete the option 1, System Functions before proceeding with option
2, Repository Functions.
Installing Repository Upgrades
Figure 8-9a
Initiate Repository Functitons
Select option 2 Repository Functions to start installing repository functions.
Note
To prevent user access to the repository during the repository upgrade, use option 2 Enable/Disable
Repository to disable the repository before beginning the repository upgrade.
Figure 8-9b
Apply Repository Upgrade
Planning and Installing AppBuilder for the Mainframe
page 145 of 284
Use the panel above to perform option 4 Apply Repository Upgrade. The actions for this panel are:
1. Select option 4 on the panel.
2. Enter the ID of the repository to be updated.
3. Press ENTER to advance to the panel selected.
4. Enter X or press END to exit the panel.
The next panel begins the installation of the repository functions.
Apply Upgrade to Repository
This panel begins the installation of the repository software, starting with creating installation tables, as shown in
Figure 8-10
Figure 8-10
Apply Upgrade to your Repository
This panel starts upgrading the repository portion of the AppBuilder CICS Online Preparation Workbench and CICS
Enterprise Server software.
Do not begin this part of the installation until you have completed the system functions portion of the
installation.
From this panel you identify the repository you want to create, and choose the options to create and process its
installation table, and finally activate the resultant repository. Perform the following options, as described below:
Create Installation Table
Process Installation Table
Activate
Planning and Installing AppBuilder for the Mainframe
page 146 of 284
Option 1 - Create Installation Table
Initiate the panel in Figure 8-10 by identifying the repository to upgrade and selecting option 1 Create Installation
Table. (You will return to this panel to perform option 2 and 3 later.)
If this is the first time upgrading this repository, the “TABLE CREATED” message appears in the top​ right corner of
Figure 8-10. In this case, perform option 2 and proceed to the panel in Figure 8-11.
After the initial upgrade of the repository using option 1, you see the panel. on Figure 8-6. After you handle that
panel, you will return to this panel for action.
Additional information about option 2 and 3 appears in sequence later.
Upgrade Repository
Figure 8-10 will appear the first time you perform this installation. The panel appearing next in Figure 8-11 is optional.
The first time you apply a repository upgrade, this panel does not appear; but it does appear subsequently. It
indicates that the installation tables are already generated; consequently, do not generate them again unless you
have introduced some change requiring another generation pass.
Figure 8-11
Upgrade Repository
This panel allows you to restart the installation if special circumstances demand it.
Under normal circumstances, select N (No) and proceed. But if you have altered the input data sets or introduced
other changes, press Y (Yes) to abandon this upgrade and start again.
This optional panel allows you to decide if the upgrade you are starting is the correct one. Depending on your
response, this repository upgrade can be continued or terminated so another can be started from the beginning:
If you want to continue the upgrade currently in progress, enter N.
If you want to stop this upgrade, not allowing it to continue, so you can initiate another modified upgrade,
press Y.
Option 2 - Process Installation Table
Figure 8-12 shows the Apply Upgrade to Repository panel, enter option 2 Process Installation Table and press
ENTER.
Figure 8-12
Apply Upgrade to Repository
Planning and Installing AppBuilder for the Mainframe
page 147 of 284
Selecting an Installation Table to Process
Figure 8-13 shows the next panel from which you start processing the installation table.
Figure 8-13
Process Installation Table
This panel contains a table of releases that you are to process. If there are more than one, select each in top-down
order and ensure each executes completely. The following lists indicators displayed in the Status column. Observe
the status of the Actions you initiate.
[blank] — No activity is occurring.
SELECTED — An action is in progress.
COMPLETED — An action is completed.
When you have executed all entries in the release table successfully, press F3.
Apply SVC34 to the Repository
Figure 8-14 applies the repository upgrade to the repository.
Figure 8-14
Apply SVC34 to Repository
This panel applies the repository upgrade to the repository in two optional steps. Select from the following options:
Planning and Installing AppBuilder for the Mainframe
page 148 of 284
1. Capture Version Variables
2. Create/Submit Installation Jobs
Option 1 - Capture Version Variables
Capture Version Variables starts a group of panels in which you specify the requisite information for each version of
a repository. The panels appear in Figure 8-15 to Figure 8-20. Handle these panels in the order they appear.
Option 2 - Create/Submit Installation Jobs
Create/Submit Installation Jobs is discussed after the six variables panels in Figure 8-16.
Capture Repository Variables
The next series of six panels capture repository variables needed to apply the repository upgrade to the CICS
environment. The first of these panels is in Figure 8-15.
Figure 8-15
Capture Repository Variables---CICS environment (1 of 6)
Enter the information required by this panel.
400.2
Runtime Dataset Name Suffixes:
Enter the runtime data set name suffix.
400.2a
Load Library Output - [Default: LOADCI]
Enter the load library output suffix, to a maximum of eight (8) characters.
400.2b
NCAL Library Output - [Default: NCALCI]
Enter the NCAL library output suffix, to a maximum of eight (8) characters.
400.2c
VSAM View Definition File - [Default: HPS001D1.VIEWDEF]
Enter the VSAM view definition file suffix.
400.2d
VSAM Rule Source Output - [Default: HPS003D1.RULESRC]
Enter the VSAM rule source output suffix.
400.2e
VSAM Rule Relation Output - [Default:HPS004D1.RLRELATN]
Enter the VSAM rule relation output suffix.
Planning and Installing AppBuilder for the Mainframe
page 149 of 284
400.2f
VSAM View Definition (PCNV) - [Default: HPS021D1.VIDTEXT]
Enter the VSAM view definition output suffix.
400.3
Runtime Dataset DDNAMES:
Enter the following DDNAMEs.
400.3a
VSAM View Definition File - [Default: HPS001D1]
Enter the DDNAME for the VSAM view definition file.
400.3b
VSAM Rule Source Output - [Default: HPS003D1]
Enter the DDNAME for the VSAM rule source output.
400.3c
VSAM Rule Relation Output - [Default: HPS004D1]
Enter the DDNAME for the VSAM rule relation output.
400.3d
VSAM View Definition (PCNV) - [Default: HPS021D1]
Enter the DDNAME for the VSAM view definition file.
The second of six panels capturing repository variables is in Figure 8-16.
Figure 8-16
Capture Repository Variables---CICS environment (2 of 6)
400.4
CICS Macro Library - [Default: CICSTS51.SDFHMAC]
Enter the CICS macro library name at your site.
400.5
CICS PL/I Library - [Default: CICSTS51.SDFHPL1]
Enter the PL/I library name at your site.
400.6
CICS COBOL Library - [Default: CICSTS51.SDFHCOB]
Enter the CICS COBOL library name at your site.
400.7
CICS C 370 Library - [Default: CICSTS51.SDFHC370]
Enter the C370 library name at your site.
400.8
CICS ASM Translator - [Default: DFHEAP1$]
Enter the CICS ASM translator name at your site.
400.9
CICS PL/I Translator - [Default: DFHEPP1$]
Enter the CICS PL/I translator name at your site.
Planning and Installing AppBuilder for the Mainframe
page 150 of 284
400.10
CICS COBOL Translator - [Default: DFHECP1$]
Enter the CICS COBOL translator name at your site.
400.11
CICS C370 Translator - [Default: DFHEDP1$]
Enter the CICS 3270 translator library name at your site.
400.12
Use HPS/CICS Autoinstall? (Y/N )
If Y is entered, AppBuilder software automatically makes the program and transaction definitions in the CICS region
available during preparation of user rules and components. It will also process AppBuilder user VSAM files and
update the AppBuilder incore table with the rule and its associated transid.
400.13
CEDA Transaction Name - [Default: CEDA]
Enter the CEDA transaction name used at your site.
400.14
CEMT Transaction Name - [Default: CEMT]
Enter the CEMT transaction name used at your site.
Complete this panel and proceed to the next.
The third of six panels capturing repository variables is in Figure 8-17.
Figure 8-17
Capture Repository Variables---CICS environment (3 of 6)
Enter the information required by this panel.
400.17
You may form CICS DB2 plan names by using the generated bitmap as the plan name prefix or
suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default: B]
Specify how the generated bitmap is used in the CICS DB2 plan name.
400.18
Use AppBuilder Project name in CICS plan name? (Y/N ) - [Default: N]
Specify if the AppBuilder project name is used in the CICS plan name.
400.19
If not, enter the string to use here: - [Default: PLNC]
If the AppBuilder project name is not used in the CICS plan name, enter the name to use.
400.20
Use the repository version number in plan name? (Y/N ): - [Default: N]
Specify if the repository version number is used in the plan name.
400.21
Use the region type (‘C’) in the plan name? (Y/N ) - [Default: N]
Specify if the region type is used in the plan name.
Planning and Installing AppBuilder for the Mainframe
page 151 of 284
Complete this panel and proceed to the next panel which is used to capture repository variables (Figure 8-18).
Figure 8-18
Capture Repository Variables---CICS environment (4 of 6)
Enter the information required by this panel.
400.22
INTERTEST (Supply these values if INTERTEST is installed):
Enter the following if INTERTEST debugging feature is installed in this region.
400.22a
Intertest ASM Program - [Default: IN25SYMA]
Enter the ASM program name.
400.22b
Intertest COBOL Program - [Default: IN25COB2]
Enter the COBOL program name.
400.22c
Intertest PL/I Program - [Default: IN25SYMP]
Enter the PL/I program name.
400.22d
Intertest PROTSYM Dataset - [Default: None]
Enter the PROTSYM data set name.
400.22e
Intertest STEPLIB - [Default: None]
Enter the STEPLIB program name.
400.23
Minimum Transaction ID for this Version: - [Default: AAAA]
Enter the minimum transaction ID for this version.
400.24
Maximum Transaction ID for this Version: - [Default: AA99]
Enter the maximum transaction ID for this version.
400.24a
If one Transaction ID is used for all CICS Rules, enter it here
Enter the single transaction ID for all CICS rules in this version.
400.25
Number of CICS Regions you want to configure for version 1 - [Default: None]
Enter the number of CICS regions you want to configure for repository version 1.
The following two panels are presented for each region requested to allow you to configure each region separately.
Complete this panel and proceed to the next. The fifth of six panels capturing repository variables is shown in Figure
8-19.
Planning and Installing AppBuilder for the Mainframe
page 152 of 284
Figure 8-19
Capture Repository Variables---CICS environment (5 of 6)
Enter the information required by this panel.
400.26
Enter the VTAM name of this region - [Default: None]
Enter the VTAM name of this region.
400.27
Enter the VTAM APPLIDs for LU2 processing: 1 - [Default: A06HPS1] 2 - [Default: A06HPS2] 3 [Default: A06HPS3]
The AppBuilder LU2 CICS Auto-install feature allows AppBuilder objects (rules, components, etc.) to be
automatically defined to CICS during AppBuilder preparation (compile, linkedit, etc.). Depending on the object being
prepared, it will connect to CICS via the VTAM applids and execute the following transactions:
HS06 - AppBuilder newcopy transaction
CEDA - CICS transaction to define AppBuilder objects
CEMT - CICS transaction to close and open AppBuilder VSAM files
UTBL - AppBuilder transaction to add rule/tranid to AppBuilder incore table (HPSTBLE2) Enter three
VTAM application IDs.
400.28
Define AB CICS group to the startup group list? (Y/N ) - [Default: N]
Specify whether the AppBuilder CICS groups should be defined to the startup group list during a rule or component
prepare.
400.29
Define AB transactions during rule prepare? (Y/N) - [Default: Y]
Specify if transactions are defined during a rule prepare.
400.30
Should the AB transaction UTBL be executed?
(Y/N) - [Default: Y]
Specify if the UTBL transaction should be executed during a rule prepare.
400.31
Enter the startup group list name for AB groups - [Default: None]
Enter the startup group list name for AppBuilder groups.
400.32
AB groups will be added to the startup list AFTER or BEFORE a specified group. Enter the
specified group name here. - [Default: None]
Enter the specified group name.
400.33
Enter A to add new groups AFTER this group or B for BEFORE - [Default: B]
Specify where the AppBuilder group will be added to the group named above.
400.34
Temporary groups will be built from a one-character prefix and the Userid. Specify the one​‐
character prefix for temporary groups - [Default: H]
Planning and Installing AppBuilder for the Mainframe
page 153 of 284
Enter a one character prefix for temporary groups. Complete this panel and proceed to the next.
The last of six panels capturing repository variables is in Figure 8-20.
Figure 8-20
Capture Repository Variables---CICS environment (6 of 6)
Enter the information required by this panel.
400.35
CICS group names for AppBuilder objects may be a constant string OR a constant string
combined with the AppBuilder project name. The combined length may not exceed 8 characters. [Default: H]
If you use the project name in the group name, enter H if the AppBuilder project should come first or C if the
constant string should come first - [Default: H]
400.36
For PPTs:
Enter the following information for PPTs.
400.36a
Use AB project name as part of the group name? (Y/N ) - [Default: Y]
Specify if the AppBuilder project name is used as part of the group name.
400.36b
Enter the optional string to use in the group name - [Default: ABGRP]
Enter an optional string to use in the group name.
400.37
For PCTs:
Enter the following information for PCTs.
400.37a
Use AB project name as part of the group name? (Y/N ) - [Default: Y]
Specify if the AppBuilder project name is used as part of the group name.
400.37b
Enter the optional string to use in the group name - [Default: ABGRP]
Enter an optional string to use in the group name. Complete this panel, and proceed to the next.
Option 2 - Create/Submit Installation Jobs
Figure 8-21 shows you returning to the panel you saw previously in Figure 8-14. This time you perform option 2
Create/Submit Installation Jobs.
Figure 8-21
Apply SVC34 to Repository, Capture/Submit Installation Jobs
Planning and Installing AppBuilder for the Mainframe
page 154 of 284
This panel applies the repository upgrade to the repository in two option steps. Select from among the following
options:
1. Capture Version Variables
2. Create/Submit Installation Jobs
When you have completed option 1, perform option 2.
Option 2 Create/Submit Installation Jobs shows two jobs that you need to process, Figure 8-22.
Regenerate/edit /submit Installation Jobs
The next panel defines the repository jobs that install updates to your repository, as Figure 8-22 shows.
Figure 8-22
Regenerate/Edit/Submit Installation Jobs
Execute the jobs in order from the top down. Select from the following actions:
Regenerate (REGEN)
View (V or VIEW)
Submit (SUB) jobs to update the software
If you enter an invalid command in the action column, the message INVALID ACTION appears in the Status column.
Press Enter to clear this message and continue.
The following describes the repository jobs:
REPJOB1 — NonDB2 processing. After this job completes, the following new data sets are created:
Note
&REPQUAL is the Repository Modification Data Set Qualifier for AppBuilder data sets.
Table 8-5
Repository Modification Libraries
Planning and Installing AppBuilder for the Mainframe
page 155 of 284
&REPQUAL..LOADCI
Note
&USRVQUAL is the System Data Set Qualifier for AppBuilder data sets. You have more than one
set of the following data sets if you specified more than one version during the Enterprise Repository
installation.
Table 8-6
User Libraries
&USRVQUAL..LOADCI
&USRVQUAL..NCALCI
Note
&VSUVQUAL is the VSAM User Qualifier for AppBuilder VSAM data sets. You have more than one
set of the following data sets if you specified more than one version during the Enterprise Repository
installation.
Table 8-7
User VSAM Data Sets
&VSUVQUAL..&VIEWDEF
&VSUVQUAL..&RULESRC
&VSUVQUAL..HPS004D1.RLRELATN
&VSUVQUAL..&VIDTEXT
&VSUVQUAL..HPS002D1.TESTDATA
&VSUVQUAL..HPS006D1.ERRLOG
&VSUVQUAL..HPSBC1D1.BDCTDATA
&VSUVQUAL..HPSBC2D1.BDCTTBL
&VSUVQUAL..HPSDNART.RTABLE
&VSUVQUAL..HPSDNAIN.INI
&VSUVQUAL..DNAFXFER
Refer to Chapter 6, “Installing the Enterprise Repository” in this document for additional information about AppBuilder
data sets.
Note
&VIEWDEFC, &RULESRCC, &RLRELATC, and VIDTEXTC are the values entered in prompt 400.3.
REPJOB2 — DB2 PROCESSING
You can monitor each jobs progress in the Status column. The following lists indicators that are displayed in the
Status column.
[blank] — No activity is occurring.
SUBMITTED — A job is in progress.
COMPLETED — A job is completed.
When you have competed these jobs successfully, press F3 to exit this panel. Return to the Apply Upgrade to
Repository panel, Figure 8-23.
Activate Repository
After completing Figure 8-22, you have applied all the repository updates for SVC34. Figure 8-23
Planning and Installing AppBuilder for the Mainframe
page 156 of 284
activates the repository.
Figure 8-23
Activate Repository
This panel appears for you to select option 3 Activate Repository. This option concludes the installation of the CICS
Online upgrade to your repository.
Planning and Installing AppBuilder for the Mainframe
page 157 of 284
Post-installation Notes: Installing CICS Online Prepration
Workbench & Enterprise Server
Perform the following step to complete and verify the successful installation of the AppBuilder CICS
Online Preparation Workbench and CICS Enterprise Server.
•
•
•
•
•
Define the following libraries to the DFHRPL concatenation of the target AppBuilder CICS regions:
&USRVQUAL..LOADCI
&USRVQUAL..LOADBS
&REPQUAL..LOADCI
&MODQUAL..LOADCI
&BASEQUAL..LOADCI
Planning and Installing AppBuilder for the Mainframe
page 158 of 284
Installing TCP IP Listener for IBM CICS
Although it is not typically part of the installation, you can install the TCP/IP Listener for IBM CICS using the
instructions in this section. This installation is optional and only applies to specific customers.
The TCP/IP Listener for IBM CICS enables AppBuilder rules for IBM z/OS CICS to communicate over TCP/IP with
AppBuilder communications programs on other platforms. This topic describes how to install the product in an IBM
z/OS environment.
Meeting Software Requirements
Performing Post-Installation Steps
Planning and Installing AppBuilder for the Mainframe
page 159 of 284
Meeting Software Requirements
The installation requires that some NetEssential modules be linked non-reentrant, as specified in section 7.3 of the
TCP/IP V3R2 for MVS: CICS TCP/IP Socket Interface Guide and Reference published by IBM.
These modules are:
DNALSTNR
HPSDNA00
The TCP/IP Listener for IBM CICS has the following software requirements:
TCP/IP V3R2 for MVS: CICS TCP/IP Socket Interface. You can verify the version by running the TSO
command NETSTAT. The EZA0217I message displays the version. Successful execution of the CICS
transaction EZAO indicates that the CICS TCP/IP Socket Interface has been installed.
NetEssential client authentication exit. Samples are shipped with AppBuilder. See the Configuring
Communications Guide for details.
The Listener uses the CICS VERIFY command to validate the end user’s CICS user ID and password. You use the
Security Node or client authentication exit to pass the user information to CICS from the client. You can also bypass
the CICS VERIFY by coding a DNAINI parameter. See DNAINI Settings for details.
Planning and Installing AppBuilder for the Mainframe
page 160 of 284
Performing Post-Installation Steps
Perform the following steps after the installation is complete:
STEP 1 - Define the NetEssential resources to CICS
The samples provided in this section contain the necessary program, transaction, files, and definitions for CICS.
Sample - Define the program DNALSTNR to the CICS region
DEFINE PROGRAM(DNALSTNR) GROUP(nnnnnnnn)
DESCRIPTION(NETESSENTIAL TCP LISTENER)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES)
DATALOCATION(ANY) EXECKEY(CICS) EXECUTIONSET(FULLAPI)
Sample - Define a listener transaction with any valid transaction ID
DEFINE TRANSACTION(tranid) GROUP(nnnnnnnn)
DESCRIPTION(NETESSENTIAL TCPIP LISTENER)
PROGRAM(DNALSTNR) TWASIZE(0) PROFILE(DFHCICST)
STATUS(ENABLED) TASKDATALOC(ANY) TASKDATAKEY(CICS)
DYNAMIC(NO) PRIORITY(255) TCLASS(NO) DTIMOUT(NO)
INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO) TPURGE(NO)
DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
Note that the NetEssential TCP/IP Listener program and transaction ID must be defined with EXECKEY(CICS). If it
is not and storage-protection is enabled, the transaction will fail with an ASRA abend code indicating an incorrect
attempt to overwrite the CDSA by EZACIC01. In addition to storage-protection being disabled, if the EZA* resources
are defined with EXECKey=USER, DNALSTNR can also fail.
You can rename the NetEssential TCP/IP Listener transaction to conform to your environment standards. Do not
forget to create a EZAC configuration record for the new transaction ID.
STEP 2 - Define the listener transaction(s) to the CICS Socket interface
Use the IBM-supplied EZAC transaction to create a configuration record for each Listener transaction. If you use
multiple TCP/IP Listeners for IBM CICS applications, be sure to assign each a unique transaction ID and port
number. Define the transaction IDs to the DNALSTNR program and configure the port numbers for the CICS region.
For details on the EZAC transaction, refer to the CICS TCP/IP Socket Interface Guide and Reference.
Planning and Installing AppBuilder for the Mainframe
page 161 of 284
Configuration Record Fields
The NetEssential Listener uses the following EZAC configuration record fields:
APPLID and TRANID are used to identify (are the keys to) the Listener's record. In the APPLID field, specify the
name of the CICS region and in the TRANID field, specify the Listener’s transaction ID.
NUMSOCK is the maximum number of connections used in the INIAPI() call (including those that are pending to be
taken and those that are to be read) that the Listener will handle. When reached, the Listener will not process any
new connection requests until one of the existing sessions terminates. Messages are displayed when the
MAXSOCK condition is reached and when MAXSOCK is no longer valid.
The current limitation for a CICS C program, such as the Listener, is 255. It can also be limited by the
SOMAXCONN value from the TCPIP configuration file <profile.tcpip> for the system. The value used is 255, unless
SOMAXCONN is less than this value.
Note that this is not the maximum number of started rule transactions, it is only the maximum number of concurrent
sockets the Listener can handle. Once they are taken by the rule transaction and closed by the Listener, they are no
longer charged to the Listener.
The number of concurrent CICS transactions using the Sockets’ interface is specified in the NTASKS parameter in
the EZAC CICS record. NTASKS specifies the number of reusable MVS subtasks to be allocated. This should be
the highest number of concurrent CICS transactions that will use Sockets’ interface, excluding the Listener(s).
ACCTIME specifies the timeout used in the SELECT() API call when the Listener waits for socket activity. "Activity"
can be either a new connection request where data is available on an already accepted or started connection, or the
rule transaction has taken the socket. During this time, the Listener is in a wait state and cannot check for shutdown
requests or process any other timeouts, such as GIVESOCKET.
A larger value reduces overhead but may increase the time it takes for the Listener to detect a shutdown request
because the call is not interrupted for such requests. The default value is 60 seconds.
GIVTIME specifies the GIVESOCKET timeout. The Listener attempts to pass the socket to the started rule
transaction by issuing a GIVESOCKET. If the GIVTIME expires before the rule takes the socket (TAKESOCKET),
the Listener issues an error message and closes the socket. Note that this process is not exact because the
Listener does not set GIVESOCKET timers, but during each SELECT cycle, as defined in ACCTIME, expired
GIVESOCKET timeouts are checked.
WLM groups are used to register the service with WLM and are passed “as is” to EZACIC12 (the WLM De/Registration module).
Other fields in the EZAC Configuration record are used by the Listener, such as:
PORT specifies the port number the listener will use.
Planning and Installing AppBuilder for the Mainframe
page 162 of 284
IMMEDIATE - A value of YES indicates that the Listener is to be automatically started when the CICS Sockets
interface is started.
BACKLOG specifies the depth of the backlog queue or number of connection requests used in the LISTEN() call that
will queue for the Listener to accept. Specify the value depending on whether it is more desirable to have the client
wait for the listener or for the connection request to fail and retry. It works in conjunction with the NUMSOCK
parameter.
Note
After creating new records, the CICS Sockets interface must be restarted to pick up the new
definition. Use the EZAO transaction to stop and restart the sockets interface.
STEP 3 - Configure the NetEssential runtime options
NetEssential is highly configurable. Some parameters are specified with the CICS Sockets EZAC configuration
record, as described in Configuration Record Fields. Most configuration parameters are specified with DNAINI
settings. Use the NEAD transaction to update the NetEssential initialization file (DNAINI). Select option 2
‘Initialization File’ from the main menu and add or modify the settings.
In most cases, the Listener reads the configuration settings once, at startup. Therefore, the Listener should be
restarted in order to read modifications to the settings. Use Option 6 (Cache Initialization File) on the Operations
menu (Option 1 ‘Operations’ from the main menu) to activate (re-cache) the changes to the initialization file.
It is recommended that you specify keywords and their values even when using default values because the DNAINI
settings are cached in order to improve performance. However, when an entry is not in the cache, NetEssential will
issue a physical I/O request in an attempt to read it from the file. For example, every rule transaction must check for
an OpenCOBOL environment, so it will always attempt to access the OPEN-COBOL /ENABLED setting. See
DNAINI Settings for a list of the settings.
STEP 4 - Start the CICS Socket Interface
Use the EZAO transaction to re-start the CICS TCP/IP Socket Interface, as described in TCP/IP V3R2 for MVS:
CICS TCP/IP Socket Interface Guide and Reference published by IBM.
For example, to stop the CICS Sockets interface issue the following command:
EZAO,STOP,CICS
Use the following command to start the CICS Sockets interface:
EZAO,START,CICS
Planning and Installing AppBuilder for the Mainframe
page 163 of 284
STEP 5 - Starting the Listener
All the TCP/IP Listeners configured to start automatically (IMMEDIATE=YES. See STEP 2 - Define the listener
transaction(s) to the CICS Socket interface) will be started as a result of successfully starting the CICS Sockets
interface (EZAO,START,CICS). All other Listeners must be manually started using the EZAO transaction. For
example:
EZAO,START,LIST(NETL)
where NETL is the Listener’s transaction ID. Use the TSO command NETSTAT to verify the start of the Listener.
STEP 6 - Routing service requests to the CICS region
Use the NetEssential Configurator on the client workstation to route service requests to the CICS region over
TCP/IP. Note that you need to specify the CICS transaction ID of the NetEssential execution server, not the listener,
in the Server ID field.
Planning and Installing AppBuilder for the Mainframe
page 164 of 284
Usage Notes
When using the CICS Listener in an MRO/Sysplex environment, TCP/IP should be installed in the front-end running
the Listener transaction; and in any back-end region running AppBuilder transactions.
Warning
A CICS Sockets restriction requires all regions in question to be in the same LPAR.
When a RPC call is received, the front-end CICS looks at the message sent by the client and passes the socket
opened by the client request to the back-end CICS, which receives the message and calls the rule requested and
sends the reply.
The BACKLOG parameter for the port should be adjusted depending on the transaction load, using the EZAC
transaction. Symptoms of the value being too low can be communication errors with tcpip protocol error code 10060.
Planning and Installing AppBuilder for the Mainframe
page 165 of 284
DNAINI Settings
The following is a list of the available DNAINI settings used to configure the NetEssential TCP/IP parameters. Note
that there are other required generic settings.
TCP/IP Port Number
Security Authentication
Session Termination Semantics
TCP/IP Listener Abend Handler
DoS Prevention
NetEssential Tracing
IP Listener Dynamic Buffer Size
OPEN-COBOL
USE_PREAMBLE_RULEID
Connection Termination Semantics
SERVER_RECV_TIMEOUT
TCPIP_ABENDPROGRAM
TCP/IP Port Number
We strongly recommend maintaining an EZAC configuration record; however, if none exists, the Listener may
attempt to use the value specified for the TCP_PORT_NUMBER variable in the DNA_SERVER section. You can
add it with a value of nnnn, where nnnn is the port number assigned to the CICS region. For example:
DNA_SERVER
TCPIP_PORT_NUMBER
nnnn
Security Authentication
Add the variable LISTENER_SECURITY to the new MVS_LISTNER section. This variable determines how the
Listener authenticates the provided user credentials.
The valid values are:
YES – issues a CICS VERIFY on the user ID and password and starts the rule using the user ID.
NO - No security check is done in the Listener.
PART - the user ID and password are not checked but the rule is started with the user ID.
For example:
MVS_LISTENER
LISTENER_SECURITY
YES
Session Termination Semantics
Planning and Installing AppBuilder for the Mainframe
page 166 of 284
There are numerous enhancements in NetEssential regarding session termination semantics. These enhancements
provide control over session termination processing and are implemented with two DNAINI settings:
DNA_SERVER
TCPIP_CLOSEWAIT
nnn
DNA_SERVER
TCPIP_LINGERTIME
nnn
where nnn is the timeout value, specified in seconds. The values for these variables may be different.
After sending the last response to the client, the CICS service (NetEssential) closes the connection. This can be
done in any of the following ways:
1. Issue a CLOSE() for the socket.
2. Issue a SELECT with a timeout as specified for TCPIP_CLOSEWAIT, and after either receiving data (the
close indication) from the client or when the timeout expires, issue a CLOSE() for the socket.
3. Issue a blocking RECV() and after receiving data (the close indication) from the client, issue a CLOSE() for
the socket.
This behavior is determined primarily according to the value of TCPIP_CLOSEWAIT:
If the TCPIP_CLOSEWAIT timeout is not specified or is empty - Do NOTHING (option 1).
If the TCPIP_CLOSEWAIT timeout is a positive number - Issue a SELECT (option 2).
Else (TCPIP_CLOSEWAIT timeout is invalid, negative or zero) - Issue a blocking RECV (option 3).
Regardless of the SELECT/RECV, you can also optionally specify a LINGER time.
If the TCPIP_LINGERTIME is a positive number - Set SO_LINGER to TCPIP_LINGERTIME.
Else only in the event of SELECT/RECV errors - Set SO_LINGER to default (5 seconds).
If the SELECT timeout or setting blocking mode (IOCTL) fails, SO_LINGER will always be set. If a valid value is not
specified, SO_LINGER is set to the default value (5 seconds).
Note
In the event of SELECT/RECV errors, SO_LINGER will not be set.
To disable the Linger option, specify a LingerTime of 0 (zero); SO_LINGER will not be set.
TCP/IP Listener Abend Handler
It may be required to perform some clean-up operation, such as WLM de-registration, in the unexpected case of a
Listener Abend. This would need to be done in an external abend handler program. A sample program, DNAABEND,
is provided in both source (C) and object format that performs WLM de-registration.
Planning and Installing AppBuilder for the Mainframe
page 167 of 284
To activate the Abend Handler for the NetEssential TCP/IP Listener, specify DNAABEND as the value for the
TCPIP_ABENDPROGRAM variable in the DNA_SERVER section. For example:
DNA_SERVER
TCPIP_ABENDPROGRAM
DNAABEND
The Listener checks the value and issues a 'HANDLE ABEND PROGRAM(DNAABEND)' if it is not empty.
Setting Up the Sample
The source is standard C and does not have any special compiler requirements. It contains EXEC CICS statements
and needs to be translated by the CICS C translator. When linking (binding), the CICS TCP/ IP module must be
included.
The Linkage-Editor cards might be similar to the following entries:
INCLUDE OBJLIB(DNAABEND)
INCLUDE SYSLIB(EZACIC07)
INCLUDE SYSLIB(DFHELII)
INCLUDE SYSLIB(DFHCPLC)
INCLUDE SYSLIB(DFHCPLRR)
NAME DNAABEND(R)
The program must be defined to CICS as a C program.
Note
The Abend Handler (DNAABEND) program's definition must match that of the Listener. For example,
if the Listener transaction is defined as TASKDATAKEY(CICS), the Abend Handler program's
definition must specify EXECKEY(CICS) or An 'AEZD' abend will occur if not.
DoS Prevention
In order to defend against DoS attacks, the NetEssential CICS TCP/IP Listener incorporates an "emergency brake".
It consists of a configurable timeout and the Listener will issue an error message and close the socket if it expires
before data is received.
Note
During the timeout period, the Listener will probably consume CPU cycles, as there is always "data"
waiting to be processed. However, other connections, existing and new requests, will be processed.
Planning and Installing AppBuilder for the Mainframe
page 168 of 284
The desired timeout value in seconds is specified with a DNAINI setting:
DNA_SERVER
SERVER_RECV_TIMEOUT
nnn
Note
Use caution when specifying the timeout value. Ensure that is takes into account the slowest
network connection, yet keep it as low as possible to avoid unnecessary CPU cycles.
NetEssential Tracing
NetEssential has a tracing feature that can be used in a test environment or to troubleshoot problems. The level of
trace output is specified with the DEBUGLVL variable in the TRACING section. In the same section, HPSCATS
specifies the CICS file (DD) name that points to the VSAM error message text file. The name does not have to be
DNAERROR, any valid CICS name is acceptable.
TRACING
DEBUGLVL
n
TRACING
HPSCATS
0:DNAERROR
where n can be one of the following values, either numeric or text (as-is):
0 - ERRORS = report only ERROR + status view
1 - ERRORS_AND_LENGTHS = report level 0 + additional messages + data lengths
2 - ERRORS_AND_DATA = report level 1 + contents of input/output data
3 - ERRORS_AND_TRACES = report level 2 + internal tracing.
IP Listener Dynamic Buffer Size
The TCP/IP Listener for CICS now supports a dynamic user-configurable sized buffer to be passed to
dna_TcpMVSDecode. This value is specified via a DNAINI setting:
DNA_SERVER TCPIP_PEEKBUFSIZE = 144
The value specified indicates the number of bytes that the Listener will pass to the dna_TcpMVSDecode function.
The default value is 144, which is also the minimum. If a lower value is specified, a value of 144 will be used.
OPEN-COBOL
Planning and Installing AppBuilder for the Mainframe
page 169 of 284
Example:
OPEN-COBOL
OPEN-COBOL
OPEN-COBOL
OPEN-COBOL
ENABLED
DATE_FORMAT
TIME_FORMAT
EIB_COMMAREA
Y
%Y-%0m-%0d
%0t.%0m.%0s.%0f
N
To determine whether it is a standard AppBuilder or OpenCOBOL runtime environment, NetEssential checks the
ENABLED setting in the OPEN-COBOL section. If set to Y[ES], the DATE_FORMAT and TIME_FORMAT settings
are used to determine the format of OpenCOBOL date and time fields.
Note
Currently the only DATE format supported is 'ISO' or '%Y-%0m-%0d', resulting in yyyy-mm-dd. The
only TIME format supported is '%0t.%0m.%0s.%0f' which implies hh.mm.ss.mls. Leading zeros
must be present. You may however, change either the DATE or TIME delimiters.
Legend:
yyyy
mm
dd
hh
mm
ss
mls
-
Year, including the century.
Month
Date
Hours in a 24-hour clock
Minutes
Seconds
Milliseconds
USE_PREAMBLE_RULEID
Example:
DNA_SERVER
USE_PREAMBLE_RULEID
Y
In order for the CICS TCP/IP Listener (DNALSTNR) to support the presence of security cookies, the Listener needs
to extract the correct rule-id to perform the required transaction switching. A new DNAINI setting in the
DNA_SERVER section is checked. If the value of the keyword USE_PREAMBLE_RULEID is 'Y' (or 'y'), the (lookedup) rule name will be taken from the preamble.
There are circumstances in which the rule ID in the preamble will be in ASCII. Therefore, the first character in the
rule ID is checked. If in the range x'41' - x'5A' (ASCII A-Z), the name is assumed to be in ASCII and will be
converted to EBCDIC. This conversion includes characters, lower and upper case, digits and blank:
Planning and Installing AppBuilder for the Mainframe
page 170 of 284
ABCDEFGHIJKLMNOPQRSTUVWXYZ,abcdefghijklmnopqrstuvwxyz,0123456789and''(blank).
Note
The security cookie is used by the Authentication exit. To implement this, HPSDNA00 must be relinked with the customized authentication exit (DNACEXIT) and the exit must also be enabled via
DNAINI settings:
DNA_EXITS
SRV_AUTHENT_EXIT
STATIC_LINK
Connection Termination Semantics
TCPIP_CLOSEWAIT
Example:
DNA_SERVER
TCPIP_CLOSEWAIT
<seconds>
TCPIP_LINGERTIME
Example:
DNA_SERVER
TCPIP_LINGERTIME
<seconds>
The NetEssential TCP/IP implementation now provides greater flexibility to implement the various connection closing
scenarios, as follows:
There are two DNAINI settings in the DNA_SERVER section: TCPIP_CLOSEWAIT and TCPIP_LINGERTIME, both
indicate a timeout value, specified in seconds.
The logic is as follows:
If the TCPIP_CLOSEWAIT timeout is not specified or is empty: Do NOTHING.
If the TCPIP_CLOSEWAIT is a positive number: Issue a SELECT.
Else (TCPIP_CLOSEWAIT timeout is invalid, negative or zero): Issue a Blocking RECV.
Regardless of the SELECT/RECV, the user can also optionally specify a LINGER time. If the LINGERTIME is a
positive number: Set SO_LINGER to TCPIP_LINGERTIME. Otherwise SO_LINGER is not set.
Planning and Installing AppBuilder for the Mainframe
page 171 of 284
Note
In the event of SELECT/RECV errors, SO_LINGER will not be set (as it will most probably fail as
well). If the SELECT time out or setting blocking mode (IOCTL) fails, SO_LINGER will always be set.
If a valid value is not specified, SO_LINGER is set to the default value (5 seconds). To disable the
Linger option, specify a TCPIP_LINGERTIME of 0 (zero), which will result in SO_LINGER not being
set.
SERVER_RECV_TIMEOUT
Example:
DNA_SERVER
SERVER_RECV_TIMEOUT
3
The Listener was vulnerable to DoS attacks by a rogue program connecting and sending only a few bytes of data.
The listener is notified that data is available and it attempts to receive (peek) a minimum amount of expected header
data. The listener loops attempting to read the data as it is not available and the listener enters a wait (for data)
state, only to be woken due to the already pending data.
The above scenario is highly unlikely unless someone is maliciously trying to sabotage the listener. In order to
defend against such an attack, the Listener was enhanced and an "emergency brake" was implemented. This
consists of a configurable timeout, that if expires before data is received, the Listener will issue an error message
and close the socket.
Note
During the timeout period, the Listener will probably consume CPU cycles as there always is "data"
waiting to be processed. Other connections, existing and new requests, will be processed.
TCPIP_ABENDPROGRAM
DNA_SERVER
TCPIP_ABENDPROGRAM
<program>
The Listener checks the value, and if not empty, the Listener will issue a 'HANDLE ABEND PROGRAM(<program>)'.
No error handling is done.
A sample program - DNAABEND - is also provided in source (C) and object format. As provided, it handles the WLM
deregistration. However, the customer can add functionality to suit their needs. For example, restart the Listener.
Planning and Installing AppBuilder for the Mainframe
page 172 of 284
How to Setup the Sample:
The source is standard C and does not have any special compiler requirements. It contains EXEC CICS statements
and needs to be translated by the CICS C translator.
When linking (binding), the CICS TCP/IP module must be included. The Linkage-Editor cards would be something
like:
INCLUDE OBJLIB(DNAABEND)
INCLUDE SYSLIB(EZACIC07)
INCLUDE SYSLIB(DFHELII)
INCLUDE SYSLIB(DFHCPLC)
INCLUDE SYSLIB(DFHCPLRR)
NAME DNAABEND(R)
The program must be defined to CICS as a C program.
Note
The abend handler (DNAABEND) program's definition must match that of the Listener. This means
that if the Listener transaction is defined as TASKDATAKEY(CICS), the abend handler program's
definition must specify EXECKEY(CICS). (An 'AEZD' abend will occur if not.)
Planning and Installing AppBuilder for the Mainframe
page 173 of 284
Configuring AppBuilder for a Multi-CICS Region Environment
This section describes how to configure your AppBuilder/CICS Runtime environment for Multi-CICS Region support
with a single Terminal Owning Region (TOR) and a single Application Owning Region (AOR). It is assumed that the
TOR will be used solely to support terminals and the AOR will be used to support the execution of all AppBuilder
applications.
Planning and Installing AppBuilder for the Mainframe
page 174 of 284
AppBuilder Repository CICS Load Libraries
The AppBuilder Repository CICS Load Libraries are:
&USRVQUAL..LOADCI
&USRVQUAL..LOADBS
&REPQUAL..LOADCI
&MODQUAL..LOADCI
&BASEQUAL..LOADCI
These libraries must be added to the DFHRPL concatenation of both the TOR and AOR CICS Regions in the order
listed above.
Planning and Installing AppBuilder for the Mainframe
page 175 of 284
AppBuilder CICS VSAM Files
Only the HPS006D1.ERRLOG VSAM file needs to be defined to the TOR. This ERRLOG file can be unique from the
ERRLOG file defined to the AOR or can be the same file by being remotely defined to the TOR and locally defined to
the AOR. All AppBuilder/CICS files must be defined to the AOR.
Planning and Installing AppBuilder for the Mainframe
page 176 of 284
AppBuilder/CICS Transient Data Queues
Only the HPEL Error Log Transient Data Queue needs to be defined to the TOR. All AppBuilder/CICS Transient Data
Queues must be defined to the AOR.
Planning and Installing AppBuilder for the Mainframe
page 177 of 284
AppBuilder/CICS Transactions
The following AppBuilder/CICS Transactions must be defined locally to the TOR:
ENAE - Enable AppBuilder/CICS environment
HPEL - Log AppBuilder/CICS Error Messages
UTBL - Update HPSTBLE2 incore table
HPI0 - Initialize AppBuilder Kernel
NE2I - Initialize NetEssential middleware
All other AppBuilder/CICS Transactions must be defined as remote transactions to the TOR so that they can be
Transaction Routed to the AOR. All AppBuilder/CICS Transaction must be defined to the AOR.
Planning and Installing AppBuilder for the Mainframe
page 178 of 284
AppBuilder/CICS Programs
The HPSSTART, HPESI10, and HPSINIRD programs must be placed in the Program List Table Post Initialization
(PLTPI) for both the TOR and the AOR.
HPESI10
HPSCGAP
HPSENAEP
HPSERRLG
HPSINIRD
HPSLMSG
HPSSTART
HPSTBLE1
HPSTBLE2
HPSTBLE3
HPSTBLE4
HPSTBLE5
HPSUTBL
HPSXZCAT
Planning and Installing AppBuilder for the Mainframe
page 179 of 284
AppBuilder/CICS Terminals
The AppBuilder LU2TYPE terminals that are used to support the Batch interface (the AppBuilder Auto- install
feature) must be defined locally to both the TOR and the AOR.
Planning and Installing AppBuilder for the Mainframe
page 180 of 284
Introduction to CICS EXCI Resource Definition
AppBuilder currently maintains the CICS Resource Definitions and associated program maintenance using the
HMALU2B program. HMALU2B is a batch program that establishes a 3270 terminal connection with CICS and
executes transactions based on an input "script". The purpose of these script commands is to create and/or update
CICS Resource Definitions and install the necessary components, including a new copy of the program, etc. in the
running region.
AppBuilder provides an alternative to the existing HMALU2B for managing CICS Resource Definitions as part of the
prepare process. Whereas, HMALU2B utilizes a batch 3270 terminal emulation, the CICS EXCI RD uses EXCI - a
standard IBM interface providing external access to CICS.
Highlights of this feature include:
User customizations for transaction and program definitions.
Per target CICS region customizations, based on the region's functionality (AOR, TOR, etc.). For example,
define only the transaction, only the program, or both.
Support for updates across LPAR boundaries.
With the implementation of CICS EXCI RD, the following existing HMALU2B functionality is maintained, regardless
of the execution environment, whether it be single region, multiple regions (MRO/ISC), or across the CICSPlex:
Create the required CSD resource definition (Transaction: CEDA).
Install the definitions into the running CICS region ((Transaction: CEDA).
Update the HPS Tables (HPSTBLE1/2) with the required definition (Transaction: UTBL).
Install a new copy of the (rule/component) program (Transaction: HS06/CEMT).
Note
Although AppBuilder Solutions will continue to support the existing HMALU2B, new enhancements
implemented in the EXCI RD are not guaranteed to be implemented in the HMALU2B program.
CICS EXCI RD is comprised of the following components:
Configuration support including FTSKELS, INI settings, script and JCL generation, etc. The required
modifications depend on the other components.
Communication engine.
Client/Server application programs. The client program is responsible for invoking the communication engine
to communicate with the server program. The server program processes the request and returns a response
code on which the client must react.
Planning and Installing AppBuilder for the Mainframe
page 181 of 284
CICS EXCI Resource Definition
Prerequisites
To utilize EXCI, the required support must be enabled in CICS. This also requires system configuration,
e.g. DFHIRP must be installed in the MVS extended link pack area. Please refer to the CICS Documentation for
details of the EXCI installation and configuration procedures and requirements. For detailed information about the INI
files, refer to the INI Settings Reference Guide within the AppBuilder documentation set.
Configuration Considerations
No special CICS configuration is required to implement the resource definition utility; however, the following program
definitions are needed:
DEFINE PROGRAM(ABXICSRV) GROUP(AB34)
DESCRIPTION(AppBuilder EXCI RD Server)
LANGUAGE(C) DATALOCATION(ANY) EXECKEY(USER)
The following INI settings support configuring and customizing the CICS EXCI RD feature. First, the variable,
CICS.COMMSTEP, determines whether the LU2 step will use the original HMALU2B (program and JCL), which is the
default, or CICS EXCI. It is also possible to configure AppBuilder not to perform any RD functions.
The settings span a few members and sections, as shown by the 'INI file' and 'Section' columns in the following
table. The value assigned to Region Name dictates the name of the INI file member containing the settings for that
particular region.
Table 1 User Environment by Version Changes
INI File
Section
INI Setting
Value(s)
Description
@USRENVn
REGIONS
REGIONCNT
Number of
Regions
Number of CICS regions.
There must be a REGIONn INI setting for
each region.
@USRENVn
REGIONS
CICSREGn
Region
Name
Name of region. n is a numeric character,
from 1 to the number of regions specified
in NUMREGIONS.
This also specifies the name of the INI
member containing variables for the
region.
(CICSRGN)
CICS
COMMSTEP
R/L/N
Specify R for AppBuilder to use EXCI, L
to use HMALU2B,or N for no RD actions.
(CICSRGN)
CICS
RDPROG
Server
program
name
Server program invoked by the EXCI
client. The default is ABXICSRV.
Planning and Installing AppBuilder for the Mainframe
page 182 of 284
(CICSRGN)
CICS
CICSEXCI
EXCI
runtime
library
The name of the EXCI runtime library
required to execute EXCI.
(CICSRGN)
REGION1
DOPROGDFN
Y/N
Specifies whether EXCI actions include
define program.
If not set, the value for DOPROG is used.
(CICSRGN)
REGION1
DOPROGINS
Y/N
Specifies whether EXCI actions include
install program.
If not set, the value for DOPROG is used.
(CICSRGN)
REGION1
PROGPARM
Define
program
parameters.
Additional parameters to use on the
CEDA DEFINE PROGRAM
(CICSRGN)
REGION1
DOTRANDFN
Y/N
Specifies whether EXCI actions include
define transactions.
If not set, the value for DOTRANS is
used.
(CICSRGN)
REGION1
DOTRANINS
Y/N
Specifies whether EXCI actions include
install transactions.
If not set, the value for DOTRANS is
used.
(CICSRGN)
REGION1
TRANPARM
Define
transaction
parameters
Additional parameters to use on the
CEDA DEFINE TRANSACTION
(CICSRGN)
REGION1
RULE_RES
SET_RES
COMP_COBOL_RES
COMP_PLI_RES
COMP_ASM_RES
COMP_C_RES
REP_C_RES
Y/N
Determines whether to define the entity
as resident. If not specified, no action is
taken. Otherwise the keyword
RESIDENT(NO) or RESIDENT(YES) is
added to the additional parameters for the
Define Program (PGMPARM).
(CICSRGN)
REGION1
DATALOC
BELOW /
ANY
Specifies whether storage allocated to the
program is below the line or above. If not
specified, no action is taken. Otherwise
the keyword DATALOC(DATALOC) is
added to the additional parameters for the
Define Program (PGMPARM).
(CICSRGN)
REGION1
TASKDATALOC
BELOW /
ANY
Specifies whether storage allocated to the
task is below or above the line. If not
specified, no action is taken. Otherwise
the keyword
TASKDATALOC(TASKDATALOC) is
added to the additional parameters for the
Define Transaction (TRNPARM).
Error Messages
Planning and Installing AppBuilder for the Mainframe
page 183 of 284
Error messages may appear in the prepare job's output, which is RES. All message numbers begin with the two
letter prefix RD followed by a four digit number. If detected by the EXCI client during a prepare, they will be in the
1xxx range and 4xxx range for the CICS EXCI RD server (e.g. RD1001I - Resource definition actions were
[un]successful for program <program> in <CICS EXCI-region>.).
For detailed information on the CICS EXCI RD error messages, refer to the Messages Reference Guide within the
AppBuilder documentation set.
Planning and Installing AppBuilder for the Mainframe
page 184 of 284
Installing IMS Online Preparation Workbench and Enterprise
Server
The information in this section describes the detailed requirements and procedures for installing an IMS Online
Preparation Workbench.
Planning and Installing AppBuilder for the Mainframe
page 185 of 284
Prerequisites of Installing IMS Online Preparation Workbench
and Enterprise Server
The following AppBuilder software is required prior to the installation of this software.
• AppBuilder REL 3.4 Host Installation Workbench
• AppBuilder REL 3.4 Enterprise Repository
Complete the checklists and worksheets provided in Appendix E, “Hardware and Software Checklists” and Appendix
J,“ IMS Online Preparation Workbench and Enterprise Server Customization Worksheets before proceeding with this
installation.
Packing List
You should have received the following software. If you did not receive all the pieces listed below, please contact
AppBuilder Distribution.
• AppBuilder REL 3.4
Planning and Installing AppBuilder for the Mainframe
page 186 of 284
Installation Notes of Installing IMS Online Preparation
Workbench and Enterprise Server
This section contains the following hierarchy of panels for installing the IMS Online product
1 - System functions
Apply System Upgrade
Update System Software
Option 1 Unload Installation Data Sets
Option 2 Continue
Create System Upgrade Jobs
Confirm update job submission
Regenerate/Edit/Submit Installation Jobs
SYSJOB2 - Set Tape Backup Parameters
SYSJOB5 - Confirm Update Job Submission
2 - Repository functions
Apply Repository Upgrade
Apply upgrade to repository
Option 1 Create Installation Table
Upgrade Repository
Option 2 Process Installation Table
Selecting an Installation Table to Process
Apply SVI34 to repository
Option 1, Capture version variables
Capture version variables (4 panels)
Option 2, Capture/submit installation jobs
Regenerate/Edit/Submit Installation jobs
Option 3 Activate Repository
Installing IMS Online Preparation and Enterprise Server
There are two parts to installing the AppBuilder IMS Online product option: “Option 1 - System Functions” and
“Option 2 - Repository Functions”. Use the panel in Figure 9-1 to navigate to both parts through the Host Installation
Workbench--- Workbench Functions.
Figure 9-1
Host Installation Workbench Functions
Planning and Installing AppBuilder for the Mainframe
page 187 of 284
The Workbench Functions panel is the starting point for installing system and repository functions. You must apply
the system functions prior to the repository functions:
Option 1, System Functions - see -“Option 1 - System Functions” . Option 2, Repository Functions - see “Option 2 Repository Functions”.
Before installing option 2, you must complete option 1 and perform four preparation steps described at the beginning
of “Option 2 - Repository Functions”.
Option 1 - System Functions
System functions are those installation processes you start when you choose option 1 System Functions
in Figure 9-1. This option lets you apply the system upgrade for IMS Online.
Apply System Upgrade
1.
When you install the IMS Online product system functions, select 1 System Functions in Figure 9-1.
The System Functions panel opens (Figure 9-2).
Figure 9-2
System Functions Main
Use this panel to perform option 2 Apply System Upgrade.
Planning and Installing AppBuilder for the Mainframe
page 188 of 284
1. Select option 2 on the panel.
2. Enter the ID of the system to be upgraded.
1. Press Enter to advance to the panel selected.
3. Enter X or press End to exit the panel.
4. The next panel opens (Figure 9-3) to begin the installation of the system functions.
Update System Software
Figure 9-3 begins the installation of the system software, starting with unloading the data sets.
Figure 9-3
Update System Software
Updating system software involves the unloading of the installation data sets required for the system installation. In
Option 1, Unload installation Data sets, you enter the data needed to create the unload JCL. In Option 2, Continue,
you activate the actual unloading of the data from tape to your system. Before selecting the options, provide the
following information.
1. Release: [Default: SVI34] Enter SVI34, the release number for this system upgrade.
Option 1 - Unload installation data Sets
Select option 1 Unload installation data sets to display job card information. Review the data and submit it. Check
the output of execution and confirm it contains these three data sets with installation software:
&instqual..&SVI34.CNTL
&instqual..SVI34.ICLIST
&instqual..SVI34.IPANELS
&instqual..SVI34.ISKELS
where &instqual is the installation data set qualifier. Refer to “Installing the Enterprise Repository” in this document
for additional information about AppBuilder data sets.
Option 2 - Continue
Select option 2 in Figure 9-3 to continue the system software installation. Press Enter to continue to the next panel.
Create System Upgrade Jobs
Planning and Installing AppBuilder for the Mainframe
page 189 of 284
Figure 9-5 appears the first time you perform this installation. The panel shown in Figure 9-4 is optional; the first time
you apply a system upgrade, it does not appear, but it does in subsequent passes. Its text says that the installation
tables are already generated; consequently, do not generate them again unless you have introduced some change
requiring another generation pass.
Figure 9-4
Create System Upgrade Jobs
Under normal circumstances, select N (No) and proceed. If you want to begin the installation again with the first job,
select Y (Yes). This action resets the status of the jobs but does not regenerate them. The status is reported in the
Regenerate/Edit/Submit Installation Jobs panel shown in Figure 9-6.
Depending on your response, regeneration either occurs or does not occur. Regenerating the table clears the status
of any jobs that are ‘SUBMITTED’ or ‘COMPLETED’. On successful completion of either choice, you are ready to
update the system software. The panel in Figure 9-4 appears only if you have already applied a system upgrade to
this system.
Confirm Update Job Submission
When the regeneration is completed, Figure 9-5 opens, confirming the update of your job submission.
Figure 9-5
Confirm Update Job Submission
The panel notifies you that no backup has been made. Under normal circumstances, select N (No) and proceed with
the backup procedure. If you have a strong reason for not backing up the installation, press Y (Yes).
Note
You cannot backup the existing system later. It is recommended that you back up your installation.
Planning and Installing AppBuilder for the Mainframe
page 190 of 284
After this selection, the Regenerate/Edit/Submit panel appears.
Regenerate/edit /submit installation jobs
Figure 9-6 provides the controls to regenerate, view, and submit installation jobs. Figure 9-6 shows the panel that
controls the actual unloading, backing up, copying, linking, and restoring of installation data set.
Figure 9-6
Regenerate/Edit/Submit Installation Jobs
Perform the appropriate steps top down. You can unload the tape, back up to tape or DASD, link the load modules,
and copy the results to system data sets, or restore the data sets, if you are not satisfied with the results. Monitor
the unload progress in the Status column and in additional panels that alert you of specific situations.
The following actions are supported:
Regenerate (REGEN)
View (V or VIEW)
Submit (SUB) jobs to update the software
You must perform SYSJOB1, 4, and 5; the other steps are optional. The system jobs are described in the following
section:
SYSJOB1---Unload the rest of the tape
Proceed with the unload process. You can view, regenerate, or submit the job for execution. The data sets listed in
Table 9-1 are unloaded by SYSJOB1.
Table 9-1
Data Sets Unloaded or Created by SYSJOB1
&BASEQUAL.SVI34.HPSDNAER
&BASEQUAL..SVI34.MFSSRCE
&BASEQUAL.SVI34.HPSDNAIN
&BASEQUAL..SVI34.NCALIM
&BASEQUAL.SVI34.HPSDNART
&BASEQUAL.SVI34.OBJ
&BASEQUAL..SVI34.IMSRES
&BASEQUAL.SVI34.PRELINK
&BASEQUAL..SVI34.IMSVSAM
&BASEQUAL..SVI34.PLKOBJ
&BASEQUAL..SVI34.LKIMEC
&BASEQUAL.SVI34.PSBSRCE
Planning and Installing AppBuilder for the Mainframe
page 191 of 284
&BASEQUAL..SVI34.LKIMEN
&BASEQUAL.SVI34.SAMPLE
&BASEQUAL..SVI34.LKIMUC
&BASEQUAL..SVI34.SAMP255
&BASEQUAL..SVI34.LKIRNC
&BASEQUAL..SVI34.SAMP80
&BASEQUAL..SVI34.LOADIM
&BASEQUAL..SVI34.VIDTEXT
&BASEQUAL..SVI34.LOADLIB
&BASEQUAL.SVI34.DBDSRCE
&BASEQUAL.SVI34.DBRMLIB
&BASEQUAL.SVI34.DDL
&BASEQUAL.SVI34.DDLVSAM
&BASEQUAL.SVI34.LKBS00
&BASEQUAL.SVI34.PCKGBASE
&BASEQUAL.SVI34.PCKGRANT
SYSJOB2---Backup data sets to tape
When you regenerate or submit SYSJOB1, and then submit SYSJOB2, the panel in Figure 9-7 opens.
Figure 9-7
Set Tape Backup Parameters
1. Enter the UNIT for the tape being used for the backup.
1. Enter the volume serial number of the tape being used for the backup.
2. Enter the number of days that you want the taped data to be retained.
3. Specify the required tape backup information, and press Enter to activate these parameters. The backup
process executes, and you return to the panel in Figure 9-6.
SYSJOB3---Backup data sets to DASD
Use this job to direct your backup to DASD.
SYSJOB4---Link load modules
When the data sets are unloaded successfully, perform the link of the load modules. Before that can be completed,
you must define additional information in another panel, shown in Figure 9-8.
Figure 9-8
Capture System Variables
Planning and Installing AppBuilder for the Mainframe
page 192 of 284
Execute the jobs in order from the top down. You can view, submit, or regenerate a job from the Action column.
Monitor its progress in the Status column and in additional panels that alert you of specific situations.
This panel is a major control panel for the repository functions update. Its options are:
600.1 IMS RESLIB -[Default: IMS.SDFSRESL]
Enter the qualified name of the IMS resident library used to link AppBuilder modules.
600.2 IMS CSSLIB - [Default: SYS1.CSSLIB]
Enter the qualified name of the CSS library used to link AppBuilder modules to support LU6.2 processing for
AppBuilder’s NetEssential middleware.
When you have specified these variables, press Enter. You return to the panel in Figure 9-6.
SYSJOB5---Copy to system data sets
When the load modules are linked successfully, copy the modules to the system data sets. After this job completes
the data sets in Table 9-2 and Table 9-3 are created or updated.
Table 9-2
System Libraries created or updated by SYSJOB5
&BASEQUAL..ACBLIB
&BASEQUAL..DBDSRCE
&BASEQUAL..DBDLIB
&BASEQUAL..HPSDNAER
&BASEQUAL..DBRMLIB
&BASEQUAL..SAMPLE
&BASEQUAL..HPSDNAIN
BASEQUAL..SAMP80
&BASEQUAL..HPSDNART
BASEQUAL..SAMP255
&BASEQUAL..LKIMEC
&BASEQUAL..LKIMEN
&BASEQUAL..LKIMUC
&BASEQUAL..LKIRNC
&BASEQUAL..LKBS00
&BASEQUAL..LOADLIB
&BASEQUAL..LOADIM
&BASEQUAL..MFSSRCE
&BASEQUAL..NCALIM
&BASEQUAL..PSBLIB
&BASEQUAL..PSBSRCE
&BASEQUAL..IMSVSAM
Planning and Installing AppBuilder for the Mainframe
page 193 of 284
&BASEQUAL..OBJ
&BASEQUAL..PCKGRANT
&BASEQUAL..PCKGBASE
&BASEQUAL..PRELINK
&MODQUAL..ACBLIB
&MODQUAL..DBDLIB
&MODQUAL..DBDSRCE
&MODQUAL..LOADIM
&MODQUAL..MFSSRCE
&MODQUAL..NCALIM
&MODQUAL..PSBLIB
&MODQUAL..PSBSRCE
Note
&BASEQUAL is the System Data Set Qualifier for AppBuilder data sets.
Note
&MODQUAL is the Maintenance Data Set Qualifier for AppBuilder data sets.
SYSJOB6 — Restore data sets from tape
The restore data sets process can be used to recover (or restore) system software data sets from the tape or DASD
backups made in SYSJOB2 or SYSJOB3 in the event that the outcome of the system software upgrade is
unsatisfactory. Of course, the restore process can be used only if SYSJOB2 or SYSJOB3 was run. To restore data
sets from a tape backup, select SYSJOB6. To restore data sets from DASD backups select SYSJOB7. The restore
process does not affect any repository data sets. If the repository installation was also completed, any updated
repository information must be manually restored and any DB2 plans rebound using the restored software level.
AppBuilder Solutions recommends that you use the View or REGEN action on SYSJOB6 or SYSJOB7 at this time
in order to create the job for later use, if necessary.
Note
Before submitting this job, edit the tape number of the backup volume used in SYSJOB2 into the
job as directed by the job stream comments.
SYSJOB7---Restore data sets from DASD See the comment above for SYSJOB6.
Status---[blank]
The following lists indicators are displayed in the Status column:
[blank] — No activity is occurring.
SUBMITTED — A job is in progress.
COMPLETED — A job is completed.
When this panel completes successfully, you have completed the System Functions installation. Return to the
starting panel by typing X and pressing Enter or by pressing F3 repeatedly. You return through the hierarchy of
installation windows to the Workbench Functions panel in Figure 9-1.
Having successfully completed the “Option 1 - System Functions,”you can either:
a. Continue the installation of this software by completing the option 2---Repository functions installation
Planning and Installing AppBuilder for the Mainframe
page 194 of 284
or
b. Install the system portion of other AppBuilder software. Refer to installation instructions of specific software for
more information--- for example, “Installing the Enterprise Repository” in this document. You would then complete the
“Option 2 - Repository Functions” for each piece of software.
Note
If you choose option a, ensure that all software is installed in the proper order.
Option 2 - Repository Functions
Repository functions are those installation processes you start when you choose option 2, Repository Functions in
Figure 9-1. This option lets you apply the repository upgrade for IMS Online.
Note
To prevent user access to the repository during the repository upgrade, use option 2,
“Enable/Disable Repository” to disable the repository before beginning the repository upgrade.
These steps are standard requirements for installing an IMS application. However, it is recommended you use
existing IMS JCL procedures already available at the installation site. See “Preparation Step 3--- Application Control
Block Generation” for important information on target libraries.
Note
You must perform the following four steps after installing the system functions, and before installing
the repository functions.
Preparation Step 1 - DBD Generation
Perform an IMS DBDGEN for each of the AppBuilder database descriptors (DBD) source members in &DBDSRCE.
Use the standard DBDGEN utility supplied in your installation’s library and modify as required. In the supplied DBD
source, you may need to change the DEVICE=xxxx in the DBD statement to suit your local environment.
Preparation Step 2 - Program Specification Block Generation
Perform an IMS PSBGEN for each of the AppBuilder PSB source members in
&BASEQUAL..SVI34.PSBSRCE.
Use the standard PSBGEN utility supplied in your installation’s library and change as required.
Planning and Installing AppBuilder for the Mainframe
page 195 of 284
Preparation Step 3 - Application Control Block Generation
Perform an IMS ACBGEN for each of the online application PSBs in &BASEQUAL..SVI34.PSBSRCE. Use the
standard ACBGEN utility supplied in your installation’s library and modify as required. A sample job to perform the
ACBGENs for all AppBuilder PSBs and databases is provided in
&BASEQUAL..SVI34.SAMPLE member ACBGEN.
The ACBs generated will need to be staged onto the IMS executable libraries. You will need to customize either your
site’s staging routine (with the IMS Systems Programmer) to include &BASEQUAL..ACBLIB, or change the name of
the target library to the name assigned by the IMS Systems Programmer.
Preparation Step 4 --- Database DBRC Definition
Define the AppBuilder databases to the DBRC utility (database recovery) if your site uses this utility.
Edit the DBRC member in &BASEQUAL..SVI34.SAMPLE for the database data set and supply to the IMS Systems
Programmer for inclusion into DBRC.
Apply Repository Upgrade
Selecting Option 2 - Repository Functions, allows you to start installing repository functions, as shown in Figure 9-9.
Figure 9-9
Apply Repository Upgrade
Use the panel above to perform option 4 Apply Repository Upgrades.
1. Select option 4 on the panel.
2. Enter the ID of the repository to be updated.
3. Press Enter to advance to the panel selected.
4. Enter X or press End to exit the panel.
Figure 9-10 begins the installation of the repository functions.
Apply Upgrade to Repository
This panel begins the installation of the repository software, starting with creating installation tables, as shown in
Figure 9-10.
Planning and Installing AppBuilder for the Mainframe
page 196 of 284
Figure 9-10
Apply Upgrade to your Repository
This panel starts upgrading the repository portion of the IMS Online option. Do not start this section until you
complete the system functions described in Apply System Upgrade.
From this panel you identify the repository you want to create, and choose the options to create and process its
installation table, and finally activate the resultant repository. Perform the following options, as described below:
Create Installation Table
Process Installation Table
Activate
Option 1 - Create Installation Table
Initiate the panel in Figure 9-10 with option 1. Begin by naming the repository to upgrade and selecting option 1
Create Installation Table. (You will return to this panel to perform option 2 and 3 later.)
If this is the first time upgrading this repository, you know that option 1 is done when the “TABLE CREATED”
message appears in the top-right corner of Figure 9-10. In this case, perform option 2 and proceed to the panel in
Figure 9-12.
After the initial upgrade of the repository using option 1, you see the panel on Figure 9-11. After you complete that
panel, return to this panel for action. Assuming you are continuing with the upgrade at hand, proceed to the panel in
Figure 9-12 to perform option 2.
Additional information about option 2 and 3 appears in sequence later.
Upgrade Repository
Figure 9-12 will appear the first time you perform this installation. The panel appearing next in Figure 9-11 is optional.
The first time you apply a repository upgrade, this panel does not appear. But it does subsequently. Its text informs
that the installation tables are already generated; consequently, do not generate them again unless you have
introduced some change requiring another generation pass.
Figure 9-11
Upgrade Repository
Planning and Installing AppBuilder for the Mainframe
page 197 of 284
This panel allows you to restart the installation if special circumstances demand it.
Under normal circumstances, select N (No) and proceed. But if you have altered the input data sets or introduced
other changes, press Y (Yes) to abandon this upgrade and start again.
This optional panel allows you to decide if the upgrade you are starting is the correct one. Depending on your
response, this repository upgrade can be continued or terminated so another can be started from the beginning:
If you want to continue the upgrade currently in progress, enter N.
If you want to stop this upgrade, not allowing it to continue, so you can initiate another modified upgrade,
press Y.
On successful completion of either choice, you move to the next panel in Figure 9-12.
Option 2 - Process Installation Table
Figure 9-12 shows the Apply Upgrade to Repository panel, where you now enter option 2 Process Installation
Table.
Figure 9-12
Apply Upgrade to Repository
Select option 2 for the same repository and press Enter. That action provides the following panel.
Selecting an Installation Table to Process
Figure 9-13 shows the next panel from which you start processing the installation table.
Figure 9-13
Process Installation Table
Planning and Installing AppBuilder for the Mainframe
page 198 of 284
This panel contains a table of releases that you are to process. If there are more than one, select each in top-down
order, and assure each executes completely. The following lists indicators displayed in the Status column. Observe
the status of the Actions you initiate.
[blank] — No activity is occurring.
SELECTED — An action is in progress.
COMPLETED — An action is completed.
When you have executed all entries in the release table successfully, press F3. See the next panel.
Apply SVI34 to Repository
The next panel applies the repository upgrade to the repository, as shown in Figure 9-14.
Figure 9-14
Apply SVI34 to Repository
This panel applies the repository upgrade to the repository in two option steps. The panel contains: Select from
among the following options:
Capture Version Variables
Create/Submit Installation Jobs
Option 1 - Capture Version Variables
Option 1 - Capture Version Variables starts a group of panels in which you specify the requisite information. The
panels appear in Figure 9-15 to Figure 9-18. Handle these panels in the order they appear.
Option 2 - Create/Submit Installation Jobs
Option 2 - Create/Submit Installation Jobs is discussed after the six variables panels in Figure 9-19.
Capture Repository Variables
Planning and Installing AppBuilder for the Mainframe
page 199 of 284
This series of four panels captures repository variables needed to apply the repository upgrade to the IMS
environment. The first of these panels is shown in Figure 9-15.
Figure 9-15
Capture Repository Variables---IMS environment (1 of 4)
Enter the runtime data set name suffixes.
600.3 Runtime Dataset Name Suffixes:
Complete the following values.
600.3a Load Library Output - [Default: LOADIM ]
Enter the name of the suffix for the Load Library Output data sets for IMS.
600.3b NCAL Library Output - [Default: NCALIM ]
Enter the name of the suffix for the NCAL Library Output data sets for IMS.
600.3c VSAM View Definition File - [Default: HPI001D1.VIEWDEF]
Enter the name of the suffix for the VSAM View Definition File data sets for IMS.
600.3d VSAM Rule Source Output - [Default: HPI003D1.RULESRC]
Enter the name of the suffix for the VSAM Rule Source Output file for IMS.
600.3e VSAM Rule Relation Output - [Default:HPI004D1.RLRELATN]
Enter the name of the suffix for the VSAM Rule Relation Output file for IMS.
600.4 Specify the Jobname for IMS Control Region - [Default: None]
Enter the jobname for the IMS Control Region at your site.
600.5 Specify the dataset name which contains the IMS VSAM Buffer Cards - [Default:
SS0216.SVI34.SAMPLE(DFSVSM)]
Complete this panel, and proceed to the next.
The second of four panels capturing repository variables is shown in Figure 9-16.
Figure 9-16
Capture Repository Variables---IMS environment (2 of 4)
Planning and Installing AppBuilder for the Mainframe
page 200 of 284
Enter the information required by this panel. These parameters are intended for future use, so enter the defaults.
600.6 You may form IMS DB2 plan names by using the generated bitmap as the plan name prefix or suffix.
Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default: P]
Enter the default value to use the bitmap as a suffix.
600.7 Use AppBuilder Project name in IMS plan name? (Y/N ) - [Default: Y]
Enter the default value to use the AppBuilder project name in the IMS plan name.
600.8 If not, enter the string to use here: - [Default: HP]
Enter the default value only.
600.9 Use the repository version number in plan name? (Y/N ): - [Default: Y]
Enter the default value to use the repository version number in the plan name.
600.10 Use the region type (‘M’) in the plan name? (Y/N ) - [Default: Y]
Enter the default value to use the region type M in the plan name.
600.11 Should a separate plan be generated for Batch Rules (Y/N ) - [Default: N]
If you want to generate a separate plan for Batch Rules, enter Y. If not, enter N.
600.12 Use AB/IMS Autoinstall? (Y/N ) - [Default: None]
If you want to use AB/IMS Autoinstall, enter Y. If not, enter N. This feature is a batch interface that automatically
connects to IMS to open and close AppBuilder databases and to update the AB incore table with the AppBuilder IMS
rule and transaction ID.
Complete this panel and proceed to the next.
The third of four panels capturing repository variables is shown in Figure 9-17.
Figure 9-17
Capture Repository Variables---IMS environment (3 of 4)
Planning and Installing AppBuilder for the Mainframe
page 201 of 284
Enter the information required by this panel.
600.13 IMS General Library Names:
600.13a General IMS Lib Prefix - [Default: IMS.PREF]
Enter the name of your general IMS library prefix.
600.13b VTAM NAME FOR IMS SYSTEM - [Default: IMSCTLR1]
Enter the VTAM region ID for this IMS system.
600.13c IMS Region name - [Default: IMSB]
Enter the IMS system name.
600.13d IMS MACLIB Library - [Default: IMS.SDSFMAC]
Enter the name of your IMS Macro library (MACLIB).
600.13e IMS Res Library - [Default: IMS.SDSFRESL]
Enter the name of your IMS Resident Library (Res Library).
600.13f IMSAGN name - [Default: None]
Enter the AGN (Application Group Name) value if AGNs are used at your site.
600.13g IMS Long Message - [Default: IMS.LGMSG]
Enter any fully qualified data set name used by the IMS Control Region. This library is used to determine
if IMS is up before submitting AppBuilder BMP jobs.
600.14 Maximum Transaction ID for this Version: - [Default: None]
Currently this value is set by a AppBuilder internal program for IMS transactions.
600.15 Number of IMS Regions you want to configure for version 1 - [Default: None]
Please enter the number of regions you want to configure for version 1.
Complete this panel and proceed to the next. The following panel appears once for each requested region to allow
you to configure each region separately.
The last of four panels capturing repository variables is shown in Figure 9-18.
Figure 9-18
Capture Repository Variables---IMS environment (4 of 4)
Planning and Installing AppBuilder for the Mainframe
page 202 of 284
Enter the information required by this panel.
600.16 Enter the VTAM APPLIDs for LU2 processing:
If you specified Y for item 600.12, then you must enter the names of the three VTAM APPLIDs for LU2 processing.
600.16a
1 - [Default: A06HPS1]
Specify the name of the first VTAM APPLID.
600.16b
2 - [Default: A06HPS2]
Specify the name of the second VTAM APPLID.
600.16c
3 - [Default: A06HPS3]
Specify the name of the third VTAM APPLID.
600.17 Define HPS transactions during rule prepare? (Y/N) - [Default: Y]
Enter the default value to define AppBuilder transactions during rule prepare.
600.18 Should the HPS databases be processed?
(Y/N) - [Default: Y]
If you want the AppBuilder databases to be processed (used to populate RuleView), enter Y. If not, enter N.
600.19 Should the HPS transaction UTBL0000 be executed? - [Default: Y]
If you want the AppBuilder transaction UTBL0000 to be executed, enter Y. If not, enter N. Complete this panel and
proceed to the next.
Option 2 - Capture/Submit Installation Jobs
Figure 9-19 shows you returning to the panel you saw previously in Figure 9-14. This time you perform option 2
Create/Submit Installation Jobs.
Figure 9-19
Apply SVI34 to Repository, Option 2 Capture/Submit Installation Jobs
Planning and Installing AppBuilder for the Mainframe
page 203 of 284
This panel applies the repository upgrade to the repository in two optional steps. Select from the following options:
Capture Version Variables
Create/Submit Installation Jobs
Because you have completed option 1, perform option 2.
Option 2 - Create/Submit Installation Jobs shows two jobs that you need to process, as shown in Figure 9-20.
Regenerate/Edit /Submit Installation Jobs
The next panel defines the repository jobs that install updates to your repository, as Figure 9-20 shows.
Figure 9-20
Regenerate/Edit/Submit Installation Jobs
Execute the jobs in order from the top down. You can view, submit, or regenerate a job from the Action column.
Monitor its progress in the Status column and in additional panels that alert you of specific situations.
This panel controls the repository functions update. Its choices are:
The Actions you can make are to regenerate (REGEN), view (V or VIEW), and submit (SUB) jobs to update the
software. The following describes the repository jobs:
REPJOB1 — NON-DB2 PROCESSING
This step processes the non-DB2 jobs, which must be handled first. After this job completes, the following new data
sets are created:
Note
&REPQUAL is the qualifier used for AppBuilder repository level data sets.
Planning and Installing AppBuilder for the Mainframe
page 204 of 284
Table 9-3
Repository Libraries
&REPQUAL..LOADIM
Note
&USRVQUAL is the qualifier used for AppBuilder user level data sets that are versioned. You
have more than one set of the following data sets if you specified more than one version during the
Enterprise Repository installation. The value for &USRVQUAL is contained in
&REPQUAL..INI(@USRENVn) where n is the version number of the repository.
Table 9-4
User Libraries
&USRVQUAL..LOADIM
&USRVQUAL..NCALIM
&USRVQUAL..ACBLIB
&USRVQUAL..DBDLIB
&USRVQUAL..DBDSRCE
&USRVQUAL..PSBLIB
&USRVQUAL..PSBSRCE
Note
&VSUVQUAL is the qualifier used for AppBuilder user VSAM data sets. You have more than one set
of the following data sets if you specified more than one version during the Enterprise Repository
installation. The value for &VSUVQUAL is contained in &REPQUAL..INI(@USRENVn), where n is
the version number of the repository.
Table 9-5
User VSAM data sets
&VSUVQUAL..&VIEWDEFI
&VSUVQUAL..&RULESRCI
&VSUVQUAL..&RLRELATI
&VSUVQUAL..HPI002D1.TESTDATA
&VSUVQUAL..HPI006D1.ERRLOG
&VSUVQUAL..HPSDNADI
&VSUVQUAL..HPI030D1.HPIRULS
&VSUVQUAL..HPI030D1.HPIRULX
&VSUVQUAL..HPI040D1.HPIRCP
&VSUVQUAL..HPI040D1.HPIRCX
&VSUVQUAL..HPI041D1.STGMNGR
Note
&VIEWDEFC, &RULESRCC, and &RLRELATC are the values entered in prompt 600.1, refer to
Figure 9-15.
Planning and Installing AppBuilder for the Mainframe
page 205 of 284
REPJOB2 — DB2 PROCESSING
This step processes the DB2 jobs, which must be handled secondly.
The following lists indicators displayed in the Status column. Observe the status of the Actions you initiate.
[blank] — No activity is occurring.
SUBMITTED — A job is in progress.
COMPLETED — A job is completed.
When you have competed these jobs successfully, press F3 to exit this panel. Return to the Apply Upgrade to
Repository panel, appearing in the next figure.
Activate Repository
After completing the previous panel, you have applied all the repository updates for SVI34. The last panel in this
series activates the repository, as Figure 9-21 shows.
Figure 9-21
Activate Repository
Select option 3 Activate Repository. This option concludes the installation of the IMS Online upgrade to your
repository.
Planning and Installing AppBuilder for the Mainframe
page 206 of 284
Post-installation Notes: Installing IMS Online Preparation
Workbench & Enterprise Server
Perform the following steps to complete and verify the successful installation of the AppBuilder IMS Online
Preparation and IMS Enterprise Server.
1
- AppBuilder Software Format Library
Run an IMS MFS Generation for each MFS format source member in
&BASEQUAL..SVI34.MFSSRCE. Three members must be generated. Two members, HPISEC4 and
HPISEC5, are part of the Message Log screen program. The third member, HPIMFS1, is the AppBuilder Main Driver
format.
AppBuilder provides an optional MFS screen that may be included if desired. HPINFO is AppBuilder utility that
retrieves date and time and obtains the LTERM name.
Use your installation’s existing version of MFSGEN to generate the three members into your site’s correct libraries.
2
- Database Dynamic Allocation Definition
Define the AppBuilder databases to the IMS Dynamic Allocation utility. The AppBuilder databases to be defined are:
HPI001D1--- AppBuilder RuleView Definition database
HPI002D1--- AppBuilder Rule View Test Data database
HPI003D1--- AppBuilder Rule View Rule Source database
HPI004D1--- AppBuilder Rule View Rule Relationship database
HPI006D1--- AppBuilder message log database
HPI030D1/HPI030X1---AppBuilder rule/transaction relationship database (and index)
HPI040D1/HPI040X1---AppBuilder/IMS Run Control database (and index)
HPI041D1--- AppBuilder IMS storage manager database
a. Define databases--- Edit the &BASEQUAL..SVI34.SAMPLE member HPSDYNAM by filling in the appropriate
value for the &VSUVQUAL variable. Make any other customizations needed for your site. Supply the edited
HPSDYNAM to the IMS Systems Programmer.
b. IMS buffers--- In the &BASEQUAL..SVI34.SAMPLE data set, the member DFSVSM contains the buffer cards
required for the AppBuilder/IMS databases.
1. IMS preload---In the &BASEQUAL..SVI34.SAMPLE data set, the member DFSMPL contains the programs to
be preloaded. Insert these programs in the preload member for your site. Change PRLD=, accordingly.
2. For better performance, it is recommended that you preload the following NetEssential modules into the
Message processing region: HPSDI200, HPSDI600, DNAPOSTE, and DNAIEVNT.
Additionally, if you are running any COBOL services, we recommend preloading the following rou​ tines from
SYS1.COB2LIB in order to eliminate the overhead of setting up the COBOL environment:
Table 9-6
NetEssential Routine Modules
IGZCPAC
IGZCPCO
IGZEINI
IGZEPCL
IGZEPSU
IGZETCO
Planning and Installing AppBuilder for the Mainframe
page 207 of 284
IGZEOPD
IGZEOPT
3 - IMS Stage 1 Input
This step is performed manually by the IMS Systems Programmer.
AppBuilder applications, databases, and some special terminals must be defined to IMS. This is done by control
record input in the IMS Stage 1 generation. The following is a description of the supplied input control records for
AppBuilder applications that must be specified in the IMS stage 1 generation.
Terminal Input
DFSCMTR0 Terminal Routing Exit
AppBuilder Transactions
AppBuilder Databases
COMM macro
Terminal Input
Define each physical terminal from which AppBuilder software will be run to IMS. Add the terminal IDs to the stage 1
generation. Refer to your IBM IMS/ESA Installation manual for more information.
All 3270 terminals defined to process AppBuilder PCIO0000 input must have the OPTION macro parameter-TRANRESP --specified. 3270 terminals must also be defined as SNA to keep the terminal session locked until the
reply message is received. This parameter can be coded in the TYPE macro, which defines parameters for all
terminal definitions that follow.
TYPE UNITYPE=SLUTYPE2,MODEL=2,FEAT=IGNORE,
(TRANRESP,PAGDEL,NOPNDST,NOCOPY)
* OPTIONS=
TERMINAL NAME=LE02,FEAT=F4 NAME LE02
TERMINAL NAME=LE03.... etc..
\\\
In addition, three special terminals are typically defined for AppBuilder software’s exclusive use. Each special
terminal contains a VTAM application ID with a location-dependent NAME. The terminal NAME can be found in the
LOGAPPLI1, LOGAPPLI2, and LOGAPPLI3 variables defined in the @ “IMS System Name” member of the
&REPQUAL..INI data set.
The following example is a special LU2 terminal from the TERMINAL member of the
&BASEQUAL..SVI34.SAMPLE data set. Use this member as a basis for each special terminal
definition.
TYPE UNITYPE=SLUTYPE2,MODEL=2,FEAT=IGNORE,
(TRANRESP,PAGDEL,NOPNDST,NOCOPY)
* OPTIONS=
TERMINAL NAME=A05HPS1,FEAT=F4,MSGDEL=NOTERM,OUTBUF=1536, * OPTIONS=(FORCRESP)
NAME A05HPS1
The default terminal names are A05HPS1, A05HPS2, and A05HPS3. The option FORCRESP is required.
Planning and Installing AppBuilder for the Mainframe
page 208 of 284
DFSCMTR0 Terminal Routing Exit
1. The output from this IMS stage 1 needs to be modified. Modification is limited to one area---the final link-edit
step that generates the IMS nucleus.
Note
The USERLIB DD statement needs to specify the DSN of the library where the AppBuilder
version of DFSCMTR0 load module resides.
2. If IMS is a single system setup (not MSC), add ORDER DFSCMTR0 after INCLUDE
SYSPUNCH(DFSCVB0I), then add INCLUDE USERLIB(DFSCMTR0).
Note
See the “HMPBTBLI is used to update the AppBuilder software incore table. Always run
HMPBTBLI when bringing up IMS. The sample JCL is contained in
&BASEQUAL..SVI34.SAMPLE(HMPBTBLI)” for more information on how the terminal user
exit is used in AppBuilder software.
3. The output of the stage 1 IMS generation is submitted to perform the build of the IMS nucleus, the stage 2
IMS generation.
4. The output of the stage 2 linking of DFSCMTR0 which includes HPICMTR0 must reside in the RESLIB.
DFSCMTR0, HPICMTR0, HPITBL1, and HPITBL2 are also linked into &BASEQUAL..SVI34.IMSRES.
Note
HPITBL1 and HPITBL2 can either be copied into RESLIB or may reside in a library accessed
by the control region.
5. A sample terminal routing exit program is contained in &BASEQUAL..SVI34.SAMPLE (DFSCMTR0).
AppBuilder Transactions
See sample member APPLCTN in dataset &BASEQUAL..SVI34.SAMPLE.
AppBuilder Databases
See sample member DATABASE in dataset &BASEQUAL..SVI34.SAMPLE.
COMM macro
The RECANY size parameter must be set to at least 2100. See sample member COMM in dataset
&BASEQUAL..SVI34.SAMPLE.
Stage 1 Requirements for AppBuilder User Applications
Planning and Installing AppBuilder for the Mainframe
page 209 of 284
At this point, you have all necessary IMSGEN input for the AppBuilder IMS run-time environment. However, each
AppBuilder application will need to supply input to IMSGEN. This input is generated by using the AppBuilder IMS
utilities. Therefore, use the AppBuilder IMS utilities to define the IMSGEN input for online conversational, nonconversational, and batch message processing applications.
4 - IMS Security Generation
5 - Changes to Control Region JCL
6 - Set Up HMPBTBLI
HMPBTBLI is used to update the AppBuilder software incore table. Always run HMPBTBLI when bringing up
IMS. The sample JCL is contained in &BASEQUAL..SVI34.SAMPLE(HMPBTBLI).
7 - HPICGAP and HPEUCGP
8 - Modify NetEssential Middleware for IMS
9 - Cold Start IMS
10 - Completing the Installation
4 - IMS Security Generation
Define two AppBuilder software BMPs with special authorities to the IMS security generation. A sample is provided
in member SECURITY in &BASEQUAL..SVI34.SAMPLE. The first BMP is the Automated Operator command
application. This program performs the IMS /STA and /DBR database operator commands for the HPI001D1 Rule
View Definition database. The second BMP is the HPS Run Control (HPIRCP1), which performs the stopping and
starting of IMS regions and batch jobs, based on the application’s use of USE RULE INIT.
Use the standard IMS security utility, SECURITY, located in the IMS PROCLIB or your installation’s modified
version.
5 - Changes to Control Region JCL
Add the following AppBuilder load libraries to the IMS region STEPLIB concatenation for those regions that will be
executing AppBuilder software transactions:
&USRVQUAL..LOADIM
&USRVQUAL..LOADBS
&REPQUAL..LOADIM
&MODQUAL..LOADIM
&BASEQUAL..LOADIM
If Global Eventing will be used, you must define the following VSAM file as shown:
DEFINE CLUSTER (NAME(&VSMQUAL..HPSDNADV) – TRACKS (1,1) –
VOLUMES (?) or MANAGEMENTCLASS (?) – SHAREOPTIONS (2,3) –
LINEAR)
where &VSMQUAL is the prefix for base VSAM data sets. The value for this is contained in
&REPQUAL..INI(@HPSENV).
To support LU6.2 and AppBuilder NetEssential middleware, the following files must be added to the Message
Processing Region JCL:
Planning and Installing AppBuilder for the Mainframe
page 210 of 284
//DIVDD DD DSN=&VSMQUAL..HPSDNADV
//DNAERR DD DSN=&BASEQUAL..HPSDNAER
//DNAINI DD DSN=&BASEQUAL..HPSDNAIN
//DNARTBL DD DSN=&BASEQUAL..HPSDNART
6 - Set Up HMPBTBLI
HMPBTBLI is used to update the AppBuilder software incore table. Always run HMPBTBLI when bringing up IMS.
The sample JCL is contained in &BASEQUAL..SVI34.SAMPLE(HMPBTBLI).
Use of HMPBTBLI
DFSCMTR0 uses the rule/transaction relationship incore tables to associate an AppBuilder rule with its assigned
IMS transaction code. Table 1 is built by a program (HMPBTBLI) reading the E_RULE DB2 table and creating a row
for each AppBuilder rule and IMS transaction code relationship. Table 2 has the same format as Table 1 and
contains entries for the rules that have been prepared since Table 1 was created.
When an AppBuilder IMS rule is prepared, a UTBL0000 IMS transaction along with the associated rule name and
IMS transaction code is put on the IMS queue for the routing exit to process. The exit scans both Tables 1 and 2 for
the existence of that relationship. If the relationship is new it is added to Table 2. When a relationship exists but the
transaction code has changed, the entry in either Table 1 or 2 will be updated.
When IMS is cold started Table 2 is empty and can have 100 new entries added to it. If the table becomes full an
error message is returned to the terminal that issued the UTBL0000 transaction. Because of this, you must be able
to run the HMPBTBLI table build program during the IMS startup procedure’s management system and while IMS is
up.
7 - HPICGAP and HPEUCGP
Review the AppBuilder IMS Global Parameters Table (HPICGAP) delivered in the &BASEQUAL..SVI34.SAMPLE
data set. This source should be modified and reassembled to satisfy site requirements. Also included in the
&BASEQUAL..SVI34.SAMPLE data set is JCL to assemble HPICGAP. The member is HPICGAPJ. Then rerun the
COPY1, COPY2, and COPY3 steps in the DSALLOC member found in the &INSTQUAL.AB34.CNTL data set. This
will place the correct version of the translate objects in the &BASEQUAL.OBJ data set. (This problem will be
corrected in the next release so the translate objects will be delivered in the runtime products.) Link the programs
into your AppBuilder IMS load library using the link function accessed from the Host Installation WorkbenchSystems Functions menu. Refer to Appendix D, “HPSCGAP, HPICGAP, HPEUCGP, and Sample Batch JCL" for
more information about HPICGAP and HPEUCGP. Repeat this exercise for the
&BASEQUAL..SVI34.SAMPLE(HPEUCGP) member using the HPICGP JCL member to assemble the HPIGAPA
load module
Planning and Installing AppBuilder for the Mainframe
page 211 of 284
8 - Modify NetEssential Middlew are for IMS
The following must be completed to provide NetEssential support for IMS:
1. For Global Events routing, setup the following:
.SMA section of NetEssential initialization file, &BASEQUAL..HPSDNAIN.
Note
The MPR has to be taken down each time you want to update the files in steps 1 and 2 above.
2. Make sure Mainframe/APPC and IMS/APPC have been set up.
3. Make sure that the VTAM definitions have been defined to support LU6.2. For sample definitions refer to the
members MODELU6.2 and AppBuilderMN in &BASEQUAL..SVI34.SAMPLE.
Note
If samples have not been provided, contact AppBuilder’s ActionLine.
4. Refer to the sample TP profile SDFMU in &BASEQUAL..SVI34.SAMPLE to set up your TP profile. Ensure
that the transcode value is HPSDI600.
5. Set up the PC Communications Manager LU6.2 session. You will need to provide the following:
NCP domain name
Partner LU for IMS (This can be obtained by the side information file in mainframe/APPC.)
TP name specified in the TP profile.
LOCAL LU as defined in step 4 above.
9 - Cold Start IMS
The IMS system must be cold started before completing the installation.
10 - Completing the Installation
Complete the following on the host (mainframe) before Host IMS Development Workbench software can run.
1. Copy LOADs, ACBs, MATRIX, MFSs, and MODBLKS to staging libraries and then onto the active libraries.
2. Define AppBuilder software regions and make them part of the standard IMS start-up.
3. Define the classes of the AppBuilder software transactions (both AppBuilder system and AppBuilder
applications) and create regions accordingly.
4. If required, define AGNs (via DFSISMP0) to authorize specific users to use AppBuilder software transactions.
Installation Verification Using TIP
The Test Installation Process (TIP) application should already be migrated into the Enterprise Repository. If not,
refer the postinstallation instructions for the migration procedure in "Installing Enterprise Repository".
1. Edit the IMS region INI member in &REPQUAL..INI and change the value for the IMSLNK variable from
NORENT to RENT.
2. Within the Enterprise Repository, go into the ADM project. Type PROJECTS at the command line, list entities
(LE), and select ADM for version 1.
Planning and Installing AppBuilder for the Mainframe
page 212 of 284
3. Within the ADM project, type IMS against the TIP project for version 1. This will select the IMS Utilities
option.
4. Select Option 1 to create the DM_TRAN record for the TIP version 1 project.
5. Select Option 4 to create the necessary stub programs required at runtime. Use a suitable range--- for
example, “AA” through to “AI” and submit the presented JCL.
6. Execute the following options:
Option 2 (Stage 1 input), Option 3 (PSBGEN), and Option 5 (ACBGEN).
7. Within the Enterprise Repository, make sure you are in the TIP project. If not, type PROJECTS at the
command line, list entities (LE), and then select TIP for version 1.
Superprepare the TIP IMS Process
1. Next to the Rebuild Package entity, type ADDE (Add Entity) to add a Rebuild Package for TIP. Name the
package whatever you like. Press F3 to save and return.
2. Next to the Rebuild Package entity, type LE to list the Rebuild Package entities. Next to the one you have
just created, type ADDR (Add Relationship) to add the TIP IMS process to the Rebuild Package for TIP.
Select Option 6 “Has Root Process” in the popup window and press ENTER. Enter
TIP_IMS_COOP_PROCESS as the “Has Root Process” name. Press F3 to save and end.
3. Next to the Rebuild Package for TIP, type SUPERPR. A message states that the job was submitted. Several
jobs will be submitted at various times.
4. After the last job finishes, check the results by typing LISTRBD next to the Rebuild Package for TIP.
Information will be displayed stating whether SUPERPR was successful or not. Press F3 to save and return.
TIP Verification
1. Logon to the IMS test system.
2. Type HPR0 (and a space) to display a list of rules for TIP. Select by entering a slash (/) next to each rule you
want to test. Select break points if you want, and press F15 or SHFT+F3 to continue. A message will display
for each rule stating whether it is successful or not.
3. Test the following rules:
1. TIP_IMS_ASM_RULE
2. TIP_IMS_ASMDB2_RULE
3. TIP_IMS_COB_RULE
4. TIP_IMS_COBDB2_RULE
5. TIP_IMS_PLI_RULE *
6. TIP_IMS_PLIDB2_RULE *
7. TIP_IMS_DB2_RULE
8. TIP_IMS_RULE
Note
The items marked with an asterisk (*) are only required if you are going to be using PL/I
components.
4. TIP should already be downloaded and prepared on the workstation. If not, refer to the Installation Verification
instructions in “Installing the Enterprise Repository” for the download and prepare procedures.
5. Refer to the AppBuilder Workstation Development Workbench Installation Instructions for the instructions for
proper configuration and communications protocol for host logon for both LU2 and LU6.2.
Planning and Installing AppBuilder for the Mainframe
page 213 of 284
6. Execute the TIP application by selecting the AppBuilder Execution Workbench on the workstation. A menu
appears with the TIP Function pulldown. Select the TIP Function pulldown menu, and then select the TIP IMS
Coop Process. Click the mainframe pushbuttons to verify the cooperative processing.
Warning
Do not click the PL/I buttons if PL/I components are not used.
7. Verification of the AppBuilder IMS Online Preparation and IMS Enterprise Server (SVI34) installation is now
complete.
IMS 3270 Converse Verification
Perform the following steps to complete and verify the successful installation of AppBuilder REL 3.4 IMS Online
Preparation.
1. The Default Repository and Test Installation Procedure (TIP) application should already be migrated into the
Enterprise Repository. If not, refer to the postinstallation instructions in “Installing the Enterprise Repository”
for the migration procedure.
2. Within the Enterprise Repository, make sure you are in the TIP Project. If not, type PROJECTS at the
command line. Select TIP for version 1. The following steps will need to be done for each version in the
Repository you wish to verify.
3. Ensure that the TIP_IMS_PROCESS has been prepared. Refer to the section IMS 3270 Converse Verification
Using TIP for more information.
4. Create an IMS 3270 Driver Rule by typing SA against the TIP_IMS_DRIVER_RULE rule (the execution
environment of IMS) and copy all of the relationships.
5. Create a new IMS rule by typing SA against the TIP_PC_RULE; copy the relationships but replace the
relationship to the TIP_IMS_DRIVER_RULE with a new relationship to the rule created in the previous step.
6. Download the TIP_IMS_PROCESS to a AppBuilder AD repository.
7. Create IMS 3270 clones for the TIP_IMS_DRIVER_WINDOW and TIP_PC_WINDOW windows. Refer to the
Design and Construction Tools manual for instructions if required.
8. Upload the windows and Prepare (PR action) them using the Enterprise Repository. Refer to the Managing
Enterprise Repositories manual if further instructions are required.
9. Prepare the two new IMS rules created in the previous step using the Enterprise Repository.
10. The new IMS 3270 IMS Driver rule will attract an IMS Transaction code and PSB. Ensure that these have
been defined and prepared to IMS. Refer to Chapter 10, “Installing IMS Online Preparation Workbench and
enterprise server" (http://) for further instructions.
IMS 3270 Converse Verification Using TIP
1. Log on to the AppBuilder 3270 IMS region.
2. Type the following to verify the text content of the IMS windows: HPC7 WTPIDVR (and two spaces)
3. To execute the IMS 3270 TIP application, type in the assigned transaction code and a space. The IMS
transaction code can be determined by typing ME against the rule in the Enterprise Repository; the value is
shown against the CICS/IMS Transaction ID.
4. Execute each of the PF (function) keys display on the window or screen.
Note
Do not use the PF keys assigned to the PL/I rules if you do not wish to use PL/I components.
5. Verification of IMS Online Preparation (SVI34) is now complete.
Planning and Installing AppBuilder for the Mainframe
page 214 of 284
Appendix A. AppBuilder variables
For information on AppBuilder variables, refer to the INI Settings Reference Guide.
Planning and Installing AppBuilder for the Mainframe
page 215 of 284
Appendix B. CICS table definitions
This appendix contains the updated CICS table definitions for AppBuilder Host Development Workbench.
Table Definitions
DFHDCT
*
*
* AB/CICS PROGRAMS USE THIS DESTINATION TO LOG ERROR MESSAGES.
* WHEN AN ERROR MESSAGE IS WRITTEN TO THIS TRANSIENT DATA QUEUE
* THE HPEL TRANSACTION IS INITIATED. THE HPEL TRANSACTION WILL
* INVOKE THE HPSERRLG PROGRAM WHICH WILL COPY THE ERROR MESSAGE
* FROM THE TRANSIENT DATA QUEUE TO THE HPS006D1 RRDS VSAM FILE.
*
* THE HS04 TRANSACTION CAN BE USED TO BROWSE THE ERROR MESSAGES
* CONTAINED ON THE HPS006D1 ERRLOG FILE.
*
HPEL
DFHDCT TYPE=INTRA,DESID=HPEL,REUSE=YES,DESTRCV=NO, X
DESTFAC=FILE,TRIGLEV=1,TRANSID=HPEL
*
* AB/CICS TERMINAL PRINT DCT ENTRY
*
* AB/CICS APPLICATIONS SPECIFY THIS DESTINATION IN THE APPLICATION
* RULE AS THE TARGET OF THE REPORT OUTPUT. EACH TRANSIENT DATA QUEUE
* IS ASSOCIATED WITH AN SNA SCS PRINTER, WHERE THE NAME OF THE
* CICS TERMINAL NAME OF THE PRINTER IS THE SAME NAME AS THE TRANSIENT
* DATA QUEUE. THE HPRT TRANSACTION THAT IS TRIGGER BY DATA IN THE
* TRANSIENT DATA QUEUE WILL READ RECORDS FROM THE QUEUE AND FORMAT
* THE DATA TO BE SENT TO THE SNA SCS PRINTER.
*
* IN THE FOLLOWING EXAMPLE, THE TRANSIENT DATA QUEUE NAME AND THE
* SNA SCS PRINTER TERMINAL NAME IS "S57P". A TRANSIENT DATA QUEUE
* AND SNA SCS PRINTER MUST BE DEFINED TO CICS FOR EVERY ELIGIBLE
* PRINTER THAT WILL RECEIVE THE AB GENERATED REPORTS.
*
* A SAMPLE CICS TERMINAL DEFINITION FOR THE S57P SNA SCS PRINTER
* IS INCLUDED IN THIS SAMPLE DATASET AND IN THE INSTALLATION
* DOCUMENTATION.
*
S57P DFHDCT TYPE=INTRA,DETID=S57P,REUSE=YES,DESTRCV=LG X
DESTFAC=TERMINAL,TRIGLEV=1,TRANSID=HPRT
DFHFCT
**********************************************************************
*
AB 3.4 FILES (FCT) FOR MVS CICS
*
**********************************************************************
DEFINE FILE(HPSDNAER) GROUP(DNA2032P)
DSNAME(&VSMQUAL..HPSDNAER.CAT)
TABLE(NO ) STRINGS(020)
Planning and Installing AppBuilder for the Mainframe
page 216 of 284
TABLE(NO ) STRINGS(020)
BROWSE(YES) READ(YES)
RECOVERY(BACKOUTONLY)
DEFINE FILE(HPSDNAIN) GROUP(DNA2032P)
DSNAME(&VSUVQUAL..HPSDNAIN.INI)
TABLE(NO ) STRINGS(020)
BROWSE(YES) READ(YES) ADD(YES) DELETE(YES) UPDATE(YES)
RECOVERY(BACKOUTONLY)
DEFINE FILE(HPSDNART) GROUP(DNA2032P)
DSNAME(&VSUVQUAL..HPSDNART.RTABLE)
TABLE(NO ) STRINGS(020)
BROWSE(YES) READ(YES) ADD(YES) DELETE(YES) UPDATE(YES)
RECOVERY(BACKOUTONLY)
DEFINE FILE(DNAFXFER) GROUP(DNA2032P)
DSNAME(&VSUVQUAL..DNAFXFER)
TABLE(NO ) STRINGS(020)
BROWSE(YES) READ(YES) ADD(YES) DELETE(YES) UPDATE(YES)
RECOVERY(BACKOUTONLY)
DEFINE FILE(HPSBC1D1) GROUP(AB2032F)
DESCRIPTION(HPS BROADCAST DATA FILE)
DSNAME(&VSUVQUAL..HPSBC1D1.BDCTDATA) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP)
DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO)
RECORDFORMAT(V) ADD(YES) BROWSE(YES) DELETE(YES) READ(YES)
UPDATE(YES) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO)
JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE)
FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DEFINE FILE(HPSBC2D1) GROUP(AB2032F)
DESCRIPTION(HPS BROADCAST ID FILE)
DSNAME(&VSUVQUAL..HPSBC2D1.BDCTTBL) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP)
DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO)
RECORDFORMAT(F) ADD(YES) BROWSE(YES) DELETE(YES) READ(YES)
UPDATE(YES) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO)
JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE)
FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DEFINE FILE(&FCTVIEW) GROUP(AB2032F)
DESCRIPTION(HPS VIEW DEFINITION FILE)
DSNAME(&VSUVQUAL..&VIEWDEFC.) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(10) STATUS(ENABLED)
OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(11)
INDEXBUFFERS(10) TABLE(NO) RECORDFORMAT(V) ADD(NO) BROWSE(YES)
DELETE(NO) READ(YES) UPDATE(NO) JOURNAL(NO) JNLREAD(NONE)
JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES)
RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DEFINE FILE(HPS002D1) GROUP(AB2032F)
DESCRIPTION(HPS TEST DATA FILE)
DSNAME(&VSUVQUAL..HPS002D1.TESTDATA) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP)
DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO)
RECORDFORMAT(V) ADD(YES) BROWSE(YES) DELETE(YES) READ(YES)
UPDATE(YES) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO)
JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE)
FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DEFINE FILE(&FCTRULES) GROUP(AB2032F)
DESCRIPTION(HPS RULE SOURCE FILE)
DSNAME(&VSUVQUAL..&RULESRCC.) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP)
Planning and Installing AppBuilder for the Mainframe
page 217 of 284
DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP)
DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO)
RECORDFORMAT(F) ADD(NO) BROWSE(YES) DELETE(NO) READ(YES)
UPDATE(NO) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO)
JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE)
FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DEFINE FILE(&FCTRLRLN) GROUP(AB2032F)
DESCRIPTION(HPS RULE RELATIONSHIP FILE)
DSNAME(&VSUVQUAL..&RLRELATC.) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(6) STATUS(ENABLED) OPENTIME(STARTUP)
DISPOSITION(SHARE) DATABUFFERS(7) INDEXBUFFERS(6) TABLE(NO)
RECORDFORMAT(F) ADD(NO) BROWSE(YES) DELETE(NO) READ(YES)
UPDATE(NO) JOURNAL(NO) JNLREAD(NONE) JNLSYNCREAD(NO)
JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES) RECOVERY(NONE)
FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DEFINE FILE(HPS006D1) GROUP(AB2032F)
DESCRIPTION(HPS ERROR LOG FILE)
DSNAME(&VSUVQUAL..HPS006D1.ERRLOG) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(4) STATUS(ENABLED)
OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(5)
INDEXBUFFERS(4) TABLE(NO) RECORDFORMAT(F) ADD(YES) BROWSE(YES)
DELETE(YES) READ(YES) UPDATE(YES) JOURNAL(NO) JNLREAD(NONE)
JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES)
RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DEFINE FILE(&FCTVIDTX) GROUP(AB2032F)
DESCRIPTION(HPS VIDTEXT FILE)
DSNAME(&VSUVQUAL..&VIDTEXTC.) LSRPOOLID(4)
DSNSHARING(ALLREQS) STRINGS(10) STATUS(ENABLED)
OPENTIME(STARTUP) DISPOSITION(SHARE) DATABUFFERS(11)
INDEXBUFFERS(10) TABLE(NO) RECORDFORMAT(V) ADD(NO) BROWSE(YES)
DELETE(NO) READ(YES) UPDATE(NO) JOURNAL(NO) JNLREAD(NONE)
JNLSYNCREAD(NO) JNLUPDATE(NO) JNLADD(NONE) JNLSYNCWRITE(YES)
RECOVERY(NONE) FWDRECOVLOG(NO) BACKUPTYPE(STATIC)
DFHPLT
*
*
*
*
*
*
*
REQUIRED CICS PROGRAM LIST POST INITIALIZATION TABLE
ENTRY FOR AB/CICS.
FOR CICS 3.X, THIS ENTRY SHOULD BE DEFINED IN THE
THIRD STAGE OF INITIALIZATION.
DFHPLT TYPE=ENTRY,PROGRAM=HPSSTART INITIALIZE XZCAT EXIT
DFHPLT TYPE=ENTRY,PROGRAM=HPESI19 INITIALIZE HPS KERNAL
DFHPLT TYPE=ENTRY,PROGRAM=HPSINIRD INITIALIZE DNA KERNAL
DFHTCT
TITLE 'AB/CICS TERMINAL CONTROL TABLE ENTRIES'
*
*
*
SAMPLE CICS TERMINAL CONTROL TABLE ENTRY FOR APPBUILDER/CICS
Planning and Installing AppBuilder for the Mainframe
page 218 of 284
*
TCTHP DFHTCT TYPE=INITIAL,SUFFIX=HP, X
ACCMETH=(NONVTAM,VTAM)
DFHTCT TYPE=GROUP,GROUP=HSAMPTCT
*
* REQUIRED TCT ENTRIES FOR THE HPSLU2B PROGRAM
*
DFHTCT TYPE=TERMINAL,TRMIDNT=HPS1,CHNASSY=YES, X
ERRATT=(LASTLINE),NETNAME=&LOGAPPL1,TRMTYPE=LUTYPE2, X
BRACKET=YES,GMMSG=NO,PGESIZE=(24,80),DEFSCRN=(24,80), X
ACCMETH=VTAM,TIOAL=(4048,4048),TRMMODL=2,
X
FEATURE=UCTRAN, X
RELREQ=(NO,YES),BUFFER=1536,RUSIZE=256,
X
TRMSTAT=TRANSCEIVE
DFHTCT TYPE=TERMINAL,TRMIDNT=HPS2,CHNASSY=YES,
X
ERRATT=(LASTLINE),NETNAME=&LOGAPPL2,TRMTYPE=LUTYPE2, X
BRACKET=YES,GMMSG=NO,PGESIZE=(24,80),DEFSCRN=(24,80), X
ACCMETH=VTAM,TIOAL=(4048,4048),TRMMODL=2,
X
FEATURE=UCTRAN,
X
RELREQ=(NO,YES),BUFFER=1536,RUSIZE=256,
X
TRMSTAT=TRANSCEIVE
DFHTCT TYPE=TERMINAL,TRMIDNT=HPS3,CHNASSY=YES,
X
ERRATT=(LASTLINE),NETNAME=&LOGAPPL3,TRMTYPE=LUTYPE2, X
BRACKET=YES,GMMSG=NO,PGESIZE=(24,80),DEFSCRN=(24,80), X
ACCMETH=VTAM,TIOAL=(4048,4048),TRMMODL=2,
X
FEATURE=UCTRAN,
X
RELREQ=(NO,YES),BUFFER=1536,RUSIZE=256,
X
TRMSTAT=TRANSCEIVE
*
*
SAMPLE TCT ENTRY PARAMETERS FOR AN LU2 TERMINAL
*
DFHTCT TYPE=TERMINAL,TRMIDNT=SERC,NETNAME=SEERC,
X
ERRATT=(LASTLINE),CHNASSY=YES,TRMTYPE=LUTYPE2,
X
ACCMETH=VTAM,TIOAL=(200,8192),TRMMODL=2,
X
FEATURE=(AUDALARM,COLOR,EXTDS,HILIGHT,UCTRAN),
X
RELREQ=(NO,YES),GMMSG=YES,BUFFER=1536,RUSIZE=256,
X
TRMSTAT=(TRANSCEIVE,NOINTLOG)
*
* SAMPLE TCT ENTRY PARAMETERS FOR AN LU6.2 TERMINAL
*
* NOTE: PLEASE REFER TO YOUR VTAM PROGRAMMER FOR ACTUAL NETNAMES
* AND MODENAME
*
DFHTCT TYPE=SYSTEM,
X00410000
TRMTYPE=LUTYPE62,
X00420000
ACCMETH=VTAM,
X00430000
FEATURE=SINGLE,
X00430000
MODENAM=SEERLU62,
X00430000
SYSIDNT=SEER,
X00440000
NETNAME=SEERB,
X00440000
BUFFER=256,
X00440000
RUSIZE=256,
X00440000
USERSEC=LOCAL,
X00440000
OPERSEC=1,
X00440000
TRMSTAT=TRANSCEIVE
00450000
*
* SAMPLE TCT ENTRY PARAMETERS FOR AN LU1 SNA SCS PRINTER
*
DFHTCT TYPE=TERMINAL,TRMIDNT=SERF,NETNAME=SEERF, X
TRMTYPE=SCSPRT,BUFFER=256, X
ACCMETH=VTAM,TIOAL=(1,4000), X
TRMSTAT=(TRANSCEIVE)
*
ENDOFTCT DFHTCT TYPE=FINAL
*
END
Planning and Installing AppBuilder for the Mainframe
page 219 of 284
END
DNA531P
Planning and Installing AppBuilder for the Mainframe
page 220 of 284
DEFINE PROGRAM(DNACEVNT) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL GLOBAL EVENTING MODULE)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(DNAGVERS) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL GET VERSION SYSTEM SERVICE)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(DNAPOSTE) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL GLOBAL EVENTING STUB MODULE)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(DNASASRV) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL SUBCELL TABLE UPDATE SYSTEM SERVICE)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSDNA00) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL SERVER MODULE)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSINIRD) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL INITIALIZATION MODULE)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSSTIRD) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL INITIALIZATION DATA MODULE)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE TRANSACTION(DEVT) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL GLOBAL EVENT SUPPORT)
PROGRAM(DNACEVNT) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) XTRANID(8485A5A3) DTIMOUT(NO) INDOUBT(BACKOUT)
RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES)
RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(NE2I) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL INITIALIZATION)
PROGRAM(HPSINIRD) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) XTRANID(9585F289) DTIMOUT(NO) INDOUBT(BACKOUT)
RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES)
RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(NE20) GROUP(DNA531P)
DESCRIPTION(NETESSENTIAL SERVER)
PROGRAM(HPSDNA00) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) XTRANID(9585F2F0) DTIMOUT(NO) INDOUBT(BACKOUT)
RESTART(NO) SPURGE(NO) TPURGE(NO) DUMP(YES) TRACE(YES)
RESSEC(NO) CMDSEC(NO)
DSNCRCT
Planning and Installing AppBuilder for the Mainframe
page 221 of 284
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
CICS / DB2 RESOURCE CONTROL TABLE ENTRIES FOR HPS/CICS
&REGCHAR = CICS DB2 APPLICATION PLAN PREFIX
FROM CLIENT WORKSHEETS
THE FOLLOWING SAMPLE TYPE=ENTRY DEFINITIONS ARE FOR AN INITIAL
SET OF 36 TRANSACTIONS AND PLANS USED BY AB/CICS APPLICATIONS.
THE ACTUAL PLAN NAMES ARE DETERMINED BY THE VALUES OF PLNDFLT,
PLNVRSN, PLNTYPE AND PLNPREF IN THE INI MEMBER FOR THIS REGION
IN &REPQUAL..INI . THE ACTUAL TRANSACTION NAMES ARE DETERMINED
BY THE TRANSACTION RANGE DEFINED FOR THIS REGION IN THE TABLE
CM_TRAN. THE EXAMPLES HERE REFLECT THE DEFAULT VALUES PROVIDED
WITH RELEASE SVC34. YOU MAY CHOOSE TO DEFINE ENTRIES FOR EACH
TRANSACTION, OR USE THE POOL EXIT LOGIC PROVIDED IN THE MEMBER
&INSTQUAL..SVC34.SAMPLE(HPSPLAN). YOU MAY ALSO COMBINE THE TWO
METHODS.
FOR A DEVELOPMENT ENVIRONMENT WHERE DEDICATED ENTRIES ARE NOT
REQUIRED FOR PERFORMANCE REASONS THE TYPE=POOL AND THE SUPPLIED
PLAN EXIT PROGRAM SHOULD BE USED TO MINIMIZE THE MAINTENANCE
EFFORT.
FOR A PRODUCTION ENVIRONMENT, DEDICATED ENTRIES SHOULD BE USED
WHEN CERTAIN PERFORMANCE CRITERIA MUST BE MET BY THE APPLICATION.
DSNCRCT TYPE=POOL, POOL THREAD DEFINITION X
THRDM=20, MAXIMUM NUMBER OF THREADS X
THRDA=20, INITIAL NUMBER OF THREADS X
AUTH=(TXID), AUTHORIZATIONS X
PLNEXIT=YES, USE PLAN EXIT FOR POOL THREADS X
PLNPGME=HPSPLAN PLAN EXIT NAME FOR POOL THREADS
*
DSNCRCT TYPE=ENTRY,TXID=AAAA,PLAN=AAAAPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAB,PLAN=AAABPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAC,PLAN=AAACPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAD,PLAN=AAADPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAE,PLAN=AAAEPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAF,PLAN=AAAFPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAG,PLAN=AAAGPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAH,PLAN=AAAHPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAI,PLAN=AAAIPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAJ,PLAN=AAAJPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAK,PLAN=AAAKPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAL,PLAN=AAALPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAM,PLAN=AAAMPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAN,PLAN=AAANPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAO,PLAN=AAAOPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAP,PLAN=AAAPPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
Planning and Installing AppBuilder for the Mainframe
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
page 222 of 284
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAQ,PLAN=AAAQPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAR,PLAN=AAARPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAS,PLAN=AAASPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAT,PLAN=AAATPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAU,PLAN=AAAUPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAV,PLAN=AAAVPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAW,PLAN=AAAWPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAX,PLAN=AAAXPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAY,PLAN=AAAYPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAAZ,PLAN=AAAZPLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA0,PLAN=AAA0PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA1,PLAN=AAA1PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA2,PLAN=AAA2PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA3,PLAN=AAA3PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA4,PLAN=AAA4PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA5,PLAN=AAA5PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA6,PLAN=AAA6PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA7,PLAN=AAA7PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA8,PLAN=AAA8PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
DSNCRCT TYPE=ENTRY,TXID=AAA9,PLAN=AAA9PLNC,
THRDM=3,THRDA=0,TWAIT=POOL
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
HMPBTBL
//******* SKELETON NAME ====>> HMPBTBL <<==== SKELETON NAME *******
//*********************************************************************
//*
*
//*
THIS JOBSTREAM MUST BE EXECUTED BEFORE THE STARTUP OF THE
*
//*
AB/CICS SYSTEM. THE PURPOSE OF THIS JOBSTREAM IS TO:
*
//*
*
//*
1) BUILD THE AB/CICS RULE - TRANSID INCORE TABLE1
*
//*
*
//*********************************************************************
//*
//* ACCESS THE AB DATA DICTIONARY TO DEFINE THE RULE - TRANSID
//* RELATIONSHIPS
//*
//HMPBTBL EXEC PGM=IKJEFT01,DYNAMNBR=20
//STEPLIB DD DSN=&DB2LOAD.,DISP=SHR
//
DD DSN=&REPQUAL..LOADLIB,DISP=SHR
//
DD DSN=&MODQUAL..LOADLIB,DISP=SHR
//
DD DSN=&BASEQUAL..LOADLIB,DISP=SHR
Planning and Installing AppBuilder for the Mainframe
page 223 of 284
//
DD DSN=&BASEQUAL..LOADLIB,DISP=SHR
//
DD DSN=&SCEERUN.,DISP=SHR
//SRCEFLE DD DSN=&&&&TBL1SRC,DISP=(NEW,PASS),
//
DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120),
//
SPACE=(CYL,(1,1)),
)SEL &VVOLREQ = Y
//
VOL=SER=&VVOL,
)ENDSEL
//
UNIT=&VUNIT
//SYSTSPRT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//HMFMSG
DD SYSOUT=*
//HMFVMSG DD DSN=&VSMQUAL..MESSAGES,DISP=SHR
//VIDTEXT
DD DSN=&VSUVQUAL..HPS021D1.VIDTEXT,DISP=SHR
//SORTWK01 DD SPACE=(TRK,(50),,CONTIG),UNIT=&VUNIT
//SORTWK02 DD SPACE=(TRK,(50),,CONTIG),UNIT=&VUNIT
//SORTWK03 DD SPACE=(TRK,(50),,CONTIG),UNIT=&VUNIT
//SORTOUT
DD DUMMY
//SYSOUT
DD SYSOUT=*
//SYSTSIN DD *
DSN SYSTEM(&DB2SUBID.)
RUN PROGRAM(HMPBTBL) PARMS('&V.CICS') PLAN(&PLAN1)
END
/*
//*
//* ASSEMBLE AND LINK HPSTBLE1
//*
//ASM
EXEC PGM=&HASMPGM.,PARM='DECK,NOOBJECT',
//
REGION=4096K,
//
COND=(4,LE,HMPBTBL)
//SYSLIB
DD DSN=&BASEQUAL..COPYASM,DISP=SHR
//SYSIN
DD DSN=&&&&TBL1SRC,DISP=(OLD,DELETE)
//SYSUT1
DD SPACE=(CYL,(2,1)),
)SEL &VVOLREQ = Y
//
VOL=SER=&VVOL,
)ENDSEL
//
UNIT=&VUNIT
//SYSUT2
DD SPACE=(CYL,(2,1)),
)SEL &VVOLREQ = Y
//
VOL=SER=&VVOL,
)ENDSEL
//
UNIT=&VUNIT
//SYSUT3
DD SPACE=(CYL,(2,1)),
)SEL &VVOLREQ = Y
//
VOL=SER=&VVOL,
)ENDSEL
//
UNIT=&VUNIT
//SYSPUNCH DD DSN=&&&&LOADSET,
//
DISP=(,PASS),
//
SPACE=(400,(100,100,1)),
//
DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),
)SEL &VVOLREQ = Y
//
VOL=SER=&VVOL,
)ENDSEL
//
UNIT=&VUNIT
//SYSPRINT DD SYSOUT=*
//LKED
EXEC PGM=IEWL,PARM=(XREF,MAP,LIST,'AMODE=24','RMODE=24'),
//
COND=(4,LE,ASM)
//SYSLIB
DD DSN=&CICSRUNT.,DISP=SHR
//SYSLMOD DD DSN=&USRVQUAL..LOADCI(HPSTBLE1),DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSUT1
DD DCB=BLKSIZE=1024,
//
SPACE=(1024,(200,20)),
)SEL &VVOLREQ = Y
//
VOL=SER=&VVOL,
Planning and Installing AppBuilder for the Mainframe
page 224 of 284
//
)ENDSEL
//
//SYSLIN
VOL=SER=&VVOL,
UNIT=&VUNIT
DD DSN=&&&&LOADSET,DISP=(OLD,DELETE)
HPESDUG
DEFINE PROGRAM(KKACGPI) GROUP(HPESDUG)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(KKACGPS) GROUP(HPESDUG)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(KKACGPT) GROUP(HPESDUG)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(KKACGPU) GROUP(HPESDUG)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE TRANSACTION(KGPI) GROUP(HPESDUG)
PROGRAM(KKACGPI) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(KGPS) GROUP(HPESDUG)
PROGRAM(KKACGPS) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(KGPT) GROUP(HPESDUG)
PROGRAM(KKACGPT) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(KGPU) GROUP(HPESDUG)
PROGRAM(KKACGPU) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
HPESDUK
Planning and Installing AppBuilder for the Mainframe
page 225 of 284
DEFINE PROGRAM(KKACGPG) GROUP(HPESDUK)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(KKACGPL) GROUP(HPESDUK)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(KKACGPN) GROUP(HPESDUK)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(KKACGPV) GROUP(HPESDUK)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE TRANSACTION(KGPG) GROUP(HPESDUK)
PROGRAM(KKACGPG) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(KGPL) GROUP(HPESDUK)
PROGRAM(KKACGPL) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(KGPN) GROUP(HPESDUK)
PROGRAM(KKACGPN) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
DEFINE TRANSACTION(KGPV) GROUP(HPESDUK)
PROGRAM(KKACGPV) TWASIZE(0) PROFILE(HPECICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
AB34
*************************************************************
* CICS 3.3 STORAGE PROTECTION
*
*
*
* IF YOUR SITE HAS STORAGE PROTECTION ACTIVATED
*
*
*
* PLEASE CHANGE PCT ENTRIES FOR
*
* 'HPSXZCAT' AND 'HPSENAEP'
*
* TO
*
* EXECKEY(CICS)
*
*
*
* AB DEFINITIONS DO NOT INCLUDE STORAGE PROTECTION
*
*
*
*************************************************************
DEFINE MAPSET(HPSFM0A) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM0D) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM2A) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM2D) GROUP(AB34)
Planning and Installing AppBuilder for the Mainframe
page 226 of 284
DEFINE MAPSET(HPSFM2D) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM3A) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM3D) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM5A) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM5D) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM6A) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM6D) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM9A) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM9B) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM9D) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSFM9F) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE MAPSET(HPSSM4) GROUP(AB34)
RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO) STATUS(ENABLED)
DEFINE PROFILE(HPECICST) GROUP(AB34)
SCRNSIZE(ALTERNATE) UCTRAN(NO) PRINTERCOMP(NO) JOURNAL(NO)
MSGJRNL(NO) MSGINTEG(NO) ONEWTE(NO) PROTECT(NO) CHAINCONTROL(NO)
DVSUPRT(ALL) INBFMH(NO) RAQ(NO) LOGREC(NO) NEPCLASS(0)
RTIMOUT(NO)
DEFINE PROFILE(HPSPROF) GROUP(AB34)
SCRNSIZE(DEFAULT) UCTRAN(NO) PRINTERCOMP(NO) JOURNAL(NO)
MSGJRNL(NO) MSGINTEG(NO) ONEWTE(NO) PROTECT(NO) CHAINCONTROL(NO)
DVSUPRT(ALL) INBFMH(NO) RAQ(NO) LOGREC(NO) NEPCLASS(0)
RTIMOUT(1000)
DEFINE PROGRAM(CGETENV) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(DB2) GROUP(AB34)
DESCRIPTION(HPS DB2 SYSTEM COMPONENT USED FOR RULEVIEW BREAKPOINTS)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPCLOSEC) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPDCLOS) GROUP(AB34)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPDDELE) GROUP(AB34)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPDGENN) GROUP(AB34)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPDOPEN) GROUP(AB34)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPDREAD) GROUP(AB34)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER)
Planning and Installing AppBuilder for the Mainframe
page 227 of 284
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
PROGRAM(HPDWRIT) GROUP(AB34)
LANGUAGE(C) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL) USELPACOPY(NO)
STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW) EXECKEY(USER)
EXECUTIONSET(FULLAPI)
PROGRAM(HPECAPI) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPECO10) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPECV10) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPECV47) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPECV86) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPEGAPA) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPEHI10) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPEHS10) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPEHS11) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPEHS17) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPEHS75) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPELM10) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPERV41) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPESI10) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPESI19) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
Planning and Installing AppBuilder for the Mainframe
page 228 of 284
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPETM10) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPEYC10) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPEYP11) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPEYP84) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPEYP86) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPEYS06) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPEYS16) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPFAMSG) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPFINDC) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPFREEC) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPGETC) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPGTAID) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPOPENC) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSAMSG) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSASND) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSCGAP) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSCMPT1) GROUP(AB34)
Planning and Installing AppBuilder for the Mainframe
page 229 of 284
DEFINE PROGRAM(HPSCMPT1) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSCONVI) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSCONVO) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSENAEP) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(CICS) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSEQTBL) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSERRLG) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT00) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT01) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT02) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT03) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT04) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT05) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT06) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT07) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT08) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT09) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSFLT10) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
Planning and Installing AppBuilder for the Mainframe
page 230 of 284
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSINIT) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSLMSG) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSLMSW) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSMODE) GROUP(AB34)
DESCRIPTION(HPS SYSTEM COMPONENT THAT RETURNS EXECUTION ENVIRONMENT)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSNEWC) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI00) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI10) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI2I) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI2O) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI20) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI30) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI40) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPCI50) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPEP) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(YES) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(CICS) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPEP3) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(YES) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(CICS) EXECUTIONSET(FULLAPI)
DEFINE PROGRAM(HPSPRNT) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
Planning and Installing AppBuilder for the Mainframe
page 231 of 284
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSSEC4) GROUP(AB34)
LANGUAGE(PLI) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSSTART) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSTBLE1) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSTBLE2) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSTBLE3) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSTBLE4) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSTBLE5) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSTRSM) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSUTBL) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSVINIT) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSXSEC) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPSXZCAT) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(CICS) EXECUTIONSET(FULLAPI)
PROGRAM(HPSXZCIN) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(BELOW)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPUBDTB) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPUCV10) GROUP(AB34)
LANGUAGE(ASSEMBLER) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
PROGRAM(HPWRITEC) GROUP(AB34)
LANGUAGE(COBOL) RELOAD(NO) RESIDENT(NO) USAGE(NORMAL)
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
Planning and Installing AppBuilder for the Mainframe
page 232 of 284
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
DEFINE
USELPACOPY(NO) STATUS(ENABLED) CEDF(YES) DATALOCATION(ANY)
EXECKEY(USER) EXECUTIONSET(FULLAPI)
TRANSACTION(ENAE) GROUP(AB34)
PROGRAM(HPSENAEP) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HPC7) GROUP(AB34)
PROGRAM(HPECV47) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HPEL) GROUP(AB34)
PROGRAM(HPSERRLG) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HPI0) GROUP(AB34)
PROGRAM(HPESI10) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HPRT) GROUP(AB34)
PROGRAM(HPSPRNT) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HPR0) GROUP(AB34)
PROGRAM(HPERV41) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HPT0) GROUP(AB34)
PROGRAM(HPETM10) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HSND) GROUP(AB34)
PROGRAM(HPSASND) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HS04) GROUP(AB34)
PROGRAM(HPSSEC4) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HS06) GROUP(AB34)
PROGRAM(HPSNEWC) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(HS08) GROUP(AB34)
PROGRAM(HPSLMSW) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(PCIO) GROUP(AB34)
PROGRAM(HPSPCI00) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(STRT) GROUP(AB34)
PROGRAM(HPSSTART) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
Planning and Installing AppBuilder for the Mainframe
page 233 of 284
DEFINE
DEFINE
DEFINE
DEFINE
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(TRCL) GROUP(AB34)
PROGRAM(HPSFLT00) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(TRLE) GROUP(AB34)
PROGRAM(HPSCMPT1) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED)
TASKDATALOC(BELOW) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(TRLS) GROUP(AB34)
PROGRAM(HPSFLT10) TWASIZE(0) PROFILE(HPSPROF) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
TRANSACTION(UTBL) GROUP(AB34)
PROGRAM(HPSUTBL) TWASIZE(0) PROFILE(DFHCICST) STATUS(ENABLED)
TASKDATALOC(ANY) TASKDATAKEY(USER) DYNAMIC(NO) PRIORITY(1)
TCLASS(NO) DTIMOUT(NO) INDOUBT(BACKOUT) RESTART(NO) SPURGE(NO)
TPURGE(NO) DUMP(YES) TRACE(YES) RESSEC(NO) CMDSEC(NO)
HPSPLAN
*ASM XOPTS(NOPROLOG,NOEPILOG)
*------------------------------------------------------​
*The following MUST be done to use the DB2 RCT Plan Exit:
*------------------------------------------------------​
*-​
*(1) An RCT entry must be made as follows:
*-​
* DSNCRCT TYPE=POOL, Pool thread definition
* THRDM=20,
Maximum number of threads
* THRDA=20,
Initial number of threads
* PLNEXIT=YES,
Use plan exit for pool threads
* PLNPGME=HPSPLAN
Plan exit name for pool threads
*--​
*and
*--​
* (2) A PPT entry must be made as follows:
*-*
HPSPLAN DFHPPT TYPE=ENTRY,PROGRAM=HPSPLAN,PGMLANG=ASSEMBLER
*
* (3) The following code must be assembled, link-edited and placed
*
into your CICS load libraries.
*
NOTE: The 1st line '*ASM XOPTS(NOPROLOG,NOEPILOG)' is not a
*
---- comment but an assembler directive - DO NOT ERASE.
*
NOTE: The SP option needs to be specifed on the CICS translate
*
---- step.
*
NOTE: The DB2 macro library needs to be specifed in the STEPLIB
*
---- of the compile step.
*
*
.$.0 031793 HPS DB2 Plan Exit for CICS
HPSPLAN0.ASM 0 NS
*********************************************************************
*
*
* Classification
= BluePhoenix Solutions, Inc.
*
*
(c) Copyright 2002
*
*
*
*
*
* $$NAME
NAME=HPSPLAN
*
Planning and Installing AppBuilder for the Mainframe
page 234 of 284
* $$NAME
NAME=HPSPLAN
*
* $$VERSION
ID=5.2.0
*
* $$CALL
TYPE=PROGRM
NAME=&&&& ID=3.1.0
*
* Programmer
= Field Support
*
* Date
= Oct. 5, 2002
*
* Brief Module
= HPS DB2 Plan Exit FOR CICS
*
Description
*
* Detailed Description =
* This is the DB2 RCT plan exit for the HPS/CICS Pool threads.
*
* It checks the name of the program that is tied to the current
* transaction and alters the plan name to be executed.
*
* Rules:
* If the transaction is defined to either program HPSPCI00 or
* HPETM10 then the transaction ID is concatenated with the
* characters 'PLNC'. Thus the DAAW transaction would use the
* DAAWPLNC plan. Otherwise exit back to CICS.
*
* Inputs
=
*
* Outputs
=
*
* External Routines
=
*
* ASM Copy Statements =
*
* EXEC SQL INCLUDE's
= None
*
* Modification History =
*
* CHANGE ACTIVITY:
* SEQ RVML PI YYMMDD --- Description -----------------------------*
****************************************************************
*
DSNCPRMA
PROGRAM DS
CL8
EJECT
HPSPLAN DFHEIENT CODEREG=12,
R12 is base register
X
DATAREG=13,
R13 for dynamic storage
X
EIBREG=11
and R11 for the EIB
B
START
START
EQU *
L
R2,DFHEICAP
Get COMMAREA address
USING CPRMPARM,R2
Map the commarea
MVC CPRMPLAN,=CL8' '
Clear out existing plan name
MVC PROGRAM,=CL8' '
Initialize variable
EXEC CICS INQUIRE TRANSACTION(EIBTRNID)
X
PROGRAM(PROGRAM)
X
NOHANDLE
SPACE
* The following compare statements check the programs defined to the
* CICS transaction.
CLC PROGRAM,=CL8'HPSPCI00' Is it an HPS transaction ?
BE
$LMOVE
CLC PROGRAM,=CL8'HPETM10 ' Is it a PCV 3270 transaction ?
BNE $LRETURN
No, back to CICS
$LMOVE MVC CPRMPLAN(4),EIBTRNID
Else move TRAN ID ...
Planning and Installing AppBuilder for the Mainframe
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
page 235 of 284
$LMOVE
MVC CPRMPLAN(4),EIBTRNID
Else move TRAN ID ...
MVC CPRMPLAN+4(4),=CL4'PLNC' ... plus 'PLNC'
$LRETURN DS 0H
Back to CICS
EXEC CICS RETURN
LTORG
DFHEISTG
DFHEIEND
R0
EQU 0
R1
EQU 1
R2
EQU 2
R3
EQU 3
R4
EQU 4
R5
EQU 5
R6
EQU 6
R7
EQU 7
R8
EQU 8
R9
EQU 9
R10
EQU 10
R11
EQU 11
R12
EQU 12
R13
EQU 13
R14
EQU 14
R15
EQU 15
END
Planning and Installing AppBuilder for the Mainframe
page 236 of 284
Appendix C. VTAM definitions
This appendix contains the sample VTAM definitions that apply to AppBuilder on CICS and IMS.
M06HPS
*
* VTAM APPLICATION DEFINITIONS REQUIRED BY THE HPSLU2B PROGRAM
* WHICH EMULATES A LU2 DEVICE
*
* YOU MAY SUBSTITUTE DIFFERENT ACBNAMES FOR THE ONES GIVEN BELOW.
*
M06HPS
VBUILD TYPE=APPL
A06HPS1 APPL ACBNAME=A06HPS1,
APPLID FOR ACB
AUTH=(ACQ,PASS,VPACE), AB CAN ACQUIRE, PASS, & VPACE
MODETAB=MODESNA,
DEFAULT MODE TABLE
DLOGMOD=HPSLU2,
AB LU2 MODE ENTRY
EAS=1
EASTIMATED SESSIONS = 1
*
A06HPS2 APPL ACBNAME=A06HPS2,
APPLID FOR ACB
AUTH=(ACQ,PASS,VPACE), AB CAN ACQUIRE, PASS, & VPACE
MODETAB=MODESNA,
DEFAULT MODE TABLE
DLOGMOD=HPSLU2,
AB LU2 MODE ENTRY
EAS=1
EASTIMATED SESSIONS = 1
*
A06HPS3 APPL ACBNAME=A06HPS3,
APPLID FOR ACB
AUTH=(ACQ,PASS,VPACE), AB CAN ACQUIRE, PASS, & VPACE
MODETAB=MODESNA,
DEFAULT MODE TABLE
DLOGMOD=HPSLU2,
AB LU2 MODE ENTRY
EAS=1
EASTIMATED SESSIONS = 1
*
X
X
X
X
X
X
X
X
X
X
X
X
MODELU62
Planning and Installing AppBuilder for the Mainframe
page 237 of 284
*
* SAMPLE VTAM LOGMODE TABLE DEFINITIONS FOR LU62 COMMUNICATIONS
* USED BY OS/2 COMMUNICATIONS MANAGER AND CICS
*
MODELU62 MODETAB
ABLU62
MODEENT LOGMODE=ABLU62,
TYPE=0,
FMPROF=X'13',
TSPROF=X'07',
PRIPROT=X'B0',
SECPROT=X'B0',
COMPROT=X'50B1',
SSNDPAC=X'00',
SRCVPAC=X'03',
RUSIZES=X'8585',
PSNDPAC=X'03',
PSERVIC=X'060200000000000000002C00'
*
A32792B MODEENT LOGMODE=A32792B,
LOCAL SNA(3274-X1A) 3279-2B
FMPROF=X'03',
TSPROF=X'03',
PRIPROT=X'B1',
SECPROT=X'90',
COMPROT=X'3080',
RUSIZES=X'87C7',
LANG=X'80',
PSERVIC=X'02C000000000185000007E00'
*
MODEEND
END
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
MODESCS
************************************************************
*THIS LOGMODE ENTRY DEFINES A LU1 SCS PRINTER WITH THE QUERY FACILITY *
* WHICH IS REQUIRED FOR THE IBM 5577 PRINTER.
*
***********************************************************
MODESCS MODETAB
SCSPRTQ MODEENT LOGMODE=SCSPRTQ,
X
TYPE=1,
X
FMPROF=X'03',
X
TSPROF=X'03',
X
PRIPROT=X'B1',
X
SECPROT=X'90',
X
COMPROT=X'7080',
X
RUSIZES=X'85C7',
X
PSERVIC=X'01000001E100000001000000'
MODEEND
END
MODESNA
Planning and Installing AppBuilder for the Mainframe
page 238 of 284
*-AppBuilder-**-AppBuilder-**-AppBuilder-**-AppBuilder-**-AppBuilder-*
*
*
*
V T A M
D E F I N I T I O N S
*
*
*
*-AppBuilder-**-AppBuilder-**-AppBuilder-**-AppBuilder-**-AppBuilder-*
*
* VTAM LOGMODE TABLE DEFINITIONS REQUIRED BY THE HPSLU2B PROGRAM
* WHICH EMULATES A LU2 DEVICE
*
MODESNA MODETAB
HPSLU2
MODEENT LOGMODE=HPSLU2,
AppBuilder/CICS RUNTIME ENVIRONMENT
FMPROF=X'03',
TSPROF=X'03',
PRIPROT=X'B1',
SECPROT=X'B0',
COMPROT=X'3080',
RUSIZES=X'E8E8',
PSERVIC=X'020000000000185018507F00'
MODEEND
END
ABMN
*
* SAMPLE VTAM DEFINITION FOR AN AB OS/2 WORKSTATION THAT COMMUNICATES
* TO THE HOST ACROSS A TOKEN RING VIA DLC. THE SECOND LOGICAL UNIT
* IS DEFINED TO AS AN APPC TERMINAL AND THE SIXTH LU IS DEFINED AS AN
* SNA SCS PRINTER.
*
ABMN
VBUILD TYPE=SWNET,
SWITCHED MAJOR NODE
MAXGRP=2,
NUMBER OF UNIQUE PATH GROUPS
MAXNO=2
NUMBER OF UNIQUE DIALNO NUMBERS
*
ABPU
PU
ADDR=01,
ANY VALUE (NOT USED, BUT REQ'D)
IDBLK=05D,
FOR VTAM XID (DO NOT CHANGE)
IDNUM=0010A,
FOR VTAM XID, COULD BE SERIAL #
MAXPATH=2,
NUMBER OF PATHS TO THE PU
MAXOUT=7,
MAX PIUS TO PU BEFORE RESP REQ
MODETAB=MODELU62,
MODE TABLE
DLOGMOD=A32792B,
MODE TABLE ENTRY
PACING=7,
# NORM RUS BEFORE PACING RESP
PASSLIM=7,
MAX CONGTIGOUS PIUS AT 1 TIME
SSCPFM=USSSCS,
CHARACTER CODED RUS
USSTAB=USSSNA,
USS TABLE
VPACING=0
NO VPACING FOR LU
*
ABA
LU
LOCADDR=0
ABB
LU
LOCADDR=2,DLOGMOD=ABLU62
ABC
LU
LOCADDR=3
ABD
LU
LOCADDR=4
ABE
LU
LOCADDR=5
ABF
LU
LOCADDR=6,DLOGMOD=SCSPRTQ,MODETAB=MODESCS
*
Planning and Installing AppBuilder for the Mainframe
X
X
X
X
X
X
X
X
X
X
X
X
X
page 239 of 284
Appendix D. HPSCGAP, HPICGAP, HPEUCGP, and sample
batch JCL
This appendix contains the detailed descriptions for HPSCGAP, HPICGAP, and HPEUCGP---load module tables that
contain site-specific information required by AppBuilder software.
HPSCGAP and HPSIGAP
The AppBuilder CICS Global Parameters Table (HPSCGAP) is a load module holding site-specific information
AppBuilder requires. It is located in &BASEQUAL..LOADBT and &BASEQUAL..LOADCI.
For IMS, the corresponding file is the AppBuilder IMS Global Parameters Table (HPSIGAP). The files are located in
&BASEQUAL..LOADIM
Note
Two links are required if you change HPSCGAP or HPSIGAP.
For CICS, the source is located in &BASEQUAL..SVC34.SAMPLE(HPSCGAP) and sample JCL is located in
&BASEQUAL..SVC34.SAMPLE(SKLCGAP). HPSCGAP is a CSECT containing site​ specific information and is
accessed during AppBuilder processing. Modify the source to reflect parameters at your site, then reassemble the
source. You should ensure the currency symbol (HGACSTOK) and default country (HGAXTRYD and HGACTRYC)
variables are correct for your site.
For IMS, the source is located in &BASEQUAL..SVI34.SAMPLE(HPICGAP) and sample JCL is located in
&BASEQUAL..SVI34.SAMPLE(HPICAPJ).
Table D-1 is a description of the significant parameters for HPSCGAP and HPSIGAP.
Table D-1 provides the supported country/language numbers for HPSCGAP and HPSIGAP variables.
Table D-1 HPSCGAP and HPSIGAP Variables
Variable
Description
TCTUAOFF
The requirement for a TCTUA has been removed in AppBuilder. Must be set to the default value
(0).
EXECENV
Type of CICS or IMS execution environment. D for Development and P for Production. The
default value is D.
SECURITY
Mainframe Security Active (Y or N). The default value is Y.
SAF
No longer used. Must be set to the default value (N).
NOTIFY
No longer used. Must be set to the default value (N).
STRAT62
Mainframe to Stratus LU6.2 Link Active (Y or N). The default value is (N).
HPS
No longer used. Must be set to the default value (N).
CNV3270
3270 Converse Product Active (Y or N). The default value is (Y).
SDS
Software Distribution System Active (Y or N). The default value is (Y).
LU62SAF
No longer used. Must be set to the default value (N).
Planning and Installing AppBuilder for the Mainframe
page 240 of 284
WKSSECR
Workstation Security Active (Y or N). This applies only to 3270 Converse Logic. If this is set to
Y, the 3270 Converse modules validate Workstation Security when AppBuilder Security is
active. The default value is (Y).
XSECEXIT
Invoke user exit from the HPSXSEC external security interface module (Y or N). The default
value is (N).
ASYNC
Asynchronous communications support to workstations active (Y or N). The default value is (Y).
HGACSTOK
Currency symbol token used to determine the hexadecimal value of the dollar sign "$" in the
local code page. This value must be set too display the dollar in the local code page. the default
value is $ (x’5B’).
HGAHREPL
AppBuilder repository version. This is set to the character that identifies the current AppBuilder
repository version this CICS region supports. The default value is (1).
HGAHREPN
AppBuilder repository name. A character string that uniquely identifies the current AppBuilder
repository version this CICS or IMS region supports. The default value is blank.
HGACTRYD
Default country this CICS or IMS region supports. The default value is USA (34). See Table D-2.
HGACTRYC
Current country this CICS or IMS region supports. The default value is USA (34). These two
fields should both be set to the required country number. See Table D-2.
HGANLNGD
Default Language Abbreviation for MLS support. The default value is ENU for the United States.
Refer to Table 5-3, “Definition of Default Language Abbreviations” in Chapter 6, “Installing the
Enterprise Repository” for more information.
HPS001D1
DDNAME for the view definition file. The default value is HPS001D1 for CICS or HPI001D1 for
IMS.
HPS002D1
DDNAME for the test data file. The default value is HPS002D1 for CICS or HPI002D1 for IMS.
HPS003D1
DDNAME for the rule source file. The default value is HPS003D1 for CICS or HPI003D1 for IMS.
HPS004D1
DDNAME for the rule relationship file. The default value is HPS004D1 for CICS or HPI004D1 for
IMS
SEC001H1
DDNAME for the menu file. The default value is SEC001H1 for CICS or SEI001H1 for IMS
HPS006D1
DDNAME for the ERROR LOG file. The default value is HPS006D1 for CICS or HPI006D1 for
IMS
SEC003H1
DDNAME for the security log file. The default value is SEC003H1 for CICS or SEI003H1 for IMS
HPS008D1
No longer used. The default value is HPS008D1.
HPSBC1D1
DDNAME for asynchronous broadcast data. The default value is HPSBC1D1.
HPSBC2D1
DDNAME for asynchronous broadcast ID table. The default value is HPSBC2D1.
HPEL
Transient data queue for error logging. The default value is HPEL.
HCSW
Transient data queue for security logging. The default value is HCSW.
HPNL
No longer used. The default value is HPNL.
Planning and Installing AppBuilder for the Mainframe
page 241 of 284
Table D-2 defines the supported country and language numbers supported in the AppBuilder environment.
Table D-2 Supported AppBuilder environment country/language numbers
Country
#
Country
#
Albania
1
Netherlands
19
Argentina
2
New Zealand
20
Austria
3
Norway
21
Belgium
4
Poland
22
Brazil
5
Portugal
23
Canada---French
6
Romania
24
Canada---English
7
South Africa
25
China
8
South Korea
26
Czechoslovakia
9
Spain
27
Denmark
10
Sweden
28
Finland
11
Switzerland
29
France
12
Taiwan
30
Germany
13
Thailand
31
Greece
14
Turkey
32
Hungary
15
United Kingdom
33
Iceland
16
United States
34
Italy
17
Yugoslavia
35
Japan
18
HPSCGAP Code
The following is the source code for HPSCGAP for CICS and Batch.
• The CICS file is located in: &BASEQUAL..SVC34.SAMPLE(HPSCGAP).
• The Batch file is located in: &BASEQUAL..SVB34.SAMPLE(HPSCGAP).
*
.$.0 081094 HPS/CICS GLOBAL PARAM CSECT HPSCGAP.ASM
DC 25
*********************************************************************
*
*
* Classification
= BluePhoenix Solutions, Inc.
*
*
(c) Copyright 2002
*
*
*
*
*
* $$NAME
NAME=HPSCGAP
*
*
*
* $$VERSION
ID=3.4.0
*
Planning and Installing AppBuilder for the Mainframe
page 242 of 284
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
*
$$VERSION
ID=3.4.0
*
*
$$CALL
TYPE=PROGRM
NAME=&&&&&&&& ID=3.4.0
*
*
Programmer
= N. Shing, M. Dolciger
*
Date
= October 11, 2002
*
Brief Module
Description
= HPS/CICS incore global parameters
table used to configure the HPS/CICS
run time environment.
*
*
*
*
*
*
Detailed Description =
*
THIS CSECT GENERATES A LOAD MODULE WHICH IS USED
*
AS A GLOBAL PARAMETER TABLE FOR ALL HPS/CICS PROGRAMS. *
THIS PARAMETER TABLE WILL ALLOW FOR ONSITE CUSTOMIZATION.*
*
Inputs
=
*
*
Outputs
=
*
*
External Routines
=
*
*
ASM Copy Statements =
*
*
EXEC SQL INCLUDE's
= None
*
*
Modification History =
*
*
CHANGE ACTIVITY:
*
SEQ RVML PI YYMMDD --- Description ------------------------------*
025 5300 DC 940810 Add Default National Language
*
024 3700 DC 931111 Add file read parameters
*
023 3480 DC 930413 Add CICS release level
*
022 3480 NS 930408 Set HPS Error Log DDNAME to HPS006D1
*
021 3480 NS 930312 Default Version Number to One
*
020 3480 DC 930201 Add address of Codepage translation routine
* 019 3480 NS 930201 Restored Correct Broadcast File Names
*
*018 3400 DM 930121 Chg WXTRNs into EXTRNs, Link-Ed fail if missing *
* 017 3400 DM 921215 Match to DSECT chgs, Repos name, Nat Lang Supp *
* 016 3400 JL 920603 Changed fields for CASIM security support
*
* 015 3400 NS 920116 Added fields for ASYNC support
*
* 014 3400 DC 910726 Added new flag to switch the user signon exit *
*
on or off.
*
* 013 3400 NS 910717 Added new parameter to switch Workstation
*
*
Security on or off.
*
* 012 3400 DM 910530 Add HGACONP addr of HPSCONP converse text
*
*
constants CSECT.
*
* 011 3200 JAK 900912 Add HGALMGP addr of HPSLMGP message tabl CSECT.*
* 010 3200 DM 900807 Split off SDS constants and Exit Code in a new *
*
CSECT.
*
* 009 3200 JAK 900711 Converse constants and exit code in new CSECT. *
* 008 3200 JDS 900715 Added HPS API Exit Area.
*
* 007 3200 MD 900522 Changed defaults as following:
*
*
NOTIFY=N,LU62SAF=N
*
* 006 3200 MD 900419 Added LU62 SAF Program Name.
*
* 005 3200 MD 900309 Added Time Interval Value for Post Wait Event- *
*
Cancel Mechanism.
*
* 004 3200 DM 900213 Changed SDS Default to 'Y'.
*
* 003 3200 MD 900213 Changed HPO Defualt to 'Y' and filled some
*
*
fields of the Converse Global Area.
*
* 002 3200 DM 900131 Filled some of the SDS Area
*
* 001 3200 MD 900124 Added 256 Bytes Area for SDS
*
*
*
Planning and Installing AppBuilder for the Mainframe
page 243 of 284
*
*
********************************************************************
EJECT
TITLE ' HPS/CICS GLOBAL PARAMETERS TABLE'
HPSCGAP CSECT
EXTRN HPSCVGP
CONVERSE GLOBAL AREA
EXTRN HPSGXIP
API GLOBAL EXIT AREA
EXTRN HPSSDSP
SDS GLOBAL AREA
10
EXTRN HPSLMGP
HPS ERROR MESSAGE ROUTE TABLE
11
EXTRN HPSCONP
HPS CONVERSE TEXT CONSTANTS
12
EXTRN HPEHL64
HPS CTRY/LANG SUPPORT TABLE
17
EXTRN HPELX10
CODEPAGE TRANSLATION ROUTINE
19
DC
CL8'HPSCGAP'
DC
CL16'&SYSDATE-&SYSTIME' DC
CL8' V3R4M8 '
SPACE 2
HGADDR EQU *
HGCPARMA DC
A(HGCPARM)
@ OF CONFIGURATION PARAMETER AREA
HGTBLA DC
A(HGTBL)
@ OF HPS INCORE TABLES AREA
HGFILEA DC
A(HGFILE)
@ OF HPS FILES AREA
HGTDQA DC
A(HGTDQ)
@ OF HPS TDQ'S AREA
HGTSQA DC
A(HGTSQ)
@ OF HPS TSQ'S AREA
HGCONSTA DC
A(HGCONST)
@ OF HPS CONSTANTS AREA
HGACVGL DC
A(HPSCVGP)
@ OF CONVERSE GLOBAL AREA
09
HGADBUG DC
A(HGRDBUG)
@ OF DEBUG AREA
HGASDSA DC
A(HPSSDSP)
@ OF SOFTWARE DISTRIBUTION PARM 10
HGARESV DC
A(HGRESV)
@ OF FUTURE USE AREA
HGAEXIT DC
A(HPSGXIP)
@ OF HPS API EXIT AREA
09
HGALMGP DC
A(HPSLMGP)
@ HPS ERROR MESSAGE ROUTE TABLE 11
HGACONP DC
A(HPSCONP)
@ HPS CONVERSE TEXT CONSTANTS 12
HGALANG DC
A(HPEHL64)
@ HPS CTRY/LANG SUPPORT TABLE 17
HGACPTR DC
A(HPELX10)
@ HPS CODEPAGE TRANSLATION
19
HGADDRF EQU HPSCGAP+256-*
LENGTH TO PAD
DC
(HGADDRF)X'0'
PAD WITH BINARY ZEROS
ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256) ALIGN TO X'100'
HGCPARM EQU *
TCTUAOFF DC
H'0'
TCTUA OFFSET
EXECENV DC
C'D'
EXECUTION ENVIRONMENT
DEVELOP EQU C'D'
DEVELOPMENT ENVIRONMENT
PROD
EQU C'P'
PRODUCTION ENVIRONMENT
SECURITY DC
C'N'
SECURITY ON (YES/NO)
SAF
DC
C'N'
INVOKE HPSSAF (YES/NO)
NOTIFY DC
C'N'
PHASEII NOTIFICATION (YES/NO)
STRAT62 DC
C'N'
STRATUS LU6.2 INTERFACE
HPO
DC
C'N'
HIGH PERFORMANCE OPTION(YES/NO)
CONV3270 DC
C'Y'
3270 CONVERSE SUPPORT (YES/NO)
SDS
DC
C'Y'
SOFTWARE DISTRUBUTION(YES/MO)
LU62SAF DC
C'N'
LU62 SAF ACTIVE
WKSSECR DC
C'Y'
WORKSTATION SECURITY (YES/NO)
*
CURRENTLY APPLIES ONLY TO
*
3270 CONVERSE SECURITY LOGIC
XSECEXIT DC
C'N'
USER SECURITY SIGNON EXIT (Y/N)
ASYNC
DC
C'Y'
ASYNCH SUPPORT (YES/NO)
HGACSTOK DC
C'$'
DOLLAR
THE CURRENCY SYMBOL TOKEN
17
*
USED TO DETERMINE HEX VALUE OF $ IN LOCAL CODE PAGE 17
HGAHREPL DC
C'1'
HPS REPOSITORY LEVEL
21
HGAHREPN DC
CL8' '
HPS REPOSITORY NAME
17
HGACTRYD DC
H'34'
USA
HPS COUNTRY - DEFAULT
17
HGACTRYC DC
H'34'
USA
HPS COUNTRY - CURRENT
17
HGANLNGD DC
CL3'ENU'
English - USA National Lng - default 25
DC
CL1' '
Unused
25
HGCPARMF EQU HGCPARM+256-*
LENGTH TO PAD
DC
(HGCPARMF)X'0'
PAD WITH BINARY ZEROS
ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
HGTBL
EQU *
HPS INCORE TABLES AREA
TBL1ADDR DS
F
RULE/TRANSID TABLE 1
TBL2ADDR DS
F
RULE/TRANSID TABLE 2
Planning and Installing AppBuilder for the Mainframe
page 244 of 284
TBL2ADDR
TBL3ADDR
TBL4ADDR
TBL5ADDR
TBL6ADDR
TBL7ADDR
TBL8ADDR
TBL9ADDR
TBL10ADR
HGTBLF
DS
DS
DS
DS
DS
DS
DS
DS
DS
EQU
DC
ORG
HGFILE
EQU
HPS000D1 DS
HPS001D1 DC
HPS002D1 DC
F
RULE/TRANSID TABLE 2
F
USRUSG/WKSNGP/BP TABLE
F
NOTIFICATION TABLE
F
USER/WRKSTN TABLE
F
CONNECTIONS/SESSIONS TABLE
F
HPS PROGRAMS TABLE
F
RESERVED
F
RESERVED
F
RESERVED
HGTBL+256-*
LENGTH TO PAD
(HGTBLF)X'0'
PAD WITH BINARY ZEROS
HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
*
HPS FILES AREA
CL8
RESERVED
CL8'HPS001D1'
VIEW DEFINITION FILE
CL8'HPS002D1'
TEST DATA FILE
HPS003D1
HPS004D1
SEC001H1
HPS006D1
SEC003H1
HPS008D1
HPSBC1D1
HPSBC2D1
HGFILEF
DC
CL8'HPS003D1'
RULE SOURCE FILE
DC
CL8'HPS004D1'
RULE RELATIONSHIP FILE
DC
CL8'SEC001H1'
MENU FILE
DC
CL8'HPS006D1'
ERROR LOG
DC
CL8'SEC003H1'
SECURITY LOG
DC
CL8'HPS008D1'
NOTIFICATION LOG
DC
CL8'HPSBC1D1'
BROADCAST MESSAGE DATA
DC
CL8'HPSBC2D1'
BROADCAST ID TABLE
EQU HGFILE+256-*
LENGTH TO PAD
DC
(HGFILEF)X'0'
PAD WITH BINARY ZEROS
ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
HGTDQ
EQU *
HPS TDQS AREA
HPEL
DC
CL4'HPEL'
ERROR LOG TD QUEUE
HCSW
DC
CL4'HCSW'
SECURITY LOG TD QUEUE
HPNL
DC
CL4'HPNL'
NOTIFICATION LOG TD QUEUE
HGTDQF
EQU HGTDQ+256-*
LENGTH TO PAD
DC
(HGTDQF)X'0'
PAD WITH BINARY ZEROS
ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
HGTSQ
EQU *
HPS TSQS AREA
DC
XL256'00'
HGTSQF
EQU HGTSQ+256-*
LENGTH TO PAD
DC
(HGTSQF)X'0'
PAD WITH BINARY ZEROS
ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
HGCONST EQU *
HPS CONSTANTS AREA
APPCTERM DC
X'C0F0'
-APPC TERMINAL
T3270
DC
X'91F2'
-3270 TERMINAL
POSTWAIT DC
PL4'5959'
-ALMOST ONE HOUR
LU62SAFN DC
CL8'FBCSAFZ'
-LU62 SAF
PGMNAME
HGACREL DC
CL4'0000'
-CICS RELEASE LEVEL
23
DS
CL4
Unused
24
DS
CL16
Reserved for HPEGAPA
24
HGAFIWAT DC
PL4'5'
Wait 5 secs bet reads (0HHMMSSs)24
HGAFIRET DC
H'1'
Retry VSAM read once
24
HGCONSTF EQU HGCONST+256-*
LENGTH TO PAD
DC
(HGCONSTF)X'0'
PAD WITH BINARY ZEROS
*
ORG ,
ORG TO TOP OF AREA USED
11
ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
11
*
*--Please name all reserved areas with HGRxxxx here.
*
HGRDBUG DC
XL256'00'
HPS DEBUG AREA
*
HGRESV DC
XL256'00'
HPS FUTURE USE
*
Planning and Installing AppBuilder for the Mainframe
page 245 of 284
*
HPSCGAPE EQU
END HPSCGAP
*
END OF PROGRAM
08
HPEUCGP
This sample file defines the area of AppBuilder/CICS that users can customize for their site.
TITLE 'H P E U C G P
HPS User Customizable Constants
'
* .$.0 081094 HPS/CICS User Custom Constants HPEUCGP.ASM DC 02
***UCGP HCEEAAG VER=2.0.3.2,TYPE=TABL, Documentation Only !
***
MSG=' User Customizable Constants
!'
**-*-*
*
HPSCPYR ' (c) Copyright 2002, BluePhoenix Solutions, Inc. '
*
* $$NAME
NAME=HPEUCGP
*
* $$VERSION
ID=3.7.0
*
* $$CALL
TYPE=PROGRM
NAME=&&&&&&&& ID=3.7.0
*
* Programmer
= Jeffrey Katz
*
* Date
= August 2002
*
* Brief Description
= Constants Area Changed by End User
*
* Detailed Description = This program defines an area in which the
*
end user may customize constants.
*
* Inputs
= None
*
* Outputs
= None
*
* External Routines
= none
*
* ASM Copy Statements =
*
* EXEC SQL INCLUDE's
= None
*
* MODE: AMODE=31,RMODE=ANY
*
* Modification History =
* .SEQ RVML PI YYMMDD --- Description +---------+--------+--------+* 02 5300 DC 940810 Added Default National Language
* 01 3700 JAK 930831 First version for Country specific information
**-*-*
*-HPEUCGP CSECT ,
\UCAP User Customizable Constants area
DC
CL08'HPEUCGP '
DC
CL16'&SYSDATE-&SYSTIME'
DC
CL08' V3R7M0 '
***
*** USER: DO NOT ALTER ANYTHING BEFORE THIS LINE
***
HGACSTOK DC
CL1'$'
Dollar Sign
Currency Symbol Token
*
Defines the binary value of the Currency Symbol in the
*
Local Code Page.
Set to a single national character.
*
HGAHREPL DC
CL1'1'
Default HPS Repository Level
Planning and Installing AppBuilder for the Mainframe
page 246 of 284
HGAHREPL DC
CL1'1'
Default HPS Repository Level
DC
CL8' '
Do NOT ALTER
*
HGACTRYD DC
H'34'
USA
Default HPS Country Number
HGACTRYC DC
H'34'
USA
Current HPS Country Number
HGANLNGD DC
CL3'ENU' English - USA Default National Language 02
*
***
DC
CL1' '
Do NOT ALTER
02
*** USER: DO NOT ALTER ANYTHING AFTER THIS LINE
***
PGMEND DC
0D'0'
End of program
END ,
\PGMEND
SKLCGAP.JCL
The following is the sample JCL file for CICS, located in &BASEQUAL..SVC34.SAMPLE(SKLCGAP).
//*
PLACE JOBCARD HERE
//*---------------------------------​
//* THIS JOBSTREAMASSEMBLES HPSCGAP INTO THE LEVELC OBJECT LIBRARY
//* AND LINKS IT INTO THE &MODQUAL.LOADCI LIBRARY.
//*---------------------------------​
//* ASSEMBLE AND LINK HPSCGAP
//*---------------------------------​
//ASM
EXEC PGM=&HASMPGM.,PARM='DECK,NOOBJECT',
//
REGION=512K
//SYSLIB
DD DSN=SYS1.MACLIB,DISP=SHR
//
DD DSN=&MODGEN,DISP=SHR
//
DD DSN=&CICSLMAC,DISP=SHR
//SYSIN
DD DSN=&BASEQUAL..SAMPLE(HPSCGAP),
//
DISP=SHR
//SYSUT1
DD SPACE=(CYL,(2,1)),
//
UNIT=&TUNIT
//SYSUT2
DD SPACE=(CYL,(2,1)),
//
UNIT=&TUNIT
//SYSUT3
DD SPACE=(CYL,(2,1)),
//
UNIT=&TUNIT
//SYSPUNCH DD DSN=&MODQUAL..OBJ(HPSCGAP),DISP=OLD
//
UNIT=&TUNIT
//SYSPRINT DD SYSOUT=*
//LKED
EXEC PGM=IEWL,PARM=(REUS,XREF,LIST,'AMODE=31','RMODE=ANY')
//SYSLIB
DD DSN=&CICSRUNT,DISP=SHR
//OBJECT
DD DSN=&MODQUAL..OBJ,DISP=SHR
//
DD DSN=&BASEQUAL..OBJ,DISP=SHR
//SYSLMOD DD DSN=&MODQUAL..LOADCI,DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSUT1
DD DCB=BLKSIZE=1024,
//
SPACE=(1024,(200,20)),
//
UNIT=&TUNIT
//SYSLIN
DD *
SETSSI
01039407 .$.0 NEW NLS INFO GLOBAL
HPSCGAP.LKC
DC
INCLUDE
OBJECT(HPSCGAP)
INCLUDE
OBJECT(HPSCVGP)
INCLUDE
OBJECT(HPSGXIP)
INCLUDE
OBJECT(HPSSDSP)
INCLUDE
OBJECT(HPSLMGP)
INCLUDE
OBJECT(HPSCONP)
INCLUDE
OBJECT(HPSCNVC)
INCLUDE
OBJECT(HRNTBL)
NLS UPPER, LOWER TRANS TABLES
Planning and Installing AppBuilder for the Mainframe
page 247 of 284
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
INCLUDE
ENTRY
NAME
OBJECT(HRNTBL)
OBJECT(HPEHL64)
OBJECT(HPEHL10)
OBJECT(HPETODT)
OBJECT(HPETOTM)
OBJECT(HPEUE11)
OBJECT(HPEUE12)
OBJECT(HPEUE13)
OBJECT(HPEUE14)
OBJECT(HPEUE15)
OBJECT(HPEUE16)
OBJECT(HPEUE17)
OBJECT(HPEUE18)
OBJECT(HPEUE19)
OBJECT(HPEUE20)
OBJECT(HPEUE50)
OBJECT(HPELX10)
OBJECT(HLXOS2)
OBJECT(HLXUNIX)
OBJECT(HLXWIN)
OBJECT(HLX9999)
HPSCGAP
HPSCGAP(R)
NLS UPPER, LOWER TRANS TABLES
ENTRY PTS HPEHL00 AND HPEUE10
CODEPAGE TRANSLATION ROUTINE
TRANS TABLE FOR OS2
TRANS TABLE FOR UNIX
TRANS TABLE FOR WINDOWS
TRAILER TABLE ENTRY
Host Batch JCL
The following code samples show the JCL for AppBuilder batch DB2 and non-DB2 rules. The chief difference
between them is that the DB2 version runs under the DB2 command processor DSN
Batch DB2 JCL
The code sample below shows the JCL for AppBuilder batch DB2 rules.
//***********************************************************
//* SAMPLE BATCH DB2 JCL
*
//***********************************************************
// RUNBATCH EXEC PGM=IKJEFT01,DYNAMNBR=50,REGION=4096K
//***********************************************************
//* THE STEPLIB SHOULD CONTAIN
//* 1. THE DB2 RUNTIME LIBRARIES
//* 2. THE COBOL RUNTIME LIBRARIES
//* 3. THE PLI RUNTIME LIBRARIES
//* 4. THE C/370 RUNTIME LIBRARIES
//* 5. HPS USER BATCH LOADLIB
//* 6. HPS BASE BATCH LOADLIB
//* 7. HPS BASE LOADLIB
//***********************************************************
//STEPLIB
DD DSN=&DB2LOAD.,DISP=SHR
//
DD DSN=&DB2LINK.,DISP=SHR
//
DD DSN=&COB2LINK.,DISP=SHR
//
DD DSN=&PLILINK.,DISP=SHR
//
DD DSN=&PLILINK2.,DISP=SHR
//
DD DSN=&C370LNK1.,DISP=SHR
//
DD DSN=&C370LNK2.,DISP=SHR
//
DD DSN=&USRVQUAL..LOADBT,DISP=SHR
//
DD DSN=&REPQUAL..LOADBT,DISP=SHR
//
DD DSN=&MODQUAL..LOADBT,DISP=SHR
Planning and Installing
AppBuilder for the Mainframe
page 248 of 284
//
DD DSN=&MODQUAL..LOADBT,DISP=SHR
//
DD DSN=&BASEQUAL..LOADBT,DISP=SHR
//
DD DSN=&REPQUAL..LOADLIB,DISP=SHR
//
DD DSN=&MODQUAL..LOADLIB,DISP=SHR
//
DD DSN=&BASEQUAL..LOADLIB,DISP=SHR
//***********************************************************
//* INPUT DD REQUIRED
//***********************************************************
// INPUTDD DUMMY
//***********************************************************
//* OUTPUT DD REQUIRED - USED FOR MESSAGES
//***********************************************************
//OUTPUTDD SYSOUT=*
//***********************************************************
//* USERS VIEWDEF VSAM FILE
//***********************************************************
//VIEWFILE DD DSN=&VSUVQUAL..BATCH.VIEWDEF,DISP=SHR
//***********************************************************
//* ALLOCATE APPLICATION INPUT AND OUTPUT FILES HERE
//* (E.G., REPORT, INPUT FILES, OUTPUT FILES)
//***********************************************************
//SYSTSPRT DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//PLIDUMP DD SYSOUT=*
//***********************************************************
//* INPUT FOR RUNNING UNDER DB2:
//* SYSTEM - THE DB2 SUBSYSTEM YOU ARE RUNNING UNDER
//* PROG - ALWAYS EXECUTING HPSBATCH
//* PLAN - PLAN NAME FOR RULE
//* PARM - SYSTEM ID OF RULE
//***********************************************************
//SYSTSIN
DD *
DSN SYSTEM(&DB2SVBID.)
RUN PROG(HPSBATCH)
+
PLAN(B1A1PLNB)
+
PARM('AAQANR')
END
Batch JCL (non-DB2)
The code sample below shows the JCL for AppBuilder non-DB2 batch rules.
Planning and Installing AppBuilder for the Mainframe
page 249 of 284
//***********************************************************
//* SAMPLE BATCH JCL
//***********************************************************
//***********************************************************
//* PARM IS RULE SYSTEM ID
//***********************************************************
// RUNBATCH PGM=HPSBATCH,PARM='AAMNNR'
//***********************************************************
//* THE STEPLIB SHOULD CONTAIN
//* 1. THE COBOL RUNTIME LIBRARIES
//* 2. THE PLI RUNTIME LIBRARIES
//* 3. THE C/370 RUNTIME LIBRARIES
//* 4. HPS USER BATCH LOADLIB
//* 5. HPS BASE BATCH LOADLIB
//* 6. HPS BASE LOADLIB
//***********************************************************
//STEPLIBDD DSN=&COB2LINK.,DISP=SHR
// DD DSN=&PLILINK.,DISP=SHR
// DD DSN=&PLILINK2.,DISP=SHR
// DD DSN=&C370LNK1.,DISP=SHR
// DD DSN=&C370LNK2.,DISP=SHR
// DD DSN=&USRVQUAL..LOADBT,DISP=SHR
// DD DSN=&REPQUAL..LOADBT,DISP=SHR
// DD DSN=&MODQUAL..LOADBT,DISP=SHR
// DD DSN=&BASEQUAL..LOADBT,DISP=SHR
// DD DSN=&REPQUAL..LOADLIB,DISP=SHR
// DD DSN=&MODQUAL..LOADLIB,DISP=SHR
// DD DSN=&BASEQUAL..LOADLIB,DISP=SHR
//***********************************************************
//* INPUT DD REQUIRED
//***********************************************************
// INPUT DD DUMMY
//***********************************************************
//* OUTPUT DD REQUIRED - USED FOR MESSAGES
//***********************************************************
//OUTPUT DD SYSOUT=*
//***********************************************************
//* USERS VIEWDEF VSAM FILE
//***********************************************************
//VIEWFILE DD DSN=&VSUVQUAL..BATCH.VIEWDEF,DISP=SHR
//***********************************************************
//* ALLOCATE APPLICATION INPUT AND OUTPUT FILES HERE
//* (E.G., REPORT, INPUT FILES, OUTPUT FILES)
//***********************************************************
//OUTPUTF
DD DSN=&&OUTPUT1,DISP=(,CATLG,DELETE),
//
DCB=(RECFM=FBA,LRECL=133,BLDSIZE=23408)
//SYSTSPRT DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//CEEDUMP DD SYSOUT=*
//PLIDUMP DD SYSOUT=*
/*
HPICGAP Code
The following is the source code for HPICGAP for IMS, located in: &BASEQUAL..SVI34.SAMPLE (HPICGAP).
Planning and Installing AppBuilder for the Mainframe
page 250 of 284
*.$.0 031793 HPS/IMS GLOBAL PARAM CSECT HPICGAP.ASM 1 PC 22
*************************************************************
*
*
* Classification
= BluePhoenix Solutions, Inc.
*
*
(c) Copyright 2002
*
*
*
*
*
* $$NAME
NAME=HPICGAP
*
*
*
* $$VERSION
ID=3.4.0
*
*
*
* $$CALL
TYPE=PROGRM
NAME=&&&&&&&& ID=3.4.0
*
*
*
* Programmer
= P. Cobley
*
*
*
* Date
= October 17, 2002
*
*
*
* Brief Module = HPS/IMS incore global parameters
*
*
Description table used to configure the HPS/IMS
*
*
run time environment.
*
*
*
* Detailed Description =
*
* THIS CSECT GENERATES A LOAD MODULE WHICH IS USED
*
* AS A GLOBAL PARAMETER TABLE FOR ALL HPS/IMS PROGRAMS.
*
* THIS PARAMETER TABLE WILL ALLOW FOR ONSITE CUSTOMIZATION. *
*
*
* Inputs
=
*
*
*
* Outputs
=
*
*
*
* External Routines
=
*
*
*
* ASM Copy Statements =
*
*
*
* EXEC SQL INCLUDE's
= None
*
*
*
* Modification History =
*
*
*
* CHANGE ACTIVITY:
*
* SEQ RVML PI YYMMDD --- Description --------------------- *
* 022 3600 PC 930317 Program created from HPSCGAP to
*
* avoid any differences
*
*021 3600 PC 930305 Created the IMS File library names
*
* for the HPS0 references
*
* 020 3480 DC 930201 Add address of Codepage
*
* translation routine
*
*019 3480 NS 930201 Restored Correct Broadcast File Names *
*018 3400 DM 930121 Chg WXTRNs into EXTRNs, Link-Ed fail *
* if missing
*
* 017 3400 DM 921215 Match to DSECT chgs, Repos name,
*
* Nat Lang Supp
*
* 016 3400 JL 920603 Changed fields for CASIM security
*
* support
*
* 015 3400 NS 920116 Added fields for ASYNC support
*
* 014 3400 DC 910726 Added new flag to switch the user
*
* signon exit on or off.
*
*013 3400 NS 910717 Added new parameter to switch
*
* Workstation Security on or off.
*
* 012 3400 DM 910530 Add HGACONP addr of HPSCONP
*
* converse text constants CSECT.
*
* 011 3200 JAK 900912 Add HGALMGP addr of HPSLMGP
*
* message table CSECT.
*
* 010 3200 DM 900807 Split off SDS constants and Exit Code *
* in a new CSECT.
*
Planning and Installing AppBuilder for the Mainframe
page 251 of 284
* 009 3200 JAK 900711 Converse constants and exit code in *
* new CSECT.
*
* 008 3200 JDS 900715 Added HPS API Exit Area.
*
* 007 3200 MD 900522 Changed defaults as following:
*
*
NOTIFY=N,LU62SAF=N
*
* 006 3200 MD 900419 Added LU62 SAF Program Name.
*
* 005 3200 MD 900309 Added Time Interval Value for
*
* Post Wait Event*
*
Cancel Mechanism.
*
* 004 3200 DM 900213 Changed SDS Default to 'Y'.
*
* 003 3200 MD 900213 Changed HPO Defualt to 'Y' and filled *
* somefields of the Converse Global Area.
*
* 002 3200 DM 900131 Filled some of the SDS Area
*
* 001 3200 MD 900124 Added 256 Bytes Area for SDS
*
*
*
***********************************************************
EJECT
TITLE ' HPS/IMS GLOBAL PARAMETERS TABLE'
HPSCGAP CSECT
EXTRN HPSCVGP
CONVERSE GLOBAL AREA
EXTRN HPSGXIP
API GLOBAL EXIT AREA
EXTRN HPSSDSP
SDS GLOBAL AREA
10
EXTRN HPSLMGP
HPS ERROR MESSAGE ROUTE TABLE
11
EXTRN HPSCONP
HPS CONVERSE TEXT CONSTANTS
12
EXTRN HPEHL64
HPS CTRY/LANG SUPPORT TABLE
17
EXTRN HPELX10
CODEPAGE TRANSLATION ROUTINE
19
DC
CL8'HPSCGAP'
DC
CL16'&SYSDATE-&SYSTIME'
DC
CL8' V6R0M0 '
SPACE 2
HGADDR EQU *
HGCPARMA DC
A(HGCPARM)
@ OF CONFIGURATION PARAMETER AREA
HGTBLA DC
A(HGTBL)
@ OF HPS INCORE TABLES AREA
HGFILEA DC
A(HGFILE)
@ OF HPS FILES AREA
HGTDQA DC
A(HGTDQ)
@ OF HPS TDQ'S AREA
HGTSQA DC
A(HGTSQ)
@ OF HPS TSQ'S AREA
HGCONSTA DC
A(HGCONST)
@ OF HPS CONSTANTS AREA
HGACVGL DC
A(HPSCVGP)
@ OF CONVERSE GLOBAL AREA
09
HGADBUG DC
A(HGRDBUG)
@ OF DEBUG AREA
HGASDSA DC
A(HPSSDSP)
@ OF SOFTWARE DISTRIBUTION PARM 10
HGARESV DC
A(HGRESV)
@ OF FUTURE USE AREA
HGAEXIT DC
A(HPSGXIP)
@ OF HPS API EXIT AREA
09
HGALMGP DC
A(HPSLMGP)
@ HPS ERROR MESSAGE ROUTE TABLE 11
HGACONP DC
A(HPSCONP)
@ HPS CONVERSE TEXT CONSTANTS 12
HGALANG DC
A(HPEHL64)
@ HPS CTRY/LANG SUPPORT TABLE 17
HGACPTR DC
A(HPELX10)
@ HPS CODEPAGE TRANSLATION
19
HGADDRF EQU HPSCGAP+256-*
LENGTH TO PAD
DC
(HGADDRF)X'0'
PAD WITH BINARY ZEROS
ORG HPSCGAP+(((*+256-1-HPSCGAP)/256)*256) ALIGN TO X'100'
HGCPARM EQU *
TCTUAOFF DC
H'0'
TCTUA OFFSET
EXECENV DC
C'D'
EXECUTION ENVIRONMENT
DEVELOP EQU C'D'
DEVELOPMENT ENVIRONMENT
PROD
EQU C'P'
PRODUCTION ENVIRONMENT
SECURITY DC
C'N'
SECURITY ON (YES/NO)
SAF
DC
C'N'
INVOKE HPSSAF (YES/NO)
NOTIFY DC
C'N'
PHASEII NOTIFICATION (YES/NO)
STRAT62 DC
C'N'
STRATUS LU6.2 INTERFACE
HPO
DC
C'N'
HIGH PERFORMANCE OPTION(YES/NO)
CONV3270 DC
C'Y'
3270 CONVERSE SUPPORT (YES/NO)
SDS
DC
C'Y'
SOFTWARE DISTRUBUTION(YES/MO)
LU62SAF DC
C'N'
LU62 SAF ACTIVE
WKSSECR DC
C'Y'
WORKSTATION SECURITY (YES/NO)
*
CURRENTLY APPLIES ONLY TO
*
3270 CONVERSE SECURITY LOGIC
Planning and Installing AppBuilder for the Mainframe
page 252 of 284
XSECEXIT DC
ASYNC
DC
HGACSTOK DC
*
HGAHREPL DC
HGAHREPN DC
HGACTRYD DC
HGACTRYC DC
HGCPARMF EQU
DC
ORG
HGTBL
EQU
TBL1ADDR DS
TBL2ADDR DS
TBL3ADDR DS
TBL4ADDR DS
TBL5ADDR DS
TBL6ADDR DS
TBL7ADDR DS
TBL8ADDR DS
TBL9ADDR DS
TBL10ADR DS
HGTBLF EQU
DC
ORG
HGFILE EQU
HPS000D1 DS
HPS001D1 DC
HPS002D1 DC
HPS003D1 DC
HPS004D1 DC
SEC001H1 DC
SEC002H1 DC
SEC003H1 DC
HPS008D1 DC
HPSBC1D1 DC
HPSBC2D1 DC
HPS030D1 DC
HPS031D1 DC
HPS032D1 DC
HPS033D1 DC
HPS034D1 DC
HPS035D1 DC
HPS040D1 DC
HGFILEF EQU
DC
ORG
HGTDQ
EQU
HPEL
DC
HCSW
DC
HPNL
DC
HGTDQF
EQU
DC
ORG
HGTSQ
EQU
HGTSQF
EQU
DC
ORG
HGCONST EQU
APPCTERM DC
T3270
DC
POSTWAIT DC
LU62SAFN DC
HGCONSTF EQU
DC
C'N'
USER SECURITY SIGNON EXIT (Y/N)
C'Y'
ASYNCH SUPPORT (YES/NO)
C'$'
DOLLAR
THE CURRENCY SYMBOL TOKEN
17
USED TO DETERMINE HEX VALUE OF $ IN LOCAL CODE PAGE 17
C' '
HPS REPOSITORY LEVEL
17
CL8' '
HPS REPOSITORY NAME
17
H'34'
USA
HPS COUNTRY - DEFAULT
17
H'34'
USA
HPS COUNTRY - CURRENT
17
HGCPARM+256-*
LENGTH TO PAD
(HGCPARMF)X'0'
PAD WITH BINARY ZEROS
HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
*
HPS INCORE TABLES AREA
F
RULE/TRANSID TABLE 1
F
RULE/TRANSID TABLE 2
F
USRUSG/WKSNGP/BP TABLE
F
NOTIFICATION TABLE
F
USER/WRKSTN TABLE
F
CONNECTIONS/SESSIONS TABLE
F
HPS PROGRAMS TABLE
F
RESERVED
F
RESERVED
F
RESERVED
HGTBL+256-*
LENGTH TO PAD
(HGTBLF)X'0'
PAD WITH BINARY ZEROS
HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
*
HPS FILES AREA
CL8
RESERVED
CL8'HPI001D1'
VIEW DEFINITION FILE
021
CL8'HPI002D1'
TEST DATA FILE
021
CL8'HPI003D1'
RULE SOURCE FILE
021
CL8'HPI004D1'
RULE RELATIONSHIP FILE
021
CL8'SEI001H1'
MENU FILE
CL8'HPI006D1'
ERROR LOG
021
CL8'SEI003H1'
SECURITY LOG
CL8'HPI008D1'
NOTIFICATION LOG
021
CL8'HPSBC1D1'
BROADCAST MESSAGE DATA
CL8'HPSBC2D1'
BROADCAST ID TABLE
CL8'HPI030D1'
Rule Tran Relationship DB 021
CL8'HPI031D1'
Sign-On Database
021
CL8'HPI032D1'
Control Directory AllocDB 021
CL8'HPI033D1'
List Directory Database 021
CL8'HPI034D1'
Controls Extent Alloc DB 021
CL8'HPI035D1'
Object Database
021
CL8'HPI040D1'
Run Control Database
021
HGFILE+256-*
LENGTH TO PAD
(HGFILEF)X'0'
PAD WITH BINARY ZEROS
HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
*
HPS TDQS AREA
CL4'HPEL'
ERROR LOG TD QUEUE
CL4'HCSW'
SECURITY LOG TD QUEUE
CL4'HPNL'
NOTIFICATION LOG TD QUEUE
HGTDQ+256-*
LENGTH TO PAD
(HGTDQF)X'0'
PAD WITH BINARY ZEROS
HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
*
HPS TSQS AREA DC
XL256'00'
HGTSQ+256-*
LENGTH TO PAD
(HGTSQF)X'0'
PAD WITH BINARY ZEROS
HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
*
HPS CONSTANTS AREA
X'C0F0'
-APPC TERMINAL
X'91F2'
-3270 TERMINAL
PL4'5959'
-ALMOST ONE HOUR
CL8'FBCSAFZ'
-LU62 SAF PGMNAME
HGCONST+256-*
LENGTH TO PAD
(HGCONSTF)X'0'
PAD WITH BINARY ZEROS
Planning and Installing AppBuilder for the Mainframe
page 253 of 284
*
ORG
ORG
*
* Please
*
HGRDBUG
*
HGRESV
*
HPSCGAPE
,
ORG TO TOP OF AREA USED
HPSCGAP+(((*+256-1-HPSCGAP)/256)*256)
11
11
name all reserved areas with HGRxxxx here.
DC
XL256'00'
HPS DEBUG AREA
DC
XL256'00'
HPS FUTURE USE
EQU
END
*
HPSCGAP
END OF PROGRAM
08
HPICGAPJ.JCL
This sample JCL file for IMS is located in: &BASEQUAL..SVI34.SAMPLE (HPICGAPJ).
//*
PLACE JOBCARD HERE
//*----------------------------------------------------------------​
//* THIS JOBSTREAM ASSEMBLES HPICGAP INTO THE &MODQUAL..OBJ LIBRARY.
//* USE THE LINK OPTION IN THE AppBuilder HOST INSTALLATION WORKBENCH
//* TO RE-LINK HPICGAP FOR IMS.
//*----------------------------------------------------------------​
//*
//*
//*REFER TO INI FILE MEMBERS (@MVSENV AND @HPSENV) TO RESOLVE VARIABLE
//*
//* ASSEMBLE AND LINK EDIT FOR HPICGAP
//*
//ASM
EXEC PGM=IEV90,REGION=4M,
//
PARM=(NODECK,OBJECT,'SYSPARM=AppBuilder',LIST,SOURCE)
//SYSLIB
DD DSN=&MACLIB,DISP=SHR
//
DD DSN=&MODGEN,DISP=SHR
//SYSLIN
DD DSN=&MODQUAL..OBJ(HPICGAP),DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSUT1
DD SPACE=(CYL,(2,1),RLSE,CONTIG),
//
DCB=BLKSIZE=1024,UNIT=SYSDA
//SYSIN
DD DSN=&BASEQUAL..SVI531.SAMPLE(HPICGAP),
//
DISP=SHR
//*
//LKED
EXEC PGM=IEWL,REGION=4M,
//
PARM=(LIST,XREF,'AMODE=31','RMODE=ANY',NORENT,REUS),
//
COND=(4,LT,ASM)
//SYSLIB
DD DSN=&BASEQUAL..LOADIM,DISP=SHR
//
DD DSN=&BASEQUAL..LOADLIB,DISP=SHR
//
DD DSN=&SPFLINK,DISP=SHR
//SYSUT1
DD DCB=BLKSIZE=1024,
//
SPACE=(CYL,(2,1),RLSE),UNIT=SYSDA
//SYSPRINT DD SYSOUT=*
//SYSLIN
DD DSN=&BASEQUAL..LKIMUC(HPICGAP),DISP=SHR
//OBJECT
DD DSN=&MODQUAL..OBJ,DISP=SHR
//
DD DSN=&BASEQUAL..OBJ,DISP=SHR
//SYSLMOD DD DSN=&MODQUAL..LOADIM,DISP=SHR
//*------- END OF JOB TO COMPILE HPICGAP
Planning and Installing AppBuilder for the Mainframe
page 254 of 284
Planning and Installing AppBuilder for the Mainframe
page 255 of 284
Appendix E. Hardware and software checklists
Use the following checklists to verify that you have the necessary hardware and appropriate software versions
supported by AppBuilder Host Development Workbench installed at your site. Enter all values on the lines provided.
If you have versions of third-party software that differ from those listed, please contact AppBuilder’s ActionLine or
your AppBuilder account manager for information and instructions.
After completing the checklists, return all of the pages to AppBuilder Solutions by facsimile machine or return mail.
Corporate Headquarters
Magic Software Enterprises
5 Haplada Street
Or Yehuda
60218 Israel
Tel: +972 3 5389213
Fax: +972 3 5389333
www.AppBuilder.com
© 1992-2021 AppBuilder Solutions Ltd
Hardware Requirements
This section summarizes the hardware and software prerequisites and corequisites for the AppBuilder 3.4 Host
Development Workbench.
Table E-1 shows the hardware requirements for the AppBuilder 3.4 Host Development Workbench. Complete the
checklist by defining the computer system and peripherals that will be used to install AppBuilder Host Development
Workbench.
Table E-1
Hardware Requirements
Mainframe Model
IBM 3090 or equivalent
Communications
3270 SDLC communication protocol
Magnetic Media
6250 BPI (tape cartridge)
DASD Requirements
Table E-2 shows the DASD cylinder allocations for the base AppBuilder Host Development Workbench and its
optional products. The DASD cylinder allocations are based on a DASD class of 3380. Complete the checklist by
calculating the amount of DASD allocations required to install and run AppBuilder Host Development Workbench at
your site.
Note
Approximate DASD allocations for AppBuilder are derived from AppBuilder's QA testing, and limited
to specified parameters. Customers should consider their own experience, normal system usage, and
growth when determining their overall DASD requirements.
Planning and Installing AppBuilder for the Mainframe
page 256 of 284
Table E-2
DASD cylinder allocations
DASD
Allocation
AppBuilder Host Development Workbench
AppBuilder Enterprise Repository (Base)
This is the DASD requirement to install and use base AppBuilder
Host Development Workbench (Host Installation Workbench,
Enterprise Repository, and one repository version) for
approximately 6 months.
2550 cylinders (total),
comprised of: 1350 cylinders
for base software and one
repository version
980 cylinders for DB2 data
sets
220 cylinders for temporary
work data sets
DASD cylinder allocation for each additional repository version
660 cylinders per version
(includes repository software
and data for each version)
Optional products
CICS Online Preparation
70 cylinders for data sets 250
cylinders for backups
15 cylinders per repository
version
CICS 3270 Converse Preparation Workbench
5 cylinders for data sets 250
cylinders for backups
Mainframe Batch Preparation
60 cylinders for data sets 250
cylinders for backups
15 cylinders per repository
version
Mainframe Report Writer
5 cylinders for data sets 250
cylinders for backups
IMS Online Preparation
70 cylinders for data sets 250
cylinders for backups
15 cylinders per repository
version
IMS 3270 Converse Preparation Workbench
5 cylinders for data sets 250
cylinders for backups
Supported Third-party Products
The following is a summary of supported versions of operating systems, compilers, runtime libraries, and databases.
Complete the checklist with the versions of applicable software installed at your site.
Note
Planning and Installing AppBuilder for the Mainframe
page 257 of 284
Refer to Chapter 4, "Installation Requirements" for additional information about required put levels,
PTFs, and notes about optional products. For further details, contact AppBuilder’s ActionLine.
Table 5-4
Third-party Support
Versions
Installed at Your
Site
Categories
Mainframe
Operating
System
System Software
Third-party Product
Publisher
Supported
Versions for
AppBuilder 2.0.3.2
OS/390
IBM
2.9, 2.10
z/OS
IBM
1.1, 1.2, 1.3
CICS TS
IBM
1.3, 2.1, 2.2
IMS
IBM
6.0, 7.0
MQSeries
IBM
1.2
IBM
3.5
Assembler H
IBM
2.1
High Level Assembler
IBM
2.1
IBM Cobol for OS/390
IBM
2.1, 2.2
IBM Cobol for z/OS
IBM
3.1
OS PL/I
IBM
2
IBM
2
PL/I for MVS
IBM
1.1
LE Runtime OS/390
IBM
2.9, 2.10
DB2
IBM
6.1, 7.1
WebSphere Application Server for
OS/390 (Standard Edition)
Compilers and
Runtime Libraries
Visualage PL/I for OS/ 390
Database
Planning and Installing AppBuilder for the Mainframe
page 258 of 284
Appendix F. Host installation workbench customization
worksheets
Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are from the
actual installation. Enter all values which must be customized for your site on the lines provided. After completing
this worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.
Corporate Headquarters
Magic Software Enterprises
5 Haplada Street
Or Yehuda
60218 Israel
Tel: +972 3 5389213
Fax: +972 3 5389333
www.AppBuilder.com
© 1992-2021 AppBuilder Solutions Ltd
Using Customization Worksheets
Numbers in this worksheet correspond to items in Chapter 5,“The Host Installation Workbench” the installation
instructions for this product.
Note
In some cases, you may wish to use the default values provided by AppBuilder.
100.1
Installation Workbench Dataset Qualifier [Default: AB.INS34]
Enter the dataset qualifier to be used for Installation Workbench data sets at your site. This qualifier forms the basis
of all data set names used in this installation. Enter a maximum of 24 characters.
100.2
Volume Serial Number of your INS34 tape [Default: None]
Enter the six-digit volume serial number located on the label of your Installation Workbench tape.
100.3
Unit used to read your INS34 tape [Default: CART]
Enter the unit used to read your InstallationWorkbench tape.
100.4
Use Bypass Label Processing to unload tape? (Y/N) [Default: None]
Enter Y to use Bypass Label Processing and N to not use it.
100.5
DASD Unit for Installation Workbench Datasets [Default: SYSDA]
Enter the unit of the DASD containing the installation workbench data sets.
100.6
Volume for Installation Workbench Datasets (Optional) [Default: None]
Enter the volume ID for the installation workbench data sets.
100.7
DASD Unit for Temporary Datasets [Default: SYSDA]
Planning and Installing AppBuilder for the Mainframe
page 259 of 284
Enter the DASD unit for temporary data sets.
100.8
Volume for Temporary Datasets (Optional) [Default: None]
Enter the volume ID for your temporary data set.
100.9
Access Method Services Program -[Default: IDCAMS]
Enter the name of your access method services program.
100.10
Access Method Services Loadlib (Optional)[Default: None]
Enter the name of your Access Method Services Loadlib.
100.11
LE Link Library [Default:CEE.SCEELKED]
Enter the name of your LE link library.
100.12
LE Runtime Library [Default:CEE.SCEERUN]
Enter the name of your LE Runtime library.
Planning and Installing AppBuilder for the Mainframe
page 260 of 284
Appendix G. Enterprise repository customization worksheets
The following worksheet can assist you in planning how AppBuilder software will be installed at your site. All items
are from the actual installation. Enter all values which must be customized for your site on the lines provided.
After completing this worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.
Corporate Headquarters
Magic Software Enterprises
5 Haplada Street
Or Yehuda
60218 Israel
Tel: +972 3 5389213
Fax: +972 3 5389333
www.AppBuilder.com
© 1992-2021 AppBuilder Solutions Ltd
Using Customization Worksheets
Numbers in this worksheet correspond to items in Chapter 6, “Installing the Enterprise Repository” the installation
instructions for this product.
In some cases, you may wish to use the default values provided by AppBuilder.
200.1
Enter the System ID of the new system [Default:None]
Specify up to eight (8) alphanumeric characters per system name for your AppBuilder base system software. This
name will be used to associate your AppBuilder base system software to one or more AppBuilder repositories. It
must be a valid PDS member name which does not exist in the PDS
&globqual..USER.CLIST. Refer to Chapter 5, "The Host Installation Workbench" section "Repository- System
Association" for more information.
200.2
Enter Installation Dataset Qualifier [Default: AB1.INSTALL]
Enter the name of the installation data set qualifier. This must be a different qualifier than that entered for 100.1. This
qualifier defines data sets that hold the AppBuilder system and repository installation software. Enter a maximum of
17 characters.
200.3
Enter System Dataset Qualifier [Default: AB1.BASE]
Enter the name of the system data set qualifier. This qualifier defines data sets which hold the AppBuilder system
software. Enter a maximum of 17 characters.
200.4
Enter Maintenance Dataset Qualifier [Default: AB1.MOD]
Enter the name of the maintenance data set qualifier. This qualifier defines data sets which are created empty and
can be used to hold client modifications or product fixes received from AppBuilder. Enter a maximum of 17
characters.
Planning and Installing AppBuilder for the Mainframe
page 261 of 284
200.5
Enter System VSAM data set qualifier [Default: AB1.BASE]
Enter the name of the system VSAM data set qualifier. This qualifier defines VSAM data sets which are part of the
AppBuilder system software and not specific to a repository. Enter a maximum of 17 characters.
200.6
Enter Language for Messages and Panels [Default: ENG]
Enter the language code for the messages and panels. Enter ENG (English) or DB for double-byte characters
(Japanese).
200.7
Enter the AppBuilder Release Name [Default:None]
You must enter AB34.This code indicates which AppBuilder product you are installing.
200.8
Enter the Volume Serial Number of your AppBuilder tape [Default: None]
Enter the volume serial number of the AppBuilder tape. Each tape shipped by AppBuilder has a unique number. This
number can be found on the tape and in the packing list provided with the tape.
200.9
Enter the Unit used to read your AppBuilder tape [Default: CART]
Enter the name of the unit used to read your AppBuilder tape.
200.10
Use Bypass Label Processing to unload tape? (Y/N) [Default: None]
Specify Y or N to use Bypass Label Processing to unload tape.
200.11
Enter the DASD Unit for AppBuilder Datasets [Default: SYSDA]
Enter the DASD unit for AppBuilder data sets.
200.12
Enter the DASD Volume for AppBuilder Datasets (Optional) [Default:None]
Enter the DASD volume for AppBuilder data sets, if applicable.
200.13
Enter the following for VSAM data sets if they apply:
Enter either a volume or management class.
200.13a
Volume [Default: SYSDA]
Enter the volume for VSAM data sets, if applicable.
200.13b
Management class [Default: None]
Enter the management class for VSAM data sets, if applicable.
200.14
Create FB or VB Clists for SYSPROC DD? (F/V) [Default: F]
Specify if the SYSPROC DD concatenation uses F (fixed block) or V (variable block) CLISTS.
200.15
If VB, specify LRECL and BLKSIZE:
If V (variable block CLISTs)entered in step 200.14, enter the required LRECL and BLKSIZE.
200.15a
LRECL [Default: None]
Enter the record length if variable blocked CLISTs are used in step 200.14 (LRECL).
200.15b
BLKSIZE [Default: None]
Enter the block size if variable blocked CLISTS are used in step 200.14 (BLKSIZE).
200.16
LE Link Library [Default: CEE.SCEELKED]
Planning and Installing AppBuilder for the Mainframe
page 262 of 284
Enter the name of the LE Link Library.
200.17
LE Runtime Library [Default: CEE.SCEERUN]
Enter the name of the LE Runtime Library.
200.18
PL/I Math Library [Default:blank].
Enter the name of the PL/I Math Library. If you do not use a PL/I Math Library, leave it blank..
200.19
PL/I Call Library [Default: CEE.SIBMCALL]
Enter the name of the PL/I Call Library.
200.20
COBOL II Compiler Library [Default: IGY.SIGYCOMP]
Enter the name of the COBOL II Compiler Library.
200.21
Include STEPLIB in the Cobol Compile step (Y/N )? [Default: Y]
Do you want to include STEPLIB in the COBOL Compile step of rule preparation?
200.22
COBOL II Compiler Name [Default:IGYCRCTL]
Enter the name of the COBOL II Compiler.
Required Parameters
[Default:RENT,'TRUNC(BIN)',LIB]
You cannot change the required parameters.
Optional Parameters
[Default:LIST,'FLAG(W)',OPT]
You can modify the optional parameters if necessary. CPARM1 will be concatenated with CPARM2.
200.23
H Assembler Name [Default: ASMA90]
Enter the Assembler H program name.
Required Parameters
[Default: NODECK,OBJECT]
You cannot change the required parameters.
Optional Parameters
[Default: LIST]
Modify the optional parameters if necessary.
200.24
Mainframe Macro Library [Default: SYS1.MACLIB]
Enter the mainframe Macro library name.
200.25
Mainframe Distribution MGEN Library [Default: SYS1.AMODGEN ]
Enter the name of the mainframe Distribution MGEN library.
Planning and Installing AppBuilder for the Mainframe
page 263 of 284
200.26
Mainframe Target MGEN Library (Optional) [Default: SYS1.MODGEN]
Enter the name of the mainframe Target MGEN library if the IBM default name is not used.
200.27
Is the PL/I Compiler Installed? [Default: N]
Specify if the PL/I compiler is installed. Enter Y or N. If not installed, the following PL/I items are optional.
200.28
PL/I Compiler Library [Default: IBMZ.SIBMZCMP]
Enter the name of the PL/I Compiler Library.
200.29
Include STEPLIB in the PL/I Compile step? (Y/N ) [Default: Y]
Do you want to include STEPLIB in the PL/I Compile step?
200.30
PL/I Compiler Name [Default: IBMZPLI]
Enter the PL/I Compiler name. Define the required and optional parameters needed by the PL/I Compiler.
Required Parameters
[Default: INC,OP,AG,NEST,STMT,GRAPHIC,'OPTIMIZE(TIME)']
You cannot change the required parameters.
Optional Parameters
[Default: 'A(F)','X(F)',MAP,OF,STG]
You can modify the optional parameters if necessary. Optional parameters are concatenated with required
parameters.
200.31
Is the MQ Series installed? [Default: N]
200 .32 MQ Series Load Library (optional)
Enter the name of the MQ Series Load Library.
200.33
C Compiler Library [Default: CBC.SCCNCMP]
Enter the name of the C Compiler Library.
200.34
C Messages [Default: CEE.SCEEMSGP(EDCPMSGE)]
Enter the library containing the C compiler messages.
200.35
Enter the following if you will be creating C components.
Steps 200.33 thru 200.35c are optional. They are only required if C components will be written.
200.35a
200.35b
Include STEPLIB in the C compile step? (Y/N ) - [Default: Y]
C Compiler Name [ Default : CCNDRVR]
Enter the name of the C compiler.
200.35c
C Headers [Default: CEE.SCEEH.H]
Enter the library containing the C header files.
200.36
TCPIP SEZATCP Library
Planning and Installing AppBuilder for the Mainframe
page 264 of 284
200.37
TCPIP SEZACMTX Library
200.38 Sort Program [Default: SORT]
Enter the sort program name.
200.39
Access Method Program [Default: IDCAMS]
Enter name if n o t IDCAMS.
200.40
Access Method Library (optional) [Default: None]
Enter library only if access method is not IDCAMS.
200.41
PDS Utility Program [Default: IEBCOPY]
Enter the name of the PDS copy utility program if not IEBCOPY.
200.42
PDS Utility Library (optional) [Default:None]
Enter the library name only if PDS copy utility program is not IEBCOPY.
If this value is blank, you must manually edit the @MVSENV INI file and set the IEBLIB variable to
‘N/A’.
____________ 200.44 Reason Code from LISTDSI if Dataset is Not Found [Default: 5]
If a third party package translates return codes from TSO LISTDSI, specify the TSO LISTDSI equivalent. [5] is
returned by TSO LISTDSI. Used to designate the reason code from LISTDSI for data sets that are not found.
200.45
Is Dataset Archival Software such as HSM Used? (Y/N ) [Default: Y]
Specify if data set archival software is used on this system.
200.45a
Name of Program to Delete Archived Data Set [Default: HDELETE]
If “Y” entered for step 200.45, (data set archival software used) enter the name of the program used to
delete archived data sets.
200.45b
Delete Program Parameter String [Default: PURGE WAIT]
If “Y” entered for step 200.45, (data set archival software used) enter the delete program parameter
string.
200.45c
Reason Code Issued if Data Set is Migrated [Default:9]
If “Y” entered for step 200.45, (data set archival software used) enter the return code issued if the data
set is migrated.
200.46
Linkage Editor AMODE [Default: 31]
Enter the addressing mode of AppBuilder generated modules.
200.47
Linkage Editor RMODE [Default: ANY]
Enter the residency mode of AppBuilder generated modules.
Planning and Installing AppBuilder for the Mainframe
page 265 of 284
200.48
Link Pack Area Library [Default: SYS1.LPALIB]
Enter the library name of the link pack area if not SYS1.LPALIB.
200.49
DB2 Load Library [Default: DSNA11.SDSNLOAD]
Enter the name of the DB2 load library that has the DSN command processor.
200.50
DB2 Link Library [Default:DSNA11.SDSNLINK]
Enter the name of the DB2 link library that will be used to link DB2 programs.
200.51
DB2 Preprocessor Name [Default: DSNHPC]
Enter the DB2 preprocessor program name.
200.52
200.53
Include STEPLIB in the DB2 Preprocessor step? (Y/N ) [Default: Y]
DB2 Utility Proc Name [ Default: DSNUPROC ]
Enter the DB2 utility procedure name.
200.54
DB2 Utility Load Library [Default:DSNA11.SDSNLOAD]
Enter the DB2 load library that contains the load module DSNUPROC or its equivalent at your site.
200.55
ISPF Link Library [Default: ISP.ISPLOAD]
The name of the ISPF link library used to link AppBuilder ISPF modules.
ISPF library names should not be left blank.
200.56
ISPF Profile Library [Default: None]
The name of the common ISPF table library that contains member ISPPROF.
200.57
Specify Mainframe Codepage [Default: 037]
The codepage is a number assigned by IBM to designate the character set in each country. It defines which
character will be produced on a display or printer for a given byte value (0 to 255). Many of these are unvarying
across codepages, but some produce different results---for example, the value that produces a dollar sign in the US
shows as a monetary pound sign in the UK.
Specify the host codepage for your national language.
200.58
Specify PC Codepage -[Default: 437]
Enter the PC codepage used on the development workstation. 437 is default codepage for US or UK English: 850is
the MLS codepage (US and UK English, French, Spanish, Italian, German, Danish, etc.). The [NLS] Codepage_OS2
value can be found on the development workstation in \HPS\HPS.INI.
200.59
Specify AIX Codepage [Default: 2]
Enter the AIX codepage used on the development workstation: 1 - IBM-850, or 2 - IS08859-1.
200.60
PC Equivalent of ‘AT’ Character [Default: @]
If the codepage you have selected does not support the “@” character, enter the character that maps to the
equivalent host value (for example, the character EBCDIC hex 7C is mapped to on the host).
200.61
Default Language for Repository Objects (Abbreviation) [Default: ENU]
Planning and Installing AppBuilder for the Mainframe
page 266 of 284
Enter the default language abbreviation for the repository objects. For example, ENU means US English. The
following table lists valid codepage and default language combinations between mainframe, PC, and AIX, referenced
by items 200.54, 200.55, 200.56, and 200.58
200.62
Default Retrieval Format for DB2 DATE Values [Default:ISO]
Specify the retrieval format of DB2 DATE values. Valid values are EUR—IBM European Standard, ISO—
International Standards Organization, JIS—Japanese Industrial Standard, USA—IBM USA Standard or LOCAL—Site
defined.
200.63
If a LOCAL Date Format is used, enter it Here [Default: None]
Specify the DB2 date format if LOCAL specified in the previous step.This value must match the DATE format
defined when DB2 was installed at your site. Example: % Y-% 0m-% 0d--- year-month-day.
200.64
Default Retrieval Format for DB2 TIME Values [Default: ISO ]
Specify the retrieval format of DB2 TIME values. Valid values are: EUR—IBM European Standard, ISO—
International Standards Organization, JIS—Japanese Industrial Standard, USA—IBM USA Standard or LOCAL—Site
defined.
200.65
If a LOCAL Time Format is used, Enter it Here [Default: None]
Specify the DB2 date format if LOCAL specified in the previous step.This value must match the TIME format
defined when DB2 was installed at your site. Example: % 0t.% 0m.% 0s---hour.minute.second.
200.66
Maximum Nested IF statements in Rules [Default: 40]
Specify the maximum level allowed for nesting IF statements consecutively. When rules code exceeds this limit,
severe error #87959 will occur.
200.67
Retention Period for Tape Datasets in Days [Default: None]
Enter the following for HPS tape data sets. Specify the number of days tape data sets will be kept.
Retention Period in Days: number of days data sets will be kept.
200.68
CLIST Libraries [Default: None]
Enter the CLIST libraries (SYSPROC) for background TSO jobs (5 entries)
200.69
ISPF Panel Libraries [Default: ISR.ISRPLIB]
Enter the ISPF PANEL libraries (ISPPLIB) for background TSO jobs. (5 entries)
200.70
ISPMLIB [Default: None]
Enter the ISPF MESSAGE libraries used for background TSO jobs. (5 entries)
200.71
ISPSLIB [Default: None]
Enter the ISPF SKELETON libraries used for background TSO jobs. (5 entries)
200.72
ISPTLIB [Default:None]
Enter the ISPF TABLE libraries used for background TSO jobs. (5 entries)
200.73
The ISPLLIB entries are optional. Omit if not used at your site. [Default: None]
Enter the optional ISPL libraries used for background TSO jobs. (5 entries)
_
200.74
Enter the repository ID (name) of the new repository.
Planning and Installing AppBuilder for the Mainframe
page 267 of 284
Specify up to eight (8) alphanumeric characters per repository name for your AppBuilder repository software. This
name will be associated with your AppBuilder base system software which was created during the System Functions
installation. (Refer to Chapter 5, "The Host Installation Workbench" section "Repository-System Association" on
page-3 for more information.) In the example used in this document, “repname” is used as a sample repository name
and “sysname” is used as a sample system name. Panels displayed on your system will display the repository name
you have entered.
_
200.75
Enter the System ID which will be associated with the new repository [Default:
None]
The Repository ID name cannot be the same as the System ID.
200.76
DB2 Subsystem ID [Default: DSN ]
Enter the subsystem ID where AppBuilder DB2 objects will reside.
200.77
DB2 Object Creator ID [Default: <Installer’s ID>]
Enter the creator or owner ID for all AppBuilder system tables. This ID can either be the installer’s ID or a secondary
auth ID.
200.78
DB2 Plan Owner ID [Default: Installer’s ID]
Enter the DB2 Plan Owner ID. This ID can either be the installer’s ID or a secondary auth ID for the installers’ ID. For
an upgrade, this must be a different ID than INST1ADM.
200.79
AB Database Name [Default: AB34]
Enter the name of the database in which AppBuilder system DB2 objects are to reside.
200.80
DB2VCAT or Storage Group [Default: None]
Specify whether VCATs or storage groups are used. Enter V for VCAT or S for storage groups. V creates objects in
an existing storage groups and VSAM is automatically created.
200.81
DB2 Storage Group Name [Default: None]
If you chose “S” (storage group) in step 200.80, enter the storage group name of an existing storage group you want
touse.
200.82
DB2 VCAT Name [Default: None]
If you chose “V” (VCAT) in step 200.80, enter the VCAT name.
200.83
Volume ID for DB2 Tablespaces [Default: None]
If you chose VCAT in step 200.80, enter the DASD device where AppBuilder’ DB2 tablespaces are to be stored. The
same volume name can be used for DB2 tablespaces and indexspaces.
200.84
Volume ID for DB2 Indexspaces [Default: None]
If you chose VCAT in step 200.80, enter the DASD device where HPS’ DB2 indexspaces are to be stored. The same
volume name can be used for DB2 tablespaces and indexspaces.
200.85
DB2 Plan name and Collection ID for repository software [Default: None]
Enter the DB2 Plan name (also known as the Collection ID)for the repository software. There is a maximum limit of 8
characters.
200.86
Owner of Application DB2 Tables [Default: &SYSUID]
Enter the owner ID of the AppBuilder application tables.
Planning and Installing AppBuilder for the Mainframe
page 268 of 284
200.87
Repository ID [Default: None]
Enter the unique two-character alphabetical suffix used in AppBuilder short name object generation.
200.88
Number of Versions [Default: 1]
Enter the number of versions or partitions within the repository. You may define a minimum of 1 and a maximum of
10 versions per enterprise repository. Additional versions can be installed. Individual versions require additional
allocations of DASD as non-DB2 data sets must be allocated for each version.
200.89
Specify the prefix for each of these non-versioned data sets:
Enter a prefix for each of the following. The prefix entered will be used in the data set name at your site. All variables
support more than one node.
200.89a
Repository Modification [Default: AB1.REP]
Enter the repository modification data set prefix. This qualifier defines data sets which hold information
specific to a given repository. You can also use these data sets to hold software modifications which are to affect
only one repository. Enter a maximum of 18 characters.
200.89b
User Datasets [Default: AB1.USER]
Enter the user data set prefix. This qualifier defines data sets which hold user application information for
specific repository versions. Enter a maximum of 17 characters.
200.89c
VSAM User [Default: AB1.USER]
Enter the VSAM data set prefix. This qualifier defines VSAM data sets which hold user application
runtime information for CICS, IMS, and Batch. Enter a maximum of 17 characters.
200.89d
Temporary Output [Default:TEMP.NN]
Enter the temporary output data set prefix. This qualifier defines data sets that will be generated by the
user while working in the AppBuilder Enterprise Repository.May be a maximum of 10 characters, with the final node
being seven (7)characters or less since it is specific to a repository version. The repository version number is
concatenated to the final node.
Note
The &SYSUID variable is not allowedto be used as part of the prefix.
200.89e
User-ID (Short-term) [Default: &SYSUID]
Enter the prefix for output user ID data sets which are short-term, to a maximum of 18 characters. This
qualifier defines data sets that will be generated by the user while work​ ing in the AppBuilder Enterprise Repository.
This value must contain the &SYSUID variable since it is specific to each user. For example, you can specify
HPS.&SYSUID.
200.89f
User-ID (Permanent) [Default: AB1OUT]
Enter the prefix for user output data sets that are permanent or long-term. This qualifier defines data
sets that will be generated by the user while working in the AppBuilder Enterprise Repository. May be a maximum of
10 characters.
Note
The &SYSUID variable is not allowed to be used as part of the prefix.
200.90
Should VIEW Copybooks Include Alignment Bytes? (Y/N) [Default: N ]
Specify if VIEW copybooks should include alignment bytes.
200.91
Permanent data sets
Enter the following information for permanent data sets.
Planning and Installing AppBuilder for the Mainframe
page 269 of 284
200.91a
Unit [Default: SYSDA]
Enter the name of the direct access storage device that will store AppBuilder permanent data sets.
200.91b
Volume ID Required? [Default: N ]
If pool DASD is used (that is, JCL parameter VOL=SER is not used), then enter N and leave Permanent
Volume ID blank. Otherwise, enter Y and a volume ID.
200.91c
Volume ID
Enter the Volume ID.
200.92
Temporary data sets
Enter the following information for temporary data sets.
200.92a
Unit [Default: SYSDA]
Enter the name of the direct access storage device that will store AppBuilder temporary data sets.
200.92b
Volume ID Required? [Default: N]
If pool DASD is used (JCL parameter VOL=SER not used), enter N and leave Tempo​ rary Volume ID
blank. If DASD must be specified, enter Y and a volume ID.
200.92c
Volume ID [Default: None]
Enter the Volume ID.
200.93
VIO data sets
Enter the following information for VIO data sets.
200.93a
Unit [Default: SYSDA]
Enter the name of the direct access storage device that will store AppBuilder VIO data sets.
200.93b
Volume ID Required? [Default: N]
If pool DASD is used (that is, JCL parameter VOL=SER is n o t used), then enter N and leave VIO
Volume ID blank. If DASD must be specified, then enter Y and a Volume ID.
200.93c
Volume ID [Default: None]
Enter the Volume ID.
200.94
Job Class (CLASS) [Default: 1]
Enter the JCL Job Class used for user-submitted jobs through the repository interface.
200.95
Message Class (MSGCLASS) [Default: A]
Enter the JCL Message Class used for user-submitted jobs through the repository interface.
200.96
Time Parameter (TIM E) [Default: None]
Enter the JCL time parameter if required for the job card.
200.97
Priority (PRTY) [Default: 12]
Enter the JCL priority parameter if required for the job card.
200.98
Region size (REGION ) [Default: 4M ]
Planning and Installing AppBuilder for the Mainframe
page 270 of 284
Enter the JCL region size parameter if more than 4M is required.
200.99
Default Jobname Suffix Character [Default: M ]
Enter a default JCL suffix character.
200.100 Default Job Description [Default: JO B]
Enter a default job description for AppBuilder jobs.
200.101 Overnight Job Class [Default: 1]
Enter the job class used to defer jobs for overnight execution.
200.102 SYSOUT Class for Batch Jobs [Default: *]
Enter SYSOUT class for batch job processing and batch reports.
200.103 Internal Reader Name [Default: INTRDR]
Enter the name of the internal reader if different from the default name.
200.104 Internal Reader Output Class [Default:1]
Enter the output class for the internal reader.
200.105 Default Printer [Default: None]
Enter default printer ID to be used for printing reports.
200.106 Use Customized Job Card Skeleton [Default:N]
Specify Y or N to use a customized job skeleton.
200.107 Batch JOB Submission Option [Default: Y]
Specify Y to submit jobs automatically or N to save jobs in a data set.
The JCL will be saved in data set &USRVQUAL..JCL. To override this, you must specify the fully
qualifieddata set name in the INI variable called JCLDSN in &REPQUAL..INI(@HPSENV). Y or N
for an external scheduling interface.
200.108 Is there an External Scheduling Interface? [Default: N]
Enter the default value only.
200.109 Include the STEPLIB DD in batch jobs?
Specify Y or N if the STEPLIB DD should be included in batch jobs.
200.110 Include the STEPLIB DD in non-DB2 steps?
Specify Y or N if the STEPLIB DD should be included in non-DB2 steps.
200.111 Include each of the following in STEPLIB:
Specify with Y or N whether to include each of the following in STEPLIB. TSODD is a batch job skeleton.
200.111a DB2 Load Libraries [Default: Y]
Specify if the DB2 load libraries should be in the STEPLIB of TSODD.
Planning and Installing AppBuilder for the Mainframe
page 271 of 284
200.111b MODQUAL Load Library [Default: Y]
Specify if the AppBuilder modification load libraries should be in the STEPLIB of TSODD.
200.112 Specify the CICS or IMS Transaction ID Option:
Specify the following option, as appropriate. The following are valid values: S-Use Source ID, T-Use Target ID, BBlank.
200.112a CICS [Default: T]
Specify the CICS transaction ID option.
200.112b IMS [Default: T]
Specify the IMS transaction ID option.
200.113 Default Migration Dataset High Level Qualifier [Default: HPSOUT]
Enter the default migration data set high level qualifier. May be a maximum of 8 characters.
200.114 Analyze Collisions During Import? (Y/N ) [Default: Y]
Specify if collisions are analyzed during import.
200.115 Analyze Collisions on SYSTEMID or LONGNAME? (S/L) [Default: L]
Specify if collisions are analyzed on SYTEMID or LONGNAME.
200.116 Process User Exits During Migration? (Y/N) [Default: N]
Specify if user exits are processed during migration.
200.116a If ‘Y’ Enter Name of Optional Exit Rexx Exec [Default: None]
If “Y” entered for 200.116a, enter the name of the exit REXX.
200.117 For each of the following enter Y to include the item in a migration or N to exclude
it from migration:
Enter Y or N for the following
200.117a Default Option for ‘Create’ Entities (Y/N ) [Default: Y]
Specify Y or N to allow default option for ‘Create’ entities.
200.117b Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the ‘Create’ entities option. ‘
200.117c Default Option for ‘Update’ Entities (Y/N) [Default: Y]
Specify Y or N to allow default option for ‘Update’ entities.
200.117d Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the ‘Update’ entities option.
200.117e Default Option for ‘Delete’ Entities (Y/N) [Default: Y]
Specify Y or N to allow default option for ‘Delete’ entities.
200.117f Can the User Modify this Option? (Y/N) [Default: N ]
Planning and Installing AppBuilder for the Mainframe
page 272 of 284
Specify Y or N whether the user can modify the ‘Delete’ entities option.
200.117g Default Option for Source (Y/N) [Default: Y]
Specify Y or N to allow default option for Source.
200.117h Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the Source option.
200.117i Default Option for Keywords (Y/N ) [Default:Y]
Specify Y or N to allow default option for Keywords.
200.117j Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the Keywords option.
200.117k Default Option for Text (Y/N) [Default: Y]
Specify Y or N to allow default option for Text.
200.117l Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the Text option.
200.118 Enter Y to include the following steps in MIGRATE method processing or N to
exclude them:
Enter Y or N for the following.
200.118a Include IMPORT Step? (Y/N) [Default: N]
Specify Y or N to include the IMPORT step.
200.118b Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the include IMPORT step option.
200.118c Include REBUILD Analyzer? (Y/N) [Default: N]
Specify Y or N to include the REBUILD Analyzer.
200.118d Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the include REBUILD Analyzer option.
200.118e Include REBUILD Prepare? (Y/N ) [Default: Y]
Specify Y or N to include the REBUILD Prepare.
200.118f Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the include REBUILD Prepare option.
200.118g Include REBUILD Install? (Y/N ) [Default: Y]
Specify Y or N to include the REBUILD Install.
200.118h Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the include REBUILD Install option.
200.118i Include REBUILD Export? (Y/N) [Default:N]
Planning and Installing AppBuilder for the Mainframe
page 273 of 284
Specify Y or N to include the REBUILD Export.
200.118j Can the User Modify this Option? (Y/N) [Default: N ]
Specify Y or N whether the user can modify the include REBUILD Export option.
200.119 Application DB2 environment
200.119a SupportDB2 Packages? (V/N/P) [Default: N]
Specify V or P to support DB2 packages. N indicates that packages are not supported. V indicates DB2
packages will be supported for all the projects within a repository version. P indicates DB2 packages will be
supported per project within a repository version. Please refer to the Managing Enterprise Repositories manual for
more information on DB2 package support.
200.119b If V or P, specify Collection ID [Default:None]
If using packages, specify the default Collection ID for this repository version.
200.119c If V or P, specify Owner ID [Default: None]
If using packages, specify the default Owner ID for this repository version.
200.119d If V or P, specify Qualifier ID [Default: None]
If using packages, specify the default Qualifier ID for this repository version.
200.119e If V or P, specify Plan Name [Default: None]
If using packages, specify the default Plan Name for this repository version.
200.119f If V or P,specify E if a Package List is Required or W if the Wildcard
(*) is Supported (E/W) [Default: W]
If you use Packages, specify E to require an explicit package list or specify W to support the asterisk
(*) for wildcards for this repository version.
200.119g Perform GRANT as part of Prepare Method? (Y/N ) [Default: Y]
Specify Y or N to perform GRANT as a part of the Prepare method.
200.119h Use Configuration Units for Preparation? (Y/N) [Default: N ]
Specify Y or N to use configuration units for preparation.
200.120 Optional User Libraries for Component Prepares
Enter the following library names.
200.120a NCAL Batch Library [Default: None]
Define the NCAL batch library.
200.120b NCAL CICS Library [Default: None]
Define the NCAL CICS library.
200.120c NCAL IMS Library [Default: None]
Define the NCAL IMS library.
200.120d Other NCAL Library [Default: None]
Planning and Installing AppBuilder for the Mainframe
page 274 of 284
Define the other NCAL batch library.
200.120e Batch Load Library [Default: None]
Define the batch load library.
200.120f CICS Load Library [Default:None]
Define the CICS load library.
200.120g IMS Load Library [Default: None]
Define the IMS load library.
200.120h Other Load Library [Default:None]
Define the other load library.
200.120i ASM Copylib [Default: None]
Define the ASM copylib.
200.120j COBOL Copylib [Default: None]
Define the COBOL copylib.
200.120k C Copylib [Default: None]
Define the C language copylib.
200.120l PL/I Copylib [Default: None]
Define the PL/I copylib.
200.120m ASM DCLGEN [Default: None]
Define the ASM DCLGEN.
200.120n COBOL DCLGEN [Default:None]
Define the COBOL DCLGEN.
200.120o C DCLGEN [Default:None]
Define the C Language DCLGEN
200.120p PL/I DCLGEN [Default: None]
Define the PL/I DCLGEN.
Planning and Installing AppBuilder for the Mainframe
page 275 of 284
Appendix H. Batch preparation workbench customization
worksheets
Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are from the
actual installation. Enter all values which must be customized for your site on the lines provided.After completing the
worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.
Corporate Headquarters
Magic Software Enterprises
5 Haplada Street
Or Yehuda
60218 Israel
Tel: +972 3 5389213
Fax: +972 3 5389333
www.AppBuilder.com
© 1992-2021 AppBuilder Solutions Ltd
Using Customization Worksheets
Numbers in this worksheet correspond to items in Chapter 7, “Installing Batch Preparation Workbench” the
installation instructions for this product.
Note
In some cases, you may wish to use the default values provided by AppBuilder.
300.1
Plan name prefix or suffix - [Default: B]
You can form DB2 plan names by using the generated bitmap as the plan name prefix or suffix. Enter B as the prefix
or P to use the bitmap as the suffix.
300.2
Use AppBuilder Project name in Batch plan name? (Y/N ) - [Default: N]
Enter Y or N to specify if you want to use the AppBuilder project name in the Batch plan name.
300.3
If not, enter the string to use here: - [Default: PLNB]
If you specified N above, enter the string you want to use for the Batch plan name.
300.4
Use the repository version number in plan name (Y/N ) - [Default: N]
Enter Y or N to specify if you want to use the repository version number in the Batch plan name.
Planning and Installing AppBuilder for the Mainframe
page 276 of 284
Appendix I. CICS online preparation workbench and enterprise
server customization worksheets
Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are from the
actual installation. Enter all values which must be customized for your site on the lines provided.After completing the
worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.
Corporate Headquarters
Magic Software Enterprises
5 Haplada Street
Or Yehuda
60218 Israel
Tel: +972 3 5389213
Fax: +972 3 5389333
www.AppBuilder.com
© 1992-2021 AppBuilder Solutions Ltd
Using Customization Worksheets
Numbers in this worksheet correspond to items in the installation instructions for this product described in Chapter 9,
"Installing CICS Online Preparation Workbench and Enterprise Server".
Note
In some cases, you may wish to use the default values provided by AppBuilder.
400.1
CICS Runtime Library - [Default: CICSTS51.CICS.SDFHLOAD]
Enter the name of the CICS runtime library used to link AppBuilder modules.
400.2
Runtime Dataset Name Suffixes:
Enter the runtime data set name suffix.
400.3
Load Library Output - [Default: LOADCI]
Enter the load library output suffix, to a maximum of eight (8) characters.
400.4
NCAL Library Output - [Default: NCALCI]
Enter the NCAL library output suffix, to a maximum of eight (8) characters.
400.5
VSAM View Definition File - [Default: HPS001D1.VIEWDEF]
Enter the VSAM view definition file suffix.
400.6
VSAM Rule Source Output - [Default: HPS003D1.RULESRC]
Planning and Installing AppBuilder for the Mainframe
page 277 of 284
Enter the VSAM rule source output suffix.
400.7
VSAM Rule Relation Output - [Default:HPS004D1.RLRELATN]
Enter the VSAM rule relation output suffix.
400.8
VSAM View Definition (PCNV) - [Default: HPS021D1.VIDTEXT]
Enter the VSAM view definition output suffix.
400.9
Runtime Dataset DDNAMES:
Enter the following DDNAMEs.
400.10
VSAM View Definition File - [Default: HPS001D1]
Enter the DDNAME for the VSAM view definition file.
400.11
VSAM Rule Source Output - [Default: HPS003D1]
Enter the DDNAME for the VSAM rule source output.
400.12
VSAM Rule Relation Output - [Default: HPS004D1]
Enter the DDNAME for the VSAM rule relation output.
400.13
VSAM View Definition (PCNV) - [Default: HPS021D1]
Enter the DDNAME for the VSAM view definition file.
400.14
CICS Runtime Library - [Default: CICS33.LOADLIB]
Enter the CICS runtime library name at your site.
400.15
CICS Macro Library - [Default: CICS.MACLIB]
Enter the CICS macro library name at your site.
400.16
CICS PL/I Library - [Default: CICS.PLILIB]
Enter the PL/I library name at your site.
400.17
CICS COBOL Library - [Default: CICS.COBLIB]
Enter the CICS COBOL library name at your site.
400.18
CICS ASM Translator - [Default: DFHEAP1$]
Enter the CICS ASM translator name at your site.
400.19
CICS PL/I Translator - [Default: DFHEPP1$]
Enter the CICS PL/I translator name at your site.
400.20
CICS COBO L Translator - [Default: DFHECP1$]
Enter the CICS COBOL translator name at your site.
400.21
CICS C370 Translator - [Default: DFHEDP1$]
Enter the CICS 3270 translator library name at your site.
400.22
Use AB/CICS Autoinstall? (Y/N )
Planning and Installing AppBuilder for the Mainframe
page 278 of 284
If Y is entered, AppBuilder software automatically makes the program definitions in the CICS region available during
preparation of user rulesand components.Itwill also process AppBuilder user VSAM files and update the AppBuilder
incore table with the rule and its associated trans ID.
400.23
CEDA Transaction Name - [Default: CEDA]
Enter the CEDA transaction name used at your site.
400.24
CEMT Transaction Name - [Default: CEMT]
Enter the CEMT transaction name used at your site.
400.25
CICS Version - [Default: 4]
Enter the CICS version number used at your site.
400.26
CICS Release - [Default: 4]
Enter the CICS release number used at your site.
400.27 You may form CICS DB2 plan names by using the generated bitmap as the plan
name prefix or suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default: B]
Specify how the generated bitmap is used in the CICS DB2 plan name.
400.28
Use AppBuilder Project name in CICS plan name? (Y/N ) - [Default: N]
Specify if the AppBuilder project name is used in the CICS plan name.
400.29
If not, enter the string to use here: - [Default: PLNC]
If the AppBuilder project name is not used in the CICS plan name, enter the name to use.
400.30
Use the repository version number in plan name? (Y/N ): - [Default:N]
Specify if the repository version number is used in the plan name.
400.31
Use the region type (‘C’) in the plan name? (Y/N ) - [Default: N]
Specify if the region type is used in the plan name.
400.32
INTERTEST (Supply these values if INTERTEST is installed):
Enter the following if INTERTEST debugging feature is installed in this region.
400.33
Intertest ASM Program - [Default: IN25SYMA]
Enter the ASM program name.
400.34
Intertest COBOL Program - [Default: IN25COB2]
Enter the COBOL program name.
400.35
Intertest PL/I Program - [Default: IN25SYMP]
Enter the PL/I program name.
400.36
Intertest PROTSYM Dataset - [Default: None]
Enter the PROTSYM data set name.
400.37
Intertest STEPLIB - [Default: None]
Enter the STEPLIB program name.
Planning and Installing AppBuilder for the Mainframe
page 279 of 284
400.38
Minimum Transaction ID for this Version: - [Default: AAAA]
Enter the minimum transaction ID for this version.
400.39
Maximum Transaction ID for this Version: - [Default: AA99]
Enter the maximum transaction ID for this version.
400.40
Number of CICS Regions you want to configure for version 1 - [Default: None]
Enter the number of CICS regions you want to configure for repository version 1.
400.41
Enter the VTAM name of this region - [Default:None]
Enter the VTAM name of this region.
• Enter the VTAM APPLID’s for LU2 processing:
1 - [Default: A06HPS1]
2 - [Default: A06HPS2]
3 - [Default: A06HPS3]
The AppBuilder LU2 CICS Auto-install feature allows AppBuilder objects (rules, components, etc.) to be
automatically defined to CICS during AppBuilder preparation (compile, linkedit, etc.). Depending on the object being
prepared, it will connect to CICS via the VTAM applids and execute the following transactions:
• HS96 - AppBuilder newcopy transaction
• CEDA - CICS transaction to define AppBuilder objects
• CEMT - CICS transaction to close and open AppBuilder VSAM files
• UTBL - AppBuilder transaction to add rule/tranid to AppBuilder incore table2 (HPSTBLE2)
Enter three VTAM application IDs.
400.42
Define AB CICS group to the startup group list? (Y/N ) - [Default: N]
Specify whether the AppBuilder CICS groups should be defined to the startup group list during a rule or component
prepare.
400.43
Define AB transactions during rule prepare? (Y/N) - [Default: Y]
Specify if transactions are defined during a rule prepare.
400.44
Should the AB transaction UTBL be executed? (Y/N) - [Default: Y]
Specify if the UTBL transaction should be executed during a rule prepare.
400.45
Enter the startup group list name for HPS groups - [Default: None]
Enter the startup group list name for AppBuilder groups.
400.46 AB groups will be added to the startup list AFTER or BEFORE a specified group.
Enter the specified group name here. - [Default:None]
Enter the specified group name.
400.47
Enter A to add new groups AFTER this group or B for BEFORE - [Default: B]
Specify where the AppBuilder group will be added to the group named above.
Planning and Installing AppBuilder for the Mainframe
page 280 of 284
400.48 Temporary groups will be built from a one-character prefix and the Userid.
Specify the one​ character prefix for temporary groups - [Default: H]
Enter a one character prefix for temporary groups.
400.49 CICS group names for AB objects may be a constant string O R a constant string
combined with the HPS project name. The combined length may not exceed 8 characters.
If you use the project name in the group name, enter H if the HPS project should come first or C if the constant
string should come first - [Default: H]
400.50
For PPTs:
Enter the following information for PPTs.
400.51
Use AB project name as part of the group name? (Y/N ) - [Default: Y]
Specify if the AppBuilder project name is used as part of the group name.
400.52
Enter the optional string to use in the group name - [Default: HPS]
Enter an optional string to use in the group name.
400.53
For PCTs:
Enter the following information for PCTs.
400.54
Use AB project name as part of the group name? (Y/N ) - [Default: Y]
Specify if the AppBuilder project name is used as part of the groupname.
400.55
Enter the optional string to use in the group name - [Default:ABGRP]
Enter an optional string to use in the group name.
Planning and Installing AppBuilder for the Mainframe
page 281 of 284
Appendix J. IMS online preparation workbench and enterprise
server customization worksheets
Use the following worksheet to plan how AppBuilder software will be installed at your site. All items are from the
actual installation. Enter all values which must be customized for your site on the lines provided. After completing
this worksheet, return all of the pages to AppBuilder by either facsimile machine or return mail.
Corporate Headquarters
Magic Software Enterprises
5 Haplada Street
Or Yehuda
60218 Israel
Tel: +972 3 5389213
Fax: +972 3 5389333
www.AppBuilder.com
© 1992-2021 AppBuilder Solutions Ltd
Using Customization Worksheets
Numbers in this worksheet correspond to items in the installation instructions for this product described in Chapter
10,"Installing IMS Online Preparation Workbench and Enterprise Server".
Note
In some cases, you may wish to use the default values provided by AppBuilder.
600.1
IMS RESLIB -[Default: SYS1.RESLIB]
Enter the qualified name of the IMS resident library used to link AppBuilder modules.
600.2
IMS CSSLIB - [Default: SYS1.CSSLIB]
Enter the qualified name of the CSS library used to link AppBuilder modules to support LU6.2 processing for
AppBuilder’s NetEssential middleware.
600.3
Runtime Dataset Name Suffixes:
Complete the following values.
600.4
Load Library Output - [Default: LOADIM ]
Enter the name of the suffix for the Load Library Output data sets for IMS.
600.5
NCAL Library Output - [Default: NCALIM ]
Enter the name of the suffix for the NCAL Library Output data sets for IMS.
600.6
VSAM View Definition File - [Default: HPI001D1.VIEWDEF]
Planning and Installing AppBuilder for the Mainframe
page 282 of 284
Enter the name of the suffix for the VSAM View Definition File data sets for IMS.
600.7
VSAM Rule Source Output - [Default: HPI003D1.RULESRC]
Enter the name of the suffix for the VSAM Rule Source Output file for IMS.
600.8
VSAM Rule Relation Output - [Default:HPI004D1.RLRELATN ]
Enter the name of the suffix for the VSAM Rule Relation Output file for IMS
600.9
Specify the Jobname for IMS Control Region - [Default: None]
Enter the jobname for the IMS Control Region at your site.
600.10 Specify the dataset name which contains the IMS VSAM Buffer Cards - [Default:
SS0216.SVI531.SAMPLE(DFSVSM )]
600.11 You may form IMS DB2 plan names by using the generated bitmap as the plan
name prefix or suffix. Enter B to use the bitmap as the prefix or P to use the bitmap as the suffix - [Default: P]
Enter the default value to use the bitmap as a suffix.
600.12 Use AppBuilder Project name in IMS plan name? (Y/N ) - [Default: Y]
Enter the default value to use the AppBuilder project name in the IMS plan name.
600.13 If not, enter the string to use here: - [Default: HP]
Enter the default value only.
600.14 Use the repository version number in plan name? (Y/N ): - [Default: Y]
Enter the default value to use the repository version number in the plan name.
600.15 Use the region type (‘M’) in the plan name? (Y/N ) - [Default:Y]
Enter the default value to use the region type M in the plan name.
600.16 Should a separate plan be generated for Batch Rules (Y/N ) - [Default: N]
If you want to generate a separate plan for Batch Rules, enter Y. If not, enter N.
600.17 Use AB/IMS Autoinstall? (Y/N ) - [Default: none]
If you want to use HPS/IMS Autoinstall, enter Y. If not, enter N. This feature is a batch interface that automatically
connects to IMS to open and close AppBuilder databases and to update the HPS incore table with the AppBuilder
IMS rule and transaction ID.
600.18 IMS General Library Names:
600.19 General IMS Lib Prefix - [Default: IMS410.VENDOR]
Enter the name of your general IMS library prefix.
600.20 IMS VTAM ID - [Default: IMS41]
Enter the VTAM applid for this IMS system.
600.21 IMS Region name - [Default: IMSB]
Enter the IMS system name.
600.22 IMS MACLIB Library - [Default: SYS1.IMS.MACLIB]
Planning and Installing AppBuilder for the Mainframe
page 283 of 284
Enter the name of your IMS Macro library (MACLIB).
600.23 IMS Res Library - [Default: IMS410.VENDOR.RESLIB]
Enter the name of your IMS Resident Library (Res Library).
600.24 IMS AGN name - [Default: none]
Enter the AGN (Application Group Name) value if AGNs are used at your site.
600.25 IMS Long Message - [Default: IMS.LGMSG]
Enter any fully qualified data set name used by the IMS Control Region. This library is used to determine if IMS is up
before submitting AppBuilder BMP jobs.
600.26 Maximum Transaction ID for this Version: - [Default: none]
Currently this value is set by a AppBuilder internal program for IMS transactions.
600.27 Number of IMS Regions you want to configure for this version - [Default: none]
Please use the default value.
600.28 Enter the VTAM APPLIDs for LU2 processing:
If you specified Y for item 600.17, then you must enter the names of the three VTAM APPLIDs for LU2 processing.
600.29 1 - [Default: A06HPS1]
Specify the name of the first VTAM APPLID.
600.30 2 - [Default: A06HPS2]
Specify the name of the second VTAM APPLID.
600.31 3 - [Default: A06HPS3]
Specify the name of the third VTAM APPLID.
600.32 Define ab transactions during rule prepare? (Y/N) - [Default: Y]
Enter the default value to define AppBuilder transactions during rule prepare.
600.33 Should the AB databases be processed? (Y/N) - [Default: Y]
If you want the AppBuilder databases to be processed (used to populate RuleView), enter Y. If not, enter N.
600.34 Should the AB transaction UTBL0000 be executed? - [Default: Y]
If you want the AppBuilder transaction UTBL0000 to be executed, enter Y. If not, enter N.
Planning and Installing AppBuilder for the Mainframe
page 284 of 284