This document outlines the required hardware
and software for VisualAge PL/I, the software you need for the components of
VisualAge PL/I you choose to install, and the software you need for the
products you want to operate with VisualAge PL/I.
This section provides hardware requirements for VisualAge PL/I
for Windows, Refresh V2.1.10.
Processor
Pentium-based 100MHz processor (minimum) or higher (recommended)
Memory
128 MB or higher
Hard drive space
- Basic installation: 400 MB
- Swap space: 128 MB
All hard drive space estimates are for the full product. You can reduce the space required by selectively installing components.
InstallShield displays the amount of hard drive space required for the
components you select.
Adapter card
For host communications, LAN adapter card supported by Windows
RELATED REFERENCES
Required software
Optional software
This section provides the minimum software required for VisualAge PL/I for
Windows, Refresh V2.1.10.
For remote edit-compile-debug
On the OS/390 host
- OS/390 Version 2 Release 6 or later, or z/OS, which includes the following required
software:
- TCP/IP
- IBM HTTP Server (formerly known as Domino Go Webserver for OS/390),
plus the appropriate PTF for APAR PQ29311
- For job monitor support, the PTF for JES APAR 0W41734
- For JES3 support, the PTF for APAR OW36022
and the PTF for APAR OW45210
- OS/390 Language Environment. Apply the PTFs for the
following APARs as appropriate:
PQ088138, PQ05057, and PQ07402 for OS/390 V2R5; remote debug of programs with DBCS data
requires OS/390 Language Environment V2R9.
- For Remote-Edit-Compile Only:
- OS/390 Version 2 Release 6 or later
- IBM PL/I for MVS & VM Version 1 Release 1 Full Function Offering
(5688-235), including the remote edit-compile component.
In addition, apply the PTFs for the following APARs:
- PTF UQ37265 (APAR PQ32582) (TSO Command Server)
- For Remote-Edit-Compile-Debug
:
- Using IBM Enterprise PL/I for z/OS and OS/390 Version 3 Release 1 Full Function Offering
(5655-H31) (when available), including the remote edit-compile-debug component and Debug Tool:
- OS/390 Version 2 Release 10 or later or z/OS Version 1 Release 1 or later
- In addition, apply the PTFs for the following APARs:
- The PTFs for APAR PQ40768 (Remote Debug)
- The PTFs for APARs PQ33668 and PQ37039 (Debug Tool)
- Using IBM VisualAge PL/I for OS/390 Version 2 Release 2 Full Function Offering
(5655-B22), including the remote edit-compile-debug component and Debug Tool:
- OS/390 Version 2 Release 7 or later
- In addition, apply the PTFs for the following APARs:
- The PTFs for APAR PQ40768 (Remote Debug)
- The PTFs for APARs PQ33668 and PQ37039 (Debug Tool)
- Note: Full Function offerings include the Debug Tool. Only one Full Function offering is
required for debugging applications written in any of the debug tool supported languages.
You may use either the Enterprise PL/I for z/OS and OS/390 V3R1 Alternate Function or
the VisualAge PL/I for OS/390 V2R2 Alternate Function products for
remote debug as long as you have one Full Function offering of one of the other debug tool
supported languages.
On the Windows workstation
- IBM VisualAge PL/I for Windows, Refresh V2.1.10 (5801-AAR)
- Microsoft Windows NT** Version 4.0 (Service Pack 4 or later is required) or
Microsoft Windows 2000** Professional
- Microsoft Loopback Adapter (installable through the network properties on
Windows NT or Windows 2000 Professional)
- For the Information Center (online help):
- One of the following:
- Netscape Navigator for Windows 4.51 or later
- Microsoft Internet Explorer 5.0 or later
- One of the following:
- TCP/IP
- MS Loopback Adapter
- For online books in PDF format, Adobe Acrobat Reader 4.0 or later
For local development
One of the following:
- Microsoft Windows NT Version 4.0 (Service Pack 4 or later required) or
Microsoft Windows 2000 Professional
RELATED REFERENCES
Optional software
This section lists requirements for components of VisualAge PL/I that you
choose to install or use. It also includes
requirements for specific products that operate with VisualAge PL/I.
On the OS/390 host
- For accessing IMS data on an OS/390 host, one of the following:
- IMS/ESA Database Manager Version 6 Release 1 (5655-158), plus the PTF
for APAR PQ07947 (for remote DL/I)
- IMS/ESA Database Manager Version 5 Release 1 (5695-176) plus the PTF
for APAR PQ07950 (for remote DL/I)
- For accessing DB2 data on an OS/390 host, DB2 Universal Database for
OS/390 Version 5, Version 6, or Version 7.
- For accessing VSAM data on an OS/390 host, DFSMS/MVS (included with
OS/390) plus the following APARs: OW20884, OW23571, and OW26104 (which apply
to DFSMS/MVS Version 1.4.0 and below).
On the Windows workstation
- For accessing DB2 data on an OS/390 host:
- Run-time Client for DB2 Universal Database Version 5.2, Version 6.1, or Version 7.1:
- Available from the Web
- Included in DB2 server software
- One of the following:
- DB2 Connect Enterprise Edition (included with DB2 Universal
Developer's Edition Version 5.2, Version 6.1, or Version 7.1)
- DB2 Connect Personal Edition (included with DB2 Personal
Developer's Edition Version 5.2, Version 6.1, or Version 7.1)
- For communications, one or more of the following, as appropriate:
- IBM eNetwork Personal Communications Version 4.2 for Windows (for IMS
and SdU, but not CICS)
- IBM eNetwork Communications Server Version 5.0 for Windows NT (for IMS
and SdU, but not CICS)
- Microsoft SNA Server Version 3.0 or later (for CICS and SdU, but not
IMS)
On the Windows server
- For accessing DB2 data on a LAN, one of the following: (DB2
server requirements)
- DB2 Universal Database Enterprise - Extended Edition Version 5.2, Version 6.1, or Version 7.1
- DB2 Universal Database Enterprise Edition Version 5.2, Version 6.1, or Version 7.1
- DB2 Universal Database Workgroup Edition Version 5.2, Version 6.1, or Version 7.1
- For developing and testing CICS applications, one of the following:
- VisualAge CICS Enterprise Application Development Version 3.1,
included with VisualAge PL/I for Windows NT, Version 2.1 (includes
support for host data types)
- TX Series Version 4.2 for Windows NT (which contains CICS Version 4.2
for Windows NT) (no support for host data types)
- Transaction Server Version 4.0 for Windows NT (which includes CICS
Version 4.0 for Windows NT) plus the PTF1 Refresh Level (no support for
host data types)
On the Windows workstation
- For developing applications that access DB2 data on a LAN, the following:
(DB2 note)
- For developing applications that access CICS data on a LAN, one of the
following:
- VisualAge CICS Enterprise Application Development Version 3.1, which
includes host data type support and is provided with VisualAge PL/I,
Enterprise (recommended).
- TX Series Version 4.2 for Windows NT (which contains CICS Version 4.2
for Windows NT) (no host data type support)
- Transaction Server Version 4.0 for Windows NT (which includes CICS
Version 4.0 for Windows NT) plus the PTF1 Refresh Level (no host data
type support)
One of the following (Packaging note):
- DB2 Universal Developer's Edition Version 5.2, Version 6.1, or Version 7.1
- DB2 Personal Developer's Edition Version 5.2, Version 6.1, or Version 7.1
For more information, refer to one of the following Web addresses:
The following notes are referenced from the software requirements material.
Before embarking, you are strongly urged to get more information from one or
more of the following Web addresses.
- DB2 Universal Developer's Edition Version 7.1 is comprised of the SDK and
the developer licenses and media for the following:
- DB2 Universal Database Enterprise Edition
- DB2 Universal Database Workgroup Edition
- DB2 Universal Database Personal Edition
- DB2 Connect Enterprise Edition
- DB2 Connect Personal Edition
- DB2 Personal Developer's Edition is comprised of the SDK plus the
developer licenses and media for the following:
- DB2 Universal Database Personal Edition
- DB2 Connect Personal Edition
- DB2 Universal Database Enterprise Edition and DB2 Universal Database
Enterprise - Extended Edition include the DB2 Connect Server Support
component. All references to DB2 Connect Enterprise Edition also apply to
the DB2 Connect Server Support component.
- For IPX/SPX, NetBIOS, or TCP/IP, the Windows base operating system
provides support.
- For APPC, Microsoft SNA Server Version 3.0 (or later)
IPX/SPX, NetBIOS, TCP/IP, APPC, or Named Pipes
- For IPX/SPX, NetBIOS, or TCP/IP, the Windows NT base operating system
provides support.
- For APPC connectivity, one of the following:
- IBM eNetwork Communications Server Version 5.0 for Windows NT
- Microsoft SNA Server Version 3.0 (or later), on the LAN
You do not have to install Microsoft SNA Server on the same workstation
as the Run-time Client for DB2 Universal Database Version 6.1.
- Products running on Windows NT support communications with MVS and OS/390,
databases using SNA (APPC), TCP/IP, and MPTN (APPC over TCP/IP) protocols.
These products can support all of these protocols at the same time.
- For direct connection to MVS and OS/390 databases via SNA (APPC), one of
the following communications products is required:
- IBM eNetwork Communications Server Version 5.0 (or later) for Windows NT
- IBM eNetwork Personal Communications Version 4.2 (or later) for Windows
NT
- Microsoft SNA Server Version 3.0 (or later)
- For direct connections to host databases via TCP/IP, the Windows NT base
operating system provides support.
For developing and running production applications on Windows NT:
- TX Series for Windows NT Version 4.3 (provided with IBM WebSphere Application Server
TXSeries for Windows NT Version 3.0)
For developing and testing applications on Windows that are targeted for an
OS/390 host:
- VisualAge CICS Enterprise Application Development (provided with VisualAge
PL/I Version 2.1)
