Submit a Request | Phoenix Software International

PHX-BDT Request Worksheet

Use this worksheet to submit information for your PHX-BDT request.

On the next page, please complete the following:

PHX-BDT CPC Configuration Report
Upload most recent twelve months of SCRT reports to confirm capacity and consumption (if eligible for sub-capacity pricing).

The form has some errors. Please correct and resubmit.

* Required

Your Name (Submitter)*

Your Email (Submitter)*

Email address is invalid. Please re-enter.

Enter a valid email address.

Your Phone (Submitter)*

Company Name*

Customer Number

Enter your Phoenix Software customer number if applicable.

Billing Address*

Procurement Contact*

Procurement Contact Email*

Email address is invalid. Please re-enter.

Enter a valid email address.

Email (alternative):

Procurement Contact Phone*

Technical Contact*

Technical Contact Email*

Email address is invalid. Please re-enter.

Enter a valid email address.

Technical Contact Phone*

IBM ELA or Other Discounts

Discount Designation	Discount Amount

Current IBM BDT cost

JES System*

Components

File to File (JES2 and JES3/JES3^plus)

SNA/NJE (JES3/JES3^plus)

Please check at least one.

Preferred request start date

Coterminous Renewal

If you have other Phoenix Software products, indicate if you would like a coterminous renewal for all products.

Yes

Additional Information

Indicate any special information you want to make us aware of.

The form has some errors. Please correct and resubmit.

Phoenix Software Develops State-of-the-Art Products for Modern Enterprises

Pricing Pledge

PHX-BDT is fully supported, and can be implemented by existing IBM BDT customers through a trivial migration and at no additional cost.
Initial contract cost will closely match what customers are currently paying for IBM BDT.
Any subsequent price increases will not exceed the percentage price increases implemented by IBM.
Annual licensing in place of MLC.

What is PHX-BDT?

PHX-BDT lets you transfer data from one computer system to another. The type of data that it transfers depends on which of its features is installed:

The File-to-File feature allows users at one z/OS JES2 or z/OS JES3/JES3^plus system in a SNA network to copy data sets to or from another system in the network.
The SNA NJE feature allows z/OS JES3 users to transmit jobs, output (SYSOUT), commands, and messages from one computer system to another within a SNA network.

Use these tables to list all CPCs where PHX-BDT will be installed.

The form has some errors. Please correct and resubmit.

At least one site is required.

Site	CPC Physical Location Street Address	City	State/Province	Zip/Postal Code	Country

At least one CPC is required.

Please select a product to enter CPC information.

									% of Capacity Considered:
Site	CPC Serial# (last 5)	CPC Type	SW Model #	DR Only?	System	MSUs	JES	Eligible for Sub-Capacity Pricing w/IBM?	Traditional Workload	zNALC Workload	Eligible for Capacity Pricing?	As of (date)	Change Status

MSU Aggregation for Actively Coupled Systems (IBM PricingPlex) Eligibility

If applicable, indicate CPCs eligible for aggregation w/IBM as part of an IBM PricingPlex. Select coupled CPCs by clicking the choices under a PricingPlex column (see below for qualification information).

CPC	PricingPlex A	PricingPlex B	PricingPlex C	PricingPlex D	PricingPlex E
CPCs

Aggregate Pricing Qualification Information

For z/OS^® systems, you can sometimes aggregate MSUs associated with a sub-capacity eligible product across a Parallel Sysplex^®. Aggregation means when you run the sub-capacity eligible product in multiple LPARs on CPCs which are all part of the same Parallel Sysplex, you pay the base charge for the product only once. The values shown on the sub-capacity report are not affected by aggregation, but IBM^® adds up all the MSUs for aggregated products across each CPC in the sysplex when calculating your charges for those products. For aggregation, the Parallel Sysplex must meet the following requirements:

All CPCs in the Parallel Sysplex must be physically attached via coupling links to a common coupling facility and via timer links to a common external time reference (such as the Sysplex Timer).
Images in the sysplex must account for 50 percent of the total MVS™ workload on each machine during prime business hours. In other words, MVS-based LPARs participating in the sysplex must represent at least half of the CPC’s MVS-based processing capability.
All images in the sysplex must have at least one common systems enablement function activated to use the coupling facility. For a list of system enablement functions, see z/OS systems enablement functions.

At least one of these common systems enablement functions must be activated on all images in a sysplex for the software on that sysplex to participate in a pricing aggregation.

Application Data Sharing
GRS Star Implementation
JES2 Checkpoint in the Coupling Facility
RACF^® database caching
SmartBatch multisystem processing
VTAM^® Generic Resources

VTAM MULTINODE Persistent Sessions
Automated tape sharing and switching
System logger SYSLOG (OPERLOG)
System logger LOGREC
System logger Resource Recovery Services

IBM allows monthly software licenses to be aggregated across a qualified Parallel Sysplex. Use the document below to review the hardware, software, operation and verification criteria to be considered “actively coupled.”

Sysplex Calculator (PlexCalc): https://www.ibm.com/downloads/cas/0NKRYJ29
Pricing Tools: https://www.ibm.com/it-infrastructure/z/software/pricing-tools
Aggregated Sysplex Pricing: https://www.ibm.com/downloads/cas/MELGBJPZ

Please upload the most recent 12 months of SCRT reports for all applicable CPCs.
Accepted file types are CSV (.csv), Excel (.xls, .xlsx), text (.txt, .csv) and zip (.zip), up to 5 MB.

Drag & drop one or more SCRT files here

Browse

Invalid files were not added.

The form has some errors. Please correct and resubmit.